In plain words
A customer pays a software company upfront for a year of access to a cloud platform. The question under IFRS 15 is when that revenue is earned. Because the customer receives access continuously, revenue is recognised over time, usually evenly across the term from the date access starts. Cash received in advance is first recorded as a contract liability (deferred revenue) and released to revenue month by month.
Why it matters
Getting the over-time pattern right for subscription access changes when SAR of revenue lands in each period, not just its total: recognizing an annual invoice on billing overstates current-period revenue and profit, misstates gross margin trends, and misleads on the size of the deferred revenue balance that investors and lenders use as a forward indicator of recurring revenue. Because most SaaS contracts renew automatically and bill in advance, this is a high-volume, recurring risk rather than a one-off judgment.
Diagnostic questions
Does the customer obtain continuous access to a live, hosted platform (over-time access) rather than a copy of software delivered at a point in time? What date does access actually go live, and does revenue start there rather than at contract signing or invoicing? Is straight-line recognition still a faithful depiction of benefit transfer, or does usage vary enough that an output method would better reflect it? For annual invoices paid upfront, is the unrecognized portion correctly carried as a contract liability rather than released on billing?
Recognition
- Identify the performance obligation: confirm the customer obtains continuous access to a functioning, hosted platform rather than a right to use a specific version of software at a point in time.
- Determine the start date of access (go-live, not contract signing or invoicing) as the point recognition begins.
- Select a measure of progress: straight-line over the contract term is the default for undifferentiated access; switch to an output method (e.g., usage) only if usage varies materially and reflects the pattern of benefit.
- Recognize revenue each period as access is provided, regardless of when the customer is billed or pays.
- Record any amount billed or collected in advance of performance as a contract liability, releasing it to revenue only as the service is delivered.
- Reassess the measure of progress if the nature of what is delivered changes materially (e.g., a pure access plan adds a heavily usage-driven module).
Measurement
Measure revenue per period as the transaction price divided evenly across the contract term (straight-line) unless a usage-based output method better depicts the transfer of benefit; the measurement base is the stand-alone transaction price for the access obligation, not the gross invoice amount if other elements are bundled. Subsequently, re-measure only for contract modifications, not for changes in estimated usage under a straight-line model; reassess the appropriateness of straight-line versus usage-based measurement whenever the delivery pattern changes.
Presentation & disclosure
Disclose: (1) accounting policy for recognizing subscription revenue over time and the measure of progress used; (2) disaggregation of revenue by type (subscription vs services) and by timing (over time vs point in time); (3) opening and closing contract liability balances with revenue recognized from the opening balance; (4) aggregate transaction price allocated to remaining performance obligations and when it is expected to be recognized; (5) judgment applied for hybrid access/use arrangements.
Common mistakes
- Recognizing the full annual invoice as revenue when billed instead of over the service period
- treating a term license that behaves like an on-premise sale as if it were SaaS access recognized over time
- using contractual billing dates rather than the actual go-live date as the start of recognition
- failing to reduce the contract liability consistently when a customer receives free extension months as a retention concession
- ignoring a shift to material usage-based components that should change the measure of progress from straight-line to an output method.
Simple example
On 1 January, a customer signs a 12-month SaaS access plan for SAR 120,000, paid in full upfront on 5 January when access is activated the same day. Journal entry on 5 January (cash received, access not yet delivered beyond day one): Dr Cash 120,000 Cr Contract liability (deferred revenue) 120,000 At the end of January, one month of access (1/12) has been delivered: Dr Contract liability (deferred revenue) 10,000 Cr Revenue - subscription 10,000 At 31 January the contract liability balance is SAR 110,000 (SAR 120,000 less SAR 10,000 recognized), correctly reflecting 11 months of undelivered access rather than SAR 120,000 of revenue being taken upfront.
Professional judgment
The genuine grey area is the right-to-access versus right-to-use distinction for hybrid offerings: a term license bundled with hosting, or an on-premise-style deployment delivered through the cloud, can look like SaaS commercially while behaving like a point-in-time license legally, and the conclusion depends on whether the customer's rights and the vendor's obligations change continuously through the term. A second judgment is selecting the measure of progress when usage is present but not dominant, defaulting to straight-line is reasonable only if usage does not vary the pattern of benefit the customer receives; if a minority of customers consume vastly more, an output method may better depict transfer of control and the choice should be documented and applied consistently.
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.