France’s e-invoicing reform treats B2B and B2C differently. Domestic B2B invoices move through the regulated e-invoicing ecosystem, while B2C transactions generally shift to e-reporting of sales data.
Key Takeaways
- Domestic B2B invoicing shifts to platform-based e-invoicing using structured or hybrid formats aligned with EN 16931.
- B2C transactions usually do not require issuing an e-invoice, but they do require e-reporting of transaction data to the tax authorities.
- From September 2026, all companies must be able to receive electronic invoices, while issuing obligations are phased by company size.
- Businesses with mixed sales must separate workflows: e-invoicing for domestic B2B and e-reporting for B2C and certain cross-border flows.
- The main compliance risk is incorrect transaction classification, not format choice.
France is moving to a model where invoice exchange and invoice data reporting are standardized through an approved platform ecosystem. The objective is to strengthen VAT controls, improve data quality, and reduce reporting friction for both businesses and the tax administration.
At a high level, the reform creates two distinct compliance tracks:
The reform relies on a controlled platform architecture rather than direct invoice exchange between businesses.
This model shifts compliance focus from simple document delivery to controlled data exchange and status tracking.
The timeline below drives readiness planning across finance and IT teams.
B2B e-invoicing applies to invoices issued between taxable persons established in France for transactions that are considered domestic for VAT purposes. This is the “full invoice” compliance track. The invoice itself must be created in a compliant electronic format and routed through the approved platform ecosystem.
B2B e-invoicing covers any sale of goods or services between two VAT-taxable businesses acting as taxable persons, where VAT rules treat the transaction as within scope for business invoicing and controls. Includes but not limited to
This extends the existing public-sector invoicing approach to most inter-company transactions in the private sector.
B2B e-invoicing relies on structured, or hybrid formats aligned with the European standard EN 16931.
The commonly referenced formats include:
For many organizations, e-Invoicing reform represents a significant operational shift.
The following steps should be followed for a typical compliant B2B invoice lifecycle.
To minimize rejections and delays, businesses typically need to configure:
For B2C transactions, the core obligation is generally not the issuance of an electronic invoice to the consumer. Instead, businesses must transmit transaction data to the tax authorities through e-reporting.
The customer-facing document, such as a receipt or invoice, can usually remain unchanged. The compliance obligation lies in the reporting of sales data.
In B2C e-Reporting reform affects reporting rather than the sales experience.
The scope of e-reporting covers any sale from a VAT-taxable business to a final consumer (or other non-business customer).
e-Reporting Framework and Format
France’s e-reporting framework has two components:
The reform materials describe three practical ways to submit e-reporting:
For payment reporting specifically, the official reform deck notes it can be transmitted via the chosen platform, either through invoice status (for example, “paid”) or via an XML file / online entry depending on the situation
This simplified workflow shows how B2C compliance typically operates.
The reform materials describe three practical ways to submit e-reporting:
For payment reporting specifically, the official reform deck notes it can be transmitted via the chosen platform, either through invoice status (for example, “paid”) or via an XML file / online entry depending on the situation.
Unlike e-invoicing-style data exchange, e-reporting is not necessarily daily. In France, e-reporting is periodic, and the frequency depends on your VAT regime (which often matches how frequently you file VAT returns). Here’s the official frequency and deadline used for transaction data e-reporting:
VAT Regime | Frequency | Deadline To File |
Monthly Filing | 3 times per month (per 10-day period) | Within 10 days after each period, which typically lands on the 20th, 30th (except February), and 10th of the following month |
Quarterly Filing | Once per month | Before the 10th of the following month |
Simplified VAT Regime | Once per month | No later than the 25th to 30th of the following month |
Basic VAT Exemption Scheme | Once every 2 months | No later than the 25th to 30th of the month following the period end |
The table below highlights the main differences businesses must reflect in system design and processes.
Dimension | B2B e-Invoicing (Domestic) | B2C (Primarily e-Reporting) | Practical Impact |
Obligation Type | Full electronic invoice exchange through the regulated ecosystem. | Transmission of transaction data rather than invoice exchange. | Two separate compliance outputs are required. |
Counterparty | Taxable persons established in France. | Consumers and other non-B2B cases. | Accurate customer classification is essential. |
Document Format | Structured or hybrid formats such as CII, UBL, and Factur-X. | Sales records and reporting datasets. | Reporting focuses on data extraction, not invoice rendering. |
Transmission Channel | Approved platform selected by the business. | Approved platform for e-reporting. | A single platform can support both if configured correctly. |
Data Granularity | Invoice-level, often line-level structured data. | Transaction-level or aggregated VAT data. | Data models must support both detail and aggregation. |
Primary Failure Mode | Invoice rejection due to invalid or missing fields. | Reporting mismatches with ledgers or VAT returns. | Controls differ for invoicing versus reporting. |
The scenarios below illustrate how to apply the rules in practice.
A supplier sells goods to a French business customer. Both parties are taxable persons established in France.
Treatment:
A business sells goods or services to a consumer in France.
Treatment:
A business sells goods to a customer outside France.
Treatment:
Organizations with both B2B and B2C revenue need a coordinated approach.
The issues below frequently cause rejections or reporting gaps.
France’s reform is not a single technical upgrade. It is a data-driven compliance shift that separates domestic B2B invoicing from B2C and cross-border reporting. Businesses that invest early in classification logic, VAT data consistency, and platform integration will reduce rejections, protect cash flow, and stay audit ready as enforcement tightens.