Early warning system alerts regulator to possible calls on PPF

The Pensions Regulator's timetable for bringing into effect its code of practice on notifiable events was disrupted by the general election. Although trustees and employers have been required to act in accordance with the draft code since April, it has only just received formal parliamentary approval. We examine its provisions.


Summary of key points

The Pensions Regulator's second code of practice, on notifiable events, has now been approved by parliament, although trustees and employers have been required to comply with its provisions since 6 April 2005.

The code imposes a new duty on trustees, managers and employers to advise the regulator if specified events occur.

The purpose of the code is to alert the Pensions Regulator to the risk of possible calls on the PPF, by requiring notification of a number of matters that may be an indication of future funding difficulties.

Notifiable events are divided into those that are scheme-related and those that are employer-related. In some instances the duty does not apply if the scheme is funded above the PPF buyout level and scheduled contributions are being paid.

The code explains the background to the notifiable events and details the procedures to be followed. The events themselves are set out in Regulations and exceptions to the duty are contained in separate directions issued by the regulator.

Among the less well publicised casualties of the calling of the general election was the Pensions Regulator's code of practice on notifiable events. Although consultation on the code had been completed, it was not approved before the dissolution of parliament. With the Pensions Act 2004 requiring that the final version of each of the regulator's codes be laid before parliament for 40 days, it is only now that the code* has been approved.

This presented the regulator with something of a dilemma because the Regulations and directions that itemise the notifiable events and exceptions referred to in the code actually took effect on 6 April 2005. To deal with this problem, the regulator issued a letter explaining the delay and advising schemes that, until the code was approved, they must refer to the draft laid before parliament for guidance. Luckily for the regulator, no changes were made to the substance of the draft during the approval process.

Unlike the statutory duty to report breaches of the law (See New whistleblowing code ), which is an extension of an existing duty, the duty to notify the regulator about certain events is newly imposed by the Pensions Act. The purpose of the duty is to assist the regulator in meeting its statutory objective of reducing the risks of situations arising that may lead to calls on the Pension Protection Fund (PPF).

The company and scheme events that have to be notified are ones that could suggest forthcoming financial difficulties that might result in the PPF having to assist a scheme. However, the code points out that, taken in isolation, a notifiable event gives no indication of the financial position of an employer or of its pension scheme. Given its purpose to safeguard members and the PPF, the duty only applies in respect of schemes that are in scope to the PPF - ones that provide defined benefits or that have a defined-benefit (DB) element, such as hybrid schemes.

Once the regulator receives a report made in accordance with the provisions of the code, it then assesses the risk to the scheme. It will use other information, such as that included in the annual return, to determine its response. If it believes a scheme to be at risk, it has a range of actions available, including imposing improvement notices or appointing an independent trustee.

Extensive requirements

Depending on the circumstances, the duty to notify the regulator of certain events falls on scheme trustees, both collectively and as individuals, managers of schemes and employers. Notifiable events fall into two categories: those that must be notified by trustees (or managers) and those that must be notified by employers. Unfortunately, in order to determine which events are notifiable, those with the duty must look outside the code to the Regulations to find details.

The regulator explains that it has adopted this approach to provide greater flexibility. If the notifiable events and exceptions were contained within the code, the code would have to go through the full consultation and approval procedure every time the notifiable events are amended.

Box 1 summarises the current list of events that must be notified to the regulator. As can be seen, the list is extensive. Some respondents to the consultation commented that the code increases the regulatory burden on DB plans, giving rise to the risk that some employers will pull out of this type of provision.

However, the number of notifiable events is fewer than originally proposed. The consultation report gives details of the events that have been removed from the final list. These include a requirement to notify the regulator if more than a certain number of employees are made redundant, and also if there is a significant reduction in the number of scheme members. Respondents took the view that neither event indicated that a call on the PPF would result from such actions. Furthermore, small schemes might have needed to notify the regulator when two or three members left, as this could be a "significant reduction".

Confidentiality

Some organisations are concerned that their share price could be affected if they have to reveal some of the information required by the regulator within the given time limits. The regulator is aware of these difficulties, but insists that the duty on trustees and employers to notify overrides any other duty of confidentiality. It points out that events it is notified of do not have to be announced publicly or, in many instances, even to shareholders.

In defence of its stance on notification, it points out that:

  • the provision of information should be regarded as a normal part of a scheme's interaction with the regulator;

  • the duty is not, in the majority of cases, triggered by any wrongdoing; and

  • in isolation, the occurrence of a notifiable event gives no indication of the financial position of either the employer or the scheme.

    In spite of these reassurances, it is likely that some companies will feel that the confidentiality of their business activities is threatened.

    Exceptions to the rule

    Under the provisions of the Pensions Act, the regulator has the power to make directions concerning the circumstances in which trustees, managers or employers do not have to report a notifiable event.

    Version 1 of the directions took effect from 6 April 2005. These too have not been included in the code itself in order to maintain flexibility. The label "version 1" suggests that the regulator is likely to make more changes in this area as its experience of the practical effects of the code expands.

    Box 2 summarises the current exceptions to the duty to report certain events. Although not couched in these particular terms, effectively the regulator does not need to be informed that a notifiable event has occurred in most instances if the scheme is funded above PPF buyout level and the schedule of contributions has been adhered to. However, there are some events that the regulator should be notified of, regardless of the funding position of the scheme. These are specified in box 1.

    Timing of notifications

    The regulator expects to be notified of events in writing "as soon as reasonably practicable". This term is explained in more detail in the code of practice on reporting breaches of the law (See New whistleblowing code ). In the notifiable events code, the regulator confines itself to commenting that in all cases the term implies urgency.

    It also points out that this means that procedures for notification will need to be in place outside the usual framework for discussion of pension matters, such as quarterly trustee meetings. Procedures will also be required to ensure that administrators alert trustees and managers when something occurs that requires a report to be made.

    According to the regulator, the list of events has been worded so as to indicate the timing of the notification. Hence, the regulator has to be advised of some events when the relevant decision has been made. But others, such as changes in key personnel, often need only be notified after the event. Unlike the duty to report breaches of the law, where a view sometimes has to be taken on whether the circumstances warrant a report, the regulator believes that notifiable events should be easy to identify.

    Notifications must be made in writing, using wherever possible the standard form available on the regulator's website. Those under the duty to notify the regulator of certain events must comply with that duty unless they have reasonable excuse not to do so. If there is a failure to notify, the regulator will assess this failure by reference to whether an objective person would consider this reasonable (although the wording of the test is slightly different for employers and trustees).

    If the regulator believes that there has been a failure to comply with the duty, it has a range of possible responses available to it, from organising training for trustees to imposing civil penalties. It may take a failure to notify into account when deciding whether to issue a contribution notice.

    Properly prepared

    In order to meet their obligations under the notifiable events code, the regulator points to three practical action points for trustees and employers. They should:

  • ensure that they are aware of the full list of notifiable events applicable to all schemes;

  • know which of those events would, if they arose under their scheme, have to be reported to the regulator (that is, they need to know if any of the exceptions contained in the directions apply to their scheme); and

  • have procedures in place that will enable identification and notification of events to occur.

    * "Regulatory code of practice 02: Notifiable events", available from the Pensions Regulator's website (www.thepensionsregulator.gov.uk ) via "Codes and guidance", "Codes of practice" and then "Codes in force".

    Pensions Regulator (Notifiable Events) Regulations 2005 (SI 2005/900) and "Directions issued by the Pensions Regulator under s.69(1) of the Pensions Act 2004. Version 1 - dated 6 April 2005", both available from the same page of the Pensions Regulator's website as the code (see above).


    Box
    1
    : Events that must be notified to the Regulator

  •         
  • A decision by the scheme trustees or manager, or by any employer under the scheme, to take any action which will, or is intended to, result in any debt which is, or may become, due to the scheme not being paid in full*.

  •         
  • Two or more changes of appointed auditor or actuary to the scheme, or of chief executive, or any director or partner responsible for the financial affairs of the employer, within the previous 12 months.

  •         
  • A decision by the trustees or managers of the scheme either to make or accept a transfer payment, the value of which is greater than 5% of the value of the scheme assets (or £1.5 million if less).

  •         
  • A decision by the scheme trustees or managers to award benefits, or promise benefits for the future, that are better than those provided under the scheme rules, either without seeking actuarial advice or without obtaining additional funding after being advised so to do by an actuary*.

  •         
  • A decision by the trustees or managers to award benefits or rights to benefits to a member where the cost of the benefit is greater than 5% of scheme funds (or £1.5 million if less).

  •         
  • A decision by the employer to cease carrying on business in the UK*.

  •         
  • A decision by the controlling company to relinquish control in an employer under the scheme.

  •         
  • The conviction of a person for an offence involving dishonesty if it occurred while the individual was a director or partner of a company under the scheme*.

  •         
  • Any change in, or ceasing to have a, credit rating.

  •         
  • The breach of a covenant between an employer and a bank or similar institution, unless the latter agrees not to enforce the covenant.

  •         
  • Receipt of advice that an employer is trading wrongfully, or that liquidation due to insolvency cannot be avoided*.

    * These events do not come within any of the exceptions contained in directions issued by the regulator (see box 2).

    Source: Pensions Regulator (Notifiable Events) Regulations 2005 (SI 2005/900).



    Box 2: Exceptions to the requirement to notify the Regulator of certain events


    Direction 1: If the scheme's assets are at least equal to its liabilities calculated on the relevant basis (effectively the PPF buyout basis) and the trustees or managers have not had to comply with the duty to report any failures by the employer to make payments within the previous 12 months, they do not have to notify the regulator of the following:

  •         
  • two or more changes in key posts;

  •         
  • transfers in and out of the fund of more than 5% of the fund value (or £1.5 million if less); or

  •         
  • the granting of benefits, the cost of which exceeds the limits above.

    Direction 2: Trustees and managers do not have to notify the regulator of a decision that results in a debt not being paid in full if:

  •         
  • the scheme is not in deficit (as in direction 1);

  •         
  • no duty has arisen within the previous 12 months to report late or non-payment of monies including contributions; and

  •         
  • the amount of the debt is less than 0.5% of the scheme's assets.

    Direction 3: Employers are not required to notify the regulator that there has been (a) a breach of a banking covenant, (b) a decision by a controlling company to relinquish control, or (c) two or more changes of key posts, if:

  •         
  • the scheme is not in deficit (as in direction 1); and

  •         
  • no duty to report late or non-payment of contributions has arisen within the previous 12 months.

    Direction 4: If the two conditions set out in direction 3 are met, the employer does not have to report changes in, or the loss of, a credit rating, provided that the change is not from investment to sub-
    investment grade, and the rating is provided by a recognised credit rating agency.

    Source: Directions issued by the Pensions Regulator under s.69(1) of the Pensions Act 2004, version 1 - dated 6 April 2005.


    O
    ur research

    This feature is based on Code of practice no.2: Notifiable events, the Pensions Regulator (Notifiable Events) Regulations 2005 (SI 2005/900) and version 1 of the directions issued by the Pensions Regulator. It also draws on a press workshop held by the Pensions Regulator on 4 July 2005.