Odoo Integration Services in France
Integrations are easy to demonstrate and hard to run. The work is not the connection, it is what happens on the day one side is down.
What changes the cost of an Odoo integration in France
The delivery method is the same everywhere. What moves the number is what this market demands of the system, and how much of that Odoo already covers.
France runs Facturation electronique (mandatory B2B e-invoicing and e-reporting reform). That is configuration and testing work inside the build, not an afterthought, and it is the item most often left out of a quote.
6 of the 19 payment options that matter in France are not shipped with Odoo, so they need a paid connector or a build. 13 ship in the box.
11 of the 15 couriers used in France have no Odoo connector. 4 do. Which ones you actually use changes the estimate more than the number of users does.
Odoo's France localization does not cover everything. The gaps are listed on the country page and each one is either a build or a bought module.
Statutory payroll in France has its own rules. Whether Odoo ships a payroll localization for this market decides if that is configuration or development.
Market facts on this page checked on 22 August 2026 by Waqas Riasat, Way4Tech.
Where France starts from
France runs 6 native Odoo localization items and 6 custom ones. Integrations here sit on top of whichever of those already exists, which is a different job to building on a market with no localization at all.
Where we deliver in France
An integration depends on which systems sit on the other end, not on which city the business sits in. Paris, Lyon, Marseille, Toulouse, Lille, Bordeaux and Nantes, and businesses across รle-de-France, Auvergne-Rhรดne-Alpes, Occitanie and Hauts-de-France, are covered on the same terms.
What odoo integration has to satisfy in France
The rules that decide how much of this is configuration and how much is a build. Everything below is from our France register, checked against a primary source.
Live from 1 September 2026. Every business subject to French VAT must be able to receive e-invoices from that date, and large companies and ETIs must also issue them and file e-reporting; PME, TPE and micro-enterprises follow on 1 September 2027.
- Invoices must be issued, transmitted and received through a Plateforme Agreee (PA, formerly called PDP), a private operator registered by the DGFiP for three renewable years. Article 289 bis of the Code general des impots. The list of registered platforms is published on impots.gouv.fr.
- The chosen PA passes the invoice data to the tax administration (article 289 E CGI). This is continuous transaction control by reporting through an accredited intermediary, not per-invoice clearance where the tax authority validates an invoice before it is legally valid.
- The public portal (PPF) no longer acts as a free exchange platform. Article 123 of the loi de finances pour 2026 formalised the simplification announced in August 2025, leaving the private platforms at the centre of the flow.
- A central annuaire (directory) routes invoices to the recipient's platform. It is made available to the PAs and holds the addressing data. SIREN, SIRET and recipient establishment on the customer record are what make routing work.
- Structured format built on the EN 16931 semantic model. DGFiP external specifications version 3.2 dated 30 April 2026, backed by AFNOR norms XP Z12-012 (invoice and lifecycle status formats and profiles), XP Z12-013 (APIs between business systems and approved platforms) and XP Z12-014 (B2B use cases). The three accepted syntaxes are Factur-X (hybrid PDF plus XML), UBL and CII.
- Tax The standard TVA rate is 20 percent. Reduced rates of 10 percent, 5.5 percent and 2.1 percent apply only to categories expressly listed in the Code general des impots. Guadeloupe, Martinique and La Reunion run a separate 8.5 percent standard rate.
- Tax Three VAT regimes. Franchise en base (no VAT declaration) below 85,000 euros turnover for goods and hospitality or 37,500 euros for services. Regime reel simplifie between those thresholds and 945,000 euros (goods) or 286,000 euros (services), filed annually on form CA12, with advance payments in July (55 percent) and December (40 percent) and a May balance. Regime reel normal above those thresholds, filed monthly on form CA3, or quarterly if VAT due is under 4,000 euros a year.
- Tax A business on the regime simplifie whose annual VAT exceeds 15,000 euros has to switch to monthly filing. That threshold is the one that usually forces a mid-year change in how the ERP files.
- Tax All VAT returns and payments go online through the espace professionnel on impots.gouv.fr. Paper filing is not an option.
- Tax From 1 September 2026 the DGFiP receives invoice and transaction data through approved platforms with the stated aim of pre-filling VAT returns. Plan for the VAT return in the ERP to be reconciled against what the platform already sent, not just computed locally.
- Chart of accounts, fiscal positions and tax configuration for companies based in mainland France (l10n_fr_account). The module is scoped to mainland France, so overseas departments need separate handling.
- French VAT report export that can be sent to the DGFiP, an OGA or an accountant (l10n_fr_reports).
- POS anti-fraud certification under CGI article 286 I-3 bis (l10n_fr_pos_cert).
- Mandatory e-invoicing. Odoo completed the DGFiP registration and is an approved platform, and ships l10n_fr_pdp to send and receive through it, plus l10n_fr_pdp_pos for POS e-reporting. Activation is in Accounting or Invoicing, Configuration, Settings, French Electronic Invoicing.
- Factur-X and UBL generation, and Chorus Pro submission for public-sector customers (l10n_fr_facturx_chorus_pro).
- FEC import for loading opening balances and prior-year history (l10n_fr_fec_import).
- French payroll. France is not on Odoo's payroll localization list and l10n_fr_hr_payroll_account only carries the accounting postings. DSN generation, URSSAF contribution logic, conventions collectives and the bulletin de paie layout are not in the box. Budget for a separate payroll tool plus an interface, not an Odoo payroll build.
- Partner and product master data for the four new mandatory invoice mentions. Buyer SIREN on every B2B partner, delivery address when it differs, and operation nature per line. This is a data cleanup project across the customer master, and it is where go-lives slip.
- Annuaire routing. Wrong or stale SIREN and SIRET on customer records is the main cause of invoices that never reach the recipient's platform. Build validation and a monitoring view for undelivered invoices and returned lifecycle statuses before go-live.
- Lifecycle status handling. The platform sends statuses back and the business has to act on rejections. Standard Odoo screens will usually need extending into a proper exception queue.
- FEC export, CA3 and CA12 filing forms, and DAS2 all sit in OCA modules rather than the standard localization, so a Community or Enterprise stack needs those pulled in and version-matched.
Reviewed 2026-08-22. The full France register
How we run the work
5 stages, the same in every market: Data flow mapping, Interface and access setup, Build with failure handling, Testing the unhappy paths, Go-live and reconciliation. The method does not change by country, so it is written up once rather than repeated here.
The integrations this market usually needs
Badged by what it takes in Odoo. Anything not marked In Odoo is a paid connector or a build, and that is the part quotes usually miss.
Questions we get asked
- How long does a typical integration take?
- A single well-documented flow with sandbox access on both sides is a short piece of work. What extends it is nearly always outside the code: waiting for credentials, discovering the other API is undocumented in the area you need, or finding that nobody has decided which system owns the customer record.
- Can you integrate a system that has no API?
- Often, through file exchange, database access or scheduled exports, and the result works. It is less immediate and needs stricter reconciliation because there is no acknowledgement to rely on. We would rather do that properly than pretend a scraped interface is an integration.
- Does Odoo have an official localization for France?
- Yes. Odoo ships 6 native items for France, covering the basics of the chart of accounts and statutory setup. 6 areas are still outside that localization and get built or bought separately.
- Is e-invoicing mandatory in France?
- Live from 1 September 2026. Every business subject to French VAT must be able to receive e-invoices from that date, and large companies and ETIs must also issue them and file e-reporting; PME, TPE and micro-enterprises follow on 1 September 2027. The France e-invoicing page carries the full detail and the sources.
- What VAT or sales tax does Odoo have to handle in France?
- The standard TVA rate is 20 percent. Reduced rates of 10 percent, 5.5 percent and 2.1 percent apply only to categories expressly listed in the Code general des impots. Guadeloupe, Martinique and La Reunion run a separate 8.5 percent standard rate.
- Do you work with businesses in Paris and other parts of France?
- Yes. An Odoo integration runs remotely by default, and being based in one city inside France does not change the plan or the price. Cities we cover for on-site visits: Paris, Lyon, Marseille, Toulouse, Lille, Bordeaux, Nantes. Regions we cover: รle-de-France, Auvergne-Rhรดne-Alpes, Occitanie, Hauts-de-France. We travel on-site for discovery workshops and go-live week when the engagement calls for it.