Every entity added to your organisation makes group reporting harder for your finance team, because small inconsistencies that didn’t matter before start to create problems. Your team finds charts of accounts don’t map, some entities track and analyse things that others don't, permissions don’t carry over between entities and each entity may calculate KPIs its own way. To fix it, agree one structure across every entity, so you can roll any figure up to a group total or drill down to a single site.
The short version
- In a single entity, your team can live with small inconsistencies for years. Once you add a second, fifth or tenth entity, those inconsistencies start to clash.
- Finance teams usually run into trouble first with the chart of accounts, reporting dimensions, permissions and KPI definitions.
- Your board needs a group roll-up and managers need entity-level detail – and you should be able to produce both from the same data.
- If every entity uses the same dimensions and category definitions, you can roll any figure up to a group total or drill down to a single site without remapping it.
- The finance teams at The Recruitment Group and A-One Insurance Group both ran multiple companies on Sage 50 and moved to one consistent structure before they could see a clean group view.
A single-entity finance team can live with an inconsistency for years. Perhaps one cost centre uses a category slightly differently from the rest, or a manager has broader access than they need. With only one set of books, none of that does much harm.
When you add a second entity, your team can suddenly find it has two sets of numbers that should agree but don’t. Add more entities and the mismatches pile up. Either someone reconciles them by hand every reporting cycle, or the group figures hide them.
Here we look at where finance teams run into trouble first as a group grows, and how you can keep a reliable group view without losing the entity-level detail underneath. How quickly you close your books is a separate question, which we cover elsewhere.
Why reporting gets harder with every entity you add
Each entity you add gives your team more chances for figures to clash. If one entity miscategorises a cost, it’s a rounding error. If 10 entities each record the same cost their own way, nobody on the board can trust the group total until someone checks how each entity booked it. With one entity, your team has nothing to compare against, so they never see the inconsistency.
Problems start when your team puts a second entity’s numbers next to the first and finds they were built to a different standard. Perhaps whoever set up each entity used the same department code to mean slightly different things or gave someone broader access than they intended.
Where finance teams run into trouble first
Most finance teams run into trouble first with four things: the chart of accounts, reporting dimensions, permissions and KPI definitions. Whoever set up each entity built these for that entity alone, without a second one in mind. So your team usually only spots the gaps when they put two sets of numbers side by side.
- Charts of accounts that don’t map between entities: One entity’s team might book a cost as ‘professional fees’ while another books the same cost as ‘overheads’. When you add the two together, you’re combining figures that nobody set up to be compared.
- Reporting dimensions that only some entities use: If one entity tracks cost by project and another doesn’t, you either leave that entity out of your group-wide project view or someone has to estimate its figures by hand.
- Permissions that don’t carry over: If you built access rules around one company’s structure, you’ll usually have to rework them from scratch to fit a second entity’s departments and roles.
- KPIs that nobody defined centrally: If one entity’s team calculates gross margin one way and another’s does it slightly differently, your board sees a group figure that looks precise but isn’t.
How to keep entity-level detail and a group view
You keep both views by agreeing the structure underneath them. If every entity uses the same dimensions and category definitions, your team can roll any figure up into a group total or drill back down to a single site without remapping it first. Your board and your local managers are then looking at the same data, just at different levels.
If you get the balance wrong, someone loses out. Report at too high a level and your local managers lose the detail they need to run their part of the business. Report only by entity and your board can’t get the group answer it asked for.
What this looks like in practice
The Recruitment Group grew through nine acquisitions before simplifying into four businesses. On Sage 50, Finance Director Narinder Uppal found it “wasn’t easy to see profit and loss by cost centre, division or department”. Now that the companies sit on one platform, he can see reports “by company and then by department and then, within that, by division”.
Narinder also has tighter control over who does what. The payroll team works with access set “for specific functions within the business”. Because “we can see who has made an update”, he can spot where someone needs training when the same mistake keeps recurring.
A-One Insurance Group’s finance team was producing accounts for nine companies on Sage 50. “Information wasn’t being consolidated. There were replication conflicts. We were driving the business blind,” says Group Operations Director Sarah Smith. Now, says Accounts Manager Danielle Morris: “You can see instantly the profit and loss and you can consolidate everything or flag if there’s a duplicate.”
Where iplicit fits
If your team fixes mismatched entities in a spreadsheet every month, they’ll be doing the same work again next month. For a lasting fix, your finance team needs one system where every entity shares the same structure, with unlimited reporting dimensions, real-time consolidation and access you can set by function. That’s how iplicit approaches multi-company accounting for growing organisations.
With automated group consolidation, iplicit consolidates every transaction in real time, including FX calculations and group eliminations. Your team can analyse figures by project, site, department or division using unlimited dimensions.
The bottom line
Agree your categories, dimensions, permissions and KPI definitions centrally before the next entity joins. If you wait until the board asks why the numbers don’t add up, your team will be untangling every entity at once.
If your bigger concern is how quickly your team closes the books each month, Why multi-entity accounting is so complicated explains how intercompany transactions and consolidation slow finance teams down.
To see how it works, take the three-minute quick tour, or book a demo with our team.
Why does group reporting become harder with each entity you add?
Why does group reporting become harder with each entity you add?
Your team can ignore small inconsistencies in categories, permissions and KPI definitions while there’s only one entity. Once there’s a second, fifth or tenth entity to compare against, those inconsistencies start to clash, and the reconciliation work grows with every entity you add.
How do you keep a group-level view without losing entity-level detail?
How do you keep a group-level view without losing entity-level detail?
You standardise the categories and reporting dimensions that every entity uses. Your team can then roll any figure up into a group total or drill it back down to a single entity from the same data, instead of maintaining separate group and entity reports that sometimes disagree.
What causes a group KPI to be unreliable across entities?
What causes a group KPI to be unreliable across entities?
Usually nobody agreed the KPI’s definition centrally, so each entity’s team calculates it slightly differently. Two entities can report gross margin under the same label using different calculations, which gives your board a combined group figure that nobody can rely on enough to act on.
Is this the same as improving how fast a group closes its books?
Is this the same as improving how fast a group closes its books?
No. Closing speed is about how quickly your team gets the numbers to the board after the month ends, while this is about whether your categories, permissions and KPI definitions still hold together once you run more than one entity.
What is a reporting dimension?
What is a reporting dimension?
A reporting dimension is a tag your team adds to a transaction alongside its account code, such as department, project, site or division. Dimensions let you analyse the same figures in different ways without creating a new account for every combination, so your chart of accounts stays manageable as the group grows.
