How to Consolidate Reporting Across Multiple ERPs Without Migrating Any of Them

29 Jul 2026 · 7 min read

Most multi-entity businesses do not choose their accounting systems. They inherit them.

A new acquisition brings Xero. The legacy entity has been on Dynamics for eight years. The Czech subsidiary runs on ABRA Flexi and nobody is going near it. Your US portco uses QuickBooks, your UK one uses Sage Intacct, and the newest deal came with a NetSuite instance that the previous owner had half-implemented.

You are not looking at a technology problem. You are looking at the reality of how groups grow.

The instinct is to solve it by standardising. Pick one ERP, migrate everyone onto it, and reporting becomes simple. In theory, yes. In practice, an ERP migration takes 12 to 24 months, costs more than the estimate, and disrupts the finance team of the entity going through it right when you need that team focused on the business. And when you are looking across four or five portcos, you do not have the bandwidth to run four or five migrations in parallel.

There is a faster path.

Most migrations get started because someone needs better reporting. The reporting problem is solvable without the migration.

You do not have to migrate anything

The alternative is not to standardise the systems. It is to standardise the data layer above them.

Each accounting system keeps running exactly as it does today. Xero stays Xero. ABRA Flexi stays ABRA Flexi. What changes is that each system feeds a single data platform, where your definitions of revenue, EBITDA, net debt, and working capital are applied once, consistently, across every entity.

Creditinfo Group did this across 30 markets. Each country runs whatever local accounting system it has, ranging from basic bookkeeping tools to full ERPs. Pulling all that data together, cleaning it, and making it consistently queryable took nine months. Now, when a question comes up in the boardroom about a specific metric in two different markets, the answer is ready in minutes, not a week. That is the ROI. Not the technology. The ability to answer questions in the room.

30

markets

Creditinfo Group entities connected

9 months

to unify all data

across the full group, from source to queryable

2 months

to deploy

from first connection to production

How it works in practice

The process has three parts.

First, you connect each accounting system. Keboola has pre-built connectors for the systems most commonly found across multi-entity groups. The portco does not change anything. All you need is read-only access to their system.

Second, you build the shared data model. Keboola brings a starting structure built from how similar groups typically work. What fits your entities goes in directly. What does not gets built to your exact definitions, because no two charts of accounts are the same. This is where your finance logic lives: how you define gross margin, how intercompany flows are handled, which cost centres map to which consolidated categories.

Third, the output goes wherever you need it. Keboola has its own reporting and dashboard layer. Or connect directly to Power BI, Tableau, or any BI tool your team already uses. LP reports, board packs, ad hoc questions from the investment team. One source, multiple consumers.

The accounting systems do not change. The people running them do not change. What changes is that you stop rebuilding the consolidation every month someone exports to Excel.

The accounting systems to connect

Each system below has a pre-built connector. If yours is not listed, it can likely still be connected via a direct database or API integration.

Xero

Common in UK, Irish, and APAC portfolio companies. Pulls accounts, invoices, bank transactions, and journal entries. If you have portcos running separate Xero organisations, all of them land in one consolidated dataset. For groups that need to push data back - invoices or payment records - that works too.

Sage Intacct

Most common in US mid-market portcos, particularly professional services and SaaS. Adapts to your specific instance configuration, so it works with however your Sage is set up rather than assuming a fixed module structure.

Microsoft Dynamics 365 Finance & Operations

Found in larger portcos in manufacturing, distribution, and logistics. Covers finance, accounting, production, and warehousing. You configure which legal entities feed your consolidated model.

Microsoft Dynamics 365 Business Central

Common in mid-size European and North American portcos. Pulls invoices, journal entries, and sales data across separate company environments and combines them in one view.

QuickBooks Online

The most common system in US portcos at earlier growth stages. Pulls Balance Sheet, Profit and Loss, Trial Balance, and General Ledger. Write journal entries back if your workflow requires it.

Oracle NetSuite

Common in growth-stage software and professional services companies. Connector in active development. OAuth authentication and incremental loading confirmed. Contact us for current availability.

Acumatica

Found in cloud-native mid-market portcos, often technology-forward businesses. Connects to invoices, journal transactions, financial periods, purchase orders, and customer records.

Odoo

Common in tech-forward portcos and European companies that chose a flexible modular ERP. Connects to any model in your instance across all Odoo versions.

ABRA Flexi (formerly FlexiBee)

The standard system in Czech and Slovak entities. Bidirectional: extract for consolidation, write back to create or update records from your consolidation process.

K2

Found in Central European manufacturing and distribution, often on-premises. Supports any K2 data object with parent-child hierarchy. On-premises instances connect via SSH tunnel.

Oracle E-Business Suite

Common in larger, more established portcos in manufacturing and complex enterprise environments. Extracts across General Ledger, Accounts Payable, Accounts Receivable, and more, with multi-org filtering for single EBS instances running multiple legal entities.

Helios Inuvio and Helios Easy

Czech ERP, relevant for any fund with Central European portcos. Connects to any data view the system exposes. Bidirectional. Beta.

Money S3

Czech and Slovak accounting (Seyfor). Common in smaller or mid-size Czech portcos. Pulls invoices, journals, and accounting records. Bidirectional. Beta.

UOL (Účetnictví online)

Czech cloud accounting. Invoices, orders, bank movements, accounting records. Bidirectional.

Oracle Hyperion

Some portcos already run Hyperion as their consolidation layer. If that is the case, Keboola can extract from it rather than from the underlying ERPs directly.

From ERP list to portco overview

Connecting your accounting systems is the first step. What you get from it depends on what you build on top.

The most common starting point is a monthly portco overview: revenue, EBITDA, net debt, and working capital across every entity, updated automatically when the source systems close the month. No manual exports, no consolidation spreadsheet someone has to run.

From there, the same data supports two directions.

Upward: board packs, LP reports, exit models - the numbers trace to source, so you can defend any figure without going back to the portco.

Downward: when a number looks off, you drill to the journal entry it came from, not to a summary someone else prepared.

Some groups go further and connect financial data to operational metrics from within each portco - sales data, headcount, utilization - so the monthly review covers the full picture, not just the accounting view. That connection lives in the same place as the financial consolidation. You are not building a separate analytics layer. You are adding to the one you already have.

Common questions

We have two portcos on Xero and one on Sage Intacct. Can Keboola consolidate all three?

Yes. Each system connects independently and feeds into the same shared model. You define the common data model once, and it applies to all three sources.

Where chart-of-account mappings differ between entities, you handle that in the mapping layer, with full transparency on what maps to what.

Do we need to standardise chart of accounts first?

You do not need to standardise before connecting. Many groups build the cross-entity CoA mapping inside Keboola as a lookup table, maintained by finance, version-controlled and auditable.

It is one of the first things we build with you, and it tends to surface discrepancies in the existing chart of accounts that would not have been visible otherwise.

What about ERPs/systems that are not on this list?

If your entity runs on a system with a database or an API, it can be connected. Keboola has a generic database connector (PostgreSQL, MySQL, Oracle, MSSQL, Snowflake, Redshift) and supports custom REST and FTP integrations. If you are dealing with a system that exports CSV or Excel, that is also connectable.