IFRS 15CoreSaaS / Software

Contract liabilities and deferred revenue

IFRS 15 · Revenue from Contracts with Customers

Applies to: All business models

In plain words

When customers pay before receiving service, such as a three-year contract paid upfront, the company owes them future service. Under IFRS 15 this is a contract liability, often called deferred revenue, reduced as revenue is recognised. There is also a presentation question: the part expected to become revenue within twelve months is current and the rest non-current, based on the delivery schedule, not billing.

Why it matters

Contract liabilities (deferred revenue) are typically the largest liability on a SaaS balance sheet and a headline metric lenders, investors and boards use as a proxy for future recurring revenue, so an incorrect current/non-current split or an unreliable roll-forward directly undermines confidence in reported liquidity and forward revenue visibility.

Diagnostic questions

Does the entity invoice customers in advance, and if so, is the contract liability recognized at the amount received that exceeds revenue recognized to date? Are there multi-year prepaid contracts, and is the roll-forward of the contract liability balance reconciled to actual revenue recognized each period? Is the current/non-current split based on the expected timing of revenue recognition within twelve months, rather than on the contractual billing or payment schedule?

Recognition

  1. Recognize a contract liability whenever consideration is received, or becomes unconditionally due, before the related performance is satisfied.
  2. At each reporting date, determine the current portion as the amount expected to be recognized as revenue within twelve months of the reporting date, and the remainder as non-current.
  3. Build the liability from the actual performance obligation satisfaction schedule (when access/service will be delivered), not simply from the invoice or billing schedule, since these can diverge (e.g., an invoice issued for a future renewal period before that period begins).
  4. Reduce the liability systematically as revenue is recognized, reconciling the roll-forward (opening balance, additions from new billings, revenue recognized, closing balance) each period.
  5. Reassess the current/non-current split at every reporting date for multi-year contracts as the remaining term shortens.

Measurement

Measure the contract liability at the amount of consideration received or receivable that exceeds revenue recognized to date for the related performance obligation. Split current versus non-current based on the expected timing of revenue recognition, not the contractual payment or invoicing schedule; for a straight-line multi-year contract this is typically the amount expected to be recognized in the next twelve months. Reconcile the liability roll-forward against the revenue recognized from the opening contract liability balance disclosure required under IFRS 15.

Presentation & disclosure

Disclose: (1) contract liability balances split between current and non-current; (2) revenue recognized in the period that was included in the opening contract liability balance; (3) a roll-forward of contract liabilities (opening, additions, revenue recognized, closing); (4) the aggregate transaction price allocated to remaining performance obligations and expected timing of recognition; (5) accounting policy for determining the current/non-current split.

Common mistakes

  • Labeling the balance '
  • deferred revenue'
  • but calculating it purely from the billing schedule instead of the actual performance satisfaction pattern
  • failing to split multi-year prepaid contracts between current and non-current, overstating current liabilities or misstating working capital ratios
  • not reconciling the contract liability roll-forward to revenue recognized, leaving unexplained differences
  • treating a contractually non-refundable but unearned amount as recognizable revenue simply because it cannot be repaid
  • missing contract liabilities that arise from unconditional prepayment obligations even when cash has not yet been physically received.

Simple example

A customer signs and pays a 3-year prepaid contract of SAR 360,000 on 1 January (SAR 10,000/month recognized straight-line over 36 months).
Journal entry at inception:
Dr Cash 360,000
Cr Contract liability (deferred revenue) 360,000

End of January, one month recognized:
Dr Contract liability 10,000
Cr Revenue - subscription 10,000

At 31 January, the remaining SAR 350,000 balance is split: SAR 120,000 expected to be recognized in the next twelve months (current contract liability) and SAR 230,000 expected beyond twelve months (non-current contract liability), reflecting the remaining 35-month schedule.

Professional judgment

This area is largely mechanical and process-driven rather than judgmental, but genuine grey areas arise for non-standard billing arrangements: a milestone-based enterprise contract with an uneven delivery pattern requires judgment on how much of the liability relates to obligations expected to be satisfied within twelve months versus later, since it is not simply a function of elapsed contract time. System configuration and sub-ledger reconciliation discipline (billing system versus revenue system versus GL) is often the real source of error, not conceptual misunderstanding, so control design matters as much as accounting policy.

Source basis

IFRS 15 · Revenue from Contracts with Customers

Paragraph references

IFRS 15.105–109IFRS 15.116–118

Verified against the official standard texts used in the IFRS Expert skill.

IFRS 15 Revenue from Contracts with Customers
Issued: 28 May 2014 · Effective: 1 January 2018

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.