The timeline, precisely
| Date | Obligation | Who |
|---|---|---|
| 1 Sept 2026 | Must be able to receive e-invoices via an accredited platform | Every VAT-registered business in France |
| 1 Sept 2026 | Must issue e-invoices (and e-report) | Large enterprises and mid-sized companies (ETIs) |
| 1 Sept 2027 | Must issue e-invoices (and e-report) | SMEs and micro-enterprises |
The legal fine framework is in place from day one — €50 per non-compliant invoice, capped at €15,000 a year for issuance failures, and €500 per missed e-reporting transmission. In practice the DGFiP has said there will be no automatic penalties in late 2026: enforcement starts with individual review, support and formal notice, and a business that fails to register with a receiving platform gets a three-month window to fix it before fines apply. Do not read that as a postponement — the obligations themselves start on 1 September 2026, and issuers' files have to be right for their invoices to be delivered at all.
Exchange does not run over email or a free public portal: invoices flow between Plateformes Agréées (PAs) — accredited private platforms — with the tax administration receiving extracted data. You will need a PA (as of mid-2026 only around twenty are operationally exchanging flows, so onboarding queues are real). We are not a Plateforme Agréée, and no converter or validator makes you one.
So what is the actual problem to solve?
Your PA handles transmission. What it does not do is fix your data. The French system accepts three structured formats (the socle): Factur-X (PDF/A-3 with embedded CII XML), UBL and CII — all constrained by EN 16931 semantics. The gap most businesses discover in the last weeks is between what their invoicing software exports and what their platform accepts:
| You have | The gap | Close it with |
|---|---|---|
| Spreadsheet/CSV exports from accounting software | No structured XML at all | CSV → UBL/CII converter, validated before download |
| A “Factur-X” PDF from your tooling | Is the XML really embedded? Which profile? Does it validate? | Free Factur-X inspector |
| XML that your platform or customer rejects | A bare rule ID like BR-CO-16 | Free validator + plain-English rule library |
Checking files before they enter the platform circuit is cheap; chasing a rejected invoice through a PA's support queue in September will not be.
Factur-X profiles matter in France
Factur-X is the French-German hybrid standard, and its profiles differ sharply: MINIMUM and BASIC WL carry no invoice lines and are not full EN 16931 invoices, while BASIC, EN 16931 and EXTENDED are. The inspector reads the embedded XML, tells you which profile the file declares, and validates the full profiles against the official ruleset — so you know what you are actually sending your platform.
Five weeks is enough — if you test now
Drop your XML into the validator or your PDF into the Factur-X inspector. Every failing rule links to a plain-English explanation and fix. Free, no signup, nothing stored.
Validate an e-invoice freeNeighbouring deadlines
Belgium's B2B mandate is already in force with penalties. Germany's issuance obligation phases in from January 2027.