Provisions & Contingent Liabilities
Why a company being sued for ₹10,000 crore might show nothing at all on its balance sheet about it — while a company facing a much smaller, more certain claim has to book the full amount as an expense today.
In plain English
Imagine two companies are each facing a legal claim. Company A is being sued for ₹500 crore in a dispute where its own lawyers think it's more likely than not to lose — say, a 70% chance. Company B is being sued for ₹10,000 crore in a case its lawyers consider a long shot — maybe a 10% chance, tied up in appeals for years. Common intuition might say the ₹10,000 crore case is the bigger worry and should show up more prominently in the accounts. Accounting sees it differently: it's Company A's ₹500 crore that has to be recorded as a real expense and liability today, while Company B's ₹10,000 crore claim might get nothing more than a footnote. The dividing line isn't the size of the number — it's how LIKELY it is to actually happen.
Words you'll need first
A liability of uncertain timing or amount that a company recognises IN FULL on its balance sheet, with a matching expense in the P&L, because it is judged 'probable' (generally read as more likely than not — over 50% chance) that money will actually have to be paid out, and the amount can be reliably estimated.
A possible obligation that ISN'T recognised on the balance sheet at all — it only gets disclosed in a footnote — because either the chance of it crystallising into a real payment is 50% or below, or the amount genuinely cannot be reliably estimated. This is the accounting equivalent of a warning label: 'this could cost us money, but we can't or shouldn't put a number on the balance sheet for it yet.'
Where a claim lands depends on the odds
Probable (>50% chance) → Provision
If it is more likely than not that the company will have to pay, and the amount can be reasonably estimated, the FULL best estimate is recognised immediately: an expense hits the P&L, and a matching liability sits on the balance sheet, right now — even though the case hasn't actually been decided.
Possible or remote (≤50% chance) → Contingent Liability
If the chance of having to pay is possible but not probable — or if it's probable but the amount can't be reliably estimated — nothing is recognised on the balance sheet at all. The company discloses the nature of the claim, an estimate of exposure if known, and its own likelihood assessment, in a note. If the chance is remote, disclosure isn't even required.
A worked example, with numbers
| Dispute | Likelihood of loss | Estimated exposure | Accounting treatment |
|---|---|---|---|
| Tax demand under appeal | 75% (probable) | ₹120 crore | Provision — ₹120 cr expensed & booked |
| Customer contract dispute | 40% (possible) | ₹80 crore | Contingent liability — notes only |
| Regulatory penalty threat | 10% (remote) | ₹500 crore | No disclosure required |
- Only the ₹120 crore tax demand — the smallest of the three amounts — actually hits the P&L and balance sheet, because it's the only one judged 'probable'.
- The ₹80 crore contract dispute is disclosed but changes NOTHING in the reported numbers — no expense, no liability — even though there's a real 40% chance it costs the company money.
- The ₹500 crore regulatory threat, by far the largest number, might not even require a mention if genuinely assessed as remote — showing why headline litigation amounts in the news can look alarming without moving a company's reported financials at all.
- If circumstances change — say new evidence makes the contract dispute suddenly look 'probable' rather than merely 'possible' — the ₹80 crore would move from a footnote straight into a P&L expense in that same reporting period, which is exactly how large, sudden 'one-off' charges often originate.
What it does to the financial statements
Impact on the P&L
- Recognising a new provision, or increasing an existing one, hits the P&L immediately as an expense — a real, though estimated, current-period cost, even though no cash has necessarily left the company yet.
- Provisions are reassessed each period; if a dispute's outlook improves, part or all of it can be reversed, flowing through the P&L as a gain — a genuine source of 'other income' surprises in some quarters.
- Because the probable/possible line is a judgement call, changes in a company's own assessment of a dispute, with no change in the underlying facts, can shift a large number between 'no P&L impact' and 'immediate expense'.
- Contingent liabilities, by definition, have ZERO impact on the P&L or balance sheet until and unless they cross the probability threshold — they exist only in the notes.
Impact on the Balance Sheet
- A Provision sits on the balance sheet as a genuine liability, usually split between current and non-current depending on expected timing, reducing net assets and equity by the same amount as the matching P&L expense.
- Contingent liabilities appear nowhere on the face of the balance sheet — meaning ratios like Debt/Equity can understate a company's true risk exposure if it is carrying large, undisclosed-on-balance-sheet contingent claims.
- When a provision is finally settled in cash, the liability is simply reduced and cash goes down by the same amount — if the actual settlement differs from the amount provided for, the difference hits the P&L again.
- A pattern of provisions being repeatedly 'released' in good years, or built up conservatively in bad years, is a classic area analysts scrutinise for potential earnings smoothing.
Which standard covers this
In India this is governed by Ind AS 37 – Provisions, Contingent Liabilities and Contingent Assets, notified under the Companies (Indian Accounting Standards) Rules and applicable to companies that follow Ind AS.
How it's recognised globally
Globally, the equivalent is IAS 37, issued by the International Accounting Standards Board, and the core probable/possible/remote framework described above is essentially identical worldwide. Under US GAAP, equivalent guidance sits in ASC 450 (Contingencies), which uses a similar three-tier framework — 'probable', 'reasonably possible', and 'remote' — with broadly the same recognition threshold. One practical difference: US GAAP's 'probable' threshold has historically been interpreted somewhat more strictly in practice, and the rules around discounting provisions and disclosure detail differ in the fine print, but the fundamental logic — recognition depends on likelihood, not the size of the number — holds true across India, IFRS and US GAAP alike.
Real example — Indian listed company
India's most consequential real-world example of provisioning and contingent liabilities at scale is Vodafone Idea's Adjusted Gross Revenue (AGR) dues dispute with the Department of Telecommunications, stretching from a landmark 2019 Supreme Court judgment through years of subsequent litigation, reassessment, and partial relief. At various points, the amounts owed, disputed, or under review have run into the tens of thousands of crores of rupees — reported dues have been frozen at levels above ₹87,000 crore during parts of the reassessment process — with different portions of the claim treated differently in the accounts depending on how probable and how reliably estimable each component was judged to be at each reporting date. Some of the demand has been recognised as a provision and expensed, materially deepening the company's reported losses in the years the recognition happened, while other, more contested components have moved in and out of contingent liability disclosures as the legal and regulatory position evolved. This is a genuine, large-scale illustration of exactly the mechanism explained in this article: the accounting treatment of a single dispute can shift dramatically, and shift reported profit by tens of thousands of crores, purely based on changes in probability assessment — without the underlying telecom business changing at all. (Given how actively this dispute continues to evolve, treat any specific figure here as illustrative of scale rather than a current balance — check the company's latest filings for the up-to-date position.)
Where you'll see this
Related concepts
Employee Benefits (Gratuity & Defined Benefit Plans)
Why a company can owe an employee who hasn't resigned yet, and won't for years, a real liability on its balance sheet today — calculated using life-expectancy tables and interest-rate assumptions, not a simple formula.
Deferred Tax Assets & Liabilities
Why a profitable company can owe the tax department far less than its P&L 'tax expense' suggests — and why a loss-making company can still show a tax expense on its books.
Onerous Contracts
Why a company can be forced to book a loss today on a contract it hasn't even started performing yet — simply because it already knows, with certainty, that the contract is going to lose money.