France Confirms September 2026 E-Invoicing Go-Live and Publishes Start-Up Guidance

France will not be pushing back its e-invoicing reform. Despite speculation that the government might shift the launch to December 1, the mandate remains set for September 1, 2026. What has changed is the enforcement posture: the tax authority is signaling a soft landing for businesses that make a genuine, documented effort to comply.

The Release of a Start-Up Guide

On July 10, 2026, France’s Minister for Public Accounts gathered the reform’s “community of relays” at Bercy to confirm both the official timeline and the administration’s approach to controls. That same week, the Directorate General of Public Finances (DGFiP) released its practical start-up guide, Facturation électronique: guide pratique de démarrage, answering 29 questions across six themes: continuity of receipt, mandatory issuance, voluntary early adoption, e-reporting regularization, start-up incidents, and dialogue with the administration.

The DGFiP guide rests on three principles:

• The legal calendar is unchanged. The obligation takes effect on 1 September 2026.
• Economic continuity is protected. The reform alters how invoices are transmitted, not the underlying rules governing commercial debt, payment terms, accounting, or VAT deduction.
• Continuity does not mean exemption. Businesses that rely on a fallback channel while getting up to speed are expected to work toward regularization, not to treat the fallback as a lasting substitute for the electronic circuit.

What This Means for Businesses

Every business within the reform’s scope must be able to receive electronic invoices via an approved platform (PA) starting September 1, 2026. Large companies and mid-sized enterprises (ETI) are additionally required to issue invoices electronically and submit e-reporting data from that same date.

Smaller businesses – SMEs and micro-enterprises – are not required to issue electronic invoices until September 1, 2027. However, they must be fully prepared to receive e-invoices from larger suppliers starting September 1, 2026, which requires selecting a compatible approved platform (PA) or software solution in advance. They may also opt into the system earlier on a voluntary basis, provided this is done properly: through an approved platform, using complete invoices, and with client notification. Should an early voluntary attempt not work out, these businesses can revert to standard invoicing while continuing to prepare for their 2027 start date. Notably, a customer cannot compel a supplier whose obligation has not yet begun to issue electronic invoices ahead of schedule – any such arrangement remains a voluntary commercial choice.

Handling the Transition Period

Companies not yet fully connected to an approved platform are encouraged by DGFiP to start the process immediately, rather than wait until all requirements are met.

Large companies and ETIs are expected to follow a progressive rollout: activate the ready flows, prioritize higher-volume flows, transmit available data, and bring the remaining flows online in parallel. Technical difficulties do not pause these obligations, but they also will not be treated as automatic violations if handled transparently.

Several operational tolerances apply during this start-up phase:

• Invoices remain valid regardless of channel: An invoice received by email, PDF, or paper after September 1, 2026, remains valid, payable, and eligible for VAT deduction. The transmission method does not change the substance of the underlying transaction, provided the invoice reflects a real transaction and contains the necessary information.
• Regularization is encouraged, not mandatory for processing: Asking a supplier to correct a non-compliant invoice is good practice, but it is not a precondition for handling or paying that invoice.
• Duplicate invoices must be resolved, not rejected: If the same invoice arrives through multiple channels, the business must designate one reference copy and label the others as duplicates, rather than refusing them or processing them twice.
• Third-party failures are not automatically the company’s fault: If a service provider, software vendor, or state tool experiences an outage, the business should document the incident, continue operating, and regularize matters once the issue is resolved, without needing to fix the third party's failure itself.

For e-reporting specifically, any incidents should be documented and corrected precisely, by period, transaction, and amount, rather than resolved through an uncontrolled bulk catch-up. Businesses are also advised to keep records of correspondence, evidence of incidents, and remedial steps taken to demonstrate good faith if later questioned by the administration.

How to Document Start-Up Difficulties

This flexibility is not a blanket exemption from penalties. Sanctions will not be applied automatically to businesses facing genuine start-up difficulties, provided those difficulties are real, documented, and accompanied by corrective action. The administration will distinguish authentic difficulty from inertia, avoidance, or deliberate refusal to engage with the reform.

Evidence that can support a credible compliance trajectory includes:

• A signed contract with an approved platform, including a connection schedule
• Support tickets, error logs, and incident notifications
• Internal instructions issued to billing, accounting, or payment teams
• Flows that have already been switched over, even if full coverage has not yet been reached

Businesses are not required to report every isolated incident, but must be prepared to provide a complete, documented response if contacted by DGFiP.

Where the obligation concerns receiving invoices via an approved platform, the law provides a three-month formal notice period before any financial penalty can be imposed. Other sanctions remain fully in force, including per-invoice penalties for issuance failures and the e-reporting penalty regime, under CGI articles 1737, 1788 D, and 1737 IV bis.

AFNOR Updates Technical Standards Ahead of Go-Live

Alongside the administrative guidance, France’s standards body AFNOR published version 1.4 of the three technical standards underpinning the reform on June 30, 2026:

• XP Z12-012 – defines the semantic data model and syntax for all mandate formats, along with codelists and business rules
• XP Z12-013 – specifies a recommended standardized API for communication between businesses and approved platforms, intended to simplify solution portability
• XP Z12-014 – catalogs the commercial use cases that all platforms must support consistently

The main changes introduced in version 1.4 include:

• The addition of bidirectional self-billing – a single document that combines self-billing with a sale to the same counterparty, expected to be used particularly in the agricultural sector.
• Completed rules for cross-sales and margin-scheme VAT.
• Integrated the overseas consumption tax (octroi de mer)
• The clarification of the “Refused” status
• An addition of provisions for the energy, media buying, and real estate sectors, including VAT-liable co-ownership associations.

These additions bring the total number of documented use cases to 45, up from 44 in version 1.3, which was published on 26 February 2026 and had itself added 2 new cases while enriching cases 2, 13, 37, 38, and 41.

Whether version 1.4 will be the final update before go-live has not been officially confirmed by AFNOR or DGFiP. According to statements from the commission’s May 5, 2026, plenary session, the group is expected to enter maintenance mode following this release, with the next update anticipated in November 2026 and an annual update cadence thereafter. This has not been independently verified in an official AFNOR or impots.gouv.fr publication and should be treated as reported guidance rather than a confirmed fact.

There’s more you should know about e-invoicing in France – learn more about the new and upcoming regulations.