Why Revenue Recognition Gets Scrutinized

Revenue recognition directly impacts an organization’s financial statements, which makes it a common area of audit focus. Errors related to timing, documentation, or performance obligations can lead to audit findings, delays, or additional follow-up during the audit process.

Common Finding #1: Cutoff Errors

Auditors test for cutoff by designing procedures to ensure transactions are recorded in the correct financial period. Common cutoff findings include sales from the last period of the fiscal year not being recorded as revenue until the invoice is sent, even though the underlying transaction has already occurred. For example, if an organization makes a sale and provides the good or service in December but does not send the invoice until January, the revenue should still be recognized in December when the underlying good or service was provided.

Another common cutoff error relates to service contracts where revenue is recognized immediately instead of over time. For service contracts, revenue should be recognized when the performance obligation is satisfied.

Common Finding #2: Insufficient Documentation

Auditors use supporting documentation such as invoices, contracts, purchase orders, and shipping documentation to identify revenue and determine the period in which it should be recognized. Without this documentation, auditors may be unable to verify that revenue is valid, which could lead to material findings in the financial statement audit. It is crucial for organizations to maintain documentation for all revenue transactions to help prevent material audit findings and support proper internal recordkeeping.

Common Finding #3: Improper Identification of Performance Obligations

This occurs when multiple deliverables are treated as a single obligation when they should be separated. An example would be an organization bundling multiple goods or services, such as a software license with implementation services. In this example, there are two distinct performance obligations, with revenue from the software license recognized at the delivery date and revenue from implementation services recognized as the services are performed. It is crucial to perform an analysis for each contract to identify all performance obligations and properly record revenue.

Best Practices to Help Avoid Revenue Recognition Audit Findings

Need help preparing for your next audit?

Revenue recognition can be complex, especially when contracts, service periods, or multiple deliverables are involved. HBE’s assurance professionals can help your organization understand audit expectations and prepare with confidence.