Discover
Process workshops, data audit, and a fit-gap against the standard product.
Phase 1 · Awareness
Enterprise architecture and ecosystem integration
Multi-country and multi-entity rollout: a playbook for cross-border Dynamics 365
How to manage cross-border compliance, localised tax, multi-currency reporting and a multi-tenant Azure estate from one global template.
The short answer
Design the core once, prove it on a pilot entity, and let each country add a documented local layer. A new country should be a configuration and a mapping, not a new build.
Stages
From pilot entity to the Nth country
-
1
Define the global core Chart, dimensions, processes, security and the rules for what a country may change.
-
2
Prove it on a pilot Run the core in one entity through a real close before anyone copies it.
-
3
List the local layer Tax, e-invoicing, statutory reports, banks and payroll, each with its cost at update time.
-
4
Roll out Deploy to the next entity from the template, localising only where the law requires.
-
5
Govern change A country asks for a change to the core through one forum with one approver.
Decision points
Three questions that change the answer
Is the requirement the law, or a preference?
YesBuild it in the local layer, with a named owner.
NoUse the global process. Reject the exception.
Will another country need the same thing?
YesRaise it to the core and design it once.
NoKeep it local and register its update cost.
Does the group need one view?
YesAlign dimensions and reporting currency in the core.
NoReport locally, and consolidate with a documented mapping.
Milestones
What done looks like, and when
- Month 0 to 3 Global design signed off by group finance.
- Month 4 to 8 Pilot entity live and closed.
- Each rollout Entity live in a repeatable cycle, local gaps documented.
- Yearly Template reviewed against what countries proved wrong.
Principles we hold to
- One chart, one set of dimensions, many statutory books.
- Local needs are extensions with a cost, not exceptions.
- The template changes only where a country proved the core wrong.
- Tax and e-invoicing live inside posting.
Frequently asked questions
How do you manage tax in a multi-country Dynamics 365 rollout?
Tax is configured in the ledger by country and kept inside posting, with e-invoicing in the local layer, so a tax change is a configuration change.
Do we need a separate tenant per country?
Not by default. The decision depends on data residency, identity and who administers each environment. We make it explicitly at design time.
Related
Multi-country deployments: one template →
Multi-country blueprint →
Dynamics 365 ERP project types →
Take this to your own programme.
Tell us where you are. We will tell you plainly what this means for your estate and what we would do first.
Book a consultation
Next: Microsoft Fabric and Dynamics 365: operational analytics without ETL pipelines →
How an engagement runs
01
02
03
04
It starts with a 45-minute consultation, then a discovery and fit-gap workshop on your own processes. You receive a written fit-gap and a phased plan before a programme is agreed. Four phases follow, each with something you can use and review.
Design
Solution blueprint, integration map, and the extensions we will actually need.
Deploy
Configuration, migration rehearsal, role-based training, UAT and phased cutover.
Support
Hypercare, managed services, client portal, scheduled optimisation reviews.
What drives the cost: users, legal entities and currencies, integrations, data migration and the gaps found against standard. See how pricing works, run the three-minute readiness score, or book a consultation.