How Deductibles Apply in Commercial Claims: Per-Event, Per-Location, and Aggregate Disputes

At placement, the deductible is a single number on the schedule that the buyer treats as a known, retained amount: the first slice of any loss the business will carry itself. It looks settled. The disputes begin only when a loss arrives and the question turns from how much the deductible is to how it applies, and that second question is where the money moves.

The same schedule figure can produce very different retentions depending on how it is applied. A deductible applied once to a single event is one number; the same deductible applied separately to each of several damaged locations, or to each of a series of related losses, multiplies the insured's retention several times over. On a nat-cat loss spread across a business's sites, the difference between one deductible and one-per-location can be the difference between a claim worth collecting and a claim swallowed almost entirely by retentions.

The reason this surfaces only at claim is that the application rules live in the operative and definitions clauses of the wording, not in the headline schedule, and buyers rarely read them until a loss forces the question. This piece works through the application disputes that actually recur on Indian commercial claims, one event or many, series-loss aggregation, percentage nat-cat deductibles, the order of average and deductible, and business-interruption time excesses, and sets out the drafting fixes to demand at placement so the fight is settled before the loss rather than during it.

The most common deductible dispute is the simplest to state and the hardest to resolve from a loose wording: a single cause damages more than one location, and the parties disagree on how many deductibles apply.

Consider a business with three insured sites in a city, all damaged by the same cyclone on the same day. If the policy applies the deductible per occurrence, and the cyclone is one occurrence, one deductible is retained across the whole loss. If the policy applies it per location or per item, three deductibles are retained, one for each damaged site. On a percentage nat-cat deductible, the three-times application can remove a large share of the recovery. The insured expected to carry one retention for the storm; the insurer applies three, and the gap is real money.

Which reading prevails depends entirely on the words. An excess expressed as applying to each and every occurrence points toward a single retention for a single event. An excess expressed as applying to each and every location, or each and every item, or each and every loss, points toward multiple retentions. Nat-cat perils in particular are frequently written with per-location deductibles precisely so the insurer retains one excess per affected site, and a buyer who did not notice this at placement discovers it when the storm lands.

The one-event-or-many question has a temporal cousin: when a single underlying cause produces damage over hours or days, or a chain of related losses over time, how does the wording decide what counts as one occurrence for deductible purposes. The answer is the aggregation language, and on catastrophe-exposed risks it is the hours clause.

An hours clause defines a single occurrence by a time window. Catastrophe wordings commonly treat all loss from a windstorm or flood arising within a defined period, often a 72-hour window, as one occurrence, so the deductible applies once to everything within the window even though the damage accumulated over several days. Other perils sometimes carry a longer window. The clause matters in both directions: it can help the insured, by collapsing a multi-day storm into a single deductible, and it can hurt, by defining the occurrence so that losses just outside the window fall into a second occurrence with its own deductible.

Series-loss language does the same job for non-catastrophe causes. Where multiple losses flow from one originating cause or defect, the aggregation clause decides whether they are one loss with one deductible or many losses each bearing an excess. A recurring defect, a series of similar failures, or a sequence of related incidents can be aggregated or disaggregated depending on how the wording defines a series and an originating cause, and the insured and insurer will read that definition in opposite directions according to which produces the better outcome for them.

The practical exposure is that many commercial wordings are vague on aggregation, carrying a per-occurrence or per-loss excess without defining occurrence or loss by any time or causation test. That vagueness is resolved at claim, under pressure, in the insurer's favour more often than not. A risk with any catastrophe or series exposure should confirm the aggregation basis is stated, not left to be argued when the loss is on the ground.

The form the deductible takes, a flat rupee figure or a percentage, changes its behaviour at claim, and the percentage forms used for natural-catastrophe perils are where retentions become large and contested.

Ordinary perils usually carry a flat monetary excess: a fixed rupee amount retained on each claim, predictable and easy to apply. Natural-catastrophe perils, storm, flood and inundation, earthquake, are different. They commonly carry a percentage deductible, expressed as a percentage of the claim amount or, more severely, a percentage of the sum insured, often subject to a minimum. A percentage-of-sum-insured deductible is the one that surprises insureds, because it is calculated on the insured value of the affected property rather than on the size of the loss, so even a partial loss can attract a deductible sized to the whole insured value of the location.

The interaction with the per-location question compounds this. A nat-cat percentage deductible applied per location, on a percentage-of-sum-insured basis, across several sites hit by one storm, produces a retention that can dwarf a flat excess by an order of magnitude. This is not an error; it is how the insurer prices the peak accumulation risk of natural catastrophe, transferring a defined slice of every cat loss back to the insured. But an insured that budgeted its retention on the flat excesses of its ordinary perils, without reading the nat-cat percentage terms, will badly under-estimate what it carries on the loss that matters most.

The discipline is to model the nat-cat deductible explicitly before buying. Calculate what the percentage deductible would actually retain on a realistic catastrophe loss at the largest site, and across multiple sites if the wording applies it per location, and compare that to what the business can absorb. A retention that looks modest as a percentage can be unaffordable in rupees on a large sum insured, and that is the number to test at placement, not after the monsoon.

A quieter but frequently disputed point is the sequence in which the average clause and the deductible are applied to a loss, because on an under-insured claim the order changes the final settlement.

Where a property is under-insured, the average clause reduces the claim in proportion to the shortfall between the sum insured and the actual value. The deductible then removes the retained slice. The generally accepted sequence in Indian property claims is that average is applied first, scaling down the assessed loss for under-insurance, and the deductible is then subtracted from that reduced figure. Applying average first and the excess second produces a lower settlement than the reverse, so an insured that assumes the deductible comes off the full loss before average is applied will over-estimate its recovery.

An illustration makes the effect concrete. Take an assessed loss, apply the underinsurance proportion to it, and only then remove the excess: the insured bears both the underinsurance reduction on the whole loss and the full excess on the reduced figure. Reverse the order, and the excess is scaled down by the same proportion, giving the insured slightly more. The difference is not large on a well-insured risk, but on a materially under-insured claim it is real, and it is exactly the kind of point that gets argued when the numbers are big.

The defence against the dispute is to make the wording say which order applies, and to understand that the standard practice runs average before deductible. Where a wording is silent, the insured should not assume the more favourable order; it should confirm it. And, more fundamentally, the whole issue disappears if the property is not under-insured in the first place, which is one more reason that setting the sum insured to full value is the most valuable single discipline in property insurance.

Deductibles on business-interruption cover take a different form, and their application generates its own set of disputes distinct from the monetary excesses on material damage.

A business-interruption policy typically carries a time excess (also called a waiting period or time deductible): a period at the start of the interruption, measured in days, during which the loss of gross profit is retained by the insured and not paid. Only the loss beyond the time excess is indemnified. It is the temporal equivalent of a monetary deductible, and it is set to filter out short interruptions the business can absorb.

The application disputes are specific. The first is whether the time excess is measured in working days or calendar days, which matters for a business that does not operate seven days a week, because a calendar-day measure runs the clock through days the business was not trading anyway. The second is how the time excess interacts with a partial interruption: where the business was not wholly shut but running at reduced capacity, quantifying the excess period against a partial loss requires the loss to be expressed in equivalent full-interruption terms, which is a matter of calculation the parties can dispute. The third is the interaction with the indemnity period: the time excess sits at the front of the interruption and the indemnity period caps the back, and the insured needs to understand that the excess erodes the front of its recovery just as the indemnity-period limit caps the tail.

The practical points at placement mirror those on the material-damage side. Confirm whether the time excess is in working or calendar days, understand how it applies to a partial interruption, and size it, like any deductible, to what the business can genuinely absorb rather than accepting a standard figure. A time excess set too long to win a small premium saving retains exactly the short-to-medium interruptions that a business most often suffers.

Every deductible dispute in this piece is, at root, a wording that left the application rule unclear or unfavourable and was resolved against the insured at claim. The remedy is to fix the language at placement, when the insured has bargaining power, rather than to argue it at claim, when it does not.

The fixes to press for are specific and short:

1. Define the occurrence. Confirm whether the deductible applies per occurrence, per location or per item, and make the schedule and the operative clause say the same thing. On a multi-site risk, insist the wording states plainly how a single event damaging several locations is treated.
2. State the aggregation basis. For any catastrophe or series exposure, require an hours clause or equivalent aggregation language, such as a 72-hour window for windstorm and flood, so a multi-day event or a run of related losses attracts a defined number of deductibles rather than an argued one.
3. Model the nat-cat percentage deductible. Calculate in rupees what a percentage-of-sum-insured deductible retains on a realistic catastrophe loss, per location if applied that way, and negotiate the basis or the minimum where the retention is unaffordable.
4. Fix the order of operations. Where under-insurance is a risk, confirm in the wording whether average or the deductible applies first, and do not leave it to be resolved at claim.
5. Clarify the time excess. Specify working versus calendar days and confirm how it applies to a partial interruption.

Comparing how different insurers define occurrence, aggregation, nat-cat deductibles and the order of average across their wordings is exactly the work that decides these disputes, and it is hard to do from schedules alone. Sarvada makes insurer policy wordings searchable, so a broker can pull the deductible, aggregation and average clauses from competing property wordings side by side and place cover whose application rules are clear and affordable before the loss. If your team places or defends multi-site or catastrophe-exposed commercial property, Request Access to compare the wordings that decide how the deductible really applies.