Revenue Audit: Follow the Transaction, Not Just the Number

Revenue assurance starts with the transaction, not with a total that agrees to the ledger. Follow what was promised, what was performed, what amount is supported and when it belongs in the accounts.

Understand the promise

Read the relevant contract and supporting terms. Identify the customer, goods or services, payment arrangements and any amendments, acceptance conditions, returns or incentives that affect the accounting question.

For contracts within its scope, IFRS 15 connects recognition to satisfying performance obligations through the transfer of control. The model also addresses transaction price and allocation. A purchase order or invoice alone does not establish that the performance obligation has been satisfied.

The transaction flow will differ across retail goods, subscriptions and longer-term services. Do not copy the same document checklist into every revenue model.

Connect performance to evidence

In an illustrative goods sale, inspect the relevant dispatch, receipt or acceptance information and contractual terms. Determine what that evidence demonstrates about the transfer of control. Dispatch is not a universal recognition trigger.

For an obligation satisfied over time, consider the relevant basis and evidence of progress. This overview does not set out every eligibility condition for over-time recognition; those requirements need separate assessment under the applicable framework.

A payment may be an advance, and a receivable may arise before cash collection. Cash evidence answers a different question from whether revenue recognition is appropriate.

Test the amount and adjustments

Connect quantities and agreed prices to the recorded amount. Investigate relevant discounts, returns, rebates, credits and contract changes rather than checking only the original invoice total.

An illustrative period-end invoice may agree to its order but still omit an approved price concession. The accounting conclusion requires understanding the concession and its timing, not simply finding a matching number.

Document the basis for judgment where variable consideration or other complex terms matter. This learning map is not a complete IFRS 15 accounting checklist.

Trace in both directions

Starting from recorded revenue and examining underlying evidence helps investigate whether recorded transactions occurred. Starting from relevant source records and tracing forward helps investigate whether transactions that should be recorded were omitted.

The population and selection need to match the assertion and risk. Testing invoices already in the ledger cannot, by itself, demonstrate that all appropriate revenue is there.

ASA 315's transaction assertions provide a useful structure in Australian financial-report audits. The relevant assertions depend on the risk; they should not become labels added after testing has already been chosen.

Challenge the period and the data

Examine relevant transactions and adjustments around the reporting boundary. Compare posting dates with the underlying recognition evidence, investigate unusual changes and assess whether items belong in the correct period.

Check the completeness and reliability of system extracts, interfaces and reports used in the work. A reconciliation can show two records agree without proving the underlying transaction or accounting is correct.

ASA 500 addresses evidence quality, entity-produced information and inconsistent evidence. Corroborate explanations where needed, and retain unresolved contradictions for evaluation.

Conclude beyond the number

Explain which assertions and transaction types were addressed, what the evidence supports and what remains uncertain. Consider classification, presentation and disclosure where relevant; evaluating related receivable balances is a connected but separate part of the work.

An issue may concern occurrence, an omitted transaction, an incorrect amount, timing or several of these. Link the conclusion to the supported condition and business consequence.

An invoice records a claim. Evidence and the accounting requirements determine what revenue it supports.