If you searched for “aggregate limit insurance”, you have probably come across a policy document, a quote or a certificate that lists two different limits side by side, and you want to know what the aggregate figure actually does. In plain terms, an aggregate limit is the maximum total amount an insurer will pay for covered claims during a defined period, usually the policy period, while a per-occurrence limit caps what can be paid for a single claim or event. The two limits work together, and understanding the difference is essential, because a claim that fits comfortably within the per-occurrence limit can still be affected if earlier claims have already used up much of the aggregate. This article explains the concept in general educational terms, with worked hypothetical examples that are clearly labelled as examples, not advice for any specific policy. Always check your own policy wording, because definitions, exclusions and conditions vary.
Insurance language can feel deliberately opaque, but most of its key terms describe simple ideas. A limit is a ceiling. A deductible or excess is the amount you bear before cover responds. An occurrence is a single event or claim, as defined in the policy. An aggregate is a total across a period. Once those building blocks are clear, the rest of the document becomes much easier to read, and you are better placed to ask useful questions of your insurer or broker.
Aggregate Limit Insurance Explained in Plain English
An aggregate limit answers the question: how much, in total, will the insurer pay for all covered claims in this policy period? Suppose a policy has an aggregate limit of a certain amount for one year. Every covered payment made during that year counts towards that total, until the total is reached. After that point, the aggregate is exhausted, and further covered claims in the same period may not be paid, unless the policy provides for reinstatement or some other mechanism. That is the crucial difference from a per-occurrence limit, which resets, in effect, for each separate event.
Policies often show both limits together, for example in a format such as a stated amount per occurrence and a stated amount in the aggregate. The per-occurrence limit is applied first to each individual claim, and the aggregate limit is applied across all claims combined. A claim must therefore pass both tests: it must be within the per-occurrence limit on its own, and there must be enough aggregate limit remaining to pay it. If either test fails, the amount payable may be reduced or, in the case of an exhausted aggregate, may be nothing further for that period.
It helps to picture the aggregate as a single pot for the policy period and the per-occurrence limit as the largest single scoop that can be taken from the pot at one time. You can take several scoops during the period, but once the pot is empty, there is nothing left to scoop, even if a later event would otherwise have qualified for a large single payment. Some policies reinstate the limit after a claim, sometimes for an additional premium, and some do not. The policy wording will say which applies, and you should never assume reinstatement.
Aggregate Limit Insurance vs Per-Occurrence Limits
The contrast between aggregate and per-occurrence limits is best seen through a hypothetical example. This is an invented illustration only, using round numbers for clarity, and it is not a description of any real policy. Imagine a business liability policy with a per-occurrence limit of 100,000 and an aggregate limit of 300,000 for a one-year period. Three separate covered claims arise during the year, each valued at 100,000. Each claim fits within the per-occurrence limit, and together they total 300,000, exactly the aggregate. All three could, in this simplified illustration, be paid in full, subject to the policy terms.
Now imagine a fourth covered claim of 100,000 arises in the same period. On its own, it fits the per-occurrence limit perfectly. But the aggregate has already been used up by the first three claims, so there is no aggregate limit left. In this illustration, the fourth claim would not be paid from that policy period’s aggregate, even though it is a valid type of claim. That is the scenario aggregate limits are designed to create: a cap on total exposure over time, not just on single events.
A different hypothetical shows the reverse interaction. Imagine the same policy, but a single claim valued at 150,000. The aggregate has plenty of room, with 300,000 available, but the per-occurrence limit is only 100,000. In this illustration, the payment for that single claim would be capped at the per-occurrence limit, subject to the policy terms, even though the aggregate is far from exhausted. The two limits therefore constrain each other, and neither one alone tells the full story.
These examples also show why frequency matters as much as severity. A business that faces many small claims may exhaust its aggregate gradually, while a business that faces one very large claim may hit its per-occurrence limit first. When comparing quotes or reviewing a renewal, it is therefore worth asking not only how high each limit is, but how the two limits interact for the kinds of claims your activity is most likely to produce.
How Aggregates Work in Practice
In practice, several details shape how an aggregate operates, and each one should be checked in the wording. The first is the policy period: the aggregate usually applies to a single period, such as one year, and then resets when a new period begins, if the policy is renewed. Claims are normally allocated to the period in which they occur, but occurrence-based and claims-made policies treat timing differently, and long-tail claims can raise complex allocation questions. Your policy wording and your insurer or broker are the right sources for how timing works in your case.
The second detail is what counts towards the aggregate. Some policies count only amounts actually paid, while others also count defence costs, expenses or other amounts, depending on whether those costs are inside or outside the limit. A policy where defence costs sit inside the limit will erode the aggregate faster than one where they sit outside it, all else being equal. This is a detail that is easy to overlook, but it can change the effective cover significantly, so it is worth asking about it explicitly.
The third detail is whether sub-limits apply. A policy may have a general aggregate, plus smaller sub-limits for particular types of claim, such as a specific product, location or activity. A claim may then be capped by the sub-limit, the per-occurrence limit and the general aggregate all at once. Reading only the headline aggregate, without checking for sub-limits, can therefore give a misleading impression of the cover available for a particular risk.
Aggregate Limits and Deductibles
Deductibles, known in some countries as excesses, interact with limits in a way that is worth understanding. In general, a deductible is the amount you bear on each claim before the insurer pays, although some policies use an aggregate deductible, which is a total deductible across the period. An aggregate deductible works in the opposite direction from an aggregate limit: once you have borne the total deductible amount across several claims, later claims in the period may have no further deductible to bear. Again, the wording governs, and deductible structures vary widely, so do not assume that one policy’s approach matches another’s.
For a related definition in plain language, see our guide to what a deductible means in insurance, and for the broader context of business cover, see our explanation of commercial insurance meaning. Reading those alongside this article will help you place aggregate limits within the full set of terms that appear in a typical policy.
Worked Hypothetical Examples, Clearly Labelled
The following examples are hypothetical illustrations only, invented to show arithmetic. They are not quotations, not descriptions of real policies, and not advice about what limits any person or business should choose. Real policies contain definitions, exclusions, conditions and endorsements that can change every outcome below.
Hypothetical example one: a policy with a per-occurrence limit of 50,000 and an aggregate limit of 150,000. Claim A is 40,000 and is paid in full, leaving 110,000 of aggregate. Claim B is 50,000 and is paid in full, leaving 60,000 of aggregate. Claim C is 50,000, which fits the per-occurrence limit, but only 60,000 of aggregate remains, so it is paid in full in this illustration, leaving 10,000. Claim D is 20,000, which fits the per-occurrence limit, but only 10,000 of aggregate remains, so only 10,000 could be paid from the aggregate in this illustration, subject to the wording. The shortfall shows how a series of moderate claims can quietly erode cover.
Hypothetical example two: the same limits, but a single large claim of 80,000. The aggregate has room, but the per-occurrence limit is 50,000, so the payment for that claim is capped at 50,000 in this illustration, leaving 100,000 of aggregate for later claims. This shows that a high aggregate does not compensate for a low per-occurrence limit when a single event is large.
Hypothetical example three: a policy with a per-occurrence limit of 200,000 and an aggregate limit of 200,000. In effect, a single large claim could exhaust the entire aggregate at once, leaving nothing for later claims in the period. Some buyers choose equal per-occurrence and aggregate limits deliberately, accepting that trade-off, while others prefer an aggregate several times the per-occurrence limit, to allow for multiple events. Neither choice is right in general; the right balance depends on the risks involved, and that judgement belongs in a conversation with a qualified adviser or broker, not in a general article.
| Hypothetical scenario | Per-occurrence limit | Aggregate limit | Illustrative outcome |
|---|---|---|---|
| Three claims of 100,000 each | 100,000 | 300,000 | Each fits both limits; aggregate exactly used |
| A fourth claim of 100,000 follows | 100,000 | 300,000 (exhausted) | No aggregate remains for the fourth claim |
| One claim of 150,000 | 100,000 | 300,000 | Capped at 100,000 by the per-occurrence limit |
| One claim of 200,000 | 200,000 | 200,000 | Single claim exhausts the whole aggregate |
Questions to Ask About Your Own Policy
When you review a policy, a short checklist of questions will help you understand its aggregate. What is the aggregate limit, and what period does it cover? Is there a per-occurrence limit as well, and how do the two interact? Do defence costs or expenses count inside the limit or outside it? Are there sub-limits for particular claims? Does the limit reinstate after a claim, and if so, on what terms and at what cost? How are claims allocated to a policy period, especially for events that develop over time? Bringing those questions to your insurer or broker will usually produce clearer answers than reading the headline limit alone.
It is also worth asking what happens at renewal if the aggregate has been partly or fully used. Some insurers will renew on fresh terms, with a new aggregate for the new period, while others may adjust terms, pricing or availability in light of claims history. A partly used aggregate in one period does not automatically carry over as a reduction in the next period, but claims history can still affect renewal discussions. Keeping a simple record of claims, payments and remaining limits during the period helps those conversations, and it helps you notice early if the aggregate is being eroded faster than expected.
Finally, remember that an aggregate limit is only one part of a policy. Exclusions define what is not covered at all, conditions define what you must do to keep cover in force, and endorsements can add, remove or change cover. A generous aggregate is of limited comfort if the claim type in question is excluded, and a modest aggregate may be perfectly adequate for a risk that rarely produces claims. The whole document, read together, is the cover, not any single number in isolation.
Frequently Asked Questions
What is the difference between an aggregate limit and a per-occurrence limit?
A per-occurrence limit caps payment for a single event, while an aggregate limit caps total payments for all covered events in the policy period. A claim must fit within both limits to be paid in full.
What happens when the aggregate limit is exhausted?
In general, no further payments can be made from that period’s aggregate, unless the policy provides for reinstatement or another mechanism. The exact consequence depends on the wording, so check it and ask your insurer if you are unsure.
Does the aggregate reset each year?
Usually a new policy period brings a fresh aggregate, if the policy is renewed, but claims allocation and renewal terms can complicate the picture. Confirm the position for your own policy rather than assuming a clean reset.
How do I choose the right aggregate limit?
That is a personal or business decision that depends on your risks, finances and legal obligations. General articles can explain the concepts, but the choice itself should be made with a qualified adviser or broker who understands your circumstances.
Conclusion
An aggregate limit is, at heart, a simple idea: a ceiling on total payments across a policy period, working alongside the per-occurrence ceiling on single claims. The hypothetical examples in this article show why both limits matter, how a series of moderate claims can exhaust an aggregate, and how a single large claim can be capped by the per-occurrence limit even when aggregate room remains. Keep the checklist of questions in this article beside you when you read your own policy, pay attention to whether costs sit inside or outside the limit, and check for sub-limits and reinstatement terms. Above all, treat this article as general education, and let your own policy wording, read with your insurer or broker, be the final word on what you are actually covered for.