What Is IFRS 15? Revenue Recognition Explained

IFRS 15 is the international accounting standard that governs how companies recognize revenue from contracts with customers. Issued by the International Accounting Standards Board and effective on 1 January 2018, it replaced a scattered set of older rules with a single five-step model that applies to almost every industry.¹ The U.S. Financial Accounting Standards Board issued a substantially identical version as ASC 606, so the same core framework now sits behind revenue numbers under both IFRS and U.S. GAAP.² The core principle is simple to state: recognize revenue to reflect the transfer of goods or services in the amount the company expects to receive in exchange.

Why One Standard Replaced Several

Before 2018, IFRS reporters worked from a patchwork. IAS 18 handled general sales of goods and services, IAS 11 handled construction contracts, and a series of interpretations (IFRIC 13, IFRIC 15, IFRIC 18, and SIC-31) filled gaps for loyalty programs, real estate sales, and barter transactions.¹ The rules overlapped in some places and left blanks in others, and two companies in the same industry could report economically identical deals in different ways.

IFRS 15 collapsed all of that into one framework built around the transfer of control. The practical payoff is comparability across borders. An investor looking at a European telecom and an American one can now read the same line items built on the same logic. The trade-off is that the new standard asks preparers for significantly more judgment, especially when identifying performance obligations and estimating variable consideration.

Which Contracts IFRS 15 Covers

IFRS 15 applies to any contract in which a company promises goods or services to a customer in exchange for consideration. “Customer” here means a party contracting for the output of the company’s ordinary business, not just anyone who happens to pay money. The contract must be legally enforceable and create identifiable rights and obligations on both sides.

Several kinds of contract sit outside its scope because other standards handle them:

Leases fall under IFRS 16.
Insurance contracts fall under IFRS 17, though an entity can elect to apply IFRS 15 to certain fixed-fee service contracts that meet the insurance definition.
Financial instruments fall under IFRS 9.
Non-monetary exchanges between companies in the same line of business made to facilitate sales to end customers are excluded.

When a contract mixes elements from different standards, such as a lease bundled with a maintenance service, the entity separates the components and applies the right standard to each piece.¹

The Five-Step Model

Every revenue transaction under IFRS 15 runs through the same five steps in order, regardless of industry. Each step feeds into the next.

Step 1: Identify the Contract

A contract exists for IFRS 15 purposes only when all five of these are true:

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

If any criterion fails, no revenue can be recorded. Cash received in the meantime sits on the balance sheet as a liability until the conditions are met or the arrangement is abandoned.³

Step 2: Identify the Performance Obligations

A performance obligation is a promise to transfer a distinct good or service. A good or service is distinct when the customer can benefit from it on its own or with resources readily available, and the promise is separately identifiable from the other promises in the contract.¹

If a promised item is not distinct, such as a custom software module that only works as part of an integrated system, it is bundled with other promises until the combined package is distinct. This step drives the amount and timing of revenue recognition, so mistakes here cascade through everything that follows.

Step 3: Determine the Transaction Price

The transaction price is what the entity expects to receive, not necessarily the sticker figure on the contract. Several adjustments can move it:

Variable consideration covers discounts, rebates, refunds, penalties, and performance bonuses. The entity estimates the amount using either the expected-value method (a probability-weighted average) or the most-likely-amount method (the single most probable outcome), whichever better predicts the final figure. Variable amounts are included in revenue only to the extent that a significant reversal of cumulative revenue is highly unlikely once the uncertainty resolves.³
A significant financing component arises when the timing of payments effectively gives one party a financing benefit. The entity adjusts the price for the time value of money. A practical expedient lets entities skip the adjustment when the gap between delivery and payment is expected to be one year or less.³
Non-cash consideration (goods, services, or equity received instead of cash) is measured at fair value. If fair value cannot be reasonably estimated, the entity falls back to the standalone selling price of what it promised in exchange.⁴
Consideration payable to a customer, such as slotting fees paid to a retailer, reduces the transaction price unless the payment is for a distinct good or service.

Step 4: Allocate the Price to the Performance Obligations

If a contract has more than one performance obligation, the transaction price is split among them based on their relative standalone selling prices, meaning the price at which the entity would sell each item on its own.¹ Where a standalone price is not directly observable, the entity estimates it by one of three methods:

Adjusted market assessment, looking at what customers in the market would pay, sometimes referencing competitor pricing adjusted for the entity’s costs and margins.
Expected cost plus a margin, forecasting the cost of satisfying the obligation and adding a reasonable profit.
The residual approach, subtracting the known standalone prices of other obligations from the total and assigning what remains. This method is restricted to situations where the selling price is highly variable or has never been established.

Step 5: Recognize Revenue

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

Transfer can happen at a single point in time or over time. Revenue is recognized over time if any one of the following applies:

The customer simultaneously receives and consumes the benefits as the entity performs. A routine cleaning service is the textbook example.
The entity’s work creates or enhances an asset the customer already controls, like a building on the customer’s land.
The entity’s work 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 apply, the obligation is satisfied at a point in time. The entity then looks at indicators like transfer of legal title, physical possession, the significant risks and rewards of ownership, customer acceptance, and the present right to payment to pinpoint exactly when control passes.

Where Judgment Bites

Contract Modifications

Customers add scope, cut scope, and renegotiate prices. IFRS 15 treats a modification as a separate contract when it adds distinct goods or services and the price rises by the standalone selling prices of those additions. Nothing changes for the original contract in that case.³

Otherwise, the entity picks between two treatments. If the remaining goods or services are distinct from what has already been transferred, the entity accounts for the change as a termination of the old contract and the creation of a new one, reallocating the remaining consideration. If the remaining goods or services are not distinct because they are part of a partially completed obligation, the entity treats the modification as part of the original contract and adjusts revenue on a cumulative catch-up basis at the modification date.

Licenses of Intellectual Property

Licenses raise a specific question: is the customer getting a snapshot of the IP as it exists today, or ongoing access to something that keeps changing? A license grants a right of access, recognized over time, only when the entity is expected to undertake significant activities that affect the IP, the customer is exposed to the effects of those activities, and those activities do not themselves transfer a separate good or service.

When any of those criteria fails, the license grants a right to use the IP as it existed at the point it was transferred, and revenue is recognized at that point. In practice, licenses of functional IP like completed software or a patented drug formula usually produce point-in-time recognition, while licenses of symbolic IP like brand names or franchise rights usually produce over-time recognition because the brand depends on the entity’s ongoing activities.

Principal or Agent

When more than one party is involved in getting goods or services to the customer, the entity has to decide whether it is a principal (record gross revenue) or an agent (record only its commission or fee). The test is control: does the entity control the specified good or service before transferring it to the customer?⁵

Three indicators help with the assessment: the entity is primarily responsible for fulfilling the promise to the customer; the entity bears inventory risk before or after transfer; and the entity has discretion in setting the price. No single indicator is decisive, and their weight varies by contract. This remains one of the most debated areas of IFRS 15, particularly for platform businesses and marketplaces.

Warranties

An assurance-type warranty simply promises that the product meets agreed specifications and is free from defects. It is not a separate performance obligation; it is a provision under IAS 37. A service-type warranty offers something extra, such as extended coverage or supplemental support, and is a separate performance obligation, so a portion of the transaction price is allocated to it and recognized over the warranty period.

A warranty is likely a service-type warranty if it can be purchased separately or if it covers more than just defects. Longer periods also point in that direction. When both types are present and cannot be reliably separated, the whole warranty is treated as a single performance obligation.

Sales With a Right of Return

When customers can return products, the entity does not recognize revenue for the portion of sales expected to come back. Instead it records a refund liability for expected returns, keeps the cost of those items out of cost of sales, and records a separate asset for the right to recover the returned goods.³ Both are updated at each reporting date. A customer swapping a product for the same item in a different size or color is not treated as a return; revenue stays recognized as of the original sale.

How It Shows Up in the Financial Statements

On the balance sheet, the status of each contract shows up as either a contract asset or a contract liability. A contract asset arises when the entity has delivered goods or services but its right to payment depends on something beyond the passage of time, typically the satisfaction of another performance obligation in the same contract.¹ Once the right to payment becomes unconditional, the amount is reclassified to a receivable.

A contract liability arises when the customer has paid, or a payment is due, before the entity has transferred the corresponding goods or services. Subscription prepayments, customer deposits, and advance billings on long-term projects all sit here until the entity performs. The distinction between a contract asset and a receivable matters: a receivable carries only credit risk, while a contract asset carries both credit risk and performance risk.

Disclosures under IFRS 15 are deliberately broad. Entities disaggregate revenue into categories showing how economic factors such as geography, product line, customer type, and timing of transfer affect cash flows, and they report opening and closing balances of receivables, contract assets, and contract liabilities.⁶ They also disclose the significant judgments behind the numbers: how variable consideration was estimated, how standalone selling prices were set, and why obligations were classified as satisfied over time or at a point in time. Those judgment disclosures are what keeps aggressive assumptions from hiding inside a clean revenue line.

1
IFRS. IFRS 15 Revenue from Contracts with Customers
2
FASB. IASB and FASB Issue Converged Standard on Revenue Recognition
3
IFRS Foundation. IFRS 15 – Revenue from Contracts with Customers
4
IFRS Foundation. Revenue from Contracts with Customers – Non-cash Consideration
5
IFRS Foundation. Post-implementation Review of IFRS 15 – Principal Versus Agent Considerations
6
IFRS Foundation. Post-implementation Review of IFRS 15 – Disclosure Requirements