France's e-invoicing mandate starts 1 September and carrier invoices are in scope

What the mandate changes for logistics, and what stays with finance

France is making structured electronic invoicing compulsory from 1 September 2026, and your carrier invoices are part of it. From that date, every VAT-registered business in France has to be able to receive a structured electronic invoice, and large and mid-sized companies have to issue them too. Your carriers are covered by this. So from September, a growing share of the carrier invoices you receive in France arrive as machine-readable data instead of a PDF that someone opens by hand.

Once that flow begins, your team can check a structured invoice against the shipment it bills for. Doing that by hand from a PDF rarely repaid the effort. Whether that check works at all depends on data your own systems wrote months earlier, when the shipment was booked.

What changes on 1 September 2026

From 1 September 2026, all businesses subject to VAT in France must be able to receive structured e-invoices through an approved platform. An approved platform, a plateforme agréée, is a state-certified provider that invoices route through instead of traveling directly between you and your supplier. Large enterprises and mid-sized companies must also issue e-invoices and meet e-reporting obligations from that date. Small and micro businesses have until 1 September 2027 to start issuing. No sector gets a carve-out, so carriers, freight forwarders and shippers are all covered.

On 11 July 2026, France's public accounts minister David Amiel confirmed the deployment timetable and set out how it will be policed at the start. He said there will be no sanctions at launch for businesses acting in good faith that hit genuine implementation problems and are doing the work to fix them. He attached no end date to that tolerance. The tolerance governs enforcement; the start date is unchanged.

Plan on that basis: 1 September is the date, and you will be running two invoice formats side by side well into 2027.

Who is in scope, and when

Scope follows VAT registration, French establishment and company size.

• 1 September 2026: all VAT-registered businesses must be able to receive structured e-invoices. Large enterprises and mid-sized companies (ETIs, entreprises de taille intermédiaire) must also issue them and comply with e-reporting.
• 1 September 2027: small and micro businesses must issue.

Three invoice formats are accepted: Factur-X, UBL and CII.

E-invoicing covers domestic business-to-business transactions where both parties are established in France. Cross-border and export transactions fall under e-reporting instead. E-reporting sends transaction and payment data to the tax administration rather than routing an invoice to your counterparty, so it is the limb that catches most shippers moving goods across a border.

Reporting from The Invoicing Hub in July 2026, citing figures from the French tax administration and the state's financial IT agency, covers take-up in the voluntary pilot only. About 3,800 entities had issued e-invoices through the pilot and 3,400 had received them, against roughly 11 million entities eventually in scope. Around 25 of nearly 150 registered platforms were actively transmitting. Just 9 large companies and 37 mid-sized companies had issued anything through it, and those are the businesses obligated from day one. Plenty of companies will be building without ever touching the pilot, so read these as schedule risk rather than a readiness count. Expect an uneven inbound invoice flow through the opening months.

The mandate joins the other rules reshaping European delivery this year. We covered the full set in our guide to EU ecommerce regulations in 2026.

Will all my carriers send structured invoices from September?

No, and the gap will likely unfold for a full year.

• Carriers that qualify as large enterprises or ETIs must issue structured e-invoices from 1 September 2026, and your major national carriers will fall into those categories.

• Your smaller regional carriers, the local pallet operator, the specialist two-person delivery firm, the courier you use for one lane, are likely to fall under the SME threshold, though it is worth confirming each carrier's classification directly. They must be able to receive from 1 September 2026 like everyone else. They are not obligated to issue until 1 September 2027.

So for a full year you may receive structured invoices from some carriers and PDFs from others, covering the same week and the same lanes, sometimes the same customer. Both paths have to work and also reconcile into one view of transport spend, because otherwise the structured invoices become a second system to check rather than a replacement for one. Your team will scrutinize whichever format the automation covers while errors will accumulate in the other one.

Once the structured flow runs, the invoices you can check automatically will start generating queries. Those queries go to carriers who are themselves in the first months of a new obligation. Agree a query process with your major French carriers before September, so that who reviews what, and how fast a correction comes back, is settled while there is still time. The structured feed lets you query a single shipment rather than a monthly statement, so build the process at that level.

On penalties: the ministerial position is that good-faith businesses making real progress will not be sanctioned at launch. The opening period is about getting onto an approved platform and being able to show the work. Your commercial exposure in the first year is still where it always was, in freight charges that nobody had the time or the data to question. The opening period is about getting onto an approved platform and being able to show the work.

What a structured carrier invoice lets an operations team do

A structured invoice arrives as a set of readable fields your systems can parse. Once a carrier invoice line comes through that way, your team can compare it against the shipment it bills for without anyone reading a document. Weight, service, zone, surcharge and the applied rate all become checkable fields.

Disputes cluster on those fields: a surcharge the contract does not support, a weight break rounded the wrong way, a residential fee on a commercial address, a fuel index from the wrong month. Checking them line by line has been expensive enough that many go unchecked.

JYSK's Head of Logistics stated the goal long before these new regulations:

"We are also looking to use invoice verification so we can spot any deviations between our rates and the carriers’ pricing."

JYSK runs shipping across Sweden, Denmark, Poland and Bulgaria, so that deviation check spans four carrier bases and four sets of rates. The French mandate solves the invoice half of it, because from September the invoice arrives as data.

Why the invoice alone is not enough

The other half is your own booking data.

A structured invoice line is only checkable if you can find the shipment it refers to. Finding it depends on fields your systems wrote months before the invoice arrived: the shipment reference on the booking, the service code, the declared weight and dimensions, the cost center it was charged to. If the reference on the carrier's invoice line does not resolve to a booking in your system, the invoice is structured and still unusable. You have swapped a PDF nobody checks for a data feed nobody can join. You can start on this today, without waiting for finance to choose a platform.

The good news is that nShift Ship calculates freight rates from your carrier agreements at the point of booking, using distance, weight, geographical zones and index prices. Alternatively, nShift Transsmart's tariff engine produces cost prediction from the transport contracts you hold with each carrier.

Either way, the shipment leaves the warehouse with an expected cost attached, generated from the rate you negotiated, and that is what the structured invoice line gets measured against. Without it, a machine-readable invoice tells you what you were charged with no way to test whether the charge was right.

A clean reference means one identifier traveling from your order system to the booking, onto the label, and back on the carrier's invoice line, in the format that carrier actually returns. Carriers vary in how they handle that field, so confirm it per carrier. Reference cleanup is slow and unglamorous, and it decides whether you can join the invoice file to your shipment records or only add it up.

Embacollage, a packaging service supporting more than 220 retail brands, runs freight and fulfillment through one connected flow. It reports clear shipping cost visibility and fewer manual freight steps. Its team reads transport cost from the booking record without assembling it at month end.

Give cost center allocation its own attention, because it tends to fall to finance to sort out later. Set the cost center at booking and transport spend can be read by market, channel, warehouse or customer, without anyone rebuilding it from carrier statements at month end. Leave it unset and a structured invoice gives you an accurate total with no way to attribute it. Third-party billing, where a shipment's cost is charged to the receiving party, needs the same discipline for the same reason.

Before September, check whether the references leaving your shipping system resolve cleanly to a booking. That cleanup runs longer than platform procurement, so start it first.

Does this replace my customs paperwork?

No. The French mandate governs VAT documentation, and cross-border shippers are the readers most likely to take that too broadly.

Follow the scope, and it separates visibly:

• the e-invoicing limb covers domestic business-to-business transactions where both parties are established in France.

• export and cross-border transactions fall under e-reporting instead, and e-reporting does not cover imports of goods either, on the basis that customs channels already collect that data. The commercial invoice you attach to a shipment leaving the EU answers to customs. Nothing in the mandate's scope reaches it.

Read that as the scope logic rather than a published ruling: check your own position with your customs broker or tax adviser before changing any export process.

Customs documentation and VAT invoicing draw on the same underlying data. Transsmart's paperless invoicing sends the required customs documentation for non-EU shipments electronically, so the declaration is not waiting on a paper copy traveling with the freight. The values, weights and commodity details behind that are the same ones a VAT e-invoice and a carrier invoice line get checked against, so the booking record you clean for one serves all three.

For the wider customs picture, our guides to EU customs changes and cross-border shipping cover what is changing at the border this year.

What the logistics team should do before September

Your finance team owns platform selection, format mapping and e-reporting. That work is well documented elsewhere and is their project to own.

The operations work below is measurable before the deadline, which makes it the part of the mandate you can report progress on, whichever platform finance picks.

Confirm your French carriers' issuing dates

Ask each carrier when they will start issuing structured invoices and in which format. Large carriers are obligated from September. Smaller ones may be a year behind, and some will move early. You need that map before you can plan the flow.

Audit the reference field 

Take last month's carrier invoices and check what proportion of lines carry a reference that resolves cleanly to a booking in your system. You can measure this in a week. It tells you more about your September readiness than your platform contract does.

Fix reference discipline at the source 

Where references are missing, inconsistent across carriers, or entered by hand, correct them in the booking configuration, which sits upstream of every spreadsheet that follows. Cost centers and third-party billing details belong in the same pass.

Make sure an expected cost exists per shipment

Rate calculation from carrier agreements at booking gives every invoice line something to be checked against. If shipments leave without a predicted cost, the mandate will not fill that gap.

Plan for both formats through to September 2027

Structured and unstructured invoices need to reconcile into a single spend report, because you will be receiving both for a year.

Keep customs documentation on its own track

It stays outside the e-invoicing scope and keeps its own obligations. Feed it from the same shipment data and it gets easier anyway.

A single record with three distinct obligations

Your carbon reporting draws weight and distance from the shipment record. For cross-border movements, your customs team files values and commodity detail from the same place. E-invoicing adds one more requirement to that record: a reference that ties an invoice line back to what actually shipped. 

Shippers who already hold that record face a September that is mostly a mapping exercise, but for everyone else this becomes a data project with a deadline.

Run booking, carrier connectivity and transport data through one delivery data layer and the shipment record carries what both the invoice check and the customs file need, whether you are moving parcels or managing freight and pallets through transport management. Fix the reference field now and the September invoices arrive somewhere they can be checked.

Want to see what your shipment data could be doing before September? Talk to us about your delivery operation.