France's business-to-business e-invoicing reform reaches large and mid-sized companies in September 2026, small and medium enterprises a year after that, and micro-businesses in September 2028. The staggering is deliberate: rather than a single cutover date, the Direction Générale des Finances Publiques (DGFiP) phases the obligation by company size, giving smaller businesses more runway to build the capability larger ones are expected to have already.
The architecture underneath has moved since the reform was first announced. The original design routed all B2B invoices through a single public platform, the Portail Public de Facturation (PPF). That has shifted toward a model closer to the UAE's: businesses exchange invoices through certified private platforms — Plateformes de Dématérialisation Partenaires, or PDPs — with the PPF acting as a central directory and reporting conduit rather than the sole channel every invoice must pass through. Real-Time Tax Transformation (forthcoming) frames this kind of shift as evidence that the interoperability model, rather than a single state-run clearance point, is becoming the default architecture wherever a jurisdiction has the option to choose it.
Phasing by Size Creates a Group-Structure Problem, Not a Country Problem
A UAE group with a large French holding entity and smaller operating subsidiaries does not face one French go-live date. It faces two or three, staggered across 2026, 2027 and 2028, applied to entities that may already share ERP instances, shared services, and master data pipelines. Building the compliance capability only for the entity whose deadline is closest, then repeating the exercise when the next entity's deadline arrives, reproduces the failure Real-Time Tax Transformation warns against: the same transaction data governed differently depending on which subsidiary generated it.
The more defensible approach treats the earliest French deadline as the trigger for group-wide readiness, not entity-specific readiness. If the large or mid-sized French entity is building PDP connectivity, structured invoice mapping, and master data governance for September 2026, that same capability should be designed to extend to the SME and micro entities in the group without a second implementation project starting from zero in 2027 and 2028.
What Transfers From UAE Preparation
A business that has mapped its ERP to PINT-AE has already done the harder part of what PDP connectivity requires in France: identifying where transaction data is incomplete, inconsistent, or trapped in a format the exchange network cannot read. The specific fields, code lists, and validation rules differ between PINT-AE and the French specification, and a UAE ASP connection does not transfer unchanged. What transfers is the governance discipline — the questions about master data ownership, exception triage, and reconciliation that a Peppol-based interoperability model asks regardless of which jurisdiction is asking them.