IFRS 15

IFRS 15 is the International Financial Reporting Standard for Revenue from Contracts with Customers, issued by the IASB in 2014 and effective worldwide from 2018. It replaces dozens of fragmented rules with a single five-step framework: identify the contract, identify performance obligations, determine transaction price, allocate that price to obligations, and recognize revenue when control transfers. For multinational companies, it harmonizes accounting with ASC 606, the parallel U.S. standard.

The global shift away from rule-based recognition

Before 2018, revenue recognition was a patchwork. A company manufacturing equipment followed one rule, a software vendor another, a construction company yet another. Most rules were industry-specific and had accumulated over decades, creating inconsistency across borders and sectors. IFRS 15 eliminated that fragmentation. Rather than laying out hundreds of scenarios, it set one principle: revenue is earned when control of a promised good or service transfers to the customer. That principle applies to any contract, any industry, any geography.

Simultaneous with IFRS 15, the FASB (U.S. standard-setter) issued ASC 606, which uses the same five-step framework. The two standards are substantially identical, making it possible for multinational companies to use similar accounting logic on both sides of the Atlantic. This was not a coincidence: the two bodies worked together to create converged standards, though differences remain in a handful of narrow areas.

The five-step framework

IFRS 15 is organized around five sequential decisions:

Step 1: Identify the contract — Does an agreement with a customer exist? Is it approved by both parties? Is it probable that payment will be collected? If not, no contract exists and no revenue is recognized.

Step 2: Identify performance obligations — What promises are embedded in the contract? If a company sells hardware bundled with three years of software updates, those are separate promises (or “performance obligations”). Each must be tracked separately.

Step 3: Determine the transaction price — What is the customer paying? This includes not just the stated price but also variable consideration (discounts, rebates, returns) and financing elements. The company estimates the amount it will ultimately receive.

Step 4: Allocate the price to obligations — The transaction price is divided among the performance obligations. If a customer pays €1,000 for goods worth €600 and services worth €400 (at stand-alone-selling-price), the goods get €600 of the price and the services get €400. This allocation determines how much revenue is recognized for each part of the contract.

Step 5: Recognize revenue when (or as) control transfers — As the company satisfies each performance obligation, it recognizes the allocated portion of the price as revenue. For a single shipment of goods, this happens at delivery. For a service delivered over time, revenue is recognized over that period.

Performance obligations: the engine of the standard

The concept of “performance obligations” is central. A contract may contain one or several. Recognizing them correctly requires judgment. If a retailer sells a coffee maker with a five-year warranty, the sale and the warranty are separate obligations: one satisfied at delivery, one satisfied over five years. If a software vendor signs a five-year licensing agreement with quarterly updates, there is one obligation (the license right, satisfied over time) or multiple obligations (if each update is a separable promise). Getting this wrong cascades through the rest of the framework.

IFRS 15 says obligations are separate if the customer can benefit from the good or service on its own or in combination with other resources, and if the entity’s promise to deliver it is separately identifiable. This is clearer than it sounds in some cases, murky in others. A laptop bundled with pre-installed software is usually one obligation (the customer benefits from the bundle, not the software alone). A laptop bundled with a separate software license is often two (the license is standalone).

Estimating variable consideration

IFRS 15 requires companies to estimate the transaction price, including any variable elements. If a company offers a 10% volume rebate or accepts product returns within 30 days, those possibilities must be factored into the revenue recognised. The company estimates using either the “expected value” method (probability-weighted average of scenarios) or the “most likely amount” method (single most probable outcome). Most companies use expected value.

This is more conservative than pre-2018 rules, which often let companies ignore rebates or returns that hadn’t been incurred yet. Under IFRS 15, a retailer selling units with a 5% expected return rate must accrue for those returns at the time of sale. This often results in lower reported revenue in early periods, offset by recognition of returns revenue later when units are actually returned.

The role of stand-alone-selling-price

A practical challenge in Step 4 is determining how to allocate the transaction price when the contract bundles multiple performance obligations. IFRS 15 says the starting point is the stand-alone-selling-price of each obligation — that is, the price at which the company would sell that obligation separately. If a company usually sells a printer for $300 and ink cartridges for $20 per unit, and a customer buys a printer bundled with 12 cartridges for $540, the stand-alone selling prices dictate the allocation: roughly $300 to the printer and $240 to the cartridges. If stand-alone prices are not directly observable (for custom services, for instance), the company estimates using market conditions, adjusted prices, or expected cost plus a markup.

This can be contentious. Managers sometimes argue about what the “true” standalone price would be for a proprietary service. Auditors demand evidence. The standard requires companies to document their methods, usually in the notes to the financial statements.

From accrual accounting to control-based recognition

IFRS 15 is not purely accrual-based. Accrual accounting recognizes revenue when earned (typically at delivery or invoice); IFRS 15 recognizes revenue when control transfers. For most transactions, these are the same. But for contracts where the customer receives goods before paying, or pays before receiving them, the timing can differ. The standard also introduced new balance-sheet accounts: “contract assets” (recognised revenue not yet invoiced) and “contract liabilities” (invoiced revenue not yet earned). These replace the older “unbilled receivables” and “deferred revenue” labels, though the economics are similar.

Practical impact on earnings and disclosure

When IFRS 15 went live, many companies’ reported revenues changed. Software companies that had recognized annual licence fees upfront now spread them over the licence period. Retailers that had ignored expected returns now accrued for them. Construction companies that had used percentage-of-completion accounting had to reconcile those estimates to the IFRS 15 control-transfer principle. In some cases, reported revenue fell; in others, it rose. The adjustments were rarely small.

The standard also requires extensive disclosure: companies must explain their revenue policies, break down revenue by type, disclose unsatisfied performance obligations, and disclose judgments about variable consideration and standalone prices. For a financial statement reader, these notes are essential to understanding whether revenue quality is high or whether the company is making aggressive estimates.

Relationship to ASC 606

ASC 606 uses the identical five-step framework and was converged with IFRS 15 at issuance. Both became effective in 2018. The standards are substantially the same, allowing a multinational company to use similar revenue policies across jurisdictions. Differences exist in a few areas—contract modifications, returns, and certain software arrangements—but are narrow enough that most companies follow a unified policy. For reporting purposes, U.S. public companies file using ASC 606; non-U.S. filers use IFRS 15.

See also