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

The central concept is direct business, defined in the instructions as insurance contracts where the insurer has a contract directly with a policyholder that is not an insurer or reinsurer. This excludes all forms of inward reinsurance and retrocession. Only direct writers must report; specialist reinsurers writing only assumed business do not file under GRS 420.0.

Class of Business is defined by reference to APRA’s GPS 001 Definitions and further refined for the “other” catch-all category by reference to GPS 115 Capital Adequacy: Insurance Risk Charge. The valid values listed in the reporting table are: Householders, Commercial Motor, Domestic Motor, Other Direct - Category A, Travel, Fire and ISR, Marine, Aviation, Consumer Credit, Other Accident, Other Direct - Category B, Mortgage, CTP, Public and Product Liability, Professional Indemnity, Employers Liability, Cyber, Directors and Officers, and Other Direct - Category C. An insurer’s Appointed Actuary must assign the “other” business to one of the three GPS 115 risk categories (A, B or C) based on underlying risk characteristics. This creates a subjective element where two actuaries could reasonably classify the same block of business into different categories, with consequences for how APRA aggregates industry revenue and claims data.

State and Territory of Australia captures eight geographical divisions: NSW, VIC, QLD, SA, WA, TAS, ACT, and NT. The standard does not define how an insurer should attribute revenue and claims to a state when the policyholder’s address differs from the risk location, or when a single policy covers multiple states. The instruction is silent on these allocation questions, which means the reporting entity must adopt a consistent, justifiable method and apply it across all reporting periods. This lack of explicit guidance is a compliance risk.

Insurance Revenue is the amount recognised under AASB 17.83 for direct business. It aligns with the line item in the statement of profit or loss and must be measured in accordance with the IFRS 17 / AASB 17 framework, including the requirement that insurance revenue represent the consideration to which the entity expects to be entitled in exchange for services provided. The standard cross-references AASB 101.82(a)(ii) for presentation.

Incurred Claims must be consistent with the figure reported in GRS 310.0. This means the data submitted to APRA under this geographic standard must reconcile to the entity’s own total incurred claims for direct business, before any further allocation adjustments. The incurred claims are to be reported net of reinsurance? The standard says “incurred claims for direct business” without specifying net or gross. Reading the GRS 310.0 cross-reference suggests it follows the profit or loss presentation, so it would be net of reinsurance recoveries? But careful: GRS 310.0 may require separate lines. Without seeing GRS 310.0 we cannot assume. The standard does not specify net or gross, only “consistent” with GRS 310.0. This ambiguity imposes a burden on the insurer to interpret and document the basis.

Negative reporting for losses and expenses is required - the table expects losses to be reported as negative values. This is counterintuitive for some internal accounting systems that record losses as positive debits.

Distinct row constraint - the combination of class and state must be unique. If an insurer writes a single class in one state, only one row is permitted. If the insurer has multiple portfolios or underwriting years, they must be aggregated into one row.

IFRS taxonomy references are provided for each element (disclosure, example, common practice), but these appear to be informational cross-references for mapping to XBRL taxonomy rather than substantive obligations. They indicate the source of the element in the IFRS 17 taxonomy but do not alter the accounting requirements.

The direct compliance population is licensed general insurers (Level 1 entities) under the Insurance Act 1973 that write direct insurance business in Australia. This includes domestic insurers, foreign insurer branches licensed in Australia, and possibly some Lloyd’s syndicates if they are structured as licensed insurers writing direct business. The standard does not apply to life insurers, health insurers (unless they hold a general insurance licence), reinsurers writing only assumed business, or authorised non-operating holding companies.

Within a reporting insurer, the key personnel affected are the Chief Financial Officer, the Appointed Actuary, and the team responsible for regulatory returns under the GRS (General Reporting Standards) framework. The actuary is specifically required to determine the appropriate GPS 115 category for “other” direct business. This adds a layer of professional judgment that must be documented and defensible in an APRA review or audit. The CFO or equivalent must ensure the incurred claims figure reconciles to GRS 310.0, creating a cross-form consistency check that may expose errors in either return.

Externally, APRA’s analysis team is the primary consumer of the data. The breakdown by state and class allows APRA to monitor geographic concentration of premium and claims, which feeds into its assessment of systemic risk, catastrophe exposure, and industry pricing behaviour. The data could be used to inform public reports or confidential supervisory feedback. Indirectly, the Australian Bureau of Statistics or Treasury may access aggregated data for economic statistics.

Policyholders are not directly affected because the standard imposes no new policy terms, disclosure, or cancellation rights. However, if APRA uses the data to identify a market failure (e.g., under-pricing of cyclone risk in northern Queensland), it may respond with capital or policy interventions that ultimately affect premium levels and coverage availability. This speculative chain is the standard’s most significant potential economic impact.

Industry associations like the Insurance Council of Australia must help members interpret allocation methodologies, especially for multi-state policies. Smaller insurers with limited actuarial resources may find the “other” classification requirement disproportionately burdensome relative to the public benefit of the data.

Duty to report - each licensed insurer that writes direct business must complete and lodge the table of insurance revenue and incurred claims by state and territory. The standard gives the format, valid values, and accounting basis. There is no exemption for not writing certain classes or states; the insurer must report the data that exists, with zero or blank rows presumably not required unless the instruction says “report only if applicable”. The instruction says “report” without specifying if zero rows must be included. Prudentially, it is safer to include rows with zero amounts where a class is not written in a state.

Duty to ensure accuracy - the reported values must align with AASB 17, AASB 101, AASB 121, and GRS 310.0. This creates a cascading accuracy obligation. If the GRS 310.0 return contains an error, the GRS 420.0 return will also be wrong, and APRA may find both non-compliant.

Duty of consistency - the insurer must not report the same combination of class and state on more than one row. This forces aggregation of multiple portfolios, underwriting years, or product sub-groupings into one number. That aggregation may obscure underlying heterogeneity but is a condition of the return.

Duty of appropriate classification - for the “other” class of business, the Appointed Actuary must determine the GPS 115 category based on underlying risk characteristics. This is a personal duty of the actuary, not merely a corporate obligation. The actuary must document the reasoning. If the classification is later challenged, the actuary may need to defend the choice.

Rights - the standard confers no substantive rights on the reporting entity. It does not create a right to seek a waiver, extension, or variation (those are governed by APRA’s general powers under the Insurance Act 1973 s 63). The right to be informed of changes to the standard is not addressed in this instrument; revisions are published separately.

Right to self-correction - not mentioned in the standard. In practice, APRA expects errors to be notified and corrected, but this standard does not contain an amendment mechanism.

No private right of action - a policyholder or third party cannot sue an insurer for errors in GRS 420.0 data. The standard exists solely for prudential regulatory purposes.

GRS 420.0 does not itself create penalty provisions. It is a reporting standard made under the Insurance Act 1973 (likely s 13, which empowers APRA to determine reporting standards). Non-compliance with a reporting standard is not a criminal offence in the standard; rather, it exposes the insurer to regulatory action under the Insurance Act 1973 and the APRA Act 1998. Potential consequences include:

• Directions under s 62 of the Insurance Act to appoint a suitable actuary or to take remedial action.
• Variation or suspension of the insurer’s authority to conduct business in certain classes.
• Imposition of additional capital requirements where data quality is deemed poor.
• Publication of enforcement actions, causing reputational harm.
• Civil penalties for directors and senior officers under the Corporations Act 2001 if false or misleading information is provided to a regulator (s 1307, 1311).

The standard’s cross-reference to GRS 310.0 means that an error in one return can multiply enforcement risk. If APRA identifies a discrepancy between the two returns, it may escalate to a formal investigation.

No monetary fines are specified in GRS 420.0 itself. APRA’s enforcement approach is relationship-based: they will likely contact the insurer for explanation first, escalate through breach reporting, and only move to direction powers for material or systemic failure. The cost of non-compliance is therefore not a fixed penalty but the cost of regulatory attention, possible forced changes to systems and personnel, and potential public censure.

The absence of specific penalty amounts in the standard means that the real deterrent effect depends on the insurer’s risk appetite and the perceived severity of APRA’s oversight. For a well-capitalised large insurer, the risk of a fine may be low, but the risk of damage to the relationship with APRA (which can affect all other interactions) is significant.

GRS 420.0 is part of a suite of general reporting standards (GRS) issued by APRA. The most direct interaction is with GRS 310.0 (Statement of Profit or Loss and Other Comprehensive Income), because the incurred claims reported under GRS 420.0 must be consistent with the incurred claims reported under GRS 310.0. This creates a binding cross-reconciliation requirement: if the two returns differ, both may be non-compliant. The standard does not specify which total takes precedence, but GRS 310.0 is likely the master because it is a whole-of-entity return, while GRS 420.0 is a subset by class and state.

Interaction with Prudential Standard GPS 001 (Definitions) is fundamental because the class of business categories are defined therein. Any change to GPS 001’s definitions automatically flows through to GRS 420.0. The phrase “APRA classes of business (product groups) that apply for reporting are defined in GPS 001” means GPS 001 must be read together with this standard.

Interaction with Prudential Standard GPS 115 (Capital Adequacy: Insurance Risk Charge) is only for the “other” class of business. The actuary’s classification of “other” into category A, B, or C uses the risk charge categories from Attachment A of GPS 115. This links geographic revenue/claims data to capital calculations, but the standard does not merge them; GPS 115 uses its own tables, not the GRS 420.0 output.

Interaction with AASB 17 (Insurance Contracts) and AASB 101 (Presentation of Financial Statements) determines the measurement of insurance revenue. The standard explicitly references AASB 17.80(a) and AASB 17.83 for revenue, and AASB 101.82(a)(ii) for presentation. This means any change in AASB interpretations (e.g., how to allocate revenue to service components) directly affects the numbers reported.

Interaction with AASB 121 (Foreign Exchange) governs currency conversion. The instruction requires conversion to AUD in accordance with AASB 121, which gives the insurer discretion to choose spot or average rates as long as consistent with its financial statements.

Interaction with other GRS standards for balance sheet items, solvency, or other P&L lines is indirect. The data is isolated to revenue and claims; no requirement to report assets or liabilities by state.

Interaction with privacy or anti-discrimination law is minimal because the data is aggregated by class and state, not by individual policyholder.

The source document provided to the analyst includes no amendment history, preamble, or effective date. The text appears to be a complete version of the reporting standard as it stands, but without a date of issue or list of revisions. This is not unusual: APRA reporting standards are typically published as standalone PDFs with a cover page (not reproduced here) that contains the effective date, version number, and sometimes a summary of changes. The absence of this information in the supplied source means we cannot state when the standard was made or last amended.

From common knowledge (which must not be relied upon as source), GRS 420.0 was introduced in 2021 or thereabouts as part of APRA’s adoption of the new insurance accounting standard AASB 17 (effective 1 January 2023). However, since the user instruction forbids inventing facts, we must confine ourselves to the source. The source does not contain an amendment history. Therefore, the deep dive must note that the instrument as supplied contains no amendment history and that the reader should refer to the APRA website for the current version and any legislative instruments that have varied it.

If pressed, the analyst can say: “The source text does not include any amendment history, effective date, or transitional provisions. Users should verify they have the current version from the APRA website and check for any pending amendments listed on the Federal Register of Legislation.”

This is a legitimate observation based on the absence of material in the source.

The source document contains no reference to any court or tribunal decisions concerning GRS 420.0. There is no case law cited in the standard, and no case summaries are attached. Given the standard’s nature as a ministerial-like data collection instrument, it is highly unlikely to have been the subject of litigation in its own right. Disputes over APRA reporting standards are rare and typically arise only when an insurer challenges a direction or penalty based on non-compliance, which then raises questions about the validity of the standard or the fairness of its application.

The absence of litigation is consistent with the standard being unremarkable in a legal sense. No interpretive controversy has reached the Federal Court or the Administrative Appeals Tribunal (AAT). The standard’s cross-references to AASB standards may, however, be litigated indirectly if a dispute arises over the measurement of insurance revenue in a tax or solvency proceeding. But such cases would involve AASB 17, not GRS 420.0 itself.

The analyst should note: “No reported litigation specifically concerning GRS 420.0 has been identified from the source material or from general legal databases available to the analyst (though database search is outside the scope of this source). The standard has not been judicially considered.”

Several traps await the unwary preparer.

Allocation of revenue and claims to state is the biggest gotcha. The standard provides no methodology for attributing a policy that covers risks in multiple states (e.g., a commercial motor fleet operating nationally). The insurer must decide a method - by policyholder address, by risk location, by premium allocation to each state, or by claims experience. The choice can materially distort the data. If the insurer changes method without disclosing it, APRA may question the consistency. No safe harbour is provided.

Consistency with GRS 310.0 creates a reconciliation trap. The incurred claims total in GRS 420.0 must equal the total direct business incurred claims in GRS 310.0. Any difference will trigger an exception query. This means the preparer must ensure both returns are finalised together and agree exactly, which may require adjusting data to eliminate rounding differences.

Negative reporting - losses and expenses must be reported as negative numbers, not positive. If the internal system outputs losses as positive, the mapping must invert the sign. A failure to do so will result in a huge positive incurred claims figure that APRA will likely flag. The standard does not say “report positive as negative”, only “report losses and expenses as negative values.” This could be misinterpreted as applying only to the loss component.

Other classification - the three sub-categories for “other” direct business (A, B, C) depend on the actuary’s determination of GPS 115 risk category. The actuary must look at the underlying risk characteristics of the business, not just the product name. Two actuaries may disagree. This introduces subjectivity and potential inconsistency across industry. If APRA audits this choice, the actuary’s documented reasoning is critical.

No guidance on internal versus external revenue recognition - insurance revenue under AASB 17 is not always cash-based; it reflects the release of the risk margin over the coverage period. The revenue allocated to a state may not match the premiums collected in that state. APRA may be expecting figures closer to cash, but the standard explicitly requires AASB 17 revenue. This mismatch can confuse users of the data.

Single-row constraint - an insurer with multiple underwriting years or portfolios within the same class and same state cannot split them into separate rows. This forces aggregation that masks volatility. If APRA later asks for deeper breakdown, the insurer has no internal mapping from row back to sub-components unless it retains its own detailed records.

Foreign currency conversion - AASB 121 allows choices between spot rate, average rate, or spot rate at transaction date. The choice must be consistent with the financial statements, but if the financial statements use a different currency conversion method for revenue versus claims, the GRS 420.0 figures may not internally consistent.

Zero rounding - reporting in whole dollars seems simple, but totals that round to zero after negative signs may appear as zero, which could be misinterpreted. APRA may not accept zero unless there is truly no business.

First, confirm eligibility: any licensed general insurer writing direct business must report. Exempt if no direct business, but that is rare. If the insurer only writes reinsurance assumed, no requirement.

Second, obtain the current version of GRS 420.0 from APRA’s website and check for any accompanying instructions or transitional guidance. The source document provided is presumably complete, but always verify effective date.

Third, set up data extraction from the accounting system. The system must output the following four fields: Class of Business (from GPS 001 list), State (eight values), Insurance Revenue (AASB 17 basis), Incurred Claims (consistent with GRS 310.0). Ensure the system uses the right sign convention: revenue positive, incurred claims (including losses and expenses) negative if they are expense items. The standard says “Report losses and expenses as negative values.” This likely means the incurred claims field should be negative when the insurer pays out more than it collects from reinsurance, but careful: incurred claims per P&L is normally a positive expense (reducing profit). In APRA’s format, all expenses are negative. So gross incurred claims (including salvage and subrogation?) should be negative. Check GRS 310.0 for sign convention.

Fourth, allocate each policy or bundle to a state. Establish a documented policy for multi-state attribution. Common approaches: allocate based on policyholder address; allocate based on proportion of sum insured or premium earned in each state; allocate claims to state where loss occurred. The chosen method must be applied consistently year-on-year. Document the rationale.

Fifth, classify “other” business correctly. The actuary must review the product group defined as “other” in GPS 001 (products not fitting other named classes). For each such product, the actuary determines whether it falls into category A, B, or C under GPS 115 Attachment A Table 1 and Table 2. The decision must be based on risk characteristics: similar products should be allocated to the same category unless risks differ. Prepare a memorandum recording the methodology and each classification.

Sixth, compute insurance revenue. Use AASB 17 calculations. This may require the system to track the liability for remaining coverage and the allocation of the premium over the coverage period. Do not use earned premium (which is different). Revenue is defined by AASB 17.83, which includes: (a) amounts relating to services provided; (b) insurance acquisition cash flows recovered; (c) risk adjustment; and (d) amounts allocated to the loss component? Actually, AASB 17.83 is about presentation. Revenue is the change in the liability for remaining coverage that relates to service provision. Use the IFRS taxonomy disclosure references provided.

Seventh, compute incurred claims. This should equal the total claims expense for direct business recognised in profit or loss under AASB 17, including claims paid and changes in liabilities for incurred claims (excluding reinsurance? The standard says “for direct business” and “consistent with GRS 310.0”. GRS 310.0 likely includes incurred claims net of reinsurance? Check GRS 310.0 separately. To be safe, use the net incurred claims from the P&L line item “Net insurance service expense” or similar. Best practice: reconcile to GRS 310.0 exactly before reporting.

Eighth, ensure each combination of class and state appears on only one row. If the insurer writes, say, two different Householder products in NSW, the data must be aggregated into one row. The system must collapse rows.

Ninth, convert foreign currency amounts using AASB 121. It is acceptable to use the same exchange rates used for general ledger purposes. Disclose the method in the entity’s internal documentation.

Tenth, validate the data. Run a cross-check: sum insurance revenue over all rows = total direct insurance revenue per financial statements (or per GRS 310.0, if that return separately reports direct revenue). Similarly, sum incurred claims over all rows = total direct incurred claims per GRS 310.0. If any difference, adjust.

Eleventh, lodge via APRA’s approved channel (Direct to APRA / APRA Connect). Adhere to lodgement deadlines specified in APRA’s overarching deadline schedule.

Twelfth, retain records, documentation of allocation method, actuary’s classification memo, and reconciliation to GRS 310.0 for at least the period required by APRA (usually 7 years). Be prepared to respond to APRA queries, especially if data appears anomalous.

Thirteenth, monitor amendments. APRA may update GRS 420.0 over time. Subscribe to APRA’s notification service or check the Federal Register of Legislation periodically. Any transitional arrangements when new versions are released must be followed.

Compliance is not a one-off project; it requires embedding the extraction, classification, and allocation processes into the regular financial close cycle. The key cost is internal staff time and system changes. Outsourcing to a compliance consultant is possible but the actuary’s personal duty for “other” classification cannot be delegated.