Internal:Training/IFRS17/Contract modifications and portfolio transfers

🔗 Recall. In the previous page, you learned how reinsurance held is accounted for as a mirror image of direct insurance contracts, with key asymmetries around day-one gains and loss recovery. Now we turn to what happens when a contract's terms change after initial recognition, or when an entire portfolio moves from one insurer to another.

🎯 Objective. In this page, you will learn:

• How to determine whether a change in contract terms should be treated as a continuation of the existing contract or as the end of one contract and the start of a new one.
• What specific criteria trigger a contract modification under IFRS 17 and what the accounting consequences are for each outcome.
• How portfolio transfers between insurers are measured at the transaction date and how the receiving insurer brings transferred contracts onto its balance sheet.

~*~

When contract terms change: derecognize or continue?

🔄 Change is inevitable. Insurance contracts do not always stay the same from start to finish. A policyholder might ask for higher coverage limits, add a new risk to an existing policy, or convert a temporary life cover into a permanent one. A regulator might impose new mandatory benefits that alter the scope of existing contracts. In each case, the insurer faces a fundamental question: does the original contract continue with adjusted terms, or should the insurer treat the old contract as ended and a new one as begun? The answer matters because it determines how the contractual service margin, the fulfilment cash flows, and the rest of the measurement are carried forward.

📑 Two possible paths. IFRS 17 provides a clear fork in the road. If the change is substantial enough to create, in effect, a different contract, the insurer derecognises the original contract and recognises a brand-new one. If the change is less fundamental, the insurer continues measuring the existing contract and simply updates the estimates to reflect the new terms. Think of it like renovating a house: replacing a kitchen is an update to the same property, but demolishing the building and constructing something entirely new is a different property altogether. The distinction between these two paths drives all of the accounting that follows.

⚠️ Common misconception. Learners often assume that any change to a policy's terms automatically triggers derecognition. In practice, most routine changes, such as adjusting a sum insured within the same product structure, or updating a beneficiary, do not meet the threshold. Derecognition is reserved for changes that are so significant that the modified contract would not have belonged in the same group as the original. Routine endorsements and minor amendments typically remain within the existing measurement.

🤔 Think about it. If minor changes simply update the existing measurement, what exactly makes a change significant enough to cross the line into derecognition? What criteria does the standard use to draw that boundary?

~*~

The criteria and consequences of modification

📐 Drawing the line. IFRS 17 states that a contract modification requires derecognition of the original contract and recognition of a new one when four conditions are met together. The modified terms must have the effect of replacing the existing contract with a new contract that falls within IFRS 17's scope. In other words, if the new terms had been offered as a standalone contract on that date, they would have been recognised as a separate insurance contract in their own right. Additionally, the modified contract would have belonged to a different group than the original, because its risk profile or expected profitability has shifted so much that the original grouping no longer fits. If these conditions are satisfied, the insurer treats the original contract as extinguished and the new contract as freshly issued.

🏠 A practical example. Suppose a policyholder in Italy holds a standard annual home insurance policy. Midway through the year, they ask to convert it into a multi-year comprehensive property and liability package that includes earthquake cover and a ten-year term. The risk profile has changed dramatically, the coverage period is fundamentally different, and the new contract would clearly belong in a different group. In this case, the insurer derecognises the original one-year policy and recognises a new ten-year contract. The CSM of the old contract is released at that point, and the new contract is measured from scratch using the general model (or VFA, if applicable) at initial recognition.

⚠️ Common misconception. Some people believe that when derecognition occurs, any remaining CSM from the old contract is simply lost or written off. That is not the case. The remaining CSM and other balances of the original contract are accounted for at the modification date. Any difference between the derecognised amounts and the premium charged for the new contract feeds into the day-one measurement of the replacement contract. Nothing vanishes into thin air; it is redirected.

🔧 When the contract continues. If the modification does not meet the threshold for derecognition, the insurer keeps the existing contract on the balance sheet and treats the change as an update to future cash flow estimates. Under the general model, changes relating to future service adjust the CSM, just as any other favourable or unfavourable change in assumptions would. For example, if AXA increases the sum insured on a group of German motor policies and collects an additional premium, the revised expected inflows and outflows are fed into the existing measurement. The CSM absorbs the net change, and the contract group carries on as before, with updated numbers but the same identity.

🤔 Think about it. We have covered what happens when the terms of individual contracts change. But what happens when an entire portfolio of contracts moves from one insurer to another, for example through an acquisition or a transfer agreement? How does the receiving insurer measure contracts it did not originally write?

~*~

Portfolio transfers: measuring at the transaction date

🤝 When portfolios change hands. In the insurance industry, portfolio transfers occur regularly. One insurer may sell a block of business to another, or a corporate restructuring may move contracts between entities within the same group. Whatever the reason, the receiving insurer inherits contracts it did not underwrite, often with complex histories of claims, reserves, and CSM balances. IFRS 17 requires the receiving insurer to treat the transaction date as its own initial recognition date for those contracts. This means the new owner measures the transferred contracts as if it were writing them fresh on that day, using current assumptions and current discount rates.

📊 Building the measurement from scratch. At the transaction date, the receiving insurer estimates all remaining fulfilment cash flows, including expected future claims, expenses, and any remaining premium collections. It discounts those cash flows using rates appropriate at the transaction date, adds a risk adjustment, and determines the CSM. The CSM is calculated as the difference between the fulfilment cash flows (including the risk adjustment) and the consideration paid for the transfer. If an insurer like AXA acquires a block of 20,000 motor contracts in Spain for €15,000,000, and the fulfilment cash flows plus risk adjustment total €13,500,000, the CSM would be €1,500,000, representing the expected profit embedded in the acquired book.

⚠️ Common misconception. A common error is to assume the receiving insurer simply copies the CSM balance from the transferring insurer's books. That does not happen. The receiving insurer starts from its own assumptions and the price it actually paid. The original insurer's CSM is irrelevant to the new owner's measurement. Two insurers looking at the same block of contracts on the same date may arrive at different CSM figures because they use different discount rates, different expense assumptions, or paid a different price.

🔍 Grouping and classification. The receiving insurer must also apply IFRS 17's grouping rules to the transferred contracts. It forms portfolios of contracts with similar risks, separates them into profitability groups, and assigns annual cohorts based on the contracts' original issue dates, not the transfer date. If the acquired block contains contracts issued over several years, the receiving insurer cannot lump them all into a single cohort. Each vintage must be kept separate, exactly as if the receiving insurer had written them itself in those original years. This preserves the transparency and comparability that IFRS 17 is designed to achieve, even when business changes hands.

~*~

Takeaways

📌 Key takeaways.

• When contract terms change, the insurer must decide whether to derecognise the original and recognise a new contract, or to continue the existing measurement with updated estimates; the threshold depends on whether the modified contract would belong in a different group.
• If derecognition is triggered, the old contract's balances feed into the new contract's day-one measurement; if not, changes relating to future service adjust the CSM within the existing group.
• In a portfolio transfer, the receiving insurer measures the acquired contracts at the transaction date using its own assumptions and the price paid, applies all grouping rules including annual cohorts, and does not inherit the transferring insurer's CSM.

~*~