Resources·for PE firms
Consolidated reporting across a multi-country portfolio
The practical mess of comparing portfolio companies that report under different national charts of accounts, and why standardized KPI definitions matter more than standardized accounting.
A European portfolio rarely shares one accounting standard. A German portco reports under HGB. A French one maps to the Plan Comptable Général. An Estonian company follows local RTJ conventions. A Luxembourg add-on runs on a PCN 2020 chart its bookkeeper set up years before the fund was involved. None of this is unusual, and none of it is a problem that needs fixing directly.
The problem shows up one level up: when the fund tries to put these companies side by side in a single portfolio KPI table, and the numbers don't mean the same thing even when the labels match.
Why standardizing the accounting is the wrong first move
The instinctive fix, getting every portco onto the same chart of accounts or the same accounting software, is expensive, slow, and usually unnecessary.
the constraint
Statutory reporting is local by law
Each portco still has to file statutory accounts under its local standard, work with a local auditor, and satisfy local tax authorities. Ripping out an established local chart of accounts creates real risk for no reporting benefit.
the cost
Migration projects rarely pay for themselves
Moving a portco onto a new chart of accounts or new accounting software is a multi-month project with real disruption risk to the local finance team, all to solve a problem that sits at the portfolio level, not the entity level.
What actually needs standardizing: KPI definitions
The fund doesn't need every portco's ledger to look the same. It needs a small set of portfolio-level KPIs defined identically everywhere, regardless of what the underlying chart of accounts looks like.
| KPI | The definition question that has to be answered the same way, everywhere |
|---|---|
| EBITDA | Which add-backs are allowed, such as management fees, one-off restructuring, or FX gains/losses? Local GAAP treatment of leases and provisions varies; the add-back policy needs to be fund-defined, not inherited from each entity's default. |
| Revenue recognition point | Some local practices recognise revenue on invoicing, others on delivery or completion. A portfolio revenue comparison is meaningless if two companies are recognising at different points in the same type of transaction. |
| Net debt | Whether shareholder loans, lease liabilities, or factoring balances count as debt differs by local convention and by facility structure. Fix the definition once at fund level. |
| Working capital | Aging bucket conventions and provisioning policy for receivables differ by country and by auditor. The fund needs one working-capital definition applied consistently for portfolio comparison. |
A concrete version of the second row: Portco A recognises revenue on invoicing, Portco B on delivery. Both are defensible under their own local standard. But in a month with a large order shipped late, a portfolio revenue comparison between the two can differ by 15% or more for a reason that has nothing to do with either business actually performing differently.
Map once per portco, migrate nothing
The practical fix is a mapping layer, not a migration project: for each portfolio company, map its existing local chart of accounts to the fund's fixed set of KPI definitions, once, at onboarding. The local books stay exactly as they are, filed under whatever standard applies locally. The portfolio-level view is generated from the mapping, not from a rebuilt set of books.
This is the same principle as covenant tracking across a portfolio. Each party owns the data closest to them, and the fund's roll-up is derived, not manually re-entered. The mapping is entity-specific work done once; the KPI definitions are fund-wide policy set once. Neither needs to be repeated every reporting cycle.
What this looks like in practice
One KPI framework, however many local standards sit underneath it
Each portfolio company maps its own local accounting into AHQ Financialsonce. Your fund sees every company against the same KPI definitions inAHQ Insights: no separate consolidation project per country, and no re-mapping every time a new portco joins the portfolio.