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 combines a readable PDF/A-3 file with structured CII data. Using the format does not by itself prove that a French or German recipient will accept it. Confirm the exact package version, profile, and delivery channel with the recipient.
Explanation
Uses a PDF container with embedded XML for structured processing.
Typically used alongside French routing requirements (platform-dependent).
Common mistakes
- Using a filename from another package. Current Factur-X packages use factur-x.xml; confirm the exact filename in the package specification.
- Reusing an AFRelationship value from another profile or version. The permitted value depends on the exact package and profile.
- Choosing MINIMUM or BASIC WL by name alone. These profiles carry less structured data; check whether the recipient and transaction require EN 16931 or EXTENDED.
- 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 French B2B e-invoicing?
No. Factur-X is one supported format. The recipient channel and current French technical rules determine which formats and profiles it accepts.
Which Factur-X profile should I use?
Use the exact profile required by the recipient and transaction. The current package names include MINIMUM, BASIC WL, BASIC, EN 16931, and EXTENDED. Validate the chosen package and profile before delivery.
Can a Factur-X file be opened as a normal PDF?
Yes. A correctly formed Factur-X file contains a readable PDF/A-3 layer. Compatible systems can also extract the embedded factur-x.xml for structured processing.