IFRS 15 Revenue Recognition: The 5-Step Model Explained for Practitioners

2026/3/21/

This article is also available in Japanese: IFRS 15 収益認識の5ステップをわかりやすく解説

TOC

Have You Ever Faced These Challenges?

You understand the five steps conceptually, but struggle to apply them consistently across different contract types in your organisation
Your auditors keep raising questions about whether revenue should be recognised at a point in time or over time — and you’re not confident in the reasoning
You adopted IFRS 15 during transition, but some of the underlying logic still feels unclear

What You Will Learn From This Article

Why IFRS 15 replaced IAS 18 and IAS 11, and what problems the old standards created in practice
How the five-step model works as an integrated framework
The key judgements required at each step and where practitioners commonly go wrong

Who This Article Is For

Finance and accounting professionals working at IFRS-reporting entities
Candidates preparing for USCPA, ACCA, or other professional qualifications
Finance professionals transitioning from local GAAP to IFRS for the first time

What Is IFRS 15 and Why Was It Created?

IFRS 15 Revenue from Contracts with Customers was jointly developed by the IASB and FASB and became mandatorily effective for annual periods beginning on or after 1 January 2018.

To understand why IFRS 15 matters, it helps to understand the problems it was designed to solve.

The Fragmented Landscape Under the Old Standards

Before IFRS 15, revenue recognition under IFRS was governed primarily by two standards that operated in parallel:

Standard	Scope	Recognition principle
IAS 18 Revenue	Sale of goods, rendering of services, interest, dividends, royalties	Transfer of risks and rewards (goods) / stage of completion (services)
IAS 11 Construction Contracts	Construction contracts	Percentage of completion method

On the surface, this appeared to be a clear division of scope. In practice, it created significant problems.

Problem 1: Form Over Substance

The most fundamental flaw was that economically similar transactions were accounted for differently depending on how the contract was structured, rather than on their economic substance.

Consider a large-scale IT system implementation. If the contract was framed as the sale of a completed system (goods), IAS 18 applied and revenue was recognised at delivery. If it was framed as development work performed to a customer’s specification (construction), IAS 11 applied and revenue was spread over the development period using percentage of completion.

The same economic activity, structured differently on paper, produced materially different financial statements. This undermined comparability across entities and periods.

Problem 2: Inadequate Guidance for Bundled Arrangements

Modern business models rarely involve the sale of a single product or service in isolation. Bundled arrangements — software licences combined with implementation services and multi-year maintenance, for example — were commonplace. Yet IAS 18 provided no robust framework for:

Allocating the contract price among the different elements of a bundle
Determining whether each element should be recognised separately or together
Handling situations where different elements were delivered at different points in time

The result was significant diversity in practice. Two companies with identical commercial arrangements could present revenue in materially different ways, making financial statement comparison meaningless — particularly in the software, SaaS, and telecommunications industries.

Problem 3: Inconsistent Treatment of Variable Consideration

Rebates, volume discounts, performance bonuses, returns, and price protection clauses are common features of commercial contracts. IAS 18 provided no systematic framework for estimating and constraining variable consideration. Entities applied widely varying approaches, with some recognising variable consideration early and others deferring recognition conservatively, resulting in further incomparability.

Problem 4: Ambiguous Scope of IAS 11

IAS 11 was originally designed for long-term civil engineering and construction contracts. Over time, it was extended by analogy to long-term service arrangements in industries including IT, aerospace, and defence. This stretched the standard beyond its intended design, and the guidance on measuring stage of completion left significant room for management judgement and, in some cases, manipulation.

What IFRS 15 Set Out to Achieve

The IASB and FASB responded by developing a single, principles-based framework applicable to all contracts with customers, regardless of industry or contract structure. The core innovation was replacing the IAS 18 concept of “transfer of risks and rewards” with a unified principle: revenue is recognised when control of a good or service transfers to the customer.

This control-based model provides a consistent analytical lens for all transactions — whether goods, services, or long-term contracts — and forms the foundation of the five-step model.

The Five-Step Model: An Overview

IFRS 15 establishes a five-step process for recognising revenue. The steps must be applied sequentially — if Step 1 is not satisfied, the entity cannot proceed to Step 2.

Step	Description
Step 1	Identify the contract with a customer
Step 2	Identify the performance obligations in the contract
Step 3	Determine the transaction price
Step 4	Allocate the transaction price to the performance obligations
Step 5	Recognise revenue when (or as) each performance obligation is satisfied

Step 1: Identify the Contract with a Customer

A contract is an agreement between two or more parties that creates enforceable rights and obligations. It does not need to be in writing — oral agreements and arrangements established by customary business practice also qualify, provided they are legally enforceable.

For a contract to be within the scope of IFRS 15, all five of the following criteria must be met (IFRS 15.9):

The parties have approved the contract and are committed to their respective obligations
Each party’s rights regarding the goods or services to be transferred can be identified
The payment terms for the goods or services can be identified
The contract has commercial substance
It is probable that the entity will collect the consideration to which it will be entitled

The fifth criterion — collectability — is frequently underestimated in practice. It requires an assessment of the customer’s ability and intention to pay, not merely the existence of a signed contract. Where collectability is not probable, revenue cannot be recognised even if the other four criteria are met.

Step 1 also addresses contract combinations (where multiple contracts should be treated as one) and contract modifications (changes to the scope or price of an existing contract), both of which require careful judgement.

Step 2: Identify the Performance Obligations in the Contract

A performance obligation is a promise to transfer a distinct good or service (or a series of distinct goods or services that are substantially the same and have the same pattern of transfer) to the customer.

A good or service is distinct if both of the following criteria are met (IFRS 15.27):

Criterion 1 — Capable of being distinct: The customer can benefit from the good or service on its own, or together with other resources that are readily available.

Criterion 2 — Distinct within the context of the contract: The promise to transfer the good or service is separately identifiable from other promises in the contract.

The second criterion is where most of the complexity lies in practice. Where goods or services are highly interdependent — for example, where an entity provides a significant integration service that combines multiple inputs into a single output — they are treated as a single performance obligation even if each input could theoretically be obtained separately.

Why this matters: The number of performance obligations identified determines how and when revenue is allocated and recognised. Misidentifying a bundle as a single performance obligation (or vice versa) can result in material misstatement of the timing and amount of revenue.

Step 3: Determine the Transaction Price

The transaction price is the amount of consideration to which the entity expects to be entitled in exchange for transferring the promised goods or services. Amounts collected on behalf of third parties (such as sales taxes) are excluded.

Four factors affect the determination of the transaction price:

Variable consideration: Where the consideration is variable (due to rebates, discounts, refunds, performance bonuses, penalties, or similar items), the entity must estimate the amount using either the expected value method (probability-weighted average across possible outcomes) or the most likely amount method (the single most likely outcome). Crucially, variable consideration is included in the transaction price only to the extent that it is highly probable that a significant reversal of cumulative revenue will not occur when the uncertainty is subsequently resolved.

Significant financing component: Where the timing of payment provides the customer or the entity with a significant benefit of financing, the transaction price must be adjusted to reflect the cash selling price. A practical expedient allows entities to disregard the financing component where the interval between transfer and payment is one year or less.

Non-cash consideration: Measured at fair value.

Consideration payable to a customer: Treated as a reduction of the transaction price unless it represents payment for a distinct good or service received from the customer.

Step 4: Allocate the Transaction Price to the Performance Obligations

Where a contract contains more than one performance obligation, the transaction price is allocated to each on the basis of relative standalone selling prices (SSPs).

The SSP is the price at which an entity would sell the good or service separately to a customer. Where SSPs are directly observable (i.e., the entity sells the item on a standalone basis), the observed price is used. Where SSPs are not directly observable, they must be estimated using one of three methods:

Adjusted market assessment approach — based on observable market prices for similar goods or services, adjusted for the entity’s circumstances
Expected cost plus a margin approach — based on the expected cost of satisfying the performance obligation plus an appropriate profit margin
Residual approach — the transaction price less the sum of observable SSPs of other performance obligations (permitted only in limited circumstances where the SSP is highly variable or uncertain)

Discounts are generally allocated across all performance obligations in proportion to their SSPs, unless specific criteria are met that demonstrate the discount relates only to a subset of the obligations.

Step 5: Recognise Revenue When (or As) Each Performance Obligation Is Satisfied

Revenue is recognised when control of the promised good or service transfers to the customer. Control transfers either at a point in time or over time, depending on the nature of the performance obligation.

Over Time Recognition

A performance obligation is satisfied over time if any one of the following three criteria is met (IFRS 15.35):

The customer simultaneously receives and consumes the benefits as the entity performs (e.g., routine cleaning or payroll processing services)
The entity’s performance creates or enhances an asset that the customer controls as the asset is created or enhanced (e.g., construction on the customer’s land)
The entity’s performance does not create an asset with an alternative use to the entity, and the entity has an enforceable right to payment for performance completed to date

Where over-time recognition applies, revenue is recognised based on the entity’s progress towards complete satisfaction of the obligation. Progress can be measured using output methods (e.g., milestones achieved, units delivered) or input methods (e.g., costs incurred relative to total estimated costs, labour hours).

Point in Time Recognition

Where none of the three criteria above is met, revenue is recognised at the point in time when control transfers. IFRS 15.38 provides five indicators to assist in determining when control has transferred:

The entity has a present right to payment
The customer has legal title to the asset
The entity has transferred physical possession
The customer has the significant risks and rewards of ownership
The customer has accepted the asset

No single indicator is determinative — the assessment requires judgement based on all relevant facts and circumstances.

Summary: Key Takeaways From the Five-Step Model

IFRS 15 replaced IAS 18 and IAS 11 to address comparability failures caused by form-driven accounting and inadequate guidance for bundled arrangements
The five steps must be applied sequentially — failure at any step affects all subsequent steps
The number of performance obligations identified (Step 2) determines how revenue is allocated (Step 4) and when it is recognised (Step 5)
Variable consideration (Step 3) requires careful estimation and must be constrained to the amount for which a significant revenue reversal is highly improbable
The over-time vs point-in-time distinction (Step 5) is one of the most judgement-intensive areas in practice, particularly for long-term contracts in construction, IT, and manufacturing

Each of these five steps contains significant technical depth. In the articles that follow, we examine each step in detail — covering the key judgements, common pitfalls, and industry-specific considerations that practitioners encounter in applying IFRS 15.