APRA Retirement Reporting Framework: What Super Funds File

ByOfficer

Last updated: June 2026

The trap in APRA’s Retirement Reporting Framework is the calendar, not the forms. The proposed new collection has a first reporting period of the year ending 30 June 2027. That sounds far away until you notice what it means in practice: a registrable superannuation entity (RSE) licensee has to be capturing member-level retirement data from 1 July 2026 to have a complete year to report. A fund that waits for final standards before building its data pipeline will be reconstructing a year it never measured.

On 23 March 2026 the Australian Prudential Regulation Authority opened consultation on how to give effect to the Government’s Retirement Reporting Framework through APRA’s reporting standards. Written submissions closed on 3 June 2026. The proposals do not change the substance of any trustee’s retirement income strategy. They change what data that strategy has to surface, in what shape, and on what schedule.

This is a transparency reform built on top of the existing Retirement Income Covenant, not a new conduct obligation. The reporting officer’s job is to make sure the member data dictionary, the systems that feed it, and the assurance sign-off are all ready before the first reporting period closes.

Related reading: our analysis of the ASIC DFCRC RegTech innovation work.

What the APRA Retirement Reporting Framework changes

The Retirement Reporting Framework itself is a Government reform. Treasury published the final framework design in February 2026, setting out the indicators and metrics APRA will eventually publish from 2028 onwards, with data first collected in 2027. APRA’s March 2026 consultation is the mechanism: the reporting standards that turn those indicators into actual data fields a fund has to file.

Four reporting standards sit in the package. APRA proposes to make a new standard, SRS 611.1 Retirement Member Profile, to collect the demographics and actions of members approaching or in retirement. It proposes to revise SRS 607.0 RSE Business Model to capture fund-level offerings such as drawdown options, lifetime income products and member support. It proposes to revise SRS 101.0 Definitions for Superannuation Data Collections so the shared data dictionary covers the new terms. And it proposes to revoke the existing SRS 610.0 Membership Profile to avoid duplicating what the new collection captures.

Each standard is made under subsection 13(1) of the Financial Sector (Collection of Data) Act 2001. That is the same statutory hook behind every APRA superannuation return, which matters for one reason: a reporting standard determined under that Act is binding once registered, and the data has to be the product of systems an RSE auditor has reviewed and tested. This is not a voluntary survey.

SRS 611.1 Retirement Member Profile: the new form

SRS 611.1 is the heart of the package and the one most teams will underestimate. It collects member counts, members’ benefits and payments for members who were aged 60 and above at the end of the reporting period, broken down by member age, sex and a members’ benefit bracket that runs in bands from under $1,000 up to $2,000,000 and above. Alongside the demographics, the form asks which account types a member holds: accumulation, transition to retirement, account-based pension, allocated pension, lifetime income, or another retirement income stream.

The draft splits into three tables: Table 1 Member Profile and Income, Table 2 Accumulation Member Actions, and Table 3 Pension Member Actions. The reporting form must be completed by each RSE licensee for each RSE within its business operations, and the data has to be authorised by the Chief Executive Officer or Chief Financial Officer and digitally signed.

Where teams get this wrong is treating SRS 611.1 as a headcount return. It is a behaviour return. Tables 2 and 3 ask what members actually did, account closures, drawdowns, the actions that show whether a fund’s retirement strategy is moving people into income products. You cannot derive that retrospectively from a balance snapshot. The capture has to be designed into the member administration system before the year starts.

When the data is actually due

APRA’s stated timeline targets final reporting standards in Q3 2026 and first data collection in Q4 2027. The draft standards put hard edges on that. For SRS 611.1, the first reporting period is the year ending 30 June 2027, with data due within three months after the end of the reporting period. SRS 607.0 adds a new annual table for retirement income solution member support, also first reportable for the year ending 30 June 2027. SRS 101.0 is drafted to apply to reporting periods ending on or after 30 June 2027.

Read those dates together and the operational point is blunt. To file a complete year ending 30 June 2027, a fund needs the data flowing from 1 July 2026. The consultation deadline of 3 June 2026 was about shaping the standards. The build deadline is the start of the financial year that follows. Anyone running an Australian regulatory data build will recognise the pattern from the AUSTRAC and ASIC reporting cycles, where the capture window quietly opens long before the first submission is due, an issue we covered in our look at AUSTRAC’s 2026 financial crime risk snapshot.

Who reports and who is carved out

Consistent with the Retirement Income Covenant, the collection applies to all RSE licensees. There is one carve-out worth flagging early because it is easy to get wrong in the data layer. Members whose interests can be excluded from the retirement income strategy requirements under subsection 52AA(3) of the Superannuation Industry (Supervision) Act 1993, broadly, defined-benefit-only interests, are excluded from the SRF 611.1 collection. A fund that pulls every member aged 60 and above without filtering that exclusion will overstate its population.

This is also where the framework’s purpose and its mechanics can be confused. The collection does not replace the covenant obligation in section 52(8A) of the SIS Act. Trustees still have to formulate and implement a retirement income strategy. The framework simply gives APRA, and eventually the public, a consistent way to see what funds are offering and how members are behaving, so that variability between funds becomes visible.

What the framework does not do

One line in Treasury’s framework design deserves to be read twice: the Retirement Reporting Framework is a transparency reform and will not introduce new consequences or penalties for superannuation trustees. That changes how a reporting team should scope the work. The risk here is not a fine for a poor retirement outcome. The risk is filing a return your auditor cannot stand behind, or missing the capture window so the first published dataset shows your fund as an outlier for reasons of data quality rather than member outcomes.

The other common misread is the definitions standard. SRS 101.0 looks like housekeeping. It is not. Every term used in SRF 611.1 that appears in bold italics is defined in SRS 101.0, which means the new collection is only as reliable as the definitions mapping underneath it. Teams that have worked through a regulator’s data dictionary, the same discipline behind the kind of issues we track in reporting data point model known-issues lists, know the definitions work is where most of the rework hides.

Frequently Asked Questions

What is APRA’s Retirement Reporting Framework?

It is a Government transparency reform that requires APRA to collect and publish consistent data on superannuation funds’ retirement product offerings, services and member outcomes. Treasury published the final framework design in February 2026, and APRA consulted in March 2026 on the reporting standards that give it effect.

Which reporting standards change under the proposals?

APRA proposes a new standard, SRS 611.1 Retirement Member Profile; revisions to SRS 607.0 RSE Business Model and SRS 101.0 Definitions for Superannuation Data Collections; and revocation of SRS 610.0 Membership Profile.

When does the first reporting period start and when is data due?

For SRS 611.1, the first reporting period is the year ending 30 June 2027, with data due within three months after the end of that period. APRA targets final standards in Q3 2026 and first collection in Q4 2027, with first publication from 2028.

Who has to report, and who is excluded?

The collection applies to all RSE licensees in respect of each RSE within their business operations. Members whose interests can be excluded under subsection 52AA(3) of the SIS Act, broadly defined-benefit-only interests, are excluded from the SRF 611.1 collection.

Does the framework introduce new penalties for trustees?

No. Treasury’s framework design states it is a transparency reform that will not introduce new consequences or penalties for superannuation trustees. The reporting obligations themselves remain binding because they are made under the Financial Sector (Collection of Data) Act 2001.

What does SRS 611.1 actually collect?

Member counts, members’ benefits and payments for members aged 60 and above, segmented by age, sex and benefit bracket, plus the account types held and the actions members take in accumulation and pension phase. It is structured in three tables covering member profile and income, accumulation member actions and pension member actions.

How does this connect to the Retirement Income Covenant?

The covenant in section 52(8A) of the SIS Act requires trustees to formulate a retirement income strategy. The framework does not change that duty. It gives APRA a consistent measure of how trustees are progressing against it, which is why the scope tracks the covenant’s own application.

What should reporting teams be doing now that consultation has closed?

Map the draft SRF 611.1 and SRS 607.0 fields against current member administration data, confirm the SRS 101.0 definitions your systems can and cannot produce, and stand up the capture for the year beginning 1 July 2026 so the first reporting period is complete.

Related Articles

Key Takeaways

  • APRA consulted from 23 March 2026 to 3 June 2026 on reporting standards to implement the Government’s Retirement Reporting Framework.
  • The package makes a new SRS 611.1 Retirement Member Profile, revises SRS 607.0 RSE Business Model and SRS 101.0 Definitions, and revokes SRS 610.0 Membership Profile.
  • All standards are made under subsection 13(1) of the Financial Sector (Collection of Data) Act 2001 and require auditor-reviewed systems.
  • The first reporting period for SRS 611.1 is the year ending 30 June 2027, with data due within three months after period end.
  • To file a complete first year, member-level retirement data capture needs to be running from 1 July 2026.
  • The collection applies to all RSE licensees; defined-benefit-only interests excluded under subsection 52AA(3) of the SIS Act are out of scope for SRF 611.1.
  • The framework is a transparency reform and does not introduce new penalties for trustees, but the returns themselves are binding.
  • SRS 101.0 definitions, not the headline forms, are where most of the mapping work and rework will sit.

Sources and References

The build window opens before the deadline does

The consultation closed on 3 June 2026, but for reporting teams the date that matters is 1 July 2026. That is when the first full reporting period for SRS 611.1 begins. A fund that treats the Retirement Reporting Framework as a 2027 problem will spend 2027 reconstructing a year of member behaviour it never captured. Treat it as a 2026 data-build problem and the first filing becomes a reporting exercise instead of a recovery exercise.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.

Similar Posts