In plain words
Clients often hold back part of each payment (retention) and sometimes pay advances upfront. The question is how to classify these balances. A retention becomes a receivable once certification makes the right unconditional, even if cash comes later; before that it is a contract asset. Advances received are a contract liability released as work is done. Both receivables and contract assets need a credit loss allowance.
Why it matters
Retentions, advances and contract balances are frequently misclassified, treating a certified retention as still part of a contract asset (subject to progress remeasurement) instead of an unconditional receivable, or netting advances against gross contract assets, which misstates working capital, understates ECL exposure on amounts that are actually past-due-eligible receivables, and misleads readers of the balance sheet about the entity's true liquidity and credit risk profile on government and mega-project counterparties.
Diagnostic questions
Has the customer's certification or approval already made the right to a retained amount unconditional, so it should be reclassified from a contract asset to a receivable even though cash settlement is delayed? Is the remaining retention period (e.g. the defects liability period) tracked so an expected credit loss allowance can be applied? Are mobilization advances tracked separately and offset against future certificates rather than netted directly against gross contract assets? Is the ECL model applied to retention receivables using the counterparty's actual credit risk rather than an assumed zero-loss rate?
Recognition
- Distinguish a contract asset (conditional right to consideration, dependent on something other than passage of time, e.g. further work or certification) from a receivable (unconditional right, only the passage of time remains).
- Reclassify a contract asset to a receivable at the point certification/approval makes the right to the retained amount unconditional, even though cash settlement is deferred.
- Recognize advances/mobilization payments received as a contract liability on receipt, and release them systematically against revenue as the related performance obligation is satisfied (commonly pro-rata with progress or per contractual deduction schedule).
- Track retentions separately from routine trade receivables given their longer settlement horizon and distinct release triggers (substantial completion, defects liability period expiry).
- Present contract assets, contract liabilities and receivables separately on the face of or in the notes to the balance sheet; do not net across unrelated contracts.
Measurement
Apply the IFRS 9 expected credit loss model to retention receivables and contract assets, considering the specific credit risk of the government or private employer and historical release/delay patterns rather than a blanket zero-loss assumption; contract assets follow the simplified approach (lifetime ECL from initial recognition) consistent with related trade receivables. Measure the contract liability for advances at the amount received, releasing it against revenue as work is performed; where the advance carries a significant financing component (see the related financing-component consideration), separate imputed interest from the revenue release.
Presentation & disclosure
Disclose: (1) separate carrying amounts of contract assets, contract liabilities (advances) and trade/retention receivables, not a single net 'contract balances' figure; (2) ageing and expected release timing of retentions; (3) the ECL provision matrix or methodology applied to retentions and contract assets, including loss rates by counterparty type; (4) significant changes in contract assets/liabilities during the period and the reasons; (5) amount of revenue recognized from advances (contract liabilities) held at the start of the period.
Common mistakes
- Leaving certified retentions classified as contract assets after the right to payment has become unconditional, so they are not properly assessed as receivables for ECL and ageing purposes
- netting advances/mobilization payments against gross contract assets on the balance sheet rather than presenting the liability separately
- applying a zero or negligible ECL rate to government retentions purely because '
- government does not default,'
- ignoring payment delay risk which is itself a form of credit/time-value loss
- failing to release the contract liability for advances in line with actual progress, leaving stale balances on the books.
Simple example
A contractor completes a project with SAR 4,000,000 of retention certified by the engineer: 50% (SAR 2,000,000) is released immediately at substantial completion, and 50% (SAR 2,000,000) is deferred for a 12-month defects liability period. Because certification makes the entire right unconditional (only time must pass for the deferred half), both halves are receivables, not contract assets. Journal entry on certification: Dr Retention receivable - current 2,000,000 Dr Retention receivable - non-current 2,000,000 Cr Contract asset 4,000,000 An ECL allowance of 1% is assessed against the deferred retention given the employer's credit standing: Dr ECL allowance expense (P&L) 20,000 Cr Loss allowance - retention receivable 20,000 On release of the deferred half after the defects liability period: Dr Cash 2,000,000 Cr Retention receivable - non-current 2,000,000
Professional judgment
The precise point at which a retention right becomes 'unconditional other than the passage of time' can be genuinely unclear where certification is provisional, subject to a final account reconciliation, or where the employer retains a contractual right to offset defect-rectification costs against the retention, in those cases part of the balance may still be a contract asset rather than a full receivable. Assessing ECL on government and mega-project counterparties requires distinguishing structural payment-cycle delay (a feature of the sector, not necessarily default risk) from genuine credit deterioration, and building a forward-looking overlay for macro conditions (oil price, budget cycles) rather than relying solely on historical loss rates, which is inherently judgmental for counterparties that have never actually defaulted.
Source basis
IFRS 15 / IFRS 9 · Revenue from Contracts with Customers / Financial Instruments
Paragraph references
Verified against the official standard texts used in the IFRS Expert skill.
Related issues
- IFRS 15Over-time revenue recognition and progress measurement
- IFRS 15Variations, claims and disputes in contract price
- IFRS 15Mobilization and contract fulfilment costs
- IFRS 15Significant financing component in contract consideration
- IFRS 15Principal versus agent in subcontracted scope
- IFRS 15Combining and segmenting construction contracts
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.