IFRS 15 for Usage-Based Revenue
The Complete Guide
IFRS 15 governs revenue recognition for companies reporting under international accounting standards. This guide covers how the five-step model applies to usage-based and consumption contracts, the right-to-invoice expedient, and exactly where IFRS 15 diverges from its US counterpart, ASC 606.
IFRS 15 Definition
IFRS 15, Revenue from Contracts with Customers, is the International Accounting Standards Board's converged revenue recognition standard, effective for periods beginning on or after January 1, 2018. For usage-based and consumption contracts, revenue is recognized as the customer consumes the service — using the same five-step model, right-to-invoice expedient, and variable-consideration framework as the equivalent US standard, ASC 606.
The five-step model, applied to usage
Structurally identical to ASC 606 — the practical difference for usage-based revenue shows up in steps 3 and 5.
Identify the contract with a customer
IFRS 15.9 sets the same five criteria as ASC 606 — approval, identifiable rights, payment terms, commercial substance, and probable collectibility.
Identify the performance obligations
A distinct good or service, or a series of distinct goods/services that are substantially the same and have the same pattern of transfer — the basis for stand-ready usage obligations.
Determine the transaction price
Including estimates of variable consideration (IFRS 15.50–54) using expected value or most-likely-amount, whichever better predicts the amount of consideration.
Allocate the transaction price
Based on relative standalone selling prices (IFRS 15.73–86), consistent with ASC 606.
Recognize revenue as obligations are satisfied
Over time or at a point in time (IFRS 15.31–38) — usage and consumption contracts are almost always satisfied over time.
Where IFRS 15 and ASC 606 agree
The two standards were built jointly. For usage-based revenue specifically, they land in the same place.
Core five-step model
Identical structure and largely identical wording — IFRS 15 and ASC 606 were developed jointly by the IASB and FASB as a converged standard.
Right-to-invoice practical expedient
Available under both (IFRS 15.B16 / ASC 606-10-55-18) — if the invoice corresponds directly to the value transferred, recognize the amount you have the right to bill.
Sales- and usage-based royalty exception
Both standards limit this exception to licenses of intellectual property (IFRS 15.B63 / ASC 606-10-55-65) — it does not apply to most usage-based SaaS.
Variable consideration methods
Both require expected value or most-likely-amount, whichever better predicts the entitlement, with a constraint on inclusion.
Where they differ
Narrow, and mostly outside the core usage-recognition mechanics — but worth documenting if you report under both frameworks.
Collectibility threshold
ASC 606 requires collection to be "probable" (a US GAAP-defined threshold, generally interpreted as more likely than not to a high probability). IFRS 15 also uses "probable" but under IAS-based interpretation, which can produce different practical outcomes in marginal cases.
Contract costs
IFRS 15 has narrower guidance on incremental costs of obtaining a contract than the equivalent ASC 340-40 guidance under US GAAP — capitalization outcomes can differ for commission-heavy SaaS sales models.
Interim disclosures
IFRS entities generally follow IAS 34 for interim reporting, which has different disaggregation and disclosure requirements than the ASC 606 interim disclosure package under US GAAP.
Licensing guidance nuances
Application guidance on licenses of IP has minor wording differences between the boards' final standards, though the usage-based royalty exception itself is aligned.
How LedgerUp handles IFRS 15
Ari reconciles usage to the contract and generates recognition schedules using the same estimation logic that underlies both ASC 606 and IFRS 15, with policy documentation for the narrower reporting differences between them.
IFRS 15 FAQ
What is IFRS 15?
IFRS 15, Revenue from Contracts with Customers, is the International Accounting Standards Board's revenue recognition standard, effective for annual periods beginning on or after January 1, 2018. It was developed jointly with the US FASB's ASC 606 as a converged global revenue standard and uses the same five-step model: identify the contract, identify performance obligations, determine the transaction price, allocate the price, and recognize revenue as obligations are satisfied.
How does IFRS 15 apply to usage-based revenue?
Usage-based fees are variable consideration under IFRS 15, just as under ASC 606. Most usage-based SaaS contracts either qualify for the right-to-invoice practical expedient (IFRS 15.B16) — recognizing revenue at the amount you have the right to bill when it corresponds to value transferred — or require an expected-value or most-likely-amount estimate when minimum commitments, tiered pricing, or retroactive pricing decouple the invoice from the value delivered.
Is IFRS 15 the same as ASC 606?
IFRS 15 and ASC 606 are substantially converged — same five-step model, same right-to-invoice expedient, same usage-based royalty exception limited to IP licenses, and the same core approach to variable consideration and the constraint. Differences are narrower and concentrated in collectibility thresholds, contract cost capitalization guidance, interim disclosure requirements under IAS 34 versus the ASC 606 disclosure package, and minor licensing application guidance — not in how usage-based revenue itself is recognized.
Does the right-to-invoice practical expedient exist under IFRS 15?
Yes. IFRS 15.B16 provides the same expedient as ASC 606-10-55-18: if an entity has a right to consideration from a customer in an amount that corresponds directly with the value to the customer of the entity's performance completed to date, the entity may recognize revenue in that amount. This is the most commonly used simplification for straightforward, arrears-invoiced usage-based SaaS contracts under both standards.
Does the usage-based royalty exception apply under IFRS 15?
Only to licenses of intellectual property (IFRS 15.B63, paralleling ASC 606-10-55-65). Most usage-based SaaS is a service — access to a hosted platform, not a license of IP — so the royalty exception does not apply. Revenue is instead recognized as the service is consumed, typically via the right-to-invoice expedient or a variable-consideration estimate.
Can a company use one revenue recognition policy for both US GAAP and IFRS reporting?
For usage-based revenue specifically, in most cases yes — because the core mechanics (five-step model, right-to-invoice expedient, royalty exception, variable consideration methods) are aligned. Companies reporting under both frameworks typically maintain one policy for the usage-recognition mechanics and document narrower reconciling items separately (collectibility assessment, contract cost capitalization, and disclosure formatting) rather than running two parallel recognition engines.
How does LedgerUp support both ASC 606 and IFRS 15?
LedgerUp reconciles usage against the signed contract and generates recognition schedules using the same expected-value / most-likely-amount and constraint logic that underlies both standards, with configurable policy documentation for the narrower areas — collectibility assessment, contract cost treatment, and disclosure detail — where ASC 606 and IFRS 15 diverge.