Financial Statement Analysis and Reporting Case Studies
Finance5 Case StudiesUpdated Sep 2026
Financial statements look settled once published, but the work behind them is full of small disagreements someone must resolve. The five cases here come from routine practice: a ledger that will not tie to the bank, a cash forecast drifting from plan, a flagged payment, a thinly supported loan request, and an audit report needing owners. Each turns on four matters: how reliable the records are, how much exposure sits behind an error, what evidence shows a control operated, and where a judgment must be escalated. The organizations are fictional; the decisions are not.
Case Study 1
Inventory receipts that never reached the general ledger
Cobalt Ridge Distribution, a regional parts distributor running three warehouses and 1,400 trade accounts.
The situation
Cobalt Ridge closes its books at the end of each month, and at the most recent close the inventory subledger carried $318,400 more value than the general ledger control account. Nobody noticed until the external auditors asked for a tie-out during interim fieldwork. The warehouse system posted a goods receipt when an operator scanned a pallet, while accounts payable posted the vendor invoice when it arrived by email. Timing differences were expected, since receipts near period end often reached the subledger days before the invoice did. The gap, however, was far larger than timing could explain, and it had grown across three closes.
The challenge
Marisol, the controller, had to answer three questions before the lender package went out: how much of the gap was real, which entries caused it, and whether the same failure could repeat in the next close. The warehouse team was already short on staff, and no single report matched receipts to invoices line by line across the two systems. The lender had already asked for the revised balance sheet twice.
Analysis
The first step was to treat the two records as independent evidence. The subledger held 4,112 open receipts and the ledger held 3,986 matched invoices, so the 126 unmatched receipts became the working list. Of the $318,400, roughly $41,000 came from receipts posted twice after a scanner timed out and an operator rescanned the pallet. The remainder was goods received but never invoiced, an accrual reversed too early in each close. A $25,000 threshold per account turned the search into a short list of entries that had to be cleared before sign off.
Teams grounded in Financial Statement Analysis and Reporting usually ask a second question once the amount is traced: what evidence proves the fix worked. At Cobalt Ridge the scanner timeout had no log entry that anyone reviewed, so the duplicate receipts were discovered only by matching timestamps by hand. The accrual reversal had a preparer signature but no reviewer signature, which meant the control existed on paper and not in practice. A useful control here produces evidence each period: a daily exception report of receipts without invoices after a set number of days, reviewed and signed by someone outside the warehouse team. Without that record, an auditor would repeat the exercise.
- Capture receipts Warehouse scans each pallet once and flags any rescan for supervisor review.
- Match invoices Accounts payable matches vendor invoices to open receipts within the ten day window.
- Review exceptions Controller reviews every reversal above $25,000 and signs the aging report weekly.
- Lock and evidence Preparer and outside reviewer sign the tie-out before the close is locked.
Actions taken
- Freeze the scanner timeout rule so a rescanned pallet creates a warning and a second receipt is blocked until a supervisor confirms the first one.
- Reverse the accrual only when the matching invoice posts, and require the controller to review every reversal above $25,000 before the close is locked.
- Run a daily aging report of receipts without invoices, and escalate to accounts payable any receipt older than ten days, with the log kept for audit.
- Add a reconciliation sign off to the close checklist that requires a preparer, a reviewer outside the warehouse team, and a dated tie-out of each control account.
Results
The duplicate receipts were reversed in the second week, which reduced the inventory asset by $41,000. Correcting the accrual cleared the remaining $277,400, and the interim balance sheet was restated for that item before the lender saw it. Marisol sent a short memo that named the cause, the control changes, and the threshold. In the following close the aging report flagged nineteen receipts, all cleared inside the ten day window, and the tie-out was signed before the close was locked.
Questions for discussion
- Which of the four actions would you put first if the scanner vendor could not change the timeout behavior for six weeks?
- How would you set the aging threshold for receipts from vendors with long shipping lead times, and who should approve an exception?
- What evidence would convince an external auditor that a control operated in a period with no exceptions at all?
Case Study 2
Seasonal revenue miss tests the cash plan
Larkspur Home Goods, an importer and online retailer of kitchen and bath products with two distribution centers.
The situation
Larkspur approved its annual plan with a revenue target that assumed steady growth in online orders and a stable freight rate. Midway through the peak season, order volume ran about 14 percent under the plan, while container freight costs rose sharply on the lanes that carried most of its inventory. The finance team had built the plan on a quarterly cash forecast that linked receipts to shipments, but the link assumed that promotional discounts would stay at the planned depth. Discounts had already been deeper than planned for two weeks. The revolving credit line covered the working capital gap only if collections held up.
The challenge
Ines, the chief financial officer, had to decide before the next board call whether to cut inventory buys, extend a promotion, or draw on the credit line early. Each option moved revenue, margin, and covenant headroom in different directions, and the forecast model did not yet show those trade-offs side by side. The board wanted a single recommendation, with the downside case stated plainly.
Analysis
The model had one scenario, which was the plan. The rebuild used three cases. The base case held the current run rate and discount depth through the peak. The downside case kept order volume 14 percent under plan and pushed freight costs up another 9 percent on the main lane. The severe case added a two week receiving delay that moved part of the holiday revenue into the next period. Each case was tested against a minimum cash balance of $850,000 and a leverage ratio that had to stay at least 0.3 turns under the covenant level.
The assumptions that mattered most were not the ones in the plan. Discount depth and collection timing carried the most weight, so the team checked each against records instead of the sales summary. Discount depth came from the point of sale export, which showed the planned depth was exceeded on about a third of orders. Collections were tested against the aging of receivables from the prior peak, where the share paid within thirty days had fallen. The freight assumption was tested against three signed carrier quotes rather than the rate card. The review turned up a single error: the plan had counted returns as revenue in the second half.
Actions taken
- Hold inventory buys at the current level for the peak, and release only the orders that the carrier quotes cover at the signed freight rate.
- End the deepest promotion early on categories where discounts already exceed plan, and keep the shallower offer running until projected cash stays above the threshold.
- Keep the revolving line undrawn unless the downside case breaches the cash threshold, and set a standing trigger when projected cash falls below $1,200,000.
- Remove returns from revenue in the restated plan, and report the reforecast to the board with all three cases and the covenant headroom in one table.
Results
The board approved a reduced buy for the peak and a shorter promotion on the two categories with the deepest discounts. Projected cash stayed above the $850,000 minimum in the base and downside cases, although the severe case still required the credit line for about three weeks. Leverage held with 0.4 turns of headroom in the downside case, which was tighter than the plan but inside the covenant. The restated plan showed revenue about 6 percent lower than the original, a figure the board accepted because it matched the records.
Questions for discussion
- Which assumption in the plan would you test first if the freight quotes expired before the peak began?
- How should the leverage headroom target change if the covenant test falls at a different point in the season?
- When sales staff argue that a deeper discount protects share, what evidence would you require before approving it?
Case Study 3
Structured payments that tripped three screening rules
Brightline Remittance, a licensed payments firm that moves vendor and payroll funds for about 600 small business clients.
The situation
Brightline Remittance processes outbound vendor payments for small businesses. In the third week of the quarter, the monitoring queue flagged a client account, Tallow Creek Hardware, after it sent 14 wire transfers over four days, each just under the $10,000 internal review level. The transfers went to three new beneficiary accounts at two banks, and the beneficiaries had been added by a single user from an IP address that also logged in to an unrelated client portal. The client's stated reason was a bulk supplier payment schedule that the account manager had reviewed by phone but not in writing.
The challenge
Hakim, the compliance officer, had to decide whether to hold the transfers, file a report, or release them with enhanced questions. The client had a clean history over several years, and the account manager was keen to keep the relationship. The file held no signed supplier list, and the hold window before the next batch was short. Releasing the funds on a verbal explanation would leave no record.
Analysis
Taken one at a time, each transfer looked routine. Together they formed a pattern: total value of $138,600 over four days, a median amount of $9,700, and three beneficiary accounts that had never received funds from this client before. The internal review threshold of $10,000 was a control, but it also told anyone structuring payments exactly where the line sat, so the team treated a cluster of transfers just below it as a stronger signal than any single one. The escalation rule required a second-level review when aggregate value exceeded $100,000 within five days for new beneficiaries, which this account crossed on the third day.
The documentation was the weakest point. The phone call about the supplier schedule was a note with no date stamp or named counterparty, and the new payees carried no approval in the system. The written screening procedure requires dual approval and a verified client contact for any payee change on a recently opened account, and three of the beneficiaries met neither test. A clean name screen did not explain why one user added payees from a device shared with an unrelated client. Clustered indicators of this kind required a suspicious activity assessment under the firm's own standard, so the file could not be closed on the screening result alone.
Actions taken
- Hold the remaining transfers in the batch and require a signed supplier schedule, with the contact verified by callback to the number on file.
- Freeze payee additions on the account and ask a second approver to confirm the three new beneficiaries against the bank's account ownership records.
- Open a suspicious activity assessment in the case system, record the indicators that clustered, and set the decision deadline so the file cannot age silently.
- Review the other accounts that used the same login device in the past quarter, and apply the $100,000 five day aggregate rule to each one.
Results
The suspicious activity assessment was filed within the reporting window, and it described the clustering pattern rather than the client's explanation. Callbacks confirmed two of the three new beneficiaries, and the third was closed before any further transfer. The client account now sends payments only to reviewed payees for 60 days, and the supplier schedule arrived in writing. The device review found one other client account with a similar pattern, which was escalated the same day and remains under review.
Questions for discussion
- At what point would you have moved from a hold to a report, and what new fact would have changed that timing?
- How should a firm weigh a long, clean client history against a short cluster of indicators that all fall just below a control threshold?
- Which records would you require before accepting a verbal explanation from an account manager for a bulk payment schedule?
Case Study 4
Expansion loan request for a second production line
Pellmore Kitchens, a regional maker of commercial kitchen equipment with one plant and about 180 dealer accounts.
The situation
Pellmore Kitchens asked its relationship bank for a $4,200,000 term loan to fund a second production line and a larger warehouse. The company had two years of audited statements, which showed revenue growing and a gross margin that had slipped as steel costs rose. Its largest dealer accounted for about a fifth of sales, and the order backlog covered roughly four months of production. The owner projected that the new line would double output within the first year after commissioning and lift EBITDA by about a third. The bank's credit team had until the end of the month to recommend a decision to the loan committee.
The challenge
Owen, the senior credit officer, had to decide whether the projections could carry the debt service under a downturn, and whether the owner's personal guarantee and the equipment pledge were enough to cover a shortfall. The request also raised a suitability question: the bank had no prior lending relationship with a manufacturer of this size, and the loan officer's notes were thin on the dealer contracts.
Analysis
The historical statements did not support the projection without adjustment. Gross margin had fallen from about 28 percent to about 24 percent, and operating cash flow covered interest but left little room for principal. The team rebuilt the forecast from the order book and the dealer contracts rather than the owner's growth rate. The base case assumed the new line ran at 60 percent of capacity in the first year. The downside case cut dealer volume by a third and held steel costs at their recent peak. Under the downside, debt service coverage fell to 1.05 times, which sat below the bank's 1.25 times minimum.
Control evidence mattered as much as the numbers. The dealer contracts were not in the file, only a summary written by the loan officer, so the team could not confirm termination rights or volume commitments. The equipment pledge was valued at the owner's estimate, and an independent appraisal would show the resale value of the existing press. Given the thin evidence, the bank could consider a smaller facility sized to the base case, a delayed draw tied to the second line's commissioning, and covenants that test coverage quarterly. Those conditions turn an uncertain projection into a structure the bank can monitor.
- 1Test the projectionsRebuild the forecast from the order book and contracts, not the growth rate.
- 2Run downside casesCut dealer volume by a third and hold steel costs at peak levels.
- 3Verify collateralObtain an independent appraisal before accepting the owner's pledge value.
- 4Check coverage thresholdApprove only if base case coverage clears 1.25 times in every quarter.
- 5Set conditions or declineAttach delayed draw and quarterly tests, or reject the request as submitted.
Actions taken
- Approve a facility of $3,100,000 sized to the base case debt service, with the remaining amount available only after the second line commissions.
- Require the signed dealer contracts, including termination notice and minimum volume terms, before any drawdown beyond the initial tranche, starting with the largest dealer.
- Commission an independent appraisal of the existing press and the planned line, and advance only the portion of the pledge the appraisal supports.
- Set a minimum debt service coverage of 1.25 times tested each quarter, with a cure period of one quarter before the facility is repriced.
Results
The committee approved a facility of $3,100,000 with a delayed draw and quarterly coverage tests, and declined to fund the full request. The owner accepted the structure after the largest dealer confirmed a three year volume commitment. The first coverage test came in above 1.25 times in the quarter the second line was commissioned, although the margin was narrow. The file now carries a standing item for the dealer contract review, which the relationship manager owns.
Questions for discussion
- Which downside scenario would you add to the model before accepting the owner's output projections, and why?
- If the largest dealer will sign only after the loan closes, how would you sequence the conditions?
- What evidence would justify relaxing the coverage covenant after the second line has run for several quarters?
Case Study 5
Billing control findings ranked for remediation
Tallgrass Veterinary Group, a network of eleven clinics sharing one billing center and about 9,000 active client accounts.
The situation
Tallgrass Veterinary Group runs eleven clinics that send their invoices through one shared billing center. The internal audit team reviewed the billing cycle over the past two quarters and issued a report with five findings. The most serious was that credit memos could be approved by the same clinic manager who requested them. Other findings covered unbilled procedures, a write-off policy applied inconsistently, stale deposit balances, and manual price overrides with no reason codes. Management responded within the usual window, but the responses lacked owners, dates, and any description of the evidence that would show each fix had worked.
The challenge
Dorothea, the group controller, had to rank the five findings by materiality, assign accountable owners that were not the same people who had caused the gaps, and define closure tests the audit committee would accept. The committee wanted the plan before the next quarterly meeting, and two of the findings touched revenue that had already been reported. Her team had three weeks to turn the report into a plan.
Analysis
Ranking started with exposure, not with the order the auditors listed the findings. Credit memos totaled $486,000 over the period, and the approver and requester were the same person on 212 of them, which made this the largest reach. Unbilled procedures came second, with an estimated $133,000 of services delivered but not invoiced, traced from appointment records. The stale deposits involved many accounts but only about $19,000 in value. The price overrides and write-off inconsistency were control failures with smaller dollar effects. The group set $50,000 as the threshold for material findings, and anything touching reported revenue moved to the top.
Closure needs evidence that a control operates, not a memo saying it was redesigned. For the credit memo finding, the test is a system rule that blocks approval when requester and approver match, plus a sample of later memos showing the rule fired and was not overridden. For unbilled procedures, a weekly sample of appointments compared against invoices must stay below an agreed exception rate for three consecutive weeks. Owners should sit in finance or operations and should not run the clinics they test.
- Week oneBlock self-approval of credit memos and assign all five owners in writing.
- Weeks two through fourStart weekly appointment sampling and block overrides that lack a reason code.
- After five weeksUnbilled exception rate falls below target, and the sampling test is signed off.
- Within the quarterComplete deposit recovery and rewrite the write-off policy for committee review.
Actions taken
- Block self-approval of credit memos in the billing system this week, and route any memo above $5,000 to the group controller for a second approval.
- Assign the unbilled procedures fix to the operations director, with a weekly sample reviewed by the revenue accountant and a target exception rate.
- Recover the $19,000 of stale deposits through refund or application within the quarter, and assign the write-off policy rewrite to the credit manager.
- Make reason codes mandatory on every manual price override, and have the finance systems analyst test the code list against a full month of activity.
Results
The credit memo rule went live in the first week, and the follow-up sample showed no self-approved memos in the next period. The unbilled exception rate fell below the agreed level after five weeks, which was later than the target but within the committee's tolerance. Recovery of the stale deposits was complete before the quarter closed. The audit committee accepted four of five closures and kept the unbilled finding open for one more cycle, with a named owner and a weekly report.
Questions for discussion
- Which of the five findings would you rank first if the revenue impact turned out to be larger than the appointment records suggest?
- How would you test closure for the price override finding if the billing system cannot force a reason code on every entry?
- What separates an owner who can credibly close a finding from one who only reports its status, and how would you check the difference?
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.