The Multi-ERP Problem: Why Most Consolidation Tools Break Down in Real-World Group Structures

Here is the ERP reality for a mid-sized PE portfolio or industrial group. Entity one runs Tripletex, acquired before the current management team. Entity two runs Business Central, migrated two years ago. Entity three, acquired last quarter, runs Fortnox. Entity four still uses Visma Net from before the restructuring. A fifth entity is being acquired and runs SAP.

This is not an edge case. It is the norm. Groups accumulate ERP systems over time through acquisitions, organic growth, and historical decisions made by people who are no longer there. No CFO chose this landscape deliberately. They inherited it.

Most consolidation platforms were designed with a more controlled assumption: that the group runs on a small number of compatible systems, or that standardisation can be completed before the platform goes live. For groups with homogeneous stacks, this works. For groups with heterogeneous stacks — the majority of PE portfolios and multi-entity industrial groups — it creates a fundamental problem.

Standardisation-first architecture means every new entity triggers a mapping project. A PE firm acquiring a company each quarter cannot absorb a four-to-six-month implementation cycle per acquisition. The math simply does not work. So the firm stays in Excel, consolidates manually, and accepts the information lag as an operational cost.

Genuine heterogeneity support requires a different architectural approach. Rather than requiring each entity's ERP to conform to a standard structure before data can flow, the platform must connect to systems as they are and operate at the level of financial logic — which is consistent across ERPs — rather than at the level of ERP syntax, which is not.

This means account mapping runs on financial behaviour, not account codes. It means intercompany matching operates on transaction logic, not on system-specific identifiers. It means a new entity can connect its ERP and contribute to consolidated financials within hours, not after a standardisation project.

Corvenia is live across 51 subsidiaries spanning multiple ERP systems. The architecture was designed for this reality from the ground up — not retrofitted to handle it.

→ Read the full analysis:

‍Why AI-Native Architecture Is the Only Way to Automate Intercompany Eliminations Across Multiple ERPs