Australian Prudential Regulation Authority (confidentiality) determination No. 1 of 2022

The instrument rests on a small set of statutory and administrative concepts set out in the text. These are the levers by which the confidentiality status of data is changed and by which APRA may subsequently act.

• Determination power under the APRA Act. The delegate acts under s 57 of the Australian Prudential Regulation Authority Act 1998 to make a confidentiality determination. The instrument explicitly cites s 57 and paragraph 57(2)(b) of the Act as the head of power used to determine that specified reporting documents do not contain confidential information. The instrument also relies on the Acts Interpretation Act 1901, subsection 33(3), for delegation/interpretation formalities. The combination anchors the determination to APRA's statutory confidentiality regime.

• Confidentiality and publication under the APRA Act. The Note in the instrument points to subsection 56(5C) of the APRA Act as the publication gateway: once a document or part is determined not to contain confidential information, APRA may publish the non-confidential information under that subsection. The instrument itself does not mandate publication; it makes the data non-confidential so publication becomes a permissible action under the Act.

• Scope defined by reporting documents and reporting standards. The determination applies to "reporting documents" as defined by section 13 of the Financial Sector (Collection of Data) Act 2001. The Schedule identifies specific reporting standards (GRS numbering) and GRF form numbers and, in many instances, particular sections or data items within each form. The instrument therefore works by identifying particular data flows that APRA receives under the financial sector data-collection regime and removing confidentiality protections for them as specified.

• Timing condition , 14 day window. The determination applies only after a 14 day period has elapsed from the date the general insurer (or Level 2 parent entity, as applicable) "was required to provide" the information under the relevant reporting standard. For general insurers the reference is to paragraph 5 of Reporting Standard GRS 001 Reporting Requirements; for Level 2 parent entities the reference is to paragraph 7 of the same Reporting Standard. The 14 day delay is a mechanical trigger in the instrument that must be met before the specified reporting documents are treated as non-confidential.

• Distinction between types of reporting and entities. The Schedule separates: (a) quarterly and annual information given to APRA by a general insurer under current GRS instruments, (b) semi-annual and annual information given to APRA by a parent entity of a Level 2 insurance group under Level 2 GRS instruments, and (c) transitional or superseded reporting documents from prior vintages of GRS. Many entries indicate precise sections or exclusions (for example certain "adjustments" or "exclusions" are expressly left out of the non-confidential scope).

• Revocation of an earlier determination. The instrument expressly revokes Australian Prudential Regulation Authority (confidentiality) determination No. 11 of 2015. That revocation is part of the instrument's operative effect. The text therefore both replaces (in substance) and updates APRA's prior approach to confidentiality for those reporting documents.

These concepts together form the mechanism: APRA, using delegated statutory power, declares a defined set of reporting forms and parts to be non-confidential after a set time period following the obligation-to-provide date, thereby enabling APRA to publish the specified non-confidential data under the statutory publication power.

The determination names two categories of data providers as directly affected: (1) general insurers who submit quarterly and annual reporting information to APRA under the identified General Insurance Reporting Standards (GRS), and (2) parent entities of Level 2 insurance groups that provide semi-annual and annual information under the Level 2 GRS instruments. The Schedule cross-references many GRF form numbers and, for Level 2 groups, GRF form variants with a _G suffix.

Who pays and who bears the immediate operational consequences:

• General insurers. They supply the reporting documents to APRA under the Financial Sector (Collection of Data) Act 2001 and the specified reporting standards. For the items listed, once the 14 day window expires, the forms or parts of forms are determined to be non-confidential. That means information that previously might have been treated as confidential to APRA is subject to being lawfully published by APRA under subsection 56(5C).

• Parent entities of Level 2 insurance groups. The Schedule includes semi-annual and annual parts for parent entities of Level 2 groups. These entities supply consolidated or group-level data. The determination treats specified parts of those semi-annual and annual returns as non-confidential after the 14 day rule.

• APRA. APRA is the decision-maker that now has legal authority to publish the specified non-confidential information. The instrument does not compel APRA to publish; it removes confidentiality for the specified items and therefore enables APRA to exercise its publication power under subsection 56(5C). APRA's Data Analytics & Insights team is signatory here; the delegate making the determination is the General Manager of that area.

• Market participants and public users. The determination, by making certain prudential data non-confidential and publishable, affects competitors, investors, auditors, reinsurers, rating agencies, journalists, researchers and the public. Those parties may gain access to granular prudential metrics (capital components, asset risk charges, claims development tables and similar items listed in the Schedule) if APRA elects to publish.

• Internal compliance and legal teams. Insurers' compliance, actuarial and finance teams must track which forms and parts are listed and the timing trigger for potential public release. The Schedule includes many specific exclusions and data-item granularity; internal process owners must reconcile their reporting templates with the listed GRF parts to identify what becomes non-confidential.

Who decides:

• The delegate under s 57 of the APRA Act makes the determination, evidenced by the signature of the General Manager Data Analytics & Insights. APRA retains discretion whether to publish non-confidential information under s 56(5C).

What behaviour changes:

• Insurers will need to treat the listed reporting items as potentially publishable after the 14 day period and may adjust pre-submission processes accordingly. In practice this could affect internal review cycles, decisions about whether to flag particular submissions under any confidentiality processes (if such processes exist elsewhere), and communications to boards or brokers about disclosure timing.

• APRA may choose to publish the information, which could alter market transparency. The instrument does not impose additional reporting burdens but changes post-submission confidentiality expectations.

The instrument does not enumerate affected third-party contracts, reinsurance counterparties, or other external relationships. Any effect on those relationships would follow from publication choices that APRA might make under s 56(5C).

The instrument itself is not a reporting standard; it does not create new duties to provide data. Instead it modifies the confidentiality status of already-required reporting documents once certain conditions are met. Key duties and rights arising from the text are therefore procedural and conditional.

Duties (as implicated by the instrument):

• Duty to provide reporting documents remains governed by the Financial Sector (Collection of Data) Act 2001 and by the GRS instruments listed in the Schedule. The determination refers to "reporting document" as defined in section 13 of that Act. The instrument assumes the prior existence of statutory duties to supply the forms under those regimes; it does not alter those duties.

• Timing obligations under GRS 001. The instrument triggers only after a period of at least 14 days has elapsed from the date a general insurer (or Level 2 parent) "was required to provide" the information under paragraph 5 (general insurers) or paragraph 7 (Level 2) of Reporting Standard GRS 001 Reporting Requirements. The duty to determine the "required to provide" date rests with the reporting standard's timing provisions; compliance teams must track that date to know when the confidentiality removal comes into effect.

Rights and administrative powers:

• APRA's right to determine confidentiality status. Under paragraph 57(2)(b) and s 57 more generally, the delegate determines specified documents do not contain confidential information. The instrument exercises that right and clarifies which documents and parts are non-confidential after the timing condition.

• APRA's right to publish non-confidential information. Subsection 56(5C) of the APRA Act is the statutory mechanism referenced in the instrument's Note. Once documents are non-confidential, APRA may publish the non-confidential information. The determination therefore grants APRA the right to publish the specified items, but does not oblige APRA to do so.

Implied obligations for affected entities (practical duties arising from the instrument):

• Recordkeeping of submission and due dates. Because the 14 day delay is measured from the date the insurer was required to provide the information under the relevant GRS paragraph, an immediate compliance implication is that reporting entities must document the "required to provide" date for each listed report to determine when confidentiality protection lapses under this determination.

• Reconcile forms to Schedule entries. Many Schedule entries specify sub-sections or exclude particular items (for example the phrase "excluding 'Adjustments and exclusions to prudential requirements for the OCL Insurance Risk Charge'"). Reporting entities must map their internal returns to the GRF parts listed to determine which data items are captured.

Limitations and boundaries:

• The determination does not grant a general right to publish all reporting documents; it lists specific forms and parts. If a reporting document or a part is not identified in the Schedule, the determination does not change its confidentiality status. The instrument also often excludes particular data items or adjustments, leaving them outside the determination’s non-confidential ambit.

• The instrument does not create penalties for failure to provide reporting documents or for release of information by reporting entities. Enforcement of reporting duties remains with the underlying data-collection legislation and the APRA Act, not with this instrument.

Procedural note:

• The instrument commences on registration. The determination becomes operative from the registration date; entities should check the Federal Register of Legislation for the actual commencement date and take the 14 day condition into account from the "required to provide" date.

The determination itself does not create new offences, penalties, civil remedies, or administrative sanctions. It is an administrative instrument that changes confidentiality status of specified reporting documents and references existing statutory authorities. The instrument must therefore be read in conjunction with the enforcement and penalty provisions in the underlying Acts cited.

What the instrument says about enforcement:

• No penalty provisions are included in the instrument text. The determination contains no express criminal, civil or administrative sanctions for either APRA or reporting entities in relation to the confidentiality decision.

• Enforcement of the requirement to provide the reporting documents is not altered by this instrument. Reporting obligations and any sanctions for non-compliance remain governed by the Financial Sector (Collection of Data) Act 2001 and the relevant provisions of the APRA Act and the reporting standards themselves. The instrument does not purport to modify those enforcement regimes.

How publication/disclosure interacts with enforcement powers:

• Publication is enabled under subsection 56(5C) of the APRA Act once the instrument has determined particular documents or parts are non-confidential. The instrument’s Note explicitly states that "the effect of this instrument is that the non-confidential information may be published under subsection 56(5C) of the Act." The statutory disclosure power specified by Parliament will therefore be the legal basis for any publication. The instrument does not indicate internal APRA processes for deciding to publish, nor does it set limits on form or frequency of publication.

• The instrument’s revocation of the previous determination (No. 11 of 2015) effectively changes APRA’s internal authorisation for which data may be published. Enforcement of any misuse of published data would be subject to general legal frameworks (contract, tort, or statutory regimes) and policy constraints outside this instrument.

Practical enforcement implications and compliance risks:

• Reporting entities face the risk that data they submit and which falls within the Schedule may be made public by APRA if APRA chooses to do so under s 56(5C). That risk is not framed as a penalty but as a change in confidentiality: after the 14 day window, the reporting documents or parts listed are not confidential for APRA purposes. Entities that consider some items to be commercially sensitive or confidential should be aware that the instrument creates a statutory pathway for APRA to publish them.

• If a reporting entity were to seek redaction or to argue confidentiality for a listed item, the instrument does not set out an internal procedure for challenging or excluding particular items from its scope. Any such procedure would have to be found in the APRA Act, the Financial Sector (Collection of Data) Act, or the reporting standards themselves. The instrument does not prescribe a right of review in its text.

• The instrument does not provide enforcement mechanisms against third parties who use published data in particular ways. Any legal remedy for misuse, defamation, or breach of other statutory duties would have to rely on the general law.

In short, this determination changes the legal classification of certain data as non-confidential after a timing trigger, thereby enabling publication under the APRA Act. It does not itself create penalties, nor does it alter the underlying statutory enforcement mechanisms available for data collection or other breaches.

This determination expressly references a small set of statutory instruments and provisions. The interaction is mechanical: the instrument operates within the architecture of the APRA Act and the data collection regime, and it is bounded by definitions in the Financial Sector (Collection of Data) Act and procedural references in Reporting Standard GRS 001.

Key statutory interactions referenced in the text:

• Australian Prudential Regulation Authority Act 1998. The determination is made under section 57 of the APRA Act and uses paragraph 57(2)(b) as the operative subsection to declare documents non-confidential. The Note refers to subsection 56(5C) of the APRA Act as the publishing gateway for non-confidential information. Thus the instrument modifies confidentiality status under the APRA Act and interacts directly with the APRA Act’s publication and confidentiality framework.

• Acts Interpretation Act 1901. The instrument cites subsection 33(3) of this Act in the revocation recital. That provision typically relates to power to make instruments and the effect of revocation by a delegate. The instrument therefore uses the statutory framework for making and revoking delegated instruments.

• Financial Sector (Collection of Data) Act 2001. The instrument defines reporting document by reference to section 13 of the Financial Sector (Collection of Data) Act. That Act is the statutory source of APRA’s data-collection powers and the definition of what counts as a reporting document. The determination does not change the definition but ties its scope to that statutory meaning.

• Reporting Standard GRS 001 Reporting Requirements. The 14 day timing rule is measured from the date the general insurer or Level 2 parent entity "was required to provide" information under paragraph 5 (general insurers) or paragraph 7 (Level 2). That means the timing trigger is directly dependent on the GRS 001 Reporting Requirements instrument. Any change to the dates or timing rules in GRS 001 would change when the confidentiality removal takes effect.

• The Schedule cross-references numerous Reporting Standards (GRS 110.1, GRS 114.0, GRS 115.0, GRS 310.0, and many more). The instrument does not amend those standards; it overlays a confidentiality determination on top of the data reporting architecture. Entities must therefore reconcile the content and timing of their returns under those standards with the coverage in the Schedule.

What the instrument does not reference or change:

• The instrument does not reference the Freedom of Information Act or bureaucratic information-access regimes. The determination concerns APRA’s confidentiality regime under the APRA Act and data-collection definitions. Any interaction with FOI, privacy law, or other disclosure regimes is not addressed in the instrument’s text.

• The instrument does not amend reporting standard obligations or create exemptions from the Financial Sector (Collection of Data) Act. Duties to submit remain as before.

Potential cross-checks and operational interactions:

• Where the Schedule lists "excluding" clauses or particular data items that remain outside the non-confidential scope, reporting entities must track both the reporting standard content and the determination’s exclusions. That means reconciling GRF form fields with the Schedule to determine which items remain confidential and which do not.

• Any subsequent APRA publications using s 56(5C) would need to be consistent with this determination, the APRA Act and the Financial Sector (Collection of Data) Act. The determination is therefore a pre-condition for lawful APRA publication of those items.

• Revocation of the 2015 determination by this instrument may interact with transitional arrangements or historical practices. The instrument lists superseded reporting standards back to 2002; entities working with historical data need to consider the instrument’s vintage and the commencement date of any publication activities.

In summary, the instrument is an internal statutory instrument that sits on top of APRA’s data-collection regime. It interacts directly with the APRA Act’s confidentiality and publication provisions, the Financial Sector (Collection of Data) Act’s definition of reporting documents, and the timing rules in Reporting Standard GRS 001. It does not alter reporting duties or create cross-cutting exemptions from other disclosure regimes.

The instrument contains a built-in amendment event: it revokes Australian Prudential Regulation Authority (confidentiality) determination No. 11 of 2015. The text explicitly records that action in recital (a). This is the only express revocation or amendment recorded in the instrument as reproduced.

Chronology and immediate changes recorded in the instrument:

• Date of instrument and signature: The determination is dated 18 January 2022 and signed by Alison Bliss, General Manager Data Analytics & Insights. The instrument states it "commences upon registration on the Federal Register of Legislation." That gives a clear effective moment tied to registration.

• Revocation: By recital (a) the delegate revokes determination No. 11 of 2015. The instrument therefore replaces the earlier determination’s confidentiality settings for the items at issue. The text does not reproduce the prior instrument’s text so readers must compare with the revoked instrument externally to identify precise differences. The revocation is absolute in the text provided; there is no savings clause or transitional carve-out in the present instrument itself.

• Additions and scope: The Schedule is extensive and lists current reporting standards (various GRF forms), Level 2 group forms (with _G suffixes), transitional forms and a broad set of superseded forms and parts across many GRS vintages (from 2002 through 2013 and a variety of years in between). The instrument therefore both updates and consolidates the set of reporting instruments for which APRA determines particular data items are non-confidential.

What the instrument does not do in the way of amendment history:

• The instrument does not state that it amends any reporting standards or the Financial Sector (Collection of Data) Act. It also does not attach a schedule of prior amendments or a legislative history. The only explicit historical action is the revocation of the 2015 determination.

• The instrument does not provide any transitional details for submissions made prior to the commencement date; for example it does not say whether data already supplied before the instrument’s commencement are treated retroactively as non-confidential. The Schedule includes historical/superseded reporting standards, but the instrument leaves interpretation of retroactivity to the reading of the determination and the relevant Acts. The absence of a retroactivity clause means readers should check APRA practice or seek clarification if they are concerned about pre-commencement submissions.

Practical consequence from an amendment perspective:

• Practitioners and compliance teams should note that the instrument replaced the 2015 confidentiality determination and broadened or clarified the set of forms and parts that APRA treats as non-confidential. The detailed Schedule is the operative list; clients should map their own reporting templates and historical submissions to those GRF form numbers to determine whether past or future submissions are captured.

• For audit trails and governance, entities should retain records of when specific submissions were "required to be provided" under GRS 001, since the 14 day delay measured from that date is the trigger for the confidentiality change and could be relevant if APRA publishes older returns.

The instrument text does not reference any judicial decisions, litigation, or disputes. It names no cases and records no judicial review outcomes. The instrument is an administrative determination under the APRA Act and does not, in its text, indicate any challenge, appeal, or litigation connected to this confidentiality decision.

What we can say, solely on the basis of the instrument text:

• No litigation is recorded in the instrument itself. There are no references to court proceedings, tribunal decisions, or settled litigation concerning the determination or the particular reporting forms listed.

• The instrument does not include an express right of review, appeal, or internal reconsideration procedure in its text. Any procedural review or merits review rights would therefore be found in the APRA Act or in statutes governing administrative decisions more generally. The instrument itself is silent on dispute resolution mechanisms for parties who disagree with the determination’s application to particular data items.

Practical implications for prospective litigation or review (grounded in the instrument):

• If a reporting entity or third party wished to challenge the determination, the proper legal grounds and procedure would need to be identified in the APRA Act or in administrative law channels. The instrument does not set out those avenues. Practitioners should therefore look to the APRA Act’s review provisions and to the Administrative Decisions (Judicial Review) Act 1977 for judicial review possibilities, recognizing this instrument is an exercise of statutory power under s 57.

• Because the instrument applies to specified reporting documents after a 14 day delay, disputes over whether particular data items are included in the Schedule (or whether the 14 day trigger has been satisfied) may give rise to administrative disputes. The instrument contains specific phrasing (for example exclusions such as "excluding 'Adjustments and exclusions to prudential requirements for the OCL Insurance Risk Charge'") that could be points of contention if parties interpret form fields differently. Any litigation would have to engage the instrument text and the referenced reporting standards to resolve scope issues.

As the instrument records no litigation history, and names no cases, readers should treat litigation history as absent in the instrument. Any subsequent litigation would be external to the instrument and would need to be located in court or tribunal records.

This determination contains several practical traps or detailed points that are easily missed if one reads only the headline claim that "these reports are non-confidential". The Schedule is granular and conditional. Key gotchas to watch for, all drawn from the instrument text:

• 14 day timing trigger. The determination applies only after "a period of at least 14 days has elapsed from the date the general insurer was required to provide the information required under the reporting standards in accordance with paragraph 5 of Reporting Standard GRS 001 Reporting Requirements" (and paragraph 7 for Level 2 parent entities). If an insurer miscalculates the "required to provide" date or does not retain evidence of that date, it may misjudge when confidentiality protections lapse.

• Limited to specified forms and parts. The Schedule lists many GRF forms and often specifies only parts or sections. If a reporting entity assumes the whole form is non-confidential but the Schedule only covers certain sections, the entity will be mistaken. Several entries explicitly include or exclude particular data items. For example, GRF 115.0: Outstanding Claims Liabilities - Insurance Risk Charge is covered "All data items, excluding 'Adjustments and exclusions to prudential requirements for the OCL Insurance Risk Charge'". Failure to map internal fields precisely to the GRF parts risks misunderstanding.

• Historical and superseded standards included. The Schedule covers reporting standards and forms that "ceased to have effect" for general insurers and many vintage GRS instruments dating back to 2002. That raises two practical issues: first, mapping historical submissions to the Schedule may be non-trivial; second, the instrument does not specify whether it intends retrospective application to historical reports supplied to APRA. The absence of a retroactivity clause means the legal position for pre-commencement data could be ambiguous in operational terms.

• Level 2 vs general insurer distinction. The instrument separates quarterly/annual returns for general insurers from semi-annual/annual returns for Level 2 parent entities. Entities that operate in both capacities must treat each role differently and apply the correct timing provision (paragraph 5 vs paragraph 7 of GRS 001).

• Exclusions for adjustments and approvals. Several Schedule items are qualified by phrases like "Adjustments to ... as approved by APRA - Total amount". The instrument sometimes designates those adjustments as included in non-confidential items and sometimes excludes them. Practitioners should not assume that every APRA-approved adjustment is non-confidential.

• The instrument makes information "not confidential" only for APRA purposes. The instrument determines that the reporting documents do not contain confidential information under the APRA Act and therefore may be published under subsection 56(5C). It does not change contractual confidentiality obligations between the insurer and third parties, nor does it alter other statutory confidentiality regimes. Reporting entities should not assume that because APRA may publish an item, all third-party contractual confidentiality obligations evaporate. The instrument is specific to APRA’s statutory powers.

• No guarantee of publication scope or format. The instrument permits publication under s 56(5C) but provides no detail on what APRA may publish, in what aggregate form, or with what frequency. Entities should be prepared for publication of aggregated or individual-level items, depending on APRA’s discretion.

• Potential misalignment between reporting standard change and Schedule coverage. The Schedule references specific reporting standard numbers and form identifiers. If APRA or Treasury amends a GRS instrument or renames form identifiers in the future, the Schedule’s references could become misaligned. Until clarified, entities should assume the Schedule applies to the form numbers and parts as listed in the instrument date.

• Revocation of 2015 determination. The earlier determination No. 11 of 2015 is revoked. Entities that relied on the prior determination’s terms need to re-evaluate the new list and timing provisions. There is no saving clause indicating whether data treated as confidential under No. 11 of 2015 remains so for submissions made prior to this instrument’s commencement.

• Granularity of data items includes highly sensitive categories. The Schedule lists items such as "Details of Investment Assets", "Claims Development Tables", "Outstanding Claims Liabilities", "Premium Revenue by State and Territory", and "Statement of Financial Position". Those data points can be commercially sensitive. The instrument’s broad inclusion of such items means that once the 14 day window passes APRA may be able to publish granular, perhaps company-specific data, unless specifically excluded.

In short, the gotchas are all about mapping, timing, and precise content. The determination is not a blanket waiver of confidentiality for all insurer reporting; it is a measured, granular instrument dependent on form identifiers, parts, and a short timing trigger. Compliance teams should not assume blanket protection or blanket publicity; they must reconcile their specific GRF forms and timestamps with the Schedule.

Compliance with this instrument requires operational mapping, controls around dates, and internal governance to manage commercial and regulatory disclosure risk. The determination does not add reporting duties, but it does change post-submission confidentiality expectations for a discrete set of reporting items. The following steps are directly grounded in the instrument text.

1. Map all submitted GRF forms and parts to the Schedule entries

• Reconcile each GRF form you submit to APRA with the Schedule’s list. The Schedule identifies GRF form numbers and specific sections or data items. For each GRF you file, produce a crosswalk that shows whether the form or the particular data item is listed in the Schedule and whether any exclusions apply. The instrument often uses phrasing such as "All data items, excluding ...", or identifies specific sections. Accurate mapping is essential.

2. Track "required to provide" dates under GRS 001

• The instrument’s 14 day timing trigger is measured from the date the insurer "was required to provide" the information under paragraph 5 of Reporting Standard GRS 001 (or paragraph 7 for Level 2 parent entities). Maintain auditable records of the statutory due date and the date on which you were required to provide the report. Include any extension notices or approvals from APRA that alter the required-to-provide date. This record will determine when items become non-confidential under the determination.

3. Establish a post-submission disclosure checklist and governance protocol

• Once submissions are made, run a checklist to determine which items will be non-confidential after the 14 day window. Prepare internal notifications to business units (finance, actuarial, legal, commercial teams, the board) that certain data may become publishable by APRA after the specified date. If your business has commercial concerns, the notification should trigger an internal review to decide whether extra steps (for example engagement with APRA or requesting confidentiality protections under other statutory regimes, if available) are warranted.

4. Review contract and third-party confidentiality clauses

• The instrument changes APRA’s ability to publish certain data; it does not explicitly change contractual confidentiality obligations. Contracts with reinsurers, investment managers or other counterparties may need review if the data APRA could publish overlaps with contractual confidentiality. Document which contract clauses might be implicated and develop a disclosure risk assessment.

5. Prepare redaction or commentary plans (if needed)

• The instrument does not provide a mechanism for insurers to redact parts of returns prior to submission. If a reporting entity considers some items particularly sensitive, explore operational alternatives before submission (for example, check whether the reporting standards themselves permit aggregation or alternative formatting). Keep a contemporaneous record of any consultation with APRA about particular data fields.

6. Maintain an audit trail for historical submissions and legacy forms

• The Schedule includes a substantial list of superseded reporting standards and transitional forms. If you have historical reports that map to those GRF forms, maintain an audit trail of their submission dates and content. That will help determine whether APRA’s removal of confidentiality could apply to older datasets.

7. Coordinate with APRA liaison contacts

• If there is any uncertainty about whether a particular GRF field is captured by the Schedule or about the applicable required-to-provide date, raise the issue with APRA’s data or supervision contact. The instrument delegates the determination to APRA personnel; clarifications about scope or timing are likely to come from APRA rather than from this instrument.

8. Update public disclosures and investor communications policies

• Given the potential for APRA to publish prudential items such as capital charges, claims development, premium by state, asset risk charges, and so on, align investor relations and public disclosure policies with the new timetable. If APRA publishes company-specific figures, ensure communications teams are prepared to respond and to correct any misinterpretations.

9. Monitor APRA publications and the Federal Register of Legislation

• The instrument takes effect on registration. Regularly monitor the Federal Register of Legislation for the registration date and APRA’s public releases under subsection 56(5C). Publication patterns will reveal APRA’s practical approach to the permissive publication power enabled by this determination.

10. Consider governance documentation for board and audit committees

• The shift in confidentiality status is a governance matter for boards and audit committees. Prepare briefing materials that explain which reporting items will become non-confidential and the timetable from submission date to potential publication. Include the crosswalk, key dates, and a risk matrix for commercial sensitivity.

These steps flow from the instrument’s mechanics: a specific list of GRF forms and parts; the 14 day measurement from the GRS 001 "required to provide" date; and APRA’s discretion under subsection 56(5C) to publish non-confidential information once the instrument has declared it non-confidential. Following these compliance steps reduces the risk of surprise publication and enables timely engagement with APRA if necessary.