Financial Sector (Collection of Data) (reporting standard) determination No. 95 of 2023

The Reporting Standard organises several interlocking concepts and definitions that determine when and what must be reported, and how the reported items are to be calculated and presented.

Purpose and scope. The stated purpose is prudential supervision (s 2). The scope is limited to the parent entity of a Level 2 insurance group as defined in GPS 001; the Standard applies for reporting periods ending on or after 1 July 2023 (s 3). The parent entity must ensure compliance with every requirement (s 4) and must provide APRA with the information for each reporting period (s 5).

Reporting obligation and frequency. The parent entity must submit the required information (s 5). The default reporting period is annually for each financial year of the Level 2 insurance group (s 7), with annual reports due within three months of the end of the reporting period (s 9(a)). APRA can impose a different frequency or specify periods for a particular group by written notice if it considers it necessary or desirable (s 8), and it can grant extensions in writing (s 10).

Data collected. GRS 460.1.G collects data assessing the impact of reinsurance counterparty failure on the Level 2 group’s capital base and each component of the prescribed capital amount. The primary items to be reported include: total impact on capital base; total impact on Insurance Risk Charge; Insurance Concentration Risk Charge (ICRC); Asset Risk Charge (after aggregation formula); Asset Concentration Risk Charge (ACRC); Operational Risk Charge; and total impact on prescribed capital amount (the aggregation of impacts across components after applying GPS 110 aggregation benefits). The tables specify column-level constraints: e.g. amounts in column 7 (total impact on capital base) must be equal to or less than zero; columns 8, 9 and 12 must be equal to or greater than zero; column 13 must be equal to or less than the sum of columns 8-12 after aggregation benefit adjustments (Table 1 and Table 2 instructions).

Counterparty identification. APRA maintains a reinsurer identifier list on its website; Table 1 must be used where the counterparty appears on that list (Table 1 instructions, Reinsurer identifier section). Table 2 is for unassigned counterparties or Lloyd’s syndicates (Table 2 instructions). For Lloyd’s syndicates the identifier value is 'LLO' and the name is reported as Lloyds XXXX (Table 2). Certain fields in Table 1 are to be left blank (columns 2-6), reflecting that identifier-driven reporting requires less textual detail.

Trigger for inclusion. A Level 2 group need only report individual counterparties where the failure of that counterparty results in a five per cent change in capital coverage of the Level 2 insurance group relative to capital coverage at the end of the financial year (Specific instructions). The Standard defines failure for reporting purposes as a situation where the counterparty no longer meets its obligations to the Level 2 group, meaning no recovery from on-balance-sheet reinsurance assets and the reinsurer is not replaced on any previous or current programmes (Specific instructions).

Calculation and cross-references. Several reported items are to be calculated or understood in terms of other Prudential Standards and reporting standards. For example, capital base is determined under GPS 112 and prescribed capital amount under GPS 110 (see definition "Capital coverage" under C). Asset Risk Charge and ACRC reference GPS 114 and GPS 117 respectively; Insurance Risk Charge and ICRC reference GPS 115 and GPS 116; Operational Risk Charge references GPS 118; net outstanding claims liabilities and net premiums liabilities are to be considered under AASB 17 and GPS 340 (see definitions OCL surplus/deficit and PL surplus/deficit). The Standard permits the use of simplifying assumptions provided they do not have material impact (several table notes).

Controls and authorisation. All information must be subject to systems, processes and controls developed by the Level 2 group for internal review and authorisation; Boards and senior management hold responsibility for ensuring an appropriate set of policies and procedures for authorisation (s 11). Electronic submissions require digital signatures using certificates acceptable to APRA (s 13); agents must be authorised and parent entities must retain copies of agent-provided submissions (ss 14-15).

Audit posture. Under GPS 310, the Group Auditor is not ordinarily required to provide a limited assurance review for information provided under this Reporting Standard (s 12). Insurance (exemption) determination No. 1 of 2023 exempts Appointed Auditors of general insurers from auditing or certifying GRS 460.1 data (Audit matters). APRA retains the power under GPS 310 to require special purpose reviews of the systems, processes and controls, or the data itself (Audit matters).

Discretion and variation. APRA retains a series of discretions: to change reporting periods (s 8), to vary reporting requirements for a particular Level 2 insurance group (s 16), to specify submission methods (s 6(b)), to accept digital certificates (s 13), and to require special audits or reviews under GPS 310 (Audit matters). APRA must exercise powers or discretions in writing (s 20).

Supplementary and technical conventions. Units are whole Australian dollars; foreign currency amounts are to be converted to AUD in accordance with the relevant accounting standard (multiple Units of measurement paragraphs). The Standard requires underlying calculations and assumptions be made available to the APRA responsible supervisor upon request (Supplementary information).

Together these interlocking concepts create a structured requirement: identify material reinsurer exposures (>=5% change in capital coverage), calculate the impacts across defined capital components using cross-referenced prudential and accounting standards, submit standardised electronic tables with specified data validation rules, and maintain robust internal controls and authorised sign-off.

Directly affected parties. The primary, express obligation falls on the parent entity of a Level 2 insurance group (s 3-5). The parent entity must ensure compliance with each requirement (s 4), provide the required information for each reporting period (s 5), and is responsible for internal systems, processes and controls for review and authorisation (s 11).

Entities within the group. The Standard requires reporting on a Level 2 insurance group basis (Reporting basis). This compels the parent entity to coordinate across subsidiaries and branches within the Level 2 group to collect data about reinsurance exposures, domicile information, insurance liabilities (OCL and PL), capital base and prescribed capital components (definitions and table instructions). Group-level actuarial, capital, treasury and finance teams will be materially involved in preparing the data.

Agents and auditors. A parent entity may use an agent to submit the information, but the parent must obtain and retain a copy of the completed information (s 14). Submissions made electronically by an officer or agent must be digitally signed using a digital certificate acceptable to APRA (s 13). The Group Auditor is referenced in relation to assurance obligations , under GPS 310 the Group Auditor is not ordinarily required to provide limited assurance for information provided under this Reporting Standard (s 12). However, APRA may require special purpose reviews under GPS 310, and Insurance (exemption) determination No. 1 of 2023 removes the Appointed Auditor’s obligation for general insurers in relation to the related GRS 460.1 (Audit matters). Therefore internal audit, outsourced agents, and external auditors are affected by the assurance posture and by possible APRA directions to undertake special reviews.

Board and senior management. s 11 explicitly places responsibility on the Board and senior management of the parent entity to ensure that an appropriate set of policies and procedures for authorisation of information submitted to APRA is in place. That means governance-level involvement in setting controls, delegations and authorisation procedures.

Primary decision-makers and signatories. The reporting standard specifies that an officer or agent who submits the information must be authorised by either the Principal Executive Officer or the Chief Financial Officer of the parent entity (s 15). These two roles therefore have explicit decision and authorisation responsibilities.

Regulatory bodies. APRA is the recipient and administrator of the reporting requirement. APRA has the power to change reporting frequency or specify alternative reporting periods for particular groups by written notice (s 8) and may vary reporting requirements for a particular group by written notice (s 16). APRA determines acceptable electronic submission methods (s 6) and acceptable digital certificates (s 13). APRA can grant extensions in writing (s 10) and can require special purpose reviews under GPS 310 (Audit matters). APRA’s reinsurer identifier list is hosted on its website and is used by reporting entities for identifier values (Reinsurer identifier section). The Australian Prudential Regulation Authority is defined in the Interpretation (s 18).

Insurers outside Level 2. The Standard mentions GRS 460.1 for general insurers and an exemption determination affecting Appointed Auditors of general insurers (Audit matters). Although the Standard itself applies to Level 2 parent entities, general insurers and their auditors are affected by related instruments and exemptions referenced in the Standard.

Who bears costs. The parent entity and the Level 2 insurance group bear the compliance costs: staff time to gather and compute impacts, build and maintain systems, implement digital signature processes, provide supporting documentation and calculations to APRA on request, and respond to possible APRA special reviews. If an agent is engaged to prepare or submit the data, the parent entity still bears the obligation to obtain and retain copies (s 14) and to ensure appropriate authorisation (s 15). Boards and senior management will have governance costs associated with the required policies and procedures (s 11).

Who decides. APRA retains discretion to change reporting schedules, methods and requirements (ss 6, 8, 16), to accept digital certificates (s 13) and to require special audits (Audit matters). Inside the group, the Principal Executive Officer and Chief Financial Officer decide who is authorised to submit (s 15), and Boards and senior management decide on internal policies and controls (s 11).

Behavioural consequences. Reporting entities must identify and model scenarios where a reinsurer’s failure produces a five per cent change in capital coverage; they must adopt internal procedures to calculate impacts across capital charge components as defined by other prudential standards (GPS 110, 112, 114-118, 340); and they must maintain documentation and audit trails that enable APRA review. That will influence capital modelling, counterparty monitoring and risk management practices at group level.

Duties

• Provide required information to APRA: The parent entity must provide APRA with the information required by the Reporting Standard for each reporting period (s 5). This includes completing GRS 460.1.G and submitting it in the prescribed electronic format or other APRA-notified method (s 6).

• Ensure compliance across the group: The parent entity is required to ensure that each requirement in the Reporting Standard is complied with (s 4).

• Apply reporting thresholds and calculation rules: Report individual counterparties where the failure would result in a five per cent change in capital coverage compared to year-end capital coverage (Specific instructions). For each reported counterparty, calculate and report impacts on capital base and each prescribed capital component in the specified columns of Table 1 or Table 2, with the required sign and range constraints (Tables 1 and 2 columns 7-13).

• Maintain quality control systems: All information provided must be subject to systems, processes and controls developed by the Level 2 insurance group for internal review and authorisation; Boards and senior management are responsible for ensuring appropriate policies and procedures are in place (s 11).

• Authorisation and signature: Electronic submissions must be digitally signed by the officer or agent using a digital certificate acceptable to APRA (s 13). Submitters must be authorised by the Principal Executive Officer or Chief Financial Officer (s 15).

• Retain agent-submitted copies: If an agent submits on behalf of the parent entity, the parent must obtain a copy of the completed information provided to APRA and retain it (s 14).

• Make underlying calculations available: The Level 2 insurance group must ensure any underlying calculations and assumptions used to complete GRS 460.1.G are made available to APRA upon request (Supplementary information).

• Observe units and currency conversion: Report amounts in whole Australian dollars and convert foreign currency amounts in accordance with the relevant accounting standard (Units of measurement).

• Ensure unique row combinations: Any specific combination of values in a table must not appear on more than one row in that table when reported (Reporting tables).

Rights and APRA discretions (as framed by the Standard)

• APRA’s discretion to vary: APRA may change reporting periods for a particular group, or specify reporting periods, by written notice if it considers it necessary or desirable (s 8). APRA may vary the reporting requirements for a particular Level 2 insurance group by written notice (s 16).

• APRA may grant extensions: APRA may grant an extension of a due date in writing (s 10).

• Submission method choice constrained by APRA: Information must be submitted electronically via APRA’s website or by a method notified by APRA (s 6). APRA decides what other methods may be acceptable (s 6(b)).

• Audit and assurance discretion: Under GPS 310 the Group Auditor is ordinarily not required to provide a limited assurance review in relation to information provided under this Standard (s 12). Insurance (exemption) determination No. 1 of 2023 exempts Appointed Auditors of general insurers from auditing or certifying GRS 460.1 data, but APRA may require special purpose reviews of systems and data under GPS 310 (Audit matters).

Operational duties implied by cross-references

• Calculation duties referencing other prudential standards: The reported items must be calculated in light of definitions and methodologies in GPS 110 (aggregation benefits and prescribed capital amount), GPS 112 (capital base), GPS 114-118 (various capital charge calculations), and GPS 340 and AASB 17 for insurance valuation impacts (definitions and table instructions). Practically, this imposes duties on the Level 2 group to align their calculations with those standards.

Execution and communication duties

• Written exercise of power: Where the Reporting Standard provides for APRA to exercise a power or discretion, it must be exercised in writing (s 20). Notices in relation to reporting period changes, variations, or extensions therefore will be in writing (ss 8, 10, 16, 20).

Constraints and validation duties encoded in tables

• Table field constraints: The reporting tables impose sign constraints (e.g. column 7 amounts must be equal to or less than zero) and relational constraints (column 13 capped by aggregated sum of columns 8-12 after aggregation benefits). Entities must validate their submissions against these constraints to ensure acceptance and consistency.

No explicit statutory penalties in the text

• The Standard sets out obligations, discretions and audit arrangements, but does not itself enumerate civil or criminal penalties or enforcement sanctions within the text provided. It does, however, establish APRA procedural powers (notice, variation, special-purpose review) and cross-references to GPS 310, which governs audit and related matters.

In short, the core duties are to identify material counterparty failures (>=5% capital coverage impact), calculate component impacts in accordance with cross-referenced standards, submit standardised tables electronically with appropriate sign-off and digital signature, maintain internal controls and retain submission copies, and make supporting calculations available to APRA on request. APRA retains balancing rights to vary requirements, impose different reporting cadences and require special reviews, and to accept or specify submission methods.

Express enforcement mechanisms provided in the text are administrative and supervisory rather than criminal or monetary penalties spelled out within this Reporting Standard. The instrument sets out mechanisms APRA may use to enforce compliance or to obtain assurance, and it cross-references GPS 310 for audit-related powers.

APRA notices and variations. APRA may direct changes in reporting periods or specify reporting periods for a particular Level 2 insurance group by written notice if it considers it necessary or desirable (s 8). APRA may vary the reporting requirements of this Reporting Standard in relation to a particular Level 2 insurance group by written notice (s 16). These notices are instruments APRA can use to compel compliance with a modified set of obligations, and the Standard requires such powers or discretions to be exercised in writing (s 20).

Due-date control and extensions. APRA sets due dates, and the Standard prescribes the default due date (annual within three months of year‑end) (s 9). APRA may in writing grant an extension of a due date (s 10). Failure to file by the statutory due date without an extension would ordinarily expose an entity to APRA follow-up action, although the Standard itself does not set out fines or civil penalties within the text provided.

Audit and information assurance. The Standard places the Reporting Standard within the GPS 310 audit framework. It states that the Group Auditor is not ordinarily required to provide a limited assurance review in relation to information provided by the parent entity under this Reporting Standard (s 12). Insurance (exemption) determination No. 1 of 2023 exempts Appointed Auditors of general insurers from auditing or certifying GRS 460.1 data; however, APRA retains the power under GPS 310 to require the Appointed Auditor or the Group Auditor to undertake a special purpose review of systems, processes and controls surrounding the completion of GRS 460.1 and GRS 460.1.G, or the data itself (Audit matters). The exercise of this audit power is an enforcement and verification mechanism APRA can deploy to examine compliance and underlying controls.

Information requests and supervisory powers. The Standard requires that the Level 2 insurance group ensure underlying calculations and assumptions used to complete GRS 460.1.G are made available to the APRA responsible supervisor upon request (Supplementary information). The requirement to provide supporting documentation on request is a supervisory instrument APRA may use to verify reported numbers and to escalate matters if discrepancies are found.

Administrative handling of agents. The Standard requires the parent entity to obtain and retain a completed copy of any submission made by an agent (s 14) and to ensure appropriate authorisation of submitters (s 15). Failure to maintain such records may trigger APRA queries or special reviews under GPS 310.

Limits of enforcement described in the text. The Reporting Standard itself does not state fines, licensing consequences, criminal liabilities or civil penalty provisions. It therefore relies on APRA’s administrative powers (notice, variation, audit requests, and supervisory review) and cross-references to broader supervisory frameworks (GPS 310 and the APRA Act and Insurance Act as definitional references in s 18). The text does not specify timeframes or processes for APRA escalation beyond the written notice and special review mechanisms noted above.

Implication for entities. Given the absence of enumerated monetary penalties in the Standard text, enforcement will likely proceed via APRA supervisory actions: requirement to correct or resubmit data, invocation of GPS 310 special-purpose reviews, variation of reporting periods or requirements, and engagement with the responsible supervisor requesting underlying calculations. Organisations should therefore treat APRA’s audit/review powers and notice authorities as the principal enforcement levers and should prioritise readiness for reviews and data validation.

In summary, the Standard establishes administrative enforcement tools: written notices to change or vary reporting, written extensions, and APRA-directed special-purpose reviews under GPS 310 supplemented by the requirement to furnish underlying calculations on request. The instrument itself does not, in the provided text, set out defined civil or criminal penalties.

The Reporting Standard explicitly cross-references a number of Prudential Standards, other reporting standards, accounting standards and statutory instruments. These cross-references create substantive interdependencies for calculations, definitions and assurance arrangements.

GPS 001 (Definitions). The Standard applies to the parent entity of a Level 2 insurance group as defined in GPS 001 (s 3) and states that, unless the contrary intention appears, words and expressions have the meanings given to them in GPS 001 (s 18(a)). The Level 2 insurance group definition used to determine who must report is located in Attachment D of GPS 001 (s 18).

GPS 110 and GPS 112 (Capital measurement and prescribed capital). The Standard uses capital base and prescribed capital amount concepts. The definition "Capital coverage" refers to capital base as determined under GPS 112 and prescribed capital amount under GPS 110 (C: Capital coverage). The instructions for "Total impact on prescribed capital amount" require applying the aggregation benefit in accordance with GPS 110. That means reported impacts must be computed using GPS 110 aggregation rules and GPS 112 capital base definitions; consequently firms must reconcile GRS 460.1.G calculations with their GPS 110/112 capital models.

GPS 114-118 (Capital charge calculations). The Standard refers to Asset Risk Charge (GPS 114), Asset Concentration Risk Charge (GPS 117), Insurance Risk Charge (GPS 115), Insurance Concentration Risk Charge (GPS 116), and Operational Risk Charge (GPS 118) in the definitions and in the table descriptions (C, I, O). The table requires reporting the change in those charges due to reinsurer failure and in some cases the amount after aggregation (Asset Risk Charge after aggregation formula). Entities must therefore compute changes to each relevant risk charge using the methodologies in those Prudential Standards, or apply reasonable simplifying assumptions documented in line with the Standard’s allowance for simplifying assumptions where not material.

GPS 340 and AASB 17 (Insurance liability valuation). The definitions "OCL surplus/deficit" and "PL surplus/deficit" refer directly to net liabilities determined under AASB 17 and net outstanding claims liabilities determined under GPS 340. The calculation of capital base impacts and insurance risk charges requires consideration of changes to net outstanding claims provisions and net premium liabilities as determined under AASB 17 and GPS 340.

GRS 114.0 and GRS 114.0.G (Asset Risk Charge reporting). The Standard notes that a Level 2 group may estimate Asset Risk Charge impact by applying percentages from aggregated risk charge components on Reporting Standard GRS 114.0 or GRS 114.0.G (T: Total impact on Asset Risk Charge). This ties the data requirement to other APRA reporting templates and aggregation conventions.

GPS 310 (Audit and Related Matters). The Standard explicitly references GPS 310 in the Quality control and Audit matters sections. s 12 states the Group Auditor is not ordinarily required to provide a limited assurance review; Audit matters reiterate this and state APRA may nevertheless exercise its power under GPS 310 to require special purpose reviews. This places the reporting standard within the broader audit and assurance framework and means entities must be familiar with GPS 310’s provisions for special-purpose reviews and APRA’s authority to direct auditors.

Insurance Act 1973 and Corporations Act 2001. The Interpretation section defines Appointed Auditor with reference to the Insurance Act (s 18), and defines "financial year" in terms of the Corporations Act 2001 (s 18). The Standard also notes "general insurer" as authorised under the Insurance Act (s 18). This links definitions and assurance responsibilities to broader statutory frameworks.

Insurance (exemption) determination No. 1 of 2023. The Audit matters section notes that this exemption determination removes an Appointed Auditor’s obligation to audit or provide certificates in relation to information provided under GRS 460.1 for general insurers. That exemption is a legislative instrument and directly interacts with the auditing expectations for related reporting.

APRA website lists and identifiers. The Standard depends on APRA-maintained lists: the reinsurer identifier list and country code lists (definitions under Reinsurer identifier and Country code). Use of these lists is mandatory for Table 1 reporting and for domicile reporting (C and Reinsurer identifier).

Accounting standards. Units and currency conversion must be performed "in accordance with the relevant accounting standard" (Units of measurement). The Standard also explicitly references AASB 17 for net liability comparisons (definitions). This requires alignment with Australian accounting frameworks when preparing GRS 460.1.G submissions.

Implications of these interactions. Because the Standard requires calculations that draw on multiple prudential and accounting standards, a reporting entity must co‑ordinate across compliance, actuarial, finance and legal functions to ensure methodology alignment. The requirement to use GPS 110 aggregation benefits, GPS 114-118 charge methodologies and GPS 340/AASB 17 liability measures means the reporting data are not standalone figures but must be consistent with the entity’s capital modelling and financial statements. The audit posture under GPS 310 and the Insurance exemption determination mean that while routine external assurance may not be mandated, APRA still retains the right to demand special reviews and to audit systems and controls.

Limitations. The Reporting Standard does not itself supersede or replace the substantive obligations in the referenced Prudential Standards or Acts; rather it draws upon them to define what must be reported. Where an entity needs to interpret methods or apply judgement (for example in using simplifying assumptions), it must do so in a manner that is consistent with the referenced standards and be prepared to justify those choices to APRA upon request.

Commencement and applicability. The Reporting Standard applies for reporting periods ending on or after 1 July 2023 (s 3). That is the commencement date for applicability of these reporting obligations to the parent entity of Level 2 insurance groups.

Revocation and transition. Section 17 addresses transition: a parent entity of a Level 2 insurance group must report under the old reporting standard in respect of a transitional reporting period. The Standard defines "old reporting standard" as the reporting standard revoked in the determination making this Reporting Standard, and "transitional reporting period" as a reporting period under the old reporting standard that ended before 1 July 2023 and for which the parent entity was required under the old standard to report by a date on or after the date of revocation (s 17). The Note to s 17 clarifies that if the due date under the old standard fell before the date of revocation, the parent entity is still required to provide any overdue reporting documents in accordance with the old reporting standard.

Insurance (exemption) determination No. 1 of 2023. The Audit matters section notes this instrument: it exempts the Appointed Auditor of a general insurer from auditing or certifying information provided under GRS 460.1 (Audit matters). That exemption appears to have been made concurrent with the new reporting arrangements, and it affects the audit posture for related reporting. The text does not provide the date of that exemption determination within the material presented, but its existence is noted as relevant.

No further amendments recorded in the provided text. The Standard cross-references other prudential standards "as in force from time to time" (s 19), which means that changes to GPS 110, GPS 112, GPS 114-118, GPS 340, GPS 310, or GPS 001 will feed into how this Reporting Standard is operationalised, without the need to amend GRS 460.1.G itself. Section 19: "Unless the contrary intention appears, a reference to an Act, Prudential Standard, Reporting Standard, Australian Accounting or Auditing Standard is a reference to the instrument as in force from time to time."

APRA discretions to vary. The Standard grants APRA the power to vary reporting requirements by written notice for a particular Level 2 insurance group (s 16). That provision enables APRA to make group-specific modifications without formally amending the Standard, providing a supervisory lever to adjust obligations case by case.

Implications for change management. Given these arrangements, the most relevant amendment-related operational requirements for reporting entities are:

• Monitor changes to the referenced Prudential Standards and accounting standards, because those changes can alter the calculation basis for items reported under GRS 460.1.G by virtue of s 19.

• Be prepared for APRA to alter reporting periods, frequency or data requirements for particular groups by notice (ss 8, 16) and to act accordingly.

• For transitional reporting periods, ensure that the old reporting standard is followed where the reporting obligation under the old standard remains outstanding after revocation (s 17).

No historical legislative amendment log, version numbers or prior standard text are provided within the material supplied beyond the transitional rule in s 17 and the reference to the old standard being revoked in the determination making this Reporting Standard. Entities should consult APRA’s formal determination instruments and website for the formal amendment and instrument history.

The text of the Reporting Standard contains no references to decided cases, litigation, judicial review proceedings, or tribunal matters. Neither are there citations to court judgments nor a history of successful challenges recorded within the supplied text. The document lists only statutory and supervisory instruments and explanatory instructions; it does not report any litigation outcomes.

Potential litigation risk areas identified by the Standard (based on the text). Although no cases are named, the Standard contains features that commonly give rise to disputes or supervisory escalation in other contexts. These are not litigation outcomes but areas where disagreements could arise and, if contested, could surface in administrative review or judicial proceedings:

• Interpretation of what constitutes a "failure" for reporting purposes. The Standard defines "failure" as the counterparty no longer meeting obligations such that the Level 2 group makes no recovery from on-balance-sheet reinsurance assets and the reinsurer is not replaced (Specific instructions). Disputes could arise about whether circumstances amount to "no recovery" or whether replacement arrangements nullify the trigger for reporting.

• Whether simplifying assumptions are "material" in their impact. The Standard permits the use of simplifying assumptions where those assumptions do not have a material impact on capital coverage outcomes (e.g. T entries and Specific instructions). A dispute could concern what is material and whether an entity’s assumptions were reasonable.

• APRA discretion to vary reporting and require special reviews. Section 8 and s 16 give APRA the power to change reporting periods or vary reporting requirements by written notice. Disagreement could arise about whether APRA’s exercise of discretion was lawful, reasonable or procedurally fair, potentially giving rise to administrative law challenges (judicial review) of APRA notices, although no cases are cited.

• Adequacy of internal systems, processes and controls. Section 11 places responsibility on Boards and senior management for having appropriate policies and procedures. APRA may, under GPS 310, require special reviews of systems and controls. Disputes could arise over the adequacy or interpretation of those systems or the findings of an APRA-ordered review.

• Data quality and submission constraints. The tables impose precise validation constraints (e.g., column sign constraints, uniqueness of row combinations). Disagreement could arise between APRA and a reporting group about the correct interpretation of those constraints or the correct mapping to APRA lists, potentially escalating to formal dispute resolution if APRA takes supervisory action.

Observations on absence of reported litigation. The supplied text does not identify any litigation history challenging the Standard itself or its predecessor. It provides procedural and supervisory machinery intended to be implemented administratively rather than litigiously. Where disputes arise, the appropriate procedural channels will include engagement with APRA’s supervisory team, possible exercise of APRA’s formal powers under the APRA Act and related statutes, and finally any available administrative or judicial review routes; none of these are described by the Standard itself.

Practical implication. Because the Standard requires technical modelling cross-referenced to other prudential standards and leaves some judgement (materiality of simplifying assumptions; the triggers for failure) to the reporting entity and to APRA’s supervisory interpretation, entities should expect the potential for supervisory scrutiny and should document rationale for key judgements to reduce the likelihood of contested findings.

The Reporting Standard contains multiple specific requirements and interdependencies where small oversights can cause reporting errors, non-compliance or supervisory follow-up. The following points collate concrete operational "gotchas" drawn from the text.

1. Reporting threshold is a 5% capital coverage change, not dollar-based. The Standard requires reporting only where the failure of a counterparty results in a five per cent change in capital coverage of the Level 2 insurance group compared to capital coverage at year-end (Specific instructions). Firms that rely on materiality thresholds expressed in dollar terms rather than percentage capital coverage may mis-identify which counterparties require reporting.

2. Distinction between Table 1 and Table 2 inputs. Use Table 1 only where the counterparty is on APRA’s reinsurer identifier list (Table 1 instructions and Reinsurer identifier), and Table 2 for unassigned counterparties or Lloyd’s syndicates (Table 2 instructions). Table 1 requires leaving several columns blank (2-6) and using the reinsurer identifier; Table 2 requires free-text names and domicile codes. Misclassifying a counterparty between tables will produce invalid submissions.

3. Column sign constraints and relational caps. Several columns have explicit sign constraints: column 7 (total impact on capital base) must be equal to or less than zero; columns 8, 9 and 12 must be equal to or greater than zero, while columns 10 and 11 permit positive or negative amounts for increases or decreases respectively (Table 1 & 2 instructions). Column 13 is constrained to be equal to or less than the sum of columns 8-12 after applying aggregation benefits. Failure to enforce these constraints will lead to validation failures or queries.

4. Unique row combinations. The Reporting tables stipulate that any specific combination of values in a table must not appear on more than one row when reported (Reporting tables). Duplicate rows or repeated combinations will likely be rejected or queried.

5. Digital certificate acceptance is APRA-determined. Submissions must be digitally signed using a digital certificate acceptable to APRA (s 13). Entities must ensure their digital certificate meets APRA’s acceptance criteria before submitting; failure to do so could invalidate the submission.

6. Authorisation must be by PEO or CFO. The person submitting must be authorised by the Principal Executive Officer or the Chief Financial Officer (s 15). Lack of documented authorisation by one of these two roles will breach the Standard’s sign-off requirements.

7. Agent submissions do not remove parent obligations. If an agent submits, the parent entity must obtain and retain a copy of the completed information (s 14). Relying on an agent without written arrangements to deliver and retain the completed submission places the parent entity in breach.

8. Boards and senior management are accountable for policies. s 11 assigns responsibility to Board and senior management to ensure appropriate authorisation policies and procedures exist. Treating the requirement as purely administrative without Board-level oversight can create governance exposure.

9. Simplifying assumptions permitted only if not material. Although the Standard allows simplifying assumptions, they must not have a material impact on capital coverage outcomes (multiple table notes). Assumptions should therefore be conservative, documented and stress-tested to demonstrate non-materiality.

10. Currency conversion must follow accounting standards. Units are whole Australian dollars, with foreign currency converted “in accordance with the relevant accounting standard” (Units of measurement). Using an inconsistent or incorrect exchange rate methodology relative to the entity’s financial statements can cause reconciliation issues.

11. Underlying calculations must be available to APRA. The Level 2 group must ensure underlying calculations and assumptions used to complete GRS 460.1.G are made available to the APRA responsible supervisor upon request (Supplementary information). Failure to retain or produce these workpapers invites APRA special-purpose review under GPS 310.

12. Audit expectations are muted but APRA can require reviews. The Group Auditor is not ordinarily required to provide limited assurance (s 12), and there is an exemption for Appointed Auditors of general insurers (Audit matters). However, APRA may still require an auditor special-purpose review under GPS 310 (Audit matters). Entities should not assume complete absence of external assurance.

13. APRA variations and notices are written. APRA’s power to change reporting periods, impose variations, or grant extensions is exercised by written notice (ss 8, 10, 16, 20). Be attentive to written communications from APRA; oral directions have no standing under the Standard.

14. Transitional reporting under the old standard. Transitional reporting periods that ended before 1 July 2023 may need reporting under the revoked old standard if due after revocation (s 17). Entities must track legacy reporting due dates carefully during transition.

15. The Standard ties into many other Prudential Standards. Calculating the impact on capital base and each prescribed capital component requires applying GPS 112, GPS 110, GPS 114-118 and GPS 340/AASB 17. Lack of coordination between the capital, actuarial and accounting functions risks inconsistent numbers and APRA queries.

16. Use of APRA lists and country codes. The Standard requires use of APRA’s reinsurer identifier list and ISO 3166 country codes (Reinsurer identifier; Country code). Using non-standard names, casing or alternate country codes will create mapping errors.

17. Rows must not be duplicated across reporting periods. The Reporting basis requires reporting at year-end balances for each reporting period on a Level 2 insurance group basis. Cross-period reconciliation and version control of reported tables is necessary.

These gotchas are practical and specific to the Standard’s text. Entities should build validation and governance checks to detect each of the above before submission.

This section sets out an operational checklist and recommended steps to implement the Reporting Standard’s requirements, strictly referencing the obligations and constraints present in the text.

1. Determine applicability and reporting scope

   • Confirm that the entity is the parent entity of a Level 2 insurance group as defined in GPS 001 (s 3 and s 18). If applicable, the parent entity is the reporting entity and must ensure compliance (s 4).
   • Confirm reporting periods that apply (annual by default for each financial year,s 7; annual due within three months of year‑end,s 9(a)). Monitor for APRA notices changing reporting periods for your group (s 8).

2. Governance and policies

   • Ensure Board and senior management adopt and approve policies and procedures for internal review and authorisation of information to be submitted (s 11). Document the internal control framework, authorisation delegations, sign-off processes and retention policies.
   • Nominate and document who may authorise submitters: the Principal Executive Officer and the Chief Financial Officer (s 15). Maintain formal delegations showing that submitters are authorised by one of those officers.

3. Data mapping and identification

   • Obtain APRA’s reinsurer identifier list from APRA’s website and map your reinsurance counterparties to the identifier list for Table 1 reporting where applicable (Reinsurer identifier).
   • For counterparties not on the list or Lloyd’s syndicates, prepare to use Table 2 and its conventions (Unassigned or LLO) including the required free-text name fields and correct domicile codes (Table 2 instructions).
   • Ensure unique combinations: do not report any specific combination of values more than once in a table (Reporting tables).

4. Threshold testing

   • Identify counterparties where a failure would result in a five per cent change in the group’s capital coverage compared to capital coverage at the end of the financial year (Specific instructions). This requires a capital coverage baseline (capital base divided by prescribed capital amount) and scenario modelling of reinsurer failure impacts.

5. Calculate impacts consistently with related standards

   • Compute capital base as per GPS 112 and prescribed capital amount as per GPS 110; determine Aggregation Benefit application per GPS 110 for column 13 limitations (C: Capital coverage; T: Total impact on prescribed capital amount).
   • Calculate Asset Risk Charge, Asset Concentration Risk Charge, Insurance Risk Charge, Insurance Concentration Risk Charge, and Operational Risk Charge using GPS 114, 117, 115, 116, and 118 methodologies respectively (definitions under C, I, O). For Asset Risk Charge after aggregation formula, apply GPS 114 aggregation conventions (T).
   • For impacts on insurance liabilities, consider changes in OCL surplus/deficit and PL surplus/deficit as measured under AASB 17 and GPS 340 (OCL/PL definitions).
   • If using estimating shortcuts for Asset Risk Charge impact, document the method (for example applying percentage allocations from GRS 114.0 or GRS 114.0.G) and ensure assumptions do not materially affect capital coverage (T).

6. Document and test simplifying assumptions

   • Where simplifying assumptions are used, document them and perform sensitivity analysis to demonstrate they are not material to capital coverage outcomes (multiple table notes; Specific instructions).
   • Retain all workpapers and evidence to justify the non-materiality determination, as APRA may request underlying calculations and assumptions (Supplementary information).

7. Units, currency and validation

   • Report amounts in whole Australian dollars (AUD) and convert foreign currency amounts in accordance with applicable accounting standards (Units of measurement).
   • Ensure numeric sign conventions and column constraints are enforced: column 7 ≤ 0, columns 8, 9, 12 ≥ 0, columns 10 and 11 may be positive or negative per description, and column 13 ≤ sum(columns 8-12) after aggregation benefit (Table 1 and Table 2 specifications).
   • Ensure no duplicate rows, and that each row’s field values conform to the "Valid values" in the table definitions.

8. Systems, processes and controls

   • Build electronic templates aligned with APRA’s electronic submission format available via APRA’s website (s 6). Validate that the template enforces the sign and relational rules.
   • Implement version control for tables and a reconciliation between reported lines and source systems (actuarial reports, general ledger, reinsurance ledgers).
   • Implement controls to capture submission date/time, authorising officer (PEO/CFO) authorisation evidence, and digital signature metadata.

9. Digital signature and submission

   • Obtain a digital certificate acceptable to APRA and ensure the submitting officer or agent uses it to digitally sign the submission (s 13). Test certificate compatibility with APRA’s electronic submission portal.
   • Ensure the electronic submission method follows APRA’s technical requirements; APRA may notify alternative methods (s 6(b)).

10. Agent use and retention

    • If an agent prepares or submits the report, contractually require the agent to provide the parent entity with a completed copy and retain that copy (s 14). Confirm retention procedures (location, access, retention period) internally, noting the Standard does not specify a minimum retention period.

11. Authorisation and record-keeping

    • Before submission, obtain documented authorisation from the Principal Executive Officer or Chief Financial Officer for the named submitter (s 15). Maintain signed authorisation records linked to each submission.
    • Retain supporting calculations and assumptions in a manner that enables prompt production to the APRA responsible supervisor (Supplementary information).

12. Audit readiness and interaction with auditors

    • Understand the GPS 310 context: the Group Auditor is not ordinarily required to provide limited assurance (s 12), and there is an exemption for Appointed Auditors in relation to GRS 460.1 for general insurers (Audit matters). Nevertheless, build records to support a possible APRA-required special-purpose review under GPS 310 (Audit matters).
    • Engage internal audit to test controls around data aggregation, assumption setting and sign-off prior to initial submission.

13. Monitor APRA notices and maintain flexibility

    • Track written notices from APRA that might vary reporting periods, methods or other requirements (ss 8, 16, 20). Ensure the compliance team maintains a register of APRA communications and adjusts reporting calendars accordingly.
    • If APRA grants an extension, retain the written notice and operate to the new due date specified (s 10).

14. Reconciliation and post-submission actions

    • Reconcile submitted numbers to year-end capital reporting, financial statements and other APRA returns (GPS 110/112/340 related filings).
    • Monitor for APRA follow-up queries, and be prepared to provide underlying calculations and to explain simplifying assumptions and materiality judgements.

15. Training and documentation

    • Train finance, actuarial and compliance staff on the thresholds (5% capital coverage change), table mappings (Table 1 vs Table 2), sign conventions, and APRA identifier usage.
    • Maintain an internal guidance document referencing the exact sections of the Reporting Standard (ss 5, 6, 7-10, 11-16, Supplementary information) and an index of where supporting evidence lives.

By following the above checklist , which maps directly to the Standard’s sections and table instructions , a Level 2 group’s parent entity will align its processes with the Reporting Standard’s mechanical and governance requirements, and will be prepared to respond promptly to APRA requests or notices.