Reinsurance

Large Loss Register: Template for One View of Big Claims

On this page

Last reviewed: November 2026

The biggest claims are often tracked in the most scattered way, with an email here and a spreadsheet there.

When the board asks what one event will cost net of reinsurance, the answer takes days.

A large loss register is one controlled list of every claim above an agreed trigger, with its estimate history, treaty split and expected recoveries.

It gives claims and risk leaders one live view of big claims across treaties.

Key Takeaways

  • Set triggers against retentions. A flat amount misses claims that matter to specific treaties.
  • Keep every estimate. The history of a loss tells you more than its latest figure.
  • Link each loss to every treaty it touches. Recoveries, reinstatements and notices follow from that link.
  • Give every entry an owner and a review date. An unreviewed entry is a stale entry.

What Is a Large Loss Register?

A large loss register is a single, controlled list of the claims that could move results, reserves or reinsurance recoveries.

It sits above the claims system, not instead of it.

The register is a management artefact. It answers three questions: what are our big losses, what are they worth now, and what will we recover?

What Should Trigger Entry to the Large Loss Register?

Entry to the large loss register should be triggered by size relative to retention, and by features that make a claim risky whatever its size.

TriggerIllustrative ruleWhy it matters
Size against retentionLatest gross estimate at or above 50% of the per risk retentionCatches claims before they reach the layer
EventAny claim coded to a named catastrophe or occurrenceLosses aggregate across policies
LitigationSuit filed or external counsel appointedEstimates can move sharply
Coverage disputeReservation of rights or declinature under reviewRecovery may be contested
Notification clauseTreaty requires notice at a set thresholdLate notice can put recovery at risk
Accumulation in group lifeSeveral deaths from one event in one schemeCatastrophe cover may respond

Why set the trigger against retention rather than a flat amount?

A trigger set against retention works because the same claim size means different things on different treaties.

A USD 2m claim is routine under a USD 10m retention. Under a USD 2.5m retention, it needs watching now.

What Fields Does a Large Loss Register Need?

A large loss register needs four groups of fields: identification, financials, treaty links and controls.

The four tables below form a reusable template.

Which identification fields come first?

Identification fields come first because every later figure must attach to one unambiguous loss.

FieldPurpose
Register IDUnique key that never changes
Cedent claim referenceLinks to the cedent's file and bordereaux
Event codeGroups claims from one catastrophe or occurrence
Date of lossTests the treaty period and any hours clause
Class and causeSupports aggregation and trend review
TerritoryTests territorial scope and currency
Insured or member referenceIdentifies the original policy or group member
StatusOpen, reopened, closed or disputed

Which financial fields should the register hold?

Financial fields should hold the latest position and enough history to explain how it got there.

FieldPurpose
CurrencyOriginal currency of the loss
Paid to dateCash already paid on the claim
Outstanding reserveRemaining case estimate
Gross incurredPaid plus outstanding
First estimate and dateBaseline for measuring creep
Previous estimate and dateShows the latest movement
Reason for movementOne line on why the estimate changed
Net retainedGross incurred less expected recoveries

The register should link each loss to every treaty it touches, with the layer and share that apply.

FieldPurpose
Treaty ID and layerIdentifies the cover that responds
Retention and limitDrives the ceded amount
Ceded amount by treatyExpected recovery per cover
Reinstatement premium dueCost of restoring the limit
Notice date to reinsurersEvidence the notification terms were met
Retrocession impactOnward recovery where it applies

Notice dates matter most where a claims cooperation clause sets conditions on recovery.

Which control fields keep the register honest?

Control fields keep the register honest by showing who owns each entry and when it was last challenged.

FieldPurpose
Claim ownerNamed handler accountable for the entry
Last review dateShows whether the entry is current
Next review dateDrives the review cycle
Approver of last movementEvidence of maker-checker control
Lead arrangementWho leads and who follows on the claim
Dispute flagMarks contested coverage or recovery

In the Lloyd's market, the Claims Lead Arrangements provide for a lead and second lead to act jointly on complex claims.

Recording who leads saves time when a large loss needs a decision.

How Does One Loss Look in the Register?

One loss in the register reads like a short story told in figures.

This hypothetical property claim sits under a USD 15m xs USD 5m per risk excess of loss treaty, fully placed.

DateGross incurred (USD m)Ceded to treaty (USD m)Net retained (USD m)Reason for movement
Month 16.01.05.0First notice
Month 312.07.05.0Adjuster's report
Month 618.013.05.0Business interruption added
Month 921.015.06.0Layer exhausted

The ceded amount is the gross loss above USD 5m, capped at USD 15m. At month 9, that is USD 16m capped to USD 15m, leaving USD 6m net.

The latest estimate is 3.5 times the first. Net retained stayed at the retention until the layer ran out.

A register showing only the latest figure would hide both facts.

Why keep the estimate history rather than overwrite it?

Estimate history matters because the pattern of revisions is an early warning in its own right.

In June 2024, Reinsurance News reported Swiss Re's call for an industry focus on European catastrophe loss creep.

One Italian hail estimate it cited rose from USD 2.2bn to USD 6bn.

Swiss Re pointed to a lack of up-to-date exposure and risk value data as a key cause. A register that keeps first estimates lets you measure your own creep.

How Do You Keep the Register Current?

The register stays current only when updates are tied to events and reviews are tied to a calendar. The timings below are illustrative.

WhenWhoWhat
Any estimate movement above an agreed amountClaim ownerUpdate financials and reason within 2 working days
MonthlyClaims team leadsReview every open entry and confirm the next review date
QuarterlyLarge loss committeeChallenge movements, recoveries and disputes
Quarter-end closeFinance and actuarialReconcile register totals to the claims ledger
Treaty renewalReinsurance buyerUse the register's history in renewal data

The quarter-end check matters most. The register and the reinsurance claims ledger must tell the same story.

Who should sign off on a movement?

A movement above an agreed amount should be signed off by someone other than the person who entered it.

Our guide to maker-checker in reinsurance claims explains how to set that control up.

Where Does Insurnest Fit for Large Losses?

Insurnest fits large loss work for group life and credit life reinsurance claims, which is what the Reinsurance Claim Core Platform is built for.

The platform registers claims against the relevant treaty and member census and attaches supporting documents.

It applies configured treaty, eligibility, validation and claim-quantum rules. Approvals follow maker-checker and configured authority limits.

It configures treaty structures, counterparties, shares and retrocession, and its ledger tracks retrocession.

Original bookings and later adjustments stay visible as separate movements, which is the estimate history this template asks for.

Structured claims and period reporting includes closing balances by currency, much like a period movement report.

For property and casualty large losses, the template still applies, but the platform is not positioned for those classes.

What will the register still need people for?

The register will still need people for every judgement call: reserve adequacy, coverage positions and whether claims aggregate into one event.

Authorised claims professionals make final decisions. The platform records and controls those decisions, but does not make them.

How Should a CRO Start the Register This Quarter?

A CRO can start the register this quarter without waiting for a new system. Five steps are enough.

  1. Agree the triggers. Set entry rules per treaty, relative to retention.
  2. Load the current population. Add every open claim that meets a trigger today.
  3. Back-fill first estimates. Capture the first estimate and its date for each entry.
  4. Name an owner per entry. No entry goes live without a person and a next review date.
  5. Run the first committee. Review the top ten by movement, not just by size.

Key Terms

  • Large loss: A claim that crosses an agreed size or risk trigger for closer oversight.
  • Loss creep: The upward drift of a loss estimate after the first report.
  • Retention: The amount kept before an excess of loss treaty responds.
  • Reinstatement premium: The premium paid to restore an excess of loss limit after a loss.
  • Event code: A reference that groups claims arising from one catastrophe or occurrence.

Sources

Frequently Asked Questions

What is a large loss register?

A large loss register is a single, controlled list of every claim above an agreed size or risk trigger, across all treaties and classes. It records the loss, its estimate history, the treaties it touches, expected recoveries and the owner, so claims and risk leaders see big exposures in one place.

Why do reinsurers and cedents need a large loss register?

Reinsurers and cedents need a large loss register because big claims drive volatility, reserve movements and reinsurance recoveries. Without one view, the same loss can be tracked differently by claims, actuarial and finance teams, and estimate creep or a missed treaty notification is spotted too late.

When should a claim enter the large loss register?

A claim should enter the large loss register when it crosses a trigger set relative to the relevant retention, such as half the excess of loss attachment, or when it is litigated, coverage is disputed or it may aggregate into an event. Entry should be based on the latest estimate, not paid amounts.

Who should own the large loss register?

The large loss register is best owned by the Chief Claims Officer, with named claims handlers updating each entry. The CRO uses it for exposure and reserve oversight, finance uses it for recovery and cash planning, and a large loss committee reviews movements on a fixed cycle.

Which metrics should a large loss register report?

A large loss register should report the number of open large losses, total incurred and movement since the last review, the ratio of current to first estimate, expected recoveries by treaty, entries without a review in 90 days, and notices outstanding to reinsurers. Each metric needs a named owner.

Can automation maintain a large loss register?

Automation can maintain much of a large loss register by flagging claims that cross triggers, recording every estimate as a dated movement and linking losses to treaties. Reserve judgement, coverage positions and aggregation decisions still need experienced claims professionals, so automation should feed the register rather than decide what it says.

How does a large loss register differ from a claims ledger?

A large loss register differs from a claims ledger in purpose. The ledger records every financial movement on every claim for accounting, while the register is a management view of the few claims that matter most, adding estimate history, treaty impact, recovery expectations, ownership and review dates.

Should a large loss register be a spreadsheet or a system?

A large loss register can start as a controlled spreadsheet if it has fixed fields, one owner and dated estimate history. Once it must link claims to treaty shares, approvals and retrocession, a claims system with structured records is safer, because spreadsheets lose history when cells are overwritten.

Hitul Mistry

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 →
ShareLinkedInX

Read our latest blogs and research

Featured Resources

Reinsurance

Reinsurance Claims Ledger: Track Every Claim Movement

A reinsurance claims ledger records every paid, outstanding and adjusted amount as its own movement. Learn the structure, split chain and controls that matter.

Read more
Reinsurance

Granular Claims Triage for Treaty Recoveries: Prioritising Dollars at Risk, Not Inbox Order

Granular claims triage for treaty recoveries prioritises dollars at risk over inbox order. Learn how recovery triage ranking by financial exposure accelerates settlements and protects treaty results.

Read more
Reinsurance

Reinsurance Claims Period Movement Report: A Clear Guide

A reinsurance claims period movement report explains every change from opening to closing claims balances. See how to build one that answers the board quickly.

Read more

Meet Our Innovators:

We aim to revolutionize how businesses operate through digital technology driving industry growth and positioning ourselves as global leaders.

circle basecircle base
Pioneering Digital Solutions in Insurance

Insurnest

Empowering insurers, re-insurers, and brokers to excel with innovative technology.

Insurnest specializes in digital solutions for the insurance sector, helping insurers, re-insurers, and brokers enhance operations and customer experiences with cutting-edge technology. Our deep industry expertise enables us to address unique challenges and drive competitiveness in a dynamic market.

Get in Touch with us

Ready to transform your business? Contact us now!

We respond within one business day.