Aggregation for IFAs: defined benefit transfer advice

Why the advice model shapes the answer

Aggregation clauses look for a connection either between the acts or omissions, or between the matters or transactions, or both. Transfer advice supplies a strong candidate for the first and a weak one for the second. The acts may well be similar — the same suitability template, the same assumptions about attitude to risk, the same analysis run on every case, the same shortfall in the file. But the transactions are not obviously related to each other. Client A’s transfer neither depends on nor connects with client B’s; they simply happen to have been handled the same way.

That is the structure the courts have repeatedly found insufficient. In AIG Europe Ltd v Woodman [2017] UKSC 18 the Supreme Court held that “related” matters or transactions must fit together and be connected in significant ways when viewed objectively and in the round — and it declined to aggregate across two schemes that were, on the facts, strikingly similar in structure. Similarity of method is not connection. The same logic applied to a book of individual advice files points firmly away from aggregation, unless something genuinely ties the files together.

When transfer claims might aggregate

There are patterns where the argument is real. Where a firm ran a defined exercise for members of one employer’s scheme at one point in time — a bounded population, a common set of scheme-specific inputs, often a common introducer or seminar — there is a serious case that the matters are related to one another and not merely alike. Where the advice rested on a single flawed input applied identically to every case, such as one incorrect scheme assumption or one defective analysis tool setting, the “same act or omission” framing becomes available rather than merely “similar”. And where several clients were advised into a single underlying investment or arrangement that then failed, the connection may lie downstream of the advice rather than in it. Our wiki entry on defined benefit transfer PI sets out how these claims have typically presented.

None of those is a safe assumption. Whether a particular set of files aggregates is a fact-sensitive judgement on the specific wording, and both sides can hold reasonable views until the facts are laid out. The point is to know which pattern your book looks like before a claim arrives, not after.

What aggregation, or its absence, costs

Work the arithmetic in both directions, because the direction that hurts depends on the structure. If claims do not aggregate and the limit is any-one-claim, each claim has its own limit — helpful — but also its own excess, and that excess is paid by the firm every time. Across a large advice book that uninsured total can dwarf any single claim. If claims do aggregate and the limit is any-one-claim, one limit and one excess answer everything, which is excellent unless the aggregated loss exceeds the limit, in which case the balance falls on the firm and, ultimately, on its members and any successor liability. If the limit is an aggregate for the period, aggregation adds little and the aggregate itself becomes the binding constraint. The any-one-claim versus aggregate comparison sets out the mechanics.

Two further points bear on advice firms specifically. Defence costs treatment matters more here than in most sectors, because a book of similar complaints generates costs on every file whether or not each is ultimately upheld; if costs erode the limit, the limit is smaller than it looks. And claims of this kind emerge over years, so the retroactive date and any run-off arrangements need to be continuous — see PI run-off cover on what happens when a firm stops writing new business.

Notification is the lever you actually control

Because the wording is usually settled before the problem appears, the practical control is notification. Where a firm identifies that a particular process, period or population of files may be defective, notifying that as a single, broadly described circumstance — with the evidence of what links the files — gives the best available foundation for treating the resulting claims consistently under one policy year. Drip-feeding individual complaints as they arrive achieves the opposite: it spreads the same problem across policy years and insurers, which is how firms end up arguing about which year responds as well as about how many limits do. Our notification guide sets out how a circumstance should be framed.

It is also worth remembering that the underlying regulatory framework shapes what a claim alleges. Under COBS 19.1.1A(1) a firm must ensure that advice on pension transfers, conversions and opt-outs is given or checked by a pension transfer specialist. A failing in that process is, by its nature, a process failing rather than a one-off — which is precisely why it produces many similar files and why the aggregation question then matters so much.

What a broker does differently here

We look at the shape of the book before we look at the wording: how many transfer files, over what period, arising from what sources, and whether any of them cluster around a single scheme, introducer, tool or investment. That tells you which aggregation limbs are live. We then test the limit against both the aggregating and the non-aggregating scenario, check whether defence costs sit inside or outside the limit, check the excess structure for the many-claims case, and confirm the retroactive date and run-off position survive any change of insurer. Where the aggregation wording varies between insurers — and outside the professions with prescribed minimum terms it usually does — we compare the actual clauses rather than the summaries. See aggregation clauses by regulator for how far different regimes constrain this. Apex is Bristol-based and FCA-regulated; we are insurance brokers and do not advise on pension transfers or on regulatory compliance.

Frequently asked questions

Do defined benefit transfer claims usually aggregate?

Usually not, on the authorities. Each client’s transfer is its own transaction and each loss flows from their own advice, so even where the advice failings are similar the matters are often not related to one another. AIG Europe v Woodman held that similarity of structure was not enough to connect two schemes; the same reasoning applies to a book of individual advice files.

If claims do not aggregate, is that good for the firm?

Not necessarily. Separate claims each get their own limit, which helps, but each also attracts its own excess, which the firm pays every time. Across a large advice book the total uninsured excess can exceed anything the firm planned for. Test the limit and the excess structure against the non-aggregating scenario as well as the aggregating one.

When could a set of transfer claims aggregate?

Where something genuinely ties the files together rather than merely making them alike: a defined exercise for members of one employer’s scheme over a short window, a single flawed input or tool setting applied identically across cases, or a common underlying investment that failed. Each is fact-sensitive and turns on the specific wording, so it should be assessed on the actual files rather than assumed.

Does how we notify affect the outcome?

It is the part the firm still controls. A single, broadly framed circumstance notification covering the affected process, period or population, supported by the evidence of what links the files, gives the best foundation for one consistent treatment. Reporting complaints one at a time as they arrive spreads the same problem across policy years and adds a which-year dispute to the how-many-limits one.

This page is general insurance information about how aggregation provisions in UK professional indemnity policies are commonly drafted and argued. It is insurance information, not legal advice, and it is not a statement of what any particular policy covers. Position stated as at August 2026. Where a claim, a circumstance or a limit is actually in issue, read your own wording and take advice on your own facts.

Apex Insurance Brokers Limited is authorised and regulated by the Financial Conduct Authority (FRN 724952). This page is general information, not advice on a specific policy.