Have You Ever Faced These Challenges?
- You prepared the revenue recognition note by working through the disclosure checklist mechanically, only to be told by your auditors that the note does not adequately explain the significant judgements your entity made
- You reviewed a peer company’s IFRS 15 disclosures and could not determine whether your own disclosures were at a comparable level of detail
- You are unsure of the difference between a contract asset and a contract liability, and whether the balances on your balance sheet are correctly classified and labelled
What You Will Learn From This Article
- The five categories of IFRS 15 disclosure and what each requires in practice
- The definitions of contract asset, contract liability, and refund liability — and how to distinguish between them on the balance sheet
- The minimum level of detail expected for judgement and estimate disclosures, based on the objective of the standard
Who This Article Is For
- Finance professionals responsible for preparing or reviewing IFRS 15 disclosures in annual reports or financial statements
- Those preparing IFRS 15 disclosures for the first time
- Practitioners who have received audit comments on the sufficiency of their revenue recognition notes
The Disclosure Objective: Substance Over Checklist
The overarching objective of the IFRS 15 disclosure requirements is to enable users of financial statements to understand the nature, amount, timing, and uncertainty of revenue and cash flows arising from contracts with customers (IFRS 15.110).
This objective-based framing has an important practical implication: satisfying the disclosure objective cannot be achieved by mechanically populating a checklist. Two entities that include exactly the same line items in their revenue notes may produce disclosures of very different quality — one that genuinely helps a reader understand the entity’s revenue streams and judgements, and one that provides boilerplate language that conveys little information.
Auditors and regulators have increasingly focused on the quality, rather than just the presence, of IFRS 15 disclosures. The question to ask when reviewing a revenue note is not “have we included everything on the list?” but “would a reader of these financial statements understand how and when we recognise revenue, and what uncertainties are involved?”
The Five Categories of Disclosure
IFRS 15 organises its disclosure requirements into five categories. Each addresses a different dimension of the entity’s revenue recognition.
| Category | Standard reference | Core question answered |
|---|---|---|
| Disaggregation of revenue | IFRS 15.114–115 | What types of revenue does the entity earn, and how do they differ? |
| Contract balances | IFRS 15.116–118 | What amounts are on the balance sheet relating to customer contracts? |
| Remaining performance obligations | IFRS 15.120–122 | How much revenue remains to be recognised on existing contracts? |
| Significant judgements | IFRS 15.123–126 | What were the most important judgements in determining when and how much revenue to recognise? |
| Significant estimates | IFRS 15.126–128 | What estimates most significantly affect the amount and timing of revenue? |
Category 1: Disaggregation of Revenue
The Objective
Disaggregated revenue disclosure is intended to show how different types of revenue relate to the entity’s financial performance — helping users understand what drives revenue growth, margin differences, and risk concentrations across the entity’s customer base (IFRS 15.114).
Choosing the Disaggregation Axes
IFRS 15 does not prescribe specific disaggregation categories. The entity selects the disaggregation approach that best achieves the disclosure objective in light of its specific facts and circumstances. IFRS 15.B89 suggests the following as potentially useful disaggregation axes:
- Type of good or service (product revenue vs service revenue)
- Geography (domestic vs international; regional breakdown)
- Market or customer type (consumer vs enterprise; industry sector)
- Contract type (fixed-price vs time-and-materials; long-term vs spot)
- Timing of transfer (point-in-time vs over-time)
- Sales channel (direct vs distributor vs online)
The appropriate level of granularity depends on how different the revenue streams are in terms of risk profile and growth drivers. An entity with three materially different business lines selling to distinctly different customer types in different geographies will need more granular disaggregation than an entity with a homogeneous product sold through a single channel.
Integration with Segment Reporting
IFRS 15.115 permits an entity to use the disaggregated revenue information already presented in its segment disclosures under IFRS 8, provided that information satisfies the disaggregation objective. In practice, entities typically cross-reference between the segment note and the revenue note, supplementing the segment data with additional disaggregation where the segment presentation does not fully address the IFRS 15 disclosure objective.
Minimum disclosure example — manufacturing entity:
Disaggregation of revenue
Japan International Total
¥m ¥m ¥m
Product revenue x,xxx x,xxx x,xxx
Service revenue x,xxx x,xxx x,xxx
Total revenue x,xxx x,xxx x,xxx
Of which:
Recognised at a point in time x,xxx
Recognised over time x,xxx
Total x,xxxCategory 2: Contract Balances
Defining the Three Balance Sheet Items
Understanding the distinction between contract assets, contract liabilities, and refund liabilities is a prerequisite for correct balance sheet presentation and disclosure.
Contract asset
A contract asset arises where the entity has satisfied a performance obligation — that is, it has transferred control of a good or service to the customer — but its right to receive the corresponding consideration is conditional on something other than the passage of time (IFRS 15 Appendix A).
The most common condition is the satisfaction of another performance obligation in the same contract. For example, where an entity transfers a software licence (Performance Obligation 1) but the contractual payment is only due after the implementation services are also complete (Performance Obligation 2), the entity has a contract asset for the licence consideration until the implementation is finished.
How contract assets differ from trade receivables: A trade receivable represents an unconditional right to receive consideration — the only remaining condition is the passage of time (i.e., the invoice due date). A contract asset has not yet become unconditional. The distinction matters for impairment purposes: trade receivables are subject to the IFRS 9 expected credit loss model from initial recognition; contract assets are also subject to IFRS 9 impairment, but the disclosure and presentation requirements differ.
Contract liability
A contract liability arises where the entity has received consideration from the customer — or has an unconditional right to receive it — but has not yet satisfied the corresponding performance obligation (IFRS 15 Appendix A).
The most familiar example is a prepayment or advance received from a customer. Annual software subscriptions billed at the start of the subscription period, maintenance contracts paid upfront, and deposits on long-term supply arrangements all give rise to contract liabilities at the billing date, which are released to revenue as the performance obligation is satisfied over time.
Refund liability
A refund liability represents the entity’s obligation to return consideration already received — or to forgo collection of consideration already billed — because it expects some or all of the consideration to be refunded to the customer. The most common source is a right of return: where the entity has recognised revenue for goods transferred to the customer but expects a portion to be returned, the consideration associated with expected returns is presented as a refund liability rather than as revenue.
The critical distinction between contract liabilities and refund liabilities: A contract liability represents an obligation to transfer a good or service. A refund liability represents an obligation to return cash. Where both exist, they must be presented separately on the balance sheet — netting is not permitted.
Required Disclosures for Contract Balances
IFRS 15.116 requires disclosure of the opening and closing balances of:
- Contract assets
- Contract liabilities (separately for current and non-current where material)
- Trade receivables arising from contracts with customers (if not separately presented on the face of the balance sheet)
IFRS 15.117 additionally requires:
- The amount of revenue recognised in the period that was included in the opening contract liability balance
- The amount of revenue recognised in the period from performance obligations satisfied (or partially satisfied) in previous periods — for example, from changes in estimates of variable consideration
IFRS 15.118 requires qualitative and quantitative explanation of significant changes in contract asset and contract liability balances, including:
- Changes from contract modifications
- Changes from business combinations
- Cumulative catch-up adjustments from changes in estimates
- Impairment of contract assets
Disclosure example:
Contract balances
Opening balance Closing balance
¥m ¥m
Contract assets x,xxx x,xxx
Contract liabilities
— current x,xxx x,xxx
— non-current x,xxx x,xxx
Refund liabilities x,xxx x,xxx
Revenue recognised in the period that was included in the
opening contract liability balance: ¥x,xxx million.
The decrease in contract liabilities during the period primarily
reflects the recognition of revenue on annual maintenance contracts
billed at the start of the contract year, partially offset by new
contracts entered into during the period.Category 3: Remaining Performance Obligations
What Must Be Disclosed
IFRS 15.120 requires disclosure of:
- The aggregate amount of the transaction price allocated to performance obligations that are unsatisfied or partially unsatisfied at the end of the reporting period, and
- An explanation of when the entity expects to recognise that amount as revenue — either as a quantitative time band or as a qualitative description
This disclosure provides users with a forward-looking view of contracted but unrecognised revenue — essentially a revenue backlog.
The Practical Expedients
IFRS 15.121 permits an entity to omit this disclosure for:
Performance obligations with an original expected duration of one year or less. This expedient is widely applied and eliminates the disclosure requirement for the majority of commercial transactions in manufacturing, retail, and distribution.
Performance obligations where revenue is recognised in the amount to which the entity has a right to invoice. This expedient applies to service contracts billed on a time-and-materials basis, where the entity recognises revenue equal to the amount invoiced in each period.
Variable consideration allocated entirely to a wholly unsatisfied performance obligation, where the variable consideration is in the form of a sales-based or usage-based royalty.
For entities that apply the one-year expedient to all or most of their contracts, the disclosure may be limited to a statement that the expedient has been applied, with a qualitative description of the nature of the excluded performance obligations.
For entities with significant long-term contracts — construction, infrastructure, multi-year SaaS arrangements, or defence contracts — the disclosure requires quantitative time banding.
Disclosure example — entity with significant long-term contracts:
Remaining performance obligations
The aggregate transaction price allocated to unsatisfied performance
obligations at the end of the reporting period is ¥x,xxx million.
The Group expects to recognise this amount as revenue as follows:
Within 1 year ¥x,xxx million
Between 1 and 3 years ¥x,xxx million
More than 3 years ¥x,xxx million
Total ¥x,xxx million
The above amounts exclude contracts with an original expected
duration of one year or less, in accordance with the practical
expedient in IFRS 15.121(a).Category 4: Significant Judgements
IFRS 15.123 requires disclosure of the judgements — and changes in judgements — made in applying IFRS 15 that significantly affect the determination of the amount and timing of revenue.
Judgements in Determining the Timing of Satisfaction
The most important timing judgement is the over-time versus point-in-time determination for each material performance obligation. The disclosure should explain, in plain language, why a given performance obligation is recognised over time or at a point in time — not merely assert that it is.
Where Criterion 3 (no alternative use plus enforceable right to payment) is the basis for over-time recognition, the disclosure should explain:
- Why the asset has no alternative use — whether because of physical or contractual constraints
- What the enforceable right to payment consists of and how it is established under the applicable contract terms and jurisdiction
Example disclosure — bespoke manufacturing:
Revenue recognition — bespoke manufacturing contracts
Revenue from contracts for the manufacture of customer-specified
components is recognised over time. The components are manufactured
to specifications that are unique to each customer and cannot be
redirected to other customers without significant economic loss.
Accordingly, the components have no alternative use to the Group.
In addition, the Group's standard contract terms provide that in
the event of termination by the customer for convenience, the
customer is required to reimburse the Group for all costs incurred
to date plus a margin of x%, representing a reasonable profit on
performance completed to date. The Group has confirmed with legal
counsel that this right is enforceable under the laws governing
the relevant contracts.
Progress is measured using the cost-to-cost method. Revenue is
recognised based on costs incurred to date as a proportion of
total estimated contract costs, excluding the cost of materials
that have been purchased but not yet incorporated into production.Judgements in Identifying Performance Obligations
Where the identification of performance obligations involves significant judgement — particularly in bundled arrangements — the disclosure should explain the basis on which the entity concluded that specific goods or services are (or are not) distinct.
Category 5: Significant Estimates
IFRS 15.126 requires disclosure of information about the methods, inputs, and assumptions used to:
- Determine the transaction price (particularly for variable consideration)
- Assess whether variable consideration is constrained
- Allocate the transaction price (particularly where SSPs are estimated rather than observed)
- Measure progress toward complete satisfaction of over-time obligations
Variable Consideration Disclosures
The disclosure should address, at minimum:
- The types of variable consideration present in the entity’s contracts
- The estimation method applied (expected value or most likely amount)
- The basis for concluding that the constraint has been appropriately applied
- The balance of refund liabilities and the assumptions underlying the estimate of expected returns
Example disclosure — volume rebates:
Variable consideration — volume rebates
Certain contracts with distributors include retrospective volume
rebates payable if the customer's annual purchases exceed specified
thresholds. The Group estimates rebate obligations using the
expected value method, based on historical purchase patterns and
current period purchase data. Rebate obligations are recognised
as a reduction to revenue and a corresponding refund liability
as sales are made. The refund liability is remeasured at each
reporting date. At [date], the refund liability in respect of
volume rebates was ¥x,xxx million.
The Group has assessed that it is highly probable that a
significant reversal of cumulative revenue will not occur in
respect of the amounts included in the transaction price, based
on the relatively low variability in customer purchase volumes
and the Group's extensive experience with similar contracts.Progress Measurement Disclosures
Where an input method is used to measure progress on over-time obligations, the disclosure should explain:
- The basis for selecting the input method over available output methods
- The specific input measure used (cost-to-cost, labour hours, etc.)
- How costs that do not reflect progress are identified and excluded
- The sensitivity of revenue to changes in total estimated costs
A Self-Assessment Checklist for IFRS 15 Disclosures
Before finalising the revenue note, the following questions should be addressed:
Disaggregation
- Does the disaggregation reflect the dimensions along which revenue streams differ in risk, growth rate, and margin?
- Is the disaggregation consistent with how management discusses revenue performance internally?
Contract balances
- Are contract assets and trade receivables correctly distinguished and separately presented?
- Are contract liabilities and refund liabilities separately presented?
- Is the revenue recognised from opening contract liabilities disclosed?
- Are significant movements in contract balances explained?
Remaining performance obligations
- Are long-term contracts quantitatively disclosed with time banding?
- Are practical expedients applied and disclosed where appropriate?
Significant judgements
- Is the over-time versus point-in-time conclusion explained, not merely asserted?
- Where Criterion 3 is relied upon, are both conditions (no alternative use and enforceable right to payment) specifically addressed?
- Are significant performance obligation identification judgements disclosed?
Significant estimates
- Are variable consideration types, estimation methods, and constraint assessments disclosed?
- Is the progress measurement approach explained, including the exclusion of costs that do not represent progress?
Comparison with Japanese GAAP
| Area | IFRS 15 | Japanese GAAP (ASBJ No. 29) |
|---|---|---|
| Disaggregation of revenue | Required; entity determines appropriate axes | Same |
| Contract balances | Opening and closing balances required | Same, with some simplifications for immaterial items |
| Remaining performance obligations | Quantitative disclosure required for long-term contracts | Same, with practical expedients |
| Significant judgements | Detailed qualitative disclosure required | Same in principle; somewhat less prescriptive in practice |
| Significant estimates | Detailed disclosure of methods and inputs required | Same |
The frameworks are substantially aligned. In practice, IFRS reporters tend to face higher scrutiny from auditors and regulators on the quality of judgement disclosures — particularly regarding over-time recognition criteria and variable consideration constraint assessments.
Summary
The key takeaways from the IFRS 15 disclosure requirements are as follows:
- The disclosure objective is to enable users to understand the nature, amount, timing, and uncertainty of revenue — checklist compliance is necessary but not sufficient
- Contract assets represent earned but conditionally receivable consideration; contract liabilities represent received but unearned consideration; refund liabilities represent expected cash returns — the three must be distinguished and separately presented
- Remaining performance obligation disclosures are required for long-term contracts; the one-year practical expedient eliminates the requirement for most short-duration transactions
- Judgement disclosures must explain the reasoning behind significant conclusions — not merely state the conclusion reached
- Variable consideration disclosures must address the estimation method, the basis for the constraint assessment, and the refund liability balance
- Progress measurement disclosures must explain how costs that do not represent progress are identified and excluded from input-method calculations
Comments