Definition
AU-C 240 requires the auditor to presume that there are risks of fraud in revenue recognition. The auditor evaluates which types of revenue, transactions or assertions give rise to those risks. If the auditor concludes the presumption does not apply to a given stream, the reasons go into the working papers.
Why it matters in an audit or review
Revenue is a common target because management often has both pressure and room to act, through timing, side agreements, bill-and-hold, channel stuffing or unsupported estimates of variable consideration. The presumption forces the auditor to plan specific procedures for revenue instead of defaulting to a standard program. Rebuttal can be reasonable for simple revenue, such as rental income from a single lessee under a lease, and is hard to defend for complex or judgmental streams.
Example
Illustrative: a company has two revenue streams: a fixed monthly management fee from one related entity, and project revenue recognized over time using cost-to-cost. The auditor rebuts the presumption for the management fee, documenting that it is fixed by contract and agrees to bank receipts. For project revenue, the auditor treats estimated total cost as a significant risk and tests the estimates against vendor commitments and subsequent cost.
Common mistakes
Rebutting the presumption for a whole revenue line because revenue is a small share of the business, without addressing the types of transactions involved.
Sources
- AICPA, AU-C Section 240, Consideration of Fraud in a Financial Statement Audit (presumed fraud risk in revenue recognition; documentation of reasons for rebuttal)
- FASB ASC 606 (revenue from contracts with customers)
Definitions paraphrase AICPA and FASB guidance; read the standard itself before relying on a requirement. Example figures are illustrative. This page is guidance, not professional advice. Report an error