The DGFIP has made Odoo's final registration as an Accredited Platform official. Companies that were waiting for this signal to decide on their compliance path now have all the elements they need to decide.
A status moving from "subject to conditions" to "final"
The DGFIP directory of Accredited Platforms had so far listed Odoo with the mention "registered subject to conditions": the file had been reviewed, but the cross interoperability tests with the Public Invoicing Portal and the other PAs remained to be completed. This last step has now been passed. The publisher therefore joins the list of fully operational platforms able to carry B2B electronic invoicing in France.
For finance directors and IT directors who were managing their 2026 project conditionally, the consequence is immediate: there is no longer any risk of having to switch to a third-party PA midway if final accreditation had not been obtained. The Odoo path is secured all the way.
Why a native PA in the ERP changes the budget equation
Most ERP vendors do not embed their own PA. They rely on a partner e-invoicing operator, who charges per flow and imposes their own contractual cycle and their own exchange channel. Odoo's logic is different: the PA is a module of the ERP, plugged into the accounting engine and into sales management.
Three direct consequences for total cost of ownership:
- No volume-based pricing. Issuing, receiving and routing invoices do not fall into a third-party provider's "per flow" price grid.
- One vendor, one contract. The ERP, the PA and support are with the same publisher, which avoids the pitfall of shared chains of responsibility in the event of an incident.
- One single scope to operate. No third-party interface to maintain, monitor or update with every regulatory change.
For a multi-company SME or a high-volume mid-sized company, the cumulative gap over five years is significant.
Hosting: no forced switch
The PA module is independent of the deployment mode. It works on Odoo Online, on Odoo.sh and on on-premise installations — including on dedicated infrastructure. This point matters for manufacturers and groups with data location constraints or hybrid architectures: 2026 compliance does not trigger, as a side effect, a cloud migration project.
Supported versions: V18 and V19, V17 pending
The publisher's scope currently covers Odoo 18 and Odoo 19. There is no firm commitment on V17 at this stage. Companies still on V17 must therefore treat the upgrade as a compliance prerequisite, not as a disconnected IT topic. An Odoo version upgrade is not a reinstallation — it is becoming industrialized — but it needs to be prepared, especially if custom modules are involved. The reasonable window to start the work is before summer 2026.
The regulatory calendar to keep in mind
| Deadline | Scope |
|---|---|
| September 1, 2026 | Mandatory reception for all VAT-liable companies. Mandatory issuing for large companies and mid-sized companies. |
| September 1, 2027 | Mandatory issuing for SMEs, very small businesses and micro-enterprises. |
The September 2026 deadline therefore concerns 100% of companies on the reception side. An SME that will only be required to issue in 2027 must nevertheless be able to receive structured-format invoices from autumn 2026.
The three workstreams of a compliance project
Technically activating the PA is not the longest part. The groundwork covers three areas.
The partner master data. SIRET numbers, intra-community VAT numbers and billing addresses must be complete, up to date and consistent. Incomplete partner data will block issuing or cause a rejection on reception. On master data built up over ten years, the anomaly rate typically runs between 5 and 15%. This is the item that requires the most anticipation.
PA and endpoint configuration. Module activation, registration in the DGFIP directory, choice of routing model (per company, per SIRET establishment, per document type). This structuring is an organizational decision, not a technical topic: it determines how readable incoming flows are for accounts payable and expense report management.
Validation workflows. Invoice lifecycle statuses — submitted, rejected, paid, etc. — are returned by the counterparties' PAs. Internal approval and reminder circuits must be adapted to make use of this feedback. It is an opportunity to review reconciliation and customer reminder automations at the same time.
Lessons from Belgium
Belgium moved to mandatory structured B2B invoicing on January 1, 2026 via Peppol. The French architecture is not the same — the PA/PPF pairing with a centralized directory is a French specificity — but the friction points observed in Belgium will recur here in the same way:
- Initial quality of the partner master data underestimated.
- High volume of rejections in the first weeks, for lack of sufficient pre-production testing.
- Internal approval circuits poorly calibrated to handle incoming statuses.
French companies have the advantage of being able to learn from a neighbor already under the mandatory regime. This is an asset to exploit during scoping.
Our take for the coming weeks
- If you are on Odoo 17, the priority is the version path. Scope the upgrade to V18 or V19 now to aim for a go-live before summer.
- If you are on V18 or V19, start the partner master data audit and the invoicing flow mapping without waiting. This is the phase where surprises concentrate.
- Whatever your case, make the organizational decision on reception endpoints ahead of the final opening of the directory. Changing this configuration after go-live is technically feasible but operationally costly.
The reform remains a regulatory constraint. But it forces a discipline — clean master data, structured endpoints, status traceability, automated reconciliation — whose benefit goes well beyond the scope of compliance. Companies that treat the subject seriously today come out with a more robust management system, and a shorter order-to-cash cycle.