The IFRS 15 Five-Step Model Applied to SaaS
IFRS 15 establishes a five-step framework for recognising revenue from customer contracts. The steps are sequential and each involves judgements that are specific to the SaaS business model. Working through them carefully, rather than treating them as a box-ticking exercise, is the foundation of a defensible revenue recognition policy.
- Identify the contract with the customer. A contract exists when it has commercial substance, the parties are committed, rights and payment terms are identified, and collection is probable. For SaaS, the contract is typically the signed order form or master service agreement. Watch for arrangements where the customer has a unilateral right to terminate without penalty: depending on the termination provisions, this may mean the contract is treated as a series of rolling monthly contracts rather than the stated term.
- Identify the performance obligations in the contract. Each distinct promise to transfer goods or services is a performance obligation. In SaaS contracts, the most common distinct performance obligations are: the right to access the software platform (a single ongoing obligation, typically recognised over time), implementation and onboarding services (potentially a distinct obligation or bundled with the licence), and support and maintenance (typically bundled with the access right unless it provides a service capability the customer could not obtain without it).
- Determine the transaction price. For pure subscription contracts with a fixed monthly or annual fee, this is straightforward. For usage-based or tiered contracts, the transaction price includes variable consideration that must be estimated under IFRS 15.50-58. The estimate must reflect the amount of variable consideration to which the entity will "probably not suffer a significant reversal" — the constrained estimate principle.
- Allocate the transaction price to the performance obligations. If the contract has multiple distinct performance obligations (e.g. implementation plus subscription), the transaction price is allocated to each based on standalone selling price (SSP). SSP is the price at which the entity would sell the good or service separately; where it is not directly observable, it must be estimated.
- Recognise revenue when (or as) each performance obligation is satisfied. Access rights to SaaS platforms are almost always recognised over time, as the customer simultaneously receives and consumes the benefit of the entity's performance. Usage-based fees are typically recognised as the usage occurs.
Usage-Based Fees and Variable Consideration
Usage-based pricing models (consumption pricing, transaction-volume pricing, API call pricing) create variable consideration under IFRS 15. The question is how to recognise revenue when the total consideration depends on future customer behaviour.
IFRS 15 provides a specific exception for usage-based (variable) consideration that relates entirely to a distinct performance obligation or to a specific part of a distinct performance obligation (the "allocation exception" in IFRS 15.B16). In practice, this exception allows SaaS businesses to recognise usage-based revenue as the usage occurs, without needing to estimate total contract value and allocate it over the contract term. This is the correct treatment for most pure usage-based pricing models.
The situation becomes more complex when usage-based fees are combined with a minimum commitment. A contract that charges £5,000 per month for up to 200,000 API calls, with a per-call charge above that threshold, has two components: a fixed minimum (recognised over the month as access to the platform is provided) and a variable overage (recognised as the calls above threshold occur).
Subscription vs Usage: The Recognition Timing Difference
The table below shows how different SaaS pricing models map to IFRS 15 recognition treatment. Understanding these mappings is essential for designing a revenue recognition policy that both reflects the commercial substance of your contracts and is defensible to auditors.
Multi-Element Arrangements: Implementation + Subscription + Support
Many SaaS businesses charge a separate implementation or onboarding fee alongside the subscription. Under IFRS 15, the question is whether the implementation service is a distinct performance obligation or whether it is combined with the access right into a single performance obligation.
The test for distinctness under IFRS 15.27-28 has two parts: (i) the customer can benefit from the good or service either on its own or together with other resources readily available to the customer (capable of being distinct), and (ii) the entity's promise to transfer the good or service is separately identifiable from other promises in the contract (distinct in the context of the contract).
In practice, the answer for SaaS implementation services depends on whether the implementation creates a "significant transformation" of the customer's environment. If the implementation is a standard data migration and configuration exercise that the customer could have completed using their own staff or a third-party implementation partner, it is likely capable of being distinct. If the implementation involves creating customised code or integrations that are integral to the subscription service, it is more likely to be combined with the access right into a single performance obligation.
Where implementation is determined to be a separate performance obligation, the transaction price must be allocated between implementation and subscription based on SSP. If you typically charge £10,000 for implementation and £2,000 per month for the subscription, the implementation SSP is £10,000. If the contract bundles them at a discount, the allocated amounts will differ from the stated prices.
"The most consequential IFRS 15 judgement for most SaaS businesses is not about variable consideration or performance obligations. It is about what happens to revenue timing when a customer has a perpetual right to terminate without penalty. Get this wrong and you are recognising annual contract revenue on day one of a rolling monthly arrangement."
Contract Modifications
SaaS customers frequently modify their contracts: upgrading to a higher tier, adding seats, reducing scope at renewal, or extending the term. Each of these is a contract modification under IFRS 15.18-21, and the accounting treatment depends on whether the modification adds distinct goods or services at their standalone selling price.
There are three scenarios. If the modification adds distinct goods or services at their SSP (e.g. a customer adds ten seats at the standard per-seat rate), it is treated as a separate contract. Revenue on the added seats is recognised from the date of the modification. If the modification is for distinct goods/services but not at SSP (e.g. a discounted upsell as an incentive), the original contract is terminated and a new combined contract is created, with the total remaining consideration allocated across remaining and new performance obligations. If the modification is for services not yet provided and is not distinct from the original services (e.g. an extension of the subscription term), it is treated as a modification of the original contract and revenue is recognised over the revised remaining term.
Common Errors That Auditors Flag
Based on the IASB's post-implementation review of IFRS 15 and publicly available commentary from Big 4 audit firms, the most common revenue recognition errors in SaaS businesses fall into the following categories.
- Treating implementation fees as upfront revenue: The most common error by some distance. Implementation fees are recognised when the implementation performance obligation is satisfied, not when cash is received. If implementation is a single distinct obligation completed over two to four months, revenue is recognised over that period. If it is combined with the subscription, it is recognised over the subscription term.
- Incorrect constraint of variable consideration: Companies sometimes apply the variable consideration constraint too conservatively, deferring recognition of usage-based fees that are highly probable. Conversely, they sometimes apply it too liberally, recognising full contract value without adequately constraining variable elements. The constraint should reflect the entity's historical experience of revenue reversals.
- Contract term determination for rolling contracts: Where a customer has a contractual right to terminate without penalty with 30 days' notice, some companies recognise annual contract value on the basis of the stated contract term. The correct treatment is typically to recognise revenue only over the period the contract is substantively non-cancellable, which in this case is 30 days. This can have a material impact on revenue timing and contract asset balances.
- SSP estimation: Where standalone selling prices are not directly observable, companies are required to estimate them. Common errors include using list prices (which may differ materially from actual selling prices), applying a single SSP to all geographies or customer segments (where pricing differs), and not updating SSP estimates when pricing changes occur.
- Contract cost capitalisation: IFRS 15.91-94 requires capitalisation of incremental costs of obtaining a contract (e.g. sales commissions) where they are expected to be recovered. The practical expedient allows immediate expensing where the amortisation period would be one year or less. Many SaaS companies apply this expedient to all sales commissions without assessing whether the commission relates to a contract with an expected term greater than one year. For enterprise SaaS contracts with three to five year terms, this may not be appropriate.
Key Takeaways
- Pure usage-based fees benefit from the IFRS 15.B16 variable consideration exception: they are recognised as usage occurs, without needing to estimate total contract value.
- Implementation fees must be analysed for distinctness. If distinct from the subscription, they are allocated a portion of the transaction price and recognised when the implementation is complete. If not distinct, they are recognised over the subscription term.
- Rolling monthly contracts with termination-for-convenience provisions should have their "contract term" assessed carefully. The recognition period is the substantively non-cancellable period, which may be far shorter than the stated contract term.
- Contract modifications are among the most judgment-intensive areas of IFRS 15 for SaaS businesses. Document each material modification and apply the three-scenario framework consistently.
- Capitalise sales commissions for contracts with expected terms greater than one year. Do not apply the short-term practical expedient to enterprise contracts without assessing the expected term.
- Revenue recognition policy should be documented in detail, reviewed annually, and signed off by the CFO and audit committee. Verbal descriptions of policy are insufficient for audit purposes.
- Align your ARR definition with your IFRS 15 revenue recognition policy. If your revenue recognition treats a contract as monthly but your ARR counts it as annual, you will face investor questions about the discrepancy.
