The document organises reporting around three Operational Risk Charge categories and a set of data controls and submission mechanics. The central conceptual elements are:

• Operational Risk Charge categories: The tables and definitions require reporting under three business buckets used to calculate Operational Risk Charges:
  • ORCR: Operational Risk Charge for risk business (items 1.1-1.3);
  • ORCI: Operational Risk Charge for investment-linked business (items 2.1-2.4);
  • ORCO: Operational Risk Charge for other business (items 3.1-3.4). These categories are set out in Table 1 and the Definitions table for the corresponding data fields.
• Key data fields: For each category APRA requires a combination of accrued premiums, adjusted policy liabilities (gross and/or net of reinsurance), and gross claim payments for the 12 months ending on the reporting date. Specific items require values at the reporting date and, for some items, at the date 12 months prior to the reporting date (see Item 1.2, Item 2.2, Item 3.2 and related notes in the Specific instructions).
• Linkage to prudential measurement standards: Several definitions are not defined in the Reporting Standard itself but reference other prudential standards. For example, “accrued premium” is defined in Prudential Standard LPS 118 (see Definitions and the Definitions table). “Adjusted policy liabilities” are determined in accordance with Prudential Standard LPS 112 (Definitions table). The Reporting Standard must therefore be read in conjunction with LPS 118, LPS 112 and LRS 001 (paragraph 1; Objective and opening paragraphs).
• Data quality and assurance regime: The information must derive from systems, processes and controls reviewed and tested by the company Auditor (paragraph 11). The Auditor’s work must be at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance, insofar as those guidance notes are not inconsistent with LPS 310 (paragraph 11(b)). The Board and senior management of the life company have responsibility to ensure policies and procedures for authorisation of data submitted to APRA are in place (paragraph 12).
• Submission mechanics and authorisation: Electronic submission is mandatory via APRA’s electronic methods or another APRA-notified method (paragraph 6). Electronic submissions require digital signing using an APRA-acceptable digital certificate (paragraph 14). The officer or agent who submits must be authorised by the Principal Executive Officer or the Chief Financial Officer (paragraph 15).
• Timing and frequency: Standard reporting frequency is quarterly (unaudited) and annually (audited), with specific due-dates: quarterly within 20 business days after the period end; annual within three months after the period end (paragraph 9). APRA may change reporting periods for an individual life company (paragraph 8), or grant extensions in writing (paragraph 10).
• Application scope and commencement: Applies to all life companies registered under the Life Act and commences for reporting periods ending on or after 1 July 2023 (paragraph 3).
• Transition and variation mechanisms: Transitional reporting under the old reporting standard is required for certain reporting periods as defined (paragraph 17), and APRA may vary the reporting requirements by written notice to a particular life company (paragraph 16).

These concepts structure the compliance task: map statutory funds to the three ORC categories, extract accrued premium and adjusted liabilities according to LPS 118 and LPS 112, ensure systems produce whole-AUD values at specified dates, implement auditor-reviewed controls and digital sign and authorise submissions within the stated timeframes.

The Standard applies to "all life insurance companies including friendly societies" registered under the Life Insurance Act 1995 (paragraph 3). Practically this implicates:

• Life insurers operating statutory funds: For life insurers with multiple statutory funds, reporting is required at the level of each statutory fund (Specific instructions: Reporting basis). The granular statutory fund-level requirement increases volume and may require separate data extraction and validation per fund.
• Friendly societies: For friendly societies the reporting obligation is at the management fund level (Specific instructions: Reporting basis).
• Auditors of life companies: Paragraph 11 requires the Auditor appointed under paragraph 83 of the Life Act (Definition: Auditor in paragraph 18(b)) to review and test systems, processes and controls and to perform at least a limited assurance engagement. This imposes an audit workload beyond standard financial statement audit tasks for auditors of life companies.
• Senior management and boards of life companies: The Board and senior management are responsible for ensuring policies and procedures for internal review and authorisation of data submitted to APRA are in place (paragraph 12). The Principal Executive Officer and Chief Financial Officer play specific signatory roles by authorising the officer or agent who submits the data (paragraph 15).
• Actuaries and actuarial functions: The Standard mandates that actuarial valuations and calculations used in reported information must be in accordance with the prudential standards in force for the reporting period (paragraph 13). This makes actuarial teams directly responsible for producing or validating LPS 112 and LPS 118 derived figures used in reporting.
• IT, data and compliance teams: The requirement for data to be submitted in electronic format using APRA’s methods (paragraph 6), the need to provide whole AUD values and to report at specific dates, and the auditor review of systems (paragraph 11) create a compliance burden for data extraction, transformation and submission teams.
• Reinsurance functions: Several items require reporting “net of reinsurance” or “gross of reinsurance” depending on the item (Definitions table). Reinsurance accounting and data feeds must therefore be correctly mapped into reporting templates.
• Policy owners: The Standard explicitly states the information reported is not required to be given to policy owners under s 124 of the Life Act and does not constitute a reporting document for that purpose (paragraph 5). This means policy owners are not a direct regulatory recipient of the reported datasets under this Standard.
• APRA: As the recipient and determiner of reporting methods and variations, APRA is the decision-maker about format, frequency and possible variations (paragraphs 6, 8, 16). APRA will use the data for prudential supervision and capital adequacy assessment (paragraph 2).

Who pays: the compliance, audit, actuarial and systems costs fall to each life company. Auditors and external service providers will receive fees for limited assurance engagements and system testing. Who decides: APRA defines the required items and submission mechanics, but the life company's board, CEO/PEO and CFO must approve and authorise submissions.

Duties imposed on life companies and their officers are specified and structured; the Standard does not enumerate rights in the human-rights sense but sets procedural entitlements such as extension of due dates and APRA’s discretion. Key duties:

• Submission duty: A life company must provide the information required by the Reporting Standard for each reporting period (paragraph 4). This is an ongoing periodic reporting obligation.
• Method of submission: Provide the information electronically via APRA’s electronic method or another APRA-notified method (paragraph 6).
• Timing duty: Submit quarterly unaudited data and annual audited data, with prescribed due dates: quarterly within 20 business days after period end; annual within three months after period end (paragraph 7 and paragraph 9).
• Data content and format duty: Report items listed in Table 1 at the statutory fund or management fund level, in whole Australian dollars and as at the reporting date (Specific instructions; Units of measurement).
• Data quality and testing duties: Ensure information is produced by systems, processes and controls reviewed and tested by the Auditor (paragraph 11). The Auditor must perform an annual review or more frequently if needed and undertake at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance insofar as consistent with LPS 310 (paragraph 11(b)). The Board and senior management must ensure appropriate policies and procedures for internal review and authorisation are in place (paragraph 12).
• Actuarial conformity duty: Actuarial valuations and calculations used in reported information must comply with prudential standards in force for the reporting period (paragraph 13). For unaudited submissions within a year, reasonable estimates may be used (paragraph 13).
• Authorisation and digital signing duties: Electronic submissions must be digitally signed with a certificate acceptable to APRA (paragraph 14), and the submitting officer must be authorised by the PEO or CFO (paragraph 15).
• Transitional duty: Report under the old reporting standard for transitional reporting periods as defined (paragraph 17).
• Respond to APRA variation notices: If APRA issues a written notice changing reporting periods or specifying different reporting periods, the life company must follow the notice (paragraph 8). APRA may also vary reporting requirements for a particular life company by written notice (paragraph 16).

Entitlements and APRA discretions stated in the Standard:

• Extension of due date: APRA may, in writing, grant an extension of a due date (paragraph 10).
• APRA’s power to adjust reporting frequency: APRA may change reporting periods or specify different reporting periods for a particular life company if it considers necessary or desirable (paragraph 8).
• APRA may vary reporting requirements: Paragraph 16 allows APRA to vary reporting requirements in relation to a particular life company by notice in writing.

Notable absences in the Standard about duties and rights:

• The Standard does not set out civil penalties, criminal offences or explicit enforcement mechanisms within the text provided. It prescribes reporting, authorisation and audit requirements but leaves enforcement and sanction mechanics to APRA’s broader regulatory framework; see the Penalties and enforcement section below for how the Standard treats enforcement and where the instrument is silent.

Who decides and who must act: APRA decides the content, format, frequency and can vary or extend; company boards, senior management, PEO/CFO and the Auditor must put in place controls, prepare and authorise the data, and ensure audit review.

The Reporting Standard itself does not specify penalty amounts, criminal offences or direct enforcement sanctions in the text provided. The instrument focuses on reporting obligations, submission mechanics and quality control requirements. Relevant points drawn from the Standard:

• No explicit penalties in the text: The Standard prescribes mandatory duties (for example, the duty to submit information under paragraph 4 and deadlines in paragraph 9) but does not in the contained provisions set out civil penalties or criminal sanctions for failure to report or for incorrect reporting. Therefore, within the text provided there are no specific pecuniary penalties or infringement notices defined.
• APRA’s supervisory and discretionary mechanisms: The Standard gives APRA express powers to vary reporting frequency (paragraph 8) and vary reporting requirements by written notice in relation to a life company (paragraph 16). While these are not penalties, they are supervisory mechanisms that can increase regulatory demands on particular firms.
• Administrative relief: APRA may grant an extension of a due date in writing (paragraph 10). This is an administrative discretion that can relieve immediate compliance pressure when exercised.
• Audit and assurance obligations as an enforcement lever: The requirement that an Auditor review and test systems, and provide at least a limited assurance engagement (paragraph 11), imports professional audit standards and obligations that generally involve auditor reporting obligations under LPS 310 and auditing standards. While this Standard does not itself specify consequences of adverse auditor findings, those findings feed into APRA’s supervisory processes.
• Implicit enforcement through referenced laws and standards: The Reporting Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). That parent Act and the Life Insurance Act 1995 contain provisions and regulatory mechanisms governing APRA’s data collection powers and enforcement. The Standard’s silence on sanctions should therefore be read together with the legal framework granting APRA powers under the Financial Sector (Collection of Data) Act and other prudential standards. The Standard also cross-references Prudential Standard LPS 310 Audit and Related Matters and capital adequacy standards; non-compliance with those prudential standards can attract APRA’s regulatory measures under the Life Act and APRA’s general powers.
• Practical enforcement pathways: In practice, failure to report, misreporting or deficient systems that produce unreliable data will likely trigger APRA supervisory engagement, requests for remediation, directions under the Life Act and potentially public action or licences conditions, on the basis of the broader APRA regulatory framework even if this Reporting Standard does not itself create a penalty regime.

Users must therefore treat the Standard as prescribing mandatory reporting steps and quality obligations while recognizing that enforcement and sanctions are administered through APRA’s broader statutory powers under the Financial Sector (Collection of Data) Act 2001 and the Life Insurance Act 1995 as well as the prudential standards that are cross-referenced. The Standard explicitly preserves APRA’s discretion to vary reporting requirements and periods (paragraphs 8 and 16), which is an instrument of supervisory control rather than a stand-alone penalty mechanism.

LRS 118.0 is designed to sit inside APRA’s prudential framework and explicitly references several other instruments. The interactions are operational rather than declarative:

• Financial Sector (Collection of Data) Act 2001: The Standard is made under section 13 of that Act (paragraph 1). That Act is the statutory grant of power for APRA to collect data; enforcement and other data-collection consequences will be governed by that Act as the enabling statute.
• Life Insurance Act 1995 (Life Act): The Standard applies to life companies registered under the Life Act (paragraph 3). The Auditor referred to in the Standard is "an auditor appointed under paragraph 83 of the Life Act" (paragraph 18(b)); the Standard therefore ties auditor duties back to the appointment mechanisms within the Life Act.
• Prudential Standard LPS 118 Capital Adequacy: Operational Risk Charge (LPS 118): The Reporting Standard must be read in conjunction with LPS 118; accrued premium is defined in LPS 118 and the reporting items are the data inputs used to calculate the Operational Risk Charge under LPS 118 (Objective and multiple references).
• Prudential Standard LPS 112 Capital Adequacy: Measurement of Capital (LPS 112): Adjusted policy liabilities used in reporting are to be determined in accordance with LPS 112 (Definitions table and Specific instructions). Several items call for adjusted policy liabilities gross or net of reinsurance, referencing LPS 112 calculations.
• Reporting Standard LRS 001 Reporting Requirements: LRS 118 must be read in conjunction with LRS 001, including the general instruction guide and Attachment A (Objective and paragraph 1; paragraph 18(b) definitions). LRS 001 contains the general instruction guide, which determines reporting formats, file layouts and metadata likely required for submission.
• Prudential Standard LPS 310 Audit and Related Matters: The Standard requires that annual audited information be submitted with the annual auditor’s report as required under LPS 310 (Note 2 to paragraph 7). Paragraph 11(b) also requires the Auditor to perform at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance insofar as not inconsistent with LPS 310, creating an interaction between auditing standards and prudential audit requirements.
• Corporations Act 2001: "Financial year" is defined as in the Corporations Act 2001 (paragraph 18(b)), which affects timing and the reporting year definitions.
• Australian Accounting and Auditing Standards: Paragraph 19 cross-references Australian Accounting or Auditing Standards, indicating that where such standards apply they are to be read as in force, unless a contrary intention appears.

Consequences of these interactions:

• Compliance is not discrete. Companies cannot prepare LRS 118.0 returns without ensuring their LPS 118 and LPS 112 computations are completed correctly. The data required is an extraction of prudential and actuarial measures defined elsewhere.
• Audit and assurance linkage: The auditor’s engagement must meet requirements of LPS 310 and existing auditing standards. This elevates audit involvement beyond a mere check of completeness to a systems and controls review in line with auditing guidance.
• Definitions and variation: The Standard uses definitions from LPS 001 and other prudential instruments; changes to those instruments over time will change the meaning of terms in this Standard (paragraph 19).
• Administrative discretion and supervisory overlay: APRA may vary reporting periods or requirements for particular firms (paragraphs 8 and 16). That discretionary power interacts with firms’ compliance planning and systems investments.
• Transitional interplay: The transitional provisions require companies to report under the old standard for specified transitional reporting periods (paragraph 17), creating a need to manage dual architectures or mappings if revocation timing overlaps reporting due dates.

In short, LRS 118.0 is not self-contained; it imports definitional, measurement and audit standards from other prudential instruments and the Corporations Act, placing obligations on life companies to align actuarial, accounting, audit and reporting processes across that regulatory stack.

The text provided contains limited explicit amendment record information. From what the instrument states:

• Commencement: The Standard applies for reporting periods ending on or after 1 July 2023 (paragraph 3). That is the effective commencement for reporting obligations under this instrument.
• Transition: Paragraph 17 provides transitional arrangements for reporting periods under the "old reporting standard" that ended before 1 July 2023 but were required to be reported on or after the date the old reporting standard was revoked. The Standard defines "old reporting standard" and "transitional reporting period" for that purpose and instructs life companies to comply with the old standard for those transitional periods. The note clarifies that overdue reports due before revocation are still required under the old standard.
• Revocation implied: The transition clause (paragraph 17) indicates that an earlier reporting standard was revoked when this Standard was made. The Standard does not reproduce the text of the revocation or the date of revocation; it simply sets rules for transitional reporting where prior obligations overlapped the revocation date.
• Incorporation of future changes: Paragraph 19 provides that references to Acts, Prudential Standards, Reporting Standards, Australian Accounting or Auditing Standards are references to those instruments "as in force from time to time." This means that amendments to referenced standards will automatically affect the operation of this Reporting Standard without the need to amend the Reporting Standard itself.
• Variations by APRA to individual firms: Paragraphs 8 and 16 permit APRA to change reporting periods or vary reporting requirements for particular life companies. Those are firm-specific variations rather than amendments to the Reporting Standard as a whole, but they function as operational amendments in relation to particular entities by written notice.

The text does not list prior versions, dates of instrument-making, or legislative amendment entries within the document provided. To construct a complete amendment ledger one would need the APRA determinations or Federal Register of Legislation entries that record the instrument’s making, revocation of the prior standard and any subsequent determinations. The Standard itself, however, embeds continuity by deferring to current versions of the instruments it references (paragraph 19), and it contains transitional and variation mechanics to manage changes at the firm or system level.

The material supplied contains no references to judicial or tribunal decisions, appeals, or litigation arising from this Reporting Standard. The Standard does not cite any cases and does not include any judicial interpretations. Therefore, within the four corners of the provided text:

• There is no litigation history recorded in the instrument.
• No cases are named or relied upon to interpret the requirements.
• No appeals mechanism against APRA’s use of the reported data or its exercise of variation powers is identified in the Standard itself.

For entities seeking the operational impact of any disputes, the appropriate sources to consult would include APRA's broader policy statements and any case law arising from enforcement action under the Financial Sector (Collection of Data) Act 2001 or the Life Insurance Act 1995. Those are not present in this Standard, which is purely a data-collection instrument with audit and systems obligations.

Practical traps and subtle compliance points apparent from the Standard text that can catch in-house counsel, compliance and actuarial teams:

• Five submissions per year: The Standard’s note that reporting will be submitted five times for a full financial year (Note 1 to paragraph 7) can surprise teams expecting four quarterly plus one annual to be redundant. The Standard expressly treats the annual audited submission as separate from the quarterly unaudited submissions. Operational workflows must accommodate that cadence.
• Differing dates for some items: Several adjusted policy liabilities must be reported at the date 12 months prior to the reporting date (Item 1.2, Item 2.2, Item 3.2). This requires storage or reconstruction of balance sheet positions at 12 months prior and may complicate systems that typically capture only current-period snapshots.
• Statutory fund level granularity: The Specific instructions require reporting at each statutory fund for insurers and at the management fund for friendly societies. Companies with numerous statutory funds must map data to multiple reporting units rather than producing a consolidated group return.
• Gross versus net of reinsurance mix: Items require a mix of gross and net reporting for adjusted policy liabilities and claims. Accurate mapping of reinsurance recoverables and ceded premium data is essential to avoid misreporting.
• Audit expectations are not purely sign-off: Paragraph 11 requires the Auditor to review systems, processes and controls and to perform at least a limited assurance engagement. This is not a mere reconciliation; it is an evidence-rich controls assurance exercise that will require documentable controls over data extraction, transformations and aggregations.
• Estimates permitted only for unaudited submissions: Paragraph 13 allows "reasonable estimates" for information that will not be audited (i.e. the first four submissions for a full financial year), but requires actuarial valuations and calculations used in preparation of the information to be in accordance with prudential standards. Companies must ensure that estimates are defensible and that audited submissions ultimately meet full prudential-standards-based valuation requirements.
• Digital signature and authorisation tied to named roles: Electronic submissions must be digitally signed with a certificate acceptable to APRA (paragraph 14) and the submitting officer must be authorised by the Principal Executive Officer or Chief Financial Officer (paragraph 15). This creates procedural controls and potential single-point failure risk if the named officers are unavailable; companies should plan delegation protocols consistent with the Standard and any APRA guidance.
• APRA variations and targeted demands: APRA may change reporting periods or specify different reporting periods for a particular life company (paragraph 8) and may vary reporting requirements by written notice (paragraph 16). This gives APRA discretion to increase reporting frequency or content for a particular firm, which can create sudden compliance resource demands.
• Not a policy-owner disclosure: Paragraph 5 makes clear the data reported is not required to be given to policy owners under s 124 of the Life Act. Companies must maintain internal confidentiality and cataloguing of what is internal regulatory reporting versus owner-facing communications.
• Units in whole Australian dollars: The Specific instructions require whole Australian dollars, which eliminates decimal rounding but requires consistent rounding policies to avoid aggregation differences.
• Reliance on other prudential standards for definitions and calculations: Accrued premium and adjusted policy liabilities are defined in LPS 118 and LPS 112 respectively. Changes in those prudential standards change the required calculations for reporting; companies need processes to track amendments to LPS 112, LPS 118, LPS 001 and LRS 001.
• Transitional reporting window traps: Paragraph 17 requires reporting under the old standard for specified transitional periods. If a company had a reporting period ending before 1 July 2023 but due after revocation of the old standard, the company must still report under the old standard. This can lead to dual-format submissions if revocation timing is not managed carefully.
• Absence of prescribed penalties in the Standard: The instrument does not set out penalties; this may produce uncertainty about enforcement consequences from the Standard alone. Firms must assume non-compliance will be addressed under the enabling statutes and other prudential standards, so risk assessments should not treat the Standard as unenforceable.
• Auditor appointment reference: The definition of Auditor refers to appointment under paragraph 83 of the Life Act (paragraph 18(b)). Firms must ensure the auditor performing the review is the statutory appointee; using a different firm for the limited assurance engagement may raise technical issues.

Prepare for these gotchas by mapping data lineage, implementing statutory-fund-level reconciliations, retaining 12-month-prior snapshots, coordinating actuarial and audit timetables, and building procedures for APRO-authority-driven changes.

A practical compliance checklist and recommended implementation steps grounded in the Standard’s provisions:

1. Governance and responsibility allocation

   • Assign clear ownership: Board oversight and senior management responsibility are required under paragraph 12. Ensure the Board delegates day-to-day ownership to a named Chief Reporting Officer or equivalent, with escalation to the PEO and CFO who must authorise submissions (paragraph 15).
   • Document authorisation policies and delegation: Prepare an internal authorisation policy that sets out who may prepare and submit reports, how PEO/CFO authorisation is given, and contingency plans for their unavailability (paragraph 15).

2. Data mapping and systems

   • Map statutory fund and management fund boundaries: Ensure systems can produce the required items at the statutory fund level for life insurers and the management fund level for friendly societies (Specific instructions: Reporting basis).
   • Identify and map required fields: Build a data dictionary mapping internal fields to Table 1 items: accrued premium, adjusted policy liabilities (gross/net), gross claim payments for the 12 months ending on the reporting date, and the 12-month-prior snapshots where required (Table 1 and Specific instructions).
   • Capture 12-month prior positions: For items that must be reported as at the date 12 months prior to the reporting date (Items 1.2, 2.2, 3.2), maintain archival or reconstructable position records to ensure accurate reporting.

3. Actuarial and accounting calculations

   • Align calculations with LPS 112 and LPS 118: Since adjusted policy liabilities and accrued premium are defined in LPS 112 and LPS 118 respectively, ensure actuarial teams produce valuations and calculations in accordance with those standards for the reporting period (paragraph 13 and Definitions).
   • Document estimates and reconciliations: For unaudited submissions where reasonable estimates are permitted (paragraph 13), keep clear documentation of estimation methodologies so auditors can assess their reasonableness and permit seamless transition to audited numbers.

4. Audit and assurance readiness

   • Engage the Auditor early: Paragraph 11 requires Auditor review and testing of systems, and a limited assurance engagement. Engage the statutory Auditor appointed under the Life Act (paragraph 18(b)) early to agree on scope, timing and evidence requirements.
   • Prepare controls evidence: Build an evidence pack demonstrating data lineage, controls tests, reconciliations, data validation routines and exception handling for the Auditor’s review (paragraph 11).
   • Ensure consistency with LPS 310: Annual audited information must be submitted with the annual auditor’s report as required by LPS 310 (Note 2 to paragraph 7). Coordinate audit schedules with LPS 310 reporting deadlines.

5. Submission mechanics and security

   • Implement APRA-acceptable digital signatures: Confirm the digital certificate solution acceptable to APRA and ensure IT can apply digital signatures as required for electronic submissions (paragraph 14).
   • Authorisation workflow: Implement a secure electronic authorisation workflow where the officer submitting the files is authorised by the PEO or CFO and the electronic signature and authorisation evidence is retained (paragraph 15).
   • Follow APRA’s electronic format and metadata requirements: Use the electronic submission method on APRA’s website or other APRA-notified method and conform to LRS 001 general instruction guide and Attachment A for file formats (paragraph 6; paragraph 18(b) reference to general instruction guide).

6. Quality control and governance

   • Board-level oversight: Establish board reporting on reporting readiness, audit findings, open data issues and remediation plans. Paragraph 12 places responsibility for authorisation policies on the Board and senior management.
   • Quarterly controls testing: The Auditor’s review is required at least annually but paragraph 11 also contemplates more frequent review "if necessary." Firms should adopt quarterly internal controls testing aligned with the four unaudited quarters to prevent surprises in the audited annual submission.

7. Timing and contingency planning

   • Calendar the five submissions: Calendar the quarterly unaudited submissions (each due within 20 business days after period end) and the audited annual submission due within three months after period end (paragraph 9 and Note 1).
   • Plan for APRA variations and extensions: Build processes to respond quickly to APRA notices changing reporting periods or requirements for a particular life company (paragraphs 8 and 16). Understand how to request and secure an extension of a due date from APRA (paragraph 10).
   • Manage transitional obligations: If any reporting periods fall into the transitional definition (paragraph 17), maintain the old reporting standard templates and processes for those specific periods.

8. Reinsurance and claims mapping

   • Ensure gross/net consistency: Map reinsurance recoverables and ceded premiums to the reporting items that require gross or net reporting. Reconciliation between ledger positions and reporting items will be critical.

9. Documentation and record retention

   • Retain audit trail: Keep a full audit trail of data extraction, calculations, approvals, digital signatures and auditor reports to facilitate internal reviews, auditor requests and APRA inquiries.
   • Prepare explanatory schedules: For any estimates, reconciling differences between unaudited and audited submissions, or between fund-level aggregates and consolidated accounts, produce explanatory schedules for auditors and APRA.

10. Continuous monitoring of referenced standards

• Track LPS 112, LPS 118, LPS 001, LRS 001 and LPS 310 amendments: Because the Reporting Standard imports definitions and calibration from these instruments (paragraphs 1, 13, 18 and 19), maintain a regulatory-watch process to update models and reporting templates when those standards change.

Implementing these steps produces a demonstrable compliance framework consistent with the Standard’s requirements: statutory-fund granularity, auditor-tested systems, APRA-compliant electronic submission, PEO/CFO authorisation and actuarial conformity with relevant prudential standards.