Accounts Payable Management Case Studies
Finance5 Case StudiesUpdated Sep 2026
Payables sits where operations, treasury, and financial reporting meet, so a single bad entry rarely stays contained. A duplicate approval or a vendor statement that will not tie to the subledger can distort cash, expense, and liabilities at the same time. The five cases below come from different organizations and different pressure points. Each one tests the same things: whether transaction records are complete, whether the ledger still reflects them, whether approvals did their job, and whether there was time before close to catch the problem. The notes are written from the people who did the repair work.
Case Study 1
Three ledgers that refused to agree at quarter end
Corvane Industrial Supply, a distributor of pump and valve parts with four regional warehouses and about 620 active vendor accounts.
The situation
At Corvane, the payables subledger and the general ledger control account were supposed to agree at the end of every close. In the second week after quarter end, the controller noticed a gap of $48,300 between them. The gap sat in the liability line the lender reviewed, and the close calendar had four working days left before the package went out. The AP lead, Dorian, pulled the vendor statements for the top twelve suppliers and found that three of them showed invoices that the subledger had recorded as paid. The payment file had been transmitted, but the bank confirmation for those runs had arrived late and was keyed against the wrong batch number.
The challenge
The team had to answer three questions before the close deadline: which of the three records was wrong, whether the subledger or the bank file held the true payment status, and how many other batches carried the same keying error. Dorian could not simply reverse the entries, because the ledger had already been posted to the period that the lender would review. Anything they changed had to be documented with the original posting reference, and the approval trail for each adjustment had to show who authorized it.
Analysis
The first step was to stop treating the three records as equal. Dorian matched each open item on the vendor invoice number plus the remittance date, then sorted the mismatches by cause rather than by amount. That produced four buckets: timing differences inside the cutoff, keying errors in the batch reference, duplicate postings, and items that existed only in the vendor's records. Teams grounded in Accounts Payable Management tend to sort before proposing any fix, because the bucket counts show whether the failure is in the process or in a single event. At Corvane, keying errors held most of the dollar value, while the duplicates were few but expensive per item.
The keying error pointed to a control gap rather than a person. The payment run template allowed the batch reference to be edited after the bank file was generated, and nothing in the system required the bank confirmation to match the batch before the payment status changed. Approval for the payment run was recorded correctly, so the approval step worked, but it only tested the amount and the vendor, not the reference that tied the cash to the ledger. The close calendar made the problem worse, because the controller had scheduled the reconciliation for the last day, leaving no room for a second pass on the affected suppliers.
Actions taken
- Lock the batch reference once the bank file is generated, and require the bank confirmation to match that reference before any payment status changes in the subledger.
- Add a second approval check on payment runs that compares total cash released to the sum of ledger postings, with variances above a set threshold held for review.
- Run a weekly three-way match for the top twenty suppliers, comparing vendor statements, the subledger, and bank activity, and log every break with an owner and a clearing date.
- Move the payables reconciliation to the third working day of close so that breaks found in the first pass can be corrected and re-tested before the package is locked.
Results
Within the close window, the team cleared 41 of the 44 open breaks, and the remaining three were traced to a bank cutoff difference that the treasury group confirmed the following week. The subledger and control account agreed to the cent before the package went out. The batch reference lock was live for the next quarter's runs, and the first weekly three-way match caught two duplicate postings that would otherwise have reached the lender's review. The investigation took six working days, and the sorting step is now a standard template for the close checklist.
Questions for discussion
- Which of the four buckets would have been hardest to detect with the controls that existed before the close, and why?
- How should the threshold for a second approval on payment runs be set so that it catches real variances without holding routine runs?
- When the bank file and the subledger disagree, what evidence should decide which record is treated as authoritative?
Case Study 2
Cash forecast falling apart as input costs climb
Ostrander Pet Nutrition, a regional maker of dry and wet pet food with two plants and about 240 wholesale accounts.
The situation
Ostrander planned its cash position around a stable input cost base and a volume increase of about 6 percent for the year. By the middle of the second quarter, the payables ledger told a different story. Supplier invoices for meat meal and packaging had risen faster than the plan assumed, and two large wholesale accounts had moved their payment terms from thirty to sixty days. The cash forecast, prepared by Marisol in finance planning, still showed a minimum balance of $1,840,000 at the end of the quarter. Her revised model suggested the true low point could fall well below that, and the revolving line covenant required the company to stay above a set liquidity floor.
The challenge
The question for the planning group was not whether the forecast was wrong, since everyone knew it was, but what response could be defended to the lender and the board. Cutting spend broadly would hurt production, while drawing the full line would raise interest cost and signal stress. Each scenario depended on assumptions about payment timing, supplier credit limits, and when the next price contract reset, and none of those assumptions had been tested against the actual invoice ledger.
Analysis
Marisol started by rebuilding the payment timing assumption from the transaction records rather than from the terms schedule. Over four quarters she traced each paid invoice through its receipt date, approval date, and payment run. The company was paying about nine days later than terms implied, because raw material invoices sat in approval queues during peak months. The forecast had used contractual due dates, so that lag never showed up. She also found two supplier accounts with unapplied credit memos, overstating the open payable by a few hundred thousand dollars. Together, the lag and the unapplied credits moved the low point more than the price assumption did.
With the timing error corrected, Marisol built three scenarios: a base case with current volumes and the observed payment lag, a price shock case where protein costs held at the higher level for two more quarters, and a receivables stress case where one of the wholesale accounts paid late again. Each scenario was tied to a named trigger. The approval queue was the cheapest lever, since clearing it did not change any supplier term, and the close calendar showed that the monthly payment run could be moved earlier without breaking the cutoff. A defensible response used the levers the company controlled and disclosed the rest.
Actions taken
- Replace contractual due dates in the cash model with the observed payment lag for each supplier group, refreshed at the end of every close.
- Clear the aged approval queue for raw material invoices by adding a standing approver for amounts under a set limit, so payment runs stop waiting on one manager.
- Apply the two outstanding supplier credit memos and confirm the open payable balance with each vendor before the forecast is reissued to the lender.
- Draw the revolving line only if the price shock scenario crosses the liquidity floor, and set a written trigger that the treasurer reviews weekly.
Results
The corrected model moved the projected low point up, but not enough to close the gap entirely. The company cleared the approval queue within two weeks, which recovered roughly four days of the payment lag, and the wholesale accounts paid within terms on the next cycle. Marisol presented the three scenarios to the board with the trigger for each one, and the line was not drawn. The minimum balance stayed above the covenant floor in the base and price shock cases, though the stress case came within a narrow margin.
Questions for discussion
- Which of the three scenarios would you have ranked as most likely before the payment lag was measured, and what would have changed your ranking?
- How much weight should a forecast give to supplier credit memos that have not yet been applied, and who should own that judgment?
- What single trigger would you put in front of the board to decide when to draw on the line, and how often should it be reviewed?
Case Study 3
Bank change request on a carrier with duplicate invoices
Kettleby Freight Partners, a third-party logistics provider handling inbound freight for four regional manufacturers.
The situation
Kettleby moves inbound freight for four regional manufacturers and pays roughly 310 carriers and subcontractors each month. In the third week of the month, a mid-sized carrier that had been paid steadily for two years submitted a request to change its remittance account. The request came in by email, carried a letterhead that matched the carrier's prior invoices, and asked that the next payment run go to the new account. Within the same week, the payables system showed three invoices from that carrier, each for $38,400, with the same fuel surcharge line and different invoice numbers. The payment run was scheduled to release in two days.
The challenge
The controls had worked in pieces. The bank change had come through an email address on file, the invoices had passed a three-way match because the freight bills had PDF attachments that looked right, and the approver had been signing off on the batch total rather than on individual lines. The compliance officer, Thandiwe, needed to decide whether to hold the payment, whether the event required escalation beyond finance, and what the company owed the carrier if the request turned out to be legitimate.
Analysis
The exposure was easy to size once the transaction records were pulled together. The three invoices totaled $115,200, against a monthly billing pattern of roughly $41,000 over the prior twelve months. The subledger had not flagged them because its duplicate check matched only exact invoice numbers, and the three shared a purchase order and an identical fuel line. Only one of the three invoices had a matching bill of lading and shipment record. The team treated the pattern as a probable duplicate or fabricated billing until the carrier's own records could be checked.
The bank change was the stronger warning sign, and it had passed through a control built for a different risk. Vendor master changes required a call-back to a number already on file, but the clerk called the number in the email signature. Company procedures also send any remittance change made close to a payment run to compliance before release. That rule existed on paper, but few people in payables had been trained to apply it. Thandiwe held the run, notified the bank's fraud desk through the relationship contact, and timestamped each step so internal audit could review the decision later.
- 1Hold the runStop release of the affected batch before any other step.
- 2Verify the changeCall back the carrier on the number already held in the vendor master.
- 3Refer to complianceSend the invoices, bills of lading, and change request with timestamps.
- 4Notify the bankUse the relationship contact to ask for a recall of any sent funds.
- 5Record and reviewLog the decision and send it to internal audit for review.
Actions taken
- Freeze remittance changes for any vendor until a call-back to a contact already held in the vendor master is logged, with the caller's name and the time of the call.
- Run a duplicate test on vendor, amount, and purchase order rather than invoice number alone, and route every hit to a second reviewer before approval.
- Train payables approvers on the compliance referral rule and add it to the payment run checklist, so the referral is triggered by a field in the system, not by memory.
- Review every payment to the carrier over the last twelve months against signed bills of lading, and report any unmatched invoice to compliance with the supporting records attached.
Results
The carrier confirmed by phone, through the number on file, that it had not requested a change. The bank confirmed the attempted redirection had been stopped before any funds left Kettleby's account. Of the three invoices, one was valid and was paid in the following run after the bill of lading matched; the other two were rejected and referred to compliance for review under the company's escalation procedure. The review found the carrier's email account had been compromised.
Questions for discussion
- When a vendor's remittance change arrives close to a payment run, what evidence should be required before the change is accepted, and who should be allowed to waive it?
- Why did the duplicate check pass three invoices that shared a purchase order, and what other fields would you test against?
- How should the company decide whether a suspected misdirected payment needs to be reported beyond internal compliance, and who owns that call?
Case Study 4
Working capital line for a thin-margin bakery chain
Sable Hollow Bakehouse, a family-owned chain of eleven bakeries and two central production kitchens.
The situation
Sable Hollow Bakehouse asked for a $1,500,000 revolving line to fund a new central kitchen and a seasonal inventory build. The family-owned company runs eleven bakeries and two production kitchens, and its last two years of statements showed revenue growth but compressed margins. The loan officer, Rafael, received three years of financial statements, the year-to-date ledger, aged receivables from its wholesale accounts, and a projection prepared by the owner's brother-in-law, who handles bookkeeping. The projection assumed that the new kitchen would reduce cost of goods by a sizable share within the first season. The company's existing debt was modest, but the payables ledger showed slower payments to flour and packaging suppliers than the stated terms.
The challenge
Rafael had to decide whether the request was a sound use of a credit line or a way to bridge an operating shortfall. The kitchen would improve unit cost only if volumes held, and the seasonal build depended on wholesale accounts that were already paying late. The committee wanted a recommendation with clear conditions, not a yes or no, and the owner had asked for an answer before the next supplier price increase took effect.
Analysis
Rafael checked first whether the statements agreed with the ledger beneath them. They did, but only after two reclassifications in the cost of goods line, both posted in the last week of the fiscal period. Once those were reversed, gross margin in the most recent two quarters was about 3 points lower than the statements showed. The payables aging was the more useful signal. Invoices from the two largest flour suppliers had moved from roughly thirty days to past sixty, and the company had taken early payment discounts on none of them. That pattern usually means cash is being stretched, not that suppliers changed terms.
The projection had to be rebuilt before any downside case could mean much. Rafael set three scenarios: full savings, half the savings with flat volumes, and no savings while wholesale accounts kept paying late. In the third case the line peaked near its full commitment for two seasons, and debt service consumed most operating cash flow. Suitability cuts both ways: a line funding inventory against slow receivables is a bet on collections, and the owner's personal guarantee would be exposed. The projection was also prepared by a family member, so someone independent needed to rebuild its formulas.
- Start of reviewLedger reconciliation and independent review of cost of goods.
- Second weekRebuilt projection and stress case presented to the committee.
- End of first monthBorrowing base test run against receivables paid within terms.
- Second month-end closeAging test passed and personal guarantee review completed.
- Following quarterFirst advance drawn after overdue wholesale balances cleared.
Actions taken
- Require the owner to supply bank-verified statements for the last twelve months and an independent reconciliation of cost of goods to purchase records before committee review.
- Rebuild the projection with a base case, a flat volume case, and a collections stress case, and approve only if the line stays covered under the stress case.
- Set a borrowing base tied to eligible receivables that are paid within terms, with an aging test run at each month-end close before any advance is released.
- Make the first advance conditional on a personal guarantee review, a covenant on minimum liquidity, and quarterly delivery of ledger-tied statements to the lender.
Results
The committee approved a smaller facility of $900,000 rather than the full $1,500,000 request, with the balance available only after the kitchen reached a stated volume and the aging test passed for two consecutive month-end closes. The owner accepted the conditions, and the independent reconciliation found the cost of goods reclassifications had overstated margin in one period. The first advance was drawn the following quarter, after the wholesale accounts cleared their overdue balances. Rafael noted the request was reasonable in intent but sized to a projection nobody could yet rely on.
Questions for discussion
- Which of the three scenarios should carry the most weight in a credit decision when the borrower's own projection is the least reliable input?
- What would have to be true about the wholesale accounts for a receivables-based borrowing base to be a safe control here?
- How should a lender treat a family member's role in preparing financial statements when deciding whether to rely on them?
Case Study 5
Ranking payables control findings after a dental group audit
Greaves Dental Partners, a group practice of nine clinics sharing one central payables office.
The situation
Greaves Dental Partners runs nine clinics from a shared central office that handles payables for all of them. The group had grown by acquisition, and each acquired practice brought its own vendor list and approval habits. An internal audit of payables was requested after the chief financial officer, Imani, found that two clinics were paying the same lab invoices from separate vendor records. The audit covered a sample of 1,200 invoices, drawn from the prior twelve months, and reviewed vendor master changes, approval evidence, and payment runs against the general ledger. The board's audit committee wanted a ranked list with owners and dates before its next meeting.
The challenge
The findings were not equally serious. A duplicate lab payment that had cleared the bank was a real loss, but a vendor master record with a stale address was an annoyance. Owners were thin: the central payables manager, Tobias, was responsible for most of the fixes, and two clinic office managers had been approving invoices without documented thresholds. The remediation had to be ranked by materiality, assigned to people who could act on it, and closed only with evidence that a second reviewer could repeat.
Analysis
Tobias sorted the findings by materiality using two measures: the value of transactions that could not be supported by approval evidence, and whether the ledger balance was affected in a way the board would see. The duplicate lab payments, totaling $86,400 across the sample, were ranked first because the cash had left the bank and the expense sat in the wrong clinic's cost center. The unapproved invoices came second, since the sample had found 37 of them above the threshold and the population was much larger. The stale vendor addresses ranked last, although they were the easiest to fix, because they affected no balance and no payment.
Closure tests were written before any fix was marked complete, so no one could settle the question by reviewing their own work. For the duplicate payments, the test required a rerun of the vendor master duplicate check against the full twelve months, with zero hits at the vendor tax identification level and a sign-off from a reviewer outside the clinic. For the approval thresholds, the test sampled new invoices across all nine clinics in each close and required approver evidence on every item above the limit. The ledger test was simpler: the reclass had to appear in the close package and tie to the subledger to the cent.
Actions taken
- Assign each finding to one named owner with a clinic-level deputy, and record the owner's acceptance in the remediation log before any work starts.
- Block vendor master changes that lack a second approver, and run the tax identification duplicate check every week until two clean cycles are recorded.
- Publish written approval thresholds for each clinic office manager, signed by the central controller, and sample invoices above each limit at every close.
- Recover the duplicate lab payments from the vendor, reclassify the expense to the correct cost center, and confirm both entries against the bank statement.
Results
The duplicate payments were recovered in full from the vendor within the following month, and the reclass cleared the cost center variance before the board pack went out. The approval threshold findings took longer, because two clinics had to rebuild their routines and the closure sample failed at the first two closes. Tobias corrected the stale address records in one batch, which took less time than the group expected. The audit committee closed the duplicate payment finding and kept the approval threshold item open until the sample was clean for two consecutive closes.
Questions for discussion
- How would you weigh a control gap that has not yet produced a loss against a smaller error that has already reached the ledger?
- Which closure test in this case would you trust least if the person running it also owned the process, and what would you change?
- When an owner accepts a finding but the evidence keeps failing, at what point should the item move from the owner to the audit committee?
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.