France E-Invoicing 2026: Compliance Guide

On September 1, 2026, an estimated 290,000 large and mid-size French companies will be required to issue structured electronic invoices for every B2B transaction -- and every VAT-registered business in France must be able to receive them. By September 2027, the remaining 3.7 million SMEs and micro-enterprises join the issuing mandate. That is roughly 2.5 billion invoices per year shifting from PDF attachments and paper to machine-readable formats validated in real time by government-connected platforms. For any organization that sells to or buys from French companies, the reform is not optional -- and it is only one of several major 2026 compliance deadlines, alongside the MiCA regulation for crypto-asset service providers. Companies that fail to comply face penalties of up to EUR 15 per non-compliant invoice, capped at EUR 15,000 per year.

This guide covers the timeline, the three mandatory formats, the platform architecture, the field-level validation requirements, the penalties, and -- critically -- how automated document validation fits into the compliance chain.

Timeline: Who Must Comply and When

The French e-invoicing reform (réforme de la facturation électronique) was originally scheduled for July 2024 but was postponed to allow more preparation time. The revised timeline, confirmed by the Direction Générale des Finances Publiques (DGFiP), is now set in two phases.

What "Issue" and "Receive" Mean in Practice

Issuing means generating invoices in one of the three authorized structured formats (Factur-X, UBL, or CII), transmitting them through a registered platform (PDP or PPF), and ensuring every mandatory field is present and correctly formatted before submission. A simple PDF sent by email no longer qualifies.

Receiving means having the technical capability to accept structured invoices from any platform in any of the three formats, parse the data, and integrate it into your accounting workflow. Even companies not yet required to issue must be ready to receive from September 2026.

This asymmetry -- all companies must receive before all companies must issue -- creates an immediate compliance burden across the entire B2B ecosystem.

The Three Mandatory Invoice Formats

France's reform accepts three structured formats. Each embeds machine-readable data that platforms validate automatically before delivery.

All three formats must conform to the European standard EN 16931, which defines the semantic data model for the core elements of an electronic invoice. France adds a national extension -- the CIUS-FR (Core Invoice Usage Specification for France) -- that mandates additional fields specific to French tax law.

Factur-X: The Dominant Choice

For most French businesses, Factur-X will be the path of least resistance. The PDF component looks and prints like a traditional invoice, while the embedded XML satisfies the structured data mandate. The Forum National de la Facturation Electronique (FNFE) maintains the specification.

Factur-X defines multiple profiles (Minimum, Basic WL, Basic, EN 16931, Extended). For the French mandate, invoices must meet at least the EN 16931 profile, which includes over 100 data elements. Generating a visually correct PDF is trivial, but embedding a fully compliant XML payload is where most errors occur. A missing SIRET number, an incorrect VAT rate code, or a malformed date field will cause the invoice to be rejected -- and the sender may not discover the rejection until the payment cycle is already disrupted.

PDP vs. PPF: The Platform Architecture

Invoices do not flow directly from seller to buyer. They pass through intermediary platforms that validate, route, and report transaction data to the French tax administration.

PPF -- Portail Public de Facturation

The PPF is the free, government-operated platform built on Chorus Pro (used for public procurement invoices since 2020). It serves as the central directory and default routing platform but offers limited functionality beyond basic validation and transmission.

PDP -- Plateforme de Dématérialisation Partenaire

PDPs are private-sector platforms registered and audited by the tax administration. They perform the same core functions as the PPF but add ERP integration, format conversion, archiving, analytics, and workflow automation. As of early 2026, over 70 PDP candidates have applied for registration, with approvals expected before September.

For organizations already using automated document workflows, selecting a PDP that integrates with your existing validation pipeline is critical. Our API and ERP integration guide covers the technical architecture for connecting validation tools to e-invoicing platforms.

Mandatory Fields: What Gets Validated

Every invoice submitted through a PDP or the PPF is validated against a set of mandatory fields before being accepted for delivery. A single missing or malformed field triggers rejection.

Core Mandatory Fields (EN 16931 + CIUS-FR)

The Arithmetic Trap

Platforms validate arithmetic automatically: the sum of line-item net amounts must equal the total net amount; each line's VAT amount must equal the net amount multiplied by the stated VAT rate (within rounding tolerance); and total VAT plus total net must equal the gross total. These checks catch approximately 12-15% of invoices generated by ERP systems that have not been configured for EN 16931 compliance, based on early pilot data from PDP candidates.

For accounting firms managing invoicing on behalf of clients, these validation requirements add a significant quality assurance layer. See how accounting firms are automating document verification to handle this at scale.

Penalties for Non-Compliance

The Finance Act establishes clear penalties for businesses that fail to comply with the e-invoicing mandate.

For a mid-size company issuing 5,000 invoices per year, non-compliance on even 20% of invoices hits the EUR 15,000 annual cap. Beyond the direct financial penalty, non-compliant invoices may be rejected by the buyer's platform, delaying payment and damaging commercial relationships.

Why Automated Validation Matters Before Submission

Here is where most compliance strategies fall short. Companies focus on choosing a PDP and configuring their ERP for format generation, but they neglect the validation step that happens -- or should happen -- before the invoice reaches the platform.

When a PDP rejects an invoice, the cycle is expensive:

1. Invoice generated by ERP and submitted to PDP.
2. PDP validates and rejects (missing field, arithmetic error, invalid code).
3. Rejection notification sent back to the seller's system.
4. Accounting team investigates the error.
5. ERP configuration or invoice data is corrected.
6. Invoice resubmitted.
7. Payment cycle delayed by days or weeks.

For organizations processing thousands of invoices monthly, even a 5% rejection rate generates hundreds of manual investigations per month. This is the hidden cost of manual document validation applied to e-invoicing compliance: the labor, delay, and rework that accumulate when validation happens after submission instead of before.

Pre-Submission Validation: The Compliance Buffer

Automated document validation catches errors before they reach the PDP. Instead of discovering that 200 out of 4,000 invoices have malformed SIRET numbers after submission, a validation layer flags them during generation -- before they enter the transmission pipeline.

The validation checks mirror what the PDP performs:

• Schema validation: does the XML conform to the Factur-X, UBL, or CII schema?
• Mandatory field completeness: are all CIUS-FR required fields present and non-empty?
• Format compliance: are dates in ISO 8601, currency codes in ISO 4217, country codes in ISO 3166?
• Arithmetic consistency: do line items sum correctly? Do VAT calculations match stated rates?
• Cross-reference validation: does the seller's SIRET match official records? Is the VAT number valid in VIES?
• Business rule validation: is the correct tax category code used for intra-EU supplies? Is an exemption reason provided for zero-rated lines?

This is precisely the kind of structured, rules-based validation that goes beyond OCR and IDP to catch compliance failures at the field and cross-document level.

How Document Validation Fits Into the E-Invoicing Workflow

The optimal architecture places automated validation as a middleware layer between your ERP (invoice generation) and your PDP (invoice transmission):

1. ERP generates the invoice in the chosen format (Factur-X, UBL, or CII).
2. Validation engine checks the invoice against the full EN 16931 + CIUS-FR specification -- schema, mandatory fields, arithmetic, and cross-references.
3. Compliant invoices are transmitted to the PDP automatically. Non-compliant invoices are flagged with specific error codes and routed to the accounting team.
4. The PDP validates and routes the invoice to the buyer's platform, with a near-zero rejection rate because errors were already caught upstream.

This architecture reduces PDP rejection rates from the 10-15% observed in early pilots to below 1% and creates a complete audit trail of every validation check -- essential for tax audits.

Preparing Now: A Practical Timeline

With September 2026 as the hard deadline for Phase 1, organizations should already be in active preparation. Here is a realistic implementation timeline.

For SMEs and micro-enterprises with a September 2027 deadline, starting early is advisable. PDP capacity will be constrained as 3.7 million businesses onboard simultaneously.

FAQ

What invoice formats does France accept for the 2026 e-invoicing mandate?

France mandates three structured formats: Factur-X (hybrid PDF with embedded XML), UBL 2.1 (pure XML), and CII (Cross Industry Invoice, pure XML). All three must conform to the European standard EN 16931, with additional French-specific fields defined in the CIUS-FR extension. Simple PDFs, scanned images, and Word documents will no longer qualify for B2B transactions subject to the mandate.

What is the difference between a PDP and the PPF?

The PPF (Portail Public de Facturation) is the free government platform with basic validation and routing. A PDP (Plateforme de Dématérialisation Partenaire) is a private-sector platform registered with the tax administration that adds ERP integration via API, format conversion, compliant archiving, analytics, and higher volume capacity. Most mid-size and large companies are expected to use a PDP.

Can my company be penalized if invoices are rejected by a platform?

Rejection itself does not trigger a penalty -- the penalty applies when a company fails to issue a compliant e-invoice for a transaction that requires one. However, if a rejected invoice is not corrected and resubmitted, the transaction lacks a compliant invoice, which can trigger the EUR 15 per invoice penalty (capped at EUR 15,000 per year). Persistent rejection also delays payments and disrupts buyer relationships.

How does automated document validation help with e-invoicing compliance?

Automated validation acts as a pre-submission quality gate. Before an invoice reaches the PDP, the validation engine checks schema conformance, mandatory fields, arithmetic consistency, VAT number validity, and business rules. This catches errors at the source rather than after submission, where rejections create manual rework. Organizations using pre-submission validation in early pilots have reduced rejection rates from 10-15% to below 1%.

Automate Your E-Invoicing Compliance with CheckFile

The September 2026 deadline is seven months away. The format specifications are final, the PDP ecosystem is taking shape, and the penalties are defined. What remains is execution: configuring your systems to generate compliant invoices, validating them before submission, and ensuring that your rejection rate stays near zero from day one.

CheckFile provides automated document validation that integrates into your e-invoicing workflow as a pre-submission compliance layer. Our platform validates Factur-X, UBL, and CII invoices against the full EN 16931 + CIUS-FR specification -- schema compliance, mandatory fields, arithmetic, VAT number cross-referencing, and business rules -- before your invoices reach the PDP. Errors are flagged with specific correction guidance, not generic rejection codes.

Whether you are a large enterprise preparing for Phase 1 or an SME planning ahead for Phase 2, automated validation eliminates the most expensive part of the compliance transition: the manual investigation and correction cycle for rejected invoices.

Explore our pricing to find the plan that matches your invoice volume, or request a demo with your own invoice files. Compliance is mandatory -- the rejection rate does not have to be.