The entity count nobody chose.
A privately held hospitality group runs more than ten operating entities alongside a separately licensed affiliate. Licensing, not finance, sets that number, and every system bought afterward is priced per company. Multi-Entity Management for Microsoft Dynamics 365 Business Central unifies these as one company, with entities kept distinct as a dimension.
10+
operating entities in the hospitality division alone.
2
generations of ERP running during the migration.
1
unified division with Multi-Entity Management.
This privately held group operates multiple consumer-facing hospitality properties, alongside a separately licensed affiliate. Both sides are entangled: corporate services serve both, management fees run between them, and inventory is expected to move across.
But they can't be the same legal entity. Licensing fixes the boundary, and finance has no authority to redraw it.
As a result, the hospitality division alone runs more than ten operating entities, each a distinct legal and tax identity. Every application the group buys is priced and configured per company.
An operating license attaches to a specific legal entity.
The license defines what that entity is permitted to do.
The boundary can’t be redrawn for accounting convenience.
Most groups keep that separation in their systems, not just on paper.
The entity count becomes a multiplier on every system the group buys, repeated with each acquisition.

|
|
The solution |
Entities are defined once and carried on a global dimension, so connected systems such as spend management, procurement and reporting need only one company and one configuration. A new entity does not require a new subscription. Each entity keeps its own identity where that matters, with its own document number series where wanted, or the platform default where not.
Every document carries a header entity and line entities. Where they differ, due-to and due-from entries are generated automatically from a configured account mapping, so the failure behind an unbalanced month-end is removed. Entity hierarchies add trading rules on top: postings can be suppressed between a parent and what is effectively its division, and routed through the parent for entities outside that branch.
Allocation templates split a single transaction across entities by percentage, fixed amount, or variable amount, and a split can be overridden on one line without changing the template. Corporate purchases are coded once and land where they belong.
Standard financial reports are replaced with entity-aware equivalents, so a single dataset produces a balance sheet per entity, per group of entities, and consolidated with eliminations, with nothing exported. The elimination journal posts and then reverses itself the following day, without anyone having to remember to go back.
Access and master records follow the entity structure. Users see only the entities their role covers, from a single venue up to the whole group, and a vendor or customer is visible only to the entities that trade with it. Licensing separation becomes something the system automatically enforces.
| + | Compare |
| Requirement | Standard BC | With Multi-Entity Management |
|---|---|---|
| Intercompany balancing | Possible by dimension, but due-to/due-from entries aren’t generated automatically. | Due-to/due-from entries are injected automatically at posting — configured once. |
| Entity-level security | Achievable, but requires extensive customization. | Governed directly by the entity dimension. A user with rights to three entities sees only those three. |
| Master data control | Any user can select any vendor, customer, or GL account, regardless of entity. | Per-entity allow lists. Ineligible vendors don’t appear in the lookup at all. |
| Entity-specific setup | No native concept of entity-level settings. | Each entity carries its own bank account, document numbering, and configuration. |
| Eliminations | Handled downstream in the reporting layer. | Calculated automatically, reviewable before posting, and reverse on a defined date. |
| Cross-entity documents | Manual creation of the matching document in the other company. | Entities transact as virtual customers/vendors of each other; the companion document is created automatically. |
| Reporting | Build it yourself. | Any report can run per-entity or across entities in real time, including consolidated views and FP&A extraction. |