Best practices for preparing financial statements under IFRS 17
Preparing financial statements under IFRS 17 requires more than replacing familiar insurance accounting terminology with new labels. The standard changes how insurers measure contracts, recognize profit, present insurance activity, and explain performance to investors. Finance teams must connect actuarial assumptions, policy administration data, general ledger postings, and disclosure processes into one controlled reporting framework.
A reliable approach begins with a clear understanding of the insurance contract portfolio. Groups of contracts must be identified, aggregated, measured, and monitored according to their characteristics and profitability. The resulting figures should be traceable from source systems through actuarial models and subledgers into the statement of financial position, statement of profit or loss, and notes.
The work also has a strong organizational dimension. Accountants, actuaries, technology teams, tax specialists, auditors, and business leaders need shared definitions and agreed timetables. Professional events such as the IASA Conference can help insurance executives and finance professionals compare implementation practices, learn from reporting developments, and evaluate supporting technology.
Establish a controlled reporting foundation
The first best practice is to document the reporting architecture before focusing on individual outputs. This architecture should show how contract data moves from underwriting and policy administration platforms into actuarial valuation engines, IFRS 17 subledgers, consolidation systems, and financial reporting tools. Every major figure should have an identifiable source, transformation rule, owner, and review point.
A formal accounting policy manual is equally important. It should explain the insurer’s approach to contract boundaries, portfolios, groups, coverage units, discount rates, risk adjustment, onerous contracts, reinsurance held, and transition. Policies need to distinguish mandatory requirements from management judgments. When judgments are recorded consistently, financial statement preparation becomes more repeatable and audit discussions become more focused.
Governance should include a reporting calendar that integrates actuarial valuation, close activities, controls testing, management review, and external audit. Late changes to assumptions or data can affect several disclosures at once, so a controlled change-management process is essential. Each adjustment should identify the affected portfolios, financial statement lines, comparative information, and explanatory notes.
Apply measurement models consistently
IFRS 17 measurement starts with the fulfilment cash flows: expected future cash flows, discounting, and the risk adjustment for non-financial risk. For groups measured under the general measurement model, the contractual service margin represents unearned profit and is released as insurance services are provided. The liability for remaining coverage and liability for incurred claims should be reconciled separately so that changes in future service are not confused with claims already incurred.
The premium allocation approach can simplify measurement for eligible short-duration contracts, but it still requires disciplined analysis. Teams must assess eligibility, establish the liability for remaining coverage, determine whether a significant financing component exists, and calculate the liability for incurred claims. A simplified model does not remove the need for sound data, appropriate discounting decisions, or transparent disclosures.
Variable fee approach contracts require particular attention because changes in the entity’s share of the fair value of underlying items can affect the contractual service margin. Reinsurance contracts held also demand separate analysis because their accounting outcomes do not simply mirror the underlying direct insurance contracts. Measurement policies should therefore be documented by portfolio and product type rather than applied as a single broad rule.
| Reporting area | Key preparation practice | Evidence to retain |
|---|---|---|
| Contract grouping | Define portfolios and annual cohorts using documented criteria | Product mapping, profitability analysis, approval records |
| Fulfilment cash flows | Reconcile expected claims, expenses, premiums, and acquisition cash flows | Actuarial files, data extracts, movement analysis |
| Discounting | Apply approved curves and explain changes between periods | Curve governance, methodology papers, sensitivity analysis |
| Risk adjustment | Document the confidence level or other measurement technique | Methodology, calibration results, assumption approvals |
| Contractual service margin | Reconcile opening and closing balances and service release | Roll-forward, coverage-unit analysis, journal support |
| Presentation and disclosure | Separate insurance service result, insurance finance result, and required note information | Disclosure checklist, ledger mapping, review sign-offs |
Strengthen data and actuarial controls
Financial statement quality depends on data quality. IFRS 17 calculations often require information that was not previously captured at the necessary level of detail, including issue dates, expected coverage periods, acquisition cash flows, claims development, product features, and changes in assumptions. A data inventory should identify where each field originates, how it is transformed, and which report uses it.
Reconciliations should operate at multiple levels. Policy counts and premium amounts should agree between administration systems and actuarial extracts. Actuarial cash flows should reconcile to valuation outputs. Subledger balances should tie to the general ledger, while movements in liabilities and the contractual service margin should agree with the notes. These controls are stronger when they use tolerances, exception reports, and documented resolution procedures rather than relying on manual inspection alone.
Assumption governance is another central control area. Discount rates, lapse rates, mortality, morbidity, expenses, claims severity, inflation, and risk adjustment parameters should have named owners and approval thresholds. Changes should be categorized as experience adjustments, assumption updates, model changes, or data corrections. That classification helps determine whether the effect belongs in current service, future service, finance income or expense, or another component of the IFRS 17 accounting model.
Automation can improve speed and consistency, but it should not obscure judgment. System-generated calculations need version control, access restrictions, independent validation, and a clear audit trail. Where spreadsheets remain in use, teams should limit uncontrolled copies, protect formulas, record changes, and establish an independent review. A technically sophisticated platform still produces weak reporting if the underlying process cannot explain how a number was created.
Connect performance reporting with the statements
IFRS 17 changes the relationship between operational activity and reported revenue. Insurance revenue reflects the provision of insurance services during the period, rather than simply the amount of premiums billed or received. Finance teams should therefore create bridges that explain how opening coverage, expected claims and expenses, risk adjustment release, contractual service margin release, and other movements lead to the reported insurance service result.
Separate presentation of insurance service result and insurance finance income or expense should be supported by clear accounting rules. The treatment of discount rate changes, changes in financial assumptions, and the use of other comprehensive income should be consistent with the insurer’s accounting policy and product economics. The choice can affect volatility in profit or loss and equity, so it should be explained to senior management and applied consistently across relevant portfolios.
Management reporting should use measures that complement, rather than contradict, IFRS 17 figures. New business value, embedded value, gross written premium, claims ratios, and operating metrics may remain useful, but their definitions and relationship to the statutory statements should be clear. A reporting pack can include a bridge from internal performance measures to IFRS 17 results, helping executives interpret the effect of coverage periods, cohorting, discounting, and service release.
This alignment also supports investor communication. Analysts need to understand why profitable new business may initially increase the contractual service margin, why loss-making groups can create immediate expense, and why changes in estimates can affect current results differently depending on the remaining service. Consistent explanations reduce the risk that technically correct figures are misunderstood.
Design transparent disclosures and comparatives
The notes to the financial statements should be designed early, not assembled after the primary statements are complete. IFRS 17 disclosures require information about recognized amounts, significant judgments, changes in fulfilment cash flows, contractual service margin movements, risk exposure, and the nature and extent of insurance risks. Building a disclosure catalogue helps map every requirement to a data source, calculation, responsible owner, and review procedure.
Roll-forward tables deserve special attention. They should explain opening and closing balances for insurance contract liabilities and assets, separating components such as the liability for remaining coverage, liability for incurred claims, and contractual service margin where required. Movements should be labeled in language that connects accounting mechanics to business activity, including new contracts, services provided, claims incurred, cash flows, and changes in assumptions.
Risk disclosures should be specific to the insurer’s exposures. Generic statements about underwriting, market, credit, liquidity, and operational risk are less useful than analyses showing concentration, sensitivity, claims development, and how risk management practices affect the reported amounts. The information should agree with internal risk reports while preserving the distinction between financial reporting requirements and regulatory solvency disclosures.
Comparative information and transition disclosures also require careful planning. Teams should document whether contracts were measured using the full retrospective approach, modified retrospective approach, or fair value approach, and explain the judgments applied when historical data was incomplete. Transition balances should reconcile to opening equity and provide enough detail for users to understand how prior reporting has been reshaped.
Build a review process that withstands scrutiny
A strong close process uses layered review. Preparers should perform completeness and reasonableness checks, subject-matter specialists should review actuarial and accounting judgments, and finance leadership should assess the overall story presented by the statements. Internal audit or an independent control function can test whether key controls operated as designed throughout the reporting period.
Analytical review should go beyond comparing current-period totals with prior periods. Teams should investigate changes in coverage units, loss ratios, claim development, contractual service margin release, risk adjustment, discount rates, and product mix. Variance thresholds should be tailored to the portfolio, since a small percentage change in a large long-tail book may be more significant than a larger movement in a small product line.
External audit engagement is more efficient when evidence is prepared continuously. Methodology papers, model validation reports, data reconciliations, control testing, assumption approvals, and disclosure support should be organized in a central repository. Audit trails should show who prepared, reviewed, approved, and changed each significant item. This approach reduces repeated requests during the reporting timetable.
Senior management should review the statements as a connected package. The balance sheet, profit or loss, cash flow information, equity movements, and notes should tell a consistent story. If the contractual service margin increases while the explanation suggests deteriorating profitability, or if risk disclosures do not align with observed claims trends, the inconsistency should be investigated before publication.
Practical priorities for finance and accounting teams
The most effective preparation programs focus on repeatability rather than a one-time implementation milestone. Teams should monitor close duration, unresolved data exceptions, manual journal volume, model changes, audit adjustments, and disclosure production time. These indicators reveal whether the reporting process is becoming stable or whether it remains dependent on individual expertise and late intervention.
Recommended priorities include:
- Maintain a single controlled inventory of IFRS 17 accounting policies, judgments, models, data sources, and disclosure requirements.
- Reconcile policy administration, actuarial, subledger, and general ledger data at every reporting cycle.
- Separate current-service, future-service, finance, and experience effects in movement analyses and journal support.
- Test contractual service margin release and coverage units against the actual pattern of insurance service.
- Review disclosures alongside the primary statements so that narrative, tables, and reported balances remain consistent.
The value of these practices extends beyond compliance. A well-controlled IFRS 17 process can improve product profitability analysis, support pricing decisions, reveal data weaknesses, and create a more useful view of how insurance services generate earnings over time. It can also make collaboration between finance, actuarial, technology, and operations teams more structured.
Executives and emerging leaders who understand both the technical standard and the operating model will be better positioned to guide future reporting changes. Use the next reporting cycle to test one portfolio end to end, document every handoff, resolve the largest control gaps, and turn the resulting lessons into a repeatable group-wide process.