France E-invoicing September 2026: A Practical Checklist for Businesses

Three months. That's how long businesses selling to large French enterprises have before structured e-invoicing becomes a legal requirement. For companies that are just starting to evaluate their options, the timeline is tight but workable — if you start now.

This is a practical checklist of what needs to be in place before 1 September 2026, who it applies to, and what happens if you're not ready.

Who needs to be ready by September 2026

The September 2026 deadline applies in two directions:

All businesses must be able to receive structured e-invoices from 1 September 2026, regardless of company size. There is no SME exemption for the receiving obligation.

Large and mid-size enterprises must also be able to send structured e-invoices from 1 September 2026. This covers:

• Companies with more than 5,000 employees or annual turnover above EUR 1.5 billion (large enterprises)
• Companies with 250–5,000 employees (mid-size enterprises)

SMEs (under 250 employees) have until 1 September 2027 for the sending obligation — but they must still be set up to receive invoices from September 2026.

Practical implication: If you supply large French companies, you need your sending infrastructure in place before September 2026, even if your own company is an SME.

The checklist

1. Choose a PDP or the PPF

France's e-invoicing system requires that invoices flow through either:

• The PPF (Portail Public de Facturation) — the government's free platform
• An accredited PDP (Plateforme de Dématérialisation Partenaire) — a private platform with full accreditation from DGFiP

Most businesses operating at scale use a PDP rather than the PPF directly. A PDP handles invoice submission, routing to the buyer's platform, DGFiP directory lookups, and status callbacks. The PPF is suitable for low volumes and manual workflows.

Clearvo is an accredited French PDP, meaning invoices submitted via our API are routed directly into the French network without requiring you to register separately with the PPF.

Action: Decide which platform you're using. If you need API access and automated submission, use a PDP.

2. Confirm your format capability

France accepts three formats for B2B invoices:

• Factur-X (EN 16931 profile) — a PDF/A-3 with embedded CII XML. The most common format.
• UBL 2.1 — the OpenPeppol standard, also accepted
• CII (UN/CEFACT Cross Industry Invoice) — accepted standalone

The B2B mandate requires at least the EN 16931 profile of Factur-X. The simplified profiles (MINIMUM, BASIC WL) are not sufficient for mandated transactions.

Action: Confirm your ERP or billing system can generate Factur-X EN 16931 or UBL 2.1, or that your PDP handles format generation from structured data.

3. Have SIRET numbers ready for both parties

Every invoice under the French mandate must identify both the supplier and buyer using their SIRET number (14 digits) or SIREN (9 digits for non-French buyers). This is the routing mechanism — the PPF directory maps SIRET numbers to the correct PDP or inbox.

Action: Confirm your billing system stores customer SIRET numbers. For new French enterprise customers, add SIRET collection to your onboarding flow.

4. Understand e-reporting obligations (even if you're an SME)

Even where the B2B structured invoice mandate doesn't apply — B2C transactions, or invoices to foreign buyers — businesses must submit e-reporting data to DGFiP:

• Flux 2 (B2C aggregate reporting): transaction totals by period
• Flux 3 (payment events): when invoices are paid

E-reporting applies to all French VAT-registered businesses from September 2026, regardless of size. It runs through the same PDP/PPF infrastructure as e-invoicing.

Action: Check whether your PDP handles e-reporting (Flux 2 and Flux 3) in addition to e-invoicing. Not all platforms cover both.

5. Test before go-live

DGFiP operates a pre-production sandbox environment. Before switching to live submission, run end-to-end tests covering:

• Invoice creation and submission
• Buyer acknowledgement and status callbacks
• A rejection scenario (to confirm your error-handling works)
• At least one credit note

Action: Build sandbox testing into your integration timeline. Allow at least 2–3 weeks for this.

6. Plan for status lifecycle management

Unlike a simple email attachment, a Factur-X invoice has a lifecycle managed by the PDP/PPF:

• Deposited — submitted to the platform
• Delivered — routed to the buyer's inbox or PDP
• Acknowledged / Rejected — buyer's system confirms receipt or reports an error
• Paid — payment event reported (Flux 3)

Your accounts receivable or ERP workflow needs to handle these status updates, not just treat submission as the end of the process.

Action: Map the invoice status lifecycle to your AR workflow. Webhook-based status updates are easier to integrate than polling.

What happens if you're not ready

France has not published specific fine amounts for non-compliance at launch, but failure to issue a legally valid structured invoice means:

• The invoice may not be accepted by the buyer's platform
• The transaction lacks legal standing for VAT deduction until a compliant invoice is issued
• Repeat non-compliance risks audit scrutiny from DGFiP

Large enterprise buyers will also start rejecting non-structured invoices from their suppliers as their own receiving systems go live — this is a commercial pressure that operates regardless of formal enforcement.

How Clearvo handles this

Clearvo's France integration covers the full stack:

• Factur-X EN 16931 generation from your standard invoice JSON — no format expertise required
• PDP submission with direct DGFiP routing via our provisional accreditation (file 31890388)
• SIRET validation against the INSEE directory before submission
• E-reporting (Flux 2 and Flux 3) via the same API
• Sandbox testing against DGFiP's pre-production environment

The API call is the same as for any other country. Set country: "FR", supply supplierSiret and customerSiret, and the pipeline handles the rest.

Read the full France e-invoicing guide for technical details, format specifications, and code examples.