Built with purposeA group with four legal entities almost always starts the same way: one spreadsheet, rebuilt every quarter, by one person who copies numbers out of four different accounting exports and maps them by hand into a shared structure. It works, until that person is on holiday during close, or a fifth entity gets added and the spreadsheet does not scale.
Why consolidation is a different problem from reporting
A single-entity report reads numbers that are already in one chart of accounts. A group consolidation has to solve three problems before a single "group revenue" figure means anything.
A common structure. Four companies rarely use the same chart of accounts, even when they are all in the same industry. Someone has to map each entity's accounts to one shared structure, once, in a way that survives next year's chart of accounts changes.
Intercompany elimination. If entity A invoices entity B, that revenue and cost cannot both count at the group level, or the group looks bigger than it actually is. Finding and removing intercompany transactions is usually the single most error-prone manual step in a quarterly close.
Currency, if it applies. A group spanning more than one country needs a consistent approach to converting figures, and a decision about which rate to use and when.
What "done" actually looks like
A working consolidation model produces two different views from one source of truth, because the group's owner and the group's bank usually want different things. The owner wants a management view: real profitability, without dressing anything up. A lender or investor typically wants a statutory-style view that follows accounting conventions more strictly. Building both from one model, instead of maintaining two separate spreadsheets, is what actually saves the time.
Where this usually goes wrong without help
The most common failure is not a technical one. It is that the mapping logic lives in one person's head, encoded as formulas in a spreadsheet nobody else fully understands. The close still happens, but it is fragile: a new account code appears, a formula silently miscounts it, and nobody notices until the group number looks slightly wrong three months later.
The fix is not more spreadsheet discipline. It is moving the mapping and elimination logic into a model that documents itself, and a refresh process that flags a mismatch instead of quietly absorbing it.
What this actually takes to build
For a group of four entities, consolidation usually takes more work than a single-entity report: mapping four charts of accounts, agreeing an elimination approach and validating the group total against the current control spreadsheet. We discuss those steps explicitly when defining the scope, rather than assuming a single-entity model will fit.