Private equity reporting tends to break in five predictable ways after an acquisition closes: the diligence model cannot be reproduced from the acquired company’s systems, two charts of accounts have to feed one consolidated view, metric definitions stop meaning the same thing across the combined business, reporting turns out to depend on individuals who are leaving, and portfolio-level standards collide with what the new company can actually produce. These are not five separate failures. They are five symptoms of the same underlying condition, which is that the transaction transferred ownership without transferring the ability to measure what was purchased.
The central point: These five problems are diagnostic. They tell you where post-acquisition reporting is going to fail and roughly when. The structural answer is a separate question, and we cover it in our piece on why post-acquisition data integration starts before the dashboard. This article is about recognizing the symptoms early enough that the fix is a scoping decision rather than a recovery project.
The Diligence Model Cannot Be Rebuilt From the Systems
The financial model that supported the investment case was assembled by a diligence team working from data room extracts, management-prepared schedules, and direct conversations with the seller’s finance function. It was fit for its purpose.
After close, the sponsor asks for the same measures on a monthly cycle. That is when it emerges that several of them were never produced by any system. They were constructed for the process, in a spreadsheet, by someone who has now moved on, using judgments that were reasonable and undocumented.
The gap tends to surface late, because the first month or two after close runs on continuity reporting produced the old way. It becomes visible around the point where the sponsor tries to compare actual performance against the model and finds that the two are not measuring the same thing.
Worth doing before close: identify which measures in the model originate in a system and which were constructed. The constructed ones are the future reporting obligations, and they need a production method that does not depend on the person who built them for diligence.
Two Charts of Accounts, One Consolidated View
The acquired business keeps its own general ledger structure for a period after close, for good reasons. Statutory filing obligations continue. The finance team knows the existing structure. Changing it during an integration adds risk at the worst possible moment.
Meanwhile, the sponsor needs consolidated reporting from month one. So someone builds a mapping between the two structures, usually in a spreadsheet, usually under time pressure, and that mapping becomes load-bearing infrastructure without ever being treated as such.
The failure mode is not that the mapping is wrong at the outset. It is that it does not get maintained. A new account is opened in the acquired entity and does not appear in the mapping. A cost gets reclassified on one side and not the other. Six months in, the consolidated view and the underlying entities have quietly diverged, and reconciling them takes longer than building the mapping did.
Post-acquisition reporting that depends on an unowned, unversioned mapping file is one of the more common ways a clean systems integration produces unreliable numbers.
Metric Definitions Stop Meaning the Same Thing
Both businesses report gross margin. Both report headcount. Both report pipeline. Neither calculates them the same way, and both calculations are defensible.
Gross margin is the reliable example. One business loads fulfilment and support cost into cost of sales; the other treats it as operating expense. Both are acceptable treatments. Consolidate them without reconciliation, and the combined figure describes nothing. Worse, it moves, and the movement gets read as performance rather than as an artifact of aggregation.
Headcount produces the same problem more quietly. Contractors counted or excluded, open roles included or not, part-time treated as headcount or as full-time equivalent. Nobody flags this, because everyone assumes headcount is unambiguous.
These differences are not difficult to resolve technically. They are difficult to resolve politically, because agreeing a combined definition means one side’s reported history changes. That conversation is easier to have in the first sixty days, when everything is provisional, than in month nine, when a trend has been presented to an investment committee on the old basis.
Definitions are cheaper to settle in month two than month nine. Stratiform Group works with sponsors and portfolio company leadership to establish measure definitions and reporting structure during integration.
Reporting Depends on People Who Are Leaving
Acquisitions produce departures. Some are planned, some are retention failures, and some are the seller’s finance staff whose role genuinely ends at close.
In most mid-market businesses, monthly reporting depends on undocumented individual knowledge to a degree that surprises everyone once it is examined. Which adjustment gets applied at quarter end and why. Which of four similarly named files is the current one. Which system figure is known to be unreliable and gets overridden by hand.
When that person leaves, the reporting does not stop. It continues, produced by someone following the visible steps without the invisible judgments, and it looks correct. This is the most dangerous of the five problems, because the other four announce themselves and this one does not.
The mitigation is unglamorous: during the retention period, document the production of every reported measure, including the exceptions and manual adjustments, and have someone else produce a cycle end to end while the original owner is still available to check it. The cost of that exercise is a few days of a departing person’s time. The cost of skipping it is discovered later, usually by an auditor or a buyer.
Portfolio Standards Collide With What the Company Can Substantiate
Sponsors with several portfolio companies reasonably want comparable reporting across them. A standard pack, standard definitions, standard cadence. Comparability is much of the point of holding a portfolio.
The newly acquired business frequently cannot produce it. Not through resistance, but because the standard assumes source systems, data granularity, or a close discipline that the company does not have. A monthly pack requiring revenue split by product line and customer segment is straightforward for a company whose systems carry those dimensions, and impossible for one whose ERP records revenue at entity level only.
What follows is a manual workaround. Someone estimates the split each month using a method that is never written down. The sponsor receives a pack that satisfies the standard and contains figures that are not derived from anything. The reporting is complete, on time, and unsubstantiated, which is more dangerous than an openly acknowledged gap, because a gap gets managed and an invisible estimate gets treated as data.
The correct response to a standard the company cannot meet is to say so, report what can be substantiated, and treat the gap as a data project with a timeline. That is a harder conversation than producing the estimate, and considerably cheaper than discovering the estimate later.
Why These Five Arrive Together
Because they share a cause. Diligence measures whether the business is worth buying. Integration planning covers systems, people, customers, and operations. Neither process asks how the combined business will produce reliable numbers on an ongoing basis, so nobody owns that question, and it becomes visible only when the first consolidated reporting cycle is due.
By then the deal team has moved on, the finance function is absorbing statutory work for an additional entity, and the sponsor is asking for monthly figures. That is a poor moment to begin designing a reporting structure, which is why the work usually gets done as a workaround instead of as a design.
The timing is consistent enough to plan around. Problems one and two surface at the second or third consolidated cycle. Problem three surfaces when a trend has run long enough to be questioned. Problem four surfaces when the person leaves, which is often after the retention period rather than during it. Problem five surfaces when someone asks how a portfolio-standard figure was calculated and the answer is that it was estimated.
What This Means for M&A Data Integration Scope
M&A data integration is often scoped as a systems exercise: connect the systems, migrate the data, decommission what is redundant. That work is necessary, and it is not the same as making the combined business reportable.
A scope that addresses these five patterns includes, in rough sequence:
- An inventory, before close where possible, of which model measures originate in systems and which are constructed
- A decision on the account mapping approach, with a named owner and a maintenance process, rather than a file
- An agreed definition for each measure the sponsor reports on, settled early while positions are still provisional
- Documented production of every reported measure, completed during the retention period
- An honest assessment of which portfolio standards the business can meet now, which need a data project first, and what gets reported in the interim
None of this requires the target systems to be integrated first. Most of it can begin during the retention period, and the parts that involve definitions are easier before anyone has defended a number to a board. Where the answer is a longer-term one, it usually points at the future-state structure for the combined organization rather than at another connector.
The Same Questions Come Back at Exit
Sponsors treat these five problems as an entry-side inconvenience. They are also an exit-side exposure, and that is the part that gets underweighted.
A buyer’s diligence team asks the questions the sponsor asked at entry. How is this measure defined? Which system produces it? Who owns it? Show us the derivation across the hold period. A portfolio company that has been reporting on an unmaintained mapping, an undocumented estimate, or a definition that changed quietly in month nine cannot answer cleanly, and the gap gets priced.
The work that makes reporting reliable during the hold is the same work that makes it evidenceable at exit. It is unusual to get a second, cheaper opportunity to do it.
Scope the Reporting Work Before It Becomes Recovery Work
If you are integrating a newly acquired business, or preparing for one, the question worth asking in the first sixty days is not whether the reporting is late. It is whether the combined business is capable of producing the measures the investment case depends on, from systems, repeatably, without the person who set it up.
Stratiform reviews how a combined business produces its reported measures, where the structure will not support the requirement, and which of those gaps to close first. We work with sponsors, operating partners, and portfolio company leadership teams.
Where the answer is no, that is a scoping problem. It is considerably cheaper to treat it as one before the first consolidated cycle than after the third.
Private Equity Reporting FAQs
What reporting problems do private equity firms face after an acquisition?
Five recur. Measures used in the investment case turn out to have no system behind them. Ledger structures differ across the entities, so consolidation runs through a mapping that nobody maintains. Each side calculates the same metric on a different and defensible basis. Monthly production relies on individual knowledge that walks out during the transition. And sponsor-level standards ask for detail the newly held company’s systems do not carry. These cluster because none of them is anyone’s job during the deal itself.
When do these problems usually surface?
Around the second or third consolidated cycle. Immediately after close, the finance team is generally still assembling the pack exactly as it always did, and that continuity hides the gap. It opens up when performance gets set against the investment case, and the two turn out to rest on different bases, or when a restated figure prompts a question about the original derivation that nobody can answer.
How is M&A data integration different from ordinary systems integration?
Ordinary integration connects systems built by one organization for a single operating model. M&A data integration connects two organizations that made independent, internally consistent decisions about structure, definitions, and processes. The technical connection is often the easier half. The harder half is reconciling two defensible answers to the same question, and that is a governance exercise rather than an engineering one.
Can this work start before the deal closes?
Parts of it. Working out which investment case figures come out of a system and which were assembled by hand for the process can usually be done from material the deal team already holds. Reconciling definitions and documenting how each figure gets produced both need access to the target’s finance staff, so that portion waits until people are available. The advantage of moving early is largely political: agreeing a shared basis is easier while nothing has yet been reported on either one.
Do we need this if the portfolio company is being held short term?
Arguably more so. A shorter hold means less time to recover from unreliable reporting, and exit preparation places its own demands on the ability to evidence the production of figures. A buyer’s diligence team will ask the same provenance questions the sponsor asked at entry.
Which of the five should we address first?
Usually the account mapping and the documentation of reporting production, because both have a closing window. The mapping gets harder to correct the longer it runs unmaintained, and documentation depends on people who are still in the building. Definitional reconciliation is urgent but not time-boxed in the same way, though it does get politically harder each month a trend is reported on the old basis.