Consolidation is no longer just a statutory reporting exercise. It is an end-to-end design challenge that determines how quickly, accurately and confidently financial services firms can report across finance, risk, liquidity and regulatory domains.
For most financial services groups, "consolidation" still lives in a box marked finance systems, owned by a small team, judged on whether the numbers tie out by month-end. That framing is comfortable, familiar — and increasingly wrong.
Consolidation sits at the centre of a much bigger challenge: producing consistent, defensible, group-level numbers across financial, regulatory, liquidity and risk reporting — on a timeline that no longer tolerates a three-week close. Firms that keep treating it as an IFRS or local GAAP exercise are underinvesting in the one capability that increasingly determines how fast, how accurately, and how confidently they can report to regulators, investors and their own boards.
Here's why consolidation deserves a seat at the top table — and what separates firms that get it right from those still fighting their own systems.
Ask most finance teams what "consolidation" means and you'll get an answer about statutory accounts. But group-level reconciliation doesn't stop there. FINREP, STDF, IRRBB, liquidity returns, internal management reporting — every one of these needs to reconcile back to a consolidated view, even where scopes, boundaries and bases of preparation differ.
Treating consolidation as a purely financial-GAAP topic misses this entirely. The real requirement is a consolidation capability that can flex across multiple regulatory and risk lenses without falling apart at the seams.
Built correctly, this doesn't have to mean reconciliation in the traditional sense. If every regulatory and financial view is run from the same granular, transaction-level dataset, the differences between them stop being a data quality problem to chase down and become a known, explainable set of definitional differences — scope, basis of consolidation, treatment of specific entities or instruments. What firms need isn't a reconciliation exercise bolted on after the fact; it's a clear walk that explains, view by view, exactly why FINREP, IRRBB, liquidity and statutory numbers differ — because they were built from the same granular base in the first place.
Very few groups consolidate in a single step. In practice, Group numbers are typically built through a sequence: legal entities roll into sub-groups, sub-groups roll into regional or divisional consolidations, and only then does the final Group number emerge. Each step applies its own eliminations, adjustments and currency translation — and each one adds a layer of timing, judgement and potential error before the number ever reaches the top.
This sequential design is often inherited rather than deliberately chosen, and it has real consequences. A correction made at the sub-consolidation level needs to cascade cleanly through every layer above it — and often doesn't, without manual intervention. Timing differences between when each layer closes can leave the Group number reconciling against an earlier version of a sub-group's position. And because each layer is typically owned by a different team, visibility into what's actually happening at each step of the chain is often thinner than firms realise.
None of this means a sequential approach is wrong — for many group structures it's unavoidable. But it does mean the sequence needs to be designed deliberately, with clear ownership, consistent timing across layers, and a mechanism for cascading changes automatically rather than chasing them level by level. Firms that treat each layer as someone else's problem tend to discover, at the worst possible moment, that their Group number depends on a chain of assumptions nobody has actually tested end to end.
Intercompany reconciliation. Balance sheet substantiation. Data lineage from source ledgers. None of these are "adjacent" to consolidation — they're part of the same end-to-end chain, and treating them as separate workstreams is one of the most common (and costly) mistakes we see.
Design consolidation in isolation and you get a technically capable tool that still can't produce a clean number on its own, because the inputs feeding it are unreconciled, unsubstantiated, or arriving too late. The result is predictable: manual workarounds, spreadsheet patches, and a "consolidation system" that quietly depends on a small army of people doing things the system was supposed to eliminate.
Getting this right means designing consolidation and its adjacent processes together, from day one — not bolting reconciliation and substantiation on afterwards as a fix.
For multinational firms with complex group structures, the field of vendors genuinely capable of handling sophisticated consolidation requirements is narrow. That's not the risky part. The risk lies in the calculation complexity that sits inside the platform: non-controlling interests, IFRS 12 scope and disclosure requirements, FX reserve movements, and the myriad of adjustments that come with multi-entity, multi-currency groups.
Selecting a platform is a commercial decision. Configuring it to handle these calculations correctly, consistently, and transparently is where deep technical expertise earns its keep — and where many implementations quietly fall short.
A consolidation engine that produces accurate numbers quickly is doing its job — nothing more. What actually changes the game is what happens next: automated variance analysis, commentary generation, and exec-ready explanations that don't require a team of analysts to manually chase down every unusual movement.
The best consolidation setups don't just report the number — they flag the account, entity or currency that moved unexpectedly, before anyone has to go looking for it. That's the difference between a system that produces reports and one that produces understanding.
Few design decisions matter as much — or are as often under-invested in — as the chart of accounts. A single-dimensional COA might have been adequate once. It is not adequate for a multinational firm reporting across entities, currencies, products and regulatory bases simultaneously.
A multi-dimensional, clearly structured, genuinely understood COA is what allows consolidated numbers to be sliced, defended and explained. Just as important is the ability to drill down — from a Group-level account, through the consolidation adjustments, back to the originating GL account and the underlying transaction. That full data lineage is what allows consolidation and audit teams to answer their own questions, trace a number back to its source, and challenge an entry without depending on someone else's institutional memory.
Critically, the COA needs to be owned — not just implemented and forgotten, but actively maintained by people in the firm who understand why it's built the way it is. A COA nobody understands, or can't be traced back to source, is a COA nobody trusts.
Ask most firms how long their consolidated close takes and the honest answer is: longer than it should. There should be a clear, deliberate target for how long consolidation takes — not an accepted status quo. The current market average is still too slow, and that's rarely a headcount issue. It's usually a symptom of an end-to-end process that was never designed to move fast in the first place.
Firms serious about accelerating the close need to look upstream — at data flows, reconciliation timing, and system architecture — not just at the consolidation tool itself.
A well-designed entity taxonomy sounds like a technical footnote until you're trying to compare numbers across reporting domains and discover the structure doesn't hold together. This becomes acute for firms active in M&A, where new entities, restructures and disposals need to slot cleanly into an existing taxonomy without breaking historical comparability.
Underneath that sits a more fundamental question: can you demonstrate completeness? That means reconciling the full population of reporting entities back to the legal entity structure, entity by entity, and maintaining a clear, current view of ownership and control — including where it has changed. A stake that moves from significant influence to control, or a structure that shifts from proportionate to full consolidation, changes the numbers materially. A taxonomy that doesn't track this in real time will quietly misstate the group position without anyone noticing until much later.
Getting this right requires real expertise — not a generic template, but a structure designed with the firm's actual corporate history and future trajectory in mind.
Most firms still treat consolidation as a monthly event. But the case for weekly — even daily — consolidation is only getting stronger, not least for stress-testing purposes in periods of market turbulence. There is no longer a credible technical reason preventing this. The barriers that remain are almost always about legacy design, not capability.
Firms that can consolidate on demand have a materially different level of visibility into their own risk position — and a materially different story to tell regulators when it matters most.
None of the above is solved by buying better software. Successful consolidation transformation depends on a genuine, deep understanding of a firm's specific pain points, combined with hands-on knowledge of end-to-end financial and regulatory reporting processes and the data flows that feed them.
This isn't theoretical knowledge. It comes from having actually sat in the seat of financial reporting — having owned the close, wrestled with the reconciliations, and understood exactly how consolidation systems interact with everything around them. Without that grounding, transformation programmes tend to reproduce the same problems in a new system, just with a bigger price tag.
If your consolidation process still feels like a monthly scramble, if your chart of accounts is something only two people in the building truly understand, or if you've never quite trusted the entity comparisons your teams present to the board — these aren't isolated issues. They're symptoms of the same underlying design gap.
We work with financial services firms to close that gap: from diagnosing where the end-to-end process is breaking down, to designing a consolidation architecture — platform, chart of accounts, taxonomy and adjacent processes — that's built to last, not patched together.
If any of this sounds familiar, let's talk. Get in touch to discuss where your consolidation process stands today, and what a genuinely fit-for-purpose design could look like for your firm.
Let's start with a conversation about your specific challenges.