Multi-Entity ERP for Belgium, the Netherlands and France — Odoo & ERP article by Rui Codex

Yes, a multi-entity ERP can serve Belgian, Dutch and French entities, provided the design separates legal entities, currencies, VAT registrations and languages from shared master data. A single instance with clear company codes suits groups with common processes, while separate instances fit groups whose processes or regulatory obligations diverge.

Key takeaways

  • A multi-entity ERP should model each legal entity as its own accounting unit, linked to the others through shared master data.
  • A single instance suits groups with common processes, while separate instances suit entities whose processes or systems cannot be aligned.
  • Decisions on currency, language and VAT registration shape the data model and are costly to change after go-live.
  • Personal data should be shared between entities only where a documented purpose requires it.
  • Intercompany pricing and the design checklist should be settled with named owners before the build begins.

How does a multi-entity ERP model Belgian, Dutch and French entities?

The direct answer is that each legal entity should be a separate accounting unit, linked to the others through shared master data for customers, products and suppliers. Each entity keeps its own ledgers, statutory reports and bank accounts, while the group works from one set of reference data.

In practice, the design starts with a mapping exercise. List every legal entity, the country it is registered in, the currency it trades in, the language of its invoices and the processes it runs. Entities that look similar on an organisation chart often differ in how they buy, price or invoice, and those differences decide the configuration.

Intercompany transactions need special attention. When the Belgian entity sells goods to the Dutch entity, the ERP should record both sides automatically, with matching intercompany accounts and a clear reconciliation rule at month end. Manual intercompany entries are a common source of mismatches that appear only at consolidation.

Tip: Agree intercompany pricing rules with finance before the build starts. The software can enforce a rule, but it cannot decide which rule the group should use.

Should you run one ERP instance or several?

A single shared instance is usually the right answer when the three countries run the same core processes and report to the same group finance team. Separate instances are the better choice when entities have different regulatory setups or processes that cannot be aligned without disrupting daily work.

When one shared instance works

A shared instance gives one product catalogue, one customer view and one consolidation path. Users move between entities without learning a new system, and reporting does not depend on exporting files between tools.

It fails when a local entity needs a process the rest of the group cannot accept. A local payroll rule or a specific invoice format can force configuration choices that complicate every other entity. Upgrades also become harder, because each local change must be tested against all entities.

When separate instances make sense

Separate instances isolate change. A Dutch entity can upgrade or alter its sales process without touching the Belgian books. This matters most for groups built through acquisitions that still run different systems in different countries.

The cost is integration. Every shared master record must be synchronised between instances, and every consolidation needs a maintained data pipeline. Without a clear owner for that pipeline, the instances can drift apart quickly.

Hybrid designs

Many groups settle in the middle, with shared finance and master data alongside local operational modules. This can work well, but only if the boundary is written down. Decide which module, data field and process belongs to the group and which belongs to the entity.

How do currency, language and VAT registration change the design?

These three settings change the data model more than most teams expect. Each entity needs a base currency, the ability to hold transactions in other currencies, and invoice documents in the language its customers expect. VAT registration determines which tax codes and returns the entity must produce.

Currency handling is mostly about where conversion happens and which rate is used. Decide whether transactions are stored in document currency and converted at posting, and agree which exchange-rate source the group uses. Changing this later means restating historical data.

VAT rules are set by national law within an EU framework, and the EU texts are published on EUR-Lex, the official EU law database. Rates, reporting and invoice requirements differ between Belgium, the Netherlands and France, and whether one legal entity needs separate registrations in each country is a question for the group's tax adviser rather than for the software configuration. This article is general information and not legal or tax advice. Build the tax codes only once the registration structure is confirmed.

Language affects documents and master data. Product descriptions, customer-facing invoices and standard messages may need Dutch or French versions, and those translations must be maintained over time. Decide early which texts are stored once and which are translated per entity.

Which data should be shared across entities and which should stay local?

Share reference data such as product codes, price lists and supplier records, and limit access to personal data to the entities and roles that need it. The more sensitive the data, the more it should stay local or be restricted by role. This decision also carries data protection consequences.

The GDPR applies across the EU, and its text is available on EUR-Lex. It requires that personal data is processed for specified purposes and limited to what is necessary, so a shared customer table that lets every entity see every contact needs a clear basis. Supervisory authorities publish guidance in their own languages, such as the Dutch Autoriteit Persoonsgegevens and the French CNIL, and that guidance should be checked when roles and access are defined.

Tip: Map each personal data field to a documented purpose and an owning entity before granting cross-entity access.

Hypothetical examples of multi-entity designs

Here are two hypothetical scenarios:

Scenario one: a manufacturer with shared products

Prefer a delivered project to a scenario? Read the case study: Netsis B2B Sales Platform.

Imagine a manufacturer with a Belgian production entity, a Dutch sales entity and a French distribution entity. Products, bills of materials and price lists are shared, while each entity keeps its own ledgers and tax returns. The design works because the core processes are common and the local differences sit mainly in tax and documents.

The risk is intercompany margin. If transfer prices are not agreed, the consolidated view can look correct while entity results mislead local managers. The fix is a documented pricing rule before go-live, not a more complex system.

Scenario two: a services group with divergent payroll

Imagine a services group whose French entity runs payroll and timekeeping under different rules from the Belgian and Dutch entities. A shared finance instance can still hold the general ledger, while payroll stays in a separate module that feeds totals through a controlled interface.

The lesson is to isolate the divergent process rather than force one configuration on everyone. Each interface then needs monitoring, error handling and a named owner.

Which checks should you complete before choosing a design?

Complete these checks before selecting a design, because most expensive rework comes from decisions made by default rather than on purpose. Each check should have an owner in finance and an owner in IT.

  • List every legal entity with its country, currency, language and tax registration status.
  • Document which master data is shared and who may change it.
  • Agree intercompany pricing and the reconciliation calendar.
  • Identify processes that differ by country and decide whether they are configured or isolated.
  • Define how access to personal data is restricted by entity and role.
  • Plan how upgrades will be tested across all entities.

Integration with other systems is the final check, because connections to e-commerce, banking and reporting tools must follow the chosen data ownership. Rui Codex offers technical implementation support for these connections through its ERP and CRM integration service, and related trade-offs are discussed in our article on ERP and CRM integration.

Frequently Asked Questions

Can one ERP instance handle Belgium, the Netherlands and France?

Yes, one ERP instance can handle entities in all three countries, provided each entity has its own legal and accounting setup inside the system. A shared instance works well when the countries run similar core processes and report to one group finance team. Local differences in tax, language and payroll must be configured without forcing changes on the other entities, so test the design against each country before go-live.

When should a multi-entity group split into separate ERP instances?

A group should consider separate instances when its entities run processes that cannot be aligned, or when one entity needs to change systems without affecting the others. Acquisitions that bring existing systems are a frequent reason. The trade-off is that shared master data and consolidation then need a maintained integration with a named owner, otherwise the instances drift apart.

Does one ERP mean one VAT registration for the group?

No, one ERP can hold several VAT registrations, and it is common to configure a separate tax code set for each country. Whether each legal entity needs its own registration depends on the tax rules of each country and on where the entity is established. That question should be settled with the group's tax adviser before the tax codes are built.

Which personal data should be shared across the entities?

Only personal data that a given entity needs for a documented purpose should be shared. Reference data such as products and price lists can usually be shared, while customer contacts, employee records and payroll data should be limited by entity and role. Check the GDPR text and the guidance of the national authority for each country where the data is processed.

Conclusion

A single ERP can serve Belgium, the Netherlands and France when the design keeps legal entities, currencies, VAT registrations and personal data clearly separated from shared reference data. Start with an entity map, then choose between one instance, separate instances or a documented hybrid. Rui Codex is led by a founder with 200+ projects delivered and 12+ years of hands-on experience, and published work is listed on the case studies page. To discuss your group structure, request a project consultation or email info@ruicodex.com.

Sources

Tags: multi-entity ERP ERP design Belgium ERP Netherlands ERP France ERP intercompany accounting VAT registration GDPR compliant software

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request