France E-Invoicing Fines Take Effect September 2026

A PDF attached to an email is not an e-invoice. Starting 1 September 2026, that distinction carries a €50 fine per invoice.

France's e-invoicing mandate has been discussed for years, delayed twice, and revised repeatedly. The 2026 Budget Law, officially approved on 2 February 2026, locked in the final rules. The penalties are steeper than previous drafts proposed, but a grace period softens the transition for one specific failure mode. Here is what finance teams need to know before September.

What takes effect on 1 September 2026

Two obligations kick in simultaneously.

First, all companies established in France and subject to VAT must be able to receive electronic invoices from that date. Every VAT-registered business, regardless of size.

Second, large companies and mid-sized companies (ETIs) must begin issuing e-invoices. SMEs and micro-enterprises get an extra year for issuance (1 September 2027), but the receive obligation is universal from day one.

Non-established large and intermediate-sized taxpayers have a deferred issuance deadline of September 2027, though they too must be able to receive from September 2026.

The government's stated objectives: combating VAT fraud through improved traceability, standardising business processes, and eventually pre-filling certain VAT returns from the collected data.

The penalty structure: tripled fines, one grace period

The 2026 Budget Law rewrote the fine schedule. The numbers are significantly higher than what earlier drafts proposed.

E-invoicing non-compliance: €50 per invoice, capped at €15,000 per calendar year. The previous figure was €15 per invoice. That is more than a tripling.

E-reporting non-compliance: €500 per transmission, also capped at €15,000 per year. The former penalty was €250. E-reporting covers B2C sales taxable in France and cross-border transactions, not just domestic B2B.

A business processing 300 invoices per month hits the €15,000 annual cap in just one month of non-compliance.

There is one built-in safety valve. Taxpayers that fail to use an accredited platform to receive e-invoices will be notified by the tax authority and given a three-month period to correct the compliance gap before fines apply. That grace period only covers the platform registration requirement. It does not cover ongoing issuance failures or e-reporting obligations.

The most common compliance mistake: PDFs are not e-invoices

This is where most businesses will trip up.

Under the reform, an e-invoice must use a structured format that allows automated processing. The accepted formats are Factur-X, UBL, and CII. A standard PDF sent by email is not, in itself, an electronic invoice within the meaning of the reform, unless it is part of a compliant system (Factur-X embeds structured XML data inside a PDF/A-3 container, which does qualify).

The distinction matters because many businesses believe they already send “electronic invoices” when they email a PDF. Under this mandate, that workflow is non-compliant. The invoice must contain machine-readable structured data, transmitted through an accredited platform.

If your current process involves receiving vendor invoices as PDF attachments and manually keying them into your accounting system, the September 2026 deadline changes both sides of that workflow. For more on how AI handles PDF invoice extraction today, see our guide on extracting data from PDF invoices.

New mandatory invoice fields from September 2026

The format requirement is not the only change. Invoices issued from September 2026 (for large companies and ETIs) must include four new mandatory fields:

• Customer SIREN number (the nine-digit French business identifier)
• Delivery address of goods, where it differs from the billing address
• Transaction category: whether the invoice covers goods, services, or both
• VAT-on-debits flag, where the supplier has opted for payment of VAT on debits

SMEs and micro-enterprises must include these fields from 1 September 2027.

These fields must be captured at the point of invoice creation, not added later. That means upstream data collection (purchase orders, supplier onboarding, delivery records) needs to feed the right information into your invoicing system before the invoice is generated. You can use a VAT calculator to verify tax amounts and an invoice validator to check that your documents include the required fields before submission.

Rollout timeline by business size

The mandate uses turnover thresholds to determine which businesses must issue e-invoices and when:

The receive column is uniform. Every VAT-registered business must accept structured e-invoices from September 2026, even if they are not yet required to issue them. If you are an SME receiving invoices from a large supplier, you need a compliant receiving setup twelve months before your own issuance deadline.

How the infrastructure works: accredited platforms and the Central Directory

E-invoices do not flow directly between buyer and seller. They route through government-accredited platforms called Plateformes Agréées (PAs), replacing the earlier “PDP” terminology.

The Public Invoicing Portal (PPF) serves as the Central Directory, responsible for routing invoices to the correct recipients based on data populated by the PAs. As of January 2026, over 100 accredited platforms had been approved by DGFiP.

One practical protection: a one-year minimum service continuity requirement obliges your former PA to maintain services when you switch platforms. That reduces the risk of being locked into a platform that does not fit your needs.

E-reporting data (for B2C and cross-border transactions) follows a separate cadence. Under the standard VAT regime, transmission happens by ten-day period, within seven days. This is not real-time reporting.

What this means for invoice processing workflows

The France e-invoicing September 2026 mandate is a structured data requirement. Compliance depends on your ability to generate, transmit, and receive invoices in Factur-X, UBL, or CII format, with the correct mandatory fields, through an accredited platform.

For accounts payable teams, this shifts the question from “can we read this invoice?” to “can we ingest structured data and validate it against the new field requirements?” AI invoice processing tools that parse Factur-X and UBL natively, extract SIREN numbers, delivery addresses, and transaction categories, and flag missing fields before submission reduce the risk of non-compliance fines stacking up. For a deeper look at how AI handles invoice data extraction, see our guide to AI invoice processing.

The three-month grace period for platform registration provides a window, but it only applies once and only to the receive-side platform requirement. For everything else, the fines are immediate.

FAQ