Insurance and legal commentary, not advice on your specific position. Aggregation outcomes are highly fact-sensitive — consult your broker and legal advisors. Apex Insurance Brokers Limited is authorised and regulated by the Financial Conduct Authority, FRN 724952.

Aggregation in IFA and financial services PI — including DB transfer case studies

The IFA and wealth management sector has the most volatile aggregation environment in UK PI. The combination of (a) FCA regulation that drives mass-claim events (DB transfers, pension review, SIPP suitability, structured product mis-selling), (b) the Financial Ombudsman Service ("FOS") and its compensation framework, and (c) market PI wordings that vary widely on aggregation language means that an IFA's aggregation position is a moving target. Lloyds TSB v Lloyds Bank Group Insurance [2003] UKHL 48 — covered in Spoke 3 — remains the most directly relevant case, but Spire Healthcare and AIG v Woodman now also bite.

This article is Spoke 7 of the Apex hub on aggregation and series clauses in PI insurance.

Plain English explanation

An IFA gives advice to many clients. Where advice is suitable, each client's matter stands alone. Where advice is systematically unsuitable — for instance, recommending DB pension transfers without proper consideration of the underlying scheme guarantees, or recommending SIPP investments in high-risk unregulated investments — the claims can run into the hundreds. Each individual claim might be modest (FOS-awarded sums are usually under £200,000 plus interest); the cumulative exposure can be many millions.

Whether those claims aggregate decides whether the IFA's PI cover is exhausted once or many times. Aggregation wordings used by IFA insurers vary more than in any other sector: some use only "series of related matters or transactions" (Woodman territory); some use "originating cause" (Spire/Lloyds TSB territory); some use both, with aggregation triggered if either applies; some include bespoke aggregation language for specific product types.

The regulatory and PI framework

IFAs are regulated by the FCA. PI insurance is required under FCA SYSC and IPRU-INV provisions. The FCA's PI rules set minimum cover levels (currently £1.4 million per claim and £2 million in aggregate for most IFA firms) and excess limits. They do not prescribe aggregation language.

FOS compensation limits also matter: the FOS compensation ceiling rose to £415,000 (for complaints about acts or omissions on or after 1 April 2019, indexed annually) and is now (2026) circa £445,000. Below the ceiling, the IFA's PI carries the loss subject to excess. Above the ceiling, the IFA carries the loss personally unless covered by separate cover.

The interaction with PI is that FOS awards may aggregate or fragment differently from court judgments. FOS is not bound by the policy's aggregation clause but is bound by its own compensation ceiling per complainant. The policy aggregation clause applies between IFA and insurer; the FOS award is between IFA and complainant.

How the leading cases apply

Lloyds TSB v Lloyds Bank Group Insurance — directly relevant. The pensions mis-selling problem (1988–94) is the closest historical analogue to today's DB transfer mass claims. The House of Lords fragmented the claims by treating each pension recommendation as its own originating cause. Today's insurers cite Lloyds TSB when they want to fragment a cluster and load up the excess.

Spire Healthcare v RSA — also relevant where the wording uses "originating cause". The Court of Appeal aggregated 750+ claims by treating Paterson's pattern of conduct as a single originating cause. IFAs facing aggregation arguments under originating-cause wording should expect insurers to cite Spire. Whether Spire fits the IFA fact pattern depends on whether the IFA's conduct is best described as a "pattern" (Spire-like) or as "many individual judgments" (Lloyds TSB-like). The two are distinguishable on the facts.

AIG v Woodman — relevant where the wording uses "series of related matters or transactions". DB transfer mass claims involving a common ceding scheme can satisfy Woodman aggregation because the matters (the individual transfers) are connected to a common scheme.

DB transfer aggregation — case studies

The DB transfer wave (mainly 2015–2018, with claims still being heard) is the defining IFA aggregation case study of the past decade. Two stylised case studies illustrate the issues.

Case study 1 — British Steel Pension Scheme (BSPS) advisers. Many IFAs advised steelworkers to transfer out of BSPS during the 2017 "Time to Choose" exercise. Hundreds of advisers gave advice to thousands of members. FOS and FSCS subsequently determined that much of the advice was unsuitable. Aggregation question: does an IFA who advised 100 BSPS members face one aggregated claim or 100 separate ones?

Common scheme (BSPS): yes.
Common timeframe (2017–18): yes.
Common advice methodology (in many cases — failure to consider scheme features, failure to assess critical yield, failure to properly evaluate sustainability of transfer): often yes.
Woodman analysis: a common scheme is an aggregating connecting feature. Series-of-related-matters rung likely satisfied.
Lloyds TSB analysis: each advice event is its own originating cause; the common scheme is context, not cause.
Spire analysis: if the IFA's conduct is best described as a "pattern" of failing to consider scheme features, the pattern is the originating cause and aggregation under that rung succeeds.

Practical outcome: most BSPS-related PI claims have been treated as aggregated by reference to the BSPS scheme. Insurers have applied one limit per IFA, and IFAs have looked to the FSCS where the limit was exhausted.

Case study 2 — SIPP mis-selling involving unregulated collective investments. IFAs recommending SIPPs into unregulated, illiquid, high-risk underlying investments (often property-based, sometimes overseas) faced mass claims. Common underlying investment (e.g. a particular Caribbean development), common SIPP provider, common methodological flaw — these features can satisfy aggregation under any of the three rungs.

Woodman: common scheme, common provider = related series. Aggregation likely.
Lloyds TSB: each recommendation is individual. Aggregation perhaps not.
Spire: pattern of failing to assess underlying investment risk = originating cause. Aggregation likely.

Practical outcome: many SIPP-related PI clusters have been treated as aggregated. Insurers have argued aggregation up; IFAs have sometimes pushed back on the basis that recommendations involved individual suitability assessments. Outcomes have varied.

Worked example with numbers

Take an IFA with the FCA minimum cover (£1.4 million each claim / £2 million aggregate) and a £25,000 excess per claim. 60 clients received DB transfer advice over an 18-month period. FOS has upheld 40 complaints. Average award: £80,000 per complaint. Total FOS exposure: £3.2 million.

Under "series of related matters or transactions" aggregation (Woodman-aggregable through common scheme): one aggregated claim. £25,000 excess. £2 million aggregate limit. Insurer pays £1.975 million; IFA pays £25,000 + £1.2 million limit shortfall = £1.225 million. (FSCS may pick up some of the shortfall depending on the IFA's solvency.)

Under "originating cause" aggregation (Lloyds TSB-fragmented): 40 individual claims. Each £80,000. 40 × £25,000 excess = £1 million in excesses. Insurer pays 40 × £55,000 = £2.2 million — but is capped at £2 million aggregate limit. IFA pays the £200,000 above limit too.

Under "originating cause" aggregation (Spire-aggregable through pattern): one aggregated claim. Same as Woodman analysis above.

Net effect: the IFA's net position depends on whether the wording fragments (Lloyds TSB) or aggregates (Spire / Woodman). The same losses produce very different IFA payouts: - Lloyds TSB fragmentation: £1 million excesses + £200,000 limit overrun = £1.2 million. - Spire / Woodman aggregation: £25,000 excess + £1.2 million limit shortfall = £1.225 million.

In this scenario the two outcomes are within £25,000 of each other — coincidence of arithmetic. With slightly different cluster sizes, the outcomes can diverge by hundreds of thousands of pounds. Map your specific cluster against your specific wording.

Sector implications

DB transfer specialists. Highest aggregation exposure of any IFA sub-sector. Common ceding scheme, common methodology, common product. Aggregation under Woodman and Spire wordings is the norm. Size limits accordingly; expect insurer pressure to load.

SIPP and pension administration. Pattern-of-conduct claims around suitability of underlying investments. Aggregation likely under Spire-style wording.

Investment management. Per-mandate exposure. Each client is usually a separate matter. Aggregation requires a common scheme or fund (e.g. model portfolios with a systemic flaw).

Mortgage and protection advice. Generally fragmented. Each client is a separate matter. Aggregation requires a systemic flaw across many advice events.

Auto-enrolment, GPP and group risk. Usually project-scoped engagements with employers. Aggregation by reference to the employer scheme.

What this means for your firm

Read your wording carefully and benchmark against peers. Wordings vary in this sector more than in any other. A "originating cause" rung pulls in Spire; a "matters or transactions" rung pulls in Woodman. Knowing your wording is the first step.

Size limits against worst-case clusters, not best-case clusters. A £2 million aggregate limit looks fine against 10 modest claims. It looks ridiculous against 100 claims at £100,000 average. Map your worst-case scenarios and buy limits to suit. Many IFAs now carry excess layers up to £10 million or higher.

Disclose product, scheme and methodology exposures at proposal. Use the cluster-disclosure approach in our IFA PI proposal completion guide. The duty of fair presentation under Insurance Act 2015 section 3 catches cluster-level features.

Notify by cluster. Where a complaint suggests cluster issues (e.g. multiple complaints about the same product or scheme), notify the cluster.

Stress-test run-off. IFA run-off is governed by FCA rules (mandatory for FCA-regulated firms exiting). Most appointments require 6 years. Aggregating wordings apply in run-off. See our IFA run-off cover deep dive.

How IFA aggregation differs from other professions

Wording variation is greatest. Solicitors have SRA Minimum Terms. Architects have project-level conventions. Surveyors have a published list of approved wordings. IFAs have a wider range of insurer-specific wordings.

FOS interaction. FOS awards are capped at a per-complainant limit. The interaction with the policy's aggregation clause creates two-layer aggregation analysis (between IFA and complainant, and between IFA and insurer).

FSCS interaction. Where an IFA's limit is exhausted and the firm cannot pay, FSCS picks up consumer claims subject to FSCS limits. This shifts some of the aggregation pressure from insurer to FSCS and is one reason insurers are aggressive on aggregation arguments in IFA claims — they know FSCS is behind them.

FAQs

Q1. Does FOS apply aggregation to its awards? No. FOS is bound by its compensation ceiling per complainant. It does not aggregate claims for the purposes of capping its awards.

Q2. Is the policy aggregation clause binding on FOS? No. The aggregation clause applies between IFA and insurer. FOS is not bound by it.

Q3. Does FSCS apply aggregation to its compensation? FSCS has its own compensation limits per consumer per firm. Aggregation in the PI policy does not control FSCS exposure.

Q4. What does "originating cause" mean for an IFA? A single source or root cause of the claims. Lord Hoffmann in Lloyds TSB held that a systemic context is not, by itself, a single originating cause; each advice event is its own cause. Spire Healthcare later held that a pattern of conduct can be a single cause. Whether your IFA conduct is "pattern" or "many decisions" depends on the facts.

Q5. Do BSPS claims aggregate? In most policies yes, under the "series of related matters or transactions" rung. The common scheme is the aggregating feature.

Q6. Do model portfolio claims aggregate? Yes if the model portfolio is the source of the loss. Common portfolio = common scheme/fund = related series.

Q7. Can I argue against aggregation as an IFA? Yes, on Lloyds TSB grounds: each advice event was individual. But the argument is harder where the policy uses originating-cause wording and the facts present as a pattern.

Q8. Is aggregation in IFA wordings ever helpful to me? Yes — for small-value high-volume claims. One excess across 100 small claims is much better than 100 excesses. The same dynamic as in solicitor will-writing or in surveyor panel work.

Q9. How do I tell which rungs my wording uses? Read the policy. The aggregation clause is usually in the General Provisions or in the definitions. Brokers should annotate the wording for you at renewal.

Q10. What is the single most important step in 2026? Map your aggregation exposures (scheme, product, methodology) and size limits and run-off cover against them. The FCA minimum is a regulatory floor, not a sensible commercial cover level for most IFAs.

Aggregation in IFA PI - defined benefit transfer claims