The Standard is built around a limited set of concepts that determine what must be reported, at what level, and how the reported values are to be produced and assured. Key concepts are: Insurance Risk Charge components, life company fund types, insurance benefit categories, submission frequency and timing, quality control and assurance, and the data capture and format rules.

Insurance Risk Charge components: the Standard lists the elements that form the Insurance Risk Charge calculation and associated reporting items. These include adjusted policy liabilities (gross and net of reinsurance), stressed policy liabilities (gross and net), insurance risk charge tax benefits (for statutory/benefit funds), and, for friendly societies, a set of servicing-related components such as expected management fees, expected servicing expenses, expected deficiency (before and after prescribed multiplier), additional deficiency from prescribed servicing expense stress, total servicing expense reserve and reductions in management fees assumed under asset/insurance stress (see Definitions and Table 1/Table 2 instructions). The Standard instructs that Insurance Risk Charge - tax benefits should be reported as a positive value where tax benefits are recognised (Table 1/Table 2 descriptions).

Life company fund type and reporting granularity: data must be submitted at fund level , statutory fund for life insurers and benefit fund for friendly societies (Table 1 instruction). Friendly societies have a separate requirement to report at the management fund level for the servicing expense reserve and related components (Table 2 instruction). The Reporting Standard therefore distinguishes between product-level liability measures (policy liabilities, stressed liabilities) and servicing/management fund measures (which affect interaction between benefit funds and management funds for friendly societies).

Insurance benefit categories: where required, reporting must be broken down by insurance benefit type. The Standard sets out the valid values: non-participating benefits without entitlement to discretionary additions; non-participating benefits with entitlement to discretionary additions; participating benefits; and friendly society benefits (Definitions and Table 1). This means APRA expects fund-level data partitioned by product/benefit design where relevant to the Insurance Risk Charge calculation.

Submission timing and frequency: the Standard specifies quarterly unaudited submissions for each quarter and an annual audited submission, with the consequence that a life company will typically submit five sets of data per financial year (para 7 and Note 1). APRA can alter frequency for a particular life company where it considers it necessary or desirable, by written notice (para 8). Due dates are explicit: quarterly within 20 business days, annual within three months (para 9). APRA may grant written extensions (para 10).

Quality control and assurance concepts: the Standard makes the Auditor responsible for review and testing of the reporting systems, processes and controls supporting the data (para 11). That testing must occur at least annually and include a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance, insofar as not inconsistent with LPS 310 (para 11(b)). Boards and senior management are explicitly responsible for establishing policies and procedures for internal review and authorisation of data to be submitted to APRA (para 12). Actuarial valuations used for the reporting must comply with prudential standards in force, though reasonable estimates may be used for unaudited submissions (para 13).

Data format, validation and authorisation: the Standard requires submission in electronic format by methods available on APRA’s website or other notified methods (para 6). Electronic submissions must be digitally signed with a certificate acceptable to APRA and the submitter must be authorised by the Principal Executive Officer or Chief Financial Officer (paras 14-15). Tables set constraints on duplicate combinations (no specific combination may appear in more than one row), units (whole Australian dollars), valid values for coded fields, and the precise column order for reported datasets (General instructions, Reporting tables, Table 1 and Table 2 specifics).

Interpretation and cross-references: the Standard imports definitions from Prudential Standard LPS 001 (para 18(a)) and references other prudential and auditing standards (para 19). It therefore operates within APRA’s broader prudential framework (for example, cross-reference to LPS 112 for adjusted policy liabilities and to LPS 115 for stressed liabilities).

Primary affected entities: the Standard applies to "all life insurance companies including friendly societies (together referred to as ‘life companies’) registered under the Life Insurance Act 1995" for reporting periods ending on or after 1 July 2023 (para 3). That means each registered life insurer and friendly society that operates statutory funds or benefit funds is directly in scope for the obligation to report the nominated Insurance Risk Charge items to APRA every reporting period.

Within affected entities, the roles required to act: the Board and senior management bear responsibility for internal policies and procedures for authorisation and review of data submitted to APRA (para 12). The Principal Executive Officer or the Chief Financial Officer must authorise the person who actually submits data (para 15). Auditors, defined as auditors appointed under paragraph 83 of the Life Act (para 18), must review and test systems and controls supporting the reported data and perform at least a limited assurance engagement consistent with applicable auditing standards (para 11). Operational staff in finance, actuarial and data teams must assemble the fund-level datasets and ensure values are in whole Australian dollars and conform to the specified valid values (Table instructions).

Secondary impacts: IT and compliance teams will be required to implement APRA-acceptable digital certificates for electronic signing (para 14) and the electronic submission method in use on APRA’s website (para 6). Actuarial teams must prepare valuations and calculations in accordance with prudential standards in force for the reporting period (para 13). For friendly societies, management fund teams must calculate servicing expense reserve components and expected management fees, and reconcile reductions in management fees assumed under stress (Table 2 instructions).

Who decides: APRA retains discretion to require altered reporting frequencies for particular life companies (para 8), to vary reporting requirements by written notice to a life company (para 16), and to grant extensions of due dates (para 10). Those provisions mean APRA can tailor reporting to a firm-specific supervisory need, and life companies must implement those directions when given.

Who pays and bears costs: the Standard does not set levies or fees. The direct compliance costs fall on life companies: assembling the data; maintaining systems and controls; having the Auditor perform review and limited assurance; implementing digital signature infrastructure; and preparing audited annual returns and the auditor’s report for submission with the annual return (paras 11, 14, Note 2). Boards and senior management must maintain the internal governance framework described in para 12. Friendly societies may face additional work to reconcile management fund servicing items with benefit funds per Table 2 instructions.

Information flow and confidentiality: the Standard notes that information reported under this instrument is not required to be given to policy owners pursuant to section 124 of the Life Act and does not constitute a reporting document for the purposes of section 124 (para 5). That means APRA receives this data without a parallel obligation to provide the same data to policyholders under s124 of the Life Act; the Standard does not itself address external disclosure to policy owners.

Mandatory reporting duty: a life company must provide APRA with the information required by this Reporting Standard for each reporting period (para 4). The duty includes submission of the specific datasets described in Table 1 and Table 2 instructions, with values in whole Australian dollars and adherence to the listed valid values and field order.

Timing duties: the company must submit quarterly unaudited information within 20 business days after the reporting period and annual audited information within three months after the reporting period (para 9). The annual audited submission must be accompanied by the annual auditor’s report as required under Prudential Standard LPS 310 (para 7 Note 2). APRA may alter reporting periods for a particular company by written notice (para 8), and may grant a written extension to due dates (para 10). The Standard explicitly states that even if a due date falls on a non-business day, the company must submit no later than the due date (para 10 Note).

Assurance and quality-control duties: the information provided must be produced by systems, processes and controls that have been reviewed and tested by the Auditor (para 11). That review must be carried out on an annual basis or more frequently when necessary to enable the Auditor to form an opinion on reliability and accuracy of data (para 11(a)). The Auditor must also undertake at least a limited assurance engagement consistent with professional standards and guidance notes issued by the Auditing and Assurance Standards Board, subject to not being inconsistent with LPS 310 (para 11(b)). Boards and senior management are required to ensure appropriate policies and procedures for internal review and authorisation of data (para 12). Actuarial valuations and calculations must comply with prudential standards in force for the reporting period, though reasonable estimates may be used for information that will not be audited (i.e. first four submissions in a full financial year) (para 13).

Authorisation duties for submitters: electronically submitted information must be digitally signed using an APRA-acceptable digital certificate (para 14). The officer or agent submitting the data must be authorised by the Principal Executive Officer or the Chief Financial Officer (para 15). These steps create an auditable responsibility chain from submitter through CFO/PEO and the Board.

APRA’s rights and discretions: APRA may change reporting frequency or specify reporting periods for a particular life company when necessary or desirable (para 8). APRA may issue written notices varying reporting requirements in relation to a life company (para 16). APRA may also permit alternative submission methods by prior notification (para 6(b)). APRA may grant extensions of due dates (para 10). The Standard is made under the Financial Sector (Collection of Data) Act 2001 (para 1), thereby exercising APRA’s statutory data-collection authority under that Act.

Data content duties: the Standard prescribes the data fields and valid values that must be used for Tables 1 and 2, including specification of reporting basis (fund-level), units (whole Australian dollars), and the valid coded values for fund type, insurance benefit, and component types (Table 1 & Table 2 instructions). There is a reporting data constraint that any specific combination of values in a table must not appear in more than one row (General instructions).

Rights of life companies in the Standard: the text gives life companies the limited right to use "reasonable estimates" when preparing unaudited information (para 13), which provides some flexibility ahead of audited submissions. Additionally, life companies may seek or rely on APRA-granted extensions (para 10). The Standard does not itself grant other procedural rights such as appeal rights against APRA directions in this text; any such rights would have to be identified elsewhere.

Absent entitlements and enforcement details: this Standard does not, in its text, set out penalties or explicit enforcement mechanisms for non-compliance with its reporting obligations. It states the purpose of the information collection (prudential supervision and assessing compliance with capital adequacy standards) (para 2), and it establishes APRA’s discretion to vary reporting for particular companies (paras 8 and 16). Where enforcement remedies or penalties exist will depend on the parent statutes and other prudential standards, but the Standard as provided does not itself specify fines or sanctions.

The Reporting Standard LRS 115.0, as presented in the text, sets out reporting obligations, assurance requirements and APRA’s discretion to alter reporting, but it does not include express provisions within the Standard itself prescribing civil or criminal penalties for non-compliance (the document does not list fines, offence provisions, or enforcement steps). The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (para 1), which provides APRA’s statutory authority to collect data; however, this Reporting Standard’s text does not restate enforcement powers that may exist elsewhere under the Financial Sector (Collection of Data) Act 2001, the Life Insurance Act 1995, or other instruments.

What the Standard does provide concerning enforcement-adjacent mechanisms:

• APRA may change reporting periods or specify reporting periods for a particular life company by written notice where APRA considers it necessary or desirable (para 8). That is a supervisory power to modify reporting obligations at the firm level.

• APRA may, by written notice, vary the reporting requirements of this Reporting Standard in relation to that life company (para 16). That gives APRA scope to adapt data demands to particular supervisory needs.

• APRA may grant extensions of due dates in writing (para 10). This is a procedural discretion that can mitigate timing non-compliance in some situations.

• The Standard prescribes assurance and authorisation steps (paras 11-15). While not enforcement per se, the requirement that auditors undertake review and limited assurance, and that submissions be digitally signed by an authorised officer, creates audit trails and responsibility channels that support APRA’s supervision and investigation capacity.

What the Standard does not specify (in the text provided):

• No offence provisions, monetary penalties, or administrative sanctions are set out within the Standard itself for failure to comply with LRS 115.0 obligations.

• No explicit administrative process for dispute resolution, review of APRA notices altering reporting obligations, or appeal mechanisms is contained in the Standard text provided.

Practically, this means that a reader must look to the Financial Sector (Collection of Data) Act 2001, the Life Insurance Act 1995, and APRA’s general enforcement regime and prudential framework (including any prudential standards such as LPS 115 and LPS 310) for the specific legal consequences of non-compliance. The Reporting Standard references those other instruments (for definitions, prudential measurement requirements, and auditor reporting linkages), but does not itself reproduce or summarise their enforcement provisions. Where APRA exercises its formal statutory powers under its enabling Acts, consequences for non-compliance are implemented under those statutes rather than within this Reporting Standard’s provisions.

The Reporting Standard explicitly cross-references multiple other instruments and statutes. The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (para 1). It applies to life companies registered under the Life Insurance Act 1995 (para 3). Definitions and measurement bases are imported from or required to comply with specific prudential standards: adjusted policy liabilities are determined in accordance with Prudential Standard LPS 112 Capital Adequacy: Measurement of Capital (Definitions A); stressed policy liabilities are determined in accordance with Prudential Standard LPS 115 (Definitions S and the Objective). Actuarial valuations and calculations must be in accordance with the prudential standards in force for the reporting period (para 13).

Auditor and audit standard linkages: the Standard requires the Auditor to review and test reporting systems, processes and controls, and to perform at least a limited assurance engagement consistent with professional standards and guidance issued by the Auditing and Assurance Standards Board, to the extent not inconsistent with Prudential Standard LPS 310 Audit and Related Matters (para 11(b)). The annual audited submission must be provided in conjunction with the annual auditor’s report required under LPS 310 (para 7 Note 2). Therefore, there is operational coupling between this reporting obligation and APRA’s broader audit and assurance framework under LPS 310.

Definitions and interpretative cross-references: the Standard states that, unless the contrary intention appears, words and expressions have the meanings given in Prudential Standard LPS 001 Definitions (para 18(a)). Further, para 19 says 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 the reporting obligations are dynamically linked to the content of those other instruments and may be affected by amendments to the referenced standards or accounting/auditing standards. For example, the calculation basis for adjusted policy liabilities references LPS 112 and stressed liabilities LPS 115; changes to those prudential standards will change the definitional and measurement inputs to LRS 115.0.

Interaction with the Life Act and policyholder disclosure: the Standard explicitly states that information reported to APRA under this Reporting Standard is not required to be given to policy owners pursuant to section 124 of the Life Act and does not constitute a reporting document for the purposes of section 124 (para 5). That draws a line between supervisory reporting to APRA and statutory disclosure obligations to policyholders under the Life Act.

Electronic submission infrastructure: the Standard requires electronic submission via methods available on APRA’s website or by a method notified by APRA (para 6). Any legislative or regulatory requirements governing electronic signatures, data protection, or record-keeping under other laws (including Corporations Act duties around financial reporting and auditors) may therefore intersect operationally, although the Standard itself limits those linkages to the requirement that the digital certificate be acceptable to APRA and the submitter be authorised by the PEO or CFO (paras 14-15).

Transition from prior reporting standard: the Standard contains a transition clause requiring reporting under the old reporting standard for certain transitional reporting periods (para 17). This indicates that LRS 115.0 replaces a prior reporting standard and that legacy obligations under the old standard continue to apply to relevant transitional reporting periods.

In practical terms, life companies must therefore coordinate compliance with LRS 115.0 with their obligations under the Life Insurance Act 1995 (registration and statutory fund rules), Prudential Standards LPS 115 and LPS 112 (capital adequacy measurements and stress application), and LPS 310 (audit requirements). The Standard’s frequent cross-references and the dynamic interpretation clause (para 19) mean that changes to those referenced instruments will influence how LRS 115.0 applies in practice.

The Reporting Standard text supplied contains limited explicit amendment history. What is available in the document:

• Commencement: The Standard applies for reporting periods ending on or after 1 July 2023 (para 3). That is the principal effective date provided in the Standard.

• Replacement of an earlier standard: The Standard includes a transition provision requiring life companies to report under the "old reporting standard" in respect of certain transitional reporting periods, where the old standard is defined as "the reporting standard revoked in the determination making this Reporting Standard" (para 17). The transitional reporting period is a reporting period under the old reporting standard which ended before 1 July 2023 and in relation to which the life company was required to report by a date on or after the date of revocation of the old reporting standard (para 17(a)-(b)). The note clarifies that overdue reporting documents required under the old reporting standard remain due in accordance with the old standard notwithstanding revocation.

• Dynamic cross-references: the Interpretation section makes clear 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" (para 19). That means future amendments to the referenced prudential, accounting or auditing standards will, by operation of para 19, affect how LRS 115.0 is interpreted and applied.

What the Standard does not provide in its text:

• The Standard does not contain a schedule of prior amendments, dates of drafting, amending instrument numbers, or legislative history beyond the note that it replaces a previously revoked reporting standard. It does not list prior versions or a chronology of changes.

• There is no explicit statement of the date on which APRA made the determination revoking the old reporting standard, nor the identification of the old standard by name or version number in the text provided, except as "the reporting standard revoked in the determination making this Reporting Standard" (para 17).

Practical implication: practitioners seeking a full amendment history, version control, or the wording of the "old reporting standard" will need to consult APRA’s determinations and the official instrument history (for example, the notice that revoked the old reporting standard and made LRS 115.0) and, where relevant, any repository APRA maintains of prior reporting standards and their revocations. The Standard’s transitional clause anticipates overlap between old and new reporting schedules and preserves obligations for overdue reports required under the old standard.

The text of Reporting Standard LRS 115.0 supplied contains no litigation history. It does not name or cite any cases, tribunal decisions, or litigation outcomes. There are no references to contested APRA decisions, judicial review, or dispute resolution outcomes within the body of the Standard as provided.

What the Standard does state that is litigation-adjacent:

• The Standard requires auditor review and limited assurance engagements (para 11) and connects to LPS 310 (para 7 Note 2), which sets audit and related matters. Disputes could theoretically arise about the sufficiency of auditor assurance, but none are recorded or referenced in this text.

• The Standard gives APRA power to vary reporting requirements and change reporting periods by written notice to a life company (paras 8 and 16). The text does not discuss dispute mechanisms, appeals or review of such notices.

Absent judicial record in the instrument: since LRS 115.0 is a reporting standard that establishes administrative obligations rather than adjudicating rights or penalties, its litigation profile, if any, would be expected to appear in separate case law concerning APRA’s data-collection powers or enforcement actions under the Financial Sector (Collection of Data) Act 2001, the Life Insurance Act 1995, or other prudential instruments. Those materials are not included in the Standard, and no cases are mentioned in the source text.

For practitioners: to identify any litigation involving LRS 115.0 or its predecessor reporting standard, or disputes arising from APRA’s exercise of its data-collection or notice powers, consult court databases, tribunal records, and APRA’s published decisions and determinations. The Reporting Standard itself provides no litigation citations.

1. Five submissions per financial year: the Standard’s structure produces five submissions for a full financial year , four quarterly unaudited returns and one annual audited return , explicitly noted in para 7 and Note 1. This is easy to overlook if teams plan only quarterly and annual tasks without recognising the extra submission frequency and the sequencing (first four submissions may be unaudited and allow estimates; the fifth must be audited and reconciled).

2. Reasonable estimates permitted only for unaudited submissions: para 13 allows life companies to use reasonable estimates for information that will not be audited (that is, the first four submissions in a full financial year). That provides short-term flexibility but creates practical risk: unaudited estimates will be subject to later audit and potential adjustment in the annual audited submission, requiring reconciliation processes and possibly restatement of prior quarter figures.

3. Auditor obligations are substantive: para 11 requires auditors to review and test the life company’s systems, processes and controls supporting reporting, on at least an annual basis, and to perform at least a limited assurance engagement consistent with Auditing and Assurance Standards Board guidance (subject to LPS 310 consistency). This is not a token certification; it imposes substantive assurance work on auditors and implies associated cost and timetable implications for auditor scheduling.

4. Fund-level granularity and valid values: Table 1 and Table 2 instructions require submission at statutory fund or benefit fund level for insurers and at management fund level for friendly societies (Table 1/Table 2 reporting basis). Field-level valid values (e.g. insurance benefit categories, component types) are prescribed. The requirement that any specific combination of values in a table must not appear on more than one row means data-structure constraints must be enforced in reporting systems to avoid rejects.

5. Whole-dollar reporting only: Tables repeatedly specify whole Australian dollars with no decimal place. Systems that produce figures with cents must round or truncate appropriately; incorrect format may produce validation failures.

6. Digital certificate and authorisation chain: para 14 requires a digital certificate acceptable to APRA. Para 15 requires that submitters be authorised by the Principal Executive Officer or Chief Financial Officer. Companies must ensure their digital certificate implementation meets APRA’s acceptance criteria and that appropriate delegations are documented; otherwise submissions may not be accepted or could raise questions about proper authorisation.

7. Tax benefits reporting treatment: the Standard instructs that Insurance Risk Charge - tax benefits and Insurance Risk Charge - tax benefits (FS) be reported as positive values where recognised (Table descriptions). Misunderstanding the sign convention could misstate report totals or cause validation issues.

8. Friendly societies have additional servicing components: Table 2 lists items (expected management fees, expected servicing expenses, expected deficiency before/after prescribed multiplier, total servicing expense reserve, additional deficiency from prescribed servicing expense stress, reduction in management fees assumed under stress) specific to friendly societies’ management funds. Friendly societies must ensure reconciliations between benefit funds and management funds are in place to produce these figures reliably.

9. No policyholder disclosure obligation: para 5 states the information reported under this Standard is not required to be given to policy owners under s124 of the Life Act. This creates a potential internal information asymmetry , policyholders do not automatically receive the data that APRA collects , which may matter for governance and public relations, but it is an explicit legal point to note.

10. APRA’s discretion to vary reporting: paras 8 and 16 permit APRA to change reporting periods or vary reporting requirements for a particular life company by written notice. This introduces supervisory flexibility but also regulatory uncertainty for firms , they must have systems capable of adapting to tailored reporting demands at short notice.

11. Transition overlaps: para 17 requires reporting under the old reporting standard for certain transitional reporting periods that ended before 1 July 2023 but were required to be reported on or after revocation. Practitioners must track whether any outstanding obligations under the old standard exist and ensure timely submission in accordance with the old standard’s rules.

12. Limited enforcement detail in the Standard: as noted earlier, the Standard does not specify penalties or enforcement steps within its text. Firms cannot rely on the absence of such provisions in the Standard to assume no regulatory consequences; enforcement authorities and sanctions are established in other legislation or APRA’s broader powers not reproduced here.

13. Cross-reference to other prudential standards: the Standard requires measurements be made in accordance with LPS 112 and LPS 115 for adjusted and stressed policy liabilities respectively (Definitions). Changes to those prudential standards will change how LRS 115.0 reporting must be prepared, so firms must monitor updates in those linked standards.

14. Data uniqueness constraint: the guidance that "any specific combination of values in the table must not appear on more than one row" can be operationally tricky when product characteristics overlap; reporting systems must enforce composite-key uniqueness at submission time.

15. Repetition in the instrument: the supplied text contains repeated sections and duplicated instructions. That does not change legal obligations, but practitioners should refer to the authoritative APRA version and the reporting form available on APRA’s website to avoid confusion caused by duplication in working versions.

Below is a practical compliance checklist and recommended implementation steps grounded in the Standard’s text (citations refer to paragraph numbers and table instructions where relevant).

1. Confirm scope and reporting periods

   • Verify that the entity is a life company registered under the Life Insurance Act 1995 and that reporting periods end on or after 1 July 2023 (para 3).
   • Expect quarterly unaudited submissions for each quarter and an annual audited submission (para 7 and Note 1). Build the calendar: four quarterly submissions and one annual audited submission per financial year.

2. Prepare fund-level data architecture

   • Ensure systems can produce data at the required fund granularity: statutory fund for life insurers; benefit fund for friendly societies; and management fund for friendly societies where Table 2 applies (Table 1/Table 2 Reporting basis).
   • Map product/benefit lines to the valid insurance benefit categories prescribed (non-participating with/without entitlement to discretionary additions; participating benefits; friendly society benefits) (Table 1).

3. Implement data definitions and field constraints

   • Implement the exact Insurance Risk Charge component types required by Table 1 and Table 2 (e.g., adjusted policy liabilities gross/net, stressed policy liabilities gross/net, tax benefits, expected management fees, expected servicing expenses, expected deficiency before/after multiplier, total servicing expense reserve, additional deficiency from prescribed servicing expense stress) (Definitions and Table instructions).
   • Enforce unique rows so that any specific combination of values does not appear more than once as per the General instructions.
   • Ensure values are reported in whole Australian dollars (no decimals) (Units of measurement).

4. Actuarial and valuation preparation

   • Prepare adjusted policy liabilities in accordance with LPS 112 and stressed policy liabilities in accordance with LPS 115 (Definitions A and S).
   • Prepare actuarial valuations and calculations in accordance with prudential standards in force for the reporting period (para 13).
   • If preparing unaudited quarterly submissions, note that "reasonable estimates" may be used for items that will not be audited (first four submissions) but plan to reconcile and replace estimates with audited numbers in the annual submission (para 13).

5. Quality control, governance and audit

   • Implement systems, processes and controls that produce the reported information and document them for Auditor review (para 11).
   • Engage the Auditor early to schedule annual review and the limited assurance engagement required by para 11(b), and ensure the Auditor understands the reporting timetable and submission format.
   • Board and senior management must adopt policies and procedures for internal review and authorisation of reported data (para 12). Document delegations that authorise the submitter.

6. Submission and authorisation workflow

   • Implement electronic submission via APRA’s website method (para 6(a)), and monitor APRA notifications for any alternative submission method (para 6(b)).
   • Obtain and deploy an APRA-acceptable digital certificate for digital signing of submissions (para 14). Coordinate with IT and legal for certificate procurement, security, and continuity planning.
   • Ensure the officer or agent submitting is authorised by the Principal Executive Officer or Chief Financial Officer (para 15). Maintain written delegation records to evidence authorisation.

7. Timing and scheduling

   • Quarterly unaudited data: schedule preparation so submissions are ready within 20 business days after quarter-end (para 9(a)).
   • Annual audited data: schedule audit and produce annual audited submission with the annual auditor’s report within three months after financial year end (para 9(b) and Note 2).
   • Maintain contingency procedures to seek written extensions from APRA if necessary (para 10).

8. Friendly societies specific steps

   • For friendly societies, prepare management fund-level reporting for Table 2 items like expected management fees, expected servicing expenses, expected deficiencies, total servicing expense reserve, and reductions in management fees assumed under asset/insurance stress (Table 2).
   • Ensure reconciliations between benefit funds and the management fund are in place to derive expected management fees and reductions under stress.

9. Validation and test submissions

   • Build validation logic to enforce the table structure and valid values for each field; perform trial uploads to APRA test environments if available to identify formatting or value errors (General instructions and Table structure).
   • Enforce the "no duplicate combination" rule for reported rows to avoid rejections.

10. Monitor for APRA notices and standard changes

    • Track APRA notices that may change reporting periods for the company (para 8) or vary reporting requirements (para 16). Implement monitoring to detect when APRA issues such notices and to adapt reporting promptly.
    • Monitor changes in LPS 112, LPS 115, LPS 310, LPS 001, and relevant accounting/auditing standards because para 19 makes the Standard subject to those instruments as in force from time to time.

11. Documentation and retention

    • Retain evidence sufficient to demonstrate that reported figures are the product of reviewed systems, processes and controls, consistent with auditor review (para 11).
    • Maintain audit trails for authorisations (para 15) and digital signatures (para 14).

12. Reconciliation and post-audit adjustments

    • Maintain processes to reconcile unaudited quarter estimates with the audited annual submission, and to document any changes or restatements arising from the auditor’s limited assurance or full audit findings (paras 11 and 13).

13. Operational resilience and continuity

    • Ensure the digital certificate programme has continuity plans for expiry and replacement to avoid submission failures.
    • Build capacity to respond quickly to APRA-written notices adjusting reporting frequency or content (paras 8 and 16).

14. Practical record-keeping of tax benefit sign conventions

    • Ensure tax benefits items are reported as positive values where benefits are recognised and that reductions in management fees assumed under stress are reported as positive values where they have been assumed for friendly societies (Table notes).

15. Transition obligations

    • Review any outstanding reporting obligations that remain under the old reporting standard for transitional reporting periods as described in para 17 and ensure overdue documents are delivered in accordance with the old standard where applicable.

Carrying out the steps above will align an entity’s reporting architecture, control environment, audit engagement, and governance processes with the explicit duties and mechanisms set out in LRS 115.0. For detailed field-level mapping, practitioners should use the official APRA reporting templates and technical instructions published on APRA’s website, and coordinate the Auditor’s review plan with the submission timetable and the requirements in para 11 and LPS 310.