Audit Procedures for IFRS 15 Revenue Recognition

Audit procedures for IFRS 15 revenue recognition follow the standard’s five-step model as a testing framework, beginning from the presumption that revenue carries a fraud risk and ending with a check that the disclosures match what the ledger actually shows. At each step the auditor asks a different question: is there a real contract, what did the company promise, how much will it collect, how should that amount be split across promises, and when has control passed to the customer. The work is judgment-heavy wherever contracts involve variable pricing, bundled deliverables, or long delivery schedules.

Starting From a Presumed Fraud Risk

International auditing standards treat revenue as a presumed fraud risk. ISA 240 requires the auditor to assume that revenue transactions create opportunities for material misstatement through manipulation and to design the audit response accordingly.¹ The presumption can be rebutted in narrow cases, such as a single, simple stream like rent from one property, but for most engagements it stays in place.

Before any detailed testing, the auditor identifies which revenue streams, transaction patterns, and financial statement assertions are most exposed. Companies that lean on estimates, book large year-end deals, or run complex contracts get the closest look. That risk assessment shapes sample sizes and the aggressiveness with which the auditor challenges management’s assumptions on things like variable pricing.

Assessing Internal Controls Over Revenue

Control testing determines how much the auditor can rely on the company’s own systems and how much must be tested transaction by transaction. Weak controls mean larger substantive samples; strong controls mean smaller ones.

The controls that matter most for IFRS 15 are:

Segregation of duties across sales order entry, billing, and payment processing, so one person does not run the full chain from contract approval to cash collection.
Documentation and approval layers, with evidence that supervisors or a separate department review revenue transactions before they are finalized in the accounting system.
Consistent policy application across contracts with similar characteristics, rather than ad hoc judgment that shifts from deal to deal.²

Where the auditor finds gaps, the plan shifts toward heavier substantive procedures on individual transactions.

Testing Whether a Contract Exists

Step 1 of the model asks whether a valid contract exists. Five criteria must all be met at the same time: both parties have approved the contract, each side is committed to its obligations, the rights to be transferred are identifiable, payment terms are clear, and collection is probable.³

Auditors inspect signed agreements, master service contracts, or digital purchase orders to confirm approval. Payment terms get traced back to the contract documents, and pricing is checked for enough specificity to measure reliably. Commercial substance receives particular attention where related parties trade back and forth; if future cash flows are not genuinely expected to change, the agreement fails and cannot support revenue.

Collection probability is where auditors push back hardest. They review the credit assessment process for new customers, looking at credit reports, historical payment patterns, and internal documentation about financial health. A contract with a customer known to be in financial distress cannot support recognition regardless of the sales figures, and the auditor will require an adjustment.

Contract Modifications

Contracts change mid-flight. The auditor’s job is to confirm each modification has been classified correctly, because the accounting differs sharply depending on how it is treated.²

A modification is a separate contract only when the added goods or services are distinct and the price increase reflects their standalone selling prices. When both conditions hold, the auditor tests it independently. When they do not, the auditor checks whether the company took the correct path. If the remaining deliverables are distinct from what has already been delivered, the old contract is treated as terminated and a new one created, with consideration reallocated at current standalone selling prices. If the remaining deliverables are not distinct, the company records a cumulative catch-up adjustment at the modification date. Auditors recompute those adjustments carefully; the wrong method can materially move revenue in the modification period.

Testing Performance Obligations

Once a valid contract is confirmed, the auditor identifies every distinct good or service the company promised. Each is a separate performance obligation and drives its own slice of revenue. A good or service is distinct when the customer can benefit from it on its own or with other readily available resources.³

Auditors read statements of work, technical specifications, and marketing materials to catalogue every promise. If the company sells a service separately to other customers, that is a strong signal it is distinct within a bundle. Where deliverables are highly interrelated, such as a custom software build with code and integration that have no standalone value, they are grouped into a single obligation. Interviews with project managers help expose the actual functional dependencies between deliverables.

Principal Versus Agent

A principal records gross revenue; an agent records only its commission or fee. IFRS 15 turns on whether the company controls the good or service before it reaches the customer.⁴

Auditors weigh three indicators: whether the company is primarily responsible for fulfilling the promise, whether it bears inventory risk before or after transfer, and whether it has discretion to set the price.⁴ No single indicator settles it, and a company can be a principal for one deliverable and an agent for another within the same contract. Where gross recording is not supported by genuine control, restatement to net reporting is required and the top line shrinks accordingly.

Warranties

Warranties fall into two classes. An assurance-type warranty simply promises the product meets agreed specifications and is accounted for as a cost accrual, not a separate obligation. A service-type warranty gives the customer something beyond that basic guarantee and is a separate obligation with its own share of the transaction price.⁵

Three factors guide classification: whether the warranty is legally required (pointing to assurance-type), how long the coverage lasts (longer periods point toward a service component), and the nature of the tasks the company will perform. Where both types are bundled and cannot reasonably be separated, the whole warranty is treated as one obligation. Auditors test the classification carefully, since calling a service warranty assurance-type accelerates revenue.

Testing the Transaction Price

Fixed price with a single deliverable is rare. Most of the audit effort goes into contracts with variable consideration, such as volume discounts, performance bonuses, or refund rights. The company must estimate these amounts using the expected value method (probability-weighted across outcomes) or the most likely amount method (the single most probable outcome).³

Auditors compare the estimates to historical data, current market conditions, and internal sales forecasts. They also verify the constraint on variable consideration, which limits recognized revenue to amounts highly unlikely to be reversed later. This is where the most aggressive accounting surfaces. Booking a full performance bonus before the customer has even evaluated the deliverable almost always breaches the constraint.

Allocation Across Performance Obligations

The transaction price is then distributed across each performance obligation based on relative standalone selling prices.³ Where observable prices exist, the math is straightforward. Where they do not, companies estimate using approaches like expected cost plus a margin or an adjusted market assessment. Auditors compare those internal models to third-party price lists, historical invoices, and competitor pricing, then recalculate the weighted distribution to confirm the allocated amounts sum to the total and that no obligation has been inflated to pull revenue forward.

Significant Financing Components

Long gaps between payment and delivery can embed a financing arrangement in what looks like a simple sale. IFRS 15 requires the transaction price to be adjusted for the time value of money where the financing benefit is significant.² Auditors calculate the implied interest rate and compare it to prevailing market rates, checking that interest income has not been buried inside revenue.

A practical expedient allows the adjustment to be skipped where the gap is one year or less. The auditor confirms the expedient is applied consistently and not cherry-picked contract by contract. Exceptions also apply to advance payments where the customer controls the delivery timing, such as gift cards, and to milestone-based payments tied to third-party approvals.

Rights of Return

Where customers can return products, revenue cannot be recognized on the goods expected back. The company records a refund liability for expected returns and a corresponding asset for the right to recover the products. Auditors test the return estimates against historical rates and current trends, verify that the refund liability is remeasured each reporting date, and confirm the return asset is recorded separately and adjusted for expected recovery costs or declines in value.

Testing When Revenue Is Recognized

Recognition turns on whether control of the good or service has actually passed. IFRS 15 defines control as the ability to direct the use of and obtain substantially all the remaining benefits from the asset.³ Auditors look at indicators such as physical possession, legal title, and transfer of significant risks.

Cutoff testing near period-end is where point-in-time recognition is proven or broken. Shipping logs, bills of lading, and freight invoices pin down when goods left the warehouse. Incoterms in the contract set the legal moment of transfer. A sale recorded on December 31 with goods that did not ship until January 2 gets moved to the correct period.

For revenue recognized over time, auditors evaluate the progress measurement method. Input methods rely on costs incurred or labor hours worked; output methods rely on milestones reached or units delivered. Input measures get traced to timesheets, payroll records, and subcontractor invoices. Output measures are tested against third-party certifications or engineering reports confirming that milestones are complete. Large progress jumps near period-end draw particular skepticism, since front-loading costs or claiming milestones early is a common way to accelerate revenue.

Bill-and-Hold Arrangements

Where the company bills the customer and books revenue while goods stay in its warehouse, four conditions must all be met:²

A substantive business reason exists, such as a customer facility not yet ready to receive the goods.
The goods are separately identified as belonging to the customer, through segregated storage or labeling.
The goods are complete and ready for physical delivery at any time.
The seller has no ability to use the goods or redirect them to another customer.

Auditors verify these through physical inspection of storage, review of customer correspondence requesting the hold, and examination of inventory records showing segregation. Missing any one condition keeps the revenue off the books until actual delivery.

Licensing

Licenses of intellectual property raise a timing question: does the customer receive a right to access the IP as it exists throughout the license period, or a right to use the IP as it existed at the grant date. The answer decides whether revenue is over time or at a single point.⁶

A right to access exists (over-time recognition) when three conditions all hold: the company undertakes activities that significantly affect the IP, the license exposes the customer to the effects of those activities, and those activities do not transfer a separate good or service to the customer. Activities that significantly change the IP’s form or functionality, or on which the customer’s ability to benefit substantially depends, meet the threshold.⁶ If any condition fails, it is a right to use and revenue is recognized at grant. Auditors examine what activities the company actually performs during the license period and whether they genuinely change the value of the IP the customer holds.

Testing Disclosures and Practical Expedients

IFRS 15 requires disaggregation of revenue so readers can understand the nature, amount, timing, and uncertainty of the company’s cash flows. Common categories include type of good or service, geographic region, and timing of transfer.⁷ Auditors reconcile the disclosed categories back to the audited trial balance to confirm every dollar of revenue is captured and correctly classified.

Contract balances need particular attention. Contract assets represent work completed but not yet billed; contract liabilities represent payments received for work not yet done. Auditors review the reconciliation of these balances from the start to the end of the reporting period, tracking how much revenue came from prior-period liabilities and how much new obligation was created. Inconsistencies between the disclosed reconciliation and the underlying ledger entries are a red flag.

IFRS 15 offers practical expedients with conditions attached. The portfolio approach lets the standard be applied to a group of similar contracts rather than individually, provided the financial statement effect would not differ materially. Another lets companies expense the costs of obtaining a contract immediately when the expected amortization period is one year or less.²

Auditors verify that each expedient is applied consistently across similar contracts and that documentation supports the conditions for using it. The final checks confirm that qualitative descriptions of accounting policies in the notes match the methods observed during testing. Where the written policy and the actual accounting diverge, the disclosures need to be corrected before the audit opinion is issued.

1
IAASA. International Standard on Auditing 240 – The Auditor’s Responsibilities Relating to Fraud
2
IFRS Foundation. IFRS 15 Revenue from Contracts with Customers – Full Standard
3
IFRS Foundation. IFRS 15 Revenue from Contracts with Customers
4
IFRS Foundation. IFRS 15 Post-Implementation Review – Principal Versus Agent Considerations
5
IFRS Foundation. IFRS 15 Transition Resource Group – Warranties
6
IFRS Foundation. IFRS 15 Post-Implementation Review – Licensing
7
IFRS Foundation. IFRS 15 Post-Implementation Review – Disclosure Requirements