%402x.svg)
A governed finance data warehouse for multi-entity groups, on any ERP, planning system and data platform, with controls that check the numbers on every load.
Controls & Data Quality, one load
Pass
Pass
Pass
Pass
Pass
3 items disclosed
Illustrative statuses for one load. Each control is computed against the warehouse on every load; names and definitions follow the Controls & Data Quality view.
At our largest finance reference, a global professional services group with 324 legal entities
The income statement and balance sheet on each ledger layer with the reconciliation control, and ERP revenue to consolidated revenue, leg by leg.
Statements & Reconciliation, Consolidated Revenue Bridge
Growth and profitability by entity, margin by department and office with the loss-makers in plain view, best and worst jobs with billing realisation, and where the return on capital comes from.
Group Performance, Department & Office P&L, Job & Client Profitability, Entity ROIC
Work in progress that ties to the general ledger and work never billed, receivables ageing with trade separated from intercompany, and payables by vendor tied to the control account.
Work in Progress, Receivables, Payables
Budget, forecast and actual side by side, variance by driver and the full-year outlook.
Budget, Forecast & Outlook
Six controls computed against the warehouse, and natural-language questions and variance commentary on the certified numbers.
Controls & Data Quality, with the AI layer on top. Tie-Out →
For manufacturers
The same layer carries SG&A with allocations, product and customer margin, order to cash and inventory. See all five areas →
Every team pulls its own extract from the ERP, so the same number has three values depending on who you ask.
Reports were built straight on raw tables, and when the auditor asks which transformation produced a figure, nobody can say.
An acquisition means months of mapping before the new business shows up in the group numbers.
The group already runs a data platform, and finance still does not sign from it. Every team has its own Excel jockeys, rebuilding the same numbers their colleagues in the next entity are rebuilding at the same time.
The ERP layer and the consolidation layer hold the same transactions, so adding them together counts every transaction twice. Layer integrity catches it.
A plain join on entities drops the elimination entities and overstates group revenue. Elimination integrity catches it.
Joining on the wrong account key moves amounts to the wrong lines. One conformed account key prevents it.
Leaving out the adjustments made in the group planning platform means the warehouse never matches the signed number. They load as their own ledger layer, reconciled and kept with their source.
Every ERP and the group planning platform load into the warehouse. A reconciliation control compares them on every load. Reports and the AI layer read only from the presentation layer, so each one starts from the same certified numbers.
Underneath, every entity carries the same code in every system, with one chart of accounts and column-level lineage generated by the build. Infrastructure is defined in code, every change moves through one deployment pipeline, and access runs on federated identity with no stored secrets. At our largest reference: 500+ tables from six systems, and the monthly full load from about 50 to about 12 hours.
An estimated 1,570 person-days of manual finance work taken back every year, direct ERP ingestion in place of a manual extract relay, and more than 80% of data objects shared across reporting domains. Read the case study →
Legal entity hierarchies mastered: 500,000+ master data records in 12 weeks, with zero trading disruption. For finance, that meant faster consolidation, KPIs comparable year on year and better financial planning. Read the case study →
The first release is the start. The same layer carries a catalogue of 33 use cases, from one master record for clients, vendors and entities to acquisition onboarding and automated tax reporting, each a small project with its own business case. Get all 33 use cases as a PDF →
Nothing needs replacing first.
SAP S/4HANA and ECC, Oracle Fusion Cloud ERP and E-Business Suite, Microsoft Dynamics 365, NetSuite, Infor, Sage and Maconomy, plus entities that still report on files.
OneStream, Oracle Hyperion and EPM Cloud, Anaplan, SAP BPC, Workday Adaptive Planning, CCH Tagetik, Board and Jedox.
CRM, warehouse management, project management, and HR and payroll, such as Salesforce, SAP EWM, Jira and Workday.
On-premise SQL Server or Oracle, Databricks, Snowflake, BigQuery, Microsoft Fabric, Azure Synapse and Amazon Redshift.
Two ways to build it. We build the governed layer on the platform you choose. Or we build the finance data products inside the platform you already run, in its data catalogue and its deployment pipeline, and test the platform itself independently.
The ones your group already runs. ERPs such as SAP, Oracle, Microsoft Dynamics 365 and NetSuite, planning systems such as OneStream, Oracle Hyperion and Anaplan, and data platforms on-premise or on Databricks, Snowflake, BigQuery and Microsoft Fabric. The layers, controls and deployment pipeline follow the same pattern on each.
You do. The hand-over includes the infrastructure code, the deployment pipeline, and the data catalogue and column-level lineage the build generates. The use-case catalogue then becomes your roadmap, and each item is a small project with its own business case.
Infrastructure is defined in code, every change moves through one deployment pipeline, access is federated with no stored secrets, and every load leaves an audit trail. Our largest reference was built to SOX requirements from day one.
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.
We map where each finance number is built today, and what one governed layer underneath it would take. Every engagement starts with a fixed-price assessment of four to twelve weeks, typically EUR 15k to 60k. You talk to Michał Dębski, co-founder. How the assessment works
