It's official on the vendor side: Odoo is now registered as an Accredited Platform (PA, Plateforme Agréée) under the French e-invoicing reform. The final certification step — interoperability tests with the Public Invoicing Portal (PPF) and the other PAs — has been validated.
What this changes in practice
Until now, Odoo appeared on the DGFIP list with a "registered subject to conditions" status: application accepted, interoperability being validated. The move to final accreditation lifts the last uncertainty for companies that hesitated to rely on Odoo as the cornerstone of their 2026/2027 compliance.
Three points are worth highlighting.
- Built-in PA, not a third-party solution. Odoo issues, receives and routes electronic invoices directly from the ERP, without going through an external dematerialization operator. No cost per invoice, no separate contract, no additional interface to maintain on top of the management system.
- Hosting independence. The PA works equally well on Odoo Online, Odoo.sh and on-premise. For customers on dedicated infrastructure — a sensitive topic for several of our industrial integrations — this is a real relief: no forced cloud migration to stay compliant.
- Versions concerned: V18 and V19. V17 is still under discussion on the vendor side, with no commitment at this stage. Customers on V17 must therefore factor this into their upgrade path, with autumn 2026 as the horizon.
Reminder of the DGFIP timeline
- September 1, 2026: receiving obligation for all VAT-liable companies, and issuing obligation for large companies and mid-sized companies (ETI).
- September 1, 2027: issuing obligation extended to SMEs, very small businesses and micro-enterprises.
The question is no longer "should we prepare?" but "when do we start the project?". On an existing Odoo estate, compliance revolves around three workstreams: making the third-party master data reliable (SIRET, intra-EU VAT number, billing addresses), activating the PA module and configuring the endpoints in the DGFIP directory, and adapting validation workflows to handle the statuses returned by counterparties' PAs.
Lessons from the Belgian experience
Structured B2B e-invoicing has been mandatory in Belgium since January 1, 2026, and Odoo already operates there via Peppol. The French architecture (PA + directory + e-reporting) is specific, but the underlying logic is the same. The friction points reported in Belgium — master data quality, handling of rejections, adapting approval workflows — will recur identically in France. Better to anticipate them.
What we recommend
- Customers on V17: plan the upgrade to V18 or V19 before summer 2026.
- Customers on V18/V19: start now with an audit of third-party master data and invoicing flows to identify the gaps to address.
- Everyone: formalize the structure of receiving endpoints (by company, by SIRET establishment or by document type — vendor invoices, expense reports) before the directory opens definitively.
The reform is a regulatory constraint, but it demands a structuring effort that benefits the whole system: more reliable data, no more re-entry, traceability of invoice lifecycle statuses, faster reconciliation and cash collection. Companies that take it seriously today will come out with more robust operations — not just compliant ones.