Guide
E-Invoicing in France
Key formats, routing options, and a practical checklist for sending compliant e-invoices in France.
What matters in practice
This France guide explains how Factur-X, Chorus Pro routing, PEPPOL exchange, and validation checkpoints fit together so invoices are more likely to clear on the first pass.
This article treats E-Invoicing in France as a practical reference, not just a navigation page. It explains the term or workflow in context, shows why it matters for European e-invoicing, and connects the topic to invoice creation, validation, routing, archiving, and ERP implementation decisions.
Common e-invoice formats
Common e-invoice formats is where the general explanation of E-Invoicing in France becomes operational. The section focuses on Factur-X (EN 16931 profile) and UBL/CII (platform-specific), so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Factur-X (EN 16931 profile)
- UBL/CII (platform-specific)
Routing & delivery
Routing & delivery connects E-Invoicing in France with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding Chorus Pro and PEPPOL to validating or converting the invoice file.
Common identifiers
Common identifiers is where the general explanation of E-Invoicing in France becomes operational. The section focuses on SIREN/SIRET and VAT ID, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- SIREN/SIRET
- VAT ID
Mandate & scope
France uses Factur-X and platform-based exchange for many public workflows, with PEPPOL also relevant in cross-border scenarios.
Mandate & scope
Mandate & scope is where the general explanation of E-Invoicing in France becomes operational. The section focuses on Factur-X: a PDF with embedded EN 16931-aligned XML, widely used for hybrid workflows, Routing: public sector invoicing traditionally uses Chorus Pro; requirements depend on the… and Syntax: some channels accept UBL or CII, but platform constraints apply, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Factur-X: a PDF with embedded EN 16931-aligned XML, widely used for hybrid workflows.
- Routing: public sector invoicing traditionally uses Chorus Pro; requirements depend on the recipient.
- Syntax: some channels accept UBL or CII, but platform constraints apply.
How to send (practical steps)
How to send (practical steps) is where the general explanation of E-Invoicing in France becomes operational. The section focuses on Determine the recipient workflow (platform/portal vs network) and the required format (Factur‑X…, Ensure seller/buyer identifiers are correct (SIREN/SIRET, VAT ID) and Validate EN 16931 mapping and required code lists before submission, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Determine the recipient workflow (platform/portal vs network) and the required format (Factur‑X vs UBL/CII).
- Ensure seller/buyer identifiers are correct (SIREN/SIRET, VAT ID).
- Validate EN 16931 mapping and required code lists before submission.
- Submit via the chosen channel and keep confirmation/acknowledgement records.
Validation & compliance
Validation & compliance is where the general explanation of E-Invoicing in France becomes operational. The section focuses on Treat the XML payload as the invoice data of record (even if a PDF is present), Keep identifiers consistent across PDF header data and embedded XML and Validate VAT breakdown and rounding rules to avoid downstream rejections, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Treat the XML payload as the invoice data of record (even if a PDF is present).
- Keep identifiers consistent across PDF header data and embedded XML.
- Validate VAT breakdown and rounding rules to avoid downstream rejections.
Common pitfalls
Common pitfalls is where the general explanation of E-Invoicing in France becomes operational. The section focuses on Mismatch between PDF totals and embedded XML totals, Wrong or missing SIRET/SIREN values in party identifiers and Using the wrong profile/syntax for the recipient channel, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Mismatch between PDF totals and embedded XML totals.
- Wrong or missing SIRET/SIREN values in party identifiers.
- Using the wrong profile/syntax for the recipient channel.
Frequently asked questions
Frequently asked questions answers the practical questions that usually appear after reading the main explanation of E-Invoicing in France. The answers focus on When should I use Factur-X in France and What should I verify before submission and are written to clarify implementation choices quickly.
When should I use Factur-X in France?
Use Factur-X when the recipient accepts the hybrid PDF plus XML model, and confirm the required channel before sending.
What should I verify before submission?
Check SIREN or SIRET values, invoice totals, VAT breakdowns, and the recipient’s channel requirements so the file matches the expected profile.
Official links
Official links connects E-Invoicing in France with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding Chorus Pro (public invoicing portal), Factur-X (format information) and OpenPeppol (PEPPOL network) to validating or converting the invoice file.