Skip to Content

E-invoicing: the formats generated by Odoo

Factur-X, UBL, approved platform, Chorus Pro: what Odoo produces natively and what still needs checking before adding a layer.
November 16, 2026 by
ANOR, Cyrille de LAMBERT
| No comments yet

In brief Odoo natively generates invoices in Factur-X format (PDF/A-3 with embedded CII XML) from version 17 to version 20, without any third-party module. For the French approved platform, the l10n_fr_pdp module emits UBL 2.1 at the French profile and checks BR-FR rules before sending. Post-conversion is unnecessary: the structured file is born from the same accounting entry as the human-readable document.

A vendor recently offered to convert into Factur-X the PDFs that Odoo already produces in Factur-X. The intention was kind. The need does not exist. This small incident is a useful reminder: before adding a layer to an Odoo Factur-X e-invoicing project, it is worth knowing what the ERP already does. We reviewed Odoo's public source code to answer that question precisely.

What Odoo produces natively, from version 17 to version 20

Odoo has generated invoices in Factur-X format since version 17. For a French client, Factur-X is the default format offered, via the account_edi_ubl_cii module present in branches 17.0 to 20.0 of the public repository (github.com/odoo/odoo, consulted in November 2026).

In practice, this covers several technical guarantees:

  • A human-readable PDF and a structured XML in a single file.
  • The XML declares the Factur-X EXTENDED profile, compliant with the European standard EN 16931.
  • The PDF is produced in PDF/A-3 format, the archiving format that Factur-X requires.
  • Odoo also reads Factur-X invoices from your suppliers: it recognises the XML embedded in the PDF and creates the purchase invoice from its data.

One comment in the code is worth quoting: on each send, Odoo generates a Factur-X XML and embeds it in the PDF, even when another transmission format is selected. The stated reason is interoperability. This behaviour is consistent across versions 17, 18, 19 and 20.

A single file, born from the same accounting entry

When you validate an invoice in Odoo, the PDF and the XML are born from the same accounting entry. There is no second data entry, no reconstruction of data from an image.

This changes how you check things. A single file needs to be verified. That file says exactly the same thing as the accounting records. No visible seam between the document your client reads and the data their software reads.

Post-conversion follows the reverse path: it takes an already-produced PDF, reconstructs its data and inserts an XML into it. Each step is an opportunity for a discrepancy between the PDF, the XML and the accounting records. You then need to demonstrate that nothing has been distorted. That is additional verification work for a result the ERP already delivers.

The approved platform: UBL on emission, all formats on reception

The tax authority requires mandatory reception for all companies from 1 September 2026 and emission for SMEs from 1 September 2027 (impots.gouv.fr, page "External specifications and standards for electronic invoicing", consulted in November 2026).

For this transition, Odoo offers the l10n_fr_pdp module ("France - E-Invoicing (Approved Platform)"). Its code was added on 19 December 2025 in versions 18, 19 and 20, then backported to version 17 in July 2026 (commit dates from the public repository).

  • On emission, an invoice sent to a recipient on the platform is transmitted as UBL 2.1 at the French profile. Odoo enforces this: for regulated French invoices, only this format is accepted. The human-readable PDF is included in the UBL file.
  • On reception, the platform accepts UBL 2.1, CII, Factur-X and the corresponding French profiles.
  • For other sends, in particular by email, the PDF retains its embedded Factur-X XML.

These two channels do not conflict. They originate from the same accounting entries. The structured file changes its wrapping according to the channel; the source data remains identical. It is worth noting that UBL Peppol BIS 3 has been available for French companies in Odoo for several versions; what is new is the French profile for the approved platform.

The BR-FR rules the code applies before export

An electronic invoice must comply with the European standard EN 16931 and, in France, additional rules. In Odoo's code, these French rules carry the prefix BR-FR. Here are the ones we found:

  • BR-FR-05: mandatory legal notices: flat-rate debt recovery indemnity of 40 euros, late payment penalties, early payment discount notice.
  • BR-FR-12 and BR-FR-13: the buyer's and seller's electronic addresses; for a company on the approved platform, Odoo checks that the Peppol identifier and its endpoint are filled in.
  • BR-FR-CO-09: the due date, populated for the relevant invoicing frameworks.
  • BR-FR-04: code 386 for a down-payment invoice and 503 for a down-payment credit note.

Odoo also checks, before export, that the SIREN or SIRET of both parties is present, along with the platform identifier and the original reference for a credit note. These checks prevent an incomplete file from being issued. They guide corrections before sending.

Chorus Pro: an adaptation available since June 2022

For invoicing public sector bodies, Odoo offers the "France - BIS3 integration for Chorus Pro" module. It adds the three fields used with Chorus Pro: buyer reference, order reference and contract reference. These references are integrated into the XML at export. The module also verifies the SIRET of the final recipient and that of the supplier. To our knowledge, Chorus Pro has accepted Factur-X invoices produced by Odoo since its launch.

Five checks before adding a layer

Software that checks its files at export does not replace independent verification. On every project, we validate each type of emitted file with an external validator, against EN 16931 and BR-FR rules, before go-live. The French rules are published as Schematron by the FNFE-MPE, based on the AFNOR XP Z12-012 standard (fnfe-mpe.org, consulted in November 2026). This check is performed once per use case, on a single file.

Before considering an additional tool, review these five points:

  • Your Odoo version. Native Factur-X exists from version 17 to version 20. If you are on an earlier version, an Odoo upgrade is the real topic.
  • The formats activated. On each customer record, check the electronic invoice format selected and the sending method.
  • Your partners' data. SIREN or SIRET, VAT number, Peppol electronic address: these are what pass the checks.
  • Your company settings. Payment terms, legal notices, bank details, platform identifier.
  • A test send. Issue a test invoice for each case: private customer, customer on the approved platform, public sector customer. Validate the produced files with an independent tool.

If all of this is in place, there is nothing to convert. To learn more about the obligation in force, see our article on mandatory e-invoicing. And if you want to understand the detail of the Odoo applications involved, the Odoo Accounting page gives you the full picture.

Are you preparing your move to e-invoicing? Spend 30 minutes with an ANOR consultant: we look at your Odoo version, your activated formats and your partner configuration. We will tell you precisely what still needs to be done.

Frequently asked questions

Does Odoo generate Factur-X without a third-party module?

Yes. Factur-X is produced natively by the e-invoicing module included in Odoo, from version 17 to version 20. For a French client, it is the default format offered, with no additional installation required.

What is the difference between Factur-X and UBL 2.1 in Odoo?

Factur-X is a PDF/A-3 that embeds a CII-type XML. UBL 2.1 is a pure XML file that can include the PDF as an attachment. Odoo emits UBL 2.1 at the French profile to the approved platform and retains Factur-X for direct email sends.

Should the files produced by Odoo be checked before go-live?

Odoo applies its own checks at export, including the BR-FR rules. We also recommend independent verification, using the FNFE-MPE Schematron, on each type of invoice issued, before the first production send.

Is the approved platform module (l10n_fr_pdp) available on Odoo 17?

Yes. The module was added in December 2025 in versions 18, 19 and 20, then backported to version 17 in July 2026, according to the commits in Odoo's public repository.

What happens if I remain on an Odoo version earlier than 17?

Native Factur-X and the approved platform module are not available before version 17. Versions 16 and earlier are no longer supported by the publisher. Migrating to Odoo 18, 19 or 20 is the appropriate step to remain compliant.

ANOR, Cyrille de LAMBERT November 16, 2026
Share this post
Tags
Archive
Sign in to leave a comment

A topic concerns you? Let's talk

Thirty minutes with an Odoo consultant to link this news to your situation and decide what comes next.