{"id":11699,"date":"2026-03-23T17:46:36","date_gmt":"2026-03-23T16:46:36","guid":{"rendered":"https:\/\/www.retarus.com\/blog\/en\/e-invoicing-in-frankreich-was-sich-mit-schematron-v1-3-aendert\/"},"modified":"2026-03-25T16:09:31","modified_gmt":"2026-03-25T15:09:31","slug":"e-invoicing-in-france-whats-changing-with-schematron-v1-3","status":"publish","type":"post","link":"https:\/\/www.retarus.com\/blog\/en\/e-invoicing-in-france-whats-changing-with-schematron-v1-3\/","title":{"rendered":"E-Invoicing in France: What\u2019s Changing with Schematron v1.3"},"content":{"rendered":"\n
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<\/a> (Schematron v1.3) standard gives rise to important adjustments for companies and solution vendors.<\/p>\n\n\n\n For companies, this means:<\/strong> Changes to data structures, control logic, and routing processes.<\/p>\n\n\n\n This blog post sets out the most important changes and how they will affect implementation in practice.<\/p>\n\n\n\n XP Z12-012 is a technical standard at the heart of French e-invoicing. It defines:<\/p>\n\n\n\n In this way, it lays the foundations for the standardized interchange of electronic invoices in France.<\/p>\n\n\n\n The XP Z12-012 standard is based on the European EN16931<\/strong> standard, which is implemented in UBL<\/strong> and UN\/CEFACT CII<\/strong> syntax, among other formats.<\/p>\n\n\n\n In the French model, invoice details and status updates are exchanged between the following parties:<\/p>\n\n\n\n Status updates track the progress of an invoice through its various stages, such as submission, acceptance, rejection, or payment.<\/p>\n\n\n\n For more details: https:\/\/www.impots.gouv.fr\/specifications-externes-b2b<\/a><\/p>\n\n\n\n The latest version of XP Z12-012<\/a> (Version 1.3, February 2026) includes several important functional and technical adjustments. An overview of the key changes follows:<\/p>\n\n\n\n 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.<\/p>\n\n\n\n For companies and providers of e-invoicing solutions, this means: <\/strong><\/strong><\/p>\n\n\n\n Routing errors may result in the rejection or non-delivery of invoices.<\/p>\n\n\n\n The EXTENDED-CTC-FR<\/strong> profile, which defines additional requirements, is subject to several changes.<\/p>\n\n\n\n These include:<\/p>\n\n\n\n Practical implications<\/strong><\/p>\n\n\n\n The new specification demands more precision when it comes to processing credit notes.<\/p>\n\n\n\n One critical requirement:<\/p>\n\n\n\n Corrections need to take place using structured credit note documentation.<\/p>\n\n\n\n Practical implications<\/strong><\/p>\n\n\n\n Systems are required to generate credit notes in the correct structure, otherwise they may be rejected by platforms.<\/p>\n\n\n\n In addition to these structural changes, there are a number of other adjustments, primarily related to tax logic and validation rules.<\/p>\n\n\n\n The new specifications contain additional clarifications for dealing with tax issues, especially regarding:<\/p>\n\n\n\n Practical implications<\/strong><\/p>\n\n\n\n The tax and validation logic in ERP and e-invoicing systems must be assessed and adapted as required.<\/p>\n\n\n\n The new version includes previously unclarified use cases, such as:<\/p>\n\n\n\n Practical implications<\/strong><\/p>\n\n\n\n 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\u00e4t zwischen Plattformen.<\/p>\n\n\n\n Status updates play a key role in the French model. They document the progress of an e-invoice and regulate downstream processes.<\/p>\n\n\n\n The new specifications define:<\/p>\n\n\n\n Additional status codes, which were already introduced in earlier versions, enable a more accurate reflection of special cases, for instance when invoices can\u2019t be transmitted.<\/p>\n\n\n\n Practical implications<\/strong><\/p>\n\n\n\n Companies have to ensure that their systems are able to:<\/p>\n\n\n\n For companies currently preparing for the introduction of mandatory e-invoicing in France, the focus is on three key areas.<\/p>\n\n\n\n The XP-Z12 standards are still undergoing further development. Accordingly, implementation should be designed to permit flexibility and facilitate future updates.<\/p>\n\n\n\n Changes to:<\/p>\n\n\n\n necessitate adjustments in data mapping and validation rules.<\/p>\n\n\n\n Certified platforms and software vendors play a crucial role when it comes to:<\/p>\n\n\n\n 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.<\/p>\n\n\n\n While many of the changes at first appear technical, they have a direct impact on:<\/p>\n\n\n\n For companies, this means:<\/strong><\/p>\n\n\n\n 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.<\/p>\n\n\n\n Companies would therefore be well advised to assess well in advance whether their systems meet the latest requirements.<\/p>\n\n\n\n We\u2019re here to support you with analysis and implementation.<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" The new XP Z12-012 specification (Schematron v1.3) brings significant changes to e-invoicing in France. Find out what\u2019s changing and what your business needs to implement now.<\/p>\n","protected":false},"author":72,"featured_media":11700,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","_s2mail":"yes","footnotes":""},"categories":[8],"tags":[1673,3730],"class_list":["post-11699","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-e-invoicing","tag-france"],"acf":[],"yoast_head":"\nXP Z12-012 at a Glance<\/h2>\n\n\n\n
\n
\n
What\u2019s New in Version 1.3?<\/h2>\n\n\n\n
1. New data flow: Flow 11 (directory \/ annuaire)<\/h3>\n\n\n\n
\n
2. New requirements in the EXTENDED-CTC-FR profile<\/h3>\n\n\n\n
\n
\n
3. More detail and precision regarding credit notes<\/h3>\n\n\n\n
\n
4. Changes to VATEX codes and tax logic<\/h3>\n\n\n\n
\n
5. Additional examples and use cases<\/h3>\n\n\n\n
\n
6. Changes to the lifecycle<\/h3>\n\n\n\n
\n
\n
What Does This Mean in Practice for Businesses?<\/h2>\n\n\n\n
1. Constantly keeping an eye on specifications<\/strong><\/h3>\n\n\n\n
2. Tailoring systems to meet specific requirements<\/strong><\/h3>\n\n\n\n
\n
3. Collaboration with solution providers<\/strong><\/h3>\n\n\n\n
\n
Conclusion<\/h2>\n\n\n\n
\n
<\/a>Sources
<\/strong>French tax authority (DGFiP) \u2013 external specifications for B2B<\/a>
AFNOR XP Z12-012 \u2013 Formats et profils des messages factures et statuts de cycle de vie
<\/a>French Public Service: Electronic invoicing: it\u2019s coming soon!<\/a><\/p>\n\n\n\n