Financial Accounting and Reporting Standards (IFRS/GAAP) Case Studies
Finance5 Case StudiesUpdated Sep 2026
Standards like IFRS and GAAP read cleanly on paper, but they are tested in the ledger. The five cases below come from fictional organizations and follow finance teams through problems most practitioners will recognize: records that disagree, forecasts that drift, warning signs in a live portfolio, a funding request built on thin evidence, and an audit that finds gaps nobody expected. Each case runs from facts to analysis to action. Pay attention to how deadlines, approval controls, and ledger integrity shape what a team can prove and when it can prove it.
Case Study 1
A subledger gap that hid a double import
Pellmore Logistics Group, a regional freight operator with four subsidiaries and a shared finance service center.
The situation
Pellmore's controller noticed during the first week after quarter-end that the accounts payable subledger and the general ledger control account differed by 184,300 dollars. The gap was small against quarterly revenue but large enough to block the close checklist. Vendor statements from the three largest fuel suppliers did not match either figure. The shared service center processed about 9,000 invoices a month across four entities, and most approvals ran through a workflow tool that let approvers release payments on a single click if the invoice had been matched to a purchase order. Nobody could say with confidence which entity had posted what, or whether duplicate invoices had been loaded.
The challenge
The close calendar allowed four working days for reconciliation before the consolidated statements went to the audit committee. The team had to identify the variance, decide what to book, and avoid adjusting entries that would hide the cause. Two staff members were already committed to a separate tax filing. The controller also needed to know whether the variance pointed to a control failure that the external auditors would have to test, because a weak control would change the scope of their work.
Analysis
Teams grounded in Financial Accounting and Reporting Standards (IFRS/GAAP) usually start by asking whether the two sides were ever meant to agree. The subledger holds invoice detail and the control account holds summaries. A posting without a matching subledger record is an integrity problem, not a timing issue. Here the batch history showed a bulk import run twice for one entity during a system migration, which explained most of the gap. The remainder came from a foreign currency invoice translated at a rate that differed from the payment system. The invoice should have been measured at the transaction date rate and then remeasured at the reporting date.
The second question is why the duplicate reached payment at all. The approval workflow released invoices once they were matched to a purchase order, but it did not check whether the same vendor invoice number existed in another entity. That is a design gap in the approval control, not a failure of the people using it. The close deadline made it worse. With four working days for reconciliation, the team could not wait for vendor statement confirmation, so they relied on the batch log instead. A useful test is whether a control would have stopped the error on the day it occurred, and here the answer was no.
Actions taken
- Reverse the duplicate import entries for the affected entity and document the batch reference, the approver, and the posting date in a single correction memo. Attach the subledger extract that supports the reversal.
- Add a duplicate check on vendor and invoice number across all four entities so the workflow blocks release before payment, with an override that requires a second approver and a written reason.
- Run a daily tie-out of subledger totals to control accounts for each entity during the close window, and require a signed variance log before any manual journal is posted to a control account.
- Set a rule that unexplained differences above a fixed threshold escalate to the controller on the day they appear, and tell the external auditors which control changed and when it took effect.
Results
The duplicate entries were reversed early in the close window, and the subledger and control account agreed for all four entities before the consolidated statements were drafted. The residual foreign currency difference was corrected through a documented remeasurement entry. The duplicate check blocked two similar invoices in the following month, both loaded by different entities for one vendor. The external auditors tested the revised workflow and reduced their sampling of payables for that period, though they still asked for the variance log. The controller now reviews the daily tie-out before the first board pack leaves the building.
Questions for discussion
- Which of the four controls in this case would have prevented the error on the day it occurred, and what would it have cost to run it?
- How should a team decide whether a posting error is a one-time measurement problem or evidence of a deeper design weakness in the ledger?
- What evidence would you ask a shared service center to produce before you accepted its month-end subledger totals as reliable?
Case Study 2
A revenue shortfall that exposed stale receivables aging
Calloway Beverage Partners, a regional bottler and distributor serving independent grocers in three states.
The situation
Calloway's finance team built its annual forecast in the autumn, before a large grocery chain announced it would consolidate suppliers. By the fourth month of the year, revenue from that account was running 22 percent below plan, while packaging and freight costs had risen because the company had committed to a new bottling run. Operating cash flow had turned negative for two consecutive weeks. The forecast had been built on a ledger of about 14,000 open customer invoices and a receivables aging that assumed customers paid within their terms. Nobody had stress tested the payment assumption, and the board wanted a revised outlook before the next financing review.
The challenge
The revised forecast had to answer three questions in one sitting: how much of the revenue gap was permanent, how long the cash shortfall would last under different collection patterns, and which costs could be deferred without damaging the business. The treasurer needed a range rather than a point estimate, and the lender wanted to see that management had tested its own assumptions before asking for a covenant waiver.
Analysis
Start with the transaction records, because a forecast is only as good as the ledger underneath it. The team traced the open invoice population and found that about a fifth of the balance from the affected account carried payment terms that had been changed in the master file after the original sales orders were posted. Those changes did not alter the invoice records, so the aging report showed the new terms against old dates. That is an integrity problem that made receivables look healthier than they were. The team first rebuilt the aging from invoice data and reconciled it to the control account, which took most of a week.
Scenarios should rest on the assumptions that carry the most weight. The team defined a base case in which the lost account recovered half its volume by the end of the next quarter, a downside in which it did not recover at all, and a severe case that added slower collections from two other grocers. Approval controls mattered too. The board packet could only include figures that the controller had signed off after the close, so the team presented ranges and marked which inputs were still provisional. That discipline made the forecast harder to write and far easier to defend.
- Rebuild the base Reconcile aging and orders to control accounts before changing assumptions.
- Test assumptions Run base, downside, and severe cases, each with named inputs, owners, and source documents.
- Check approvals Confirm the controller has signed off each input that reaches the board packet.
- Decide and monitor Set cash triggers for deferred spend and review actuals against the chosen case monthly.
Actions taken
- Rebuild the receivables aging from invoice-level data, flag every invoice whose terms changed after posting, and reconcile the result to the control account before any scenario is circulated.
- Write each scenario as a list of named assumptions with a numeric value, an owner, and a source document, so that the board can see which input moved the outcome most.
- Defer discretionary packaging purchases and the second bottling run until collections on the affected accounts stabilize, and set the trigger as a measured cash threshold rather than a calendar date.
- Ask the lender for a covenant review based on the base case, and attach the downside and severe cases with the sign-off status of each input so the waiver request rests on evidence.
Results
The rebuilt aging moved about 3,400 open invoices into a later collection window, which lowered the forecast cash position for the next two months but made the shortfall predictable. The board approved a revised outlook with a base, downside, and severe case, and the packaging purchase was reduced to the minimum needed for existing orders. The lender granted a short covenant review rather than a waiver, with a monthly reporting requirement. By the end of the following quarter, collections on the affected accounts had improved enough to trigger the deferred bottling run, which went ahead on the revised schedule.
Questions for discussion
- Which of the three scenarios would you have presented first to the board, and what evidence would have changed your choice?
- How would the forecast have looked if the aging had been rebuilt before the original plan was approved, and which inputs would have moved?
- When is a covenant review a better outcome than a waiver request, and what does the lender need to see to agree?
Case Study 3
A counterparty name mismatch inside a bond fund
Hollis Ridge Asset Management, a small manager running three bond funds and a private credit sleeve for institutional clients.
The situation
Hollis Ridge's compliance team received an alert in the second week of the month, after a bond fund's net asset value moved once the close had already been locked. The alert traced to a privately placed note bought from a counterparty that had been added to the approved list only three days earlier. At cost, the position was about 4.6 percent of the fund's net assets, which sat above the single issuer limit in the prospectus. Trade confirmations, valuation committee minutes, and the broker statement each named the counterparty differently. The fund accounting system had booked the trade under a holding entity that did not appear in the investment register.
The challenge
The compliance officer had to decide whether the alert was a documentation error or something more serious, such as a related party purchase or a valuation set to stay under a limit. The fund's board met in four days, and the valuation committee needed to know whether the note should be marked down before the next published price. The officer also had to decide whether the event triggered a notification to the regulator, and on what timeline.
Analysis
The first task was to find which record was wrong. The trade confirmation named the counterparty's legal entity, the valuation minutes used a trading name, and the ledger carried a holding company created that same week. Ledger integrity depends on a single traceable link between the instrument, the counterparty, and the holding entity, and here that link was missing. The approval workflow had allowed the trade to be entered before the counterparty was cleared, because the desk could post provisional bookings with a compliance flag that nobody reviewed before the close. The close then carried the old price forward. Each step looked routine on its own.
The exposure question is separate from the record question. At cost, the position exceeded the single issuer limit, and the rules in the prospectus measure that limit at the time of purchase, so the breach is real whatever the later valuation. Documentation has to show when the limit was checked and by whom. Escalation depends on the fund's governance documents and the applicable securities rules, which counsel reviewed. The safest path was to treat the breach as reportable at once, to freeze further purchases from the counterparty, and to hold the published price until the valuation committee had reviewed the marked-down figure.
Actions taken
- Freeze new purchases from the counterparty and flag the holding entity in the investment register, with the approver and timestamp of the change recorded in the audit trail.
- Reconcile the three counterparty names to a single legal entity identifier, and correct the trade confirmation, minutes, and ledger entry so each record points to the same instrument.
- Require compliance clearance before any trade can be booked, and have the system block provisional bookings that carry an open compliance flag at close.
- Mark the note down to the committee's independent value, recompute the limit test at cost and at the revised value, and document both results for the board and the auditors.
Results
The holding entity was mapped to the correct legal counterparty within the week, and the duplicate names disappeared from the records. The note was marked down by a little under a fifth of its cost, which brought the fund back within its single issuer limit at the revised value but left the historical breach on file. The board received a written account of the timing, the approvals that failed, and the control changes. The regulator was notified within the window the governance documents required, and the auditors reviewed the revised workflow with a narrower sample than they had planned.
Questions for discussion
- Which quadrant would you place the alert in before any valuation work had started, and what information would move it?
- Why does an exposure measured at cost sometimes matter more to a limit test than the current mark, and when would you disagree?
- What should a compliance officer be able to show an examiner about the time between a trade being booked and its counterparty being cleared?
Case Study 4
A term loan resting on an unsigned contract
Ferris Valley Commercial Bank, a community lender with eleven branches, reviewing a request from Tallis Fabrication, a precision parts maker with two plants.
The situation
Tallis Fabrication asked Ferris Valley Commercial Bank for a 4,200,000 dollar term loan to refit a second plant with automated machining. The company had grown steadily for several years, with revenue of about 31,000,000 dollars in its most recent fiscal year. The request came with three years of audited statements, a management forecast, and a draft equipment schedule. The owner pointed to a large contract with a regional automotive supplier that would begin in the next fiscal year. The credit committee had seen the company before, but the last facility had been paid down early, and the file did not show how the current receivables were distributed across customers.
The challenge
The loan officer had to decide whether the forecast deserved weight. Revenue growth depended on a single contract that had not yet been signed, and the equipment payments would start before that contract produced cash. The committee wanted to know what happened to debt service if the contract slipped by two quarters, if the supplier cut volumes, or if the plant ramp took longer than the schedule showed. The answer would decide the amount, the term, and the covenants.
Analysis
Start with the books. The audited statements show revenue and margins for three years, but the receivables detail was a summary aging with no customer breakdown, and the reconciliation between the aging and the general ledger differed slightly in the most recent year. A gap like that is not disqualifying on its own, though it means the aging cannot yet be trusted for collection timing. The team asked for invoice-level detail for the trailing twelve months and rebuilt the customer concentration table from it. Only then did the revenue assumption carry weight, since the table showed heavy dependence on two customers.
The downside case mattered more than the base case. The team built three scenarios: the contract starts on time, the contract slips by two quarters, and the contract never starts while fixed costs continue. Under the second scenario, debt service coverage fell below the bank's internal minimum for two quarters, which policy permits only with a mitigation plan. Suitability also counted. A facility of this size, with a plant ramp and a single anchor contract, belonged in a structure with a longer interim period, a reserve account, and a covenant tied to the contract signing date rather than to a calendar. Approval was therefore conditional on those terms and on the receivables rebuild.
Actions taken
- Require invoice-level receivables for the trailing twelve months, tie the customer concentration table to the general ledger, and sign off the reconciliation before the committee reviews the request.
- Model debt service under the three contract timing scenarios using the borrower's actual margins, and set the minimum coverage ratio the facility must hold in the slip case.
- Structure the loan with an interest-only period that ends on contract signing, a debt service reserve account, and covenants measured on quarterly actuals rather than projections.
- Set the approval as conditional, with release of funds tied to a signed supplier contract and a second approver confirming that the reconciled aging matches the ledger on the release date.
Results
The committee approved a reduced facility of 3,600,000 dollars with a twenty-four month interest-only period ending on contract signing. The supplier contract was signed in the third quarter of the loan's first year, and the reserve account was not drawn. Coverage fell below the slip-case minimum for one quarter, which the mitigation plan had anticipated, and the company remained within its covenants. The receivables rebuild showed that the two largest customers accounted for most of the revenue growth, so the bank added quarterly concentration reporting. Management accepted the conditions without objection.
Questions for discussion
- Which single assumption in the forecast would you test first, and what document would you ask for to test it?
- Should a lender ever approve a loan whose repayment depends on a contract that has not yet been signed, and what structure would make that acceptable?
- How would you weigh a reconciliation gap in a borrower's aging against the strength of its audited statements?
Case Study 5
Remediating control gaps across a hotel group
Brindle Hospitality Group, a hotel operator with six properties and a central accounts payable and general ledger team.
The situation
Brindle's internal audit team and the external auditors reviewed the group's control environment in the same period, and both arrived at overlapping concerns. Six properties fed a central ledger through a nightly interface, and the interface did not reject entries that lacked a valid cost center. Manual journal entries for accruals were approved by the same person who prepared them at two properties. Cash counts at the front desks were recorded in a spreadsheet that the property manager could edit. The audit committee had asked for a ranked list of findings, owners, and closure tests before the next meeting, and the chief financial officer wanted every finding traced to a specific transaction record, not to a general impression.
The challenge
The findings varied widely in severity. Some were likely to produce misstatements in the consolidated accounts, while others were process weaknesses with no present error. The team had to rank them by materiality, assign owners who could actually fix the problem, and define closure tests that a reviewer could repeat without relying on the owner's word. The challenge was to avoid a list that treated every item as equally urgent.
Analysis
Ranking began with the transaction records rather than with the finding titles. For each finding the team pulled the affected entries and their dollar value. The interface finding looked alarming because it allowed unvalidated entries, but testing showed that about 1.2 percent of nightly entries lacked a cost center and that all of them were reclassified before the month-end close. The accrual approval finding was smaller in count but more serious: the same person preparing and approving entries means no independent check on estimates. Materiality was judged on the combined effect on the consolidated balances, and on whether a misstatement could be concealed by the control weakness itself.
Owners and closure tests depend on the close calendar. The interface fix could be owned by the systems lead because it required a validation rule at the point of entry, while the accrual finding belonged to the controller because only the controller could reassign approval rights. Closure tests were evidence-based: for the interface, a rerun of the nightly batch over two consecutive close periods with zero unvalidated entries; for accruals, a sample of journal entries showing a different preparer and approver with the approval timestamp before posting. Cash count spreadsheets were closed only when the edit history was locked and a second person had signed the count sheet.
- 1Log and rankRecord each finding with affected entries, dollar value, and periods exposed.
- 2Assign ownerName one accountable person who can change the control, not only the report.
- 3Fix the controlChange the system rule, approval right, or count process at the source.
- 4Run closure testRepeat the test over consecutive periods using filed evidence and an independent reviewer.
- 5Report and closePresent closure to the audit committee with evidence references and reviewer sign-off.
Actions taken
- Add a validation rule to the nightly interface that rejects entries without a valid cost center into a suspense queue owned by the systems lead.
- Separate preparation and approval of accrual entries by changing user rights in the ledger, and require a second approver for any accrual above a set threshold until the controller signs the closure test.
- Lock the cash count spreadsheets at each property, move counts into the controlled system, and require two signatures on the count sheet on the day the count is taken.
- Report closure to the audit committee only after the rerun and sample tests are filed with the owner's name, the evidence reference, and the reviewer's independent sign-off.
Results
The interface rejected its first batch of unvalidated entries in the following close, and the suspense queue cleared within two business days. Accrual approvals were split across two people at all six properties, and the second approver caught one estimate that had been entered twice. Cash counts moved into the controlled system at four properties, with the remaining two scheduled for the next quarter. The external auditors reduced their reliance on property-level testing and asked for the rerun evidence each period. Two findings remained open at the committee's review, both with named owners and closure tests.
Questions for discussion
- How would you rank a finding that is small in dollar terms but could conceal a larger misstatement, and which evidence would settle the ranking?
- What makes a closure test independent of the owner who fixed the control, and how many periods of evidence should a reviewer require?
- When should internal audit accept a remediation that changes the process but has not yet produced a clean close?
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.