France E-Invoicing 2026: What Your Business Needs Before September

France is about to flip the switch on mandatory e-invoicing. Starting September 1, 2026, large enterprises will be required to both send and receive structured electronic invoices for domestic B2B transactions. Medium and small businesses follow in 2027 and 2028.

If you've been watching the EU e-invoicing landscape, you know every country does this differently. Germany went with a reception-first approach. Belgium jumped straight to full Peppol. France? France built its own ecosystem around certified platforms and a government portal, and then rewrote the rules halfway through.

Here's what the current plan looks like, what formats you need to support, and what to do before September.

The Timeline: Three Phases

France's original plan was to launch in July 2024. That got pushed back — twice. The current timeline, confirmed by the Direction Générale des Finances Publiques (DGFiP), is:

Phase 1 — September 1, 2026

• Large enterprises (over 5,000 employees or €1.5B revenue) must send and receive structured e-invoices
• All businesses, regardless of size, must be able to receive e-invoices through a registered platform

Phase 2 — September 1, 2027

• Medium-sized enterprises (250–4,999 employees or €50M–€1.5B revenue) must send structured e-invoices

Phase 3 — September 1, 2028

• Small and micro enterprises must send structured e-invoices
• Full mandate for all VAT-registered businesses

The company size thresholds follow the standard French legal definitions. If you're unsure where your organization falls, check your most recent annual report — the criteria are cumulative (employees or revenue).

The PDP Model: How France Differs from Everyone Else

Most EU countries let businesses exchange invoices however they want, as long as the format is correct. France took a different approach. Every e-invoice must flow through one of two types of certified intermediaries:

Plateformes de Dématérialisation Partenaires (PDPs) are private platforms registered and certified by the French tax authority. They handle invoice routing between businesses and report transaction data to the government. Think of them as certified gateways — your invoices go through a PDP to reach your buyer, and the PDP simultaneously reports the data to the government's system.

Portail Public de Facturation (PPF) is the government's own platform. Originally it was planned as a central hub that all invoices would flow through. After the redesign, the PPF acts more as a directory and fallback — it maintains the business registry and handles cases where businesses haven't registered with a PDP.

In practice, most businesses will work through a PDP. Your ERP vendor, your accounting software, or a dedicated e-invoicing provider will likely become (or partner with) a certified PDP.

E-Reporting: The Tax Transparency Layer

France's system also includes "e-reporting" — a requirement to report transaction data for invoices that fall outside the B2B e-invoicing mandate (B2C transactions and cross-border sales). This data flows through your PDP to the tax authority.

The e-reporting obligation follows the same phased timeline as the e-invoicing mandate. It's separate from e-invoicing, but you'll need the same PDP infrastructure for both.

Accepted Formats

France accepts three structured formats, all compliant with the EN 16931 European standard:

Factur-X

Factur-X is France's preferred hybrid format. It's a PDF/A-3 file with an embedded CII XML payload — human-readable and machine-processable in one file. If you're familiar with Germany's ZUGFeRD, they're technically the same specification (more on that later).

For the French mandate, the Factur-X profile must be at least "EN 16931" (also called the "Comfort" profile). The Minimum and Basic WL profiles don't carry enough structured data to satisfy the mandate.

UBL (Universal Business Language)

UBL 2.1 invoices are accepted. This is a pure XML format — the same syntax used by Peppol BIS Billing. If your systems already generate UBL invoices for Belgian, Dutch, or Nordic customers, the same output works for France (with the right French-specific fields populated).

CII (Cross-Industry Invoice)

CII is the UN/CEFACT XML syntax that sits inside Factur-X. You can also submit standalone CII invoices without the PDF wrapper. This is less common in practice, but it's technically valid.

What's NOT Accepted

• PDF invoices (even well-formatted ones)
• Scanned documents
• EDI messages that don't conform to EN 16931
• XRechnung specifically — while XRechnung is EN 16931 compliant, it carries Germany-specific CIUS rules that aren't applicable in France. A valid XRechnung invoice might need adjustments for French requirements.

How France Differs from Germany

If you're already compliant with Germany's e-invoicing rules, you might assume France is similar. The format requirements overlap, but the infrastructure is fundamentally different.

The biggest practical difference: in Germany, you validate and send. In France, you validate, route through a PDP, and the PDP handles government reporting. Your compliance strategy needs to account for that intermediary.

What to Do Right Now

Whether you're a large enterprise hitting the September 2026 deadline or a smaller business preparing ahead, here's the practical checklist:

1. Choose a PDP (or confirm your provider is becoming one)

Check whether your ERP vendor, accounting software, or e-invoicing service provider is in the process of PDP certification. The DGFiP maintains a list of registered PDPs. If your current provider isn't on the path to certification, start evaluating alternatives now — switching platforms takes time.

2. Validate Your Invoice Output

Before you connect to a PDP, make sure the invoices your system generates actually pass validation. Common issues with French-bound invoices include:

• Missing or incorrect SIRET numbers (the French business identifier)
• Factur-X profiles set to "Minimum" instead of "EN 16931" or higher
• Tax category codes that don't match French VAT requirements
• Missing mandatory fields that France requires beyond the EN 16931 core

Use the Invoice Navigator validator to catch these issues before they hit production. Upload a sample invoice and check for format errors specific to your output.

3. Map Your Transaction Flows

Not every invoice goes through e-invoicing. Map out which of your transactions are:

• Domestic B2B (subject to e-invoicing)
• Cross-border B2B (subject to e-reporting only)
• B2C (subject to e-reporting only)
• Exempt (certain financial services, insurance, etc.)

This determines what goes through your PDP and what gets reported differently.

4. Set Up Reception

Even if your sending deadline is 2027 or 2028, you need to receive e-invoices from September 2026. This means:

• Registering on the PPF business directory so senders can find you
• Having a PDP connection (or using the PPF directly) to receive incoming invoices
• Updating your AP (accounts payable) workflow to process structured XML, not just PDF

5. Test End-to-End

Once your PDP connection is in place, run test transactions. The PDP ecosystem will have sandbox environments — use them. Validate that:

• Your invoices generate correctly (syntax + business rules)
• Routing works (your PDP can deliver to your test trading partner's PDP)
• The data flows back into your ERP/accounting system correctly

Common Mistakes

From what we've seen in early PDP testing and from businesses preparing for the mandate, these are the recurring problems:

Confusing Factur-X profiles. The Minimum profile is not sufficient. Your Factur-X invoices need the EN 16931 profile (formerly "Comfort") at minimum. Many PDF generation tools default to Minimum because it requires the least data.

Assuming your current Chorus Pro setup covers you. Chorus Pro is for B2G (government invoices). The B2B mandate is a separate system with different requirements. If you only invoice government entities, you might already be e-invoicing — but B2B to private companies is a different flow.

Ignoring e-reporting. The e-invoicing mandate gets all the attention, but e-reporting for B2C and cross-border transactions launches on the same timeline. If you sell to consumers or export within the EU, you need to report those transactions through your PDP too.

Waiting for "final" regulations. France has changed the timeline before, and there are still details being finalized around PDP certification and technical specifications. But the core requirements — structured formats, PDP routing, phased rollout — are settled. Waiting for every last detail means running out of time for implementation.

The Bigger Picture

France's mandate is part of the EU-wide push toward real-time transaction reporting and structured e-invoicing. The EU's ViDA (VAT in the Digital Age) proposal aims to standardize this across all member states by 2030, but countries like France, Germany, and Belgium aren't waiting.

If you're building compliance for one country, you're going to need it for others soon. The formats overlap — Factur-X, UBL, and CII show up everywhere. The validation rules vary by country, but the underlying EN 16931 standard is the same. Investing in proper validation and format support now pays off across borders.

Check the deadlines page to see how France fits into the broader EU timeline, and use the validator to test your invoices against French requirements today.

FAQ

When does France's e-invoicing mandate start?

The first phase starts September 1, 2026, for large enterprises. All businesses must be able to receive e-invoices from that date. Medium enterprises must send from September 2027, and all businesses from September 2028.

What formats does France accept for e-invoicing?

France accepts three EN 16931-compliant formats: Factur-X (PDF/A-3 with embedded CII XML), UBL 2.1, and standalone CII. Factur-X is the most commonly used in France. Plain PDF invoices are not accepted.

What is a PDP in French e-invoicing?

A Plateforme de Dématérialisation Partenaire (PDP) is a certified private platform that handles invoice routing between businesses and reports transaction data to the French tax authority. Most businesses will send and receive e-invoices through a PDP.

Do I need to register somewhere to receive e-invoices in France?

Yes. You need to register on the PPF (Portail Public de Facturation) business directory so that senders and their PDPs can route invoices to you. You also need an active PDP connection or PPF account to actually receive incoming invoices.

Is Factur-X the same as ZUGFeRD?

Technically, yes — Factur-X and ZUGFeRD 2.x are the same specification maintained jointly by France and Germany. The differences are mostly in naming and country-specific validation context. See our detailed comparison for the nuances.

Can I use XRechnung invoices in France?

While XRechnung invoices are EN 16931 compliant, they carry Germany-specific CIUS rules (the BR-DE business rules) that aren't recognized in France. You'd need to generate invoices without the German-specific constraints and ensure French-specific fields are populated.

What happens if I'm not ready by September 2026?

For large enterprises required to send from September 2026, non-compliance means your invoices may be rejected by your trading partners' PDPs. The DGFiP has indicated that penalties will follow, though the exact enforcement approach for B2B is still being detailed. For reception, failing to accept e-invoices could disrupt your supply chain as large senders switch to structured formats.