Financial consolidation starts with a reporting policy and a controlled data model. Adding entity trial balances together is only one step. The difficult work is making sure the group view reflects the intended scope, definitions and adjustments, with a route back to the source.
This guide covers implementation planning for group finance teams. Your accounting advisers should confirm the policies and statutory requirements applicable to your group.
Define the reporting purpose
Management consolidation, budget consolidation and statutory consolidation can have different requirements. Establish which outputs the project must produce and who signs them off. Do not assume that a dashboard showing group totals is a statutory consolidation system.
Document the entity scope, ownership changes, reporting periods, currencies and the expected treatment of acquisitions or disposals. Where specialist accounting judgements are needed, identify the responsible reviewer before building calculation rules.
Create a controlled account mapping
Entities may use different charts of accounts or apply similar account names differently. The mapping should identify the source account, target group account, applicable entity and effective period.
Preserve an unmapped-account report. Automatically dropping an unfamiliar code can make the consolidation appear to balance while omitting relevant activity. When mappings change, decide whether prior periods must be restated and keep a record of the decision.
Design intercompany matching and adjustments
Identify counterparties at the level required for reconciliation. Agree who resolves differences and how timing, currency or classification differences are recorded.
Consider this simplified example in a single currency:
| Revenue | Amount |
|---|---|
| Entity A external revenue | £900,000 |
| Entity A sale to Entity B | £100,000 |
| Entity B external revenue | £600,000 |
| Revenue before elimination | £1,600,000 |
| Intercompany revenue elimination | (£100,000) |
| Group external revenue | £1,500,000 |
The example illustrates only the revenue side of a simple internal transaction. It is not a complete consolidation entry: the corresponding expense, balances, inventory or other effects depend on the transaction and accounting policy.
Make currencies and versions explicit
Store the source currency and reporting currency distinctly. Agree which exchange-rate rules apply to each type of balance or movement and how translation differences will be reviewed. Do not apply a single rate indiscriminately because it makes the import easier.
Separate submitted data, adjustments and final published results. An approved reporting version should be reproducible after a planner changes a forecast or an entity resubmits its ledger.
Build acceptance criteria before automation
A useful acceptance pack includes:
- Source totals reconciled to each submitted trial balance.
- A complete mapping report with exceptions visible.
- Intercompany matches, differences and approved resolutions.
- Adjustments with preparer, reviewer and explanation.
- A bridge from entity results to the published group totals.
- A rerun of a prior reporting period with the same approved inputs.
Test exceptions as well as the normal path. A late entity, missing counterparty and revised mapping are ordinary operating conditions, not rare edge cases.
Choose an implementation your team can operate
A consolidation project needs a model owner, a close calendar and a support process after go-live. Establish who can change rules and how those changes are tested.
Profitcura supports Jedox planning and consolidation and custom finance applications. Start by defining the reporting requirement and controls, then choose the appropriate implementation.