Private Equity and Venture Capital Case Studies
Finance5 Case StudiesUpdated Sep 2026
Private equity and venture capital firms make decisions on financial records that rarely arrive clean. Capital account statements, fund administration reports, portfolio company management accounts, and bank confirmations each describe part of the same position, and they seldom agree on the first pass. The five cases below follow working teams through situations where the numbers pulled in different directions. Each case asks what the variance actually is, how much exposure it carries, what evidence exists, and where the decision line sits. The aim is a sequence of steps a reviewer can defend.
Case Study 1
Capital call totals that would not tie out
Harrow Point Partners, a mid-market buyout firm with three funds and an operations group of six people.
The situation
Harrow Point Partners runs a fund with forty limited partners and three active portfolio companies. In the third week after quarter end, the fund accounting team found that total called capital in the general ledger sat 412,800 dollars above the sum of the administrator's investor statements. Two calls had been booked on the funding date in the ledger, while the administrator recorded one of them on wire settlement, three business days later. The gap was small against 310,000,000 in commitments, but the auditors had already flagged timing differences in this account. The controller needed an answer before the investor letter went out.
The challenge
The variance was not one number. The team had to separate timing from error, and the ledger, the bank statement, and the administrator's notice each carried a different date. Two possible causes were a late wire that had been booked early, and a duplicate entry from a manual journal. Each cause implied a different correction and a different message to investors, and the controller could not tell which applied without pulling the underlying wire confirmations.
Analysis
The first step was to build a three-way match for each call, keyed to one reference number across the investor notice, the bank confirmation, and the ledger. Teams grounded in Private Equity and Venture Capital tend to examine the date fields first, because a variance that shows up as an amount is often a timing problem seen from the wrong side. Once the dates were aligned, one call matched cleanly. The other showed a 412,800 dollar entry posted twice, once from the subscription schedule and once from a manual journal entered later in the month. The exposure was inconsistent investor balances across two quarters, found first by the auditors instead of the team.
The team set a threshold before reviewing any more entries. Any difference above 25,000 dollars, or any difference touching investor balances, would reach the controller within one business day and hold the investor letter. Smaller differences would be logged and cleared in the monthly close. The evidence standard mattered as much as the threshold. A reconciliation counted as closed only when a preparer and a second reviewer had both initialed the wire confirmation and the journal support, and the reviewer had compared both against the administrator statement rather than the ledger alone. Without that second comparison, the same duplicate could have passed a second time.
Actions taken
- Rebuild the capital call reconciliation as a three-way match on a shared reference number, with funding date and settlement date held in separate columns.
- Reverse the duplicate manual journal, confirm the reversal against the administrator statement, and document the corrected balance for each affected limited partner before the investor letter is released.
- Set a written escalation threshold of 25,000 dollars and require a second reviewer to initial the wire confirmation and journal support before any reconciliation is marked complete.
- Add a monthly exception report listing every call where funding date and settlement date differ, reviewed by the controller and retained in the close file for audit.
Results
The duplicate was reversed the same week, and the investor letter went out with balances that tied to the administrator's statements. The three-way match caught two more small date mismatches the next quarter, and the team cleared both without escalation. The auditors reviewed the exception report in the next cycle and asked that second-reviewer initials extend to every manual journal, which the firm adopted. One question remains open: whether the administrator should move to a single settlement convention.
Questions for discussion
- Which evidence would you require before accepting an administrator's date as the funding date for a capital call?
- How would you set the escalation threshold for a variance that is small in dollars but touches investor-facing balances?
- What would a three-way match miss, and what additional control would catch it?
Case Study 2
Revenue shortfall tests a portfolio company forecast
Tallow Ridge Capital, a growth equity firm holding majority stakes in four software and services businesses.
The situation
Kestrel Route Systems is a fleet scheduling software company with about 1,200 paying customers, a revolving credit facility from two lenders, and a board that approved a revenue plan of 48,000,000 dollars for the year. At the end of the second quarter, recognized revenue was 2,300,000 dollars below plan, and two large renewals had slipped into the second half. The finance lead had to present a reforecast to the fund's investment committee within the week. The lenders test a leverage covenant at each quarter end, measured on trailing EBITDA, so any revised number would also decide how much room the company had.
The challenge
The reforecast had to hold up under questions, not just look reasonable. Management wanted to keep the full-year number, pointing to a pipeline that had grown over the quarter. Pipeline value had not yet turned into signed contracts, though, and the renewals that slipped were the ones with the longest sales cycles. The committee would press on covenant headroom under a weaker case and on whether the company could fund itself without new equity.
Analysis
Build three cases from the bottom up rather than adjusting the plan downward. The base case assumed the two delayed renewals closed in the third quarter at 80 percent of prior contract values, with churn at the trailing rate. The downside removed one renewal and cut new bookings by a third. The severe case added churn among the smallest accounts, which made up a larger share of revenue than the sales team had assumed. Each assumption traced to a contract, an invoice, or a signed pipeline stage, so a reviewer could test it directly.
The covenant set the real boundary. Leverage had to stay under 4.25 times trailing EBITDA at quarter end. The base case left about 0.3 turns of headroom, and the downside case breached it. That result moved the question from whether revenue would recover to what management could do before the test date. The committee had agreed a trigger in advance: a breach probability above one in three would start cost actions and an early conversation with the lenders, not a new sales target. Each scenario was logged with its assumptions, so actual results could be checked against the case the committee approved.
- Rebase assumptions Use signed contracts and invoice history, not pipeline value alone.
- Stress the covenant Test headroom in turns of EBITDA under each scenario.
- Set response triggers Name the breach probability that starts cost actions or a waiver talk.
- Review actuals Compare bookings to the case each month and log the variance.
Actions taken
- Rebase the forecast on contract-level renewals and signed pipeline stages, removing any opportunity without a signed letter of intent from the base case.
- Run the covenant test under all three scenarios each month and report headroom in turns of EBITDA to the investment committee alongside the revenue variance.
- Open a waiver conversation with the lenders early, using the downside case as the basis, so any amendment is negotiated before the test date rather than after a missed covenant.
- Approve a cost reduction plan of 1,800,000 dollars sized to keep the downside case above the covenant line, with named owners and a start date inside the quarter.
Results
The reforecast landed at 44,700,000 dollars, below the original plan and well above the downside case. One of the two delayed renewals closed in the third quarter, and the other moved into the following quarter, which the downside had already priced. Leverage stayed under the covenant at the test, with headroom of about 0.2 turns. The lenders agreed to reset the covenant for two quarters in return for monthly reporting. The committee accepted the reforecast and asked for pipeline to be reported by stage, not value.
Questions for discussion
- Which assumption in the base case would you test first, and what document would settle it?
- When should a lender amendment be preferred over a cost plan, and what evidence supports that choice?
- How should a reforecast treat growth in pipeline value that has not yet converted to signed contracts?
Case Study 3
Offshore payment flows in a bolt-on acquisition
Sable Rock Capital, a regional buyout firm focused on industrial services businesses and three active funds.
The situation
Sable Rock was ready to sign a bolt-on acquisition of Eastgate Fabrication Group at an enterprise value of 18,500,000 dollars. During financial diligence, the accounting firm flagged that about 9 percent of supplier spend over the trailing twelve months, roughly 1,140,000 dollars, went to a related entity registered in a jurisdiction on the fund's high-risk list. Two invoices from that entity carried round-sum amounts with no purchase order and no matching delivery record. The seller wanted to close within six weeks, and the deal team was keen to keep that timetable.
The challenge
The indicators were consistent with a legitimate related party arrangement, and they were also consistent with a payment channel the fund should not touch. The compliance lead had to decide whether further diligence spend was justified, what the sanctions and anti-money-laundering obligations required of the fund, and who needed to see the file. Time pressure made the seller's verbal explanation look sufficient, and that was the part of the file most in need of checking.
Analysis
Start with the records. Payments were traced through bank statements, invoice registers, and the vendor master, and the trail showed no written contract, out of sequence invoice numbers, and an account in a third country. The exposure was measurable. A year of spend at this level, about 1,140,000 dollars, would matter a great deal if any of it reached a restricted party. Documentation was thin exactly where the fund would need it most, and those gaps were the finding, not the dollar amount.
Escalation was set by policy, not by the deal calendar. Under the fund's compliance procedures, any indicator tied to a high-risk jurisdiction went to the chief compliance officer before further diligence spend, and any unexplained round-sum payment above 50,000 dollars put the file on hold. The decision threshold was simple to state. If the ownership of the related entity could not be traced to named individuals who cleared screening within the diligence window, the deal would stop. Evidence for each step had to be kept: screening logs with dates, the ownership chain, and a written opinion from counsel on any reporting obligation.
Actions taken
- Freeze further diligence spend on the related entity payments and notify the chief compliance officer in writing, with the transaction file attached.
- Obtain ownership records for the related entity, run screening on every named beneficial owner, and retain the screening logs with dated sign-offs.
- Require the seller to end or restructure the related party arrangement, with an escrow sized to the twelve-month exposure and a specific indemnity.
- Set a written rule that any unexplained round-sum payment above 50,000 dollars is held for review before the deal can move to signing.
Results
The deal was held while counsel traced the related entity's ownership. The trail led to family members of a former site manager, who held a minority stake in a company linked to a restricted party. None appeared on a list, but the link was enough to stop the deal as drafted. The seller agreed to end the arrangement, placed 2,000,000 dollars in escrow against the twelve-month exposure, and accepted a specific indemnity. Counsel advised on whether a report to the relevant authority was required, and the firm filed one. The fund closed five weeks later at 17,200,000 dollars.
Questions for discussion
- Which document would you request first to establish beneficial ownership, and what would count as a clean result?
- Should a seller's verbal explanation ever reduce the diligence required for a flagged payment flow?
- How would you decide whether an indicator is a reporting event or only a file note?
Case Study 4
Scoring a leveraged acquisition loan request
Lowell Ferris Credit Partners, a direct lending group that provides senior and unitranche loans to lower middle market companies.
The situation
Callow Foods Holdings is a regional distributor of refrigerated and dry goods, with three distribution centers and two years of audited statements. It asked for a 22,000,000 dollar senior term loan to buy a smaller competitor, and a 3,000,000 revolver draw would bring total funded debt to 25,000,000 dollars at close. Trailing EBITDA was 4,800,000 dollars before adjustments and 6,100,000 dollars after 1,300,000 of add-backs for owner expenses and one-time legal fees. The sponsor would put in 40 percent of total capitalization.
The challenge
The request looked workable on adjusted numbers and considerably tighter on reported ones. The credit committee needed to know whether the add-backs would survive review, how the business held up if its largest customer left, and whether the sponsor's equity was real cushion or a paper figure tied to the purchase price. The answer would decide whether the fund lent at the requested size, lent smaller, or declined.
Analysis
The add-backs carried most of the argument. About 820,000 dollars of owner expenses were supported by ledger detail for only part of the amount, and the legal costs came from a dispute that had run for several periods. Together the add-backs equaled 21 percent of adjusted EBITDA. In the downside case, losing the largest customer, which provided 31 percent of revenue, cut EBITDA by roughly 1,900,000 dollars. Leverage then approached 6 times on adjusted figures and passed 8 times on reported ones, and fixed charge coverage fell under 1.0. Slow-moving inventory had also been revalued recently, so that figure needed testing too.
Suitability turned on the fund's credit policy rather than the sponsor's pitch. The policy capped leverage at 4.5 times adjusted EBITDA at close, required base case fixed charge coverage of at least 1.2 times, and limited unvalidated add-backs to 15 percent of adjusted EBITDA. At 21 percent, the request breached the add-back limit. The decision line sat where leverage would exceed the cap, which at the requested size meant EBITDA below about 5,560,000 dollars. Approval therefore needed a third-party quality of earnings review that supported that figure, a smaller facility, or both. Below that line, the fund would decline at the requested size.
Actions taken
- Reduce the term loan to 18,500,000 dollars, so total funded debt with the revolver stays at or below 4.5 times reported EBITDA of 4,800,000 dollars.
- Commission a third-party quality of earnings review covering owner expenses and one-time legal costs, and accept add-backs only to the extent the review supports them.
- Require a signed extension with the largest customer before funding, or hold back a tranche of the loan that releases only once the contract is executed.
- Set a cure reserve of 1,500,000 dollars held by the sponsor, with a fixed charge coverage test at the first two quarter ends and monthly reporting from closing.
Results
The committee approved a facility of 18,500,000 dollars with conditions. The quality of earnings review supported 5,400,000 dollars of EBITDA, which cleared the threshold for the smaller facility, though it accepted only about 600,000 of the 1,300,000 in add-backs. The largest customer signed a two-year extension before funding. The sponsor posted a cure reserve of 1,500,000 dollars, and the first leverage covenant was set at 4.75 times, stepping down over the life of the loan. Early monthly reporting tracked the reviewed figure closely.
Questions for discussion
- Which of the add-backs would you accept without third-party support, and which would you refuse outright?
- How should the decision line move if the largest customer's contract is only partly secured?
- What does a sponsor's equity cushion tell a lender that reported leverage does not?
Case Study 5
Remediation path for four audit findings
Pinecrest Alder Capital, a private markets manager running two closed-end funds and a managed account program for institutional clients.
The situation
Internal audit completed its annual review of fund operations and found four control weaknesses. In one fund, the management fee had been calculated on commitments rather than invested capital for part of the post-investment period, producing an overcharge of 310,000 dollars across 38 limited partner accounts. Valuation committee minutes were missing for two portfolio positions with a combined carrying value of 9,200,000 dollars. Capital call notices had gone out with a single approver on a subset of calls, and four users held administrator access on the fund accounting system beyond their documented roles. Management had already begun fixing the fee calculation.
The challenge
The findings did not carry equal weight, and the audit committee wanted them ranked before any remediation effort began. The fee error was quantifiable and already owed back to investors. The valuation gap was not yet an error, but it touched net asset value, which drives investor reporting. The access and approval gaps were control failures with no dollar figure attached yet. Each finding needed a named owner and a closure test that did not depend on management saying the work was done.
Analysis
The ranking used two lenses. The first was quantitative. The audit committee set a planning threshold of 150,000 dollars for errors that could be measured directly, and the fee overcharge exceeded it, so it ranked first. The second was qualitative. A valuation evidence gap on positions worth 9,200,000 dollars could change reported net asset value without any proven error, and that figure drives investor reporting. The approval and access findings ranked third and fourth. They carried no measured loss, but a single approver on a capital call or an excess administrator right is the kind of gap that lets a loss go unnoticed.
Each finding got one accountable owner, named by role and person, with a due date tied to the next investor reporting cycle. The fee correction belonged to the fund controller, with a closure test in which internal audit recalculates fees on invested capital for all 38 accounts. The valuation finding belonged to the valuation committee chair, who had to produce signed minutes for both positions across two quarter ends. The approval and access findings belonged to the operations director. Closure required a full population test of capital calls over the next two periods and an access export matched line by line to documented roles. No finding closed on management's word alone.
- 1Fee base correctionRecalculate fees on invested capital for all 38 limited partners.
- 2Valuation evidenceSigned committee minutes for both positions across two quarter ends.
- 3Capital call approvalSecond approver evidenced on every notice in the next two quarters.
- 4System access reviewExport user roles and match each to a documented business need.
- 5Independent retestInternal audit reperforms each control before closing the finding.
Actions taken
- Recalculate management fees on invested capital for all 38 limited partner accounts, issue corrected statements, and return the overcharge with interest as the partnership agreement sets out.
- Collect signed valuation committee minutes for both positions across the two most recent quarter ends, and require a sign-off template for every future valuation.
- Require dual approval in the fund accounting system for every capital call notice, and evidence the second approver's sign-off in the system log rather than by email.
- Remove excess administrator rights, document each remaining user's business need, and have internal audit retest the access export before the finding is closed.
Results
The overcharge was returned to investors in the next reporting cycle, and the fee calculation now pulls invested capital directly from the ledger. Minutes were found for one of the two positions, and the committee re-reviewed the other in full, which reduced its carrying value by 640,000 dollars. Dual approval on capital calls ran cleanly through the following period. Access rights were cut for three of the four users, and the fourth was kept with a documented need and a monthly review.
Questions for discussion
- How would you set the materiality threshold for a finding that has no measured loss but a severe control gap?
- What evidence would convince you that a valuation committee actually challenged a mark rather than ratified it?
- When should internal audit retest a remediated control, and who should be allowed to sign off on closure?
Learning Resources
Finance CASE STUDIES
China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.