← All insights
Insurance2 min read

IFRS 17 needs judgement lineage, not another close checklist

The hard IFRS 17 questions sit in assumptions, methodology choices and the seam between actuarial and finance.

IFRS 17 is often managed as a reporting timetable. The harder issue is judgement lineage: how assumptions, methodology choices, data inputs, actuarial model outputs, finance postings and disclosure lines connect across the reporting chain.

Where the seam sits

Actuarial and finance teams work at different levels of detail. Actuarial engines produce model outputs. Finance needs ledger balances, CSM roll-forwards, disclosure reconciliations and explanations of movement. The seam between them is usually bridged by people and spreadsheets, relying on memory of which assumption changed and which methodology version applied.

Process context across the seam

xflow holds the IFRS 17 process as one connected view across technologies: the assumptions and methodology versions, the code and models that apply them, the manual steps between actuarial and finance, and the owner of each judgement. Regulatory traceability has been proved this way across a system built on multiple technologies.

The engines and reporting tools stay in place. What changes is that every disclosure line can be traced back through the judgements that shaped it.

Which outcome do you need to prove now?

Start with one critical outcome. We’ll show you how it is produced today, where that differs from what is documented, and how to close the gaps.

Start with one critical outcome