Solvency II and IFRS 17 reporting: proving how each outcome was produced
Insurers can show that their figures reconcile. The harder question is how each outcome was produced, across actuarial, finance and spreadsheets.
Solvency II and IFRS 17 reporting asks an insurer to show how each reported outcome was produced: the Own Funds and Solvency Capital Requirement in its quantitative reporting templates, and the contractual service margin and insurance revenue in its IFRS 17 disclosures. Both run through actuarial models, assumptions, finance systems and spreadsheets owned by different teams. Supervisors and auditors now look past the template to that chain. Most insurers can show that their figures reconcile. Fewer can show, quickly and from evidence they already hold, how an outcome was produced and why it is right.
What Solvency II and IFRS 17 reporting require
Solvency II sets the prudential regime for European insurers, and in the UK its successor is Solvency UK. Insurers report quarterly and annually to their supervisor through quantitative reporting templates (QRTs), publish a Solvency and Financial Condition Report (SFCR) and submit a Regular Supervisory Report. Behind the templates sit the valuation of technical provisions, the calculation of Own Funds and the Solvency Capital Requirement, whether by standard formula or internal model. The amended Solvency II Directive, which applies from early 2027, changes parts of those calculations, and changes to calculations mean changes to the code and spreadsheets that perform them.
IFRS 17, effective since 1 January 2023, sets how insurers measure and report insurance contracts in their financial statements. It requires contracts to be grouped, cash flows projected and discounted, a risk adjustment calculated and a contractual service margin (CSM) held and released over time. Each of those steps depends on assumptions, methodology choices and judgements, and each is examined at year end.
The two regimes draw on much of the same data and many of the same models, but they answer different questions. A Solvency II technical provision and an IFRS 17 liability for the same contracts are not the same outcome, and they are not meant to be.
Where the evidence breaks down
Between actuarial and finance. Actuarial models produce cash flows and assumptions; finance systems turn them into reported outcomes. The hand-off is often a file, a spreadsheet or a manual load, owned by neither side. When an outcome is questioned, the trail runs into that gap.
In the judgement. IFRS 17 and Solvency II both depend on judgement: assumption setting, methodology versions, expert overrides. A close checklist records that a judgement was approved. It rarely records which version of the assumption flowed into which reported line. IFRS 17 needs judgement lineage, not another close checklist.
In the checks. Reconciliations and movement analysis confirm that figures agree and move plausibly. An error of treatment agrees every period. In a 2026 Final Notice, the PRA set out how a £99.9 million overstatement of an insurer's Own Funds passed through a data hand-off between two teams and the firm's checks for five quarters before a committee question exposed it.
In change. When an assumption, a model or a rule changes, which reported outcomes move? Without a connected view of the process, the answer comes from people who know, and impact analysis is redone for every change.
Why it is a process question
Every one of these breaks has the same cause. The process as documented (policies, methodology papers, model documentation, the data catalogue) and the process as operated (data flowing through actuarial models, code, spreadsheets and manual steps to a reported line) are held together by people and projects. Each audit, each supervisory question and each change rebuilds the link by hand.
That is the same gap banks face under BCBS 239 and in their regulatory reporting process, with more hand-offs and more judgement.
Process context for insurers
xflow builds process context: one executable view of a reporting process in which the documented and operated versions are held together, from the regulatory objective through policy, methodology, actuarial models, code, data, spreadsheets and manual steps to the reported outcome.
For an insurer that gives three things. The route from contract data and assumptions to each disclosure line or template cell is traced across every model, system and spreadsheet it runs on, so a reported outcome can be explained without assembling a team. Real data can be run through the process to check that it produces the reported outcome, which tests the treatment, not only the agreement. And when an actuarial model or assumption changes, the reported outcomes it touches are visible before anything is altered.
At an insurer, this traceability has been proved across a reporting system built on multiple technologies, from contract data, assumptions and measurement logic through to each disclosure line, and it can be re-run at close.
Questions about Solvency II and IFRS 17 reporting
What are Solvency II quantitative reporting templates?
QRTs are the standard templates insurers use to report their balance sheet, Own Funds, Solvency Capital Requirement, technical provisions, assets and other data to their supervisor, quarterly and annually.
What is the difference between Solvency II and IFRS 17?
Solvency II is a prudential regime that measures solvency for supervisors. IFRS 17 is an accounting standard that measures insurance contracts for financial statements. They use much of the same data but answer different questions, so their outcomes differ by design.
What is the contractual service margin under IFRS 17?
The CSM is the unearned profit in a group of insurance contracts, recognised in profit or loss as the insurer provides services. Its roll-forward is one of the most examined parts of an IFRS 17 close.
Why do Solvency II and IFRS 17 errors go undetected?
Because most controls test whether figures agree with their sources and move plausibly. An error of treatment, applied consistently, agrees and moves plausibly, so it passes.
What changes with the Solvency II review?
The amended Directive, applying from early 2027, changes parts of the calculation of technical provisions and capital, among other areas. Each change has to be carried through the models, code and spreadsheets that perform those calculations.
How can an insurer prove how a reported outcome was produced?
By connecting the outcome to the process that produced it, across actuarial models, finance systems and manual steps, and running real data through that process to check that it produces the reported outcome.