In force 🚨 Action required E-invoicing

France sets the technical standards accredited e-invoicing platforms must meet

This page records one dated change. For the rules in France as they stand today, see the France guide →

Jurisdiction: France
Tax: VAT
Change type: E-invoicing
Status: In force
Impact: Action required
Announced: 28 July 2026
Effective: 29 July 2026
Instrument: FR-MINORDER-EINV-2026
Authority: Journal officiel de la République française (Légifrance)
Systems: Invoicing, Tax engine, ERP
Verified: Fetched from official source · high confidence

Who this affects

Accredited platforms (plateformes agréées) operating under the French e-invoicing mandate, and every business that relies on one from 1 September 2026.

What to do

Confirm with your accredited platform that its invoice formats and APIs conform to AFNOR XP Z12-012, XP Z12-013 and XP Z12-014 before the 1 September 2026 mandatory start.

InvoicingTax engineERP

The change

The Arrêté du 27 juillet 2026 relatif à la généralisation de la facturation électronique, published in JORF n°0174 of 28 July 2026 alongside Décret n° 2026-677, sets the technical requirements accredited platforms must meet. It requires conformance with AFNOR standards XP Z12-012 for invoice and status-message formats and profiles, XP Z12-013 for the application programming interfaces between company information systems and accredited platforms, and XP Z12-014 for business use cases.

What changed in detail

The Arrêté du 27 juillet 2026, published in JORF n°0174 of 28 July 2026 alongside Décret n° 2026-677, sets what accredited platforms must actually do: conform to AFNOR XP Z12-012 for invoice and status-message formats and profiles, XP Z12-013 for any standardised APIs a platform chooses to implement, and XP Z12-014 for the use cases it puts into effect.

What it means

Conformance moves from a specification your vendor claims to meet, to a legal condition of their accreditation. The practical question to put to a provider is no longer “do you support Factur-X” but “which profiles of XP Z12-012 do you implement, and which XP Z12-014 use cases do you cover” — the arrêté binds a platform only to the use cases it actually puts into effect, so the gap between two accredited platforms is a real procurement question.

Proof

« 3° De respecter les spécifications décrites dans la norme XP Z12-014 pour les cas d'usage qu'elles mettent en œuvre ; « 4° De respecter les spécifications décrites dans la norme XP Z12-013 pour les interfaces de programmation applicatives (API) standardisées qu'elles souhaitent implémenter. »

"3° To comply with the specifications described in standard XP Z12-014 for the use cases they implement; 4° To comply with the specifications described in standard XP Z12-013 for the standardised application programming interfaces (APIs) they wish to implement."

Arrêté du 27 juillet 2026 relatif à la généralisation de la facturation électronique — Journal officiel de la République française / Légifrance · captured 8 August 2026

Archived from the official distribution · JORFTEXT000054499535 · NOR CPPE2610309A · JORF n°0174 du 28 juillet 2026 · echanges.dila.gouv.fr

« a) Une spécification d'usage de la norme EN16931, dénommée “profil EN16931” implémentée dans la norme d'échange “Cross Industry Invoice” CII, élaborée par l'organisme UN/CEFACT (United Nations Centre for Trade Facilitation and Electronic Business), conformément à la norme XP Z12-012 publiée sur le site internet de l'Association française de normalisation ;

a) A usage specification of standard EN16931, called the “EN16931 profile”, implemented in the “Cross Industry Invoice” CII exchange standard, developed by UN/CEFACT (United Nations Centre for Trade Facilitation and Electronic Business), in accordance with standard XP Z12-012 published on the website of the Association française de normalisation;