What is a contingent liability and when must it be disclosed under IAS 37?

Under IAS 37, a contingent liability is not recognised on the balance sheet but must be disclosed in the notes unless the possibility of an outflow of economic benefits is remote. IAS 37 creates a strict three-way decision framework based on probability thresholds that every CFO and finance director must apply consistently: - Definition (IAS 37.10): A contingent liability is either (a) a possible obligation arising from past events whose existence will be confirmed only by uncertain future events not wholly within the entity's control, or (b) a present obligation that does not meet the recognition criteria — i.e., it is not probable that an outflow will be required, or the amount cannot be measured reliably. - Recognition boundary (IAS 37.14 & IAS 37.27): A provision is recognised only when an outflow of resources is probable (more likely than not, generally interpreted as >50%). If the likelihood is merely possible (below probable but not remote), no provision is booked — instead, a contingent liability disclosure is required. If the outflow is remote, neither recognition nor disclosure is needed. - Disclosure trigger (IAS 37.86): Unless the possibility of any outflow is remote, an entity shall disclose for each class of contingent liability: (a) an estimate of its financial effect, (b) an indication of the uncertainties around the amount or timing of any outflow, and (c) the possibility of any reimbursement (e.g., an insurance claim or indemnity from a third party).

How does the IAS 37 probability threshold ('probable' vs 'possible') interact with IFRIC 23 when the contingency relates to an uncertain tax position?

- No double-counting with provisions (IAS 37.27): Where an entity has recognised a provision for part of an exposure (the probable element), any residual possible exposure beyond that amount remains a contingent liability requiring disclosure under IAS 37.86. - Aggregation (IAS 37.87): Where a contingent liability arises from the same set of circumstances as other contingencies, the overall probability assessment must reflect the portfolio effect — individual low-probability items may collectively warrant disclosure. - Reimbursement assets (IAS 37.53–54): If a third-party reimbursement (e.g., an insurer) is virtually certain, it may be recognised as a separate asset — but the gross contingent liability disclosure is still required; netting is not permitted in the income statement except in specific circumstances. Scenario: A manufacturing entity is defending a product liability lawsuit. External legal counsel advises the probability of losing is 35% — possible but not probable. The claim is for €2,000,000. There is no insurance cover. Accounting treatment: Because the outflow is possible but not probable, no provision is recognised (IAS 37.14). The contingent liability is disclosed in the notes with an estimated financial exposure of €2,000,000.

When a contingent liability at year-end subsequently crystallises before the financial statements are authorised for issue, does IAS 10 require it to be reclassified as an adjusting event?

- Conflating "possible" with "remote": Practitioners sometimes conclude that because an outcome is unlikely, no disclosure is needed. IAS 37.86 is clear — only remote possibilities escape disclosure entirely. A 20% probability is still possible and triggers note disclosure, not silence. - Omitting the financial effect estimate (IAS 37.86(a)): Many preparers disclose the existence of a contingent liability but omit a quantified estimate, citing uncertainty. IAS 37.86 requires at least a range or qualitative basis; the "cannot be estimated" exemption (IAS 37.86, final sentence) is narrow and must itself be disclosed. - Prejudicial information exemption misuse (IAS 37.92): Entities sometimes suppress contingent liability disclosures entirely by invoking the "seriously prejudicial" exemption. IAS 37.92 permits omission of specific details (e.g., the legal strategy), but the existence of the contingency and the fact that information has been omitted must still be disclosed — blanket suppression is non-compliant. - IAS 37.10 — Definition of a contingent liability (possible obligation vs. unrecognised present obligation) - IAS 37.14 — Recognition criteria for provisions (probable + reliable measurement) - IAS 37.27 — The explicit prohibition on recognising contingent liabilities - IAS 37.86 — Mandatory disclosure requirements: financial effect, uncertainties, reimbursement - IAS 37.87 — Aggregation principles for disclosure of similar contingencies - IAS 37.92 — The narrow "seriously prejudicial" exemption and its limits

IAS 37 Contingent Liability Disclosure

IAS 37 Contingent Liability Disclosure — Core Rule

Under IAS 37, a contingent liability is not recognised on the balance sheet but must be disclosed in the notes unless the possibility of an outflow of economic benefits is remote.

How IAS 37 Contingent Liability Disclosure Works

IAS 37 creates a strict three-way decision framework based on probability thresholds that every CFO and finance director must apply consistently:

Definition (IAS 37.10): A contingent liability is either (a) a possible obligation arising from past events whose existence will be confirmed only by uncertain future events not wholly within the entity's control, or (b) a present obligation that does not meet the recognition criteria — i.e., it is not probable that an outflow will be required, or the amount cannot be measured reliably.

Recognition boundary (IAS 37.14 & IAS 37.27): A provision is recognised only when an outflow of resources is probable (more likely than not, generally interpreted as >50%). If the likelihood is merely possible (below probable but not remote), no provision is booked — instead, a contingent liability disclosure is required. If the outflow is remote, neither recognition nor disclosure is needed.

Disclosure trigger (IAS 37.86): Unless the possibility of any outflow is remote, an entity shall disclose for each class of contingent liability: (a) an estimate of its financial effect, (b) an indication of the uncertainties around the amount or timing of any outflow, and (c) the possibility of any reimbursement (e.g., an insurance claim or indemnity from a third party).

No double-counting with provisions (IAS 37.27): Where an entity has recognised a provision for part of an exposure (the probable element), any residual possible exposure beyond that amount remains a contingent liability requiring disclosure under IAS 37.86.

Aggregation (IAS 37.87): Where a contingent liability arises from the same set of circumstances as other contingencies, the overall probability assessment must reflect the portfolio effect — individual low-probability items may collectively warrant disclosure.

Reimbursement assets (IAS 37.53–54): If a third-party reimbursement (e.g., an insurer) is virtually certain, it may be recognised as a separate asset — but the gross contingent liability disclosure is still required; netting is not permitted in the income statement except in specific circumstances.

IAS 37 Contingent Liability Disclosure — Practical Example

Scenario: A manufacturing entity is defending a product liability lawsuit. External legal counsel advises the probability of losing is 35% — possible but not probable. The claim is for €2,000,000. There is no insurance cover.

Accounting treatment: Because the outflow is possible but not probable, no provision is recognised (IAS 37.14). The contingent liability is disclosed in the notes with an estimated financial exposure of €2,000,000.

Contrast this with a second claim where legal counsel assesses probability of loss at 70% and quantifies the best estimate at €500,000. Here a provision is recognised:

Account	Dr (€)	Cr (€)
Legal expense (P&L)	500,000
Provision for legal claims (liability)		500,000

If the original €2,000,000 claim (35% probable) subsequently resolves adversely — say damages are awarded at €1,800,000 — the entry at that point becomes:

Account	Dr (€)	Cr (€)
Legal expense (P&L)	1,800,000
Accrued liability / cash		1,800,000

The contingent liability disclosure in prior periods would have alerted stakeholders to exactly this risk.

IAS 37 Contingent Liability Disclosure — Common Pitfalls

Conflating "possible" with "remote": Practitioners sometimes conclude that because an outcome is unlikely, no disclosure is needed. IAS 37.86 is clear — only remote possibilities escape disclosure entirely. A 20% probability is still possible and triggers note disclosure, not silence.

Omitting the financial effect estimate (IAS 37.86(a)): Many preparers disclose the existence of a contingent liability but omit a quantified estimate, citing uncertainty. IAS 37.86 requires at least a range or qualitative basis; the "cannot be estimated" exemption (IAS 37.86, final sentence) is narrow and must itself be disclosed.

Prejudicial information exemption misuse (IAS 37.92): Entities sometimes suppress contingent liability disclosures entirely by invoking the "seriously prejudicial" exemption. IAS 37.92 permits omission of specific details (e.g., the legal strategy), but the existence of the contingency and the fact that information has been omitted must still be disclosed — blanket suppression is non-compliant.

IAS 37 Contingent Liability Disclosure — Key Paragraphs

IAS 37.10 — Definition of a contingent liability (possible obligation vs. unrecognised present obligation)
IAS 37.14 — Recognition criteria for provisions (probable + reliable measurement)
IAS 37.27 — The explicit prohibition on recognising contingent liabilities
IAS 37.86 — Mandatory disclosure requirements: financial effect, uncertainties, reimbursement
IAS 37.87 — Aggregation principles for disclosure of similar contingencies
IAS 37.92 — The narrow "seriously prejudicial" exemption and its limits