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 has gone live as of 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.

We've been running this at Solvimon with customers for months. Here's how the reform works, where teams get stuck, and a checklist you can run against your own stack to see whether you're compliant or just feel compliant.

What is the E-invoicing reform about?

France is replacing paper and PDF invoices for domestic B2B transactions with a structured electronic system. "Structured" is the word doing the work. A PDF emailed to a customer doesn't count. The invoice must be a machine-readable 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 are then routeD through accredited private platforms (Plateformes Agréées, aka PAs) that validate, transmit, and track each 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 DGFiP's technical standards now document 45 different use cases (version 1.4, June 2026), such as self-billing, deposits, credit notes, invoices to buyers not yet in the directory. Most billing systems built before 2025 handle maybe a third of them natively.

The timeline

The reception obligation is the one people underestimate. If your suppliers are large French enterprises, they're sending you structured e-invoices now. Your accounts payable side needs to receive, validate, and ingest structured files, and it needs a registered reception address in the central directory (the Annuaire), or those invoices go nowhere.

What the DGFiP's start-up guidance changes in practice

In July 2026 the tax authority published a practical guide (29 questions, six themes) that reads like a soft landing for teams making a documented effort. The rules worth knowing:

Invoices sent by email, PDF, or paper during the start-up period remain valid invoices. They don't stop being a compliance gap, but they don't void the invoice either.

If your PA has an outage or your customer's platform fails, that's not automatically your violation, provided you document it.

Penalties for non-compliant reception come with a three-month formal notice before they bite. Penalties for issuance failures are per invoice. E-reporting penalties (CGI articles 1737, 1788 D) apply in full from day one, with no grace at all!

Duplicate invoices are the operational risk everyone flags at launch. The guidance says: flag them, don't reject them. Rejection is a lifecycle status with legal weight, and using it loosely creates disputes you'll spend Q4 cleaning up.

What compliance requires

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. A billing system that natively produces UBL, CII, or Factur-X also produces cleaner data for your own reporting and fewer manual reconciliation steps. The compliance requirement and the operational upgrade point the same way.

Connection to an accredited platform. You don't connect to the government portal. You connect to a PA, which handles validation, routing, and regulatory reporting. Once that integration is live, delivery is automated and tracked end to end.

SIREN and SIRET on every French customer record. The network routes invoices via electronic addresses built from these identifiers. FNFE-MPE's go-live checklist recommends one reception address per SIREN rather than multiplying them. Collecting the identifiers from your customer base is a one-time enrichment job... for accounts onboarded without those fields, it takes a few weeks longer than anyone budgets.

Lifecycle status handling. Invoices move through defined statuses: Deposited, Rejected, Refused, Cashed, and a handful of others. Your PA sends them back in real time. For AR teams this replaces manual follow-up with structured workflow. A rejected invoice surfaces the same day instead of ageing silently for 60.

Structured archiving. E-invoices must be stored in their original structured format for the legal retention period. If your archive already handles structured documents, it's a configuration change. If it only stores PDFs, it's a project.

E-reporting streams. Separate from the invoice itself: transaction and payment data for B2C, cross-border, and non-domestic B2B flows. This is the piece with no grace period, and it's the piece most teams discover last.

What you need to know

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 PA transmits data to the PPF and generates a Deposited status marked NON_TRANSMISE. You're compliant. The customer can't demand a PDF workaround (though during the start-up period you can send one alongside). When they set up a PA, your platform replays the transmission so the invoice arrives through the regulated network.

A buyer isn't in the Annuaire. If a VAT-registered customer is missing from the directory because of administrative delays, you can temporarily treat them as a non-taxable person and submit via the B2C e-reporting flow. Neither side faces penalties, provided the reporting data is filed correctly.

Credit notes and corrections. They must reference the original invoice number and generate their own lifecycle events. If your billing system already handles corrections as structured documents with proper references, you're done. If credit notes are free-text PDFs someone types up in Finance, you're not.

Duplicates. A supplier resends an invoice through a second channel, or two PAs both deliver it. Your AP process needs a rule for this before it happens, because the default human reaction (reject the second one) is the wrong lifecycle move.

The checklist

Tick what you can prove, not what you've planned. Each item has a test you can run today.

Everyone established in France (reception, live now)

• You have a signed contract with an accredited PA for reception. Test: name the PA and the contract date.

• Your SIREN is registered in the Annuaire with the correct reception address. Test: look yourself up in the directory. If a large supplier can't find you, they'll issue with NON_TRANSMISE and you'll never see the invoice.

• You use one reception address per SIREN unless there's a documented reason for more.

• AP can ingest UBL, CII, and Factur-X without a human converting them to PDF first. Test: send yourself a Factur-X test invoice and follow it to the ledger.

• You have a written rule for duplicate invoices (flag, don't reject).

• Someone owns lifecycle statuses on the buy side and knows when "Refused" is warranted and when it isn't.

• Inbound e-invoices are archived in their original structured format, not as rendered PDFs.

Large enterprises and ETIs (issuing and e-reporting, live now)

• Every domestic B2B invoice leaves your system as UBL, CII, or Factur-X. Test: pull last week's invoices and count the ones that went out as plain PDF.

• Your issuing PA is connected and the integration has been tested end to end: issued, routed, received, statuses returned.

• Every French B2B customer record has SIREN and SIRET. Test: run the query. Anything under 100% is a routing failure waiting to happen.

• Electronic address fields (BT-34 and friends) are populated correctly on outbound invoices and status messages.

• You process inbound lifecycle statuses automatically. Test: a Rejected status triggers something in your AR workflow within the hour, not when someone checks the portal on Friday.

• Credit notes and corrections reference the original invoice number and travel through the same PA flow.

• The NON_TRANSMISE case is handled: you know what happens when a customer isn't on a PA yet, and you can replay later.

• E-reporting for B2C, cross-border, and non-domestic B2B is live. Test: name the reporting frequency you're on and show the last submission.

• Outbound e-invoices are archived in original structured format for the retention period.

• You keep a log of start-up incidents (PA outages, customer-side failures, fallback invoices sent). This is what "documented effort" means if the DGFiP asks.

SMEs and micro-enterprises (issuing from September 2027)

Reception applies to you already, so run the first block first. Then, with 12 months of runway:

• You've picked an issuing PA, or confirmed your billing vendor is one (or connects to one).

• You know which of your invoices are domestic B2B (in scope) versus B2C, cross-border, or B2G (different flows).

• SIREN/SIRET enrichment on your customer base has started. Test: what percentage is complete today?

• Your billing system can produce at least one of the three formats now, even if you're not sending them yet.

• You've sent a test invoice through the PA-to-PA flow to a friendly customer and watched the statuses come back.

• Credit notes are structured documents with references, not free-text PDFs.

• If you're replacing your billing system anyway, the replacement project and the compliance project are one project, not two.

If you ticked everything in your block, good!

If you ticked most of it, the gaps are the SIREN enrichment and the e-reporting stream, probably.

Why this is bigger than France

Germany's issuing obligation phases in from 2027. ViDA brings structured e-invoicing and digital reporting across the EU from 2028. Belgium is live already. The French model (accredited platforms, lifecycle statuses, e-reporting alongside the invoice) is the template the rest of the bloc is converging on.

So the question for a finance team is whether to build a French compliance bolt-on or a billing layer that emits structured, routable invoice data by default. The second one is more work this quarter and much less work over the next three years.

France is just one, more countries are coming

Germany's issuing obligation phases in from 2027. ViDA brings structured e-invoicing and digital reporting across the EU from 2028. Belgium is live already. The French model (accredited platforms, lifecycle statuses, e-reporting alongside the invoice) is the template the rest of the EU is very likely converging on.

So the question for a finance team is whether to build a French compliance bolt-on or a billing layer that emits structured, routable invoice data by default. The second one is more work this quarter and much less work over the next three years.

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 see our France e-invoicing glossary entry. For the broader global mandate landscape, see What is E-Invoicing.

Related

• Solvimon automated invoicing. Compliant invoices generated straight from billing data.

• Revenue recognition. When revenue can be booked, and why the timing rules matter.