The Standard organises reporting around a short list of legal and actuarial concepts and ties those into reporting tables. Key concepts are defined in the Interpretation and Definitions sections and in the alphabetised glossary in the General instructions. The principal concepts are:

• Level 2 insurance group and parent entity: the reporting entity is the parent entity of a Level 2 insurance group as defined in GPS 001 (para 3). The parent entity is responsible for compliance with every requirement in the Standard (para 3).

• Premiums liabilities (PL) components: The Standard breaks PL into a set of granular items used in GPS 340 (and mapped to an AASB basis where applicable): gross PL central estimate (excluding and including CHE and PAE), expected future reinsurance costs for current and future arrangements, commissions, reinsurance commissions, claims handling expenses (CHE), policy administration expenses (PAE), diversified and stand‑alone risk margins, non‑reinsurance recoveries and expected reinsurance recoveries. These definitions are located throughout the Definitions alphabet (G, E, C, N etc.) and are referenced in the columns of Tables 2-5 and 8-9.

• Insurance Risk Charge calculation: The PL Insurance Risk Charge is explicitly defined (P section). For GPS 340 basis: PL Insurance Risk Charge = (net PL - total) × PL capital factor %. For AASB basis: PL Insurance Risk Charge = adjusted net premiums liabilities × PL capital factor %. The Standard also prescribes that where net PL - total or adjusted net premiums liabilities are negative, apply a zero risk charge (P section).

• PL capital factor % and mapping: The PL capital factor % follows GPS 115 (P section and PL capital factor definition). For international business, groups must map their international business to Australian classes (G and P sections) and report a weighted average capital factor for each region.

• Reporting bases: Two preparation bases are recognised and reported separately. The GPS 340 basis requires reporting the components in accordance with GPS 340. The AASB basis allows derived valuations of the GPS 340 PL based on accounting records, subject to meeting GPS 340 requirements and to the Group Actuary adjustments (Tables 4-5, Table 9 and accompanying notes).

• Assurance and controls: The Group Auditor must review and test the systems, processes and controls that produce the data, on at least an annual basis and in a limited assurance engagement consistent with Auditing and Assurance Standards and GPS 310 (para 11). The Board and senior management must ensure appropriate policies and procedures for authorisation of data submitted to APRA (para 12).

• Submission, authorisation and retention: Data must be submitted electronically by a method on APRA’s website or another method notified by APRA (para 5). Officers or agents must digitally sign with a digital certificate acceptable to APRA (para 13). If an agent submits on the parent entity’s behalf, the parent entity must obtain and retain the completed submission copy from the agent (para 14). Submitters must be authorised by the Principal Executive Officer or the Chief Financial Officer (para 15).

• APRA discretion: APRA can vary reporting frequency, reporting periods and the Standard’s requirements in relation to a particular group (paras 7 and 16). APRA may grant extensions (para 9).

• Group adjustments and elimination: The Standard requires separate reporting of group adjustments (Tables 6 and 10). It specifies treatment of intra‑group reinsurance and inter‑regional reinsurance on consolidation, and the need to report consolidation adjustments where reinsurance crosses regions (Specific instructions A and B).

These concepts drive the structure of the tables and the edit/validation constraints: values in whole Australian dollars (monetary fields), percentages to two decimal places, and one‑row per specific combination of field values in reporting tables (General instructions). The Standard’s cross‑references to GPS 340, GPS 115, GPS 001 and GPS 310 embed supervisory and actuarial standards into the data definitions and assurance obligations (Objective and multiple paras).

The Standard applies to one narrow class of entities: the parent entity of a Level 2 insurance group, defined by GPS 001 (para 3). The parent entity is the legal reporting party and bears all primary obligations: to provide APRA with the required information for each reporting period (para 4) and to ensure each requirement of the Standard is complied with (para 3).

Affected parties within and related to that parent entity include:

• Board and senior management: they must ensure appropriate policies and procedures for internal review and authorisation of data submitted to APRA (para 12). That places a governance duty on the governing body and executive.

• Group Actuary and Appointed Actuary: definitions and instructions require actuarial inputs for derived valuations and for determining categorisations (for example, assigning ‘other direct’ business to category A, B or C in GPS 115 for PL capital factor application) (Class of business definition in C). The Standard also asks that certain estimates be consistent with the most recent Actuarial Valuation Report prepared by the Group Actuary (Net PL - non‑reinsurance recoveries definition in N).

• Group Auditor: required to review and test systems, processes and controls on at least an annual basis and to perform a limited assurance engagement consistent with professional standards and GPS 310 (para 11). GPS 310 cross‑reference is explicit and the Group Auditor’s reports relating to the information required must be provided by the time specified in GRS 001 (para 8 note).

• Chief Financial Officer (CFO) and Principal Executive Officer (PEO): only officers authorised by the PEO or the CFO may submit information (para 15). The CFO is defined as the chief financial officer of the parent entity (Interpretation para 18).

• Agents and service providers: third‑party agents may submit on the parent entity’s behalf, but the parent entity must obtain and retain a copy of the completed information provided (para 14). An agent’s submitter must digitally sign and be authorised (paras 13 and 15).

• Subsidiaries and regional entities within the Level 2 group: consolidation rules apply. Where reinsurance occurs between regions or entities, reporting and consolidation treatment is specified; intra‑group reinsurance within a region is eliminated on consolidation, while intra‑group reinsurance between regions requires consolidation adjustments to be reported separately (Specific instructions A and B).

• External systems and data providers: the Standard’s specific data fields, unit conventions (whole dollars, percentages to two decimal places), and the requirement that any specific combination of table values appear only once create IT and data model requirements (General instructions, Tables).

APRA also has operational obligations: it may change reporting periods or frequency for a particular Level 2 insurance group if it considers it necessary or desirable (para 7); it may vary reporting requirements for a particular group (para 16); it receives and uses the data for prudential supervision, including assessing compliance with capital standards (para 2). These discretions and uses shape the compliance work of the affected entities.

Sectors indirectly affected include audit firms that perform group audit and limited assurance work under GPS 310 (para 11 note) and reinsurers and brokers whose contracts influence the calculations reported (definitions on reinsurance commissions, expected reinsurance recoveries, and APRA‑authorised reinsurer in para 18).

Duties

• Parent entity reporting duty: The parent entity of a Level 2 insurance group must provide APRA with the information required by the Standard for each reporting period and ensure compliance with each requirement (paras 3 and 4). This is the primary duty.

• Timing and frequency: The parent entity must report half‑year unaudited information and annual audited information (para 6). Half‑year and annual submissions are due within three months after the end of the reporting period (para 8). The annual information and certain other annual information will form part of the group’s annual accounts within the meaning of GPS 001 (para 6 note), and Group Auditor requirements under GPS 310 govern audit obligations (para 6 note).

• Quality control and assurance: The Group Auditor must review and test systems, processes and controls producing the reported information on at least an annual basis and carry out a limited assurance engagement consistent with Auditing and Assurance Standards and GPS 310 (para 11). The Board and senior management must ensure policies and procedures for internal review and authorisation are in place (para 12).

• Authorisation and signatory requirements: Electronic submissions must be digitally signed using a digital certificate acceptable to APRA (para 13). Submitters must be authorised by the Principal Executive Officer or the Chief Financial Officer (para 15). If an agent submits on the entity’s behalf, the parent entity must obtain and retain a copy of the completed submission (para 14).

• Data preparation and mapping duties: Groups must map international business to Australian classes for capital factor application (G and P sections). Where the group has a reporting adjustment to report Australia by region rather than by class, it must use the region tables (Specific instructions B).

• Reporting conventions and content duties: The Standard enumerates precise fields to be reported (Tables 1-10), units of measure (whole dollars, percentages to two decimal places), and reporting conventions (for example, report reinsurance commissions as a positive number if they act to reduce gross PL) (Table descriptions and General instructions).

Rights and discretions (afforded to APRA and the reporting entity)

• APRA’s discretions: APRA may require more or less frequent reporting than standard half‑year/annual cycles by written notice (para 7), may vary reporting requirements in relation to an individual group by written notice (para 16), may grant extensions for due dates in writing (para 9), and may exclude the requirement to provide half‑yearly information on written application (para 10). APRA also prescribes the method of electronic submission (para 5).

• Reporting entity’s procedural rights: The parent entity may apply in writing to APRA to be excluded from half‑year reporting (para 10). The parent entity may also apply for extensions; APRA may grant them in writing, thereby changing the due date (para 9). The parent entity may choose to use an agent for filing, subject to retention requirements and authorisation obligations (paras 14-15).

• Use of AASB basis: The Standard permits, subject to GPS 340 requirements and Group Actuary assessment, the use of derived valuations of the GPS 340 PL based on accounting records (AASB basis) for Australian and international business (Tables 4-5, Table 9 note). This provides reporting entities with some flexibility in preparation methodology, but constraints apply (see tables and definitions).

• Classification and actuarial judgement: The Appointed Actuary is required to determine, for the ‘other’ direct class, whether the business falls into GPS 115 categories A, B or C based on underlying risk characteristics (Class of business definition in C). This is an operational right/duty to exercise actuarial discretion within a supervisory framework.

Enforcement levers and information rights are embedded by requiring the parent entity to produce and retain documentary proof (para 14), to have digital certificates (para 13), and to provide auditor assurance consistent with GPS 310 (para 11 note). APRA’s ability to vary the reporting structure and frequency (paras 7 and 16) and its authority under the Financial Sector (Collection of Data) Act 2001 (para 1) underpin enforcement and supervisory follow‑up.

The text provided sets out reporting, assurance and authorisation requirements but does not itself specify criminal, civil or administrative penalties in this document. The Reporting Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (para 1), and compliance obligations are established by the Standard; enforcement powers and penalties associated with contraventions of reporting obligations typically derive from the enabling Act and APRA’s broader statutory powers rather than the Reporting Standard text itself. The Standard does, however, build procedural mechanisms that enable monitoring, verification and follow‑up:

• Audit and assurance link to GPS 310: The Group Auditor’s limited assurance engagement and the requirement that the Group Auditor review and test systems, processes and controls (para 11) create a documented assurance trail. GPS 310 contains provisions governing audits and related matters and sets relevant obligations for the Group Auditor (para 6 note). Failure to satisfy GPS 310 audit requirements would be identifiable in audit reports provided to APRA (para 6 note).

• Digital signature and authorisation trail: Electronic submission and digital certificate requirements (paras 5 and 13) and the requirement that submissions be authorised by the PEO or CFO (para 15) create traceability and accountability for the submitted data.

• Retention and agent obligations: Where an agent submits, the parent entity must obtain and retain a copy of the completed submission (para 14). That retention obligation supports enforcement and audit activity by APRA.

• APRA discretions enabling targeted supervision: APRA’s ability to change reporting periods or frequency for a particular group (para 7), to vary reporting requirements by notice (para 16), and to seek additional or less frequent data gives APRA administrative leverage to intensify supervision where concerns arise.

• Data completeness and format checks: The Standard’s prescriptive table structure and one‑row uniqueness rule in tables (General instructions) will allow APRA to apply data validation and edit checks. The requirement to report monetary values in whole dollars and percentages to two decimal places supports automated validation.

Because the Standard does not itself list monetary or criminal penalties, practitioners should look to the Financial Sector (Collection of Data) Act 2001 and other applicable legislation (for example GPS 310 and relevant Corporations Act provisions where applicable) for the sanctioning regime and APRA’s statutory enforcement powers. The Standard’s design, including audit and authorisation requirements (paras 11-15), strengthens APRA’s capacity to identify non‑compliance and to take action under its statutory powers.

The Reporting Standard is explicitly cross‑referenced and designed to operate within a framework of other prudential standards, accounting and auditing standards, and the Act under which it is made. The principal statutory and regulatory interactions in the text are:

• Financial Sector (Collection of Data) Act 2001: The Standard is made under section 13 of that Act (para 1). That Act provides APRA’s statutory authority to require information and governs the legal basis for collection, use and enforcement.

• GPS 001 Definitions: Terms and the definition of Level 2 insurance group are drawn from GPS 001; the Standard repeatedly states that words and expressions have the meaning given in GPS 001 unless a contrary intention appears (Interpretation para 18(a)). The obligation to include the annual information as part of the Level 2 group’s annual accounts is linked to GPS 001 (para 6 note).

• GPS 340 Insurance Liability Valuation: The Standard requires that components of the PL be determined in accordance with GPS 340 where the GPS 340 basis is used (Objective and multiple table headings). It permits, subject to GPS 340 requirements, derived valuations based on AASB accounting records (Tables 4-5 and Table 9 notes).

• GPS 115 Capital Adequacy: Insurance Risk Charge: The PL capital factor % and the overall Insurance Risk Charge mechanics come from GPS 115; the Standard directs that the PL capital factor % be as per GPS 115 and requires mapping of international business to GPS 001 classes for capital factor application (P and G sections).

• GPS 310 Audit and Related Matters: The Group Auditor assurance requirements are to be consistent with GPS 310; the Standard notes that GPS 310 contains provisions governing audits and that the Group Auditor’s reports required by GPS 310 must be provided to APRA as specified in GRS 001 (para 6 note and para 11).

• Australian Accounting and Auditing Standards (AASB and Auditing and Assurance Standards Board guidance): The Standard requires that limited assurance engagements be consistent with professional standards and guidance issued by the Auditing and Assurance Standards Board, to the extent they are not inconsistent with GPS 310 (para 11). The AASB basis reporting option explicitly interfaces with AASB accounting measures and AASB 17 disclosure references are required for insurance contract assets and liabilities in several fields (I section and Tables 4-5).

• Insurance Act 1973: The definition of APRA‑authorised reinsurer references the Insurance Act and the definition of a Lloyd’s underwriter for reinsurance purposes (Interpretation para 18).

• Corporations Act 2001: The Standard uses the Corporations Act meaning of financial year for the reporting period definition (Interpretation para 18).

Operationally, the Standard requires compliance with its own provisions and with the cross‑referenced prudential and accounting standards when preparing the reported items. Two practical interaction effects follow:

1. Audit and prudential overlap: The Standard folds reporting items into the annual accounts and specifies the Group Auditor’s role, meaning audit work under GPS 310 and audit standards intersects with APRA’s prudential reporting obligations (para 6 note; para 11). Practitioners should co‑ordinate audit procedures, actuarial work, and the APRA reporting timetable.

2. Accounting/prudential reconciliation: Where an AASB basis is used to derive GPS 340 PL figures, the Standard requires adjustments and documentation (Tables 4-5 and Table 9 include Adjustment to AASB net liabilities for remaining coverage). This creates a reconciliation obligation between accounting numbers and prudential valuation requirements under GPS 340.

Interpretation para 19 confirms that references to Acts, Prudential Standards, Reporting Standards, and Australian Accounting or Auditing Standards are to the instruments "as in force from time to time", which signals ongoing dynamism: changes to those linked instruments will affect the content and application of this Reporting Standard.

The provided text records a limited and specific amendment and commencement history within itself, rather than a full chronological amendment log. The explicit elements in the document are:

• Authority for the Standard: made under s 13 of the Financial Sector (Collection of Data) Act 2001 (para 1).

• Commencement / application date: The Standard applies for reporting periods ending on or after 1 July 2023 (para 3). That date is the operational start for the obligations described.

• Revocation / transition: The Standard contemplates an "old reporting standard" which was revoked by the determination that made the current Standard. Paragraph 17 imposes a transitional reporting obligation: a parent entity must report under the old reporting standard in respect of transitional reporting periods that ended before 1 July 2023 where reporting was still required under the old standard on or after its revocation (para 17). The Standard also clarifies that overdue reporting documents due under the old standard remain required (para 17 note).

• No other express amendments are recorded in the body of the provided text. The Standard itself contains a general interpretive clause that references other instruments "as in force from time to time" (para 19), which means amendments to GPS 001, GPS 340, GPS 115, GPS 310, AASB standards, or the enabling Act could change the operation or content of the reporting obligations indirectly.

Practical consequence: this Standard replaced an earlier reporting standard at the time of its issue and set a clear cut‑over date of 1 July 2023 (para 3 and para 17). The transitional paragraph preserves the filing obligations for reporting periods that fall within the overlap window created by the revocation. The Standard does not itself list prior amendment dates, earlier versions, or subsequent amendments beyond the commencement and transitional provisions in the text supplied. For a complete legislative amendment history one must consult APRA’s determinations and the relevant gazette or APRA website entries where the Standard and its revocation of the predecessor were published.

The text of this Reporting Standard contains no references to case law, litigation, or judicial interpretation. There are no judicial decisions, administrative law appeals, or enforcement adjudications cited in the document. The Standard cross‑references other prudential and statutory instruments but does not refer to legal challenges or tribunal outcomes.

Given that the Standard operates as an administrative prudential reporting instrument, any litigation arising from its application would appear in separate administrative law or tribunal records and would not be recorded in the Standard itself. Practitioners looking for litigation-based interpretations or challenges to these reporting requirements should search judicial and administrative tribunal databases, and APRA's public records for any determinations, enforcement actions, or case references; none are present in the text provided.

The Standard is precise in many respects; those precisions generate practical pitfalls and operational risks that the reporting entity and its advisers must manage. The following are concrete items to watch carefully, with direct sourcing to the Standard where applicable.

• Parent entity responsibility and consolidation subtleties: The parent entity must ensure each requirement is complied with (para 3). Consolidation at Level 2 must reflect the Level 2 insurance group as defined in GPS 001 and intra‑group reinsurance transactions between entities in different regions must be reported as consolidation adjustments (Specific instructions A and B). Misapplication of consolidation or inconsistent treatment of intra‑group reinsurance can produce reconciliation and validation failures in Table 6 or Table 10.

• Two preparation bases with different reporting requirements: The Standard requires reporting on either a GPS 340 basis or an AASB derived basis, and separate tables exist for each (Tables 2-3 for GPS 340; Tables 4-5 and Table 9 for AASB). Use of the AASB basis is permitted only "subject to meeting the GPS 340 requirements" (Table headings and notes). Where a group adopts the AASB basis it must report adjustments to AASB net liabilities (Tables 4-5 and Table 9). Confusing the bases or failing to provide required adjustments can yield incorrect PL Insurance Risk Charge calculations.

• Actuarial judgements and classification of 'other' direct business: The Appointed Actuary must determine the most appropriate GPS 115 category (A, B or C) for 'other' direct business based on underlying risk characteristics (Class of business definition in C). The actuarial choice determines the PL capital factor applied and interacts directly with capital charge calculation (P). Misclassification can materially change the assigned PL capital factor.

• Mapping international business to Australian classes: For international business the Standard requires that groups map international business to Australian classes to assign an insurance risk capital charge and report a weighted capital factor per region (G and P). This mapping is required even where region reporting is used (Specific instructions B). The mapping and calculation must be supplied as a reporting supplement to APRA (Specific instructions B), and there is an operational burden in documenting and defending that mapping.

• Treatment of recoveries and reinsurance: Expected future reinsurance costs are to be reported gross of recoveries and should not include CHE, PAE, or risk margin (E). Expected reinsurance recoveries are to be reported gross of any provision for depreciation or impairment (Net PL - expected reinsurance recoveries in N). Differences in gross/net conventions and timing of recognition under accounting standards create potential reconciliation issues.

• Zero floor on risk charge: The Standard instructs to apply a zero risk charge where net PL - total or adjusted net premiums liabilities are negative (P). Groups must ensure this floor is implemented in reporting systems to avoid negative charges being reported.

• Units, rounding and positivity conventions: Monetary values must be reported in whole Australian dollars and percentages to two decimal places; certain items (e.g. reinsurance commissions) are to be reported as positive numbers if they reduce gross PL (Tables 2 and 3 descriptions). Failure to apply these sign conventions and rounding rules will cause validation failures.

• Audit and assurance scope: The Group Auditor must review and test systems, processes and controls and provide at least a limited assurance engagement consistent with professional standards and GPS 310 (para 11). The Standard requires the Group Auditor to perform the review at least annually or more frequently if necessary to form an opinion (para 11). Underestimating audit scope or timing can lead to late or non‑compliant audit evidence.

• Digital signature and authorisation: Electronic submissions must be digitally signed with a certificate acceptable to APRA (para 13), and the submitter must be authorised by the PEO or CFO (para 15). Digital certificate procurement, managing authorised signatories and agent authorisations can be administratively taxing. If an agent submits, the parent entity must obtain and retain the completed submission (para 14). Failure to retain may raise compliance questions in any post‑submission review.

• APRA discretion creates case‑by‑case variation: APRA can vary reporting periods or reporting requirements for a particular group (paras 7 and 16). While this is useful flexibility, it creates uncertainty and the potential for differing reporting regimes across otherwise similar groups, increasing compliance complexity.

• Transitional reporting traps: Paragraph 17 requires reporting under the old standard for certain transitional reporting periods that ended before 1 July 2023 but were due on or after the old standard’s revocation. Entities must identify any outstanding transitional filings and apply the old standard, not the new one, to those periods. Missing this identification can lead to inconsistent filings.

• Requirement that "any specific combination of values in the table must not appear on more than one row": The tables enforce uniqueness constraints (General instructions). Reporting systems must enforce these uniqueness rules; failure will cause submission errors.

• Evidence trail for actuarial estimates: The Standard requires non‑reinsurance recoveries to be estimated consistent with the most recent Actuarial Valuation Report prepared by the Group Actuary (Net PL - non‑reinsurance recoveries definition in N). Entities must maintain actuarial documentation linking estimates in the return to the Actuarial Valuation Report.

Each of these items is specified in the Standard; they should be treated as operational constraints rather than optional best practice.

This section sets out a practical, source‑grounded compliance checklist tied to the Standard’s paragraphs and tables. The checklist is organised as immediate, structural and periodic steps.

Immediate actions (set up and governance)

1. Confirm reporting entity and scope: Verify the parent entity is a Level 2 insurance group parent per GPS 001 and that the group falls within the Standard’s application for reporting periods ending on or after 1 July 2023 (para 3).

2. Determine reporting basis and table set: Decide whether the group will report on a GPS 340 basis or use derived AASB basis valuations for GPS 340 PL. If the group has a reporting adjustment to report Australia by region rather than by class, plan to complete Tables 7-10 instead of Tables 1-6 (General instructions; Specific instructions A and B).

3. Map international business: For international business, map business to Australian classes as required for capital factor assignment and prepare the reporting supplement documentation for APRA (G and P sections; Specific instructions B).

4. Assign responsibilities and authorisations: Confirm the persons authorised to sign and submit (must be authorised by PEO or CFO) and arrange digital certificates acceptable to APRA for officers or agents who will sign submissions (paras 13 and 15).

Structural requirements (systems, documentation, audit coordination)

5. Data model and table controls: Build or update reporting systems to produce the exact fields in Tables 1-10. Enforce units (whole dollars; percentages two decimal places), sign conventions (items to be reported as positive if they reduce gross PL), and the uniqueness constraint that specific combinations of table values appear only once (General instructions; Table descriptions).

6. Consolidation rules and intra‑group reinsurance: Implement consolidation logic that eliminates intra‑group reinsurance within a reported region, reports inter‑regional reinsurance as direct business in both regions and generates consolidation adjustments for intra‑group reinsurance between entities in different regions to populate Table 6 or Table 10 as applicable (Specific instructions A and B).

7. Actuarial workflows and documentation: Ensure the Group Actuary/Appointed Actuary produces the required evidence for derived valuations and classifications, including category selection for ‘other direct’ business per GPS 115 (Class of business definition in C) and actuarial estimates for non‑reinsurance recoveries consistent with the most recent Actuarial Valuation Report (Net PL - non‑reinsurance recoveries in N). Retain actuarial memoranda to support reported numbers.

8. Reinsurance and recoveries detail: Establish processes for calculating expected future reinsurance costs gross of recoveries, and expected reinsurance recoveries gross of impairments; ensure CHE and PAE are treated according to the table instructions (E, G, C sections and Table notes).

9. Audit engagement plan: Coordinate with the Group Auditor early. The Group Auditor must review and test systems, processes and controls used to generate the reporting information on at least an annual basis and carry out a limited assurance engagement consistent with Auditing and Assurance Standards and GPS 310 (para 11). Agree timing so that limited assurance and Group Auditor’s reports can be provided in line with GRS 001 and GPS 310 timeframes (para 6 note; para 11).

10. Authorisation and record retention: Implement internal policies and procedures for authorisation of data submitted to APRA (para 12). If an agent will submit on the entity’s behalf, put contractual and procedural arrangements in place to ensure the parent entity obtains and retains the completed submission copy (para 14).

Periodic operational matters (pre‑submission and submission)

11. Reporting calendar and deadlines: Calendar the reporting dates: half‑year and annual information due within three months after the end of the relevant reporting period (para 8). Note APRA’s discretion to specify different periods or frequencies for particular groups (para 7), and the ability to apply for an exclusion from half‑year reporting (para 10) or an extension (para 9).

12. Data validation and reconciliations: Run pre‑submission validation checks against table constraints (unique rows, whole‑dollar fields, percentage formatting). Reconcile the PL components to accounting records and to actuarial valuation outputs. Ensure net PL - total or adjusted net premiums liabilities floor logic (zero floor) is applied before calculating PL Insurance Risk Charge (P).

13. Sign and submit: Submit via APRA’s electronic method on APRA’s website or by another method notified by APRA (para 5). Ensure the officer or agent digitally signs with an APRA‑acceptable digital certificate (para 13) and that the submitter has PEO or CFO authorisation (para 15).

14. Prepare supporting files and reporting supplements: Prepare the supplementary mapping of international business to Australian classes and the methodology for calculating weighted average capital factors for each region where required (P and Specific instructions B). Maintain supporting actuarial reports and the Group Auditor’s assurance workpapers to respond to any APRA enquiries.

15. Post‑submission recordkeeping and governance: Retain a copy of the completed submission and supporting documentation (para 14). Maintain change logs for any post‑submission corrections and document reasons for actuarial judgements and mapping decisions, as those may be the focus of APRA follow‑up or validation.

Contingencies and APRA engagement

16. Manage APRA notices: If APRA issues a notice changing reporting periods or varying reporting requirements for the group, implement the change promptly and document the basis for the change (paras 7 and 16). If more frequent reporting is required, coordinate with the Group Auditor to maintain assurance coverage for the increased frequency (para 11).

17. Transitional obligations: Identify any transitional reporting periods that fall under the old reporting standard per paragraph 17 and ensure those reports are prepared under the old standard if still due. Do not assume all historical periods automatically convert to the new Standard (para 17).

18. Use of consultants and vendors: If engaging third‑party service providers for data extraction, actuarial calculations or submission, ensure their deliverables meet the Standard’s table structure, sign conventions, and auditability requirements and that contractual arrangements require retention and timely access to underlying workpapers.

By following these steps and cross‑referencing the specific paragraphs and tables noted above, a parent entity can align its data collection, internal controls, audit coordination and submission procedures with the Standard’s requirements. The Standard’s explicit definitions, table structures and assurance expectations make compliance a matter of mapped processes, documented actuarial judgements, validated data flows and formalised authorisation.