Provisions are recognised liabilities. Contingent liabilities are not recognised; they are usually disclosed unless the possibility of outflow is remote.
Under Indian GAAP, this distinction is set out in AS 29, Provisions, Contingent Liabilities and Contingent Assets. For entities reporting under Ind AS, ICAI’s Ind AS 37 educational material page confirms that Ind AS 37 deals with recognition, measurement and disclosure of provisions, contingent liabilities and contingent assets. The core decision is the same in practice: recognise when there is a present obligation, probable outflow, and a reliable estimate; otherwise consider contingent-liability disclosure.
Direct Distinction
| Point | Provision | Contingent liability |
|---|---|---|
| Nature | Present obligation from a past event | Either a possible obligation, or a present obligation that fails recognition criteria |
| Recognition in financial statements | Yes | No |
| Outflow test | Outflow is probable | Outflow is not probable, or obligation itself is only possible |
| Measurement | Best estimate of expenditure required to settle the obligation | No recognised amount because the item is not booked as a liability |
| Disclosure | Disclosure required for each class of provision | Disclosure required unless outflow possibility is remote |
| Later reassessment | Reviewed and adjusted at each balance sheet date | If outflow later becomes probable and estimable, it moves into provision territory |
Recognition Test: When an Item Becomes a Provision
AS 29 requires recognition of a provision only when all three conditions are met:
- There is a present obligation as a result of a past event.
- An outflow of resources embodying economic benefits is probable.
- A reliable estimate can be made of the amount.
If any of these conditions is missing, the item is not recognised as a provision.
That is where many classification errors start. Teams often focus only on uncertainty of amount. But uncertainty of amount does not by itself make something contingent. A provision can be highly estimated and still be recognised if the obligation already exists and outflow is probable.
What Makes a Liability Contingent
Under AS 29, a contingent liability covers two different situations:
- A possible obligation arising from past events, whose existence depends on uncertain future events not wholly within the entity’s control.
- A present obligation arising from past events that is not recognised because either outflow is not probable or the amount cannot be estimated reliably.
This is the key professional distinction. A contingent liability is not a weaker version of an ordinary payable. It is an item that remains outside recognition because the recognition threshold has not been crossed.
Practical Comparison Through Scenarios
1. Product warranty portfolio
Assumptions: A manufacturer sold 10,000 units before year-end with a one-year repair warranty. Based on past data, management expects 3% of units to need service, and the average repair cost is Rs. 1,200 per affected unit.
Expected cost = 10,000 x 3% x Rs. 1,200 = Rs. 3,60,000.
This is ordinarily a provision, not a contingent liability. The past event is the sale with warranty. Some claims are expected across the population of contracts, so outflow is probable for the class as a whole, and an estimate can be made.
2. Court case with uncertain outcome
Assumptions: A company faces a damages claim. At year-end, external counsel says the company is more likely than not to succeed.
That usually indicates a contingent liability disclosure, not a provision, because a present obligation requiring probable outflow has not been established on the available evidence.
Change in facts: In the next reporting period, new evidence emerges and counsel now advises that losing the case is probable, with an estimated settlement range of Rs. 18 lakh to Rs. 25 lakh.
At that stage, the item usually becomes a provision, measured at the best estimate.
3. Financial guarantee
Assumptions: Parent Co. guarantees a bank loan of Subsidiary Co. At the first year-end, Subsidiary Co. is financially sound and default is not probable.
This is generally treated as a contingent liability unless the possibility of outflow is remote.
Change in facts: Before the next year-end, Subsidiary Co. goes into severe financial distress and the guarantor now expects a likely payout.
The guarantee may then require provision recognition because the outflow threshold has changed.
4. Future operating losses
Assumptions: Management expects a loss-making branch to incur losses next year because of falling demand.
This is neither a provision nor a contingent liability merely because losses are expected. AS 29 expressly says provisions should not be recognised for future operating losses. Expected losses may instead indicate impairment issues under the relevant asset standard.
5. Onerous contract
Assumptions: A company has a non-cancellable service contract. The unavoidable cost of meeting the contract is Rs. 14 lakh, while the economic benefits expected are only Rs. 9 lakh.
Where the contract is onerous, the present obligation is recognised as a provision. This is an important edge case because the contract may still be executory in form, but once it becomes onerous the standard requires recognition.
How Measurement Differs
A provision is measured at the best estimate of the expenditure required to settle the present obligation at the balance sheet date. AS 29 also says provisions should reflect risks and uncertainties, should not include gains from expected disposal of assets, and should be reviewed at each balance sheet date.
A contingent liability is not measured for recognition purposes because it is not booked as a liability. If disclosure is required, the notes should describe the nature of the item and, where practicable, its financial effect and related uncertainties.
Disclosure Difference Matters in Practice
The accounting outcome changes both the numbers and the note disclosures:
- For a provision, AS 29 requires disclosure of movements during the period, including opening and closing carrying amount, additions, utilisation and reversals.
- For a contingent liability, AS 29 requires a brief description and, where practicable, an estimate of financial effect, uncertainties and possible reimbursement, unless the outflow possibility is remote.
This is why the label matters. Misclassifying a provision as a contingent liability can understate liabilities and expenses. Misclassifying a contingent liability as a provision can overstate liabilities and distort profit.
Decision Framework for Close Cases
- Identify the past event. What exactly has already happened before the reporting date?
- Ask whether that past event created a present obligation. Could the entity realistically avoid settlement?
- Assess whether outflow is probable, not merely possible.
- Decide whether a reliable estimate can be made, even if the amount is a range.
- If the answer to all three recognition tests is yes, recognise a provision.
- If there is only a possible obligation, or a present obligation without probable outflow or reliable estimate, consider contingent liability disclosure.
- If outflow possibility is remote, no contingent-liability disclosure is ordinarily required under AS 29.
Edge Cases That Commonly Cause Errors
Constructive obligations
An obligation does not have to arise only from contract or statute. AS 29 also recognises obligations arising from normal business practice, custom or a public commitment that leaves the entity with no realistic alternative but to settle. Refund policies and established warranty practices often fall here.
Board intent versus obligating event
A management plan, budget or internal decision is not enough by itself. If the entity can still avoid the expenditure by future action, there may be no present obligation at the reporting date.
Single item versus large population
For a single lawsuit, the analysis may depend heavily on legal evidence. For a large class of similar obligations such as warranties, probability is assessed for the class as a whole. That difference often changes the answer.
Reimbursements
If insurance or indemnity recovery is virtually certain, AS 29 allows recognition of a separate asset for reimbursement, subject to the amount of the provision. That does not eliminate the need to recognise the underlying provision when the entity remains primarily liable.
Bottom Line
A provision is a recognised present obligation with probable outflow and a reliable estimate. A contingent liability is an unrecognised possible obligation, or an unrecognised present obligation that does not yet meet that recognition threshold.
For Indian practice, the most defensible way to classify the item is to work through the AS 29 recognition test first and then apply the disclosure rules. The real distinction is not certainty versus uncertainty. It is recognition threshold versus disclosure threshold.
