RESEARCH DOSSIER
Reconciliation of Accounting and Prudential Insurance Data
Abstract. An insurance undertaking produces several authoritative descriptions of its financial condition from overlapping contracts, cash flows, assets, claims, and policyholder obligations. General-ledger balances, general-purpose financial statements, actuarial valuation engines, statutory returns, and prudential solvency reports have different recognition rules, aggregation levels, valuation purposes, and reporting timetables. The central research problem is how to establish a verifiable relationship between those representations without treating equality of unlike figures as a necessary condition of reconciliation. This monograph examines the relationship through documentary analysis of IFRS 17, IFRS 9, European Solvency II legislation and reporting instruments, International Association of Insurance Supervisors principles, United States statutory accounting, and targeted improvements to U.S. long-duration insurance accounting. It integrates official implementation evidence, selected actuarial scholarship, and transparent hypothetical calculations. The analysis distinguishes five operations: identifying the same underlying economic item; aligning entities, dates, currencies, and contract populations; reproducing each reporting basis from controlled source data; quantitatively explaining legitimate changes of measurement and presentation; and demonstrating that residual differences are investigated, documented, and resolved. A reconciliation is therefore evaluated by its supported transformations and the completeness of its audit trail. IFRS 17's required movements in insurance contract balances and Solvency II's comparison of material valuation differences serve different disclosure purposes; an internal bridge must preserve both. The European Insurance and Occupational Pensions Authority's empirical implementation study substantiates the materiality of discounting, risk adjustment, contractual service margin, boundaries, and expense allocation, while its sample constraints prevent treating reported group averages as general calibration parameters. Worked illustrations reconstruct a financial-to-prudential technical-provision bridge, an asset admissibility and capital reconciliation, and a closing-to-opening movement with independently checked arithmetic. A reproducible control inventory links each adjustment to governing requirements, input data, methodology, approval, and version. The study finds that strong reconciliation combines contractual identity with reporting-basis specificity, treats residual amounts as classified exceptions, and maintains separate evidence for operational agreement, valuation judgment, and supervisory filing. These findings are analytical applications of established accounting, actuarial, and supervisory principles; they do not introduce a new named theory or claim empirical validation from synthetic cases.
Keywords: Insurance accounting; prudential reporting; financial reconciliation; IFRS 17; Solvency II; statutory accounting principles; NAIC; ASC 944; technical provisions; contractual service margin; risk adjustment; risk margin; general ledger; audit trail; supervisory taxonomy; data provenance; insurance solvency; insurance reporting controls.
Introduction
Accounting–prudential reconciliation begins with a deceptively simple observation: an insurer can have one insurance contract and more than one correct reported value for its obligations. The contract generates economic exposures and contractual rights, the ledger records accounting transactions, the financial reporting system recognizes and measures those rights and obligations under an adopted financial reporting framework, and the prudential regime converts relevant exposure into supervisory valuations and capital resources. Each value is meaningful only in relation to its reporting basis, reporting entity, valuation date, and reporting perimeter. The analytical task is to establish the documented sequence that connects them.
In the European context, the International Accounting Standards Board's IFRS 17 insurance contract framework requires current estimates of fulfillment cash flows, explicit consideration of nonfinancial risk, and recognition of unearned profit through a contractual service margin for applicable groups. Solvency II's valuation and technical-provision rules evaluate assets and obligations for policyholder protection and supervisory solvency. These rules can share policy, claims, and investment data while producing different amounts. The distinction is institutional as well as numerical: financial statements describe general-purpose financial performance, while prudential returns facilitate supervision of the insurer's ability to meet its commitments.
The need for an explicit bridge is embedded in supervisory disclosure. Under Article 296 of Delegated Regulation (EU) 2015/35, the Solvency and Financial Condition Report must include quantitative and qualitative explanations of material differences between solvency valuation and financial statements for assets, technical provisions, and other liabilities. The provision does not require every figure to coincide. It calls for enough information to explain why valuations diverge. Reconciliation consequently means more than tracing a total from one column to another; it identifies the cause, legitimacy, completeness, and timing of differences.
The EIOPA implementation study of April 2024 provides empirical context. The authority analyzed first-application information from 53 insurance or reinsurance groups in 17 participating Member States, drawn from June 2023 semiannual reporting. It documented both significant methodological synergies and differences concerning contract boundaries, discount rates, risk adjustments, contractual service margins, and allocation of expenses. EIOPA expressly treated the data as informative about orders of magnitude and choices rather than precise population estimates: the sample was limited, interim reports were unaudited, and some responses were best-effort. This monograph therefore uses that study to identify mechanisms, while avoiding the transplantation of its summary percentages into entity-specific reconciliation formulas.
International comparison requires additional distinctions. The NAIC statutory accounting framework focuses on insurer solvency, the availability of assets, conservative recognition, and consistency while respecting state prescribed and permitted practices. U.S. general-purpose reporting under FASB Topic 944, including the 2018 long-duration insurance amendments, is a distinct accounting basis. No universal numerical conversion can replace identification of the actual accounting regimes. The IAIS Insurance Core Principles supply a global supervisory perspective: financial and regulatory valuations should be as consistent as their different purposes permit, and material differences should be explained.
Research questions and object
The first question is how accounting and supervisory data sets can be proven to represent the same contracts, exposures, claims, and assets at a defined observation time. The second is how adjustments arising from measurement, recognition, aggregation, presentation, and national reporting requirements can be reconstructed rather than merely assigned to a residual balancing category. The third is how an insurer can preserve reproducible evidence when valuations depend on models, changing assumptions, regulatory taxonomies, and reporting revisions. A related interpretive question asks whether better agreement between totals always implies greater data quality. The analysis answers in the negative: an unexplained coincidence can be weaker evidence than a documented and authorized difference.
The object of study is the end-to-end bridge from operational records and the general ledger to financial statements and supervisory schedules. The scientific boundary is operational reconciliation and control. Detailed derivation of financial valuation theories belongs to the separate dossier on accounting and prudential valuation differences; this study explains enough measurement mechanics to make bridges auditable. It also separates movement reconciliation within a reporting basis from cross-basis reconciliation at a single reporting date. Both can be required, and neither substitutes for the other.
Sources, methods, and limitations
The research uses primary standard-setter and regulator publications; current public descriptions of accounting and prudential requirements; the EU legal text; official reporting and taxonomy documentation; a regulator's published empirical implementation study; and selected peer-reviewed actuarial work on reserve uncertainty. Methods comprise structured comparative reading, classification of reconciling dimensions, elementary accounting identities, analytical construction of hypothetical cases, and source-to-claim review. The worked tables are explicitly synthetic and use monetary units rather than real insurer records. They demonstrate internal consistency, not the statutory accuracy of a particular filing.
Every legal assertion is bounded by jurisdiction and date. The updated EIOPA supervisory requirements describe a substantial Solvency II reporting transition associated with January 30, 2027. A 2026 reporting bridge and a 2027 reporting bridge must use their respective effective taxonomies and supervisory instructions. IFRS 18 is generally effective for annual periods beginning on or after January 1, 2027, subject to the entity's actual adoption circumstances; its presentation and disclosure changes also require version-aware mapping. United States state requirements, legal entity filing obligations, and group consolidation must likewise be assessed separately.
Accounting and Supervisory Data Perimeters
Economic population, legal entity, and reporting basis
A data perimeter identifies which items are included before values are calculated. In insurance, relevant populations include policy systems, claims systems, ceded and assumed reinsurance, investment subledgers, recoverable balances, expenses, and tax accounts. The same insurance group may prepare consolidated IFRS financial statements, separate legal-entity statutory returns, and group or solo prudential reports. A direct comparison of these published totals without deconsolidation and scope alignment can create false differences. Reconciliation first defines the tuple: reporting entity, consolidation boundary, reference date, currency, accounting basis, prudential basis, contract set, and measure.
Consider a group with two insurance subsidiaries and a noninsurance services company. Group financial statements include the service company and eliminate intragroup transactions. A solo insurance supervisory return covers one licensed undertaking, may include related-party exposures subject to specific supervisory valuation, and may eliminate or retain balances under different rules. The controlled bridge first isolates the licensed company from the consolidated group, reinstates or removes appropriate intercompany balances, and then applies prudential valuation. Without this operation, every later valuation difference contains an unidentified perimeter component. The direction of each adjustment must therefore be explicit.
IAIS guidance on supervisory reporting recognizes the role of quantitative and qualitative information and comparability. Its ICP 9 addresses reporting and supervisory review; ICP 14 addresses asset and liability valuation; ICP 17 addresses capital adequacy. These principles point to an important operational distinction: a regulator may receive confidential granular data in addition to public statements. An external reader can reconstruct only the subset published in financial statements and the Solvency and Financial Condition Report, whereas a controlled internal reconciliation can track the complete bridge.
Contract boundaries and insurance risk
A product identifier is not a sufficient cross-framework contract key. Accounting and supervisory assessments may differ in recognition timing, contract boundaries, treatment of extensions and options, and whether features fall within the insurance measurement unit. Under the IFRS 17 identification and grouping requirements, contracts are analyzed for significant insurance risk and grouped according to the standard's requirements. Solvency II technical provisions cover obligations as defined by its rules and may require different contract-boundary assessment. A reconciliation table needs the legal policy identifier and the analytical representation used by each regime.
A single life contract may appear as one administrative policy, contribute to a cohort-specific accounting group, and occupy a line-of-business segment for prudential valuation. A one-to-many mapping is normal. The ability to reverse the transformation matters: an auditor should be able to identify which underlying contracts contribute to each material accounting group and supervisory segment, including cancellations, transfers, and reinsurance features. Many-to-many mappings require a documented allocation key and consistent treatment of ambiguous cases.
The EIOPA comparison of IFRS 17 and Solvency II confirms that differences in scope, contract boundary, and recognition are substantive sources of divergence. The appropriate operational response is to calculate a defined perimeter adjustment, measured on a consistent valuation basis where feasible, before interpreting the remaining variance as a valuation effect. A difference that arises because different contracts were included has a different meaning from one that arises because the same projected cash flows were discounted at different rates.
Financial ledger, actuarial engine, and supervisory data
The general ledger commonly organizes postings by accounts, transaction dates, legal entities, currencies, and accounting periods. Actuarial systems organize projected premiums, claims, benefits, lapses, expenses, and recoveries by policy and risk characteristics. Supervisory data models may require reporting dimensions with no one-to-one ledger account, such as line of business, claim duration, geography, exposure type, or maturity. A reliable bridge retains these data origins rather than forcibly standardizing every item into a single table before verification.
The EIOPA supervisory reporting portal identifies implementing technical standards for supervisory templates, including Regulation (EU) 2023/894 as applicable from the 2023 reporting transition and the associated public-disclosure instrument. The reporting process thus has an independent regulatory schema and submission obligation. A ledger trial balance that balances correctly can still produce an incomplete supervisory return if mandatory dimensions are missing or a model output uses the wrong taxonomy version.
The insurance DPM and XBRL documentation illustrates the continuing importance of versioned data definitions, validation rules, and digital taxonomies. Data Point Model identifiers and template cells are reporting coordinates, not permanent semantic identities across regulatory revisions. A mapping should record the taxonomy version, submission reference period, filing cell, and the underlying economic concept separately. This becomes particularly important when an old template is retired and the same economic exposure is subsequently reported through a revised structure.
Cutoff, effective dating, and comparative periods
A report may incorporate transactions booked after the economic event but before the reporting close, late-reported claims, retroactive policy changes, model calibrations approved after period-end, or subsequent adjustments processed in a separate run. The reconciliation must therefore differentiate effective date, posting date, extraction date, valuation date, and submission date. Those dates answer different questions. A reserve can be economically attributable to year-end while its actuarial calculation was finalized during the following month; the documentation must show which information was known and authorized at the reporting cutoff.
This analysis favors an explicit period bridge: opening balance, recognized inflows and outflows, remeasurement movements, foreign-exchange effects, reclassifications, portfolio transactions, and closing balance. An additional after-close adjustment log links late changes back to the period they affect. Reconciliation should be reproducible both as originally submitted and as subsequently corrected. Replacing old data silently can make an apparently current number impossible to audit historically.
Materiality, coverage, and exception priority
Materiality is a reporting and assurance judgment; it does not imply that immaterial items may lack identity or data lineage. A bridge must cover the full population and may apply different investigation thresholds based on potential effects on assets, liabilities, available capital, or disclosures. The exception log should preserve every unmatched item with status, cause, affected reporting bases, period, owner, and disposition. A net-zero exception group can contain individually significant offsetting errors. Completeness must therefore be assessed in gross and net terms.
A balanced trial balance is evidence about double-entry totals, not proof that policy coverage and actuarial valuations are complete. Similarly, a total financial-to-prudential bridge may reconcile numerically while individual lines of business are wrongly mapped. The correct conclusion from aggregate agreement is limited: a defined total equals the sum of specified components. Stronger conclusions require reconciliations at materially relevant sublevels and sample-based or full-population controls over underlying source identities.
Contract and Asset Mapping
Identity before valuation
Mapping begins with stable identifiers for economic rights and obligations. A contract crosswalk should preserve insurer legal entity, policy identifier, insured risk, issuance and coverage dates, contract amendment history, IFRS accounting group, Solvency II line of business, reinsurance treaty or section, and relevant statutory reporting category. A separate claim crosswalk must distinguish the claim event, claim version, settlement transaction, outstanding reserve, and subrogation or reinsurance recovery. Multiplying a claim reserve by the number of claims-system status rows is a classic form of data duplication; the valid accounting measure is tied to one approved valuation of the obligation at the reference date.
An insurer's financial accounts also distinguish direct obligations from reinsurance assets. Under IFRS 17, reinsurance contracts held are measured and presented as a separate population, with their own relevant requirements. Under Solvency II Article 77, the best estimate of technical provisions is calculated gross, while reinsurance recoverables are calculated separately under the applicable rules. A reconciliation that nets reinsurance into gross technical provisions and then compares the result with an IFRS net contract position creates a definitional error before any measurement difference has been assessed.
Mapping by contract characteristics
The crosswalk should establish how contract boundaries, accounting groups, lines of business, and the reporting entity are derived. Insurance product names are insufficient because a named product can include several riders, embedded features, or categories of insurance risk. An explicit rule-based classification is preferable to a mapping inferred from the most common historical practice. When judgment affects classification, the rule and approval must be versioned and connected to the underlying contract attributes.
An effective contract-control total includes at least an independently reconstructed count of unique in-scope contract identifiers, a count of mapped reporting units, and a statement of excluded and partially mapped items. Counts may legitimately change as data is aggregated; the reconciliation should show the mapping cardinalities and explain duplicates arising from decomposition. A financial accounting portfolio is not assumed to equal a supervisory line of business. The link is documented through the underlying contracts and their basis-specific grouping rules.
Investment assets and financial instruments
Asset reconciliation crosses another boundary: an investment security may be measured under IFRS 9, presented within a consolidated financial statement, classified in a prudential investment inventory, and treated in solvency own-funds analysis. The IFRS 9 measurement categories depend on the relevant business model and contractual cash-flow characteristics. Prudential regimes may apply a different valuation or recognize a different eligibility or concentration treatment. The crosswalk consequently needs instrument identifiers, lot positions, accounting classification, currency, fair-value sources, valuation hierarchy where relevant, and encumbrance status.
Reconciliation of investments begins with positions before prices. Quantity and nominal amount should agree between custody, investment subledger, ledger, and the reporting inventory for the same entity and cutoff, after independently identified settlement timing adjustments. The second comparison concerns valuation—amortized cost, fair value, currency conversion, accrued interest, and model-based prices. Combining quantity errors with price differences into one aggregate unexplained balance hides their remedies. The asset ledger should retain the instrument-level decompositions through reporting aggregation.
For U.S. statutory accounting, the NAIC discussion of admitted assets explains why an economic asset recognized for general-purpose accounting may be excluded from statutory admitted assets if it is not available to satisfy policyholder obligations. A nonadmitted-asset adjustment is a recognition and statutory-surplus item; it should not be represented as an investment pricing discrepancy. Distinct columns are necessary for asset existence, valuation, admission, and capital treatment.
Ceded reinsurance and recoverability
Reinsurance adds multiple identifiers: original insurance contract, assumed or ceded treaty, layer, counterparty, settlement account, and claim recovery. A gross-to-net reconciliation must distinguish contractual risk transfer, actuarial recoverable, recognized receivable, cash settlement, and counterparty collectibility. Recoverables and collateral are related but not identical measures. The mapping also identifies whether a reinsurance asset appears as a separate financial reporting balance, a supervisory recoverable, or a credit-risk exposure used in capital assessment.
An analytical example illustrates the danger of conflation. Suppose a direct claim provision of 160 and an expected ceded recovery of 45 are independently supported. The gross provision remains 160 on the relevant gross basis; the expected net economic exposure is 115 before other risk, discounting, or recoverability effects. If the accounting return presents a net figure of 115 and the supervisory return presents gross obligations of 160 and recoverables of 45 separately, their information can be reconciled without changing the underlying claim. The difference of 45 belongs to presentation and gross/net structure, not to a reserve-development assumption.
Entity, currency, and group mapping
Group reconciliation also needs ownership percentages, consolidation and elimination rules, functional and presentation currencies, and supervisory group inclusion. A reserve calculated in local currency must carry its original unit and conversion rate through all layers. Translation movements should be separately measured from underlying insurance-service and actuarial movements. A reporting group may have a solvency perimeter different from its financial consolidation perimeter; that is a structural difference requiring explicit scope and ownership adjustments.
The central operational judgment is that a mapped item must be reproducible in both directions. Starting from a supervisory line, an examiner should find the underlying asset, policy or claim population, valuation run, and financial source; starting from a financial account, the same examiner should find its prudential treatment or a documented exclusion. A one-way summary table is a useful presentation but is weaker evidence of completeness than a crosswalk that accounts for every eligible source record.
Valuation Bridge Schedules
Structure of a basis-to-basis bridge
Once the reporting population is aligned, the valuation bridge explains why amounts assigned to the same economic obligations differ. A properly specified bridge keeps four layers visible: the amount under the first basis, the population and presentation changes necessary for comparison, the effects attributable to different measurement methods, and the amount under the second basis. The bridge is a reproducible computation accompanied by evidence about each adjustment. Its value extends beyond the fact that two endpoints can be made to agree.
The accounting starting point depends on the IFRS 17 measurement approach. Under the general model, fulfillment cash flows incorporate expected future cash flows, discounting and an explicit adjustment for nonfinancial risk; a contractual service margin ordinarily represents unearned profit for non-onerous groups. Under the premium allocation approach, the liability for remaining coverage has a different measurement structure. Insurance contracts issued, reinsurance contracts held, remaining coverage, and incurred claims also need distinct presentation. These requirements are explained by the IFRS 17 measurement framework. An all-purpose one-line liability formula cannot adequately describe every accounting portfolio.
For Solvency II, the best estimate is a probability-weighted present value of future cash flows, calculated using the relevant risk-free interest-rate term structure; technical provisions ordinarily combine the best estimate and a risk margin under Articles 76 and 77. The IFRS adjustment for nonfinancial risk and the prudential risk margin are separately defined requirements. Their conceptual proximity does not establish numerical equality. The IFRS contractual service margin has no direct Solvency II counterpart. The primary bridge should separately identify CSM instead of treating it as a prudential reserve error.
Worked insurance-liability bridge
The following values are synthetic and internally consistent, representing one aligned portfolio at one reporting date. Amounts are in millions of hypothetical currency units. An illustrative IFRS 17 liability is 1,120: projected discounted fulfillment cash flows of 920, an adjustment for nonfinancial risk of 70, and contractual service margin of 130. This example assumes that the selected balance is meaningfully comparable before the stated adjustments and that reinsurance-held positions are reported independently. Its Solvency II technical provision is 1,025: best estimate of 960 and risk margin of 65.
| Reconciliation step | Signed adjustment | Running amount |
|---|---|---|
| IFRS 17 insurance liability | — | 1,120 |
| Remove contractual service margin | −130 | 990 |
| Align contract boundary and reporting population | +25 | 1,015 |
| Align discount-rate methodology | +18 | 1,033 |
| Align expense and claim cash-flow scope | −12 | 1,021 |
| Align other expected cash-flow assumptions | +9 | 1,030 |
| Replace IFRS risk adjustment of 70 by prudential risk margin of 65 | −5 | 1,025 |
| Solvency II technical provision | — | 1,025 |
The independent identities are 1,120 = 920 + 70 + 130; 960 = 920 + 25 + 18 − 12 + 9; and 1,025 = 960 + 65. The direct difference is 1,025 − 1,120 = −95. The adjustment sum is −130 + 25 + 18 − 12 + 9 − 5 = −95. The calculated equality provides an exact check of this example. No amounts are offered as calibrated regulatory inputs, observations about insurers, or required percentage adjustments.
The order of adjustments must be controlled. A contract-boundary adjustment calculated under an accounting discount curve can differ from the same population adjustment calculated under the prudential curve. The bridge therefore needs a specified order of transformations and attribution of interactions. When the interaction is material, it should be disclosed as an identified component or allocated under a declared methodology. A zero final residual cannot establish the causal accuracy of an arbitrary decomposition.
The +25 scope adjustment requires a list of included and excluded contracts or cash flows. The +18 discounting adjustment requires both curve versions, projected cash flows, and a controlled revaluation of the same population. The −12 expense change requires an expense allocation record, and the +9 assumption item requires an approved comparison of the underlying projection runs. The −5 margin adjustment requires independent identification of the two risk measures. Each bridge line is supported by a traceable object; unexplained miscellaneous adjustments are classified as exceptions, not buried within modeling changes.
Interest-rate sensitivity and valuation attribution
A discounted valuation changes with cash-flow sign, timing, and the selected discount rate. For cash flows CF at periods t, a simplified constant-rate expression is PV(r) = sum of CF_t/(1+r)^t. Actual frameworks apply their own curve construction, risk treatment, term structure, currency-specific requirements, and insurance contract assumptions. The simplified relationship explains why one common source-data set can produce different reported liabilities without implying a contradiction.
The EIOPA IFRS 17 implementation report documents that many respondents used the supervisory risk-free curve as an input to IFRS 17 discounting, even when final accounting discount rates differed. An apparently shared curve is thus only one component of the valuation bridge. The reconciliation should identify curve construction, liquidity or matching adjustments when relevant, and the effect of cash-flow timing. It should not equate common reference inputs with identical final values.
A certain cash outflow of 100 payable one year from now has a present value of approximately 95.2381 when discounted at 5 percent and 94.3396 at 6 percent. The change is approximately −0.8985. The case omits insurance uncertainty and other risk adjustments, and its arithmetic can be reproduced directly from 100/1.05 and 100/1.06. The point is sensitivity direction. For a long-duration insurance portfolio the magnitude depends on the entire projected cash-flow pattern.
From balance-sheet bridge to own-funds analysis
An accounting-to-prudential insurance-liability bridge does not by itself reconcile equity to prudential own funds. Asset valuation, different treatment of intangible assets, deferred taxes, other liabilities, capital instruments, and regulatory eligibility constraints may affect the result. Solvency II excess of assets over liabilities is conceptually distinct from eligible own funds after all applicable supervisory adjustments. The prudential balance-sheet rules therefore require a full balance-sheet perspective.
Consider another synthetic comparative balance sheet, in the same hypothetical monetary units.
| Defined component | IFRS basis | Prudential basis | Change |
|---|---|---|---|
| Assets | 1,500 | 1,465 | −35 |
| Insurance obligations | 1,120 | 1,025 | −95 |
| Other liabilities | 70 | 90 | +20 |
| Equity or excess of assets over liabilities | 310 | 350 | +40 |
The financial identity is 1,500 − 1,120 − 70 = 310. The prudential identity is 1,465 − 1,025 − 90 = 350. Changes in net assets reconcile as −35 − (−95) − 20 = +40. The prudential 350 is deliberately identified as excess of assets over liabilities; no inference that it equals eligible regulatory own funds or a solvency ratio is warranted without additional eligibility and capital requirements.
The −35 asset change could be decomposed hypothetically into +20 investment revaluation, −35 recognition adjustment, and −20 a documented perimeter change. These changes sum to −35. The example does not import the U.S. statutory concept of admitted assets into the EU Solvency II framework. A supervisor-specific exclusion or recognition adjustment requires its own jurisdictional authority. The NAIC statutory admissibility approach is relevant to the separate U.S. comparison; the legal basis of each adjustment must be independently identified.
Analytical classification of reconciling differences
A practical reconciliation matrix classifies differences by population, recognition, measurement, presentation, currency, reporting time, and capital eligibility; a parallel classification identifies the affected financial object. This is a transparent arrangement of established accounting and supervisory concepts, not a new scientific model. It facilitates a reviewer asking both why a difference exists and which reported object is affected.
Each line needs the first-basis amount, transformation, target-basis amount, reason, numerical evidence, controlling standard or rule, approval, and stable input version. Each endpoint must tie independently to its actual statement. The bridge then explains two independently controlled results rather than manufacturing either endpoint from the other. Material offsetting errors become visible when adjustments retain their separate categories and signs.
Adjustment and Reserve Reconciliation
Point-in-time bridges and longitudinal movements
A cross-sectional bridge reconciles financial and prudential measurements at a specified date. A longitudinal roll-forward explains movement under one reporting basis between two dates. Both are necessary in a closed reporting cycle. The first addresses differences among frameworks; the second explains additions, payments, remeasurements, and other changes. Neither proof automatically entails the other.
IFRS 17 requires disclosures connecting opening and closing contract balances, including cash flows and recognized income or expenses. The IFRS taxonomy reconciliation examples explicitly concern IFRS 17 paragraphs 100, 101, and 106. Distinctions among remaining coverage, incurred claims, loss components, fulfillment cash flows, risk adjustment, and CSM are necessary when the respective requirements apply. An internal ledger roll-forward of one total is not a replacement for those financial-statement disclosures.
Solvency II forms have their own reporting schemas and dimensions. Commission Implementing Regulation (EU) 2023/894 governs reporting templates in its period of application. The same economic event may affect an IFRS reconciliation line and a prudential template cell differently, including cases where an IFRS movement is omitted from a particular supervisory format. The mapping must preserve the actual obligations of both regimes rather than constructing artificial one-for-one equivalence between line items.
Worked claim-liability roll-forward
This illustration uses a simplified gross claim reserve within one chosen basis; it is not an actual IFRS 17 disclosure or Solvency II filing. All amounts are hypothetical millions. Opening reserve is 240, new obligations add 90, development of outstanding claims adds 18, an illustrative finance movement adds 5, claims payments remove 65, and a translation effect removes 3.
| Movement | Signed effect | Running balance |
|---|---|---|
| Opening claim reserve | — | 240 |
| Newly incurred claims | +90 | 330 |
| Prior claim reserve development | +18 | 348 |
| Finance accretion illustration | +5 | 353 |
| Claims paid | −65 | 288 |
| Currency translation | −3 | 285 |
| Closing claim reserve | — | 285 |
The identity is 240 + 90 + 18 + 5 − 65 − 3 = 285. If the claim subledger shows 283 and the ledger shows 285, the residual of 2 is an unresolved exception pending investigation. Possible causes include cutoff mismatches, missing claims, double-counted versions, valuation-run mismatches, or unposted journals. Correct arithmetic alone cannot establish which cause occurred.
For a separate hypothetical reinsurance recoverable, opening amount 70, an increase from reassessment of 12, and recoveries received of 8 produce a closing amount of 74. The identity is 70 + 12 − 8 = 74. The difference between closing gross reserve 285 and recovery 74 gives an indicative net exposure of 211 before any other distinct financial measurement differences; it must not be substituted for required separate gross and ceded presentations. Reconciliation requires both streams and their own documentary evidence.
Reserve uncertainty and limits of balancing
A perfectly reconciling reserve can still be economically misestimated. Claim development, inflation, reporting delay, settlement behavior, reinsurance recoverability, and portfolio change affect projections. The scholarly study by England and Verrall (2002) addresses stochastic reserve models and predictive uncertainty. Mack's 1993 reserve-error study derives an error measure for the chain-ladder method under its assumptions. These sources explain the distinct need for actuarial validation.
Reconciliation can establish that an approved model result was transported faithfully into the reporting system and that the recorded movement was accounted for. It does not establish sufficiency of IBNR, realism of mortality assumptions, adequacy of tail estimation, or the appropriateness of a risk margin. Those questions require independent actuarial and regulatory analysis. The difference between correct transmission and correct estimation is especially important when management interprets absence of ledger exceptions as a verdict on liability adequacy.
CSM, claims development, and changes in estimates
Accounting for changed estimates under IFRS 17 depends on service timing, the applicable measurement approach, and whether an adjustment relates to future, current, or past service. The IFRS 17 accounting requirements treat the contractual service margin as the unearned profit component of relevant contract groups. A CSM movement is not automatically identical to a cash-flow change, nor is it a Solvency II risk-margin movement. These distinctions require appropriate mapping to profit or loss, CSM, and finance income or expenses.
Suppose an actuarial valuation run produces separate changes from unwinding of discounting, revision to future benefits, claims incurred this period, updates to historical claims, and release from risk. Posting one net amount to the ledger can preserve a grand total while obscuring the accounting determination of where each component belongs. Reconciliation reconstructs the original causes and their reporting treatment. Any simplification of journal entries should preserve access to a controlled analytical decomposition.
Corrections, restatements, and after-close data
Reporting cutoff problems arise when claims are reported late, contracts are backdated, reinsurance recoverability is revised, or top-side adjustments are posted after the actuarial snapshot. The reconciliation register needs the economic effective date, system-entry date, journal posting date, valuation-run date, and the date on which a filing was approved or amended. These timestamps must remain distinguishable. A prior-period correction, a current-period remeasurement, and a change in submission status have different reporting implications.
For example, a second reserve run may reveal omitted claims and increase the required reserve by 7. An auditable investigation preserves the old input snapshot, the new one, the newly included claim IDs, the 7 increase, and the associated approval. If a financial close is reopened, both accounting and prudential bridges should be recalculated for the approved version. If a previous supervisory filing remains effective, the evidence must preserve its contents and any later correction or replacement. Silent overwriting makes historical reconciliation impossible.
Movement reconciliation across operational systems
Claim payments should be traceable across claims administration, approved payment orders, bank confirmation, subledger, and general ledger, subject to explicitly documented timing and currency effects. Premium flows should be connected across policy billing, intermediaries, collections, cash allocation, and accounting recognition. Reinsurance settlements require a comparable sequence from treaty eligibility to expected recovery, booked receivable, and collected payment. These relationships uncover operational lag separately from reserve measurement.
The general movement identity can be expressed in words as closing balance equals opening balance plus recognized increases minus recognized decreases under the basis-specific sign rules. A zero arithmetic residual proves only that recorded movement components sum to their recorded ending amount. Completeness, correct classification, and economic validity require other controls. A sound data reconciliation combines these proofs instead of conflating them.
Control and Audit Evidence
The evidence chain of a reconciled amount
A reconciled amount becomes trustworthy through the ability to reproduce its origin, meaning, transformation, and approval. An insurer's reporting architecture normally combines transaction-processing controls, accounting controls, actuarial model governance, investment valuation oversight, and supervisory reporting controls. Each addresses a different failure mode. Source validation tests whether relevant transactions and contract attributes were correctly captured; ledger controls test posting and classification; actuarial review tests assumptions and estimation; report preparation controls test aggregation and disclosures. The output of one control must be connected to the next.
The IAIS online Insurance Core Principles address the reliability and transparency of solvency valuation. Revised ICP 14 emphasizes that financial and supervisory methodologies should be consistent where appropriate, and that differences in data, discount rates, methods, and assumptions should be explained. The broader implication for an operational bridge is direct: explanation needs evidence about the process that created a difference. A narrative label such as 'regulatory adjustment' is not an adequate description of a material difference unless its source and computation can be established.
For each material reconciliation adjustment, a minimal evidence record should identify the reporting entity, period, basis, target disclosure, source dataset and version, extraction criteria, transformation logic, underlying standard or regulator instruction, calculation output, preparer, reviewer, approval date, and exception disposition. Where a spreadsheet is part of the process, the evidence should include the stored version or equivalent reproducible source, not merely a screenshot of the ending cell. A controlled audit trail distinguishes a calculation that was performed, a calculation that was reviewed, and a calculation that was subsequently adopted for filing.
Source completeness and independent controls
Data completeness begins before valuation. A count of active policy records reconciles to the administration population only after relevant exclusions, cancellations, and amendments have been identified. The corresponding premium and claims amounts reconcile through their transaction paths. The investment inventory should be matched against controlled custody or asset-management records, with timing differences isolated. Where an insurer relies on several source systems, a unique identifier and clear effective-date convention reduce the risk that a single contract or payment appears in more than one extract.
A strong control tests both completeness and uniqueness. If policy identifiers are duplicated because of legitimate coverage components, a control should count the legal policies and analytical components separately. If a claim appears in multiple historical status records, the process should identify the approved reporting-date version before aggregation. Duplicate removal without an economic identity test may delete valid components. Similarly, aggregation cannot be validated solely by adding values when currency, entity, or contract boundary are inconsistent.
A reconciliation should preserve positive and negative exceptions rather than net them before investigation. Consider two offsetting misclassifications: a 6 liability omitted from one business line and a 6 liability duplicated in another. The total remains unchanged, while both segment disclosures are wrong. Reviewers should therefore test gross exceptions, line-of-business consistency, and mapped populations. Control thresholds should be tied to the materiality of the reporting line and potential prudential effect, with separate escalation for high-risk legal or capital classifications even when amounts are small.
Evidence for actuarial valuations
Actuarial outputs typically depend on assumption tables, projection software, claim triangles, model settings, management overlays, and approval decisions. Reconciliation must connect the number booked in the ledger to one controlled output, and the amount in the supervisory return to the correct prudential calculation. The model inventory and run identifier should record methodology, currency, valuation date, input-data timestamp, software version, assumption set, approval, and actual output. A manual reserve adjustment must be separately signed and supported.
The scholarly literature on stochastic reserving and prediction error establishes why a modeled reserve carries estimation uncertainty in addition to data-processing risk. A financial-to-prudential bridge may be numerically complete yet vulnerable to a common input error shared by both valuations. Independent reconciliation thus needs tests against external or separately controlled records and model validation by qualified reviewers. Agreement between two systems is weak assurance when both systems depend on the same erroneous source.
A reasonable control package separates three conclusions. Computational reproducibility means the approved inputs and method reproduce the output. Data integrity means the input population and fields agree with identified records and cutoffs. Valuation reasonableness means the method, assumptions, and results have received appropriate substantive actuarial and reporting review. Each conclusion requires its own documented evidence. Treating them as a single pass/fail field obscures the nature of remaining risk.
Approvals, audit evidence, and governance
The structure of approvals follows the materiality and judgment of the issue. A routine transaction timing reconciliation may be reviewed by accounting operations. A change to mortality assumptions requires actuarial governance. Interpretation of a new supervisory template requires regulatory reporting expertise. A significant change in eligible capital can warrant finance, actuarial, risk, and legal review. Review should be independent enough to challenge source selection and transformation, especially where reconciliation relies on management overlays.
Insurance reconciliation also operates within the scope of formal financial and supervisory audit requirements. The IAIS discusses supervisory reporting, external audit opinions on annual financial statements, and the possibility of audit or actuarial review of selected regulatory information in its global supervisory standards. These are not a universal mandate that every reconciliation cell receive an external audit opinion. The actual assurance obligations follow the jurisdiction, reporting entity, and applicable period.
Internal controls should retain evidence of inquiry, recalculation, supporting documents, and resolution of exceptions. An exception is closed only when the final accounting and regulatory disposition is recorded; 'investigated' is not the same as 'resolved.' Corrected material adjustments should trigger rerun of affected reconciliations, and the revised outputs should be compared with prior authorized versions. When a report has already been filed, changes to filing status should be recorded alongside the financial corrections.
Automated checks and human evaluation
Automated checks are useful for identity uniqueness, missing mappings, reproducible sums, negative balances where unexpected, unusual period changes, taxonomy-valid value types, currency consistency, and link integrity. They should test both end figures and intermediate transformation outputs. A reconciliation application can generate exception classifications and evidence pointers, but judgment remains necessary to decide whether a difference arises from valid accounting policy, contractual substance, model estimation, or an error.
Automation cannot infer legal applicability merely from a field name. The same label 'insurance liability' can refer to an IFRS 17 group balance, an ASC 944 reserve, a statutory liability, or a Solvency II technical provision. A rule engine should identify the basis, jurisdiction, and standard version before applying a test. Version-aware controls also require the ability to rerun a historical reporting period under its original rules; using today's taxonomy as if it applied unchanged to a prior filing can create spurious anomalies.
A reconciliation control register can be presented as a compact audit matrix:
| Control object | Evidence of performance | Principal residual risk |
|---|---|---|
| Population alignment | Contract counts, scope exclusions, dated crosswalk | Omitted or duplicated contracts |
| Ledger completeness | Trial balance, posting logs, subledger agreement | Wrong entity or cutoff |
| Valuation bridge | Approved model runs, assumptions, signed differences | Misattributed methodology effect |
| Reinsurance | Treaty, gross claim, recoverable, settlement links | Improper netting or collectibility |
| Investments | Position reconciliation and pricing evidence | Quantity, price, or admission error |
| Movement schedule | Opening/closing versions and transaction trail | Unexplained reserve movement |
| Supervisory mapping | Effective taxonomy, template coordinates, validation log | Wrong cell or obsolete filing rule |
| Capital analysis | Prudential adjustments and eligibility record | Excess mistaken for eligible funds |
| Approval | Reviewer identity and decision history | Unsupported closure of exception |
These entries illustrate an evidence design. The specific controls and evidence to be retained must fit the actual size, complexity, legal regime, and reporting obligations of the insurer. The analysis recognizes the difference between documenting a reasonable control design and empirically demonstrating its operating effectiveness.
Cross-Jurisdictional Implementation
International supervisory principles and local law
The international comparison begins with a hierarchy. The IAIS establishes globally accepted supervisory principles and guidance, while each jurisdiction determines its binding accounting, valuation, reporting, and capital rules. The IAIS ICP and ComFrame framework provides a reference for coherent supervision. It does not cause IFRS 17, Solvency II, U.S. GAAP, or NAIC statutory accounting to become interchangeable. A multinational insurer must maintain jurisdiction-specific records where the standards impose different recognition or valuation requirements.
The shared conceptual elements are cash-flow projections, asset and liability measurement, risk sensitivity, legal entity identification, and disclosure of material differences. The differences arise in the precise measurement objectives, permitted approaches, discounting, risk margins, admissibility, accounting presentation, capital resources, and filing taxonomies. The reconciliation should preserve shared inputs when appropriate while establishing separate, independently approved outputs for each regime.
The identity of a corporate group adds complexity. The global financial reporting parent may prepare consolidated statements under IFRS while domestic insurance subsidiaries file under local law. The group may also report an economic capital position or group-wide supervisory measure. A bridge should identify whether reported amounts cover the same legal entities and currencies, and whether material eliminations are symmetrical. Reporting a group IFRS liability beside a solo statutory liability without an entity bridge is not substantive comparability.
European Union: IFRS 17 and Solvency II
The EU comparison is particularly informative because accounting and supervision have partly compatible valuation technology but distinct purposes. IFRS 17 emphasizes the financial position and performance arising from contracts, including service results and unearned profit. Solvency II focuses on prudential valuation, technical provisions, own funds, capital requirements, and supervisory disclosure. The 2024 EIOPA study of IFRS implementation shows that common actuarial inputs can support both bases while material differences remain. Those differences should be allocated to identifiable drivers rather than treated as unexplained regulatory adjustments.
Article 296 makes the public communication obligation concrete. The Solvency II material-differences disclosures require explanation of material distinctions between the valuation of assets, technical provisions, and other liabilities for solvency purposes and for financial statements. A responsible analytical approach prepares an internal line-item bridge with more detail than the final published explanation may need; materiality and lawful confidentiality affect what appears publicly. Public disclosure is a summary of supported analysis, not a replacement for its underlying evidence.
The effective regulatory date is essential. EIOPA stated in its 2026 Solvency II reporting transition notice that reporting for the fourth quarter and financial year 2026 should follow the pre-review legal framework, while revised requirements are applicable from January 30, 2027 and first-quarter 2027 reporting. Public SFCR disclosure for the year 2026, submitted in 2027, remains based on the previous framework; the revised 2027 SFCR is disclosed in 2028. Early relief concerning certain retiring templates is a separate transitional matter. These temporal distinctions preclude a simplistic assumption that every 2027 filing uses identical requirements.
The July 2026 EIOPA completion announcement describes final guidelines and draft technical standards supporting the new framework. Proposed, adopted, and applicable rules need separate fields. A research or implementation system should not treat a submitted draft as binding merely because it is recent. The exact legal act and regulatory authority governing the filing period must control the reconciliation logic. The 2027 transition demonstrates that taxonomy versioning is a legal and historical issue as well as a technical engineering issue.
IFRS presentation also changes over time. The IFRS 18 standard summary establishes the general January 1, 2027 effective date, with earlier application permitted. A financial-to-prudential bridge spanning the transition should retain the earlier statement presentation as reported and document the new presentation basis when adopted. A changed caption can reflect reclassification without changing the insurance cash flows or prudential technical provisions. Comparatives and related disclosures must follow the requirements applicable to the entity.
United States: U.S. GAAP, statutory accounting, and RBC
The United States requires another kind of bridge. U.S. general-purpose insurance reporting under Topic 944 and statutory financial reporting under NAIC principles have different objectives and may use different measurement and presentation practices. The FASB long-duration accounting improvements address financial reporting for life insurance and annuity contracts, including more current liability assumptions and enhanced disclosures. Subsequent FASB transition amendments show the need to track actual adoption and transition treatment for contracts covered by the amendment.
The NAIC statutory accounting principles emphasize conservatism, recognition of assets available for policyholder obligations, and consistent reporting for supervisory purposes. The NAIC expressly recognizes that state law and prescribed or permitted accounting practices can modify the national model. Consequently, a U.S. GAAP-to-SAP bridge must record the insurer's state of domicile, legal entity, line of business, applicable reporting year, statutory accounting texts, and any prescribed or permitted practices. A single nation-wide adjustment table without those attributes is insufficient for institution-specific compliance.
The NAIC risk-based capital explanation establishes that RBC requirements reflect insurer size and risk and are designed to support supervisory intervention. They should not be interpreted as an all-purpose ranking or as identical to accounting shareholders' equity. Thus, U.S. statutory surplus, total adjusted capital, calculated RBC thresholds, and general-purpose equity are distinct measures. Reconciliation should map the capital components and adjustments and separately explain the denominator or threshold employed; equating two capital ratios because their numerators have similar labels would be analytically unsound.
For U.S. general-purpose financial statements, the entity's actual FASB guidance and transition date matter. For statutory filings, the reporting instructions and the domicile regulator's requirements matter. The same actuarial claim data might underlie several measurements, but their outputs must be tested against the authority that actually governs each report. In particular, solvency-oriented asset admissibility under NAIC SAP should not be imported as a universal rule into other jurisdictions' accounting or regulatory frameworks.
Cross-border reinsurance, branches, and currencies
International insurance groups face cross-border data connections in which the claims-paying legal entity, policy issuing entity, reinsurer, and consolidation parent may be in different jurisdictions. Reinsurance can be recognized differently across ceding and assuming entities in timing, counterparty, and gross/net presentation. Branch reporting introduces questions of allocation of assets and obligations to the branch, home-state supervision, and reporting currency. Where a transaction affects multiple entities, the relevant mappings must include both entity-specific and group-elimination effects.
Currency controls require the original transaction currency, functional currency, reporting currency, exchange-rate source, rate date, and conversion method. It is necessary to distinguish the change in economic expectation from the change in translation. A matched reserve converted on different dates can differ with no underlying change in claims; a ledger adjustment that forces the total to agree can mask a rate-definition error. Multi-currency group reporting should therefore separate valuation assumptions in original currency from translation movements after valuation.
Data-sharing and governance also matter. A parent may receive standardized extracts from local insurers, but it must preserve the local reporting basis, approved valuation, and controls that substantiate those figures. Central processing can improve consistency and operational efficiency while introducing risks of mistaken global mapping. A controlled local-to-group reconciliation should record the meaning of each local figure before converting it to a common group view. Homogenized field names are not a guarantee of harmonized accounting substance.
Comparative interpretation of reconciled differences
Three conclusions emerge from comparing the jurisdictions. First, a strong bridge starts with the same underlying economic population but applies the applicable governing regime before computing reported values. Second, some divergences can be reduced through shared data and modeling infrastructure, while others reflect legitimate, durable differences in purpose and law. Third, reproducibility depends on effective dates and version histories. The bridge is therefore an evidence-producing research and reporting process rather than a purely algebraic conversion.
The EIOPA evidence supports the possibility of data synergies between IFRS 17 and Solvency II, not a general numerical equivalence. The NAIC and FASB sources show that financial reporting and insurer solvency reporting also diverge within one country. IAIS principles encourage explanation and transparency rather than global uniformity of all balance-sheet figures. These conclusions synthesize stated institutional requirements and research evidence. No new statistical finding is claimed beyond the published empirical studies actually cited.
Conclusion
Reconciliation of accounting and prudential insurance data is a controlled demonstration of how overlapping economic rights, obligations, assets, claims, and cash flows are represented under different authoritative reporting bases. Its first obligation is identity: the entities, contracts, periods, currencies, and populations under comparison must be established. Its second is method: each transformation between financial and prudential recognition, valuation, presentation, and capital treatment must be specified and linked to governing requirements. Its third is evidence: source records, model versions, financial journals, reporting taxonomies, and approval decisions must support the changes. The final arithmetic equality is the result of that process.
IFRS 17 and Solvency II illustrate the difference between legitimate value divergence and operational failure. IFRS 17's contractual service margin, nonfinancial-risk adjustment, contract groupings, and service-related presentation are not interchangeable with Solvency II best estimates, risk margin, technical provisions, and prudential own-funds requirements. A reconciled portfolio can therefore show materially different liabilities and still satisfy both frameworks. Its justification lies in a transparent calculation and a reproducible explanation of the differences. Article 296's comparison of material financial and prudential valuation differences gives this principle direct supervisory significance in the European regime.
The worked hypothetical liability bridge establishes a −95 difference between accounting and prudential liabilities with an exact independently calculated adjustment sum. The reserve roll-forward establishes a closing claim liability of 285 from disclosed opening and movement components. The complete balance-sheet example shows why a +40 difference in net assets cannot be interpreted automatically as eligible prudential capital. These calculations prove only the arithmetic and conceptual distinctions for their stated assumptions; actual insurer reporting requires its own populations, valuations, rules, and audit evidence.
The international comparison establishes the need for version-aware regulatory logic. The January 2027 Solvency II review transition and the IFRS 18 effective date demonstrate that the same insurer may change reporting presentation or supervisory templates without equivalent changes in economic claims and contracts. In the United States, NAIC statutory accounting and U.S. GAAP require distinct legal and accounting mapping; state prescribed or permitted practices are an additional material dimension. International supervisory principles encourage consistent, understandable and properly explained valuations, while domestic law determines specific obligations.
The final research conclusion is that reconciliation quality is measured by the completeness of explained differences and by the reproducibility of the supporting evidence. A zero residual is a valuable control, but a reported figure remains susceptible to shared data errors, inappropriate assumptions, misclassification, and changes in applicable reporting rules. High-quality insurance reporting maintains distinct controls for population integrity, accounting transmission, actuarial valuation, supervisory eligibility, and filing. This conclusion is an original analytical synthesis of established standards, regulator evidence, and actuarial scholarship; it establishes no new named theory, model, principle, or doctrine.
References
England, Peter D., and Richard J. Verrall. 2002. “Stochastic Claims Reserving in General Insurance.” British Actuarial Journal 8 (3): 443–518. Journal publication and DOI.
European Commission. 2015. “Commission Delegated Regulation (EU) 2015/35, Article 296: Solvency and Financial Condition Report, Valuation for Solvency Purposes.” Consolidated supervisory rulebook presentation by EIOPA. Article 296 text.
European Commission. 2023. “Commission Implementing Regulation (EU) 2023/894 of 4 April 2023 Laying Down Implementing Technical Standards for the Application of Directive 2009/138/EC as Regards the Templates for the Submission by Insurance and Reinsurance Undertakings to Their Supervisory Authorities of Information Necessary for Their Supervision.” Official Journal of the European Union. Official EU regulation.
European Insurance and Occupational Pensions Authority (EIOPA). 2024. Report on the Implementation of IFRS 17 Insurance Contracts. April 15. EIOPA research report.
European Insurance and Occupational Pensions Authority (EIOPA). 2026a. “EIOPA Proposes Amendments Aimed at Easing Insurers’ Supervisory Reporting and Disclosure Requirements.” March 30. Regulatory reporting announcement.
European Insurance and Occupational Pensions Authority (EIOPA). 2026b. “EIOPA Completes Solvency II Review Mandate with Final Guidelines and Draft Technical Standards Before Revised Framework Takes Effect Early Next Year.” July 15. Solvency II review completion.
European Insurance and Occupational Pensions Authority (EIOPA). 2026c. “Supervisory Reporting.” Regulatory templates, instructions, and reporting instruments; accessed November 15, 2026. Supervisory reporting portal.
European Insurance and Occupational Pensions Authority (EIOPA). 2026d. “Supervisory Reporting: Data Point Model (DPM) and XBRL.” Taxonomy and technical materials; accessed November 15, 2026. DPM and XBRL materials.
European Parliament and Council. 2009. “Directive 2009/138/EC of 25 November 2009 on the Taking-Up and Pursuit of the Business of Insurance and Reinsurance (Solvency II).” Consolidated version of January 17, 2025. Official Journal of the European Union. Consolidated Solvency II directive.
Financial Accounting Standards Board (FASB). 2018. “FASB In Focus: Accounting Standards Update No. 2018-12, Targeted Improvements to the Accounting for Long-Duration Contracts Issued by Insurance Companies.” August 15. FASB issuer explanation.
Financial Accounting Standards Board (FASB). 2022. “Financial Services—Insurance (Topic 944): Transition for Sold Contracts.” Completed standard-setting project and transition information. Topic 944 transition project.
IFRS Foundation. 2014, as amended. “IFRS 9 Financial Instruments.” Issued-standards summary; accessed November 15, 2026. IFRS 9 standard overview.
IFRS Foundation. 2017, as amended in 2020 and subsequently. “IFRS 17 Insurance Contracts.” Issued-standards summary, effective for annual periods beginning January 1, 2023. IFRS 17 standard overview.
IFRS Foundation. 2024. “IFRS 18 Presentation and Disclosure in Financial Statements.” Issued April 2024, generally effective for annual periods beginning January 1, 2027. IFRS 18 standard overview.
IFRS Foundation. n.d. “IFRS Taxonomy Illustrative Examples.” Including IFRS 17 insurance-contract reconciliations. Accessed November 15, 2026. Illustrative taxonomy examples.
International Association of Insurance Supervisors (IAIS). 2026a. “Insurance Core Principles (ICPs): Online Tool.” Official text and updates; accessed November 15, 2026. Online ICP framework.
International Association of Insurance Supervisors (IAIS). 2026b. “Insurance Core Principles and Common Framework (ComFrame).” Standard-setting overview; accessed November 15, 2026. ICP and ComFrame overview.
Mack, Thomas. 1993. “Distribution-Free Calculation of the Standard Error of Chain Ladder Reserve Estimates.” ASTIN Bulletin 23 (2): 213–225. Casualty Actuarial Society abstract.
National Association of Insurance Commissioners (NAIC). 2026a. “Statutory Accounting Principles.” Updated June 23, 2026. Official statutory accounting overview.
National Association of Insurance Commissioners (NAIC). 2026b. “Risk-Based Capital.” Insurance topics overview; accessed November 15, 2026. Official RBC overview.