vaayaa Inclusive Education

Business Valuation and Due Diligence Case Studies

Finance5 Case StudiesUpdated Sep 2026

Valuation and diligence work rarely fails on one dramatic error. It usually fails where small mismatches sit unexplained, where a forecast leans on a single optimistic input, or where a sign-off arrives before the evidence does. The five cases below each open with a situation that looked manageable. They then move through the records, the exposure, the controls that were or were not in place, and the thresholds that decided what happened next. Firms, people, and figures here are fictional, and each decision is one a reviewer would need to defend before a committee.

1

Case Study 1

Receivables gap surfaced during a buyer's diligence review

Pemberton Fleet Services, a regional vehicle leasing company with four branches.

The situation

Pemberton Fleet Services, a regional vehicle leasing company with four branches, was in the second week of a buyer's financial diligence when Priya, the review lead, noticed a gap in the lease receivables. The general ledger control account showed 2,184,600 in outstanding receivables at period end. The aging schedule prepared by the billing system summed to 2,141,900. The difference was 42,700, and the company's own monthly reconciliation for that month had been signed off as complete. Two branches also reported that several customer statements disagreed with the schedule for reasons nobody could explain on the call. The buyer had shared a preliminary valuation range built on reported net income, so the variance touched the earnings base directly.

The challenge

The variance was small against total receivables, about two percent, but it sat inside the balance that drove the earnings multiple. Priya needed to know whether the gap was a timing issue, a posting error, a billing system defect, or a manual journal posted to force agreement. The seller's controller said the reconciliation was reviewed every month. The buyer's team had three working days before the next steering call, and the seller wanted the price discussion to continue.

Analysis

The first task was to separate the records from the explanations. The GL control account, the billing aging, and the bank confirmations each came from a different system with different cutoffs, so a gap this size could come from several places before anyone considered fraud. Priya pulled the invoice-level detail for the forty largest open balances and matched each to its posting date and any credit memo issued after period end. That work showed that 29,300 of the gap came from credit memos dated in the first days of the following month but posted back into the prior period. The remaining 13,400 had no explanation in the subledger at all.

Practitioners working in Business Valuation and Due Diligence treat a clean reconciliation signature as a claim that still needs testing. The monthly sign-off in this company had no preparer evidence attached, no record of which items were cleared, and no threshold that forced escalation. The team proposed a simple rule for the remainder of the review: any unexplained difference above the higher of 5,000 or one percent of the control balance goes to the controller in writing, and anything above 25,000 changes the valuation basis until it is resolved. Those thresholds were set against the risk to the earnings base, not against what the seller found comfortable.

Where the receivables gap concentrated
Cutoff timing8/10
Early credit memos posted to prior period, 29,300 of the gap.
Unapplied lockbox receipts6/10
Two customers paid through lockbox but never applied to their accounts.
Unexplained residual5/10
Remaining 3,600 with no subledger explanation, carried as an open item.
Sign-off evidence9/10
Reconciliation signed as complete with no preparer or cleared-item list.

Scores set by the review team in this scenario, 10 = highest priority.

Actions taken

  1. Obtain the raw cash receipts and the amendment history for the Tallis Coast loan, and rebuild the mark from payments before accepting the broker quote.
  2. Ask the controller to document the reconciliation procedure, including preparer, reviewer, cutoff date, and the list of cleared items, for the last twelve months of closes.
  3. Adopt the escalation thresholds in the deal memo so that any unexplained difference above the higher of 5,000 or one percent goes to the controller in writing within two business days.
  4. Hold the earnings base at the lower reported figure, with a price adjustment mechanism tied to the resolved variance, until the open items are cleared by the seller's auditor.

Results

The seller's team found the cutoff problem within a week. Credit memos dated early in the following month had been posted to the prior period, which accounted for 29,300 of the gap. Lockbox receipts for two customers explained 9,800 of the remaining 13,400, leaving 3,600 open. The buyer reduced the earnings base for the unresolved portion and set a holdback of 60,000 against open items. The reconciliation was rebuilt with preparer and reviewer evidence, and the following close agreed to the bank without a manual journal.

Questions for discussion

  • Which of the three variance sources would you have tested first, and what evidence would have changed that order?
  • How should a buyer weigh a seller's signed monthly reconciliation when the sign-off carries no preparer evidence?
  • At what size of unexplained difference would you move from adjusting the price to pausing the transaction entirely?
2

Case Study 2

Retail volume shortfall tested against a covenant floor

Ashgrove Provisions, a privately held frozen seafood processor with two plants and a senior credit facility.

The situation

Ashgrove Provisions, a privately held frozen seafood processor with two plants, had built its annual plan around a new retail contract that was expected to add about 18 percent to volume in the second half. By the end of the second quarter, the contract had shipped at roughly half the planned rate. Gross margin was holding, but fixed plant costs had not come down, and the cash forecast the lender required showed the revolving facility dropping below its minimum liquidity level in the fourth quarter. Hadley, the chief financial officer, had to decide what to present to the board and the bank before the next covenant test.

The challenge

The forecast had two moving parts that were tangled together. Volume was the obvious one, but the plan also assumed a price increase on the retail contract that had not yet been signed. Hadley needed to know how much of the shortfall was timing, how much was structural, and which levers could be pulled without damaging the retail relationship. The bank had asked for a revised case within ten business days, and the board wanted a single recommendation rather than a menu.

Analysis

The forecast was rebuilt from shipment records. Weekly order data showed the retail contract running about 9 percent above the prior year base, not the 18 percent in the plan, and the gap sat mostly in two of the six SKUs covered by the contract. Three scenarios followed from that. The base case held the current run rate and pushed the price increase out one quarter. The downside kept the run rate flat and assumed the price increase was never signed. The recovery case brought the two lagging SKUs to plan by the fourth quarter. Each case was tested against the covenant level.

The assumption most in need of testing was the price increase, because it carried the largest share of the plan's margin uplift and it had no signed contract behind it. The team treated the unsigned price as a probability rather than a fact and gave it a weight of one in three in the base case. Fixed plant costs were modeled as fixed in every scenario, because both plants had labor agreements running all year. The forecast had also never been reconciled to the shipment data since the plan was approved. Any response had to rest on numbers the bank could trace to invoices.

From plan miss to a defensible response
  1. 1Rebuild from run rateReplace plan volume with shipment data and separate the price assumption.
  2. 2Score scenarios against covenantBase, downside, and recovery cases each tested for the liquidity minimum.
  3. 3Set liquidity triggersName automatic actions if the downside case crosses the threshold.
  4. 4Engage the lender earlyPropose a reset with monthly reporting before the covenant test date.
  5. 5Hold discretionary spendDefer second-shift hiring until the price increase is signed.

Actions taken

  1. Replace the plan's 18 percent volume assumption with the observed run rate, and show the price increase as a separate line with its own probability weight.
  2. Set a liquidity trigger of 4,000,000 in the cash forecast, and name the actions that start automatically if the downside case crosses it within two months.
  3. Defer the planned second-shift hiring until the retail contract signs at the new price, and tell the board which headcount decisions depend on that signature.
  4. Open a covenant reset discussion with the bank now, using the downside case as the floor, rather than waiting for the test date and presenting a revision under time pressure.

Results

The board approved the revised case with the price increase carried at a one-in-three weight, which put the base case liquidity low point just above the minimum. The second-shift hiring was deferred for two quarters. The bank agreed to a covenant reset with a temporary step-down in the minimum liquidity level, in exchange for monthly reporting on the retail contract. Two months later the contract signed at a smaller price increase than hoped, and the downside trigger was not hit. The margin recovered more slowly than the recovery case assumed.

Questions for discussion

  • If the retail contract signed at half the proposed price increase, which scenario would you move to the base case, and why?
  • How much weight should a single unsigned commercial term carry in a forecast that a lender will rely on?
  • What evidence would convince you to present a recovery case to the board rather than the downside case?
3

Case Study 3

Mark raised on a borrower that stopped paying on time

Ferrowick Capital Partners, a private credit manager running one senior secured lending vehicle.

The situation

Ferrowick Capital Partners manages a senior secured lending vehicle with a portfolio of 34 loans. In the third quarter, the valuation committee approved a mark that raised the value of one borrower, a regional packaging group called Tallis Coast, by 6 percent, even though the borrower had missed two interest payments and its quarterly statements were late. The mark came from a broker quote that the valuation team had not seen before. The fund's own policy required an independent check on any mark that moved more than 3 percent from the prior mark, and that check was not documented. A general partner's associate had also been an advisor to the borrower in an earlier transaction.

The challenge

The compliance officer, Renata, had to decide whether this was a valuation judgment that happened to look odd or a control failure that needed reporting. The mark fed the fee base and the performance figures in the next limited partner notice. Renata also had to consider whether the associate's prior role created a conflict that needed disclosure under the fund's governing documents and the adviser's registration obligations. The valuation committee had a meeting in six business days, and the auditors had asked about the Tallis Coast position already.

Analysis

The exposure was larger than the single position. Tallis Coast represented about 4 percent of committed capital, but the same broker had quoted two other borrowers in the same sector, and both of those loans were on the watch list. The records showed three sources of value that did not agree: the borrower's own financials, the payment ledger from the administrator, and the broker quote. Renata asked for the raw cash receipts and the amendment history, not the summarized mark. Only the cash receipts showed what the borrower had actually paid, and that was the figure a valuation had to start from.

The control gap was the independent check, which the policy required and the file did not contain. A reviewer should treat a documented exception as a control event, even when the final value turns out to be reasonable. Renata set a threshold: any mark that moves more than 3 percent from the prior value, or that rests on a quote the valuation team has not used before, must carry an independent price check before the committee votes. The associate's prior role went to the conflicts log and to counsel, with a written question about whether disclosure to limited partners was required before the next notice went out.

How the warning signs stacked up
  1. Well before the markAssociate advised the borrower on an earlier refinancing.
  2. Two periods backInterest payments missed twice while statements arrived late.
  3. Quarter endBroker quote arrived from an unfamiliar source the team had not used.
  4. Committee meeting dayMark approved up 6 percent without the required independent check.
  5. Six business days laterAuditors asked about the position and compliance opened an escalation review.

Actions taken

  1. Obtain the raw cash receipts and the amendment history for the Tallis Coast loan, and rebuild the mark from payments before accepting the broker quote.
  2. Commission an independent price check on the two sector peers quoted by the same broker, and hold both marks at the prior value until that check is documented.
  3. Log the associate's prior advisory role in the conflicts register, and ask counsel to determine in writing whether limited partner disclosure must precede the next notice.
  4. Reopen the quarter's valuation minutes, record the exception and its owner, and set a standing rule that any unchecked mark over the threshold cannot reach a committee vote.

Results

The independent check on Tallis Coast came back 11 percent below the broker quote, so the original mark was overstated. The mark was reversed in the next valuation cycle, and the two peer loans were written down after the cash receipts review. Counsel concluded that limited partner disclosure of the prior advisory role was required, and the notice was delayed by one week to include it. The fund's compliance log now records the exception with a named owner and an open closure test.

Questions for discussion

  • Where would you draw the line between a valuation judgment and a control exception when the final value still looks reasonable?
  • Should an associate's prior advisory role trigger a conflicts review on its own, or only when it touches the pricing decision?
  • Which evidence would you ask for first if the borrower's statements were late but its cash receipts were on time?
4

Case Study 4

Clinic expansion loan weighed against leverage and collateral

Linden Hollow Veterinary Group, a five-clinic practice owned by two partners and seeking expansion debt.

The situation

Linden Hollow Veterinary Group, which operates five clinics, asked a regional bank for a 1,800,000 term loan to open a sixth clinic and retire a short-term equipment line. Caroline, a senior credit analyst at the bank, received the package with three years of financial statements, a clinic-level profit breakdown, and the owners' plan for the new site. Revenue for the last full year was 6,850,000 and reported EBITDA was 1,020,000. The two oldest clinics produced most of that margin, and the newest clinic had not yet reached monthly breakeven. The owners expected the sixth site to reach breakeven within the first year of operation.

The challenge

Caroline had a credit committee that met in four weeks and a standing concern about leverage in veterinary roll-ups. The requested facility would take total debt to roughly 3.4 times EBITDA on a pro forma basis. The bank's policy ceiling for this sector was 3.5 times, which left little room for a cost overrun or a slow ramp at the new clinic. The owners had offered a personal guarantee from both partners and a pledge of equipment, but neither was valued independently yet.

Analysis

Caroline rebuilt the forecast from the clinic-level ledgers rather than the consolidated statements. The consolidated figures blended a mature region with a new site and hid the ramp risk. Taking the newest clinic's actual monthly visit counts, she ran three cases: the owners' plan, a slower ramp that reached breakeven in the second year, and a downside where visit volume plateaued at 70 percent of plan. In the downside, the group's debt service coverage fell below 1.2, which was the bank's floor for this size of facility. The equipment pledge was the weakest part of the collateral, since its value depended on used-market prices nobody had checked.

Suitability turned on whether the debt matched the cash the business actually generated. A term loan that amortizes over seven years against a clinic that is still ramping is a mismatch unless the covenants leave room for the first year. Caroline proposed a conditional approval with a lower initial draw, a debt service coverage covenant tested quarterly from the first full quarter, and a step-down in the advance rate on the equipment pledge until an independent valuation came back. The owners' guarantees were useful but the bank treated them as support, not as the primary source of repayment.

Loan approval path under downside coverage
Does coverage hold under the downside ramp?
YesApprove with conditionsReduced draw, quarterly coverage test, and independent equipment appraisal before release.
NoDecline the requested amountLeverage or coverage breaches the policy floor, so the request goes back to the owners.
Approval depends on the tranche release conditions.

Actions taken

  1. Require an independent appraisal of the equipment pledge and cap the advance rate at a level set by that appraisal, not by the owners' asset schedule.
  2. Model the sixth clinic at 70 percent of planned visits for eighteen months and confirm that coverage stays at or above 1.2 times under that case before committee.
  3. Reduce the initial draw to cover the build-out and retire the equipment line, with the remaining tranche released only after the new clinic posts two breakeven months.
  4. Set the approval thresholds in writing: decline if pro forma leverage exceeds 3.5 times or if the coverage downside falls below 1.2, and revisit only with new audited figures.

Results

The committee approved a reduced facility of 1,150,000, with the balance of the original request declined. The appraisal of the equipment came in roughly 22 percent below the owners' schedule, which reduced the advance on the pledge and made the guarantees a larger share of support. The sixth clinic opened and reached monthly breakeven in its eleventh month, which was between the slower ramp and the plan. The second tranche was released after two breakeven months were posted, and the covenant was met in the first full quarter.

Questions for discussion

  • How would your recommendation change if the owners offered a larger personal guarantee in place of the equipment pledge?
  • What downside assumption would you consider too optimistic for a clinic that has not yet reached monthly breakeven?
  • Should a lender ever approve a facility that depends mainly on guarantees rather than the cash flow it is meant to service?
5

Case Study 5

Six audit findings ranked for a pre-sale remediation plan

Tovane Packaging Group, a family-owned packaging company with two plants and a shared accounts payable center.

The situation

The internal audit team at Tovane Packaging Group completed a review of accounts payable and inventory controls in the second half of the year, in preparation for a sale process that the owners had started. The review found six control weaknesses. Four were design gaps, one was a failure to perform a documented check, and one was an access issue in the vendor master file. Vendor bank details could be changed by two users who also approved payments. The sale advisers had asked for a remediation plan before the data room opened.

The challenge

Ruth, the group's head of internal audit, had to rank the six findings by materiality before the management team could assign owners. Several findings looked small individually. The vendor bank change issue touched a payment stream of about 3,400,000 a year, while the inventory cutoff gap was worth about 180,000 at the period end. The CFO wanted a plan that closed the high-risk items first, and the advisers wanted evidence that would survive a buyer's testing.

Analysis

Materiality was judged on two measures at once: the value of the transactions that passed through each weakness, and the chance that an error would reach the financial statements unnoticed. The vendor bank change scored highest because it touched outgoing payments and had no independent review. The inventory cutoff gap was smaller in value but sat in the balance that drove gross margin, so it ranked second. The four design gaps were ranked lower because each had a compensating review that worked in practice, even if it was not documented. Ruth kept a short written note for each ranking, so a buyer could check the reasoning.

Closure evidence had to be reproducible by a buyer's tester. For the vendor bank change, that meant a system report of every bank detail change in the period, matched to a signed request and an independent call-back, with no change made by the same user who approved payments. For the inventory cutoff, it meant a period-end count sheet with a second signature and traced receipts. A finding closed only when a post-fix sample passed the test, not when the owner said it was done. Owners missing that sample by the agreed date went to the sale steering group, and any exposure above 250,000 went to the board.

Remediation cycle for the audit findings
Closure loop
1Rank by materiality
2Assign owners
3Test the fix
4Close on evidence
  1. Rank by materiality Score each finding by value and by the likelihood of unnoticed error.
  2. Assign owners Name one accountable owner and a due date for every finding.
  3. Test the fix Draw a post-fix sample that a buyer's tester could reproduce.
  4. Close on evidence Close only when the sample passes, then file the evidence with the finding.

Actions taken

  1. Require the vendor bank change to run through a second approver who cannot also release payments, and confirm the system change with a written test before any sample is pulled.
  2. Assign each of the six findings a named owner and a due date, and make the inventory cutoff owner accountable for a second count at each period end.
  3. Prepare a closure test for every finding in advance, specifying the population, the sample size, and the document that proves the control operated.
  4. Disclose any finding still open at data room opening with its compensating review and expected closure date, rather than presenting it as resolved.

Results

Ruth's team closed the vendor bank issue first, after the system was changed so that a single user could no longer both edit bank details and approve payments. The first sample of changes that passed was drawn in the third week after the fix. The inventory cutoff took longer, because two warehouses counted on different days, and it closed only after a second count. Three of the four design gaps closed within the quarter. The last one remained open with a documented compensating review, and the sale advisers disclosed it in the data room.

Questions for discussion

  • How would you rank a control weakness that is small in value but sits in a balance the buyer will test first?
  • What would count as sufficient closure evidence for a bank detail change control if the sample came back clean?
  • When should an open finding be disclosed in a data room rather than closed on paper before the process starts?

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.

Hourly Active: 37,008 Learners