Odoo France E-Invoicing 2026: PA Status, Setup and How to Prepare

France's e-invoicing reform is now live, and the question for Odoo users is no longer whether Odoo will comply but whether your own database, data and processes are ready. Our Odoo consulting services cover that readiness check for French entities.

This guide is for CFOs, finance managers and IT leads running Odoo for a French company or a French subsidiary. If you also invoice Belgian customers, read our Odoo Peppol e-invoicing guide for Belgium, as the two rules differ.

What is the France e-invoicing mandate in 2026?

The France e-invoicing mandate requires VAT-registered companies to exchange domestic B2B invoices in a structured format through an approved platform and to report other sales data to the tax authority. It runs in two phases.

Date	Who	Obligation
1 September 2026	Every VAT-registered company	Receive domestic B2B e-invoices through an approved platform
1 September 2026	Large (GE) and mid-sized (ETI) companies	Send domestic B2B e-invoices and submit e-reporting data
1 September 2027	Small and medium (PME) and micro businesses	Send e-invoices and submit e-reporting data
Since January 2020	All suppliers to the public sector	Send B2G invoices through Chorus Pro

The Odoo France localization documentation states the same dates. Your category (GE, ETI, PME or micro) follows the official French company size rules, so confirm it with your accountant.

A PDF sent by email is not a facture électronique. The DGFiP FAQ says an e-invoice carries 34 structured data fields, including four new ones used to route it:

• the customer's SIREN number;
• the category of the operation: goods, services or both;
• the option chosen for paying VAT;
• the delivery address of goods when it differs from the customer's address.

Is Odoo a plateforme agréée (PA) in France?

Yes, Odoo is a registered plateforme agréée, listed by the DGFiP among operators that met every condition, including live interoperability tests. The list on impots.gouv.fr, updated on 30 October 2026, shows Odoo with a registration date of 15 April 2026.

Odoo announced the news in its post on Odoo as an approved platform registered in France, dated 22 April 2026. The term PA replaced the older PDP (plateforme de dématérialisation partenaire), so "Odoo PDP" and "Odoo PA" mean the same thing.

This matters for your setup. With a PA built into Odoo, you do not need a separate platform contract or a connector between Odoo and another PA. The DGFiP FAQ notes that about 150 platforms hold State approval, so you can still choose another one if you prefer.

Which Odoo versions support French e-invoicing?

The l10n_fr_pdp module exists in Odoo 17, 18, 19 and 20, so Odoo 16 and older databases must upgrade or use an outside platform. The module is published under the LGPL-3 licence in Odoo's main code base.

Odoo version	French PA module	What to do
Odoo 20	Yes, plus POS e-reporting	Activate and test
Odoo 19	Yes, plus POS e-reporting	Activate and test
Odoo 18	Yes, documented by Odoo	Activate and test
Odoo 17	Yes, in the code base	Activate, then plan an upgrade, as standard support ended September 2026
Odoo 16 and older	No	Upgrade, or route invoices through another PA
Odoo Online	Follows Odoo's hosted release	Activate in Settings

Odoo 17 left standard support in September 2026, and our Odoo version support timeline explains what that means. Not sure what you run? The free Odoo health check shows your version and modules.

What changes in your Odoo setup?

Odoo adds a French e-invoicing section to Accounting settings, new fields on contacts and invoices, an e-reporting menu, and automatic import of supplier e-invoices. Most of the work is in data, not code.

Area	Before the reform	After activating the PA module
Sending B2B invoices	PDF by email	UBL e-invoice through the e-invoicing network
Receiving supplier bills	Email, OCR or manual entry	Draft bills imported several times a day
Customer records	VAT number, address	SIREN checked against the national directory
Invoice lines	Free form	At least one product or label and exactly one tax per line
B2C and export sales	No report	XML e-report sent every ten days
Correcting a sent invoice	Reset to draft	Not allowed for domestic B2B invoices already e-reported

Odoo receives Factur-X, UBL and CII documents but sends only UBL. Once registered on the French network, your company is also registered on Peppol automatically, with no separate step. Odoo's general electronic invoicing documentation covers the shared formats.

Odoo 20 adds helpful touches, listed in our Odoo 20 accounting release notes. The send dialog groups invoices by sending method, a list action downloads all PDF and XML files in one zip, and delivery addresses gain a GLN field.

How do you set up Odoo French e-invoicing step by step?

Activation takes one session if you have a legal representative on hand, but plan a full test cycle before you rely on it. The steps below follow Odoo's documented flow.

1. Check the module: confirm France E-Invoicing (Approved Platform), l10n_fr_pdp, is installed. Install the POS e-reporting module if you sell over the counter.
2. Activate: in Accounting or Invoicing, open Settings, find French Electronic Invoicing and click Activate Electronic Invoicing.
3. Authenticate: enter a legal representative's email, confirm a 5-digit code, upload an ID card, passport or residence permit, then sign the Attestation de désignation de plateforme agréée.
4. Validate the SIREN: refresh, check the Identifier field holds your SIREN and click Validate Registration.
5. Set options: choose the incoming bills journal, enable e-reporting and sending to the PPF if your company is in scope, and set the e-reporting periodicity.
6. Wait one day: your entry in the national e-invoicing directory (annuaire) becomes effective the day after setup.
7. Verify contacts: add each French customer's SIREN and click Verify until Odoo shows "Partner is in the annuaire".
8. Test: send a small batch, check the E-Invoicing Status reaches Done, then refuse and confirm a test supplier bill.

Each legal entity has its own SIREN, so a group repeats steps 2 to 6 per company. Our guide to Odoo multi-company setup covers the wider structure.

How does e-reporting work in Odoo?

E-reporting sends transaction and payment data that is not an e-invoice, such as B2C sales and cross-border B2B sales, to the tax authority through your PA. Odoo builds and submits an XML report every ten days.

Find reports under Accounting, Reporting, E-reporting. Each has a status: Ready, Error (resubmitted in 5 to 7 days), Sent or Completed. Smart buttons show which invoices and payments each report includes.

Three cases trip teams up. Domestic B2B invoices paid in cash also go through e-reporting. VAT-exempt operations under articles 261 to 261 E are excluded. If you reset an e-reported B2C or export invoice to draft, Odoo sends the correction when you confirm it again.

Shops and restaurants need extra care. The POS e-reporting module handles Flux 10 reporting, so test a full day of sessions, refunds and closing before you rely on it. Our Odoo POS implementation guide covers the session setup.

What does Odoo French e-invoicing cost?

Odoo's own France e-invoicing page calls Odoo a free PDP, so the platform itself adds no fee to your subscription; the real cost is preparation and testing. Other platforms often charge per document or by credits.

Odoo's French e-invoicing page says "Odoo is a free PDP." You still pay your normal licence: on the Odoo pricing page, US Standard is US$31.10 and Custom US$61.00 per user a month billed yearly.

The bigger budget lines are internal. Typical effort, as an illustrative industry estimate rather than a quote:

• Data clean-up: SIRENs, delivery addresses, taxes and product labels on customers and open invoices.
• Configuration and tests: one company with standard flows often needs a few days of consultant time.
• Customization fixes: custom invoice reports or tax logic that break the one-tax-per-line rule.
• Upgrade: Odoo 16 and older need a version move first, which is usually the largest item.

For full projects, our published Odoo implementation ranges are US$3k to US$9k for small firms, US$9k to US$27k for mid-size and US$27k to US$150k+ for large ones, varying with scope.

What problems do French Odoo users hit?

Most failures come from missing or wrong master data and from formats the customer's platform does not accept, not from the Odoo module itself. Plan for these before you switch your sending method.

One user on the Odoo forum, in a thread on French e-invoicing through the approved platform, found the customer in the directory but got "Partner cannot receive format" when sending. The suggested cause was a format mismatch, with no confirmed fix.

Other common issues we see in testing:

• Missing SIREN: customers imported with only a VAT number cannot be found in the directory.
• Mixed taxes on one line: custom reports or imports that put two taxes on a line block sending.
• Customers not yet on a PA: the invoice is rejected; the DGFiP allows email or post as an exception.
• Correcting sent invoices: teams used to reset-to-draft must switch to credit notes.
• Duplicate copies: sending a PDF copy as well risks double payment, so follow the delivery status first.

The DGFiP's start-up guide says firms on a serious compliance path will not face automatic sanctions during the launch phase. It also says this is not a postponement, so keep a written record of issues and fixes.

Which industries need extra care with Odoo e-invoicing in France?

Retail, construction, distribution, services and public-sector suppliers each have one flow that needs specific testing. The table shows where to focus.

Industry	Pain or cost driver	Odoo approach	How iVentureTeam helps
Retail and restaurants	High B2C volume, cash sales	POS e-reporting module, e-reports every ten days	Test sessions, refunds and closings
Wholesale and distribution	Many delivery addresses	Delivery address and GLN on invoices	Clean address data, map routes
Construction	Progress billing, retentions	Down payments and credit notes in Accounting	Test billing stages end to end
Professional services	Recurring and timesheet invoices	Subscriptions and timesheets feeding invoices	Check operation category and taxes
Public-sector suppliers	Chorus Pro references	Chorus Pro module over Peppol	Set buyer, contract and order references
Exporters	Cross-border B2B sales	E-reporting, not e-invoicing	Verify scope and fiscal positions

For suppliers to French public bodies, Odoo sends invoices to Chorus Pro over Peppol with the Chorus Pro module. Fill the buyer reference, contract reference and purchase order fields that Chorus Pro expects.

How should you prepare your Odoo database before September 2027?

Small and mid-sized firms still have time, but receiving is already mandatory, so activate now and use the months before 2027 to fix data and test sending. Large and mid-sized firms should be live already.

1. Confirm scope: your company category, B2B, B2C and export share, and any public-sector customers.
2. Check the version: Odoo 17 or newer, with the l10n_fr_pdp module available.
3. Clean master data: SIREN, delivery addresses, VAT payment option and product labels.
4. Fix customizations: custom invoice layouts, tax logic and imports that break the line rules.
5. Activate and register: one legal representative per entity, one SIREN per company.
6. Run a pilot: send to a few friendly customers and track every status.
7. Train the team: credit notes instead of resets, refusal reason codes and the e-reporting menu.

Our Odoo upgrade services handle step 2 when you run Odoo 16 or older.

How iVentureTeam helps with Odoo France e-invoicing 2026

iVentureTeam prepares Odoo databases for the French reform, from the version check to the first live e-invoice. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• Readiness check: version, modules, custom code and master data reviewed against the PA rules.
• Localization setup: French accounting, e-invoicing, e-reporting and Chorus Pro configured per company, as part of our Odoo implementation services.
• Data clean-up: SIRENs, addresses and taxes corrected in bulk, with an audit trail.
• Customization fixes: invoice reports and imports adjusted to pass the format checks.
• Training: finance staff taught how to send, refuse, correct and read e-reporting statuses.

Odoo localization case study: Fernando Tax Management

A Dutch tax firm needed accurate localized reports from Odoo, the same discipline French e-invoicing now demands. Fernando Tax Management B.V. serves clients in the Netherlands and Curaçao.

The firm's legacy system relied on hand-keyed data, which produced duplicate and inconsistent records. Its reports also had translation gaps, a real risk for output that feeds government compliance.

We migrated the firm to Odoo 18 in 10 weeks, fixed a hidden journal lines issue, corrected translation defects and built custom tax compliance reports for both jurisdictions. Manual data entry fell by 60%.

Read the full Fernando Tax Odoo accounting automation case study, and see how Odoo Accounting works for the basics behind it.

The bottom line on Odoo France e-invoicing 2026

Odoo is a registered French approved platform, so compliance depends on your version and your data, not on buying another tool. Get to Odoo 17 or newer, clean your SIREN and tax data, and test before September 2027.

Receiving is already mandatory for everyone. Activate the module now, run a pilot with a few customers, and train your team on credit notes and e-reporting. Firms that start early will reach 2027 with a calm cutover.

Ready to make your Odoo database e-invoicing ready for France?

Find out what your database needs before your sending deadline. Request an Odoo France e-invoicing readiness review, call +91-90235-15208, or email business@iventureteam.com.