France’s mandatory B2B e-invoicing regime (set to come into effect in September 2026) is taking concrete shape. The new version of the AFNOR XP Z12-012 (Schematron v1.3) standard gives rise to important adjustments for companies and solution vendors.
For companies, this means: Changes to data structures, control logic, and routing processes.
This blog post sets out the most important changes and how they will affect implementation in practice.
XP Z12-012 at a Glance
XP Z12-012 is a technical standard at the heart of French e-invoicing. It defines:
- formats and profiles for electronic invoicing
- status messages during the invoicing lifecycle
- validation and operating guidelines for platforms
In this way, it lays the foundations for the standardized interchange of electronic invoices in France.
The XP Z12-012 standard is based on the European EN16931 standard, which is implemented in UBL and UN/CEFACT CII syntax, among other formats.
In the French model, invoice details and status updates are exchanged between the following parties:
- suppliers and customers
- certified platforms (Plateformes Agréées – PA)
- compatible solutions
- the government’s Public de Facturation (PPF) portal
Status updates track the progress of an invoice through its various stages, such as submission, acceptance, rejection, or payment.
For more details: https://www.impots.gouv.fr/specifications-externes-b2b
What’s New in Version 1.3?
The latest version of XP Z12-012 (Version 1.3, February 2026) includes several important functional and technical adjustments. An overview of the key changes follows:
1. New data flow: Flow 11 (directory / annuaire)
Version 1.3 introduces a new data flow, Flow 11, which builds on Flow 10. This revision concerns the directory service (annuaire), which plays a crucial role in the routing of invoices by determining which platform needs to be used to deliver an invoice to its recipient.
For companies and providers of e-invoicing solutions, this means:
- Directory information must be retrieved accurately.
- The destination platform for a recipient must be identified definitively.
- Invoices must be routed correctly in line with the new data flow rules.
Routing errors may result in the rejection or non-delivery of invoices.
2. New requirements in the EXTENDED-CTC-FR profile
The EXTENDED-CTC-FR profile, which defines additional requirements, is subject to several changes.
These include:
- reasons for VAT exemptions (VATEX) in the case of discounts and surcharges
- provision of additional textual or coded information relating to tax exemptions
- more detailed subline structures within invoice line items
- new rules for specifying quantities in parent line items
Practical implications
- Data mappings need to be adapted
- New data fields have to be integrated
- Validation logic must be updated
3. More detail and precision regarding credit notes
The new specification demands more precision when it comes to processing credit notes.
One critical requirement:
- Negative credit notes are no longer permitted.
Corrections need to take place using structured credit note documentation.
Practical implications
Systems are required to generate credit notes in the correct structure, otherwise they may be rejected by platforms.
In addition to these structural changes, there are a number of other adjustments, primarily related to tax logic and validation rules.
4. Changes to VATEX codes and tax logic
The new specifications contain additional clarifications for dealing with tax issues, especially regarding:
- the provision of services within the EU and outside of the EU
- discounts and surcharges at the document level
- price and discount logic at item line level
Practical implications
The tax and validation logic in ERP and e-invoicing systems must be assessed and adapted as required.
5. Additional examples and use cases
The new version includes previously unclarified use cases, such as:
- multi-seller scenarios
- detailed subline item structures
- more examples and documentation of implementation scenarios
Practical implications
The additional examples and use cases make it easier to implement complex scenarios and improve interoperability between platforms.tern die Umsetzung komplexer Szenarien und verbessern die Interoperabilität zwischen Plattformen.
6. Changes to the lifecycle
Status updates play a key role in the French model. They document the progress of an e-invoice and regulate downstream processes.
The new specifications define:
- structure and mandatory fields
- validation rules
- communication logic between platforms and company systems
Additional status codes, which were already introduced in earlier versions, enable a more accurate reflection of special cases, for instance when invoices can’t be transmitted.
Practical implications
Companies have to ensure that their systems are able to:
- receive status updates,
- interpret them correctly,
- and automatically trigger subsequent processes
What Does This Mean in Practice for Businesses?
For companies currently preparing for the introduction of mandatory e-invoicing in France, the focus is on three key areas.
1. Constantly keeping an eye on specifications
The XP-Z12 standards are still undergoing further development. Accordingly, implementation should be designed to permit flexibility and facilitate future updates.
2. Tailoring systems to meet specific requirements
Changes to:
- data structures,
- tax logic,
- and lifecycle status updates
necessitate adjustments in data mapping and validation rules.
3. Collaboration with solution providers
Certified platforms and software vendors play a crucial role when it comes to:
- implementing technical requirements correctly
- ensuring compatibility with the French ecosystem
Conclusion
The revision of the XP Z12-012 specification (Schematron v1.3) makes it clear that the French e-invoicing framework is still evolving and undergoing further refinement.
While many of the changes at first appear technical, they have a direct impact on:
- data structures
- tax logic
- lifecycle processes
- the routing of platforms via the national directory
For companies, this means:
Implementation needs to remain flexible and frequently be revised. Taking action at an early stage allows enterprises to minimize the risk of rejected invoices, integration problems and delays when going live in 2026.
Companies would therefore be well advised to assess well in advance whether their systems meet the latest requirements.
We’re here to support you with analysis and implementation.
Sources
French tax authority (DGFiP) – external specifications for B2B
AFNOR XP Z12-012 – Formats et profils des messages factures et statuts de cycle de vie
French Public Service: Electronic invoicing: it’s coming soon!
