France · Factur-X: e-invoice formats and rules
Use this page to choose the France · Factur-X check, identify the fixed package and follow diagnostic examples before sending an invoice to its recipient.
Formats and syntax
DGFiP describes structured UBL, CII and mixed formats that contain structured data plus a readable representation. Factur-X is the hybrid option, with profiles MINIMUM, BASIC WL, BASIC, EN 16931 and EXTENDED documented by FNFE-MPE. Profile names describe different data scopes. Being able to validate a profile does not establish that every French receiving platform accepts it for the business transaction; consult the platform’s requirements and the reform documentation.
Rules XSDHub applies
XSDHub applies Factur-X 1.09.2 / ZUGFeRD 2.5.2 profile schemas and Schematron. It extracts embedded XML from a supported PDF or checks supplied XML directly, then reports the declared profile and applicable layers. The EN16931 profile receives the separate EN 16931 layer; other profiles have their documented profile scope. PDF/A-3 conformity, electronic signatures, visual-to-XML consistency and the full French reform workflow are outside this validator’s coverage.
Who this affects
The DGFiP overview describes domestic transactions between businesses established in France and subject to French VAT, including businesses under the franchise regime. It distinguishes e-invoicing from transaction and payment e-reporting. Public-sector B2G invoicing uses the separate Chorus Pro context. For business-to-business invoices, an approved platform handles the required exchange; an XML checker is not such a platform. Consult the official page for the timetable and the relevant situation.
Common errors to investigate
- Profile scope and limits — Choose a profile containing the business information required by the recipient; a low-detail profile cannot supply missing invoice lines.
- VAT breakdown — Reconcile the taxable base with the lines and allowances belonging to the same VAT category.
- Document totals — Fix the sum in the underlying data before generating a fresh hybrid PDF, so its embedded XML contains the correction.
| Check | XSDHub coverage |
|---|---|
| XML structure and fixed rules | Factur-X 1.09.2 / ZUGFeRD 2.5.2; profile-specific XSD and Schematron |
| Certification and legal acceptance | Not provided |
| Government portal submission | Not provided |
| Peppol | Not supported yet |
Working with the result
Start with the actual hybrid invoice, rather than a screenshot or a scanned copy. Read whether each reported layer ran, failed or was outside the detected profile. Preserve the source document when reviewing a discrepancy between what the PDF shows and what its XML carries. The linked profile guide explains why a successful technical result cannot be used as certification of the PDF or as proof of French tax acceptance.