What is Contingent Liability?
IAS 37.10 defines a contingent liability in two limbs. The first covers a possible obligation where the existence of the obligation itself depends on a future event the entity cannot control (a pending lawsuit where liability has not yet been established). The second covers a present obligation that fails the recognition criteria because an outflow is not probable or the amount cannot be measured reliably. In neither case does the entity record a liability on the balance sheet. Instead, IAS 37.86 requires disclosure unless the possibility of outflow is remote.
The practical difficulty sits in the boundary between a provision and a contingent liability. Both originate from past events. The dividing line is probability: if an outflow of economic benefits is probable (IAS 37 uses "more likely than not"), the entity recognises a provision. If the outflow is possible but not probable, it discloses a contingent liability. If the outflow is remote, it does nothing. ISA 501.9 requires the auditor to design procedures to identify litigation and claims that may give rise to a risk of material misstatement, which includes evaluating whether management has drawn the probable/possible line in the right place.
Key Points
- A contingent liability is disclosed in the notes but never recognised on the balance sheet; if outflow becomes probable and measurable, it becomes a provision instead.
- IAS 37.86 requires disclosure of the nature of the contingency, an estimate of its financial effect, an indication of uncertainties, and the possibility of reimbursement.
- Regulators consistently find that entities disclose too little about pending litigation, with the FRC flagging inadequate contingent liability disclosures in over 30% of sampled files in its 2022/23 annual review.
- Omitting a contingent liability disclosure entirely (rather than misstating a number) is the type of error that triggers an opinion qualification for material misstatement of the notes.
Worked example: Hoffmann Maschinenbau GmbH
Client: German engineering company, FY2025, revenue €28M, HGB reporter also preparing IFRS consolidated accounts for the parent. Hoffmann sold a custom hydraulic press to an automotive tier-1 supplier in 2023. The press malfunctioned in September 2025, halting the customer's production line for six days. The customer filed a claim for €1,400,000 in consequential damages in November 2025. Hoffmann's external legal counsel assesses the likelihood of an adverse outcome as possible but not probable. The claim has not been settled or adjudicated at the balance sheet date of 31 December 2025.
Step 1 — Identify the obligation type
A past event exists (the sale and subsequent malfunction). The obligation depends on the court's ruling, an event not within Hoffmann's control. Legal counsel's assessment is "possible but not probable." This is a contingent liability under IAS 37.27, not a provision.
Documentation note: record the nature of the claim, the date filed, and the external counsel's written probability assessment. Cross-reference to the legal confirmation letter obtained under ISA 501.10.
Step 2 — Assess disclosure requirements
IAS 37.86 requires Hoffmann to disclose the nature of the contingent liability, an estimate of its financial effect (€1,400,000 claimed), an indication of the uncertainties, and the possibility of reimbursement. Hoffmann's product liability insurance covers manufacturing defects up to €2,000,000 with a €200,000 deductible. If the claim succeeds, the net exposure after insurance recovery would be approximately €200,000.
Documentation note: record the insurance policy terms, the deductible, and the maximum coverage. Document the basis for the estimated financial effect disclosed (full claim amount per IAS 37.86(a), with the insurance offset noted separately per IAS 37.86(c)).
Step 3 — Evaluate the "prejudice" exemption
IAS 37.92 permits an entity to omit certain disclosure if it would seriously prejudice the entity's position in a dispute. Hoffmann's counsel confirms that disclosing the existence and amount of the claim does not prejudice the defence because the claim is already public (filed in court). The prejudice exemption does not apply.
Documentation note: record counsel's confirmation that the standard disclosure would not seriously prejudice the outcome. If the exemption had been invoked, document the basis per IAS 37.92 and disclose that fact in the notes.
Step 4 — Draft and audit the note
Hoffmann's note reads: "A product liability claim of €1,400,000 has been filed by a customer relating to a hydraulic press malfunction in September 2025. External legal counsel assesses the outcome as possible but not probable. The company carries product liability insurance with coverage of up to €2,000,000 and a deductible of €200,000. The timing of resolution is uncertain."
Documentation note: verify the note against IAS 37.86(a)–(c) requirements. Confirm the note includes the nature, financial estimate, uncertainty indication, and reimbursement possibility. Cross-reference to the legal confirmation and insurance certificate on file.
Conclusion: the contingent liability disclosure is defensible because it rests on a written legal opinion, the financial effect ties to the actual claim amount, and the insurance offset is documented with reference to the policy terms.
Why it matters in practice
The FRC's 2022/23 annual review of corporate reporting found that entities frequently provided boilerplate contingent liability disclosures with no entity-specific detail about the nature of the claim, the estimated financial effect, or the basis for the probability assessment. IAS 37.86 requires each of these elements. An auditor who accepts "the company is subject to various legal proceedings" as a complete disclosure has not applied ISA 720.13 to evaluate whether the information in the notes is materially consistent with the financial statements.
Teams sometimes reclassify a contingent liability as a provision at year-end without reassessing the probability threshold. IAS 37.98 requires the entity to review contingent liabilities at each balance sheet date to determine whether an outflow has become probable. The reassessment must be documented with updated legal or technical evidence, not performed as a mechanical rollover from the prior period.
Contingent liability vs [provision (IAS 37)](/glossary/provision-ias-37)
| Dimension | Contingent liability | Provision |
|---|---|---|
| Recognition | Not recognised; disclosed in notes only (IAS 37.27) | Recognised as a liability on the balance sheet (IAS 37.14) |
| Probability threshold | Outflow is possible but not probable, or amount is not reliably measurable | Outflow is probable (more likely than not) and amount can be estimated reliably |
| Measurement | Estimated financial effect disclosed per IAS 37.86; no balance sheet amount | Best estimate of expenditure required to settle (IAS 37.36) |
| Reassessment | Reviewed each reporting date; may become a provision if probability increases (IAS 37.98) | Reviewed each reporting date; may be reversed if outflow is no longer probable (IAS 37.59) |
| Audit focus | Completeness of disclosure; legal confirmation letters; probability assessment | Measurement of the recognised amount; adequacy of the estimate; discount rate if material |
The distinction matters because misclassifying a provision as a contingent liability understates liabilities on the balance sheet, while misclassifying a contingent liability as a provision overstates them. Both errors affect the auditor's assessment of whether the financial statements are free from material misstatement. On engagements with significant litigation exposure, the auditor tests the probability boundary for each matter individually rather than accepting management's blanket classification.
Related terms
Frequently asked questions
What happens if a contingent liability becomes probable after the balance sheet date?
If the outflow becomes probable between the balance sheet date and the date the financial statements are authorised for issue, IAS 10.22(b) requires the entity to disclose the nature of the event and an estimate of its financial effect as a non-adjusting event (unless it provides evidence of conditions that existed at the balance sheet date, in which case IAS 10.10 applies and the entity adjusts). The auditor evaluates subsequent events under ISA 560.10 to determine whether the financial statements need amendment.
Does a contingent liability ever appear on the balance sheet in a business combination?
Yes. IFRS 3.23 requires the acquirer to recognise a contingent liability assumed in a business combination at fair value at the acquisition date, even if an outflow is not probable, provided the fair value can be measured reliably. This is one of the few situations where the normal IAS 37 recognition threshold does not apply. The auditor tests the completeness of identified contingent liabilities under ISA 540.18 as part of the purchase price allocation review.
How do I document a contingent liability when the client's lawyer refuses to respond?
ISA 501.10 requires the auditor to request management to instruct its legal counsel to communicate directly with the auditor. If counsel refuses or the response is inadequate, ISA 501.11 treats this as a scope limitation. The auditor considers whether the inability to obtain sufficient appropriate evidence requires a qualified opinion or a disclaimer under ISA 705.13.