Binary Stream logo

Multi-entity accounting for hospitality groups.

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.

THE STRUCTURE

Why licensing, not finance, sets the entity count.

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.

Why license-bound groups face this.
01

An operating license attaches to a specific legal entity.

02

The license defines what that entity is permitted to do.

03

The boundary can’t be redrawn for accounting convenience.

04

Most groups keep that separation in their systems, not just on paper.

The result

The entity count becomes a multiplier on every system the group buys, repeated with each acquisition.

The legalities mean we can’t just consolidate that. That would be my ideal—that we have one instance that we deal with, but we can’t.

Chief Information Officer, privately held hospitality group.
Multi-entity accounting for hospitality & franchising
THE CHALLENGES

Five things finance was absorbing by hand.

01

A per-entity price on a fixed entity count.

The group’s spend-management platform was already live, connected to another of its ERP tenants that held a single company. Extending it to a tenant with more than ten companies left the vendor offering three options, and no good one.
  • Separate instance per entity → A subscription for every entity, and every new one.
  • Keep exporting files → Manual imports with no audit trail.
  • Reshape the ERP as one company → Lose the entity separation licensing requires.
02

Intercompany postings that rely on someone remembering.

Without an entity layer, every transaction that crosses an entity boundary needs its due-to and due-from entries created by hand. This means a month-end where the books don’t balance and nobody can say which entry was missed. The industry-specific ERP being replaced handled this well, and moving to a general-purpose platform meant losing that discipline unless something replaced it.
03

Shared spend booked where it’s convenient.

Corporate functions buy on behalf of the whole group, so two kinds of inter-entity transaction come up constantly:
  • Group purchases coded to whichever entity is easiest to transact through, then billed back later.
  • Purchases that genuinely serve two businesses at once and have to be split between them.
Both are real accounting events, but both were being handled as administrative follow-up.
04

Reports that treat one company as one business.

Business Central’s standard reports add up everything in a company and present a single result. That doesn't work for a company that deliberately holds separate entities. Finance needs reports per entity, per licensed group and consolidated, all from the same data, without exporting it.
05

Separation that has to be visible.

When entity separation exists for licensing reasons, it has to hold inside the system as well as on paper. A venue’s staff see that venue, a regional manager sees their group, and corporate sees everything. Master records follow the same rule: a vendor that trades with three entities is visible to those three only.
Multi-Entity Management The solution

One company outside. Many entities inside.

MEM carries the division’s entities on one of Business Central’s global dimensions, so every connected system—from spend management to reporting—sees one company and needs one configuration.

Inside, each entity stays distinct. Due-to and due-from entries are generated at posting, allocation templates split shared spend across entities as it’s entered, and reports run per entity, per group or consolidated, from one dataset.

Because MEM sits inside Business Central, the groundwork carries straight over: a chart of accounts rebuilt to match across every entity, and standardized posting groups. The licensed affiliate stays in its own tenant, connected through MEM’s cross-tenant intercompany.
Before — Per-entity connections
One subscription and configuration per entity.
Operating entity Operating entity Operating entity 8+ more entities
After — Multi-Entity Management
One company in Business Central; entities as dimensions.
Operating entity Operating entity 8+ more entities
Microsoft Dynamics 365 Business Central + Multi-Entity Management Compare

Business Central native intercompany vs. Multi-Entity Management.

EXPECTED RESULTS

What's changing for the finance team.

Connected apps are set up once for the whole group, not once per entity, so a new entity no longer means a new subscription in every system.
Balances between entities are created automatically when a transaction is posted, so month-end no longer depends on someone remembering a manual entry.
Shared corporate spend is split across the entities that used it at the moment it’s entered, instead of being booked in one place and recharged later.
Reports for each entity, each group and the whole business come from the same data, with no exporting, and eliminations post and reverse on their own.
The separation licensing requires is built into the system, so each vendor and customer is visible only to the entities that trade with it.
New acquisitions are added as entities in the existing structure, so software costs stop rising with every entity licensing requires.

Bring us your entity structure. We'll show you it working.

No matter your setup or regulatory requirements, show us where Business Central is causing you pain and we'll show you how to make it run smoothly.

Book a demo to see how our solutions simplify complex financial processes.