France e-invoicing 2026: latest guidance before 1 September

The clock hasn’t stopped

We’re inside the final weeks before France’s e-invoicing mandate takes legal effect, and the question worth answering isn’t whether the date will move. It won’t. What’s changed since our July update is that France has closed the gaps businesses were still asking about: which platform rules apply, how invoice routing works, and what happens if something breaks on day one.

That detail arrived through a decree, an implementing order, and an official start-up guide, all published in the second half of July. None of it delays the mandate. All of it changes what “being ready” now means in practice.

The September deadline hasn’t moved

The obligations from 1 September 2026 are unchanged and confirmed on the government’s official e-invoicing hub: every VAT-registered business in France, regardless of size, must be capable of receiving electronic invoices. Large enterprises and entreprises de taille intermédiaire (ETIs, roughly mid-market) must also issue their invoices electronically and transmit transaction and payment data to the tax authority. Small and micro-enterprises get an extra year, coming into scope for issuance and reporting on 1 September 2027.

That two-tier timetable was set by the 2024 Finance Law and hasn’t shifted despite guidance still arriving weeks before go-live. If anything, the late-stage detail signals a government tightening implementation, not loosening the calendar.

What’s changed since our July update

The most significant development is Decree No. 2026-677 of 27 July, paired with an implementing Order published the same day. Together, as PwC’s tax practice sets out, these texts rewrite the tax code provisions behind the reform and retire the last of the old terminology.

Two changes matter most. First, the “partner dematerialisation platform” (PDP) and the “public invoicing portal” (PPF) disappear as separate concepts, replaced by a single figure: the plateforme agréée, or accredited platform (PA). Second, the state’s central directory, the annuaire central, is now formally the addressing backbone of the system. The PPF no longer exchanges invoices itself; it routes them, via the directory, between accredited platforms.

The decree also introduces a formal switching regime for changing platforms, requiring signed customer authorisation, fixed notice periods, and a year of continued receiving service from the old platform after a switch. It also confirms the technical formats that platforms must support: EN16931 and its French extension, across three syntaxes.

What the latest guidance means in practice

Strip away the legal language and three things follow for finance and AP teams.

The accredited platform is now the only door in and out of the system. Businesses don’t connect to government infrastructure directly; they connect to a PA, which talks to the central directory on their behalf. Selecting and onboarding a PA, or confirming your software provider routes through one, remains the single item that gates everything else. Switching platforms later is now a formal, timed process rather than an informal handover, so build in lead time if you’re still mid-selection.

The data requirements are also explicitly phased. A “starter” dataset applies from go-live, including four new mandatory invoice mentions from 1 September 2026: the customer’s SIREN number, the transaction type, the VAT-on-collection option where relevant, and the delivery address where it differs from the billing address. A fuller “target” dataset, with a new price-adjustment field, only becomes mandatory from 1 September 2027. Build for the starter set now, but design for the fuller one so you’re not rebuilding next year.

What happens if everything isn’t ready on day one?

This is where the July article’s language needs revisiting. We described a “grace period” running to the end of 2026. The DGFiP’s official start-up guide and economie.gouv.fr describe something narrower: an approach of “tolerance and good faith,” not a suspended obligation.

The guide sets out three principles, and the third is the one worth sitting with. The legal calendar stands. Invoices that still arrive by email, PDF or paper after 1 September shouldn’t be rejected outright if they reflect a genuine transaction: that’s the continuity principle, aimed at preventing payment gridlock. But continuity is explicitly not an exemption. Businesses whose invoices miss the electronic route are expected to keep trying, or regularise promptly, and be able to show it.

Concretely, DGFiP won’t apply sanctions automatically to businesses hitting genuine, documented implementation problems while actively working through them: a failed integration, a platform outage, an unidentifiable recipient in the directory. It won’t extend the same tolerance to inertia, avoidance, or durable refusal to engage. The distinguishing factor is evidence, meaning dated correspondence with your provider, records of the difficulty, and a visible trajectory toward compliance. That’s a more precise picture than a flat extension to 31 December. There’s no blanket amnesty date, just a case-by-case standard tied to whether you can prove you’re genuinely trying.

What finance teams should confirm now

With weeks rather than months remaining, the checklist has narrowed to proof points:

• Your accredited platform is selected, contracted, and connected, not just shortlisted.
• Your ability to receive electronic invoices is tested end to end, including the four new mandatory mentions.
• If you’re subject to the issuing obligation from September, outbound workflows are tested against real supplier and customer data, not sample files.
• Your ERP and AP integrations correctly map the “starter” dataset, with a plan for extending to the “target” dataset ahead of 2027.
• You know what to do if a platform is unreachable, an invoice is rejected, or a recipient can’t be identified in the directory, and who owns that fix.
• Responsibilities between your business, your software provider, and your accredited platform are documented, particularly for outages and regularisation.
• You have a way to log implementation difficulties, in case you need to evidence a compliance trajectory to DGFiP.

From preparation to live operation

The story of the past six weeks isn’t that France softened its mandate. It’s that France finished the operating manual for it, weeks before go-live. The decree, the order, and the start-up guide point the same direction: less ambiguity about the rules, more expectation that businesses can show their processes hold up under them.

That shifts what “readiness” means from here. It’s no longer about whether you’ve read the requirements correctly, but whether an invoice can move from your system, through your platform, into your counterparty’s, and out the other side without a person intervening. It’s also about whether, when something goes wrong, you can show it’s the exception, not the norm. Get that operational resilience right, and September stops being a compliance event and becomes what it was always meant to be: a faster, more reliable way of getting paid.