Structured Finance and Capital Raising Case Studies
Finance5 Case StudiesUpdated Sep 2026
Each case below comes from a problem a working team in asset-backed lending, note placement, or fund credit might meet in an ordinary cycle. The organizations are fictional, and the figures are internal to each one. They show how a variance, a forecast gap, a concentration breach, a loan request, or an audit finding moves from first signal to documented resolution. Read them for the sequence of decisions rather than the numbers. Each one asks how records were tested, which exposure was real, what evidence counted, and where thresholds sat before pressure arrived.
Case Study 1
Tracing a remittance gap through a migrated servicing ledger
Marlow Ridge Servicing, a fictional loan administrator that collects payments and reports cash to trustees for several auto loan trusts
The situation
Marlow Ridge Servicing administers collections for four auto loan trusts with a combined outstanding balance of $612,000,000. Each month, the servicer's remittance report is matched against the trustee's cash receipt statement before funds flow to noteholders. In the third week after a cycle closed, the reconciliation team found a gap of $184,260 between reported collections and cash received for one trust. The waterfall had already run on the servicer figure, so an overpayment to the subordinate class was possible. The lockbox files that would settle the question had been moved during a system migration and were not indexed.
The challenge
The variance had to be explained before the monthly distribution date, which was five business days away. The team had to decide whether to release funds on the servicer number, hold the subordinate payment, or pay the trustee figure and accept a later true-up. Management also wanted to know whether the same break existed in the other three trusts, which all used the same migrated reporting template.
Analysis
Teams grounded in Structured Finance and Capital Raising treat a variance as evidence about the process, not only as a number to clear. The first step was to rebuild the cash side from bank-level detail rather than the report totals, because the report itself was under suspicion. That work isolated the gap to 61 loan-level payments with posting dates falling on the migration cutover. Each break was tagged by type: timing, duplicate posting, or unrecorded receipt. Timing items were the bulk, but the duplicate postings carried the exposure, since they inflated the collections base used in the waterfall.
The decision threshold was set before anyone argued about the answer. Any unexplained difference above $25,000 per trust would trigger a hold on the subordinate class, while smaller differences could be trued up in the next cycle with a documented note. Here the duplicate postings made up $141,900 of the $184,260, so the hold was required. The control gap mattered more than the dollar figure. The reconciliation had no required field linking a posting to its lockbox image, so a reviewer could sign off without seeing evidence. The migrated template now requires an image reference for every posting above $5,000.
Actions taken
- Hold the subordinate distribution for the affected trust until the duplicate postings are reversed and the trustee statement is re-matched to the lockbox images.
- Re-run the reconciliation on all four trusts using bank-level detail, with each posting carrying a lockbox image reference before it can be marked matched.
- Add a hard stop in the posting workflow that blocks sign-off on any item above $5,000 without an attached image, and log every override with the approver's name.
- Record the migration cutover as a control event, and require the servicing team to re-perform the monthly tie-out for two cycles before the old manual check is retired.
Results
The duplicate postings were reversed in the second week, and the subordinate distribution was paid after the trustee statement tied to the cent. The other three trusts showed 14 timing breaks and no duplicates, and those closed without funds moving. In the next two cycles the team reported zero unmatched items above threshold, and the override log recorded four approvals, all documented. The reviewer who signed the original tie-out was reassigned to the migration project, and sign-off authority now sits with a separate control group. Audit asked for the posting-to-image mapping and received it without a follow-up request.
Questions for discussion
- Which of the break types should have triggered a hold even if the dollar amount had been below the threshold, and why?
- How would you decide whether the old manual check should be retired, and what evidence would convince you the new workflow is reliable?
- What would change in the analysis if the duplicate postings had been spread evenly across all four trusts?
Case Study 2
Liquidity pressure in a lease warehouse facility
Coldharbor Equipment Finance, a fictional lender that funds medical and agricultural equipment leases through a warehouse line
The situation
Over the first half of the year, originations ran about 18 percent below plan, and the warehouse lenders tightened the advance rate after one large obligor missed two payments. The plan had assumed $48,000,000 of first-half originations and enough collections to cover facility interest and a scheduled paydown. By the middle of the quarter, the treasury team's rolling forecast showed liquidity falling below the minimum cushion within eleven weeks unless something changed. The lease book was healthy on paper, but most of its cash was locked in leases that had not yet reached the securitization sale date.
The challenge
The question was not whether to cut costs, since the cost base was already lean. It was which assumption to stress, and what response would hold up if the forecast was wrong in either direction. The treasurer wanted a single recommended path, and the board wanted to see that the recommendation would not depend on one optimistic collection curve.
Analysis
Scenario design started with the assumptions that moved cash, not the ones that moved reported income. Origination volume and the advance rate drove most of the swing, while the credit loss rate mattered only in the downside case. Three scenarios were built: a base case with originations recovering to 91 percent of plan, a stressed case where the advance rate fell a further 10 points, and a severe case where one more obligor defaulted. Each carried its own collection curve, drawn from the last eight quarters of paid-down balances rather than from the sales forecast.
Decision thresholds were the most useful part of the work. The team set a liquidity floor of $6,500,000 and a trigger at $9,000,000, so any scenario breaching the trigger needed action before the floor was reached. Under the stressed case the trigger was hit in the seventh week, which left time to sell seasoned leases instead of drawing on the facility at a worse advance rate. The severe case breached the floor regardless of response, which pointed to a conversation with the facility agent about covenant relief. Each weekly variance report was tied to the forecast version used for the decision.
- 1Stress origination paceTest volume at 91 percent of plan and below.
- 2Model the advance rateTighten the rate and rerun cash timing each week.
- 3Check the liquidity triggerFlag any week where cash falls under $9,000,000.
- 4Sell seasoned leasesRaise cushion before the trigger is breached.
- 5Open covenant talksStart with the agent while options remain open.
Actions taken
- Sell a block of seasoned leases from the oldest vintage at current bids, capped at $7,200,000, to restore cushion above the trigger before the seventh week.
- Freeze discretionary spending on the origination systems project and renegotiate the vendor schedule, which frees roughly $310,000 across the forecast window.
- Open a covenant discussion with the facility agent now, supported by the severe-case forecast, rather than waiting for a breach notice.
- Rebuild the weekly forecast so every assumption carries its source and a named owner, and review the advance rate assumption each Monday against the lender's latest notice.
Results
The lease sale closed in the fifth week at a price about 1.4 percent below par, inside the range the committee had approved. Liquidity stayed above the trigger through the rest of the window in the stressed case. The facility agent agreed to a temporary reduction in the cushion requirement after reviewing the severe case, but only for one quarter and with monthly reporting attached. The origination shortfall did not close, so the plan was reset to a lower volume, and the board approved that revision with the thresholds written into the minutes.
Questions for discussion
- Which assumption would you stress first if the collection curve from the last eight quarters proved too optimistic?
- At what point would selling leases at a discount become worse than drawing on the facility, and how would you estimate it?
- How should the team weigh a covenant conversation against the cost of signaling weakness to other lenders?
Case Study 3
Concentration breach and missing income files in a note program
Pellworth Capital Markets, a fictional placement firm that structures and sells private notes backed by small business loans
The situation
Pellworth Capital Markets placed a $75,000,000 note program backed by small business loans from three originators. Three months after closing, monitoring flagged fourteen loans from one originator with delinquency at twice the program average, nine of them lacking signed income verification. A separate allocation problem surfaced in the same report: one investor group held 22 percent of the Class B notes against a 15 percent concentration limit. The analyst had raised both items in a routine email before the monthly call, and no one had assigned an owner. Neither item had been logged in the exceptions register.
The challenge
The firm had to decide whether these were two separate problems or one problem with two symptoms. Its obligations ran to the noteholders under the indenture, to the investor under the offering memorandum, and to its own supervisory procedures, and each had a different clock. The compliance lead also had to avoid assuming bad faith before the facts were in.
Analysis
Exposure was measured in two layers. The delinquency cluster touched about 11 percent of program balance, which the waterfall could absorb under current subordination, but only if the originator's servicing held. The verification gap was the more serious problem. Without income documentation, the eligibility representations made to noteholders could not be supported for nine loans. The team rebuilt each file from bank statements and tax transcripts where they existed, and marked any loan without support as ineligible for the borrowing base pending review.
Strong teams write escalation thresholds before the facts arrive, because the clock starts when someone first notices a problem. Here any concentration breach above 5 percentage points went to the chief compliance officer the same day, and any eligibility failure above $2,000,000 of pool balance went to the trustee notice committee before the next distribution date. The Class B allocation needed its own test. The subscription had been accepted before the limit was checked, so the firm had to decide whether the waiver language in the offering memorandum applied at all.
- Day of monitoring reportAnalyst flags the delinquency cluster and allocation breach by email.
- Same dayChief compliance officer receives a written summary of the breach.
- Before next distributionNine loans removed from the borrowing base pending documents.
- Within the following monthFund reduces its Class B position below the concentration limit.
Actions taken
- Assign a named owner to each open item today and log both in the exceptions register, tracking the originator file review and the allocation review separately.
- Suspend the nine unverified loans from the borrowing base and rerun eligibility once the originator delivers signed income documents or a documented exception.
- Send the chief compliance officer a written summary of the allocation breach, with the subscription date, and obtain a legal read on the waiver language before any notice goes out.
- Require the originator to deliver a monthly delinquency certificate and six months of servicing reports until the cluster is explained.
Results
The nine loans stayed out of the borrowing base for two distribution dates, reducing eligible balance by $1,840,000. Counsel concluded the waiver held only if the fund cut its position below the limit within a fixed period, and the fund agreed to sell down the following month. The originator produced documents for six loans, and the other three were repurchased under the sale agreement. The matter went to the trustee notice committee and the exceptions register, with both owners named. Monitoring now runs the concentration test on every subscription before allocation.
Questions for discussion
- Which of the two problems would you have escalated first, and would your answer change if the allocation breach had come from a non-affiliated investor?
- What evidence would you need before concluding that the originator's servicing problem was a process failure rather than a credit deterioration?
- How should a firm decide whether a waiver in an offering document is strong enough to cure an allocation that was accepted before the limit was checked?
Case Study 4
Approving a packaging acquisition loan under thin earnings evidence
Ardent Bridge Partners, a fictional private credit fund that lends to founder-led manufacturers under a single-credit limit
The situation
Sable Ridge Packaging makes folding cartons for food and household goods and wants a $14,000,000 senior secured term loan to acquire a smaller competitor with two plants. The company reported trailing revenue of $61,000,000 and adjusted EBITDA of $7,300,000, but the seller's figures came from management accounts rather than audited statements. Pro forma leverage would sit close to the proposed covenant, and only if the target's margins held through the next two quarters. The committee had declined a packaging deal before, after customer concentration proved heavier than the data room showed.
The challenge
The credit team had to decide whether the structure protected the fund if the acquired plants underperformed, and whether the sponsor's equity cushion was funded or only assumed. Management was confident, and their projections were internally consistent, which is not the same as being reliable. The committee needed conditions specific enough to test, not a general request for more information.
Analysis
The earnings base was thin, so the team rebuilt the target's EBITDA from invoices and bank deposits for the trailing twelve months. That work removed $640,000 of add-backs for owner expenses with no documented business purpose, along with a one-time equipment repair that recurred in three of the last four quarters. Combined adjusted EBITDA came down to about $6,900,000 once those items were excluded. Working capital also needed a closer look, since the seller had pushed receivables collections in the final month before the sale process began, which flattered the cash conversion figure in the teaser.
The base case held leverage under the covenant with about 0.6 turns of headroom. The downside, with a 12 percent volume decline and a 150 basis point margin squeeze, left headroom near zero in the second year. The severe case removed the largest customer and breached the covenant in the fourth quarter. Size fit the fund's single-credit limit, so the decision turned on downside behavior. The committee set the approval threshold at a downside leverage ratio no higher than the covenant level, with the sponsor's equity treated as a condition rather than an assumption.
Actions taken
- Require a sell-side quality of earnings review with access to bank statements, and recompute adjusted EBITDA before the term sheet is finalized.
- Set the covenant at 4.25 times total leverage with a step-down after the second year, and tie the first draw to the sponsor's equity being funded at close.
- Obtain contracts for the top five customers with renewal dates, and make the largest customer's renewal a condition precedent to closing.
- Approve only if the downside leverage stays within the threshold, otherwise cut the commitment to $10,500,000 with a delayed draw for the second plant.
Results
The committee approved a reduced commitment of $10,500,000 with a delayed draw tied to the second plant's integration milestones. The earnings review removed a further $210,000 of add-backs, and the largest customer renewed early, which let the condition be satisfied before signing. The sponsor funded $9,000,000 of equity at close, and the covenant package required monthly reporting for the first year. Six months after closing, the business is tracking near the downside case, inside the threshold but with little room. The fund's sector exposure is now at its internal limit, so the next packaging request needs a different structure.
Questions for discussion
- Which add-back would you have been most willing to accept, and what documentation would have changed your view?
- At what point would a delayed draw structure stop protecting the lender, and how would you test for that?
- How should a fund weigh a deal that passes its threshold but leaves almost no downside room against one that fails it narrowly?
Case Study 5
Ranking trustee audit findings for closure and ownership
Thornbury Trust Company, a fictional trustee and administrator for nine asset-backed programs
The situation
Thornbury Trust Company acts as trustee and administrator for nine asset-backed programs. Internal audit reviewed its cash management and investor reporting processes over the year and issued seven findings. Two of them touched the distribution calculation directly: one allowed manual overrides to the excess spread figure without second approval, and another used a reporting template that excluded reserve account balances from the investor report. Management disputed the severity of several smaller items, and the reviewers had to decide which findings deserved to go to the audit committee.
The challenge
The audit committee would only see a short list, so the ranking had to hold up item by item. Each finding needed an owner who could actually change the process, not just sign the response, and each closure needed evidence a tester could check without relying on management's word. The team also had to avoid closing anything on the strength of a single clean month.
Analysis
Materiality was measured three ways: dollar exposure to investors, the likelihood that an error would reach a distribution, and whether the control could be bypassed without detection. The excess spread override ranked first because it touched the waterfall on every distribution date. The sample showed 11 overrides across the year totaling $3,870,000 of adjusted amounts, none with a second approver. The reserve exclusion ranked second. The omitted balances averaged about $1,200,000 per program, though noteholders could see them in a separate statement. Only the top two findings went to the committee as standalone items.
Ownership followed the control, not the org chart. The override approval belonged to the head of distributions, while the template fell to the reporting lead. Closure tests were written before remediation began. For the override finding, the test was a full-year re-performance of every distribution calculation, with zero overrides lacking a second approver across three consecutive distribution dates. For the template finding, reviewers reconciled reserve balances in the report to account statements for six programs, with no unexplained difference above $5,000.
- Rank by materiality Score dollar exposure, likelihood of error, and bypass risk.
- Assign owners Name the person who can change the control, not only sign the response.
- Test evidence Re-perform calculations and reconcile to account statements.
- Monitor recurrence Check later distribution cycles before closing the finding.
Actions taken
- Disable manual excess spread overrides in the distribution system and require a second approver for any adjustment, logged against the distribution run.
- Rebuild the investor report template to pull reserve balances directly from the account ledger, and document the source field for every line.
- Run a look-back over the last twelve distribution cycles for all nine programs, quantify each override, and report any unexplained amount to the audit committee.
- Schedule closure testing for each finding and keep the evidence package in the audit repository, with the owner signing only after the tester has signed.
Results
The override workflow went live in the second month, and the look-back found 14 adjustments across the programs, all supported by documentation except one. That one, totaling $58,000, was reversed and reported. The reserve template reconciled for six programs on the first test, and the remaining three cleared after minor mapping corrections. Both high-ranked findings closed after three clean distribution cycles and tester sign-off, while the five lower findings stayed open with dated owners. The committee accepted the ranking and asked that these closure tests become the standard for future findings.
Questions for discussion
- Would you rank the reserve exclusion above the override issue if the omitted balances had been material to a single program rather than spread across several?
- What closure evidence would you accept from a team that says a control worked during a quiet period with few distributions?
- How should ownership be split when a finding crosses two departments, and who should carry the final sign-off?
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.