IFRS 17 Insurance Contracts: What Auditors at Non-Big 4 Firms Actually Need to Know

Who does IFRS 17 actually apply to?

The scope question matters more than most auditors assume. IFRS 17 does not apply only to insurance companies. It applies to any entity that issues insurance contracts, reinsurance contracts, or investment contracts with discretionary participation features (provided the entity also issues insurance contracts). IFRS 17.3 sets this out. A manufacturing group with a captive insurer, a construction firm that issues warranty contracts meeting the insurance contract definition, a financial holding company with an embedded guarantee: all of these can fall within scope.

The definition itself has not changed from IFRS 4. An insurance contract is one under which the issuer accepts significant insurance risk from the policyholder by agreeing to compensate if a specified uncertain future event adversely affects the policyholder (IFRS 17 Appendix A). The “significant insurance risk” test is where judgment sits. If the contract transfers risk that is genuinely uncertain and would cause a material payment obligation, it is probably in scope. Financial guarantee contracts present an additional choice. IFRS 17.7(e) permits entities that have previously applied IFRS 9 to financial guarantees to continue doing so. But if the entity previously asserted these were insurance contracts under IFRS 4, IFRS 17 applies.

For auditors at non-Big 4 firms, the practical trigger is this: when a client has a subsidiary, joint venture, or contractual arrangement that involves risk transfer and premium collection, check whether IFRS 17 applies before assuming it sits under IFRS 9 or IFRS 15. The scope net is wider than the name suggests.

How does the grouping requirement work?

IFRS 17 does not measure individual contracts. It measures groups of contracts, and the grouping rules are prescriptive. Getting the grouping wrong affects every number downstream.

IFRS 17.14 requires the entity to identify portfolios first. A portfolio contains contracts subject to similar risks and managed together. Within each portfolio, IFRS 17.16 requires the entity to divide contracts into at least three profitability groups: contracts that are onerous at initial recognition, contracts that at initial recognition have no significant possibility of becoming onerous subsequently, and a remaining group.

IFRS 17.22 adds a further constraint: a group cannot include contracts issued more than one year apart. This annual cohort requirement prevents the entity from burying losses in older profitable groups by adding new contracts.

The grouping decision is made at initial recognition and is not reassessed (IFRS 17.24). This is a critical audit point. If management grouped contracts incorrectly at inception, the error propagates through every subsequent measurement. Your file should document how the client determined which contracts were onerous at initial recognition, what evidence supported the “no significant possibility of becoming onerous” classification for the second group, and whether the annual cohort constraint was applied.

The EU endorsed IFRS 17 with an exemption to the annual cohort requirement for certain intergenerational mutualized contracts. If your client operates in the EU and claims this exemption, you need to document the basis separately.

The general measurement model explained

The general measurement model (GMM) is the default under IFRS 17. Every group of insurance contracts is measured using this model unless the premium allocation approach or variable fee approach applies.

The GMM has four building blocks. The first is the estimate of future cash flows: the expected present value of all cash inflows (premiums) and outflows (claims, benefits, expenses) arising from the group. IFRS 17.33 requires these to be current estimates based on the most up-to-date information at the reporting date. The second building block is the discount rate adjustment. IFRS 17.36 requires discounting at rates reflecting the time value of money and the financial risks associated with those cash flows. The entity can derive discount rates either top-down (from observable asset portfolio yields, adjusted for differences in cash flow characteristics) or bottom-up (from a risk-free yield curve plus an illiquidity premium). Both methods should produce a similar result, but they rarely produce an identical one. The choice and the resulting rates are audit evidence you need.

The third building block is the risk adjustment for non-financial risk. IFRS 17.37 requires a separate, explicit provision reflecting the compensation the entity demands for bearing uncertainty about the amount and timing of cash flows from non-financial risk. The standard does not prescribe a technique. Entities use confidence level approaches, cost-of-capital methods, or other quantitative techniques. Whatever method the client uses, IFRS 17.119 requires disclosure of the confidence level equivalent.

The fourth building block is the contractual service margin (CSM). This is where IFRS 17 differs most dramatically from what came before. The CSM represents unearned profit. At initial recognition, if expected future cash inflows exceed expected outflows (plus risk adjustment), the difference is not recognised as a day-one gain. It is stored in the CSM and released to profit or loss over the coverage period as the entity provides insurance services (IFRS 17.44). The release pattern must reflect the transfer of services, measured in coverage units (IFRS 17.B119).

For the auditor, the CSM is where most judgment concentrates. How management defines coverage units determines the profit recognition pattern for the entire group. A life insurer that defines coverage units purely on sum assured will release CSM differently from one that weights both sum assured and expected claims incidence. Both might be defensible. Your job is to evaluate whether the chosen basis reflects the actual service being provided, and to document why.

If a group of contracts is onerous at initial recognition (expected outflows exceed expected inflows plus risk adjustment), no CSM is recognised. The loss is taken immediately in profit or loss (IFRS 17.47). At each subsequent reporting date, the entity reassesses whether a previously profitable group has become onerous. This is the loss component test, and it should appear in the working papers for every group.

When can the client use the premium allocation approach?

The premium allocation approach (PAA) is a simplification permitted under IFRS 17.53. It is not a separate model. It produces results similar to the GMM for contracts that meet the eligibility criteria.

A group of contracts qualifies for the PAA if the coverage period is 12 months or less, or if the entity reasonably expects that the PAA measurement would not differ materially from the GMM measurement (IFRS 17.53). Most non-life, short-duration contracts (annual motor, property, liability policies) will qualify under the first criterion. That test is simple and binary. For contracts exceeding 12 months, the materiality assessment requires more judgment. The client needs to demonstrate (and you need to verify) that the cash flow variability and timing patterns over the coverage period would not cause the PAA liability to differ materially from the GMM liability.

Under the PAA, the liability for remaining coverage is measured as premiums received minus amounts recognised as revenue for services provided, minus any acquisition cost asset (IFRS 17.55). There is no explicit CSM calculation, no risk adjustment for remaining coverage (unless the contract is onerous), and no discounting of the liability for remaining coverage unless the time value of money is significant. The liability for incurred claims is still measured the same way as under the GMM: fulfilment cash flows comprising current estimates and discounting, plus a risk adjustment.

The PAA removes significant measurement complexity. For most non-Big 4 engagements involving insurance contracts, the PAA will be the applicable approach. Your audit file should document the eligibility assessment, not just state that the PAA was applied.

The variable fee approach for participating contracts

Some insurance contracts include direct participation features: the policyholder receives a share of returns from a specified pool of underlying items (IFRS 17.B101). Life insurance contracts linked to a unit fund or a with-profits fund are common examples. For these contracts, IFRS 17 requires the variable fee approach (VFA), a mandatory modification of the GMM.

Under the VFA, the CSM absorbs changes in the entity’s share of the fair value of underlying items. This means that financial risk variations adjust the CSM rather than flowing through profit or loss. The logic is that the entity’s remaining obligation is effectively a variable fee for investment management services. The VFA also adjusts the CSM for changes in the time value of money and financial risk assumptions, which the standard GMM would recognise in profit or loss (or OCI, if elected).

The VFA eligibility test (IFRS 17.B101) requires the entity to demonstrate that the contractual terms specify the policyholder participates in a clearly identified pool, the entity expects to pay the policyholder a substantial share of returns from that pool, and a substantial proportion of any change in amounts paid relates to variation in the underlying items. All conditions must be met at inception.

For auditors, the VFA matters because it changes where volatility appears. If a client incorrectly applies the GMM to a contract that qualifies for the VFA (or vice versa), the profit or loss pattern and balance sheet volatility will be wrong. Your file should include the VFA eligibility assessment for any participating contract.

Worked example: auditing a captive insurer under IFRS 17

Client: Veldkamp Holdings N.V., a Dutch industrial group with €87M consolidated revenue. Veldkamp owns Veldkamp Verzekeringen B.V., a captive insurance subsidiary that underwrites product liability and property damage policies for group entities. Annual premiums collected: €2.1M. All policies have a coverage period of 12 months. The captive reinsures 40% of risk with an external reinsurer.

Step 1: Confirm scope

The captive issues insurance contracts transferring significant insurance risk from group entities. IFRS 17.3(a) applies. The reinsurance contract held with the external reinsurer is also in scope under IFRS 17.3(b).

Step 2: Assess measurement model eligibility

All policies have coverage periods of 12 months or less. The PAA eligibility criterion under IFRS 17.53(a) is met.

Step 3: Verify grouping

The captive underwrites two product lines: product liability and property damage. These have different risk profiles and are managed as separate portfolios (IFRS 17.14). Within each portfolio, management classified all contracts as having no significant possibility of becoming onerous at initial recognition, based on historical loss ratios of 45% and 52% respectively.

Step 4: Test the liability for remaining coverage

Under the PAA, the liability for remaining coverage at year-end equals premiums received (€2.1M) minus revenue recognised for the portion of coverage provided (€1.75M based on 10 months elapsed), minus the deferred acquisition cost asset (€0.12M). Resulting liability: €0.23M.

Step 5: Test the liability for incurred claims

The captive has 14 open claims totalling €0.38M in management’s best estimate, plus a risk adjustment of €0.04M. Discounting is immaterial given claims settlement within 18 months.

A reviewer opening this file sees the scope assessment, the PAA eligibility conclusion, the grouping rationale, and the liability tested in two components with specific ISA 540 documentation for the estimate.

Practical checklist for your file

1. Confirm IFRS 17 scope by checking whether any subsidiary, JV, or contractual arrangement involves risk transfer and premium collection. Reference IFRS 17.3 and IFRS 17.7(e) for financial guarantees.
2. Document the measurement model eligibility assessment. For PAA, record why IFRS 17.53(a) or IFRS 17.53(b) is satisfied. Do not assume PAA applies without evidence.
3. Verify the grouping by checking the portfolio definitions (IFRS 17.14), the profitability classifications (IFRS 17.16), and the annual cohort constraint (IFRS 17.22).
4. For GMM engagements, obtain and test the discount rate derivation (top-down or bottom-up per IFRS 17.B72–B85), the risk adjustment methodology, its confidence level equivalent (IFRS 17.119), and the CSM coverage unit definition.
5. For PAA engagements, recalculate the liability for remaining coverage and separately test the liability for incurred claims using fulfilment cash flows.
6. Check the onerous contract test at each reporting date. Even PAA groups require this assessment when facts and circumstances indicate the group may be onerous (IFRS 17.57).

Common mistakes

• Skipping the scope assessment entirely on non-insurance clients. The FRC’s thematic review of IFRS 17 first-year disclosures noted that disaggregation and proportionality remain areas requiring continued focus, and auditors of groups with captive insurance subsidiaries should assess whether IFRS 17 applies to any entity in the group structure.
• Applying the PAA without documenting the eligibility assessment. Stating “coverage period is 12 months” is insufficient if some contracts have extension clauses or multi-year terms with annual renewal options.
• Treating the CSM release as a mechanical straight-line allocation. IFRS 17.B119 requires coverage units to reflect the quantity of benefits and expected duration. A straight-line release is only appropriate if the service provided is uniform across the coverage period.

Related Ciferi content

Related guides:

Put audit concepts into practice with these free tools:

Frequently asked questions