The short answer
To report across portfolio companies that run different ERPs, you do not need to replace their systems first. Pull data from each ERP on a schedule, map every company’s accounts to one standard chart of accounts, define each KPI once, and build dashboards and monthly packs on that shared layer. Most holding companies can get consolidated, comparable reporting this way in weeks or months instead of years.
Key takeaways
- Buy-and-build strategies guarantee a mix of ERPs. Plan reporting around that, not against it.
- A connected reporting layer delivers consolidated numbers far sooner than an ERP consolidation.
- Chart of accounts mapping and shared KPI definitions matter more than the dashboard tool.
- Build a repeatable onboarding playbook so every add-on joins reporting quickly.
- Reconcile to each company’s own financials before anyone trusts the roll-up.
If your portfolio grows by acquisition, you already know the pattern. Each new company arrives with its own ERP, its own chart of accounts and its own idea of what gross margin means. Month end turns into a scramble of exports, emails to portfolio CFOs and spreadsheets stitched together by hand.
That pattern is not going away. Add-on deals made up 75.9% of all U.S. private equity buyout activity in Q1 2024, according to PitchBook. Every add-on is another system to report from, so the reporting approach has to scale with the deal pace.
Why is portfolio reporting so hard when every company runs a different ERP?
Because the systems disagree on structure, timing and definitions, not just on software. Two companies can both use a well-known ERP and still be impossible to compare.
- Different charts of accounts. One company books freight in cost of goods sold, another in operating expenses.
- Different KPI definitions. EBITDA adjustments, backlog and utilization are calculated differently in each business.
- Different close calendars. Some close in five days, some in fifteen, so the roll-up waits on the slowest one.
- Different data access. Cloud ERPs have APIs, older on-premise systems may only offer exports.
- Manual assembly. The holding company finance team rebuilds the same pack every month by hand, which is where errors creep in. We cover that cycle in why your companies still run on five versions of the same spreadsheet.
Do you need to move every company onto one ERP first?
No. ERP consolidation can be the right long-term goal, but it is slow, expensive and disruptive, and reporting should not wait for it. Most portfolios are better served by connecting systems first and consolidating selectively later.
| Approach | Best when | Time to reporting | Tradeoff |
|---|---|---|---|
| Connect existing ERPs to a shared reporting layer | Companies run different systems and you need consolidated numbers now | Weeks to months | Requires good mapping and ongoing upkeep of connections |
| Standardize charts of accounts and KPI definitions | Numbers roll up but comparisons mislead | Months, done in stages | Needs buy-in from each portfolio CFO |
| Consolidate onto one ERP | Companies are merging operations, not just ownership | Many months to years per company | High cost and disruption during cutover |
The three are not either-or. Connecting systems gives you reporting now, standardizing definitions makes it trustworthy, and consolidation can follow where it makes operational sense.
How does a multi-ERP reporting layer work?
It works by moving each company’s data into one place on a schedule, translating it into a common structure, and reporting from that structure instead of from each ERP directly.
- Extract. Pull general ledger, AR, AP and key operational data from each ERP through an API, connector or scheduled export.
- Map. Link every company’s accounts to a standard reporting chart of accounts. Chart of accounts mapping is the step that makes companies comparable.
- Define. Write down each KPI once, including adjustments, and apply it the same way to every company.
- Reconcile. Tie the mapped numbers back to each company’s own financial statements every month so leadership trusts the roll-up.
- Report. Build consolidated dashboards, company drill-downs and board or lender packs that refresh automatically.
The connections are usually integration work, and the model, dashboards and packs are data, analytics and BI work. Tools like Power BI are common for the reporting layer, but the mapping and definitions are what make it useful.
Running monthly portfolio reporting out of spreadsheets? Book a working session and we will map your systems and the fastest path to one view.
What should a consolidated portfolio dashboard show?
It should show the few numbers the deal team and boards actually use, consistently defined, with the ability to drill from the total into each company.
- Revenue, gross margin and EBITDA by company and in total, against budget and prior year
- Cash, cash conversion and working capital trends
- Covenant and lender metrics with early warnings
- Two or three operational drivers per business, such as backlog, utilization or same-store sales
- Data freshness, so everyone can see which companies have closed the month
Margin by product and customer is often the next layer once the basics are in place. We walk through it in building a margin by product and customer report.
How do you bring a new add-on into reporting quickly?
Treat reporting onboarding as a standard step in every acquisition, with a checklist and an owner, rather than a project that starts after the integration team frees up.
| Timing after close | Reporting step |
|---|---|
| First weeks | Get ERP access, identify the finance contact, collect the chart of accounts |
| First month | Map accounts to the standard chart and agree on KPI definitions |
| First two months | Load history, reconcile to the company’s own financials |
| First quarter | Company live in consolidated dashboards and monthly packs |
Companies on an ERP you already connect to move fastest, because the pipeline exists and only the mapping is new. Fixing the close process and handoffs behind the numbers is business performance and operations work, and it often shortens the whole monthly cycle. The handoff can start before close: a deal pipeline that already records each target’s systems and finance contacts makes onboarding faster, as covered in what an M&A pipeline dashboard should show.
What usually goes wrong with multi-ERP reporting?
Most failures come from skipping definitions and reconciliation, not from the technology.
- Building dashboards before agreeing on definitions. Pretty charts with inconsistent numbers lose trust fast.
- No reconciliation. If the roll-up does not tie to each company’s statements, CFOs will keep their own spreadsheets.
- One-off mapping. Mappings must be maintained as companies add accounts, or reports drift.
- Trying to automate everything at once. Start with one or two companies, prove the model, then roll it out.
- No clear owner. Someone has to own the KPI definitions and the monthly pack.
Our process starts with the definitions and one or two companies before scaling. You can see how this applies to holding companies on our private equity and holding companies page, and to businesses with many sites on our multi-location organizations page.
Frequently asked questions
Can you get consolidated reporting without putting every company on the same ERP?
Yes. Data is pulled from each company’s ERP, mapped to a shared chart of accounts and shared KPI definitions, and combined in a central reporting layer. Most holding companies get consolidated dashboards and monthly packs this way in weeks or months, long before any ERP consolidation would be finished.
What is chart of accounts mapping?
Chart of accounts mapping links each company’s general ledger accounts to one standard set of reporting accounts. It lets revenue, cost of goods sold, operating expenses and adjustments roll up the same way for every company, even when their ledgers are structured differently. It is the foundation of comparable portfolio reporting.
What tools are used to build multi-ERP portfolio reporting?
A typical setup uses connectors or scheduled exports to pull data from each ERP, a central database or data warehouse to store and map it, and a BI tool such as Power BI for dashboards and monthly packs. The right mix depends on the systems involved, data volumes and who needs to maintain it.
How do you onboard a newly acquired company into portfolio reporting?
Start with access to its ERP and a map of its accounts to your standard chart within the first few weeks. Load history, reconcile it to the company’s own financials, then add it to the dashboards and packs. Companies on an ERP you already connect to go fastest because the pipeline already exists.
Who should own portfolio reporting at a holding company?
Usually the holding company or fund finance team owns the definitions and the monthly pack, with each portfolio CFO accountable for timely close and clean mappings. Technical upkeep can sit with an internal data person or an outside partner. Clear ownership of KPI definitions matters more than where the tools live.
