The standard’s architecture pivots on a few core concepts. First, the reporting unit is the RSE licensee, defined by reference to the Superannuation Industry (Supervision) Act 1993 (SIS Act), subsection 10(1) (Interpretation, para 1). The obligation is to report on the RSE licensee’s business operations, not at an overarching group consolidation level unless those items are the RSE licensee’s own financials (Application, para 1; Reporting level instruction).

Second, the instrument operates as a data collection tool rather than a prescriptive accounting standard. It requires mapping from the RSE licensee’s audited financial statements prepared in accordance with Australian Accounting Standards to a set of structured fields in SRF 340.0 (Reporting basis and units of measurement; Instruction Guide). Reportable tables are fixed: income statement, balance sheet, changes in equity and related party disclosures. Many table cells are derived items calculated from subcomponents, for example Revenue is the sum of items 1.1 to 1.5 and Expenses is the sum of 2.1 to 2.7 (Table 1 instructions).

Third, the standard imposes an assurance layer. APRA requires that information be the product of systems, procedures and internal controls reviewed and tested by the RSE auditor; that review and testing must be on at least an annual basis and include at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance and not inconsistent with Prudential Standard SPS 310 (Quality control, para 1). That links statutory reporting to audit procedures and elevates data reliability expectations.

Fourth, APRA sets operational submission rules. Submissions must be electronic using an APRA method (Form and method of submission, para 1). An officer or agent who provides the information must digitally sign using a digital certificate acceptable to APRA, and submissions must be authorised by the CEO or CFO of the RSE licensee (Authorisation, paras 1 and 3). If an agent submits, the licensee must retain a copy of the completed form provided by the agent (Authorisation, para 2).

Fifth, APRA retains procedural discretion. It can change reporting frequency for specific licensees by written notice and grant extensions in writing (Notices, paras 1-3). It can also make minor variations to the form or instructions to remedy technical or programming errors without changing substantive requirements, and must notify filers when it does so (Minor alterations, paras 1-2).

Finally, definitions and cross‑references anchor the standard within the broader regulatory and accounting framework. The instrument explicitly ties to the SIS Act definition of RSE licensee, to SRS 101.0 Definitions for Superannuation Data Collections, to Australian Accounting Standards, AASB 124 for related parties, and to Prudential Standard SPS 310 for audit matters (Interpretation; Table 4 instructions; Quality control). The standard thus functions as a bridge between audited financial information, APRA’s supervisory dataset, and existing accounting and audit regimes.

Primary legal obligation: each RSE licensee must report under this standard (Application, para 1; Reporting level). The RSE licensee is defined by reference to the SIS Act subsection 10(1) (Interpretation, para 1). APRA’s instruction is to report “in respect of its business operations,” so reporting aligns to the RSE licensee entity level rather than to unrelated group entities (Application, para 1; Reporting level instruction).

Auditors and audit firms are directly implicated. The standard mandates auditor review and testing of systems, procedures and internal controls that generate the reported data and requires at least a limited assurance engagement consistent with professional standards and SPS 310 (Quality control, para 1). RSE auditors will therefore need to expand usual audit procedures if systems feeding APRA have not previously been covered, and must form an opinion or provide limited assurance on the reliability and accuracy of the information.

Senior management and boards of RSE licensees carry governance responsibility. The standard places explicit operational responsibility on the Board and senior management to ensure policies, procedures and controls for the authorisation of information submitted to APRA are in place (Quality control, para 2). Submission authorisation must come from the Chief Executive Officer or Chief Financial Officer (Authorisation, para 3), which concentrates sign‑off responsibility at senior executive level.

Service providers and agents that prepare and submit returns on behalf of RSE licensees are affected by the digital signature, retention and authorisation rules. If a licensed agent submits information, the RSE licensee must obtain and retain a copy of the completed form provided to APRA (Authorisation, para 2). The submitting officer or agent must digitally sign with an APRA‑acceptable certificate (Authorisation, para 1).

APRA and, by extension, ASIC are downstream users. APRA will use the data for prudential supervision and publication, and the instrument specifically states the data may also be used by ASIC (Purpose, para 1). Publication means that some data will be made public or used for published analysis; the instrument itself does not specify publication formats, but it links reporting to APRA’s supervisory and public reporting functions.

IT, compliance, and finance functions inside RSE licensees will be required to supply mapped, validated values in the specified format and unit (whole AUD, no decimals). Reporting basis is Australian Accounting Standards (Reporting basis and units of measurement). Related party counterparties must be identified by ABN or LEI where available, which may require cooperation with corporate groups, parent entities and market counterparties to capture identifiers (Table 4 instructions).

Finally, while the instrument does not itself create penalties within the text, it is an instrument under the Financial Sector (Collection of Data) Act 2001 and therefore sits within APRA’s broader data collection regime; compliance failure and enforcement would be dealt with under the Act and APRA’s powers under it, not by this form alone (instrument header referencing paragraph 13(1)(a) and s 15). The instrument therefore imposes administrative and compliance costs on the licensed entities, their auditors and suppliers, and concentrates control of reporting cadence and minor form changes with APRA.

Duties imposed by the instrument

• File annual SRF 340.0 returns covering four tables: Statement of comprehensive income, Statement of financial position, Statement of changes in equity, Related Party Disclosures, for each financial year of the RSE licensee (Reporting periods table; Instruction Guide tables). Each return is due within three months after the end of the reporting period (Reporting periods table).

• File the first return for the first financial year ending on or after 30 June 2025 (Reporting periods table).

• Provide the information in electronic format using APRA’s electronic method or another method APRA notifies prior to submission (Form and method of submission, para 1).

• Ensure submitted information is produced by systems, procedures and internal controls that have been reviewed and tested by the RSE auditor, with such review and testing performed at least annually and as a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance, to the extent not inconsistent with SPS 310 (Quality control, para 1).

• Ensure internal review and authorisation systems for data prior to submission are in place and maintained by Board and senior management (Quality control, para 2).

• Digitally sign submissions with a digital certificate acceptable to APRA (Authorisation, para 1) and ensure submissions are authorised by either the CEO or CFO (Authorisation, para 3).

• If an agent submits on the RSE licensee’s behalf, obtain and retain a copy of the completed form provided to APRA (Authorisation, para 2).

• Report using Australian Accounting Standards principles and in whole Australian dollars, no decimal place (Reporting basis and units of measurement; Instruction Guide).

Rights and APRA discretions expressed in the instrument

• APRA may change reporting periods for particular RSE licensees by written notice, either increasing or decreasing reporting frequency as APRA considers necessary or desirable (Notices, para 1). Where APRA has changed reporting periods, the RSE licensee must provide information within the time specified by that written notice (Notices, para 2).

• APRA may grant extensions of due dates in writing; the extended due date will be the date specified on the extension notice (Notices, para 3).

• APRA may make minor technical variations to a form or its instructions to correct technical, programming or logical errors, or to clarify application of instructions, without changing substantive requirements; APRA must notify each affected RSE licensee where it does so (Minor alterations, paras 1-2).

• APRA may use the information for prudential supervision and for publication and share use with ASIC (Purpose, para 1); the licensee therefore has the right to expect that APRA will use the data in those ways as set out.

Notably absent or limited rights/duties in this instrument

• The Reporting Standard does not set out explicit civil or criminal penalties within its text for failure to report. Enforcement and penalty arrangements are matters dealt with under the Financial Sector (Collection of Data) Act 2001 and other applicable legislation, not within this instrument’s terms. The instrument does, however, place procedural duties on licensees, including audit and sign‑off requirements, and reserves APRA discretion over timing and minor form changes.

Practical effect of duties

• Responsibility for compliance is concentrated at the Board and senior management level via governance and sign‑off obligations (Quality control, para 2; Authorisation, para 3). RSE auditors are obliged to include the reporting systems and controls in their review and provide at least a limited assurance engagement on reliability and accuracy (Quality control, para 1). APRA retains the right to change cadence and to accept electronic submissions only via its methods, creating operational dependencies for filers (Form and method of submission, para 1; Notices, paras 1-3).

The text of Reporting Standard SRS 340.0 itself does not set out specific penalties, infringement notices, civil sanctions or criminal offences for non‑compliance. The instrument is an APRA reporting standard made under paragraph 13(1)(a) of the Financial Sector (Collection of Data) Act 2001 and its commencement and application are declared under section 15 of that Act (instrument header). Enforcement mechanisms and penalties, if any, are therefore matters for the Financial Sector (Collection of Data) Act 2001 and other relevant legislation and are not detailed in the Reporting Standard text provided.

What the standard does provide regarding enforcement‑adjacent mechanisms

• APRA has procedural levers. It may change reporting periods by written notice and require compliance with the times specified in such notices (Notices, paras 1-2). It may grant extensions in writing (Notices, para 3). These written notices are forms of administrative direction which, while not labelled as penalties, are enforceable administrative instruments in the context of APRA’s statutory powers.

• The standard imposes audit and assurance requirements. By mandating that the RSE auditor review and test the reporting systems, and perform at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance and SPS 310, APRA elevates the role of auditors in verifying reporting reliability (Quality control, para 1). While the standard does not itself state consequences for auditor findings, failures identified by auditors may trigger supervisory follow up by APRA.

• Authorisation and retention obligations create evidentiary trails. The requirement for digital signing with an APRA‑acceptable digital certificate and CEO/CFO authorisation (Authorisation, paras 1 and 3), together with retention of copies when agents submit (Authorisation, para 2), will create records APRA can inspect in supervisory activity.

Limits and implications

• Because the instrument does not specify penalties, readers must consult the Financial Sector (Collection of Data) Act 2001 and other applicable statutes for the regime of enforcement, statutory powers, directions, civil penalties, or offences that APRA can or may exercise in response to non‑compliance. This Reporting Standard nests within that broader statutory enforcement framework but does not itself purport to detail it.

• APRA’s discretion to vary reporting frequency and grant extensions provides administrative flexibility but also creates compliance uncertainty for RSE licensees who must monitor APRA notices and be prepared to comply with written directives (Notices, paras 1-3).

In short, SRS 340.0 establishes mandatory reporting mechanics and governance, but it does not specify penalties within its text; enforcement consequences rely on the Act and APRA’s broader statutory powers, and the standard embeds procedural tools APRA can use to manage compliance through timing, audit requirements and data governance obligations.

The Reporting Standard is explicitly framed as part of a networked regulatory and accounting regime. The instrument is made under the Financial Sector (Collection of Data) Act 2001 (instrument header referencing paragraph 13(1)(a)) and declared under s 15 of that Act (instrument header). Its interpretation section cross‑references multiple external instruments and statutes.

Key legal and technical references in the standard

• SIS Act (Superannuation Industry (Supervision) Act 1993): RSE licensee is defined by reference to subsection 10(1) of the SIS Act (Interpretation, para 1). That connection means the universe of obliged filers tracks the statutory definition of RSE licensee in the SIS Act.

• Corporations Act 2001: financial year is defined as within the meaning of the Corporations Act (Interpretation, para 1), which aligns the reporting period definition to a well‑established corporate law reference point.

• Australian Accounting Standards and AASB 124: the instrument requires reporting in accordance with relevant Australian Accounting Standards (Reporting basis and units of measurement; Instruction Guide) and aligns related party disclosures to AASB 124 (Table 4 instructions). That means accounting recognition, measurement and classification rules under the AASBs will govern what is reported.

• Auditing and Assurance Standards Board guidance and Prudential Standard SPS 310: the RSE auditor’s required limited assurance engagement is to 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 Prudential Standard SPS 310 Audit and Related Matters” (Quality control, para 1). This explicitly ties the assurance scope to both general auditing standards and APRA’s prudential audit standard, which may require reconciling any differences.

• Reporting Standard SRS 101.0 Definitions for Superannuation Data Collections: SRS 101.0 is referenced as the definitions source for bold italicised terms in the Reporting Standard (Interpretation, para 1). This creates a consistent definition set across APRA’s superannuation data collections.

• Legislation Act 2003: the Federal Register of Legislation is referenced as the register established under s 15A of the Legislation Act 2003 (instrument header definitions), which governs commencement by registration.

Inter‑agency and public uses

• The instrument states directly that collected information is used by APRA for prudential supervision and publication and may be used by ASIC (Purpose, para 1). That creates an inter‑agency data flow to ASIC for its regulatory uses, and an explicit possibility of public reporting by APRA. Entities should therefore take into account that data reported under this standard may end up in public or inter‑agency products.

Operational interactions and potential friction points

• Auditing standards versus prudential requirements. The standard requires limited assurance consistent with Auditing and Assurance Standards Board guidance, but only “to the extent they are not inconsistent” with SPS 310 (Quality control, para 1). Where AASB or Auditing and Assurance Standards Board guidance differs from SPS 310, auditors and licensees must prioritise APRA’s prudential standard, potentially creating tension that requires explicit reconciliation and potentially additional audit work.

• Data protection and disclosure regimes. The instrument requires data used for publication (Purpose, para 1) but provides no detail on confidentiality, privacy, or disclosure thresholds within its text. Filers must therefore consider other legal frameworks governing data privacy, disclosure and FOI when assessing the risks of publication and secondary uses.

• Corporate group reporting and identifiers. Related party reporting requires ABN or LEI where available (Table 4 instructions). That forces cross‑border groups or non‑Australian related parties to provide LEIs or other identifiers and to reconcile group reporting systems to APRA’s primary key and uniqueness rules for related party rows.

Overall, the Reporting Standard integrates with existing accounting and audit law and APRA prudential standards, aligning reporting to the SIS Act, Corporations Act definitions and AAS/Audit standards while reserving APRA discretion (for timing and minor form changes). Entities must map accounting and audit practices to APRA’s reporting data model and consider inter‑agency publication and the interaction between audit guidance and prudential requirements.

The document provided is titled "Financial Sector (Collection of Data) (reporting standard) determination No. 2 of 2025" and is dated 06 January 2025 with Andrew Robertson, Chief Data Officer, as delegate of APRA, determining Reporting Standard SRS 340.0 (instrument header). The instrument declares commencement at the start of the day after registration on the Federal Register of Legislation (instrument header; Commencement). The Schedule contains Reporting Standard SRS 340.0 and an Instruction Guide for Reporting Form SRF 340.0.

Within the text of the Reporting Standard and its Instruction Guide there are provisions that permit APRA to make minor, non‑substantive variations to forms and instructions without changing substantive requirements and require APRA to notify affected RSE licensees when such a variation is made (Minor alterations, para 1-2). These internal mechanisms allow APRA to correct technical or programming errors and to clarify instructions but do not constitute formal legislative amendments.

No earlier versions, repeal or replacement entries are included in the text supplied. The instrument itself is the making of SRS 340.0 as Determination No. 2 of 2025; there is no list of prior determinations, amendments or disallowances contained in the provided material. Where the Reporting Standard cross‑references other instruments it also states that references to Acts, Regulations, Prudential Standards, Reporting Standards, Australian Accounting Standards or Auditing Standards are to instruments “as in force or existing from time to time” (Interpretation, para 1). That language means the standard will operate against the current versions of those external instruments without requiring formal amendment to SRS 340.0 whenever the external instruments change.

What to watch for in practice

• APRA’s ability to make minor variations to forms and instructions means filers should monitor APRA communications closely for notifications of such changes (Minor alterations, paras 1-2). While APRA must notify filers, these notifications may be operational rather than legislative.

• Because the instrument references external instruments as “in force or existing from time to time” (Interpretation, para 1), changes to Australian Accounting Standards, Auditing Standards, SPS 310 or the SIS Act may alter the practical implementation of SRS 340.0 without an amendment to the Reporting Standard itself. Practitioners should therefore track changes in those external instruments as part of their compliance program.

• The absence of an amendment log or transitional provisions in the text supplied means that any future amendments to SRS 340.0 will likely appear as separate determinations or instrument notices on the Federal Register. Entities should check the registration details and APRA’s communications for subsequent determinations or amendments.

In summary, SRS 340.0 is newly determined as at the date on the instrument; it contains mechanisms for APRA to make minor non‑substantive variations and binds filers to external instruments as they evolve, but no historical amendments or prior versions are included in the supplied text.

The Reporting Standard text supplied contains no references to judicial decisions, disputes, or litigation involving SRS 340.0. The instrument does not name any cases, and the schedule and instruction guide make no reference to litigation history, precedents, or judicial interpretations. Accordingly, based on the source material provided, there is no litigation history recorded within the Reporting Standard itself.

What this means for practitioners

• There are no case law interpretations of the provisions in SRS 340.0 included in the document. Any judicial clarifications of obligations under this Reporting Standard would need to be sourced externally and are not referenced in the instrument.

• Because the instrument is an administrative data collection measure that integrates auditing and accounting standards, disputes arising from its application would likely engage statutory interpretation of APRA’s powers under the Financial Sector (Collection of Data) Act 2001, the SIS Act (for RSE licencing and status), and possibly administrative law principles. None of these are canvassed or cited in the Reporting Standard text provided.

• Practitioners should therefore treat the Reporting Standard as a technical compliance instrument and rely on statutory texts, APRA guidance and, should disputes arise, the standard avenues of administrative review or judicial review under the Administrative Decisions (Judicial Review) Act or equivalent. Any litigation would be documented outside the Reporting Standard and must be identified from judicial registries, APRA enforcement notices or external legal reporting, none of which are present in the supplied material.

In short, the instrument itself contains no litigation history and cites no cases. If litigation arises later about interpretation or enforcement, it will be outside the content of this Reporting Standard and needs to be researched in legal databases and court records.

Several practical pitfalls and friction points flow directly from the language of the standard. These are concrete compliance and operational risks that responsible officers should address deliberately.

1. Timing and first reporting period. The first reporting period is “the first financial year ending on or after 30 June 2025” (Reporting periods table). For an RSE with a 30 June year end, the first report will therefore cover the year ended 30 June 2025 and be due within three months after that date. The due date rule is strict in the table and the Note says APRA expects submission no later than the due date even if it falls on a non‑business day (Reporting periods table; Notices, para 3 note). Entities must plan for the compressed initial implementation timetable.

2. Audit assurance burden. The Quality control provision requires the RSE auditor to review systems, procedures and internal controls that produce the reported information and to perform at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance, “to the extent that they are not inconsistent with the requirements of Prudential Standard SPS 310” (Quality control, para 1). That phrasing can create uncertainty where audit technical guidance and SPS 310 differ. Auditors and licensees must assess how to reconcile conflicts, which may increase audit time and cost.

3. CEO/CFO authorisation requirement. Only the Chief Executive Officer or Chief Financial Officer may authorise the submission (Authorisation, para 3). That concentrates sign‑off authority and can become a bottleneck where the CEO/CFO is unavailable close to the due date. Delegations should be planned carefully, though the standard does not itself provide for further delegation beyond the CEO/CFO.

4. Digital certificate acceptance is at APRA’s discretion. The officer or agent must digitally sign using a digital certificate “acceptable to APRA” (Authorisation, para 1). APRA’s acceptance criteria are not contained in the Reporting Standard, so filers must validate certificate types and signing workflows against APRA’s technical guidance or portals in advance.

5. Agent submission and records retention. If an agent submits on behalf of the RSE licensee, the licensee must obtain and retain the completed copy of the form provided to APRA (Authorisation, para 2). This places record retention and verification obligations onto the licensee even when outsourcing submission. Firms should ensure contractual obligations with agents cover timely delivery of the completed forms.

6. Data granularity and mapping. The instruction guide requires mapping financial statement line items to specific fields (for example, trustee service fees, trustee risk reserve fees, trustee risk reserves in equity tables) and requires whole-dollar reporting and no decimals (Instruction Guide; Reporting basis and units of measurement). Some RSE licensees may aggregate expenses or present them differently in financial statements. The guide permits aggregations to be reported in ‘Other Expenses’ if not itemised, but APRA “expects where revenue and expense items are able to be broken down…that they be reported under the relevant category” (Table 1 instructions). Preparing consistent mappings may require chart of accounts changes.

7. Related party primary key and identifier requirements. Table 4 requires specific primary key uniqueness rules and ABN or LEI identifiers where available (Table 4 instructions). Entities with complicated related party structures or overseas counterparties will need to field LEIs or leave ABN blank and use LEIs, potentially requiring corporate data collection exercises. Uniqueness constraints may require data cleansing to avoid submission rejections.

8. Minor alterations to forms. APRA may make minor variations to forms to correct technical or programming errors without changing substantive requirements and must notify filers (Minor alterations, paras 1-2). While labelled minor, such changes can require IT or data submission template updates at short notice. Filers should monitor APRA notifications and have change management processes in place.

9. No explicit confidentiality regime in the standard. The Reporting Standard states APRA will use data for publication but does not set out redaction or confidentiality rules in this text (Purpose, para 1). Filers should assume publication and consider potential commercial confidentiality sensitivity of related party payments, reserves and fee schedules and consult APRA or privacy/statutory disclosure frameworks for specifics.

10. Reconciliation to audited financial statements. The return requires values to be consistent with audited financial statements prepared under Australian Accounting Standards (Instruction Guide). Any post‑balance‑date adjustments or reclassifications must be reconciled and documented, and auditors will be testing systems and control processes that produce the submitted figures (Quality control, para 1).

Addressing these gotchas requires cross‑functional planning across finance, audit, IT and corporate governance, early engagement with auditors, testing of APRA electronic submission processes and establishing retention and sign‑off workflows that meet the instrument’s strict authorisation and record retention rules.

This is a pragmatic, stepwise compliance checklist mapped to the requirements in the Reporting Standard and Instruction Guide. Each step points to the relevant part of the instrument.

1. Confirm applicability

   • Verify that the entity is an RSE licensee per subsection 10(1) of the SIS Act and therefore within the Reporting Standard’s scope (Application, para 1; Interpretation, para 1).
   • Determine the RSE licensee’s financial year (Corporations Act definition referenced in Interpretation, para 1) and identify the first reporting period (first financial year ending on or after 30 June 2025).

2. Establish project governance and responsibilities

   • Assign Board and senior management accountability for authorisation and internal control frameworks, as required by the standard (Quality control, para 2).
   • Designate the CEO and CFO as the authorised signatories for submissions, and create contingency workflows so that the CEO/CFO sign‑off requirement is satisfied in practice (Authorisation, para 3).

3. Map accounting to APRA fields

   • Use the Instruction Guide to map audited financial statement line items to SRF 340.0 table fields. For example, map trustee service fees, trustee risk reserve fees, interest income, executive remuneration, staff wages, regulatory levies, trustee risk reserves and other reserves as per the specified table lines (Table 1-3 instructions).
   • Ensure rounding to whole Australian dollars with no decimal places and adherence to relevant Australian Accounting Standards (Reporting basis and units of measurement; Instruction Guide).

4. Prepare related party disclosures

   • Extract related party transaction details in line with AASB 124 and map to Table 4 fields. Collect ABNs for Australian related parties; where ABN is not available collect LEI identifiers for counterparties, and ensure each unique combination of Related Party name, transaction type and direction is reported on a separate line as required (Table 4 instructions).
   • Implement data validation for primary key uniqueness constraints in Table 4 before submission.

5. Engage auditors early

   • Instruct the RSE auditor to scope the review and testing of systems, procedures and internal controls that generate the reported data. Plan for at least an annual review and a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance and SPS 310 (Quality control, para 1).
   • Agree on audit deliverables, evidence requirements and timelines that align with the submission due date.

6. Implement and test submission technology and digital signature

   • Confirm the APRA electronic submission method and format via APRA’s website and any pre‑submission technical guides (Form and method of submission, para 1).
   • Obtain and test a digital certificate that is acceptable to APRA for signing submissions (Authorisation, para 1). Test the full submission workflow including data file formats, validations and acceptance by APRA’s portal.

7. Internal control, review and authorisation

   • Develop internal controls and policies for preparation, review and authorisation of the SRF 340.0 return. Ensure the Board and senior management roles are clearly documented and that CEO/CFO sign‑off is scheduled to meet the due date (Quality control, para 2; Authorisation, para 3).
   • If using an external agent to prepare or submit the form, contractually require timely delivery of the completed form back to the RSE licensee and retain a copy (Authorisation, para 2).

8. Data quality and assurance testing

   • Reconcile all return values to audited financial statements. For any non‑itemised aggregated expenses, follow the Instruction Guide rule to report totals in ‘Other Expenses’ and not to populate the disaggregated fields (Table 1 instructions).
   • Execute auditor testing and obtain the limited assurance engagement result prior to submission.

9. Submission timing and extensions

   • File each annual SRF 340.0 return within three months after the end of the RSE licensee’s financial year (Reporting periods table). For the initial filing cycle, plan for the first due date tied to the first financial year ending on or after 30 June 2025.
   • If exceptional circumstances arise, apply to APRA in writing for an extension to the due date; APRA may grant written extensions (Notices, para 3).

10. Post‑submission governance and record keeping

• Retain copies of submitted forms and authorisation records, including signed files and the evidence of CEO/CFO sign‑off, and, if applicable, copies provided by agents (Authorisation, para 2).
• Document reconciliations and audit working papers evidencing the systems and controls review required by the RSE auditor.

11. Monitor APRA communications and changes

• Monitor APRA notices for any written changes to reporting periods (Notices, para 1), for minor variations to forms and instructions (Minor alterations, paras 1-2) and for updates to APRA’s electronic submission methods.
• Track changes to Australian Accounting Standards, AASB 124, Auditing and Assurance Standards Board guidance and Prudential Standard SPS 310, since the Reporting Standard references those instruments as “in force or existing from time to time” and requires consistency with them (Interpretation, para 1; Quality control, para 1).

12. Data privacy and publication readiness

• Prepare for potential publication of reported information by APRA and possible use by ASIC by reviewing what fields may be sensitive (Purpose, para 1). Consult privacy counsel or APRA guidance as needed to understand the scope of publication and any available mechanisms for redaction or confidentiality claims.

Following these steps will align an RSE licensee with the mechanical and governance requirements set out in SRS 340.0 and the SRF 340.0 Instruction Guide. The key compliance controls are the auditor’s systems review and limited assurance engagement, the CEO/CFO authorisation and the technical readiness to submit whole‑dollar, AAS‑aligned data using APRA’s electronic method.