Deploying Odoo Internationally: Fiscal Localization, Subsidiary vs Branch, and Multi-Currency

An SMB or mid-sized company structuring its business across several countries — the Gulf, Asia, Europe — rarely asks the question in the right order. The question isn't just "does Odoo handle multi-currency?" but at what level local tax compliance is decided, and at what point that choice becomes irreversible. Here is what Odoo's official documentation (odoo.com/documentation) says on the topic.

The base principle: one company = one fiscal localization module

In Odoo, each company can use a different fiscal localization module. The module matching the company's registered country installs automatically when the relevant applications are launched. It remains possible to manually select a different localization module from Accounting → Configuration → Settings — but the official documentation is explicit about the limit: this change is only possible as long as no accounting entry has been posted for that company.

Subsidiary or branch: a distinction with a direct accounting impact

Odoo distinguishes two ways of representing a foreign entity within its multi-company structure. A standalone company can have its own fiscal localization, independent from the other entities in the group. A branch, on the other hand, must follow its parent company's localization settings — the documentation explicitly recommends creating separate companies rather than branches once multiple countries are involved.

In practice: if a subsidiary based in the UAE or Egypt must comply with local tax rules different from a French or Belgian head office, it must be configured as a separate company in Odoo — not as a branch, or it will inherit the head office's localization.

60+ officially documented fiscal localizations

• ✓Europe: Belgium, Switzerland, France, Germany, Spain, Italy, Netherlands, Luxembourg, Austria, Poland, Romania, Croatia, Denmark, Hungary, United Kingdom
• ✓Gulf and Middle East: Saudi Arabia, United Arab Emirates, Egypt, Jordan, Oman
• ✓Asia-Pacific: Hong Kong, India, Singapore, Malaysia, Indonesia, Vietnam, Thailand, Taiwan, Australia, New Zealand, Philippines
• ✓Americas: Canada, Mexico, Brazil, Argentina, Chile, Colombia, Peru, Ecuador, Dominican Republic, Guatemala, Uruguay
• ✓Africa: Kenya, Uzbekistan (Central Asia, grouped by Odoo under the same documentation block)

The documentation notes that this list keeps expanding with each version — a country missing from this list today may be added tomorrow, so the exact module available for a given country should be checked before committing to a rollout timeline.

Multi-currency: what's natively handled in accounting

The accounting module includes a multi-currency system built for international transactions, allowing invoicing, collection, and consolidation across several currencies within a single Odoo environment. Combined with the multi-company structure, this lets a group operate one company per currency zone while keeping a consolidated view.

The point to lock down before go-live, not after

The real project risk isn't technical, it's organizational: deciding late that an entity needs a different fiscal localization after the first accounting entries have already been posted means starting that company's setup over from scratch, per Odoo's own documentation rules. For any multi-country rollout, the structure (company vs. branch) and the fiscal localization of each entity must be validated before the first accounting data import — not adjusted along the way.

For support structuring a multi-company setup for an international Odoo rollout, see our offering at /odoo/services.