Published by Shah Teelani & Associates | PCAOB-Registered Audit Firm | Reg. No. 7161
Revenue recognition PCAOB inspectors examine ranks as the single most consistently deficient area across all inspection cycles and all firm categories. Year after year, inspection reports from Big Four firms, mid-tier firms, and smaller registered firms all identify revenue testing as a primary source of Part I.A findings. Revenue involves complex judgments, significant management estimates, fraud risk presumptions, and multiple-element arrangements. Each of these creates conditions where misstatement risk runs high.
Revenue recognition consistently comes up as the top area of regulatory focus. In over 50 enforcement cases, executives faced personal liability for issues tied to revenue recognition.
Furthermore, internal controls testing, risk assessment, and revenue recognition have been among the top deficiency areas for years running in IFIAR’s global inspection survey. This confirms that the revenue recognition challenge extends well beyond any single jurisdiction.
At Shah Teelani & Associates, we treat revenue recognition as a high-risk area on every engagement. This blog explains why PCAOB inspectors focus intensely on revenue, what AS 2401 and ASC 606 require auditors to test, and where deficiencies most commonly arise in 2026.
Revenue Recognition PCAOB Risk: Why It Exists on Every Engagement
Revenue recognition presents audit risk on multiple dimensions simultaneously. Management exercises significant judgment in applying the five-step ASC 606 model. Estimates for variable consideration, standalone selling prices, and contract modifications all involve subjective assumptions. Moreover, PCAOB standards presume fraud risk in revenue recognition on every single engagement.
AS 2401’s fraud risk presumption requires auditors to presume the risk of fraud in revenue recognition and evaluate whether journal entries are being used to manipulate financial results.
This presumption never disappears — even where revenue processes appear well-controlled and prior-year audits found no issues. Auditors must design procedures that address fraud risk in revenue specifically. Consequently, the revenue testing approach must combine fraud-risk procedures under AS 2401 with substantive testing under AS 1105 and assessment of management’s ASC 606 accounting judgments.
The ASC 606 Five-Step Model: Where Audit Risk Concentrates
Understanding where revenue recognition PCAOB audit risk concentrates requires understanding the five-step ASC 606 model. Each step carries distinct risks — and each demands specific audit procedures.
Step 1 — Identify the Contract
Revenue recognition starts with confirming whether an enforceable contract exists. Verbal contracts, implied arrangements, and contracts modified near period-end all require specific attention. Auditors must evaluate whether each criterion for contract existence is met — including whether collectability is probable.
Step 2 — Identify Performance Obligations
Identifying distinct performance obligations within a multi-element contract requires management to evaluate whether each promised good or service is capable of standing alone. Management may bundle obligations that should be separated — or disaggregate obligations that should stay combined. Both errors directly affect recognition timing. Auditors must evaluate management’s performance obligation identification independently — not simply confirm that a process exists.
Step 3 — Determine the Transaction Price
Transaction price determination concentrates the most significant management judgment. Variable consideration enters the transaction price only to the extent it is probable that a significant reversal in cumulative revenue will not occur when uncertainty is resolved. This prevents companies from recognizing revenue that may later require reversal.
Significant financing components add another layer of complexity. Management must assess whether payment timing differs from transfer timing and adjust the transaction price for time value of money. Each assumption is susceptible to management bias. Therefore, auditors must independently evaluate the reasonableness of each input — not merely confirm the methodology.
Step 4 — Allocate the Transaction Price
Allocating the transaction price to multiple performance obligations requires management to determine standalone selling prices for each. Standalone selling price allocation often proves complex when companies do not regularly sell goods or services separately. Estimating these prices requires considering market conditions, competitor pricing, cost structures, and customer-specific factors.
Management’s allocation directly determines how much revenue is recognized when each obligation is satisfied. Allocation errors shift revenue between periods — creating overstatement in one period and understatement in another. Auditors must evaluate whether management’s standalone selling price estimates have independent support.
Step 5 — Recognize Revenue as Obligations Are Satisfied
Revenue is recognized either at a point in time or over time. The criterion is when control of the good or service transfers to the customer. Management’s determination of the recognition pattern directly affects both the amount and timing of revenue.
Period-end cutoff concentrates the highest risk at this step. Auditors must test whether revenue in the final days of a reporting period relates to obligations actually satisfied before period close — not obligations management recorded prematurely to meet targets.
Revenue Recognition PCAOB Fraud Risk Procedures Under AS 2401
The fraud risk presumption requires more than standard substantive testing. AS 2401 requires auditors to design procedures that respond specifically to the risk of intentional misstatement through revenue manipulation.
Analytical procedures for unusual revenue patterns must be designed to detect anomalies — not confirm expected trends. Comparing revenue by quarter, product line, region, or customer against prior periods and independently developed expectations identifies unusual relationships. Furthermore, comparing revenue to non-financial metrics — units shipped, service volumes, headcount — exposes disconnects between reported revenue and actual business activity.
Revenue-related journal entry testing addresses the management override risk. Management can manipulate revenue through unauthorized entries — recording fictitious amounts, accelerating recognition through manual adjustments, or reversing appropriate reserves. Entries recorded at period-end, entries to unusual account combinations, and entries lacking proper authorization all require examination.
Evaluating the fraud risk presumption requires auditors to document why they presume fraud risk in revenue and how their procedures address it. Where management proposes to reduce revenue testing scope, auditors must evaluate whether that proposal is supportable. The presumption applies on every engagement and requires specific documentation of how procedures address it.
Substantive Revenue Testing: Key Assertions
Substantive testing of revenue must address the specific assertions that carry the highest risk for each revenue stream and contract type.
Occurrence and cutoff ask whether recorded revenue relates to transactions that actually occurred in the reporting period. Testing occurrence requires examining evidence that performance obligations were satisfied — shipping documents, customer acceptance records, and service completion evidence. Cutoff testing requires examining transactions near period-end to confirm the recognition date is appropriate.
Completeness addresses whether all earned revenue appears in the financial statements. This assertion often receives less attention than occurrence. However, underreported revenue can reflect control failures, system limitations, or fraud. Procedures must address completeness as specifically as they address occurrence.
Measurement addresses whether revenue reflects the correct transaction price. Management’s variable consideration estimates, standalone selling price allocations, and financing component adjustments all affect measurement. Where estimates drive measurement, auditors must independently evaluate those estimates rather than simply confirming that a process was followed.
Presentation and disclosure addresses whether revenue is appropriately disaggregated and whether ASC 606 disclosures — including significant judgments, remaining performance obligations, and contract balances — are complete and accurate. Disclosure deficiencies in revenue have been a specific PCAOB inspection focus for several consecutive cycles.
High-Risk Revenue Areas That Attract Inspection Scrutiny
Certain revenue arrangements consistently attract heightened PCAOB attention because of the complexity of management judgment involved.
Software and SaaS arrangements. Separating licenses, implementation services, support, and updates requires identifying which elements are distinct performance obligations. Whether a software license transfers at a point in time or over time depends on whether the customer’s right is to access or use the intellectual property. Both distinctions directly affect revenue timing — and both require specific audit evidence.
Long-term contracts. Percentage-of-completion recognition requires reliable estimates of total contract costs and progress toward completion. Where estimates change, the cumulative catch-up must appear in the current period. Auditors must evaluate both current-period estimates and whether prior-period estimates were reasonable.
Arrangements with variable consideration. Rebates, volume discounts, refund obligations, and performance bonuses all introduce estimation risk. Auditors must evaluate the methodology management used, the historical data supporting the estimate, and whether management applied the constraint appropriately.
Bill-and-hold transactions. Revenue on bill-and-hold arrangements requires satisfying four specific criteria simultaneously. Auditors must examine the substantive terms of each arrangement — not merely review the accounting documentation management prepared.
Principal versus agent analysis. Whether a company acts as principal — reporting gross revenue — or agent — reporting net revenue — depends on whether it controls the good or service before transfer. Management has direct incentives to report gross revenue because it inflates reported totals. Auditors must evaluate whether the principal-agent determination reflects the contractual and operational facts — not management’s preferred presentation.
Revenue Recognition PCAOB Inspection Deficiencies: What Keeps Appearing
Revenue recognition deficiencies in PCAOB inspections include auditors failing to test whether revenues were accurately reported or properly classified, particularly under ASC 606.
Beyond classification failures, recurring patterns include performing analytics without independent expectations — accepting management’s variance explanations rather than developing auditor benchmarks first. Auditors also test occurrence while ignoring completeness — addressing one direction of misstatement risk while leaving the other unexamined. Another pattern involves checking management’s ASC 606 process without evaluating whether it produces a reasonable result — methodology compliance without output evaluation. Auditors further miss the journal entries through which revenue was actually recorded — overlooking the management override risk embedded in the recognition entries. Finally, inadequate period-end cutoff sampling consistently appears — where both error and fraud risk concentrate, testing is often insufficient.
What Issuers and Finance Teams Should Know
Revenue recognition PCAOB audit demands directly affect finance team preparation. Well-organized contract documentation, consistently applied accounting policies, and clear support for management’s significant judgments all reduce mid-engagement requests and late-stage findings.
Specifically, finance teams should maintain complete contract files — including side agreements, amendments, and informal modifications — accessible to auditors before fieldwork begins. Documenting the performance obligations identified in each significant contract, the standalone selling price estimates used, and the basis for variable consideration estimates also strengthens the audit process. Additionally, applying and documenting revenue cutoff procedures consistently throughout the year — rather than reconstructing them at year-end — directly supports reliable auditor cutoff conclusions.
The Bottom Line
Revenue recognition PCAOB inspection findings are persistent, widespread, and consequential. Every public company audit requires revenue testing procedures that address the fraud risk presumption under AS 2401 and the substantive risks in the five-step ASC 606 model. Complex revenue arrangements — multiple performance obligations, variable consideration, principal-agent analysis, and point-in-time versus over-time recognition — all create judgment risk that auditors must challenge independently.
In 2026, revenue continues to rank as the top inspection deficiency area globally. Every registered firm must therefore treat revenue recognition as a primary engagement risk — not a standardized testing area handled with generic templates.
Shah Teelani & Associates (PCAOB Reg. No. 7161) applies rigorous, fraud-risk-responsive revenue testing procedures on every public company engagement. We work with US-listed and OTC public companies that understand what a defensible revenue recognition audit conclusion requires.
If your organization requires a PCAOB-registered auditor with deep revenue recognition expertise, we welcome the conversation.
Shah Teelani & Associates PCAOB-Registered Audit Firm | Reg. No. 7161 Ahmedabad | Dubai | United States
