Revenue Recognition Control Testing

Revenue audit

Written by Lead audit analyst October 28, 2026

Begin With Contract Evidence

We start with the mistake many reporting teams have already made: treating the invoice as the centre of the revenue conclusion. It is not. An invoice records a billing event, while recognition depends on the contract, the obligation performed, the evidence available at the reporting date, and the amount that can be supported. We compare written terms with operational reality before relying on the ledger. Delivery conditions, acceptance clauses, service periods, amendments, cancellation rights, and continuing obligations can all change the assessment. This work is deliberately practical because broad policy language often fails when applied to specific arrangements. Historical adjustments and prior exceptions help us identify where the organisation has already struggled. The review should show which facts support the entry, which matters remain judgmental, and who owns the next decision.

Read The Contract First

We examine the contract before testing the ledger because the promised obligation determines which evidence matters. Delivery terms, customer acceptance, renewal language, cancellation provisions, service periods, and amendments may change the reporting conclusion. We compare those terms with operational records and document the point at which performance occurred. When a policy uses broad wording, we identify the specific contract feature that requires a more careful assessment. This prevents a general rule from replacing evidence about the arrangement actually under review.

Separate Billing From Performance

We distinguish invoices, receipts, delivery records, acceptance notices, and completion evidence because each document represents a different event. An invoice may be issued before delivery, while consideration may be received before the organisation has completed its work. We trace selected transactions from source records to ledger posting, then assess which facts were available at the reporting date. Where evidence is missing, we record the limitation plainly instead of treating administrative activity as proof of performance. That distinction helps management decide whether the issue requires correction, further evidence, or policy clarification.

Trace Contract Changes

Contract amendments deserve direct attention because revised pricing, added services, extensions, concessions, or changed acceptance terms can alter the original conclusion. We establish when the change became effective, which obligations it affected, and whether billing and accounting records reflect the revised arrangement. Approval records, customer correspondence, operational schedules, billing instructions, and ledger entries should tell the same story. If the contract file changed but the reporting process did not, the gap becomes a control finding rather than an isolated documentation issue.

Test Timing, Estimates, And Control Operation

Once the obligation is clear, we test whether the recorded amount belongs in the selected period and whether estimates reflect information available at close. Cut-off work is often reduced to checking invoice dates near year end, but that shortcut misses delivery conditions, customer approvals, service allocations, credit notes, and manual entries. We examine activity on both sides of the reporting boundary, focusing on transactions whose timing, value, or structure differs from normal processing. The objective is not to collect exceptions for their own sake. It is to explain the reporting boundary and identify weaknesses likely to recur.

Test The Reporting Boundary

We trace transactions before and after period end through order records, dispatch or completion documents, customer acceptance, service logs, invoices, credit notes, and ledger entries. Each source answers a different question, so one matching date cannot settle the conclusion. A service may have started without being complete, or goods may have been delivered while acceptance remained outstanding. We state which evidence supports the period allocation, what uncertainty remains, and whether the matter points to a broader process weakness.

Make Estimates Traceable

We examine returns, rebates, concessions, milestones, and other variable amounts by tracing assumptions to source data, calculations, approvals, and later developments. Later outcomes can inform the review, but they do not automatically prove that an earlier estimate was unreasonable. We ask whether the judgment reflected information available at the reporting date and whether similar arrangements received consistent treatment. Unsupported precision is not stronger analysis. A clear record identifies the assumption, its owner, its review point, and the evidence that could change the conclusion.

Connect Controls To Ownership

We test whether reporting controls operated, not merely whether they appear in a policy document. The assigned person should perform the review, retain evidence, resolve exceptions, and escalate matters according to the defined process. Manual overrides receive particular attention because they can bypass a sensible workflow without creating an obvious system warning. We compare contract fields, operational records, billing rules, approval paths, and ledger outputs to find where information is lost or re-entered. Over a three-to-five-year horizon, a process dependent on one experienced employee remains fragile, so remediation must clarify ownership and preserve evidence.

Explore audits Read next

How Revenue Recognition Audits Turn Contract Evidence Into Reliable Reporting Decisions