Contingent Liabilities and Contingent Assets under Ind AS 37

Contingencies sit at the boundary between recognised amounts and uncertainty that remains outside the balance sheet. A contingent liability may reflect a possible obligation or a present obligation that fails the recognition conditions, while contingent assets arise from possible assets whose existence depends on uncertain future events. Operationalising the requirement requires clear ownership, stable data, documented judgements and a link between the technical conclusion and the amounts presented in the financial statements. Because recognition and disclosure thresholds differ, careful probability assessment is essential. A robust approach connects commercial substance, the Ind AS 37 decision criteria, measurement evidence and presentation consequences in one coherent file.

Distinguish possible from present obligations

The principle. A possible obligation depends on uncertain future events, while a present obligation may exist but remain unrecognised because outflow is not probable or the amount cannot be reliably estimated. For a review-ready file, legal and factual analysis should determine the nature of the obligation before probability is applied. The risk to avoid is labelling every disputed claim a contingent liability without considering whether a present obligation already exists. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.

Apply disclosure thresholds to liabilities

The technical anchor. Contingent liabilities are generally disclosed unless the possibility of outflow is remote, with information about nature, estimate and uncertainties where practicable. In application, the entity should maintain a complete claims register including matters not recognised as provisions. A frequent failure mode is omitting disclosure simply because management believes loss is less likely than not. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.

Avoid recognising contingent assets prematurely

The accounting logic. Contingent assets are not recognised when inflow is merely probable; disclosure may be appropriate when inflow is probable, while recognition occurs when realisation is virtually certain and the asset is no longer contingent. Operationally, finance should separate optimism about litigation or insurance claims from the recognition threshold. The main judgement risk is recognising expected legal recoveries based on a favourable preliminary opinion. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.

Reassess continuously

The decision point. Contingencies can move into or out of recognition as probability, enforceability and available evidence change. For implementation, legal letters and management assessments should be updated at each reporting date and after significant developments. Where errors often arise is carrying the same disclosure wording for years despite material changes in the case. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.

Avoid misleading net presentation

The core requirement. A possible recovery from another party does not automatically cancel a present obligation, and contingent assets and liabilities should be assessed independently under the standard's requirements. In a controlled close process, the gross obligation, reimbursement criteria and separate asset recognition should be analysed distinctly. A common weakness is netting an uncertain insurance recovery against a probable legal provision. Where the conclusion is sensitive to a contractual clause or estimate, the file should show the alternative outcome and why the selected treatment is more appropriate.

Practical illustration

Assume a company is defending litigation. External counsel believes loss is possible but not probable. The matter may require contingent-liability disclosure rather than a provision. If the company also believes its insurer may reimburse part of any settlement, that possible recovery is assessed separately and is not used to avoid disclosure of the underlying exposure. The illustration is deliberately simplified: its purpose is to show how the accounting conclusion follows the underlying facts rather than to prescribe a single mechanical answer for every entity. Before posting an entry, the preparer should reconcile contractual terms, management's commercial intent, relevant estimates and system data to the specific accounting requirement. Where the outcome is sensitive, the file should show the key judgement and explain why the selected assumption is reasonable at the reporting date.

Documentation and control points

Professional application depends as much on process quality as technical knowledge. For this topic, a minimum control set should cover legal-claims register; probability scale; disclosure threshold review; contingent-asset approval; and quarterly reassessment. Ownership should be clear between the business, finance and any legal, tax, valuation, credit-risk or other specialists whose evidence is required. Source data should be dated and version-controlled; manual adjustments should show preparer, reviewer, rationale and approval. The final accounting memorandum should connect the conclusion to the general ledger or relevant subledger, presentation and disclosures. If facts or estimates change, the entity should reassess the conclusion when required and preserve an audit trail explaining the change.

Closing perspective

Contingency accounting is asymmetric by design: uncertain losses may require disclosure before recognition, while uncertain gains face a higher bar before entering the balance sheet. The most useful way to apply Ind AS 37 is to treat the requirement as a decision framework rather than a compliance slogan. When the facts, accounting criteria, measurement evidence, controls and disclosure implications are considered together, the result is more consistent across reporting periods and easier to explain to management, auditors and users of the financial statements.