France Went Live: What the First Week of the Mandate Is Teaching Everyone
France did not blink. The 1 September date held, the legal option to push to December went unused, and the France e-invoicing go-live happened on schedule.
What happened next is more interesting than the date itself. Within hours of the switch, the government made an announcement that reframed the whole first phase and the first week of live traffic exposed which parts of the French model were ready and which were not.
Here is what the go-live is teaching everyone, including the countries going live after France.
What actually changed on 1 September
Every business established in France and subject to French VAT must now be able to receive structured e-invoices through an accredited platform, a Plateforme Agréée (PA). Large enterprises and ETIs must also issue them and meet e-reporting obligations. SMEs and micro-enterprises follow in September 2027.
That is the mechanics. We covered the architecture in detail in our France 2026 e-invoicing mandate guide. The rest of this post is about what week one revealed.
Lesson 1: "No penalties in 2026" is not "no obligation in 2026"
The headline from go-live day was the Ministry's confirmation that no penalties would be applied to businesses during the remainder of 2026. The minister described 1 September as the kick-off rather than a cut-off.
Read carefully, that is a communication commitment, not a change in law. The penalty provisions remain in force. The obligation to receive through a PA applies from 1 September regardless.
What the tolerance actually rewards
The DGFiP's start-up guidance draws a line between two groups: businesses hitting genuine, documented implementation problems while working through them, and businesses doing nothing.
The first group is tolerated. The second is not.
The practical consequence is that evidence matters more than readiness right now. Dated correspondence with your platform provider, a log of technical failures, a visible trajectory that file is what protects you in a later audit of this period. If your finance team is not keeping one, start today.
Lesson 2: The directory is the bottleneck, not the format
Most implementation projects spent the last year on formats: Factur-X, UBL, CII. Formats turned out to be the easy part.
The routing register the annuaire is where week one hurt. An invoice can be perfectly valid and go nowhere because the recipient has no reception address published, or no platform declared against their SIREN.
Directory enrichment was never going to be complete by 1 September. Entities in several sectors are absent entirely, and newly created companies waiting on a SIREN cannot be routed to at all.
What this means in practice
Do not assume a trading partner is routable because they are in scope. Test the actual lookup for your top customers and suppliers, one by one. A failed routing test in September is an inconvenience. The same failure in December is a cash flow problem.
Lesson 3: Platforms face a harder line than their customers
There is an asymmetry worth noticing. Businesses got a penalty-free runway. Accredited platforms did not.
Platforms must report their cybersecurity posture to the DGFiP, flag incidents immediately, and complete penetration testing this autumn. Falling short risks suspension of operations.
If your platform is suspended, your compliance goes with it. Platform selection is now a continuity question, not just a pricing one.
Lesson 4: Reception is where teams got hurt first
Issuance had a project plan behind it. Reception often did not.
Structured invoices started arriving at accounts payable teams that had built nothing to consume them. The invoice was compliant, the sender was compliant, and the document sat outside the ERP.
Two distinctions caused the most confusion in week one:
Technical rejection is a validation, format or routing failure. Correct it and resubmit.
Buyer refusal is a lifecycle event with commercial meaning. It should not trigger an automatic credit note.
Treating these as the same thing produces duplicate documents and reconciliation work that lasts for months. This is an ERP integration problem, not a platform problem the same gap we described for Business Central AP teams and for Danish companies trading into France.
What the France e-invoicing go-live signals for what comes next
France has set a pattern other markets will copy: hold the legal date, soften the enforcement, absorb the readiness gap in the first quarter of operation.
That pattern is comfortable for tax authorities and dangerous for finance teams, because the commercial penalty arrives long before the regulatory one. An invoice that cannot be routed does not get paid. No fine is needed to damage a cash position.
Poland, Germany and Norway all have obligations landing in the next four months. The France e-invoicing go-live suggests where to put the effort: directory registration and reception capability first, format perfection second.
FAQ
Did France delay the mandate? No. The 1 September 2026 date applied in full. The legal option to defer to 1 December was not used.
Are penalties really waived for 2026? The Ministry has said no penalties will be applied during 2026. The underlying penalty rules remain in law, and businesses are expected to document a genuine compliance trajectory. Confirm the current position with your tax adviser before relying on it.
What happens if a trading partner is not in the annuaire? The invoice cannot be routed to them electronically. Business continuity guidance allows alternative channels temporarily while the directory entry is resolved, and the invoice remains commercially valid.
Does this apply to companies outside France? It depends on establishment rather than nationality. A French subsidiary or branch is in full scope. French VAT registration without a fixed establishment brings e-reporting obligations rather than e-invoicing ones.
What changes on 1 January 2027? The 2026 tolerance window closes. Enforcement of the existing rules becomes the default rather than the exception.
Getting the reception side right
If invoices are arriving in France and your ERP cannot consume them, the gap is integration, not accounting software.
HubBroker connects Dynamics 365, SAP Business One, e-conomic, Uniconta and other systems to e-invoicing infrastructure as a layer on top of what you already run format conversion, routing, status handling and exception management, without replacing your ERP. You can see how that fits in our e-invoicing solution overview and ERP integration services.
Working out where your French flows break? Talk to our integration team.