Home / Insights / One error, thousands of members: aggregation and excess in pensions PI
Insights for actuaries and pension consultants
One error, thousands of members: aggregation and excess in pensions PI
A wrong factor or system setting does not make one mistake. It makes the same mistake for every member it touches. Two parts of your PI decide how that is counted: the aggregation clause and the excess. They need reading together.
Guidance only. Cover depends on your own policy wording; speak to us about your position.
Why pensions errors come in thousands
Most professional errors hurt one client once. Pensions work is different. An increase rule coded wrongly, a commutation factor not updated, a flaw in a GMP equalisation template: each produces a small error for every member it is applied to, in every scheme that uses it, every month until someone notices.
The claims then come from several directions. The trustees of each scheme may claim. Members may complain to the Pensions Ombudsman, whose jurisdiction can extend to those concerned with a scheme’s administration (Pension Schemes Act 1993, section 146). The employer may claim the cost of putting it right. So the policy has to answer a question most firms never ask: is this one claim, or 2,400?
What an aggregation clause says
An aggregation clause treats claims that share a defined link as one claim. The link is everything, and wordings differ.
| Typical words | How wide | A pensions example |
|---|---|---|
| “Arising from one originating cause or source” | Usually the widest. It looks back to the underlying reason for the claims. | A flawed data load that produced several different errors across schemes may be drawn together. |
| “The same act, error or omission” | Narrower. The claims must flow from one act. | One wrongly coded increase rule is likely to be one. The same mistake made separately by two teams may be two. |
| “A series of related acts or omissions” | Depends on how “related” is defined and read. | One template reused on separate projects for different clients may or may not qualify. |
These are general descriptions. How a clause applies depends on its exact words and the facts, and the point is often argued. That is why we read the clause against your work, not in the abstract.
Aggregation cuts both ways
An illustration. An administrator overpays 2,400 pensioners by an average of £1,500 each, £3.6 million in all. Its policy has a limit of £2 million any one claim and an excess of £10,000.
| How it is counted | The excess | The limit |
|---|---|---|
| As one claim | One excess of £10,000. | One limit of £2 million for a £3.6 million loss. £1.6 million is uninsured. |
| As 2,400 claims | £10,000 on each. No member’s loss reaches it, so the policy pays nothing. | A separate limit for each claim, never reached. |
Neither result is comfortable, and a limit that is in aggregate for the year improves neither. The answer is not to hope for one reading. It is a limit sized for the whole loss when aggregated, and an excess that does not multiply.
How the excess is worded
Some general wordings apply the excess to each claimant where a claim is brought by more than one. For a firm with thousands of members behind every instruction, that sentence matters more than the figure in the schedule.
- Claim or claimant. Whether the excess applies once to the claim or to each claimant, and whether “claimant” means the trustees, the scheme or each member.
- Annual cap. Whether the excesses you can bear in one year are capped.
- Costs. Whether defence costs carry the excess.
- IFoA licensed firms. The DPB Handbook caps both the excess per claim and the aggregate excess (IFoA DPB Handbook).
- Ombudsman awards. Some wordings give these a separate limit for the whole year. Several upheld complaints from one error can use it up. Distress awards usually run from £500 to £2,000 each (Ombudsman’s factsheet), on top of any financial loss.
Notify the cause, not the first complaint
Aggregation also bears on which policy year answers. Under a claims made policy, a circumstance that is properly notified usually attaches the later claims to the year of notification. If you notify only the first member’s complaint and then change insurer, the remaining claims may be argued to belong to neither policy.
We would notify the error itself as one circumstance: the cause, every scheme it touched, the benefit tranche, the period, the number of members and an estimate, including members who have not yet been told. Then agree the correction plan with insurers before work starts. Rectification is not automatically an insured loss, and doing it quietly at your own cost can breach the admissions condition. How we support claims
What we check at renewal
- The aggregation words, tested against your largest client and your platform.
- Whether the limit is any one claim or in aggregate, and whether it is enough for one systemic loss counted as a single claim.
- That the excess applies to each claim, not each claimant, with an annual cap where insurers will agree one.
- The Ombudsman clause: which ombudsman, what sub-limit and whether it is in aggregate.
- Cover for mitigation or rectification costs incurred with insurers’ consent.
- How you describe shared factors, templates and system settings, and your error log, so underwriters understand the controls as well as the volumes.
Hammond PI has specialised in professional indemnity since 1990. We read these clauses together before you buy, because the time to find out how your policy counts a systemic error is not the week you discover one. The clause guide
Found an error that repeats?
Call us before you start correcting it, and we will help you notify one circumstance that protects every scheme.
Speak to a PI specialistPI for actuaries and pension consultants
Related: PI for actuaries and pension consultants · The clause guide · Claims support