

Arnon Shimoni
✓ Expert opinion
France's e-invoicing reform is the most significant structural change to B2B billing in Europe in a decade. For finance and billing teams, it's also a genuine upgrade: cleaner AR workflows, automated invoice lifecycle tracking, real-time status visibility, and a billing stack ready for the broader EU wave that follows.
The mandate goes live September 1, 2026. Large and intermediate-sized enterprises established in France begin issuing e-invoices and reporting transaction data from that date. SMEs and micro-enterprises follow September 1, 2027. One deadline applies to everyone from September 1, 2026 regardless of size: all French-established businesses must be able to receive e-invoices.
Solvimon is already live for French mandate compliance. We've been working with customers on this for months and have the infrastructure in place. Here's how the reform works and how we get you ready.
What the Reform Actually Is
France is replacing paper and PDF invoices for domestic B2B transactions with a structured electronic system. "Structured" is the key word. A PDF emailed to a customer is not compliant. The invoice must be a machine-readable data file in one of three accepted formats:
UBL (Universal Business Language)
CII (Cross Industry Invoice)
Factur-X: a hybrid format embedding structured XML inside a human-readable PDF
These invoices don't travel by email. They route through a network of accredited private platforms (Plateformes Agréées, or PAs) that validate, transmit, and track every invoice through a defined lifecycle.
The architecture is called the 5-corner model. Your invoice travels from your accredited platform to your customer's accredited platform. At the same time, your platform sends a regulatory data subset to the government's Public Invoice Portal (PPF). The tax authority gets the fields it needs for VAT monitoring. Your customer gets the invoice. You stay compliant.
The Timeline
Date | Who | What |
|---|---|---|
September 1, 2026 | All French-established businesses | Must be able to receive e-invoices |
September 1, 2026 | Large and intermediate-sized enterprises | Must issue e-invoices and report transaction data to DGFiP |
September 1, 2027 | SMEs and micro-enterprises | Must issue e-invoices and report transaction data |
The reception obligation is worth flagging for teams on the buy side: if your suppliers are large French enterprises, they'll be sending you structured e-invoices from September 2026. Your accounts payable systems need to be ready to receive, validate, and ingest structured invoice files. This is a good moment to audit both sides of the flow.
What Compliance Requires, and What It Unlocks
Getting compliant involves changes at several layers of your billing stack. The good news: most of these changes are improvements you'd want anyway.
Structured invoice output. Compliant invoices must be machine-readable data files, not PDFs. A billing system that natively produces UBL, CII, or Factur-X also produces cleaner data for your own reporting, faster processing for your customers, and fewer manual reconciliation steps. The compliance requirement and the operational upgrade point in the same direction.
Connection to an accredited platform. You don't connect directly to the government portal. You connect to a PA (Plateforme Agréée), which handles validation, routing, and regulatory reporting. Once that integration is live, invoice delivery is automated and tracked end to end.
SIREN and SIRET numbers on customer records. The network routes invoices via electronic addresses built from these identifiers. Collecting them from your French B2B customer base is mostly a one-time enrichment exercise, and it gives your customer data a level of precision that's useful well beyond compliance.
Lifecycle status callbacks. Under the reform, invoices move through defined statuses: Deposited, Rejected, Refused, Cashed. Your platform sends these back in real time. For AR teams, this replaces manual invoice follow-up with structured, automated workflow. A rejected invoice surfaces immediately rather than ageing silently.
Structured archiving. E-invoices must be stored in their original structured format for the legally required period. If your archiving already handles structured documents, this is a configuration change. If not, it's worth addressing as part of the broader compliance build.
Operational Scenarios Worth Knowing
The reform anticipates edge cases and has clear rules for each. Knowing them in advance means no surprises in September.
Your customer hasn't set up their platform yet. You're still obligated to issue the e-invoice. Your platform transmits data to the PPF and generates a "Deposited" status marked NON_TRANSMISE. You remain compliant. The customer can't demand a PDF workaround. If they set up a PA quickly, your platform can replay the transmission so the invoice arrives properly through the regulated network.
A buyer isn't in the Central Directory. If a VAT-registered customer is absent from the Directory due to administrative delays or technical issues, you can temporarily treat them as a non-taxable person and submit via the B2C e-reporting flow. Neither party faces penalties, provided the reporting data is correctly filed.
Credit notes and corrections. These must reference the original invoice number and generate their own lifecycle events. If your billing system handles corrections as structured documents with proper references, the reform's requirements are already met.
Why Now Is the Right Time to Get This Right
The work that benefits most from lead time isn't technical. It's operational.
Collecting SIREN and SIRET numbers from your existing French customer base is mostly an enrichment exercise, but it's one that takes a few weeks for accounts that were onboarded without those fields. Starting now means it's done before you need it, not while you're trying to go live.
Testing the full PA-to-PA flow (invoice issued, routed, received, statuses returned) is also smoother with time on your side. Validation errors that surface during testing are learning opportunities. The same errors in September are delays.
And for teams considering a broader billing infrastructure upgrade alongside the compliance work, combining the two projects is more efficient than running them sequentially. The structured data requirements of the French reform are a natural forcing function for building a billing stack that handles the EU's broader mandate wave: Germany from 2027, ViDA across the bloc from 2028.
How Solvimon Supports French E-Invoicing Compliance
Solvimon is built for exactly this: structured invoice generation in compliant formats, accredited platform connectivity, electronic address storage and routing, lifecycle status processing, and the data architecture to handle the reform's requirements without retrofitting a system that wasn't designed for them.
We're already working with customers on French mandate readiness. If you want to map your current billing infrastructure against what September requires, talk to our team. We'll tell you where you stand and what needs to move.
For the full technical architecture (the 5-corner model, the Central Directory, the mandatory lifecycle statuses), see our France e-invoicing glossary entry. For the broader global mandate landscape, see What is E-Invoicing.
