France Switches on Mandatory Electronic Invoicing From 1 September 2026: Every Business Must Be Able to Receive

France switches to mandatory electronic invoicing from 1 September 2026, and every VAT-registered business established in the country must, from that date, be able to receive structured electronic invoices through an approved platform. This is not a soft launch or a voluntary pilot: the receiving obligation applies universally and immediately, regardless of company size, while issuing and e-reporting duties are phased by category. Large companies and mid-sized enterprises (entreprises de taille intermédiaire, or ETIs) must also begin issuing electronic invoices and reporting transaction data from the same date, whereas smaller businesses have until 1 September 2027 to issue.

The legal foundation sits in the Code général des impôts (CGI), reinforced by the framework established under successive finance laws, and detailed operational guidance from the Direction générale des finances publiques (DGFiP). This pillar guide sets out who is in scope, the technical formats that qualify, contractual consequences, intra-group routing, penalties, and a practical readiness plan.

Intro: what changed and why it matters

The headline is simple and the deadline is fixed. France switches to mandatory electronic invoicing from 1 September 2026, replacing the informal exchange of PDF invoices by email, which will no longer satisfy the B2B requirement for transactions in scope, with structured, machine-readable invoices routed through an approved platform, the plateforme agréée (previously referred to as a plateforme de dématérialisation partenaire, or PDP). The obligation to receive compliant e-invoices lands on all VAT-registered entities at once; the obligation to issue them and to submit e-reporting data is staged by company size.

For in-house counsel, tax and compliance leads, and CFO teams, the practical challenge is threefold: confirm your scope, select and integrate a platform, and update contracts to reflect the new transmission and receipt mechanics. Non-compliance carries monetary penalties set by the CGI, subject to the caps and adjustments in force. The remainder of this article translates the statutory framework into an operational roadmap.

1. Who is in scope, receiving vs issuing obligations and timeline by company size

Scope is defined by VAT registration and by company size classification. Because France switches to mandatory electronic invoicing from a single fixed date for receipt, the first question every business must answer is not “when do I issue” but “am I ready to receive from 1 September 2026”. The answer, for any business established in France and subject to VAT, is that you must be.

Definitions: large company, ETI, SME and micro-entreprise

• Large companies (grandes entreprises). Entities exceeding the ETI thresholds, broadly, those with the largest headcount and turnover. They must issue e-invoices and perform e-reporting from 1 September 2026.
• ETIs (entreprises de taille intermédiaire). Mid-sized enterprises sitting between SMEs and large companies. They fall into the same first wave: issuing and e-reporting from 1 September 2026.
• SMEs (petites et moyennes entreprises). Smaller enterprises whose issuing obligation is deferred to 1 September 2027, though they must be able to receive from 1 September 2026.
• Micro-entreprises. The smallest businesses, also deferred to 1 September 2027 for issuing, but bound by the universal receiving obligation from 1 September 2026.

The critical takeaway is that deferral applies only to the issuing obligation. There is no deferral for receiving. An SME or micro-entreprise that cannot receive a structured invoice from a large supplier on 1 September 2026 is non-compliant, even though it will not have to issue until 2027. Company-size classification for these purposes follows the definitions used by the French tax administration; teams should confirm their category against current DGFiP criteria.

Practical examples: single-entity vs group

Consider a French SME buying from a large French supplier. From 1 September 2026, the supplier must issue a structured e-invoice through its platform; the SME must be connected to a platform able to receive it. Now consider a multinational group with a French large-company subsidiary invoicing a French SME sister entity: both the issuing subsidiary and the receiving sister must be on compliant platforms from day one, because the issuing entity is large. Company size is generally assessed at the level of the relevant entity or group as defined by the applicable thresholds, a nuance that materially affects rollout sequencing inside international groups, and one that should be confirmed with counsel for each structure.

2. Legal basis and official guidance

Understanding why France switches to mandatory electronic invoicing from this particular framework requires reading the CGI alongside the relevant finance laws and DGFiP’s operational documentation. Together they define the obligation, the enforcement regime and the implementation detail.

The statutory framework (summary)

The Code général des impôts establishes that issuance, transmission and receipt of electronic invoices for in-scope domestic B2B transactions must be carried out via an approved platform, a plateforme agréée. This is the pivotal legal mechanism: it is not enough to generate a structured file; the file must travel through an approved channel. This architecture, introduced by the reform, moves invoicing away from private bilateral exchange and toward a controlled, auditable network of certified intermediaries. Businesses should consult Legifrance for the current consolidated text of the applicable CGI provisions.

Key changes introduced by the finance laws

Successive finance laws confirmed and adjusted the timetable and enforcement framework surrounding the rollout, including the 1 September 2026 and 1 September 2027 dates. They address the penalty regime for non-compliant issuance and e-reporting and reinforce the practical consequences of failing to route invoices through an approved platform. Businesses should treat the current finance law as the authoritative reference for penalty thresholds and for any late adjustments to the timeline or enforcement approach.

DGFiP practical guidance, what it covers

The DGFiP publishes practical guidance on the impots.gouv.fr portal covering timelines, technical format references, the registration of platforms, and frequently asked questions on cross-border and intra-group scenarios. It is the primary operational resource for finance and IT teams, and it is the document to consult for sample data fields, testing rules and the current list of registered platforms. Because guidance is updated as the rollout progresses, teams should check the DGFiP pages directly rather than relying on secondary summaries.

3. Technical requirements: formats, transmission channels and approved platforms

The technical core of the reform is the shift from human-readable documents to structured data. When France switches to mandatory electronic invoicing from PDF-by-email to structured formats, the invoice becomes a data object that systems can parse, validate and reconcile automatically. This section explains the accepted formats and the transmission architecture.

Factur-X, UBL and CII, a quick technical primer

• Factur-X. A hybrid format combining a human-readable PDF with embedded structured XML data, developed jointly with the German ZUGFeRD standard. It is popular because it preserves a visual invoice while carrying machine-readable fields, easing the transition for teams accustomed to PDFs.
• UBL (Universal Business Language). A widely adopted XML standard for electronic business documents, used extensively across European e-invoicing networks.
• CII (Cross Industry Invoice). A UN/CEFACT XML syntax for invoices, forming part of the European semantic standard for e-invoicing (EN 16931).

All three are structured formats supported under the French reform. The essential point is that an invoice must carry validated structured data in one of these accepted syntaxes. A scanned or exported PDF attached to an email contains no structured payload the receiving platform can process, which is why it no longer satisfies the B2B requirement for transactions in scope.

What is a plateforme agréée?

A plateforme agréée is a platform authorised to issue, transmit and receive electronic invoices on behalf of businesses within the reform’s architecture. Registration is granted against official criteria covering security, data integrity, format handling and interoperability. Businesses connect to an approved platform, which handles routing, format conversion where needed, and the transmission of required data to the authorities. Businesses should verify a prospective provider’s status against the DGFiP’s published list.

Transmission models: portal, SFTP, API and hub/PEPPOL

Platforms typically offer several integration options:

• Web portal. Manual entry or upload, suitable for low-volume businesses with no ERP integration.
• SFTP. Scheduled file transfer of batches, appropriate for mid-volume operations.
• API. Real-time programmatic exchange integrated directly into ERP or billing systems, suited to high-volume issuers.
• Hub / PEPPOL. Connection through interoperability networks such as PEPPOL, which support cross-border transmission and standardised delivery between endpoints.

Because France switches to mandatory electronic invoicing from bilateral email to a networked model, the choice of transmission channel directly determines how much internal IT work is required. High-volume issuers will generally favour API integration; smaller receivers may start with a portal.

4. Issuing obligations and e-reporting

For large companies and ETIs, the 1 September 2026 date brings two parallel duties: issuing structured e-invoices and performing e-reporting. E-reporting is the transmission of transaction and payment data for flows that fall outside the domestic B2B e-invoicing perimeter, for example B2C transactions and certain international flows, so that the administration receives the data even where a mandatory structured invoice is not exchanged between two French VAT-registered parties.

Data fields and mapping

The structured invoice and the e-reporting stream both require defined data fields: parties’ identifiers, VAT numbers, taxable amounts, VAT rates and amounts, invoice references and payment data. Finance and IT teams must map these fields from source systems to the accepted format so that the platform can validate and transmit them. Incomplete or misformatted fields are a common cause of rejected invoices, so the mapping exercise should be treated as a project workstream in its own right.

Timing and reconciliation

E-reporting is submitted on a defined periodic basis, and businesses must reconcile the data transmitted against their accounting and VAT records. The reform effectively creates a continuous data feed to the administration, which raises the premium on accurate, timely reconciliation. Discrepancies between reported data and declared VAT will be more visible than under the legacy regime.

Common integration pitfalls

• Master data gaps, missing or incorrect VAT numbers and buyer identifiers that block transmission.
• Format mismatches between ERP output and the accepted structured syntax.
• Duplicate or credit-note handling that is not correctly represented in the structured format.
• Insufficient testing before go-live, leading to a spike in rejections at the deadline.

5. Penalties, enforcement and practical risk management

The reason France switches to mandatory electronic invoicing from a voluntary to a compulsory regime is enforcement, and the penalty framework gives the obligation teeth. Businesses should quantify their exposure early and build controls to keep it near zero.

How fines are calculated

The CGI provides for fixed monetary penalties for failure to comply with the e-invoicing and e-reporting obligations, calculated on a per-invoice or per-transmission basis and subject to an annual cap per business. Because the precise figures and caps are set by the CGI and may be adjusted by finance law, businesses should confirm the current amounts against Legifrance and DGFiP guidance rather than rely on a fixed figure. For a high-volume issuer, per-invoice penalties can accumulate quickly toward the annual cap, and separate exposure may arise in respect of e-reporting failures.

Mitigation and voluntary disclosures

• Run parallel testing well ahead of go-live to catch format and mapping errors before they generate penalties.
• Implement automated validation at the platform layer so non-compliant invoices are flagged before transmission.
• Maintain audit trails demonstrating good-faith compliance efforts, which support any dialogue with the administration.
• Where an error is discovered, correct it promptly and document the correction, as voluntary and timely rectification is generally viewed more favourably than administration-detected failures.

Industry observers expect enforcement to focus initially on systemic non-compliance, businesses that have made no attempt to connect to a platform, rather than isolated technical rejections, though the statutory penalties apply regardless of intent.

6. Contracts, commercial terms and recommended clause language

Because France switches to mandatory electronic invoicing from private document exchange to platform-mediated transmission, existing contracts frequently need amendment. Standard invoicing clauses drafted for PDF-by-email no longer reflect how invoices are lawfully delivered. The following sample clauses are illustrative only, seek legal advice before adopting them.

What to change in standard invoicing clauses

• Specify that invoices will be issued and delivered through an approved platform (plateforme agréée).
• Define the accepted structured format (for example Factur-X, UBL or CII).
• Set out when an invoice is deemed received and how disputes over transmission are handled.
• Allocate responsibility for platform failures and for maintaining accurate master data.

Sample clause: acceptance and deemed receipt

“The Supplier shall issue all invoices in a structured electronic format (Factur-X, UBL or CII) and transmit them to the Customer via an approved platform (plateforme agréée). An invoice shall be deemed received by the Customer upon successful delivery to the Customer’s designated approved platform, and the platform delivery record shall constitute evidence of receipt.”

Sample clause: intra-group routing

“Each Group entity that is VAT-registered in France and within the scope of the e-invoicing obligation shall connect to a designated approved platform. Intra-group invoices shall be issued, transmitted and received through such platforms in the required structured format, and the Group’s shared services centre shall maintain the mapping of entities to platforms.”

Sample clause: supplier/platform indemnity and liability

“The Supplier shall indemnify the Customer against penalties arising directly from the Supplier’s failure to transmit compliant electronic invoices, save where such failure results from incorrect data supplied by the Customer or from a failure of the Customer’s designated approved platform.”

7. Intra-group billing and cross-border issues

Multinational groups face the most complex analysis. When France switches to mandatory electronic invoicing from bilateral exchange to a networked platform model, groups must map precisely which legal entities are VAT-registered in France and in scope, then decide how to route flows between them and across borders.

Centralised invoicing: pros and cons

A centralised billing model, where a shared services centre or a single billing entity handles invoicing for multiple group companies, can simplify platform integration and standardise data quality. However, the obligation attaches to the legal entity that is the supplier of record for VAT purposes, not to the shared services centre as such. Groups must ensure that the entity legally issuing the invoice is correctly represented on the platform, even where processing is centralised. Decentralised models give each entity autonomy but multiply integration points and testing effort.

Cross-border transmission to and from France

Domestic B2B flows between two French VAT-registered parties fall within the mandatory structured e-invoicing perimeter. Cross-border flows, where one party is outside France, are generally addressed through e-reporting rather than mandatory structured invoicing between the parties, so the French entity must report the relevant transaction and payment data. Interoperability networks such as PEPPOL are relevant where groups wish to standardise cross-border transmission, and EU-level work on VAT digitalisation (including the “VAT in the Digital Age” package) is shaping how these flows will interoperate across member states over time.

Practical checklist for multinational groups

• Map every French VAT-registered entity and classify each by size to determine issuing dates.
• Confirm all entities can receive from 1 September 2026, without exception.
• Decide centralised versus decentralised invoicing and document the supplier-of-record for each flow.
• Identify which cross-border flows require e-reporting rather than structured invoicing.
• Align platform selection with any group-wide ERP and interoperability strategy.

8. Choosing and onboarding a plateforme agréée, procurement and IT checklist

Platform selection is the single most consequential procurement decision in the project. Because France switches to mandatory electronic invoicing from open exchange to approved-platform routing, the platform effectively becomes part of your compliance infrastructure.

Vendor due diligence

• Confirm the platform holds registration as a plateforme agréée under the official criteria and appears on the DGFiP list.
• Review the service level agreement, including uptime, support and incident handling.
• Check data retention, archiving and security arrangements, including where data is hosted.
• Verify supported formats (Factur-X, UBL, CII) and format-conversion capabilities.
• Assess transmission options (portal, SFTP, API, PEPPOL) against your volume and IT landscape.

Integration and testing

Plan for a testing phase in which invoices are generated, transmitted and received end to end in a controlled environment. Validate field mapping, credit notes, corrections and edge cases before go-live. The testing window should be built into the timeline with contingency, because integration issues are the primary cause of deadline slippage.

User training and change management

Finance, procurement and IT staff must understand the new process: how invoices are issued, how receipt is confirmed, how rejections are handled and how disputes are escalated. Change management is often underestimated; a technically compliant platform still fails if users revert to sending PDFs by email out of habit.

9. Implementation timeline: a 12-week readiness plan

With the deadline fixed, a structured programme is essential. The following twelve-week plan compresses the core workstreams; groups with many entities should extend it into a six-month programme.

1. Weeks 1–2. Scope assessment: map French VAT-registered entities, classify by size, confirm issuing dates and universal receiving obligation.
2. Weeks 3–4. Platform shortlist and due diligence: verify registration, SLAs, formats and transmission options.
3. Weeks 5–6. Contract review: identify agreements needing amendment; draft platform and clause updates.
4. Weeks 7–8. Integration build: connect ERP/billing systems, complete field mapping to structured formats.
5. Weeks 9–10. Testing: end-to-end issue, transmit and receive; validate edge cases and reconciliation.
6. Weeks 11–12. Training, go-live and monitoring: train users, activate the platform, and monitor rejections closely in the first weeks.

A readiness checklist and clause pack can help teams track each milestone.

Comparison table: receiving vs issuing obligations by company size and date

Conclusion and next steps

France switches to mandatory electronic invoicing from 1 September 2026, and the practical implications reach every VAT-registered business established in France, from the universal obligation to receive, to the phased duties to issue and report, to the contractual and cross-border adjustments that follow. The immediate priorities are clear: confirm your scope and company-size classification; ensure you can receive structured invoices through an approved platform by the deadline; select and integrate a plateforme agréée; and amend contracts to reflect platform transmission and deemed receipt. Large companies and ETIs must also stand up issuing and e-reporting capability from the same date, while SMEs and micro-enterprises should use the runway to 1 September 2027 wisely rather than complacently.

With statutory penalties applying to non-compliant invoicing, early, well-tested implementation is the surest route to compliance. For groups with French operations, a compliance review, covering scope mapping, platform selection, contract clauses and intra-group routing, is the sensible starting point. You can find guidance on how to choose an international tax lawyer in France and connect with the relevant expertise through the International Tax author profile, or read the broader introduction to navigating the complexities of international tax law.

This article is general information, is time-bound to the position as at the date of writing, is non-exhaustive, and does not constitute legal advice. Verify current requirements against official DGFiP guidance and seek local counsel for your specific circumstances.

Sources

1. Legifrance, Code général des impôts and applicable finance laws
2. Direction générale des finances publiques (DGFiP), e-invoicing practical guidance
3. Factur-X (ZUGFeRD / Factur-X official site)
4. PEPPOL, European eDelivery resources
5. European Commission, VAT digitalisation and e-invoicing
6. OECD, guidance on e-invoicing and VAT digitalisation