France E-Invoicing Mandate Takes Effect Sept 1

DGFiP holds the line on September 1, no delay this time

France's tax administration confirmed at its annual E-Invoicing Day on May 7, 2026 that the France e-invoicing mandate will go live on September 1 as planned, with a soft landing on enforcement. DGFiP Director General Amélie Verdier stated that no penalties will be imposed from 1 September 2026, as there will first be contact with businesses before any enforcement can occur. That's the headline EDI teams with French trading partners need to register right now, three weeks out: the date is real, the fines are real, but day-one enforcement is not the risk. Readiness is.

The runway has already been tested. On February 24, the DGFiP and AIFE officially launched the live pilot phase, with real transactions beginning February 27, and by early spring around 60,000 businesses were already involved out of 600,000 companies listed in the central directory. That pilot window closes at the end of August. If your organization hasn't pushed a single real invoice through it yet, you're behind most of your peer group, not ahead of the deadline.

The deadline table: what applies to whom, and when

The mandate is size-tiered and splits into two separate obligations that get conflated constantly: e-invoicing (structured domestic B2B invoices) and e-reporting (B2C and cross-border transaction data). They run on different clocks.

Note the legal safety valve: these dates may be postponed by decree to 1 December 2026 and 1 December 2027, respectively, without new legislation. That's a real contingency, not just a rumor — and it's part of why speculation about a delay keeps circulating even though DGFiP's public position hasn't moved.

Where EDI actually fits, and where it doesn't

Here's the detail most EDI teams miss: your existing EDIFACT or X12 INVOIC flow with a French customer doesn't get replaced by the mandate. It gets wrapped. France's model isn't peer-to-peer transmission anymore — it's a five-corner Continuous Transaction Control (CTC) architecture where every invoice routes through a certified Plateforme Agréée (PA), which validates it, reports the transaction data to DGFiP, and forwards it to the recipient's own PA.

Non-standard syntaxes survive, but only inside that structure. As one vendor white paper puts it plainly, non-stipulated syntaxes such as EDIFACT remain possible on a voluntary basis via a PA, with conversion to one of the three fiscally recognized formats — Factur-X, UBL 2.1, or CII — before the tax administration ever sees it. EDICOM frames the mechanism the same way: only Approved Platforms will have the possibility to send other types of formats like EDIFACT, as long as both suppliers and clients use an Approved Platform. Send an invoice directly to the PPF portal instead of through a PA, and only the three base formats are accepted at all.

Practically: your VAN or AS2 connection to a French partner doesn't go away, but it now terminates at a PA instead of at the partner directly. If you're routing INVOIC transactions today over a point-to-point EDI connection with no PA in the chain, that connection stops being compliant for domestic B2B French invoices once the size-appropriate deadline hits.

What changes for your team, and by when

Four things need to happen before September 1, regardless of company size, because reception is mandatory for everyone from day one:

• Confirm your PA registration and run at least one live transaction through the pilot rails before it closes at the end of August — this is your only pre-production test of the full lifecycle.
• Map existing EDIFACT/X12 invoice fields against the AFNOR XP Z12-012 semantic model now, since your PA will convert to Factur-X, UBL, or CII regardless of what syntax you send.
• Separate your e-invoicing project (domestic B2B) from your e-reporting project (B2C, cross-border) — they carry different formats, different deadlines, and in the case of non-established taxpayers, a full year's difference in enforcement date.
• Confirm reception capability even if your organization is a small supplier not yet required to issue — every VAT-registered business must receive from a PA on day one.

The PA and vendor landscape is moving fast

The provider side isn't waiting. OpenText was confirmed among the first wave of certified platforms, and its own team notes on January 15, 2026, the DGFiP published the first official list of definitively certified Approved Platforms, just over 100 platforms. TrueCommerce has been building out CTC capability country by country, with Gustav Lantz, product manager for e-invoicing and continuous transaction controls at TrueCommerce, describing the e-invoicing obligation as the beginning of a new era of digital compliance for companies across various countries. EDICOM, ecosio, and SEEBURGER are all positioning as PA-adjacent EDI providers that can carry your existing EDIFACT flows through the conversion layer rather than forcing a rip-and-replace. If you're also managing carrier and freight EDI alongside this — separate from invoice compliance but frequently tangled with the same VAN infrastructure — platforms like Cargoson are part of a broader pattern of transport connectivity tools absorbing document exchange that used to sit with standalone EDI VANs.

Three weeks left: what to do this week

Verify your PA contract is signed, not just quoted. Push one real invoice through the pilot environment before it closes at the end of August — don't wait for a production failure to discover a mapping gap. Confirm your AFNOR XP Z12-012/014 field mapping against your current EDIFACT INVOIC segments. And document a good-faith compliance roadmap you can show DGFiP if contacted, given the administration's own stated posture of contact before enforcement. The deadline isn't moving. Your mapping work should already be underway.