You require more info on French E-Invoicing & Reporting mandate, just send a message to [email protected].
Source AFNOR
France’s e‑invoicing reform is often discussed in terms of Factur‑X, PDP accreditation, and September 2026 go‑live dates.
What is still largely underestimated is the operational reality hidden in AFNOR XP Z12‑014: a catalogue of 40+ standardized B2B use cases, referenced by DGFiP and embedded in version 3.1 of the external specifications.
These use cases are not theoretical. They describe how real ERP billing scenarios must flow through PDPs, the PPF, and DGFiP systems.
This article maps those use cases to day‑to‑day ERP processes companies already run.
Regulatory context and sources
The French tax authorities (DGFiP) explicitly confirm that:
- Version 3.1 of the external specifications formalizes the framework for the start of the reform on 1 September 2026
- B2B use cases are not defined directly by DGFiP, but by AFNOR standards, notably XP Z12‑014
[impots.gouv.fr]
AFNOR XP Z12‑014:
- Describes the nominal e‑invoicing workflow
- Covers all specific B2B use cases
- Has expanded to more than 40 scenarios
[theinvoicinghub.com]
- Core domestic B2B invoicing (ERP “happy flow”)
Typical ERP scenarios
- Standard domestic B2B invoice
- Multiple VAT rates on one invoice
- Discounts, rebates, and surcharges
- Periodic or consolidated billing
- Advance payment (deposit) invoices and final settlement
- Foreign‑currency invoices with French VAT
Why this matters
Even “simple” invoices now require:
- Structured format compliance
- Mandatory lifecycle statuses
- Correct PDP routing and reporting
These scenarios correspond to the baseline AFNOR use cases every ERP will trigger from day one.
- Credit notes and invoice corrections (where complexity starts)
Typical ERP scenarios
- Full invoice cancellations
- Partial credit notes
- Quantity corrections
- VAT‑only corrections
- Credit notes without invoice reference
- Cancel‑and‑replace logic
- Late corrections after reporting
- Rounding and settlement adjustments
ERP reality
These are routine finance operations today. Under the French model, they become high‑risk scenarios because:
- Each correction must preserve traceability
- Status sequencing matters
- Inconsistencies are visible to DGFiP
AFNOR XP Z12‑014 explicitly documents these patterns as standardized use cases. [theinvoicinghub.com]
- Special commercial arrangements (often ignored, but mandatory)
Typical ERP scenarios
- Self‑billing (autofacturation)
- Third‑party invoicing
- Agent / commissionaire models
- Intragroup management fees
- Rebate and bonus settlements
- Penalty and late‑interest invoices
- Framework contracts with call‑offs
- Mixed taxable and exempt supplies
- Multi‑establishment (multi‑SIRET) sellers
Why companies underestimate this
Most ERP deployments already support these models — but not in a standardized, reportable way aligned with AFNOR semantics.
DGFiP explicitly relies on AFNOR standards to govern these B2B scenarios. [impots.gouv.fr]
- Invoice lifecycle, rejections, and failures
Typical ERP scenarios
- Buyer rejection of an invoice
- Technical or semantic rejection by PDP/PPF
- Acceptance with reservation
- Cancellations before or after acceptance
- Duplicate invoice handling
- Late transmission
- Missing or incorrect lifecycle statuses
Key shift
Invoice status is no longer internal ERP metadata.
It is regulated, structured data shared with the tax authority.
This lifecycle orchestration is a core pillar of the French model. [impots.gouv.fr]
- Transitional and edge cases
Typical ERP scenarios
- Buyer or supplier not yet registered in the annuaire
- PDP migration or change
- Multi‑ERP landscapes
- Historical invoice references
- Audit or re‑submission requests by DGFiP
These scenarios are explicitly foreseen in AFNOR use‑case documentation, which is why they are standardized rather than “exceptions”. [theinvoicinghub.com]
Key takeaway for companies and CFOs
France’s e‑invoicing reform is not about:
- Picking a PDP
- Generating Factur‑X files
It is about ensuring that existing ERP billing behaviour matches standardized use cases defined outside the ERP — by AFNOR, endorsed by DGFiP.
Most large groups will encounter 25–35 of these use cases in year one, often without realizing it.
Sources
- DGFiP – Spécifications externes et normes pour la facturation électronique (v3.1) (last modified March 2026):
https://www.impots.gouv.fr/specifications-externes-b2b [impots.gouv.fr] - DGFiP / AFNOR ecosystem overview confirming expanded B2B use‑case catalogue:
https://www.theinvoicinghub.com/fresh-publications-further-clarify-frances-2026-e-invoicing-requirements/ [theinvoicinghub.com]
AFNOR XP Z12‑014 – 44 B2B use cases (1 line per case)
- Standard domestic B2B invoice
- Invoice with multiple VAT rates
- Invoice with discounts or price reductions
- Periodic or consolidated billing invoice
- Advance payment (deposit) invoice
- Final invoice following deposit
- Pro‑forma invoice followed by final invoice
- Invoice in foreign currency with domestic VAT
- Invoice covering multiple deliveries
- Cancelled invoice before transmission
- Full invoice cancellation via credit note
- Partial credit note (value adjustment)
- Partial credit note (quantity adjustment)
- VAT‑only correction
- Credit note without invoice reference
- Replacement invoice (cancel and re‑issue)
- Late correction after reporting
- Rounding correction
- Settlement / write‑off credit note
- Self‑billing (autofacturation)
- Third‑party invoicing on behalf of seller
- Agent or commissionaire invoicing
- Marketplace or platform‑mediated invoicing
- Intragroup or intercompany invoice
- Framework contract with call‑off invoices
- Bonus or year‑end rebate settlement
- Penalties or late‑payment interest invoice
- Mixed taxable and exempt supplies
- Assujetti unique / VAT group invoicing
- Buyer rejection for commercial reasons
- Buyer rejection for technical reasons
- Acceptance with reservation
- Cancellation after transmission, before acceptance
- Cancellation after acceptance
- Duplicate invoice handling
- Late invoice transmission
- Missing or incorrect lifecycle status
- Exceptional fallback outside structured exchange
- Buyer not found in the annuaire
- Supplier not yet PDP‑connected
- Change of PDP (platform portability)
- Multi‑ERP or multi‑system seller environment
- Reference to historical (pre‑mandate) invoice
- Audit re‑submission or DGFiP request
Briefing document & Podcast: France’s E‑Invoicing & E‑Reporting – VATupdate
Found in Revo newsletter
- See also
- Join the Linkedin Group on Global E-Invoicing/E-Reporting/SAF-T Developments, click HERE
- Join the LinkedIn Group on ”VAT in the Digital Age” (VIDA), click HERE
Latest Posts in "France"
- Revo Takes the Stage: Understanding the French e‑Invoicing Mandate (May 22)
- Applicable VAT Rates for Public Waste Management Services: Collection, Treatment, and Related Operations
- VAT Scope and Territoriality: Composite Offers and Special Cases, Including Insurance with Goods or Services
- VAT Scope and Territoriality: Composite Offers, Principles, and Definitions for Public Service Operations
- Reduced VAT Rates for Certain Taxable Services Including TV Subscriptions and Public Service Operations
