France E-Invoicing Mandate 2026: What Corporate Travel Buyers Must Do Before September 1
TL;DR: France's e-invoicing mandate takes effect September 1, 2026. From that date, large and medium-sized enterprises must issue Factur-X e-invoices, and all French VAT-registered entities must be able to receive them. Small businesses follow on September 1, 2027. Corporate travel buyers have roughly eight weeks to audit their TMC model, select a Plateforme de Dématérialisation Partenaire (PDP), configure ERP ingestion, and update travel policy for VAT ID pass-through.
France's transition to mandatory business-to-business e-invoicing has been rescheduled twice, but the current September 1, 2026 deadline is now set in law by the 2024 Finance Act. Drawing from 8+ years building AI-powered corporate travel platforms serving multinational buyers, the patterns that hold up in cross-border regulatory transitions come down to two disciplines: knowing who invoices you (supplier direct, agent, or reseller), and hard-testing your ingestion stack before the enforcement date. This piece walks through the regulatory basis, the phased timeline, the corporate-travel-specific implications, and the five concrete steps a travel buyer should complete before the deadline. For readers new to the underlying framework, our primer on what e-invoicing means for corporate travel and EU mandates covers the pan-European context.
The Regulatory Basis: Article 91 and the PPF/PDP Architecture
Article 91 of the 2020 French Finance Law (Loi de Finances pour 2021) established the mandatory e-invoicing regime for domestic B2B transactions. The 2024 Finance Act amended the original timeline and confirmed the current phased schedule after the July 2024 postponement announced by the Direction Générale des Finances Publiques (DGFiP). Under the amended framework, French VAT-registered entities must transmit and receive electronic invoices exclusively through either the Portail Public de Facturation (PPF)—the state hub operated by the DGFiP—or through certified private platforms known as Plateformes de Dématérialisation Partenaires (PDPs). The DGFiP's official PDP registry, published on impots.gouv.fr, listed more than 90 certified PDPs as of the July 2026 publication cycle. Structured invoices must comply with the Factur-X hybrid format (a PDF/A-3 file with embedded XML metadata) or the pure UBL 2.1 and UN/CEFACT CII XML formats supported by the PPF.
Timeline and Scope: Who Must Do What, and When
The mandate rolls out in two phases based on company size, using thresholds aligned with French accounting law. Effective September 1, 2026, all "grandes entreprises" (large enterprises with more than 5,000 employees or turnover above €1.5 billion) and "entreprises de taille intermédiaire" (mid-market enterprises with 250–4,999 employees or turnover between €50 million and €1.5 billion) must ISSUE e-invoices in a structured format via a PDP or the PPF, per DGFiP guidance updated in early 2026. Small and medium enterprises (SMEs) and micro-enterprises must issue from September 1, 2027. Critically, the RECEIVE obligation is universal from September 1, 2026: every French VAT-registered entity, regardless of size, must be technically capable of receiving an e-invoice on that date. A small hotel in Bordeaux that is not yet obliged to issue Factur-X invoices must still be able to accept them from a large corporate supplier or intermediary.
Why This Matters for Corporate Travel Programs
Corporate travel is one of the most exposed spend categories to the French mandate because the invoice trail is fragmented across three commercial models: agent (TMC bills you a fee, hotel invoices you directly), pass-through/bill-back (TMC forwards supplier invoices), and reseller (TMC issues its own invoice for the underlying service). Each model creates a different Factur-X compliance path, and misidentifying the model is the single most common cause of downstream reclaim leakage.
French hotels invoicing your travelers directly must be Factur-X ready by 2027 at the latest—and many chains will move earlier to align with their own large-enterprise obligations. If you receive supplier invoices, your ERP or accounts-payable platform must ingest the embedded XML from the Factur-X PDF/A-3, not just the human-readable PDF layer. If your TMC operates a reseller model, the TMC itself becomes the issuing party and its own Factur-X readiness determines your compliance. Understanding which model applies to each supplier—hotel, airline, ground transport, MICE—is the first step. For the tax mechanics behind reclaim in each model, see our reference article on e-invoicing, VAT reclaim, and EU mandates and the deeper breakdown of TMC commercial models and VAT reclaim.
The 5-Step Readiness Plan
Drawing from active deployments across French subsidiaries of multinationals, the following sequence works when executed in order. Skipping steps—particularly the end-to-end test invoice—is the most common cause of go-live failure.
- Audit your TMC commercial model. Ask your TMC to confirm, in writing, whether they operate as agent, pass-through, or reseller for each supplier category (hotel, air, rail, ground). The answer determines who is your Factur-X counterparty and which VAT lines you can reclaim.
- Choose a PDP (or default to the PPF). The PPF is free but provides only baseline routing. PDPs offer richer validation, native ERP connectors, and better error-recovery workflows. Compare at least two certified PDPs against your ERP's existing e-invoicing capability before signing.
- Configure ERP ingestion. Your accounts-payable system must parse the XML layer of Factur-X, not the PDF layer. Confirm with your ERP vendor that the target release supports Factur-X Basic, EN 16931, and Extended profiles, and that VAT lines, line-item quantities, and supplier VAT IDs map cleanly into your general ledger.
- Update travel policy on VAT ID pass-through. Every booking made in France by a French VAT-registered entity's employee must carry your VAT ID at the point of purchase. Update booking-tool profiles, mandatory OBT fields, and traveler-facing prompts so the VAT ID is captured before payment—not reconciled after. See our corporate travel policy compliance guide for language you can lift into your own policy.
- Run at least one test invoice end-to-end. Have a French supplier or your PDP issue a Factur-X test invoice, route it through the PPF or PDP, and confirm it lands in your ERP with all VAT and line-item data intact. Time this before mid-August 2026, allowing four weeks for defect resolution.
Common Failure Modes
Three failure modes account for the majority of go-live incidents observed across EU e-invoicing rollouts (Italy 2019, Poland 2024, France 2026). First, treating a Factur-X invoice as a PDF: finance teams archive the PDF but ignore the embedded XML, losing structured VAT data at ingestion and forcing manual re-keying at month-end close. Second, PPF/PDP mismatch: the buyer chooses the PPF while key suppliers route through PDPs, causing silent routing failures that surface weeks later as "missing invoice" tickets and unpaid supplier balances. Third, missing VAT ID at booking time: without the buyer's VAT ID captured at point-of-sale, the French hotel or supplier cannot generate a compliant B2B Factur-X invoice, and the transaction defaults to a B2C receipt, which is not reclaimable under French VAT law. All three failure modes are preventable with the audit and end-to-end test steps described above.
PPF vs Certified PDP: A Buyer's Comparison
| Criterion | Portail Public de Facturation (PPF) | Plateforme de Dématérialisation Partenaire (PDP) |
|---|---|---|
| Cost | Free (state-operated) | Typically €0.10–€0.50 per invoice, or annual subscription |
| Routing | Direct PPF-to-recipient only | PDP-to-PDP and PDP-to-PPF interoperability |
| Format validation | Baseline Factur-X + UBL/CII | Extended validation, error recovery, format conversion |
| ERP connectors | Generic APIs, limited pre-built connectors | Native connectors for SAP, Oracle, Sage, Cegid, Microsoft Dynamics |
| DGFiP e-reporting | Automatic | Automatic (certified PDPs transmit on your behalf) |
| Support model | DGFiP helpdesk, ticket-based | Dedicated implementation and go-live support |
| Best fit | Low volume, single ERP, direct-to-DGFiP | Mid-to-high volume, complex supplier mix, multi-entity groups |
Where Travel Code Fits
Travel Code operates as a BYOD (Bring Your Own Data) overlay on top of your existing TMC and OBT stack—we do not invoice travelers or clients for the underlying travel, so the French mandate does not change our commercial footprint or add compliance burden on your finance team. What we do add is continuous rate re-shopping through RateGuard (priced at 25% of validated savings, with no fee if no savings are booked), real-time duty-of-care visibility, and unified analytics that sit alongside whichever TMC and PDP configuration your team lands on. In practical terms: your finance team can focus fully on Factur-X readiness while the overlay keeps generating booked-rate savings on the same reservations your TMC already handles.
Frequently Asked Questions
What is the exact date for France's e-invoicing mandate?
September 1, 2026, for large and medium-sized enterprises (issuance obligation) and for all French VAT-registered entities (receipt obligation). Small and micro-enterprises must issue from September 1, 2027, per the 2024 Finance Act.
Is Factur-X the only accepted format?
Factur-X is the recommended and most-adopted format for B2B invoices in France. The PPF also accepts pure XML formats (UBL 2.1 and UN/CEFACT CII). A traditional PDF without an embedded XML layer is not compliant for B2B transactions in scope of the mandate.
Do I need to use a PDP, or is the PPF enough?
Legally, either satisfies the mandate. Operationally, most mid-to-large corporate buyers select a certified PDP because the PPF's baseline validation and limited ERP connectivity make it a poor fit for high-volume, multi-supplier environments like corporate travel.
How does this affect my TMC contract?
It depends on your commercial model. In agent and pass-through models, the supplier invoices you and the TMC does not become the Factur-X counterparty. In reseller models, the TMC issues its own invoice, and their Factur-X readiness—not the underlying supplier's—determines your compliance path. Ask your TMC to confirm the model in writing, per supplier category.
Is Travel Code a TMC?
No. Travel Code is a BYOD overlay that runs alongside your existing TMC and OBT. We do not manage bookings or issue invoices for the underlying travel, so the French mandate does not require any change to Travel Code's operating model or your contract with us.
What happens if we miss the September 1 deadline?
Article 91 of the 2020 Finance Law provides for administrative penalties of €15 per non-compliant invoice, capped at €15,000 per year per entity, plus additional penalties for repeated PPF/PDP transmission failures. The DGFiP has signaled a soft-enforcement grace period for the first quarter post-launch, but no formal amnesty has been published as of July 2026.
Sources
- Direction Générale des Finances Publiques (DGFiP), Facturation électronique, impots.gouv.fr, updated July 2026.
- Loi de Finances pour 2021 (2020 French Finance Law), Article 91, official Journal Officiel de la République Française.
- Loi de Finances pour 2024 (2024 Finance Act), amendments to Article 91.
- DGFiP, Liste des Plateformes de Dématérialisation Partenaires immatriculées, July 2026 publication cycle.
- Portail Public de Facturation (PPF) technical documentation, portail.chorus-pro.gouv.fr.
