The Reporting Burden a Fund Places on a Portfolio Company, Costed

The package nobody has priced

Ask a portfolio company CFO how much the monthly sponsor package costs to produce and you will get a wince, then a shrug. Ask the operating partner on the other side and you will get a blank look, because from the fund's chair the package is free. It arrives. It has tabs. Somebody made it.

Everybody in private equity agrees the reporting burden is real. Very few people have ever put a number on it. That gap matters more than it looks, because a cost nobody has measured is a cost nobody can decide to keep or cut. The fund keeps asking for more. The finance team keeps absorbing it. Nobody ever sees the bill.

What the literature admits, and where it stops

The material on page one of any search for this topic is honest about the weight and silent about the price.

Zachary Scott, writing for owners preparing for a sale, describes PE ownership as bringing "increased breadth, depth, and frequency of financial and operating reporting," demanding "ongoing attention from the Chief Financial Officer (CFO) and his or her team on a monthly and even weekly basis" (Zachary Scott). Mueller Prost makes the same point from the accounting side: sponsors want information "much sooner after the end of each period," with more analysis and more forecasting than an owner-run business ever produced (Mueller Prost).

Then both pieces stop. Neither says how many hours. The firms best placed to count them are mostly outsourced finance providers, and their answer to "this is heavy" is "hire us to carry it." That is a fair business. It is not a neutral measurement.

Why the burden grows without anyone deciding it should

The mechanism is a deadline cascade, and it runs downhill.

A fund has its own obligations to its LPs and its lenders. To meet them, it needs portfolio numbers on a fixed clock. Consero, a finance-as-a-service provider, puts the expected monthly board package at "within 10 to 15 business days of close" (Consero). If the company cannot close inside that window, the fund's own calendar is at risk. So the pressure on the portfolio company is to go faster before anyone has asked whether it can.

Speed pressure arrives before capacity does. Consero's 2024 CFO survey found that 48 percent of CFOs without an outside finance partner took 21 or more days to close, against 35 percent of those with one (Consero). That is a vendor-published figure about the value of the vendor's own category, and it should be read as one. Notably, the same firm's pages quote two different year-on-year comparisons for nine-day closes that do not reconcile with each other. The direction is still informative: a large share of mid-market finance teams close far slower than the sponsor calendar assumes.

Then the requests accumulate. A KPI tab added for one board meeting stays forever. A lender adds a covenant certificate. A new operating partner wants the cohort view their last fund used. Each addition is small and each is reasonable. None is ever retired, because retiring a tab requires someone to decide, and adding one only requires someone to ask.

How to cost it, at the level of the pattern

The arithmetic is not hard. What is hard is that nobody has a reason to do it.

Start with people, not reports. List everyone in finance and the adjacent functions who touches the sponsor or lender package in a month: the controller, the FP&A analyst, the AP lead who pulls the vendor aging, the ops manager who exports the KPI data from a system finance does not own. For each, estimate the hours spent assembling, reconciling, formatting and re-explaining. Re-explaining is the line people forget, and it is often the largest, because every variance question from the board generates a thread.

Then price it at loaded cost. As an illustration, not a benchmark: a finance team of six where the controller spends a week a month on the package, one analyst spends half their time on it, and three other people lose a couple of days each to supporting pulls is already carrying a bit over one full-time equivalent of reporting work. At a fully loaded cost for those roles, that is a six-figure annual line item that appears in no budget and no board deck.

You will not know your company's real number until you count it. The CFO usually has a rough sense already. The fund, which has only ever seen the output, is the party most likely to be surprised.

The part that is never read

Costing the package is half the exercise. The other half is the uncomfortable one: how much of it does anyone use?

A reporting package grows by accretion. Nobody designed the current version. It is the sum of every question anyone ever asked, preserved in amber. The predictable result is tabs the board has not referenced in a year, metrics that are computed by hand each month and then not discussed, and reconciliations that exist because two systems disagree and the package papers over it rather than fixing it.

That last category is the one worth chasing. A reconciliation that a human performs every month to make the numbers agree is not a reporting cost. It is an operations defect being charged to finance. We wrote about the same phenomenon from the diligence side in what operational diligence finds that financial diligence will not: the manual work that produces a clean number is invisible until you ask who produced it.

Automate it or shrink it

Here is where the vendor answer and the buy-side answer split.

The vendor answer is to automate the package: a portfolio monitoring platform, a reporting layer on top of the ERP, a dashboard tool. Some of those are good. All of them, applied to an unexamined package, will faithfully automate the tabs nobody reads and the reconciliations that should not exist. You end up with a faster version of a burden you never chose.

The better sequence is boring. Cost the package. Ask the fund which parts it actually uses. Cut the rest. Fix the upstream defects that create manual reconciliations. Then decide what is worth automating, and you will find it is a smaller, cheaper project than the one you were pitched. We made a similar argument for multi-unit operators in standardize the reports before you automate them, and it applies with more force here, because a fund can change its own request with one email.

Timing also matters. If a consolidation is underway, some of this work belongs on the far side of it and some does not. Our piece on whether to automate before or after the ERP consolidation covers how to tell the difference. Reporting logic built on the current chart of accounts is a bet on the current system. Removing a tab is a bet on nothing and pays immediately.

Why the fund should want this more than the company

It is tempting to frame all of this as the portfolio company defending itself from its owner. That is the wrong frame.

The fund pays for the package twice. Once in the finance hours, which come out of the EBITDA the fund is trying to grow. And once in attention: a CFO spending a week a month assembling numbers is not spending that week on working capital, pricing, or the system the growth case depends on. A burden nobody costed is a quiet tax on the value creation plan, levied by the people who wrote it.

A fund that has seen its own reporting package priced has, for the first time, a basis for a real decision: keep it, trim it, or pay to systematize it. A fund that has not is simply buying it on autopilot. Monthly. With no invoice. (If there were an invoice, at least it would close on time.)

Where writing stops

An article can tell you the package has a price and roughly where to look for it. It cannot sit with your controller for a close cycle, trace which tabs the board actually opens, and find the reconciliation that is really a broken integration. That is fieldwork, and the answer differs for every company in a portfolio.

If your portfolio companies are spending finance capacity on reporting nobody has costed, or you are a CFO trying to have that conversation with your sponsor with a number instead of a complaint, talk to us. We will help you price what the package costs today and decide what is worth keeping before anyone buys software to produce it faster.