Investment Banking and Capital Markets Case Studies
Finance5 Case StudiesUpdated Sep 2026
Capital markets work runs on records that have to agree with each other. Trades confirm to ledgers, ledgers feed risk reports, and risk reports drive lending and underwriting decisions. When one link slips, the consequences travel quickly. The five cases below reflect situations that deal, risk, and audit teams meet regularly. Each one sets out the facts as they arrived, the pressure that followed, and the reasoning used to reach a decision. Read them for the judgment as much as the outcome, and notice where each team chose a threshold and why.
Case Study 1
Unsupported receivable traced to a duplicate manual journal
Halvorsen Clearing Partners, a regional introducing broker-dealer with a single operations center.
The situation
Halvorsen Clearing Partners is a mid-sized broker-dealer that introduces its trades to a clearing firm and carries a book of about 340 institutional accounts. At the close of the month, the operations team reconciled three sources: the trade blotter, the clearing firm's position statement, and the internal general ledger for securities receivables and payables. The blotter and the statement agreed on quantity for nearly every security, but the ledger carried a receivable of $1,846,300 that the statement did not support. The gap sat in a single corporate bond line. Rachel, the operations manager, flagged it on the second business day and asked for the variance to be traced before the monthly net capital calculation was signed off.
The challenge
The variance was small relative to the firm's capital, but the net capital calculation treats unsupported receivables as deductions, so the gap moved the buffer above the internal early-warning line. The ledger entry had been posted by a manual journal two days after the trade date, and the supporting ticket was attached to nothing. Nobody could say yet whether the bond trade was wrong, the statement was late, or the journal was duplicated. The team had to answer that before the month closed.
Analysis
Start with the records, because a variance is only a number until each side is tied to a document. The blotter is the firm's view of what it traded, the clearing statement is the counterparty's view of what it holds, and the ledger is the accounting view of what the firm is owed. A clean reconciliation requires that each of the three can be matched to a confirmation. The ledger line had no ticket behind it, making the journal the weakest link in the chain. Risk exposure sits in the gap too, since an unsupported receivable is an asset the firm may never collect.
Controls are where the investigation earns its keep. A manual journal posted two days after trade date, with no attachment, should have been caught by a maker-checker step, so the first question was whether the approval field existed at all. Set thresholds before opening the file: any unmatched item above a fixed dollar amount goes to the controller, and any item older than one settlement cycle is treated as a break rather than a timing difference. Practitioners in Investment Banking and Capital Markets tend to write those limits down first so the investigation has an end point instead of a search that never closes.
- Trade dateBond purchase booked in the blotter at the agreed price.
- Day twoManual journal posted to receivables with no attached ticket.
- Month closeClearing statement shows no matching position for the line.
- Business day fourDuplicate journal reversed after ticket and approval check.
- Sign-offAdjusted net capital and break policy sent to the committee.
Actions taken
- Pull the confirmation, the clearing statement line, and the journal header for the bond entry, and match them field by field. Log each mismatch with its source document.
- Reverse the manual journal, then repost it only after the trade ticket is attached and a second person has approved the amount. Do not net the difference into an unrelated suspense account.
- Recalculate net capital with the disputed receivable fully deducted, and report the buffer to the treasurer before the monthly sign-off. Show both the reported and adjusted figures in the same schedule.
- Set a written break policy with dollar and age limits, name an owner for each limit, and test the policy against the last three months of closed breaks before it takes effect.
Results
The investigation traced the variance to a manual journal that had been posted twice, once with the wrong settlement date. The bond trade was correct, and the blotter and statement agreed once the duplicate was removed. The reversal went through on the fourth business day, and the adjusted buffer stayed above the internal early-warning line, by a narrower margin than first reported. The break policy was approved the following month. When back-tested against closed breaks, it would have flagged two items left open for weeks. Rachel sent the reversal, the schedule, and the policy to the audit committee together.
Questions for discussion
- Which of the three records should carry the most weight when they disagree, and how would that answer change if the clearing statement arrived late?
- What evidence would have been enough to release the ledger entry without a second approval?
- How should the break policy treat an item that sits under the dollar limit but has aged past the settlement cycle?
Case Study 2
Fee shortfall tests a boutique advisory firm's liquidity
Stowell Vance Partners, an independent advisory boutique with a revolving credit facility and two sector groups.
The situation
Stowell Vance Partners is a boutique advisory firm with about 62 professionals split between a mergers group and a leveraged finance group. Its annual plan assumed completed fees of $38,400,000, most of it from transactions expected to sign in the first half. By the end of the second quarter, completed fees stood at $19,700,000, and three of the eleven mandates in the pipeline had slipped by at least a quarter. Costs had followed the plan, with compensation accrued against the original revenue figure, so the monthly cash burn was running well above projection. Gareth, the chief financial officer, owned the forecast and had to present a revised view to the partners before the next distribution date.
The challenge
The revised forecast had to answer two questions at once. If the slipped mandates closed late in the year, the firm could recover most of the shortfall without changing its cost base. If they died, the firm would need to cut compensation or draw on its revolving facility to meet the minimum liquidity covenant, which the lenders had set at a fixed balance. The partners wanted one number they could defend, not three scenarios with no recommendation.
Analysis
Begin by rebuilding the forecast from the transaction level rather than adjusting the total. Each mandate carried a probability of signing, an expected fee, and an expected close month, and the plan had assigned those inputs in a single cell. Gareth split the pipeline into three buckets: mandates with signed engagement letters, mandates in final negotiation, and mandates still in early discussion. Only the first bucket was treated as firm. The middle bucket was haircut for historical slippage in the firm's own records, and the early bucket was excluded from the base case altogether. This made each assumption visible and tied the forecast to documents the partners could check.
The cash side needed its own test, because revenue timing and liquidity are different risks. Compensation accrued at plan levels was a fixed claim on cash in the second half, so the firm's exposure rose even where fees held. The revolver was sized to cover a shortfall up to a set amount before leverage covenant headroom disappeared, and that amount became the decision threshold. A useful number here is not the expected case but the month in which minimum liquidity would be breached under the downside, because that date sets how much time the response has. Control evidence was the monthly cash report tied to bank balances.
Actions taken
- Rebuild the base, upside, and downside cases from the mandate-level pipeline, with each assumption entered once and linked to its source document.
- Run the downside case with compensation accrued at the plan level and no change in headcount, then identify the first month in which liquidity falls below the minimum balance.
- Present the partners with one recommended case and two stated triggers: a fee threshold that keeps the revolver undrawn, and a liquidity threshold that starts a compensation review.
- Hold the early-stage pipeline out of the base case, and review it at each month end so that any mandate moving into the middle bucket is added with its own slippage factor.
Results
The revised forecast put completed fees for the year at $27,900,000, well below plan but above the downside case the partners had feared. The base case assumed two of the three slipped mandates would sign before the year ended, and the third was excluded. Compensation fell in line with the revenue shortfall rather than across the board, which kept two senior hires the sector groups depended on. The downside case showed minimum liquidity would hold through the year without a draw on the revolver. The partners approved the revised plan with the two triggers written into the minutes.
Questions for discussion
- Which mandate bucket would you have excluded first if the partners asked for a more aggressive base case, and what evidence would justify including it?
- How would the liquidity trigger change if the revolver covenant were tested quarterly instead of monthly?
- Where should the firm draw the line between cutting compensation and drawing on credit, and who should own that line?
Case Study 3
Clustered alerts on a fixed income portfolio
Tarnwood Capital, an independent asset manager with pension and insurance mandates.
The situation
Tarnwood Capital manages a fixed income book of about $412,000,000 for pension and insurance clients, with mandate limits that cap any single issuer at a fixed share of assets. In the third week of the quarter, the surveillance system flagged three indicators together. A regional utility bond had moved above the issuer limit after two large purchases, both executed in the final hour of trading. The purchase prices sat outside the range of the dealer quotes the firm had captured. And one of the two counterparties had been onboarded only days earlier, with its beneficial ownership form still marked incomplete. Maribel, the chief compliance officer, had to decide whether the trades were reportable and whether any client was harmed.
The challenge
Each indicator alone had an innocent explanation. Concentration can follow a benchmark change, off-quote pricing can reflect a stale dealer screen, and a late onboarding can be an administrative lag. Together they formed a pattern that the firm's own procedures required it to escalate, and the timing left little room. The trades had settled, the client reports were due in the following week, and the portfolio manager had already described the purchases to a client as a routine rebalance.
Analysis
Exposure comes first, measured three ways. The concentration breach was a mandate problem, the pricing gap was a valuation problem, and the unfinished onboarding was a counterparty credit problem. Each has its own measure: the excess above the issuer cap in dollars and basis points of assets, the difference between execution price and the average of captured quotes, and the amount of unsettled exposure to the new counterparty. The firm measured the first two within the hour. The third needed the settlement team to confirm what remained open. Documentation decided whether the file could be defended. Order tickets, quote captures, and the onboarding checklist had to be pulled with timestamps, not reconstructed from memory.
The control question was whether the procedures worked as designed. The surveillance flag fired, which is evidence the monitoring control worked. The pre-trade check on the issuer limit did not block the second purchase, which points to how the limit was loaded after a benchmark update. Escalation rules should not depend on proving intent. The written procedure required a same-day report to compliance when two or more indicators coincide, regardless of whether the trader had an explanation. A rule like that works as a control because the decision to escalate is made in advance and cannot be argued away under pressure.
- Detect alert Surveillance flags concentration, pricing, and onboarding gaps together.
- Assess exposure Measure the excess, the price gap, and unsettled counterparty amounts.
- Document evidence Link tickets, quote captures, and checklists with timestamps.
- Escalate and decide Report same day and decide on client notice and remediation.
Actions taken
- Freeze further purchases in the issuer, obtain the trader's written rationale, and pull the dealer quote captures for both executions before anyone speaks to the client.
- Complete the counterparty onboarding file, confirm settled exposure with the settlement team, and restrict new trading with that counterparty until beneficial ownership is verified.
- Record the three indicators, the timestamps, and the compliance decision in the surveillance case file, with each document linked rather than summarized from memory.
- Report the matter to the chief compliance officer and the risk committee the same day, and assess whether any client reporting or remediation obligation under the applicable rules has been triggered.
Results
An independent reviewer engaged by the committee examined both executions. The pricing gap was real, since the trades sat outside the afternoon quotes, and no model input explained the difference. The concentration breach was reduced to within limit over the following two weeks, and the affected clients received the notice their agreements required. The portfolio manager was restricted from trading the issuer while the review ran. The complete file, with each document linked, went to the records group the same week.
Questions for discussion
- Which of the three indicators would you have escalated on its own, and does that answer change once they are read together?
- What should the firm have done with the onboarding file before the second trade was accepted?
- How would you separate a suspicious late-day trade from legitimate rebalancing that also happens near the close?
Case Study 4
Packaging term loan sized to a downside case
Brindle Packaging Group, a family-controlled manufacturer with a long relationship with the bank.
The situation
Brindle Packaging Group produces molded fiber containers at three plants and employs about 1,100 people. It is asking the bank's leveraged lending group for a $64,000,000 term loan to finance a fourth line at its largest plant, with the proceeds to repay a bridge facility that matures in the coming months. The most recent full-year figures showed revenue of $211,000,000 and adjusted EBITDA of $27,400,000, but a single customer accounted for roughly a third of sales and the management accounts for the current year ran behind budget by the second quarter. Sanjay, the credit officer assigned to the file, had to write a recommendation the credit committee could act on within two weeks.
The challenge
On the reported numbers, the loan looked comfortable, with leverage a little under three times. The question was what happened if the largest customer reduced orders, as it had done once before in the company's own records, and whether the new line would generate cash before the bridge matured. The committee also had to consider suitability: the fund that would hold most of the loan had concentration limits by sector and by obligor, and a second loan to a packaging company would test both.
Analysis
The reported EBITDA needed adjustment before it could carry any weight. Roughly $3,100,000 of the add-backs were restructuring costs from two prior years, and the lender's view of recurring earnings excluded them. On a cleaner base, leverage at the proposed debt level moved to just over three and a half times. The downside case removed the largest customer's volume in steps, with a margin hit from the lost fixed-cost absorption, and it showed interest coverage dropping below the level at which the existing covenant package would hold. Revenue visibility was the other weak point, since contracted volume covered only the first half of the next year.
Suitability and conditions decide the shape of the answer. A loan at the proposed size would take the fund's sector exposure close to its limit, so the bank could approve only with a smaller hold or a syndicate partner. The thresholds the committee set were specific: minimum interest coverage of 2.0 times in the downside case, leverage below four times on the covenant basis, and a customer concentration step-down if the largest account fell under a set share of sales. Those thresholds were written before the model was rerun, so the team could not adjust them to fit the answer.
Actions taken
- Require a quality-of-earnings review of the add-backs, with the restructuring charges either evidenced by invoices or removed from the covenant base.
- Size the facility so that the downside coverage test holds with the largest customer at its lowest volume in the last three years, and reduce the amount if it does not.
- Hold the bank's share at a level the fund's sector limit allows, and bring in a syndicate partner for the balance rather than stretching the concentration limit.
- Write the covenant package and the customer step-down trigger into the term sheet, with a monthly reporting requirement on order volume and a cure period that is short.
Results
The committee approved a $48,000,000 facility, $16,000,000 below the request, with the balance to be placed with a syndicate partner. The quality-of-earnings review removed $2,400,000 of add-backs, leaving leverage just under four times, inside the threshold with little room. Once resized, the downside case held interest coverage at 2.1 times, and the customer step-down trigger went into the term sheet. Management accepted the smaller amount but asked for a bridge extension, which the committee declined pending the next quarter's order data.
Questions for discussion
- Which add-backs would you accept without invoices, and how would that choice change the leverage figure the committee sees?
- What evidence from the next two quarters would justify returning to the original request?
- How should the bank weigh a loan that fits its own limits but takes the fund close to a sector cap?
Case Study 5
Allocation control gaps ranked and closed by evidence
Marlowe Hart Capital Markets, a mid-sized investment bank with a sales and trading desk and a syndicate function.
The situation
Marlowe Hart Capital Markets runs a sales and trading desk, a syndicate function that places new issues, and a back office in a second city. The internal audit team reviewed the last two fiscal quarters and found twelve control weaknesses, five of them rated significant. The most serious sat in new-issue allocation, where orders for a subset of issues were released by the same team that entered them, with no second approver. Other findings covered stale valuations on two structured notes, system access that stayed active for leavers, and a fail-to-deliver balance that had gone unreviewed for two cycles. Vivian, head of internal audit, had to present the findings with owners and deadlines.
The challenge
The findings overlapped. The allocation weakness affected which clients received bonds and at what price, the valuation issue affected the balance sheet, and the access problem affected the reliability of every approval recorded in the system. Management disagreed on the ranking. Sales wanted the allocation finding treated as a process issue, while finance argued the valuation gap was the larger number. The committee needed a ranking it could defend and owners who would be held to dates.
Analysis
Materiality here was measured on three axes: dollar exposure, the chance the weakness would produce a misstatement or client harm, and whether the weakness had already occurred. The allocation gap scored highest because it had occurred. In a sample of orders, a subset had been released without a second approver, and two of those allocations were priced above the final book price. The valuation gap scored high on dollars, since the two structured notes carried positions of about $38,000,000 marked on quotes older than the policy allowed, but the exposure had not produced a loss. Access rights for leavers scored lower on dollars but undermined every other control trail, so it ranked above its face value.
Closure tests have to produce evidence that a reviewer could pick up without the owner in the room. For the allocation finding, the test is a sample of new-issue allocations drawn after the fix date, with the second approval timestamped before release and no exceptions above a set tolerance. For the valuation gap, the test is a recalculation of the two notes from independent quotes, with each quote date inside the policy window. Owners were assigned by process rather than by seniority: the syndicate operations lead owned allocations, the valuation committee chair owned the notes, and the identity team owned access. Each owner signed a plan with interim dates, and the audit team would not close a finding on a verbal update.
Actions taken
- Restrict release rights for new-issue allocations to a second approver who is outside the syndicate desk, and document the change in the entitlement register.
- Re-mark both structured notes from independent quotes this week, and set a rule that any quote older than the policy window triggers an automatic escalation to the valuation committee.
- Remove active system access for all leavers in the last cycle, then run the leaver report each month against the HR list and retain the signed comparison.
- Clear the fail-to-deliver balance by reviewing each open item with its counterparty, and report any item older than the agreed threshold to the operations committee with a named owner.
Results
Four of the five significant findings closed within the agreed window, each with evidence filed against its closure test. The allocation sample came back clean, and the valuation gap closed once both notes were re-marked and the escalation rule had run a full month without exception. The access finding stayed open one more cycle because two leaver records did not match the HR list, and the identity team traced both to a manual feed. The fail-to-deliver review cleared all but one item, which was escalated with a documented reason. Vivian presented the closure file to the audit committee.
Questions for discussion
- Would the ranking change if the allocation sample had come back clean, and which finding would move up to take its place?
- What closure evidence would you accept for a leaver control when the system log for the audit period no longer exists?
- When an owner asks to close a finding on a verbal update, what does the audit team give up by agreeing?
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.