Financial Sector (Collection of Data) (reporting standard) determination No. 4 of 2015 - SRS 160.1 - Defined Benefit Member Flows

This Reporting Standard requires registrable superannuation entity (RSE) licensees to provide APRA with a specified dataset, SRF 160.1 Defined Benefit Member Flows, for each defined benefit RSE and each defined benefit sub‑fund within their business operations (paras 1, 2, 3, 5). APRA will use the information for prudential supervision and publication, including assessing compliance with Prudential Standard SPS 160 Defined Benefit Matters (para 2). The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (para 1).

Operationally, the Standard prescribes the format (electronic), the submission channel (the Direct to APRA application, also called D2A), and fallback arrangements where D2A is not available (para 6). It sets reporting periodicity as quarterly, aligned to the year of income of each defined benefit RSE or the RSE that contains a sub‑fund (para 7), subject to APRA varying the frequency for particular RSEs or sub‑funds by written notice (para 8). It sets due dates for quarterly returns: for reporting periods ending on or after 1 July 2015 but before 1 July 2017, within 35 calendar days after the end of the quarter; for reporting periods ending on or after 1 July 2017, within 28 calendar days after the end of the quarter (para 9(a)). APRA may specify different timing by written notice where it has varied the reporting period (para 9(b), 8), and APRA may grant written extensions (para 10).

The Standard mandates internal controls, board and senior management responsibility for authorisation policies and procedures, and external assurance. The RSE auditor must review and test the systems, procedures and internal controls that produce the information, on at least an annual basis and in the form of at least a limited assurance engagement consistent with professional standards and guidance from the Auditing and Assurance Standards Board, to the extent not inconsistent with SPS 310 (para 11). All submitted information must be subject to the RSE licensee’s internal review and authorisation processes, and the Board and senior management are explicitly responsible for ensuring appropriate policies and procedures exist (para 12).

Authorisation and record‑keeping are prescribed: submissions via D2A require a digital signature using an APRA‑acceptable digital certificate (para 13); agents submitting on behalf of an RSE licensee require the licensee to obtain and retain a copy of the completed form submitted (para 14); and the person submitting must be authorised by either the Chief Executive Officer or the Chief Financial Officer of the RSE licensee (para 15). APRA retains discretion to vary reporting requirements for particular RSE licensees, RSEs or sub‑funds by written notice (para 16). The Standard includes defined terms and cross‑references to other prudential and statutory instruments (para 17).

The Standard revolves around a small set of concepts: defined benefit RSEs and sub‑funds, the specified reporting form SRF 160.1, electronic submission via D2A, reporting periodicity and due dates, assurance over reporting systems, internal authorisation, and APRA’s case‑by‑case variation and extension powers. Each of those concepts is defined or operationalised in the numbered paragraphs of the Standard.

Defined benefit RSE and sub‑fund: the Standard applies only to RSE licensees in respect of defined benefit RSEs and defined benefit sub‑funds, where those phrases have the meanings given in Prudential Standard SPS 160 (paras 3, 17). This ties scope to prudential definitions rather than, for example, accounting labels.

SRF 160.1: the data to be supplied is the form SRF 160.1 Defined Benefit Member Flows. The Standard mandates provision of the information required by that form in respect of each reporting period (para 5). The Standard does not set out the fields of SRF 160.1 itself; it makes provision for APRA to collect that dataset and for licensees to submit it.

Electronic transmission: submissions must be in electronic format through APRA’s Direct to APRA application (D2A), or by an alternative method notified by APRA where D2A is not available (para 6). D2A is specifically identified as the preferred channel and the software may be obtained from APRA (para 6 note).

Reporting periods and due dates: the primary cadence is quarterly, aligned with the year of income of each defined benefit RSE or the RSE that contains each sub‑fund (para 7). APRA can change reporting frequency for particular entities (para 8). Due dates change depending on the date of the reporting period, with a historical transition in 2017: 35 calendar days for quarters ending from 1 July 2015 until before 1 July 2017, and 28 calendar days for periods ending on or after 1 July 2017 (para 9). APRA can also specify timing by written notice for any altered reporting periods (para 9(b)) and can grant extensions in writing (para 10).

Quality and assurance: the data must be the product of systems, procedures and internal controls reviewed and tested by the RSE auditor (para 11). The review and testing must be performed on at least an annual basis or more frequently if needed to form an auditor opinion on reliability and accuracy (para 11(a)). The assurance engagement must be at least a limited assurance engagement consistent with Auditing and Assurance Standards Board professional standards and guidance notes, to the extent not inconsistent with SPS 310 (para 11(b)). Separately, the licensee must have internal processes for review and authorisation and the Board and senior management must ensure appropriate policies and procedures for authorisation of information submitted to APRA (para 12).

The direct legal obligation under the Standard falls on RSE licensees. Paragraph 3 states the Standard applies to each RSE licensee in respect of each defined benefit RSE and each sub‑fund within its business operations. Therefore the primary financial and compliance burden is on RSE licensees that operate defined benefit funds or sub‑funds.

Within an RSE licensee, the organisational roles explicitly implicated are the Board, senior management, the Chief Executive Officer and the Chief Financial Officer. Paragraph 12 makes the Board and senior management responsible for ensuring appropriate policies and procedures for authorisation of information submitted to APRA are in place. Paragraph 15 requires that the officer or agent who submits the information be authorised by either the CEO or the CFO. These provisions place governance and delegation tasks on senior management and the board.

RSE auditors are secondarily affected: paragraph 11 prescribes that the information must be the product of systems, procedures and internal controls reviewed and tested by the RSE auditor, and sets the frequency and minimum assurance level for that engagement. That creates a recurring assurance engagement obligation, with professional standards from the Auditing and Assurance Standards Board informing the scope, subject to consistency with SPS 310 (para 11(b)).

Agents and service providers who perform data aggregation or submission on behalf of an RSE licensee are implicated operationally. Paragraph 6 allows submission by a method notified by APRA where D2A is not available, and paragraph 14 requires RSE licensees to obtain and retain a copy of any completed form submitted by an agent. Paragraph 13 requires digital signature using an APRA‑acceptable digital certificate for D2A submissions, which can affect third‑party submission workflows.

APRA itself is the recipient and decision‑maker. The Standard grants APRA the authority to change reporting periods (para 8), to vary reporting requirements in relation to particular RSE licensees, RSEs or sub‑funds (para 16), and to grant extensions (para 10). APRA also determines acceptable digital certificates for signatories (para 13) and notifies alternative submission methods where D2A is not available (para 6).

Other affected parties are implicit: professional auditors and assurance practitioners who must deliver at least limited assurance engagements under prevailing professional standards, and internal compliance teams who must design, maintain and certify systems, procedures and internal controls that produce the SRF 160.1 information (paras 11, 12). The Standard links to SPS 160 and SPS 310, so entities subject to those prudential standards will have an overlapping compliance perimeter (paras 2, 11(b), 17).

The Standard sets out duties for RSE licensees, duties for RSE auditors, obligations for authorising officers, and rights exercisable by APRA. These are concrete and procedural rather than substantive prudential prescriptions.

Duties of RSE licensees:

• Provide to APRA the information required by SRF 160.1 in respect of each reporting period (para 5). The duty is continuous for each reporting period covered by the Standard.
• Submit information in electronic format via D2A, or by an alternative APRA‑notified method if D2A is not available (para 6).
• Ensure information is produced by systems, procedures and internal controls that have been reviewed and tested by the RSE auditor (para 11).
• Maintain systems, processes and controls for internal review and authorisation of information, and ensure the Board and senior management establish appropriate policies and procedures for authorisation of information submitted (para 12).
• Obtain and retain a copy of any completed form submitted by an agent on its behalf (para 14).

Duties of RSE auditors:

• Review and test the RSE licensee’s systems, procedures and internal controls designed to enable reliable reporting to APRA (para 11). This review and testing must be done at least annually or more frequently if necessary to form an opinion on reliability and accuracy (para 11(a)).
• Perform at least a limited assurance engagement consistent with Auditing and Assurance Standards Board professional standards and guidance notes, insofar as those are not inconsistent with SPS 310 (para 11(b)).

Authorising officers and signatory duties:

• Submissions via D2A must be digitally signed using a digital certificate acceptable to APRA (para 13).
• The officer or agent who submits must be authorised by the Chief Executive Officer or the Chief Financial Officer of the RSE licensee (para 15).

APRA’s rights and discretions:

• Vary the reporting periods for a particular defined benefit RSE or sub‑fund by written notice (para 8).
• Specify alternative timeframes for provision of information where reporting periods are varied (para 9(b)).
• Grant written extensions of due dates (para 10).
• Vary the reporting requirements of SRF 160.1 in relation to an RSE licensee, or to one or more defined benefit RSEs or sub‑funds within the RSE licensee’s operations, by written notice (para 16).

The Reporting Standard, as provided, does not set out express penalties, fines or criminal sanctions for non‑compliance within its own text. It prescribes procedural obligations and APRA’s powers to vary reporting periods and requirements, and to grant extensions, but it contains no language creating offences or administrative penalties (paras 8, 9, 10, 16).

Enforcement mechanisms contained in the Standard are administrative rather than punitive. APRA may change reporting periods (para 8), specify new due dates when it does so (para 9(b)), grant written extensions of due dates (para 10), and vary reporting requirements for particular RSE licensees, RSEs or sub‑funds (para 16). These are instruments for tailoring operational compliance and managing timing, not express enforcement penalties.

The Standard does require assurance and audit activity,RSE auditors must review and test the systems, procedures and internal controls producing the reported information and perform a limited assurance engagement at least annually (para 11). Failure to arrange those assurance engagements could have indirect regulatory consequences insofar as auditors, trustees and licensees have overlapping obligations under audit, prudential and statutory regimes; however, such consequences are not specified in this Standard and would rest on other legal or prudential instruments.

Because the Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (para 1), there may be enforcement pathways in that Act or in the prudential framework that are not spelled out here. The Standard itself limits its express enforcement content to APRA’s administrative powers to vary, specify and extend reporting requirements and to require digital signature and assurance practices (paras 6, 10, 11, 13, 16). Any further sanctions or actions that APRA might take for non‑compliance would need to be located in APRA’s enabling legislation, in related prudential standards (for example SPS 160 or SPS 310), or in general powers APRA has under other statutes, none of which are set out in this Reporting Standard text.

In practice, RSE licensees should treat the Standard’s obligations as binding data‑collection duties that are integrated into APRA’s supervisory apparatus. Non‑provision of data, provision of unreliable data or failure to maintain the required assurance regime may lead APRA to exercise supervisory remedies available under other instruments; the Standard itself does not specify those remedies.

The Standard contains explicit cross‑references to other prudential standards and statutes and thereby integrates into the existing prudential and auditing framework. The interaction points are procedural, definitional and assurance‑related.

Legal authority: the Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (para 1). It therefore operates as a data collection instrument within the statutory architecture created by that Act. The Standard does not itself reproduce the enforcement or sanctioning powers that may exist under that or other Acts.

Prudential standards: APRA will use the information to assess compliance with Prudential Standard SPS 160 Defined Benefit Matters (para 2). The Standard also imports requirements from SPS 310 by reference when it requires assurance engagements to be consistent with Auditing and Assurance Standards Board guidance to the extent such guidance is not inconsistent with SPS 310 (para 11(b)). Those references mean that the content and application of SPS 160 and SPS 310 intersect with the reporting, assurance and audit requirements in this Standard. The Standard does not restate SPS 160 or SPS 310; it assumes their ongoing application.

Superannuation law definitions: several defined terms cross‑refer to the Superannuation Industry (Supervision) Act 1993 (SIS Act) and the Superannuation Industry (Supervision) Regulations 1994 (SIS Regulations). The Standard uses statutory definitions for RSE, RSE licensee and year of income by reference to section 10(1) of the SIS Act (para 17). Consequently, scope and timing choices depend on how those terms are defined and interpreted under the SIS Act. For example, the reporting periods are aligned to the year of income as defined in the SIS Act rather than to a universal calendar year (paras 7, 17).

Auditing standards and professional guidance: the Standard requires at least a limited assurance engagement consistent with professional standards and guidance issued by the Auditing and Assurance Standards Board, to the extent those standards are not inconsistent with SPS 310 (para 11(b)). That creates a cross‑link between APRA’s prudential requirements and the professional auditing framework. The Standard does not itself set audit procedures or sampling thresholds; it delegates technical assurance detail to professional standards.

Operational systems and APRA’s software: the Standard mandates use of APRA’s Direct to APRA (D2A) application for electronic submissions and permits APRA to notify alternative methods where D2A is unavailable (para 6). D2A is an operational interface that APRA controls; its availability and technical specifications therefore interact with the licensee’s system requirements and potential legal obligations to submit data electronically.

The Standard itself contains a small number of temporal markers and operational changes that reflect an amendment to reporting timelines and the commencement date. The text records the following timeline and status items.

Commencement and application: paragraph 4 states the Standard applies for reporting periods ending on or after 1 July 2015. Paragraph 3 specifies the entities to which it applies (each RSE licensee in respect of each defined benefit RSE and each sub‑fund within its business operations).

Change in due date: paragraph 9 sets out a clear two‑tier due‑date regime reflecting a change in the due date policy. For reporting periods ending on or after 1 July 2015 but before 1 July 2017 the required submission timeframe was within 35 calendar days after the end of the quarter. For reporting periods ending on or after 1 July 2017 the timeframe is within 28 calendar days after the end of the quarter (para 9(a)(i) and (ii)). This shift in due dates is recorded within the Standard itself and shows a tightening of reporting deadlines effective from 1 July 2017.

APRA variation and extensions: paragraphs 8, 9(b) and 10 provide mechanisms for APRA to alter reporting periods by written notice and to grant extensions in writing. Those provisions amount to a continuing right of APRA to change the reporting regime for particular RSEs or sub‑funds after the Standard’s commencement. Paragraph 8 explicitly contemplates that APRA may require more or less frequent reporting than the default quarterly schedule.

No other amendments recorded: the Standard as supplied does not include a schedule of prior amendments, rescissions, or a version history beyond the items above. There are footnote markers in the supplied text ([1], [2], [3], [4]) that appear to reference sources or annotations but the content of those footnotes is not provided in this text. The Standard does not, within the text supplied, list earlier versions of SRF 160.1 or identify any superseded instruments.

Consequently, from this document alone the only internal amendment‑type information that can be reported is the commencement date (1 July 2015), the later change in due dates effective 1 July 2017, and the continuing power of APRA to vary reporting periods and requirements or to grant extensions (paras 4, 9, 8, 10, 16). Any other amendment history would need to be established from external records or from APRA notices, which are not part of the Standard text provided here.

The Reporting Standard text supplied contains no reference to any litigation, tribunal decisions, administrative appeals, or court cases concerning SRF 160.1 or the Reporting Standard itself. There are no named cases, determinations or legal precedents cited in the Standard. The document therefore does not record any litigation history.

Because the Standard is an administrative data‑collection instrument, potential disputes over its application could arise in practice (for example, challenges to APRA’s exercise of variation powers under paragraphs 8 or 16, or disputes over the adequacy of assurance work under paragraph 11), but no such proceedings are mentioned in the text. Any litigation or contested enforcement matters would need to be identified from external case law databases, tribunal records or APRA enforcement records, none of which are included in the material provided.

In the absence of express litigation references, practitioners should not infer from the silence of this Standard that disputes have not occurred. They should instead consult relevant court and tribunal records as well as APRA enforcement publications to determine whether any judicial or administrative decisions have interpreted these paragraphs or APRA’s related powers under the Financial Sector (Collection of Data) Act 2001 or other statutes. That material is outside the scope of this Standard’s text.

This Reporting Standard contains several operational and governance prescriptions that frequently trip up implementers if not carefully managed. The following points are drawn directly from the text and identify common compliance risks, timing traps and delegation issues.

Scope tied to SPS 160 definitions: the Standard applies to defined benefit RSEs and defined benefit sub‑funds as defined in SPS 160 (paras 3, 17). Misclassifying funds because of internal accounting labels rather than prudential definitions can lead to under‑reporting. The Standard’s scope is not the same as accounting or tax classifications, it is prudentially defined.

Reporting periods aligned to year of income: reporting is quarterly but is explicitly based on the year of income of each defined benefit RSE or the RSE within which a sub‑fund is located (para 7, 17). If a licensee has multiple defined benefit RSEs or sub‑funds with different years of income, reporting cadence and quarter boundaries can differ across those legal entities. Treating all reporting as aligned to a single calendar year may produce submission timing errors.

Tight deadlines and historical change: due dates are tight (28 calendar days after quarter end for periods ending on or after 1 July 2017) and the Standard records a prior 35‑day requirement for an earlier period (para 9). Professionals should note which rule applies to their reporting period and ensure operational calendars reflect the applicable timeframe.

APRA’s discretion to change frequency and requirements: APRA may require more or less frequent reporting for particular RSEs or sub‑funds and may vary reporting requirements by written notice (paras 8, 16). Changes may arrive on short notice; governance processes should include monitoring for APRA notices and a capacity to adapt reporting frequency and form.

Assurance minimums and potential conflicts: the RSE auditor must review and test systems, procedures and internal controls and perform at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance, where not inconsistent with SPS 310 (para 11). The phrase “to the extent that they are not inconsistent with the requirements of SPS 310” creates a potential sequencing or scope issue between auditing professional guidance and SPS 310; practitioners need to reconcile the two when designing the assurance engagement.

Board and senior management responsibility: paragraph 12 places responsibility on the Board and senior management to ensure an appropriate set of policies and procedures for authorisation of information submitted to APRA. Some licensees treat data submission as an operational function under outsourced arrangements; the Standard makes clear that ultimate responsibility rests with the Board and senior management.

Compliance under this Reporting Standard requires coordinated operational, governance, audit and technical steps. The following is a checklist‑style sequence grounded in the Standard’s paragraphs.

1. Identify scope and reporting entities (paras 3, 17).

   • Confirm which RSEs and sub‑funds are “defined benefit” under SPS 160 and therefore in scope.
   • For each in‑scope RSE or sub‑fund, determine the year of income per the SIS Act definition to set the reporting calendar (paras 7, 17).

2. Establish reporting cadence and due‑date calendars (paras 7, 9).

   • Set quarterly reporting periods based on each RSE’s year of income.
   • Apply the correct due date rule: historically 35 days for reporting periods ending on or after 1 July 2015 but before 1 July 2017; 28 days for periods ending on or after 1 July 2017 (para 9).
   • Maintain an internal calendar that flags APRA notices that may change reporting periods (para 8).

3. Design data collection and systems, with internal controls (paras 11, 12).

   • Implement systems and procedures that capture the SRF 160.1 dataset reliably.
   • Document internal controls and authorisation workflows for sign‑off by Board and senior management (para 12).
   • Ensure processes can produce the dataset in the electronic format required by D2A (para 6).

4. Engage the RSE auditor for ongoing review and assurance (para 11).

   • Plan for the RSE auditor to review and test systems, procedures and internal controls at least annually or more frequently if necessary (para 11(a)).
   • Arrange for at least a limited assurance engagement consistent with Auditing and Assurance Standards Board professional standards and guidance notes, ensuring compatibility with SPS 310 (para 11(b)).
   • Ensure auditor reporting timelines align with the submission due dates.

5. Implement D2A submission capability and digital certificate arrangements (paras 6, 13).

   • Obtain and test the Direct to APRA application (D2A) or confirm APRA‑notified alternative submission methods where D2A is unavailable (para 6).
   • Obtain a digital certificate acceptable to APRA for the officer or agent who will sign submissions, and integrate signing into submission workflows (para 13).