Run UAE VAT and India GST in one Odoo database

A group with a Dubai entity and an India entity has a problem most Odoo guides skip: you are running two completely different tax regimes inside one system. The UAE side wants flat 5 percent VAT and a simple return. The India side wants multi-rate GST, HSN codes, place-of-supply rules, and e-invoicing. Put both in one Odoo database the wrong way and every month-end becomes a reconciliation fight between two countries' books. Set it up right and the same database files clean VAT in Dubai and clean GST in India while giving you one consolidated view of the group.

This is the structure that makes that work. It is not a generic multi-company walkthrough - the established Odoo multi-company setup best practices cover the basics. This is specifically about the two-country tax problem, where a UAE and an India entity share one Odoo instance and neither filing is allowed to break.

One database, separate companies - and why

The instinct to merge everything into one company to keep it simple is the mistake that costs you later. Each legal entity is a separate Odoo company inside the shared database. That separation is what lets each one carry its own:

• Chart of accounts and fiscal localization. The UAE company runs the UAE localization; the India company runs the Indian localization with GST. These are different account structures and different tax logic, and they must not be forced into one chart.
• Tax configuration. UAE VAT at 5 percent with standard, zero-rated, and exempt treatments on one side; Indian CGST, SGST, and IGST at multiple rates on the other. Defined per company, never shared.
• Currency. AED as the company currency for the UAE entity, INR for the India entity, with the group consolidating to a chosen presentation currency.
• Sequences and compliance documents. Separate invoice sequences and the country-specific document formats each tax authority expects, including India e-invoicing where it applies.

The shared database still gives you the prize: consolidated reporting, shared partners and products where it makes sense, and one login for the finance team. You get the group view without collapsing two tax regimes into one broken chart.

The tax setup that keeps both filings clean

Tax is where a two-country Odoo build is won or lost. Configure each company's taxes against its own fiscal localization, not by hand-rolling tax codes. For the UAE entity, that means the standard 5 percent VAT with correct handling of zero-rated exports and exempt supplies, mapped to the right boxes of the VAT return. For the India entity, it means CGST and SGST for intra-state, IGST for inter-state, HSN codes on products, and place-of-supply logic that picks the right tax automatically - the kind of automation our GST tax compliance automation work is built around.

The detail that catches teams out is fiscal positions. A fiscal position in Odoo remaps taxes and accounts based on the customer or vendor - domestic versus export, registered versus unregistered. Get the fiscal positions right per company and the correct tax is applied without anyone remembering to pick it. Get them wrong and you discover the error at filing time, on entries already posted, across two jurisdictions. That retro-fix is the single most expensive mistake in a two-country setup, which is why it belongs in the implementation plan, not in month three.

Inter-company transactions across the border

The moment your UAE entity buys from or sells to your India entity, you have a cross-border inter-company transaction that has to land correctly in both sets of books. Odoo can automate the matching document - a sale in one company creating the corresponding purchase in the other - but the tax treatment is yours to get right. A supply from the India entity to the UAE entity is an export on the India side, with its own GST treatment, and an import on the UAE side. If both legs are not configured deliberately, your GST return and your VAT return will tell two different stories about the same transaction, and reconciliation becomes a manual hunt every month.

The principle is consistency: one economic event, two correct postings, automatically. That is harder across two tax regimes than within one country, and it is the part of a UAE-India build that most rewards getting an experienced partner involved early rather than discovering the gaps at the first cross-border invoice.

Access, reporting, and what to plan for

With the structure in place, two operational details finish the job. First, access rights: finance staff should see only the companies they are responsible for, while group controllers see the consolidated picture. Odoo's multi-company access rules handle this, and they matter for audit as much as for tidiness. Second, consolidated reporting: with separate companies done correctly, group-level profit and loss and balance sheet roll up cleanly in the presentation currency, and each entity still produces its own statutory reports for its own authority.

If you are still scoping the project, two things help: a realistic cost picture, which our guide to Odoo implementation cost in Dubai by module sets out, and a clear view of how to choose a multi-company approach, covered in selecting multi-company management software for Dubai. When you are ready to build, our Odoo ERP implementation team handles the cross-border tax and inter-company configuration, and the India-side work is the same discipline behind our Odoo implementation services in India.

FAQ

Can one Odoo database handle both UAE VAT and India GST?

Yes, as long as each legal entity is a separate Odoo company with its own fiscal localization. The UAE company runs 5 percent VAT, the India company runs multi-rate GST with HSN and e-invoicing, and the shared database consolidates the group. The mistake is merging both into one company and one chart of accounts.

How do inter-company transactions between UAE and India work in Odoo?

Odoo can auto-create the matching document so a sale in one company becomes a purchase in the other, but you must configure the cross-border tax treatment on both legs - an export on the India side and an import on the UAE side. If only one leg is set up, the VAT and GST returns will disagree on the same transaction.

What is the most common multi-company tax mistake?

Wrong or missing fiscal positions, discovered at filing time on entries that are already posted. Across two tax regimes the cleanup is expensive because it touches both countries' books. Getting fiscal localization and fiscal positions right at go-live is far cheaper than retro-fixing them later.

Do we need separate currencies for each company?

Yes. The UAE entity should run in AED and the India entity in INR as their company currencies, with the group consolidating to a chosen presentation currency. Forcing both into one currency distorts each entity's statutory reporting and complicates reconciliation against the local tax authority.

The takeaway: a UAE and India group in one Odoo database is not about cramming two countries into one company - it is about keeping them as separate companies that share a database. Give each its own localization, tax setup, and currency, drive tax from fiscal positions, configure both legs of every cross-border transaction, and get it right at go-live. Do that and one system files clean VAT in Dubai, clean GST in India, and shows you the whole group at a glance.