Factur-X & French E-Invoicing Reform 2026: Chorus Pro Mandatory B2B Rollout Guide

The 2026 French E-Invoicing Architecture at a Glance

Few European reforms touch as many companies, in as short a window, as the French facturation électronique obligatoire. The cards below summarise the six pillars of the new architecture — keep them in mind as you read each deep-dive section.

1. Factur-X — The Hybrid PDF/A-3 + XML CII Format

A Pragmatic Compromise Between Humans and Machines

Factur-X is the answer to a question that has dogged European e-invoicing since its earliest pilots in the 1990s: how do you give the tax authority a perfectly structured machine-readable invoice without taking away the printable, human-readable PDF that accountants, auditors and customers have used for thirty years? The answer turned out to be elegant: embed the XML inside the PDF. Factur-X is a PDF/A-3 document — the ISO-19005-3 archival profile of PDF — with an embedded XML payload conforming to UN/CEFACT Cross-Industry Invoice (CII) syntax. Open the file in Acrobat or a browser: you see a human-readable invoice. Drop it into an ERP with a Factur-X parser: it extracts the XML in milliseconds and posts a fully structured accounting entry.

The format was co-designed by the FNFE-MPE (Forum National de la Facture Électronique et des Marchés Publics Électroniques) on the French side and the FeRD (Forum elektronische Rechnung Deutschland) on the German side. The two organisations explicitly agreed to publish identical technical specifications under two brand names — Factur-X 1.0 in France and ZUGFeRD 2.x in Germany — making this the most successful binational e-invoicing standard in Europe.

The Five Conformance Profiles

Factur-X / AFNOR XP Z12-013 defines five conformance profiles, layered from the most minimal subset of data fields to the richest extension. Choosing the right profile is the single most important architectural decision you will make in your migration.

Anatomy of a Factur-X File

Open any Factur-X invoice with a binary viewer and you will see three logical components:

• The PDF/A-3 visual layer — the printable invoice. Your customer can save it, print it, attach it to a payment instruction. The visual representation is what humans see.
• The embedded XML file, named factur-x.xml, attached at the document level via the PDF/A-3 /AFRelationship mechanism with the relationship type set to Alternative. This is the machine-readable payload.
• The XMP metadata, signalling Factur-X presence, profile name (e.g. urn:cen.eu:en16931:2017), conformance level and version. ERP systems probe the XMP first to decide whether to parse the XML.

The mechanism is deliberately backward-compatible: any PDF viewer can still display the invoice, regardless of whether it understands Factur-X. The XML is invisible to legacy tools but immediately consumable by modern ERPs.

2. Chorus Pro — The French Government Invoicing Portal

From Ordonnance 2014 to Universal B2G

Chorus Pro is the French public administration's e-invoicing portal, operated by the AIFE (Agence pour l'informatique financière de l'État). It went live in January 2017 as the implementation of Ordonnance n° 2014-697 of 26 June 2014, which mandated electronic invoicing for all suppliers of the French State, local authorities (collectivités territoriales) and public hospitals. The rollout was phased by company size — large enterprises first in 2017, ETI in 2018, PME in 2019 and TPE in January 2020 — and by 2026 Chorus Pro processes more than 140 million invoices per year from roughly 250,000 active suppliers.

For French companies selling to the public sector — which collectively account for around 9% of national GDP — Chorus Pro is the only legal channel. Paper invoices to the State have been refused since the rollout completed in 2020, and any contractor still attempting to ship a paper invoice to a ministry, town hall or hospital will simply be paid late or not at all.

How Chorus Pro Fits the New 2026 Architecture

A frequent misconception in 2026 is that Chorus Pro "disappears" with the reform. It does not. The reform reorganises the broader e-invoicing flow, but Chorus Pro remains:

• The B2G channel — every invoice to a French public entity continues to transit through Chorus Pro, with the AIFE operating the dossier.
• Integrated with the PPF — the PPF acts as an entry point for B2G invoices too, routing them transparently into Chorus Pro on behalf of the issuer.
• Reachable via every accredited PDP — sellers connected to a PDP automatically reach Chorus Pro through the unified network, without needing a separate Chorus Pro account.

Chorus Pro Formats Accepted in 2026

Chorus Pro accepts a broad spectrum of formats, all of which must conform to either Factur-X profiles or pure XML structured invoicing standards:

• Factur-X — MINIMUM, BASIC WL, BASIC, EN 16931, EXTENDED (recommended)
• UBL 2.1 — Universal Business Language as defined by OASIS, aligned with EN 16931 via the CIUS conformance
• UN/CEFACT CII — the pure XML variant of the same data model embedded in Factur-X
• PDF + structured envelope — legacy, deprecated in 2026, no longer accepted for new contracts

If you can issue Factur-X, you can invoice every French public entity. Zunapro defaults to Factur-X EN 16931 for Chorus Pro submissions, with automatic downgrade to BASIC for entities that explicitly request it.

3. The 2026–2027 Mandatory Rollout Timeline

A Reform Twice Postponed

The French e-invoicing reform was first formalised by Article 153 of the Loi de finances pour 2020 and detailed by Ordonnance n° 2021-1190 of 15 September 2021. The original timetable scheduled a 2024 launch, but operational challenges with the PPF — particularly the technical complexity of merging the existing Chorus Pro architecture with a new B2B-grade backbone — forced a first postponement in summer 2023. A revised timetable, stabilised by the Loi de finances 2024, sets the current dates the French e-invoicing community has been preparing for.

The Two-Wave Calendar

Every French VAT-registered company falls into one of two waves, based on the size criteria defined by Article 51 of the Loi n° 2008-776 of 4 August 2008 (de modernisation de l'économie):

Date	Obligation	Companies in Scope	Sizing Thresholds
1 September 2026	Mandatory issuance (B2B) + reception (all companies)	Grandes entreprises & ETI	>250 employees OR turnover >€50M OR balance sheet >€43M
1 September 2026	Mandatory reception (B2B)	All French VAT-registered companies	No size threshold — universal
1 January 2027	Mandatory issuance (B2B)	PME & TPE (incl. auto-entrepreneurs)	<250 employees AND turnover ≤€50M AND balance sheet ≤€43M
1 January 2027	E-reporting (B2C, foreign, payment-status)	All companies in scope	Aligned with B2B issuance dates

Reading the table: The asymmetry between issuance and reception is critical. From 1 September 2026, every French company — including the smallest auto-entrepreneur — must be able to receive a structured Factur-X invoice. Only large enterprises and ETI must issue structured invoices from that date. SMEs and micro-businesses have four extra months — until 1 January 2027 — before they must also start issuing.

Why That Matters in Practice

Two operational consequences of the calendar trip up many companies in 2026:

• If you are an SME selling to a large enterprise from October 2026, your customer will send you Factur-X invoices for their purchases of your service. You need a receiving and parsing pipeline before you start issuing your own Factur-X invoices in January 2027.
• If you are a large enterprise buying from SMEs from September 2026, your suppliers will not yet issue Factur-X to you. The reform allows them to continue issuing PDF or paper invoices until 1 January 2027, and your accounts-payable pipeline must accept both legacy and Factur-X inputs in parallel.

This dual-track period — September 2026 to January 2027 — is the single most operationally complex window of the entire rollout. Zunapro's compliance dashboard tracks every supplier's transition status so accounts payable teams know exactly which format to expect from which counterparty.

4. AFNOR XP Z12-013 — The French Reference Standard

What AFNOR Publishes and Why

AFNOR (Association Française de Normalisation) is the French national standards body, member of CEN at European level and ISO at global level. AFNOR publishes the experimental standard XP Z12-013 as the French formal reference for the Factur-X hybrid format. "XP" stands for "norme expérimentale" — an AFNOR designation used for standards in their first generation, expected to mature into a final NF Z12-013 after 3–5 years of industry feedback.

The role of AFNOR XP Z12-013 in the French reform is threefold:

• Legal anchor — French tax law references the AFNOR standard directly, giving Factur-X regulatory weight at the same level as ISO PDF/A-3.
• Profile catalogue — the document enumerates the five conformance profiles (MINIMUM, BASIC WL, BASIC, EN 16931, EXTENDED) with their exact field-by-field requirements.
• Interoperability bridge — AFNOR XP Z12-013 maps every Factur-X profile to the European EN 16931 semantic model and to UN/CEFACT CII XSD schemas, guaranteeing cross-border compatibility.

The Five Profiles in Detail

Profile	Data Coverage	Typical Use Case
MINIMUM	Header only: SIRET, TVA, total, currency	Very small B2C-style invoices, simple memos
BASIC WL	Header + VAT breakdown, no line items	Service invoices with flat fees
BASIC	Header + line items + VAT + payment terms	Standard French SME invoicing
EN 16931 (formerly COMFORT)	Full EN 16931 semantic model	De-facto B2B default and cross-border interop
EXTENDED	EN 16931 + logistics, contracts, item attributes	Retail, automotive, transport, complex supply chains

How AFNOR XP Z12-013 Relates to ISO PDF/A-3

The PDF container side of Factur-X is governed by the international standard ISO 19005-3 (PDF/A-3), not by AFNOR. ISO PDF/A-3 enables embedding arbitrary file types (here, the factur-x.xml payload) as document-level attachments, with archival guarantees: no external resources, fully self-contained, deterministic rendering over a 100-year horizon. AFNOR XP Z12-013 sits on top of ISO PDF/A-3, specifying which XML profile is embedded and with which XMP metadata. The two standards are designed to be read together.

5. PDP — Plateformes de Dématérialisation Partenaires

The Competitive Private Layer

A PDP (Plateforme de Dématérialisation Partenaire) is a private accredited intermediary in the French e-invoicing architecture, sitting between the issuer's accounting software and the broader network. Where the PPF offers a free, baseline State portal, PDPs compete on advanced features: ERP integration, automated reconciliation, deep analytics, archival, multi-format conversion, supplier portals, accounts-receivable financing and so on.

The PDP regime is defined by Article 290 of the Code général des impôts (as inserted by the Loi de finances 2024) and detailed by the DGFiP Direction des Grandes Entreprises. By mid-2026, more than 80 PDP candidates had filed accreditation dossiers with the DGFiP, with the first wave of fully accredited PDPs publishing their service catalogues in autumn 2026.

PDP Accreditation in Three Steps

• Step 1 — Dossier filing: candidate publishes a technical specification, security audit report (typically based on ISO 27001), an archiving roadmap and a service-level agreement template.
• Step 2 — DGFiP review: a 6-to-12-month conformity assessment, including interoperability testing against the PPF reference platform and against other candidate PDPs.
• Step 3 — Three-year accreditation: granted for three years, renewable, with annual conformity reports and mandatory penetration testing.

Why Choose a PDP Over the Free PPF?

The PPF is free and usable. Many SMEs and auto-entrepreneurs will reasonably issue and receive Factur-X via the PPF web interface without paying for a PDP. The case for a PDP is operational depth:

• ERP / accounting integration — Sage, Cegid, EBP, Pennylane, QuickBooks France, Dougs, Indy push invoices into a PDP via REST API or EDI; the PPF expects portal uploads or narrow APIs.
• Multi-format conversion — PDPs accept legacy PDF, UBL or proprietary XML and emit Factur-X transparently to the customer's preferred profile.
• Archiving — the regulatory requirement is 10 years WORM; PDPs typically bundle this in.
• Analytics & cash flow — payment-status, DSO dashboards, automated dunning, factoring.
• Multi-country VAT — one PDP relationship covering Factur-X (FR), ZUGFeRD (DE), Peppol (BE/NL/LU) and Italian SDI.

The Practical Choice in 2026

The pragmatic mid-market choice in 2026 is a PDP for outbound and inbound structured invoices, with the PPF kept as a backup. Zunapro plugs into a PDP relationship behind the scenes — your accounting software, sales channels and B2G workflows reach every French counterparty without per-invoice routing decisions.

6. PPF — Portail Public de Facturation Integration

What the PPF Actually Does

The PPF (Portail Public de Facturation) is the State-operated free baseline e-invoicing portal, operated by the DGFiP through the AIFE. It is the successor of the original "Chorus Pro Factures" extension that was scoped in 2020 before the reform's architecture was revised to allow private PDPs to compete. By 2026 the PPF offers three core functions:

• Issuance — French companies can upload Factur-X PDFs, UBL or CII XML files via the web interface or a basic API, and the PPF routes them to the recipient through the unified network.
• Reception — companies receive their incoming structured invoices in the PPF's inbox, downloadable as PDF or XML, with optional email notifications.
• Annuaire (directory) — the PPF hosts the central national directory of SIREN / SIRET identifiers, mapped to each company's preferred receiving platform (PPF or a specific PDP). Every PDP synchronises against the PPF annuaire in near real time.

The PPF Annuaire — The Hidden Plumbing of the Reform

If there is one component of the reform that deserves deeper attention than its marketing visibility suggests, it is the PPF annuaire. Every French B2B counterparty must publish in the annuaire how they wish to be reached: directly via the PPF, or via a named PDP, with technical routing identifiers (SIRET, TVA, GLN / EAN where relevant). When you issue an invoice, your sending platform queries the annuaire to determine where the invoice should land. The annuaire is therefore the unique source of truth for routing; misconfigurations here are the #1 cause of failed deliveries in the dry-run period.

PPF API and File Formats

The PPF accepts the same family of formats as Chorus Pro: Factur-X (all profiles), UBL 2.1, UN/CEFACT CII. Maximum file size for a single Factur-X file is 25 MB; for very large EXTENDED invoices with hundreds of line items, the recommended approach is to split into multiple structured documents. The PPF API is REST-based, secured by OAuth 2.0, with rate limits in the order of 10,000 invoices per hour per company — far higher than any individual issuer's realistic throughput.

7. B2C vs B2B — What Changes and What Doesn't

B2B Domestic — Full E-Invoicing

The headline obligation of the reform applies to B2B domestic transactions: a French VAT-registered seller invoicing another French VAT-registered buyer. Every such invoice must be issued in a structured electronic format (Factur-X, UBL or CII), routed through the PPF or a PDP, and stored for 10 years in compliance with Article L102 B of the Livre des procédures fiscales. Paper invoices for domestic B2B become legally invalid after the rollout dates.

B2C — E-Reporting Only

For B2C sales (sales to French consumers), the seller has no obligation to issue a structured Factur-X invoice — French consumers do not need an XML-readable invoice. Instead, the seller transmits an aggregated daily or periodic e-reporting flow to the DGFiP via their PDP or the PPF, summarising B2C revenue by VAT rate, transaction count and payment type. The reporting cadence is typically every 10 days for sellers under the standard VAT regime, and monthly for sellers under simplified regimes.

Cross-Border — E-Reporting Too

Cross-border transactions — sales to non-French customers (intra-EU and extra-EU) and purchases from foreign suppliers — fall under e-reporting rather than e-invoicing. The reasoning is pragmatic: the French reform cannot impose Factur-X on a German or Spanish counterparty, so the DGFiP collects the data via the seller's own reporting flow, leaving the actual invoice format to bilateral agreement (typically Peppol, EDIFACT or commercial XML).

Transaction Type	Obligation	Format	Cadence
Domestic B2B	E-invoicing	Factur-X, UBL, CII	Per transaction
Domestic B2G	E-invoicing	Factur-X, UBL, CII (via Chorus Pro)	Per transaction
Domestic B2C	E-reporting	Aggregated XML	Every 10 days (standard regime)
Cross-border intra-EU sales	E-reporting	Aggregated XML	Every 10 days (standard regime)
Cross-border extra-EU sales	E-reporting	Aggregated XML	Every 10 days (standard regime)
Foreign purchases	E-reporting (acquéreur)	Aggregated XML	Every 10 days (standard regime)

Payment-Status Reporting — The Fourth Flow

Often forgotten in the marketing material, the reform introduces a fourth obligatory flow: payment-status reporting. Each company must report the actual payment date of incoming invoices, in addition to the invoice itself. The flow is light — three or four data points per invoice — but powers the DGFiP's macroeconomic dashboard on French B2B payment delays, a longstanding political concern.

8. Cross-Border EU EN 16931 Compatibility

The European Norm Behind Every National Reform

EN 16931 is the European semantic standard for e-invoicing, published by CEN/TC 434 (the CEN technical committee on electronic invoicing) under mandate from the European Commission. It is the cornerstone of Directive 2014/55/EU on electronic invoicing in public procurement, which obliged every EU member state to accept EN 16931 invoices from suppliers across the Union since 2019.

EN 16931 does not prescribe a specific XML syntax. It defines a core semantic model — the data points an invoice must carry to be unambiguously interpreted — and then provides two reference syntactic bindings:

• UN/CEFACT CII — the XML used inside Factur-X and ZUGFeRD
• UBL 2.1 — the OASIS Universal Business Language, used by Peppol and most northern-European national networks

Both bindings carry identical semantic content. A Factur-X invoice and a UBL invoice with the same EN 16931 profile are functionally equivalent — they can be converted between each other losslessly.

Why That Matters for French Sellers

If you are a French seller invoicing a Belgian or Dutch B2B buyer, your buyer's accounts-payable team almost certainly expects UBL 2.1 over the Peppol network. With EN 16931 compatibility, you can:

• Issue Factur-X (CII) in France for your domestic B2B and B2G flow
• Have your PDP automatically convert outbound cross-border invoices to UBL 2.1 over Peppol
• Receive Belgian, Dutch, Luxembourg and Norwegian inbound invoices in UBL 2.1 and have your PDP normalise them to Factur-X for your French ERP

The conversion is mechanical — both formats are EN 16931 bindings — and accredited PDPs typically expose Peppol Access Point capabilities out of the box.

The German Factur-X / ZUGFeRD Symmetry

The Franco-German alignment is the strongest cross-border story in EU e-invoicing. Factur-X 1.0 and ZUGFeRD 2.x are technically identical — same PDF/A-3 container, same UN/CEFACT CII XML, same XMP metadata. A French issuer sending a Factur-X invoice to a German buyer is parsed natively by ZUGFeRD-aware German ERPs (SAP, DATEV, Diamant, Sage 100 etc.). The Franco-German market is, for practical purposes, a single e-invoicing zone.

Italy, Spain and the Wider EU

• Italy (SDI) — FatturaPA XML, mandatory since 2019; EN 16931 via the SDI translation gateway.
• Spain (Verifactu / SII) — EN 16931-aligned; UBL 2.1 is the recommended cross-border format.
• Belgium & Netherlands — Peppol-first, UBL 2.1 over Peppol BIS Billing 3.0 (a CIUS of EN 16931).
• Germany — ZUGFeRD 2.x = Factur-X 1.0; pure XRechnung XML for B2G.
• Poland (KSeF) — mandatory since February 2026; FA(2) XML, EN 16931-aligned via a national CIUS.

9. Penalties for Non-Compliance

Article 1737 CGI — The Fixed Fine

The headline penalty for issuing a non-compliant invoice is defined by Article 1737 of the Code général des impôts, as updated by the Loi de finances 2024: €15 per non-compliant invoice, capped at €15,000 per calendar year per company. The fixed amount looks modest, but the cap is reached after 1,000 violations — far less than the annual volume of even a small B2B SME.

The Bigger Risk — VAT Recovery Challenge

For most companies the heavier exposure is not the €15 fine but the VAT recovery challenge. Article 271 of the CGI conditions the recovery of input VAT on the receipt of a conforming invoice. If your supplier issued a non-compliant paper invoice after 1 September 2026 (when reception of structured invoices is mandatory for all buyers), the DGFiP can during a tax audit deny your VAT recovery on that invoice. On a typical mid-market portfolio of inbound invoices, the cumulative exposure can run into hundreds of thousands of euros — well beyond the headline fine.

Article 1737 — Other Triggers

Article 1737 also defines a wider set of triggers that the DGFiP can activate during audit:

• Refusal to issue an electronic invoice — €15 / invoice, capped at €15,000 / year
• Refusal to receive an electronic invoice — €15 / invoice, same cap
• Refusal or delay in transmitting e-reporting data — €250 per non-transmitted period, capped at €15,000 / year
• Late transmission of payment-status data — €250 per non-transmitted period
• Deliberate non-compliance after formal notification — escalation to Article 1729 CGI, with penalty rates of 40–80% of recovered tax

The Tolerance Window

The DGFiP has announced a tolerance window of approximately 12 months after each wave, during which good-faith errors will be flagged but not fined. It does not apply to companies that have made no attempt to migrate — accountants should not treat it as a pass to delay PDP onboarding.

10. Migration Strategy from PDF/Paper

Phase 1 — Audit (Months -12 to -9)

Start with an honest inventory. Map every outbound invoice stream (sales orders, recurring subscriptions, manual services, B2G, intra-group) and every inbound stream (suppliers, expenses, utilities). Tag each with its current format (paper, PDF, UBL, EDIFACT) and its 2026 target. The audit typically surfaces 5–15 forgotten streams — particularly automated subscription billing inside SaaS platforms.

Phase 2 — Accounting Software & PDP Selection (Months -9 to -6)

With the audit in hand, choose:

• Accounting suite — Sage, Cegid, EBP, Pennylane, QuickBooks France, Dougs, Indy, Tiime all have Factur-X-ready 2026 versions.
• PDP relationship — based on connector matrix, EU coverage, archival SLA and pricing.
• E-commerce integration — Zunapro handles this, routing orders from Amazon FR, Cdiscount, Fnac, Veepee, Manomano to your accounting suite as compliant Factur-X.

Phase 3 — Pilot & Dry Run (Months -6 to -3)

Run a parallel pipeline for ~3 months: issue both your legacy PDF and a Factur-X version for every B2B invoice. Send the Factur-X to the PPF test environment, verify acknowledgement, validate the XML against the AFNOR XP Z12-013 profile, archive both versions. Pick ~20% of suppliers and ask them to send you their inbound Factur-X via the dry-run environment to test your reception pipeline. This is the phase where you catch SIRET mismatches, VAT rate misclassifications and rounding errors — fix them under no pressure.

Phase 4 — Cutover (D-day)

1. D-30: freeze legacy invoice numbering. Communicate cutover date to all suppliers and customers.
2. D-7: dry-run final batch. Verify PPF annuaire entry for your SIRET is correct and points to your chosen PDP.
3. D-day: switch primary issuance to Factur-X via PDP. Keep legacy PDF generation enabled internally as a safety net for the first 60 days.
4. D+30: review rejection log. Typical first-month rejection rate is 2–5%, mostly SIRET routing errors.
5. D+90: disable legacy PDF generation. Your finance team now lives in a Factur-X-only world.

Phase 5 — Continuous Improvement

The post-cutover months reveal the qualitative benefits of structured e-invoicing: faster reconciliation, accounts-payable automation rates above 90%, real-time DSO visibility, embedded factoring via PDP partners. Operational gains typically dwarf the migration cost within six months.

French E-Invoicing FAQ 2026