About this tool

Top-up vs Super Top-up Deductible Simulator

Run a year of hospital claims through a per-claim deductible and a policy-year aggregate deductible side by side, claim by claim.

A top-up vs super top-up deductible simulator runs one policy year of hospital claims through the same rupee deductible measured two different ways, and shows claim by claim who pays what. The only structural difference between the products is the basis of measurement: a top-up applies the deductible to EACH claim separately, so a claim smaller than the deductible pays nothing no matter how many such claims occur, while a super top-up applies it to the AGGREGATE of all admissible claims in the policy year, so everything above the deductible line is payable once cumulative claims cross it. Both readings come from the same standard clause — IRDAI's standard definition of Deductible (Guidelines on Standardisation in Health Insurance, Ref. IRDA/HLT/REG/CIR/146/07/2016, 29 July 2016) says the insurer is not liable for a specified rupee amount before benefits are payable, and that the deductible does not reduce the sum insured; whether that amount is per claim or per year is stated on your policy schedule. It is for anyone holding a base policy plus an upper layer who wants to see, in rupees, what a year of mid-sized hospitalisations does under each basis.

How to use Top-up vs Super Top-up Deductible Simulator

1. 1

   Open Top-up vs Super Top-up Deductible Simulator on AltFTool — it loads instantly in your browser.

2. 2

   Enter the values you already know.

3. 3

   Fine-tune the options to match your scenario.

4. 4

   Read the result and use it in your planning or reporting.

Why use Top-up vs Super Top-up Deductible Simulator

• The distinction stated the right way round

  Per claim for a top-up, policy-year aggregate for a super top-up — the same deductible, two bases of measurement, shown as two columns on the same claims.

• A claim-by-claim waterfall, not a total

  Every claim shows what the base policy paid, what fell below the deductible line, what the upper layer paid on each basis, and what was left out of pocket.

• The case where a top-up pays nothing

  When no single claim clears the deductible, the per-claim column is zero for the whole year while the aggregate column pays from the crossing claim onward — the page flags it explicitly.

• Sums insured deplete like real annual cover

  The base policy and the upper layer both run down across the year, and the deductible never eats the upper layer's sum insured, matching the standard definition.

Common use cases

• Read the deductible line on an upper-layer schedule and see what 'Rs 5,00,000 per claim' does to a year of Rs 3,00,000 hospitalisations versus 'Rs 5,00,000 aggregate'
• Model a chronic year — four or five mid-sized admissions rather than one large one — which is exactly the pattern the two bases treat differently
• Check which claim in the year the running total first crosses an aggregate deductible on, and how much of that claim becomes payable
• See what happens when the upper layer's own sum insured runs out mid-year, and how much of the bill that leaves unpaid

Frequently asked questions