Financial Sector (Collection of Data) (reporting standard) determination No. 20 of 2015 - SRS 610.2 - Membership Profile

SRS 610.2 organises around a handful of principal concepts and a single reporting form. Each concept corresponds to specific items on SRF 610.2 and a set of instructions that determine measurement, timing and exclusions.

• Scope and subject matter: the reporting standard applies to each registrable superannuation entity (RSE) licensee in respect of each MySuper product within its business operations (paragraph 3). “MySuper product” is defined by reference to s 10(1) of the SIS Act (Interpretation). The standard applies to MySuper interests only; where a member account has both MySuper and non-MySuper interests, only the MySuper interests are to be reported (Reporting basis).

• Reporting unit and frequency: the reporting unit is the MySuper product (SRF 610.2 must be completed for each MySuper product: Reporting level). The baseline reporting frequency is annually, for reporting periods ending on or after 1 July 2015, tied to the year of income of the RSE in which the MySuper product is located (paragraphs 4 and 7). APRA can require more or less frequent reporting by written notice (paragraph 8). Standard due date is within three months of the end of the relevant year of income (paragraph 9).

• Data taxonomy: the SRF form captures (a) member account movement figures (opening, new accounts, rollovers, successor fund transfers, closed accounts, closing balances, and the split between MySuper interest resulting from member investment choice and MySuper interest not resulting from member choice); (b) detailed member account segmentation by age bracket, gender and members’ benefit bracket (Item 5); (c) the count of members without insurance by insurance type and whether opt-outs explain lack of cover (Item 6); and (d) membership by lifecycle strategy stages if the MySuper product has a lifecycle investment strategy (Item 7). The form requires both counts of member accounts (whole numbers) and monetary values (thousands of dollars) as specified in the instructions.

• Measurement and exclusions: monetary items are reported in accordance with Australian Accounting Standards unless specified otherwise. The form and instructions repeatedly exclude defined benefit members’ benefits and unallocated contributions from defined contribution members’ benefits reporting (see Item 1 and the Item 4 instructions). “Defined contribution members’ benefits” and “defined benefit members’ benefits” are defined by reference to accounting concepts (instructions).

• Quality control and assurance: RSE licensees must ensure that the information is the product of systems, procedures and internal controls reviewed and tested by the RSE auditor (paragraph 11). That review must be performed annually or more frequently as necessary, and must be at least a limited assurance engagement consistent with professional standards and guidance from the Auditing and Assurance Standards Board, except where inconsistent with SPS 310 (paragraph 11(b)). The Board and senior management are explicitly responsible for policies and procedures for internal review and authorisation (paragraph 12).

• Submission and authorisation mechanics: submissions must be electronic via the Direct to APRA (D2A) application or another method notified by APRA (paragraph 6). Persons submitting must digitally sign using a certificate acceptable to APRA (paragraph 13). An agent submitting on behalf of an RSE licensee requires the licensee to obtain and retain a copy of the completed form (paragraph 14). The submitter must be authorised by either the Chief Executive Officer or the Chief Financial Officer of the RSE licensee (paragraph 15).

• APRA’s tailoring and administrative powers: APRA may change reporting periods for particular licensees or products (paragraph 8), grant extensions of due dates (paragraph 10), and vary the reporting requirements of SRF 610.2 for particular licensees or products by written notice (paragraph 16).

• Legal and regulatory cross-references: the standard relies on terms defined in the SIS Act and SIS Regulations, invokes Australian Accounting Standards, references Prudential Standard SPS 310 (audit and related matters) and Prudential Standard SPS 510 (governance) for particular obligations (footnotes and Interpretation). The standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 and is declared to apply under section 15 of that Act (Authority and front matter).

These concepts set the boundaries of the information APRA standardises, the cadence and mechanics of reporting, and the governance and assurance expectations APRA places on RSE licensees when reporting MySuper membership profiles.

SRS 610.2 applies to RSE licensees that operate MySuper products. Paragraph 3 states the standard applies to “each registrable superannuation entity (RSE) licensee in respect of each MySuper product within its business operations.” The instrument clarifies that an RSE licensee’s business operations include all activities as an RSE licensee and other activities relevant to or impacting its RSE activities; if the RSE licensee is trustee of more than one MySuper product, it must separately provide the information for each product (footnote 1). Conversely, an RSE licensee that does not have any MySuper products is not required to provide information under this reporting standard (footnote 1).

This produces a clear population:

• Directly affected: trustees/RSE licensees that have one or more MySuper products. For each MySuper product they must prepare a separate SRF 610.2 (Reporting level; footnote 1).

• Indirectly affected: RSE auditors engaged to audit or provide assurance over the RSE licensee’s reporting systems and controls (paragraph 11). The RSE auditor must perform review and testing of systems, procedures and internal controls and deliver at least a limited assurance engagement consistent with applicable auditing standards (paragraph 11(b)). Boards and senior management are explicitly addressed by the standard as responsible for policies and procedures authorising submissions (paragraph 12).

• Service providers and agents: third-party administrators, technology vendors and agents who submit via Direct to APRA on behalf of the RSE licensee are affected by obligations to provide the RSE licensee with a copy of the completed form and the requirement that submissions be authorised by CEO or CFO (paragraphs 14-15). Agents must also ensure they can digitally sign with a certificate acceptable to APRA if submitting (paragraph 13).

• Insurers: indirectly affected because Item 6 tracks members without insurance and opt-outs. Although insurers are not obliged by the standard, their products and cover rules determine how many members are recorded as without cover or as opt-outs.

• Internal control and compliance functions: required to implement systems, policies and procedures so the data reported are reliable and auditable (paragraphs 11-12). Management is also tasked with ensuring adherence to Australian Accounting Standards for measurement.

Exclusions and boundary conditions limit who must report and what must be reported:

• Only MySuper interests are in scope; where accounts hold mixed interests, only the MySuper portion is reported (Reporting basis: Reporting Form SRF 610.2). This confines the reporting burden to MySuper product portfolios rather than entire fund registers.

• Defined benefit member liabilities and unallocated contributions are excluded from the defined contribution members’ benefits reported on SRF 610.2 (Item 1 and Item 4 instructions). However, where liabilities cannot be allocated to specific members, they are to be reported in Item 5 as ‘age not available’ with zero in the count column and the liability value in the monetary column (Item 5 instructions).

• The standard applies to reporting periods ending on or after 1 July 2015 (paragraph 4) so it affects historical data requirements from that date forward.

APRA retains the administrative capacity to tailor reporting for particular licensees and products (paragraphs 8 and 16), which in practice may mean some entities receive bespoke notices changing frequency or content. The standard also explicitly contemplates APRA publishing the collected information, since paragraph 2 states the information will be used for prudential supervision and publication; this creates potential reputational and public data disclosure implications for affected RSE licensees.

The reporting standard imposes specific duties on RSE licensees and sets out administrative rights for APRA. Those duties are precise about what must be reported, when, how and under what assurance arrangements.

Primary duties

• Submission of SRF 610.2 for each MySuper product: An RSE licensee must provide APRA with the information required by SRF 610.2 in respect of each reporting period (paragraph 5). The reporting level is the MySuper product (Reporting level and instructions).

• Reporting frequency and due date compliance: Report for each year of income of each RSE within which a MySuper product is located (paragraph 7). The information must be provided within three months after the end of the year of income to which the information relates (paragraph 9(a)). If APRA specifies a change under paragraph 8, the RSE licensee must comply with the time specified in APRA’s notice (paragraph 9(b)).

• Electronic submission and authorisation: The information must be provided electronically via Direct to APRA or, if unavailable, by another APRA-notified method in writing (paragraph 6). Submissions via D2A must be digitally signed using a certificate acceptable to APRA (paragraph 13). The person who submits must be authorised by the CEO or CFO of the RSE licensee (paragraph 15).

• Retention of copies when agents submit: If an agent submits the form on behalf of the RSE licensee, the licensee must obtain and retain a copy of the completed form provided to APRA (paragraph 14).

• Data quality, systems and internal controls: The information must be the product of systems, procedures and internal controls reviewed and tested by the RSE auditor. That review and testing must be performed annually (or more often if necessary) and be at least a limited assurance engagement consistent with professional standards and guidance notes from the Auditing and Assurance Standards Board, insofar as those are not inconsistent with SPS 310 (paragraph 11).

• Board and senior management responsibilities: Boards and senior management are responsible for ensuring an appropriate set of policies and procedures for internal review and authorisation of information submitted to APRA is in place (paragraph 12).

Measurement and content duties

• Report only MySuper interests: Where accounts contain both MySuper and non-MySuper interests, report only the MySuper interests (Reporting basis and instructions).

• Monetary reporting standard: Report monetary amounts in accordance with Australian Accounting Standards unless otherwise specified; amounts are to be shown as thousands of dollars where required (Reporting basis and Unit of measurement).

• Exclusions: Do not include defined benefit members’ benefits or unallocated contributions in defined contribution members’ benefits reported in specified items (Item 1 and Item 4 instructions).

Administrative and procedural rights of APRA

• Variation and tailoring: APRA may change reporting periods for specific RSE licensees or MySuper products by written notice (paragraph 8). APRA may also vary the reporting requirements of SRF 610.2 in relation to an RSE licensee or one or more MySuper products by written notice (paragraph 16). APRA may also grant time extensions in writing (paragraph 10).

• Method of submission and software control: APRA prescribes D2A as the primary electronic method and may notify other methods where D2A is not available (paragraph 6). APRA controls acceptance of digital certificates for signature (paragraph 13).

Other obligations and implied duties

• RSE auditors’ engagement scope: The RSE auditor must review and test the systems, procedures and internal controls that enable reliable reporting. That imposes an assurance duty on the auditor and a disclosures duty on the licensee to enable the auditor’s work (paragraph 11).

• Publication and prudential use: APRA intends to use the data for prudential supervision and publication (paragraph 2). While the instrument does not specify publication policy, the declared use means RSE licensees should expect their data to be capable of being published or used to inform APRA’s regulatory activities.

Limits and absence of certain duties

• No express penalty regime in the standard: The reporting standard itself does not set out penalties or sanctions for non-compliance. APRA’s enforcement powers under the Financial Sector (Collection of Data) Act 2001 and other legislation are not detailed in the text of SRS 610.2; the standard instead focuses on process, content and assurance requirements (see overall instrument). RSE licensees must therefore consider the Act and other prudential standards for enforcement consequences; those are not reproduced in this instrument.

In short, duties concentrate on timely, accurate electronic submission for each MySuper product, maintenance of controls and auditor assurance, and internal authorisation processes. APRA retains rights to vary, grant extensions and set submission mechanics.

The reporting standard (SRS 610.2) as presented is a data collection instrument that prescribes content, timing and process; it does not itself set out civil or criminal penalties or a detailed enforcement regime within its text. The Determination is made under the Financial Sector (Collection of Data) Act 2001 (front matter and Authority), and the front matter notes the Determination and reporting standard are declared to apply under section 15 of that Act. The instrument therefore sits inside a statutory framework that provides APRA with data-collection powers and, separately, enforcement mechanisms. However, the text of SRS 610.2 does not enumerate specific sanctions such as fines, directions, or criminal offences for non-compliance.

What SRS 610.2 does specify, which has enforcement implications in practice, are administrative controls and APRA’s discretionary powers:

• APRA may change reporting periods for particular RSE licensees or MySuper products by written notice (paragraph 8). Non-compliance with such a notice would put a licensee outside the reporting requirements APRA has prescribed for that licensee.

• APRA may grant extensions in writing to a due date for provision of information (paragraph 10). Absent such an extension, the statutory due date is within three months after the end of the year of income (paragraph 9). Failure to meet due dates could trigger APRA follow-up under the Act, though the Determination itself does not state specific penalties.

• APRA may vary reporting requirements for a particular RSE licensee or MySuper product by written notice (paragraph 16). This is an administrative enforcement tool because it allows APRA to tailor obligations and respond to deficiencies or particular risks.

Quality-control and assurance obligations create indirect enforcement channels:

• The RSE auditor must review and test systems and controls and perform at least a limited assurance engagement consistent with professional standards and guidance (paragraph 11). Where an auditor identifies weaknesses, their findings could lead to regulatory engagement by APRA, remedial requirements under prudential standards referenced by the instrument (SPS 310, SPS 510), or further supervisory action.

• Boards and senior management are assigned responsibility for ensuring policies and procedures for authorisation and internal review are in place (paragraph 12). APRA can use failures in governance identified via the data submission process or auditor reports as grounds for supervision under prudential standards.

Publication of data can function as a reputational enforcement mechanism:

• The standard expressly states that information is used for prudential supervision and publication (paragraph 2). Publication of poor metrics or data quality issues may prompt market or member response and lead to APRA inquiries or remediation steps.

What SRS 610.2 does not do explicitly

• It does not itself list penalties, sanctions, or a timetable for enforcement action such as infringement notices, penalties under criminal law, or specific remedial powers. Those reside in the Financial Sector (Collection of Data) Act 2001 and APRA’s broader prudential powers and are not reproduced in this Determination.

Practical enforcement risks for RSE licensees

• Administrative risk: missing the three-month due date (paragraph 9) without having sought or been granted an extension (paragraph 10) will place the licensee in breach of the standard and expose it to APRA follow-up under the governing Act.

• Assurance risk: inadequate auditor review or failure to meet at least a limited assurance engagement standard (paragraph 11) may trigger supervisory scrutiny and require remedial action under SPS 310 or governance requirements referenced (footnote to paragraph 11 and footnote 3 referencing SPS 510).

• Data publication risk: as APRA uses the data for publication (paragraph 2), inadequate or inaccurate reporting can have reputational consequences and may prompt further regulatory attention.

In sum, while the Determination itself prescribes obligations and grants APRA administrative levers to tailor and manage compliance, it does not specify in-text penalties. Enforcement and sanctioning powers lie in the underlying Act and APRA’s prudential standards framework to which this reporting standard is connected; those specific legal consequences are not set out within the SRS 610.2 text provided.

SRS 610.2 is embedded in, and cross-references, a network of statutory and prudential instruments. The Determination is made under the Financial Sector (Collection of Data) Act 2001 (Authority) and declared to apply under section 15 of that Act (front matter). It refers to, and depends on, the definitions and constructs in the Superannuation Industry (Supervision) Act 1993 (SIS Act) and the SIS Regulations, and it cross-links to prudential standards and accounting and auditing regimes. Specific interactions are as follows:

Primary statutory references

• Financial Sector (Collection of Data) Act 2001: The Determination is made under section 13 of that Act (Authority), and declared to apply under section 15 (front matter). That Act provides APRA with the power to require certain entities to provide data. SRS 610.2 operationalises those powers with the specific SRF 610.2 form and instructions.

• Superannuation Industry (Supervision) Act 1993 (SIS Act): The reporting standard relies on the SIS Act for core definitions. “MySuper product,” “RSE,” “RSE licensee” and “year of income” are defined by reference to s 10(1) of the SIS Act (Interpretation). The instructions further reference SIS Act provisions defining MySuper and related concepts (e.g. item definitions referencing SIS Act s.10(1) and lifecycle investment strategy definition in section 29TC(2)).

• SIS Regulations: The instructions refer to specific SIS Regulations when defining rollovers and successor fund transfers (SIS Regulations, r. 5.01, r. 6.28, r. 6.29 and r. 1.03 are cited in Item 2 instructions).

Prudential standards and guidance

• SPS 310 Audit and Related Matters: Paragraph 11 requires the RSE auditor’s review and testing to be at least a limited assurance engagement consistent with professional standards and guidance notes issued by the Auditing and Assurance Standards Board, to the extent those standards are not inconsistent with the requirements of SPS 310. Footnote 2 explicitly references SPS 310. That creates an interaction where the content of the auditing work must align with both professional auditing standards and the prudential standard SPS 310.

• SPS 510 Governance: The instrument’s Interpretation section cross-references Prudential Standard SPS 510 for the definitions of Chief Executive Officer and governance responsibilities (footnote 3). Paragraph 12 also places responsibility on Board and senior management for policies and procedures relevant to reporting and authorisation, aligning with the governance requirements in SPS 510.

Accounting and auditing frameworks

• Australian Accounting Standards: The instructions require reporting “in accordance with the Australian Accounting Standards unless otherwise specified” (Reporting basis and Unit of measurement). This ties the valuation and presentation of members’ benefits to the general accounting framework and ensures consistency with financial statements and actuarial valuations where appropriate.

• Auditing and Assurance Standards Board guidance: Paragraph 11 requires the assurance engagement to be consistent with professional standards and guidance notes issued by the Auditing and Assurance Standards Board. The standard therefore imports the technical content of auditing standards for the assurance work performed by RSE auditors.

Administrative and technical interactions

• Direct to APRA (D2A) and digital certificates: Paragraph 6 mandates electronic submission via APRA’s D2A application where available. Paragraph 13 requires digital signing with a certificate acceptable to APRA. These technical requirements interact with other regulatory obligations for privacy, information security and record retention; while those obligations are not detailed in SRS 610.2, affected entities must ensure submission mechanisms align with the data protection and privacy obligations under other laws and APRA policies.

Publication and prudential use

• Paragraph 2 states APRA will use the data for prudential supervision and publication. Publication may interact with general laws on disclosure and privacy and with APRA’s own publication policies. Entities should therefore consider interplay with the Privacy Act and APRA’s data publication practices when preparing data for submission and when assessing member-identifiability risks.

What the standard does not do in relation to other laws

• It does not displace or explicitly amend the content of SIS Act obligations concerning member benefits, fiduciary duties, or insurance; it collects data that may be used in the performance of prudential functions under those other laws.

• It does not specify enforcement mechanisms or sanctions; enforcement would be effected under the Financial Sector (Collection of Data) Act 2001 and APRA’s broader prudential powers and standards.

Implications for compliance planning

• Entities must align their accounting and internal reporting systems so the same valuations and member data can be reconciled between statutory financial statements, actuarial valuations (where relevant) and the SRF 610.2 submissions, consistent with Australian Accounting Standards.

• Assurance activities must be planned to meet both auditing standards and SPS 310 requirements.

• Governance arrangements required by SPS 510 should be reflected in the policies and procedures for authorising and reviewing the data submitted to APRA.

In summary, SRS 610.2 is tightly integrated with the SIS Act/SIS Regulations for definitions, with Australian Accounting Standards for measurement, with auditing standards and SPS 310 for assurance, and with SPS 510 for governance expectations. Its effect is to create a data-reporting pathway that sits inside APRA’s statutory collection and prudential frameworks.

The Determination document itself records a specific amendment action: it revokes Financial Sector (Collection of Data) (reporting standard) determination No. 91 of 2013 and determines Reporting Standard SRS 610.2 Membership Profile in its place (front matter). The Determination is made by an APRA delegate under paragraph 13(1)(a) of the Financial Sector (Collection of Data) Act 2001 and subsection 33(3) of the Acts Interpretation Act 1901, dated 10 June 2015, and declares application from 1 July 2015 under section 15 of the Act (front matter). The instrument’s Schedule contains the full text of the reporting standard and the SRF 610.2 form and instructions.

From the material provided, the recorded amendment history is thus:

• Pre-existing instrument: Reporting Standard SRS 610.2 (or a prior format) had been contained in Determination No. 91 of 2013. The 2015 Determination expressly revokes Determination No. 91 of 2013 and replaces it with this Determination No. 20 of 2015, which includes the new form and instructions.

• Effective date: The new reporting standard applies to reporting periods ending on or after 1 July 2015 (paragraph 4) and the Determination lawfully commences on registration with the Federal Register of Legislative Instruments (front matter). The delegate signs the Determination dated 10 June 2015.

• Content changes implicit in replacement: While the text does not provide a redline to the 2013 standard, the inclusion of the SRF 610.2 form and detailed instructions indicates that APRA updated or reissued the Membership Profile reporting standard, replacing the form and clarifying expectations on scope, measurement, authorisation and assurance. Notable features of the 2015 text include explicit requirements for RSE auditor review at a limited assurance level (paragraph 11), clear digital signature requirements (paragraph 13), and specific segmentation and measurement instructions in the form.

• Footnotes and cross-references: The 2015 Determination cross-references SPS 310 and SPS 510 (footnotes 2 and 3), which suggests an alignment or update to ensure the reporting standard’s assurance and governance obligations map to those prudential standards. The explicit reference to D2A as the submission channel also formalises APRA’s preferred electronic method.

No subsequent amendments, revocations or further changes beyond the 2015 replacement are recorded in the text provided. If there were later variations to SRS 610.2 after 2015, they are not included in this instrument and would need to be checked by searching APRA’s legislative instruments or the Federal Register of Legislative Instruments for later determinations or amendments.

Practical consequence for compliance history

• Entities that were reporting under the 2013 Determination needed to switch to the 2015 SRS 610.2 requirements for reporting periods ending on or after 1 July 2015. The Determination gives APRA the ability to change reporting periods or vary requirements for specific RSE licensees (paragraphs 8 and 16), so compliance obligations may have been modulated subsequently in particular cases, but such changes are not recorded in this document.

• Because the 2015 Determination explicitly revokes the earlier Determination, the 2013 standard ceased to have effect as of 1 July 2015 for the entities covered by this Determination.

For a complete and current amendment history beyond the 2015 replacement, practitioners should consult the Federal Register of Legislative Instruments and APRA’s published reporting standards register; such searches are outside the scope of the text provided here.

The text of Reporting Standard SRS 610.2 and its Determination No. 20 of 2015 does not record any litigation or judicial decisions. There are no cases named or legal disputes referenced in the instrument itself. The standard is an administrative data-collection instrument and its text provides the reporting form, instructions, and administrative powers without reference to judicial interpretation or litigation history.

Consequently, based on the instrument as provided:

• There are no reported court decisions, tribunal findings, or litigation narratives included in SRS 610.2 that interpret or challenge the standard’s provisions.

• The instrument does reference statutory sources and prudential standards (Financial Sector (Collection of Data) Act 2001, SIS Act, SIS Regulations, SPS 310 and SPS 510), which have their own bodies of interpretation and possible litigation not included here. Any litigation arising from APRA’s use of data, enforcement actions, or disputes about reporting requirements would appear in separate records not contained in this Determination.

Implications for practitioners

• Absence of litigation in the instrument means there is no instrument-specific judicial guidance on the meaning of particular phrases or obligations in SRS 610.2. Where ambiguity exists in interpretation (for example the application of “MySuper interest as a result of member investment choice” in complex account structures), APRA guidance, prudential standards, and professional judgement will be primary interpretive sources.

• If an RSE licensee faces an enforcement action or dispute relating to SRF 610.2 submissions, the legal questions will likely involve interpretation of the underlying statutes (Financial Sector (Collection of Data) Act, SIS Act) and relevant prudential standards. Those matters would be litigated or administratively adjudicated outside the confines of this Determination; no such matters are recorded here.

• Practitioners seeking precedent on the interpretation of reporting obligations, the scope of APRA’s data powers, or the interplay with prudential standards should look to case law and administrative decisions concerning APRA and the SIS framework more generally. Those materials are not contained in this instrument and must be sourced separately.

In short, SRS 610.2 contains no litigation history in its text. Any legal disputes involving these reporting obligations would be recorded in external case law or administrative records not included in the standard itself.

The reporting standard contains several detailed requirements and design choices that create operational risks and potential traps for RSE licensees and their advisers. Below are specific “gotchas” drawn from the text and instructions, together with the concrete mechanism by which each can create compliance or governance exposure.

1. Scope limited to MySuper interests only

• Mechanism: SRF 610.2 repeatedly requires that items be reported in relation to MySuper interests only (Reporting basis and Item instructions). Where a member account has both MySuper and non-MySuper interests, only the MySuper portion is reported.
• Risk: Systems that extract “per-account” balances without separating MySuper vs non-MySuper portions will over-report. Reconciliation between financial statements and SRF submission requires splitting balances, which can be non-trivial where accounting or custody data store a single account balance.

2. Excluding defined benefit liabilities and unallocated contributions

• Mechanism: Item 1 and Item 4 explicitly say do not include defined benefit members’ benefits or unallocated contributions in defined contribution members’ benefits reported (Item instructions).
• Risk: Funds that operate hybrid arrangements or have pooled accounting ledgers risk misclassifying amounts. Also, unallocated contributions are excluded but must be tracked elsewhere; failure to do so may produce inconsistencies between SRF 610.2 and statutory accounts.

3. Measurement in thousands and whole numbers

• Mechanism: Members’ benefits are to be reported in thousands of dollars (monetary columns) while member account counts are whole numbers (Unit of measurement).
• Risk: Rounding and scaling errors can lead to apparent discrepancies. Small accounts that round to zero in thousands may disappear from monetary reporting but still appear in counts, creating reconciliation issues.

4. Maximum of 384 segmentation lines

• Mechanism: Item 5 combines age brackets (12), gender categories (up to 6 as shown headers), and member benefit brackets (8), producing a maximum of 384 combinations (Item 5).
• Risk: Systems must be capable of producing full cross-tabulations. Omitted combinations or mis-ordered lines may require manual correction or APRA follow-up.

5. “Age not available” handling for unallocated liabilities

• Mechanism: Liabilities that cannot be allocated to specific members are to be reported as ‘age not available’ with zero in member account count and liability value in monetary column (Item 5).
• Risk: Treating these as zero-count lines is counterintuitive and can produce reconciliations that look inconsistent to non-technical reviewers.

6. Rollover vs successor fund transfer definitions

• Mechanism: Item 2 defines rollovers (referencing SIS Regulations r.5.01, r.6.28 and r.6.29) and successor fund transfers separately, excluding successor fund transfers from rollovers.
• Risk: Misclassification of transfers will distort inflows reporting. Funds must map operational transfer codes to the regulatory definitions.

7. “MySuper interest as a result of member investment choice”

• Mechanism: Item 4.1 requires reporting the portion attributable to a MySuper interest because of member investment choice, where a member has exercised choice to direct any portion into MySuper (Item 4 definition referencing SIS Act, s.10(1)).
• Risk: Distinguishing between defaulted membership and member-directed movement into MySuper requires accurate, time-stamped investment choice records.

8. Assurance level and auditor obligations

• Mechanism: Paragraph 11 requires the RSE auditor to review and test systems annually and to perform at least a limited assurance engagement consistent with professional standards, subject to SPS 310.
• Risk: If auditors do not perform the required level of assurance or if the licensee’s systems are not auditable, APRA may query reliability. The standard’s cross-reference to SPS 310 means auditing work must align with prudential expectations, not only general auditing practice.

9. Digital signature and authorised submitter requirement

• Mechanism: Submissions via D2A must be digitally signed using a certificate acceptable to APRA (paragraph 13), and the submitter must be authorised by the CEO or CFO (paragraph 15).
• Risk: Operational failure to maintain valid certificates or to secure CEO/CFO authorisation before submission can invalidate a submission or trigger APRA enquiries. Agents submitting must provide the RSE licensee with a copy and the licensee must retain it (paragraph 14).

10. APRA’s power to change frequency and vary requirements

• Mechanism: APRA may change reporting periods (paragraph 8) or vary requirements for particular RSE licensees or products (paragraph 16).
• Risk: Expectation management is needed: an RSE may be required to supply data more frequently or in different formats at short notice. Systems must be adaptable and staff must track APRA notices.

11. Publication risk

• Mechanism: Paragraph 2 states APRA will use the data for prudential supervision and publication.
• Risk: Reported metrics may be publicly disclosed. Data quality or unfavourable metrics can have reputational consequences and affect member retention or market positioning.

12. Reconciliation to accounting and actuarial numbers

• Mechanism: Reporting must align with Australian Accounting Standards and, where appropriate, actuarial concepts are referenced for defined benefit calculations (Item 1 definitions).
• Risk: Differences in valuation timing, actuarial assumptions, or recognition policies between financial statements and SRF 610.2 lines can create apparently inconsistent figures. Preparers must document mapping logic.

13. Lifecycle strategy stage reporting

• Mechanism: Item 7 requires, where the MySuper product has a lifecycle investment strategy, reporting of member accounts and benefits in each lifecycle strategy stage using identifiers from SRF 001.0 (Item 7).
• Risk: Misalignment between product lifecycle identifiers in SRF 001.0 and SRF 610.2 will produce mismatched records; where lifecycle strategies change during the period, allocation rules must be clear.

14. Board and senior management responsibility

• Mechanism: Paragraph 12 places explicit obligation on the Board and senior management to establish appropriate policies and procedures for authorisation.
• Risk: Boards must ensure oversight; failure to document governance may give APRA cause for supervisory intervention under governance prudential rules.

Mitigation for these gotchas will require careful mapping of operational data to regulatory definitions, robust internal control frameworks, audit-ready documentation, and cross-functional coordination between compliance, actuarial, accounting and IT teams.

Compliance with SRS 610.2 requires coordinated changes across data capture, accounting, audit and governance. Below is a practical, step-by-step compliance checklist derived from the instrument’s text and instructions. Each step cites the relevant paragraph or instruction as the guiding source.

1. Identify in-scope products and reporting units (paragraph 3; Reporting level)

• For each RSE licensee, list all MySuper products within the RSE business operations. Prepare a separate SRF 610.2 for every MySuper product (footnote 1).

2. Map data sources to form items (SRF 610.2 form and Specific instructions)

• Member account movement: map register records and transaction flows to Item 1-4 (opening accounts, new accounts, rollovers, successor fund transfers, closed accounts, closing balances, and the split between member-choice-derived MySuper interests and non-choice-derived MySuper interests).
• Segmentation (Item 5): build extraction logic that cross-tabulates age bracket, gender categories and members’ benefit brackets into the required combinations (maximum 384 lines).
• Members without insurance (Item 6): gather counts per insurance type and counts of opt-outs.
• Lifecycle strategy stage (Item 7): if product has lifecycle strategy, map internal lifecycle stage identifiers to SRF 001.0 identifiers to ensure consistency.

3. Ensure measurement and accounting alignment (Reporting basis and Unit of measurement; Item instructions)

• Use Australian Accounting Standards for monetary measurement unless stated otherwise (instructions).
• Report counts as whole numbers and monetary amounts in thousands of dollars where specified. Document rounding conventions and reconciliation approach to financial statements.

4. Separate MySuper and non-MySuper interests (Reporting basis)

• Implement logic to allocate balances in accounts that contain both MySuper and non-MySuper interests so that only the MySuper portion is reported.

5. Exclude defined benefit liabilities and unallocated contributions where required (Item 1 and Item 4)

• Ensure defined benefit members’ benefits and unallocated contributions are not included in defined contribution members’ benefits columns. For liabilities not allocable to members, report them in Item 5 as ‘age not available’ with zero in the count and the liability amount in the monetary column (Item 5).

6. Prepare data pipelines capable of producing required cross-tabulations (Item 5; Item 7)

• Build or configure reporting extracts that can produce all allowed combinations for segmentation and lifecycle stage lines; include checks for completeness and formatting.

7. Implement quality-control processes and audit trail (paragraphs 11-12)

• Develop internal policies and procedures for the review and authorisation of information submitted to APRA, and ensure they are approved by the Board and senior management (paragraph 12).
• Create documented systems, processes and controls that produce the SRF 610.2 data and maintain audit trails of the calculations, source records and reconciliation work.

8. Engage and coordinate with the RSE auditor (paragraph 11)

• Notify the RSE auditor of the reporting requirements and ensure they plan to review and test the systems, procedures and internal controls at least annually, and perform a limited assurance engagement consistent with relevant professional standards, to the extent not inconsistent with SPS 310 (paragraph 11(b)).
• Ensure the auditor’s scope of work covers the data pipeline end-to-end and the assumptions used in allocation of mixed-interest accounts.

9. Test the submission process and digital-signature capability (paragraphs 6 and 13)

• Obtain access to APRA’s Direct to APRA (D2A) application and test the submission process.
• Ensure the persons authorised to submit have digital certificates acceptable to APRA and that the certificate lifecycle (renewals, replacements) is managed.
• If D2A is not available, obtain APRA’s written notice of the alternative submission method (paragraph 6).

10. Implement authorisation procedures for submitters (paragraph 15)

• Maintain documented authorisation from the CEO or CFO delegating submission authority to named officers or agents. Ensure that the submitter digitally signs the submission as required (paragraph 13).

11. Agent arrangements and record retention (paragraph 14)

• If an agent submits on behalf of the RSE licensee, require the agent to provide a copy of the completed form and retain that copy in compliance with internal record-retention policies (paragraph 14).

12. Timeliness and extension planning (paragraphs 7-10)

• Calendar the reporting cycle based on the relevant year of income, and prepare SRF 610.2 within three months of the year end (paragraph 9).
• If additional time will be required, submit a written request to APRA for an extension and obtain written approval; record the revised due date from APRA’s notice (paragraph 10).

13. Prepare reconciliation and governance pack

• Create reconciliation between SRF 610.2 figures and statutory accounts, member registers, and actuarial valuations where applicable. Document methodologies, assumptions and mapping rules for audit and APRA review.
• Prepare a governance pack for the Board showing controls, reconciliations, and auditor assurance conclusions as APRA may review Board-level oversight (paragraph 12).

14. Monitor APRA notices for tailoring or variation (paragraphs 8 and 16)

• Maintain a log of APRA written notices that change reporting periods or vary reporting requirements for the RSE licensee or particular MySuper products (paragraphs 8 and 16).
• Ensure systems and processes are adaptable to deliver data at higher frequency or altered content if APRA issues a notice.

15. Address publication and privacy considerations (paragraph 2)

• Since APRA uses the information for publication, review data for member-identifiability risks and ensure disclosures align with privacy obligations. Coordinate with legal and privacy teams as needed.

16. Operationalise periodic testing and continuous improvement

• Schedule periodic internal testing cycles and dry-run submissions in D2A to catch format or data issues ahead of the due date.
• Maintain an issues register documenting data anomalies, remedial actions, and process improvements.

17. Document everything for auditability

• Ensure every data transformation, rounding rule, allocation decision (e.g. splitting mixed interest accounts), and reconciliation to accounts or trustee records is documented and retained for the RSE auditor’s review and for APRA inquiries.

By following these steps, an RSE licensee will align its operational, accounting and assurance processes to the text of SRS 610.2, satisfy the electronic submission and authorisation mechanics, meet the assurance expectations of paragraph 11, and provide APRA with complete and auditable MySuper membership profile data within the required timeframe.