How FDD hunts, sizes and prices contingent liabilities and litigation: routing off-balance-sheet exposure into net debt, provisions or SPA indemnities and escrow.
The most expensive number in a deal is often the one that isn't in the accounts. A pending lawsuit, a disputed tax assessment, a warranty claim brewing in a customer's legal department, a guarantee given over a subsidiary's bank loan — none of these may appear as a liability on the balance sheet, and yet any of them can eat a chunk of the equity value the buyer is about to pay for. Contingent liabilities are where financial due diligence stops being a reconciliation exercise and turns into detective work. The seller has every incentive to keep these exposures in the "possible but not probable" bucket, off the face of the accounts, tucked into a note. Your job is to drag them into the light, size them, and make sure the price and the contract reflect them.
This is also the topic that most cleanly separates a candidate who has read a textbook from one who understands how a deal actually gets done. Anyone can recite the IAS 37 definition. The skill is knowing what to do with a €4m litigation exposure once you've found it — whether it belongs in net debt, in a provision, or in an indemnity that never touches the accounts at all.
A contingent liability is a possible obligation whose existence or amount depends on some future event outside the company's control, or a present obligation that isn't recognised because payment isn't probable or can't be measured reliably. Under IAS 37 the logic is binary in spirit: if an outflow is probable and can be reliably estimated, you book a provision on the balance sheet; if it's only possible, you disclose it in the notes; if it's remote, you say nothing at all. That threshold — the line between "provide" and "disclose" — is exactly where management judgement, and management optimism, live.
The exposures FDD sees most often fall into a handful of families:
| Type | Typical trigger | Where it hides |
|---|---|---|
| Litigation | Customer, supplier or employee claim | Legal letters, board minutes, notes |
| Tax disputes | Challenged filing, transfer pricing | Tax correspondence, uncertain tax positions |
| Warranties & guarantees | Product defect, parent guarantee of debt | Sales contracts, intercompany agreements |
| Environmental | Contaminated site, remediation duty | Property files, regulatory notices |
| Regulatory & compliance | Fines, data-protection breaches | Regulator correspondence |
The unifying feature is that they are off-balance-sheet until something crystallises. That is precisely why they are dangerous: the reported EBITDA and the reported net assets both look clean, and the buyer can walk into completion oblivious to a claim that is one court ruling away from becoming real cash out the door.
A contingent liability is not a small liability. It is a full-sized liability wearing a disguise. Size it as if it will land, then negotiate the probability.
There are structural reasons the balance sheet flatters the position, and none of them require the seller to be dishonest.
First, the probable threshold is genuinely high. A claim the company reasonably expects to defend successfully is disclosed, not provided — so a €10m lawsuit the seller believes it will win shows up as a footnote with a nil balance. If your read of the merits differs from management's, the accounts are silent on that difference.
Second, measurement uncertainty lets a real obligation stay unbooked. If the range of outcomes is wide and no point in it is more reliable than another, the standard permits non-recognition. Management naturally frames ranges to keep the number out of the accounts.
Third, timing. Provisions are set at the reporting date. A claim that arrived three weeks after year-end, or that has escalated since, may not be reflected at all in the last audited numbers you're working from — which is why the FDD process always chases events after the balance-sheet date.
Fourth, incentive. A vendor preparing for sale has an obvious reason not to volunteer provisions that would reduce reported profit or invite price chips. This is one of the clearest cases where reading a vendor due diligence report demands scepticism: the analysis is competent, but the framing of contingencies will be as favourable as the facts allow.
You cannot rely on a schedule labelled "contingent liabilities" — the interesting ones never make the schedule. The work is triangulation across sources that were never meant to be read together:
The output of this hunt is not a yes/no. It is a list of exposures, each with an estimated quantum, a probability and a view on timing — the raw material for both the price and the SPA.
Suppose the target, a mid-market manufacturer, has three live exposures at completion. Management has provided for none of them because each sits below its "probable" bar. FDD builds an expected-value view and, separately, a worst-case view, because the buyer needs both — the expected value informs the price, the worst case informs how much protection to demand.
| Exposure | Face amount | Probability of loss | Expected value | Worst case |
|---|---|---|---|---|
| Customer warranty claim (defective batch) | €3.0m | 70% | €2.10m | €3.0m |
| Transfer-pricing tax assessment | €2.5m | 40% | €1.00m | €2.5m |
| Ex-employee tribunal claim | €0.4m | 50% | €0.20m | €0.4m |
| Total | €5.9m | €3.30m | €5.9m |
Two numbers now matter. The €3.3m expected value is the amount the buyer would rationally strip from equity value if it had to bear these risks itself — a direct hit to the equity bridge. The €5.9m worst case is the amount of protection (indemnity cap, escrow) the buyer should want if the exposures are handed back to the seller. The warranty claim, at 70% probability, is arguably over the line into provision territory and should be argued as debt-like regardless; the tax and tribunal claims are better handled through specific indemnities because their probability is lower and their outcome binary.
Notice what this does to the deal. On a headline EV of, say, €60m built on an 8x multiple, a €3.3m expected exposure is not a rounding error — it is more than 5% of equity value, and it is invisible in the reported EBITDA the multiple was applied to.
Finding the number is half the job. The other half is deciding how it flows into the deal, and there are three distinct routes, each with different consequences.
Route 1 — Provision (in working capital). If the obligation is really probable and estimable, it belongs in the balance sheet as a provision, which pulls it into the net working capital analysis. The risk here is double-counting: if a provision sits in the working-capital target and you deduct it again as debt-like, the seller is charged twice. Be explicit about which mechanism carries it.
Route 2 — Debt-like item. Genuine one-off, non-operating obligations — a crystallising tax settlement, a definite legal payout — are typically treated as debt-like items and deducted from EV in the bridge, pound for pound, just like a bank loan. This is the cleanest treatment for a claim that is effectively certain to pay out.
Route 3 — Indemnity and escrow in the SPA. For genuinely contingent, probabilistic exposures, the elegant answer is contractual, not accounting. The seller gives a specific indemnity covering the identified risk, often backed by an escrow or retention — a slice of consideration held back until the exposure resolves. The buyer pays full price today but claws back if the risk lands.
The rule of thumb: certain and quantifiable → net debt; probable and operational → provision in working capital; possible and specific → indemnity with escrow. Match the mechanism to the character of the risk, not to whichever chip is easiest to argue.
The choice is not neutral for the seller either. An indemnity leaves the risk with the vendor; a net-debt deduction transfers it to the buyer in exchange for a lower price. This is a negotiation, and understanding the trade-off is what lets an FDD adviser add value beyond the arithmetic.
Contingent liabilities rarely travel alone. A warranty exposure is often a symptom of a quality problem that also shows up in the quality of earnings — recurring warranty provisions that management keeps recycling as "one-off" are both a contingent-liability question and an EBITDA adjustment question. A tax dispute may reveal an aggressive structure that inflated historical earnings. The best analysts read these exposures as red flags that point back to the sustainability of the earnings base, not as isolated line items to be netted off at the end. The FDD report should carry the exposure through consistently: flagged in the executive summary, quantified in a dedicated section, and reflected in both the net-debt schedule and the SPA recommendations.
Interviewers use contingent liabilities to test whether you can move from an accounting definition to a deal decision. A weak answer stops at "you disclose it in the notes." A strong answer prices it and places it in the contract.
"I'd treat the reported balance sheet as a floor, not the full picture, because IAS 37 lets management keep possible-but-not-probable claims off the face of the accounts. I'd triangulate — legal confirmation letters, board minutes, the legal-fees line, tax correspondence — and for each exposure I'd estimate a quantum, a probability and a timing. Say I find a €3m warranty claim at 70% likelihood, a €2.5m tax assessment at 40%, and a small tribunal claim. The expected value is around €3.3m, and that's what I'd argue should come out of equity value; the worst case near €5.9m is what sizes the protection. Then I'd match the mechanism to the risk: the warranty claim is probably over the 'probable' line, so I'd push for it as a provision or a debt-like deduction; the tax and tribunal claims are genuinely contingent and binary, so I'd handle them with specific indemnities backed by an escrow, rather than a blanket price chip. The key discipline is not double-counting — if it's in the working-capital target, it can't also come out as net debt. And I'd flag whether the warranty issue points to a recurring quality problem, because then it's a quality-of-earnings question too, not just a one-off exposure."
That answer works because it does four things in sequence: it distrusts the accounts, it sizes the risk two ways, it chooses a contractual mechanism, and it connects the exposure back to earnings quality. Practise delivering it with a specific number, because the interviewer's follow-up is always "so how much would you take off the price?"
Watch for these in the target — and avoid them in your own analysis:
Contingent liabilities are the part of due diligence where the numbers you can't see matter more than the ones you can. A buyer who reads only the balance sheet is pricing a business that may not exist — one court date, one tax ruling, one warranty batch away from a very different set of accounts. The discipline is unglamorous: read the legal letters, follow the fees, size each exposure two ways, and then have the judgement to route it correctly — into net debt, into working capital, or into an indemnity with money held in escrow. Do that well and you protect the buyer from the most expensive surprise in dealmaking: the liability that was always there, just waiting for a footnote to become a fact.
The Transaction Services Interview Programme (€119.99, one-time) includes a full module on off-balance-sheet exposures — how to hunt, size and price litigation, tax and warranty risk, and how to argue whether each belongs in net debt, working capital or a specific SPA indemnity. Enrol today.
Hundreds of candidates prepared their interviews with this programme. Those who landed the role have one thing in common: they worked the cases before walking into the room.
