← 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.

Keep reading

More insights

Process context2 min read

Reconcile only when the same question gives two different numbers

Golden-source programmes assume one true number is waiting to be found. There isn't. The number depends on the question, so the question has to travel with it.
Code2 min read

The code behind a regulatory figure should be something the business can question

The business owns the regulatory outcome but rarely built the systems that produce it. Joining the code to the process gives accountable people a view they can interrogate.
Agentic processes2 min read

Your data says what happened. Your catalogue says why. The process says how.

Entity and transaction data give the what and the when. Catalogues and policies give the why. The how, the process that turns a rule into a reported figure, is the context agents need.
Request a demo

Which number matters most to you?

Tell us the number and we will expose the process context on which it is built: the objective it serves, and the code, data, spreadsheets and people that produce it.

Request a demo