Back to Insights
Industry Analysis

Reinsurance recoveries: where claims money sits between two ledgers

October 21, 2026
ESSAM Team
Reinsurance recoveries: where claims money sits between two ledgers

A reinsurance recovery passes through five handoffs between the day the claim is paid and the day the cash is applied. Most of the delay sits in the gap between claims and finance, and it starts with how the cedant's numbers arrive.

Your loss ratio looks fine. Your recovery ageing is the number that tells you what the book actually cost.

What is a reinsurance recovery, and why does it age?

A reinsurance recovery is money the ceding insurer (the cedant) has already paid to a policyholder and is entitled to claim back from its reinsurer. The insurer books it as a receivable. Receivables age.

How the claim is shared depends on the placement:

  • Under a proportional treaty, such as quota share or surplus, the reinsurer takes an agreed share of premiums and claims. The cedant reports both on periodic bordereaux.
  • Under a non-proportional treaty, such as excess of loss, the recovery is triggered when a loss crosses an agreed retention. The cedant documents that loss to the reinsurer.
  • Under a facultative placement, a single risk is reinsured on its own terms and claimed individually.

The mechanics differ by wording, so check your own treaties. The loop underneath is the same in all three: a claim is paid, someone tells the reinsurer, a bordereau carries the numbers, and cash comes back.

A bordereau is a structured schedule of premiums or claims that the cedant sends to the reinsurer under a treaty. Claims bordereaux support recoveries. Premium bordereaux support the account. Both need to reconcile to the cedant's own ledgers before anyone accepts them.

Why are reinsurance recoveries a data-arrival process, not a claims process?

Most teams hand recoveries to the claims function. That is a mistake of category. By the time a recovery exists, the claim is settled. What remains is information: the paid amount, the treaty it falls under, the loss date, the reserve movement, and the supporting documents.

The reinsurer pays when that information arrives in a form it can accept. So the recovery clock does not start at the date of payment. It starts when the numbers arrive complete, in one format, and reconciled to what was paid.

That is the argument of this post. Reinsurance recoveries are a data-arrival process. Fix how the numbers arrive and the recovery clock starts working.

The treaty defines when money is due. Nothing in your process defines when the paperwork starts moving.

Try a simple test. Ask three people how many open recoveries you have. If you get three answers, you don't have a process. You have an inbox.

What is the five-handoff recovery map?

Every recovery loop can be described as five handoffs. Treat the map below as a working draft of your own loop, not a standard. Practice varies by insurer and by treaty.

# Handoff Usually owned by What must arrive Where it stalls
1 Claim paid Claims operations Paid amount, payment date, treaty reference The treaty is not tagged at payment, so nobody knows a recovery exists
2 Notification or advice Claims, sometimes technical accounts Loss advice, reserve, cause of loss, documents The advice waits for the next bordereau cycle instead of leaving on its own
3 Bordereau build Nobody (ownership gap) Paid claims for the period, mapped to treaty, in the agreed layout Rebuilt each month from a claims extract, a spreadsheet, and an email trail
4 Cedant submission Reinsurance or technical accounts Bordereau, supporting documents, account statement Queried for format or mismatches, then sent back to handoff 3
5 Cash application Finance Remittance matched to specific recoveries Cash arrives net and unallocated, and the claim stays open on the claims side

Where is the ownership gap?

There are two, and both are on the border between claims and finance.

The first is handoff 3. Claims paid the money, so claims believes the bordereau is a finance job. Finance expects the cash, so finance believes the bordereau is a claims job. In practice, whoever is least busy that month builds it.

The second is the loop back from handoff 5 to handoff 1. Finance applies the cash. The claims record does not close. Six months later, nobody can say which recoveries are open, which is how you get three answers to one question.

On the reinsurer side, the map runs in mirror. A bordereau is received, validated, accepted, and paid. The same gap appears between the claims team that validates and the finance team that pays. Labuan reinsurers and domestic inward-treaty writers sit on the other end of the same bordereaux that cedants in Malaysia and Singapore build.

How do treaty terms set the clock?

Treaties set the outer clock. They typically define reporting periods for accounts, how and when large losses must be notified, and when balances are settled once accepted. The specific periods vary by wording, and we will not quote any here.

Your own cut-offs are the inner clock. These include the day the claims extract is frozen, the day the bordereau is built, who signs it, and the day it leaves the building.

Most cedants manage the outer clock well because a contract enforces it. The inner clock is where the days go, because nothing enforces it.

A common objection runs: "We can't chase recoveries faster than the treaty allows." That is true about the clock and false about the queue. The treaty fixes when the reinsurer must pay. It does not fix how long a paid claim waits before anyone builds the bordereau.

Insurers in Malaysia operate under Bank Negara Malaysia supervision, and in Singapore under the Monetary Authority of Singapore. Reinsurance recoverables sit on the balance sheet that supervisors and auditors read. Ageing is a finance and risk concern as well as an operations one.

Why does the loss ratio hide a slow recovery?

When a claim is paid, the net result typically recognises the expected recovery straight away. A recovery that is late, queried, or disputed carries on at full value until someone tests it.

The reported net loss ratio therefore shows what the treaty says should come back, not what has come back. Recovery ageing shows the difference earlier.

That is why recovery cycle time works as a leading indicator of reporting discipline. Late bordereaux, unscheduled bordereaux, and bordereaux in three formats all signal the same condition. Recoveries are sitting as an ageing receivable that nobody owns. The loss ratio can look healthy for several quarters while the economics are already written.

Claims leakage analysis looks at money the insurer pays out wrongly. This is the other side: money the insurer has paid correctly and has not yet collected. If you have worked through claims leakage in process analytics, treat recovery ageing as the follow-on measure.

What is the arrival-quality test?

Before improving any recovery, test how the numbers arrive. Three questions, asked of each treaty:

  1. Is it scheduled? Does a fixed cut-off date and send date exist, written down, and does the bordereau leave on it?
  2. Is it one format? Does every bordereau for that treaty use the same columns, the same treaty codes, and the same definition of "paid"?
  3. Is it reconciled to paid claims? Does the bordereau total tie to the paid-claims ledger before it is sent, with exceptions listed?

Score each treaty. Three yeses mean the recovery clock is working. One or two yeses mean the delay is in your arrival process. Zero yeses mean the inbox is your process.

Most cedants find the answers differ by treaty type. A quota share running on a monthly template may pass all three while a facultative book run from email passes none. That is useful. It tells you where to start.

How do you build a recovery ageing worksheet?

Recovery ageing measures time from claim payment to cash received, split by the state the recovery is in. It is not claim ageing. Claim ageing ends when the claim closes. Recovery ageing begins there.

Use one row per recovery, with these columns:

Treaty Claim ref Claim paid Advice sent Bordereau accepted Cash received Days: paid to advice Days: advice to accepted Days: accepted to cash Total days
(treaty name) (ref) (date) (date) (date) (date) (calc) (calc) (calc) (calc)

Four rules keep the worksheet honest:

  • Use the paid date, not the notification date. The clock starts when your money leaves.
  • Count open items. For anything without cash received, calculate days to today. Open items are the point of the exercise.
  • Group by treaty type. Proportional, non-proportional, and facultative recoveries age differently.
  • Name one owner. Whoever holds the worksheet holds the answer to "how many open recoveries do we have?"

Worked example (illustrative)

Consider a team that pays a facultative claim on 12 March. The recovery advice leaves the building on 9 June, because the bordereau is rebuilt each month from three spreadsheets and the advice waits behind it. The reinsurer accepts on 4 July. Cash arrives on 18 August. This is a constructed example, not a client case.

Treaty Claim paid Advice sent Bordereau accepted Cash received Paid to advice Advice to accepted Accepted to cash Total
Facultative (example) 12 Mar 9 Jun 4 Jul 18 Aug 89 days 25 days 45 days 159 days

Read the row from left to right. The cedant's own state, paid to advice, took 89 days, which is more than half the total. The reinsurer's review took 25 days. Cash application took 45.

A team looking only at the treaty clock would see a reinsurer that paid within terms. A team looking at the worksheet sees that the first 89 days belonged to the cedant's own arrival process. That is where to work.

What are the three arrival fixes that need no system change?

You can improve arrival quality this month without buying or configuring anything.

1. Fix the calendar

Set one cut-off date and one send date per treaty, and write them down. Freeze the claims extract on the cut-off date. Move large-loss advices out of the bordereau cycle, so they leave when the claim is paid.

2. Fix the format

Agree one template per treaty type with the counterparty, in writing. Fix the columns, the treaty codes, and the definition of "paid". Retire every variant. This is the Simplify & Standardise action applied to a spreadsheet.

3. Fix the reconciliation point

Before the bordereau leaves, tie its total to the paid-claims ledger. Put a named person's sign-off on it. List exceptions one line each. Catching a mismatch before submission costs minutes. Catching it after a query costs a cycle. The pattern is the same one described in reconciliation breaks investigation, applied at the point where the break is created.

Once these three are stable, add recovery ageing to your close routine. The financial close and month-end acceleration post covers where a status line like this belongs on a close checklist.

Where do E-S-S-A-M and the 7-step cycle fit?

ESSAM classifies every step of a process with the E-S-S-A-M framework: Eliminate, Simplify & Standardise, Automate, Migrate. Automate is the fourth action on purpose. You design before you automate.

Applied to a recovery loop:

  • Eliminate: the re-keying of the same bordereau into the claims system and again into finance, and the email chasing that exists only because nobody can see status.
  • Simplify & Standardise: one bordereau template and one cadence per treaty type.
  • Automate: extraction and reconciliation, once the format is stable. Automating three formats gives you three automations to maintain.
  • Migrate: move the cut-off checklist and status prompts to where the team already works.

In the 7-step AI Lean Cycle (Baseline, Map, Analyse waste, Optimise, Document, Deploy, Improve), the Baseline step is recovery ageing, not claim ageing. The worksheet above is that baseline.

ESSAM captures a process in a single conversation. For a recovery loop, that means mapping the path across the claims system, the spreadsheet, and the email trail in one session, and producing one recovery map per treaty type. The result goes to the floor as a living work instruction over WhatsApp, the channel Singapore and Malaysia teams already use, and the audit view shows before and after.

The one real ESSAM client result shows why the order matters. A Kuwait bank's procurement cycle went from 139 days to 57, a 59% reduction, with 82 days of work retired and the same headcount. That outcome was reached after Eliminate and Simplify, before any automation. It is a real ESSAM case, and it is a procurement cycle only. We make no claim that reinsurance recoveries will move by the same amount. The point is the order of operations.

To see how this fits into a wider practice, read what an AI process engineer does or browse the ESSAM features.

Frequently asked questions

What is bordereau reconciliation?

Bordereau reconciliation is the check that a premium or claims bordereau agrees with the cedant's own ledgers, and later with the reinsurer's account. It confirms the right claims, in the right amounts, under the right treaty, are on the schedule.

How long should a reinsurance recovery take?

It depends on the treaty wording and on the counterparty, so no single figure applies. Measure your own. The worksheet gives you days in each state, and the largest number is usually inside your own process.

What is the difference between recovery ageing and claim ageing?

Claim ageing measures time to settle the claim with the policyholder. Recovery ageing measures time from that payment to cash received from the reinsurer. The second starts when the first ends.

Who should own the bordereau?

One named owner per treaty, agreed between claims and finance. Which function holds it matters less than the fact that someone does. The ownership gap, not the choice of function, is what causes delay.

The recovery clock starts when the numbers arrive

The treaty gives you the outer clock. You control the inner one. Schedule the bordereau, put it in one format, reconcile it to paid claims, and measure the days in each state.

Start by mapping your own recovery loop, treaty by treaty, in a single session at apac.essam.ai

← All InsightsESSAM Insights