Message IconCustomer SupportUser IconContact SalesLock IconLogin

France's E-Invoicing Mandate September 2026

France e-invoicing mandate going live september 2026

Here's What You Need to Know

The days of emailing a PDF invoice to French business partners are numbered. We break down the mandate, the five-corner model, and how to get compliant before the deadline.

If your business handles invoicing with French companies, September 1, 2026 is a date you need to circle in red. France's landmark e-invoicing mandate officially takes effect, and it's far more comprehensive than simply switching from PDFs to digital files. It's a full-scale shift in how tax data is captured, transmitted, and reported — and the window to prepare is closing fast.

To help demystify this, Arratech hosted a live webinar with Thibault Samson, co-founder of The Invoicing Hub and one of France's leading independent experts on the mandate. Here's what every software vendor, ERP provider, and finance team needs to understand.

What the mandate actually requires

At its core, the French mandate makes electronic invoicing compulsory for domestic B2B transactions — meaning any invoice between two French businesses. But the requirements go well beyond that:

E-invoicing replaces PDF, postal, or email invoices for French B2B transactions. Invoices must be transmitted electronically through a certified platform and in one of three mandatory formats: UBL, CII, or Factur-X (a hybrid format combining a human-readable PDF with an embedded XML invoice, similar to Germany's ZUGFeRD).

The invoice life cycle requires both parties to exchange structured status updates throughout the invoice's journey — from "submitted" and "sent by platform," through "approved," "disputed," "suspended," and ultimately "paid." Some statuses are mandatory, others optional, but all require your systems to communicate in a structured XML format.

E-reporting extends the mandate to international B2B transactions and all B2C transactions. Rather than transmitting invoices themselves, companies must send periodic reports of tax-relevant data to the French tax authority (DGFiP). Depending on your VAT regime, this can be required every 10 days, monthly, or bi-monthly.

The deadlines, broken down by company size

Deadlines for French e-Invoicing mandates

Understanding the five-corner model

France has moved away from a centralized platform model (like Italy's SDI) and instead adopted what's effectively a five-corner exchange model. Here's how each party fits together:

5 corner model for e-invoicing applied in France

Two terms are essential here. The PA (Plateforme Agréée) is a privately certified platform that handles transmission between supplier and buyer, and simultaneously extracts tax data for the government. Using a PA is mandatory you cannot transmit compliant invoices without one.

The PPF (Portail Public de Facturation) is the government's public billing portal. It acts as a data concentrator for all tax extracts and e-reports, and hosts the annuaire a public directory that works just like a Peppol SMP, identifying which PA each company uses. Invoices are exchanged over the Peppol network in one of the three mandated formats. If an invoice fails the PA's technical validation, it is rejected before transmission the tax liability remains with the sender.

The complexity hiding in plain sight: use cases

Beyond the core framework, the mandate defines 44 (and growing) specific "use cases" real business scenarios that require extended invoice formats or special handling. These include factoring arrangements, marketplace transactions, subcontracting, self-billing, insurance payments, deposit invoices, and even employee expense reimbursements.

PAs are not required to support every use case, so it's essential to map which ones apply to your business and confirm your platform covers them. The specifications are published by the AFNOR commission in document XP Z12-014 — and the guidance was updated as recently as February 2026, so staying current matters.

How Arratech makes compliance fast and future-proof

Arratech was built by founders with decades of experience of the Peppol network, including former OpenPeppol leadership. That foundation shapes everything about how our platform works.

We handle the transport layer so you can focus on the invoice payload and your core product. Our infrastructure is scalable to handle any transaction volume, and we partner with a SecNumCloud-certified hosting provider to meet French sovereign cloud requirements.

Not sure if we're the right fit? You can sign up for a free sandbox environment directly on our website and have your technical team test the integration today no sales call or subscription required.

Contact Us

FAQs Hero Image

FAQs

Do I need to upgrade my SMP immediately?

No, but don’t wait until the last moment. Migration to HTTPS must be complete by Feb 1, 2026, and you can begin moving from Nov 1, 2025. Early testing is strongly recommended.

Will the switch to NAPTR records disrupt document exchange?

Not if you prepare. Both CNAME and NAPTR will work in parallel from May 1 – Nov 1, 2025, giving you a testing window. By Feb 1, 2026, all systems must use NAPTR.

Do I need new infrastructure to comply?

In most cases, no. You’ll need:

  • Valid TLS certificates for HTTPS
  • DNS updates to support NAPTR records
  • Updated software configurations for Access Point lookups

Glossary

Peppol Service Metadata Publisher (SMP)

A Service Metadata Publisher (SMP) is a registry on the Peppol network that stores essential details about a business or organisation — such as which types of electronic documents (e-documents) it can receive (e.g., e-invoices, purchase orders) and how those documents sho

If your organisation wants to receive e-documents via Peppol, it must be registered in an SMP. Without this registration, other companies and government agencies cannot find the technical information they need to deliver documents to you.

Service Metadata Locator (SML)

The Service Metadata Locator (SML), the only central component in the Peppol eDelivery Network. It keeps track of where each participant’s Service Metadata Publisher (SMP) is located. When a sender wants to deliver an electronic document, their Access Point queries the SML to find the correct SMP address for the recipient. The SMP then provides the detailed technical information needed to send the document securely and correctly.

CNAME record

A DNS record type formerly used for SML lookups (pointing one domain name to another) that is being deprecated in this context.

NAPTR (U-NAPTR) record

A DNS record type that replaces CNAME in the new lookup method. It supports more advanced and flexible routing for metadata resolution.

Glossary Hero Image
More Stories
France e-invoicing mandate going live september 2026
France's E-Invoicing Mandate September 2026

The days of emailing a PDF invoice to French business partners are numbered. We break down the mandate, the five-corner model, and how to get compliant before the deadline.

What is the identity of the person submitting a tax report illustration
Identity: A forgotten theme in Digital Tax Reporting

As tax reporting moves into real time, identity can no longer be assumed. In a world of continuous transaction controls and outsourced compliance, tax authorities must instantly know who is submitting a report, on whose behalf, and under what authorization. Without verifiable identity, automation breaks and trust with it.

Difference between VAN networks and Peppol networks illustration
The difference between the Peppol network and traditional e-invoicing networks

The Peppol network is a decentralized, international e-invoicing infrastructure using a 4-corner model. This allows organizations to exchange e-invoices through certified service providers without needing bilateral agreements between senders, receivers, or providers. It ensures interoperability and avoids vendor lock-in. Traditional e-invoice (VAN) networks rely on bilateral agreements, creating a fragmented ecosystem.