Most businesses that take private equity investment are operationally ready for it. Their systems are not. The gap does not show up during diligence, when everyone is focused on historical numbers and the team is working nights to answer questions. It shows up about thirty days after close, when the reporting expectations become permanent rather than a one-time exercise.
The change is not that the new owner wants more information. It is that they want the same information, on a fixed schedule, in a consistent format, at a level of detail your previous reporting never needed to produce. That is a systems problem long before it is a staffing problem.
What actually gets asked for
The specifics vary by firm, but the shape is consistent. Expect some version of the following within the first quarter.
A monthly reporting package on a hard deadline. Usually due somewhere between ten and twenty days after month end, every month, without exception. The deadline is the part that breaks teams. A close that takes fifteen days and occasionally slips to twenty was survivable before. Against a fixed board deadline it is not.
Results cut by dimension. Revenue and margin by product line, by location, by customer segment, by channel. Not as a one-off analysis somebody builds in a spreadsheet, but as a standing part of the package that has to tie to the financials every time.
Budget versus actual with variance explanations. Not just the numbers, but a written account of why each meaningful variance happened. This is hard to do quickly when the underlying data has to be reassembled by hand each period.
Covenant compliance. If the deal carries debt, there are ratios to calculate and certify on a schedule, with real consequences for getting them wrong or late.
A rolling forecast. Often thirteen weeks for cash, plus a longer view for the operating plan, updated monthly rather than annually.
Why this is harder than it sounds
Almost every one of those requirements depends on your accounting system being able to slice the same transaction more than one way. A sale is not just revenue. It is revenue for a particular product line, in a particular location, through a particular channel, attributable to a particular entity.
Entry-level accounting systems typically give you one usable dimension, the chart of accounts, and sometimes a second called classes or departments. So teams do what the tool allows: they encode the extra dimensions into the account structure itself, producing a chart of accounts with several hundred accounts where the same expense type repeats for every location. Or they export everything to a spreadsheet each month and rebuild the cuts by hand.
Both approaches work until the deadline gets fixed and the detail gets deeper. Then the first one makes the chart of accounts nearly unmaintainable, and the second one makes the close longer every month at exactly the point where it needs to get shorter.
The diligence trap
There is a specific pattern worth naming, because it catches well-run businesses.
During diligence, your team produced everything that was asked for. It took enormous effort, a lot of manual work, and probably several weekends, but it got done and the deal closed. That success creates a reasonable but wrong conclusion on both sides: that the finance function can produce this kind of information.
What it actually proved is that your team can produce it once, under pressure, with everything else deprioritized. The monthly cadence asks for it repeatedly, while everyone also does their normal jobs. The effort that was heroic for one quarter is unsustainable for twelve.
What the timing means for you
There is a practical argument for acting early that has nothing to do with software and everything to do with attention.
The first six to twelve months after an investment are the period when capital expenditure for infrastructure is easiest to justify, when the new owner expects change, and when nobody has yet built a year of habits around manual workarounds. A systems project in that window is understood as part of the plan. The same project proposed in year three, after the team has been grinding out manual packages for thirty months, reads as an admission that something has been broken for a long time.
The parts that break first
These are the specific failures that show up in the first few reporting cycles after a change in ownership.
The close cannot hit a fixed date
A close that averaged twelve days with occasional slippage was fine when the only audience was internal. Against a board deadline, the average matters far less than the worst case. Teams start closing early on estimates and truing up later, which creates restatements in the package and erodes confidence in the numbers faster than a late report would have.
Every cut of the data is rebuilt by hand
Revenue by product line, margin by location, spend by category. If your system holds only one usable dimension, each of these is a separate export and a separate spreadsheet, rebuilt every period. The numbers are usually right. The problem is that nothing ties automatically, so any question about a figure means reconstructing how it was built.
No audit trail behind the numbers
The first time an investor asks why a figure changed between two versions of a report, you need to be able to answer from the system rather than from memory. Entry-level systems record limited history of who changed what and when. That gap is uncomfortable in a board meeting and genuinely serious at the first audit.
Consolidation is a person, not a process
If the investment involves multiple entities, or if an add-on acquisition follows, someone has to combine them. Done manually, that work grows with every entity added and lives with whoever built the spreadsheet. That is a real risk when reporting has a hard deadline and one person holds the mapping in their head.
Questions we hear most often
How quickly do we need to fix this after a PE investment?
There is rarely an emergency in month one, but the useful window is the first six to twelve months. That is when infrastructure investment is easiest to justify, when the new owner expects operational change anyway, and before the team has built a year of manual habits. Waiting until year three means proposing the same project with much less goodwill behind it.
Our team produced everything during diligence. Does that mean we are fine?
It means your team can produce it once under pressure with other work deprioritized. Monthly reporting asks for the same output repeatedly while everyone also does their normal jobs. If diligence ran on exports and hand-built spreadsheets, you have already seen what the ongoing cadence will cost. The question is whether that cost is sustainable for twelve cycles rather than one.
What specifically do private equity owners ask for that we probably do not produce today?
Most commonly: a monthly package on a fixed deadline, results cut by product line, location, segment and channel, budget versus actual with written variance explanations, covenant calculations where there is debt, and a rolling forecast updated monthly. Individually these are all producible. The difficulty is producing all of them accurately, every month, against a date somebody else set.
Is this a staffing problem or a systems problem?
Usually systems, though it presents as staffing. If the reporting requires exporting data and rebuilding the same cuts by hand each period, adding a person shortens the work but does not remove the rebuild, and the effort still grows with every entity, location or product line you add. Adding capacity to a manual process makes the next twelve months survivable rather than fixing the underlying constraint.
We only have one entity. Does multi-entity capability still matter?
It matters if an add-on acquisition is part of the thesis, which it often is. Buying a platform that handles one entity well and then acquiring two businesses in eighteen months means doing the migration twice. Worth asking your investor directly what the acquisition plan looks like before deciding how much capability you need.
Related problems
- Consolidating multiple entitiesWhy group reporting slows down as entities are added, and what fixes it.
- Reports take days to buildWhy a simple report takes days to assemble and what real-time reporting requires.
- Why your month-end close keeps getting longerThe complete breakdown of what stretches a close and what shortens it.
- We acquired a company and now run two systemsWhat the first close after an acquisition reveals, and what it costs.
Get a clear picture of where your gaps actually are
The free ERP Readiness Scorecard covers reporting, inventory, purchasing, multi-entity complexity, and more. Get a score based on your specific situation in under 5 minutes.
No sales pitch. No vendor push. Just a clear picture of where your systems stand.