IFRS 15CoreSaaS / Software

Revenue disaggregation and remaining performance obligation disclosures

IFRS 15 · Revenue from Contracts with Customers

Applies to: All business models

In plain words

Investors want to know what kinds of revenue a SaaS company earns and how much contracted revenue is still to come. IFRS 15 requires disaggregating revenue into categories showing how economic factors affect it, such as subscription, usage and services. It also requires disclosing the transaction price allocated to remaining performance obligations, split by expected timing and based on allocated prices, not billings.

Why it matters

IFRS 15 requires disaggregating revenue into categories that depict how economic factors affect the nature, amount, timing, and uncertainty of revenue and cash flows, plus disclosure of the aggregate transaction price allocated to remaining performance obligations; SaaS companies frequently under-scope both, leaving investors unable to distinguish durable recurring subscription revenue from lumpy services or usage revenue, or to gauge forward revenue visibility from the backlog.

Diagnostic questions

What categories of disaggregation (subscription plan, usage-based, professional services, geography, contract length) best depict how economic factors affect this entity's revenue? Is the disclosed remaining performance obligation balance reconciled to deferred revenue and unbilled backlog, so the figures are internally consistent? Are the practical expedients for contracts of one year or less applied consistently and disclosed where relevant performance obligations are excluded?

Recognition

  1. Identify the economic factors that most affect how the entity's revenue streams behave (e.g., subscription versus professional services, usage-based versus fixed-fee, geography, contract duration, customer segment) as the starting point for choosing disaggregation categories.
  2. Select categories that align with information the entity already reviews internally (e.g., in board reporting or investor materials) as a strong indicator of what is decision-useful externally, while avoiding a mechanical copy of internal segments if they do not reflect revenue-relevant economic factors.
  3. At each reporting date, quantify the aggregate transaction price allocated to performance obligations that are unsatisfied (or partially satisfied) as of that date, drawing from the same data used to build the contract liability roll-forward.
  4. Determine the expected timing of recognition for that remaining transaction price, typically split between within twelve months and beyond twelve months, or in more granular time bands where useful.
  5. Apply available practical expedients correctly (e.g., excluding remaining performance obligations that are part of a contract with an original expected duration of one year or less, or where revenue is recognized based on the right-to-invoice practical expedient) and disclose that an expedient was used.
  6. Reconcile disaggregated revenue categories and the remaining performance obligation figure back to total contract balances and total reported revenue to ensure consistency across the disclosures.

Measurement

Quantify the aggregate transaction price allocated to unsatisfied or partially unsatisfied performance obligations at period end using the same allocated transaction prices applied in revenue recognition, not gross contract value or billings. Split this amount by expected timing of recognition, typically within twelve months and thereafter, based on the actual delivery schedule of each obligation rather than an assumed straight-line profile if delivery is genuinely uneven (e.g., ramped or milestone contracts). Reconcile the disaggregated revenue figures to the total revenue line in the statement of profit or loss to confirm completeness.

Presentation & disclosure

Disclose: revenue disaggregated into categories reflecting the most relevant economic factors (e.g., subscription tier, geography, timing of transfer, usage-based versus fixed-fee); the aggregate transaction price allocated to remaining performance obligations at period end; the expected timing of recognizing that remaining amount, in time bands; any practical expedients applied (e.g., one-year-or-less contracts, right-to-invoice) and confirmation that excluded amounts are appropriately scoped out; a reconciliation of disaggregated categories to total revenue and of remaining performance obligations to contract balances.

Common mistakes

  • Providing only a single total revenue line with no disaggregation, or disaggregating along an internal management dimension (e.g., sales region only) that does not reflect the economic factors most relevant to revenue recognition patterns
  • omitting the remaining performance obligation disclosure entirely
  • including only billed or invoiced backlog in the remaining performance obligation figure rather than the full unsatisfied allocated transaction price, including amounts not yet invoiced
  • applying the practical expedients (one-year contracts, right-to-invoice) inconsistently or without disclosing that they were used
  • failing to reconcile disaggregated revenue back to the total revenue reported in the primary statements.

Simple example

A SaaS group discloses revenue disaggregated by type: subscription SAR 180,000,000, usage-based SAR 25,000,000, and professional services SAR 15,000,000 (total SAR 220,000,000, reconciling to the statement of profit or loss). Separately, it discloses SAR 42,000,000 of remaining performance obligations at year end, of which SAR 30,000,000 is expected to be recognized as revenue within 12 months and SAR 12,000,000 thereafter, excluding contracts with an original term of one year or less under the practical expedient.
No journal entry is required for this disclosure itself, since it is a note-level disaggregation and reconciliation exercise; the underlying figures are drawn directly from the revenue recognized in the general ledger (Dr Contract asset/receivable, Cr Revenue entries recorded throughout the year) and the contract liability roll-forward (Dr Contract liability, Cr Revenue as performance obligations are satisfied), reconciled to produce the disclosure tables.

Professional judgment

Selecting the most decision-useful disaggregation categories requires judgment about which economic factors are most relevant to users of the financial statements, and the right answer is entity-specific rather than a fixed template, a usage-heavy platform may need to disaggregate by consumption pattern, while an enterprise-contract-heavy business may need duration or renewal-based categories; the disclosure should evolve as the business model does rather than remaining static once set. A further judgment concerns scoping the remaining performance obligation figure for contracts with variable consideration or optional renewals, where the entity must decide how to handle constrained variable amounts and unexercised options consistently with how the transaction price was determined for recognition purposes.

Source basis

IFRS 15 · Revenue from Contracts with Customers

Paragraph references

IFRS 15.114IFRS 15.116–118IFRS 15.120IFRS 15.121

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.