France’s B2B e-invoicing reform mandates the exchange of structured electronic invoices for domestic transactions between VAT-registered businesses, routed through approved platforms. It replaces PDFs and paper, introduces parallel e-reporting flows, and applies progressively from September 2026 to all French-established businesses.
Key Takeaways
- All VAT-registered businesses in France must be able to receive structured e-invoices from 1 September 2026.
- Issuance starts in phases: large and mid-sized companies in 2026, SMEs and microbusinesses in 2027.
- Domestic B2B transactions use e-invoicing; B2C and cross-border flows rely on e-reporting, not invoices.
- Invoices must pass through a state-approved platform and be routed using the central directory (Annuaire).
- Only structured formats such as Factur-X, UBL, or CII are compliant; emailed PDFs are not.
B2B e-invoicing is the mandatory exchange of invoice data in a structured electronic format for domestic transactions between VAT-registered businesses established in France. It replaces sending invoices as paper, email PDFs, or other unstructured documents.
France’s reform also introduces two related data flows:
Note: The reform concerns B2B. B2G e-invoicing already runs through Chorus Pro and continues under its existing rules.
This table helps you quickly determine whether e-invoicing, e-reporting, or both apply.
Transaction scenario | e-Invoicing required? | e-Reporting required? | Practical note |
Domestic B2B (both parties established in France, French VAT rules apply) | Yes | No (invoice flow covers reporting) | Includes advance payments relating to those transactions. |
B2G (invoice to the public sector) | Already mandatory via Chorus Pro | No | Separate channel from B2B onboarding. |
B2C (sales to consumers) | No | Yes | Transaction data is reported instead of an e-invoice exchange. |
Exports, imports, and many cross-border transactions | No | Yes (when in scope) | Reporting covers flows that do not have a domestic e-invoice. |
Services where VAT is due on payment (VAT on collection) | Depends | Often yes | Payment data must be reported on the required frequency. |
The e-invoicing mandate is phased by company size, with a universal receive milestone first, followed by phased issue obligations. Company size classification is tied to thresholds in French law and is relevant for determining which date applies.
The following table summarizes the operational deadlines most businesses plan around.
Company Category | Definition | Must be able to receive | Must issue (and e-report) |
Large enterprises | Typically 5,000+ employees or very high turnover thresholds (per French definitions). | 1 Sep 2026 | 1 Sep 2026 |
ETI (intermediate) | Roughly between SME and large (per French definitions). | 1 Sep 2026 | 1 Sep 2026 |
SMEs (PME) | Under SME thresholds (per French definitions). | 1 Sep 2026 | 1 Sep 2027 |
Micro-enterprises | Very small entities (per French definitions). | 1 Sep 2026 | 1 Sep 2027 |
These reform drivers explain why the changes go beyond invoice format and reach the full invoicing chain.
The key to compliance is combining the right platform, the right data format, and operational controls that prevent rejected invoices.
From September 2026, companies submit invoices via a government-approved platform, either directly or through a compliant solution that relies on an approved platform (PA or PDP officially).
A central directory called the Annuaire supports routing by identifying the recipient’s declared platform and invoicing address.

To be interoperable, invoices must be structured in a format supported by your platform and compatible with the ecosystem’s minimum common formats.
The fastest way to reduce rejections is to standardize invoice data and ensure identifiers match what is registered in the directory.
Mandatory element to manage
Invoices must be retained for at least six years under French tax law. Secure archiving requires preserving integrity, authenticity, and readability throughout the retention period, using tamper-proof storage, and traceable access logs.
France’s B2B e-invoicing model is built on a dual-layer framework that separates public regulatory oversight from private operational invoice exchange.
This end-to-end flow shows what must happen from invoice creation to delivery, reporting, and audit-ready archiving.
Step 1: Classify the transaction
Classify each sale using customer type, location, and VAT rules, then route it to either the e-invoice flow (domestic B2B) or the e-reporting flow (outside domestic B2B).
Step 2: Create a structured invoice in your ERP or billing system
Generate the invoice in a supported structured format and ensure mandatory legal and VAT fields are populated, including the new mandatory particulars that apply at go-live.
Step 3: Validate the invoice before submission
Run pre-checks for mandatory fields, arithmetic, VAT logic, and identifiers, including customer SIREN or SIRET and delivery address rules.
Step 4: Submit the invoice to your approved platform
Send the invoice to the platform for format checks, business-rule validation, and preparation for routing to the recipient’s platform.
Step 5: Route using the Annuaire
The platform queries the Annuaire to find the recipient’s declared platform and invoicing address, then routes the invoice accordingly.
Step 6: Receive acknowledgements and life-cycle statuses
Platforms exchange standardized acknowledgements and life-cycle statuses so both parties can track delivery, processing, and outcomes inside their AR and AP workflows.
Step 7: Buyer processing and dispute handling
If the buyer rejects or refuses the invoice, treat it as an exception workflow: correct data, issue a replacement invoice or credit note where required, resend, and retain the audit trail.
Step 8: Transmit e-reporting and payment data when required
For sales outside domestic B2B, the platform transmits the required transaction data to the administration. For services where VAT is due on payment, it also transmits payment information on the required schedule.
Step 9: Archive and retain audit evidence
Store the structured invoice, any human-readable representation if used, and all acknowledgements and status logs in an audit-ready archive.
Correct routing ensures every invoice reaches the buyer through the PA they have declared in the Annuaire. If routing fails, invoices may be rejected or never delivered, and required tax data may not be reported. This routing logic allows businesses to use different providers while ensuring interoperability, traceability, and consistent tax reporting across the entire e-invoicing framework.
The table below explains, in simple terms, how invoices and reporting data move in each scenario.
Business situation | How the invoice is exchanged | What is sent to the tax authority |
Sender and buyer use the same PA (approved platform) | A single PA handles invoice submission, delivery to the buyer, and status updates | The PA automatically transmits the required invoice data to the tax authority as part of the process. |
Sender and buyer use different PAs | The sender’s PA identifies the buyer’s PA via the Annuaire and routes the invoice to it | Invoice data and any required reporting data are transmitted through the respective PAs to the tax authority. |
Transaction is outside domestic B2B scope, such as B2C or many cross-border sales | No e-invoice is exchanged between parties | Only transaction data, and payment data when required, is reported to the tax authority via the PA. |
Use this checklist to turn the mandate into an operational process that does not break at go-live.
These actions reduce integration delays and rejection rates.
It is important to determine the operating approach based on invoice volume, integration needs, and process maturity.
Decision Factor | Public Portal Approach (manual) | Approved Platform (PA) Approach (integrated) |
Invoice volume | Best suited for very low volume issuance and reception. | Best suited for recurring volume and automation requirements. |
ERP integration | Limited integration, more manual work. | Designed for ERP and workflow integration and format conversion. |
Operational monitoring | Requires disciplined portal checks and manual exception handling. | Enables automated alerts, routing, and exception workflows. |
Compliance scalability | Compliance is possible but process risk rises with volume. | Scales better for multi-entity and multi-system environments. |
Its important to partner with the right platform for e-invoicing compliance. Here are a few thing you could consider
This table highlights the most common issues that block delivery and how to prevent them.
Common failure point | How to prevent it |
Recipient not found or wrong routing address | Keep customer identifiers and invoicing address validated against the Annuaire. |
Missing new mandatory particulars | Update invoice templates to capture customer SIREN, delivery address logic, and transaction category. |
VAT calculation or totals mismatch | Add automated arithmetic and VAT rule checks before sending. |
Format validation error | Use platform validation in pre-production and lock to a supported format profile. |
Unresolved rejected or refused statuses | Define a timed exception workflow and track resolution until closed. |
France's framework includes financial penalties and practical commercial consequences that can disrupt cash flow. Penalties referenced in implementation guidance include a per-invoice fine for failing to issue electronically when required and a per-report fine for missing e-reporting obligations, both with annual caps.
These benefits come from treating e-invoicing as a process upgrade rather than a last-minute compliance change.
France’s B2B e-invoicing reform is less about replacing PDFs and more about making invoice data usable across finance, tax, and operations. Start with clean identifiers and transaction mappings, then choose a platform you can operate reliably, test early, and treat exceptions as a tracked workflow, not an afterthought.
Use these official references to validate scope, deadlines, directory lookups, and platform registration.
Resource | What it covers |
Service-Public: publication of the list of registered approved platforms | Official rollout timetable, scope highlights, new mandatory particulars, and links to the platform list and legal texts. |
Reform overview, calendar PDFs, and access to the official list of approved platforms. | |
Definitions of e-invoicing, e-reporting, and payment reporting. | |
Directory search to identify recipient routing details (platform and invoicing address). | |
| DGFiP external specifications for B2B e-invoicing and e-reporting | Technical and standards references for platform exchanges and reporting services. |