Integrating an acquired insurer under IFRS 17 is fundamentally a measurement problem before it is an accounting problem. The transaction closes; the policies are now yours; the disclosure clock starts; and the question is whether the CSM, risk adjustment and onerous-contract identification you publish in the next reporting period will survive challenge from your auditor, the PRA and — increasingly — your equity analysts.
The measurement choices that drive the disclosure
Three decisions, made early, that determine almost everything downstream:
- Initial-recognition date for the acquired book. Fair-value-at-acquisition or modified-retrospective? The choice is rarely neutral.
- Discount-rate alignment. If the target used a different yield curve construction, you will be living with the divergence for as long as the legacy cohorts persist on the balance sheet.
- Coverage-unit definition. CSM release patterns hinge on this and inconsistency across legacy and new books triggers audit conversations you do not want.
Operating-model reality
The clean technical answer collides with the dirty operational truth: the target's actuarial system is different, the data lineage is incomplete, the model documentation refers to assumptions no-one in the current team can defend, and the actuarial close calendar is incompatible. Engineering the bridge is where most of the work — and most of the audit risk — sits.
We treat this as a model-risk problem first. Inventory the inherited models, classify them by criticality, decide which migrate and which get re-fitted on group methodology, and run both regimes in parallel for at least one close cycle. The cost of the parallel run is trivial against the cost of an audit re-statement.
What good looks like
The acquired book closes on the group methodology by the second reporting period after deal completion, with a documented methodology bridge for every material assumption change. CSM, RA and onerous-contract walk-forwards are explainable line by line, not just totals-reconcilable. The disclosure narrative tells a story your audit committee can defend without producing a separate technical paper.