Pensions Regulator Defined Benefit Funding Code of Practice 2024

Lord Davies of Brixton Excerpts

Monday 21st October 2024 Grand Committee

Moved by

[Lord Davies of Brixton]

That the Grand Committee takes note of the draft Pensions Regulator’s Defined Benefit Funding Code of Practice 2024, laid before the House on 29 July.

Relevant document: 2nd Report from the Secondary Legislation Scrutiny Committee

[Lord Davies of Brixton (Lab)]

I always appreciate a challenge, and I was quite interested to note that our Whips have got the idea that this debate will last half an hour, but I will not take up the whole 30 minutes.

First, I have to declare an interest: I am a fellow of the Institute and Faculty of Actuaries, or IFoA as it is now. Many members of the institute provide advice on funding of defined benefit or DB schemes, and they will be significantly affected by the code that is before us. However, I add with some emphasis that I no longer practise as an actuary, hence nothing of what I say must be regarded as constituting actuarial advice. It might sound like actuarial advice, but I assure those here that it is not; noble Lords have to get their own advice rather than take it from me. Nevertheless, I speak from experience as a scheme actuary who has undertaken scheme valuations including, in the past, under the Pensions Regulator or previous iterations.

We are talking about the regulator’s defined benefit code of practice—the code—issued under Part 3 of the Pensions Act 2004. I very much welcome the opportunity to make a few remarks about the code and to ask my noble friend the Minister some questions.

TPR has been producing codes of practice on funding going back to 2006, but it is worth pointing out that it first consulted on this iteration of the funding code more than four years ago, in March 2020, with a second attempt in December 2022. This version was published for consultation in March this year, so its final form comes after years of waiting and four Prime Ministers; the whole Covid epidemic; a significant shift in the financial position of many defined benefit schemes, with increased investment returns in particular; considerable discussion about how these funds should be invested in the light of the Mansion House reforms under the last Government; the pension review under this Government; and, not least, an increased appreciation of the risks to defined benefit schemes from climate change. So much has happened and the code has, in effect, had to hit a moving target. Unfortunately, I would argue that even this version has not really caught up with developments and events.

The new code, together with the Occupational Pension Schemes (Funding and Investment Strategy and Amendment) Regulations 2024, which we discussed in this Room last March and which came into force in April, gives trustees and advisers most of the tools and processes to follow for DB funding valuations with a valuation date on or after 22 September 2024. There has been a bit of time-shifting going on here, but it is not a concern. It is clear that there will be specific areas of the code where further clarification is required, which will be found out only in practice.

I will not repeat everything I said in March, but I want to emphasise my main point. I was talking about the regulations, but it applies to the code as well:

“The regulations are patently too prescriptive. The details that they require are not directed at the objective of protecting members’ benefits but are about establishing a system where box-ticking will take priority over the longer term and broader interests of scheme members”.—[Official Report, 26/3/24; col. GC 165.]


This version may well be better than earlier drafts but, given that the code is already in effect in practice, it should be understood that it is only one stage of the longer-term reassessment that is required, given the continued pace of developments in this sphere. We should not be under the delusion that this constitutes a job done.

There are positives that I want to recognise. The DWP tells us that the draft code has been revised to strike a balance between setting clear funding standards and maintaining flexibility for scheme-specific approaches. The move to a more principle-based rather than prescriptive approach to areas such as the low dependency investment allocation and assessment of the covenant is helpful and gives the trustees some flexibility. Other commentators have welcomed the redefinition of what constitutes significant maturity; clarification of what happens when the valuation is based on notional investment rather than actual investment; greater clarity on how to assess the employer covenant; and—this is particularly important—what applies when there are surplus assets. It is to be welcomed that the final version includes a section for open schemes, collating the guidance that is relevant to them across the code.

Nevertheless, the code remains a work in progress. The IFoA has said:

“The totality of the changes being introduced by the new code remain complex”,


and that there are still a few more steps on the journey to take. It says that it hopes

“the regulator will adopt a pragmatic approach when considering the first valuations under the new regime, due to the short implementation period for the final rules”,

emphasising the point that this is a work in progress.

My major concern remains that here we have 100 pages of detailed instructions and rules, albeit with quite a lot of repetition, not just on how to undertake a valuation under the terms of the legislation for a defined benefit scheme but about how such a fund should operate, particularly in the field of investment. It passed through my mind to go through the document quoting the minutiae that is dealt with—for example, telling us that we have to use a Macaulay duration calculation. I have resisted that temptation—I do not wish to delay people too much—but I have no doubt that the requirements, while well intentioned, are excessive. Although there are references to proportionality, what will happen in practice is that the code will suffer from what is described as procedural drift, where individuals become overreliant on routine processes, potentially leading to reduced understanding of the overall decision: failure to see the wood for the trees.

The underlying belief, as far as I can tell, is that detailed prescriptions and requirements are better than general principles. I do not know what evidence there is for such a belief. Is it true that detailed prescriptions and reporting requirements along the lines set out in the code make it any more likely that members will receive their benefits? I doubt it. As an overriding principle, given the inherent uncertainty about any attempt to forecast the future, there is no reason to believe that making an algorithm more complex improves the outcome.

One problem that concerns me, which I raised in the debate in March, is how the code reacts with Technical Actuarial Standard 300: Pensions. TAS is set by the Financial Reporting Council and lays down how any actuary in the UK should undertake technical actuarial work required by legislation to support decisions on funding, contribution requirements and benefit levels. I have the latest version here; it came into effect in April. The point is that the actuary who undertakes the valuation at the request of the trustees must comply with the professional standard. However, we are in the peculiar position where the code makes no reference to TAS, and TAS refers only by implication to the requirements of the code in an appendix.

It is a matter of concern that the 18 pages of TAS, only four of which refer to scheme funding, make more sense than the 100 pages in the code. What exactly in the code achieves anything that is not already achieved by those four pages in TAS 300? We are told that in its review of TAS 300, the Financial Reporting Council has deferred consideration of the provisions on funding and financing until the new legislation on funding and TPR’s revised code of practice are in place. I am not convinced that this will work. There must be a real question about who is responsible for setting technical standards on funding DB schemes—the Financial Reporting Council or the Pensions Regulator. Judging by the record, my vote goes to the Financial Reporting Council.

Having made that general point, to which I will no doubt return in future, I have three specific questions about how the code will deal with continuing developments in DB pensions. First, there must be a question of whether the code deals with whatever comes out of the first stage of the pensions review. We have been told that the first stage is due to report in the next few months and will consider further measures to support the pensions Bill. It will take account of the need to prioritise gilt market stability, liquidity and diversity. The objective, we are told, is to boost investment, increase saver returns and tackle waste in the pensions system. The problem is that this objective is not reflected adequately in the code. How and when will these issues be reconciled? How will what comes out of the pensions review be reconciled with what has been established in the code?

The second question arises from the improved state of DB funding, which has led to more schemes being run on—continuing rather than moving quickly to buyout. Because schemes will be running on and must, under the code, have the objective of being fully funded, this raises a question: when schemes move into surplus, what rules apply to that surplus? In discussions that people have initiated since we have seen the improvement in scheme funding, it has been suggested that schemes with a material surplus may invest in a greater allocation to growth assets. This aligns with the policies I have just referred to—of both the previous and the new Governments—which emphasise investing for UK growth. That objective is not adequately reflected in the code. In addition to the issue of investing surplus, there are other possible results of improved financial conditions for DB schemes. Not least of them is the possibility of improvements in members’ benefits, either through trustees exercising the discretionary powers that many of them have or through rule changes.

In the same way, some people are talking about the possibility of powers being used to refund sponsoring employers or to use the surplus in the scheme to cover the cost of accruing benefits. Unfortunately, the Pensions Regulator appears to have given insufficient thinking to such developments and to how its powers will be exercised when confronted with such issues. The code does touch on the issue, talking about covenant leakage but in a way that is clearly inadequate when faced with the challenges that will arise from these moves. Will the Government press the Pensions Regulator to give the issues that arise from the potential existence of scheme surplus further thought and more adequate thinking? I have already complained that the code is too complex. I am not suggesting that this should be in the code, which is complex enough, but it is an area to which the Pensions Regulator has to give considerably more thought, so that we know where it is coming from when confronted with these issues.

The third issue, which I will cover swiftly as we will debate it again on Thursday, is the impact of climate change. The code touches briefly on the issue, in paragraph 23 of the application module, but it is an issue on which the Pensions Regulator has to take much more of a lead. Will the Government encourage the regulator to pursue what needs to be done to enable schemes to confront the challenge of the greater risks that face the financial system, including defined benefits schemes, as a result of global warming?

--- Later in debate ---

I think I am probably running out of time as I am getting a nod from the Whip. I am sure I have missed questions, and I apologise for having done that. I am grateful to all noble Lords for taking the time to discuss something in this depth, with such technical competence and in such detail. I hope I have been able to inform and reassure the Committee about the code and our wider strategy. I look forward to us continuing this debate in years to come. We all want to make sure that members who have saved long and hard for their pension get the benefits they have been promised and to which they are entitled. I hope this will be a contribution to that process.

[Lord Davies of Brixton (Lab)]

I thank the Minister for her long and detailed response. I think I need to use the formula used by Ministers: “I will read the entry in Hansard”. There was so much information in it, for which I thank her. I also thank noble Lords who came for the debate on Russian sanctions; I hope they found it informative to hear about pensions.

The phrase that had particular resonance with me was that used by the noble Baroness, Lady Altmann: “spurious accuracy”. When I was a trainee actuary, we were told specifically that making calculations more complex and difficult did not make them any better. Trying to forecast the future is difficult enough. Making complex calculations does not improve the outcome for members.

My major point is that current developments in pensions will require the code to be kept under review in any event, whether they are an increasing appreciation of the risks of climate change or the development of pension scheme surpluses. I welcome the remark about that. These changes accumulate and I hope that the Minister will enjoy further debates and discussions. I look forward, in particular, to the pensions Bill. Not many people say that, but I think we will have some interesting debates.

Motion agreed.