Financial Sector (Collection of Data) (reporting standard) determination No. 7 of 2015 - SRS 320.1 - Statement of Financial Position

The Reporting Standard is structured around a small set of core concepts. The primary reporting unit is the defined benefit "sub-fund" as that term is defined in Prudential Standard SPS 160 Defined Benefit Matters. The Standard applies to each registrable superannuation entity licensee in respect of each sub-fund within its business operations (para 3). The reporting obligation is therefore at the RSE licensee level but directed to each defined benefit sub-fund located within the RSE.

"Reporting period" is a defined term that, absent an APRA variation, means the period relevant to the requirement in paragraph 7: each year of income of each RSE within which a sub-fund is located (para 7). "Year of income" and the meaning of RSE and RSE licensee are drawn from section 10(1) of the Superannuation Industry (Supervision) Act 1993 as captured in the Interpretation section (para 17). The "due date" for the return is specified as within three months after the end of the relevant year of income, unless APRA specifies a different time by notice or grants an extension in writing (paras 9 and 10).

"SRF 320.1 Statement of Financial Position" is the form that identifies the data fields APRA requires; the Standard mandates provision of the information required by that form for each reporting period (para 5). The method of delivery is electronic using APRA’s Direct to APRA application, colloquially D2A, or another method APRA notifies in writing where D2A is not available (para 6). The Standard notes D2A may be obtained from APRA (para 6 note).

Quality control is a central concept. The information must be the product of systems, procedures and internal controls reviewed and tested by the RSE auditor of the RSE in which the sub-fund is located (para 11). That review and testing must be undertaken at least annually, and must include at least a limited assurance engagement consistent with professional standards and guidance notes issued by the Auditing and Assurance Standards Board, but only to the extent those are not inconsistent with the requirements of Prudential Standard SPS 310 (para 11(b)). The Board and senior management of the RSE licensee are explicitly assigned responsibility to ensure appropriate internal review and authorisation policies and procedures are in place (para 12).

Authorisation and custody of submissions are also key. Submissions made via D2A must be digitally signed with a certificate acceptable to APRA (para 13). If an agent submits on a licensee’s behalf, the licensee must obtain and retain a copy of the completed form submitted (para 14). Submissions must be made by an officer or agent authorised by the CEO or the CFO of the RSE licensee (para 15).

Finally, APRA’s supervisory discretion is embedded in two mechanisms: changing reporting periods in particular circumstances (para 8) and varying reporting requirements for a specific RSE licensee or its sub-funds by written notice (para 16). Those mechanisms allow APRA to tailor frequency, timing or content to particular circumstances.

The immediate legal addressees are RSE licensees that have one or more defined benefit sub-funds within their business operations. Paragraph 3 states the Standard applies "to each registrable superannuation entity (RSE) licensee in respect of each sub-fund within its business operations." The Interpretation section confirms the meanings of RSE and RSE licensee are those given in s 10(1) of the Superannuation Industry (Supervision) Act 1993 (para 17). Because the Standard uses the term "sub-fund" as defined in Prudential Standard SPS 160, the universe of affected sub-funds is the class of defined benefit sub-funds captured by SPS 160 (para 17).

Internal stakeholders at affected RSE licensees who will have duties or be implicated include the Board and senior management (para 12), the Chief Executive Officer and Chief Financial Officer because they are the named officers whose authorisation is required for submission (para 15), and in-house systems and controls personnel responsible for preparing the SRF 320.1 information and maintaining the internal review and authorisation processes (paras 11 and 12). The RSE auditor is an expressly affected external party. Paragraph 11 requires the RSE auditor to review and test the RSE licensee’s systems, procedures and internal controls designed to enable reliable reporting to APRA, to do so at least annually or more frequently if necessary, and to perform at least a limited assurance engagement consistent with professional standards and guidance notes to the extent not inconsistent with SPS 310.

Agents engaged by RSE licensees to submit returns on their behalf are affected as well. Paragraph 14 requires that if an agent submits using D2A on the licensee’s behalf the licensee must obtain and retain a copy of the completed form. The officer or agent who submits must be authorised by the CEO or CFO (para 15) and, if using D2A, must digitally sign with an APRA-acceptable certificate (para 13).

APRA is both the recipient and the decisionmaker under the Standard. APRA can change reporting periods for a particular sub-fund where it considers it necessary or desirable (para 8), grant reporting extensions in writing (para 10), and vary the reporting requirements of SRF 320.1 in relation to an RSE licensee or one or more sub-funds by written notice (para 16). The Standard therefore affects APRA operationally because it dictates methods of submission, quality assurance expectations and the circumstances in which APRA will exercise discretion to vary content or frequency.

Those not directly affected by the instrument include RSE licensees that do not have defined benefit sub-funds, and non-RSE entities. The Standard makes no reference to private individuals or employers except insofar as they may be beneficiaries of an RSE containing a defined benefit sub-fund; no direct obligations are placed on those parties within this document.

Duties imposed on RSE licensees are concrete and specific. The primary duty is to provide APRA with the information required by SRF 320.1 in respect of each reporting period for each applicable sub-fund (para 5). This obligation is annual as a baseline: subject to paragraph 8, the licence holder must provide the information in respect of each year of income of each RSE within which a sub-fund is located (para 7). The basic due date for provision is within three months after the end of the year of income to which the information relates (para 9(a)).

The Standard imposes duties about the format and delivery method. The information must be given to APRA in electronic format using the Direct to APRA application or, where D2A is not available, by a method notified by APRA in writing prior to submission (para 6). An associated duty is to digitally sign the information when submitted using D2A with a digital certificate acceptable to APRA (para 13).

Quality control duties attach to the preparation of the information. Paragraph 11 mandates that the information must be the product of systems, procedures and internal controls that have been reviewed and tested by the RSE auditor of the RSE in which the sub-fund is located. That review must be performed on an annual basis or more frequently if necessary and must include at least a limited assurance engagement consistent with professional standards and guidance notes issued by the Auditing and Assurance Standards Board, as may be amended from time to time, to the extent they are not inconsistent with SPS 310 (para 11(b)). Paragraph 12 requires the RSE licensee to maintain systems, processes and controls for internal review and authorisation of the information and assigns responsibility for that obligation to the Board and senior management.

If an agent submits returns, the RSE licensee has the duty to obtain and retain a copy of the completed form submitted by the agent (para 14). The RSE licensee must ensure that the officer or agent submitting information is authorised by the CEO or CFO (para 15).

Rights or procedural safeguards present in the instrument are limited but specified. APRA may grant an extension of a due date in writing, in which case the new date on the notice of extension becomes the due date (para 10). APRA may also, by written notice, change reporting periods for a particular sub-fund where APRA considers it necessary or desirable (para 8). Separately, APRA may vary SRF 320.1 reporting requirements for a particular RSE licensee or one or more sub-funds by written notice (para 16). These are rights that rest with APRA, not the licensee. The licensee’s procedural right is to seek or rely on any written extension or variation that APRA grants; the Standard specifies how such notices operate (paras 8, 10 and 16).

There are procedural duties concerning authorisation: the submitting officer or agent must be authorised by the CEO or CFO (para 15). There is a record-keeping duty if an agent is used: the licensee must obtain and retain the completed copy provided to APRA (para 14). Finally, the Standard requires compliance with external professional standards as part of the RSE auditor’s assurance work (para 11(b)), which imposes a duty to ensure the auditor’s engagement conforms to relevant auditing and assurance professional standards, subject to SPS 310 consistency.

The Standard does not itself create statutory privacy rules, confidentiality exemptions, or explicit data publication procedures beyond stating in paragraph 2 that the information is used by APRA for prudential supervision and publication. The Standard does not set out appeal rights against APRA’s notices, nor does it set penalties in this instrument. Those matters sit outside the text of the Standard as provided.

The Reporting Standard as reproduced here does not set out any specific penalties, civil sanctions, criminal offences, or detailed enforcement procedures. The instrument prescribes obligations and processes for submission, authorisation, assurance and record-keeping (paras 5, 6, 9 to 15), and describes APRA’s discretion to vary reporting periods, reporting requirements and to grant extensions (paras 8, 10 and 16), but it does not include express penalty schedules or enforcement mechanics within its text.

Because the Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (para 1), enforcement, sanctions, or consequences for non-compliance may be found in the enabling legislation or other applicable legislation that confer enforcement powers on APRA. The Standard itself, however, does not reproduce those enforcement provisions nor does it specify internal APRA administrative steps for non-compliance. The document likewise does not specify any administrative review, internal appeal or external merits review process for APRA’s exercise of discretions under the Standard such as variation of reporting requirements or reporting periods.

Given the absence of penalties or enforcement procedures in the text, readers should treat the duties and dates in the Standard as mandatory subject-matter obligations, and should look to the enabling statute and APRA’s broader regulatory framework for the practical consequences of late, incomplete, inaccurate or omitted returns. The Standard does indicate some procedural responses APRA may take within its remit under the instrument: it can change reporting periods (para 8), grant extensions in writing (para 10) and vary the reporting requirements for specific licensees or sub-funds by written notice (para 16). Those are the only express administrative mechanisms contained in the Standard itself for responding to particular circumstances.

The RSE auditor’s role is also specified, but the Standard does not detail any sanctioning route against auditors within this text. Paragraph 11 sets out the auditor’s review and assurance requirements but does not specify penalties for failure to perform those duties.

In short, the Reporting Standard sets out obligations, assurance expectations and APRA’s discretionary administrative powers, but it does not itself set or enumerate enforcement penalties. The practical enforcement framework will depend on the relevant powers and processes conferred by the Financial Sector (Collection of Data) Act 2001 and other instruments not reproduced in this document.

The Reporting Standard explicitly imports or references several external instruments and professional frameworks, and repeatedly ties its definitions to existing statutory meanings. Paragraph 1 states the Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001. The Interpretation section (para 17) explicitly defines key terms by reference to other legislation and prudential standards: "APRA" is defined by reference to the Australian Prudential Regulation Authority Act 1998; "RSE" and "RSE licensee" are defined by reference to section 10(1) of the Superannuation Industry (Supervision) Act 1993; and "year of income" likewise has the meaning given in section 10(1) of the SIS Act.

The Standard relies on Prudential Standard SPS 160 for the meaning of "sub-fund" (para 17). That means the class of entities and sub-funds brought within the Standard’s scope depends on the definition provided by SPS 160. The Standard also cross-references Prudential Standard SPS 310 in the context of assurance requirements: paragraph 11(b) requires the RSE auditor to undertake at least a limited assurance engagement consistent with professional standards and guidance notes issued by the Auditing and Assurance Standards Board "to the extent that they are not inconsistent with the requirements of SPS 310." This creates a prioritisation rule: professional auditing standards apply unless inconsistent with SPS 310, in which case SPS 310 would take precedence for the relevant aspects of assurance work.

The Standard’s reliance on APRA-provided digital submission infrastructure (Direct to APRA) means it interacts operationally with APRA’s IT systems. Paragraph 6 requires electronic submission using D2A or another method notified by APRA where D2A is unavailable, and notes that D2A may be obtained from APRA. That cross-references APRA’s systems and potentially APRA’s terms for use of the software.

The Standard does not itself restate or change privacy, confidentiality, record retention or information publication rules contained in other laws. Paragraph 2 states that the information collected is used by APRA for prudential supervision and publication, but it does not identify the statutory privacy regime or the statutory authorisation for publication. Those matters therefore remain governed by the relevant provisions in the enabling or related statutes and APRA’s policies, which are not reproduced in this text.

The Standard also situates company officer definitions internally: "Chief Executive Officer" and "Chief Financial Officer" are defined generically in para 17 as the CEO and CFO of the RSE licensee "by whatever name called." That avoids conflict with company law titles by using the practical incumbency within the RSE. The mandatory requirement that the submitting officer be authorised by the CEO or CFO (para 15) therefore interacts with the internal appointment and delegation regimes under corporate law and the RSE’s constitution, though those instruments are not discussed here.

Finally, the Standard’s non-exhaustive referencing of external professional standards and prudential standards means its operational effect will depend on the content of SPS 160 and SPS 310, and the Auditing and Assurance Standards Board guidance. Paragraph 11(b) makes that relationship explicit; RSE licensees and auditors must read the Standard alongside those instruments to determine precise assurance practice and the precise population of sub-funds in scope.

The Reporting Standard text provided here contains a single clear commencement statement and no express subsequent amendments within the document. Paragraph 4 states the Standard "applies for reporting periods ending on or after 1 July 2015." No later amendment clauses, repeal history, or modification notes are included in the text supplied.

The instrument contains footnote markers [1], [2] and [3] in paragraphs 3, 11 and 17 respectively. The content of those footnotes is not reproduced in the body of the text provided. Where footnotes are referred to but their text is not included, users should check the original instrument as published by APRA for any additional cross-references, explanatory material or transitional arrangements that might have been contained in those footnotes.

There are no recorded insertions, savings clauses, transitional arrangements or sunset clauses shown in the provided text beyond the commencement date. Paragraphs 8, 10 and 16 do give APRA powers to change reporting periods, grant extensions and vary requirements by written notice, but those are operational discretions rather than formal amendments to the Standard’s text. The Standard itself does not lay out an amendment procedure within the document beyond its being made under the enabling statutory power in paragraph 1.

If an updated status or consolidated version is required, readers will need to consult APRA’s published instrument register or the Federal Register of Legislation for any subsequent amendments, consolidations, revocations or replacement instruments. The text provided should be treated as the version that commenced 1 July 2015 unless and until a later amendment is identified in the authoritative legislative or APRA publication.

The Reporting Standard text supplied contains no references to litigation, court decisions, administrative reviews, or judicial consideration. There are no case citations, no references to disputes about the Standard’s interpretation, and no recorded challenges or judicial clarifications included in the document itself.

Because the Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (para 1), any litigation or merits review that has arisen from obligations under this Standard would be recorded in external legal sources, court records or administrative determinations, none of which are reproduced here. The document as provided does not include an annex or note of any litigation history.

Practitioners seeking to know whether the Standard has been the subject of judicial review, enforcement action, or contested interpretation should consult public court records, APRA enforcement publications, or legal reporting services. The absence of litigation references in the instrument itself means the Standard contains no internal record of case law or adjudicative history.

Several practical pitfalls and potential sources of implementation error are embedded within the Standard’s text. First, the scope is narrower than a general superannuation reporting obligation; it applies to RSE licensees in respect of each defined benefit sub-fund as that term is defined in Prudential Standard SPS 160 (para 3 and Interpretation para 17). If an RSE has both accumulation and defined benefit sub-funds, only the defined benefit sub-fund classification triggers this Standard. Misreading "sub-fund" to include non-defined benefit sub-funds would lead to unnecessary reporting.

Second, the reporting unit is the sub-fund. Paragraph 7 requires reporting "in respect of each year of income of each RSE within which a sub-fund is located." That means where an RSE licensee operates multiple defined benefit sub-funds, separate SRF 320.1 returns will be required for each sub-fund for each year of income. Practitioners should not assume a single consolidated return will satisfy the obligation.

Third, quality control obligations are specific and place duties both on the RSE auditor and on the RSE licensee’s Board and senior management. Paragraph 11 requires the RSE auditor to review and test systems, procedures and internal controls and to perform at least a limited assurance engagement annually or more frequently where necessary. Paragraph 12 places responsibility for internal review and authorisation policies and procedures squarely on the Board and senior management. Failure to have those systems and auditor reviews in place could render a submission non-compliant even if the numbers in SRF 320.1 are accurate.

Fourth, the auditor assurance standardisation clause in paragraph 11(b) creates an interaction trap. The limited assurance engagement must be consistent with professional standards and guidance notes issued by the Auditing and Assurance Standards Board "to the extent that they are not inconsistent with the requirements of SPS 310." That requires a cross-check between professional auditing guidance and SPS 310; practitioners cannot assume standard limited assurance practice without verifying whether SPS 310 introduces different requirements for this work.

Fifth, authorisation and submission mechanics are prescriptive. Submissions using D2A require a digital certificate acceptable to APRA (para 13). The standard requires the submitting officer or agent to be authorised by the CEO or CFO (para 15). If an agent submits on behalf of a licensee, the licensee must obtain and retain a copy of the completed form (para 14). Failure to maintain the required authorisation chain, a compliant digital certificate, or the retention of agent-submitted copies may lead to administrative non-compliance.

Sixth, APRA has residual administrative discretions that can change the operational parameters. Paragraph 8 allows APRA to require more or less frequent reporting for a particular sub-fund by written notice; paragraph 16 allows APRA to vary SRF 320.1 reporting requirements by notice for a specific licensee or sub-fund. RSE licensees must therefore monitor APRA communications actively and not assume the baseline annual schedule or the form content will remain unchanged.

Seventh, the Standard does not set out penalties or an explicit enforcement pathway (see Penalties and enforcement). Practitioners should not infer from that absence that APRA lacks enforcement options. Instead, the absence means that enforcement and sanctioning will be governed by the enabling and other statutes and APRA’s own policies, none of which are reproduced in this instrument.

Eighth, the commencement date is fixed. The Standard applies for reporting periods ending on or after 1 July 2015 (para 4). For transitional reporting obligations or prior data requests, practitioners must look to other instruments or APRA notices. The Standard’s footnote references are not reproduced in the text provided. Those footnotes may contain transitional or clarificatory material. Failure to consult the original instrument with footnotes risks missing explanatory or saving provisions.

Finally, the Standard records that APRA may notify an alternative submission method where D2A is not available (para 6). Relying on D2A being always available without an agreed contingency procedure may present operational risk. Practitioners should confirm APRA’s operational instructions prior to each submission window and maintain contingency processes to respond to APRA notices varying method, timing, or content.

Checklist and stepwise compliance actions grounded in the Standard’s text:

1. Confirm scope and identify sub-funds in scope. Determine whether the RSE licensee operates any defined benefit sub-funds as defined in Prudential Standard SPS 160 because the Standard applies only to those sub-funds (para 3 and Interpretation para 17).

2. Establish reporting periods. For each applicable sub-fund, identify the relevant year of income as defined by section 10(1) of the SIS Act and schedule SRF 320.1 submissions for each year of income ending on or after 1 July 2015, unless APRA has changed the reporting period by written notice (paras 4 and 7; para 8 permits APRA to change reporting periods).

3. Prepare the SRF 320.1 Statement of Financial Position for each sub-fund and for each reporting period. Ensure that the SRF 320.1 is completed in accordance with APRA’s instructions for that form (para 5).

4. Put governance and internal controls in place. Ensure systems, processes and controls are developed for internal review and authorisation of data intended for APRA, and that the Board and senior management have oversight and policies that ensure appropriate authorisation procedures (para 12).

5. Engage the RSE auditor early. Arrange for the RSE auditor to review and test the RSE licensee’s systems, procedures and internal controls supporting the SRF 320.1 data. The auditor’s work must be undertaken at least annually or more frequently if necessary and must include at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance, to the extent not inconsistent with SPS 310 (para 11).

6. Maintain audit evidence and documentation. Ensure audit planning, workpapers and the limited assurance engagement documentation are retained in line with professional standards as this audit work underpins the report’s reliability (para 11).

7. Adopt a submission protocol. Register for and obtain APRA’s Direct to APRA software where appropriate, or confirm an alternative APRA-notified method where D2A is not available. Review the APRA guidance for D2A and have technical staff test the submission pathway ahead of the due date (para 6).

8. Secure digital signing capability. Obtain or arrange a digital certificate acceptable to APRA for the officer or agent who will submit via D2A. Confirm certificate validity and the process for renewal ahead of submission deadlines (para 13).

9. Authorise submitters. Ensure any officer or agent who will submit the SRF 320.1 is expressly authorised by the RSE licensee’s CEO or CFO in advance of submission. Maintain written authorisations on file (para 15).

10. If using an agent, document and retain copies. Where an agent submits on the licensee’s behalf, obtain from that agent a copy of the completed form as provided to APRA and retain that copy in the licensee’s records (para 14).

11. Meet due dates or seek extensions. Prepare to submit each SRF 320.1 within three months after the end of the year of income unless APRA has specified a different deadline by written notice. If more time is needed, make a written application to APRA and secure a written extension; APRA’s written extension will set the new due date (paras 9 and 10).

12. Monitor APRA notices for variations. Keep a compliance log of APRA written notices affecting reporting periods, submission methods or content, and implement any APRA-directed changes to frequency or form content promptly (paras 8 and 16).

13. Reconcile internal and external reporting. Where other regulatory reporting obligations exist for the RSE or other sub-funds, align internal processes so the SRF 320.1 preparation is consistent with ledger and statutory accounts, and ensure differences are documented and explainable to APRA and the RSE auditor (paras 11 and 12).

14. Implement record retention and audit trail. Retain copies of submitted SRF 320.1 forms, digital certificate details, submitter authorisations, internal sign-off records, and the RSE auditor’s review workpapers. This retains an evidentiary trail in case APRA questions a submission or requests clarification (paras 12, 13 and 14).

15. Cross-check assurance consistency with SPS 310. Work with the RSE auditor to confirm the scope and format of the limited assurance engagement aligns with Auditing and Assurance Standards Board guidance and is not inconsistent with SPS 310 requirements, addressing any inconsistencies before the audit is finalised (para 11(b)).

16. Integrate the process into the RSE licensee’s annual compliance calendar. Make SRF 320.1 preparation and audit review a recurring annual task tied to the year-of-income cycle, with checkpoints for data collation, auditor engagement, Board sign-off on authorisation policies, digital certificate validation, agent coordination and final submission.

Adhering to these steps aligns operations with the Standard’s explicit requirements. Because APRA retains the administrative ability to vary reporting periods and requirements and to grant extensions by written notice, compliance should also include an active monitoring function to capture APRA communications and act on any bespoke directives affecting timing, frequency or content.