Quick Answer
The fastest way to consolidate portfolio data for board meetings is to stop collecting the numbers by hand. Connect each entity's ERP directly, map every chart of accounts once to one standard set of metrics, and build the board pack from that consolidated layer instead of from spreadsheets. One US roll-up with 30 entities cut board pack preparation from three and a half weeks to a day this way.
The add-on lands on the CFO's desk
The deal team closes the add-on. The press release goes out. And on Monday morning, the platform CFO inherits another entity to consolidate.
It rarely arrives tidy. It comes with its own ERP (often QuickBooks), its own chart of accounts, its own month-end routine and its own idea of what "revenue" means. The board still expects one pack, on the same date as last quarter.
That's the quiet problem with a buy-and-build strategy. Every acquisition adds work to the reporting process faster than it adds people to do it. Finance teams grow one hire at a time. Reporting complexity multiplies.
Why complexity outruns headcount
Adding an entity doesn't add one more line of work. It adds a new set of connections to everything already there:
- Another system to pull from. Three acquisitions can easily mean five ERPs, because the platform is often mid-migration while the add-ons are still on whatever they ran before the deal.
- Another chart of accounts to map. Each entity's codes have to land on the same revenue, COGS, S&M, R&D and G&A lines before anything can be compared.
- Another close to wait for. Every entity closes on its own timetable, and the consolidated pack can only move as fast as the slowest one.
- More relationships between entities. Intercompany activity grows with the number of pairs, not the number of companies. Three entities make three possible pairs. Seven make 21. Twenty make 190.
- More lines in the board pack. Every new entity is another set of numbers someone has to check before the pack goes out.
| Entities in the group | Possible intercompany pairs |
|---|---|
| 3 | 3 |
| 5 | 10 |
| 7 | 21 |
| 10 | 45 |
| 20 | 190 |
Headcount grows in a straight line, when the budget allows. The work grows faster. That gap is where board packs slip, and where finance teams end up re-keying the same numbers into spreadsheets every quarter.
What we hear from roll-up teams
We speak to platform CFOs and operating teams every week. The details change, but the pattern doesn't.
Add-ons arrive unfinished. Many of the companies a platform buys are early in their finance maturity: QuickBooks, light accounting processes, and important data sitting in email or old local databases. Bringing them into a consolidated board pack is a project before it's a report.
A patchwork of ERPs, and no one to build the pipes. It's common to find QuickBooks, Acumatica and NetSuite in the same portfolio. Consolidation ends up in manual Excel templates, because the team has no spare engineering time to build and maintain integrations.
Tools layered on tools. Some platforms respond by stacking BI and data warehouse tools to make consolidation work. Each layer adds friction, and board packs still go out late.
The view from the portfolio company. Finance teams at acquired companies feel it too. Their biggest worry is usually being asked to feed one more system, or having numbers pulled before month-end close is finished.
The fastest way to consolidate portfolio data for board meetings
The fastest way is to stop collecting the numbers by hand. Connect each entity's systems once, map every chart of accounts to one standard set of metrics, and build the board pack from that consolidated layer instead of from spreadsheets.
In practice, that comes down to five steps:
- Connect every ERP directly. QuickBooks, Xero, NetSuite, Acumatica: each entity's system feeds in by API. Where there's no API yet, a scheduled file export (Excel, CSV or SFTP) fills the gap so nothing waits on a build.
- Map each chart of accounts once. Every entity's codes are mapped to the same reporting lines when it joins. After that, the mapping runs on every pull without anyone touching it.
- Pull on the close calendar. Schedule pulls for after each entity closes (from the fifth working day, say) so nobody sees revenue numbers before month-end is done.
- Keep reporting through migrations. If an add-on is moving from QuickBooks to NetSuite, connect both. Data keeps flowing from the old system until the new one goes live, so there's no blind spot in the first 90 days.
- Generate the pack from the consolidated layer. The board pack, LP report and dashboards all draw from the same numbers, with an audit trail back to source.
The difference shows up in the calendar. One US roll-up with 30 entities used to spend three and a half weeks of FP&A time producing its board packs. With every ERP and CRM connected, it now takes a day.
It also changes what happens on the next deal. A new add-on becomes a mapping exercise, not a new monthly reporting process.
Make the next add-on easier than the last
Roll-ups create value by adding companies. The reporting shouldn't get harder every time they do.
If you're a platform CFO or operating partner, it's worth asking a simple question before the next deal closes: how many manual steps sit between each entity's ledger and the board pack? Count them. That's the work that grows with every acquisition.
Related Reading
How Funds Get Operational Data Live
From Static Exports to Live Answers: How Planr DataThread Keeps Claude Current
Frequently Asked Questions
What's the fastest way to consolidate portfolio data for board meetings?
Connect each entity's ERP directly, map every chart of accounts once to a standard set of metrics, and generate the board pack from that consolidated layer. One US roll-up with 30 entities cut board pack preparation from three and a half weeks to a day this way.
Why does reporting get harder with every acquisition?
Each add-on brings another system, chart of accounts and close calendar, and intercompany relationships grow with the number of pairs of entities. The work grows faster than the finance team.
When should a roll-up replace spreadsheets for portfolio reporting?
When each add-on means another manual consolidation step, or when the board pack takes weeks to build. At that point, connecting each entity's systems saves more time with every acquisition.
What if an acquired company has no modern ERP or API?
A scheduled file export (Excel, CSV or SFTP) can feed the same consolidated layer until a direct connection is in place.
Can we keep reporting while an add-on migrates ERPs?
Yes. Connect both the old and new system so data keeps flowing until the switch, with no gap in the first 90 days.
Will portfolio company finance teams have to update another system?
Very little. Finance and CRM data are pulled from the systems they already use, on a schedule set around their month-end close. The aim is fewer data requests from the fund, not more.
