International accounting with Odoo: one group, multiple countries (and sometimes a Chinese ledger alongside)

As soon as a growing company gets an entity abroad - a purchasing office in China, a sales point in Germany, an entity in the US - the same question comes up: does that country’s accounting also run in Odoo, or do you keep it local and connect it to the group? The answer is not “everything in one system” and not “a separate package everywhere”, but a deliberate choice per country. This is the honest trade-off, with the Chinese ledger as a sharp example.

The question behind the question

“Can Odoo handle international accounting?” is quickly answered technically: yes. Odoo runs multiple entities as multi-company, in multiple currencies and languages, with consolidated reporting, and has fiscal localisation packages for dozens of countries. But that is not where the real decision sits.

The real question is: which country ledger do you put in Odoo, and which do you keep local and connect? That is not a technical but a strategic choice, and the answer differs per country, depending on regulation, the local accountant, the language and practice.

Two models

There are roughly two ways to organise international accounting with Odoo.

Model 1: everything in Odoo, with fiscal localisation per country. You run each entity in Odoo and install the fiscal localisation package per country: the chart of accounts, the taxes and the fiscal positions. This is the cleanest setup: one system, one data model, direct consolidation. It fits countries with a localisation Odoo covers well and where there is no heavy local requirement to book in other software or with a local party.

Model 2: local accounting local, connected to the group. For some countries it is wiser to keep the accounting local - with an external firm or in local software - because the law, the language or practice call for it. Odoo then remains the group system for the operation (purchasing, sales, inventory, projects) and for consolidation, and the local ledger is connected: via periodic journal entries, a subset of data, or a daily import.

The art is not to choose one dogmatically, but to determine the right one per entity.

China: where the choice is sharpest

China is often portrayed as “cannot be done in Odoo”. That is not true. Odoo has a Chinese fiscal localisation (chart of accounts and taxes), and the community (OCA) offers additional modules, including for fapiao (Chinese invoicing). China is therefore not an exception where Odoo stops - it is precisely the sharpest example of the choice between the two models.

The trade-off comes down to two questions:

• Do you have your own accounting capacity in China? If so - an own accountant or finance team on the ground - keeping the Chinese ledger in Odoo is often the best choice: one system, direct consolidation, no separate package alongside. The localisation plus any OCA or partner modules cover the chart of accounts and the invoicing.
• Do you work with an external local firm, or do you have very specific statutory requirements? Think of certain parts around the Golden Tax System or filings you would rather leave to a local specialist. Then it can be wiser to keep the accounting local and connect it to the group.

So there is no default answer “China = connect”. The operation (orders, purchasing, margins, stock flows) belongs in Odoo regardless; for the accounting you test whether the localisation covers your specific requirements and whether you have the capacity on the ground - and then deliberately choose between booking in Odoo or keeping it local and connecting. We saw exactly this kind of scenario recently at a sourcing and import company with entities in China and Hong Kong.

Bank connections: be honest across the border

A concrete point that often comes up too late: bank connections do not work the same everywhere. For European banks an automatic connection in Odoo is standard. For banks outside the EU - for example in China or Hong Kong - that is not a given. The honest approach: test it per bank before you promise anything. If it cannot be automatic, a daily or periodic bank import is the real alternative. That is not a shortcoming, but a choice you make deliberately instead of being surprised by it.

Where the data runs matters

Connecting accounting across countries also touches the question of where your system runs and who can reach it. If a large part of your team sits in a country with limited access to certain cloud services, the hosting location (for example Singapore versus Europe) becomes a real trade-off. We work that choice out in the hosting guide, and the broader international approach in Odoo for international rollouts.

What you need in Odoo

For full international accounting you lean on the heavier side of Odoo:

• Full accounting (bank reconciliation, assets, tax reporting) - that is the Enterprise functionality, see Odoo Community vs Enterprise.
• Multi-company with intercompany transactions and consolidated reporting.
• Fiscal localisation packages per country where you book in Odoo.
• Multiple currencies and languages in a coherent whole.
• Interfaces for the entities that stay local: journal entries, subset sync or import.

The honest nuance

Not every foreign ledger belongs in Odoo, and not every one belongs outside it. For a German or Belgian entity with a good localisation, model 1 (everything in Odoo) is often fine. For a Chinese entity it can go either way: with own accountants and a covering localisation, booking in Odoo is excellent; if you lean on an external local firm or specific statutory requirements, keeping it local and connecting is wiser. The mistake is not one model or the other, but not choosing deliberately - and then discovering afterwards that you forced a local tax requirement into a system not meant for it, or that you are missing a group view.

How to approach it

1. Map the entities. Per country: which tax requirements, which accountant, which language, which bank.
2. Determine the model per entity. Book in Odoo (with localisation) or keep local and connect.
3. Test the bank connections per bank, with import as a fallback.
4. Design the consolidation at group level, with intercompany and elimination.
5. Weigh the hosting location if part of your team has limited cloud access.

In short

International accounting with Odoo is not a technical but an architecture question: which country ledger do you put in Odoo, and which do you keep local and connect to the group? Odoo delivers the multi-company, the localisations and the consolidation; the art is to choose the right setup per entity. China is not a wall but the sharpest example of that choice: with own accountants and a covering localisation, booking in Odoo is excellent; otherwise a group system with a connected local ledger is the honest answer - one view, without forcing the local requirements.

Do you have a foreign entity and are unsure about the setup? Schedule a no-obligation Quickscan and we will map your entities, your tax requirements and the best connection strategy.

Read more: Odoo for international rollouts · Odoo for procurement, sourcing and import companies · Odoo hosting and data residency international · Odoo Community vs Enterprise · What does an Odoo implementation cost?