Financial Sector (Collection of Data) (reporting standard) determination No. 11 of 2017

The Reporting Standard builds on a small set of definitional and operational concepts. The principal concepts are “RSE licensee”, “relevant RSE”, “reporting period”, the SRF 720.0 form, submission method, and quality control and authorisation protocols.

Relevant RSE: A relevant RSE for the Standard is an RSE, defined benefit RSE, pooled superannuation trust (PST) or eligible rollover fund (ERF) that had total assets equal to or greater than $200 million at the end of the most recent year of income at the time of reporting (paragraph 4). The instrument explicitly excludes from the RSE definition, for the purposes of this Standard, some categories identified in the SIS Act; the defined list of “RSE” in paragraph 19 states an RSE means a registrable superannuation entity as defined in section 10(1) of the SIS Act that is not a defined benefit RSE, PST, ERF, small APRA fund or single member approved deposit fund. The interplay of these definitions means that the Standard can apply to several types of vehicles (RSEs, defined benefit RSEs, PSTs and ERFs) subject to the $200 million asset threshold (paragraphs 3, 4 and 19).

Form and use: Information collected in SRF 720.0 is used by the Australian Bureau of Statistics (ABS) for compilation of the Australian National Accounts and other publications, and may be used by APRA for prudential supervision and publication (paragraph 2). The Standard therefore channels administrative accounting and balance sheet data into ABS and APRA uses.

Reporting periods and due dates: The default reporting rhythm is quarterly based on the RSE’s year of income (paragraph 8). The Standard sets a specific due date for quarterly submissions of 28 calendar days after the end of the quarter (paragraph 10(a)). APRA retains the power to require a different reporting frequency or timing for a particular RSE where it considers it necessary or desirable (paragraph 9), and it may specify alternate due dates by written notice (paragraph 10(b)). APRA may also grant extensions in writing (paragraph 11).

Submission method: The Standard requires electronic submission using APRA’s ‘Direct to APRA’ application where available (paragraph 7). Where D2A is not available, APRA may notify an alternative method in writing. The D2A software is noted as obtainable from APRA. For submissions via D2A, the submitting officer or agent must digitally sign using a digital certificate acceptable to APRA (paragraph 15).

Quality control and estimation: Reporting must be subject to internal systems, processes and controls for review and authorisation (paragraph 12). The Board and senior management carry responsibility to ensure appropriate policies and procedures are in place (paragraph 12). The Standard does not require the RSE auditor to audit or test the reported information (paragraph 13). Where accurate information is not readily available, the licensee may report a “careful estimate” provided that estimate is the product of the licensee’s systems, processes and controls developed for that purpose (paragraph 14).

Authorisation and record retention: Submissions must be authorised by the CEO or CFO in respect of the officer or agent making the submission (paragraph 17). If an agent submits on the licensee’s behalf, the licensee must obtain and retain a copy of the completed form submitted (paragraph 16).

Variation: APRA may, by written notice to an RSE licensee, vary SRF 720.0 reporting requirements as they apply to that licensee or one or more relevant RSEs in its operations (paragraph 18). The Standard thus establishes a baseline with express APRA discretion to change the obligations for particular entities.

Interpretation cluster: Paragraph 19 lists statutory references and definitions used for interpretation, including APRA, the meaning of CEO and CFO for these purposes, defined benefit RSE, ERF, PST, RSE auditor, RSE licensee, SIS Act and year of income. Those definitions determine the scope and some operational requirements of the Standard.

Primary statutory obligors: The immediate legal obligors under the Standard are RSE licensees that fall within the defined application scope. Paragraph 3 says the Standard “applies to each RSE licensee in respect of each relevant RSE within its business operations.” A “relevant RSE” is an RSE, defined benefit RSE, PST or ERF with total assets of $200 million or more at the end of the most recent year of income (paragraph 4). Accordingly, the direct compliance burden falls on RSE licensees that operate such large funds or trusts. Paragraph 19 defines RSE licensee with reference to the SIS Act.

Who bears operational cost: The RSE licensee bears the operational cost of collecting, validating, and submitting the SRF 720.0 data. Paragraphs 6, 12, 14, 15 and 16 identify duties that create direct costs: implementing systems, processes and controls for internal review and authorisation (paragraph 12); producing careful estimates when accurate data are not readily available (paragraph 14); acquiring and using a digital certificate acceptable to APRA for D2A submissions (paragraph 15); and retaining copies of agent-submitted forms (paragraph 16). If an agent submits reports on behalf of a licensee, the licensee must still retain the completed form and ensure the agent is authorised, which shifts some administrative burdens back to the licensee (paragraphs 16 and 17).

Governance actors who decide and sign: The instrument assigns authorisation responsibilities to named senior officers. An officer or agent who submits information must be authorised by either the Chief Executive Officer or the Chief Financial Officer of the RSE licensee (paragraph 17). The instrument also places responsibility for ensuring an appropriate set of policies and procedures for authorisation on the Board and senior management of the RSE licensee (paragraph 12). These provisions make the Board and senior executives the decision nodes for compliance and authorisation.

APRA’s role: APRA is the recipient and regulator under this Standard. APRA can set the method of submission (paragraph 7), grant extensions (paragraph 11), change reporting frequency or periods for particular RSEs by notice (paragraph 9), and vary reporting requirements for a licensee by written notice (paragraph 18). APRA thus controls both the timing and the specific content or format for individual licensees through notices, in addition to operating D2A.

Third parties: Agents that submit on behalf of a licensee are involved operationally. Paragraph 16 requires the licensee to obtain and retain the completed copy from the agent, and paragraph 15 requires that whoever uses D2A signs the submission with a digital certificate acceptable to APRA. RSE auditors are explicitly disassociated from a mandatory audit or testing role for reported information; the Standard states the information is not required to be audited or tested by the RSE auditor (paragraph 13).

Excluded or marginal entities: The Standard’s definition of RSE in paragraph 19 excludes defined benefit RSEs, PSTs, ERFs, small APRA funds and single member approved deposit funds from the term “RSE” for the purposes of that interpretation. However, paragraph 4 separately identifies defined benefit RSEs, PSTs and ERFs as types of relevant RSEs subject to the asset threshold. This means the Standard targets larger funds across several legal categories rather than very small funds and single member deposit funds.

Users of data: The ABS is an intended user of the SRF 720.0 data for the compilation of National Accounts and other publications, and APRA may use the data for prudential supervision and publication (paragraph 2). These destination statements define the downstream consumers of the submitted data and help determine the type of information required.

Duties established by the Standard are primarily data provision, internal control, authorisation and recordkeeping obligations. Rights are largely procedural: the ability to apply estimates under conditions, to seek an extension, and to receive alternative reporting instructions from APRA.

Duty to provide specified data: An RSE licensee to which the Standard applies must provide APRA with the information required by SRF 720.0 in respect of each reporting period (paragraph 6). That duty is continuous for each relevant RSE and for each reporting period as defined by the Standard or as varied by APRA (paragraphs 8 and 9).

Duty to submit electronically: The required information must be given to APRA in electronic format using D2A, or if D2A is not available, by a method notified by APRA in writing prior to submission (paragraph 7). The note under paragraph 7 identifies D2A software as obtainable from APRA. For practical compliance, the licencee must ensure technical capability to use D2A and any digital certificate requirements imposed by APRA (paragraph 15).

Duty to meet timetables and apply for extensions where needed: Quarterly information must be provided within 28 calendar days after the end of the quarter to which the information relates (paragraph 10(a)). Where APRA has specified alternative reporting periods under paragraph 9, the licensee must provide information within the time specified in that written notice (paragraph 10(b)). APRA may grant extensions in writing, and the new due date will be the date on the notice of extension (paragraph 11). These duties create calendar-driven compliance processes within licensee operations.

Duty to implement internal review and governance: All information provided must be subject to systems, processes and controls developed by the RSE licensee for internal review and authorisation (paragraph 12). The Board and senior management bear responsibility to ensure appropriate policies and procedures for authorisation are in place (paragraph 12). That is a governance-level obligation which will typically require documented policies, delegated authorities, and evidence of internal signoffs.

Duty to report accurate information and to use controlled estimates where necessary: The licensee must ensure information reported is “as accurate as possible” (paragraph 14). Where accurate information is not readily available, the licensee may provide a “careful estimate” if that estimate is produced by the licensee’s systems, processes and controls developed for that purpose (paragraph 14). This creates both an obligation to aim for accuracy and a limited right to use estimates under controlled conditions.

Authorisation and signature duties: Submissions using D2A require a digital signature using an APRA-acceptable digital certificate (paragraph 15). The submitting officer or agent must be authorised by the CEO or CFO (paragraph 17). An agent who submits on behalf of a licensee triggers a duty on the licensee to obtain and retain a copy of the completed form (paragraph 16).

APRA variation rights and licensee rights: APRA may, by notice, change reporting frequency for a particular relevant RSE if it considers it necessary or desirable (paragraph 9) and may vary reporting requirements in relation to a particular licensee or RSE (paragraph 18). On the licensee side, APRA may grant extensions in writing (paragraph 11). Thus, APRA has discretion to change the compliance profile of an entity, while licensees have procedural rights to receive written notice and to request or obtain extensions.

Absence of audit requirement: The Standard explicitly states that the information is not required to be audited or tested by the RSE auditor (paragraph 13). This duty allocation clarifies that the licensee’s internal controls, not external audit, are the primary assurance mechanism for these returns under this Standard.

Recordkeeping requirement: If an agent submits on the licensee’s behalf, the licensee must obtain a copy of the completed form and retain it (paragraph 16). That is a specific record retention duty tied to the use of agents for submission.

The Reporting Standard specifies obligations and APRA discretion but does not itself set out express penalties, fines or criminal sanctions within its text. The instrument focuses on procedural requirements, timetable obligations, and governance and authorisation protocols. The following enforcement-relevant mechanisms are present in the Standard.

APRA’s administrative controls and notices: APRA controls submission method (paragraph 7), can require different reporting frequency or timing for a particular RSE by written notice (paragraph 9), can specify due dates for non-standard reporting periods (paragraph 10(b)), and may vary reporting requirements by written notice to an RSE licensee (paragraph 18). These notice powers are mechanisms by which APRA can change an entity’s obligations and thereby influence compliance. The Standard also provides that APRA may grant written extensions to due dates (paragraph 11). These are administrative levers for APRA to manage compliance.

Obligations that enable monitoring: The Standard requires digital submissions through D2A and digital certificates for signatories (paragraph 15), and it authorises APRA to receive data electronically (paragraph 7). Electronic submissions combined with identified authorised submitters enable APRA to monitor and attribute compliance. The requirement that the licensee ensure systems, processes and controls for internal review and authorisation are in place and that the Board and senior management bear responsibility (paragraph 12) creates an expectation of governance oversight that APRA can observe or inquire into.

Record retention and audit caveats: The Standard requires RSE licensees to retain copies of completed forms submitted by agents (paragraph 16), which supports post-submission review. The Standard expressly states the information is not required to be audited or tested by the RSE auditor (paragraph 13). That absence reduces direct involvement of external auditors in enforcement under this Standard, placing reliance instead on internal controls and APRA oversight.

No explicit sanctions in the Standard text: The Standard does not enumerate sanctions, monetary penalties, or express powers to issue infringement notices or directions in its own paragraphs. Where enforcement or sanctioning powers exist, they are not contained in this Reporting Standard text as provided. Users of the Standard should therefore note that it prescribes obligations and administrative levers but does not itself describe enforcement penalties or a sanction regime within these paragraphs.

Implication for compliance monitoring: Because the Standard mandates electronic reporting of a defined form and gives APRA discretion to alter timing and content by written notice, APRA’s practical enforcement path will be through monitoring submissions, written correspondence, and potentially other statutory powers outside this instrument. The Standard equips APRA with structured data and authorisation metadata that facilitate detection of non-compliance, but the Standard itself does not define the downstream enforcement steps or penalties.

The Reporting Standard explicitly references and is made under a particular statutory collection power, and it adopts definitions from related statutes. It therefore operates in a legal environment shaped by the instruments it cites.

Statutory basis for the reporting power: The instrument is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). That is the statutory authority that enables the reporting requirement in this Standard. The Standard’s requirements are therefore an exercise of that delegated power.

Cross-references to SIS Act definitions: Paragraph 19 uses and references definitions from the Superannuation Industry (Supervision) Act 1993 (SIS Act), for example by defining eligible rollover fund (ERF), pooled superannuation trust (PST), year of income and what counts as an RSE by reference to section 10(1) of the SIS Act. The Standard therefore should be interpreted in conjunction with the SIS Act definitions for those terms. The Standard itself draws its scope from those SIS Act categories and from asset thresholds.

APRA’s statutory identity: Paragraph 19 defines APRA as the Australian Prudential Regulation Authority established under the Australian Prudential Regulation Authority Act 1998. The Standard’s assigns functions to APRA in receiving, using and varying data requirements, so it operates within APRA’s statutory context under that Act. While the Standard does not reproduce APRA’s wider powers, it situates the Reporting Standard as one of APRA’s data collection instruments.

Data usage by ABS and APRA: Paragraph 2 states the ABS uses SRF 720.0 data for compilation of the Australian National Accounts and other publications. It also states that APRA may use the data for prudential supervision and publication. This establishes an interaction between statistical reporting obligations and prudential supervision objectives. The flow of data to the ABS creates an information-sharing intersection, while APRA’s use of the same returns for supervision means the Standard crosses both statistical and regulatory domains.

Auditor relationship and external assurance: The Standard explicitly clarifies that the information provided under this Reporting Standard is not required to be audited or tested by the RSE auditor (paragraph 13). This creates a separation between the statutory financial audit regime that may apply to RSEs under other laws and the assurance expectations for SRF 720.0 submissions. Practically, that means compliance rests on internal governance rather than mandatory external audit under this instrument.

Electronic submission and signature regimes: The Standard requires digital signature using a digital certificate acceptable to APRA for D2A submissions (paragraph 15). That interacts with any broader electronic signature or identity verification frameworks that apply in other legislation or administrative regimes, although the Standard itself specifies acceptance criteria only as “acceptable to APRA”. The interaction point is administrative: licensees must meet APRA’s technical and identity verification requirements when submitting under this Standard.

Notices and administrative discretion: APRA’s ability to change reporting frequency or vary requirements by written notice (paragraphs 9 and 18) creates an administrative interface. The Standard acts as a baseline which APRA can modify for particular licensees. How APRA exercises those discretions may involve operational interactions with other statutory obligations or supervisory initiatives, but this Standard limits that interaction to written notices and specified procedural changes.

Limits of the Standard as a standalone instrument: The Standard does not state broader enforcement powers or penalties itself. Any statutory enforcement consequences for failing to comply with a written notice, or for failing to meet the reporting obligations more generally, would arise from the broader legislative framework under which APRA and the Financial Sector (Collection of Data) Act operate. Those interacting enforcement provisions are not set out in this document.

The Reporting Standard’s text provides limited material on its own temporal dimensions. The document records the commencement application date and the statutory authority but does not include a record of amendments within the supplied text.

Commencement and application: The Standard applies for reporting periods ending on or after 1 July 2017 (paragraph 5). That is the only explicit temporal marker in the text indicating when the instrument’s requirements took effect for reporting periods.

Statutory origin: The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). This locates the Standard as an instrument subordinate to that Act and subject to any amendment machinery or repeal provisions available under that Act.

No amendment log included: The provided text contains no schedule of amendments, amending instruments, dates of amendment, version history, or revocation clauses. There is no explicit notation in the supplied paragraphs identifying changes since the original making or subsequent modifications. Therefore, readers should treat the text as a snapshot of the Standard as provided, effective for reporting periods on or after 1 July 2017, and should consult APRA or the Commonwealth legislation register for any later amendments not contained in this document.

Provisions enabling change: The Standard itself contemplates administrative change at the entity level via APRA notices (paragraphs 9 and 18) and administrative extensions (paragraph 11). Those are operational variations rather than statutory amendments. They evidence that APRA can adjust reporting periods and requirements for particular licensees without a formal amendment to the Standard itself, by issuing written notices.

Practical recommendation implicit in the text: Given the absence of an amendment history within the instrument, practitioners and compliance officers should assume that the Standard may have been revised externally and should verify the current operative text and any APRA notices before relying on this copy for compliance. The Standard identifies its legislative basis and commencement date but does not list subsequent amendments in the supplied text.

The Reporting Standard text as supplied contains no litigation history, case citations or references to disputes arising under it. There are no judicial decisions, tribunal determinations or litigation summaries included within the paragraphs provided.

No cases named or decisions cited: Paragraph 19 provides definitions and cross-references to other statutes but does not cite any cases or interpretive decisions. The text does not list precedents, appeals, or enforcement actions under the Standard.

Implication for research: The absence of litigation material in this text means any party seeking to understand legal challenges to the Standard, judicial interpretation of its terms, or enforcement precedents must search outside the instrument for decisions that may have considered SRF 720.0 obligations or APRA’s exercise of the notice and variation powers referred to here. The Standard itself gives no guidance on its judicial interpretation.

Operational context for disputes: Although not reflected in litigation in the instrument, the Standard creates duties and administrative discretions that could be the subject of disputes in practice, for example over APRA notices changing reporting frequency, the acceptability of estimates, or the adequacy of internal systems and controls. None of those potential dispute themes are adjudicated or annotated in the supplied text.

The Standard contains several practical traps for compliance if not carefully managed. These are concrete mechanics in the instrument that might be overlooked or misunderstood by RSE licensees.

Asset threshold and entity definitions: The asset threshold for “relevant RSE” is determined by total assets at the end of the most recent year of income at the time of reporting (paragraph 4). That timing element means asset levels must be assessed against the last completed year of income, not necessarily against current quarter-end positions. Paragraph 19’s interpretation of “RSE” excludes certain fund types for the purpose of the definition, while paragraph 4 includes defined benefit RSEs, PSTs and ERFs as types of relevant RSEs subject to the $200 million threshold. Practitioners should not assume all RSEs are in scope; the Standard’s scope hinges on these definitions and the asset test.

Quarterly rhythm anchored to year of income: Reporting is quarterly based on the year of income of the entity (paragraph 8). This can produce reporting periods that do not align with calendar quarters or a licensee’s internal financial reporting calendar if the entity’s year of income differs. The 28 calendar day due date runs from the end of the quarter to which the information relates (paragraph 10(a)). Licensees must map the Reporting Standard’s quarters to their year of income start and end dates to avoid late submission risks.

APRA’s right to vary frequency and content: APRA can require more or less frequent reporting for a particular RSE if it considers that necessary or desirable, by written notice (paragraph 9), and can vary reporting requirements by written notice to a licensee (paragraph 18). The existence of these powers means a licensee must monitor APRA notices and be prepared to retool reporting systems at short notice.

Electronic submission and D2A availability: The rule requires electronic submission using D2A where available, and where not available by an alternative APRA-notified method (paragraph 7). Licensees must ensure they can access D2A and comply with digital certificate requirements (paragraph 15). If D2A is temporarily unavailable, the licensee must rely on APRA notifying an alternative method, which could introduce operational uncertainty.

Digital signature and authorisation: D2A submissions must be digitally signed with a certificate acceptable to APRA (paragraph 15). Additionally, the officer or agent who submits must be authorised by the CEO or CFO (paragraph 17). Two layers of identity and authorisation controls can be overlooked: obtaining an APRA-acceptable digital certificate and maintaining a formal authorisation from the CEO or CFO. If an agent is used, the licensee must obtain and retain a copy of the completed form (paragraph 16), which requires internal processes for record collection and storage.

Internal control expectations without audit: The Standard requires internal systems, processes and controls and reserves responsibility for Board and senior management to ensure policies and procedures are in place (paragraph 12), but it explicitly states the submissions are not required to be audited or tested by the RSE auditor (paragraph 13). Licensees accustomed to relying on external audit as the primary assurance mechanism must implement robust internal assurance to meet the Standard’s expectations.

Permitted estimates are limited: The Standard allows “careful estimates” where accurate information is not readily available (paragraph 14) but conditions that the estimate be the product of the licensee’s systems, processes and controls developed for that purpose. Casual or ad hoc estimating is not authorised by the text; the estimate must be produced by established controlled processes.

Record retention obligations with agents: Where an agent submits, the licensee must obtain and retain a copy of the completed form (paragraph 16). Failure to obtain and retain the agent’s copy could leave the licensee without necessary records for its own governance reviews or for responding to APRA queries.

No sanctions in-text: The Standard does not state penalties or a sanction regime in its own text. That does not mean consequences cannot follow under broader statutes, but practitioners must recognise the Standard itself does not provide a standalone enforcement catalogue.

Below is a practical, source-grounded compliance checklist drawn directly from the Standard’s paragraphs. Each step cites the relevant paragraph(s). Licensees should integrate these items into operational policies and schedules.

1. Confirm applicability and population

   • Verify whether the licensee has any relevant RSEs as defined (RSE, defined benefit RSE, PST, ERF) with total assets equal to or greater than $200 million at the end of the most recent year of income (paragraphs 3 and 4).
   • Use SIS Act definitions for ERF, PST, RSE and year of income as referenced in paragraph 19.

2. Establish reporting calendar and deadlines

   • Map the Standard’s quarterly reporting periods to each relevant RSE’s year of income and schedule submissions accordingly (paragraph 8).
   • Note the standard due date of 28 calendar days after the end of the quarter (paragraph 10(a)), and track any APRA notices that change the reporting period or due date for a particular RSE (paragraphs 9 and 10(b)).
   • If an extension is required, apply to APRA and obtain a written extension; the new due date is the date on the notice (paragraph 11).

3. Implement data collection and internal controls

   • Develop and document systems, processes and controls for internal review and authorisation of the SRF 720.0 information (paragraph 12).
   • Ensure Board and senior management oversight and formal adoption of policies and procedures for authorisation (paragraph 12).
   • Where accurate information is not readily available, develop controlled estimation methodologies and document processes that produce “careful estimates” consistent with paragraph 14.

4. Technical submission readiness

   • Acquire and configure APRA’s ‘Direct to APRA’ software (D2A) for electronic submission where available, or document an alternate submission method in accordance with APRA’s written notification if D2A is not available (paragraph 7).
   • Obtain a digital certificate acceptable to APRA and establish processes for digitally signing D2A submissions (paragraph 15).

5. Authorisation and delegation

   • Establish formal authorisation processes for officers and agents who will submit SRF 720.0 information, ensuring each submitting officer or agent is authorised by the CEO or CFO (paragraph 17).
   • Maintain records of such authorisations and ensure the authorised signatory is familiar with both the digital signing process and content requirements.

6. Agent use and record retention

   • If using an external agent to submit, obtain a completed copy of the form from the agent and retain it in accordance with internal record retention policy (paragraph 16).
   • Ensure the agent’s submission processes meet the licensee’s internal control standards for accuracy and traceability.

7. Assurance and audit interface

   • Recognise that the Standard does not require the RSE auditor to audit or test the information (paragraph 13), and therefore implement internal assurance mechanisms proportionate to the risk profile and APRA’s supervisory expectations (paragraph 12).
   • Document internal review signoffs, reconciliation steps and controls that produce any permitted estimates (paragraph 14).

8. Monitor APRA notices and use of discretion

   • Put processes in place to monitor APRA communications for notices that alter reporting frequency, due dates, or content for particular RSEs, and to implement such changes promptly (paragraphs 9 and 18).
   • Keep a record of any written notices and extensions from APRA (paragraph 11) and align internal schedules to the notice terms.

9. Data use awareness

   • Inform relevant internal stakeholders (finance, actuarial, governance, compliance) that the data will be used by ABS for national accounts and may be used by APRA for prudential supervision and publication, as described in paragraph 2. This affects sensitivity, verification focus and publication-risk assessment.

10. Documentation and training

• Document all policies, procedures, estimation methodologies, authorisation delegations and recordkeeping practices invoked to meet the Standard’s requirements (paragraphs 12, 14, 16 and 17).
• Train staff and authorised submitters on D2A operation, digital certificate use, internal controls and the need to maintain accurate and traceable data submissions.

11. Contingency planning

• Prepare for temporary unavailability of D2A by establishing an APRA-notified fallback submission mechanism in advance or by knowing how to obtain APRA’s alternative notification (paragraph 7).
• Prepare to respond to APRA requests for more frequent or different data by maintaining flexible data extraction and reporting templates (paragraphs 9 and 18).

12. Governance sign-off and Board oversight

• Ensure the Board and senior management have reviewed and approved the policies and procedures that govern the submission process, and that governance evidence is retained to demonstrate the Board’s discharge of its responsibilities under paragraph 12.

Following the steps above aligns operational practices with each paragraph in the Standard and creates an auditable trail of compliance decisions, authorisations and submissions.