IFRS 17, Solvency II and AI: Data Readiness Guide DACH Insurers

/ ai, ai transformation, data, data transformation, development

This guide addresses the most common challenge facing CAIO, CDO, and CTO at DACH insurance carriers — P&C and Life — in 2026: how to build genuine AI capability while satisfying BaFin and FINMA regulatory requirements. The recommendations are grounded in the specific regulatory context of DACH (Germany, Switzerland, Austria) and the practical realities of organisations managing legacy infrastructure alongside ambitious AI transformation programmes.

IFRS 17 and Solvency II: The Data Architecture Imperative

IFRS 17 changed insurance accounting more fundamentally than any standard in the past two decades. The standard requires granular, contract-level measurement of insurance liabilities, which demands a data architecture that most legacy insurers in DACH were not built to support. Solvency II reinforces this requirement from a prudential angle — the Own Risk and Solvency Assessment (ORSA) process needs the same granular, high-quality data that IFRS 17 requires for financial reporting.

For insurers deploying AI, this creates both a challenge and an opportunity. The challenge: AI models using financial or actuarial data must be integrated into the same data lineage framework that satisfies IFRS 17 and Solvency II auditors. The opportunity: the data infrastructure investment required for IFRS 17 compliance — a modern data platform with documented lineage, automated quality controls, and near-real-time processing — is exactly the infrastructure that enables high-quality ML models for underwriting and claims.

IFRS 17 requires contract-level data granularity that most legacy insurer data architectures cannot currently provide from a single source without manual reconciliation.
AI models using actuarial or financial data must be integrated into IFRS 17 data lineage frameworks — regulators will ask about this during examination.
The data infrastructure investment for IFRS 17 compliance is a foundation for AI capability — treat it as dual-purpose investment, not pure compliance cost.

Building a Dual-Purpose Data Platform

The most efficient approach for DACH insurers is building a data platform that serves both IFRS 17/Solvency II regulatory reporting and AI/ML workloads simultaneously. This dual-purpose architecture has three layers: an ingestion and integration layer that standardises data from SAP FS-PM, Guidewire, Duck Creek and other source systems; a governed data layer where data quality, lineage, and access controls are enforced for regulatory compliance; and an analytics and AI layer where ML models are trained and deployed using the governed data.

Technology choices matter for regulatory compliance. Azure Microsoft Fabric and Databricks Unity Catalog both offer built-in data lineage and access control features that satisfy BaFin and FINMA documentation requirements. Snowflake Data Clean Rooms can address data sharing requirements between group entities while maintaining GDPR compliance. The critical design decision is establishing clear data ownership and stewardship: each data domain must have a named owner accountable for quality, and every transformation applied to regulatory data must be documented and version-controlled.

Dual-purpose architecture serves both IFRS 17 reporting and AI workloads from the same governed data platform — avoid building separate environments.
Azure Microsoft Fabric and Databricks Unity Catalog both provide built-in lineage features that simplify regulatory documentation obligations.
Named data domain owners are essential — without clear accountability for data quality, IFRS 17 and AI models both degrade over time.

AI Use Cases Unlocked by Regulatory Data Investment

Once the IFRS 17-compliant data platform is in place, insurers in DACH can unlock high-value AI use cases that were previously impossible. Underwriting automation becomes viable when policy application data is standardised across products and distribution channels — the same standardisation required for IFRS 17 cohort grouping. ML-powered fraud detection becomes significantly more accurate when historical claims data is complete, consistent, and spanning multiple years — which IFRS 17 compliance forces you to achieve. Predictive lapse modelling for Life insurers becomes possible when policyholder behaviour data is linked to policy and claims data in the same platform.

The typical investment sequence for DACH insurers: IFRS 17 data platform build (12–18 months), followed by AI model development (6–12 months per use case), enabled by the same data infrastructure. mindit.io has delivered this sequence for insurance clients in DACH, building data platforms that satisfy BaFin and FINMA regulatory requirements while delivering immediate AI business value.

IFRS 17 data standardisation directly enables underwriting automation — the cohort grouping logic creates the feature engineering foundation for ML models.
Claims data completeness required for Solvency II ORSA significantly improves fraud detection model performance — treat compliance data as AI training data.
Typical timeline: 12–18 months for IFRS 17-compliant platform, then 6–12 months per AI use case — plan as a continuous programme, not sequential projects.

Pro Tips

Engage BaFin and FINMA relationship managers early — pre-notification of significant AI initiatives builds regulatory goodwill and surfaces expectations that should inform your governance design.

Nearshore partners with documented BaFin, FINMA, IFRS 17, Solvency II, and GDPR delivery experience significantly reduce implementation time — they arrive with frameworks rather than building them at your cost.

Design all AI governance documentation to be regulator-readable from day one — if you cannot explain your model governance to an examiner in 10 minutes, you have a compliance gap.

Conclusion

IFRS 17 and Solvency II data investments are not sunk costs — they are the foundation for AI capability. Insurers in DACH that treat regulatory data programmes as dual-purpose investments consistently deliver faster AI ROI than those that build compliance and AI infrastructure separately. mindit.io specialises in building data platforms that satisfy BaFin and FINMA requirements while enabling high-value AI use cases.

Ready to Start Your AI & Data Transformation?

mindit.io works with banking, retail, and insurance organisations across DACH, UK, and BENELUX. Talk to our team about your programme. Contact mindit.io →