Financial Sector (Collection of Data) (reporting standard) determination No. 5 of 2015 - SRS 161.0 - Self-Insurance

The document organises reporting around a small set of repeatable concepts: claims status, monetary quantum, insurance type, reinsurance cluster, cover type, premiums flows and associated-party status. Those concepts and their precise operational meanings in this instruction are:

• Claims reported (not admitted) and claims admitted (not yet paid): Item 2 defines “claims reported (not admitted)” as notifications to an insurer for which acceptance is pending, and “claims admitted (not yet paid)” as claims where the insurer has made a final decision to admit but has not yet paid (Item 2 table). These two states separate notification incidence from insurer liability recognition.
• Claims value and claims paid: “Claims value” (Item 2) is the insurer’s expected payment for claims; Item 3’s “claims paid” covers cash or equivalent payments, explicitly including rehabilitation costs and benefits or prepayments that reduce claims experience (Item 3 table). For income protection claims, the instrument treats the monetary amount differently , reporting monthly amounts in item 2 column 4 and total period payments (including ongoing payments) in item 3 monetary columns.
• Insurance types: The instrument requires standard classification into life, TPD, income protection, and “other” insurance. Many entries are by insurance type (Item 2.1, Item 3.1).
• Reporting basis and units: The instrument distinguishes snapshot (as at end of reporting period) versus transaction-period reporting. Item 2 is a snapshot for columns 2-4; Item 3 and parts of item 4.2 are flow-based (transactions during the reporting period). Units vary by column: counts must be whole numbers; monetary values are generally thousands of dollars; income protection column 4 in Item 2 is a monthly amount (Item 2, Item 3).
• Reinsurance cluster and cover types: Item 4 requires aggregation of reinsurance policies by reinsurer (“a cluster”) and explicit breakouts by cover type , stop-loss, catastrophe, other reinsurance. For each cover type reported, the template requires member accounts covered and cover limits (Item 4.1).
• Premium flows and rebates: Item 4.2 requires reporting of premium collected, premium paid gross of rebates, and the payer (RSE, RSE licensee, employer-sponsor), plus reinsurance claims paid by the reinsurer. The instrument records how to treat reinsurance premiums charged to the RSE’s self-insurance reserve: in that case report the premium in item 4.2 column 3 and zeros in columns 2, 4, 5 and 6 where not relevant.
• Associates and ABNs: Item 4.1 requires the reinsurer’s name and ABN and a yes/no flag if the reinsurer is an associate of the RSE licensee. The instrument explicitly references s.12 of the SIS Act for the meaning of “associate” and the ABN is described as the public identifier issued by the Australian Business Register (Item 4 definitions, Interpretation).

Interpretive cross-references are central. The instrument ties several of its defined terms back to external instruments: “acquired insurance” and “insurer” are linked to Prudential Standard SPS 250; “defined benefit member” and “defined benefit RSE” are tied to SPS 160; RSE and RSE licensee refer to s.10(1) of the SIS Act; “associate” refers to s.12 of the SIS Act. The definitions constrain who must report: RSE means an RSE as defined in s.10(1) but expressly excludes defined benefit RSEs, pooled superannuation trusts, eligible rollover funds, small APRA funds and single-member approved deposit funds (Interpretation).

Main data controls in the document are prescriptive: derived totals (Item 2.2 and 3.2) must equal column totals of related sub-items; cluster identification must be consistent across item 4.1 and 4.2 (same reinsurer name and ABN); ceased policies are to be reported with zeros for cover columns but with transaction values captured for the period up to cessation; and premiums from the self-insurance reserve have a specified reporting column treatment. Those controls create deterministic validation rules that should be built into reporting systems.

Primary obliged parties are RSE licensees that maintain self-insurance arrangements covering members of an RSE. The instrument’s definition of RSE refers to section 10(1) of the SIS Act and explicitly excludes certain RSE types, meaning the reporting population is RSE licensees for non‑defined benefit funds and not pooled superannuation trusts, eligible rollover funds, small APRA funds or single-member approved deposit funds (Interpretation).

Affected internal actors within an RSE licensee include:

• Finance and actuarial teams responsible for quantifying claims admitted but unpaid, claims reported, and the value of claims (the instrument requires counts, admitted amounts and expected payments; Item 2, Item 3);
• The RSE actuary, as defined by the instrument , the RSE actuary is named in the Interpretation and will likely be relied upon to support valuation and assumptions for claims value and self-insurance reserve impacts;
• Treasury/insurance operations staff who manage reinsurance procurement, premium payments, and liaison with reinsurers and insurers to obtain ABNs and transaction-level premium and claim data;
• Compliance, legal and data teams tasked with mapping insurer and reinsurer identifiers to the template’s ABN/name fields and validating whether a reinsurer is an “associate” under s.12 of the SIS Act.

External affected parties include:

• Insurers and reinsurers who must provide claims notices, admissions, payment details, premium invoices and rebates, and confirmations of member accounts covered and cover limits. Item 4’s cluster construct and required ABNs mean insurers/reinsurers’ public identifiers are necessary inputs.
• Employer-sponsors where they bear or reimburse reinsurance premiums , item 4.2 explicitly asks for premiums paid by employer-sponsors and requires those flows to be reported separately from premiums paid by the RSE or RSE licensee.
• Auditors and regulators who use the reported data to assess claims experience, self-insurance adequacy and the alignment between reinsurance purchasing and exposures. The instrument cross-references SIS Act and prudential standards (SPS 250, SPS 160), which are enforced by the prudential regulator through the prudential framework (Interpretation).

Indirectly affected are members, because the instrument requires reporting of member accounts covered and cover limits; these data feed into the regulator’s view of fund-level insurance adequacy and the scope of retained risk for members. The identity of reinsurers and whether they are associates may affect conflict-of-interest assessments.

The instruction also affects data flows between entities: when reinsurance premiums are paid from the RSE’s self-insurance reserve, item 4.2 prescribes reporting the premium amount in a specific column and zeros elsewhere. That rule imposes an internal allocation decision on who books the premium and how the RSE records it. Reporting of previous reinsurers over a rolling five-year period requires RSE licensees to maintain a historical register of reinsurance arrangements for at least that horizon, and to include reinsurers that became “previous” during the reporting period in both items 4 and 5.

Duties

• Accurate completion of itemised reporting fields. The instrument prescribes precise columns and units (whole numbers for counts, thousands of dollars for monetary fields in many columns, monthly amounts for certain income protection fields) and requires that derived totals (e.g. Item 2.2 and Item 3.2) equal the summed correspondents in sub-items (Item 2.2, Item 3.2).
• Temporal fidelity. The reporting basis is defined differently by item and column: Item 2 columns 2-4 must be reported “as at the end of the reporting period”; Item 3 and parts of Item 4.2 are transaction-based for the reporting period (Item 2, Item 3, Item 4 instructions). The RSE licensee must therefore maintain both snapshot and flow accounting capabilities and ensure temporal alignment with the reporting window.
• Aggregate by cluster: For Item 4 the RSE licensee must aggregate reinsurance policies by reinsurer (“a cluster”) and report each cluster’s cover types and premium flows on separate lines (Item 4 instructions). The cluster construct is mandatory and requires consistent naming and ABN use across item 4.1 and 4.2.
• Associate disclosure: Where the reinsurer is an associate of the RSE licensee, the instrument requires the RSE licensee to report ‘yes’ in item 4.1 column 3; otherwise report ‘no’. The instrument points to s.12 of the SIS Act for the meaning of associate. This imposes a duty to assess relatedness under the SIS Act before populating the field (Item 4.1).
• Treatment of ceased policies: If a reinsurance policy ceased during the reporting period the RSE licensee must report zeros for item 4.1 columns 4-9 and report the premium and rebate values in item 4.2 columns for transactions prior to cessation (Item 4 instructions).
• Reporting of previous reinsurers: The RSE licensee must report reinsurers with whom it held previous reinsurance policies over the last five years and must include reinsurers whose contract became a previous reinsurance policy during the reporting period in both item 4 and item 5 (Item 5).
• Specific treatment for premiums paid from self-insurance reserve: where premiums are paid from the RSE’s self-insurance reserve, report that premium in item 4.2 column 3 and report zeros in columns 2, 4, 5 and 6 where not relevant (Item 4 instructions).

Rights and practical entitlements (implicit or operational)

• Use of estimates: The instrument recognises situations where an estimate for column 4 in Item 2 may be unavailable and permits reporting the maximum sum insured (or monthly amount for income protection) in lieu of a better estimate (Item 2). This gives operational leeway where precise expected payments are not yet determinable.
• Aggregation vs policy detail: The instrument permits aggregation of reinsurance policies into clusters by reinsurer rather than requiring each underlying policy line-by-line in item 4. That reduces granularity burdens where a single reinsurer writes many policies.
• Explicit data mapping rules: By specifying where to report premiums paid by the RSE, RSE licensee or employer-sponsor (item 4.2 columns 3-5), the instrument clarifies the allocation of premium flows across payer types. This reduces interpretive uncertainty about which column to use for each payer.

The instrument does not itself set out a rights-of-review or internal dispute mechanism about what must be reported; practical rights to challenge data requests or seek clarification will operate through the RSE licensee’s normal channels with insurers/reinsurers and through any regulator guidance. Because the document cross‑references the SIS Act, SIS Regulations and Prudential Standards, obligations under those instruments (such as disclosure obligations and the prudential regulator’s supervisory powers) provide the broader legal framework for the duties here, but the instruction itself is primarily a technical reporting specification.

The text provided is a reporting instruction and does not itself specify penalties, monetary fines or enforcement procedures. It repeatedly references the SIS Act, SIS Regulations and Prudential Standards (SPS 250 and SPS 160), which establish the wider legal and prudential environment in which these reporting obligations sit (Interpretation). The absence of express penalty clauses in the text means that any sanctioning power, compliance review or remedial action would arise under those external instruments or an agency’s supervisory powers rather than from this instruction alone.

Consequently, the enforcement landscape for failures or errors in these returns will depend on:

• The provisions of the SIS Act and SIS Regulations that govern RSE licensee obligations, records and reporting generally. The instrument cites the SIS Act and uses its definitions (Interpretation). Section references used in the definitions (s.10(1), s.12) indicate a close link to statutory definitions that are used to determine who must report and who counts as an associate.
• Prudential Standards referenced (SPS 250, SPS 160). These standards are part of the prudential framework applicable to RSE licensees and set prudential obligations around insurance, self-insurance reserves and defined benefit matters; breaches of prudential standards are actionable within the prudential supervisory regime (Interpretation).
• Operational enforcement by the prudential regulator. While the document does not name the regulator, prudential standards and SPS instruments are the tools through which prudential supervision and follow-up occur. Any regulator-led inquiries, directions, enforceable undertakings or public actions would be driven by deficiencies identified relative to these broader statutes and standards, not by this template alone.

Practical enforcement risks and compliance hazards to be considered by RSE licensees include:

• Reputational or supervisory follow-up if reported numbers are materially deficient or inconsistent with other disclosures such as financial statements, actuarial reports, or self-insurance reserve movements.
• Potential regulatory questions where associate relationships (s.12 SIS Act) are misreported or where premium flows between employer-sponsors and the RSE are not correctly classified in item 4.2 columns.
• Operational audit findings or adjustments if derived items do not reconcile with per-line inputs (the instrument mandates derived totals).

Because the instrument imposes prescriptive data controls, failures of internal systems, inconsistent ABN/name reporting across item 4.1 and 4.2, or incorrect temporal treatment of columns (snapshot vs transaction) can produce mis-statements that attract regulatory attention. However, any formal penalty or enforcement measure would be grounded in the SIS Act, SIS Regulations or prudential standards rather than this instruction’s own text.

The instrument explicitly references and integrates with several existing legal and prudential instruments; it does not operate in isolation. The most important cross‑links in the text are:

• SIS Act (Superannuation Industry (Supervision) Act 1993): The instruction uses definitions drawn from the SIS Act , RSE and RSE licensee are defined pursuant to s.10(1) of the SIS Act and the instrument also references s.12 for the meaning of “associate” (Interpretation; Item 4 definitions). Those cross-references anchor the reporting population and the treatment of associated‑party relationships to statutory definitions.
• SIS Regulations (Superannuation Industry (Supervision) Regulations 1994): The instrument references the SIS Regulations for the definition of “self-insurance arrangement” and presumably relies on the regulatory framework that governs what self-insurance is permitted and how it is prudentially overseen (Interpretation).
• Prudential Standard SPS 250 Insurance in Superannuation: Multiple defined terms such as “insurer” and “acquired insurance” are tied back to SPS 250. That implies the reporting is designed to feed into the prudential framework SPS 250 establishes for insurance arrangements within superannuation funds (Interpretation).
• Prudential Standard SPS 160 Defined Benefit Matters: The instrument uses SPS 160 to define “defined benefit member” and “defined benefit RSE” for the purpose of the exclusion in the RSE definition (Interpretation). That affects which RSEs must comply.
• Australian Business Register and Corporations Act 2001 (implied): The concept of an ABN is explained with reference to the Australian Business Register and notes that a company registered under the Corporations Act 2001 or a business entity carrying on an enterprise in Australia is entitled to an ABN (Item 4 definitions). That ties the obligations to existing business identifier and corporate-registration regimes.

Operationally, the instrument is a data collection standard that will be used in conjunction with prudential reporting and supervisory oversight under the SIS Act/regulations and SPS standards. The reporting fields concerning associated-party status and ABNs create interoperability with corporate law and tax identifiers. The instructions also require alignment between how insurance and reinsurance are recorded in financial statements, actuarial valuations and the RSE’s self-insurance reserve, linking this reporting with accounting law and prudential capital governance.

Where the instrument asks for amounts paid by employer-sponsors, or premiums paid from the RSE’s self-insurance reserve, those allocations interact with the fund’s financial reporting and with trust accounting rules for superannuation funds. The instrument does not create tax outcomes, but the reported flows may be used by supervisors to assess fund soundness, which has downstream legal consequences enforceable under the SIS Act and prudential standards.

Finally, the instrument’s requirement to report previous reinsurers over a rolling five-year period interacts with historical-contract and record-keeping obligations that are often specified elsewhere in corporate, trust and regulatory law. Although this template does not prescribe retention durations, the five-year look-back implies ongoing data-retention and historic contract-tracing capability to satisfy reporting.

The text provided does not include an explicit amendment history or version control log. There are no timestamps, enactment paragraphs, or schedule notes in the material presented that record original issue date, subsequent amendments, or repeal and replacement history. The single footnote marker [5] appears in the Interpretation but without an attached chronology in the excerpt provided.

Because the document cross-references external instruments (SIS Act, SIS Regulations, SPS 250, SPS 160) any meaningful amendment history will be tracked in one of two places:

• The hosting or instrument metadata, which commonly records version and effective date for reporting templates and which is not included in the text supplied. Administrators typically publish an amendments log alongside the template; absence of such a log here means users must check the source publication or regulator website for version history.
• Changes in the referenced instruments: updates to SPS 250 or statutory amendments to the SIS Act or SIS Regulations could necessitate consequential changes to definitions and reporting fields here. The instrument’s reliance on external definitions creates a hidden amendment channel , if the SIS Act or SPS 250 definitions change, that may alter the set of persons or items required to be reported even if the template’s wording remains the same.

Practical implications for practitioners: do not rely solely on the static text above for compliance history or versioning. Confirm the instrument’s effective date and any subsequent amendments on the publisher’s website or in the regulatory library where the instructions were published. If you are mapping compliance controls across reporting cycles, ensure your version-control processes capture any updates to the template or its referenced prudential standards, especially where an update may change exclusion criteria (e.g. the RSE exclusions) or definitions (e.g. associate, insurer).

Because the provided text contains no litigation history or amendment log, users should treat this excerpt as a snapshot and adopt an evidence-check step to retrieve the governing instrument’s release date, subsequent errata and any circulars or FAQs that clarify interpretation.

The extract supplied does not reference any judicial decisions, litigation or administrative determinations that interpret this reporting template or its obligations. No cases are named or cited in the text. The instrument is a technical reporting instruction and typically such instruments are litigated indirectly only when disputes arise about supervisory action taken on the basis of returns.

Given the absence of case law in the source, the practical points for advisers are:

• There is no precedent cited for disputes regarding the template’s interpretation in the material provided. Any legal challenge to enforcement action grounded in these returns would be litigated against the background SIS Act and prudential standards referenced by the template.
• Disputes likely to arise in practice concern definitions and boundary issues that the text itself crosses into statutory territory , for example, whether a counterparty is an “associate” under s.12 of the SIS Act, or whether a particular premium should be reported as paid by the RSE or by an employer-sponsor. Litigation on those points, if it occurs, will be driven by statutory interpretation of the SIS Act and not by this instruction alone.
• Source-based or evidentiary disputes may also occur where insurers and reinsurers provide inconsistent data; litigation or adjudication may focus on obligations under contract, data‑sharing arrangements, and regulatory expectations embedded in prudential standards.

In short, the text contains no litigation history and does not cite cases. Practitioners should therefore map potential enforcement or dispute scenarios to the underlying statutory and prudential instruments (SIS Act, SIS Regulations, SPS 250, SPS 160) when seeking precedential authority. Any litigation that refers to the template will necessarily engage the external instruments cited in the Interpretation.

The instrument is precise but contains numerous traps for the unwary. The following practical pitfalls are explicit in the text and will commonly generate errors or require additional internal decisions:

• Mixed temporal bases. Item 2 columns are a snapshot (“as at the end of the reporting period”), while Item 3 and parts of Item 4.2 are flow-based (“transactions that occurred during the reporting period”). Confusing snapshot versus flow data will produce internal inconsistencies and failed reconciliations. Ensure reporting processes separate end‑period positions from period movements.
• Unit inconsistencies and rounding. Counts must be whole numbers (many columns), monetary values are reported in thousands of dollars for many columns, and income protection has a monthly amount reporting requirement in Item 2 column 4. Failure to convert units correctly will distort reported amounts, particularly when transferring data from accounting systems that operate in dollars rather than thousands.
• Income protection special rules. For Item 2, income protection’s column 4 is a monthly amount (not an expected lump-sum), and Item 3 monetary columns for income protection must include the total amount paid during the reporting period, including claims in the course of payment subject to regular assessment. These semantics differ from life and TPD reporting and demand precise mapping.
• Use of maximum sum insured where estimates are unavailable. The instrument allows reporting the maximum sum insured where an estimate is not available for Item 2 column 4. That creates potential discontinuities year-on-year and may inflate apparent expected liabilities relative to other valuations unless the assumption is documented and disclosed.
• Derived items must reconcile. Items 2.2 and 3.2 are derived and must equal the totals of corresponding columns in the sub-items. Automated validation must enforce this or manual sign-off is required.
• Cluster aggregation and consistent identifiers. Item 4 requires reporting reinsurance policies aggregated by reinsurer (“a cluster”) and mandates the same reinsurer name and ABN in item 4.1 column 1 and item 4.2 column 1 to link cover types and premiums. Inconsistent naming, misspelt names or incorrect ABNs will break the linkage and hinder automated processing.
• Associate assessment. Item 4.1 requires a yes/no flag if the reinsurer is an “associate”, referencing s.12 SIS Act. Determining associate status often requires legal analysis; misclassification can have conflict-of-interest implications.
• Ceased policy reporting. Where a reinsurance policy ceased during the reporting period, the instruction requires a zero in item 4.1 columns 4-9 but still requires reporting of premiums and rebates in item 4.2 for transactions that occurred prior to cessation. It is easy to forget the zeros requirement and double-count premiums if the ceased policy is not handled consistently.
• Premium allocation rules. The instruction requires breaking out reinsurance premium paid by the RSE, by the RSE licensee, and by an employer-sponsor. Where premiums are paid from the RSE’s self-insurance reserve, the template requires the premium amount in item 4.2 column 3 and zeros in columns 2, 4, 5 and 6 where they are not relevant. This rule creates a single-column allocation for reserve-funded premiums and is a common source of classification error.
• Previous reinsurers reporting overlap. Item 5 requires listing previous reinsurers for a rolling five-year period and requires that reinsurers whose contract became previous during the reporting period be reported in both items 4 and 5. That creates a potential duplication trap unless the reporting process explicitly handles concurrent entries for “current but ceased within period” and “previous”.
• Member accounts reporting. Item 4.1 requires reporting member accounts covered by each cover type and cover limits applied to those member accounts. Mapping between policy schedules, underlying member data and the template’s “member accounts” field may be complex for large funds and will require clear rules on account counts (e.g. accounts with multiple policies, or members with multiple accounts).
• Interpretation cross-dependencies. Many definitions defer to external prudential standards (SPS 250, SPS 160) or the SIS Act. If those external instruments have alternative definitions or are updated, the meaning of terms in this template may change for reporting purposes. Maintain a watch on prudential standard updates.
• Documentation of estimates and assumptions. The instrument permits estimates in some fields but does not prescribe the method. Absent consistent documentation, estimates (especially claims value or the use of maximum sum insured) will be challenged in audits and supervisory reviews.
• Data privacy and consent. The instrument references member accounts; sharing member-level detail with insurers or in the course of producing aggregate counts may raise privacy issues. The instruction does not provide privacy guidance; ensure data-handling complies with relevant privacy and trustee duties.

Each gotcha maps to concrete actions: segregate snapshot/flow processes, embed unit conversion and validation rules, document estimation approaches clearly, and build legal checks for associate classification. The template’s prescriptive structure requires a rigorous data governance and reconciliation framework.

Complying with these instructions requires operational, actuarial and governance steps. Below is a practical compliance checklist mapped to the instrument’s main items and interpretive notes. Each step should be documented, signed off and retained in the reporting evidence pack.

1. Governance and responsibilities

   • Assign clear owners: finance, actuarial, insurance operations, legal/compliance. The RSE actuary should be engaged for valuation assumptions and claims value estimates (Interpretation).
   • Prepare a reporting timetable aligned with the “as at” and transaction-period definitions. Distinguish end-of-period snapshot extraction for Item 2 versus period transaction pulls for Items 3 and 4.2.
   • Establish review and sign-off: a senior officer should attest to reconciliations between items and financial statements.

2. Data mapping and system preparation

   • Build templates that enforce units: whole numbers for counts, thousands of dollars for specified columns, monthly amounts for income protection in Item 2 column 4. Embed automated unit conversions and reject mismatched input.
   • Create separate data extracts: an end-of-period snapshot for Item 2, a transactions extract for Item 3 and item 4.2.
   • Ensure derived totals (Item 2.2, Item 3.2) are computed automatically from sub-items and flagged for manual overrides only with documented justification.

3. Insurer and reinsurer identification

   • Collect reinsurer and insurer legal name and ABN for every policy cluster; validate ABNs against the Australian Business Register.
   • Enforce consistent naming conventions and ABN usage across item 4.1 and 4.2 to maintain linkage.
   • For each reinsurer test whether they are an “associate” under s.12 SIS Act and document the legal assessment; populate item 4.1 column 3 ‘yes’ or ‘no’ accordingly.

4. Claims data collection and valuation

   • Source claims reported and admitted counts from insurer declarations or the RSE’s claims administration system. For claims admitted but unpaid, capture the insurer’s admitted amount and expected payment timing.
   • For claims value where an estimate is unavailable, apply the instruction’s fallback: report the maximum sum insured for life and TPD, and the monthly amount for income protection (Item 2).
   • Document methodologies for expected claims value estimation, including discounting or timing assumptions if used, and retain actuarial sign-off.

5. Income protection special treatment

   • For Item 2 column 4, calculate and report the monthly liability or, if not available, the maximum monthly sum insured.
   • For Item 3, aggregate all payments made in the reporting period including ongoing payments that are subject to regular reassessment.

6. Reinsurance cluster and cover mapping

   • Aggregate policies by reinsurer to form clusters and report each cluster on a separate line in items 4.1 and 4.2.
   • For each cover type (stop-loss, catastrophe, other) map the member accounts covered and cover limits applied to those accounts; ensure these counts reconcile to membership records.
   • Where policies ceased during the reporting period, set item 4.1 columns 4-9 to zero and capture premiums/rebates for the period prior to cessation in item 4.2.

7. Premium and rebate allocation

   • Record reinsurance premium collected (item 4.2 column 2) and premium paid gross of any rebate allocated by payer: RSE (column 3), RSE licensee (column 4), employer-sponsor (column 5).
   • If premiums are paid from the RSE’s self-insurance reserve, report the premium amount in column 3 and zeros in columns 2, 4, 5 and 6 where not relevant (Item 4 instructions).
   • Capture reinsurance premium rebates regardless of how or to whom the rebate is paid (item 4.2 definition). Document flow and confirm with reinsurer.

8. Previous reinsurers

   • Maintain a rolling five-year register of reinsurers and policy types; at each reporting date extract reinsurers that provided previous reinsurance policies in the last five years and list them in Item 5.
   • For reinsurers that ceased during the period, ensure they are included in both items 4 and 5 if the reinsurance contract became a previous policy during the reporting period (Item 5 instructions).

9. Reconciliations and controls

   • Reconcile claims admitted (not yet paid) and claims paid to ledger entries for claims expense, self-insurance reserve movements and payments to/from reinsurers.
   • Reconcile premiums and reinsurance claims to cash flows and reserve ledger movements.
   • Validate totals and flag mismatches between clusters and member-account coverage (prevent double-counting where a member has multiple accounts).

10. Documentation and audit evidence

    • Archive insurer and reinsurer confirmations, premium invoices and rebate documentation, policy schedules, ABN validation results, and the legal opinion or analysis on associate status.
    • Document all assumptions used to convert estimates to the template’s required outputs and retain actuarial sign-off where applicable.

11. Privacy and data security

    • Where member account detail is used to derive counts, apply appropriate privacy controls and pseudonymisation in internal processes. The instruction does not provide privacy guidance; compliance must meet statutory privacy and trustee duties.

12. Engagement with counterparties and regulator

    • Build standard data requests for insurers/reinsurers to reduce turnaround time for claims, admissions and expected payments.
    • Establish an escalation path to regulatory contacts for clarifications on template semantics or reporting edge cases; document any guidance received.

13. Version control and compliance review

    • Maintain version control over the template, record effective dates, and incorporate changes to SPS 250, SPS 160 or the SIS Act definitions that would change reporting scope.
    • After completing the return, perform a governance review to confirm that the RSE licensee’s contemporaneous policies on self-insurance, reinsurance buying, and reserve funding are consistent with what is reported.

By following these steps an RSE licensee can operationalise the template and create an auditable trail linking policy schedules, insurer confirmations and reserve accounting to the reported items. The instrument’s precise column-level rules make automation feasible, but rigour is needed in mapping legal identifiers, payer allocations and the snapshot/flow split to avoid common classification errors.