Financial Sector (Collection of Data) (reporting standard) determination No. 25 of 2015 - SRS 801.0 - Investments and Investment Flows

This Determination revokes Reporting Standard No. 15 of 2014 and replaces it with Reporting Standard SRS 801.0 Investments and Investment Flows, which applies to small APRA funds (SAFs) and single member approved deposit funds (SMADFs). The instrument is made under section 13 of the Financial Sector (Collection of Data) Act 2001 and is declared to apply on and after 1 July 2015 (preamble; paragraph 1; paragraph 4). The Reporting Standard requires each registrable superannuation entity (RSE) licensee that has one or more SAFs or SMADFs within its business operations to deliver a specified electronic form, SRF 801.0, providing detailed data on asset allocation and investment flows for each SAF or SMADF (paragraphs 2-5, paragraph 3, Reporting Form SRF 801.0).

Mechanically, the Determination imposes the following primary obligations and operational steps:

• Scope: It applies to RSE licensees of SAFs and SMADFs (paragraph 3; interpretations).
• Reporting instrument: SRF 801.0 Investments and Investment Flows must be completed for each SAF or SMADF (Reporting level, SRF 801.0).
• Submission method: Data must be provided electronically using the Direct to APRA (D2A) application, or another method notified by APRA if D2A is unavailable (paragraph 6).
• Timing: Reports are due for each year of income, within three months after the end of the year of income, unless APRA changes the reporting period by written notice or grants extensions (paragraphs 7-10).
• Data content and format: Detailed line items cover total investments, directly and indirectly held investments (with asset class, domicile and listing types), investments by vehicle, movements (net transactions, income, unrealised/realised gains/losses), and yes/no declarations for directly held derivatives and securities lending (the SRF 801.0 form and specific instructions). Values are reported in thousands of Australian dollars and percentages to one decimal place (Reporting basis and unit of measurement).
• Look-through requirements: Indirectly held investments (items 3 and 6) must generally be reported on an APRA-look through basis to the underlying assets, subject to specified exceptions (APRA-look through basis; Item 3; Item 6).
• Assurance and controls: The information must be produced by systems and controls that have been reviewed and tested by the RSE auditor, at least on an annual basis and at least as a limited assurance engagement consistent with Auditing and Assurance Standards (paragraph 11; footnote 2 referring to SPS 310). Boards and senior management must ensure internal review and authorisation policies (paragraph 12).
• Authorisation and recordkeeping: Submissions require a digital certificate acceptable to APRA (paragraph 13), agents must provide and the RSE licensee must retain a copy of completed forms (paragraph 14), and submitters must be authorised in writing by the RSE licensee’s CEO or CFO (paragraph 15).
• APRA discretion: APRA may vary reporting requirements for particular RSE licensees or funds, change reporting frequency, and specify alternative submission methods (paragraphs 8, 10, 16).

The stated purpose in the instrument is prudential supervision and publication (paragraph 2). The Determination sets the precise data fields, definitions and reporting conventions APRA requires for those stated purposes, and embeds audit-quality requirements to support data reliability (paragraphs 2, 11-12, Reporting Form SRF 801.0).

SRS 801.0 encodes several core reporting concepts and conventions that determine what must be reported and how.

• Reporting unit and level: SRF 801.0 must be completed for each SAF or SMADF, not for the RSE licensee as an aggregate, although the licensee must file separately for each qualifying fund (Reporting level; footnote 1). The RSE licensee’s “business operations” extend to all its RSE activities and other activities relevant to those obligations (footnote 1).

• Asset classification: The form separates investments into asset class types (cash, fixed income, equity, property, infrastructure, commodities, other) and further by asset domicile type (Australia domicile, international domicile, not applicable) and asset listing type (listed, unlisted, not applicable). Specific allocation rules and examples are provided (Item 2; Item 3; Glossary).

• Directly vs indirectly held: Directly held investments are those owned by the RSE in its own name (including custodian-held in trust) and are reported in Item 2 and Item 5. Indirectly held investments are those held via investment vehicles and are reported in Item 3 and Item 6 (definitions; Items 2-4). Critically, Item 3 and Item 6 are to be reported on an APRA-look through basis: investments held within the vehicle must be allocated to the underlying asset class/domicile/listing of the actual holdings (Item 3; Item 6).

• APRA-look through and “most proximate investment”: The Reporting Standard defines “APRA-look through” to mean reporting the ultimate investment where held directly, or, where held by a person connected to the RSE licensee, reporting that investment, or otherwise reporting the most proximate investment of a person connected with the RSE licensee to the ultimate investment. The document explains how the “first non-connected entity” and the “most proximate investment” work in practice (APRA-look through definition; Interpretation; footnotes 4 and 5).

• Exceptions to look-through: Hedge fund investments are explicitly excluded from look-through requirements; they may be reported in asset class ‘other’ (Item 3; Specific instructions). Multi-asset class investment vehicles (cash management trust, life company products, listed/unlisted retail trusts, pooled superannuation trusts, wholesale trusts) must be allocated to the underlying asset classes rather than reported as ‘other’ (Item 2; Item 3).

• Movements and gains/losses: Items 5 and 6 capture net transactions, investment income, unrealised and realised gains/losses, with total gains/losses presented as a derived sum of unrealised and realised gains (Items 5 and 6 instructions). The standard requires apportionment of any derivative exposure within indirectly held investments to the asset classes to which they relate (Item 3, Item 6).

The Determination is explicitly targeted. Paragraph 3 states it applies to "each registrable superannuation entity (RSE) licensee of a small APRA fund (SAF) or a single member approved deposit fund (SMADF) within its business operations." The interpretation section defines SAF and SMADF by reference to section 10(1) of the SIS Act: SAFs are regulated superannuation funds with fewer than five members; SMADFs are approved deposit funds with only one member (interpretation definitions). Footnote 1 clarifies that "RSE licensee’s business operations" includes all activities as an RSE licensee and all other activities to the extent they are relevant to or may impact those RSE activities. If an RSE licensee is trustee of more than one SAF or SMADF, the licensee must provide the SRF 801.0 for each such SAF or SMADF separately (footnote 1).

Other parties affected by the mechanics of the Standard include:

• Agents and service providers who submit data via D2A on behalf of the RSE licensee. Paragraph 14 requires an agent to provide the RSE licensee with a copy of the completed form and the RSE licensee must retain it. Paragraph 15 requires that the person submitting be authorised by the CEO or CFO. This distributes operational responsibilities and recordkeeping obligations between the licensee and agents (paragraphs 13-15).
• RSE auditors, who are required to review and test the reporting systems, procedures and internal controls (paragraph 11). The standard requires at least a limited assurance engagement and refers to SPS 310 and Auditing and Assurance Standards Board guidance (paragraph 11; footnote 2). This places an independent assurance burden on the auditor to form an opinion on reliability and accuracy.
• Persons connected with the RSE licensee, including related bodies corporate and custodians, and persons investing assets under contract for the RSE licensee, may be implicated by look-through and information obligations. The Interpretation and footnote 4 explain that subsection 13(4B) of the Financial Sector (Collection of Data) Act 2001 is taken to include contract terms requiring the first party to notify the second that the assets are of a registrable superannuation entity, and requiring the second party, if notified, to provide the information of which they are aware. That mechanism extends the practical reach of information collection to parties connected with the RSE licensee.
• Investment managers and responsible entities of investment vehicles: for APRA-look through reporting, RSE licensees must seek the holdings of the first non-connected entity; if that entity is the vehicle manager or responsible entity, those entities will be the source of required data (Item 3 instructions; footnote 5 example).

Duties imposed on RSE licensees by this Determination are procedural, substantive (data content) and governance-related. Key duties include:

• Submission duty: An RSE licensee must provide APRA with the information required by SRF 801.0 for each reporting period that applies to each SAF or SMADF within its business operations (paragraph 5, paragraph 7). The due date is within three months after the end of the year of income to which the information relates, unless APRA specifies otherwise (paragraph 9).

• Form and method: The information must be given in electronic format using D2A, or another method notified by APRA (paragraph 6). Submissions require digital signing with a certificate acceptable to APRA (paragraph 13).

• Content accuracy and format: All items must be reported in accordance with Australian Accounting Standards unless specified otherwise; report in thousands of dollars and percentages to one decimal place; convert non-AUD assets using a representative closing mid-market rate as at reporting period end (Reporting basis and unit of measurement). Derived items and reconciliation rules (e.g., item 1.1, 2.1, 3.1, 4.1, 5.1, 6.1) must be observed.

• Look-through: For indirectly held investments, the RSE licensee must apply APRA-look through rules and report underlying asset classes and domicile types when required (Item 3; Item 6). The RSE licensee must seek information about the actual holdings of the first non-connected entity to identify the asset class(es) (Item 3 instructions).

• Internal controls and audit assurance: The information must be produced by systems, procedures and internal controls reviewed and tested by the RSE auditor. Reviews must occur at least annually and at least as a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance and SPS 310 where not inconsistent (paragraph 11). Boards and senior management are responsible for internal review and authorisation policies (paragraph 12).

• Authorisation, recordkeeping and agent oversight: The RSE licensee must ensure a submitter is authorised by the CEO or CFO (paragraph 15), obtain and retain copies from agents (paragraph 14), and digitally sign submissions (paragraph 13).

• Disclosure of participation in derivatives or securities lending: The RSE licensee must indicate whether the SAF or SMADF holds directly held derivatives or participates in securities lending programs (Items 7 and 8).

The Determination SRS 801.0 prescribes reporting duties, times, formats and assurance requirements, but does not itself include express penalty provisions or an enforcement schedule within the text provided. The instrument is made under the Financial Sector (Collection of Data) Act 2001 (paragraph 1; Authority), and it declares the date on which the Reporting Standard shall begin to apply under section 15 of the Act (preamble; paragraph 1). The Determination therefore sits within a statutory framework that determines enforcement and sanctioning powers; however, those statutory provisions are not reproduced or set out in this Determination document.

Operational enforcement and compliance mechanisms in the Reporting Standard include:

• APRA’s administrative controls over compliance timing and format: APRA may specify or change reporting periods for particular funds by notice in writing (paragraph 8), may notify an alternative submission method if D2A is unavailable (paragraph 6), and may grant extensions of due dates in writing (paragraph 10). These are APRA’s procedural levers to enforce or accommodate compliance.
• Data quality assurance expectations: Paragraph 11 places a substantive assurance requirement on the RSE auditor to review and test reporting systems and controls and to undertake a limited assurance engagement at least annually. Paragraph 12 places responsibility on the board and senior management for internal review and authorisation policies. These provisions create control points that APRA can examine when assessing compliance and data reliability.

The Determination creates a contractual and information-flow mechanism via the interpretation and footnote 4: subsection 13(4B) of the Act is explained to be taken as including contract terms that require a first party to notify a second party that assets are those of an RSE and to require the second party, if notified, to provide information the second party is aware of. That mechanism extends APRA’s effective reach into arrangements between RSE licensees and connected service providers, and creates an obligation on those connected service providers to supply required information when notified (interpretation; footnote 4).

What is not set out here and therefore requires reference elsewhere:

• Specific statutory penalties, enforcement procedures and sanctioning powers applicable to non-compliance are not contained in the Determination text. Users must consult the Financial Sector (Collection of Data) Act 2001 and any other relevant legislation and APRA enforcement policy to understand the consequences of non-compliance. The Determination does not itself describe fines, civil penalties, criminal offences or compliance notices.

SRS 801.0 is framed as a regulatory reporting instrument that cross-references and operates within a web of statutory and prudential instruments. The Determination explicitly identifies its source of authority and links to other legislative and prudential standards:

• Financial Sector (Collection of Data) Act 2001: The Reporting Standard is made under section 13 of that Act (Authority, paragraph 1). The instrument’s commencement and declaration that it applies on and after 1 July 2015 is made under section 15 of that Act (preamble). Several interpretation provisions,for example the meaning of "person connected with an RSE licensee",refer to provisions in subsection 13(4C) of the Financial Sector (Collection of Data) Act (Interpretation; footnote 4).

• Superannuation Industry (Supervision) Act 1993 (SIS Act): Key defined terms used to delimit scope,RSE, RSE licensee, small APRA fund, single member approved deposit fund, and year of income,are taken from section 10(1) of the SIS Act (Interpretation). The Reporting Standard therefore depends on SIS Act definitions to determine which entities must report.

• Prudential Standards and Auditing Guidance: Paragraph 11 requires review and testing of systems and controls by the RSE auditor and references Prudential Standard SPS 310 Audit and Related Matters (SPS 310) (footnote 2). Paragraph 11 also requires a limited assurance engagement consistent with professional standards and guidance notes issued by the Auditing and Assurance Standards Board. Paragraph 11 further states "to the extent that they are not inconsistent with the requirements of SPS 310", which implies that SPS 310 and Auditing Standards shape the form and minimum content of assurance work.

• Prudential Standard SPS 510 Governance: Paragraph 17’s interpretation references SPS 510 with respect to the definition of Chief Executive Officer; the Reporting Standard places governance responsibilities on the board and senior management to ensure authorisation policies are in place (paragraph 12; footnote 3).

• Life Insurance Act 1995 and Corporations Act 2001: The Reporting Form’s glossary refers to concepts that are defined in other legislation,e.g., “life company guaranteed” and “investment-linked” reference s.14 of the Life Insurance Act 1995; definitions of retail/wholesale clients and access levels refer to the Corporations Act 2001 (Investment vehicles and Glossary).

• Reserve Bank of Australia (RBA) exchange rates: The Reporting Standard recommends RBA rates as a reference for mid-market closing rates for currency conversion (Reporting basis and unit of measurement).

The Determination expressly revokes Financial Sector (Collection of Data) (reporting standard) determination No. 15 of 2014, including the previous Reporting Standard SRS 801.0 Investments and Investment Flows made under that revoked Determination, and replaces it with the Reporting Standard set out in the Schedule (preamble; paragraph 1(a)-(b)). The replacement Reporting Standard takes effect for reporting periods ending on or after 1 July 2015 (paragraph 4). The instrument is dated 24 June 2015 and the Determination commenced on the date of registration on the Federal Register of Legislative Instruments (preamble).

This Determination is therefore a formal revision and reissue of SRS 801.0; the text provided is the full replacement Reporting Standard as made in Determination No. 25 of 2015. There are no further amendments recorded in the text provided: no schedules of later amendments, transitional provisions beyond the commencement date, or subsequent modification dates appear in the instrument as supplied.

Footnotes within the Reporting Standard update interaction with other existing regulatory instruments (for example, footnote 2 references SPS 310 and auditing standards; footnote 3 references SPS 510). These cross-references implicitly tie the Reporting Standard to periodic changes in prudential standards and auditing guidance (i.e., the Reporting Standard’s operational requirements could be affected by later amendments to those external instruments), but the Determination text does not itself list a history of such external amendments.

Practical consequence for implementers: because the Determination revokes the 2014 Determination and replaces it effective 1 July 2015, RSE licensees and their auditors needed to ensure that reporting for periods ending on or after that date complied with the new SRS 801.0 text and that any operational changes from the 2014 version were implemented by that date. The Determination also builds in APRA discretion to vary requirements by notice (paragraph 16), meaning APRA may subsequently amend application to particular licensees administratively without issuing a further Determination; those administrative variations are not captured in the instrument’s formal amendment history but will be communicated in writing to affected licensees (paragraph 16).

The Reporting Standard document supplied contains no reference to litigation and names no cases. The instrument is a statutory administrative instrument replacing an earlier Reporting Standard; it does not include any discussion of judicial review, case law, or litigation outcomes.

Where a user needs the litigation or contested-administrative history concerning SRS 801.0 or the parent Financial Sector (Collection of Data) Act 2001, that material is not contained in this Determination. Investigators should search judicial and administrative law databases and APRA’s public enforcement and compliance records for any proceedings or disputes arising from the operation or enforcement of the Reporting Standard or the parent Act. The Determination itself does not record such matters and provides no internal annex summarising litigation or dispute outcomes.

The Reporting Standard contains numerous operational and conceptual traps for implementers. The following are concrete "gotchas" drawn directly from the text and instructions.

• Scope per-fund, not per-licensee aggregate. SRF 801.0 must be completed for each SAF or SMADF separately (Reporting level; footnote 1). If an RSE licensee is trustee of multiple SAFs/SMADFs, separate submissions are required. It is not sufficient to file one consolidated return for multiple SAFs.

• APRA-look through applies in specific places only. Items 3 and 6 (indirectly held investments and movements in indirectly held investments) are to be reported on an APRA-look through basis, meaning allocations to underlying assets are required where those assets are held by a person connected with the licensee or can be traced to a most proximate investment (Item 3 instructions; Item 6 instructions; Interpretation; footnotes 4 and 5). By contrast, Item 4 (indirectly held investments by vehicle) is reported on a non-look through basis and must reconcile to item 3. Misapplying look-through to Item 4 or failing to apply it to Item 3 is a common source of reconciliation errors.

• Hedge funds exception. Look-through reporting is not required for hedge fund investments; hedge fund investments are reported in asset class ‘other’ (Item 3). RSE licensees must take care not to allocate a hedge fund’s internal holdings on a look-through basis unless they are prepared to do so and have the information.

• APRA-look through hinges on “person connected” and “most proximate investment.” The standard’s footnotes explain how a managed investment scheme may be a person connected under paragraph (c) of the definition; but the trustee of a downstream private equity vehicle may not be connected, so the RSE licensee reports the managed investment scheme’s investment in the private equity vehicle rather than the private equity assets themselves (footnote 5 example). Implementers must trace legal relationships precisely to determine what to look through to, not simply apply a presumptive one-level look-through.

• Contractual information flows are deemed but may not be practically automatic. Footnote 4 explains that subsection 13(4B) is taken to include terms requiring notification and supply of information by connected parties. That shifts the right to request data onto a statutory footing, but in practice RSE licensees may still face delays obtaining detailed underlying holdings from third parties (operational friction, reporting timelines).

This section sets out a practical compliance checklist derived from the Reporting Standard text. It organises the steps an RSE licensee (or its agent) must take to meet the obligations in the Determination.

1. Confirm applicability and scope

   • Identify whether you are an RSE licensee with SAFs or SMADFs (interpretation definitions referencing s.10(1) of the SIS Act; paragraph 3; footnote 1).
   • For each SAF and SMADF within your business operations, plan to complete SRF 801.0 separately (Reporting level; footnote 1).

2. Establish reporting calendar and timetables

   • Determine the year of income for each fund (interpretation).
   • Prepare to submit SRF 801.0 within three months of the end of each year of income, unless APRA issues a notice changing the period, or you are granted an extension (paragraphs 7-10).
   • Maintain procedures to receive and respond to APRA notices under paragraph 8 (frequency changes) and paragraph 16 (variations).

3. Configure data capture and classification

   • Build or validate your general ledger / investment reporting extracts to produce asset classifications by:
     • Asset class type (cash, fixed income, equity, property, infrastructure, commodities, other);
     • Asset domicile type (Australia domicile, international domicile, not applicable);
     • Asset listing type (listed, unlisted, not applicable).
     • Where multi-asset vehicles are used, obtain or compute the allocation to underlying asset classes and domiciles (Items 2-4).
   • Implement rules to treat hedge fund investments as asset class ‘other’ unless you can and choose to look through (Item 3 instructions).

4. Implement APRA-look through processes

   • For indirectly held investments (Items 3 and 6), identify the first non-connected entity and the most proximate investment and obtain holdings information from that entity (Interpretation; footnotes 4 and 5).
   • Where only aggregate vehicle-level movements are available, apportion movements across asset classes using the vehicle’s reported allocation or effective exposure as instructed (Item 6 example and instructions).
   • Prepare to apportion derivative market exposure within indirectly held investments to the asset classes to which they relate (Item 3).