The Standard organises reporting obligations around a handful of recurrent concepts that determine the granularity, basis and format of every data item life companies must provide.

Scope and entities: The Standard applies to all life insurance companies, including friendly societies, registered under the Life Act (paragraph 3). Definitions used by the Standard are drawn from Prudential Standard LPS 001 (paragraph 18(a)) and specific definitions are included in paragraph 18(b), for example the terms "Auditor" (appointment under paragraph 83 of the Life Act) and "financial year" (meaning in the Corporations Act 2001).

Reporting periods and frequency: The baseline is annual reporting in respect of the life company’s financial year on an unaudited basis (paragraph 7(a) and Note 1). APRA may require more or less frequent reporting for particular life companies by written notice (paragraph 8). Annual submissions are due within three months after the end of the reporting period (paragraph 9(a)), though APRA may specify different timing by notice (paragraph 9(b)) and may grant extensions in writing (paragraph 10).

Submission format and authorisation: Data must be submitted electronically using APRA’s website or other method notified by APRA (paragraph 6). Electronic submissions must be digitally signed by an officer or agent using a digital certificate acceptable to APRA (paragraph 14). The person submitting must be authorised by the Principal Executive Officer or the Chief Financial Officer (paragraph 15).

Quality control and audit involvement: The Standard mandates that reported information be the product of systems, processes and controls reviewed and tested by the Auditor (paragraph 11). That review/testing must occur annually or more frequently if necessary and must include at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance and Prudential Standard LPS 310 (paragraph 11(b)). Internal review and authorisation procedures are the responsibility of the Board and senior management (paragraph 12). Actuarial valuations and calculations must be in accordance with prudential standards (e.g. LPS 340) though reasonable estimates may be used where items will not be audited (paragraph 13).

Data model and content: The Standard supplies detailed reporting tables and definitions. Reporting is at the statutory fund or benefit fund level; data fields include policy and member counts, gross and reinsured insurance amounts, gross and reinsured contractual regular contributions and movement items (increases, decreases due to claims/maturities, decreases due to voluntary discontinuance, other movements), and a wide set of AASB 17 related metrics (IACF assets and liabilities, insurance contract liabilities/assets for remaining coverage and incurred claims, risk adjustments, investment contract liabilities, and reinsurance contract held equivalents). Tables specify units as whole Australian dollars and that particular value combinations must not appear on more than one row (General Instructions, Reporting Basis and Tables 1-3).

Accounting/actuarial integration: The Standard cross‑references prudential standards LPS 001, LPS 340 (valuation of policy liabilities), LPS 310 (audit and related matters), and Australian accounting standards, notably AASB 17. Measurement models (General Measurement Model, Premium Allocation Approach, Variable Fee Approach) are referenced in the reporting tables; the Variable Fee Approach is only applicable to certain measures (Tables 2 and 3 instructions).

Allocation constraints: While LRS 001’s allocation principles are to be used to allocate accounting numbers to APRA product groups, the Standard makes explicit that allocation principles cannot be used to allocate insurance and reinsurance assets and liabilities (and investment liabilities) across the components of the Life Act reporting structure , with LPS 340 providing further detail (General Instructions).

Transition and variability: The Standard requires firms to report under the old reporting standard for certain transitional reporting periods as defined in paragraph 17; APRA retains the discretion to vary requirements for individual firms (paragraphs 16-17).

Terminology and data integrity: Many reporting fields are defined precisely (General Instructions and multiple tables), e.g. "gross contractual regular contributions" (definition at G), "gross insurance amount, account balance or equivalent" with product-specific treatment, and IACF items which are directly tied to AASB 17 paragraphs and disclosure requirements. The document repeatedly instructs that liability positions should be reported as positive values for some fields and asset positions as positive values for others (Tables instructions).

Primary regulated parties: The Standard applies to "all life insurance companies including friendly societies" registered under the Life Act (paragraph 3). Practically, that includes the regulated legal entities that carry Australian life insurance business and the separate statutory funds those entities maintain. The reporting requirement is fund‑level: each statutory fund for a life insurer and each benefit fund for a friendly society must be reported on (Reporting basis sections that precede each table).

Senior officers and governing bodies: The Principal Executive Officer and Chief Financial Officer play direct control roles. A submission must be authorised by one of those officers (paragraph 15). The Board and senior management bear responsibility for ensuring internal policies and procedures exist for the authorisation of data submitted to APRA (paragraph 12). The Auditor (as defined in paragraph 18(a), i.e. appointed under paragraph 83 of the Life Act) must review and test the systems, processes and controls supporting the reporting, and must perform at least a limited assurance engagement each year (paragraph 11).

Actuaries and accounting teams: Actuarial valuations and calculations used in preparing reported information must comply with the prudential standards in force for the reporting period (paragraph 13). The Standard ties many reported items to AASB 17 concepts and to LPS 340 valuation requirements (General Instructions), so actuarial and accounting teams are directly affected by the definitional, measurement and allocation requirements.

IT and data teams: The Standard requires electronic submissions using APRA’s website or another method notified by APRA (paragraph 6), whole‑dollar reporting and specific table structures. Data models must deliver fund-level, whole-dollar outputs for multiple APRA product groups and AASB 17 items, together with controlled allocation logic for IACF items and for APRA product group reporting (General Instructions and tables). Data teams must ensure that "any specific combination of values in the table must not appear on more than one row" and follow field constraints (General Instructions).

Auditors and assurance providers: The Auditor must review and test the reporting controls and perform a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance and LPS 310 (paragraph 11). That creates a recurring scope for audit/assurance work specifically tied to APRA reporting controls and the mapping from accounting/actuarial systems to the reporting tables.

Reinsurers and counterparties: The Standard requires reporting of reinsurance contract held items (Tables 2 and 3), including assets/liabilities for incurred claims and for remaining coverage and IACF reinsurance items. Entities that participate in reinsurance arrangements will therefore see indirect effects in data collection and the timing/formatting of information required from third parties.

Regulatory and compliance functions: APRA itself is given discretion to vary reporting requirements or frequency for particular life companies (paragraphs 8 and 16). Compliance teams must therefore monitor APRA notices and be prepared to adapt to entity‑specific instructions.

Policy owners and external stakeholders: The Standard explicitly states that the information provided to APRA under this Reporting Standard need not be given to policy owners under section 124 of the Life Act and does not constitute a reporting document for section 124 purposes (paragraph 5). Thus, although the data is granular, the Standard does not create a policy-owner disclosure right.

Mandatory duties

• Submit prescribed information: A life company "must provide APRA with the information required by this Reporting Standard for each reporting period" (paragraph 4). The mandatory data fields and table structures are set out in the General Instructions and Tables 1-3.
• Submit in required format and by due date: Submissions must be electronic using APRA’s website or other APRA-notified method (paragraph 6). Annual information is due within three months after the end of the reporting period (paragraph 9(a)); APRA‑specified or entity‑specific timings may apply (paragraph 9(b)). APRA may grant extensions in writing (paragraph 10).
• Ensure audit review and limited assurance: The information "must be the product of systems, processes and controls that have been reviewed and tested by the Auditor" (paragraph 11). This includes review and testing on an annual basis or more frequently as necessary and at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance and Prudential Standard LPS 310 (paragraph 11(b)).
• Internal authorisation and board oversight: All information must be subject to systems, processes and controls developed by the life company for internal review and authorisation; the Board and senior management are responsible for ensuring appropriate policies and procedures are in place (paragraph 12).
• Use applicable prudential standards for actuarial items: Actuarial valuations and calculations included in or used to prepare the reported information must be in accordance with prudential standards in force for the reporting period (paragraph 13), with reasonable estimates allowed where items will not be audited.
• Digital signing and authorised submitter: Electronic submissions must be digitally signed using an APRA-acceptable digital certificate (paragraph 14). The submitting officer must be authorised by the Principal Executive Officer or the Chief Financial Officer (paragraph 15).

APRA rights and discretions

• Vary frequency and content per entity: APRA may change reporting periods or specify different reporting periods for a particular life company by written notice if it considers it necessary or desirable (paragraph 8).
• Specify submission methods and grant extensions: APRA can notify methods other than its website (paragraph 6(b)) and may grant extensions in writing (paragraph 10).
• Vary reporting requirements: APRA may vary the reporting requirements of the Standard in relation to individual life companies by written notice (paragraph 16).
• Transitional direction: The Standard requires reporting under the old standard for certain transitional reporting periods as defined in paragraph 17.

Rights or allowances embedded in the Standard

• Reasonable estimates allowed for unaudited items: While actuarial valuations must comply with prudential standards, "life companies may use reasonable estimates when preparing information that will not be audited" (paragraph 13).
• APRA-specified flexibility: APRA’s ability to vary frequency, content and submission methods grants flexibility where APRA determines it is necessary (paragraphs 6, 8, 16).
• Use of allocation principles with constraints: Life insurers must apply allocation principles in LRS 001 to allocate accounting numbers to APRA product groups, but they must not use allocation principles to allocate insurance and reinsurance assets and liabilities (and investment liabilities) across the components of the Life Act reporting structure; LPS 340 provides further direction (General Instructions).

Format, unit and mapping obligations

• Fund-level reporting: Data must be submitted at the statutory fund (life insurers) or benefit fund (friendly societies) level (Reporting basis statements for each table).
• Whole-dollar reporting and integer counts: Dollar values are to be reported in whole Australian dollars and policy/member counts as whole numbers (Tables instructions).
• Specific APRA product group mapping: The Standard prescribes the APRA product group values that must be used (Tables 1-3 instructions).
• Data uniqueness constraint: "Any specific combination of values in the table must not appear on more than one row in that table when reported" (General Instructions).

Board and executive accountability

• The Standard assigns responsibility to a life company’s Board and senior management to ensure appropriate policies and procedures for authorisation are in place (paragraph 12).
• Submissions must be authorised by a senior executive (paragraph 15) and electronically signed (paragraph 14).

The Reporting Standard itself prescribes reporting obligations, quality controls and authorisation requirements but does not set out its own penalty schedule within its text. The Standard is made under the Financial Sector (Collection of Data) Act 2001 (paragraph 1), and enforcement, compliance monitoring and any statutory penalties or administrative powers lie in that Act and in the Life Act rather than the Reporting Standard text. Accordingly:

• The Standard establishes mandatory procedural and substantive reporting duties (see paragraphs 4, 6-13, 14-15). Failure to comply will expose the reporting entity to APRA action under the statutory collection and enforcement powers contained in the Financial Sector (Collection of Data) Act 2001 and, as relevant, the Life Insurance Act 1995. The Standard itself does not enumerate fines, civil penalties or criminal offences; those consequences and APRA’s powers are contained in the parent legislation.
• APRA’s practical enforcement levers within the Standard include the ability to vary reporting frequency and content, to require additional submissions on written notice (paragraphs 8 and 16), and to specify submission methods (paragraph 6). These discretions allow APRA to require remediation or greater granularity for entities where it has prudential concerns.
• Administrative compliance obligations are reinforced by the Standard’s procedural requirements: the need for auditor review and at least a limited assurance engagement annually (paragraph 11), Board and senior management responsibility for authorisation policies (paragraph 12), and digital signing and executive authorisation of submissions (paragraphs 14-15). These both raise the cost of non‑compliance (in that non‑compliant submissions are readily identifiable) and create an audit trail for enforcement actions.
• APRA may grant extensions of due dates in writing (paragraph 10); conversely, APRA can issue notices requiring earlier or more frequent reporting (paragraphs 8 and 16). The Standard’s compliance architecture therefore sits within a flexible supervisory toolkit rather than within a fixed sanctions schedule.

For firms seeking the precise statutory penalties, administrative sanctions or criminal offences that might flow from non‑compliance, the relevant legislation to consult is the Financial Sector (Collection of Data) Act 2001 and the Life Insurance Act 1995. The Reporting Standard’s text signals APRA’s supervisory mechanisms (data prescription, auditor involvement, executive sign-off and digital authentication) and its discretion to require additional or altered reporting but does not itself set out penalty amounts or enforcement procedures.

The Standard is integrative: it references and depends on other prudential standards, accounting standards, the Life Act, and the Financial Sector (Collection of Data) Act 2001. The instrument itself makes explicit cross‑references that determine measurement bases, definitional scope and the institutional allocation of responsibilities.

Statutory authority and parent Acts:

• The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). That Act provides APRA’s statutory power to collect data; enforcement and penalties relating to data collection are governed by that Act (not further detailed in the Standard).
• The Standard applies to entities registered under the Life Insurance Act 1995 (paragraph 3) and uses terminology and fund structures derived from that Act. It explicitly notes that reporting under this Standard is not required to be given to policy owners under s 124 of the Life Act and does not constitute a reporting document for s 124 (paragraph 5).

Prudential standards:

• Definitions are taken from Prudential Standard LPS 001 (paragraph 18(a)). LPS 001 thereby supplies the definitional backbone for many terms used in the tables.
• Audit and assurance requirements are aligned with Prudential Standard LPS 310 (paragraph 11(b)). The Auditor’s limited assurance engagement must be consistent with professional auditing standards to the extent not inconsistent with LPS 310.
• Valuation of policy liabilities is aligned with Prudential Standard LPS 340. The General Instructions direct readers to LPS 340 for valuation requirements and for the treatment of friendly societies. The Standard also instructs that allocation principles cannot be used to allocate insurance and reinsurance assets/liabilities across the Life Act reporting structure and refers to LPS 340 for details (General Instructions).

Australian accounting and auditing standards:

• The reporting fields map to AASB 17 concepts. Many table items expressly reference AASB 17 paragraphs and disclosure items: IACF items are defined as recognised applying AASB 17 paragraph 28B, and the IACF asset/liability disclosures refer to AASB 17.105A/105B (General Instructions I section). Insurance contract liabilities/assets for remaining coverage and for incurred claims are required to be reported in the form set out in AASB 17 Appendix A and other AASB 17 disclosure sections (General Instructions). Risk adjustment concepts are those in AASB 17 Appendix A and the referenced AASB paragraphs (General Instructions).
• The Auditor’s engagement and the limited assurance standard must be consistent with Auditing and Assurance Standards Board professional standards and guidance notes where not inconsistent with LPS 310 (paragraph 11(b)).

Corporations Act and other corporate law:

• The Standard uses the Corporations Act 2001 definition of "financial year" for the reporting period (paragraph 18(b)). Corporate governance obligations remain applicable to life companies subject to the Corporations Act and the Life Act; the Standard imposes additional specific authorisation and board responsibilities (paragraphs 12 and 15).

Reinsurance and contract law:

• The Standard requires reporting of reinsurance contract held items and reinsured amounts (Tables 2 and 3; R section definitions). Those items will depend on reinsurance arrangements documented under contract law; the Standard does not alter reinsurance contractual rights but requires disclosure of balances and risk adjustments consistent with AASB 17 and prudential standards.

Interactions and potential friction points:

• Allocation rules: LRS 001 allocation principles must be used to allocate accounting numbers to APRA product groups, but allocation cannot be used to allocate insurance and reinsurance assets and liabilities across the Life Act reporting structure (General Instructions). Firms must reconcile their accounting/actuarial systems to both LRS 001 allocation requirements and the constraints imposed by LPS 340.
• AASB 17 interpretation differences: several items refer to insurer interpretation of AASB 17 (e.g. the IACF item "may not apply based on the insurer’s interpretation of AASB 17.105A" in the I definitions). Where AASB 17 allows alternative treatments or judgement, insurers must document the interpretation used and ensure consistent mapping to the reporting tables.
• Auditor obligations and LPS 310: the interaction between the Auditor’s duties under the Life Act (appointment under paragraph 83 of the Life Act as per the definition in paragraph 18(a)), prudential audit expectations in LPS 310, and Auditing and Assurance Standards Board guidance must be managed. The Standard ties the assurance requirement to both prudential and professional auditing standards.
• Data privacy and disclosure law: paragraph 5 expressly states the APRA reporting content need not be provided to policy owners under s 124 of the Life Act. That fixes the reporting as supervisory, not policy-owner disclosure, but data protection and confidentiality obligations under other laws remain relevant should APRA or a firm disclose reported data.

In short, LRS 400.0 sits in a network of prudential, accounting and corporate law. It maps APRA’s data needs onto AASB 17 accounting constructs, LPS 340 valuation rules and LPS 310 audit expectations, while being grounded in APRA’s statutory data collection power under the Financial Sector (Collection of Data) Act 2001 and the Life Act registration regime.

The text provided sets out a limited amendment/commencement history within the instrument itself:

• Commencement and application date: The Standard applies for reporting periods ending on or after 1 July 2023 (paragraph 3). That is the principal commencement marker embedded in the text.
• Transitional arrangements: Paragraph 17 provides a transitional rule requiring life companies to report under the "old reporting standard" in respect of transitional reporting periods. "Old reporting standard" is defined as the reporting standard revoked in the determination making this Reporting Standard; "transitional reporting period" means a reporting period under the old standard which ended before 1 July 2023 and in relation to which the life company was required under the old standard to report by a date on or after the date of revocation of the old reporting standard (paragraph 17). The Note to paragraph 17 clarifies that overdue reporting obligations under the old standard remain enforceable if due before revocation.
• Revocation context: The Standard itself refers to a determination making this Reporting Standard and thereby revoking the prior reporting standard; the text does not include the revocation instrument or its date beyond the implication that revocation occurred as part of making this Standard (paragraph 17).
• No further amendments recorded in the instrument: The provided text does not list subsequent amendments, modifications, or a schedule of changes beyond the commencement date and transitional provision. The Standard repeatedly states that references to Acts, Prudential Standards, Reporting Standards, Australian Accounting or Auditing Standards are references "as in force from time to time" (paragraph 19), which implicitly allows the reporting Standard to operate in a dynamic regulatory environment as other instruments are updated (paragraph 19).

Practically, for a reporting entity the key change relating to amendment history is the shift to this Standard’s requirements effective for reporting periods ending on/after 1 July 2023, and the need to comply with transitional rules for earlier reporting periods where applicable (paragraph 17). Auditors and compliance teams should also note the ongoing cross‑references to prudential and accounting standards "as in force from time to time" (paragraph 19), meaning measurement and disclosure expectations will evolve as those referenced standards are amended.

If a practitioner requires a formal legislative amendment history (dates of determinations, revocation instrument references, or prior standard texts), those items sit outside this text and must be located in APRA’s determinations, Federal Register of Legislation entries, or APRA policy release material that records the revocation and replacement of the prior reporting standard.

The Reporting Standard text contains no references to litigation, judicial decisions or precedent. It does not cite cases, and it does not record any court or tribunal challenges. The instrument is a statutory/regulatory reporting requirement rather than a judicial instrument, and the text itself makes no mention of litigation history.

Consequently:

• There are no cases cited or described within the Standard that construe its provisions or that interpret its obligations.
• Any disputes arising from the application, validity or enforcement of this Reporting Standard (for example, challenges to APRA notices changing reporting periods or disputes about APRA’s exercise of discretion) would be matters for external legal proceedings; none are referenced here.
• For practitioners wanting to know whether subordinate reporting standards have been litigated, one must search external legal databases, tribunal records, or APRA enforcement history; that material is not present in the Standard itself.

This section therefore records the absence of litigation references in the instrument and advises the reader to consult external sources for any jurisprudence or enforcement litigation that may have taken place since the Standard’s adoption.

Several practical and legal pitfalls are embedded within the Standard’s drafting and the way it links to other instruments. These are points where firms commonly make errors or face implementation friction, and they are supported by the Standard’s own text.

1. Fund-level reporting obligation:

   • Reporting is explicitly required at the statutory fund (life insurers) or benefit fund (friendly societies) level (Reporting basis for Tables 1-3). Firms that aggregate across funds risk non‑compliance.

2. Whole-dollar and integer requirements:

   • The tables require whole Australian dollars and whole number counts for policies and members (multiple table notes). Rounding, scaling or presentation in thousands without conversion will breach the stated units.

3. Submission format, digital signature and authorised submitter:

   • Electronic submissions must be digitally signed using a digital certificate acceptable to APRA, and the person submitting must be authorised by the Principal Executive Officer or the Chief Financial Officer (paragraphs 14-15). Delegation chains must be formalised and certificates maintained; failure to use an APRA-acceptable certificate or not having PEO/CFO authorisation will create procedural non‑compliance.

4. Unaudited baseline but auditor testing required:

   • The Standard requires annual auditor review and at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance and LPS 310 (paragraph 11). Firms sometimes assume unaudited reporting means no auditor involvement; the Standard explicitly requires auditor review and testing of controls supporting the reporting.

5. Actuarial valuation linkage and reasonable estimates:

   • Actuarial valuations must comply with prudential standards (paragraph 13) but reasonable estimates may be used when items will not be audited. Firms must carefully document where estimates are used and why, and they should ensure any audited items meet the applicable actuarial prudential standard (e.g. LPS 340).

6. Allocation constraints:

   • Allocation principles from LRS 001 must be used, but allocation cannot be applied to allocate insurance and reinsurance assets and liabilities (and investment liabilities) across the Life Act reporting structure (General Instructions). Misapplying allocation rules across Life Act components will breach the Standard.

7. Mapping to AASB 17 and interpretative space:

   • Several reported items map directly to AASB 17 disclosures and definitions (General Instructions and I/R section definitions). The Standard notes that some items "may not apply based on the insurer’s interpretation of AASB 17.105A." Where AASB 17 leaves judgement, organisations must maintain documented positions supporting their mapping. Different interpretations across firms can result in inconsistent APRA data unless documented.

8. Data uniqueness and table constraints:

   • "Any specific combination of values in the table must not appear on more than one row" (General Instructions). This imposes strict data-model uniqueness rules that can trip up report generation if product-group or class-of-business mapping overlaps.

9. APRA discretion and entity-specific notices:

   • APRA can change reporting frequency and content for particular life companies (paragraphs 8 and 16). Firms with complex business models may be subject to more frequent or tailored reporting at APRA’s discretion; firms must monitor for written notices and be able to respond quickly.

10. Transitional reporting and overlap with old standard:

    • Paragraph 17 requires reporting under the old reporting standard for certain transitional reporting periods. Confusion can arise if firms assume the new Standard displaced all old obligations immediately. The Note to paragraph 17 clarifies that overdue reports under the old standard remain due.

11. Repeated/duplicated text in source material:

    • The provided instrument contains repeated sections and duplicated table text. While that does not change obligations, it increases the risk of reading inconsistencies. Practitioners should rely on APRA’s published data dictionary and formal determination text to ensure the authoritative version.

12. Board and executive authorisation obligations:

    • The Board and senior management must ensure policies and procedures are in place for authorisation of data submitted to APRA (paragraph 12). Operational teams often overlook formal Board‑level delegations and authorisation protocols; audits will look for documented policies and evidence of compliance.

13. IACF allocation and AASB 17 interaction:

    • Insurance acquisition cash flows (IACF) assets/liabilities and related allocation to APRA product groups must be based on a "systematic and rational approach reflecting how each APRA product group contributed" (I definitions). That requires careful cost allocation methodology documentation consistent with both AASB 17 and APRA’s reporting mapping.

Each of these "gotchas" maps back to specific text in the Standard (see paragraphs 3, 4, 6, 7-13, 14-16, 17 and the General Instructions and tables). Firms should treat the Standard not as a financial-statement reconciliation exercise only, but as a data, controls, governance and audit exercise that reaches into actuarial, accounting, IT and executive governance domains.

Compliance requires coordinated work across governance, actuarial, finance, IT, audit and legal functions. The following is a practical compliance checklist mapped to the Standard’s requirements and the tables it prescribes.

1. Governance and delegations

   • Ensure the Board has approved policies and procedures for the internal review and authorisation of data submitted to APRA as required by paragraph 12.
   • Document the delegation to the authorised submitter(s): maintain formal written authorisation from the Principal Executive Officer or Chief Financial Officer for individuals who will submit reports (paragraph 15).
   • Maintain a register of APRA‑acceptable digital certificates and the individuals they are assigned to; ensure arrangements for certificate renewal and secure storage (paragraph 14).

2. Data model and mapping

   • Map statutory and benefit funds precisely: reporting is fund-level for statutory funds (life insurers) and benefit funds (friendly societies) as per each table’s Reporting basis.
   • Implement APRA product group mapping consistent with the table values (Tables 1-3). For friendly societies, use the F1-F6 codes; for other life companies use the L1-L19 equivalents as listed.
   • Ensure whole-dollar reporting and whole-number policy/member counts: adjust ETL and reporting logic to deliver integer outputs per the tables.
   • Enforce uniqueness constraints in table rows so "any specific combination of values" does not appear more than once (General Instructions).

3. Accounting and actuarial alignment

   • Align actuarial valuation processes with LPS 340 for policy liabilities and ensure the actuarial valuation methodology is the source for reported policy liability items (see paragraph 13 and General Instructions referencing LPS 340).
   • For AASB 17 related items (IACF, remaining coverage, incurred claims, risk adjustments), map the firm’s AASB 17 prepared balances and disclosure lines to the reporting table fields. Document interpretations, especially where AASB 17 afford choices (the Standard notes some items may not apply based on insurer interpretation).
   • If using the Variable Fee Approach, limit its application to the measures the Standard allows (Tables 2 and 3 instructions).

4. Auditor and assurance

   • Engage the Auditor to review and test systems, processes and controls supporting the reporting on an annual basis or more frequently (paragraph 11).
   • Establish the scope of a limited assurance engagement in line with Auditing and Assurance Standards Board guidance and Prudential Standard LPS 310 (paragraph 11(b)).
   • Provide the Auditor with documentation of data flows, reconciliations from financial statements and actuarial valuations to reported APRA fields, and evidence of internal authorisation and sign-off.

5. IT, processes and controls

   • Build or adapt reporting extracts that capture the required fields in Tables 1-3 at fund level and in whole dollars.
   • Implement input controls and exception reporting to capture unusual movements (e.g. large contribution decreases due to claims or maturities, reinsured amounts).
   • Maintain an audit trail of who authorised and digitally signed each submission and the APRA acceptance records.

6. Documentation and policies

   • Maintain a detailed reporting mapping document showing: source ledger/accounting/actuarial line → APRA table field → APRA product group mapping logic → rounding and presentation rules.
   • Document allocation methodologies used to allocate IACF amounts across APRA product groups; ensure they are "systematic and rational" as required in the definitions.
   • Keep versioned documentation explaining where reasonable estimates were used for unaudited items and the rationale, per paragraph 13.

7. Scheduling and operational readiness

   • Calendar reporting deadlines: the baseline due date is three months after the financial year end (paragraph 9(a)). Build time for actuarial valuations, internal review, auditor testing and executive authorisation into the schedule.
   • Prepare for APRA notices that alter reporting frequency or content (paragraphs 8 and 16). Maintain capacity to produce more frequent or tailored reports on short notice.

8. Testing and dry runs

   • Run full reporting dry runs at least once before first live submission under this Standard, including digital signing and the authorised submitter workflow.
   • Have the Auditor perform a controls testing dry run as part of the limited assurance engagement.

9. Transition handling

   • Identify any disclosures that fall under the transitional reporting period definition (paragraph 17) and ensure that old-standard reporting obligations are fulfilled where applicable. Keep records showing which periods are governed by old‑standard submissions.

10. Regulatory engagement and change control

• Maintain a point of contact for APRA notices. Track any APRA variations given to the firm (paragraphs 8 and 16) and record them in a change log.
• Keep legal/compliance counsel engaged to interpret APRA notices, and to determine whether any deviations or exceptions require further Board-level approvals or disclosures.

11. Reinsurance mapping

• Ensure reinsurance balances and risk adjustments are captured correctly (Tables 2 and 3). Reconcile reinsured insurance amounts and IACF reinsurance items with reinsurance accounting/contract documents.

12. Record retention

• Retain detailed working papers, reconciliations and Auditor working papers that demonstrate the reported numbers are supported by the company’s accounting and actuarial records, and by the Auditor’s assurance procedures.

Practical note on resources and timelines: implementing the reporting Standard will typically require co‑ordination across actuarial, finance, IT and audit teams. The auditor’s limited assurance engagement must be planned and budgeted in advance to meet reporting timelines, and the firm must ensure PEO/CFO authorisation and appropriate digital certificate infrastructure are in place before submission.

Follow APRA’s published guidance: practitioners should supplement the Standard with APRA’s data dictionaries, technical filing guides and any sector circulars that clarify the mapping of granular AASB 17 items to APRA fields. Those materials will typically contain the precise accepted file formats, error codes, and APRA system requirements for electronic submission referenced in paragraph 6.