In plain words
SaaS deals often bundle implementation or customisation with the subscription. IFRS 15 asks whether these services are a separate performance obligation. They are distinct only if the customer can benefit from them separately and they are not highly interdependent with the subscription. If customisation is essential for the platform to work for that customer, both are combined and usually recognised over the subscription term.
Why it matters
SaaS deals often bundle implementation, customization, or integration services with the underlying subscription, and whether these services are distinct performance obligations (recognized as delivered, often quickly) or combined with the subscription into a single obligation (recognized over the longer subscription term) changes both the timing and the pattern of revenue recognized, a distinction that can shift material revenue between quarters in a way that has nothing to do with the underlying economics of the deal. Because heavily customized enterprise SaaS deals are common and lucrative, misjudging distinctness is one of the most frequently challenged revenue recognition areas in the sector.
Diagnostic questions
Can the customer benefit from the customization or integration service on its own or together with other readily available resources (capable of being distinct)? Is the service highly interrelated with, or does it significantly customize or modify, the subscribed software such that it fails the separately identifiable test? If combined into a single performance obligation, is the measure of progress reflecting the combined pattern of benefit, rather than the pattern of just one component?
Recognition
- List all promised goods and services in the bundled contract (subscription access, implementation, customization, integration, training).
- Apply the two-part distinctness test to the professional/customization services: (a) can the customer benefit from the service either on its own or together with other readily available resources (capable of being distinct)? (b) is the promise to transfer the service separately identifiable from other promises in the contract, i.e., not highly interdependent or highly interrelated with the subscription (distinct within the context of the contract)?
- Assess interdependency specifically: if the customization significantly modifies or customizes the subscription software itself, or if the subscription cannot function as intended for the customer without the customization being completed first, the services are likely not distinct and should be combined with the subscription into a single performance obligation.
- If combined, recognize revenue for the combined obligation over the period of transfer, typically matching the longer of the service delivery period or the subscription term, using an appropriate measure of progress.
- If the services are genuinely distinct (e.g., generic training that could be delivered by a third party, or configuration that does not alter the core platform's functionality), account for them as a separate performance obligation recognized as the service is delivered, typically at a point in time or over the (often short) service period.
- Document the interdependency analysis for each material bundled deal, since this determination is fact-specific and not a one-size-fits-all conclusion across all customer contracts.
Measurement
Where the services and subscription are combined into a single obligation, allocate the entire transaction price to that combined obligation (no separate SSP allocation needed since it is one unit of account) and recognize using a measure of progress reflecting the combined pattern of benefit, often straight-line over the longer of the service period or subscription term unless a different pattern is more representative. Where distinct, allocate the transaction price between the subscription and the service components based on their relative standalone selling prices, estimating SSP for the customization/implementation service using an adjusted market or expected cost-plus-margin approach if it is not sold separately at an observable price.
Presentation & disclosure
Disclose: the judgment applied in determining distinctness of bundled professional/customization services from the subscription for material contract types; the accounting policy for combined versus separate performance obligations in bundled arrangements; disaggregation of revenue by type (subscription versus services) where material, including how combined-obligation revenue is presented; the measure of progress used for combined obligations and the basis selected.
Common mistakes
- Defaulting to treating all professional services as distinct and recognizing them entirely on delivery, regardless of how customized or interdependent they are with the core platform
- failing to recognize that a customization required before the subscription can function at all is a strong indicator of interdependence and should be combined
- combining services and subscription into one obligation even when the service is genuinely generic and usable independently (over-conservative combination that delays revenue unnecessarily)
- using a single blanket policy across all deal types instead of assessing distinctness deal-by-deal for materially different arrangements
- failing to document the interdependency analysis, making the conclusion hard to defend on audit or in a due diligence review.
Simple example
A vendor charges SAR 200,000 for a heavily customized data pipeline integration required before the customer's subscribed analytics platform can ingest and process their data at all, alongside a 2-year SAR 480,000 subscription (SAR 20,000/month); because the integration is a prerequisite for the subscription to function as intended for this customer, the two are highly interdependent and combined into a single performance obligation recognized over the 2-year term. Journal entry when both amounts are invoiced at contract inception (total SAR 680,000, no performance yet delivered): Dr Contract asset / Accounts receivable 680,000 Cr Contract liability (deferred revenue) 680,000 Monthly recognition of the combined obligation over 24 months (SAR 680,000 / 24 = SAR 28,333 per month), beginning once the integration work starts contributing to the combined delivery pattern: Dr Contract liability (deferred revenue) 28,333 Cr Revenue - subscription and services (combined) 28,333 (Contrast: if the same integration work were generic and independently useful, the SAR 200,000 would instead be recognized as a separate obligation upon delivery, with only the SAR 480,000 subscription spread over 24 months.)
Professional judgment
The distinctness assessment for highly customized professional services bundled with a subscription is one of the most contested judgments in SaaS revenue recognition, precisely because 'distinct within the context of the contract' is a qualitative, facts-and-circumstances test rather than a bright-line rule, reasonable practitioners can disagree on how much customization is enough to create interdependence. Key indicators worth documenting deal-by-deal include: whether the vendor provides a significant integration service transforming the inputs into a combined output the customer could not achieve alone; whether the services significantly modify or customize the software; and whether the subscription and services are highly interdependent or interrelated (each significantly affects the other). This judgment should be made and documented for material contract types, not applied as a single blanket rule across an entire customer base with varying deal structures.
Source basis
IFRS 15 · Revenue from Contracts with Customers
Paragraph references
Verified against the official standard texts used in the IFRS Expert skill.
Related issues
Educational and navigation content only. Not professional advice. Does not reproduce official IFRS/IAS text. Consult the authoritative standards and qualified professionals; professional judgment may still be required.