What is Contract Asset?
IFRS 15.107 requires an entity to present a contract asset when it has performed by transferring goods or services to the customer but does not yet have an unconditional right to payment. The word "unconditional" does the heavy lifting. A receivable exists when nothing except the passage of time stands between the entity and cash collection. A contract asset exists when some other performance condition must still be satisfied before the right converts to a receivable.
Consider a two-phase consulting engagement where phase one is complete and invoicing depends on delivery of phase two. The entity has earned revenue on phase one (IFRS 15.35 or .38 criteria met), but the contractual payment milestone ties to phase two completion. That earned-but-not-yet-unconditional amount sits as a contract asset, not a receivable. The auditor testing this balance under ISA 540.13(a) evaluates whether the entity correctly assessed the conditionality of the right. IFRS 9.5.5.15 then requires the entity to measure an expected credit loss allowance on that contract asset from day one, using the simplified approach (lifetime ECL) unless the contract asset has a significant financing component.
The reclassification from contract asset to receivable is not merely presentational. It changes the population of balances subject to trade receivable ageing analysis and may shift the impairment methodology applied.
Key Points
- A contract asset differs from a receivable because the right to payment depends on a condition beyond the passage of time.
- Reclassification from contract asset to receivable occurs when the entity's right becomes unconditional.
- Contract assets are subject to the IFRS 9 expected credit loss impairment model from initial recognition.
- Misstating the boundary between contract assets and receivables distorts both the balance sheet and the impairment charge.
Worked example: Rossi Alimentari S.p.A.
Client: Italian food production company, FY2025, revenue €67M, IFRS reporter. Rossi enters a contract with a German retailer to supply two seasonal product lines: a summer range (delivered May 2025) and a winter range (delivered October 2025). Total contract price is €1,200,000. Payment of the full amount is due 30 days after delivery of the winter range.
Step 1 — Identify performance obligations
The summer range and the winter range are each distinct (the retailer can sell each independently, and Rossi's promises are separately identifiable under IFRS 15.27). Two performance obligations exist.
Documentation note: "Two performance obligations identified per IFRS 15.22. Summer range: distinct product line, separately identifiable. Winter range: distinct product line, separately identifiable. No significant integration or customisation between the two.
Step 2 — Allocate the transaction price
Rossi allocates based on relative stand-alone selling prices. The summer range has a stand-alone price of €500,000; the winter range, €700,000. Allocation: summer range €500,000 (500/1,200 of €1,200,000), winter range €700,000 (700/1,200 of €1,200,000).
Documentation note: "Transaction price of €1,200,000 allocated per IFRS 15.73. Stand-alone selling prices based on list prices for comparable seasonal orders. Summer: €500,000. Winter: €700,000.
Step 3 — Recognise and classify at 30 June 2025
Rossi delivered the summer range in May 2025. Revenue of €500,000 is recognised. The right to payment, however, is conditional on delivery of the winter range (the contract specifies a single payment milestone after both deliveries). Because the condition is not merely the passage of time, Rossi recognises a contract asset of €500,000 at 30 June 2025, not a receivable.
Documentation note: "Contract asset of €500,000 recognised per IFRS 15.107. Right to consideration is conditional on completion of the winter range delivery. Reclassification to receivable will occur upon delivery of the winter range in October 2025.
Step 4 — Measure the impairment allowance
IFRS 9.5.5.15 requires Rossi to recognise lifetime expected credit losses on the contract asset from initial recognition. Rossi applies its provision matrix: the German retailer is rated in the lowest-risk bucket (0.4% historical loss rate). The ECL allowance on the contract asset is €2,000.
Documentation note: "ECL on contract asset measured per IFRS 9.5.5.15 using simplified approach. Provision matrix applied: 0.4% loss rate on €500,000 = €2,000 allowance. Customer credit file reviewed, no SICR indicators.
Conclusion: the €500,000 contract asset (less the €2,000 ECL allowance) is defensible because the conditionality of the right to payment is traceable to the contractual milestone, and the impairment allowance follows the same provision matrix applied to trade receivables.
Why it matters in practice
Teams frequently classify conditional rights to payment as trade receivables, inflating the receivables balance and applying the wrong ageing bucket. IFRS 15.108 is explicit: a receivable exists only when the right to consideration is unconditional. Misclassification also distorts the entity's credit risk disclosures under IFRS 7.35H–35N, because contract assets carry a different risk profile from invoiced receivables.
The impairment requirement under IFRS 9.5.5.15 is often overlooked entirely for contract assets. The FRC's 2022/23 annual review of corporate reporting noted that some entities failed to disclose the methodology used for measuring expected credit losses on contract assets separately from trade receivables, despite the balances carrying different risk characteristics.
Contract asset vs [contract liability](/glossary/contract-liability)
| Dimension | Contract asset | Contract liability |
|---|---|---|
| When it arises | Entity has performed (transferred goods or services) before receiving payment | Customer has paid before the entity has performed |
| Balance sheet direction | Asset: entity is owed consideration | Liability: entity owes performance |
| Impairment | Subject to IFRS 9 ECL model from recognition | Not subject to impairment (it is a liability) |
| Reclassification trigger | Becomes a receivable when the right turns unconditional | Becomes revenue when the entity satisfies the performance obligation |
| Audit focus | Testing conditionality of the right to payment and the ECL allowance | Testing whether performance is genuinely outstanding and the liability is not understated |
The distinction matters on every engagement with milestone-based or advance-payment contracts. A contract asset signals the entity has earned revenue but cannot yet bill. A contract liability signals the entity has received cash but has not yet earned the revenue. Confusing the two misclassifies both the balance sheet and the revenue recognition timing.
Related terms
Frequently asked questions
How do I distinguish a contract asset from a receivable on an audit?
Test whether the entity's right to payment depends on anything other than the passage of time. If a milestone, approval, or further performance is required before the entity can invoice, the balance is a contract asset under IFRS 15.107. Review the contract payment terms and compare them to the performance obligations satisfied at the reporting date. ISA 500.9 requires the auditor to obtain sufficient evidence for each assertion, so confirm the conditionality by reading the payment clause.
Do I need a separate ECL model for contract assets?
IFRS 9.5.5.15 requires lifetime expected credit losses on contract assets that do not contain a significant financing component. Many entities use the same provision matrix as for trade receivables (IFRS 9.5.5.15 permits this), but the inputs should reflect the credit risk characteristics of the contract asset population. If the contract asset population has different debtor profiles or longer exposure periods than invoiced receivables, a separate calculation is appropriate under IFRS 9.B5.5.35.
When does a contract asset turn into a receivable?
Reclassification occurs at the point when the entity's right to consideration becomes unconditional per IFRS 15.108. In practice this is typically when the remaining performance condition is satisfied (for example, delivery of a second phase) or when the entity issues an invoice that is due solely on the passage of time. The entity records the reclassification as a transfer between line items on the balance sheet, with no income statement effect.