Revenue audit
October 28, 2026
How Revenue Recognition Audits Separate Evidence From Assumption
Revenue recognition is an evidence question before it becomes a ledger question.
Begin With The Reporting Obligation
We start with a mistake many reporting teams have made: treating an invoice as proof that revenue belongs in the reporting period. An invoice confirms a billing event, but it does not establish that the promised obligation was satisfied, that the customer accepted the work, or that the recorded amount was measured appropriately. We therefore begin with the contract and compare its wording with what operations actually delivered. Delivery conditions, acceptance clauses, cancellation rights, service periods, amendments, and continuing obligations can all change the conclusion. This comparison is necessary because commercial language often moves faster than written policy. A transaction may appear complete to one team while another material obligation remains outstanding. We document the evidence available at the reporting date and separate confirmed facts from unresolved judgment. Historical exceptions then help us identify where broad policy language has produced inconsistent decisions. The result is not a theoretical summary detached from operations. It is a clear path from contract terms to accounting treatment, with ownership assigned wherever the evidence remains incomplete.
Test Cut-Off Against Transaction Evidence
The common myth is that cut-off testing means selecting invoices issued near year end and checking their dates. That is only a starting point. We trace transactions through order records, dispatch or completion documents, customer acceptance, service logs, billing, ledger posting, credit notes, and later amendments. Each document answers a different question, so one matching date cannot settle the review. A product may have been dispatched but remain subject to acceptance. A service may have started but require allocation across several reporting periods. A credit note issued after close may indicate that the original amount depended on an assumption that had already weakened. We give additional attention to unusual timing, manual entries, large contract changes, and transactions immediately before or after the reporting boundary. None of these features proves an error, but each requires a clear explanation. We compare current findings with earlier adjustments because repeated small exceptions can reveal a process weakness more clearly than one isolated correction. The conclusion should state whether the amount belongs in the period, which evidence supports that view, and what uncertainty remains.
Make Estimates Traceable And Reviewable
Estimates require a separate discipline because uncertainty cannot simply be removed from the file. We examine returns, rebates, concessions, milestones, and other variable amounts by tracing assumptions to source data, calculations, approval records, and later developments. Later outcomes provide useful evidence, but they do not automatically prove that an earlier estimate was unreasonable. The relevant question is whether the original judgment reflected information available at the reporting date and whether comparable arrangements received comparable treatment. We record who approved each material assumption, when it should be revisited, and what evidence would change the conclusion. Unsupported precision is not stronger analysis; it is uncertainty disguised as a precise number. We also review whether operational teams understand the accounting consequence of amendments, service credits, and acceptance conditions. Where the evidence is incomplete, we state the limitation rather than filling the gap with an unsupported assumption. This creates a review trail that allows management to challenge the judgment without losing sight of the facts that supported it at the time.
Connect Controls With Durable Ownership
A written policy can be sensible and still fail in operation. We test the handoffs connecting contract review, delivery evidence, billing, amendments, credit notes, and period-end close. The practical question is whether the assigned person performed the control, retained evidence, resolved exceptions, and understood when escalation was required. Manual overrides receive attention because they can bypass a sound workflow without producing an obvious system warning. We compare system fields with policy requirements and identify where information is re-entered, delayed, or left to informal messages. If a compensating review exists, we document its owner, frequency, evidence, and limits. Over a three-to-five-year horizon, a process dependent on one experienced employee remains fragile, even when current files appear orderly. We therefore classify findings as confirmed timing errors, missing evidence, estimation uncertainty, policy gaps, or control failures. Each category needs a different response. The review should leave management with a documented decision, a practical action, and an owner who can show when the change became operational.