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

The Reporting Standard organizes a concise set of concepts and rules that govern what balance-sheet information APRA collects and how it must be produced. The principal concepts in the instrument are:

• Scope of application. The Reporting Standard applies to RSE licensees in respect of RSEs, defined benefit RSEs, PSTs and ERFs within their business operations (para 3). The definitions and exclusions are set out in para 17 and footnotes, including that RSE for the purpose of this Standard excludes defined benefit RSEs, PSTs, ERFs, small APRA funds and single-member approved deposit funds (para 17; fn [5], [6]). The phrase “RSE licensee’s business operations” is broader than a single fund and expressly requires separate reporting for each RSE of which the licensee is trustee (fn [1]).
• Form SRF 320.0 and line items. The core deliverable is SRF 320.0 Statement of Financial Position comprising items 1 through 25 (Form and Instructions). These capture assets (items 1-11), liabilities (items 12-20), members’ benefits and reserves (items 21-24) and a fund balance field for APRA levies (item 25). Several items are derived (items 10, 13, 19, 21, 22.2, 23, 24) so their values must reconcile to constituent fields (Instructions: specific items).
• Reporting basis and units. Reported amounts must follow Australian Accounting Standards unless otherwise specified, and be reported in thousands of dollars (Instructions: Reporting basis and units).
• Derived and reconciled fields. Several items are defined as arithmetic differences or sums of other items (for example item 10 = item 11 minus sum of specified other items; item 21 = item 11 minus item 20; item 22.2 = sum of closing balances in 22.1 column 6). The Instructions repeatedly emphasise these relationships and specify sign conventions (e.g. transfers reported gross; earnings and losses on reserves reported as positive numbers) (Instructions: Items 10, 21, 22).
• Cross-form and cross-standard references. The Reporting Standard requires consistency with other APRA forms (e.g. item 2 must equal item 1.1 column 1 of SRF 530.0 or SRF 530.1) and with specified prudential standards (SPS 114 ORFR, SPS 160 defined benefit matters, SPS 310 audit matters, SPS 510 governance) and accounting standards (AASB 132 for offsetting derivatives). These external texts supply substantive measurement and disclosure rules referenced back into the Reporting Standard (Instructions: item 2 and various definitions; Interpretation para 17).
• Assurance and governance. Quality control and assurance obligations place responsibilities on auditors and on the RSE licensee board and senior management to test and authorise the data , including a minimum of an annual audit review and a limited assurance engagement in line with professional standards subject to SPS 310 (paras 11-12).
• Submission mechanics and authorisation. The RSE licensee must submit electronically via D2A when available, and submissions must be digitally signed with a certificate acceptable to APRA. Agents may submit but the RSE licensee remains obliged to obtain and retain a copy and ensure authorised submitters are authorised by the CEO or CFO (para 6; paras 13-15).

These concepts combine to produce a technical, rule-based data collection regime that links statutory reporting to financial accounting, prudential standards and audit assurance.

The Reporting Standard identifies several categories of liable parties and excluded groups and places different operational obligations on them:

• Primary obligated parties. RSE licensees are the legal addressees of the Reporting Standard. Paragraph 3 imposes the obligation on “each registrable superannuation entity (RSE) licensee in respect of each RSE, defined benefit RSE, pooled superannuation trust (PST) and eligible rollover fund (ERF) within its business operations.” In practical terms, the RSE licensee must provide SRF 320.0 for each distinct RSE, defined benefit RSE, PST or ERF that it operates (para 3; fn [1]).
• Specific entity-types. The instrument distinguishes between ordinary RSEs and defined benefit RSEs, PSTs and ERFs for the purpose of reporting and definitions. Some items are adjusted in scope for PSTs and defined benefit RSEs (Instructions: Item 23 notes PSTs report item 23.1 but not 23.2 or 23.3; definitions at para 17).
• Excluded entities. The Reporting Standard does not apply to “small APRA funds” (fewer than five members) and “single member approved deposit funds” (single-member ADFs) as defined in the footnotes and para 17 and fn [5], [6]. Those entities are outside the Standard’s reporting requirement.
• Internal actors. The Board and senior management of the RSE licensee are assigned responsibility for having policies and procedures for the internal review and authorisation of data submitted to APRA (para 12). The RSE auditor must review and test systems, procedures and internal controls and perform at least a limited assurance engagement each year to enable an opinion on reliability and accuracy (para 11).
• Agents and authorised signatories. Where an agent submits on the licensee’s behalf via D2A, the RSE licensee must obtain and retain a copy of the completed form (para 14). Only submitters authorised by the RSE licensee’s CEO or CFO may submit (para 15). Submissions via D2A require a digital certificate acceptable to APRA (para 13).
• APRA. APRA is the recipient and decision-maker for notice-based changes: it may change reporting periods for particular RSEs, grant extensions, vary reporting requirements by written notice, and specify alternative submission methods where D2A is not available (paras 6-10; para 16).

Who pays and who bears operational cost. RSE licensees pay the compliance and assurance costs: systems, reconciliations, auditing/limited assurance engagements, staff time to compile and digitally sign returns, and any fees for digital certificates and agent services. APRA incurs the cost of maintaining D2A and processing returns and may publish the data (para 2).

Who decides. APRA decides the format (D2A), frequency and may vary timing or content by notice (paras 6-9; para 16). The RSE licensee decides the internal processes and resourcing required to meet the obligations, and the RSE auditor decides the scope of assurance consistent with the professional standards and SPS 310 (para 11).

Behavioural changes required. RSE licensees must adapt accounting, reconciliation and governance processes to produce the specific data fields required, ensure that cross-form matches (e.g. SRF 530.0) reconcile, maintain audit trails and ensure authorised signatory and digital certificate arrangements are in place (para 6; paras 11-15; Instructions). PSTs and defined benefit RSEs must apply tailored reporting logic where the form specifies exclusions or special reporting rules (Instructions: Item 23).

The Reporting Standard creates a set of affirmative duties on RSE licensees and assigns rights and discretions to APRA. The obligations are concrete and are tied to the form's items, governance and assurance requirements.

Primary duties of RSE licensees

• Provide the information required by SRF 320.0 for each reporting period (para 5). This is an affirmative duty attaching to the RSE licensee in respect of each RSE, defined benefit RSE, PST and ERF within its business operations (para 3).
• Submit electronically using the Direct to APRA application where available, or an APRA-notified alternative, and digitally sign submissions using an APRA-acceptable digital certificate (para 6; para 13).
• Ensure submissions are made by an officer or agent authorised by either the CEO or CFO of the RSE licensee (para 15).
• Retain copies from any agent submissions and obtain completed forms where an agent acts (para 14).
• Provide quarterly and annual reports in accordance with the specified reporting periods and due dates (paras 7-9). Note the specific transitional due-date change from 35 days to 28 days after 1 July 2017 for quarterly returns (para 9(a)).
• Ensure information produced is the product of systems, procedures and internal controls reviewed and tested by the RSE auditor at least annually and, at minimum, via a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance and SPS 310 (para 11).
• Put in place systems, processes and controls for internal review and authorisation and ensure board and senior management oversight of these policies (para 12).
• Complete item-level instructions in SRF 320.0 consistent with Australian Accounting Standards and the specified definitions and conventions, including derived items and reconciliations with other APRA forms (Instructions: Reporting basis and specific items).

APRA’s discretions and rights

• APRA may alter reporting frequency for particular entities where it considers it necessary or desirable, by written notice (para 8).
• APRA may vary the reporting requirements of SRF 320.0 in relation to an RSE licensee or particular RSEs, PSTs or ERFs by written notice (para 16).
• APRA may grant written extensions of due dates (para 10).
• APRA prescribes the acceptable digital certificate and submission method when using D2A (paras 6, 13). The Reporting Standard explicitly contemplates APRA operational control over submission processes.

Rights implicit in the instrument

• APRA has the stated right to use the collected information for publication as well as prudential supervision, and to share with the Australian Bureau of Statistics (para 2).
• RSE licensees retain the right to engage agents to submit data, but retain responsibility to obtain and keep a copy of what was submitted and to ensure authorised signatories are in place (paras 14-15).

Key reporting conventions and constraints

• Reporting must follow Australian Accounting Standards (Instructions: Reporting basis).
• Units must be reported as thousands of dollars (Instructions).
• Several items are derived and must reconcile to other data (e.g., item 2 must equal SRF 530.0 SRF 530.1; items 10, 13, 19, 21, 22.2, 23 and 24 are derived) (Instructions: Item 2 and derived item notes).
• The ORFR reserve must be separately identifiable from member accounts and other reserves in the RSE (Instructions: Item 22).

Practical consequences of duties

• The duties require RSE licensees to invest in accounting mappings and reconciliation processes between statutory accounts, APRA forms and prudential standards; to maintain auditor relationships capable of delivering the specified limited assurance; and to set up digital certificates and authorised signatory processes. The Reporting Standard connects statutory reporting to governance and audit processes (paras 11-12; paras 13-15).

The Determination itself does not specify criminal or civil penalties or enforcement sanctions within its text. The instrument is made under the Financial Sector (Collection of Data) Act 2001 (Authority 1) and the preamble records that it is declared to begin under section 15 of the Act (preamble; Authority 1). The Act provides the statutory framework for data collection and likely contains enforcement provisions and penalties, but those penalties are not set out in this Reporting Standard. Therefore the textual enforcement mechanisms contained in the Reporting Standard are primarily administrative and processual rather than punitive.

Concrete enforcement and compliance controls specified in the Reporting Standard

• Notice powers and variation. APRA may, by written notice, change reporting periods, vary reporting requirements for a particular RSE licensee or particular RSEs/PSTs/ERFs, and specify timeframes; this gives APRA administrative leverage to require amendments or additional reporting when it considers it necessary or desirable (para 8; para 16).
• Extension power. APRA may grant extensions of due dates in writing, creating an administrative remedy for late reporting where APRA exercises the discretion (para 10).
• Digital signature requirement. Submissions via D2A must be digitally signed with a certificate acceptable to APRA (para 13). That requirement creates an audit trail and a liability vector for signing officers and authorised submitters (paras 13-15).
• Assurance and audit requirements. Paragraph 11 requires that the information be the product of systems and controls reviewed and tested by the RSE auditor, with at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance and SPS 310. This imposes an external assurance mechanism that functions as an enforcement and quality-control tool.
• Internal governance obligations. Paragraph 12 places responsibility on the Board and senior management to ensure policies and procedures for authorisation of information. These obligations can be enforced indirectly via prudential supervision activities.

What is not in the instrument

• Specific pecuniary penalties, infringement notices, civil sanctions or criminal offences are not included in this Determination. If statutory penalties apply to failure to provide data or to false or misleading data they will be contained in the parent Act or other legislation not reproduced in this instrument. The Reporting Standard instead relies on process requirements, audit assurance and APRA’s statutory supervisory powers to secure compliance (paras 11-16).

Enforcement risks and practical points

• Because the Reporting Standard requires systems and auditor assurance, enforcement in practice will likely involve APRA testing reports for accuracy and seeking remedial action where inconsistencies are identified. APRA’s ability to vary and require more frequent reporting (paras 8 and 16) is a practical tool for responding to compliance problems.
• The digital-signature requirement and the CEO/CFO authorisation regime (paras 13-15) mean signatures and delegation records will be focal points in any investigation into incorrect reporting.

Readers must consult the Financial Sector (Collection of Data) Act 2001 and relevant prudential standards for definitive statements about civil or criminal liability because this Determination does not itself list penalties.

The Reporting Standard explicitly ties itself to a set of external legal and regulatory instruments and professional standards. These interactions create layered obligations and points of coordination between accounting, prudential and auditing regimes.

Primary legislative and regulatory cross-references

• Financial Sector (Collection of Data) Act 2001. The Reporting Standard is made under section 13 of that Act and its commencement is declared under section 15 (Authority 1; preamble). The Act therefore supplies the statutory power for APRA to require the data.
• Superannuation Industry (Supervision) Act 1993 (SIS Act). Numerous definitions (RSE, ERF, PST, year of income) and reporting requirements reference meanings in the SIS Act (para 17 and Instructions: Interpretation). Item 13 requires reporting of whether a borrowing arrangement falls under the exceptions in s 67 of the SIS Act and limited recourse borrowing arrangements in ss 67A and 67B (Instructions: Item 13).
• Australian Accounting Standards and AASB 132. The Reporting Standard requires that items be reported in accordance with Australian Accounting Standards, and derivative offsetting rules must follow AASB 132 (Instructions: Reporting basis; Items 4 and 14).
• Prudential Standards. The instrument cross-references multiple prudential standards:
  • SPS 114 Operational Risk Financial Requirement for the ORFR reserve (Instructions: Item 22).
  • SPS 160 Defined Benefit Matters for the definition of defined benefit RSE (para 17; Instructions).
  • SPS 310 Audit and Related Matters for auditing requirements and consistency with the limited assurance engagement (para 11; fn [3]).
  • SPS 510 Governance for the definition of Chief Executive Officer (para 17; fn [4]). These standards supply substantive measurement, governance and audit rules that influence how SRF 320.0 is prepared and assured.
• Auditing and Assurance Standards Board guidance. Paragraph 11 requires the RSE auditor’s review and testing to be at least a limited assurance engagement consistent with professional standards and guidance notes issued by the Auditing and Assurance Standards Board, subject to SPS 310.

Operational and administrative cross-references

• Other APRA reporting forms. The Instructions require consistency across APRA forms: item 2 must equal SRF 530.0 item 1.1 column 1 of SRF 530.0 Investments or SRF 530.1 (Instructions: Item 2). This enforces data consistency across APRA’s data ecosystem.
• APRA’s Direct to APRA application (D2A). The choice of submission method ties the Reporting Standard to APRA’s technological infrastructure (para 6).
• Australian Bureau of Statistics. APRA may share the collected information with ABS for statistical purposes (para 2).

Practical effects of these interactions

• Measurement and judgement. Because the Reporting Standard defers to Australian Accounting Standards, AASB 132 and prudential standards for measurement, the preparation of SRF 320.0 will require application of accounting judgement and actuarial or prudential judgement (for example in defined benefit valuations per SPS 160, or ORFR calculations per SPS 114). Those judgments are governed by the substantive standards, not by the Reporting Standard itself, which serves as the data capture mechanism (Instructions; para 11).
• Reconciliation and duplication risk. The cross-form reconciliation requirement (item 2 to SRF 530.x) and the requirement to report values according to accounting standards mean that RSE licensees must align statutory accounts, APRA forms and audit workpapers. This may increase compliance cost but also ensures internal consistency between prudential returns.
• Overlap with audit and governance obligations. The Reporting Standard embeds obligations that interact with SPS 310 and SPS 510. The RSE licensee must align governance documents, audit scope and internal controls to satisfy both the prudential standards and this Reporting Standard (para 11; para 12).
• Disclosure and confidentiality. The Reporting Standard expressly contemplates publication of collected information (para 2). The degree of publication and any confidentiality protections will be governed by APRA’s publication policies and the parent Act, which are external to this instrument.

In short, SRF 320.0 is a node that links statutory data collection to accounting, prudential and audit regimes. Compliance therefore requires attention to the substantive measurement rules and to the administrative procedures set by APRA and referenced prudential standards.

The instrument itself records a single explicit amendment action: it revokes Financial Sector (Collection of Data) (reporting standard) determination No. 18 of 2014 and replaces Reporting Standard SRS 320.0 Statement of Financial Position with the version set out in the Schedule (preamble (a) and (b)). The Determination is dated 13 August 2015 and the delegate declared under section 15 of the Act that the reporting standard shall begin to apply to those financial sector entities and the revoked reporting standard shall cease to apply on the date of registration (preamble; Authority 1). The instrument thereby effected the substitution of a new Reporting Standard.

What the text shows about subsequent amendments

• No later amendments are recorded in the document. The Schedule states that the Reporting Standard applies for reporting periods ending on or after 1 July 2015 (para 4), and the transitional due-date change (from 35 days to 28 days after quarter end for reports ending on or after 1 July 2017) is itself included in the Instructions (para 9(a)(i)-(ii)). The instrument thus contains at least one internally timed change to due dates but not an external subsequent amendment history.
• The text includes references to existing prudential standards and professional standards. Future amendments to those external standards or to the Financial Sector (Collection of Data) Act could affect the operation of SRF 320.0, but such changes are not recorded in this instrument.

Practical note for users

• Adopt the 2015 version as the operative text unless and until APRA issues a subsequent Determination or variation. Because the instrument revokes No. 18 of 2014, users moving from the older reporting regime should check for any substantive changes in item definitions, derived items, and submission mechanics between the two texts. The instrument itself does not include an amendment history beyond the revocation and replacement action taken on registration.

If a practitioner requires a consolidated legislative history covering later amendments, they must consult the Federal Register of Legislation or APRA’s current instrument register; the Reporting Standard as presented contains only the substitution event and the effective dates described.

The Reporting Standard document contains no record of litigation, judicial decisions, or tribunal determinations concerning its interpretation or enforcement. The instrument is an administrative data-collection determination made by APRA under the Financial Sector (Collection of Data) Act 2001, and the Schedule contains technical reporting instructions rather than case law references. Accordingly:

• The source text names no cases and records no legal proceedings or contested enforcement actions (entire instrument).
• The Reporting Standard’s operational features , derived items, cross-references to accounting and prudential standards, auditor assurance requirements and APRA notice powers , create potential factual and legal dispute points, but the text does not evidence any actual litigation arising from those features.

Potential dispute areas grounded in the text (these are mechanisms where contests could arise, rooted in the Standard’s content)

• Application of accounting standards and AASB 132 offsetting rules for derivatives (Items 4 and 14). Interpretation of eligibility for offset under AASB 132 involves accounting judgement that could be contested between an RSE licensee, its auditor and APRA.
• Valuation of defined benefit liabilities and the interaction with the last triennial review (Instructions: Item 23). Defined benefit valuation is actuarial in nature and may give rise to disagreement about measurement and the proper amount to report under item 23.2 and related items.
• Treatment of ORFR and reserves. The ORFR reserve must be separately identifiable and reported in item 22.1. Disputes may arise about what constitutes an ORFR reserve and the correct allocation of transfers into and out of reserves (Instructions: Item 22 and reference to SPS 114).
• Reporting of borrowings and limited recourse exceptions under ss 67, 67A, 67B of the SIS Act (Instructions: Item 13). Determining whether a borrowing falls within the exceptions involves legal interpretation of the SIS Act provisions and factual analysis of the arrangement.
• Reconciliation between SRF 320.0 and other APRA forms, for example SRF 530.0 / 530.1 (Instructions: Item 2). Failures to reconcile could generate regulatory inquiries or disputes over the correct reported numbers.

Absent judicial decisions in the source, practitioners should treat these as practical risk areas where differences in professional judgment, audit opinion and APRA’s supervisory view could escalate into formal disputes. For a definitive account of litigation history subsequent to 2015, users must consult external legal databases and APRA’s enforcement reports; that material is not contained in the Reporting Standard text.

The Reporting Standard instructs technical reporting but embeds a number of traps for the unwary. These are concrete points where errors commonly occur, or where the Standard’s mechanics create operational risk. Each “gotcha” below is grounded in the instrument’s text.

1. Derived items and arithmetic consistency

• Several items are explicitly derived and must reconcile to other fields: item 10 is total assets (item 11) minus listed asset categories; item 13 is the sum of entries in item 13.1; item 19 is total liabilities (item 20) minus specified liability categories; item 21 is item 11 minus item 20; item 22.2 is the sum of item 22.1 column 6; items 23 and 24 are derived (Instructions: Items 10, 13, 19, 21, 22.2, 23, 24). Mis‑calculation in any constituent field propagates to derived fields and can trigger APRA queries.

2. Units and rounding

• All amounts must be reported in thousands of dollars (Instructions: Reporting basis and units). Failure to scale amounts correctly will produce large reporting errors.

3. Cross-form reconciliation requirement

• Item 2 investments must equal item 1.1 column 1 of SRF 530.0 or SRF 530.1 (Instructions: Item 2). If investment data feeding those forms are inconsistent, APRA will detect discrepancies.

4. Timing and due-date change

• Quarterly due dates change from 35 days to 28 days after 1 July 2017 (para 9(a)(i)-(ii)). Practitioners must be aware of the transitional timing and apply the correct deadline for the relevant reporting period.

5. Submission mechanics, digital certificates and authorised signatories

• Submissions via D2A must be digitally signed with an APRA-acceptable certificate (para 13). Only officers authorised by the CEO or CFO may submit (para 15). Agents may submit but the licensee must retain the completed copy (para 14). Failure to have the correct certificate or authorised submitter will result in a technically invalid submission.

6. Auditor assurance specificity

• Paragraph 11 requires that the data be the product of systems and controls reviewed and tested by the RSE auditor and that this be at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance, insofar as not inconsistent with SPS 310. This is not a free-form audit tick-box. The audit scope must enable an auditor opinion on the reliability and accuracy of reported information. If the auditor’s engagement letter does not include the requisite procedures, APRA may question whether the assurance requirement has been met.

7. ORFR and reserves reporting rules

• ORFR reserves must be separately identifiable from member accounts and other reserves (Instructions: Item 22). Transfers into and out of reserves must be reported gross and earnings/losses reported as positive numbers (Instructions: Item 22). Mis‑labelling or unit errors here distort net assets and levy calculations.

8. Borrowing description and SIS Act cross-reference

• Item 13.1 must report if an arrangement falls within exclusions in s 67 or limited recourse borrowing in ss 67A and 67B of the SIS Act (Instructions: Item 13). Errors here may mischaracterise fund risk and security positions.

9. PST and defined benefit specific rules

• For PSTs, item 23.1 should be completed but 23.2 and 23.3 should not be completed (Instructions: Item 23). Defined benefit calculations must follow SPS 160 and can involve triennial review inputs; inconsistent application produces variance (Instructions: Item 23).

10. Item 25 (levies) only in annual return

• Item 25 must be reported only in the annual return. For RSEs with balance dates other than 30 June there are detailed rules about which notional or unaudited estimates to report (Instructions: Item 25). Mis‑reporting item 25 on a quarterly return will be wrong and could misstate levy bases.

11. Publication

• APRA may publish data collected (para 2). Reporting licensees should confirm whether particular items will be public and manage confidentiality and disclosure risk accordingly.

12. Scope of application

• The Reporting Standard applies to each RSE, defined benefit RSE, PST, and ERF within an RSE licensee’s business operations and requires separate submissions for each fund where the licensee is trustee of more than one RSE (fn [1]). Consolidated reporting without per-RSE breakdowns will not comply.

13. Accounting standard choices and offsetting rules

• Items 4 and 14 require the application of offsetting rules per AASB 132. Determination of what qualifies for offset involves strict eligibility criteria under AASB 132; incorrect application changes reported net derivatives positions.

14. Sign convention traps

• The Instructions specify reporting conventions: transfers into/out of reserves are to be reported as positive numbers in specified columns and transfer into reserve reported gross of transfer out, transfer out gross of transfer in, earnings/losses as positives (Instructions: Item 22). Excel formula errors or misinterpretation of sign conventions will produce inconsistent aggregates.

15. Early and late balancing RSEs

• Special rules for early-balancing (balance date between 1 January and 29 June) and late-balancing RSEs (balance date between 1 July and 31 December) apply to item 25 reporting (Instructions: Item 25). Practitioners must apply the correct 30 June reference date for notional and unaudited estimates.

Record-keeping and workflows must address each of these “gotchas” to avoid reporting errors and downstream supervisory queries.

Compliance requires a practical project plan that maps statutory fields to accounting systems, sets governance and audit scope, and ensures correct submission mechanics. The following steps translate the Reporting Standard’s requirements into an operational checklist, grounded in the instrument’s provisions.

1. Confirm Applicability and Reporting Level (para 3; para 17; fn [1], [5], [6])

• Determine the set of entities for which the RSE licensee must submit SRF 320.0: each RSE, each defined benefit RSE, each PST and each ERF within the licensee’s business operations. Exclude small APRA funds and single-member ADFs as defined in the footnotes (para 3; para 17; fn [5], [6]).

2. Map items to accounting books and other APRA returns (Instructions: Reporting basis; Item 2)

• Create a mapping document showing the source ledgers, sub-ledgers and external valuations that feed each SRF 320.0 item. Pay particular attention to items that must reconcile to other APRA forms, e.g., item 2 must equal SRF 530.0/530.1 item 1.1 column 1 (Instructions: Item 2).
• Identify derived items (Items 10, 13, 19, 21, 22.2, 23, 24) and build formulae that automatically compute derived values from constituent fields, with reconciliation checks.

3. Ensure accounting policies and measurement align with Australian Accounting Standards and referenced prudential standards (Instructions: Reporting basis; Items 4, 22; para 17)

• Confirm that measurement (e.g., derivative gross market values, offsetting, deferred tax, defined benefit liabilities) is performed in accordance with applicable Australian Accounting Standards and AASB 132 where relevant (Items 4 and 14).
• For ORFR and defined benefit measures, apply prudential standards SPS 114 and SPS 160 as required and ensure documentation linking these calculations to the SRF fields (Instructions: Item 22; para 17).

4. Set units and rounding rules (Instructions)

• All items must be reported in thousands of dollars. Establish rounding and aggregation conventions and validate scaling across systems.

5. Establish governance, internal control and authorisation processes (paras 11-12; paras 13-15)

• The Board and senior management must set and document policies and procedures for the internal review and authorisation of information submitted to APRA (para 12).
• Define who will be authorised submitters. Only individuals authorised by the CEO or CFO may submit (para 15). Maintain delegation registers and evidence of authorisation.
• Acquire and manage a digital certificate acceptable to APRA for D2A submissions and ensure submission staff are trained on D2A.

6. Coordinate audit assurance work (para 11)

• Liaise with the RSE auditor to ensure their engagement letter and scope include: annual review and testing of systems, procedures and internal controls that produce the reporting; and a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance as not inconsistent with SPS 310 (para 11). Ensure the auditor’s timing aligns with reporting due dates.

7. Build technical validation and reconciliation routines

• Implement automated validation rules to flag: derived-item mismatches, cross-form inconsistencies (e.g. SRF 530.x), negative balances where not permitted, and sign convention errors for reserves and transfers (Instructions: Item 22).
• Maintain a reconciliation log documenting the origin and calculation of each SRF 320.0 field and cross‑references to source financial statements, general ledger accounts and other APRA forms.

8. Plan reporting calendar and resourcing (paras 7-10)

• Calendar the quarterly and annual reporting cycles. Apply the correct due dates: quarterly within 35 calendar days after the end of the quarter for reporting periods ending on or after 1 July 2015 but before 1 July 2017, and within 28 calendar days for periods ending on or after 1 July 2017; annual returns within three months after year end (para 9).
• Where business circumstances demand, be prepared to respond to APRA notices changing the frequency or timing or to request an extension in writing (para 8; para 10).

9. Prepare special-purpose fields and instructions

• Reserves: implement tracking for each reserve type listed (ORFR, investment, self-insurance, administration, other) and capture transfers into/out, earnings and losses as positive numbers and closing balances (Instructions: Item 22).
• Borrowings: capture detailed descriptions for each borrowing line and report whether the borrowing falls within SIS Act exceptions (ss 67, 67A, 67B) and the secured portion (Instructions: Item 13).
• Member benefits: ensure the split between defined contribution and defined benefit members is properly calculated and that PSTs follow the special rule for item 23 (Instructions: Item 23).

10. Controls for agent submissions and record retention (paras 14-15)

• If using an agent to submit via D2A, obtain and retain a completed copy of the form and ensure agent processes are audited and documented (para 14).
• Ensure agents only submit after authorisation by CEO or CFO (para 15).

11. Prepare for data publication and regulatory use (para 2)

• Since APRA may publish the data and use it for prudential supervision and for ABS purposes (para 2), RSE licensees should review disclosed items for confidentiality implications and prepare public‑facing reconciliations where necessary.

12. Test and document

• Run “dress rehearsal” submissions well ahead of first live due dates to confirm D2A compatibility, digital signing, derived-item reconciliation and auditor sign-off processes.
• Maintain a documentation pack containing mapping, reconciliation workpapers, governance approvals, auditor assurance reports and evidence of digital signatory authorisation.

13. Ongoing maintenance and change control

• Keep an eye on changes to the referenced prudential standards (SPS 114, SPS 160, SPS 310, SPS 510), Australian Accounting Standards and AASB 132, and on any APRA notices that vary reporting periods or content (para 8; para 16; para 17).
• Update mapping and systems promptly when APRA issues variations or when accounting/prudential standards evolve.

By following these steps,mapping, governance, audit alignment, reconciliation, and rigorous controls,an RSE licensee can translate the Reporting Standard’s technical instructions into compliant, reliable reporting. The Standard’s explicit cross-references and derived-item relationships mean that preparation is not merely administrative but requires integration of accounting, actuarial and audit inputs under board-approved procedures (paras 11-12; Instructions).