Finance systems · Integration
The layer between your source systems and the truth.
A consolidation or planning platform is only as reliable as the data arriving underneath it. Most reporting errors are integration errors wearing a different system's name.
Every group runs more than one system: an ERP or several, a payroll system, subledgers, sometimes a data warehouse. Getting numbers from those systems into a platform such as OneStream or Anaplan, correctly and repeatably, is a discipline in its own right, not an afterthought bolted onto a platform project.
This page explains what that work actually involves, where it usually breaks, and what good looks like. It is written for finance teams who suspect their reporting problem is not really a reporting problem.
From £5,000. A structured review of your data flow, not a sales call.
Start here
Does the problem sound like yours?
Integration problems rarely announce themselves as integration problems. They show up as someone else's number being wrong.
The same figure differs by system
The ERP, the consolidation platform and the management pack disagree, and reconciling them is a manual, recurring exercise rather than a control.
Loads fail silently, or fail loudly at month end
A mapping breaks when a new cost centre or account is added upstream, and nobody finds out until the numbers do not add up during close.
Nobody owns the mapping logic
The transformation rules between source chart of accounts and target structure live in one person's memory, or in a spreadsheet nobody dares change.
Reconciliation happens after the fact, not as a control
Differences are investigated once reported numbers look wrong, rather than caught automatically at the point data is loaded.
What we do
Mapping, transformation and reconciliation, built to hold.
Integration work is unglamorous and easy to underinvest in. It is also where most of the risk in a finance systems estate actually sits.
Source analysis
Understanding what each source system actually produces, including the exceptions, manual adjustments and edge cases that do not show up in the documentation.
Mapping and transformation
Chart of accounts mapping, currency handling, entity structures and the business rules that convert source data into a target platform's model, whether that is OneStream, Anaplan, or a data warehouse.
Validation and error handling
Loads that fail safely and visibly when something upstream changes, rather than loading bad data quietly and letting it surface three reports later.
Reconciliation back to the ledger
Built in as a control at load time, not added later during testing or discovered during audit.
Still worrying about
Questions finance directors ask us.
Do you work alongside our existing ERP or platform implementer?
Yes, and often that is exactly the arrangement. We are frequently brought in for the integration and reconciliation layer specifically, working alongside a platform partner or an in-house team who own the rest of the build.
Can you fix an integration that is already live and misbehaving?
That is a large part of the work. Diagnosing why a live integration produces intermittent or silent errors, then correcting and hardening it, without a full platform rebuild.
Do you build integrations for systems other than OneStream and Anaplan?
Yes. The mapping, transformation and reconciliation discipline is the same regardless of target: a data warehouse, a reporting layer, or another platform entirely.
What does this work cost?
It depends on the number of source systems, the state of the underlying data and how much reconciliation control already exists. We scope and cost this work after a diagnostic, in writing, before any commitment.
Start with the diagnosis, not the platform.
A structured review of your sources, mappings and reconciliation risk, and an honest view of where the real problem sits. From £5,000, and the output is yours whether or not you go further.