Insurance SAC report design: Solvency II, technical steering and IFRS 17 in one model

Insurance reporting has three audiences that rarely see the same numbers cleanly: the actuarial/solvency function, the technical-steering team, and the accounting function now living under IFRS 17. "Insurance SAC report design" done well means one governed model that serves all three, so the solvency ratio, the combined ratio and the CSM roll-forward reconcile instead of drifting. This guide covers how to structure that model in SAP Analytics Cloud and which reports to build on it.

One model, three lenses

An insurer's reporting shares a common spine: Line of business (motor, home, life), Region, Customer segment, Distribution channel, Underwriting year and a Version dimension for actual/target/forecast. Build that once and the solvency view, the technical view and the IFRS 17 view are three lenses on the same data rather than three reconciliation headaches.

Lens 1 — solvency (Solvency II)

The solvency report tracks the SCR (solvency capital requirement), MCR (minimum capital requirement), eligible own funds and the resulting solvency ratio, by risk module and entity. The critical design rule, and the one most generic dashboards get wrong: the solvency ratio must be allowed to exceed 100%. A healthy insurer runs well above it; a report that silently caps the value at 100% hides exactly the headroom the board needs to see. Model SCR and MCR coverage against the EIOPA reference levels — our Solvency II in SAC guide covers the ladder structure, and the paid Solvency II accelerator ships it with the thresholds pre-built and uncapped.

Lens 2 — technical steering

This is the profitability lens: combined ratio, loss ratio, claim frequency and average claim cost by product and region. The combined ratio (claims plus expenses over premiums) is the single most-watched number — above 100% the underwriting book loses money before investment income. Design the technical view so the combined ratio decomposes into its loss and expense parts and drills to the product driving a deterioration.

Lens 3 — IFRS 17 accounting

IFRS 17 added a measurement layer most insurers now report through: the contractual service margin (CSM) roll-forward, risk adjustment, and the BBA/VFA/PAA model structures. It is an accounting view, but it shares the line-of-business and underwriting-year dimensions with the technical lens, so it belongs on the same model. The IFRS 17 in SAC guide walks through the CSM waterfall, and the paid IFRS 17 accelerator encodes the roll-forward.

Design habits for an auditable insurance report

Insurance reports face both a prudential regulator and a financial auditor, so build for both: never cap a solvency ratio, keep one documented definition per ratio (combined ratio and loss ratio have several conventions — pick and state yours), and version the numbers so actual, target and forecast sit together. The reconciliation between the technical result and the IFRS 17 result is the question auditors ask first; a shared model answers it by construction.

Where to start

Start from a working model rather than a blank canvas. The free Solvency II, technical steering and underwriting templates ship with the KPIs, dimensions and sample data in place. For the regulatory and accounting layers, the paid Solvency II and IFRS 17 accelerators encode the ratios and the CSM roll-forward. See also the sector companions — banking report design and utilities report design — and browse everything in the catalog.

Note: General guidance for designing insurance reporting in SAP Analytics Cloud, built from public EIOPA and IFRS materials — not regulatory, actuarial or accounting advice; you remain the validator of your own figures. Independent project, not affiliated with SAP SE. "SAP" and "SAP Analytics Cloud" are trademarks of SAP SE.