IFRS 17: Are Your Insurance Riders a Side Dish or a Separate Meal?

Think of an insurance policy like a combo meal. You have your main item—the base life insurance contract—but you can also add extras like a critical illness rider (the fries) or a waiver of premium benefit (the drink). Under previous accounting standards, you generally priced and accounted for the entire meal as one package. IFRS 17, however, asks a more pointed question: Is that rider truly part of the main meal, or should it be treated as a separate item on the bill?

This is one of the most fundamental shifts in thinking introduced by IFRS 17. The standard requires an entity to identify all the promises within a contract and decide whether to account for them together or to 'unbundle' them into separate components. This process is known as separation.

The Core Question: When to Unbundle?

The decision to separate a rider from its base contract isn't arbitrary. IFRS 17 provides a specific two-part test to determine if a component is 'distinct' and therefore requires separate accounting.

A rider must be separated if both of the following conditions are met:

1. The risks are not highly interrelated: This means the risk covered by the rider behaves largely independently of the risks in the base contract. For example, the investment risk in a unit-linked savings component is not closely related to the mortality risk of a term life policy. In contrast, an accidental death benefit is highly interrelated with a life policy, as one event often triggers the other.

2. A similar contract is, or could be, sold separately: The insurer must consider whether it, or another company in the same market, sells (or could sell) the benefit as a standalone product. A pure savings component could easily be sold separately, but a waiver of premium benefit attached to a specific policy typically cannot.

If a rider fails either one of these tests, it is considered part of the base contract and its cash flows are bundled together.

The Accounting Impact: Why Separation Matters

This isn't just an academic exercise; the decision has a direct impact on your financial statements, particularly on the Contractual Service Margin (CSM), which represents the unearned profit of a contract.

If a rider is NOT separated: Its expected premiums and benefit cash flows are merged with those of the base contract. They all form a single group, with one CSM calculated for the entire bundle. The profit is then released over the combined coverage period of the whole package.

If a rider IS separated: It is treated as its own mini-contract. It will have its own CSM, and its profit will be recognized over its specific coverage period. This is critical because the rider's coverage period might be much shorter than the base policy's. Separation ensures that profit is recognized in the period the service is delivered, preventing profits from being artificially deferred or accelerated.

A Practical Look

Consider a 20-year life policy with an attached 5-year term critical illness (CI) rider. The mortality risk of the life policy and the morbidity risk of the CI rider are not considered highly interrelated. Furthermore, standalone CI policies are widely available.

Under IFRS 17, this CI rider would likely be separated. This means the insurer would calculate a CSM for the 20-year life component and a separate CSM for the 5-year CI rider. The profit from the rider would be fully recognized over its 5-year term, rather than being spread thinly over the full 20 years of the base policy. This leads to a more accurate and transparent representation of profitability.

Getting the separation right is a foundational step in your IFRS 17 journey. It ensures your profit recognition patterns accurately reflect the services you provide to policyholders, providing clearer insights for management and investors alike.