Why revenue is the hardest part of the audit
Revenue is the most tested number in your financial statements. Auditing standards presume that revenue recognition carries a risk of fraud. That means auditors will test it hard: cut-off, contracts, and policy. It is also the area where growing companies most often get it wrong. Usually the problem is not bad intent. It is using a simple “we invoiced it, so it is revenue” rule instead of the actual standard.
The standard: ASC 606’s five-step model
Under FASB ASC 606, revenue is recognized as you transfer promised goods or services to a customer. The amount is what you expect to be entitled to receive. The standard lays out five steps:
- Identify the contract with the customer.
- Identify the performance obligations — the distinct promises in that contract.
- Determine the transaction price — including variable consideration like discounts, rebates, or refunds.
- Allocate the transaction price to each performance obligation.
- Recognize revenue as (or when) each performance obligation is satisfied.
The key idea: revenue follows delivery of the promise, not the invoice and not the cash.
Where growing companies trip up
The same handful of errors show up again and again:
- Recognizing on invoice or payment, rather than as obligations are satisfied. This is a real problem for subscriptions, setup services, and anything delivered over time.
- Bundled deals treated as one line. A contract with software, onboarding, and support may include several performance obligations. They often need to be separated and allocated.
- Ignoring variable consideration. Discounts, rebates, service credits, and refund rights change the transaction price. They often need to be estimated up front.
- Weak cut-off. This is the most common audit adjustment: revenue booked in December for something delivered in January, or the reverse. Clean cut-off is where audits are won or lost.
- Upfront fees and nonrefundable payments recognized right away when they should be spread over the service period.
Getting ready before fieldwork
You do not need to be a technical accountant to be ready. You need three things in order. First, write a revenue recognition policy that reflects the five-step model and your contracts. Second, apply that policy the same way across deals. Third, keep cut-off clean with evidence that ties revenue to delivery. If your deferred-revenue schedule ties to contracts and your cut-off holds up, the revenue part of your audit gets much shorter.
The continuous view
Revenue errors build quietly across a year and then surface all at once in the audit. Monitor revenue cut-off, credit notes, and unusual discounts as they happen. Do not wait to rebuild them at year-end. That keeps the number defensible all year and removes the biggest source of audit adjustments.
Ressura’s Order-to-Cash module monitors revenue cut-off, credit notes, and pricing exceptions continuously, so your most important number is audit-ready year-round.