IAS 37 / IFRS 15ConditionalContracting & Infrastructure

Back-to-back subcontractor claims and liability pass-through

IAS 37 / IFRS 15 · Provisions, Contingent Liabilities and Contingent Assets / Revenue from Contracts with Customers

Applies to: All business models

Why it matters

Main contractors frequently assume back-to-back subcontracts pass employer claims, delay damages or defect costs through symmetrically, but the contractor's own liability to the employer and its recovery right against the subcontractor are governed by different recognition thresholds and different counterparties' financial capacity, recognizing a full offsetting recovery asset without independently assessing the subcontractor's ability and willingness to pay overstates net assets and understates real economic exposure.

Diagnostic questions

Has your entity's own liability to the employer, such as liquidated damages or defect rectification cost, actually crystallized as probable, independently of whether a subcontractor pass-through exists? Does the back-to-back subcontract clause genuinely transfer that specific liability, or does local law or the subcontract's own limitation-of-liability cap reduce or exclude the pass-through? Is the subcontractor financially capable of paying, or are there solvency, performance, or dispute concerns that impair the recoverability of the pass-through asset? Is the recovery asset measured net of any recovery constraint rather than assumed to mirror the main liability in full?

Recognition

  1. Assess the entity's own liability to the employer independently: recognize a provision under IAS 37 (for a claim/damages liability) or reflect a reduction in transaction price under IFRS 15 (for liquidated damages as variable consideration), based on the probability and reliable estimation criteria appropriate to that liability, regardless of whether a subcontractor pass-through exists.
  2. Separately and independently assess the recovery from the subcontractor: recognize a recovery asset only when recovery is virtually certain (the higher threshol​d applicable to recognizing a reimbursement asset), not merely because the subcontract terms are legally back-to-back.
  3. Do not net the liability and the recovery asset in the income statement or present them as automatically symmetrical; present the reimbursement separately as an asset only up to the amount of the related liability.
  4. Assess the subcontractor's actual financial capacity, dispute posture, and any caps or exclusions in the subcontract limiting its liability, which frequently mean the pass-through is not one-for-one.
  5. Reassess both the employer-facing liability and the subcontractor recovery independently at each reporting date as facts develop, since they can move in different directions or at different speeds.

Measurement

Measure the subcontractor recovery asset net of any recovery constraint due to a subcontractor liability cap, financial distress, insolvency risk, or a genuinely disputed liability, even where the head contract and subcontract liability clauses are drafted as mirror images of each other. Apply an expected-credit-loss-type lens to the recovery asset's collectability, not merely its contractual existence. Where the head liability and subcontractor recovery are measured on different bases (e.g. IAS 37 probability-weighted provision versus a virtually-certain reimbursement threshold), do not assume they will move symmetrically period to period.

Presentation & disclosure

Disclose: (1) the nature and amount of the entity's own claim/damages liability separately from any subcontractor recovery asset, without netting; (2) the basis and probability threshold applied to recognizing the recovery asset (virtually certain); (3) significant judgments where head contract and subcontract liability terms are not perfectly mirrored (caps, exclusions, disputed pass-through); (4) concentration of recovery exposure to a specific subcontractor's credit risk.

Common mistakes

  • Automatically recognizing a subcontractor recovery asset equal to the full amount of the entity'
  • s own liability to the employer, without independently assessing whether recovery is virtually certain
  • netting the liability and recovery in the income statement instead of presenting them separately
  • ignoring a liability cap or exclusion clause buried in the subcontract that limits the subcontractor'
  • s actual exposure below the head contract liability
  • failing to reassess the subcontractor'
  • s financial capacity to pay when its own financial position deteriorates
  • assuming '
  • back-to-back'
  • drafting alone is sufficient evidence of virtual certainty of recovery.

Simple example

A main contractor is assessed as probable to owe the employer SAR 3,000,000 in liquidated damages for a delay attributable to a specific subcontractor's late completion. The main contractor's subcontract with that party contains a mirror liquidated-damages pass-through clause, but the subcontractor is in financial distress and disputes fault, and legal counsel assesses recovery as probable but not virtually certain (only 40% likely, and if recovered, likely capped at SAR 1,800,000 under the subcontract's liability cap).
Journal entry to recognize the head liability (reduction of transaction price, since this is delay-related LDs):
Dr Revenue from construction contracts (transaction price reduction) 3,000,000
Cr Contract liability / provision for liquidated damages 3,000,000
Because recovery from the subcontractor is only probable (not virtually certain), no recovery asset is recognized at this stage; the SAR 1,800,000 potential recovery is disclosed as a contingent asset only, not recognized on the balance sheet, until recovery becomes virtually certain (e.g. subcontractor formally admits liability and demonstrates ability to pay).

Professional judgment

The asymmetry between the probable threshold for recognizing the entity's own liability and the virtually-certain threshold for recognizing a reimbursement/recovery asset is a deliberate feature of IAS 37, not an oversight, and reflects the conservative principle that an entity should not recognize an asset for a recovery it does not yet have in hand, this asymmetry is frequently misunderstood or ignored in practice under commercial pressure to show a 'net' position. Assessing 'virtually certain' recovery requires a genuinely rigorous, largely fact-based test (a signed settlement, an uncontested and creditworthy counterparty) rather than mere contractual entitlement, and deteriorating subcontractor solvency should trigger a prompt reassessment of any previously recognized recovery asset for impairment.

Source basis

IAS 37 / IFRS 15 · Provisions, Contingent Liabilities and Contingent Assets / Revenue from Contracts with Customers

Paragraph references

IAS 37.53IAS 37.31–35

Verified against the official standard texts used in the IFRS Expert skill.

IAS 37 Provisions, Contingent Liabilities and Contingent Assets
Issued: September 1998 · Effective: 1 July 1999
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.