Reinsurance Flagging on Claims: Trigger Rules That Work
On this page
- Key Takeaways
- Which Trigger Rules Should Drive Reinsurance Flagging on Claims?
- What Happens When a Group Life Event Claim Is Never Flagged?
- Which Detection Rules Catch Missed Reinsurance Flags?
- What Should a Reinsurance Flag Record on Each Claim?
- How Does Insurnest Support Reinsurance Flagging on Group Life and Credit Life Claims?
- Where Should a Head of Claims Start on Reinsurance Flagging?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
Six employees of one scheme die in the same road accident, and six handlers register six ordinary claims.
Eleven months later, an actuary asks why the group life catastrophe cover shows no recovery for the year.
Reinsurance flagging on claims is the cedent's process of marking every claim that may involve a reinsurer, at intake and whenever it changes.
Getting it right means written trigger rules, run at registration and on every reserve movement, with a daily sweep for event aggregates.
Key Takeaways
- Flags must follow treaty triggers. Write the rules from the treaty, not from habit.
- Single claims hide event losses. Only grouping by event shows the aggregate.
- Flag below the retention. Waiting until a claim enters the layer is too late for notice.
- Re-flag on every movement. A reserve increase can create reinsurance interest.
- Unflagged recoveries stay unbilled. Nobody chases a recovery nobody knows about.
Which Trigger Rules Should Drive Reinsurance Flagging on Claims?
The trigger rules that should drive reinsurance flagging on claims come from four sources: retentions, events, treaty clauses and class.
The table is illustrative. Set percentages and amounts from your own treaty wordings.
| Trigger | Rule | Example | Flag raised |
|---|---|---|---|
| Threshold vs retention | Reserve reaches a set % of per-life or per-risk retention | 250,000 reserve on a 400,000 retention (62.5%) | Notify and monitor |
| Sum assured above retention | Benefit exceeds cedent's per-life retention | 650,000 benefit on a 400,000 retention | Surplus cession of 250,000 |
| Above free cover limit | Benefit above the scheme's free cover limit | No underwriting decision on file | Check acceptance before ceding |
| Event code | Two or more claims share a date, cause and place | Claims linked to one road accident | Event aggregate review |
| Claims control or co-operation clause | Treaty requires notice or consent for this claim | Litigation or ex gratia proposed | Consent check |
| Class or treaty mapping | Claim falls under a facultative or specific treaty | Credit life portfolio under its own quota share | Link to the right treaty |
| Same life, several covers | One life on several schemes or loans | Two loans for one borrower | Aggregate against retention |
Notification clauses often use a percentage of retention, but wordings differ. Some set a fixed amount or name specific injury or claim types.
How should event codes be assigned to claims?
Event codes should be assigned to claims at registration, using the market code where one exists and an internal event identifier otherwise.
Lloyd's catastrophe codes are built from the year of the event plus a letter suffix.
Lloyd's says they help identify the interests involved and are not intended to bind underwriters or their reinsurers.
Most group life events, such as one road accident, will never receive a market code. An internal event ID based on date, cause and location fills the gap.
What Happens When a Group Life Event Claim Is Never Flagged?
When a group life event claim is never flagged, every claim looks small, so the event recovery is not calculated, notified or billed.
The example is illustrative, in USD. A cedent retains 400,000 per life under a surplus treaty.
It also buys group life catastrophe excess of loss cover of 2,000,000 excess of 1,000,000 per event, needing at least three lives.
How large is the missed event recovery in this example?
The missed event recovery in this example is 300,000, the event total above the 1,000,000 retention.
| Life | Sum assured | Above 400,000 per-life retention? |
|---|---|---|
| 1 | 220,000 | No |
| 2 | 180,000 | No |
| 3 | 260,000 | No |
| 4 | 150,000 | No |
| 5 | 300,000 | No |
| 6 | 190,000 | No |
| Event total | 1,300,000 | Six lives; above the three-life minimum |
No single claim reaches the surplus treaty, so no per-life flag fires.
The event total is 220,000 + 180,000 + 260,000 + 150,000 + 300,000 + 190,000 = 1,300,000.
The catastrophe layer pays 1,300,000 − 1,000,000 = 300,000. It is well within the 2,000,000 limit.
Why did the reinsurance flag fail in this group life event?
The reinsurance flag failed in this group life event because the rules looked at claims one by one, and nobody recorded the shared cause.
Each death was registered on a different day by a different handler. Cause was entered as free text, and no event identifier existed.
By the time the actuary noticed, the treaty's notice period may have passed. Whether late notice reduces the recovery depends on the wording.
How can a credit life claim slip past the reinsurance flag?
A credit life claim can slip past the reinsurance flag when one borrower holds several loans and each is checked alone.
Suppose a borrower dies holding two insured loans with outstanding balances of 180,000 and 260,000. The cedent's per-life retention is again 400,000.
Neither loan reaches the retention. Together they total 440,000, so 40,000 should be ceded if the treaty aggregates by life.
Matching borrowers by identity number at registration catches this. Matching by loan account number does not.
Our post on a claims notice that gets lost covers what happens after the flag, when notice must reach reinsurers.
Which Detection Rules Catch Missed Reinsurance Flags?
Detection rules that catch missed reinsurance flags test the claims register from a different angle than the intake rules did.
- Re-run triggers on every reserve change. A claim crossing a threshold later gets flagged on the day it crosses.
- Sweep daily for shared events. Group claims by event date, cause and employer or location.
- Compare flags to ceded listings monthly. Every flagged claim should appear in the ceded bordereau.
- Alert on silent treaties. A treaty with claims but no flags for a quarter needs review.
- Check aggregation by life. Match identity numbers across schemes and loans.
- Review free text. Search causes for accident, fire, flood or similar event words.
What Should a Reinsurance Flag Record on Each Claim?
A reinsurance flag should record why it was raised and what must happen next, so anyone opening the claim can act on it.
| Field | Purpose |
|---|---|
| Flag reason | The trigger rule that fired, such as threshold, event or clause |
| Treaty and underwriting year | Which contract responds |
| Date flagged and by whom | Rule or handler, for audit of timing |
| Event identifier | Market code or internal event ID, if any |
| Notice due date | Taken from the treaty's notification clause |
| Consent required | Yes or no, with the clause reference |
| Estimated ceded amount | Current reserve above retention, by treaty |
| Status | Open, notified, recovered or closed with reason |
A flag with no notice date or status is only a label. The fields turn it into a task with an owner.
Keep the flag history as well. If a flag is removed, record who removed it, when and why, because a reinsurer or auditor may later ask how that decision was made.
Large flagged claims should also sit on the large loss register, so finance and actuarial see the same list.
How Does Insurnest Support Reinsurance Flagging on Group Life and Credit Life Claims?
Insurnest supports reinsurance flagging on group life and credit life claims through the Reinsurance Claim Core Platform.
Each claim is registered against its treaty and member. A rule engine applies treaty, eligibility, policy, validation and claim-quantum rules.
The financial ledger records claim amount, cedent retention, ceded amount, retrocession and net retained. A work queue shows rule outcomes and missing information.
It covers group life and credit life only. It does not notify reinsurers, and cross-claim event aggregation is not a stated feature, so keep the daily event sweep.
Where Should a Head of Claims Start on Reinsurance Flagging?
A head of claims should start on reinsurance flagging by testing last year's claims against triggers written from today's treaties.
- Write the trigger list per treaty. Thresholds, events, clauses and classes, with the source clause.
- Re-run last year's claims. Count the claims that should have been flagged and were not.
- Add an event field to intake. Make it mandatory for accident and disaster causes.
- Tie flags to the ledger. Every flag should end in a ceded amount or a recorded reason for none.
How flagged claims become ledger entries is covered in the reinsurance claims ledger guide.
For benefits above the free cover limit, see free cover limit monitoring.
Key Terms
- Reinsurance flag: A marker on a claim showing possible reinsurance interest and why.
- Per-life retention: The amount a cedent keeps on any one life before a surplus treaty responds.
- Event aggregate: The total of claims from one event, tested against an event excess of loss cover.
- Catastrophe code: A market code identifying claims from one major loss event.
Sources
- Lloyd's: Catastrophe codes
- Insurnest: Reinsurance Claim Core Platform
Frequently Asked Questions
What is reinsurance flagging on claims?
Reinsurance flagging on claims is the cedent's process of marking each claim that may involve a reinsurer, at intake and whenever the claim changes. The flag links the claim to the treaty, triggers notice and consent checks, and makes sure the recovery is calculated and collected.
When should a claim be flagged for reinsurance?
A claim should be flagged for reinsurance when it meets a treaty trigger, such as a reserve above a set percentage of retention, a sum assured above retention, a link to a catastrophe event, a claims control clause, or a class covered by facultative reinsurance.
What threshold should trigger a reinsurance flag?
The threshold that should trigger a reinsurance flag is the one the treaty's notification clause sets, often expressed as a percentage of the retention. Where no figure is set, many cedents choose a percentage below the retention so claims are flagged before they reach the layer.
Why do catastrophe event claims get missed for reinsurance?
Catastrophe event claims get missed for reinsurance because each claim alone sits below the retention. Only the aggregate of claims from one event reaches an event excess of loss cover, so claims must be grouped by event code or internal event identifier to be seen.
What are Lloyd's catastrophe codes?
Lloyd's catastrophe codes are market codes assigned to major loss events, built from the year of the event and a letter suffix. Lloyd's says they help underwriters identify the interests involved and are not intended to bind underwriters or their reinsurers.
How do you flag claims for reinsurance at intake?
To flag claims for reinsurance at intake, link every claim to its treaty and insured life or risk, test it against the trigger rules for retention, event, clause and class, record the flag reason, and re-run the same rules each time the reserve or facts change.
Should reinsurance flags be re-checked after intake?
Reinsurance flags should be re-checked after intake because reserves rise, causes become clear and related claims arrive later. A claim that passed the rules on day one can cross a threshold or join an event aggregate weeks after registration.
What happens if a claim with reinsurance interest is not flagged?
When a claim with reinsurance interest is not flagged, notice to reinsurers can be late, consent may not be sought and the recovery may never be billed. Depending on the treaty wording, late notice can reduce or defeat the recovery.

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 →