
Do your accountants switch between three logins before lunch? Does every month-end start with a spreadsheet called “IC recon final v7”? And when the board asks for group numbers, does someone quietly add up four trial balances by hand? If so, your group has outgrown one-company thinking. Dynamics 365 Finance multi-entity setup is Microsoft’s answer: many companies, one system, one close.
But is it right for you? Instead of a sales pitch, this guide starts with a quick self-check. After that, it explains the model in plain words, shows what changes for each role, and gives you Microsoft’s list prices and a realistic project path.
Key takeaways
- If your companies need their own currency, tax rules or fiscal year, each one becomes a legal entity in Dynamics 365 Finance, all inside one system.
- Also, intercompany journals, centralized payments and consolidation are built into Finance, so the group close needs far less re-keying.
- Licences are per user (Microsoft lists Finance at $210 per user/month, paid yearly); the timeline grows with the number of entities, countries and data sources.
The 60-second self-check
Answer these six quick questions. Then simply count your “yes” answers.
- Do you run two or more companies that each file their own VAT return?
- Also, do some companies keep their books in a different currency, such as AED, SAR or OMR?
- Do group companies sell to, buy from or recharge costs to each other every month?
- In addition, does one team pay suppliers or collect from customers on behalf of other companies?
- Similarly, do you build consolidated statements in Excel today?
- Finally, do you expect to add a new company or country in the next few years?
How to read it: mostly “yes” means a multi-entity design is worth a serious look. Mostly “no” means a single company with departments or cost centers may be enough for now.
What is Dynamics 365 Finance multi-entity, in plain words?
Picture one office tower. For example, each floor is a different company, with its own door, keys and electricity bill. Yet, at the same time, everyone shares the lift, the security desk and the building manager. Similarly, in Dynamics 365 Finance each company is a legal entity with its own ledger, accounting currency, fiscal calendar and module settings. Meanwhile, users, products and most HR data are shared across the whole building.
However, not every branch needs its own floor. Microsoft separates legal entities from operating units, such as departments and cost centers, which live inside a legal entity. So, the first design question is simple: legal entity or operating unit?
| Question | Legal entity if… | Operating unit if… |
|---|---|---|
| Currency | It needs its own functional currency | It shares the parent’s currency |
| Tax | It follows another country’s tax rules | It uses the parent’s tax setup |
| Fiscal year | It has its own fiscal calendar | It shares the parent’s calendar |
| Statements | It needs its own balance sheet | Income statements by unit are enough |
| Intercompany | It trades by sales and purchase orders | Journal recharges are enough |

Five desks, five wins
CFO
Opens consolidated reports and then drills into the original entry in any company.
Group controller
Uses due-to and due-from accounts, plus elimination rules, instead of manual matching.
Entity accountant
As a result, receives intercompany journals automatically instead of re-typing them.
Treasury
Instead, pays and collects for several companies from one legal entity, with one view of overdue invoices.
IT admin
Manages one set of users and roles. Also, company data is secured by company ID without customization.
One system, many rulebooks: Dynamics 365 Finance multi-entity in the GCC
For example, a typical GCC group might hold a mainland company, a free zone company and a sister company in Riyadh or Muscat. In Dynamics 365 Finance, each legal entity belongs to one country or region, and the country of its primary address switches on that country’s local features. For instance, a UAE company is activated by setting its address country to ARE.
As a result, Microsoft’s UAE localization covers VAT setup and reporting, the FTA Tax Audit File and an invoice printout in the FTA layout. Also, because functional currency is set per legal entity, AED, SAR and OMR books sit side by side. Finally, Microsoft Learn keeps separate localization pages for other GCC countries, so check each one during scoping.
The month-end loop, step by step
- Model the entities. First, the IT admin and controller create one legal entity per company and group them in organization hierarchies. Since version 10.0.47, the multi-company processing purpose is on by default, so users can select several companies from a parent-child list for jobs such as currency revaluation.
- Share the chart of accounts. Next, the controller links each ledger to one shared chart of accounts and dimensions, where possible.
- Post intercompany entries. Then accountants post one journal that lands in both companies, using pre-defined company pairs and due-to/due-from accounts.
- Pay centrally. After that, treasury pays or collects on behalf of other companies, and the system books the intercompany balances.
- File local VAT. Meanwhile, each company settles and reports VAT under its own country setup.
- Consolidate and eliminate. Next, the controller consolidates into a consolidation company, translates currencies and posts eliminations.
- Report to the group. Finally, the CFO reviews consolidated statements, with drill-back to the source transaction. Then the loop starts again next month.

The price tag: Dynamics 365 Finance multi-entity licences
Good news first: intercompany accounting, centralized payments and consolidation come with Dynamics 365 Finance. Therefore, licence cost follows your users and their roles. Below are Microsoft’s list prices.
| Licence | Typically for | Microsoft list price | Notes |
|---|---|---|---|
| Dynamics 365 Finance | Controllers, accountants, treasury | $210 per user/month, paid yearly | Copilot Credits not included |
| Dynamics 365 Finance Premium | Teams wanting planning and AI agents | $300 per user/month, paid yearly | 1,000 Copilot Credits per user/month |
| Attach licences | Users who need a second app | Typically $20 or $30 per user/month | Needs a qualifying base licence |
| Team Members / Operations – Activity | Light or read-mostly users | Not shown on the pages checked | Ask for a quote |
Your cost checklist. Beyond licences, budget for these:
- ☐ Roles per user: Microsoft licenses named users, and one “write” permission can move a light user into a higher tier.
- ☐ Minimum purchase: Microsoft’s licensing guidance points to the Product Terms for minimums, so confirm them early.
- ☐ Entities and countries: each one adds setup, local tax work and, of course, testing.
- ☐ Data migration: in particular, opening balances, open items and masters from several old systems.
- ☐ Training and support: similarly, each role learns its own part of the close.
How long does Dynamics 365 Finance multi-entity take?
In short, it depends on scope. For example, two companies in one country is a much smaller project than six companies in three countries. That is why Mohila works in clear phases and fixes the timeline after the free consultation.
| Phase | Multi-entity focus | Who |
|---|---|---|
| Scoping | Companies, countries, currencies, shared processes | CFO, controller |
| Design | Entities vs units, chart of accounts, hierarchies | Controller, partner |
| Configuration | Entities, intercompany pairs, payments, local tax | Partner, IT admin |
| Data migration | Balances, open items and masters per entity | Accountants, partner |
| Testing | A full test close, consolidation included | All roles |
| Training | Role-based sessions | Key users |
| Go-live | Cutover and support for the first real close | Everyone |
✅ Speeds it up
- One shared chart of accounts
- Clean customer and vendor masters
- One decision-maker for design
⚠️ Slows it down
- A different chart in every company
- Many custom reports
- Changing the entity structure late
Design the entity structure first: Microsoft notes that a legal entity ID can’t be changed once it’s saved.
Illustrative example: a close, day by day
This is an illustrative scenario, not a client story. Imagine a distribution group with a Dubai head office, a Riyadh sales company and a Muscat company. So, here is how its month-end could run.
- Day 1: Dubai posts the shared IT recharge as one intercompany journal. As a result, Riyadh and Muscat see their side at once.
- Day 2: Treasury runs one vendor payment proposal from Dubai that settles invoices in all three companies.
- Day 3: Meanwhile, each accountant reviews VAT under their own country setup.
- Day 4: Next, the controller runs consolidation and posts eliminations in a separate elimination company.
- Day 5: Finally, the CFO opens the group report and, when a figure looks odd, drills into the Riyadh entry behind it.
7 rules for a clean Dynamics 365 Finance multi-entity setup
- Decide entity vs unit before anything else. For this, use the questions in the table above.
- Don’t add entities just for reporting. For separate balance sheets only, Microsoft suggests a balancing financial dimension instead.
- Keep intercompany accounts dedicated. For instance, unique due-to and due-from accounts per company, or a trading partner dimension, make reconciliation easier.
- Set up both directions. If either company can start a transaction, also create the reciprocal relationship.
- Use a separate elimination company. You can’t post daily journals in a consolidation company, but you can in an elimination company.
- Align setups for central payments. For example, give a vendor the same address book ID in every company, and match posting profiles and payment methods.
- Guard the hierarchy. In addition, limit who can change it in production, and test restructures in draft mode with effective dates.
How Mohila can help
Mohila is a Microsoft partner that implements and supports Dynamics 365 Finance and Operations for groups in the UAE and across the GCC. In addition, our implementation approach follows clear phases from scoping to go-live. Not sure Finance is the right size for you? Compare it first in Business Central vs Finance and Operations.
Talk to an Expert
Bring your self-check answers to a free 1-hour consultation and map your group structure with a certified consultant.
Frequently asked questions
Not necessarily. What matters is how many companies need their own currency, tax rules, fiscal year or balance sheet. If none do, a single legal entity with departments or cost centers may be enough. The self-check in this article is a quick first test.
Multi-company features come with Dynamics 365 Finance, so cost follows users. Microsoft lists Finance at $210 per user/month and Finance Premium at $300 per user/month, both paid yearly (as listed on 15 November 2026). Local pricing, VAT and partner services are extra, and setup effort grows with each entity and country.
It depends on how many companies, countries and data sources are in scope. The project moves through scoping, design, configuration, data migration, testing, training and go-live, and Mohila confirms the timeline after a free consultation.
Yes. Each legal entity belongs to one country or region, and its primary address decides which local features it uses. So a UAE company and a Saudi company can run side by side, each with its own tax setup and currency.
With the Consolidations module, Finance consolidates into a separate legal entity. Alternatively, Financial reporting can consolidate during report generation. Many groups use one or both, depending on their needs and their auditors.
Sources
- Plan your organizational hierarchy – Microsoft Learn
- Define the organizational structure in Dynamics 365 – Microsoft Learn
- Intercompany accounting setup – Microsoft Learn
- Set up centralized payments – Microsoft Learn
- Financial consolidations and currency translation overview – Microsoft Learn
- United Arab Emirates (UAE) overview – Microsoft Learn
- Dynamics 365 Finance pricing – Microsoft
- Dynamics 365 licensing guidance – Microsoft




