Reference
Markdown exportFactur-X
French hybrid e-invoice format, aligned with ZUGFeRD and EN 16931 profiles.
Definition
French hybrid e-invoice format, aligned with ZUGFeRD and EN 16931 profiles.
Why this term matters
Factur-X is the only hybrid format explicitly accepted by Chorus Pro for French B2G and is on track to be a primary format for the upcoming French B2B reform routed through PPF/PDP platforms (rollout 2026–2027). Because Factur-X 1.0+ is technically aligned with ZUGFeRD 2.x, a single PDF/A-3 with embedded CII can satisfy both German and French recipients.
Explanation
Uses a PDF container with embedded XML for structured processing.
Typically used alongside French routing requirements (platform-dependent).
Common mistakes
Use these points as the practical checks for this section.
- Naming the embedded XML something other than factur-x.xml — the Factur-X 1.0+ spec mandates this exact filename at the PDF root.
- Setting AFRelationship to "Source" or "Supplement" — Factur-X 1.0+ requires "Data" (older 0.x readers used "Alternative").
- Using the MINIMUM or BASIC WL profile to bill a customer — these subset profiles cannot legally replace the human-readable invoice in France because they lack required EN 16931 totals.
- Embedding XMP metadata that omits the fx:DocumentType, fx:DocumentFileName and fx:Version entries the spec requires for downstream Factur-X readers.
Frequently asked questions
Is Factur-X mandatory for the French B2B reform?
Factur-X is one of the three core formats explicitly named in the FNFE-MPE/AIFE technical specs alongside UBL Peppol BIS Billing 3.0 and UN/CEFACT CII. Suppliers and PDPs may choose, but Factur-X is the only one that ships with a human-readable PDF in the same artifact.
Which Factur-X profile should I use?
For full EN 16931 conformance and Chorus Pro acceptance, use EN 16931 (BASIC+) or EXTENDED. MINIMUM and BASIC WL are intended for credit-management or accounts-payable workflows, not for end-customer invoicing.
Can a Factur-X file be opened as a normal PDF?
Yes — the human-readable layer is a fully valid PDF/A-3, so any PDF reader can render it. Compliant downstream systems additionally extract the embedded factur-x.xml for structured processing.