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.
Once every entity is connected, you can handroll upwards and consolidate from each add-on to the platform, and from the platform to the fund, without anyone re-keying a figure along the 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, 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 manual steps to every reporting cycle that follows:
- Another system to pull from. Three acquisitions can easily mean five ERPs. We've seen a single portfolio company running 15, five of them no longer in service, with the history still needed for reporting.
- 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 version of the truth. One entity's EBITDA includes adjustments another's doesn't. ARR is defined three different ways. Until the definitions are standardized, the numbers can't be added up, let alone 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 numbers to check. Every new entity is another set of figures someone has to validate, reconcile against last month and chase when they look wrong.
| With every add-on | Done by hand | Connected once |
|---|---|---|
| A new ERP | Exports requested every month, usually by email | Pulled automatically by API or scheduled file |
| A new chart of accounts | Re-mapped in a spreadsheet each cycle | Mapped once at onboarding, applied on every pull |
| New metric definitions | Reconciled line by line before each pack | Standardized once, consistent across every entity |
| Another close calendar | Chased until the last entity reports | Pulled on schedule after each entity closes |
| More board pack pages | Numbers re-keyed into slides | Generated from one consolidated layer |
Headcount grows in a straight line, when the budget allows. The manual work grows with every entity, every system and every month. 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.
Templates that don't stay templates. Funds send portfolio companies a standard workbook to fill in. The companies change the formatting, overwrite the formulas or send back something different, and the finance team spends the next week chasing and correcting before anything can be consolidated.
Packs that are out of date on arrival. When it takes three weeks to build a board or steering committee pack, the conversation in the room is about numbers that are already a month old.
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, map the new system's chart of accounts before the switch. Reporting then carries on from the old system's last close to the new system's first, so there's no blind spot while the migration happens.
- 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, another chart of accounts, another close calendar and its own definitions of metrics like revenue and EBITDA. Someone has to pull, map, check and consolidate all of it by hand, so 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. Map the new system's chart of accounts before the switch, so reporting carries on from the old system's last close to the new system's first, with no gap while the migration happens.
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.
