Intercompany & Multi-Entity Setup for Regional Groups
A regional group is several legal companies that trade with each other, lend to each other and share costs — and the money moving between them is where clean books go to die. How to set up multiple entities in one system, keep inter-entity balances real, and where operations software stops and statutory consolidation begins.
The moment a business opens a second registered company — a Ugandan subsidiary, a Tanzanian trading arm, a holding company over the top — it stops being one set of books and becomes a group. And a group has a problem a single company does not: its entities buy from each other, pay each other's suppliers, lend each other cash and share costs that belong to more than one of them. Every one of those movements is an intercompany transaction, and intercompany transactions are exactly where a group's books quietly stop reconciling. This guide is about setting up multiple entities so those movements stay honest — and about the line where the software hands off to your auditor.
Entities as nodes, not separate systems
The setup decision that determines everything downstream is whether each company is a separate system or a node in one. Separate systems feel tidy and recreate the consolidation problem with better software — the one-system-across-the-EAC argument in miniature. The workable structure is one system where each legal entity is a full node:
- Its own registration, currency and statutory books — so each company files locally from native records, not back-conversions.
- Its own accounts, stock locations, assets and approval chains — local autonomy, so the Kampala company runs itself without waiting on Nairobi.
- A shared chart-of-accounts structure — so "sales" means the same thing in every entity and consolidation is not a translation exercise. The chart of accounts is the backbone that makes a group comparable.
- Role scoping per entity — each company's team sees its own world, group finance sees across, auditors see exactly the entity and period they are auditing.
The four intercompany movements that must be accounts, not memories
| Movement | How it bites when informal | The discipline |
|---|---|---|
| One entity pays another's supplier | A "loan" between companies that lives in a message | An inter-entity payable/receivable posted automatically on both sides |
| One entity sells to another | Revenue in A, cost in B, and a mismatch at group level | A matched intercompany sale/purchase pair, flagged for elimination |
| Cash lent between entities | A balance nobody has reconciled in six months | A real inter-office loan account, reconciled monthly, on a settlement schedule |
| Shared costs (HQ, regional roles, group audit) | Charged wherever cash was convenient, owned by no one | A written allocation policy applied identically every period as allocation postings |
The rule that keeps a group reconcilable
Every intercompany balance must agree from both ends. If the receivable in Kenya's books does not equal the payable in Uganda's books to the shilling, you have found next year's audit problem early. Undocumented, one-sided inter-office balances are the single most common reason a regional consolidation fails — reconcile them monthly, in the currency they were created, before you convert anything.
Shared costs and the allocation policy
The regional coordinator, the shared ERP subscription, the group audit fee, the vehicle that serves three countries — these belong to more than one entity, and the temptation is to charge each wherever there was cash to pay it. That destroys comparability. The discipline is a written allocation policy — by headcount, revenue, activity, or a fixed key — applied the same way every month and posted as visible allocations, so a reader can see exactly why Uganda carried 30% of the regional cost. This is the 100% rule that governs shared costs, applied across a commercial group instead of across donor grants.
Where the software stops: statutory consolidation
Here is the honest boundary. A capable system gives you multi-entity books, automatic two-sided intercompany postings, reconciled inter-office balances, consistent allocations, and a consolidated management view across the group on one dataset. What it does not do is produce your audited statutory group accounts on its own. Formal consolidation — eliminating intercompany revenue and balances, handling minority interests, applying the accounting standard your jurisdiction requires — is prepared with your auditor. The system's job is to make that preparation a clean afternoon instead of a three-week reconstruction, by handing your accountant records that already agree from both sides. This is expanded in consolidated reporting for EAC groups.
Stated plainly: management consolidation is built; statutory consolidation with eliminations is your accountant's work, done faster because the underlying records are clean. Do not buy on the belief that any operations platform files your group accounts for you.
Set up your group so the books agree
Multiple entities as nodes on one dataset, intercompany movements posted on both sides, inter-office balances reconciled monthly, and a consolidated view your auditor can trust as a starting point.
Talk to us about multi-entity setupFrequently asked questions
Can we run a holding company and its subsidiaries in one system?
Yes — each company is a full node with its own registration, currency, accounts and statutory books, structured under a group so consolidation is a filter over the same dataset. The holding company and each subsidiary keep local autonomy and native books, while group finance sees across all of them. It is one system with many entities, not one merged company that loses each subsidiary's legal identity.
How are intercompany transactions recorded?
On both sides automatically. When one entity pays another's supplier or sells to it, the system posts the matching receivable and payable (or the intercompany sale and purchase) in each entity's books, so the two agree and can be reconciled — and flagged for elimination when your auditor prepares statutory group accounts. The goal is that no cross-border movement ever lives only in someone's memory.
Does it produce our audited consolidated financial statements?
It produces consistent management consolidation from one dataset, which is most of the work and removes the spreadsheet scramble. The audited statutory statements — with intercompany eliminations and the standard your jurisdiction requires — are prepared with your auditor using those clean, two-sided records as the source. The software makes consolidation fast and trustworthy; it does not replace professional judgement.
How should we handle costs that belong to several entities?
With a written allocation policy — by headcount, revenue, activity or a fixed key — applied identically every period and posted as visible allocation entries, so anyone can see why each entity carried its share. The failure mode is charging shared costs wherever cash was convenient, which makes entities incomparable and the group total meaningless.
Can each subsidiary's team be prevented from seeing the others?
Yes — role scoping is per entity, so each company's team sees only its own data, group finance gets the consolidated view, and auditors get read-only access to exactly the entity and period they are reviewing. Visibility across the group is a deliberate design choice you configure, not an unavoidable side effect of running everything in one system.
