A contingent liability is an uncertain obligation that is generally disclosed rather than recognized when IAS 37 provision criteria are not met.
A contingent liability is an uncertain obligation that is not recognized as a liability under the IAS 37 provision model. It can be a possible obligation whose existence depends on uncertain future events, or a present obligation that is not recognized because an outflow is not probable or the amount cannot be measured reliably.
Under IAS 37, a contingent liability is generally disclosed unless the possibility of an outflow is remote. U.S. GAAP uses a loss-contingency model with different terminology and thresholds, so “contingent liability” should not be applied as if every reporting framework reaches the same result.
| Path | What remains uncertain | IAS 37 result |
|---|---|---|
| Possible obligation | Whether an obligation exists; confirmation depends on future events not wholly within the entity’s control | Do not recognize; disclose unless outflow is remote |
| Unrecognized present obligation | An obligation exists, but outflow is not probable or measurement is not sufficiently reliable | Do not recognize; disclose unless outflow is remote |
The distinction matters. A lawsuit may involve uncertainty about whether the entity committed the alleged act, while a guarantee may create a present contractual obligation whose expected settlement is uncertain. Other standards can apply to some guarantees, insurance contracts, financial instruments, and business-combination obligations.
The following table summarizes the IAS 37 logic at a high level:
| Assessment at reporting date | Typical treatment |
|---|---|
| Present obligation, probable outflow, reliable estimate | Recognize a provision |
| Possible obligation, or present obligation with outflow not probable | Do not recognize; disclose unless outflow is remote |
| Present obligation but no reliable estimate | Do not recognize; disclose unless outflow is remote; this circumstance is expected to be rare under IAS 37 |
| Outflow possibility is remote | Neither recognize nor generally disclose under IAS 37 |
This is not a mechanical probability scorecard. The assessment must consider all available evidence, the applicable reporting framework, and any standard that specifically covers the transaction.
Assume a company is sued before December 31 for alleged contract damage. At year-end:
The company does not record a liability under IAS 37 at that date. It generally discloses the nature of the matter, an estimate of financial effect when practicable, and relevant uncertainty and reimbursement information.
Three months later, new evidence makes an adverse outcome probable and supports a $320,000 best estimate. If that evidence provides information relevant to the new reporting date and the IAS 37 recognition criteria are met, the exposure is no longer treated only as a contingent liability. The company recognizes a provision:
1Dr Litigation expense $320,000
2 Cr Litigation provision $320,000
The example shows why contingencies require reassessment. The accounting changes because the evidence and recognition conclusion change, not because management chooses a preferred presentation.
| Exposure | Evidence to inspect | Important boundary |
|---|---|---|
| Litigation and claims | Pleadings, counsel letters, settlement history | Legal merits and accounting recognition are related but distinct judgments |
| Guarantees | Guarantee contract, borrower status, collateral | Financial-guarantee or other standards may apply before IAS 37 |
| Environmental matters | Law, permits, site studies, remediation plans | A present legal or constructive obligation may require a provision |
| Tax disputes | Assessments, filings, correspondence, legal analysis | Income-tax or other tax standards may govern |
| Contract disputes | Contract terms, performance evidence, notices | An onerous contract or recognized payable may exist |
| Product claims | Warranty terms, claim data, recall decisions | A large population of expected warranty claims often supports a provision rather than contingent-only disclosure |
The label should follow the accounting analysis. Calling an exposure “contingent” does not prevent recognition when another standard requires a liability.
Subject to materiality and the applicable framework, a useful contingency note helps readers understand:
Boilerplate such as “the company is subject to claims in the ordinary course of business” can be insufficient when it omits information needed to understand a material exposure. At the same time, disclosure should not imply precision that the evidence does not support.
| Term | Recognized? | Main distinction |
|---|---|---|
| Contingent liability under IAS 37 | No | Possible obligation, or present obligation that fails provision recognition criteria |
| Provision | Yes | Present obligation meeting recognition criteria, with uncertain timing or amount |
| Accrued expense | Usually yes | Cost already incurred, often with less uncertainty about obligation and amount |
| Commitment | Often not yet recognized | Agreement for future action; analysis depends on performance and contract terms |
| Contingent asset | Not recognized under IAS 37 while contingent | Possible asset confirmed by future events; disclosure threshold differs from a contingent liability |
IAS 37 uses the defined categories of provision and contingent liability. U.S. GAAP commonly uses ASC 450’s loss-contingency model, including “probable,” “reasonably possible,” and “remote” assessments. The words, probability thresholds, measurement of ranges, and disclosure requirements are not fully aligned.
For cross-border analysis, do not translate “provision” into “contingent liability” or compare reported amounts without reading the accounting policy and notes. A difference can reflect framework requirements rather than a difference in underlying economics.
Contingency conclusions can depend on privileged legal analysis and evolving facts. This page is educational and does not provide accounting, audit, tax, legal, credit, or investment advice.