France e-invoicing reform 2026: what changes

What is France's e-invoicing reform?

France's e-invoicing reform requires VAT-registered businesses established in France to exchange invoices with each other in structured form through an approved platform (plateforme agréée), and to report data on their other transactions to the tax authority (e-reporting). It matters because, since 1 September 2026, every business in scope must be able to receive such invoices.

The rule sits in Article 289 bis of the French General Tax Code (CGI): issuing, transmitting and receiving electronic invoices must go through an approved platform. A PDF sent by email is therefore no longer the target channel for business-to-business transactions within the reform. The substance does not change: whether a transaction exists, the trade debt, the accounting entry and the right to deduct VAT follow the usual rules, as the tax authority's (DGFiP) practical start-up guide of July 2026 points out.

The authority gives three aims: narrowing the VAT gap with transaction data available as it happens, preparing pre-filled VAT returns and speeding up invoice processing at the customer. For an accountant, the quality of invoicing data becomes a tax question rather than a formatting one.

The French e-invoicing timeline, as of September 2026

The legal timeline, confirmed by Service-public.fr (page checked on 11 August 2026) and the DGFiP guide, separates receiving, which applies to everyone, from issuing, which depends on company size. The size category is that of the company: large enterprise, intermediate-sized enterprise (ETI), SME or micro-enterprise.

A company whose issuing obligation starts in 2027 may join voluntarily earlier, provided it uses an approved platform. A customer cannot force it to issue e-invoices under the legal obligation before 1 September 2027, and must not refuse to pay an invoice simply because it is not electronic.

• 1 September 2026: obligation to receive for all businesses in scope, whatever their size
• 1 September 2026: obligation to issue and to e-report for large enterprises and ETIs
• 1 September 2027: obligation to issue and to e-report for SMEs and micro-enterprises
• Start-up phase: no penalties for businesses on a serious compliance path, with no postponement or suspension of the obligation

Approved platforms, the directory and the concentrator

An approved platform (PA, formerly called a partner dematerialisation platform or PDP) is an operator registered by the tax authority for a renewable period of three years. It issues, transmits and receives e-invoices, extracts and passes their data to the authority, and transmits data on transactions without an e-invoice and payment data. A business chooses its platform directly or through its business software, its chartered accountant or its bank.

The directory (annuaire), which the State makes available to the platforms, routes each invoice to the recipient's receiving platform using its identifiers, in particular the SIREN company number and, where relevant, the SIRET establishment number. When routing fails, the DGFiP guide says to check those identifiers first, then confirm the receiving details with the customer and keep a record. The State's concentrator receives the data sent by the platforms.

In practice there are at least four parties: the supplier, its platform, the customer's platform and the customer, with the authority receiving the tax data. That is what separates the French model from a clearance model, in which the State must validate each invoice before it reaches the buyer.

Formats, statuses and the invoice lifecycle

The external specifications published by the authority (version 3.2 of 30 April 2026) rely on AFNOR standards XP Z12-012 for message formats and profiles, XP Z12-013 for the interfaces between company systems and platforms, and XP Z12-014 for use cases. The three base formats are UBL, UN/CEFACT CII and Factur-X, the last combining a readable PDF and a structured XML file, all aligned with the European semantic model EN 16931.

Each invoice follows a lifecycle of statuses exchanged between platforms. The DGFiP guide draws a distinction finance teams need to learn: a rejection by a platform is a technical incident (format, missing mandatory data, wrong identification, routing), whereas a refusal by the buyer is a reasoned status, limited to the grounds allowed by the standard, which must not be used for an ordinary commercial dispute.

When the buyer refuses with good reason, the seller issues a new invoice with a new number or neutralises the old one with a credit note; it never reuses the same number. When an error is fixed after a rejection, the same invoice goes back through the circuit, with no second accounting entry.

• Rejected: the platform blocks the invoice for a format, content or routing problem
• Refused: the buyer disputes the invoice on a ground allowed by the standard and must give the reason
• Cashed (encaissée): the status that tracks payment, notably for services where VAT is due on receipt of payment
• Duplicate or continuity copy (a labelling rule, not a status): a copy sent through another channel must be linked to the original invoice to avoid paying twice

E-reporting: B2C, international and payment data

E-reporting covers the transactions that do not travel as an e-invoice between two VAT-registered businesses established in France. It concerns transaction data and, in some cases, payment data, sent to the authority by the approved platform the business has chosen, under Articles 290 and 290 A of the CGI. The data include the identity of supplier and customer, the net amount, the VAT due and the rate applied.

In practice three families of transactions are involved: sales to consumers (B2C), transactions with businesses not established in France, both purchases and sales, and cash-receipt data for services taxed on a cash basis. Minimum reporting frequencies depend on the VAT regime and are set in Annexes II and IV of the CGI.

E-reporting starts on the same dates as issuing: 1 September 2026 for large enterprises and ETIs, 1 September 2027 for SMEs and micro-enterprises. A temporary transmission problem does not affect the validity of invoices or payments; it must be documented and then corrected without creating duplicates.

New mandatory invoice mentions and a worked example

Four mentions are added to the usual ones in Article 242 nonies A of Annex II to the CGI. They are not cosmetic: without the customer's SIREN the platform cannot route the invoice, and without the transaction category the authority cannot work out when VAT becomes due.

Example: an ETI invoices a maintenance service of EUR 10,000 net on 15 October 2026 to a customer established in France, with VAT at 20 percent, so VAT of 2,000 and a total of 12,000. The invoice shows the customer's SIREN, the category services and, if the supplier has opted, the mention Option pour le paiement de la taxe d'après les débits. The supplier's entry is unchanged: Dr 411 Customers 12,000 / Cr 706 Services revenue 10,000 / Cr 44571 Output VAT 2,000. If the customer later refuses 2,000 net on a ground the standard allows, the credit note sent through the same circuit reverses 2,400: Dr 706 2,000 / Dr 44571 400 / Cr 411 2,400.

• The customer's SIREN number
• The delivery address for goods, if it differs from the customer's address
• The nature of the transactions: supplies of goods, services, or both
• The mention that the supplier has opted to pay VAT on invoicing (option pour le paiement de la taxe d'après les débits), where it has

Penalties and the start-up phase

The DGFiP's practical guide of July 2026 announces a start-up phase in which penalties are not applied to businesses facing difficulties that are on a serious compliance path, stressing that this is neither a postponement nor a suspension. The authority will separate those cases from inertia, avoidance or a lasting refusal to join. Useful evidence is concrete and dated: a contract with an approved platform, a connection schedule, tests, support tickets, internal instructions.

The amounts are set by law. Article 1737 of the CGI, as in force since 21 February 2026, sets a fine of EUR 50 per invoice not issued electronically, capped at EUR 15,000 per calendar year. For receiving, a business without an approved platform first receives formal notice to comply within three months, then a fine of EUR 500, then a further EUR 1,000 for each additional three-month period. Article 1788 D fines e-reporting failures at EUR 500 per transmission, capped at EUR 15,000 per calendar year, with no fine for a first offence in the current and three previous years if it is corrected spontaneously or within thirty days of a request.

Example: an ETI that issued 400 invoices as PDFs over a year with no compliance path would face 400 x 50 = EUR 20,000 of fines, reduced to the EUR 15,000 cap. The financial risk is real, but the operational one is larger: rejected or misrouted invoices delay collections.

What an ERP must do for the French reform

The approved platform carries and checks the invoice; the ERP remains the source of the data. If the SIREN is missing from the customer record, the transaction category is not set per item or VAT rates are wrongly assigned, the platform will reject the invoice however good it looks. The work starts with master data, before the technical connection.

On the purchasing side, receiving is the underestimated half: structured supplier invoices have been arriving since 1 September 2026 and must be matched to orders and goods received without double entry or double VAT deduction. The DGFiP guide recommends choosing one reference invoice and marking other copies as duplicates.

• Hold SIREN and SIRET numbers for customers and suppliers, and a separate delivery address
• Classify each item or service as a supply of goods or a service
• Compute VAT per line with the right rate and the right tax point (invoicing or payment)
• Keep continuous numbering and never reuse a number after a refusal
• Correct with a credit note, never by editing an invoice already sent
• Track lifecycle statuses next to the invoice, not in a separate technical log
• Record customer receipts so that payment e-reporting has its data
• Keep evidence of the compliance effort during the start-up phase

French e-invoicing with Skyline Nexus ERP

Skyline Nexus ERP already holds the core invoicing data an approved platform works from. Each business location chooses its own invoice numbering scheme, VAT rates and tax groups are set in Settings > Tax Rates, and a final sale posts automatically when auto-post is on: debit receivables, credit revenue by product category and credit output VAT, with VAT computed line by line in the same way as the tax report. Corrections go through sales returns, which produce credit notes and reverse revenue, VAT and cost of sales, and every accounting change leaves a record with old and new values in the Audit Trail.

National e-invoicing connectors are being rolled out market by market: tell us you operate in France and we will confirm your go-live date. Until then, the working route is a partner-led integration with the approved platform of your choice: the Connector module's REST API exposes sales, sales returns, contacts, taxes and payments, so the provider can pick up invoices issued in the ERP, and supplier invoices received can be brought in from the platform's spreadsheet export with Import Purchase, which offers a preview and can revert a batch.

The team knows regulated invoicing models: Skyline Nexus ERP runs the ZATCA Phase 2 integration in Saudi Arabia in production, with certificate onboarding, compliance checks, invoice clearance and reporting, XML files and QR codes. The interface is available in English and Arabic, with interface translations including French.