Reporting coverage data for RS1.1

Background

MaPS has confirmed that coverage reporting for RS1.1 is to be provided via a manual file upload, rather than being part of automated reporting by API. This means that the requirement to provide data for RS1.1 remains exactly as stated currently – as a requirement to retain records and make them available to MaPS on request.

Who must report

The reporting obligations in the reporting standards apply legally to the trustees and managers of the pension providers and schemes. However, where the pension provider or scheme has connected via a third-party connection provider, the connecting party will apply the standards by sending the data to MaPS on behalf of their client pension providers and schemes (see reporting standards paragraph 9). The connecting party is then also the reporting party. It must provide data for all its client pension providers and schemes as relevant.

All pension providers and schemes that are partially connected need to report via their connected parties.

Pension providers and schemes that have connected their relevant member records in full are not therefore required under the reporting standards to provide number of relevant member records connected.

‘Active’ holdernames refers to all holdernames added by a connecting party for pension providers and schemes (or parts thereof) that have connected – exclude those that have been registered but where the connection date is in the future. Similarly, if any holdernames have subsequently been made inactive, they should not be included in the report.

For holdernameGuids where the pension provider or scheme (or part thereof) is fully connected

For holdernames relating to pension providers and schemes that are fully connected, where data on relevant member records connected can be provided, this should be reported, and the number not connected should be set to 0. However, if membership record numbers are not available (due to the pension provider or scheme – not being subject to the requirement to report against RS1.1 – not having provided this data), the holdernames should be included as additional rows, with the general information in columns A to E provided, and the 2 RS1.1 data items (columns F and G) left blank.

How MaPS will request the data

MaPS will request, in advance, that each connected party provides data for RS1.1 for all active holdernameGuids, for data as at a particular date, to be provided by a particular date.

This is not a monthly requirement. Data should only be provided on request, and uploaded by the requested deadline.

How to submit the data

1. Download the .xlsx spreadsheet template from MaPS (this .zip file contains 'Coverage report template v1.0.xlsx')

2. Populate the spreadsheet and save it as a .csv file.

3. Upload the file via Jira using the ‘Submit coverage (RS1.1) data’ space in the PDP support portal (you will be sent a link) as per the instructions in the data request.

What data to provide

General identifiers of the connecting party, the pension provider or scheme, and the holdernameGuid

The following data items (columns A-E in the template) must always be populated in every report. This identifies the connecting party, and the pension provider or scheme (or part thereof) and the holdernameGuids. This information can be found on the ‘pension provider and schemes’ tab within the connection portal:

• Connected organisation name, such as the integrated service provider (ISP) name, or, in the case of a pension provider/scheme connected directly, the pension provider/scheme name (this is your connected party’s name and will be the same for all rows)
• Regulator (FCA or TPR) applicable to each holdernameGuid record
• Regulator number (PSR/FRN), for the pension provider/scheme (or part thereof)
• Scheme/firm name (the pension provider or scheme name)
• HoldernameGUID for the scheme/firm (or part thereof)

Coverage data for holdernameGuids where the pension provider or scheme is partially connected

Two data items are to be reported:

1. RS1.1(b) The number of relevant member records for the pension provider or scheme (or part thereof) that are connected through the connecting party (the party submitting the data).
   1. This is called ‘Member count pass’ (column F).
   2. This relates only to data for the part of the pension provider or scheme connected by the connecting party. Do not include other parts of the scheme connected via other direct connections to the ecosystem.
2. RS1.1(c) The number of relevant member records that are not yet connected through the connecting party (the party submitting the data).
   1. This is named ‘Member count fail’ (column G)
   2. This also relates only to data for the part of the pension provider or scheme connected by the connecting party.

These are to be reported per pension provider or scheme (or part thereof) and therefore must be reported at holdernameGuid level.