%402x.svg)
Your ERPs, the group planning platform and intercompany, reconciled automatically on every load. Each difference is flagged with its source, and the audit evidence is written while the platform runs.
Five parts on one governed ledger. Two report views come with them: Statements & Reconciliation, and the Consolidated Revenue Bridge.
Each ERP instance, the group planning platform and every entity reporting on files map to one entity key and one chart of accounts. A difference always traces back to the entity that caused it.
Each load compares the ERPs with the group planning platform, to the tolerance finance sets. Every row lands in one of four buckets: reconciled, adjustment, consolidation-only or outside the close window.
ERP revenue walks to consolidated revenue through close timing, consolidation-only entries, top-side adjustments and intercompany eliminations. The controller sees every reconciling difference, with its source, before signing.
Intercompany pairs are matched automatically across entities, and eliminations are computed up the full hierarchy on every load.
Every load, every difference and every adjustment leaves a record, so the evidence an auditor asks for already exists when the audit starts.
Entries the ERP posted after the group cut-off, or loads that landed in a different period. They normally clear the following period.
Entries that exist only at group level. They are booked in the group planning platform and appear in no ERP.
Adjustments group finance makes on top of the consolidated numbers, each one kept with its source.
Sales between entities of the same group, removed so the group reports only revenue earned outside it.
Illustrative figures. Each leg is a reconciling difference with a named source; the sign shows its direction.
Two groups with different starting points and the same pattern underneath. Client names stay under NDA.
Ask for a reference call under NDA
Platforms in our finance programmes: Maconomy · SAP · OneStream · SAP BPC · BigQuery · Microsoft Fabric · Power BI · dbt · Airflow · Terraform
Reconciliation is the first of five areas on one governed ledger. Once the close reconciles, the P&L, working capital and forecasting read the same numbers. Already run a data platform? We build the reconciliation on it.
Every play runs on the same governed ledger. Each one is a small project with its own return.
Payroll reconciled to the general ledger automatically, with only the exceptions sent for review.
Value: recurring cost reduction
The monthly management-reporting upload replaced by a governed feed, loaded and validated automatically.
Value: recurring cost reduction
Close status live per entity, with the automated reconciliations feeding the close checklist.
Value: recurring cost reduction
Intercompany pairs matched across entities, and mismatches flagged before the close starts.
Value: recurring cost reduction
Control evidence captured from reconciliations and workflows while the platform runs.
Value: recurring cost reduction
Because the reports read from the same place. When reconciliation runs inside the governed ledger, the reconciled number is the one in the P&L, in the dashboards and in Excel. A reconciliation tool you keep for account sign-off can read from the same ledger.
Yes. Every ERP instance and every entity on a mapping file is brought onto the same entity key and chart of accounts, so each one reconciles the same way.
Every load is reconciled and every difference is logged with its source, so the evidence builds up while the platform runs. Where a source system limits what can be extracted, consistency can be proven statistically. That is how our largest reference satisfied its SOX criteria.
At our largest reference, the first release went live in 90 days and full production followed in six months. The timeline scales with the entity count and the number of source systems.
Your systems on the table, and an honest read on where the differences come from and what it takes to reconcile on every load.
