What financial reporting do PE firms require from portfolio companies?

Private equity sponsors typically require a monthly flash within three to ten business days, a full monthly management pack with variance commentary and cash reporting, a KPI schedule tied to the investment thesis, quarterly covenant compliance certificates, a quarterly board pack, and an annual budget before the fiscal year starts. The exact package is set by the credit agreement and the sponsor's own reporting standard, so the answer is always in two documents rather than in a general convention.

What surprises most first-time portfolio-company finance leads is not the volume. It is the speed and the consistency. Sponsors care less about a perfect number arriving on day twenty than a consistently-defined number arriving on day five, because they are aggregating across a portfolio and a late portco holds up the whole roll-up. That is the single most useful thing to understand about the relationship. Our guide to FP&A software for PE portfolio companies covers the tooling implications.

Bottom line: the two documents that define your actual obligations are the credit agreement, which sets covenant reporting and deadlines, and the sponsor's reporting standard or portfolio-operations handbook, which sets the pack format and KPI definitions. Get both in week one, and reconcile their definitions to your chart of accounts before the first close.

The standard reporting package

Cadences vary by sponsor and by deal structure, but the shape below is close to universal for a mid-market sponsor-backed company.

Two entries in that table cause most of the pain. The flash is hard because three to ten days is genuinely tight when your close is not yet clean, and sponsors treat a late flash as a signal about management rather than about accounting. The covenant certificate is hard because it uses definitions from the credit agreement that almost never match your management P&L — adjusted EBITDA in particular, which will have a bespoke definition including or excluding specific add-backs.

The practical move on covenants is to build the calculation once, as a schedule that ties from your management numbers to the agreement definition with every adjustment visible. Rebuilt each quarter from memory, it will drift, and drift on a covenant calculation is the kind of error that becomes a conversation with a lender. Keeping the audit trail visible is the same discipline covered in board and investor reporting software.

What sponsors actually look at

Understanding the reading order changes how you build the pack.

They look at revenue and EBITDA against plan first, and they look at the variance rather than the absolute. Then cash, specifically headroom and runway. Then the KPIs named in the investment thesis, because those are what the deal was underwritten on and what will be in the exit story. Then, if something has moved, the commentary explaining it — which is why commentary quality matters more in a sponsor-backed company than almost anywhere else.

What they largely do not read is detail below the level of their thesis. A twelve-page departmental breakdown is work that generates no return. The instinct to demonstrate rigour by adding pages is the most common and most costly misread of the relationship. Build the pack that answers their four questions well, and keep the detail available on request rather than distributed.

• Revenue and EBITDA versus plan, with variance explained in one line each.
• Cash: closing balance, headroom against facility, runway on the current plan.
• The three to six KPIs from the investment thesis, defined identically every month.
• Forecast revision if the full-year view has changed, and what changed it.
• Covenant headroom, quarterly, tied to the agreement definition.

Where the reporting stack sits

This is worth being precise about, because the two layers are frequently confused in vendor conversations and they do not compete.

The sponsor's monitoring platform — Chronograph and S&P iLEVEL are the ones portfolio companies meet most often — aggregates data across the whole portfolio, handles valuations and produces LP reporting. It consumes what you send; it does not produce your plan. Your FP&A layer is what produces the plan, the actuals comparison and the commentary in the first place. A portco finance team that has been told the sponsor "already has a system" and therefore does not need its own planning tool has been told something misleading: those systems solve the sponsor's aggregation problem, not your production problem.

So the two are complementary, and the useful question for a portco is narrower: what is the fastest way to produce a consistently-defined pack every month from our own ERP. That is an FP&A-layer question. The current FP&A software landscape names the field, and multi-entity consolidation software covers the case where the portco is itself a group.

How to set this up in the first ninety days

1. Get the credit agreement and the sponsor reporting standard. Extract every defined term that appears in a covenant or a required schedule.
2. Reconcile those definitions to your chart of accounts before the first close, and write the mapping down. This document is the one that saves you every quarter afterwards.
3. Build the flash as a subset of the pack, not a separate artefact. Same source, fewer lines, so the two can never disagree.
4. Automate the actuals pull. The deadline pressure is entirely in assembly, not analysis, and this is where tooling earns its cost.
5. Agree the KPI definitions with the sponsor in writing. Ambiguity here surfaces at exit, which is the worst possible time.

The fourth point is where most of the recoverable time sits. If getting actuals into the pack is a manual export-and-reformat exercise, a three-day flash is not achievable no matter how organised the team is. If actuals flow into a maintained model, it becomes routine. That is the specific mechanic behind live drillable budget-versus-actual and it is the capability worth testing in any demo.

Add-on acquisitions change the answer

Buy-and-build strategies are where portco reporting gets materially harder, and it is worth anticipating rather than discovering.

Each acquisition arrives with its own chart of accounts, its own close calendar and often its own ERP. Sponsors will still expect the consolidated pack on the same deadline. The practical implication is that your reporting architecture needs to tolerate a new entity being added without a rebuild — which means mappings that finance can edit, not mappings that require a vendor ticket. That is a question to ask before you buy anything, and it is covered in the demo question list.

It also means the consolidation question arrives earlier than headcount would suggest. A 150-person company with four acquired entities has a genuine statutory consolidation requirement that a 400-person single-entity company does not, and the tier that fits is different. The FP&A versus CPM versus EPM ladder sets out where that line falls, and for the metric definitions your sponsor will benchmark you against, the Benchmarkit SaaS benchmarks we co-published is the reference set worth agreeing on early.

Common friction points with sponsors

Four recur across almost every sponsor-backed finance team, and all four are avoidable with a decision made early rather than a process improved later.

Definition drift is the most damaging. A KPI computed one way in month three and another way in month nine destroys the trend, and the sponsor will notice at exactly the wrong moment. Write each definition down, including the edge cases, and treat a change to one as a formal event with a restated history rather than a quiet correction.

Late flash is the most visible. Sponsors read a late flash as a management signal, not an accounting one, which is disproportionate but real. If the deadline is genuinely unachievable with a clean close, negotiate the deadline once rather than missing it repeatedly — the second is far more expensive to your standing than the first.

Mid-year KPI changes come from the sponsor rather than from you, usually when the thesis evolves or a new operating partner arrives. Expect them, and keep the underlying data granular enough that a new cut is a re-report rather than a re-collection. That is an argument for holding detail in a queryable layer rather than in a formatted pack.

And reporting to two masters — a sponsor standard plus a lender package with different definitions of the same terms. Build both from one source with a visible tie-out between them, never as two independently maintained artefacts. Financial reporting covers the mechanics.

What changes as you approach exit

Reporting obligations do not just continue into an exit process; they change character, and the shift catches teams out.

During the hold, reporting is about managing the business. In diligence it becomes evidence, and evidence is judged on whether it reconciles. A buyer's quality-of-earnings process will take your monthly packs, tie them to the audited financials, and ask about every difference. Packs that were internally useful but never reconciled to statutory numbers generate a long question list, and a long question list costs price.

The practical implication is to reconcile management reporting to statutory reporting quarterly through the hold period rather than assembling the bridge at exit. It is a modest quarterly task and an enormous one-off task. Teams that have done it walk into diligence with the bridge already built; teams that have not spend six weeks reconstructing it under time pressure.

• Reconcile management to statutory numbers quarterly, not at exit.
• Keep every KPI definition and every change to one, with dates.
• Preserve the audit trail from reported figure back to source transactions.
• Keep add-back and adjustment schedules with supporting evidence attached.
• Expect to reproduce any monthly pack from source on request.

The last point is the one that most often decides whether a finance function looks credible in diligence. Being able to regenerate a figure from source, live, ends a line of questioning immediately. Being unable to extends it. That capability is a function of where your reporting is built rather than how carefully it was checked, which is why the portfolio-company tooling question is worth settling early in a hold rather than late.