Audit October 28, 2026 by Lead audit analyst

Why Revenue Recognition Audits Begin With Evidence, Not Invoices

Abstract

We start with a common mistake: treating revenue as a completed sale when the underlying contract, delivery evidence, or allocation judgment remains unresolved. This review explains how a disciplined audit separates recorded amounts from defensible accounting conclusions.

Audit team reviewing revenue contracts

1.Start With The Contract

We often find teams using invoices as the starting and ending point of their review. That approach misses the actual question: what obligation was promised, when was it satisfied, and which amount belongs in the reporting period? We examine contract language, acceptance terms, delivery evidence, cancellation rights, and amendments before assessing the recorded entry. The distinction matters because a transaction can be billed, collected, and still misstated for the period under review.

Revenue is not established merely because an invoice exists or cash has been received.

2.Test The Judgments

Estimates become difficult when assumptions are stored in separate files or changed without a retained rationale. We trace variable consideration, rebates, returns, service milestones, and allocation decisions to their source data, approval records, and subsequent developments. This does not eliminate judgment; it shows whether judgment was applied consistently. Historical adjustments usually reveal where a policy was too broad, where evidence arrived late, or where operational practice had drifted from the written position.

Judgment should be visible, reproducible, and tied to evidence available at the reporting date.

3.Follow The Control Chain

We assess the controls surrounding order entry, contract review, delivery confirmation, billing, credit notes, and period-end cut-off. The practical test is not whether a control exists on paper, but whether the right person performed it, retained evidence, and resolved exceptions before reporting. We also compare system fields with the accounting policy, because a manual override can quietly defeat an otherwise sensible process. The objective is a clear chain from contract evidence to ledger presentation.

A sound policy can still fail when systems and handoffs do not enforce the required decision points.

4.Document The Decision

Our three-step review uses policy, transaction, and control lenses. First, we map the stated revenue position to relevant contract features. Next, we test selected transactions and estimates against source evidence. Finally, we document control gaps, reporting implications, and practical ownership for remediation. We keep the three-to-five-year horizon in view: a correction that depends on one experienced employee is not a durable answer. Where evidence is incomplete, we state the limitation plainly and separate fact from assumption.

A review should leave management with decisions, evidence, and ownership rather than a long list of unexplained exceptions.

Explore audits Read next