What is Contract Liability?
IFRS 15.106 creates a contract liability when the customer's payment (or unconditional right to pay) precedes the entity's performance. The most familiar form is advance billing: a customer pays €600,000 in January for a service delivered evenly over the next 12 months, and the entity records a contract liability of €600,000 at inception. Each month, the entity satisfies a portion of the performance obligation and reclassifies €50,000 from the liability into revenue.
The accounting itself is mechanical. The judgment sits in two places. First, the entity must correctly identify when it satisfies the performance obligation (over time under IFRS 15.35 or at a point in time under IFRS 15.38). Second, the entity must allocate the transaction price to each obligation using relative stand-alone selling prices before determining how much of the contract liability converts to revenue in each period. ISA 315.12(f) directs the auditor to understand the entity's revenue policies, and contract liabilities are the line item where incorrect timing surfaces first.
Key Points
- A contract liability arises whenever a customer pays before the entity delivers the promised goods or services.
- The balance reverses into revenue only when (or as) the entity satisfies the corresponding performance obligation.
- IFRS 15.116(a) requires disclosure of opening and closing contract liability balances and the revenue recognised from opening balances during the period.
- Misstating the release pattern can shift revenue between periods by hundreds of thousands of euros on a single contract.
Worked example: Rossi Alimentari S.p.A.
Client: Italian food production company, FY2025, revenue €67M, IFRS reporter. Rossi enters a 24-month exclusive supply agreement with a German retail chain on 1 July 2025. The retailer pays €1,800,000 upfront on signing for two deliverables: (a) the exclusive supply right for 24 months and (b) quarterly quality certification reports over the contract term.
Step 1 — Identify performance obligations
The exclusive supply right is a stand-ready obligation satisfied over time. The quality certification reports are distinct (the retailer could obtain them from an independent lab) and are satisfied at a point in time upon delivery of each quarterly report.
Documentation note: record the performance obligation identification per IFRS 15.22. The supply right meets the IFRS 15.35(a) criterion (simultaneous receipt and consumption). The certification reports are distinct under IFRS 15.27 and satisfied at a point in time per IFRS 15.38.
Step 2 — Allocate the transaction price
Rossi estimates stand-alone selling prices of €1,500,000 for the 24-month supply right and €75,000 per quarterly report (€600,000 for eight reports). Relative allocation: supply right receives €1,285,714 (1,500,000 / 2,100,000 x 1,800,000); certification reports receive €514,286 (600,000 / 2,100,000 x 1,800,000).
Documentation note: record the stand-alone selling price basis per IFRS 15.79. Supply right priced using the adjusted market assessment approach. Certification reports priced using Rossi's observable rate card for third-party certifications.
Step 3 — Record the contract liability at inception
On 1 July 2025, Rossi records a contract liability of €1,800,000 (cash received, no performance obligations yet satisfied).
Documentation note: "Contract liability of €1,800,000 recorded at inception per IFRS 15.106. Full amount classified as current and non-current based on expected satisfaction timing: €749,999 current (amounts expected to be recognised within 12 months), €1,050,001 non-current.
Step 4 — Release to revenue over FY2025
By 31 December 2025, Rossi has performed six months of the supply right and delivered two quarterly certification reports. Revenue recognised: supply right €321,429 (1,285,714 x 6/24); certification reports €128,571 (514,286 x 2/8). Total revenue: €450,000. Remaining contract liability: €1,350,000.
Documentation note: "Contract liability roll-forward at 31 December 2025: opening €1,800,000 less revenue recognised €450,000 equals closing €1,350,000. Reconcile to IFRS 15.116(a) disclosure requirements.
Conclusion: the contract liability of €1,800,000 converts to revenue over 24 months at rates driven by two distinct release patterns, and the allocation is defensible because both stand-alone selling prices trace to observable pricing data.
Why it matters in practice
Teams often present contract liabilities as generic "deferred revenue" without performing the IFRS 15.106 analysis that distinguishes a contract liability (payment received before performance) from a refund liability or a contract asset. The label matters: IFRS 15.105 requires separate presentation of contract assets and contract liabilities on the balance sheet, and grouping them under a legacy caption obscures the disclosure requirements in IFRS 15.116.
The FRC's 2022/23 annual review of corporate reporting flagged insufficient disclosure of the revenue recognised in the current period from opening contract liability balances. IFRS 15.116(b) requires this as a specific line, yet entities frequently omit it or bury it in a general revenue reconciliation where it cannot be traced to the opening balance.
Contract liability vs contract asset
| Dimension | Contract liability | Contract asset |
|---|---|---|
| When it arises | Customer pays before the entity performs | Entity performs before the customer pays (and the right to payment is conditional) |
| Balance sheet classification | Liability (current or non-current based on expected satisfaction timing) | Asset (current or non-current based on expected billing timing) |
| Release trigger | Satisfaction of the related performance obligation | Billing or unconditional right to payment (at which point it reclassifies to a receivable) |
| Impairment testing | Not applicable (it is an obligation, not an asset) | Subject to expected credit loss assessment under IFRS 9, per IFRS 15.107 |
| Common industries | Subscription services, advance-billing construction, licensing with upfront fees | Long-term construction, milestone-based IT implementations |
The practical question on most engagements is whether the entity has correctly identified the tipping point: the moment when performance exceeds billing (contract asset) versus when billing exceeds performance (contract liability). On long-term contracts the position can switch direction mid-year.
Related terms
Frequently asked questions
What is the difference between a contract liability and deferred revenue?
Under IFRS 15, a contract liability replaces the legacy "deferred revenue" concept with a more precise definition. A contract liability exists only when the entity has received consideration (or it is due) and the related performance obligation remains unsatisfied (IFRS 15.106). Deferred revenue under previous standards did not require this explicit linkage to an identified performance obligation, so the two terms are not interchangeable despite frequent casual use.
Do I need to disclose the contract liability roll-forward in the notes?
Yes. IFRS 15.116(a) requires disclosure of opening and closing balances of contract liabilities. IFRS 15.116(b) adds a specific requirement to disclose how much revenue recognised in the current period relates to the opening contract liability balance. The auditor tests these disclosures under ISA 720 as part of the consistency review between the financial statements and other information.
Can a contract liability become a contract asset during the same contract?
Yes. If the entity satisfies performance obligations ahead of billing, the position flips from a contract liability to a contract asset. IFRS 15.107–108 require the entity to present the net contract position on a contract-by-contract basis, not by netting across contracts. The auditor verifies that netting has not been applied across separate contracts, as this would misstate both gross assets and gross liabilities.