APRA Retirement Reporting Framework consultation: implementation concerns funds are raising ahead of the June deadline

We hosted a discussion forum in May with 30 participants. These are the themes that came up, reported as they were raised, with our own views clearly labelled. The submissions process exists to surface more of these and to give APRA the detail it needs to get this right.

APRA has stated its aim is a fit-for-purpose design that avoids unnecessary regulatory burden. That principle was welcomed in the room. The questions raised were about whether the current proposals fully reflect it.

What follows is a summary of the themes that came up. Nothing is attributed to any individual or fund. This is not a definitive list; the submissions process is where the full picture will emerge. Where we offer a view of our own, we have said so. If you need a primer on the proposed standards themselves, including the three indicators, three metrics, and affected reporting forms, you can read our summary here: APRA's Retirement Reporting Framework: What the Draft Standards Mean for Super Funds. For APRA's full consultation paper, visit Implementation of Government's Retirement Reporting Framework – APRA's proposals."

---

APRA Retirement Reporting Framework implementation concerns raised on the day

Member versus member account

The shift from account-level reporting in SRS 611.0 to member-level reporting in SRS 611.1 is a significant build. APRA has not defined "member" in SRS 101.0, only "member account", and funds currently apply different business rules to make that distinction. One panellist illustrated this with the experience of a large fund following a merger, where two funds had applied different interpretations to the same regulatory reporting and had to harmonise their approach post-merger. Without a clear definition from APRA, the same inconsistency risks playing out across the industry. In our view, this consultation is an opportunity for APRA to resolve it, and it would be worth the industry saying so clearly in submissions.

Drawdown rates

It is not clear from the consultation whether APRA is seeking to capture a member's nominated payment, the legislated minimum drawdown, or commutations. Given that the drawdown rate is likely to become a published headline figure, consistency of interpretation across the industry is critical. This had been raised directly with APRA ahead of the session and was described as still evolving. A related question was raised about purchase consideration for lifetime products: specifically, whether APRA intends the purchase amount to reflect the full balance transferred or the amount calculated under the capital access schedule, which, for lifetime products, can be materially different.

The cohort approach

Strong concern was raised about the use of yes/no flags to define member cohorts in SRS 611.1. The number of possible combinations creates a significant burden on testing and data quality. It was also noted that this approach differs from how product classification works in other APRA forms, where funds define their own product mix and report against it. The question was raised as to why retirement products could not follow the same pattern.

Averages and published data

Concern was raised that averaging within cohorts, across products within a member and across members within a cohort may produce figures that do not accurately represent the underlying population. We think this is worth articulating carefully in submissions: if published data mislead rather than inform, it works against the APRA Retirement Reporting Framework's stated purpose.

Consistency of interpretation

In an APRA Connect environment, calculations must be performed outside the form before submission, unlike in a D2A environment, where some calculations are handled within the form. With a collection of this size and complexity, there is real scope for funds to interpret requirements differently. Past experience with similar implementations suggests this surfaces as a wave of resubmissions post-lodgement. Clearer drafting and guidance on expected calculation methodology would reduce that risk.

Timing

The timeline was a consistent concern. The view in the room was that it appears Treasury-driven, with APRA working back from a fixed endpoint. Our read is that the industry may be building against a standard that will need to change once APRA sees what the data actually looks like, and that this risk is worth naming explicitly in submissions rather than leaving it unsaid.

Retiring SRS 610.0

Retiring 610.0 whilst leaving the rest of the 610 series in place was seen as an incomplete solution. The question raised was whether this is an opportunity to take a more holistic approach, redesigning member activity and demographic reporting more broadly rather than addressing retirement in isolation.

Regulatory data sharing

Participants raised the question of why more data sharing between APRA and the ATO does not occur, given that the ATO already holds detailed superannuation transactional data. The concern was that funds are increasingly being asked to report similar information to different regulators in slightly different formats, adding to the overall reporting burden without clear justification.

Published data: confidentiality versus accuracy

When asked directly whether any reported fields within APRA Retirement Reporting Framework should be considered confidential, the view in the room was that the more pressing concern is misleading publication rather than confidentiality. If the data is not sufficiently comparable or representative, there is a risk that it misrepresents retirement outcomes when published. Advice costs were noted as one area where confidentiality may be a more direct consideration. A separate but related point was also raised: a unique combination of member attributes within a published cohort could potentially allow an individual to identify themselves in the data. A minimum member count threshold before publication, or aggregation of small cohorts, was suggested as a straightforward safeguard.

Sample submissions

A practical suggestion was made that APRA invite funds to provide sample data submissions ahead of finalisation. This would allow APRA to stress-test their assumptions, including product classification assumptions, against real data structures before the standard is locked down, thereby reducing the risk of corrections post-go-live.

Industry submissions

Most attendees indicated they plan to contribute through an industry body. Concern was raised that some bodies may not engage with the more technical aspects of the consultation. If your fund wants to ensure technical details make it into a submission, please get in touch with us directly.

---

The concerns raised here are a starting point, not a summary of industry views. The submissions process is where that picture will be built, and it matters that funds engage, whether directly or through an industry body, before the 3 June deadline.

Nuj will be making a public submission to APRA. If you have any points you would like to raise or would like to contribute, please get in touch.

APRA's consultation paper and questions are available at:

apra.gov.au — Retirement Reporting Framework consultation questions