Financial Sector (Collection of Data) (reporting standard) determination No. 88 of 2023

The Standard is built around a small number of recurring conceptual building blocks: country-of-risk reporting, derived items, alignment to AASB/IFRS taxonomy elements, and presentation conventions.

Country-of-risk reporting

• The Standard requires reporting by country/region “according to where the items of income/expense are on risk, assets are invested, and liabilities are located.” The country list is explicit and limited to eight named jurisdictions/regions plus an “Other” bucket, with a ninth column containing the total (Table 1).
• This is a destination-based allocation rule rather than an ownership or legal seat rule; the relevant allocation is by where the risks, assets and liabilities sit.

Derived items and arithmetic relationships

• Several items are expressly derived and the derivations are specified in text. Examples: Item 1 is “calculated as the sum of items 1.1 and 1.2”; Item 3 is “calculated as the sum of item 1 and item 2”; Item 14 is the sum of items 9 through 13. These defined arithmetic relationships require the reporting entity to maintain internal mappings that produce consistent cell values.
• Where an item is characterised as “derived” the Standard expects consistency with the referenced accounting standard (for example, “Report this item in accordance with AASB 101.82 (a) (ii) Disclosure, AASB 17.80(a), and AASB 17.83”).

Alignment to AASB and IFRS taxonomy references

• Each accounting item reported “aligns with” specific items in GRS 310.0 or GRS 300.0 and carries cross-references to AASB standards. The Standard instructs that IFRS taxonomy elements used must include references to AASB Standards, and that reference types may be “disclosure,” “example” or “common practice.”
• The Standard repeatedly instructs that presentation and measurement should follow AASB 17 (insurance contracts), AASB 101 (presentation of financial statements), AASB 121 (foreign currency translation) and AASB 132 (financial instruments), where the individual item descriptions cite the relevant paragraphs.

Presentation conventions and units

• Values must be in whole AUD, with no decimal places. Losses and expenses must be reported as negative values. Foreign currency amounts must be converted under AASB 121.
• Totals must reconcile with other Reporting Standards: e.g. totals in Column 9 “should align with the corresponding totals in Reporting Standard GRS 310.0 and Reporting Standard GRS 300.0.”

Insurance-specific line items

• The table differentiates insurance contract assets for incurred claims and for remaining coverage (Items 9.1 and 9.2), and the same split for reinsurance contract assets and liabilities. The Standard also separates allocation of reinsurance premiums (Item 4) from amounts recoverable from reinsurers for incurred claims (Item 5), consistent with AASB 17 references.

Scope and reporting basis

• The Standard applies only “where the reporting insurer has business operations outside of Australia (i.e. where they have items of income, expense, assets, liabilities or capital outside of Australia).” Reporting is required “for each reporting period on a Level 1 (licensed insurer) basis.” The definitions of “direct business” and “inwards reinsurance” are provided for mapping purposes.

Taxonomy element reference types

• The IFRS taxonomy guidance in the text prescribes three reference types for taxonomy elements: disclosure, example, and common practice. That constrains how preparers should tag elements in any machine-readable or digital filing using an IFRS taxonomy.

Overall, the main concepts combine country segmentation with tightly-specified accounting line mappings and presentation conventions that aim to produce reconciled, AASB-consistent, country-level distributions of insurance revenues, expenses, assets and liabilities.

Directly affected

• The Standard applies to “the reporting insurer” that has business operations outside Australia, meaning any licensed insurer that has items of income, expense, assets, liabilities or capital outside Australia. The text explicitly instructs: “This Reporting Standard only needs to be completed where the reporting insurer has business operations outside of Australia.”
• Reporting is required on a Level 1 (licensed insurer) basis. That places the compliance and reporting obligation at the top legal entity level that holds the licence, rather than at the level of subsidiaries or branches, unless those feed into the licensed insurer’s Level 1 reporting consolidated basis.

Functions inside affected organisations

• Finance and accounting teams must extract and map statutory and management accounting balances to the Standard’s items (Items 1-21), apply foreign exchange conversion in accordance with AASB 121, and ensure presentation (for example, sign conventions for losses and expenses, and reporting in whole AUD with no decimals).
• Financial reporting and regulatory reporting teams must ensure alignment between this country-level statement and the insurer’s other regulatory reports, specifically GRS 310.0 and GRS 300.0, because the Standard requires totals to reconcile to those other Reporting Standards.
• Actuarial teams will be involved where items such as “insurance contract assets” and “insurance contract liabilities” require valuation consistent with AASB 17; the Standard references AASB 17 provisions for many items.

External stakeholders and users

• Auditors and external assurance providers who examine financial statements or regulatory reports will need to validate the mapping, conversion policies and reconciliations required by the Standard. The Standard’s requirement for alignment with AASB 17, AASB 101, AASB 121 and AASB 132 increases the technical work auditors must perform.
• Regulators or supervisors who rely on reporting templates (not named in the Standard itself) will be users of the disclosed country-by-country data. The Standard’s cross-references and alignment requirements indicate the intended interoperability of data with other reporting instruments.

Those not directly affected

• The Standard expressly excludes reporting where the reporting insurer has no operations outside Australia. It is therefore not applicable to purely domestic insurers. It does not create obligations for non-insurance entities, reinsurers that are not on Level 1 reporting basis, or intermediaries, unless they are the licensed insurer required to report.

Allocative consequences and operational burdens

• The principal economic cost of this Standard falls on insurers with cross-border operations: they must capture country-level allocations for multiple AASB-mandated accounting items, maintain conversion and mapping rules, and reconcile totals to other reporting standards. That creates ongoing recurring compliance costs rather than a one-off exercise, because items such as insurance contract liabilities and amounts recoverable from reinsurers change each reporting period.

Who pays and who decides

• The reporting insurer pays for collection, conversion, allocation and assurance costs. The reporting insurer also decides the internal accounting policies and allocation methodologies, subject to the Standard’s direction to follow AASB 17, AASB 121, AASB 101 and AASB 132 references.

Duties imposed by the text

• Complete Table 1: Statement of Risk by Country (columns 1-9) and populate the specified items (Items 1-21) for each reporting period where the reporting insurer operates outside Australia. The Standard states the column and item structure and directs reporting of specific sub-items (for example Item 1.1 and Item 1.2).
• Ensure arithmetic derivations where the text specifies “derived items.” For example, Item 1 is “calculated as the sum of items 1.1 and 1.2”; Item 6 is “calculated as the sum of items 4 and 5”; Item 14 is “calculated as the sum of items 9, 10, 11, 12 and 13.”
• Report values in whole AUD with no decimal place and report losses and expenses as negative values. The Standard is explicit: “Report values in whole Australian dollars (AUD) with no decimal place” and “Report losses and expenses as negative values.”
• Convert foreign currency amounts to AUD “in accordance with AASB 121 The Effects of Changes in Foreign Exchange Rates.”
• Report on a Level 1 (licensed insurer) basis for each reporting period, where the reporting insurer has business operations outside Australia.
• Present certain items separately, where the Standard requests separation. For example, Item 4 (allocation of reinsurance premiums) should be presented separately from amounts recoverable from reinsurers for incurred claims reported at Item 5.
• Align reported totals with corresponding totals in GRS 310.0 and GRS 300.0. Column 9 “should align with the corresponding totals in Reporting Standard GRS 310.0 … and Reporting Standard GRS 300.0.”

Explicit cross-reference duties

• Prepare and present individual items “in accordance with” the cited AASB paragraphs. The Standard repeatedly instructs preparers to report items in accordance with paragraphs from AASB 17, AASB 101 and AASB 132; for instance, Item 9: “Report this item in accordance with AASB 17 Appendix A, AASB 17.78 (a), AASB 17.100 Disclosure and AASB 101.54 (da).”

Rights and leeway given

• The Standard provides limited flexibility on taxonomy reference types for tagging: an IFRS taxonomy element may carry a reference type of “disclosure,” “example” or “common practice.” That allows preparers some latitude for labelling taxonomy elements where the standard supports more than one reference type.
• Preparers retain choice over allocation methodologies when the Standard refers to where “items of income/expense are on risk, assets are invested, and liabilities are located.” The Standard defines the basis (where on risk, where assets invested, where liabilities located) but does not prescribe the micro-level allocation algorithm for complex cross-border policies; the reporting insurer must apply allocation consistent with the AASB references.

What the duties mean operationally

• Internal controls must capture the country of risk, currency conversion, sign convention, and mapping to each item. For example, actuarial valuations of insurance contract liabilities will need to produce country-level splits for the “liabilities for incurred claims” and “liabilities for remaining coverage” line items.
• Wherever the Standard instructs “report this item in accordance with …” the reporting insurer must check that its AASB-conforming accounting policies are applied consistently in producing the country-level disclosure.

What the Standard does not grant

• The text does not grant enforcement or penalty powers. It does not specify submission formats, filing deadlines, or the authority to which the completed table is to be delivered. Those operational elements, if required, must be located elsewhere.

The supplied text contains no express penalties, sanctioning regime, or named enforcement authority. There are no provisions in the excerpt that specify fines, criminal liability, civil penalties, administrative sanctions, or disclosure filing deadlines. The absence of an enforcement clause in the Standard itself means that the Standard, as drafted and supplied, is a set of reporting instructions and cross-references to AASB requirements rather than a self-contained statutory enforcement instrument.

Practical implications of that absence

• Compliance will depend on how the Standard is incorporated into the broader regulatory and licensing framework that governs the reporting insurer. The Standard instructs the reporting insurer what to present and how to measure it, but it does not state the consequences of failing to follow those instructions. This creates implementation uncertainty for preparers as to the effective enforceability of the Standard unless an external instrument links it to regulatory obligations.
• Enforcement, where it exists, is likely to arise through supervisory powers, licence conditions, or other legislative or regulatory instruments outside the Standard. Because the Standard requires alignment to other reporting standards (GRS 300.0 and 310.0) and to AASB accounting standards, practical enforcement could occur during supervisory reviews, financial statement audits or licensing compliance assessments. However, those enforcement mechanisms and their sanctioning powers are not contained in this text and therefore cannot be described here.

Compliance risk and assurance

• From an operational standpoint, the absence of penalties in the instrument increases the importance of internal governance, audit and assurance. External auditors tasked with attesting to financial statements or regulatory returns will likely treat this Standard’s requirements as part of the reporting framework they test, and audit findings could be the channel through which non‑compliance is escalated.
• The Standard’s requirement that Column 9 totals “should align” with GRS 310.0 and GRS 300.0 creates a reconciliation control point. Discrepancies at that junction may prompt queries from stakeholders or supervisors that can trigger remedial action even without a formal penalty specified in the Standard.

Risk of inconsistent application and litigation exposure

• Because the Standard defers to AASB accounting standards for measurement and conversion rules, disputes about recognition and measurement (for example, classification of a contract as insurance contract vs investment contract) would be resolved by applying the referenced AASB paragraphs. The Standard itself does not provide adjudicative mechanisms for disputes, so litigation or formal dispute resolution, if any occurs, would have to rely on other legal instruments, contractual arrangements, or administrative processes that fall outside the text provided.

In sum, the Standard imposes precise reporting duties but does not itself define an enforcement architecture. That makes the interface between this Standard and the insurer’s licensing, supervisory, and audit regimes the decisive factor for practical compliance enforcement.

The Standard explicitly references and is designed to be used in conjunction with other reporting standards and accounting laws. Its interactions are principally with AASB accounting standards and the other GRS reporting standards named in the text. The Standard sets presentation and measurement instructions that are conditional on or derived from those other instruments.

Explicit cross-references

• AASB 17 (Insurance Contracts): multiple items require reporting “in accordance with AASB 17” or specific AASB 17 paragraphs (for example AASB 17.78, 17.80, 17.83, 17.84, 17.86, AASB 17 Appendix A). Items describing insurance contract assets, liabilities, and reinsurance contract assets and liabilities rely on AASB 17 for recognition, measurement and disclosure rules.
• AASB 101 (Presentation of Financial Statements): the Standard cites AASB 101 disclosure paragraphs (for example AASB 101.82, 101.54 variants, 101.55, 101.54 (ma), 101.54 (m), 101.54 (da)). These references instruct preparers how to present the items and how to align the disclosure with AASB presentation requirements.
• AASB 121 (Effects of Changes in Foreign Exchange Rates): foreign currency conversion is mandated to follow AASB 121.
• AASB 132 (Financial Instruments): reporting of “other financial assets” and “other financial liabilities” is directed to follow AASB 132.11 and AASB 101.54 (d)/(m) disclosures.

Interaction with GRS 300.0 and GRS 310.0

• The Standard repeatedly states that certain items “align with” specific items in GRS 310.0 (Statement of Profit and Loss and Other Comprehensive Income) and GRS 300.0 (Statement of Financial Position). Column 9 totals are required to align with corresponding totals in both GRS 310.0 and GRS 300.0.
• That produces a reconciliation obligation: the country-level table is not an isolated disclosure but is intended to be materially consistent with the insurer’s primary profit and loss and balance sheet reporting under those other GRS instruments.

IFRS taxonomy

• The text outlines how IFRS taxonomy element references should be used, and requires that taxonomy elements carry at least one cross-reference to an AASB Standard (incorporating IFRS 17). It sets three permitted reference types for taxonomy elements: disclosure, example, common practice. Preparers producing tagged electronic reports must ensure that taxonomy usage aligns with these instructions.

Scope interactions

• The Standard applies only where the reporting insurer has operations outside Australia. This limits the Standard’s applicability and interacts with licensing and cross-border legal responsibilities, because an entity with purely domestic operations falls outside the Standard’s reporting requirements.
• The Standard establishes a Level 1 reporting basis. That interacts with consolidation and reporting rules embedded in other regulatory instruments; the Level 1 basis focuses the obligation on the licensed entity, and so the entity must determine whether subsidiary or branch-level items are to be consolidated for reporting under this Standard.

What the Standard does not do

• The Standard does not set criminal, civil or administrative penalties and does not itself name an enforcing regulator. Those enforcement and sanctioning details must be found in other legislation or administrative instruments. Consequently, the Standard is part of a broader regulatory and accounting framework but does not, in itself, create or describe the legal enforcement machinery that will ensure compliance.

Practical consequence of the interactions

• Preparers must apply the accounting rules in the cited AASB standards when producing the country-level disclosures. This means that differences in recognition or measurement under AASB rules will feed into the country-by-country numbers, and any change in those AASB rules or interpretations will change how the Standard’s tables are populated.
• The required reconciliation to GRS 300.0 and GRS 310.0 ties this table to an insurer’s main regulatory financial statements, so the interaction is operational as well as conceptual: data extraction, mapping, currency conversion and reconciliations must all be consistent across reporting instruments.

The supplied text contains no amendment history section, no list of prior versions, no effective date, and no trace in the text of prior amendments or superseded material. The Standard as provided does not include an enactment clause, commencement date, or schedule of previous amendments. It simply sets out the reporting instructions and cross-references.

Implications of an absent amendment history

• Where a standard contains no amendment history in its body, preparers and auditors must ascertain whether this copy is the current operative version through other means, for example by consulting the issuing authority’s official register, the licensing or supervisory instrument that adopted it, or the published consolidation of standards. The absence of an embedded amendment history increases the operational burden of confirming whether subsequent changes or corrigenda exist.
• The lack of an effective date in the text as supplied creates ambiguity about when the requirements first apply and whether comparative period restatements are required. Preparers need to locate the authoritative instrument or adoption notice to determine the reporting period from which the Standard applies.

Practical steps prompted by no amendment history

• Insurers should maintain an internal repository of authoritative regulatory instruments and track issuance and amendment notices from the standard-setter or regulator to ensure use of the current text. Because this extract includes many cross-references to AASB paragraphs, any amendments to AASB 17, AASB 121, AASB 101 or AASB 132 could also necessitate changes in interpretation of this Standard.
• Where the Standard is to be relied on for filing or audit purposes, entities should obtain and archive the official promulgation record (for example the adoption instrument, commencement notice or circular) that confirms the version in force.

Risk assessment

• The absence of an amendment history in the supplied copy raises practical risks: reconciliations and audit opinions could be challenged if a preparer used a non-current or superseded version. That risk is mitigated by ensuring the reporting insurer’s compliance function verifies the authoritative source and documents the version and date relied upon for each reporting period.

Because the text supplied omits amendment history, users should treat the Standard as a technical specification that must be cross-checked against the issuing authority’s official repository prior to relying on it for compliance and public disclosures.

The document supplied contains no litigation history, no references to judicial decisions, and no list of disputes or precedent authorities that interpret the Standard. There are no case names, no appeals, no tribunal findings, and no guidance from courts or administrative law bodies provided in the text.

Consequences of the lack of litigation history in the Standard

• The absence of litigation history in the Standard itself means that any legal interpretation questions that arise,such as disputes about the correct allocation of income/expense to a country, the proper classification of a contract under AASB 17, or whether a particular item should be included in an “Other” country column,will need to be resolved by applying the relevant accounting standards, contractual terms, licence conditions, or, if litigated, by reference to general principles of administrative law and accounting law outside this text.
• Because the Standard relies heavily on AASB 17, AASB 121, AASB 101 and AASB 132, precedents that interpret those accounting standards (if any exist) will be directly relevant. However, no such precedents are referenced in this Standard.

What organisations and advisers should do

• Practitioners should document their interpretation of the Standard and the AASB rules they invoked to produce the country-level numbers, to create an auditable trail in case the reporting is later challenged by auditors or supervisors. That documentation should include allocation methodologies, currency conversion policies under AASB 121, actuarial assumptions for insurance contract liabilities under AASB 17, and reconciliations to GRS 300.0/310.0.
• In the event of a dispute or enforcement action, the absence of litigation history in the Standard emphasises the need to rely on the broader corpus of accounting standards, regulatory law and administrative precedent. Where interpretive questions are material, entities may wish to seek advance binding advice or rulings from the relevant regulator or to obtain legal opinions, recognising that such remedies are outside this Standard.

Risk profile

• The lack of litigation history does not reduce legal risk: disputes may still arise, but there is no published body of judicial interpretation embedded in the Standard to help resolve them. Entities with substantial cross-border business should therefore maintain conservative, well-documented positions and expect that accounting standard interpretation (AASB 17, AASB 121) will be determinative in any legal contest about the proper content of these country-by-country disclosures.

1. Whole AUD, no decimals, negative sign convention

• The Standard mandates reporting in whole Australian dollars with no decimal place, and explicitly states “Report losses and expenses as negative values.” Failure to adhere to the whole-AUD rule can produce minor numeric mismatches with other reports, and inconsistent sign convention for losses/expenses will produce materially misleading totals. This is a formatting and control risk that is easy to miss in automated extracts.

2. Foreign currency conversion method is specified

• The Standard requires conversion “in accordance with AASB 121.” That is not simply a rounding rule, it imposes a methodology for translating transactions, assets and liabilities. Applying a different conversion policy or exchange rate (for example, a daily spot vs period-end rate applied inconsistently across items) will break reconciliations and may contravene AASB 121-derived recognition rules.

3. Level 1 basis, and scope trigger

• The Standard applies only where the reporting insurer “has business operations outside of Australia.” That scope is fact-specific: entities must establish whether their “items of income/expense are on risk, assets are invested, and liabilities are located” outside Australia. Misjudging that test can either expose an insurer to a later finding of non-compliance or impose unnecessary reporting costs.

4. Derived items require internal arithmetic consistency

• Several items are “derived” sums. For example, Item 7 is the sum of items 3 and 6. If preparers produce these items independently (for example, different teams supplying P&L and balance sheet splits) without arithmetic checks, reconciling failures will occur. Establish controls to compute derived items programmatically from sub-items rather than manual entry.

5. Reinsurance presentation nuance

• The Standard requests that the allocation of reinsurance premiums (Item 4) be presented separately from amounts recoverable from reinsurers for incurred claims (Item 5). Preparers who simply net reinsurance items may fail to present the required split. Treat Item 4 and Item 5 as discrete mapping fields.

6. Alignment requirement with GRS 300.0 and GRS 310.0

• Column 9 totals “should align” with corresponding totals in other GRS reports. This is a reconciliation control that may fail if differing recognition or classification rules apply in the other reports. The gotcha is that the Standard requires alignment but does not give reconciliation rules; preparers must design reconciliations that translate ledger or actuarial outputs into both the primary statements and the country table in a consistent manner.

7. Separate asset/liability splits for incurred claims vs remaining coverage

• Items such as 9.1/9.2 and 15.1/15.2 require splitting contract assets and liabilities between incurred claims and remaining coverage. Actuarial systems and valuation models must be able to produce these splits by country. If models are not designed for country-level outputs, significant system work may be required.

8. Taxonomy tagging and reference types

• If the reporting process includes IFRS taxonomy tagging, ensure each element carries an appropriate AASB cross-reference of the correct type (disclosure, example, or common practice). Mis-tagging increases the risk of automated validation errors when submitting machine-readable filings.

9. Negative values for expenses and losses

• Some systems export expenses as positive amounts; the Standard requires them to be negative. Automated pipelines must invert signs as required. Failing to do so will distort totals and produce obviously incorrect aggregates.

10. No filing mechanics in the text

• The Standard does not indicate where, when or to whom the completed table must be delivered, nor the sanctions for failing to submit. Do not assume filing mechanics; verify with the entity’s regulator or internal compliance team. This procedural gap is a practical gotcha for governance owners who might assume the Standard itself contains submission instructions.

11. “Other” bucket aggregation risks

• Column 8 is “all other countries.” Preparers must avoid accidental double counting between the named regional buckets (for example South East Asia excluding Japan; Continental Europe) and this residual bucket. Define mapping rules to ensure each exposure is assigned to exactly one column.

12. Alignment to AASB paragraphs creates dependency risk

• The Standard’s heavy reliance on specific AASB paragraphs means that a change in those AASB paragraphs or their interpretation will change the meaning of items in this table. Maintain version control of the AASB texts used for each reporting period.

13. Derived totals may be net income or net expense

• Item 6 notes that net expense from reinsurance contracts held “can be a net income or net expense.” Systems and validation rules must allow for either sign and not hard-code expectations.

Addressing these gotchas requires cross-functional planning among accounting, actuarial, tax, IT and compliance teams, plus robust reconciliation and documentation.

1. Confirm applicability and reporting period

• First, confirm whether the reporting insurer has operations outside Australia (i.e. items of income/expense on risk, assets invested or liabilities located outside Australia). If yes, the Standard must be completed for each reporting period on a Level 1 licence basis. Document the conclusion, the materiality thresholds used, and the effective reporting period.

2. Establish a single source of truth and mapping table

• Build an authoritative mapping between the insurer’s chart of accounts, actuarial outputs and the Standard’s Items 1-21. Use a consolidated data dictionary that maps ledger accounts and actuarial valuation outputs to each item and to the country/region columns. Where the Standard prescribes sub-items (e.g. Item 1.1, Item 1.2), map those granularly to source systems.

3. Implement AASB-consistent accounting policies

• Ensure the entity’s recognition and measurement policies conform to the AASB paragraphs cited in the Standard (AASB 17 for insurance contracts, AASB 121 for foreign currency translation, AASB 101 for presentation, and AASB 132 for financial instruments). Maintain policy documentation that shows how AASB provisions were applied to derive each table item.

4. Foreign currency conversion controls

• Apply AASB 121 rules consistently across all items that require currency conversion. Document the exchange rates used and the points in time (transaction date, period-end) applied. Retain supporting evidence for the exchange rates and the conversion method.

5. Actuarial model outputs by country

• Ensure actuarial valuation models produce country-level outputs that separate “incurred claims” and “remaining coverage” as required for Items 9.1/9.2 and 15.1/15.2 (and the equivalent reinsurance contract items). If models do not natively produce country splits, implement allocation keys supported by documented rationale and controls.

6. Reinsurance items and presentation splits

• Capture the allocation of reinsurance premiums separately from amounts recoverable from reinsurers for incurred claims. Ensure reinsurance accounting feeds map to Item 4 and Item 5 respectively and that the net expense from reinsurance (Item 6) is calculated as the sum of Items 4 and 5, allowing for either sign.

7. Reconciliation to GRS 300.0/310.0

• Implement reconciliations that demonstrate Column 9 totals align with the corresponding totals in GRS 310.0 and GRS 300.0. Automate reconciliation reports where possible, and establish sign-offs for variances above an agreed threshold. Reconciliation must include mapping logic, conversions, timing differences, and adjustments.

8. Numeric presentation rules

• Enforce reporting formats: whole AUD (no decimals) and negative values for losses and expenses. Add validation checks in the reporting template to flag non-integer values and incorrect sign conventions.

9. Taxonomy tagging and references

• If producing machine-readable or tagged filings, map each IFRS taxonomy element to at least one AASB cross-reference and select the appropriate reference type (disclosure, example or common practice) as described. Maintain a mapping register of tag-to-AASB references used.

10. Controls and governance

• Implement a formal review and sign-off workflow involving finance, actuarial, compliance and the chief financial officer or equivalent. Maintain a record of reviewers and the date of sign-off. Include a technical accounting review to confirm that AASB 17 and related standards have been correctly applied in the country-level splits.

11. Audit trail and supporting documentation

• Retain working papers that support the mapping and conversions used for each country and item. These should include ledger extracts, actuarial valuation reports, reinsurance schedules, FX source data, and the reconciliation to primary statements (GRS 300.0/310.0). Prepare an exceptions log for items requiring judgement and the rationale adopted.

12. Change management and version control

• Track the version of the Standard and of the referenced AASB paragraphs used for each reporting period. Where changes occur in the AASB or in the Standard, evaluate the impact on the reporting template and update policies and models.

13. Systems and automation

• Where feasible, automate the extraction, conversion and aggregation steps. Implement unit tests for derived item calculations and reconciliation tests to other reports. Ensure sign convention and rounding/whole-AUD conversion are applied in the final reporting layer rather than at source to avoid compounding rounding errors.

14. Materiality and disclosure

• Although the Standard is prescriptive in structure, apply the insurer’s materiality framework in preparing additional narrative disclosures if required by AASB 101 or by the wider regulatory regime. Where an allocation decision is judgemental, disclose the methodology used in working papers and, if required by the broader reporting framework, in public disclosures.

15. Verify filing mechanics

• The supplied text does not state to whom or how the completed table should be submitted. Confirm with the issuer or the insurer’s compliance/regulatory team the submission channels, deadlines and format requirements (for example, whether an electronic tagged file is required).

16. Prepare for assurance

• Anticipate auditor queries about allocations, currency translation, actuarial splits and reconciliations. Pre-emptively prepare schedules and evidence that the auditor will require, including reconciliations to GRS 300.0/310.0 and a narrative of any complex allocation methodologies used.

Following these steps will reduce reconciliation failures and create an auditable trail linking the insurer’s ledgers and actuarial valuations to the country-by-country table required by the Standard.