— March 30, 2026 · 13 min read

France e-invoicing 2026: the actual timeline

The French e-invoicing timeline has been rewritten several times in three years. The March 2026 version, the one that applies, fits in three dates: September 2026 for receipt, September 2027 for large groups and ETI emission, September 2028 for SMEs and micro-businesses. Vendors preparing their tooling must build from those dates: anything else is commentary.

What has changed since the initial announcement

The French B2B e-invoicing project is driven by the Directorate-General for Public Finances (DGFiP), with the Agency for State Financial Computing (AIFE) as technical operator. The original trajectory pointed to a July 2024 start, postponed first to September 2026 for receipt, then stabilised by the 2024 Finance Act and confirmed by the decree of 25 June 2024. The current timeline is the product of two years of negotiation between the DGFiP, candidate PDP platforms, professional bodies, and software vendors.

Three points are now stable and no longer up for debate. First, the French network is mandatory: this is a legislative mandate, not an encouragement. Second, the scope is domestic B2B: intra-community and international flows remain governed by existing European rules and, eventually, by the ViDA directive (VAT in the Digital Age) when it enters into force. Finally, the chosen architecture is "Y-shaped": invoices transit either through approved private platforms (PDP) or through a free public platform (PPF, the public invoicing portal), with systematic upstream reporting of fiscal data to the public network.

The three dates to carve in stone

The split between receipt and emission is essential. From September 2026, every French business — including the micro-business that emits no invoice — must be able to receive an electronic invoice. This is the most immediate rupture of the timeline: it instantly touches four million businesses, and it mechanically conditions the use case at every large emitter switching on the same date.

Staggered emission, in turn, exists to spread integration load across vendors and SCM partners. A mid-cap business that must switch over in September 2027 typically has between five hundred and several thousand customers to connect on the emission side — a twelve to eighteen month project. The 2026-2028 transition period will see paper invoices emitted and electronic invoices received coexist in the same accounting file. That coexistence is legally valid; it will simply be tedious to archive.

PDP, PPF, the Y-shaped architecture

The French network rests on three types of actors. Software vendors must understand their relationship to avoid aiming at the wrong technical target.

• The PPF — Public invoicing portal, operated by AIFE on behalf of DGFiP. Public service, free of charge, but minimalist: it accepts manual or API-driven deposit of a file in the mandated format, checks it, transmits it, and reports fiscal data. The PPF is designed as a safety net for businesses unwilling to rely on a private platform. It offers no mapping, no probative archiving, no ERP connector, no interoperability with other European networks.
• The PDP — Partner dematerialisation platforms, private operators that have obtained DGFiP accreditation following a technical dossier and a security audit. By the first quarter of 2026, roughly one hundred platforms have been registered (the DGFiP publishes the list on impots.gouv.fr). A few structural actors: Cegedim, Iopole, Generix, Tenor, DocuWare, Esker, Yooz, Pagero, Sage, Cegid… plus international SCM vendors and several PEPPOL access points.
• The OD — Dematerialisation operators, non-accredited intermediaries that rely on a PDP to route invoices. This is the common option for an accounting software vendor that does not wish to carry the PDP accreditation itself: it piggy-backs on an existing PDP in a white-label arrangement.

The Y-shape means every invoice, whether transiting via a PDP or the PPF, eventually deposits its fiscal data (net amounts, VAT, parties identified by SIREN) into the central DGFiP system. The PPF, in this scheme, is no longer the "central hub" originally envisioned in 2022: it has become one platform among others, integrated to the network, with a minimal guarantor role and a DGFiP consultation portal.

The three accepted formats (Factur-X, UBL, CII)

The French architecture accepts three electronic invoice formats, all conformant with EN 16931 — whose principles are detailed on the ediverse PEPPOL page.

• Factur-X — hybrid PDF/A-3 + XML CII (Cross Industry Invoice) format. The PDF carries the visual representation aligned with French accounting practice; the embedded XML carries the EN 16931 semantics. Maintained in France by FNFE-MPE (Forum National de la Facture Électronique), Factur-X is also the ZUGFeRD format on the German side. Specification 1.0 is free and published by FNFE.
• UBL 2.1 — pure XML format, identical to the one carried on the PEPPOL network for BIS Billing 3.0. This is the format of choice for fully machine-to-machine flows without PDF generation.
• CII (UN/CEFACT Cross Industry Invoice) — XML format inherited from UN/CEFACT, the official syntax inside Factur-X but also usable standalone, without the wrapping PDF.

The three formats are semantically equivalent in the sense of EN 16931 — they carry the same business terms (BT-1 to BT-200+) and pass the same business rules. The difference is syntactic: UBL and CII are two XML dialects for expressing the same content. A PDP must therefore accept and emit all three, and know how to convert semantically between them — hence the importance, for the vendor, of reasoning first in EN 16931, and only afterwards in format.

What the vendor must plan now

For a software vendor (accounting, invoicing, ERP) whose users are mostly French, the technical plan reduces to six work-streams. None is trivial, and their sequencing conditions the ability to ship on schedule.

1. Decide PDP or OD: carrying the PDP accreditation in-house is a twelve to eighteen month regulatory project, with significant recurring cost (annual audit, ISO 27001 or equivalent, specification updates). Many vendors choose the OD option by anchoring on an existing PDP: it is faster but introduces a strong commercial dependency.
2. Implement Factur-X 1.0: producer on the emission side, reader on the receipt side. A Factur-X is a PDF/A-3 with an attached CII XML: both PDF/A-3 generation and EN 16931-compliant CII serialisation must be mastered.
3. Implement UBL 2.1 Invoice + CreditNote: for PEPPOL interoperability and customers requiring pure UBL. The mapping between the internal invoice and the UBL XML is the most delicate piece: generic libraries often map EN 16931 cardinalities poorly, and the serialiser must be hand-written.
4. Wire up Schematron validation: PEPPOL BIS Billing 3.0 publishes Schematron files for TC434 rules and PEPPOL rules. The French profile adds BR-FR rules. Schematron validation typically runs with Saxon (Java) or Schxslt (XSLT 2.0); in production, a dedicated instance is better than embedding Saxon in every deployment.
5. Plan legal archiving: in France, invoice retention is ten years (Code de commerce). Archiving must guarantee integrity, traceability, and readable restitution. Many PDPs offer probative archiving as an option; otherwise, it must be contracted with a certified third-party archiver.
6. Prepare DGFiP consultation: fiscal data submitted to the PPF is consultable by the business via a portal. The vendor can either mirror that data in its own interface or defer to the public portal. The first choice improves user experience but requires an additional API integration.

What still blocks in March 2026

Several grey areas persist six months before the receipt deadline. The specification of the lifecycle flows (statuses "rejected", "suspended", "paid") has only been stabilised since late 2025, and several PDPs are still waiting for the last AIFE specification fixes to finalise their developments. Consultation with SCM partners shows ERP connectors are ready in standard form for SAP S/4 and the main French ERPs, but often beta for rarer ERPs. Finally, the articulation with ViDA — the European directive adopted in March 2025 — remains to be clarified: ViDA mandates real-time reporting of intra-community operations from 2028, and France will need to adjust its domestic mechanism to align.

For vendors who have been following this dossier since 2022, the dominant impression is that France has managed to avoid the Italian SdI scenario of 2019 — when the launch was chaotic — at the cost of a slower timeline. The progressive industrialisation in three steps gives actors time to season their pipelines. The downside is that any further delay would now cost politically dearly: there will be no fourth postponement.

The 2026 window and the work to be done

For a French vendor that has not yet engaged its e-invoicing project, March 2026 is the last reasonable window to start. The receipt deadline of 1 September 2026 obliges every customer to be able to read an electronic invoice — so, at minimum, the vendor must ship a Factur-X and UBL reader in its product, and a connector to at least one PDP, before the autumn. The emission side can follow over the next twelve to twenty-four months depending on the customer segment.

The conceptual work — understanding EN 16931, reading the PEPPOL Schematron, reasoning in business terms — is paradoxically the most cost-effective task to do first. Formats will change marginally; business terms BT-1 to BT-200+ will not change anymore. Readers who wish to deepen the European semantics can refer to the ediverse PEPPOL page and the previous blog article on EN 16931 for the base layer; this post focuses on the French component. The two readings complement each other.