A group with four entities closes in eight working days. The same group with eleven entities closes in nineteen, and nobody can point to the month it went wrong. The finance director's explanation is usually that the business got more complex, which is true and unhelpful, because the complexity that matters is a specific and short list of things that were never designed. Consolidation difficulty does not scale with entity count. It scales with the number of decisions nobody made when each entity was added.
Every acquisition adds one entity and four unresolved questions. The close calendar is where the unanswered ones accumulate
Here is what actually drives the compounding, and what to fix first.
The four things that compound
Intercompany without a matching discipline. Two entities book the same transaction at different amounts, in different periods, under different account codes, and the difference is found at consolidation rather than at source. Every new entity adds a pair to every existing one, which is why the problem grows faster than the entity count. Chart of accounts divergence. Each acquisition arrives with its own coding and gets a mapping table instead of a conversion. Mapping tables are maintained by one person and are never complete. Currency and the translation policy. Functional currency determinations made informally at onboarding, average versus closing rate treatments applied inconsistently, and a cumulative translation adjustment nobody can explain because the policy changed twice without documentation. Statutory versus group reporting divergence. Local books prepared to local standards, group reporting on a different basis, and an adjustment layer that exists in a spreadsheet maintained outside the system.
The sequence that actually works
Fix intercompany first, because it is the largest consumer of close time and the easiest to address structurally. A shared intercompany transaction reference, applied at the point of origination rather than reconciled afterwards, removes most of the matching effort permanently. Then converge the chart of accounts rather than mapping it. This is unpopular, slow and the only durable answer; mapping tables are technical debt with a finance label. Then document the translation policy formally, including the functional currency determination for each entity and the basis for it, because that is the question an auditor will ask when the group is large enough to attract attention. And leave the statutory adjustment layer until last, but get it out of spreadsheets and into the system before it becomes the single point of failure it is currently trending toward.
| Decision | What needs an agreed owner |
|---|---|
| Intercompany | Transaction references, counterparties and reconciliation rules |
| Chart of accounts | Group reporting mappings and local statutory requirements |
| Currency | Functional currency, translation and elimination treatment |
| Statutory reporting | Local reporting calendars and group-close responsibilities |
Qualitative summary of this article's source text, not a measured outcome or performance estimate.
What to do at the next acquisition
Decide the four questions in the first month, before the first close. Which chart of accounts, which functional currency and why, how intercompany will be referenced, and what the statutory-to-group adjustment looks like. An hour of decision in month one saves a permanent addition to the close calendar.
Practical Guidance for Consolidation Architecture Review
- Introduce a shared intercompany reference at origination.
- Converge the chart of accounts; do not extend the mapping table.
- Document functional currency determinations entity by entity.
- Move the statutory adjustment layer out of spreadsheets.
- Decide the four questions before an acquisition's first close.
- Measure close time by entity to find where it actually goes.
- Set an intercompany tolerance and enforce it at source.
- Assign one owner for group accounting policy.
The Regional Angle
The first factor that makes this harder in the Gulf than in most markets is that entity proliferation here is often driven by regulation rather than commerce. Ownership requirements, free zone versus mainland licensing, sector-specific establishment rules and the practical need for a separate entity per emirate or per activity mean a regional group can accumulate a dozen legal entities running what is commercially one business. Those entities were created for licensing reasons and given accounting structures as an afterthought, which is exactly the origin of the divergence described above. The second concerns the tax position, which has changed the stakes materially. With Emirati corporate tax now established and qualifying free zone treatment depending on the character of income by entity, intercompany pricing and the allocation of costs between entities are no longer purely presentational. A group that has been booking management charges informally between entities for years now has a transfer pricing exposure attached to the same weak intercompany discipline that slows its close. Fixing the mechanism serves both purposes, which is the easiest business case for this work you will ever have. The third is about the statutory layer and local practice. Several jurisdictions in the region require locally filed accounts prepared by a local auditor, sometimes in Arabic, on a timetable unrelated to the group calendar, and the adjustments between local and group basis are frequently held by the local finance manager rather than by group finance. That is a continuity risk in a market with high expatriate turnover: when that manager leaves, the reconciliation between statutory and group books leaves with them. Get those adjustments documented and systematised before the person who understands them rotates out.
The objection worth taking seriously
The strongest objection is that chart of accounts convergence is rarely worth it. It is a large, disruptive project with no visible benefit to anyone outside finance, it consumes the same scarce implementation capacity needed for commercially useful work, and mapping tables — while inelegant — do function. Plenty of large groups have run on mapping layers for decades. Advising a mid-sized group to converge its coding structures is advising it to spend a year of finance transformation budget on making the close three days shorter. That is a fair reading of the cost, and for a group that is not acquiring further, it may be the right answer. The case for doing it rests on what happens next rather than on close duration. Mapping tables break under two specific conditions: another acquisition, and any attempt to use the group data analytically — including the assistant capabilities every vendor is now shipping, which reason over the structure they are given and produce confident nonsense from inconsistent coding. A group that intends to keep acquiring, or to get any value from automated analysis of its own consolidated data, is paying for convergence eventually and at a higher price. A group that intends neither should keep the mapping table and spend the money elsewhere, which is a legitimate decision and should be a stated one rather than a default.
Common Questions
What is a realistic close target for a multi-entity group?
It depends far more on intercompany discipline than on entity count. Groups with clean intercompany matching close in single digits at twenty entities; groups without it struggle at six.
Can consolidation software fix this?
It can automate the mechanics of a process whose inputs are consistent. It cannot resolve a functional currency determination nobody made.
Where should the adjustment layer live?
In the system, as a distinct ledger or adjustment company, with the same audit trail as everything else. Spreadsheets here are the most common single point of failure in group reporting.
What should we expect over the next twelve months?
Expect regional tax scrutiny to make intercompany documentation a compliance matter rather than a close inconvenience. Expect vendors to market automated intercompany matching heavily. Expect the groups that converged their coding to get disproportionate value from analytical tooling. And expect entity counts in this region to keep rising for regulatory reasons.
Consolidation Architecture Review — we find which of the four unanswered questions is actually costing you the close, and answer that one first.