Odoo Localizations: Benelux
Belgian, Dutch, French and Luxembourgish accounting all have their own VAT regimes, e-invoicing rules, payroll specifics and reporting standards. Odoo handles them — but only if the right localization modules are configured correctly and kept up to date.
We're based in Belgium and we run Odoo for Benelux clients every week. The Belgian and Dutch localizations are mature and well-maintained, the French one is solid, the Luxembourgish one needs the most attention. Each has specific gotchas that bite the projects that didn't plan for them.
This guide collects the Benelux-specific things we wish every client knew before kick-off — VAT codes, intracom reporting, e-invoicing (Peppol), CODA bank statements, payroll quirks, and the Belgian SAF-T / digital filing requirements that are tightening each year.
Belgium — VAT, intracom, CODA, Peppol
The Belgian localization installs the BE chart of accounts, VAT codes (21%, 12%, 6%, exempt), the intracommunity sales and purchases reports, the EC sales list, and CODA bank statement import. For most Belgian SMEs the standard module covers 90% of needs out of the box.
The 10% to plan for: e-invoicing via Peppol (mandatory for B2G, increasingly relevant for B2B), the SAF-T tax filing format, the fact that Belgian VAT periods can be monthly or quarterly depending on turnover, and certain industry specifics (construction co-contractor, etc.).
- Belgian localization installs chart of accounts, VAT codes, intracom reports, CODA
- Peppol e-invoicing — mandatory for B2G, increasingly for B2B, configure early
- SAF-T tax filing format becoming standard — Odoo modules support it
- VAT period monthly or quarterly depending on turnover — configure once
- Industry specifics (co-contractor, second-hand, intracom) need extra attention
Netherlands — RGS, BTW, OB Aangifte, SBR
The Dutch localization includes the RGS chart of accounts, the standard BTW codes, the OB Aangifte (VAT return) format, and integration with the Belastingdienst for filing. SBR (XBRL) reporting is supported via specific modules and partners.
Dutch specifics that catch projects out: the small businesses scheme (KOR), the requirement for digital invoices in some sectors, the e-Herkenning login for Belastingdienst access, and the increasingly strict rules on digital archiving of invoices for 7 years.
- Dutch localization includes RGS chart, BTW codes, OB Aangifte, SBR-ready
- Filing to Belastingdienst supported — sometimes via partner connector
- KOR (small business scheme) needs explicit configuration if applicable
- e-Herkenning required for Belastingdienst access — separate from Odoo setup
- Digital archiving of invoices 7 years — Odoo native, but verify backup strategy
France — PCG, FEC, Factur-X, e-invoicing reform
The French localization is mature: Plan Comptable Général, FEC (audit file) export, French VAT codes including the specific reverse charge cases, the deadline-driven CA3 / CA12 declaration formats. For French B2B, Factur-X and the rolling e-invoicing reform are the headline items.
The French e-invoicing reform mandates structured invoicing through PDP (Plateforme de Dématérialisation Partenaire) — Odoo supports it via certified partners. Plan the configuration months ahead of your phase-in date because the certification process and PDP onboarding take real time.
- French localization includes PCG, FEC, French VAT codes, CA3/CA12
- Factur-X (hybrid PDF + XML) supported natively
- E-invoicing reform via PDP partners — plan months ahead
- FEC export required for tax audits — Odoo generates the standard format
- Specific reverse charge and intracom cases need careful VAT mapping
Luxembourg — small but specific
Luxembourgish localization is the smallest of the four but covers the basics: chart of accounts, VAT codes, eCDF filing format. For internationally-active Luxembourgish companies (SOPARFI, holdings, fund administrators) additional configuration is usually needed for IFRS reporting and consolidation.
We always check three things for Luxembourgish projects: the eCDF filing setup, the multi-currency configuration (LU companies often work in EUR + USD + others), and the IFRS adjustments for entities reporting both LuxGAAP and IFRS. None of these are hard, but skipping them means manual reconciliation pain later.
- Luxembourgish localization covers chart, VAT, eCDF filing
- SOPARFI / holdings / fund admin entities need extra IFRS configuration
- Multi-currency setup important — many LU entities operate in 2-3 currencies
- eCDF filing format supported — verify before going live
- IFRS / LuxGAAP dual reporting needs explicit modelling — don't improvise
Cross-Benelux groups and the consolidation question
Many of our clients are groups with entities in 2-4 Benelux countries. Each entity needs its own localization, its own chart of accounts, its own VAT setup. Odoo supports this multi-company pattern natively, but the consolidation layer (group reporting, intercompany elimination) needs explicit configuration.
We use Odoo's multi-company module with shared partners, shared products, separate accounting. For consolidation, either Odoo's native consolidation module (sufficient for small groups) or a dedicated consolidation tool feeding from Odoo (for groups with statutory consolidation obligations).
- Multi-company native — each entity its own localization, chart, VAT
- Shared partners and products across companies — but separate accounting
- Intercompany flows (sales/purchases between group entities) automated via module
- Native consolidation module fits small groups; complex groups need dedicated tool
- Group reporting often needs custom dashboards on top of consolidation
Benelux localization mistakes we see most often
These are the patterns that produce filing problems and audit findings.
- Default chart of accounts not aligned to local statutory format — auditor sends it back.
- Peppol / e-invoicing not configured before mandate date — last-minute rush.
- VAT codes missing for specific cases (intracom triangle, reverse charge) — declarations wrong.
- Multi-company configured without shared masters — partner duplication, reporting nightmare.
- Localization module updates not applied — declarations break when authority changes a format.
Metrics that prove your Benelux localization is healthy
We track these monthly with finance. Issues here = compliance risk.
- VAT declaration filed on time, every period, with zero adjustments.
- Intracom sales / purchases reports match VAT return to the cent.
- Bank reconciliation (CODA / camt) clears 95%+ automatically.
- E-invoicing acceptance rate above 98% for B2B / B2G destinations.
- Localization module updates applied within 30 days of release.
How we configure Benelux localizations at Flydoo
Localization is the first thing we configure after the company setup. We pick the right module per entity, verify the chart of accounts against the local statutory format, configure VAT codes for the specific business cases, set up e-invoicing channels.
For Benelux groups we set up the multi-company structure early, with shared partners and products but per-entity accounting. Intercompany rules are configured during implementation, not after — retrofitting them is painful.
- Localization module per entity, picked before configuration starts
- Chart of accounts verified against local statutory format with the client's accountant
- VAT codes for industry-specific cases (intracom, reverse charge, second-hand) set up day 1
- E-invoicing (Peppol, PDP, etc.) configured ahead of mandate dates
- Multi-company structure and intercompany rules configured during implementation, not retrofitted
Practical checklist for a Benelux Odoo localization
Walk this list with finance and your accountant. Missing items = compliance risk.
- Right localization module installed for each legal entity
- Chart of accounts matches local statutory format and is reviewed by the accountant
- VAT codes configured for all your business cases (intracom, reverse charge, etc.)
- Bank statement format (CODA for BE, camt for NL/FR/LU) imports cleanly
- E-invoicing channels (Peppol, PDP) configured and tested with real partners
- Statutory reports (VAT, intracom, EC sales list) tested against legacy outputs
- For groups: multi-company structure with shared partners and per-entity accounting
- Localization update procedure: who applies updates, when, with what testing
Key takeaways
- Belgian, Dutch, French, Luxembourgish localizations all mature — but each has specifics
- Peppol (BE) and PDP (FR) e-invoicing rolling out — configure ahead of mandate dates
- Multi-entity Benelux groups: native multi-company plus shared masters works well
- Localization updates must be applied — formats and rules change yearly
- Industry-specific VAT cases (co-contractor, intracom triangle) need explicit setup
- Have your local accountant review the chart of accounts before go-live — non-negotiable
Frequently asked questions
Is Odoo's Belgian localization good enough for an Expert-Comptable?
Yes, in our experience. The Belgian module covers chart of accounts, VAT (including the cases that matter — intracom, reverse charge, second-hand), CODA imports and the standard reports. Most Belgian accountants we work with either use Odoo themselves or accept it for client work. The key is to have the accountant review the chart of accounts during configuration, not after the fact.
How does Odoo handle Peppol e-invoicing in Belgium?
Odoo natively supports Peppol invoice sending and receiving via the standard module from version 17 onwards. For B2G (mandatory) and B2B (rolling out), it works out of the box. We always test with real Peppol partners during implementation — sandbox tests aren't enough to catch real-world quirks.
What about the French e-invoicing reform with PDP partners?
France's e-invoicing reform requires structured invoicing through certified PDP partners. Odoo integrates with multiple certified PDPs through specific modules. Plan three to six months ahead of your mandated phase-in date because PDP onboarding includes contracts, technical setup and testing.
Can we run a Belgian + Dutch group on one Odoo database?
Yes, this is a very common pattern. Each entity gets its own localization, its own chart of accounts, its own VAT registration. Partners and products can be shared across companies. Intercompany sales/purchases are automated. For statutory consolidation we either use Odoo's native consolidation (small groups) or pipe to a dedicated tool (more complex groups).
How often do localization modules need updates?
Whenever the tax authority changes a format, rule or rate. For Belgian VAT this is roughly twice a year; for Peppol and SAF-T more often as the standards evolve. We monitor releases for our clients and apply updates within 30 days, with a quick test pass before going to production. Skipping updates is the fastest way to break a declaration.
Need help applying any of this to your own context? We're happy to talk.