Related party exposures. The central concept is the company’s exposures to related parties, though the standard itself does not define “related party” or “exposure”. Instead, paragraph 16(a) provides that words and expressions have the meanings given in Prudential Standard LPS 001 Definitions, unless the contrary intention appears. The actual definitions reside in LPS 001, which is referenced but not reproduced here. In practice, related party exposures would include loans, guarantees, derivatives, investments, and other credit or market exposures to entities connected with the life company, such as parent companies, subsidiaries, directors, senior management, and substantial shareholders. The form LRF 112.3 (not attached to the standard) presumably specifies the categories and valuation methods.

Life company. This term includes both life insurance companies and friendly societies registered under the Life Insurance Act (paragraph 3). The standard treats them identically for reporting purposes.

Reporting period. The default reporting periods are each quarter (based on the life company’s financial year) for unaudited data, and each full financial year for audited data (paragraph 7). APRA may change the frequency for a particular life company by written notice (paragraph 8). Similarly, the due dates are those stated in Reporting Standard LRS 001 Reporting Requirements (LRS 001) unless APRA specifies a different time (paragraph 9).

Audited versus unaudited. Four quarterly submissions are unaudited; the annual submission is audited. Unaudited submissions may use reasonable estimates for actuarial valuations and calculations (paragraph 12). Audited submissions must be based on systems reviewed and tested by the auditor, with the annual auditor’s report attached per LPS 310.

Limited assurance engagement. The auditor must perform at least a limited assurance engagement on the life company’s systems, processes and controls that support the reported information (paragraph 10(b)). This is a lower level of assurance than a reasonable assurance (full audit) engagement, but still requires professional standards issued by the AUASB.

Digital certificate. The officer lodging the form must have a digital certificate acceptable to APRA (paragraph 13). This is a technical authentication requirement to ensure data integrity and non repudiation.

Authorised officer. The person digitally signing must be authorised by either the Principal Executive Officer or the Chief Financial Officer (paragraph 14). This does not require the signatory to be the PEO or CFO personally, but the delegation must come from one of those two executives.

Variation power. APRA may vary the reporting requirements of Form LRF 112.3 in relation to a particular life company by written notice (paragraph 15). This allows individual tailoring, but also introduces uncertainty: a life company cannot assume the standard form will remain fixed for its circumstances.

Capital standards. The purpose clause (paragraph 2) mentions assessing compliance with capital standards, defined in paragraph 16(b) as prudential standards relating to capital adequacy as defined in LPS 001. Thus the reported data feeds into the life company’s capital adequacy assessment, particularly the treatment of related party exposures under the capital framework.

Section 124 exemption. Paragraph 5 confirms that the information reported under this standard is not required to be given to policy owners under section 124 of the Life Insurance Act. This removes any risk that APRA data could be used for policyholder disclosure; the data is solely for supervisory use.

The primary obligors are all life insurance companies and friendly societies registered under the Life Insurance Act (paragraph 3). This includes both domestic and foreign owned life insurers operating in Australia. The standard applies to reporting periods ending on or after 1 April 2023, meaning all such entities must have established systems to capture related party exposures from that date onward.

Within each life company, the standard imposes concrete duties on specific officers and governing bodies. The Board of directors and senior management are collectively responsible for ensuring that an appropriate set of policies and procedures for the authorisation of data submitted to APRA is in place (paragraph 11). This is not merely a box ticking exercise; it requires ongoing governance over the data production line. The Principal Executive Officer (PEO) and Chief Financial Officer (CFO) are the two officers who may authorise the person (or themselves) to digitally sign the submission (paragraph 14). The actual officer who submits the information must use a digital certificate acceptable to APRA (paragraph 13). That officer could be the PEO, CFO, or a delegate, but the delegation must come from one of those two.

The external auditor of the life company is directly affected. Under paragraph 10, the auditor must review and test the life company’s systems, processes and controls that support the reporting of the information. This review must be conducted annually (or more frequently if needed) and must be at least a limited assurance engagement consistent with AUASB standards, to the extent not inconsistent with LPS 310. The auditor’s scope here is broader than a typical financial statement audit: it targets the internal control environment over regulatory data, not just the final numbers. The annual auditor’s report must be submitted with the audited annual form (Note 2 to paragraph 7). This adds cost and complexity for both the auditor and the life company.

APRA itself is the recipient and user of the data. The standard grants APRA unilateral powers to vary reporting periods (paragraph 8) and the form’s requirements (paragraph 15) for a particular life company. This means a life company could receive a notice altering its obligations with no industry wide consultation. APRA also sets the acceptable digital certificate method and the submission method (paragraph 6).

Smaller entities, such as friendly societies, are likely to feel the compliance burden more acutely relative to their scale. The requirement for an annual limited assurance engagement over systems, processes and controls is a fixed cost that does not scale down proportionally with the size of the life company. This may create an implicit barrier to entry or a disincentive for small mutual structures. The standard does not provide any exemption for small life companies or friendly societies, and APRA’s discretion under paragraph 8 to “specify reporting periods” only changes frequency, not the substantive reporting or audit requirements.

Policy owners are deliberately unaffected by this standard. Paragraph 5 explicitly states the information is not a reporting document under section 124 of the Life Insurance Act, so policyholders have no right to receive the APRA data. This insulates the life company from having to disclose sensitive related party information to its customers, but also means policyholders cannot independently assess related party risk from the same data.

Duty to complete and lodge the form. The core obligation is in paragraph 4: “A life company must provide APRA with the information required by Form LRF 112.3 for each reporting period.” This is a strict obligation, not qualified by materiality. The life company must identify its related party exposures, populate the form according to the specific instructions (which are cross referenced but not reproduced in the standard), and submit it electronically using APRA’s approved method.

Duty to report at the correct frequency and on time. Paragraph 7 sets a default cadence: quarterly unaudited submissions and an annual audited submission, totalling five per financial year. The due dates are determined by LRS 001 (paragraph 9(a)) unless APRA has varied them by notice (paragraph 9(b)). Missing a deadline would breach the standard.

Duty to maintain data quality controls. Paragraph 10 requires the life company’s systems, processes and controls to be reviewed and tested by the auditor annually. This is not a one off setup; the auditor must form an opinion on the reliability and accuracy of data annually, and more frequently if necessary. The life company cannot simply rely on the auditor’s work as a substitute for its own controls; paragraph 11 separately requires the life company to have internal policies and procedures for authorisation of data, with Board and senior management responsibility.

Duty to ensure actuarial compliance. Paragraph 12 mandates that actuarial valuations and calculations used in preparing the information must be in accordance with prudential standards in force for the reporting period. For unaudited submissions, the life company may use reasonable estimates, but must still comply with the underlying standards. This prevents the use of outdated methodologies or non compliant assumptions.

Duty to obtain digital authorisation. Paragraphs 13 and 14 require two layers of authorisation: the submitting officer must have a digital certificate acceptable to APRA, and must be authorised by the PEO or CFO. This ensures accountability: the PEO or CFO is on the hook for whom they authorise. The digital certificate provides non repudiation, so the life company cannot later disavow a submission.

Right to use estimates. Paragraph 12 allows the use of reasonable estimates for unaudited submissions (the first four of the year). This is a practical concession to reduce the burden of producing quarterly data on a tight timeline. However, estimates must be “reasonable” and must still comply with prudential standards. APRA might challenge estimates that are unduly favourable, particularly for related party exposures that could artificially reduce capital requirements.

Right to have APRA vary requirements (or face variations imposed upon the life company). Paragraphs 8 and 15 give APRA the power to vary reporting periods or the form’s requirements for a particular life company. While this is a right for APRA, it can be seen as a potential burden for the life company; but it also means a life company can seek relief if its circumstances warrant it. The standard does not provide a formal process for requesting a variation, but APRA can act by “written notice”.

Right to exclude data from policy owner disclosure. Paragraph 5 is protective of the life company’s confidentiality: the reported data is not required to be given to policy owners under section 124 of the Life Insurance Act. This prevents policyholders from demanding access to what could be commercially sensitive information about related party dealings.

The standard itself does not prescribe monetary penalties, imprisonment, or licensing sanctions. Instead, it is made under the Collection of Data Act, which creates its own enforcement framework. Under section 15 of that Act, a person who fails to provide information as required by a reporting standard may be subject to civil penalty provisions. The maximum penalty is 50 penalty units (currently $313.00 per unit under the Crimes Act 1914, though the Collection of Data Act may have its own penalty regime). APRA can also seek injunctions to compel compliance. The standard is not a standalone source of penalty; it is the instrument through which the Collection of Data Act’s penalty regime is triggered.

Beyond financial penalties, the purpose of the data collection is prudential supervision. APRA uses the information to assess compliance with capital standards (paragraph 2). If a life company’s reported related party exposures reveal a breach of the capital framework (e.g., LPS 112 Capital Adequacy, which is not referenced here but is the likely underlying standard), APRA could take supervisory action: imposing additional capital requirements, restricting business activities, requiring divestment of exposures, or appointing a statutory manager under the Life Insurance Act. The reporting standard is thus a detection mechanism; the real enforcement bite comes from the prudential standards and APRA’s extensive supervisory powers.

The auditor’s role in enforcement is indirect. Under paragraph 10, the auditor must perform a limited assurance engagement on the systems, processes and controls. If the auditor identifies material weaknesses in the controls, it would report them to the life company and possibly to APRA under LPS 310. A negative auditor opinion could trigger APRA scrutiny and potentially erode confidence in the life company’s regulatory compliance.

The obligation to have the data digitally signed by an authorised officer (paragraphs 13-14) means that the PEO or CFO cannot distance themselves from a false or misleading submission. An incorrect submission could expose those officers or the life company to liability under the Collection of Data Act for providing false or misleading information, which carries a higher penalty (up to 12 months imprisonment under section 137.1 of the Criminal Code for providing false information to a Commonwealth entity, if intention or recklessness is proved).

In practice, APRA’s enforcement approach for reporting standards is typically escalation based: requests for correction, formal directions, and ultimately civil penalty proceedings or licence conditions. The standard does not create a private right of action for policyholders or third parties; enforcement is exclusively APRA’s domain.

This reporting standard operates within a web of Commonwealth legislation and prudential standards.

Financial Sector (Collection of Data) Act 2001: The standard is made under section 13 of this Act. That Act provides the legal authority for APRA to impose reporting requirements, and contains the penalty provisions for non compliance. The standard is a legislative instrument (disallowable by Parliament), though it is not subject to the usual parliamentary scrutiny procedures for legislative instruments under the Legislation Act 2003 because APRA’s reporting standards are exempted from sunsetting by regulation.

Life Insurance Act 1995: The standard applies to life companies registered under that Act. Section 124 of the Life Insurance Act is directly addressed in paragraph 5: the information reported is not required to be given to policy owners under that provision. This ensures that the regulatory data does not accidentally become a disclosure document for policyholder purposes, which could create confusion or liability risks. The standard also cross references “registered under the Life Insurance Act” in paragraph 3.

Prudential Standard LPS 001 Definitions: The interpretation clause (paragraph 16(a)) imports all definitions from LPS 001. That standard defines terms like “life company”, “capital standards”, and presumably “related party”, “exposure”, and other key concepts used in Form LRF 112.3. This means the standard’s meaning is not self contained; one must consult LPS 001, which itself may incorporate definitions from other standards.

Prudential Standard LPS 310 Audit and Related Matters: The annual audited form must be submitted with the auditor’s report required under LPS 310 (Note 2 to paragraph 7). Further, paragraph 10(b) requires the auditor’s limited assurance engagement to be consistent with LPS 310 to the extent that AUASB standards are not inconsistent with LPS 310. LPS 310 governs audit arrangements for life companies and interacts with the auditor’s duties under this reporting standard.

Reporting Standard LRS 001 Reporting Requirements: The due dates for submissions are set by LRS 001 (paragraph 9(a)). LRS 001 also contains the general instruction guide (Attachment A) which must be read in conjunction with this standard (as stated in the objective). This means a life company must consult LRS 001 to determine the exact timeframes for lodging Form LRF 112.3.

Corporations Act 2001: The term “financial year” in this standard has the meaning given in the Corporations Act (paragraph 16 interpretation). This ensures alignment with the company’s reporting period under Australian corporate law.

Auditing and Assurance Standards Board (AUASB) standards: The auditor’s review and testing must be consistent with professional standards and guidance notes issued by the AUASB as amended from time to time (paragraph 10(b)). These include ASAE 3000 Assurance Engagements Other than Audits or Reviews of Historical Financial Information and ASAE 3450 Assurance Engagements on Controls. The standard gives precedence to LPS 310 over AUASB standards in case of inconsistency.

Prudential standards generally: Actuarial valuations and calculations must be in accordance with “the prudential standards in force for the reporting period” (paragraph 12). This catches any prudential standard that is relevant to the valuation of related party exposures, such as LPS 112 Capital Adequacy, LPS 116 Capital Adequacy: Asset Concentration Risk, or LPS 222 Insurance Contracts.

The instrument provided does not include any amendment history. The text reflects a consolidated version of Reporting Standard LRS 112.3 as it applies from 1 April 2023. No amending instruments or commencement dates for amendments are listed. The instrument was likely made by APRA in early 2023 under a legislative instrument number (e.g., F2023Lxxxxx) on the Federal Register of Legislation, but that information is not reproduced here.

The standard appears to be a new reporting standard. It may have replaced an earlier reporting standard on related party exposures (possibly LRS 112.2 or an equivalent under the previous reporting framework), but the text does not reference any predecessor or transitional arrangement. The application paragraph (3) states it applies for reporting periods ending on or after 1 April 2023, suggesting that life companies used an older standard for periods ending before that date.

Because the standard is a legislative instrument, any later amendments would be made by APRA issuing a new reporting standard that would revoke and replace LRS 112.3, or by a formal amending instrument. The text refers to LRS 001 and LPS 310, both of which are subject to periodic updates, but those would not amend LRS 112.3 directly; they would affect its operation via cross references.

For a life company wanting to verify the current version, the only safe method is to consult the Federal Register of Legislation (www.legislation.gov.au) for the latest compilation of LRS 112.3. The standard itself does not contain a version control table or list of amendments. The absence of an explicit amendment history in the provided text means that a life company cannot rely on a static PDF; periodic checks are necessary.

The reporting standard text does not reference any court cases, administrative appeals, or litigation history. No judicial decisions are mentioned. This is not surprising for a data collection standard that is primarily procedural and rarely the direct subject of litigation. However, litigation could arise in several ways under the parent legislation.

First, a life company might challenge the validity of the standard itself under the Collection of Data Act on grounds such as ultra vires or unreasonableness. For example, if APRA demanded information that was not reasonably related to prudential supervision, a judicial review application under the Administrative Decisions (Judicial Review) Act 1977 might be possible, though APRA’s decision to make a reporting standard is a legislative act, not a decision subject to judicial review. Alternatively, a constitutional challenge to the Collection of Data Act’s validity could arise, but none is recorded in the source.

Second, enforcement proceedings under the Collection of Data Act could generate case law. The Act has civil penalty provisions, and APRA could seek orders in the Federal Court for pecuniary penalties or injunctions. The standard would be the primary rule breached. However, no such cases are cited in the instrument.

Third, legal disputes over the definition of “related party” or “exposure” under LPS 001 might arise in the context of a penalty proceeding or a direction from APRA to treat a certain exposure as requiring additional capital. Those disputes would typically be resolved in the Administrative Appeals Tribunal (AAT) on review of APRA’s supervisory decisions, not in court directly under the reporting standard.

The absence of litigation history does not mean the standard is unimportant; it means that compliance has been generally uncontentious or that any disputes have been settled at the supervisory level without published decisions. A life company should not assume that the standard is immune to legal challenge, but the practical risk of being taken to court over this specific form is low. The greater risk is enforcement by APRA based on the data submitted.

Five submissions per year catch. Paragraph 7 and the notes clarify that the form must be submitted five times for a full financial year: four quarterly unaudited returns plus one audited annual return. A life company that thinks it only needs to submit annually because it is a small friendly society will be caught out. The quarterly submissions are not optional.

Auditor reviews systems, not just data. Paragraph 10 requires the auditor to review and test the life company’s systems, processes and controls supporting the reporting. This is broader than a typical audit of the numbers. The auditor must also test annually “more frequently if necessary” to form an opinion on reliability and accuracy. If the life company’s internal control environment is weak, the auditor may issue a qualified or adverse assurance report under LPS 310, which could trigger APRA attention.

Estimates are only for unaudited submissions. Paragraph 12 allows reasonable estimates for unaudited submissions, but the annual audited submission cannot use estimates unless they comply with prudential standards. A life company that uses estimates for its annual audited return would breach the standard and likely the capital standards as well.

Digital signature requirement is not optional. Paragraph 13 mandates a digital certificate acceptable to APRA. If an officer tries to email a PDF without a digital signature, the submission will not be accepted as meeting the standard. The standard does not specify which certificates are acceptable; a life company must check APRA’s website or contact APRA directly.

Authorisation delegation limits. The signing officer must be authorised by the PEO or CFO (paragraph 14). The standard does not allow authorisation by the Company Secretary, Head of Compliance, or the Board chair unless that person also holds the PEO or CFO title. This creates a bottleneck: if both the PEO and CFO are unavailable, the form may be delayed.

APRA can vary requirements without the life company’s consent. Paragraphs 8 and 15 allow APRA to change reporting periods or the form’s requirements for a particular life company by written notice. There is no requirement for consultation. A life company that receives such a notice must adjust its systems quickly.

The form and instructions are not included in the standard. The standard repeatedly says “Form LRF 112.3” and “associated specific instructions” but does not reproduce them. A life company must obtain the form separately from APRA. If the form contains unexpected data points (e.g., detailed breakdowns by counterparty type, collateral, maturity), the compliance team must have access to it.

Board and management liability for data authorisation. Paragraph 11 makes the Board and senior management responsible for ensuring an appropriate set of policies and procedures for authorisation. This is a personal responsibility, not a corporate one. In a breach, APRA could point to inadequate board oversight as an aggravating factor.

Section 124 exemption does not apply to all data. While the APRA reported data is exempt from policy owner disclosure (paragraph 5), the Life Insurance Act still requires other documents to be given to policy owners. A life company cannot argue that any related party exposure data is now exempt from disclosure; only the specific submissions under this standard are protected.

“Reporting period” can be changed retrospectively? Paragraph 8 says APRA may “change the reporting periods, or specify reporting periods, for the particular life company.” While the power is presumably prospective, the wording does not explicitly limit it to future periods. A life company that receives a notice changing periods should check the effective date.

Compliance with LRS 112.3 requires a structured, multi step approach within the life company. The steps are cumulative and must be embedded in ongoing operations.

Step 1: Identify the responsible officers. The PEO and CFO must be identified, as only they can authorise signatories. The company should decide who will be authorised to digitally sign the form (could be the PEO or CFO themselves, or a delegate). That individual must obtain a digital certificate acceptable to APRA. The PEO/CFO must formally document the authorisation in writing, as APRA may ask for evidence.

Step 2: Understand the data requirements. The company must obtain Form LRF 112.3 and its specific instructions from APRA. The form will define what constitutes a related party exposure for the purposes of this return. The company should map its existing internal reporting of related party transactions (loans, guarantees, investments, derivatives, etc.) to the form’s fields. Definitions from LPS 001 must be applied. If any exposure categories are unclear, the company should seek clarification from APRA or consult LPS 001.

Step 3: Build or upgrade systems. The company’s systems, processes and controls must be capable of capturing, calculating, and verifying related party exposure data in the required granularity. Paragraph 10 requires these systems to be reviewed and tested by the auditor. Therefore, the company should implement controls around data accuracy, completeness, and timely capture. A control matrix and a data dictionary will help the auditor assess the environment.

Step 4: Implement internal authorisation procedures. Paragraph 11 requires the Board and senior management to ensure an appropriate set of policies and procedures for authorisation. The company should adopt a formal policy specifying: who prepares the data, who reviews it, who signs off, and how the digital certificate is used. The policy should cover error correction procedures after submission.

Step 5: Engage the external auditor early. The auditor must review and test the systems, processes and controls at least annually. This is not a year end afterthought; the auditor needs access to the systems during the year. The company should agree with the auditor the scope of the limited assurance engagement and the evidence required. The auditor’s opinion under LPS 310 must address the reliability and accuracy of data. The annual audited form must be accompanied by the auditor’s report.

Step 6: Prepare the quarterly unaudited submissions. For each quarter, the company must populate Form LRF 112.3 using its systems. Actuarial valuations may use reasonable estimates (paragraph 12). The data must be accurate to the best of the company’s knowledge, but the auditor has not yet opined on it. The form must be submitted by the due date in LRS 001. The authorised officer digitally signs using the digital certificate.

Step 7: Prepare the annual audited submission. For the full financial year, the company must produce a final audited version of the form. The auditor’s report (and any management letter) must be included. The actuarial valuations must comply fully with prudential standards; estimates are no longer permitted.

Step 8: Monitor for APRA variations. APRA may issue a written notice changing the reporting periods or form requirements for the company (paragraphs 8 and 15). The company must ensure that its compliance officer monitors correspondence from APRA and adjusts systems, policies, and due dates accordingly.

Step 9: Retain records. Although not explicit in the standard, the Collection of Data Act imposes record keeping obligations. The company should retain all underlying data, calculations, and authorisation records for at least seven years (the general limitation period under the Act) to defend against any future APRA inquiry.

Step 10: Periodic health check. The company should annually review its compliance program for this standard, including a review of LPS 001 definitions (which may change) and any revisions to LRS 001 due dates or LRF 112.3 form instructions. The auditor’s annual review of systems should feed into a continuous improvement process.

By following these steps, a life company can minimise the risk of a late, incomplete, or inaccurate submission and the regulatory consequences that follow. The cost of compliance is not trivial, particularly for the auditor’s limited assurance engagement, but non compliance carries potentially greater reputational and financial costs under the enforcement powers of the Collection of Data Act and the Life Insurance Act.