Technical Reserves / Policy Liabilities
The money legally parked against future claims — what the float actually is on the balance sheet, and what solvency is measured against.
Why you care
Technical reserves are the insurer's promise, priced and parked: money legally set aside on the balance sheet to pay claims it already owes or soon will. They're the liability side of insurance. And the same pile, seen from the asset side, is the float the insurer invests.
Run the numbers
An insurer holds ₹150 cr of technical reserves — unearned premium, outstanding claims, and IBNR (illustrative). That ₹150 cr is both what it owes policyholders and what it's currently investing as the float. One pile, two lenses: liability and investable asset.
Where this goes
The reserves are the balance-sheet form of the float, so they drive how much there is to invest. They also set the base for capital: the bigger the policy liabilities, the bigger the required solvency margin IRDAI makes the insurer hold on top.
Why you care
Technical reserves (also called policy liabilities) are the money an insurer is legally required to hold against claims it will have to pay. That covers both claims already incurred and the future cost of cover already sold. They are the liability side of the insurance business: a priced, parked promise sitting on the balance sheet.
They matter for two connected reasons. First, they are the float seen from the other side of the balance sheet. The reserves are a liability (money owed to policyholders), but the cash backing them is an asset the insurer invests until the claims fall due. Same pile of money, two lenses. Second, reserves are the base the regulator builds capital rules on. Because getting reserves wrong is how insurers fail — under-reserve, and you've quietly spent money you owe — IRDAI forces insurers to hold a solvency cushion on top of the reserves. So the size and honesty of the technical reserves drive both how much the insurer has to invest and how much capital it must lock away. Reserving is where prudent and reckless insurers separate.
Run the numbers
An insurer's technical reserves are built from a few components:
| Reserve | What it covers |
|---|---|
| Unearned premium reserve | The unexpired portion of cover already sold |
| Outstanding claims reserve | Claims reported but not yet settled |
| IBNR reserve | Claims incurred but not yet reported |
Add them up and say they come to ₹150 crore (illustrative). Read one way, that ₹150 crore is what the insurer owes — its policy liabilities. Read the other way, the cash sitting behind it is the ₹150 crore float it invests to earn investment income. Nothing about the money changes; only the column it sits in does. And note the knock-on: if the insurer writes more business, reserves grow, the float grows, but so does the required solvency margin it must hold against those bigger liabilities. Growth in insurance is not free — every rupee of new liability pulls capital along with it.
Where this goes
Technical reserves are the balance-sheet identity of the float: they are what the insurer invests, so they set the size of the second profit engine. They also anchor the regulator's grip — the required solvency margin is calculated on top of these liabilities, so bigger or riskier reserves mean more capital tied up. Reserving therefore sits at the exact junction where the insurer's investment upside and its capital cost are both decided.
What causes what
After this
- Technical Reserves / Policy Liabilities causesInsurance FloatThe technical reserves are what the float physically is on the balance sheet — the money set aside against future claims, waiting to be invested.
- Technical Reserves / Policy Liabilities causesRequired Solvency MarginBigger policy liabilities require a bigger required solvency margin held on top of them.