Multi-GAAP Reinsurance Reporting: IFRS 17 and Local Figures
On this page
- Key Takeaways
- What Is Multi-GAAP Reinsurance Reporting?
- How Does Each Treaty Data Element Map to IFRS 17 and Local GAAP?
- Which Treaty Data Fields Must Be Captured Once for Both Bases?
- Where Do Multi-GAAP Reinsurance Figures Diverge?
- How Does One Quota Share Feed Both Bases at Quarter End?
- How Does Insurnest Support Multi-GAAP Reinsurance Reporting?
- What Should CFOs Fix Before the Next Dual Close?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
The group IFRS 17 pack and the local statutory return both show ceded premium for the same quota share.
The figures differ, and at quarter end nobody can say how much is method and how much is data.
Multi-GAAP reinsurance reporting is producing reinsurance figures under more than one accounting basis, such as IFRS 17 and a local GAAP, from the same treaty data.
Doing it without rework means capturing each treaty data element once, reconciling it, and mapping it to each basis's rules in separate layers.
Key Takeaways
- One dataset, two rule sets. Differences should come from accounting rules, never from different data.
- IFRS 17 changes the recognition date. Proportionate cover can depend on when underlying contracts began.
- Reinsurer default risk is measured in. IFRS 17 fulfilment cash flows reflect the reinsurer's non-performance risk.
- Receivables move inside the contract. IFRS 17 includes premium and claims balances in its measurement.
- Local GAAP varies by country. Map each local rule explicitly rather than assume a standard one.
What Is Multi-GAAP Reinsurance Reporting?
Multi-GAAP reinsurance reporting is the production of ceded and assumed reinsurance figures under two or more accounting bases at each close.
IFRS 17 covers insurance contracts an entity issues and reinsurance contracts it holds, says the IFRS 17 Project Summary.
The IFRS Foundation's IFRS 17 page states it applies from periods beginning on or after 1 January 2023.
Local GAAP and statutory rules often keep older concepts, such as an unearned premium reserve. These vary by country, so this article keeps them general.
How Does Each Treaty Data Element Map to IFRS 17 and Local GAAP?
Each treaty data element maps to IFRS 17 and local GAAP through different rules. The IFRS 17 column follows the IFRS Foundation's Effects Analysis.
| Treaty data element | IFRS 17 (reinsurance held) | Local GAAP (typical, varies) |
|---|---|---|
| Treaty and underlying start dates | Proportionate cover: recognised from the later of the coverage start and the underlying contracts' recognition | Often booked from treaty inception or as accounts arrive |
| Ceded premium | Part of fulfilment cash flows, or premium-based under the simplified approach | Ceded written premium with an unearned premium reserve |
| Premium payable, claims receivable | Included in measuring the reinsurance contract | Usually separate payables and receivables |
| Reinsurer default risk | Fulfilment cash flows reflect the reinsurer's non-performance risk | Often a separate credit or bad debt provision |
| Net gain or cost at purchase | Recognised as a contractual service margin; net cost for past events goes to profit or loss at once | Usually spread through premium earning |
| Grouping | Profitability groups within portfolios, contracts no more than one year apart | Often by class or treaty |
| Ceded claims and reserves | Measured on a discounted basis as part of the reinsurance asset | Ceded share of case and IBNR reserves; discounting varies |
| Results presentation | Insurance service result separate from insurance finance income or expenses | Often ceded premium and recoveries in a technical account |
The Effects Analysis also states that the variable fee approach cannot be applied to reinsurance contracts held or issued.
Which Treaty Data Fields Must Be Captured Once for Both Bases?
Treaty data fields that must be captured once are the ones both bases consume, even if each uses them differently.
| Field | IFRS 17 use | Local GAAP use |
|---|---|---|
| Treaty coverage dates and basis | Recognition date and coverage period | Earning period |
| Underlying policy inception dates | Recognition of proportionate cover | Earning of ceded premium |
| Reinsurer and share | Non-performance risk per reinsurer | Credit provision and settlement |
| Ceded premium by period | Cash flows or simplified approach | Written and earned premium |
| Ceded claims by accident date | Incurred claims measurement | Ceded reserves |
| Settlement status | Inside the contract measurement | Receivables and payables |
| Treaty year and portfolio | Grouping and annual cohorts | Class reporting |
If two teams keep separate copies of these fields, the gap becomes the problem described in reporting the same treaty differently.
Where Do Multi-GAAP Reinsurance Figures Diverge?
Multi-GAAP reinsurance figures diverge at a few predictable points. Each one should be explained by rule, not by data.
Why does the recognition date split IFRS 17 from local figures?
The recognition date splits IFRS 17 from local figures because proportionate cover may follow the underlying contracts.
Local books, by contrast, may start at treaty inception.
A quota share starting 1 January can show a full-year ceded premium estimate locally while IFRS 17 covers only underlying contracts recognised so far.
Later amendments added a nuance where underlying contracts are onerous. Confirm the current wording with your auditors.
Why do premium and claims balances look different under IFRS 17?
Premium and claims balances look different under IFRS 17 because the Effects Analysis says such amounts are included in measuring the contracts.
Local balance sheets often show reinsurance payables and receivables as separate lines. The same settlement status field feeds both views.
Why does IFRS 17 grouping create different subtotals?
IFRS 17 grouping creates different subtotals because contracts are split by profitability and issued no more than one year apart.
A local report by class or treaty will not add up to the IFRS 17 groups unless every ceded line carries a treaty year and portfolio tag.
Why does reinsurer default risk change the reinsurance asset?
Reinsurer default risk changes the reinsurance asset because IFRS 17 builds it into fulfilment cash flows, per reinsurer.
Local regimes may hold a separate provision instead. Both need reinsurer identity and share on every ceded line.
Why do onerous underlying contracts need special care?
Onerous underlying contracts need special care because later amendments added a loss-recovery component for reinsurance held.
Our guide to the IFRS 17 loss-recovery component explains it.
How Does One Quota Share Feed Both Bases at Quarter End?
One quota share feeds both bases at quarter end from the same bordereau lines, with different rules applied. The example is illustrative.
A cedent buys a 40% quota share on a risks-attaching basis from 1 January 2026. Reinsurer X takes 60% of the treaty and Reinsurer Y 40%.
Underlying annual policies of 1,000,000 gross premium are written each month from January to March. Ceded premium is 1,200,000.
| Step | Figure | Basis use |
|---|---|---|
| Ceded written premium | 1,200,000 (40% of 3,000,000) | Local written premium |
| Earned by 31 March, mid-month convention | 150,000 (4.5/12 of 400,000 monthly ceded) | Local earned premium |
| Ceded unearned premium | 1,050,000 | Local unearned premium reserve |
| Underlying contracts covered at 31 March | January to March inceptions only | IFRS 17 recognition scope |
| Reinsurer X share | 720,000 (60%) | IFRS 17 non-performance risk; local credit view |
| Reinsurer Y share | 480,000 (40%) | IFRS 17 non-performance risk; local credit view |
The earned figure uses mid-month inception: January earns 2.5 months, February 1.5 and March 0.5, or 4.5 of 12 months per 400,000 written.
Both bases start from the same 1,200,000 and the same 720,000 and 480,000 split. Any other difference must be traceable to a rule.
How Does Insurnest Support Multi-GAAP Reinsurance Reporting?
Insurnest supports the shared data layer of multi-GAAP reinsurance reporting. It does not produce IFRS 17 or local GAAP figures.
Bordereaux Calculation & Reconciliation maintains participation percentages and allocates premium and claims by reinsurer share.
It calculates reinsurer-level net positions and compares them with bordereaux, master data, premium and claim registers and settlement records.
Each reinsurer shows reconciled or variance to investigate. Measurement, grouping, discounting and disclosures stay with finance and actuarial teams.
Tracing each figure to its source is covered in reinsurance data lineage.
What Should CFOs Fix Before the Next Dual Close?
CFOs should fix the shared ceded dataset before the next dual close, starting with one large proportional treaty.
- List every field each basis uses. Mark where IFRS 17 and local teams hold separate copies.
- Capture underlying inception dates. Without them, proportionate recognition cannot be evidenced.
- Hold reinsurer and share on every line. Both non-performance risk and credit provisions need it.
- Reconcile before measuring. Tie ceded premium and claims to the registers by reinsurer.
- Write the difference bridge. Each line should name the rule that causes it.
Ceded premium earning conventions are covered in earned premium calculation.
Key Terms
- Reinsurance contract held: A reinsurance contract bought by the entity, such as a cedent's quota share.
- Contractual service margin: The IFRS 17 measure of unearned profit, or for reinsurance held, net gain or cost.
- Non-performance risk: The risk that a reinsurer fails to pay what it owes.
- Unearned premium reserve: The part of written premium relating to cover not yet provided.
- Fulfilment cash flows: Discounted, risk-adjusted estimates of future cash flows under a contract.
Sources
- IFRS Foundation: IFRS 17 Insurance Contracts
- IFRS Foundation: IFRS 17 Project Summary (May 2017)
- IFRS Foundation: IFRS 17 Effects Analysis (May 2017)
- Insurnest: Bordereaux Calculation & Reconciliation
Frequently Asked Questions
What is multi-GAAP reinsurance reporting?
Multi-GAAP reinsurance reporting is producing reinsurance figures under more than one accounting basis, such as IFRS 17 for group accounts and a local GAAP for statutory accounts, from the same treaty, premium and claims data. The aim is one dataset with two sets of rules applied.
How does IFRS 17 treat reinsurance contracts held?
IFRS 17 treats reinsurance contracts held using the general model with modifications. The IFRS Foundation's Effects Analysis lists three: the recognition date, fulfilment cash flows that reflect the reinsurer's non-performance risk, and a contractual service margin for any net gain or loss at initial recognition.
When is a reinsurance contract held recognised under IFRS 17?
A group of reinsurance contracts held covering proportionate losses is recognised from the later of the start of its coverage period and the initial recognition of the underlying contracts. Other reinsurance held is recognised from the start of its coverage period, according to the IFRS Foundation's Effects Analysis.
Why do IFRS 17 and local GAAP reinsurance figures differ?
IFRS 17 and local GAAP reinsurance figures differ because of recognition dates, discounting, grouping, reinsurer default risk and how receivables and payables are presented. Local rules vary by country, so each difference should be mapped field by field rather than assumed.
Can the variable fee approach be used for reinsurance under IFRS 17?
The variable fee approach cannot be used for reinsurance under IFRS 17. The IFRS Foundation's Effects Analysis states that a company cannot apply it to reinsurance contracts issued or to reinsurance contracts held, so the general model or the simplified approach applies instead.
How do you report reinsurance under IFRS 17 and local GAAP from one dataset?
To report reinsurance under IFRS 17 and local GAAP from one dataset, capture each treaty, underlying inception date, reinsurer share, premium, claim and settlement status once, reconcile them to registers, then apply each basis's rules in separate calculation layers that tie back to the same totals.
Which treaty data fields matter most for IFRS 17 reinsurance?
The treaty data fields that matter most for IFRS 17 reinsurance are coverage dates, underlying inception dates, treaty basis, reinsurer identity and share, expected cash flows by period, and settlement status. These drive recognition, grouping, non-performance risk and the measurement of the reinsurance asset.
Does Insurnest produce IFRS 17 or local GAAP reports?
Insurnest does not produce IFRS 17 or local GAAP reports. Its Bordereaux Calculation & Reconciliation allocates premium and claims by reinsurer share and compares the results against bordereaux, registers and settlement records, giving finance teams one reconciled ceded dataset for both bases.

Hitul Mistry
CEO, Insurnest
An InsurTech leader with more than a decade of experience across insurance and technology, focused on solving business problems with the help of technology. Has worked with brokers, insurance carriers, and reinsurance firms across the India, UAE, and US markets.
View LinkedIn profile →