Industries · Multi-entity holdings
Every subsidiary reports. The group still can't see.
Holding companies rarely have a data problem at the subsidiary level — each operating company knows its own numbers. The problem is the group: different systems, different definitions, different close dates, and a consolidation that takes weeks to assemble and is out of date the moment it lands.
Before and after
What changes when
the data finally talks.
Today's friction
- Group consolidation assembled by hand, weeks after period end
- Every subsidiary on a different stack, with no shared definitions
- The same metric meaning something different in each operating company
- Inter-company transactions reconciled manually, late, and in dispute
- Board packs built from submitted spreadsheets nobody can audit back
- No group-level view between close cycles
With Ontilus
- Consolidated group position available continuously, not at period end
- Each subsidiary keeps its own stack; consolidation happens in the data layer
- One definition per metric, agreed once and enforced everywhere
- Inter-company entries matched and posted automatically
- Board packs generated from governed data with lineage back to source
- A group view any day of the month, not only after close
What we build
Engineered for Multi-entity holdings.
Every system is bespoke to your entity structure. These are the modules this sector almost always needs.
Group consolidation
One position across every operating company, built from source data rather than submitted spreadsheets.
Metric governance
One definition per metric, agreed once and applied identically across every subsidiary.
Inter-company reconciliation
Matching entries identified and posted automatically, with exceptions raised rather than absorbed.
Subsidiary scorecards
Each operating company against its own plan and against its peers, on comparable terms.
Board reporting
Board and investor packs generated from governed data, with lineage from every figure back to source.
Entity-level isolation
Hard separation between legal entities — group reporting served from aggregates, not shared tables.
Questions
Multi-entity holdings,
answered.
The questions operators in this sector ask first. If yours isn't here, ask us directly — we answer scoping questions before there's a contract in sight.
Talk to usDo all our subsidiaries have to move onto one system?
No, and that is the point. Forcing a migration on every operating company is what makes group consolidation projects fail. Each subsidiary keeps the stack it runs on; consolidation happens in the data layer above them.
How do you consolidate when every company defines metrics differently?
Definitions are agreed once, at group level, and enforced in the data layer — including the awkward ones like where a period boundary falls and what counts as revenue. That agreement is most of the work; the integration is the easy half.
Can the group see subsidiary data without subsidiaries seeing each other?
Yes. Isolation between legal entities is architectural rather than a filter on a shared table, access is role-scoped, and group-level reporting is served from governed aggregates. Every access event is logged.
What about subsidiaries on legacy or on-premise systems?
Where there is an API or webhooks we integrate directly. Where there is not — older on-premise finance and operations systems — we deploy local sync agents and batch ETL. Neither case blocks the rollout.
How long before the group has a consolidated view?
Discovery runs three weeks, working software follows from week four, and a group-wide system is live in twelve, with hypercare after go-live. We validate against numbers your finance team already reports before anything scales.
How we deploy
Live in 12 weeks.
Proven before it scales.
We pilot on one entity and validate against your own close reports before anything goes group-wide. See the full deployment approach →