The Standard organises reporting around a small set of repeated accounting and prudential concepts and formalises their mapping into APRA data tables. Key concepts explicitly defined in the text include:

• AASB 17 SRPN, AASB 17 SRPP, AASB 17 SRP: these are the forms of shareholder retained profits determined for accounting reporting under AASB 17. AASB 17 SRPN is shareholder retained profits for non-participating business in a statutory fund; AASB 17 SRPP is shareholder retained profits for participating business in a statutory fund, and AASB 17 SRP covers shareholder retained profits within a benefit fund or within the shareholder/management fund determined for accounting reporting. The Standard also contains a note that insurers using the VSA-led method must report SRPP determined for accounting reporting and not SRPP determined for Life Act reporting (Definitions A; General instructions).

• Statutory fund (SF) / Benefit fund (BF) / Shareholder fund (SHF) / Management fund (MF): the Standard repeatedly distinguishes data at the SF/BF level and at life company level (Tables 1 and 3 operate at SF/BF level; Tables 2 and 4 operate at life company level). Reporting must be submitted for each SF/BF and rolled up to life company totals, with elimination columns required to reconcile intra-company transfers (Table 2 Column 5; Table 4 Column 3).

• Retained profits and share capital balances and movements: the instrument specifies opening and closing balances and detailed line items for movements over the reporting period. For retained profits, items include profit (loss) after income tax attributable to members, transfers between SHF/MF and SF/BF (both directions), dividends, and "other retained profits movements" (detailed in Definitions O and R and in Table item descriptions). For share capital, items include transfers between SHF/MF and SF/BF, ordinary shares issued, share capital reductions, and "other share capital movements" (Definitions O and S; Table item descriptions).

• Reporting basis and measurement rules: report all figures as at the reporting date unless otherwise stated; units must be whole Australian dollars (Specific instructions heading for each Table). Calculated columns and derived totals must reconcile (for example, Table 2 Column 6 is the sum of Columns 1-5 and the Standard requires that the sum across SFs/BFs, SHF/MF and elimination values equals life company level balances).

• Quality assurance and auditor involvement: the data must be produced by systems, processes and controls reviewed and tested by the Auditor; the Auditor must perform reviews at least annually and undertake a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance (Quality control para 11). Boards and senior management must maintain internal policies and procedures for authorisation of data submitted to APRA (para 12).

• Flexibility and APRA discretion: APRA can change reporting frequency for an individual life company, vary reporting requirements for a company, and accept alternate submission methods (paras 6, 8, 16). APRA can grant extensions to due dates (para 10).

These concepts interact mechanically: retained profits and share capital movements at fund level feed into life company level derived columns, require elimination adjustments to avoid double counting, and must be prepared on an accounting basis that aligns AASB 17 SRP concepts with the reporting tables. The Standard explicitly ties actuarial valuations to the prudential standards in force for the reporting period, while allowing reasonable estimates for unaudited quarterly submissions (para 13).

The text states the affected population directly and narrowly. The Standard applies to all life insurance companies, including friendly societies, registered under the Life Insurance Act 1995 (Application and commencement para 3). That term is defined in the instrument as "life companies" for convenience (para 3). The obligation to report applies to each such life company for each reporting period (para 4).

Within each life company, particular roles are placed with specific responsibilities:

• The Board and senior management are responsible for ensuring appropriate policies and procedures for internal review and authorisation of data submitted to APRA (Quality control para 12).
• The company’s Auditor has a statutory role in reviewing and testing the systems, processes and controls supporting the reporting. The Auditor must perform these reviews at least annually and undertake at least a limited assurance engagement consistent with professional standards (para 11).
• The officer or agent who actually submits the electronic information must digitally sign it with an APRA-acceptable digital certificate, and must be authorised by either the Principal Executive Officer or the Chief Financial Officer (Authorisation paras 14-15).

Operationally, the Standard affects several internal functions and external advisors:

• Finance and accounting teams will need to map AASB 17 SRPN/SRPP/SRP measures into the APRA table structure and ensure correct aggregation and elimination values across funds and the shareholder/management fund (General instructions; Table-specific columns and item instructions).
• Actuarial teams must produce valuations and calculations in accordance with the prudential standards in force for the reporting period, to feed into the data (para 13).
• Internal control, data governance and IT functions must implement and maintain systems that support the data production, ensure uniqueness of specific value combinations in rows, produce whole-AUD reporting, and deliver the data via APRA’s electronic method (General instructions; Method of submission para 6).
• External auditors will be engaged to perform the prescribed review and limited assurance tasks, and will incur associated time and fees (Quality control para 11).

Geographically and legally, the Standard’s scope is Australian statutory; foreign parent companies are affected to the extent that they own or control life companies registered in Australia because the obligation attaches to the registered life company (Application para 3). The Standard also directly affects firms’ reporting calendars due to the five submissions per year requirement and defined due dates (Reporting periods and due dates paras 7-9).

Finally, APRA itself is an actor under the Standard: APRA has discretion to vary reporting periods, adjust reporting frequency, accept alternate submission methods and grant extensions (paras 6, 8, 10, 16). That discretion creates a direct operational relationship between APRA and each reporting life company.

The Reporting Standard sets out specific duties and a small number of explicit rights (mainly APRA’s discretion). The duties are obligations of the life company, its management, auditors and authorised submitters; the rights are APRA’s regulatory discretions.

Principal duties placed on life companies:

• Duty to provide the information required by the Standard for each reporting period (para 4).
• Duty to submit quarterly unaudited reports and an annual audited report for each financial year, with the annual audited submission to be accompanied by the auditor’s report under Prudential Standard LPS 310 (para 7; Note 2).
• Duty to submit quarterly information within 20 business days after the quarter end and annual information within three months after financial year end, unless APRA specifies otherwise or grants an extension (para 9(a)-(b); para 10).
• Duty to prepare data as at the reporting date, in whole Australian dollars, and to comply with the table structures and defined columns and items (Tables 1-4 specific instructions; Units of measurement statements).
• Duty to ensure the information is the product of systems, processes and controls that have been reviewed and tested by the Auditor, including at least an annual review and a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance (para 11).
• Duty of the Board and senior management to maintain and ensure appropriate policies and procedures for internal review and authorisation of data submitted (para 12).
• Duty to ensure actuarial valuations and calculations used in the preparation of the information are in accordance with the prudential standards in force for the reporting period (para 13). The Standard permits reasonable estimates for unaudited submissions (para 13).

Duties placed on the Auditor and submitter:

• Auditor must review and test systems, processes and controls supporting reporting, annually or more frequently as necessary, and perform at least a limited assurance engagement (para 11).
• Officer or agent who provides the information electronically must digitally sign the submission using a digital certificate acceptable to APRA (para 14).
• Officer or agent submitting the information must be authorised by the Principal Executive Officer or Chief Financial Officer (para 15).

APRA’s rights and discretions:

• Right to alter reporting frequency for a particular life company by written notice if APRA considers more or less frequent reporting necessary or desirable (para 8).
• Right to vary reporting requirements for a particular life company by written notice (para 16).
• Right to specify a different method of submission by prior notification (para 6(b)).
• Right to grant written extensions to due dates (para 10).

Implicit rights and duties in the instrument:

• The Standard does not itself enumerate penalties or enforcement steps within the text provided, but the Standard is framed as an instrument for prudential supervision under the Financial Sector (Collection of Data) Act 2001 and the results of non-compliance would be relevant to APRA’s supervisory work (Authority para 1; Purpose para 2). The instrument assigns clear internal governance responsibilities to Boards and senior management as part of the duty structure (para 12).

Practical duties when preparing the tables:

• Reconcile SF/BF level data to life company level , the Standard mandates derived columns and elimination values and requires that sums reconcile (Table 2 Column 5 and Column 6; Table 4 Column 3 and Column 4).
• Ensure that specific combinations of values in a table do not appear on more than one row (General instructions).
• Report positive or negative values as specified in item-level instructions (for example, retained profits transfers from SF to SHF/MF are reported as negative in statutory fund tables; see Table 1 Item 1.4 and Table 3 Item 1.3).

In sum, the Standard prescribes a set of reporting, control, audit and authorisation duties for life companies and related internal actors, and grants APRA a set of administrative discretions to tailor reporting obligations or timetables for particular entities.

The Reporting Standard itself does not set out express penalties, fines or specific enforcement mechanisms in the text provided. The instrument states its statutory basis , it is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (Authority para 1) , and that APRA will use the information for prudential supervision including assessing compliance with capital adequacy standards (Purpose para 2). The Standard therefore sits within APRA’s broader supervisory framework but does not, within the text provided, specify civil or criminal sanctions or the administrative enforcement steps that follow non-compliance.

What the Standard does provide that is relevant to enforcement and evidentiary control:

• APRA is given administrative tools to vary reporting or require different frequencies for specific life companies (paras 8 and 16). Those powers enable APRA to demand more granular or more frequent information from a particular entity if APRA considers that necessary or desirable (para 8).
• APRA can specify methods of submission and grant extensions of due dates (paras 6(b), 10). These are operational tools APRA can exercise to manage compliance and timetables.
• The Standard builds in an assurance chain: systems and processes must be reviewed and tested by the company’s Auditor (para 11), and the annual audited submission must be accompanied by the auditor’s report consistent with Prudential Standard LPS 310 (para 7 Note 2). That auditor involvement establishes a formal assurance and review mechanism which APRA can rely upon in its supervisory work.
• Internal accountability is explicit: Boards and senior management are charged with ensuring policies and procedures for internal review and authorisation of data submitted to APRA (para 12). This creates documented governance responsibilities which APRA may consider in supervisory interactions.

Because the Standard does not itself state penalties, practitioners should treat it as a data-collection and assurance instrument embedded in APRA’s prudential framework. Enforcement action, if any, for failure to comply with reporting obligations would fall under APRA’s statutory powers and the general regulatory regime under the Financial Sector (Collection of Data) Act 2001 and potentially the Life Insurance Act 1995. The instrument provides APRA with pre-authorised discretion to vary reporting, and a structure of auditor and board responsibilities that create both operational and documentary evidence APRA may use in supervision. The Standard therefore increases APRA’s capacity to detect and investigate reporting failures via data, audits and governance documents, even though it does not set out detailed sanctions within its own text.

Practitioners should therefore assume:

• Non-compliance (late submission, materially incorrect data, missing digital authorisation, or lack of required auditor assurance) will be visible to APRA through its electronic submission channel and audit confirmations (paras 6, 11, 14-15).
• APRA may react administratively, using its discretion to require additional information, change reporting frequency, or request remedial actions under its broader statutory powers (paras 8, 16). The instrument’s silence on internal penalties does not remove potential enforcement under the relevant Acts; it does, however, place emphasis on prevention through audit and governance duties.

If a reporting entity needs certainty on penalties and formal enforcement powers available to APRA in the event of non-compliance, the entity should consult the Financial Sector (Collection of Data) Act 2001 and the Life Insurance Act 1995 and APRA’s supervisory statements, as this Reporting Standard does not reproduce those statutory enforcement provisions.

The Standard cross-references a number of existing prudential and reporting instruments and statutory regimes; it is designed to sit within APRA’s existing data collection and prudential architecture.

Statutory authority and context:

• The Standard is made under s 13 of the Financial Sector (Collection of Data) Act 2001 (Authority para 1). That Act is the enabling statute for APRA’s data collection powers; this Reporting Standard is therefore a statutory instrument exercising those powers. The Standard also applies specifically to entities registered under the Life Insurance Act 1995 (Application para 3), so its application is limited to the life insurance regulatory perimeter established by that Act.

Interaction with prudential standards:

• The Standard requires actuarial valuations and calculations to be prepared "in accordance with the prudential standards in force for the reporting period" (para 13). It also specifies that the annual audited information must be submitted with the annual auditor’s report as required under Prudential Standard LPS 310 Audit and Related Matters (para 7 Note 2). The Standard therefore operates alongside Prudential Standards LPS 001 (Definitions) and LPS 310 at minimum, and cross-references LRS 001 Reporting Requirements for general instruction guidance (Objective para; Interpretation para 18(a)).

Accounting standards and measurement:

• The Standard uses AASB 17 terminologies (AASB 17 SRPN, SRPP, SRP) as definitions for the reported measures (General instructions; Definitions A). The Standard explicitly requires insurers that use the VSA-led method to report SRPP determined for accounting reporting rather than SRPP determined for Life Act reporting, signalling that the Standard anchors reporting to accounting measures rather than to measures established uniquely under the Life Act (Definitions A). It also states that references to Acts, Prudential Standards, Reporting Standards, Australian Accounting or Auditing Standards are references to the instruments "as in force from time to time" (Interpretation para 19). That phrasing creates an updating mechanism so that changes to referenced accounting and auditing standards automatically affect the reporting requirements.

Auditing and assurance regimes:

• The Standard requires auditor review and a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance, to the extent not inconsistent with Prudential Standard LPS 310 (para 11(b)). The annual audited submission must be accompanied by the auditor’s report per LPS 310 (para 7 Note 2). Thus the Standard is closely integrated with Australian auditing standards and APRA’s own audit prudential standard.

Data collection and APRA’s reporting framework:

• The Standard must be read in conjunction with Reporting Standard LRS 001 Reporting Requirements and the general instruction guide set out in Attachment A of LRS 001 (Objective para; Interpretation para 18(b)). LRS 001 likely sets out common technical and schema rules, and LRS 340.1 provides the fund- and company-level table definitions that plug into that overall reporting framework.

Transitional and revocation interaction:

• The Standard contains transition rules that require life companies to report under the old reporting standard for transitional reporting periods as defined (Transition para 17). It also uses the term "old reporting standard" defined as the reporting standard revoked in the determination making LRS 340.1 (para 17). This means LRS 340.1 has replaced a prior instrument and requires companies to continue to comply with the old instrument for certain prior-period reporting obligations still outstanding.

What the Standard does not do in the text:

• It does not alter substantive capital adequacy requirements or replace prudential standards that set capital levels. It is a data collection instrument designed to provide APRA with the information it needs to assess compliance with capital adequacy standards (Purpose para 2). It therefore complements, rather than replaces, substantive prudential requirements found elsewhere.

Practical implication: reporting entities must align:

• Accounting teams to AASB 17 definitions (AASB 17 SRPN/SRPP/SRP).
• Actuarial outputs to prudential standards in force for the reporting period (para 13).
• Auditor work to both APRA’s LPS 310 and Auditing and Assurance Standards Board guidance (para 11(b); para 7 Note 2).
• IT and data architecture to APRA’s electronic submission channels and to the column and elimination structures spelled out in Tables 1-4.

In short, LRS 340.1 is a data specification that references and depends upon existing statutory, prudential and accounting regimes, and it presumes integration with APRA’s broader reporting, audit and supervisory framework.

The Standard itself contains limited internal history but does record a key commencement and transitional arrangement:

• Commencement: the Standard applies for reporting periods ending on or after 1 July 2023 (Application and commencement para 3). That is the explicit effective date set in the instrument.
• Replacement of an earlier instrument: the Standard includes a transition clause requiring life companies to report under the old reporting standard in respect of transitional reporting periods as defined (Transition para 17). The instrument defines "old reporting standard" as the reporting standard revoked in the determination making LRS 340.1 (para 17). This confirms that LRS 340.1 replaced one or more prior APRA Reporting Standards at the time it was made and that certain outstanding reporting obligations under the revoked standard must continue to be met.

No other amendments, repeal dates, or a schedule of prior versions are provided in the text supplied. The Standard contains an interpretation provision that references other instruments "as in force from time to time" (para 19), which implies the Standard will operate dynamically with changes to referenced prudential, accounting or auditing standards, but the document does not itself list any prior amendments or a legislative history. Practitioners should note:

• The Standard’s Note telling life companies to continue to satisfy overdue reporting obligations under an old reporting standard if those reports were due before the revocation (Transition para 17 Note). That creates an operational overlap risk for entities that had outstanding obligations at revocation date.
• The Standard authorises APRA to vary reporting requirements by written notice to the life company (para 16). That provision allows APRA to create bespoke reporting obligations or adjustments for a particular company without formally amending the Standard instrument across the industry; operationally this behaves like an ongoing amendment power for individual companies.

To track amendment or replacement history beyond the commencement and transition mechanics documented here, practitioners must consult:

• The formal APRA determinations and Gazetted instrument(s) that made and revoked the previous reporting standard.
• APRA’s website and the Federal Register of Legislation for any determinations, explanatory memoranda, or subsequent variations and revocations that post-date the 1 July 2023 commencement noted in this instrument.

The Standard does not provide an editions table or track changes log within its own text. For audit trails and compliance, a life company should retain copies of the revoked reporting standard, the revocation determination, and the new LRS 340.1, along with any notice(s) APRA issues under para 8 or para 16 affecting the company.

The Reporting Standard text supplied contains no references to litigation, decisions, or case law. It does not name any court decisions or administrative determinations. There are no judicial or tribunal references in the instrument as provided.

Because the instrument is a data-collection and reporting specification made under the Financial Sector (Collection of Data) Act 2001 (Authority para 1), any litigation or tribunal matters potentially arising from enforcement or disputes about reporting would not be recorded in the text of the Standard itself. The Standard’s text does not include:

• Any declaratory guidance, case law citations, or appeals procedures.
• Any recorded judicial challenges to the Standard or to APRA’s exercise of the discretions under paras 8, 10 or 16.

Practical consequence: if a life company requires precedent or litigation guidance on disputes about reporting obligations, the text here provides no internal history; the company will need to:

• Search the Federal Court and relevant tribunals for any cases dealing with APRA reporting standards or the underlying Acts (Financial Sector (Collection of Data) Act 2001; Life Insurance Act 1995).
• Review APRA’s supervisory statements, published decisions (if any), and guidance notes for examples of how APRA has enforced or interpreted reporting obligations in practice.
• Consider that disputes about interpretation of the Standard (for example, differences in how AASB 17 SRPP is measured for VSA-led insurers) will likely turn on the interplay between accounting standards, the prudential standards referred to in para 13, and the facts of the data submitted.

In the absence of litigation references in the Standard itself, the instrument is best treated as a prescriptive data collection rule that will be interpreted in practice by APRA and, if contested, by courts and tribunals considering statutory interpretation and administrative law principles applicable to APRA’s powers.

This instrument contains several detailed technical and operational requirements that can cause downstream compliance problems if overlooked. Below are specific pitfalls and traps visible directly in the text.

Five submissions per year and timing constraints:

• The Standard requires quarterly unaudited submissions and one annual audited submission, meaning five submissions for a full financial year (Reporting periods and due dates para 7; Note 1). Many entities’ processes are set up for four quarter-end reports and one annual report; the Standard’s explicit count is five submissions per financial year because it treats the annual audited report as an additional (audited) submission. Practitioners must schedule five deliverables and monitor the 20-business-day and three-month deadlines (para 9).

Audited vs unaudited data and use of estimates:

• Quarterly submissions are unaudited and reasonable estimates may be used for those unaudited submissions (para 13). The Standard permits reasonable estimates for information that will not be audited (i.e. the first four submissions), but the annual audited submission requires actuarial valuations in accordance with prudential standards (para 13). This requires careful reconciliation: estimates used in quarterlies must be adjusted and justified in the annual audited submission.

Audit assurance requirements:

• The Auditor must review and test systems, processes and controls supporting the reporting and perform at least a limited assurance engagement in accordance with Auditing and Assurance Standards Board guidance, subject to consistency with LPS 310 (para 11). Entities must budget for auditor time and ensure auditors are engaged early and have access to controls and dataflow documentation.

Data mapping and elimination columns:

• Life company level tables require elimination values (Table 2 Column 5; Table 4 Column 3) and derived totals (Table 2 Column 6; Table 4 Column 4). The Standard requires that the sum across all SFs/BFs, SHF/MF and elimination values equals life company level balances (Table 2 explanatory notes). Errors in elimination or inconsistent mapping between fund-level and company-level reporting will produce reconciliation discrepancies. Ensure chart of accounts, fund mappings, and inter-fund transfer accounting are aligned to the table structure.

AASB 17 SRPP measurement nuance:

• The Standard instructs that insurers using the VSA-led method must report SRPP determined for accounting reporting, not SRPP determined for Life Act reporting (Definitions A). This indicates an accounting-vs-prudential measurement divergence for some entities and requires explicit mapping rules in internal guidance.

Positive/negative reporting conventions:

• The item-level instructions specify when to report values as positive or negative (e.g. Table 1 Item 1.4 reports retained profits transfers from SF to SHF/MF as a negative value). Failure to follow sign conventions will produce incorrect totals and likely trigger APRA queries.

Whole-AUD reporting and uniqueness constraints:

• All values must be reported in whole Australian dollars (Units of measurement statements), so rounding rules must be agreed. The General instructions require that "Any specific combination of values in a table must not appear on more than one row", which means data de-duplication and unique keying must be validated before submission.

Digital signing and authorisation:

• Electronic submissions must be digitally signed using a digital certificate acceptable to APRA, and the submitter must be authorised by the Principal Executive Officer or Chief Financial Officer (paras 14-15). Not all submission workflows have PKI/ digital certificate capabilities; organisations must ensure their electronic submission process supports APRA’s certificate requirements and that authorisations are documented.

Transition obligations:

• Entities with outstanding reporting obligations under the old reporting standard must still provide those overdue documents in accordance with the old standard even if the old standard has been revoked (Transition para 17 Note). That creates potential parallel-reporting obligations during the cutover period.

Board and senior management accountability:

• Para 12 places responsibility on the Board and senior management to ensure appropriate policies and procedures for authorisation of data submitted to APRA. This is an explicit governance accountability that can feed into supervisory assessments.

No express penalty text in the Standard:

• The Standard does not set out penalties or enforcement actions within its own text. This is not a “gotcha” about leniency; rather, it means that any enforcement response will come through APRA’s broader statutory powers. Practitioners should not infer absence of consequences from the instrument’s silence; APRA’s supervisory response may make use of other statutory powers.

Practical test cases that typically cause issues:

• Reconciling dividends and intra-fund transfers across SF/BF and SHF/MF columns and ensuring elimination columns are correct.
• Ensuring that ordinary shares issued and share capital reductions are reported only where the Standard says (Table 4 Items 1.4-1.5 reportage restrictions).
• Confirming actuarial assumptions used for quarterly estimates are compatible with final audited-year prudential valuations to avoid large adjustments in year-end audited submission.

To mitigate these gotchas, entities should run reconciliation trials, engage auditors early, document sign and authorisation processes, and ensure the IT submission chain supports APRA’s digital certificate and file format requirements.

This section is a practical compliance checklist and recommended operational steps grounded on the Standard’s text. The steps below map directly to specific paragraphs and table instructions in the instrument.

1. Establish scope and calendar

• Confirm the entity is within the instrument’s scope: life companies and friendly societies registered under the Life Insurance Act 1995 (Application para 3).
• Build a reporting calendar for five submissions per financial year: quarterly unaudited submissions (due within 20 business days after quarter end) and one annual audited submission (due within three months of financial year end) (Reporting periods and due dates paras 7 and 9). Track the first four as unaudited (estimates allowed) and the fifth as audited (para 13).

2. Map funds and accounting measures

• Inventory all statutory funds (SFs) and benefit funds (BFs), and identify the shareholder fund (SHF) / management fund (MF).
• Map AASB 17 SRPN/AASB 17 SRPP/AASB 17 SRP outputs to the table columns specified (General instructions; Definitions A). For VSA-led insurers, ensure SRPP is the accounting-determined SRPP (Definitions A).

3. Data model and table templates

• Implement table structures consistent with Tables 1-4. Ensure Columns and Items are present as described; implement derived columns (Table 2 Column 6; Table 4 Column 4) as column formulas that sum specified columns/items.
• Implement elimination columns at life company level to reconcile intra-company transfers (Table 2 Column 5; Table 4 Column 3).
• Enforce the "no duplicate combination of table values per row" rule (General instructions).
• Use whole Australian dollars for all numeric fields (Units of measurement statements).

4. Systems, processes and internal controls

• Design systems and workflows so data is the product of controlled systems, processes and controls that can be reviewed by the Auditor (Quality control para 11).
• Implement clear policies and procedures for internal review and authorisation; assign Board and senior management responsibilities and ensure evidence of sign-off (para 12).
• Document reconciliation routines between fund-level and life company-level reporting, including treatment of dividends, transfers, ordinary shares issued, and share capital reductions per item-level instructions.

5. Actuarial and accounting controls

• Ensure actuarial valuations and calculations are performed in accordance with the prudential standards in force for the reporting period (para 13).
• For the first four unaudited submissions, define and document the reasonable-estimate methodology that will be used and how it will be reconciled to audited figures at year-end (para 13).
• Coordinate accounting and actuarial teams to avoid divergences between AASB 17 accounting positions and internal prudential measures.

6. Auditor engagement

• Engage the Auditor to review and test the systems, processes and controls supporting reporting at least annually and to perform a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance (para 11). Confirm the audit scope aligns with LPS 310 requirements for the annual audited submission (para 7 Note 2).
• Provide auditors with data lineage documentation, reconciliation procedures, and governance sign-off artifacts.

7. Authorisation and digital submission process

• Implement digital signing capability for electronic submissions using a digital certificate acceptable to APRA, and test the submission channel (Authorisation para 14; Method of submission para 6).
• Ensure the submitting officer or agent is authorised in writing by either the Principal Executive Officer or the Chief Financial Officer and keep records of that authorisation (para 15).
• Confirm the APRA electronic method’s technical requirements (file format, schema, delivery protocol) via APRA’s website or APRA notifications (para 6).

8. Reconciliation, sign-off and retention

• Perform pre-submission reconciliations between SF/BF tables and life company tables. Verify derived columns and elimination items generate life company totals that reconcile with internal statutory accounts and management accounts.
• Apply the sign conventions and positive/negative reporting rules from item-level instructions (for example, Table 1 Item 1.4 negative reporting).
• Obtain internal reviews and Board or delegated senior management sign-off in accordance with internal authorisation policies (para 12).

9. APRA interactions and bespoke notices

• Monitor APRA notices. APRA may, by written notice, change reporting periods (para 8), vary reporting requirements for the life company (para 16), specify alternative submission methods (para 6(b)), or grant extensions of due dates (para 10). Maintain a process to ingest and implement APRA notices quickly.

10. Transitional reporting

• If required to report under the old reporting standard for transitional reporting periods, follow the old standard for those periods and ensure any overdue reports due before revocation are still provided under the old standard (Transition para 17 and Note).

11. Documentation and audit trail

• Maintain full documentation of mappings from source ledgers to APRA table fields, policies for estimates used in unaudited submissions, actuarial methodologies, auditor review reports, digital certificate usage records, and authorisation letters from PEO/CFO. This documentation will be essential for both audit and APRA supervisory review.

12. Testing and dry runs

• Run mock submissions for the quarterly and annual cycles to test reconciliation, elimination columns, derived totals and APRA’s electronic submission interface well before live due dates. Use those dry runs to confirm auditor access and sign-off processes.

By following the above steps and aligning systems, actuarial, accounting and audit activities to the prescriptive items and columns in the Standard (Tables 1-4; paras 6-15), a life company can demonstrate that it has implemented the governance, control and operational measures the Reporting Standard requires.