E-invoicing
Issuing and receiving the domestic B2B electronic invoice through an approved platform, in a structured format such as Factur-X, UBL or CII.
Operational Guidelines - DGFiP
What to do, in which scenario, with which flows. A practical guide to the French B2B e-invoicing reform: mandatory e-invoicing, e-reporting, payment reporting, approved platforms (PDP).
Overview
The French model rests on three distinct obligations. Each transaction falls under at least one of them, and knowing which one applies drives the document, channel and data flow.
Issuing and receiving the domestic B2B electronic invoice through an approved platform, in a structured format such as Factur-X, UBL or CII.
Sending transaction data to the DGFiP for operations that are not e-invoiced: B2C sales and cross-border transactions.
Sending collection data when VAT becomes chargeable on payment, typically for supplies of services.
The four operational scenarios
Every operation of a French company maps onto one of four scenarios. The scenario determines the document, the channel and what the DGFiP must receive.
A French company invoicing another French company. This is the core of the reform: mandatory e-invoicing through an approved platform.
Factur-X, UBL or CII. A plain PDF is not compliant for this flow.
Statuses such as received, rejected and paid travel back through the platform.
Invoice data is sent to the tax authority by the platform itself.
Only if VAT on the operation is chargeable on payment.
A French company selling to the end consumer. No B2B e-invoice is required, but e-reporting applies.
The structured electronic invoice is not the document required toward the consumer.
Aggregated data of B2C operations is sent to the DGFiP.
For services where VAT becomes chargeable on payment, collection data may also be required.
A French company invoicing a foreign business customer. French domestic e-invoicing does not apply, but the e-reporting obligation remains.
The invoice does not travel through an FR-approved platform.
Operation data is still sent to the DGFiP.
Only if the operation is relevant for VAT on payment.
A foreign supplier invoicing a French company. The incoming invoice does not pass through the French system, but FR-side reporting may still apply.
The incoming invoice does not pass through the FR platform system.
Required if the operation is relevant for French VAT.
Intra-EU purchases, reverse charge and self-invoicing.
Infrastructure
The platform does more than carry the file. It is the only allowed channel for domestic B2B invoices, and it also sends mandatory data to the tax authority.
Matrix
A consolidated view to keep at hand: the operation drives which flow applies and what you must send to the DGFiP.
| Operation | Document / flow | Format | DGFiP reporting |
|---|---|---|---|
| Domestic B2B - FR to FR | E-invoice through the platform | Factur-X, UBL or CII | Invoice data auto-sent by the platform |
| B2C | No mandatory B2B e-invoice | Not necessarily Factur-X | Transactional e-reporting |
| B2B cross-border export / import | No French domestic e-invoice | Depends on the commercial setup | Transactional e-reporting |
| Services with VAT on payment | E-invoice or e-reporting, depending on the case | Depends on the flow | Also collection / payment data |
Reading key: the nature of the operation determines both the channel and the reporting obligation.