- Structure: Multi-entity corporate group — several legal entities
- Reporting requirement: Monthly consolidated financials for group management
- Complexity: Intercompany transactions, multi-entity projects, legacy reconciliation items
- Engagement type: Group coordination, consolidation management, and legacy issue resolution
Executive Summary
A multi-entity corporate group operating across several legal entities and jurisdictions engaged Sapphire Digital Accounting Australia to address a fundamental gap in its financial governance structure. The absence of a dedicated coordination function had resulted in fragmented reporting, accumulated legacy reconciliation issues, inconsistently recorded intercompany transactions, and a monthly consolidation cycle that consistently missed its delivery window — leaving group management without the timely financial information required to make informed decisions.
Sapphire established a structured group coordination function, resolved outstanding historical accounting discrepancies, introduced intercompany governance disciplines for new multi-entity projects, and redesigned the monthly consolidation cycle around a defined submission and review calendar. The outcome was a reliable, on-schedule consolidation process, materially reduced intercompany mismatches, and restored confidence in the integrity of group financial reporting.
Client Overview
The client is a mid-sized Australian corporate group comprising multiple legal entities, each operating with its own finance team, accounting systems, and reporting obligations. The group's financial operations involve intercompany funding arrangements, shared services, and cross-entity project activity — all of which require active coordination at the group level to produce accurate consolidated financial statements.
Engagement Scope
The engagement covered four interconnected workstreams:
- Group coordination — establishing a central liaison function between entity finance teams and group management
- Legacy issue resolution — identifying, documenting, and driving closure of historical accounting and reconciliation discrepancies
- Intercompany governance — ensuring consistent accounting treatment across entities for new projects and existing intergroup balances
- Monthly consolidation — restructuring the consolidation cycle to deliver consolidated financials within a defined, predictable window
Key Challenges
4.1 No Central Coordination Function
Each entity finance team managed its reporting obligations independently, without a common reference point for timelines, data standards, or issue escalation. Group management had no single point of accountability for consolidated financial information — creating a structural gap that no individual entity was positioned to fill.
4.2 Accumulated Legacy Issues
Historical accounting discrepancies had accumulated across entities without clear ownership. The decentralised structure meant that cross-entity issues fell between teams, and there was no mechanism for driving resolution that required coordination across multiple finance functions simultaneously.
4.3 Intercompany Mismatches
New multi-entity initiatives were generating intercompany balances that were being recorded inconsistently across counterparty entities — using different rates, classifications, or recognition timing. These mismatches surfaced during consolidation as elimination differences, requiring time-consuming late-stage adjustments.
4.4 Delayed Monthly Consolidation
The monthly group consolidation was consistently delivered outside the target window. Delays stemmed from inconsistent entity submission timelines, incomplete data requiring mid-process clarification, and the absence of a structured pre-consolidation review. Management was routinely receiving consolidated results too late to inform operational decisions for the period.
Approach and Solution
5.1 Establishing the Coordination Function
The first step was to identify finance focal points within each entity and establish a defined communication framework — covering responsibilities, escalation paths, submission requirements, and timelines. This coordination layer was treated as a prerequisite to resolving individual issues, because sustainable improvement in the consolidation process depends on a functioning structure, not one-off interventions.
5.2 Legacy Issue Resolution
All outstanding historical discrepancies were identified, documented in a centralised register, and prioritised by materiality and complexity. Resolution was then driven through structured follow-up with the relevant entity teams — coordinating root cause analysis, agreeing correcting entries, and confirming closure. Registering all items before beginning resolution was deliberate: it prevented effort being absorbed by the most visible issues at the expense of less prominent but potentially more significant ones.
5.3 Intercompany Governance
For new multi-entity projects, accounting treatment was agreed across all counterparty entities before transactions were recorded — covering classification, recognition timing, and currency conventions. Intercompany balances were reconciled monthly, with any mismatches resolved within the period. Addressing intercompany consistency at inception rather than at consolidation eliminated the elimination differences that had previously required late-stage correction.
5.4 Restructuring the Consolidation Cycle
The monthly consolidation process was redesigned around a four-stage calendar: entity close and submission; pre-consolidation review of submissions for completeness and consistency; consolidation and elimination entries; and management report issuance. Standardised submission templates were introduced to reduce variability in entity-level data. The pre-consolidation review — conducted before consolidation began — materially reduced the volume of mid-process clarifications and rework.
Tools and Systems
The engagement was delivered without requiring new technology investment. Existing entity-level accounting systems were used as the data source. Supporting infrastructure included an Excel-based centralised issue register for legacy item tracking; a structured Excel consolidation model incorporating intercompany eliminations; standardised entity submission templates; and a consolidation calendar managing deadlines, review milestones, and escalation triggers.
Results and Impact
The following outcomes were observed over the course of the engagement. Improvements are assessed against the pre-engagement baseline established during the initial diagnostic.
| Area | Baseline State | Post-Engagement State |
|---|---|---|
| Group coordination | No central function; entity teams operated independently | Structured coordination function in place; defined responsibilities and escalation path |
| Legacy discrepancies | Historical issues unresolved; no clear ownership or closure process | All items documented and registered; material discrepancies resolved through coordinated corrections |
| Intercompany mismatches | Inconsistent treatment across entities; mismatches found at consolidation | Pre-agreed treatment for new projects; monthly reconciliation; mismatches resolved within period |
| Consolidation timeliness | Consistently delayed; consolidated financials received outside the target window | Monthly consolidation delivered on schedule; management reporting cycle made predictable |
| Submission quality | Inconsistent submissions requiring extensive mid-process clarification | Standardised templates and pre-submission review reduced clarification volume materially |
Key outcome: The monthly consolidation moved from an unpredictable, frequently delayed process to one delivered on schedule each period. Group management received consolidated financial information within a consistent window, enabling earlier and better-informed operational decisions.
Conclusion
The core challenge in this engagement was structural, not technical. The accounting principles underpinning group consolidation are well-established. What was missing was the coordination layer that consolidation depends on — a defined function responsible for connecting entity finance teams, managing the close cycle, and resolving issues that cross entity boundaries.
For finance leaders managing multi-entity groups, the quality and timeliness of consolidated reporting is shaped as much by process discipline and coordination as by the capability of individual entity teams. Establishing that coordination function — with clear responsibilities, structured communication, and a predictable close calendar — is the prerequisite for reliable group financial reporting.