Internal:Training/IFRS17/Grouping contracts
🔗 Recall. In the previous page, you learned how the contractual service margin locks away unearned profit on day one and releases it over the coverage period as the insurer delivers service. Now we build on that by asking a crucial upstream question: which contracts should be measured together in the first place?
🎯 Objective. In this page, you will learn:
- How insurers organise contracts into portfolios based on similar risks managed together
- Why IFRS 17 requires contracts to be separated into profitability groups, and what happens when a group is onerous
- Why contracts issued more than one year apart must sit in different annual cohorts, even if they are otherwise identical
Portfolios: contracts with similar risks
📂 Starting with the big picture. Before an insurer like AXA can measure any insurance contract under IFRS 17, it must first decide which contracts belong together. The standard requires insurers to sort contracts into portfolios, where a portfolio is a collection of contracts that share similar risks and are managed together as a single pool. Think of it the way a library organises books: you would not shelve a novel about Mediterranean cooking next to a textbook on quantum physics. In the same way, a motor policy in Germany and a property policy in Belgium face fundamentally different risks and are overseen by different underwriting teams, so they belong in separate portfolios.
🔍 What "similar risks" means in practice. Two contracts share similar risks when they are exposed to the same type of peril and would be expected to respond to the same economic and demographic drivers. For example, 10,000 home insurance contracts covering storm damage along the Atlantic coast of France would typically form one portfolio because they all respond to the same weather patterns, construction standards, and claims behaviour. A separate block of motor third-party liability contracts in Spain would form a different portfolio, because the risk drivers, such as traffic density, legal claims costs, and repair inflation, are entirely different. The practical test is straightforward: if the contracts are managed together by the same team under the same pricing and reserving approach, they almost certainly belong in the same portfolio.
⚠️ Common misconception. A portfolio is not the same as a line of business. Many insurers manage "property" as a single line of business, but within that line there could be several portfolios: one for residential property, another for commercial property, and perhaps a third for agricultural buildings. The portfolio is a finer grouping, defined by the similarity of risks, not by the organisational chart. Always look at the underlying risk characteristics, not the label on the department door.
🏗️ Why portfolios matter. Portfolios are the first layer of structure, but they are not the final one. Within each portfolio, IFRS 17 demands further subdivision. The portfolio merely sets the outer boundary: contracts from different portfolios can never be combined, no matter how profitable or unprofitable they are. Getting this first grouping right is essential because every subsequent calculation, from fulfilment cash flows to the CSM, is performed at the group level, and the group always sits inside a single portfolio.
🤔 Think about it. If all contracts in a portfolio shared similar risks, you might wonder why the standard does not simply measure the entire portfolio as one unit. What further distinction could matter? The answer lies in profitability, and that is exactly what the next section explores.
Profitability groups: separating profitable from onerous
💰 Not all contracts earn money. Once contracts have been sorted into portfolios, IFRS 17 requires a second layer of sorting based on expected profitability at the date of initial recognition. The standard defines three profitability buckets that every portfolio must be split into. The first bucket contains contracts that are onerous at initial recognition, meaning the insurer expects to make a loss on them from the very start. The second bucket holds contracts that, at initial recognition, have no significant possibility of becoming onerous later. The third bucket captures everything in between: contracts that are profitable today but carry a meaningful chance of turning onerous as experience unfolds.
📊 A concrete example. Imagine AXA writes 5,000 home insurance contracts in a coastal region of Brittany. After analysing the expected claims, expenses, and risk adjustment, the actuarial team concludes that 4,200 of these contracts are comfortably profitable, 500 are profitable but sit in areas with rising flood exposure and could turn loss-making if climate trends worsen, and 300 are already expected to generate a net loss because they cover properties in a zone recently reclassified as high risk. IFRS 17 insists that these three groups are measured separately. The 4,200 profitable contracts form one group, the 500 borderline contracts form another, and the 300 onerous contracts form a third.
⚠️ Common misconception. Some people assume that the three profitability buckets are optional or that an insurer can simply average profitable and onerous contracts within a portfolio. This is expressly forbidden. The whole point of the split is to prevent profitable contracts from hiding losses on onerous ones. If the 300 loss-making contracts in Brittany were blended with the 4,200 profitable ones, the resulting CSM would mask a real economic loss. IFRS 17 forces transparency: losses on onerous groups must be recognised immediately in the income statement, while profit on healthy groups is stored in the CSM and released over time.
🎯 Why the middle bucket exists. The intermediate group, contracts with a significant possibility of becoming onerous, exists because uncertainty is inherent in insurance. A contract can look profitable today and deteriorate tomorrow if claims inflation accelerates or a new court ruling increases liability awards. By isolating these borderline contracts, the standard ensures that if they do turn onerous, the loss is recognised promptly rather than being diluted across a larger, healthy group. In practice, identifying this middle group requires actuarial judgment; the standard does not prescribe a precise threshold, so insurers must develop and document their own methodology.
🤔 Think about it. You now know that contracts must be grouped by portfolio and then by profitability. But what about timing? Should a contract written in January sit alongside an identical contract written the following January? The answer may surprise you, and it is the subject of the next section.
Annual cohorts: why contracts issued more than a year apart must be separated
📅 Time as a dividing line. Even after splitting contracts by portfolio and profitability, IFRS 17 adds one more requirement: contracts issued more than twelve months apart cannot belong to the same group. This is the annual cohort rule. In practical terms, it means that if an insurer writes motor policies continuously throughout 2025, all those policies form one cohort. Policies written in 2026, even if they cover the same risks in the same region at the same price, must go into a separate cohort. The cohort is defined by the year of initial recognition, not by the coverage period or the renewal date.
🔄 The logic behind the rule. The annual cohort requirement exists to preserve the integrity of profit reporting over time. Without it, an insurer could keep adding new, profitable contracts to an existing group indefinitely, and those fresh premiums would continuously replenish the CSM, making it impossible for investors and regulators to see whether older business is performing as expected. By locking each cohort after twelve months, the standard ensures that the CSM for the 2025 cohort reflects only the experience of 2025 contracts. If claims turn out worse than anticipated for those contracts, the CSM shrinks or the group becomes onerous, and that information is visible rather than obscured by newer, healthier business.
⚠️ Common misconception. A frequent objection to the annual cohort rule is that it is impractical for long-duration contracts such as life insurance or disability insurance, where policies may run for 20 or 30 years. Critics argue that maintaining separate cohorts for each issue year creates dozens of groups and enormous operational complexity. While the operational burden is real, and it was one of the most debated aspects of IFRS 17 during its development, the standard does require it. Some jurisdictions have discussed modifications, but the principle remains: mixing issue years would undermine the comparability and transparency that IFRS 17 was designed to achieve.
🧩 Putting it all together. The full grouping hierarchy works in three steps. First, sort contracts into portfolios by similar risk. Second, within each portfolio, split contracts into the three profitability buckets. Third, within each profitability bucket, create a separate group for each annual cohort. The result is a set of granular measurement groups, each containing contracts that share the same risk profile, a similar profitability outlook, and roughly the same issue date. Every subsequent calculation under IFRS 17, from the fulfilment cash flows and discount rate to the risk adjustment and CSM, is performed at this group level. For an insurer operating across multiple countries, like AXA, the number of groups can run into the hundreds or even thousands, which is why robust data systems and clear governance are essential.
Takeaways
📌 Key takeaways.
- A portfolio groups contracts with similar risks managed together; it is the outer boundary that can never be crossed when forming measurement groups.
- Within each portfolio, contracts must be separated into three profitability buckets (onerous, at risk of becoming onerous, and remaining), preventing profitable business from masking losses.
- The annual cohort rule requires contracts issued more than twelve months apart to sit in different groups, ensuring that profit patterns for each generation of business remain transparent over time.