The Government has restated its commitment to delivering pensions dashboards in a written statement.

Skip to content
Pensions dashboards programme logo
  1. Home

Connect via a third party

For pension providers and schemes connecting via a third-party connection provider, such as an integrated service provider or third-party administrator.

Step-by-step connection journey

The following steps show an overview of how pension providers and schemes connect to the live environment via a third-party connection provider.

A diagram demonstrating the process of connecting to the pensions dashboards ecosystem via a third party
Step-by-step connection journey description

Connection provider: Advise pension provider or scheme when to apply or expect codes.

Step 1 – pension providers and schemes connecting via a third-party connection provider: Receive registration codes from your regulator.

  • The Pensions Regulator (TPR): Issues codes 3–5 months before the ‘connect by’ date.
  • Financial Conduct Authority (FCA): Issues codes after receiving an application.

Step 2 – pension providers and schemes connecting via a third-party connection provider: Choose preferred connection date.

Step 3 – pension providers and schemes connecting via a third-party connection provider: Give registration code to your connection provider.

  • Connection provider: Register pension provider or scheme with PDP for connection.
  • Pensions Dashboards Programme (PDP): Check codes are valid and confirm connection date.
  • PDP: Connect pension provider or scheme on agreed date.
  • Connection provider: Confirm connection via connection portal.

Step 4 – pension providers and schemes connecting via a third-party connection provider: Complete connection.

1. Receive registration codes from your regulator

You need a unique registration code from your regulator to register each connection you make to the pensions dashboards ecosystem.

If you are connecting via more than one connection provider, you need a unique registration code for each.

For example, if your scheme operates a defined benefit (DB) and a defined contribution (DC) section which sit with different third-party administrators with different connection routes, each third-party administrator will need a unique registration code. However, if both third-party administrators use the same connection provider independently of each other, the connection provider will use one registration code.


From the Pensions Regulator (TPR)

You don’t need to request your first registration codes.

TPR will issue 2 registration codes to the scheme’s primary dashboards contact. This is usually the Chair of Trustees, the trustee nominated for pensions dashboards, or the scheme manager.

If you need additional codes, or wish to connect before the codes are issued, contact TPR’s customer support: [email protected].

TPR will issue registration codes around 3 to 5 months before a scheme’s expected ‘connect by’ date.

The registration code will expire shortly after your ‘connect-by’ date. When you receive the codes, you will be told when they expire.

Read TPR’s guidance on registration.


From the Financial Conduct Authority (FCA)

You must apply to the FCA for registration codes as a pension provider subject to the FCA’s Conduct of Business Sourcebook (COBS) 19.11.

The FCA will issue 2 registration codes to your Senior Management Function of Compliance Oversight (SMF16).

If you need additional codes, you can use the FCA application form.

The organisation you are connecting through will tell you when the registration code is needed to meet your agreed connection date.

FCA registration codes are valid for 30 days once issued.

Consider your connection date and whether your SMF16 will be available during these 30 days. Your connection provider will not be able to add pension providers using registration codes until they have successfully completed all connection steps, including operational acceptance testing (OAT).


Replacement registration codes

If you need to replace a registration code, for example, if your code expires, contact your regulator:

2. Choose preferred connection date

Consider your preferred connection date, having regard to your ‘connect by’ date set out in the Department for Work and Pensions (DWP) guidance on connection: the staged timetable.

You should agree a proposed date with your connection provider. PDP recommend you choose a working day for your preferred connection date.

Connection providers cannot add pension providers or schemes using registration codes until they have successfully completed all connection steps, including operational acceptance testing (OAT).

3. Give your registration code to your connection provider

Once you have your registration code, you need to give it to your connection provider. This should be done through a secure communication channel. Your connection provider can advise on the timing of this.

Ensure your connection provider has the following information:

  • your regulator number, either:
    • the Firm Reference Number (FRN) from the Financial Conduct Authority (FCA)
    • the Pension Scheme Registry (PSR) number from The Pensions Regulator (TPR)
  • the registration code
  • preferred connection date

Your connection provider will submit your preferred connection date and pension provider or scheme information (including registration code) to PDP via the connection portal.

PDP will review the connection date and aim to respond within 5 working days.

If for any reason PDP needs the provider or scheme to connect on a different date, PDP will liaise with the connection provider to agree an alternative date. This could be due to planned maintenance, for example.

Once a connection date has been approved, you are ready to complete your connection.

4. Complete connection

On the agreed and approved connection date, PDP will connect you to the live environment.

PDP shows when the connection is active via the connection portal. You can liaise with your connection provider on how to get confirmation of this.

Once the connection is confirmed as active, legal duties for the pension provider or scheme begin.

If for any reason connection to the live environment has not been successful, PDP will liaise with the connection provider to agree a new date.

Change connection plans

If you are planning to connect more than 30 days earlier or later than your ‘connect by’ date, it is recommended you notify PDP and your regulator of those plans.

Pension providers and schemes, or third parties acting on their behalf, can do this online.

Change connection plans

How to connect voluntarily

Some smaller schemes with fewer than 100 relevant members are out of scope of the Pensions Dashboards Regulations 2022 and do not have to connect to the pensions dashboards ecosystem. However, they may wish to connect voluntarily.

This process is in development and will be published in due course.

Changelog

15 April 2025

  • Added guidance that connection providers cannot add pension providers or schemes until they have successfully completed all connection steps, including operational acceptance testing (OAT). This should be considered in relation to registration code expiry and choosing connection dates.

20 March 2025

  • Added link to published 'Change connection plans' guidance.

11 March 2025

  • In '4. Complete connection', removed reference to taking a screenshot to confirm connection. Pension providers and schemes can liaise with their connection provider on how to get confirmation of this.

28 February 2025

  • In '3. Give your registration code to your connection provider', removed reference to the name being 'as registered with their regulator'. The name used here is not validated.

25 February 2025

  • In '1. Receive registration codes from your regulator', added clarifcation to the example of when more than one registration code is needed.