Subsequent cash receipts testing for accounts receivable is an audit procedure in which the auditor tracks payments that arrive after the balance sheet date and matches them back to the specific invoices those payments settle. If a customer owed $50,000 on December 31 and $50,000 lands in the company’s bank account in January against that invoice, the receivable was real and collectible. It is one of the most direct ways to prove that reported receivables are not fictitious or overstated, and it appears in nearly every financial statement audit.
A subsequent cash receipt, for this purpose, is any payment collected after the balance sheet date that relates to a sale recorded before that date. For a December 31 year-end, a January 20 payment on a November invoice qualifies. A January 20 payment on a January 5 invoice does not, because that sale had not been recorded yet at year-end.
What the Procedure Actually Proves
The primary assertion the test addresses is existence. Fictitious revenue is one of the most common forms of financial statement fraud, and inflated receivables are usually the residue it leaves behind. When cash from an outside party flows in and lines up with a year-end invoice, the auditor has concrete proof that the debt was genuine.
Existence is not the only assertion in play. The procedure also speaks to valuation. A receivable recorded at $80,000 that a customer pays in full at $80,000 confirms both that the debt existed and that it was collectible at face value. A customer who pays only $60,000, or who pays nothing, raises questions about whether the recorded amount can actually be recovered.
There is also a cutoff dimension. When the auditor matches a January payment to a specific invoice, the date of that invoice matters. If the invoice is dated December 28 but shipping documents show the goods left the warehouse on January 3, the sale was booked in the wrong period. Cash receipts testing can surface those cutoff errors because the auditor is already deep in the details of individual transactions.
The Subsequent Period Window
The window for examining these payments runs from the day after the balance sheet date through the date the auditor signs the report. PCAOB standards describe this as the “subsequent period,” and its length depends on the practical demands of each engagement rather than a fixed calendar rule.1Public Company Accounting Oversight Board. AS 2801 – Subsequent Events
In practice, most audit teams focus on the first 30 to 60 days after year-end, since that is when the bulk of collections on year-end receivables tends to arrive. The further out a payment falls, the weaker its connection to the December 31 balance becomes, because new transactions muddy the picture.
How the Test Is Run
Picking the Sample
The auditor starts with the year-end accounts receivable trial balance, which lists every customer and what they owed on the reporting date. From that list, the auditor selects a sample to test, typically weighted toward large-dollar balances and accounts flagged as higher-risk during planning. PCAOB sampling standards do not prescribe a specific percentage of the balance that must be covered; sample size turns on the auditor’s judgment about tolerable misstatement, the risk of material error in the account, and the characteristics of the receivable population.2Public Company Accounting Oversight Board. AS 2315 – Audit Sampling
Tracing Each Payment
For each sampled receivable, the auditor looks forward into the cash receipts records for the weeks after year-end, searching for a payment from that customer that matches the invoice number and dollar amount. The auditor then traces that payment to the bank statement to confirm the money actually arrived. A clean test produces a three-way match: the year-end receivable, the entry in the cash receipts records, and the deposit on the bank statement all agree on the customer, the amount, and the timing.
Any mismatch demands investigation. A payment that is close but not exact could reflect a legitimate discount, a partial payment, or a misapplied receipt. The auditor documents exactly what does not line up and digs into why.
The Documents on the Desk
For each sampled item, the review covers the remittance advice (the stub or electronic record showing which invoice the customer intended to pay), the deposit detail on the bank statement, and the company’s internal posting of the receipt. When the customer’s remittance references a specific invoice that matches the year-end balance, the evidence is strong. When it references a different invoice or no invoice at all, the auditor has more work to do to establish which receivable the payment actually settles.
Reading the Results
Full, Timely Payment
A full payment within the window is the cleanest outcome. It confirms both that the receivable existed and that the company could collect it. The auditor documents the match and moves on.
No Payment at All
The absence of a payment does not mean the receivable is fake. Plenty of legitimate invoices take longer than 60 days to collect, especially in industries with extended payment terms. But the missing cash raises the risk level and triggers additional procedures. The auditor usually turns to the original sales documentation: the purchase order, invoice, and proof of delivery. If those confirm a real sale with goods delivered before year-end, the receivable still passes the existence test.
Focus then shifts to collectibility. Under the current expected credit loss model required by ASC 326, companies must estimate lifetime expected losses on receivables using historical loss data, current conditions, and reasonable forecasts rather than waiting for a loss to become probable.3Financial Accounting Standards Board. ASU 2025-05 Financial Instruments – Credit Losses (Topic 326) When a sampled receivable goes unpaid, the auditor evaluates whether the allowance for credit losses adequately covers the risk. A deteriorating payment history or industry-wide financial stress may call for a larger allowance.
Partial Payments
A partial payment confirms the customer exists and acknowledges some of the debt, but it does not validate the full recorded amount. A $30,000 payment against a $50,000 balance gives the auditor solid evidence for $30,000 and leaves the remaining $20,000 to be investigated the same way as any unpaid balance: review source documents, assess collectibility, and test the allowance.
Post-Year-End Credit Memos
Auditors also look at credit memos the company issued in January and February. A credit memo reduces a customer’s balance, usually because of returned goods, pricing disputes, or billing errors. When a credit memo issued after year-end relates to a sale recorded before year-end, it may signal that the receivable was overstated on the balance sheet. A pattern of large post-year-end credit memos is a red flag that the company booked revenue it knew would be reversed.
Why the Detail Catches Lapping
Subsequent cash receipts testing is one of the best tools for catching a lapping scheme. In lapping, someone steals an incoming customer payment and covers the theft by applying the next customer’s payment to the first customer’s account. The third customer’s payment covers the second, and so on. The scheme creates a rolling trail of misapplied payments that only works as long as no one looks too closely at which customer’s money is paying which invoice.
When an auditor traces individual payments to specific invoices, lapping shows up as timing gaps and customer mismatches. Customer A’s invoice shows as paid, but the remittance detail belongs to Customer B. Or a receivable that should have cleared in early January does not clear until late February, because that is how long it took for another customer’s payment to cycle through. Deposits in transit sitting on a bank reconciliation for weeks longer than normal are the same pattern viewed from a different angle.
This is why the detail work matters. An auditor who only checks whether the total receivable balance went down after year-end would miss lapping entirely. The fraud is invisible at the aggregate level. It only surfaces when individual payments are matched to individual invoices and the customer who paid is verified against the customer whose account was credited.
Cash Receipts Testing vs. External Confirmation
External confirmation and subsequent cash receipts testing are related but different. In a confirmation, the auditor contacts the customer directly and asks them to verify what they owed as of the balance sheet date. The customer’s written reply is external evidence: it comes from a third party with no incentive to help the company misstate its books. PCAOB standards treat confirmation as the primary procedure for accounts receivable.4Public Company Accounting Oversight Board. AS 2310 – The Auditors Use of Confirmation
Cash receipts testing relies on the company’s own bank records and internal cash postings. The evidence is still strong because bank statements are generated externally, but the auditor is working with client-maintained records rather than a direct third-party response. The tradeoff is that cash receipts testing proves something confirmation cannot: that the money was actually collected, not just that someone agreed the balance was correct.
The revised AS 2310, effective for audits of fiscal years ending on or after June 15, 2025, explicitly lists subsequent cash receipts as an alternative procedure when confirmations cannot be completed. When a customer does not respond or the response is not reliable, the auditor can examine subsequent cash receipts, shipping documents, or other supporting records to get the evidence another way.5Public Company Accounting Oversight Board. PCAOB Release No. 2023-008 – The Auditors Use of Confirmation
Most audits use both procedures. Confirmations go out to a sample of customers, and cash receipts testing covers balances where the customer did not reply or where the auditor wants additional assurance. On engagements where internal controls over cash are well-tested and reliable, auditors sometimes lean more heavily on cash receipts testing to reduce confirmation volume, though they still have to justify that choice in their working papers.
Where the Procedure Falls Short
Cash receipts testing is powerful but not foolproof. The most obvious limitation is timing. If a legitimate receivable simply has not been paid by the time fieldwork wraps up, the auditor cannot use this procedure for that balance. Industries with long collection cycles, like construction or government contracting, routinely carry large receivables that will not convert to cash within the typical audit window.
The procedure also does not address completeness. It confirms that recorded receivables are real, but it says nothing about receivables the company failed to record. An unrecorded sale that generated a real receivable would not appear on the trial balance and would never be selected for testing.
A payment after year-end does not guarantee the receivable was recorded at the right amount in the right period either. A customer could pay an overbilled invoice without noticing the error, or the company could have booked the sale in December when the goods did not ship until January. The cash receipt confirms the customer paid. It does not confirm the accounting was correct. That is why auditors pair this procedure with cutoff testing and detailed invoice review rather than leaning on it alone.