Revenue Testing From Contract to Cash: A Vouching and Tracing Worked Example

Improper revenue recognition is a presumed fraud risk in the audit unless the auditor rebuts it, which means the work has to be done well and shown to be done well. The most reliable way to test revenue is from both directions. Vouching goes from the ledger back to the evidence and tests occurrence. Tracing goes from the evidence forward to the ledger and tests completeness. This post runs one test through five steps with a sample. For the recognition rules see ASC 606 revenue recognition, for the program overview see revenue recognition audit procedures and for the presumed risk see fraud risk assessment.

Step 1: Define the assertions and the direction

Step 2: Understand the revenue streams and the contract terms

For each stream, document the contract type, performance obligations, when control transfers, variable consideration, returns and payment terms. A client with product sales, installation services and annual maintenance has three streams with three recognition patterns. Read a sample of contracts from each. A recognition pattern that does not match the contract terms is a finding before testing begins.

Step 3: Vouch a sample of recorded revenue (occurrence and accuracy)

Select 30 invoices from the full-year invoice register, by monetary unit sampling plus the largest items. See monetary unit sampling. For each:

Combine with confirmation of selected customer balances. See confirmation exceptions.

Step 4: Trace from the shipping log to the ledger (completeness)

Select 25 shipments or completed jobs from the shipping log or work-order system. For each, find the invoice and the ledger entry in the right period. Shipments with no invoice are unbilled revenue. Shipments billed in a later period are cutoff errors. A separate selection of 15 customer cash receipts after year end, traced back to the invoice and the period, tests receipts that relate to unrecorded sales.

Another completeness test: compare the numerical sequence of invoices or shipping documents for gaps. Gaps need explanation.

Step 5: Test the last and first days (cutoff)

Select the last 10 shipments before year end and the first 10 after. Compare the shipping date to the invoice date and the control transfer under the terms. Test credit memos issued after year end for items that belonged to the year. See cutoff testing.

Worked example results

A client with revenue of $41.2 million and performance materiality of $65,000. Results:

Total identified misstatements: overstatement $115,600 (3,600 + 74,000 + 38,000) and understatement $21,000. Netting gives a $94,600 overstatement. These are the misstatements found in the items tested. Those in the monetary unit sample that sit below the sampling interval still need projecting to the population, as in the monetary unit sampling example. Even before projection the amount exceeds $65,000, and the overstatements all run in management's favor, so the finding is that revenue recognition controls at cutoff are weak. The auditor extends the cutoff test to the last 30 days of December and the first 15 of January, asks management to review the installation revenue population for early recognition, and tests the price master for changes. The proposed entries go on the adjusting entry log.

Fraud indicators to watch for

• Large entries near year end, especially manual journal entries to revenue.
• Customers with no history, or with a relationship to management.
• Credit memos and returns immediately after year end.
• Side agreements that grant return rights or extended terms.
• Bill-and-hold arrangements.
• Shipments to freight forwarders that do not leave the premises.
• Revenue that rises while cash collected from the same customers does not.
• Unusual changes in gross margin.

Review the revenue journal entries as part of journal entry testing.

Link to analytics

Before the detail work, run analytics: revenue by month and product against expectation, price times volume, gross margin by product, and revenue versus cash received. See analytical procedures worked example. The pattern of the detail test follows what the analytics show.

Documentation

Streams and contract terms, selection method and population tie-outs, vouching and tracing results with evidence references, cutoff tests, misstatements and projection, the evaluation of fraud indicators and the conclusion on occurrence, completeness, accuracy and cutoff.

CORAA prepares ready-to-review audit files for US CPA firms; the firm keeps the client, the review and the signature. See /us.

Sources

• AICPA, AU-C Section 240, Consideration of Fraud in a Financial Statement Audit (presumed risk in revenue recognition); AU-C Section 330, Performing Audit Procedures in Response to Assessed Risks and Evaluating the Audit Evidence Obtained
• FASB, Accounting Standards Codification Topic 606, Revenue from Contracts with Customers
• U.S. Government Accountability Office, Financial Audit Manual, Volume 1 (GAO-26-108577), June 2026, sections 265 and 480 (fraud risk responses for revenue recognition, substantive detail tests): gao.gov

AU-C references are to AICPA Professional Standards, paraphrased here; read the standard itself before relying on a requirement. This page is guidance, not professional advice. Report an error