Reporting standards update: what this means for you

If your organisation is in scope for pensions dashboards, you need to understand what's changing in how operational data is reported to MaPS, and what that means for your implementation planning. We have published draft version 2.3 of the reporting standards, which sets out the technical requirements for submitting this data daily via API.

Read on to find out how this draft version relates to the approved reporting standards, the intended implementation deadline, and what you should be doing now to prepare. This is relevant to trustees and scheme managers responsible for complying with the reporting standards, and to the third-party connection providers who support their implementation.

What the reporting standards are

The reporting standards set out requirements for generating, recording and reporting operational information to the Money and Pensions Service (MaPS). This supports MaPS's oversight and management of the pensions dashboards ecosystem, as well as the regulators' functions around compliance monitoring and enforcement.

The reporting standards are one of 4 sets of standards that apply to pension providers and schemes required to connect to the pensions dashboards ecosystem. The others are the technical standards, data standards and the code of connection. The reporting standards should be read alongside these.

What ‘draft’ means

Version 2.3 of the reporting standards sets out the detailed technical requirements for reporting data to MaPS daily via API. It is described as a draft because it is yet to be formally approved by the Secretary of State for Work and Pensions and the Department for Communities (Northern Ireland), in the same way version 2.0 was described as a draft before it was formally approved in March 2025.

We do not expect further substantive changes to version 2.3 ahead of approval. Once approved, it will become the new legally binding version of the reporting standards, replacing version 2.0, with a coming-into-force date of 1 March 2027.

What organisations should be doing already

Pension providers and schemes must currently collect and retain the data items specified in version 2.0, relating to coverage, service availability and view responses, and make this available to MaPS on request.

We have now requested this data be reported to MaPS as a monthly manual report, via file upload, until daily reporting via API is implemented. Organisations may refer to the guidance on manual reporting for details of what to submit and how.

Ad hoc reporting of coverage data on request under RS1.1 continues until 1 November 2026.

What organisations need to do between now and March 2027

Version 2.3 sets out the technical requirements for implementing daily reporting via API, together with the accompanying API schema. We expect all directly connected organisations (DCOs) to work with us to implement this voluntarily, ahead of the mandatory deadline of 1 March 2027, which is subject to approval by the Secretary of State for Work and Pensions and the Department for Communities (Northern Ireland). You can read more about this in our consultation response.

Integration testing is already underway, and directly connected organisations are now in the process of implementing daily reporting ahead of the deadline. If your organisation connects directly and has not yet begun this process, you should submit a technical change request as soon as possible to begin testing and integration. Given the scale of the technical work involved, including building and testing your connection to the reporting API, we would encourage you not to leave this until close to the deadline.

If you connect via a third-party connection provider, you should check with them that they are on track to implement daily reporting ahead of the deadline.

Once daily reporting via API has been implemented, in line with version 2.3, no additional monthly manual reporting is required.

What will be required from March 2027

Once version 2.3 is formally approved, daily reporting of data to MaPS via API, as set out in that version, will become a legal requirement. This will replace the current arrangements for ad hoc and manual reporting.

Further information

As a trustee or scheme manager, you remain responsible for compliance with the reporting standards even if your organisation connects to the dashboards ecosystem via a third-party connection provider, such as an integrated service provider (ISP) or administrator. It is important to understand the standards and how they apply to your organisation, and to work closely with your connection provider on implementation plans.

You can read draft version 2.3 of the reporting standards and the legally binding version 2.0 for full details of the requirements. If you have questions about implementing the reporting standards or need further help, you can also get in touch with us via support.