IFRS 17 Contract Grouping: A Practical 3-Step Framework for Insurers

What is Contract Grouping under IFRS 17?

Imagine being handed 50,000 active insurance contracts and told to “group them under IFRS 17.” Where do you even start? That’s the challenge many insurers across the region are facing today.

If you’ve been following our IFRS 17 series, you already know the big picture—the ‘what’ and ‘why’ of this transformative standard. In our previous post on Get ready for IFRS 17, we introduced the new measurement logic that reshapes how insurers recognize revenue and profit. Now it’s time to roll up our sleeves and tackle the ‘how.’

Here’s the reality: I’ve noticed insurers often struggle with contract grouping. Some try to break their portfolio into 47 groups, only to find that many aren’t really needed! On the flip side, others keep things too simple and end up combining everything, which can lead them to miss vital signs of profitability. Both approaches can lead to challenges, so finding a happy medium is key!

Why does grouping matter so much? Because it determines how your Contractual Service Margin (CSM) is calculated, how profit emerges over time, how disclosures are presented, and even how management interprets product profitability.

In this guide, we’ll walk through a practical three-step framework for grouping insurance contracts, illustrated with real examples from Balkan insurers, and highlight common pitfalls and how to avoid them. Finally, you’ll know exactly how to set up your groups in a way that is both IFRS 17-compliant.

Profitability Tracking

Previously, profitable contracts could quietly subsidize loss-making ones. IFRS 17 eliminates that comfort zone. Each group must reflect its own expected profitability, revealing the true economics of your portfolio.

Under IFRS 4, an insurer with a 30% loss ratio on properties around rivers (Danube, Sava, etc.) and a 15% loss ratio on standard residential properties could blend them into a single aggregate figure. Under IFRS 17? Each tells its own story. No more hiding poor performers behind good ones.

Contractual Service Margin (CSM)

Every group gets its own CSM “bucket.” That means separate profit recognition patterns for each group. How you define those groups directly affects when and how profit is released over the life of contracts.

Think about it: a 2024 motor insurance cohort with a 20% expected profit margin will release CSM differently than a 2025 cohort with 12% margins—even if they’re the same product.

Presentation & Disclosure

Financial statements now show separate insurance revenue and CSM movements by group. Transparent grouping improves investor confidence and comparability across insurers. Stakeholders can finally see which parts of your business are generating value.

Management Insight

Grouping gives insurers new visibility into which products, cohorts, or segments are truly adding value. Pricing, underwriting, and product design decisions become data-driven rather than intuition-based.

Consider a small insurer with 10,000 motor policies. Under IFRS 4, one aggregate profit figure. Under IFRS 17: minimum of 6 groups (3 annual cohorts × 2 profitability buckets), each with separate CSM tracking. That’s transparency in action.

Let’s be clear about what we mean by different risk characteristics. Take Motor Third Party Liability (MTPL) versus Property insurance:

MTPL Liability coverage. Your risk is damage to third parties (material damage to their vehicle or bodily injury). Claims can be enormous, slow to develop, and often require reinsurance.

Property Asset coverage. Your risk is damage to insured buildings or contents. Claims tend to settle faster, with different dynamics and reinsurance structures.

These are fundamentally different risks, even though both involve “damage.” That’s why they must be separate portfolios.

THE THREE-STEP GROUPING FRAMEWORK

Let’s break down the practical approach to grouping contracts. This is a sequential process—you must complete each step before moving to the next.

STEP 1: Define Portfolios

• By product type: life, non-life, or health
• By underlying risk: motor, property, liability, health, etc.
• By management responsibility: business units or product lines

An insurance company might define: Motor Third Party Liability (TPL) as one portfolio and property insurance as another portfolio.

Motor + Property together? Not allowed—different underlying risks (liability to third parties vs. property damage to owned assets), different pricing models (experience-based vs. location-based), other claims development patterns (long-tail liability vs. short-tail property), different reinsurance structures (excess of loss vs. proportional).

PRACTICAL TIP

If you’re with a smaller insurance company, consider starting with just a few product lines. Avoid overcomplicating things! For a team of 20 people, managing 15 different portfolios can be overwhelming. Remember, you can constantly adjust and refine your strategy as you progress!

STEP 2: Annual Cohorts Explained

Once portfolios are defined, contracts must be grouped into annual cohorts—sets of contracts issued within one calendar year. Contracts issued more than one year apart cannot be in the same group. This is non-negotiable.

KEY PRINCIPLE: Annual cohorts are mandatory. You cannot have group contracts issued more than one year apart, ever. No exceptions.

Why is this important?

• Prevents cross-subsidization: Stops profits from older, more profitable contracts from subsidizing newer, riskier ones.
• Reflects economic reality: Market conditions, pricing strategies, and risk profiles change year over year.
• Simplifies disclosure: Trend analysis becomes clearer when cohorts are cleanly separated.

When it comes to annual cohorts under IFRS 17, it’s essential to understand that they are defined by the initial recognition date, not by when the contract was first created or last amended. This distinction can be complex and may lead to challenging situations.

Еxample: А motor policy written in June 2024, renewed in June 2025. These are two different cohorts (2024 cohort and 2025 cohort), even though it’s the “same” customer with continuous coverage. Each cohort is entirely separate, even within the same portfolio. That means separate CSM tracking, separate disclosure, separate monitoring.

AUDITOR’S NOTE: This is a frequent audit finding. If your policy administration system doesn’t auto-tag the cohort year at policy inception, auditors will ask you to reconstruct it—potentially for 100,000+ contracts manually. Set up the automation NOW.

STEP 3: Assess Profitability Buckets

Within each annual cohort, IFRS 17 requires contracts to be grouped by expected profitability at inception into three mandatory buckets. This is where actuarial science meets accounting judgment—and where most debates with auditors happen. Let’s dive deep.

Group 1: Onerous Contracts (Loss-Making)

Loss recognized – immediately in P&L (no deferral allowed), CSM = zero (you can’t defer profit you don’t have), tracked separately forever (cannot be reclassified later).

Policy issued in high-flood-risk areas along the Danube or Sava rivers, where the annual premium received (npr. 500 EUR) is lower than expected claims and expenses (680 EUR). This loss hits P&L immediately. No CSM is created. The contract stays in the onerous group for its entire life.

Group 2: No Significant Possibility of Becoming Onerous

Within this group, you can allocate a stable, mature product with a long claims history. These are products with high expected profit margins (typically >20%), strong historical loss ratios, low volatility in key risk factors (claims frequency, severity), and robust underwriting standards. This CSM will be released systematically as insurance services are provided over the coverage period.

Group 3: Remaining Contracts (The Gray Zone)

These are products with a moderate profit margin (typically 5-15%), usually new product lines with limited historical data, products in transitional or emerging markets, products with seasonal or cyclical claims patterns, products with higher uncertainty in key assumptions. Technically profitable at inception, but the margin is thin. One bad claims quarter could flip this negative. This goes into “Remaining contracts” and requires ongoing quarterly monitoring.

Understanding “Significant Possibility”

Here’s the challenge: IFRS 17 intentionally avoids defining “significant possibility.” This is left to management judgment—subject to disclosure and audit scrutiny.

You need to establish clear, documented criteria. Auditors will expect to see:

• Clearly defined profitability criteria (written policy document)
• Quantitative analysis supporting each classification decision
• Management sign-off on criteria and classifications
• Audit trail showing when and why decisions were made
• Assumptions documentation (discount rates, claims trends, risk adjustment methodology).

AUDITOR’S NOTE: Document your profitability criteria before year-end. Post-hoc justifications rarely survive audit scrutiny. In one engagement, it took 3 months to justify classifications that weren’t documented at inception. This is where actuarial input, finance interpretation, and management judgment intersect—and where auditors will dig deep.

CONCLUSION: YOU NOW HAVE A FRAMEWORK

Congratulations! You now understand the three-step framework for contract grouping under IFRS 17:

You’ve seen how this works in practice with real examples. You understand the decision criteria for profitability assessment. You know what documentation auditors expect.

But knowing the framework is only half the battle.

The real test comes during implementation—when you’re faced with edge cases, system limitations, and tight deadlines. That’s where most insurers make costly mistakes that lead to audit findings, restatements, and months of rework.

In Part 2 of this series, we’ll dive into:

• The five most common pitfalls in contract grouping (and how to avoid them)
• Pro tips from real implementations across the Balkans 
• A comprehensive implementation checklist
• Red flags that trigger audit concerns

💬 Questions so far?

Drop a comment below or reach out directly. Understanding the framework is crucial before we tackle the implementation challenges in Part 2.

This post is also available in: srpski македонски