IFRS 15 Revenue Recognition: The Five-Step Model and Beyond

The IFRS 15 five-step revenue recognition model is the framework the International Accounting Standards Board uses to decide when and how much revenue a company reports from contracts with customers. It replaced the older “risks and rewards” approach with a control-based principle: revenue is recognized when a customer gains control of the promised goods or services, not simply when the seller has offloaded risk.¹ The five steps run in order, each building on the last, and every revenue transaction in scope passes through all of them.

The standard has been mandatory for reporting periods beginning on or after January 1, 2018, and applies across nearly every industry. In the United States, the Financial Accounting Standards Board issued ASC Topic 606 as a converged companion standard, so the two frameworks are largely aligned, with a few differences in areas like the collectibility threshold and intellectual property licenses.²

Step 1: Identify the Contract

A contract under IFRS 15 is any agreement that creates enforceable rights and obligations. It can be written, oral, or implied by customary business practices. Five criteria must all be met before the standard applies:³

All parties have approved the contract and are committed to performing their obligations.
Each party’s rights regarding the goods or services can be identified.
The payment terms are identifiable.
The contract has commercial substance, meaning it changes the risk, timing, or amount of the entity’s future cash flows.
It is probable the entity will collect the consideration it is entitled to receive.

If any criterion is not met at inception, there is no contract under IFRS 15 and no revenue can be recognized yet. The entity reassesses periodically to see whether the criteria are later satisfied. The commercial substance test is what prevents entities from manufacturing revenue through round-trip transactions with no real economic effect.

Step 2: Identify the Performance Obligations

Once a valid contract exists, the entity examines every promise it has made and identifies which ones represent separate performance obligations. A promised good or service is distinct if the customer can benefit from it on its own (or with other readily available resources) and the entity’s promise to deliver it is separately identifiable from other promises in the contract.¹

A software company that sells a license along with installation and ongoing support would typically identify three performance obligations because each deliverable can function independently. If the installation fundamentally customizes the software so it has no value without that customization, those two promises might be combined into a single obligation.

The standard also allows a series of substantially identical goods or services to be treated as one performance obligation, provided each item in the series would qualify as an over-time obligation and the same method would measure progress across all of them. Weekly cleaning services delivered under a 12-month contract are a typical example.³

Step 3: Determine the Transaction Price

The transaction price is the total amount the entity expects to receive in exchange for delivering the promised goods or services. In many contracts, that number is straightforward. It gets complicated when the price includes variable elements: volume discounts, rebates, refunds, performance bonuses, or penalties.¹

Variable consideration is estimated using one of two methods. The expected value is a probability-weighted average of possible outcomes, useful when there are many possible scenarios. The most likely amount works best for binary outcomes where the entity either earns a bonus or does not. Whichever method better predicts the actual outcome should be used consistently for that type of variable consideration.

Estimated variable consideration is also subject to a constraint. An entity includes variable amounts in the transaction price only to the extent it is “highly probable” a significant reversal of cumulative revenue will not occur when the uncertainty resolves. In practice, that means considering both how likely a reversal is and how large it would be. The constraint acts as a check against overly optimistic revenue projections.³

If the contract has a significant financing component, meaning the customer pays far in advance or well after delivery, the entity adjusts the transaction price for the time value of money. Interest income or expense is recognized separately from revenue.

Step 4: Allocate the Transaction Price

When a contract has more than one performance obligation, the total transaction price is split among them based on their relative standalone selling prices. The standalone selling price is what the entity would charge if it sold that good or service separately to a similar customer in similar circumstances.¹

Observable prices from past standalone sales are the best evidence. When those are unavailable, the entity estimates using one of three methods:

Adjusted market assessment: evaluating what customers in the market would pay, including reference to competitor pricing adjusted for the entity’s own costs and margins.
Expected cost plus margin: forecasting the costs of satisfying the obligation and adding an appropriate profit margin.
Residual approach: deducting the observable standalone selling prices of other items from the total transaction price. This method is only permitted when the selling price is highly variable or has not yet been established.

A discount in a bundled package is typically spread proportionally across all obligations rather than loaded onto one, so the revenue recognized for each deliverable reflects the value actually provided.

Step 5: Recognize Revenue

Revenue is recognized as the entity satisfies each performance obligation by transferring control of the promised good or service to the customer.¹ Control means the customer can direct the use of the asset and obtain substantially all of its remaining benefits.

A performance obligation is satisfied over time if at least one of the following is true:

The customer simultaneously receives and consumes the benefits as the entity performs, common with recurring services like cleaning or payroll processing.
The entity’s performance creates or enhances an asset the customer controls as work progresses, for example building a structure on a customer’s property.
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 work completed to date.

If none of those criteria are met, revenue is recognized at a point in time. That point is typically when the customer takes physical possession, obtains legal title, or the entity has a present right to payment for the delivered asset. For a standard product shipment, that moment usually aligns with delivery.

Principal Versus Agent

One judgment that sits inside the five-step model and often changes the reported revenue figure is whether the entity acts as a principal or an agent. A principal controls the goods or services before they reach the customer and reports revenue at the gross amount received. An agent arranges for another party to provide the goods or services and reports only its fee or commission as revenue.⁴

The difference in the top-line number can be enormous. A travel booking platform that processes $500 million in hotel reservations but earns a 15 percent commission reports either $500 million (principal) or $75 million (agent) in revenue, with identical profit either way. Several indicators help resolve the question:⁵

Whether the entity is primarily responsible for fulfilling the promise to deliver the good or service.
Whether the entity bears inventory risk before transfer or on return.
Whether the entity has discretion in setting the price.

These indicators support the overall assessment of control but are not a checklist. No single indicator is decisive on its own, and different indicators carry more weight depending on the transaction. This remains one of the most actively debated areas in applying IFRS 15, particularly for digital platforms and marketplaces.

Handling Contract Modifications

Customers expand scope, cut quantities, or renegotiate prices midway through delivery, and the treatment depends on the nature of the change.³

A modification is treated as a separate, standalone contract when two conditions are both met: the scope increases because the entity promises additional distinct goods or services, and the price increase reflects the standalone selling prices of those additions. When a customer adds 50 more units to an existing order at the normal per-unit price, revenue on the original contract continues unaffected and the new units get their own accounting.

When a modification does not qualify as a separate contract, the treatment depends on whether the remaining undelivered goods or services are distinct from what has already been transferred. If the remaining items are distinct, the entity treats the modification as though the original contract ended and a new one began, reallocating the combined remaining consideration across the remaining obligations. If the remaining items are not distinct, the entity treats the modification as part of the existing contract and makes a cumulative catch-up adjustment to revenue at the modification date. That second case is common in construction projects where the work before and after the modification forms a single integrated deliverable.

What Sits Outside the Model

IFRS 15 covers contracts where a customer purchases goods or services that are the output of an entity’s ordinary business activities, but several categories are handled by their own dedicated standards. Leases fall under IFRS 16.⁶ Insurance contracts fall under IFRS 17. Financial instruments fall under IFRS 9.⁷

When a single contract falls partly within IFRS 15 and partly under another standard, the entity applies the other standard’s separation and measurement rules first, then applies IFRS 15 to whatever remains. A contract bundling a product sale with a lease requires the entity to separate the lease component under IFRS 16 before recognizing revenue on the product portion under IFRS 15. Getting that split wrong is one of the more common sources of restatement in industries where bundled deals are the norm.

1
IFRS. IFRS 15 Revenue from Contracts with Customers
2
Financial Accounting Standards Board. Comparison of Topic 606 and IFRS 15
3
IFRS Foundation. IFRS 15 Revenue from Contracts with Customers
4
IFRS Foundation. Gross versus Net Revenue: Amounts Billed to Customers
5
IFRS Foundation. IFRS 15 Post-implementation Review – Principal versus Agent Considerations
6
IFRS Foundation. IFRS 16 Leases
7
IFRS Foundation. IFRS 9 Financial Instruments