By GreenGrowth CPAs Audit & Assurance Team · Updated October 2026 · Audit & Assurance
Learning how to audit revenue recognition comes down to two moves: treat revenue as a presumed fraud risk, and test whether each of the five ASC 606 steps was applied to real contracts the way the written policy says. Cutoff testing, contract review, confirmations, and analytics all exist to support those two moves.
This guide walks through the procedures auditors actually perform. We wrote it for finance leads who want to know what their auditor will ask for, and for teams that want their own revenue numbers to hold up before fieldwork starts.
QUICK ANSWER
To audit revenue recognition, start from the presumption that revenue carries a fraud risk. Then test the ASC 606 five-step model against signed contracts. Core procedures are contract review, cutoff testing around period end, testing variable consideration and principal versus agent judgments, external confirmations, and substantive analytics. Document every significant judgment so another auditor could follow it.
Auditing Revenue: At a Glance
- Starting point: Auditing standards presume a fraud risk in revenue recognition. Rebutting it requires documented reasons.
- Framework tested: The ASC 606 five-step model, from identifying the contract to recognizing revenue as obligations are satisfied.
- Highest-risk areas: Period-end cutoff, side agreements, variable consideration, and principal versus agent calls.
- Evidence auditors want: Signed contracts, shipping or delivery records, cash receipts, third-party confirmations, and a revenue policy memo.
- Common mistake: Testing invoices without reading the contract terms that drive when revenue is earned.
- How we help: GreenGrowth CPAs is PCAOB registered and has audited revenue across industries since 2016. Book an audit readiness review →
Why Revenue Recognition Is High-Risk
Revenue is usually the largest number on the income statement and the one most tied to bonuses, debt covenants, and valuations. That creates pressure. Auditing standards respond by building in a presumption.
For private company audits, AU-C 240 requires the auditor to evaluate which types of revenue, transactions, or assertions give rise to fraud risk, based on a presumption that such risk exists. For public company audits, PCAOB AS 2401 sets the same expectation. An auditor can rebut the presumption only with documented reasons. In practice, most audits keep it and treat revenue as a significant risk.
Inspection history backs this up. PCAOB staff have reported recurring deficiencies in revenue audits, including auditors who did not weigh all relevant contract terms when validating performance obligations or allocating price.
The ASC 606 Five-Step Model
FASB's Topic 606 replaced industry-specific rules with one model. Each step produces a judgment an auditor can test.
▶ Five Steps and What Auditors Test
| ASC 606 step | Audit focus |
|---|---|
| 1. Identify the contract | Approval, enforceable rights, payment terms, collectibility, side letters |
| 2. Identify performance obligations | Whether promised goods or services are distinct |
| 3. Determine the transaction price | Discounts, rebates, refunds, and the variable consideration constraint |
| 4. Allocate the price | Support for standalone selling prices |
| 5. Recognize revenue | Point in time versus over time, and evidence of transfer of control |
A written revenue recognition policy memo that walks through these steps for each major revenue stream gives the auditor a map. Without one, the audit team has to rebuild your reasoning from invoices, which costs time and invites findings.
Auditor Risk Assessment
Risk assessment decides where the testing goes. Auditors break revenue into streams, then ask which assertions could fail in each: occurrence, completeness, accuracy, cutoff, or presentation.
Controls and Journal Entries
Next comes an understanding of the order-to-cash process and its controls. Manual journal entries posted to revenue get special attention, especially entries near period end or made by senior staff. Strong internal controls that prevent fraud reduce how much detail testing the auditor needs.
Substantive Analytics
Analytics flag where to dig. Common tools include revenue by month and customer, gross margin trends, days sales outstanding, and credit memos issued after year end. Auditors who rely on system reports must also test that the data is complete and accurate, a topic covered in our guide to IPE and sampling in auditing.
Cutoff Testing
Cutoff testing checks that revenue lands in the right period. It targets the most common way revenue gets pulled forward: booking a sale before control transfers.
- Select sales recorded in the days before and after period end.
- Match each to delivery or shipping records and the contract terms, such as FOB point or acceptance clauses.
- Widen the window when typical delivery takes several days.
- Review credit memos and returns after year end for sales that reversed.
For services recognized over time, cutoff testing looks at progress measures instead, such as hours logged or milestones reached by the balance sheet date.
💬 The Conversation Worth Having
Ask your sales team a blunt question before the audit: are there any promises made to customers that are not in the signed contract? Extended return rights, free services, or payment terms agreed by email all change how revenue should be recognized. Auditors look for these. Finding them yourself first is far cheaper than an adjustment found in fieldwork.
Contract Review Procedures
Contract review is where ASC 606 gets tested in practice. Auditors pick a sample of contracts, often weighted toward large, new, modified, or unusual ones, and read them in full.
For each one, they compare the terms to how the company booked the revenue. Did management identify every performance obligation? Does the allocation match standalone selling prices? Were any contract modifications handled correctly? Inquiry of sales and legal staff about side agreements belongs here too.
External Confirmations
Confirmations ask customers to verify balances or contract terms directly with the auditor. For PCAOB audits, AS 2310 took effect for periods ending on or after June 15, 2025. It carries forward the expectation to confirm accounts receivable and stresses that the auditor must control the process. Confirming terms, not just balances, can surface side agreements.
Significant Estimates and Judgments
Variable Consideration
Rebates, volume discounts, performance bonuses, and rights of return make the transaction price an estimate. ASC 606 limits how much variable consideration can be included: only amounts that are not likely to reverse significantly later. Auditors test the method, the inputs, and how past estimates compared to actual results.
Principal Versus Agent
A company that controls the good or service before transfer reports revenue gross. One that arranges for another party to provide it reports only its fee, net. This call can change reported revenue sharply without changing profit, so auditors look closely at who sets price, holds inventory risk, and is primarily responsible for fulfillment.
Want to know how your revenue policy will hold up under audit? Let's review it before fieldwork.
Book a Review →Common Audit Findings and Red Flags
Certain patterns prompt auditors to expand testing. Watch for these in your own books:
- Quarter-end spikes: A surge of sales in the final days of a period, followed by returns or credits.
- Growing receivables: Days sales outstanding rising faster than revenue.
- Bill-and-hold deals: Revenue booked while goods remain in the seller's warehouse.
- Manual top-side entries: Adjustments to revenue outside the normal billing system.
- Missing paperwork: Unsigned contracts, or terms that differ from the invoice.
- Margin outliers: Results out of line with industry peers or prior periods without a clear reason.
Typical findings follow from these: performance obligations missed, variable consideration not constrained, cutoff errors, and gross reporting where net applied. When revenue judgments are complex enough, they can also surface as a critical audit matter in a public company report, as our guide to CAMs and KAMs explains.
SaaS Revenue Recognition Audit
Software and subscription companies bundle access, setup, support, and sometimes licenses into one contract. Auditors test whether each element is a separate performance obligation and how the price is split. Subscription access is generally recognized over the term, so auditors recalculate deferred revenue from contract start and end dates.
Billing system reports are central evidence, so data reliability testing matters. Usage-based fees add variable consideration questions. Our technology industry team works through these issues with software companies every year.
A Practical Revenue Audit Checklist
Use this list to prepare, whether you are the auditor or the company being audited:
- Revenue policy memo covering all five steps for each stream
- Contract listing reconciled to the general ledger
- Signed contracts and amendments for major customers
- Delivery, shipping, or acceptance records around period end
- Variable consideration estimates with support and look-back to actuals
- Principal versus agent analysis for any third-party arrangements
- Deferred revenue rollforward tied to billing data
- Journal entry listing with manual revenue entries flagged
- Credit memos and returns issued after period end
For a wider view of what auditors request, see our audit preparation guide for businesses, or explore our audit and assurance services.
KEY TAKEAWAYS
- ›Revenue carries a presumed fraud risk under AU-C 240 and AS 2401, so it almost always gets significant risk treatment.
- ›Every ASC 606 step creates a judgment that auditors test against signed contracts.
- ›Cutoff, variable consideration, and principal versus agent are where errors cluster.
- ›A clear policy memo and clean contract files shorten fieldwork and reduce adjustments.
Frequently Asked Questions
The basics
Auditors begin by assessing risk, starting from the presumption that revenue recognition carries a fraud risk. They gain an understanding of the order-to-cash process and its controls, then perform substantive procedures. Those usually include reading a sample of contracts against the ASC 606 five steps, cutoff testing around period end, confirming balances or terms with customers, and running analytics on revenue, margins, and receivables. Manual journal entries to revenue get extra scrutiny. The team documents each significant judgment.
ASC 606, Revenue from Contracts with Customers, is the US GAAP standard issued by FASB that governs when and how much revenue a company recognizes. It replaced most industry-specific revenue rules with a single principles-based model. Under it, a company recognizes revenue when it transfers control of promised goods or services to a customer, in the amount it expects to be entitled to. Public and private companies reporting under US GAAP both apply it.
The ASC 606 model
The ASC 606 model has five steps. First, identify the contract with a customer. Second, identify the performance obligations in that contract. Third, determine the transaction price, including any variable consideration. Fourth, allocate the transaction price to each performance obligation based on standalone selling prices. Fifth, recognize revenue when, or as, the company satisfies each performance obligation. Auditors test the judgments made at every step.
Frequent findings include sales recorded in the wrong period, performance obligations that were missed or combined incorrectly, variable consideration that was not properly constrained, and revenue reported gross when the company acted as an agent. Auditors also find side agreements that change contract terms, unsupported manual journal entries, and weak documentation of standalone selling prices. Many of these trace back to a revenue policy that was never written down or never updated.
Specific procedures
Start with the contract. Determine whether subscription access, implementation, support, and any licenses are distinct performance obligations, and test how the price was allocated among them. Because subscription access is generally recognized over the contract term, recalculate deferred revenue using contract start and end dates. Test the reliability of billing system reports used as evidence. Then evaluate usage-based fees, discounts, and renewals for variable consideration and contract modification issues.
Cutoff testing checks that the company records revenue in the correct accounting period. Auditors select sales booked shortly before and after the period end and match them to shipping, delivery, or acceptance records and to contract terms. If control passed after period end, the sale belongs in the next period. Auditors also review credit memos and returns issued after year end, since reversals can signal sales that were pulled forward.
Where to Go From Here
Get Your Revenue Audit-Ready
Facing a first audit, a PCAOB audit, or a messy revenue close? We review your revenue policy, contracts, and cutoff before your auditor does.
KEY NUMBERS
Clean Revenue Files Mean a Faster, Calmer Audit.
Book a free consultation with our PCAOB registered audit team and find revenue issues before fieldwork begins.
Book Your Free Consultation →GreenGrowth CPAs · Audit & Assurance Team
Related: Business Audit Services: What Companies Should Know Before Choosing an Audit Partner
Get more GreenGrowth CPAs insights in Google Search and AI Mode.


