How auditors test revenue occurrence, cutoff, receivables, and cash receipts for material misstatement.
Revenue is a high-risk audit area because it affects performance measures, debt covenants, compensation targets, and investor expectations. Auditors usually presume a fraud risk in revenue recognition unless facts clearly support a different conclusion. Substantive testing must therefore connect recorded revenue, receivables, and cash receipts to the underlying assertions.
The AUD exam often turns on direction of testing. Vouching recorded sales to source documents tests occurrence. Tracing shipping documents to the sales journal tests completeness. Cutoff testing focuses on whether revenue belongs in the correct period.
flowchart LR
A["Customer order"] --> B["Approval and shipment"]
B --> C["Invoice"]
C --> D["Sales journal and receivable"]
D --> E["Cash receipt"]
E --> F["Bank deposit and AR update"]
Revenue testing begins with the assertion at risk. The same document can support different conclusions depending on the direction of the test.
| Assertion | Risk | Common substantive response |
|---|---|---|
| Occurrence | Recorded sales did not happen or were premature | Vouch sales journal entries to contracts, shipping documents, delivery evidence, and invoices |
| Completeness | Valid shipments or services were not recorded | Trace shipping documents, service records, or cash receipts to sales records |
| Cutoff | Sales near period-end were recorded in the wrong period | Compare shipping terms, delivery dates, invoices, and recording dates before and after year-end |
| Accuracy | Prices, quantities, discounts, or taxes are wrong | Recalculate invoices and agree prices to contracts or approved price lists |
| Valuation | Receivables are not collectible | Review aging, subsequent cash receipts, credit memos, disputes, and allowance assumptions |
| Presentation | Revenue streams or contract terms are misclassified or inadequately disclosed | Inspect contracts and evaluate revenue recognition disclosures |
Recorded revenue is often tested for overstatement. Receivables are often tested for existence and valuation. Cash receipts testing helps corroborate collectability and detect misappropriation schemes.
Occurrence testing starts with recorded sales and works backward to evidence that the sale happened. Strong evidence includes customer contracts, purchase orders, shipping documents, delivery confirmations, service completion records, and subsequent cash receipts.
Cutoff testing concentrates on transactions close to period-end. The auditor compares shipment or delivery evidence to the date revenue was recorded. For goods, shipping terms matter because title and control may transfer at different points. For services, the auditor considers whether performance obligations were satisfied.
High-risk cutoff patterns include:
The stronger exam answer does not merely say “test revenue.” It identifies the assertion and procedure: for example, inspect shipping documents immediately before and after year-end to determine whether sales were recorded in the proper period.
Accounts receivable confirmations provide external evidence about recorded balances. Positive confirmations are stronger because the customer must respond whether they agree or disagree. Negative confirmations are less persuasive and are generally appropriate only when risk is low, balances are small and numerous, and recipients are expected to respond to exceptions.
If a positive confirmation is not returned, the auditor performs alternative procedures, such as:
Confirmation supports existence and rights more strongly than valuation. Even if a customer confirms a balance, the auditor still evaluates collectability through aging, payment history, subsequent receipts, and allowance methodology.
Cash receipts testing connects customer payments to bank deposits and receivable records. A key fraud risk is lapping, where an employee steals one customer’s payment and covers it by applying a later customer’s payment to the first account.
Substantive procedures over cash receipts include:
| Procedure | Audit purpose |
|---|---|
| Trace remittance advices to cash receipts journal and bank deposit | Test completeness and proper application of receipts |
| Compare deposit dates to recording dates | Identify delays or possible lapping |
| Inspect bank statements and lockbox reports | Corroborate deposits with external evidence |
| Review credit memos and write-offs | Identify attempts to conceal theft or invalid receivables |
| Reconcile subsidiary receivable ledger to the general ledger | Check consistency between detail records and control account |
Lockbox arrangements can reduce employee access to checks, but they do not eliminate the need to reconcile receipts and investigate exceptions.
Revenue analytics are useful when they are tied to plausible relationships and followed by targeted testing.
| Analytic | Possible red flag |
|---|---|
| Revenue growth compared with industry or production data | Recorded sales may not match actual activity |
| Gross margin by month or product | Improper revenue, cost cutoff, or pricing errors |
| Days sales outstanding | Collectability issues or premature revenue |
| Credit memos after year-end | Channel stuffing, returns, or cutoff problems |
| Manual journal entries to revenue | Management override or unsupported adjustments |
Management explanations for unusual revenue trends require corroboration. A claim that sales increased because of a new customer should be supported by contracts, shipping evidence, invoices, and cash receipts.
Do not confuse vouching and tracing. Vouching recorded sales to support tests occurrence; tracing source documents to the books tests completeness.
Do not assume cash receipt after year-end proves revenue cutoff. It may support collectability, but the sale still must meet recognition criteria in the period recorded.
Do not treat confirmations as proof of valuation. Collectability requires additional procedures.
Do not accept management’s explanation for a revenue spike without documentary support.