Contingent Liabilities in Balance Sheet Explained

The most expensive number in some annual reports never appears on the balance sheet. It sits thirty pages back, in a note titled "Contingent Liabilities and Commitments," written in the flat, sedating language auditors reserve for things they'd rather you skim. And every so often, a small part of that footnote stops being hypothetical and turns into cash leaving the bank.

Here is one that did. In FY25, Reliance Infrastructure disclosed that a bank guarantee of ₹35.21 crore it had given on behalf of a subsidiary had been invoked — the bank called it, and it became the parent's real payable (Reliance Infrastructure FY25 annual report, auditor's report on loans and guarantees). That ₹35 crore is rounding error against the company's books. The point isn't the size. The point is the mechanism: a "possible" obligation in a footnote became an actual one, exactly the way the note warns it can, and most shareholders never read the note.

This is an illustration of how the disclosure works, not a view on the stock. This piece is a field guide to that footnote — and to the part of it that does the real damage, which is almost never the headline number everyone quotes.

And like much of what matters on a balance sheet, the note tells you the position while management's words tell you the trajectory. Across more than 13,000 management commitments tracked on Inve over 1,500-plus listed Indian companies, footnote risks are exactly the kind management prefers not to dwell on — and Inve grades every Q&A exchange Direct, Partial, or Evasive precisely so deflections on topics like these don't slip past (Inve data, as of 2026-06-12).

What is a contingent liability?

A contingent liability is a potential obligation — one that becomes a real liability only if some uncertain future event happens. The company might have to pay, depending on how a dispute, a claim, or a guarantee plays out.

Because the outcome is uncertain, accounting rules (Ind AS 37) keep it off the main balance sheet and disclose it in the notes instead. The logic is simple: if you're not reasonably sure you'll have to pay, you don't book it as a liability — you flag it. There are three buckets, and the distinction is the whole game:

• Probable obligations where the amount can be estimated → these become a provision, booked on the balance sheet as a real liability.
• Possible obligations, or probable ones that can't be reliably measured → disclosed as a contingent liability in the notes.
• Remote obligations → not even disclosed.

So a contingent liability lives in the grey zone: real enough to mention, uncertain enough to leave off the books. Keep the base rate in view — a contingent liability is a possibility, not a certainty, and most never crystallise into cash. The note tells you the tail risk to weigh, not a number to subtract from the company's value and not a reason to act in itself. Your job is simply to figure out which footnote item is drifting toward "probable" — because that's the one about to move from the notes onto the balance sheet and out of the bank account.

Where do contingent liabilities come from?

In Indian annual reports, the note is usually a cocktail of a few recurring ingredients. Knowing the source tells you how worried to be.

• Tax disputes — by far the most common. Demands raised by income-tax, GST, customs, or excise authorities that the company is contesting in appeal. India's tax litigation is slow and voluminous, so most large companies carry sizeable disputed-tax contingencies. Many eventually settle or reverse for a fraction of the demand — but not all.
• Legal claims — lawsuits, arbitration, regulatory penalties where the company is the defendant ("claims against the Company not acknowledged as debts").
• Guarantees — corporate guarantees given on behalf of subsidiaries, joint ventures, or associates. This is the dangerous one: the parent has pledged to cover someone else's debt if they default.
• Letters of credit and bank guarantees — routine in EPC, infrastructure, and trading businesses.
• Capital commitments — contracted-but-not-yet-spent capex, disclosed alongside contingents (technically a commitment, not a contingency, but they share the note).

The forensic move is to read what kind the contingency is. A pile of disputed tax demands on a well-run company is usually noise. Take VIP Industries: on its Q4 FY25 call, management said it had "successfully removed a contingent liability of Rs.357 crores through a favourable tax judgment" (VIP Industries Q4 FY25 concall, Inve data). A ₹357 crore footnote item evaporated on one court order — which is one way disputed tax can end. Illustration, not a view on the stock. But survivorship cuts both ways: this is a case that resolved in the company's favour, and plenty don't. Some disputed-tax demands are upheld and crystallise into real cash leaving the bank, and you cannot know ex ante which way a specific case turns. Size a contingency for the adverse outcome; don't assume the reversal. A large corporate guarantee for a struggling subsidiary is a different animal entirely. Same footnote, opposite meaning.

Why the headline number is the wrong thing to size

Here is the part most explainers get wrong. They tell you to divide total contingent liabilities by net worth and worry if it's high. Useful, but it quietly assumes the danger is inside the disclosed number. Often it isn't.

Walk through Reliance Infrastructure's FY25 standalone note, because it shows the gap cleanly (Reliance Infrastructure FY25 annual report, Note 31 and auditor's report; standalone figures throughout). This is an illustration of how to read a footnote, not a view on the stock.

Run the textbook screen and you'd relax. The disclosed contingency fell by more than half year over year, and at ~19% of equity it looks like background noise. The indirect-tax line alone dropped from ₹1,104 crore to ₹357 crore (Reliance Infrastructure FY25 annual report, Note 31) — disputes resolving, the benign case.

Now read the three things the ratio doesn't capture, all in the same set of accounts:

• The guarantee book sits elsewhere. Outstanding guarantees given to subsidiaries were ₹661.73 crore as at year-end — disclosed in the auditor's report on loans and guarantees, not in the headline contingency line you just divided (Reliance Infrastructure FY25 annual report). That's about 59% of the ₹1,118.91 crore disclosed contingency and roughly 11% of equity — a second exposure of comparable size that sits outside the ratio you just ran, and it's pointed at related entities.
• One guarantee already converted to cash. ₹35.21 crore was "on account of invocation of bank guarantee on behalf of subsidiary by the Bank" (same source). The possible became actual.
• The scariest commitment is unquantified. The note says the company "has given equity / fund support / other undertakings for setting up of projects / cost overrun" for subsidiaries and associates, "the amounts of which currently are not ascertainable" (Reliance Infrastructure FY25 annual report, Note 31(b)). A risk with no number attached cannot be put in any ratio at all — which is precisely why it's easy to miss.

The lesson generalises. The disclosed contingency tells you about disputes; the guarantee book and the "not ascertainable" undertakings tell you about how much of someone else's trouble can land on this balance sheet. Size both. The headline number is the part the company was able — and willing — to quantify.

When does a contingent liability become a red flag?

Most contingent liabilities are routine and never cost the shareholder a rupee. A handful are landmines. Here's how to tell them apart.

Flag 1 — Size it against three anchors, not one. Net worth is the intuitive anchor — a contingency at 10% of equity is noise, one at 80–150% means a bad outcome could wipe out the cushion. But also size it against earnings power (could a year's profit absorb the loss?) and against the disclosures next to the note — the guarantee book, the unquantified undertakings. As Reliance Infrastructure shows, a tame headline ratio can sit beside a guarantee book of comparable size — roughly 59% of the disclosed contingency — that the ratio never touches.

Flag 2 — Guarantees for weak subsidiaries. A parent guaranteeing the debt of a loss-making or thinly-capitalised subsidiary is exporting risk into the footnotes. If that subsidiary defaults, the guarantee gets called and becomes the parent's real debt. Reliance Infrastructure's own auditor flagged this in plain words: the company "is also a guarantor for certain entities including its subsidiaries whose loans have also fallen due" (Reliance Infrastructure FY25 annual report, Emphasis of Matter) — the guarantee risk not as a hypothetical but as a present fact. This is the classic route by which trouble migrates from an unlisted entity onto the listed company's books — a cousin of the risk you read about in promoter pledging, where strain on related entities quietly becomes the shareholder's problem.

Flag 3 — Rapid growth in the line. Pull three years. A contingency ballooning year over year — especially guarantees and legal claims, not routine tax — signals rising disputes or rising off-balance-sheet support for related entities. (The reverse, a shrinking tax line, is usually benign, as above.)

Flag 4 — Vague, shrinking, or "not ascertainable" disclosure. If the note gets less detailed over time, lumps everything into one number, or — the worst tell — quantifies the routine items but leaves the subsidiary undertakings as "amounts not ascertainable," that opacity is itself the signal. Good managements disclose nature and amount; reluctant ones disclose neither.

And there's a fifth signal that sits above all of these: read the auditor's opinion paragraph first. On Reliance Infrastructure's FY25 standalone accounts, the auditors issued a Disclaimer of Opinion — they stated they "do not express an opinion … because of the significance of the matter described in the Basis for Disclaimer of Opinion," having been "not able to obtain sufficient appropriate audit evidence" (Reliance Infrastructure FY25 annual report, auditor's report). When the people paid to vouch for the numbers decline to vouch, no ratio you compute downstream is safe. Illustration, not a view on the stock.

The one case where it all stacks up

The reason to dwell on a single company rather than list rules is that the dangerous outcome is never one cause. It's several arriving together. On Reliance Infrastructure's FY25 standalone accounts, four forces converged in the same forty pages:

A disclosed contingency that looked like it was improving (down 56% year over year, ~19% of equity) — sitting beside a ₹661.73 crore guarantee book aimed at subsidiaries, an exposure of comparable size that the headline ratio never captures — one of those guarantees already invoked for ₹35.21 crore — and an auditor who, citing eroded net worth, going-concern doubt, and the company being "a guarantor for certain entities including its subsidiaries whose loans have also fallen due," declined to give an opinion at all (Reliance Infrastructure FY25 annual report). An investor who read only the headline contingency ratio would have concluded the footnote risk was receding. An investor who read the guarantee book, the invocation, the unquantified undertakings, and the auditor's paragraph would have concluded something close to the opposite.

That's the whole argument for reading the note properly. The number that's easy to find was the reassuring one. The numbers that mattered were one page over, or had no number at all.

How contingent liabilities connect to the rest of the balance sheet

A contingent liability never travels alone. Read on its own it's a scary number; read against the rest of the sheet it becomes a judgement.

The key pairing is contingencies and liquidity. A large contingent liability is far more dangerous in a company with thin cash and high debt than in one sitting on net cash. If a guarantee gets called, the question is immediate: can the company pay without breaching covenants or raising emergency capital? A firm with low debt-to-equity and surplus cash absorbs the shock. A leveraged firm running thin gets tipped over by it — the same fragility that turns an ordinary balance sheet into a debt-trap stock. The contingency is the trigger; the balance sheet's strength decides whether it's a flesh wound or fatal.

This is why the contingency note is a mandatory stop in how to read a balance sheet, not an afterthought. The face of the sheet shows assets, debt, and equity; the footnote shows the obligations that could join them — and, in the guarantee book, the obligations that belong to someone else until the day they don't.

What management says (and avoids saying) about contingencies

Footnote risks rarely get volunteered on a concall. They surface when an analyst pushes — "what's the status of the ₹400 crore GST dispute?" or "are the subsidiary guarantees likely to be called?" — and the response is information in itself. A direct, quantified answer is reassuring. A pivot, or "we're confident of a favourable outcome" with no detail, is the verbal equivalent of the vague footnote.

Sometimes management does name the number, which is the honest version. On its Q2 FY26 call, Indian Phosphate disclosed plainly that it "has provided a corporate guarantee of ₹105 crores for a related party project" (Indian Phosphate Q2 FY26 concall, Inve data) — a live guarantee, stated out loud, which is exactly the disclosure you want and the figure you'd then size against the company's own equity. Illustration, not a view on the stock. The contrast you're listening for is the company that won't say it.

These deflections are trackable. Inve's Concall AI grades each Q&A exchange as Direct, Partial, or Evasive, and Promise Tracker logs topics management persistently dodges across quarters. When questions about a tax dispute or a guarantee book get graded Evasive for two or three quarters running, that pattern is the call-level confirmation of what the footnote already hinted. For an investor holding ten or fifteen disclosure-heavy companies, catching that avoidance by hand, quarter after quarter, is the work that quietly never happens — which is how a footnote stays unread until the day it crystallises.

A short routine for reading the contingency note

1. Read the auditor's opinion paragraph first. A qualified opinion, an Emphasis of Matter on going concern, or — rare and serious — a Disclaimer of Opinion changes how much weight every other number can bear.
2. Find the note. Titled "Contingent Liabilities and Commitments," usually near the end of the standalone and consolidated financials. Read the consolidated version — it captures subsidiary exposures.
3. Don't stop at the headline number. Find the guarantee book (often disclosed in the auditor's report on loans and guarantees, or in related-party notes, not the contingency line) and any undertakings marked "amounts not ascertainable."
4. Size it against three anchors. Disclosed contingents ÷ equity, ÷ a year's profit, and the guarantee book ÷ equity separately.
5. Break it down by type. Separate routine tax demands from guarantees and legal claims. Worry more about guarantees to weak entities than about contested tax.
6. Pull three years and watch the trend — a falling tax line is usually benign; a rising guarantee line is not.
7. Listen for avoidance. If analysts ask about a big contingency and management deflects across quarters, weight the risk higher. Check liquidity and leverage before deciding whether the company could even pay.

Frequently asked questions

For a five-year owner, the contingency note is a question about tail risk: what's the worst that could come due, and could this balance sheet survive it? Most footnotes are harmless and resolve into nothing — a disputed tax demand that quietly disappears. But the discipline of reading past the headline number to the guarantee book, separating routine tax from dangerous guarantees, and noticing when the auditor or management won't speak plainly — that discipline is cheap, and it occasionally saves you from the one footnote that was the whole story.