How a Multi-Country Infrastructure Group Evaluated One vs Two Production Environments in Dynamics 365 Business Central
At a Glance
| Company profile | Infrastructure developer with legal entities in India, Southeast Asia and Europe |
| Challenge | Run all entities on one Business Central platform, managed from India, while meeting each country’s tax rules |
| Question asked | “Can we use only Indian localisation and handle the other countries’ taxes outside the system?” |
| Options evaluated | One production environment (India localisation and external tax) vs two production environments (local localisation) |
| Recommendation | Two production environments: one India, one Group (W1 base with a partner localisation) |
| Key takeaway | Localisation is an environment-level decision, and the hardest one to reverse after go-live |
Table of Contents
- Summary
- The Situation
- How Localisation Actually Works in Business Central Online
- Option 1: One Production Environment with External Tax Calculation
- Option 2: Two Production Environments with Local Localisation
- Side-by-Side Comparison
- The Cost Question
- Our Recommendation
- A Checklist Before You Decide
- Conclusion
- Frequently Asked Questions
Summary
Most multi-country ERP conversations start with modules: finance, procurement, projects, consolidation. But for groups operating across several tax jurisdictions, one of the earliest decisions matters more than any module choice. Where will each company live, and which localisation will it use?
In Business Central online, that decision is easy to underestimate. It looks like a technical setup detail. In practice, it shapes your invoices, your tax returns, your intercompany design and your audit trail for as long as you run the system.
Recently, one of our prospect, an infrastructure developer with entities in India, Southeast Asia and Europe, asked us a direct question: “Our finance team sits in India. Can we run every company on Indian localisation and handle the other countries’ taxes outside the system?” This blog walks through how we evaluated that question and what we recommended.
The Situation
The prospect was moving off separate accounting systems (a different package for each entity) with manual consolidation. Their requirements were clear:
- Several legal entities, with a holding entity planned above them.
- Different functional currencies and financial years. India runs April–March, while the other entities run January–December.
- Different reporting standards: Ind AS, IFRS and SFRS.
- Two-level consolidation.
- One central finance team in India managing all entities.
- Local tax compliance in each country: GST and e-invoicing in India, VAT in Europe, and GST with mandatory e-invoicing in Southeast Asia once registered.
Running everything from India made Indian localisation feel like the natural default. The question was whether that default would hold up for the non-Indian entities.
How Localisation Actually Works in Business Central Online
Before comparing options, it helps to be clear on three points that often surprise finance teams.
Localisation is set per environment, not per company.
Every company inside a Business Central online environment uses that environment’s localisation. That covers the tax engine, statutory reports and country-specific fields. You can create a Singapore or Cyprus company inside an India environment, but it will behave like an Indian company.
Microsoft doesn’t localise every country.
Microsoft provides its own localisation for 21 countries, including India, Australia, New Zealand, the UK, the US and much of Western Europe. Many other markets, including Singapore and Cyprus, are served by partner localisation apps on AppSource, installed on Microsoft’s base version (W1).
Localisation is free, but environments aren’t.
Microsoft doesn’t charge for localisation itself. A tenant includes one production environment. Every additional production environment needs an add-on subscription.
Changing a company’s localisation after go-live means migrating it to a new environment, then re-testing and re-validating it. Getting this right at the design stage avoids expensive rework later.
Option 1: One Production Environment with External Tax Calculation
In this model, every company sits in a single environment on India localisation. Tax for the non-Indian entities is calculated in an external tool, and the amounts are brought into Business Central through an integration.
What it involves:
- Switching off India-specific GST/TDS behaviour for the non-Indian companies.
- Custom invoice and credit-note layouts without India tax fields.
- An extension to post externally calculated tax amounts, so document totals match the original invoice.
- An API integration with the external tax tool, plus middleware and error logging.
- A custom e-invoicing integration (for example, Peppol / InvoiceNow) when it becomes mandatory.
- One environment to administer.
- Simpler intercompany and consolidation, with no cross-environment setup.
- No additional production environment subscription.
- No partner localisation apps to license.
- Tax returns are prepared outside Business Central, so they don’t tie directly to the ledger.
- More custom code to build, test and maintain through every Microsoft update.
- Two systems to reconcile every period.
- E-invoicing depends on an access-point provider supporting a non-standard setup.
- Higher audit exposure, and costly to reverse later.
Option 2: Two Production Environments with Local Localisation
In this model, the Indian entity sits in an India environment on Microsoft’s India localisation. All other entities sit in a Group environment on the W1 base, with a partner localisation app where needed and standard VAT configuration for the European entity.
Intercompany and consolidation between the two environments use Business Central’s standard cross-environment features.
- Each country’s tax is calculated and posted in Business Central.
- Local returns and audit files tie directly to the ledger.
- Invoices follow each country’s format, with no foreign tax fields.
- E-invoicing is supported through standard partner apps.
- Less custom code and lower upgrade risk.
- The same user licence works across both environments, so central finance in India is unaffected.
- An additional production environment subscription.
- Partner localisation app subscriptions.
- Cross-environment intercompany needs experienced setup and testing.
- Two environments to administer (updates, sandboxes, permissions).
Side-by-Side Comparison
| Area | One Environment (India + external tax) | Two Environments (local localisation) |
|---|---|---|
| Production environments | 1 | 2 |
| Non-Indian tax | Calculated outside BC, amounts integrated | Calculated in BC |
| Local tax returns | Prepared outside BC | Generated from BC |
| Invoice compliance | Custom layouts | Standard local formats |
| E-invoicing | Custom integration | Partner app |
| Intercompany | Same environment (simpler) | Cross-environment (standard feature) |
| Custom development | Higher | Lower |
| Audit and upgrade risk | Medium–High | Low |
| Reversibility | Costly migration later | Already correct |
The Cost Question
At first glance, the single-environment option looks cheaper because it avoids the additional environment and the partner apps. When we estimated both options in full, the picture changed:
- Implementation effort was higher for the single-environment option. The tax integration, custom layouts and e-invoicing integration added more work than the cross-environment intercompany setup they replaced.
- Subscription costs were lower for the single-environment option, with no environment add-on or localisation app fees.
- Over three years, total cost was broadly similar. The difference was in risk: one option moves compliance into custom code and manual processes, the other keeps it inside standard functionality.
The question then stops being “which is cheaper?” and becomes “where do we want our compliance risk to sit?”
Our Recommendation
We recommended two production environments. The deciding factors were:
Compliance stays in the system.
Every return, audit file and invoice comes from the ledger.
E-invoicing is already on the way.
The Southeast Asian entity will need it as soon as it registers for GST, and building custom integrations for a mandatory process is a risk we didn’t want to add.
Long-term maintainability.
Less custom code means fewer surprises with each twice-yearly Microsoft update.
Central finance is still possible.
Users switch between environments with the same licence, so the India-based team can still run everything.
We also phased the rollout. Core finance, India compliance, intercompany and project cost tracking go live first. Partner localisation and e-invoicing follow when the entity registers for GST, so investment lines up with real business events.
A Checklist Before You Decide
Before you lock in your environment design, answer these five questions:
- Which countries need in-system tax returns or e-invoicing, now or within the next two years?
- Is there a Microsoft or partner localisation for each country, and can the partner apps coexist in one environment?
- How much intercompany and consolidation runs between entities in different countries?
- Who will maintain custom tax integrations after go-live, and through every Microsoft update?
- What would it cost to reverse the decision after you’re live?
If the answers point to growing compliance requirements, local localisation almost always pays for itself.
Conclusion
Running every company on one localisation can look simpler on paper, especially when finance is centralised in one country. But in Business Central online, localisation is an environment-level decision that shapes compliance, reporting and maintainability for years.
For this prospect, two production environments gave a cleaner, more compliant and more scalable foundation, without losing the benefit of a central finance team.
I hope you found this blog useful. If you’re planning a multi-country Business Central rollout and want to talk through your environment design, feel free to reach out to us at transform@cloudfronts.com.
Frequently Asked Questions
1. Can I create companies for different countries in one Business Central environment?
Yes, but they all use that environment’s localisation. A Singapore company in an India environment will use India’s tax engine and reports.
2. Does Microsoft charge for localisation?
No. Localisation is free. An additional production environment needs an add-on subscription.
3. Does Microsoft provide localisation for Singapore and Cyprus?
No. Both are served by partner localisation apps on the W1 base version.
4. Do users need separate licences for each environment?
No. A user licence works across all environments and companies in the tenant.
5. Can intercompany work across two environments?
Yes. Business Central supports cross-environment intercompany as a standard feature, secured through an Entra ID app registration.
6. Can we calculate tax outside Business Central and bring in the amounts?
Yes, through an integration, but returns and compliance then sit outside the system. It adds custom code and reconciliation effort.
7. Can we start with one environment and move later?
You can, but moving a live company to a new environment means data migration and re-testing. It’s usually cheaper to design it right from the start.
8. How many sandboxes do we get?
Typically three sandbox environments are included with a tenant, enough for testing and UAT in both environments.
About the Author
Related posts:
How an Australian Linen Company Made Quote Approvals Secure with One Time Links in Dynamics 365
Recovering Lost Approval History After a Purchase Order Deletion in Business Central
How an Abu Dhabi-Based Diversified Holding Company Simplified Intercompany Transactions in Dynamics ...
