Asset and Portfolio Management Case Studies
Finance5 Case StudiesUpdated Sep 2026
Asset and portfolio management sits where accounting, valuation, and client reporting meet, and many of its failures first appear as numbers that refuse to agree. The five cases here come from different firms but share a set of problems practitioners will recognize: a reconciliation break, a forecast that drifted from plan, a transaction that triggered risk flags, a funding request that needed a hard look, and an audit that produced more findings than anyone expected. The organizations are fictional, but the mechanics are ordinary.
Case Study 1
Reconciling a fixed income position across three ledgers
Harrowgate Trust Administration, a fiduciary administrator that keeps books for about 140 separately managed accounts and reports to pension and endowment clients.
The situation
Harrowgate's operations group closes the books for every portfolio each business day. Early in a quarter-end close, the reconciliation team found that a corporate bond in one pension mandate carried three different values. The custodian showed a market value 38,400 higher than the administrator's ledger, and the portfolio accounting system sat 11,900 below the custodian. The bond had settled two days earlier, had a coupon date the following day, and had been partly sold. The trade blotter also showed two entries that looked like one execution. The mandate held about 310,000,000, so the break was small in proportion, but the client's performance pack was due in four business days.
The challenge
Mariana, the operations lead, needed to decide whether the break was a timing issue that would clear on its own or a booking error that had to be corrected before the pack went out. The policy set a tolerance of 25,000 on any single position's market value before escalation, and a combined tolerance of 50,000 per mandate. The 38,400 difference was over the single-position limit, and the team had no clear evidence yet of which source was right. Escalation to the chief operating officer was required, and the decision on which figure to book had to be documented.
Analysis
The first useful step was to stop treating the three figures as competing opinions and to rebuild the position from source documents. Mariana pulled the settlement confirmation, the coupon schedule, and the trade blotter, then recalculated accrued interest using the day count convention written in the bond's offering terms. That recalculation matched the custodian on accrual but not on the market value, which pointed the team toward the pricing feed. Teams grounded in Asset and Portfolio Management usually read the record trail before they read the spreadsheet, because the evidence that matters is often a confirmation that nobody thought to attach to the ledger.
The pricing feed had applied a stale evaluated price, one that predated the partial sale and so applied to a larger holding. The overstatement on the administrator side was 38,400, and the restated mandate return moved by a few basis points. The decision rule was simple. Anything over the single-position tolerance is corrected at source and disclosed to the client with the reconciling item attached, never netted into a general adjustment. The team also added a control that compares settled quantity on the confirmation against the quantity used for pricing, run before the feed publishes each day.
- Trace the source Rebuild the position from confirmations, schedules, and blotter entries.
- Test against tolerance Compare the variance to the single-position limit before deciding.
- Correct at source Book the fix where the error started and disclose the reconciling item.
- Automate the check Block publication when confirmation and pricing quantities disagree.
Actions taken
- Booked the correction at source, restated the mandate return, and sent the client a reconciling note listing the position, the original and corrected values, and the date the feed error was first observed.
- Added the settled quantity comparison as a blocking check, so the pricing run halts and routes to operations when confirmation and pricing quantities differ, rather than publishing a figure with a warning attached.
- Reviewed every bond position with a partial sale in the prior month against the pricing feed, finding two further stale prices, both under tolerance but logged so the team could see the pattern.
- Set a monthly review of the escalation log by the operations lead and the risk function, with each break recorded against its tolerance, its root cause, and the person accountable for closing it.
Results
The pack went out on schedule with the corrected figures and a short reconciling note. The client's reviewer asked two questions about the restatement, both answered from the attached confirmation, and the reported monthly return moved by less than the client's rounding. The settled quantity check later caught one further mismatch on a different bond before publication. The stale price pattern did not recur. The more lasting change was procedural: escalations now carry a root cause and a named owner, and the log is reviewed where it can influence feed design.
Questions for discussion
- What evidence would have been needed to justify booking the pricing feed value on day one rather than waiting for the confirmation to be checked?
- How should the single-position tolerance change if the mandate holds fewer, larger positions?
- Which owner should be accountable for a feed error that originates outside the operations group?
Case Study 2
Revenue shortfall and a cash forecast that stopped holding
Stonemere Asset Partners, an independent manager running three open-ended funds and a small advisory business for family offices.
The situation
Stonemere runs three open-ended funds, and its annual plan leans heavily on management fees calculated from month-end net assets. Eight months into the plan year, fee revenue was running 9 percent below budget. Two causes were visible. One large institutional redemption had reduced net assets in the flagship fund, and a fee waiver negotiated for a strategic investor was being applied more broadly than intended. The treasury team also reported that the liquidity sleeve, which had been forecast to fund operating costs and a planned hire, was showing a monthly cash shortfall that its model did not explain. Redemptions were not yet in the forecast at the level the trading desk now expected.
The challenge
Teodor, the chief financial officer, had to decide whether to cut the hiring plan and advertising spend now, or hold the cost base and draw on the credit line. The board's threshold was that cash on hand must cover at least six months of operating costs, and the cushion was currently about 4.2 months under the base case. The fee shortfall was real, but its size depended on redemption assumptions nobody yet trusted.
Analysis
The team started by rebuilding the forecast from the fund administrator's monthly net asset statements, not the planning model, which had carried redemptions as a flat percentage. The statements showed that the fee shortfall was mostly timing and mix: two funds had lower average assets, and the waiver accounted for a third of the gap. Three scenarios were built around redemption pace, one where outflows stayed at the year to date rate, one where they doubled for two quarters, and one where a single large holder exited. Each scenario carried its own cash path, and the liquidity sleeve was tested against each one separately.
Under the base case the cushion held near four months, below the six month board threshold but stable. Under the sustained outflow case it fell under three months by the end of the plan year, and only the hiring plan and discretionary spend could close that gap without drawing on the credit line. The team set a trigger at four months of cover on a rolling basis, which the sustained case would breach well before the credit line was needed. Recommending spend cuts on one scenario would have been hard to defend, so the response was tied to the trigger.
Actions taken
- Re-scoped the waiver so it applies only to the strategic investor's own share class, and wrote the change into the fee schedule before the next billing run.
- Replaced the flat redemption assumption with the three scenario paths, each tied to named inputs such as the top ten holders' notice periods and the pace of year to date outflows.
- Froze discretionary spend and deferred the planned hire to the start of the next plan year, keeping the advertising budget intact for the fund that was still gathering assets.
- Set the four month cover trigger as a standing agenda item, with treasury reporting the liquidity sleeve against each scenario every two weeks until redemptions settled.
Results
The waiver correction recovered part of the fee gap in the remaining months, and the deferred hire held the liquidity cushion in the sustained case at about four months rather than the three months the unadjusted path implied. The credit line was never drawn. The board accepted a revised revenue target and a written rule for when spending would move again. Later in the year, the fundraising team reported that one fund had begun attracting new assets, which gave the scenarios a fresh input to test and kept the trigger in use.
Questions for discussion
- Which of the three redemption scenarios should carry the most weight when the board reviews the cash plan, and why?
- At what point would a fee waiver that was meant to be narrow become a reason to rewrite the revenue forecast entirely?
- How should the trigger change if the credit line were less certain to be available when needed?
Case Study 3
Concentrated trading before a downgrade in one holding
Ostrander Pell Advisors, a registered investment adviser running discretionary equity and credit mandates for about 60 private clients, with a compliance team of four.
The situation
A portfolio manager at Ostrander Pell bought a large block of a regional utility's subordinated notes across three client accounts in the same afternoon. The notes were not in any model portfolio, and the mandates had a limit of 5 percent of assets in any single issuer. Within the following two days, the rating agency placed the issuer on watch for a possible downgrade, and a trade surveillance alert flagged the purchases for review. The client accounts together held roughly 7 percent of the issuer's outstanding notes, and two of the three mandates had a fixed income guideline that excluded subordinated debt. The manager's note in the order system described the purchase as a tactical view on spreads.
The challenge
Ruth, the chief compliance officer, had to decide whether the alert was a documentation gap or a potential breach, and what to tell the clients before they saw it themselves. The firm's escalation policy required a written review within two business days for any single-issuer exposure above the mandate limit, and a report to the regulator's filing desk if a guideline breach could be shown to be intentional. The evidence so far was thin: the note said spread view, but no research memo existed.
Analysis
The first pass was about exposure, not intent. Across the three accounts, the combined position sat just above the 5 percent single-issuer limit once the custodian's position file was reconciled, and two of the accounts held subordinated notes that their guidelines excluded. The team then checked the purchase timestamps against the research repository and the morning committee minutes and found no entry supporting a view on the issuer. Control evidence was the weakest part of the record. The order tickets carried a free-text reason field, and the pre-trade check had accepted the orders without a guideline flag.
The escalation decision turned on two thresholds in the policy. A single-issuer breach requires a written review within two business days, and an apparent guideline breach that is not reported within that window requires a report to the regulator's filing desk. The firm could not say whether the breach was intentional, and that uncertainty was a reason to escalate, not to wait. Waiting for a clean answer would have put the report past the window. The compliance team opened the review that day, froze new purchases in the issuer, and told the affected clients that the exposure was under review, without calling it a violation.
Actions taken
- Restricted the issuer across all three accounts, placed the subordinated notes on the exclusion list, and documented each account's position at the time of the alert.
- Pulled the order management audit trail for the purchases, including the reason field history, the pre-trade check log, and the approving user's access record.
- Interviewed the portfolio manager using a written question set, and recorded the answers in the case file before the research team saw the question list.
- Added a hard stop in the pre-trade check that blocks any order taking a single issuer above its mandate limit, and requires a second approver for any subordinated debt.
Results
The review found that the combined holding had breached the issuer limit in one account for two days, and that the subordinated notes were outside the guideline in two accounts. The firm reported the breach to the regulator's filing desk within the window, and reimbursed the affected clients for the spread difference between the purchase and the eventual sale price. The portfolio manager was removed from discretionary authority on the issuer pending retraining. The pre-trade hard stop has blocked two orders that would have exceeded the limit, and the reason field is now a controlled list.
Questions for discussion
- What evidence would have been enough to show intent, and what evidence would have been enough to clear the manager?
- Should a free-text reason field be allowed on orders at all, or only a list of approved rationales?
- How should the firm weigh a client's right to know about a breach against the risk of disclosing an unconfirmed finding?
Case Study 4
Private credit bridge loan to a regional distributor
Ashgrove Lane Credit, a private credit manager whose flagship fund holds about 850,000,000 in committed capital and caps any single borrower at 4 percent.
The situation
A regional distributor of building materials, Dunmore Supply, asked the fund for a bridge loan of 22,000,000 to cover a delayed working capital facility while it finished a branch acquisition. The company had revenue of about 184,000,000 in its most recent full year and an adjusted EBITDA margin that had slipped from the high single digits to around 5 percent. Its existing senior lender was amending covenants, and the company proposed a 14-month maturity with a fee, a first lien on receivables and inventory, and a pledge of the acquired branch. The request came with management accounts for seven months and a forecast that assumed the acquired branch would return to prior margins within two quarters.
The challenge
Anneliese, the head of private credit, had to decide whether the fund should lend against a business whose margin had fallen, using a bridge that depended on an acquisition that had not yet closed. The fund's rule capped any single borrower at 4 percent of committed capital, and the loan would sit at about 2.6 percent. The question was less about size than about whether the downside case still protected principal.
Analysis
The financial evidence was uneven. The seven months of management accounts were consistent with the tax returns the company supplied for the prior year, which mattered more than the forecast. The margin decline traced mostly to freight costs and a pricing lag on two product lines, and the largest customers paid within terms. Inventory had risen faster than sales, and about a fifth of the stock was slow-moving on the company's own report. The fund built three downside cases: the acquired branch stays at current margins, receivables stretch by 20 days, and the bridge is not refinanced at maturity, forcing a discounted inventory sale.
Suitability was the second test. The mandate allowed bridge lending only with a first lien and a credible refinancing path. The bridge met the first condition but not the second, since refinancing depended on a senior lender still amending covenants. The downside case returned principal in full only if inventory recovered at least 70 percent of book value, which the slow-moving report did not support. The team set conditions: a committed senior amendment before funding, a field exam on inventory, a lower advance rate on stock, and a springing liquidity covenant. Without those, the loan would be declined, and the team would say so to the company.
- 1Confirm senior supportRequire the signed covenant amendment before any funds are committed.
- 2Verify the collateralField examination sets the inventory advance rate and receivables eligibility.
- 3Test the downsidePrincipal must survive the case where inventory recovers under 70 percent.
- 4Set monitoring triggersMonthly branch margin and inventory aging reports with acceleration rights.
- 5Approve or declineFund only if all conditions hold, otherwise decline and say why.
Actions taken
- Asked for the senior lender's signed covenant amendment and a copy of the consent letter before any funds were committed, with the condition written into the term sheet.
- Commissioned an independent field examination of inventory and receivables, and set the advance rate on stock at 45 percent of appraised value rather than the 60 percent requested.
- Priced the loan with a fee and margin that compensated for the refinancing risk, and added a springing covenant that tested liquidity each month once the acquisition closed.
- Required a monthly report on branch margins and inventory aging, with a right to accelerate the bridge if either deviated from the downside case by more than the agreed band.
Results
The senior lender signed the covenant amendment in the third week, and the fund committed 18,000,000 of the 22,000,000 requested once the field examination confirmed the inventory base. The acquisition closed on those terms. Branch margins recovered more slowly than management had forecast, and the monthly report prompted a call in the fourth month, though no acceleration was needed. The bridge was repaid at maturity from the refinancing. The original request was declined in its full size, and the company accepted the smaller facility.
Questions for discussion
- How much of the approval case rested on the senior amendment, and what would the team have done if that amendment had arrived late?
- Should the advance rate on slow-moving inventory be set by the field examination alone, or by a haircut the fund applies to any category it cannot sell quickly?
- At what level of margin recovery would the fund be willing to extend the bridge rather than accelerate it?
Case Study 5
Internal audit findings on valuation and trade controls
Vellmoor Wealth Group, a wealth manager with four investment teams, a central operations unit, and an internal audit function that reports to the audit committee.
The situation
Internal audit at Vellmoor completed a review of valuation and trading controls across its four investment teams and the central operations unit. The scope covered 2,100 manual price overrides logged over the review period, 340 trade amendments after booking, and the approval matrix for new private asset valuations. Fieldwork turned up more issues than the team had expected. Override reasons were often blank or generic, amendments were approved by the same person who entered them in about one case in six, and two private asset valuations had not been refreshed in more than a year. The review team summarized the results in a draft report that the operations director had seen only in outline.
The challenge
Julian, the chief operating officer, had to decide how many of the findings to treat as material before the audit committee met, and who would own each fix. The committee's materiality line was any gap that could misstate reported client values by more than 0.5 percent of a portfolio's value, or that allowed one person to both create and approve a transaction. Some findings clearly crossed that line. Others were hard to size until the valuation evidence was pulled.
Analysis
Findings were ranked on two measures: the value that could be misstated and the likelihood that the weakness had produced an error. Stale private asset valuations were the most material, because the two holdings carried 41,000,000 of client value at a mark that predated a funding round. The override and amendment weaknesses ranked next. They were less likely to have changed reported values, but the override log could not show who had approved most of the 2,100 entries, removing the evidence needed to rule anything out. A third group was documentation: missing reasons and incomplete approvals that did not appear to misstate anything but would weaken any future defense.
Owners were chosen by the process that failed, not by the reporting line. The valuation refresh went to the investment team head who approved the marks, with the operations director accountable for evidence. Each finding closed only when a test passed against records that the owner could not edit. For the stale valuations, the test was a refreshed mark sourced independently, reconciled to the funding round documents, with no unexplained difference above 5,000. For overrides, the test sampled 60 entries drawn at random from the next two months and required a stated reason and a second approver on every one. The committee, not the owner, set closure dates.
- First weekRefresh stale valuations and restate affected client reports.
- Second weekEnforce second approval on overrides and amendments in the system.
- Within the monthMake reason fields mandatory and review existing blank entries.
- Later reviewsSample closure tests run by independent staff, not the finding owner.
- Next committee meetingCommittee confirms closure against test evidence and sets the next review.
Actions taken
- Refreshed the two stale private asset valuations from an independent source and restated client reports where the change exceeded the reporting threshold, with notes to each affected client.
- Required a second approver for every manual price override and every trade amendment, enforced by the system rather than by a written instruction to the desks.
- Made the override reason field mandatory with a controlled list of valid reasons, and reviewed the existing blank entries with the desk heads within the month.
- Set a standing valuation calendar so no private asset mark could age beyond its agreed refresh interval without an exception approved by the chief operating officer.
Results
The two stale valuations were refreshed within the first week of remediation, and one required a restatement that moved reported value by 0.8 percent for the affected portfolio. In later reviews, the override sample passed on the second attempt, after blank reasons fell from about a third of sampled entries to fewer than ten. Two amendment findings remained open because the approver list had not been updated for a departed analyst, and the committee kept them on the agenda until closure tests passed. The audit committee accepted the closure approach and asked for the same test design next time.
Questions for discussion
- Which finding would the committee have ranked higher if the override log had been complete, and would the ranking have changed?
- When should a control owner be allowed to close a finding they designed, if the test is run by someone else?
- How much of the valuation backlog should be reviewed before the next committee meeting, and how much can wait?
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.