IFRS 17 in SAP Analytics Cloud: CSM, risk adjustment and the measurement models

IFRS 17 changed how insurers report the profit on insurance contracts. Two figures carry the standard — the Contractual Service Margin (CSM) and the Risk Adjustment (RA) — and both are roll-forwards: an opening balance, a set of movements, a closing balance. In a SAP Analytics Cloud model that structure is everything. Model the movements and balances correctly and the reconciliations tie out; get the aggregation wrong and the disclosures are unauditable. This guide explains what IFRS 17 requires and how to build the CSM and RA roll-forwards in SAC.

What IFRS 17 requires

IFRS 17, issued by the IASB and effective for periods beginning on or after 1 January 2023, replaced IFRS 4 and ended the patchwork of national insurance accounting. Its principle: measure a group of insurance contracts at the fulfilment cash flows plus a Contractual Service Margin, and recognise the profit as the insurance service is delivered rather than when premiums are received. The result is far more comparable reporting — and far more data to track, contract group by contract group, period after period.

The building blocks

Under the General Measurement Model, the liability is built from four blocks:

• Future cash flows — an unbiased, probability-weighted estimate of the premiums, claims and expenses the group will generate.
• Discounting — those cash flows are discounted for the time value of money.
• Risk Adjustment (RA) — an explicit margin for the uncertainty in non-financial risk (claims frequency and severity), kept separate from the discounting of financial risk.
• Contractual Service Margin (CSM) — the unearned profit. At inception the CSM is set so that no day-1 gain is recognised; it is then released to profit or loss over the coverage period.

A simple inception example: an insurer issues 100 contracts at £1,000 each (£100k premium). If the discounted future cash outflows are £80k and the risk adjustment is £10k, the CSM is £100k − £80k − £10k = £10k. That £10k is the profit the insurer will earn as it provides cover — not on day one.

The three measurement models

IFRS 17 offers three measurement approaches, and a clean model must know which applies to each group:

• GMM (General Measurement Model), also called the building block approach — the default, used for most long-duration contracts.
• PAA (Premium Allocation Approach) — a simplified option for short-duration contracts (coverage of one year or less, or where results would not differ materially from the GMM). The liability for remaining coverage is measured much like unearned premium.
• VFA (Variable Fee Approach) — for direct participating contracts, where the CSM absorbs the insurer's share of the change in the value of underlying items.

Each model still requires a Risk Adjustment for non-financial risk. The Measurement-model split is therefore a first-class dimension in any SAC model, not an afterthought.

The CSM roll-forward — the heart of the model

The CSM is not a static number; it is a balance that moves every period. A faithful roll-forward runs: opening CSM + CSM on new business + interest accreted at the locked-in rate + changes in estimates of future cash flows (future service) − CSM released to P&L = closing CSM. Two rules govern the movements. First, changes in estimates that relate to future service adjust the CSM; changes relating to current or past service, and experience adjustments, go to profit or loss immediately. Second, the CSM can never be negative — when a group is onerous, the shortfall is recognised at once as a loss component in P&L. The Risk Adjustment runs its own parallel roll-forward, with its release also flowing to profit.

Structuring it in SAP Analytics Cloud

IFRS 17 is the clearest case in regulatory reporting where the movement structure, not just the balance, has to be modelled explicitly.

Dimensions

Five dimensions carry most IFRS 17 reporting: Group of contracts (the cohort / portfolio / annual-cohort unit of account), Measurement model (GMM, PAA, VFA), Movement type (opening, new business, interest accretion, changes in estimates, release, closing — the roll-forward steps), Entity, and Version (Actual plus scenarios). The Movement-type dimension is what turns an opaque closing CSM into an auditable reconciliation a reviewer can follow line by line.

Measures and aggregation

Here the discipline is twofold. Movements are additive within a period — opening, new business, accretion, changes and release SUM along the Movement-type dimension to give the closing balance, which is exactly what the disclosure reconciliation shows. But the closing CSM, RA and the liability balances are balances: across a time hierarchy they must aggregate with LAST (closing value), never SUM, or a yearly figure becomes the nonsensical sum of four quarter-end balances. This is the same trap covered in choosing the right aggregation in SAC, and IFRS 17 is where it bites hardest, because the model holds both movements (additive) and balances (LAST) side by side.

The coverage-unit driver

The CSM release is not arbitrary — it is allocated across coverage units that reflect the quantity of insurance service provided each period. Model coverage units as their own measure and compute the period release as a calculated measure (CSM ÷ remaining coverage units × current-period units). Storing the release as a hard number breaks the link to the driver and makes the reconciliation impossible to rebuild.

Versions: closing, re-forecast and what-if

IFRS 17 figures are re-measured every close as assumptions update. The Version dimension lets the model hold the Actual close alongside re-forecasts and assumption scenarios — a discount-rate shift, a worsening loss ratio — and watch the CSM and loss component respond. This is the Actual / Budget / Forecast / scenario pattern from using the Version dimension in SAC Planning, applied to the insurance liability instead of the P&L.

A worked mini-example

Take the £10k CSM at inception above, over a five-year coverage period with equal coverage units. In year 1 the insurer releases £10k ÷ 5 = £2k of CSM to profit, accretes interest on the opening balance, and adjusts for any change in future cash-flow estimates. If, in year 2, revised assumptions increase expected future claims by £1k (future service), that £1k reduces the CSM rather than hitting P&L — unless it pushes the CSM below zero, in which case the excess becomes an immediate loss. Model each of those as a separate Movement-type value and the closing CSM, and the disclosure reconciliation, fall out automatically.

Common mistakes to avoid

• SUM on balances. Closing CSM, RA and liability balances aggregate with LAST across time, not SUM — even though the movements within a period do SUM.
• No Movement-type dimension. Without it the roll-forward cannot be reconstructed and the disclosures are unauditable.
• Hard-coding the CSM release. Drive it from coverage units as a calculated measure.
• Ignoring onerous groups. A negative CSM is not allowed; model the loss component explicitly.
• Mixing measurement models. Keep GMM, PAA and VFA on a dimension so their different mechanics never blur together.

Where this fits

IFRS 17 rarely stands alone: the same insurers steer capital under Solvency II, and the "balance vs movement" discipline here is the accounting cousin of the "calculate, don't sum" rule that also governs Basel III ratios. For a structured starting point, our insurance template already separates groups, movements and balances, and the verified & maintained regulatory kit adds the roll-forward measures and an import guide.

Sources

IFRS 17 Insurance Contracts (IASB), effective 1 January 2023, including the June 2020 amendments; consequential amendments from IFRS 18 (2024). Always work from the current consolidated IFRS 17 text and your auditor's interpretations, as application guidance continues to evolve.