Multi-entity management: Is standard Business Central holding you back?
Multi-entity management: Is standard Business Central holding you back?
November 18th, 2026
5 min read
It’s the third working day of the month. The UK trading company has closed, but the Irish subsidiary is still waiting on a recharge from head office. Someone is matching intercompany balances in a spreadsheet, and the board pack is due on Friday.
If that sounds familiar, the cause usually isn’t your people or your ERP. It’s that the way your group is set up in Microsoft Dynamics 365 Business Central hasn’t kept pace with the way the group has grown. The good news is that the fix rarely means starting again.
The real cost of running entities side by side
No single task in multi-entity accounting is especially hard. The trouble is that small frictions repeat in every entity, every month, and they add up.
Consolidation becomes a project rather than a process, assembled in spreadsheets from figures each company sends in. Systems that don’t share data force finance to stitch together a group view by hand. Compliance multiplies: a UK group may report under FRS 102 or IFRS, file VAT through Making Tax Digital, and meet different rules for each overseas subsidiary. And because all of this takes time, the numbers leadership sees are often weeks old by the time they arrive.
The problem is widespread. Around 85% of organisations say inefficient intercompany processes delay their financial reporting, and the delay grows with every entity added.
Credit where it’s due: Business Central on its own
Business Central is not short of multi-entity features. Each legal entity runs as a separate company, intercompany partners exchange documents through an inbox and outbox, and a built-in routine consolidates the companies into a group view.
For a group with two or three entities and modest intercompany trading, that model works well, and it’s often the right place to stay. It starts to creak when the number of entities, currencies or intercompany transactions rises. Each company then needs its own master data, its own setup and its own month-end, and every link between companies is another manual step.
A five-minute self-check
Before looking at any new software, it’s worth being honest about where the time goes today. Tick any statement that applies to your finance team:
□ We expect to add entities in the next two years, through growth or acquisition.
□ Group consolidation takes days, not hours, and needs spreadsheets to finish.
□ The same customers, suppliers or bank accounts are set up in more than one company.
□ Intercompany recharges and allocations are keyed in by hand each month.
□ The board only sees group figures after month-end close.
One tick is normal for any growing group. Two or more usually means the standard setup is costing you more time than it should, and it’s worth exploring the alternatives.
Extend Business Central rather than replace it
When a group outgrows the standard setup, the instinct can be to look for a bigger ERP. Often there’s no need. Multi-Entity Management (MEM) from Binary Stream is an extension that sits inside Business Central and changes how the group is structured.
Instead of one company per legal entity, MEM runs every legal entity within a single Business Central company, with each entity tracked as a dimension. Users still post to the right entity and see only what they’re permitted to, through a user-entity security layer. But the data, setup and processes are shared, so most of the copying, sending and reconciling between companies disappears.
Businesses that have made the switch report consolidation times falling by as much as 67%.
Where the difference shows
MEM targets the same five pressure points from the self-check above.
| Pressure point | What finance experiences today | What changes with MEM |
|---|---|---|
| Intercompany activity | Recharges and allocations raised, sent and accepted company by company | Intercompany entries and shared costs generated automatically from one posting |
| Entity differences | Separate setup per company for currency, fiscal year and tax | Each entity keeps its own currency and year-end inside one shared setup |
| Group reporting | Figures compiled after close from several companies | Entity and group views available at any time from one dataset |
| Master data | Customers, suppliers and banks duplicated and kept in sync by hand | One shared set of records across all entities |
| Growth and acquisitions | A new company to configure, connect and reconcile | A new entity added as configuration within the existing company |
Making the call with Pragmatiq
There’s no standard answer to multi-entity finance, because no two groups are structured the same way. Whether to extend Business Central is a finance decision as much as a technical one, so we start with how your month-end actually runs, not with a product demo. For some groups the answer is a few changes to the current approach: tidying up the standard Business Central setup and making better use of the intercompany tools already there. For another, it’s better reporting or some targeted automation. For a group with many entities and heavy intercompany activity, an extension such as MEM may be the clear next step.
We also look at the bigger picture. Pragmatiq works across the Microsoft ecosystem, so any recommendation accounts for how finance connects to your CRM, reporting and AI plans. The aim is a set of systems that work together, not a fix for one problem that creates another.
If the self-check raised a tick or two, talk to us. We’ll give you a straight answer on whether Business Central still fits as it is, or whether it’s time to extend it. To get in touch with our team, fill out the form below, email us at info@pragmatiq.co.uk or call 01908 038110.