Skip to main content

Expertise Pillar

Multi-Entity Consolidation

Extract from any system, standardize to a common data model, report in any currency. Multisource reporting that decouples your group view from source systems — enabling seamless migration at zero transfer cost.

01

Data Governance & AI Readiness

Daily data operations — quality gates, verification, reconciliation

02

Reporting Infrastructure

Governed baseline — KPIs, packs, cadence

03

Performance & Profitability

Driver attribution — margins, variance, decisions

04

Planning & Projections

Forward view — forecasts, scenarios, driver-based planning

Each layer builds on the one above — governance is the foundation
  • Any-system, any-currency reporting

    Report in any currency from any combination of source systems. The common data model makes the source irrelevant — SAP, Navision, Pohoda, or spreadsheets all produce the same standardized output.

  • Zero-cost system migration

    When you change ERPs, only the extraction layer changes. The data model, reports, dashboards, and consolidation logic remain untouched. No rebuilding, no re-mapping, no lost history.

  • Close cycle compression

    Because data is standardized daily into the common model, the month-end close becomes a confirmation, not a construction project. From 20-day manual consolidation to real-time.

How multisource reporting works
Stage 1

Extract Raw Data

SAP · Navision · Money S5 · Pohoda · Banking · Spreadsheets

Different formats · Different structures · Different currencies

The core

Onetribe Common Data Model

Every source standardized to one structure

✓Chart harmonisation
✓Currency normalisation
✓Intercompany tagging
✓Quality validation
Stage 3

Unified Reporting

Group P&L/BS · Any-currency output · Segment views · Rolling forecasts

Migrate any source system — zero transfer cost
Add entities in days, not months
Any system, any currency, one truth
What goes wrong without this

The gaps this discipline closes.

Each new entity adds weeks to close

Multi-entity groups consolidate manually. Each acquisition or new subsidiary adds days to the monthly close. Group visibility arrives too late for real-time steering.

One person, one spreadsheet, one risk

The consolidation workbook that only one person understands. When they are unavailable, the group close stops. The knowledge is in the person, not the infrastructure.

Multi-currency handled with manual adjustments

FX translation done in spreadsheets with rates copied from websites. Translation differences allocated by judgement. Restatement required when errors surface weeks later.

The control system

The Consolidation Control System

Six capabilities that turn fragmented entity data into a unified, trustworthy group view. Each requires both IT infrastructure skill and financial domain expertise — the combination is what makes consolidation reliable.

1

Multi-System Integration

Connecting diverse ERPs, accounting systems, banking platforms, and operational tools into a single data pipeline. Not a one-time migration — a permanent, governed integration layer that handles schema differences, timing mismatches, and data format variations automatically.

We have connected 12+ ERP systems across 74 legal entities. Each integration is built to handle the specific quirks of that system — SAP exports differently from Money S5, which exports differently from Pohoda. The IT expertise is in making these connections reliable. The financial expertise is in knowing what the data should look like when it arrives.

2

Chart of Accounts Harmonisation

Every entity has its own chart of accounts shaped by local regulations, historical decisions, and system constraints. Harmonisation creates a unified reporting structure without forcing entities to change their local accounting — a mapping layer that translates local reality into group truth.

This is where financial expertise matters most. Mapping a local Slovak chart to a group reporting structure requires understanding what each account means in context — not just matching codes. A 'revenue' account in one entity might include intercompany sales that must be eliminated. Getting the mapping wrong corrupts every consolidated number downstream.

3

Intercompany Elimination

Automated matching and elimination of intercompany transactions — receivables against payables, revenue against cost, transfers against receipts. Discrepancies flagged and resolved before they reach the consolidated view.

In a group with 10+ entities, intercompany transactions can number in thousands per month. Manual elimination is where consolidation breaks down — mismatches accumulate, timing differences create phantom variances, and the reconciliation consumes days of effort. Automation with financial logic eliminates this bottleneck entirely.

4

Multi-Currency Management

Transaction currency, functional currency, reporting currency — each requiring different translation logic. Spot rates, average rates, historical rates applied correctly by account type. FX translation differences calculated and allocated automatically.

Currency is where many consolidation tools fail mid-market groups. A Czech subsidiary reporting in CZK, a UK entity in GBP, and a Hungarian entity in HUF — each needs different rate treatment for P&L vs balance sheet items. We handle this at the infrastructure level so the consolidated EUR view is always correct and traceable.

5

Consolidation Automation

Automated daily consolidation runs — data extraction, validation, harmonisation, elimination, currency translation, and publication. Each step governed by quality gates. The consolidated view is produced as a by-product of the daily data discipline, not as a month-end project.

When consolidation runs automatically every day, the month-end close becomes a confirmation, not a construction project. The finance team reviews and signs off rather than building from scratch. This is what compresses a 20-day close to real-time — the work happens continuously, not in a burst.

6

Group Reporting Layer

Consolidated views by segment, region, entity, and any dimension the group needs to manage. Drill-down from group totals to entity-level detail without leaving the reporting environment. Every number traceable from consolidated output back to source entity and transaction.

The group reporting layer is where IT infrastructure and financial expertise converge. The infrastructure delivers the data reliably. The financial expertise structures it around what management actually needs to decide — contribution by business unit, performance by geography, cash position by entity. Without both, you get either unreliable data or irrelevant reports.

Common questions

Frequently Asked Questions

What is multi-entity consolidation?

Multi-entity consolidation is the process of combining financial data from multiple legal entities — often across different systems, currencies, and jurisdictions — into a single, unified group view. It requires both IT infrastructure (connecting diverse systems reliably) and deep financial expertise (harmonising charts of accounts, eliminating intercompany transactions, handling currency translation correctly).

How many systems and entities can you consolidate?

There is no practical limit. We currently consolidate data across 74 legal entities using 12+ different ERP and accounting systems, in 11 countries and multiple currencies. The infrastructure is designed to scale — adding a new entity or system is a configuration task measured in days, not a project measured in months.

How does this differ from ERP consolidation modules?

ERP consolidation modules work within their own ecosystem. If your group runs SAP, Navision, Money S5, and Pohoda across different entities, no single ERP module can consolidate across all of them. We operate above the ERP layer — connecting any system, applying governed harmonisation rules, and producing a consolidated view that no single-vendor tool can deliver.

Read the full framework

Detailed descriptions, quality metrics, governance areas, and system connections

Any System, Any Currency, One Truth

The core problem in multi-entity reporting is not connecting systems. It is that every system produces data in its own format, its own chart of accounts, its own currency — and there is no shared standard between them.

Our approach: extract raw data from any source, standardize it to the Onetribe Common Data Model, and feed a unified reporting cycle. This three-stage process decouples your group reporting entirely from the source systems underneath. The consequences are significant:

  • Report in any currency from any system. Once data is standardized, the source is irrelevant. A Czech entity in Pohoda and a UK entity in SAP produce the same structured output.
  • Migrate systems at zero transfer cost. When you replace an ERP, only the extraction connector changes. The data model, all reports, dashboards, consolidation rules, and historical data remain untouched.
  • Add entities in days, not months. A new acquisition means configuring one extraction connector and one chart mapping — not rebuilding the consolidation from scratch.

What Multisource Standardization Produces

  1. Any-system, any-currency reporting: Management sees a unified group view in any reporting currency — regardless of which ERPs, accounting systems, or data sources the entities use.
  2. Zero-cost system migration: Because reporting is decoupled from source systems, ERP changes are an extraction-layer task. No downstream impact.
  3. Close cycle compression: Data standardized daily means the close is a confirmation, not a construction project. From 20 days to real-time.

Key Business Questions

  • Can we report the group in any currency, from any combination of systems? If the answer depends on which ERP each entity runs, your reporting is coupled to the source — and will break with every system change.
  • What happens when we replace an ERP? If migration means rebuilding reports and consolidation logic, the cost is not in the new system — it is in everything connected to the old one.
  • How quickly can we onboard a new entity? If each acquisition adds permanent days to every future close, the infrastructure cannot scale.
  • Can we drill from group totals to entity-level transactions? If the consolidated number cannot be traced back to source, it cannot be defended.
  • Is the group view independent of the source systems? If not, you need a common data model layer — not a module within one vendor’s ecosystem.

The Consolidation Control System

Consolidation is not a month-end task. It is a continuously operating infrastructure — six capabilities that turn fragmented entity data into a unified, trustworthy group view. Each requires both IT infrastructure skill and financial domain expertise.

1) Multi-system integration

Connecting diverse ERPs, accounting systems, banking platforms, and operational tools into a single governed data pipeline. We have integrated 12+ systems across 74 entities — SAP, Navision, Money S5, Pohoda, Helios, and others. Each system has its own export formats, timing patterns, and data structures. The integration layer handles these differences automatically, daily, with governed quality gates.

2) Chart of accounts harmonisation

Every entity has its own chart of accounts. Harmonisation creates a unified reporting structure without forcing entities to change local accounting — a mapping layer that translates local reality into group truth. This is where financial expertise is irreplaceable: mapping requires understanding what each account means in business context, not just matching codes.

3) Intercompany elimination

Automated matching and elimination of intercompany transactions — receivables, payables, revenue, cost, transfers. In groups with 10+ entities, intercompany transactions number in thousands per month. Manual elimination is where consolidation breaks down. Automated elimination with financial logic removes this bottleneck entirely.

4) Multi-currency management

Transaction, functional, and reporting currencies — each requiring different translation logic. Spot rates, average rates, historical rates applied by account type. FX translation differences calculated and allocated automatically. This is where many tools fail mid-market groups: entities in CZK, GBP, HUF, PLN, and EUR each need correct rate treatment for P&L versus balance sheet items.

5) Consolidation automation

Daily automated consolidation — extraction, validation, harmonisation, elimination, currency translation, publication. Each step governed by quality gates. The consolidated view is a by-product of the daily data discipline, not a month-end project. When consolidation runs daily, the close becomes a confirmation, not a construction project.

6) Group reporting layer

Consolidated views by segment, region, entity, and any management dimension. Drill-down from group totals to entity-level transactions without leaving the reporting environment. Every number traceable from output to source. The layer where IT infrastructure and financial expertise converge — reliable data structured around what management needs to decide.

The Common Data Model Advantage

The common data model is the architectural decision that makes everything else possible. Instead of building consolidation logic that depends on specific source system formats, we standardize all data into a single, governed structure first — then build everything on top of that structure.

This means:

  • Reports are system-agnostic. A dashboard built on the common model works identically whether the underlying entity runs SAP, Pohoda, or a spreadsheet. The report never knows or cares about the source.
  • Historical continuity survives system changes. When an entity migrates from one ERP to another, the historical data in the common model remains unchanged. Trend analysis, year-over-year comparisons, and audit trails are unaffected.
  • Consolidation rules are defined once. Intercompany elimination, currency translation, chart harmonisation — all defined at the common model level. Adding a new source system does not require redefining any consolidation logic.
  • Quality gates operate uniformly. Every data source passes through the same validation, regardless of origin. A missing intercompany tag is caught the same way whether the data comes from Navision or a manual upload.

System Migration at Zero Transfer Cost

This is perhaps the most underappreciated benefit of the common data model. In a traditional setup, replacing an ERP triggers a cascade: reports need rebuilding, consolidation mappings need redefining, historical data needs migrating, dashboards need reconnecting. The ERP cost is often the smallest part of the project.

With the common data model, an ERP migration means one thing: building a new extraction connector. The data model does not change. The reports do not change. The consolidation rules do not change. The dashboards do not change. Historical data remains in place because it was already standardized.

We have done this in practice — migrating entities between ERPs while group reporting continued uninterrupted. The finance team did not notice the technical change because their reporting layer was completely decoupled from the source system.

Why Both IT and Financial Expertise Matter

Building and maintaining the common data model sits at the intersection of two disciplines, and most approaches fail because they lean too far in one direction.

IT-only approaches can connect systems and move data into a shared structure. But they cannot tell you whether the chart mapping makes financial sense, whether intercompany elimination is complete, or whether the FX translation method is correct for each account type. The model exists — but the financial integrity is not verified.

Finance-only approaches understand what the common model should contain. But they cannot build the extraction connectors, automate the daily standardization, or scale beyond a handful of entities. The logic is correct — but the infrastructure cannot sustain it.

What we provide is both, operating together. Finance professionals who can build and govern the data model and the IT infrastructure that feeds it. This combination is why we standardize data from 12+ systems across 74 entities daily — because the people operating the infrastructure understand both the technology and the financial logic.

How Consolidation Connects to the Four Disciplines

Multi-entity consolidation is not a separate discipline — it is the cross-cutting infrastructure that makes each of the four disciplines work at group level:

  • Data Governance — quality gates, daily verification, and reconciliation operate across all entities simultaneously. Governance at the entity level is necessary; governance at the group level is what we deliver.
  • Reporting Infrastructure — the consolidated view IS reporting. Close cadence, pack structure, and KPI frameworks all depend on consolidation producing a trusted group baseline on time.
  • Performance & Profitability — driver attribution across entities, segments, and geographies requires consolidated data. Without it, performance analysis stops at entity boundaries.
  • Planning & Projections — group-level forecasting requires consolidated actuals. Rolling forecasts and scenario planning across entities depend on the consolidation layer feeding them current, harmonised data.

Typical Situations

  • An acquisition adds a new entity running a different ERP, and the group close extends by five days every month because the chart of accounts does not map — not a one-time effort but a permanent addition to every future cycle
  • The consolidation workbook has grown over years and only one controller understands it. When they take leave, the group close is delayed or simplified to the point where management cannot trust the numbers
  • Multi-currency entities are consolidated using rates manually copied into spreadsheets. Translation differences are allocated by judgement. An auditor questions the methodology and the team spends a week reconstructing the logic
  • A board member asks for revenue by business segment across all entities. The answer takes three days to produce because the segment definitions are not harmonised across entity-level charts of accounts
  • The group adds entities faster than the consolidation process can absorb them. Each new entity means more manual work, longer closes, and increasing fragmentation risk

See It in Practice

Next Steps

Let's go!

Running multiple entities across multiple systems?

We consolidate groups across any combination of ERPs, accounting systems, currencies, and jurisdictions — daily, not monthly. Start with a conversation about your setup.

Discuss your situation