Notice

Undefined offset: 479

ee/legacy/libraries/relationship_parser/Parser.php, line 39

Notice

Trying to access array offset on value of type null

ee/legacy/libraries/Channel_entries_parser.php, line 165

Notice

Trying to access array offset on value of type null

ee/legacy/libraries/channel_entries_parser/Parser.php, line 386

Notice

Undefined index: entry_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 209

Notice

Undefined index: entry_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 210

Notice

Undefined index: entry_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 212

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 213

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 217

Notice

Undefined index: entry_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 217

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 255

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/components/Custom_field_pair.php, line 82

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 55

Notice

Undefined index: edit_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 56

Notice

Undefined index: recent_comment_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 57

Notice

Undefined index: expiration_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 58

Notice

Undefined index: comment_expiration_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 59

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 83

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 83

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 88

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 89

Notice

Undefined index: edit_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 90

Notice

Undefined index: allow_comments

ee/legacy/libraries/channel_entries_parser/Parser.php, line 650

Notice

Undefined index: comment_expiration_date

ee/legacy/libraries/channel_entries_parser/Parser.php, line 664

Notice

Undefined index: channel_title

ee/legacy/libraries/channel_entries_parser/Parser.php, line 524

Notice

Undefined index: channel_name

ee/legacy/libraries/channel_entries_parser/Parser.php, line 525

Notice

Undefined index: screen_name

ee/legacy/libraries/channel_entries_parser/Parser.php, line 526

Notice

Undefined index: username

ee/legacy/libraries/channel_entries_parser/Parser.php, line 526

Notice

Undefined index: photo_width

ee/legacy/libraries/channel_entries_parser/Parser.php, line 528

Notice

Undefined index: photo_height

ee/legacy/libraries/channel_entries_parser/Parser.php, line 529

Notice

Undefined index: avatar_width

ee/legacy/libraries/channel_entries_parser/Parser.php, line 531

Notice

Undefined index: avatar_height

ee/legacy/libraries/channel_entries_parser/Parser.php, line 532

Notice

Undefined index: sig_img_width

ee/legacy/libraries/channel_entries_parser/Parser.php, line 534

Notice

Undefined index: sig_img_height

ee/legacy/libraries/channel_entries_parser/Parser.php, line 535

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/Parser.php, line 536

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 553

Notice

Undefined index: entry_site_id

ee/legacy/libraries/channel_entries_parser/components/Simple_variable.php, line 63

Notice

Undefined index: channel_url

ee/legacy/libraries/channel_entries_parser/components/Simple_variable.php, line 64

Notice

Undefined index: comment_url

ee/legacy/libraries/channel_entries_parser/components/Simple_variable.php, line 65

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/components/Custom_field.php, line 54

Notice

Undefined offset: 479

ee/legacy/libraries/relationship_parser/Parser.php, line 39

Notice

Trying to access array offset on value of type null

ee/legacy/libraries/Channel_entries_parser.php, line 165

Notice

Trying to access array offset on value of type null

ee/legacy/libraries/channel_entries_parser/Parser.php, line 386

Notice

Undefined index: entry_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 209

Notice

Undefined index: entry_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 210

Notice

Undefined index: entry_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 212

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 213

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 217

Notice

Undefined index: entry_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 217

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 255

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/components/Custom_field_pair.php, line 82

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 55

Notice

Undefined index: edit_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 56

Notice

Undefined index: recent_comment_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 57

Notice

Undefined index: expiration_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 58

Notice

Undefined index: comment_expiration_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 59

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 83

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 83

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 88

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 89

Notice

Undefined index: edit_date

ee/legacy/libraries/channel_entries_parser/components/Date.php, line 90

Notice

Undefined index: allow_comments

ee/legacy/libraries/channel_entries_parser/Parser.php, line 650

Notice

Undefined index: comment_expiration_date

ee/legacy/libraries/channel_entries_parser/Parser.php, line 664

Notice

Undefined index: channel_title

ee/legacy/libraries/channel_entries_parser/Parser.php, line 524

Notice

Undefined index: channel_name

ee/legacy/libraries/channel_entries_parser/Parser.php, line 525

Notice

Undefined index: screen_name

ee/legacy/libraries/channel_entries_parser/Parser.php, line 526

Notice

Undefined index: username

ee/legacy/libraries/channel_entries_parser/Parser.php, line 526

Notice

Undefined index: photo_width

ee/legacy/libraries/channel_entries_parser/Parser.php, line 528

Notice

Undefined index: photo_height

ee/legacy/libraries/channel_entries_parser/Parser.php, line 529

Notice

Undefined index: avatar_width

ee/legacy/libraries/channel_entries_parser/Parser.php, line 531

Notice

Undefined index: avatar_height

ee/legacy/libraries/channel_entries_parser/Parser.php, line 532

Notice

Undefined index: sig_img_width

ee/legacy/libraries/channel_entries_parser/Parser.php, line 534

Notice

Undefined index: sig_img_height

ee/legacy/libraries/channel_entries_parser/Parser.php, line 535

Notice

Undefined index: entry_date

ee/legacy/libraries/channel_entries_parser/Parser.php, line 536

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/Parser.php, line 553

Notice

Undefined index: entry_site_id

ee/legacy/libraries/channel_entries_parser/components/Simple_variable.php, line 63

Notice

Undefined index: channel_url

ee/legacy/libraries/channel_entries_parser/components/Simple_variable.php, line 64

Notice

Undefined index: comment_url

ee/legacy/libraries/channel_entries_parser/components/Simple_variable.php, line 65

Notice

Undefined index: site_id

ee/legacy/libraries/channel_entries_parser/components/Custom_field.php, line 54

Warning

session_start(): Cannot start session when headers already sent

user/addons/gmaps/libraries/gmaps_library.php, line 40

Notice

Undefined variable: _SESSION

user/addons/gmaps/libraries/gmaps_library.php, line 41

Warning

session_start(): Cannot start session when headers already sent

user/addons/gmaps/libraries/gmaps_helper.php, line 565

Warning

session_start(): Cannot start session when headers already sent

user/addons/gmaps/libraries/gmaps_helper.php, line 565

Warning

Cannot modify header information - headers already sent by (output started at ee/legacy/core/Exceptions.php:120)

ee/EllisLab/ExpressionEngine/Boot/boot.common.php, line 493

Sixty Second Summary - Dashing ahead with dashboards - Hymans Robertson

Publication

Sixty Second Summary

Dashing ahead with dashboards

04 Feb 2022 - Estimated reading time: 2 minutes

The Department for Work and Pensions (DWP) has begun a consultation exercise on ‘indicative’ Pensions Dashboards Regulations 2022, detailing the obligations of occupational pension scheme trustees and dashboard providers. It proposes to introduce the obligation to connect with, and supply data to, the dashboards system in stages, starting in the summer of 2023 with schemes with at least 20,000 active and deferred members. The consultation period ends on 13 March 2022.

Scope

Based on the draft Regulations, the requirements would eventually apply to all UK occupational pension schemes that have at least 100 active and deferred members and are ‘registrable’ (that is, covered by the register of occupational and personal pension schemes maintained by the Pensions Regulator). Public service pension schemes would be captured even if they are not registrable.

In its current form, the draft provisions would:

  • prescribe the conditions that must be satisfied by a ‘qualifying pensions dashboard service’ (QPDS)—an electronic communications service, run by an FCA-authorized provider, by means of which scheme members will be able to request and obtain information about their private and State pension benefits;
  • require occupational pension scheme trustees or managers to register with the Money and Pensions Service (MaPS), connect to its dashboards infrastructure, and provide data to QPDSs;
  • contain a ‘staging profile’ establishing the deadlines by which occupational pension schemes must register and connect to the dashboards system; and
  • allow the Pensions Regulator to take action to enforce compliance.

Staged application of responsibilities

The staging profile contained in the indicative Regulations covers ‘large’ (1,000-or-more member) and ‘medium’ (100-to-999 member) schemes, and runs from 30 June 2023 to 31 October 2025. Defined contribution (DC) master trusts with 20,000 or more members (only actives and deferreds are counted for these purposes) would have to connect to the dashboards system by 30 June 2023, closely followed by DC auto-enrolment schemes with at least 20,000 members, for which the deadline would be 31 July 2023. The staging profile would then encapsulate smaller and smaller DC schemes as the months pass. Private sector defined benefit (DB) schemes with 20,000 or more members would reach their staging deadline on 30 November 2023. Public service pension schemes of all sizes would have to join by 30 April 2024.

The Regulations do not apply to schemes with 99 or fewer members, but the DWP’s consultation document says that staging of this group is likely to begin in 2026.

Trustee obligations

Very simply described, the operation of the dashboards system, from the scheme perspective, will revolve around ‘find’ and ‘view’ requests. In response to a find request initiated by a dashboard user, trustees (or more likely their administrator or other service provider) will have to interrogate their scheme’s records to see if they can identify a match with the personal data supplied by the user. This ‘find data’ will include ‘verified identity attributes’ checked by the MaPS—name, home address and date of birth—and ‘self-asserted data’, such as the person’s phone number, email address and National Insurance number. The trustees will have to decide the criteria to be used for matching (the Pensions Administration Standards Association has produced guidance that is likely to become a benchmark for the industry).

When a match is made, trustees would need to confirm via MaPS that the member has consented to having their data provided to a dashboard service. If so, the trustees would have to provide ‘view data’ to the dashboard that issued the view request. View data comprises—

  • administrative data’—scheme name, benefit type, membership status, date of joining, normal pension age, contact details for the scheme administrator, and (if available) details of the member’s pensionable employment(s);
  • signpost data’—the website address for any information that trustees must disclose publicly online (details of costs and charges, the statement of investment principles, and the associated implementation statement); and
  • value data’—current and projected benefits.

In response to a view request, administrative and signpost data would have to be provided immediately, except when sought by a new member who is within three months of joining the scheme, in which case the administrative data must be provided within three months of the joining date. There would also be associated record-keeping and reporting obligations.

Value data

There are detailed requirements for value data, which are different depending on the type of benefit. All value data for the member must have a single illustration date, and must be from either a statement that was given during the preceding twelve months or a calculation performed within the same period. It must be accompanied by ‘contextual information’ such as the illustration date; whether the values are expressed as regular income, lump sums or pot values; whether there are associated dependants’ benefits; and whether the benefits would increase in payment.

Value data taken from a past statement or calculation must be given immediately. If, instead, the calculations are performed ad hoc in response to the view request, the trustees have ten working days in which to respond if theirs is a non-money purchase scheme, and three working days otherwise (we are not sure that the drafting gives effect to the policy intention ). The DWP says that it is ‘keen for these proposed timings to be reduced’ and intends 'to move towards instantaneous responses for all requests [involving money purchase schemes] in the future.'

Guidance

The draft Regulations also make provision for mandatory standards set by the MaPS, on data usage, design, reporting, and technical matters, plus a guide to a 'code of connection' that will cover security, service and operational issues. The Pensions Dashboards Programme (PDP), convened by MaPS, has published some guidance on the proposed scope of those standards, how it will go about setting them, and what they might contain. It has also issued invitations for a series of consultation-related webinars to be hosted by the DWP.

As well as re-uniting people with lost pensions, the dashboards will help to equip savers with the information that they need to plan for the best possible retirement. The 28 pages of draft legislation and 137-page consultation document will leave no-one in any doubt about the complexity of this important undertaking. We anticipate that it will take some time to work the kinks out of the proposals, with staging dates in the summer of 2023 already looming large.

Sixty Second Summary - Dashing ahead with dashboards

Download

Subscribe to our news and insights

0 comments on this post