Australia: Aggregation clauses in insurance policies

Last Updated: 4 November 2015
Article by Keith Bethlehem, Toby Blyth and Emily Brownlee

In brief - Difficult to predict who will benefit from aggregation clause until claim is made

Aggregation clauses can work in favour of either the insurer or the insured depending on the circumstances that give rise to the claim(s) and the amounts as compared to the coverage limit.

What are aggregation clauses?

Aggregation clauses are used to define the coverage limits (that is, the maximum amount to be paid per claim) in a policy. These clauses determine what constitutes a "claim" for the purposes of excesses and maximum liability under the policy, by either aggregating or segregating multiple losses on a policy.

The clauses perform two main functions:

  • Determining how many deductibles the insured must bear
  • Determining whether a policy's coverage limits / sub-limits have been reached

The insured and the insurer attempt to model their respective risk profiles before policy inception, for future circumstances that neither party can know.

Whether aggregation is in the insured's or the insurer's favour is hard to say until a claim occurs. It follows that aggregation clauses can have a significant impact on an insured's and an insurer's risk profile.

In this article, we look at the different ways parties to insurance policies have drafted aggregation clauses in an attempt to demist the crystal ball.


"An 'occurrence' (which is not materially different from an event or happening...) is not the same as a loss, for one occurrence may embrace a plurality of losses. Nevertheless, the losses' circumstances must be scrutinised to see whether they involve such a degree of unity as to justify their being described as or arising out of one occurrence. The matter must be scrutinised from the point of view of an informed observer placed in the position of the insured": Kuwait Airways Corporation v Kuwait Insurance Co [1996] 1 Lloyd's Rep. 664.

There were three mechanical breakdowns in a ship. Each breakdown led to another, sparking a chain of events that could not be segregated. The breakdowns were held to be the same "occurrence". The insured was therefore only required to bear one per occurrence deductible (instead of three): Sealion Shipping Ltd v Valiant Insurance Co [2012] EWHC 50.

Construction works were insured for storm damage. The works were damaged in a storm and while under repair a further storm caused additional damage. The insured was required to bear two separate per occurrence deductibles, as each instance of damage was treated as a separate "occurrence": Government Insurance Office (NSW) v Atkinson-Leighton Joint Venture (1981) 146 CLR 206.

A plumber negligently installed waterproof membrane in the bathrooms of 47 separate houses while under the one sub-contract. The sub-contractor's (insured's) policy included a $300 excess for each and every claim. The insured was required to pay 47 excesses, as the plumber's "negligence" could not constitute an event or occurrence: QBE Insurance Ltd v MGM Plumbing Pty Ltd [2003] QSC 27.

Series of events

A number of claims were brought against the insured for the distribution of the drug thalidomide to pregnant women. The drug resulted in children being born with severe physical deformities. The insurance policy had a coverage limit of £50,000 for all claims "arising out of all occurrences of a series consequent on or attributable to one source...".

The High Court held that a "series" was a number of events of a sufficiently similar kind following one another in temporal succession. While the ingestion of thalidomide by each mother was a separate occurrence, they formed part of a "series" of occurrences that were sufficiently similar to aggregate the claims. The insurer was therefore liable to make a maximum claim payment of £50,000 for all claims: Distillers Co Bio-Chemicals (Aust) Pty Ltd v Ajax Insurance Co Ltd (1974) 130 CLR 1.

Related series of acts or omissions

Around 22,000 claims were brought against a number of companies that failed to provide their customers with "best advice" when selling personal pension schemes, breaching the Financial Services Act 1986 (UK). The companies were covered by a policy that contained a £1 million deductible for "each and every claim" where a claim was defined as "any single act or omission (or related series of acts of omissions)".

The House of Lords held that "related" meant there needed to be a common cause to each of the losses for them to be aggregated. The insured argued that the breaches were related as the cause was inadequate training of its representatives.

The court disagreed. There was no common cause. As each breach varied in time, client, location and method, the breaches could not be considered a "related series" (and therefore each claim fell below the deductible): Lloyds TSB General Insurance Holdings v Lloyds Bank Group Insurance Company Ltd [2003] UKHL 48.

Originating cause

An "originating cause" is concerned with the underlying reason why losses occur, rather than the occurrence of the losses themselves. It will likely capture a larger number of claims to be clumped together.

Use of the phrase "originating cause" is a conscious decision by an insurer or insured to open up the widest possible search for a unifying factor for the losses that a party is seeking to aggregate: Axa Reinsurance v Field [1996] 3 All ER 517.

Examples of originating causes include:

  • Failure to provide adequate training to commission agents by an employer resulting in the mis-selling of financial products to multiple consumers (Countrywide Assured Group plc v Marshall [2003] 1 All ER 237)
  • The negligent manufacture of a product (Pacific Dunlop Ltd v Swinbank (1999) 10 ANZ Ins Cas 61-439)

Similar acts or omissions in a series of related matters or transactions

Solicitors provided advice to a number of clients regarding two complicated property investment schemes in Turkey and Morocco. There were multiple claims against the solicitors. Their professional indemnity policy had a per claim coverage limit of £3 million (with the total of all the claims exceeding £10 million).

The insurer argued that there was one claim because the policy aggregated "similar acts or omissions in a series of related matters or transactions". The court held that each claim could be considered similar as they bore a resemblance or likeness to each other without being identical.

However, the court ultimately concluded that an aggregation clause with a very wide effect and no clear limit was too uncertain and vague to be given operative effect. Therefore the claims were not aggregated, relying on the words "series of related matters" to limit the scope of the aggregation clause: AIG v The International Law Partnership LLP and Ors [2015] EWHC 2398.

Which aggregation clause is better?

When faced with a high deductible and many small claims that may not individually exceed the deductible, an insured is likely to argue for one claim.

For example, 22,000 small claims were brought against the one insured, amounting to around £125 million in insured losses. No single claim exceeded £35,000 and the policy contained a per claim deductible of £1 million.

It was in the interests of the insured to aggregate the claims, so the deductible is reached (that is, the policy would respond after £1 million). If the claims were not aggregated, then the insurer would not be liable to pay any of the claims, as no single claim reaches the deductible threshold (Lloyds TSB).

When faced with a small number of larger claims, an insured will seek to argue for multiple claims.
For example, the two World Trade Centre towers were insured by layered property insurance that had a per claim limit of around US$3.5 billion (the actual loss far exceeding this coverage limit).

If the towers collapsing was one event (i.e. one claim) the insured could only recover a maximum of US$3.5 billion.

The insured therefore argued that there were two events (and two claims), one for each tower, so the maximum it could recover would then be US$7 billion.

The claims were complicated by different wordings in different policies:

  • "All losses or damages that are attributable directly or indirectly to one cause or to one series of similar causes" - one event: World Trade Centre Properties LLC. v. Hartford Fire Insurance Co., 345 F.3d 154 (2nd Cir. 2003).
  • Occurrence not defined - jury finds two events: SR International Business Insurance Co. v. World Trade Centre Properties LLC., 467 F.3d 107 (2nd Cir. 2006). Reinsurance arbitrations found to a similar effect: AIOI Nissay Dowa Insurance Company Limited v Heraldglen Limited and Advent Capital (No 3) Ltd [2013] EWHC 154 (Comm).

Aggregation clauses can work in favour of either party

As with most legal questions, then, the answer is that it depends. The examples above show that aggregation clauses can work in favour of either the insurer or the insured depending on the circumstances that give rise to the claim(s) and the amounts as compared to the coverage limit.

Keith Bethlehem Toby Blyth
Insurance and reinsurance
Colin Biggers & Paisley

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

Keith Bethlehem
Some comments from our readers…
“The articles are extremely timely and highly applicable”
“I often find critical information not available elsewhere”
“As in-house counsel, Mondaq’s service is of great value”

Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.