This Reporting Standard organises reporting around a small set of core concepts drawn from GPS 340 and GPS 115, implemented through discrete reporting tables.

Outstanding claims liabilities (OCL), as used in the tables, are decomposed into several components for reporting: gross OCL , central estimate (excluding claims handling expenses); claims handling expenses; gross OCL , diversified risk margin; net OCL components after non‑reinsurance recoveries and reinsurance recoverables; net stand‑alone and diversified risk margins; and, ultimately, an OCL Insurance Risk Charge figure (see Tables 2-6 and 8-10). Those labels are used consistently across the GPS 340 basis and the AASB (accounting) basis variants of the tables.

Two reporting bases are explicitly accommodated:

• GPS 340 basis: reporting the GPS 340 OCL components directly (Tables 2 and 3 for class/region reporting, Tables 8 and 3/8 for regional reporting) and;
• AASB basis: deriving GPS 340 elements from accounting records (AASB basis) and reporting insurance contract liabilities, reinsurance contract liabilities, insurance contract assets and reinsurance contract assets by class or region (Tables 4 and 5 for class, Tables 9 for region).

The instrument allows Level 2 groups to adopt derived valuations for GPS 340 OCL based on accounting records (the AASB basis), but only subject to meeting GPS 340 requirements (see Specific instructions A and B, paragraphs introducing Tables 4, 5 and 9). That creates an explicit bridge between accounting measures and prudential valuation measures.

Geography and segmentation are operational concepts here. A Level 2 group will either report “Australia by class of business” (Specific instructions A) or “Australia by region” (Specific instructions B), but not both. International business is reported by region (New Zealand, South‑East Asia, Asia Pacific, USA, Americas, UK or Europe, Other) and must be mapped to Australian classes of business for capital charge assignment and as a reporting supplement to APRA (see Specific instructions A and B). Reinsurance interactions are treated explicitly: reinsurance between regions is to be reported on a separate basis, with the region assuming the risk reporting as direct business, and the region receiving reinsurance treating it as direct business as well. Intra‑group reinsurance transactions within a region are eliminated on consolidation; intra‑group reinsurance between regions requires consolidation adjustments reported in Table 6 or Table 10 (Specific instructions A and B).

Numerical conventions are specified: values in whole Australian dollars, and percentages to two decimal places where required (Tables 2-5, 8-9). Group adjustments not recognised in other tables must be reported and reported reductions in OCL are to be recorded as negative values (Tables 6 and 10).

Quality control, assurance and authorisation form part of the conceptual architecture: the Group Auditor must review and test systems, processes and controls that produce the reported data at least on an annual basis and undertake a limited assurance engagement consistent with Auditing and Assurance Standards Board professional standards (paragraph 11), and the Board and senior management are required to maintain internal review and authorisation policies (paragraph 12). Authorised signatories and digital signing are required for submissions (paragraphs 13-15).

Finally, the Standard sits within a statutory data‑collection framework: its stated purpose is to provide APRA information used for prudential supervision, including assessing compliance with capital standards (paragraph 2). The instrument therefore functions as a data provisioning rule designed to connect the group’s valuations and reinsurance arrangements into APRA’s capital supervision framework (as referenced to GPS 115 and GPS 340 in the Objective).

Primary obligors: the parent entity of a Level 2 insurance group. The Standard applies to that parent entity and requires it to ensure each requirement is complied with on behalf of the entire Level 2 insurance group (paragraph 3). “Level 2 insurance group” is a defined term referenced to GPS 001, so the scope of who is covered is tied to GPS 001’s definitions (paragraph 18(a)).

Internal stakeholders: the Board and senior management of the parent entity are explicitly assigned responsibility for establishing policies and procedures for internal review and authorisation of data submitted to APRA (paragraph 12). The Principal Executive Officer and the Chief Financial Officer are empowered to authorise officers or agents to submit data on the group’s behalf; any electronic submission by an agent must be authorised by one of those officers (paragraph 15).

External advisers and auditors: the Group Auditor has specific obligations to review and test the group’s reporting systems, processes and controls and to provide at least a limited assurance engagement consistent with professional standards (paragraph 11). The Group Auditor’s role connects the group’s internal control architecture into the reporting obligations and external assurance timetable referenced elsewhere (note in paragraph 8 and GPS 310). Actuarial service providers are also indirectly implicated: the tables ask whether actuarial services were used to complete the return (Tables 1 and 7 Items 1), and the OCL components reported are valuation outputs that commonly depend on actuarial work (the Standard’s structure assumes actuarial inputs).

Operational staff and IT: the requirement for electronic submission, digital certificates acceptable to APRA, and retention of copies where agents submit (paragraphs 5, 13-14) creates obligations for IT, compliance, and record‑keeping teams. The system owners who prepare the tables, consolidation adjustments and mapping of classes to regions must support the generation of whole‑dollar figures and percentages to two decimal places as set out.

Reinsurers: APRA‑authorised and non‑APRA‑authorised reinsurers are part of the reporting frame through the definitions and through the requirement to report reinsurance recoverables and non‑reinsurance recoveries (paragraph 18; Tables 2-5, 8-9). The Standard requires reporting of reinsurance recoverables and treatment of reinsurance between and within regions.

Who pays: costs fall on the parent entity of the Level 2 group in the form of internal staff time, system changes for data capture and submission, actuarial and audit fees (Group Auditor engagements), and potential consultancy costs to map international business to Australian classes and prepare the reporting supplement required by APRA (Specific instructions A and B). APRA bears the administrative cost of receiving, processing, and using the data for supervision, but those costs are not quantified in the Standard.

Finally, APRA as regulator is a decision‑maker in day‑to‑day operation: it can change reporting periods by written notice, grant extensions, vary reporting requirements for particular groups, and exclude the half‑year reporting requirement on application (paragraphs 7, 9, 10, 16). Those powers create ongoing compliance and responsiveness obligations for affected entities.

Obligations imposed by the Standard are concrete and prescriptive.

Primary duty to report: the parent entity of a Level 2 insurance group must provide APRA with the information specified in the Standard for each reporting period (paragraph 4). This is an affirmative, periodic data delivery obligation covering the group as a whole (paragraph 3).

Selection of reporting basis and tables: a group must determine whether it reports “Australia by class of business” (complete Tables 1-6) or “Australia by region” (complete Tables 7-10) and must not complete both sets (Specific instructions A and B). Where derived valuations (AASB basis) are used, the group must meet GPS 340 requirements to adopt that basis (Tables 4, 5 and 9 introductions).

Filing mechanics and timing: submissions must be made electronically by APRA’s electronic method or another APRA‑notified method (paragraph 5). Default timing requires unaudited half‑yearly and audited annual reporting with due dates within three months after period end (paragraphs 6 and 8). The Standard sets an expectation that the Group Auditor’s report required by GPS 310 must be provided as required by GRS 001 (note under paragraph 8).

Quality assurance duties: the Group Auditor must review and test the systems, processes and controls that produce the information and perform at least a limited assurance engagement consistent with the Auditing and Assurance Standards Board standards, subject to GPS 310 constraints (paragraph 11). The group must maintain systems, processes and controls for internal review and authorisation; the Board and senior management are responsible for ensuring appropriate policies and procedures (paragraph 12).

Authorisation and recordkeeping: electronic submissions must be digitally signed using a certificate acceptable to APRA (paragraph 13). If an agent submits, the parent entity must obtain and retain a copy of the completed submission (paragraph 14). Any officer or agent who submits must be authorised by the Principal Executive Officer or the Chief Financial Officer (paragraph 15).

Rights and regulator discretions: APRA has discretion to alter reporting frequency, specify different reporting periods by written notice (paragraph 7), grant extensions of due dates in writing (paragraph 9), exclude the half‑year requirement on application (paragraph 10), and vary reporting requirements in relation to a particular group by written notice (paragraph 16). These are procedural rights that APRA can exercise to tailor supervision and collection frequency.

Transitional duty: a parent entity must report transitional reporting periods under the old (revoked) reporting standard where those periods ended before 1 July 2023 but the required reporting date fell on or after the revocation date (paragraph 17). This imposes an obligation to follow the previous format for certain delayed or overdue reports.

Numerical and formatting duties: reporting must use whole Australian dollars and percentages to two decimal places where specified; group adjustments reducing OCL must be reported as negative values; and reporting supplements are required for mapping international business to Australian classes (Tables 2-5, 8-9; Specific instructions A and B).

Interaction duties: the Standard must be read with GPS 340, GPS 115, GPS 001, GPS 310 and GRS 001; the Standard’s purpose is explicitly prudential supervision including assessing compliance with capital standards (paragraph 2). Therefore, duty to report interacts functionally with capital adequacy obligations and audit rules outside this instrument.

What the Standard does not set out: it contains no civil or criminal penalties within its text. Enforcement and sanctions are implied via its underpinning statutory authority (the Financial Sector (Collection of Data) Act 2001) and via APRA’s supervisory powers, but specifics of penalties are not stated in the Standard itself (paragraph 1 and its link to the Act).

The Reporting Standard does not enumerate specific fines, civil penalties or criminal sanctions within its text. It is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1), and the Standard states its purpose is to provide information used by APRA for prudential supervision, including assessing compliance with capital standards (paragraph 2). Enforcement therefore sits in a statutory framework beyond the Standard’s paragraphs; the instrument provides the data obligations and supervisory mechanics but does not itself set out an enforcement schedule or penalty table.

Mechanisms through which compliance is tested and assured, as set out in the Standard, include:

• mandatory Group Auditor review and testing of the systems, processes and controls that produce the reported information, at least annually and at a minimum to a limited assurance level consistent with Auditing and Assurance Standards Board guidance, to the extent not inconsistent with GPS 310 (paragraph 11); and
• internal review and authorisation policies required to be in place and owned by the Board and senior management (paragraph 12).

Administrative enforcement levers available to APRA within the Standard include:

• discretion to change reporting periods, specify reporting periods, and require reporting more or less frequently for a particular Level 2 group by written notice (paragraph 7);
• power to grant written extensions to due dates (paragraph 9);
• power to exclude the half‑year requirement on application (paragraph 10);
• power to vary the reporting requirements in relation to a particular group by written notice (paragraph 16); and
• requirement for submissions to be digitally signed with a certificate acceptable to APRA and for authorised signatories to be designated, creating traceability and auditability (paragraphs 13-15).

Where the Standard refers to other instruments with enforcement content, those instruments supply additional audit and compliance mechanics: GPS 310 contains provisions governing audits and the Group Auditor’s role (not reproduced here but cross‑referenced in paragraph 6 and the note under paragraph 8), and GRS 001 contains the general instruction guide and procedural timelines (not reproduced here but cross‑referenced repeatedly). The Standard requires the Group Auditor’s report(s) as required by GPS 310 to be provided to APRA by the timeframes specified in GRS 001, unless an extension is granted (note under paragraph 8).

Practitioners should note that because the Standard is a data collection instrument made under the Financial Sector (Collection of Data) Act 2001, legal enforcement (including penalties, directions or other supervisory action) will be governed by that Act and APRA’s broader statutory powers; those are not repeated in the Standard. The absence of specified penalties in this document increases the importance of checking the parent Act and related prudential standards for the concrete enforcement regime applicable in the event of non‑compliance.

Implementation risks that have enforcement implications:

• failure to meet the Group Auditor’s limited assurance requirement (paragraph 11) could render reported data non‑compliant with GPS 310 expectations and trigger follow‑up from APRA under its supervisory powers;
• errors in the mapping of international business to Australian classes (required as a reporting supplement) could distort the Insurance Risk Charge calculation and prompt requests for remedial filings or supervisory action;
• the digital signature and agent authorisation/retention requirements (paragraphs 13-15) create traceability obligations; failure to retain copies or to ensure authorised signatories have been used may increase the likelihood of enforcement contact.

In short, while the Standard specifies data obligations and procedural powers for APRA, explicit sanctions are located in the parent legislative and prudential framework rather than within the Standard’s text itself (paragraphs 1-2, 6, 11, 16).

The Reporting Standard is explicitly designed to operate within and alongside a set of prudential standards, reporting standards and statutes. The instrument itself directs readers to read it in conjunction with GRS 001 Reporting Requirements (including the general instruction guide), GPS 115 Capital Adequacy: Insurance Risk Charge, and GPS 340 Insurance Liability Valuation (Objective and opening paragraphs). The mechanics of interaction are as follows.

Statutory authority and enforcement context: the Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). That Act provides the statutory power to require data from regulated entities. Enforcement, penalties and directions that APRA may issue are matters governed by the parent Act and by the broader APRA statutory toolkit; this Standard operates as an instrument within that legislative framework (paragraph 1).

Prudential standards: GPS 340 is the valuation standard whose components feed directly into the OCL fields required by the Reporting Standard. The Standard references GPS 340 OCL components and permits derived valuations from accounting records only subject to meeting GPS 340 requirements (Tables 2-5 and 8-9). GPS 115 concerns capital adequacy and the Insurance Risk Charge, and the Standard’s purpose explicitly includes supplying information to APRA for assessing compliance with capital standards (paragraph 2). Therefore, the data flows from this Reporting Standard are intended to operationalise capital computations and prudential assessments under GPS 115 and related capital standards.

Auditing standards and GPS 310: the Group Auditor’s review obligations under paragraph 11 must be performed at least to a limited assurance level consistent with Auditing and Assurance Standards Board professional standards as may be amended from time to time, to the extent not inconsistent with GPS 310. GPS 310 contains the provisions governing audits, Group Auditor duties and the audit timetable referenced in the note under paragraph 8. GRS 001 sets submission timing and contains the general instruction guide referenced multiple times. Thus, the Reporting Standard depends on GPS 310 for the minimum audit procedures and on GRS 001 for submission mechanics and deadlines.

Accounting law: the Standard accepts an AASB basis for reporting (derived valuations based on accounting records) provided GPS 340 requirements are met (Tables 4, 5 and 9). It defines “financial year” by reference to the Corporations Act 2001 (paragraph 18). All references to Australian Accounting or Auditing Standards are to instruments as in force from time to time (paragraph 19), linking the Reporting Standard to the AASB and Auditing standards regime.

Insurance Act 1973: the definition of APRA‑authorised reinsurer includes a Lloyd’s underwriter as defined under the Insurance Act; the Insurance Reinsurance Pool Corporation is also included by name (paragraph 18). That ties the reporting regime for reinsurance recoverables and reinsurance classes to the statutory definitions and authorisations under the Insurance Act.

Cross‑institutional mapping and capital reporting: the Standard requires Level 2 groups to map international business to Australian classes of business for Insurance Risk Charge assignment and to provide a reporting supplement to APRA explaining the mapping (Specific instructions A and B). This creates an explicit data harmony requirement between local prudential capital calculation regimes and foreign business segmentation.

Transitional interaction: paragraph 17 obliges entities to report under the old reporting standard for transitional periods that ended before 1 July 2023 but for which reports were still due after the old standard was revoked. That creates a temporal overlap and requires practitioners to consult both the revoked standard and this new Standard to determine reporting obligations for certain periods.

Operational interplay: the Standard’s requirements for digital signatures acceptable to APRA, agent authorisations, and retention of copies require IT, legal and compliance teams to coordinate to ensure submissions meet both technical and legal requirements set out by APRA and consistent with broader legal retention obligations under corporate and audit laws (paragraphs 13-15, 12).

Finally, paragraph 19 expressly provides that references to Acts, Prudential Standards, Reporting Standards, Australian Accounting or Auditing Standards are references to instruments as in force from time to time, making this Standard dynamically linked to changes in those external instruments. Practitioners must therefore read this Standard against the contemporaneous versions of GPS 340, GPS 115, GPS 310, GRS 001 and relevant accounting and auditing standards.

The provided text gives limited amendment information but sets a clear commencement date and transitional arrangement. Key chronological or amendment facts present in the text are:

• Commencement date for application: the Standard applies to reporting periods ending on or after 1 July 2023 (paragraph 3). That is the effective start for liabilities to be reported under this Standard.
• Transitional provision: paragraph 17 requires a parent entity of a Level 2 insurance group to report under the old reporting standard for any transitional reporting period. The paragraph defines “old reporting standard” as the reporting standard revoked in the determination making this Reporting Standard, and defines “transitional reporting period” as a reporting period under the old reporting standard which ended before 1 July 2023 and for which reporting under the old standard was required on or after the date of revocation. The note immediately following paragraph 17 emphasises that overdue reporting documents still due under the old standard must be supplied in accordance with the old standard.
• No other amendment history, prior versions, or amendment dates are included in the text provided. The Standard does not list any amendment schedule, prior version dates, or a formal history log within the text supplied here.
• Paragraph 19 states that references to Acts, Prudential Standards, Reporting Standards and Australian Accounting or Auditing Standards are references to the instruments “as in force from time to time”. That indicates the Standard is intended to operate alongside future amendments of those instruments, but does not itself record historical amendments.

Practical consequence for users: the Standard replaces a prior reporting standard via revocation in the determination that made this Standard, and it sets a cut‑off so that reporting periods ending on or after 1 July 2023 are covered by this Standard whereas some earlier reporting periods may remain governed by the old standard (paragraphs 3 and 17). For full historical amendment detail (such as the revocation determination, dates and versions), practitioners will need to consult APRA’s determination instrument and APRA’s legislative/standards register, since those materials are not reproduced in the text supplied.

The Reporting Standard, as provided, contains no litigation history and does not name any judicial decisions. The instrument itself is a reporting instrument and cites prudential and statutory instruments, but does not discuss court cases, administrative appeals or disputes arising from its application. There are no cases or tribunal decisions mentioned in the text.

For practitioners, the absence of litigation history in the instrument means:

• There is no precedent or interpretive case law embedded in this document to guide how courts or tribunals have construed its specific obligations or APRA’s exercise of the powers the Standard invokes.
• Any disputes over interpretation, enforcement or factual application would be litigated or administratively contested under the statutory framework (for example, the Financial Sector (Collection of Data) Act 2001 and associated prudential standard enforcement powers), but those proceedings are outside the four corners of this Reporting Standard text.
• To establish whether litigation or appellate guidance exists on particular issues (for example, the scope of APRA’s s13 data collection powers, or challenges to APRA notices under paragraph 7 or 16), practitioners must look beyond this Standard to case law and decisions concerning the parent Act and related prudential standards.

In short, the instrument supplies the reporting architecture but provides no record of how that architecture has been contested or interpreted by courts or tribunals in the materials provided.

This Standard contains several practical traps and detail points where non‑compliance, misreporting, or operational friction commonly arises. The following are explicit, source‑linked pitfalls to watch.

Choice of reporting basis and mutual exclusivity: a Level 2 insurance group must choose whether to report “Australia by class of business” or “Australia by region.” The chosen path determines which group of tables must be completed: Tables 1-6 for class reporting, or Tables 7-10 for regional reporting (Specific instructions A and B). Completing both sets or the wrong set is a compliance error.

Derived valuations and GPS 340 requirements: the Standard allows AASB‑basis (derived) reporting only if GPS 340 requirements are met (Tables 4, 5 and 9). Adopting an AASB basis without demonstrating compliance with GPS 340’s valuation requirements risks rejection of the derived figures or requests for resubmission and supporting material, including a reporting supplement.

Mapping international business to Australian classes: even where reporting is by region, Level 2 groups are expected to map their international business to Australian classes (Specific instructions A and B). This mapping must be documented and provided as a reporting supplement. Inconsistent or undocumented mappings can materially affect Insurance Risk Charge allocations and invite detailed APRA queries.

Reinsurance reporting nuances:

• Reinsurance between regions is to be reported on a separate basis: the assuming region must report as direct business, and the receiving region must also treat the incoming reinsurance as direct business (Specific instructions A and B). This creates potential duplication or misclassification risk if teams do not coordinate.
• Intra‑group reinsurance transactions between entities in different regions require consolidation adjustments (reported in Table 6 or Table 10). Failure to eliminate intra‑group transactions correctly at consolidation will distort OCL and capital measures.

Sign and format conventions:

• Values must be in whole Australian dollars; percentages to two decimal places where specified. Inconsistent rounding or decimal placement can lead to format rejections (Tables 2-5, 8-9).
• Adjustments that result in reductions in GPS 340 OCL must be reported as negative values (Tables 6 and 10). Sign errors are a common cause of rework.

Assurance and timing interplay: the Group Auditor must review systems and processes and perform at least a limited assurance engagement (paragraph 11). GPS 310 requires the Group Auditor to conduct a limited assurance review of the group’s annual accounts; the Group Auditor’s report(s) as required by GPS 310 must be provided to APRA by the time specified in GRS 001 (note under paragraph 8). Coordination between audit timelines and the three‑month filing deadline is necessary. Missing that coordination can produce late filings or the need to seek extensions under paragraph 9.

Digital signature and authorised submitter rules:

• Electronic submissions must be digitally signed using a certificate acceptable to APRA (paragraph 13). Not all certificates are acceptable; groups must confirm APRA’s technical and security requirements in advance.
• Agents may submit on behalf of the parent entity, but the parent entity must obtain and retain a copy of what the agent submitted (paragraph 14). Loss of agent‑submitted files or failure to retain copies can raise compliance flags.
• Agents must be authorised by the Principal Executive Officer or Chief Financial Officer (paragraph 15). Delegation without such authorisation is a compliance breach.

APRA discretion and dynamic reporting: APRA may change reporting periods or specify different reporting periods for a group by written notice (paragraph 7) and may vary the reporting requirements in relation to a Level 2 group (paragraph 16). Groups must track APRA notices actively; assumptions about fixed cycles risk sudden rework if APRA issues a notice.

Transitional reporting obligations: transitional reporting periods that ended before 1 July 2023 but whose reporting was due on or after the revocation date must be reported under the old standard (paragraph 17). Misreading the transitional rule can cause paradoxical dual‑format reporting obligations for late periods.

Audit standard interpretation differences: paragraph 11 requires limited assurance consistent with Auditing and Assurance Standards Board guidance “as may be amended from time to time, to the extent that they are not inconsistent with the requirements of Prudential Standard GPS 310.” Differences between shifting auditing standards and GPS 310 may create interpretation issues about the scope of the assurance engagement; groups should engage auditors early to agree scope.

Reporting supplements and narrative detail: the Standard anticipates reporting supplements, especially for mapping international business to Australian classes and for explaining calculation of the Insurance Risk Charge. Failure to provide adequate narrative explanation alongside tables can delay APRA’s assessment and trigger follow‑up.

No explicit penalties listed: the Standard does not state penalties. Practitioners must therefore check the parent Act and related standards for the enforcement regime. Assuming no consequence because the Standard is silent on penalties is risky.

In short, the main operational gotchas are selection of the correct reporting path, careful mapping and consolidation for reinsurance, strict adherence to numerical and sign conventions, early coordination between actuarial, accounting and audit teams, proper authorisation and retention of agent submissions, and watching for APRA notices that change reporting timing or requirements.

This section provides a practical compliance checklist aligned with the textual requirements of the Reporting Standard. Each task references the relevant paragraph(s) or table groupings so practitioners can trace obligations back to the source.

1. Confirm applicability and reporting basis

   • Confirm the entity is the parent entity of a Level 2 insurance group as defined in GPS 001 and that the reporting period ends on or after 1 July 2023 (paragraph 3).
   • Decide whether to report “Australia by class of business” (complete Tables 1-6) or “Australia by region” (complete Tables 7-10) and do not prepare both (Specific instructions A and B).

2. Set up data capture and mapping

   • Map insurance business and international operations to the Australian classes of business as defined in GPS 001; prepare a reporting supplement documenting the mapping (Specific instructions A and B).
   • For international regions, assign business to the region list given (New Zealand, South‑East Asia, Asia Pacific, USA, Americas, UK or Europe, Other) and ensure the mapping is auditable (Tables 3 and 5 introductions).

3. Valuation approach and reconciliation

   • Choose GPS 340 basis reporting (directly report GPS 340 OCL components in Tables 2 and 3 or 8) or AASB (derived) basis reporting (Tables 4, 5 or 9). If using AASB basis, ensure the derived valuations satisfy GPS 340 requirements (Tables 4, 5 and 9).
   • Reconcile accounting figures (AASB) to GPS 340 valuation components and maintain a reconciliation pack to support the audit and APRA queries (Tables 4 and 5 fields).

4. Reinsurance and consolidation controls

   • Implement procedures to classify reinsurance between regions correctly: the assuming region reports as direct business; the receiving region treats the assumed reinsurance as direct business (Specific instructions A and B).
   • Prepare consolidation adjustments for intra‑group reinsurance transactions between entities in different regions and report them in Table 6 or Table 10.

5. Numerical format, sign conventions and units

   • Ensure reporting systems output whole Australian dollars for monetary fields and percentages to two decimal places where required (Tables 2-5, 8-9).
   • Adopt the explicit sign convention that adjustments reducing OCL are negative values (Tables 6 and 10). Train preparers to avoid sign errors.

6. Assurance and audit coordination

   • Engage the Group Auditor early to plan the review and testing of systems, processes and controls. The Group Auditor must perform at least an annual review and at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance, subject to GPS 310 (paragraph 11).
   • Coordinate submission dates so audit deliverables (Group Auditor report requirements under GPS 310 and GRS 001) are available in time to meet the three‑month due date or to support any extension applications (note under paragraph 8).

7. Internal governance and authorisation

   • Implement Board‑level policies and senior management procedures for internal review and authorisation of submitted data (paragraph 12).
   • Prepare a register of authorised submitters and ensure any officer or agent who submits data is authorised by the Principal Executive Officer or Chief Financial Officer (paragraph 15).

8. Electronic submission and digital signatures

   • Ensure the electronic submission method conforms to APRA’s electronic method and that digital certificates used to sign submissions are acceptable to APRA (paragraph 5 and 13). Check APRA’s technical guidance for certificate formats, expiry policies and signing protocols.
   • If appointing an agent, establish contractual requirements for the agent to provide a copy of the completed submission and ensure the parent entity retains that copy (paragraph 14).

9. Timing, extensions and notices

   • Calendar due dates: default due date is within three months after the end of the reporting period (paragraph 8). If an actual due date falls on a non‑business day, the standard requires filing by the due date nonetheless (note under paragraph 9).
   • If a longer lead time is needed, apply to APRA in writing for an extension (paragraph 9). If an entity seeks to exclude half‑year reporting, apply in writing to APRA (paragraph 10).
   • Monitor APRA notices in case APRA changes reporting periods or varies requirements for the particular Level 2 group (paragraphs 7 and 16).

10. Reporting supplements and documentation

    • Prepare and retain a reporting supplement explaining the mapping of international business to Australian classes, the methodology used to derive any AASB basis GPS 340 valuations, and any assumptions or adjustments (Specific instructions A and B).
    • Maintain audit trails for all reported table fields, including actuarial files if actuarial services were used (Tables 1 and 7 Item 1).

11. Quality assurance, testing and contingency planning

    • Perform internal testing of the full reporting cycle including extraction, rounding, sign conventions, consolidation adjustments and file upload to APRA’s electronic portal.
    • Test digital signing, certificate validity and agent submission workflows under realistic timelines and back up signed submissions and audit evidence in accordance with record retention policies.

12. Post‑submission monitoring and APRA engagement

    • Allocate resources to respond to APRA follow‑up questions promptly, including the ability to rework mappings, recalculate OCL components or supply additional reconciliations.
    • Keep the Group Auditor informed of any APRA requests or findings that might affect the auditor’s report or the group’s controls.

13. Transitional compliance for pre‑1 July 2023 periods

    • For any reporting periods that ended before 1 July 2023 but with reporting required on or after the revocation date, prepare reports under the old reporting standard in accordance with paragraph 17 and the revoked standard’s requirements.

14. Cross‑reference to capital and prudential frameworks

    • Ensure reported OCL and Insurance Risk Charge figures reconcile to capital calculations required under GPS 115 and other capital standards referenced by APRA (Objective and paragraph 2). Coordinate actuarial, risk and finance teams to ensure consistency across prudential and financial reporting.

Following the above steps will align processes with the textual requirements of the Standard (paragraphs 3-19 and Specific instructions A and B). Practitioners should maintain a single compliance playbook that maps source paragraphs to internal procedures, assigns ownership (actuarial, finance, IT, audit, legal, compliance) and sets out evidence required for the Group Auditor’s limited assurance engagement. Where uncertainty remains (for example, acceptable digital certificate specifications or interpretation of consolidation adjustments), obtain clarification from APRA in writing to create an auditable record of the regulator’s instruction (paragraphs 5, 7, 9, 16).