Solvency II + IFRS 17: two frameworks, one compliance workflow.

This guide is built from European life and P&C engagements where teams running Solvency II Pillar III and IFRS 17 disclosures realized they were duplicating ~60% of the work.

The two frameworks at a glance

Solvency II (EU, 2016): the prudential capital regime for insurers. Three pillars — quantitative requirements (SCR/MCR), governance and ORSA, public disclosures (SFCR/QRTs). Authored by EIOPA. The regulator's question: does the insurer have enough capital, governed responsibly, and disclosed honestly?

IFRS 17 (IASB, 2023): the global accounting standard for insurance contracts. Replaces IFRS 4. Mandates a current-value measurement model (CSM, building blocks) and detailed disclosures. The auditor's question: do the insurer's published financials accurately reflect the economics of its contracts?

Different audiences, different objectives. Same source data: contracts, actuarial assumptions, risk margins, expected cash flows.

Where they overlap (and where insurers duplicate work)

The substantive overlap is significant:

• Best-estimate liability. Solvency II's BEL and IFRS 17's fulfilment cash flows are computed from the same underlying expected cash flows, with different discount-rate methodologies and adjustments. Same source data.
• Risk margin / risk adjustment. Solvency II's risk margin (cost-of-capital approach) and IFRS 17's risk adjustment (entity-specific, multiple methods allowed) differ in mechanics but rely on the same risk-driver inventory.
• Contract boundary & portfolio aggregation. Both frameworks require defining what counts as a contract and how contracts aggregate. Definitions differ in detail; the inputs are the same product taxonomy.
• Disclosures. SFCR/QRTs (Solvency II) and IFRS 17 disclosures both require sensitivity analyses, reconciliations, and explanations of significant judgments. Different formats; same underlying analytics.
• Internal controls. Both require documented controls over actuarial models, data, and assumptions. The control objectives are largely identical.

Two teams, two control libraries, two SOX-style assertions, two audit trails, two regulator interactions. Easy to see why it's expensive.

The unified compliance workflow

RegAI's approach: ingest both frameworks once, map them to a shared product/contract taxonomy, and produce a single control matrix that serves both regulator and auditor views.

Step 1 — Ingest both regimes

Solvency II Level 1 (the directive) plus delegated regulations and EIOPA technical specifications. IFRS 17 standard plus IASB IFRIC interpretations and the disclosure illustrative examples. Roughly 800–1,000 distinct obligations after deduplication, depending on taxonomy granularity.

Step 2 — Map to a shared product taxonomy

Most insurers already maintain a product hierarchy (life / non-life, by line of business, by jurisdiction). RegAI uses that as the spine. Each obligation is tagged to:

• Framework (SII / IFRS 17 / both)
• Pillar (SII Pillar I / II / III)
• Product line
• Reporting cycle (quarterly / annual / one-off)
• Materiality threshold

Step 3 — Identify shared vs. divergent obligations

A material chunk maps cleanly to both frameworks. RegAI surfaces:

• Shared — same operational obligation under both regimes (e.g., "document the methodology for setting actuarial assumptions"). Single control, two regulator views.
• Convergent — different mechanics, same data input (e.g., expected cash flows). Single data source, two computation paths.
• Divergent — genuinely different requirements (e.g., Solvency II's MCR floor has no IFRS 17 analog). Separate handling, but documented in one matrix.

Typical breakdown: 35% shared, 40% convergent, 25% divergent. The first two categories are where the savings live.

Step 4 — Gap analysis against existing controls

For each obligation, score coverage against the existing control library. Common gap patterns:

• Actuarial model documentation strong on Solvency II side, sparse on IFRS 17 disclosures (especially CSM rollforward narratives).
• Data lineage controls exist for QRTs but don't extend to IFRS 17 disclosure tables.
• Assumption-setting governance has SII committees but lacks IFRS 17-specific sign-off paths.

Step 5 — Draft and consolidate controls

For shared obligations, RegAI drafts a single control that satisfies both. For convergent obligations, RegAI links shared upstream controls (data integrity) to framework-specific downstream controls (SCR computation vs. CSM rollforward). For divergent, separate framework-specific controls.

The output is a unified control matrix that lets internal audit do one walkthrough covering both regimes.

What this saves a typical insurer

From a recent engagement with a multi-state US insurer running both regimes:

• 13,000 pages of regulation analyzed across both frameworks.
• 40%+ gap reduction after consolidation.
• One audit trail. One regulatory walkthrough. One actuarial sign-off touchpoint.

The biggest unlock isn't the page-counts — it's the org chart. Two teams running parallel programs become one team running a unified workflow with regulator-specific reporting views on top.

Common pitfalls

• Trying to merge the frameworks themselves. Solvency II and IFRS 17 are different by design. Don't unify the standards; unify the controls and data that support both.
• Forcing identical timing. Solvency II quarterly QRTs and IFRS 17 quarterly disclosures don't have the same cadence everywhere. Map cycles per jurisdiction.
• Single accountability ownership. Insurance accounting is the CFO's. Capital regime is the CRO's. Don't pick one — design the workflow with explicit hand-offs.
• Treating IFRS 17 as just "a new disclosure standard." The CSM rollforward is genuinely new and operationally complex. Underestimating it is the most common cause of late deliveries.

Where to start

Pick one product line in one jurisdiction (life, single legal entity, one currency). Run the unified mapping on that. The patterns scale; the early-discovery insights save weeks on the rest.

More on RegAI for insurance → | Book a 45-minute walkthrough → on a slice of your own SII / IFRS 17 scope.