← FleetLedger blog

Stale claims reserves on the bordereau, and the true-up that wiped out the binder's margin

The claims manager who runs the delegated authority desk believes that a quiet claims bordereau is a good claims bordereau. No new large losses, reserves holding steady, status fields unchanged from last month. To the syndicate reading it from the other side, that flat line is not stability. It is a desk that has stopped reserving.

The wrong assumption is that a reserve only needs to move when the claim moves. It is the opposite. The reserve is the estimate, and the estimate decays the moment new information arrives and nobody updates the figure. A bodily injury claim on a fleet policy that sat at 5,000 outstanding for four months while the medicals came back at a multiple of that is not stable. It is wrong, and it is wrong in the syndicate's favour until the day it isn't.

What the claims bordereau tells the syndicate that the premium one doesn't

The premium bordereau tells the syndicate what was written. The claims bordereau is the only forward view of what was written turning into loss. Under the LIMOSS Claims Bordereaux SOP that governs delegated reporting in the London market, the reserve fields are the core of the file: outstanding, paid to date, and the movement between periods. Those columns are how the syndicate builds an incurred figure and projects it forward.

Drop the premium bordereau and the syndicate knows roughly what exposure it priced. Drop the claims bordereau, or send one with reserves that never move, and the syndicate is pricing next year's renewal and reporting this year's binder on numbers that describe a fleet program that is already deteriorating in the dark.

Why stale reserves distort binder loss ratios and capacity decisions

A loss ratio is incurred over earned premium. Incurred is paid plus outstanding reserves. If the outstanding column is stale, the numerator is understated, and the binder reads a loss ratio that looks like a winner. The syndicate's actuary works off what the bordereau reports. Lloyd's verifies, through the Signing Actuary in the solvency return, that the profit a syndicate claims on unearned premium is no greater than the actuarial view supports. That check only works if the underlying reserves are honest. Feed it stale figures and the whole chain prices off a fiction.

The damage is not confined to one quarter's report. Capacity for next year, the commission terms, the appetite to grow the line, all of it is set against a loss ratio that was never real. The claims manager who let the reserves drift didn't make the binder look good. They borrowed against next year's credibility and didn't write it down anywhere.

The true-up moment: how delayed reserving lands all at once

Reserves do not stay wrong forever. A reconciliation, an audit, a large claim that finally forces the file open, and every month of suppressed movement arrives in a single period. The loss ratio steps, not drifts. A binder that reported in the fifties suddenly clears seventy or eighty because two years of catch-up reserving landed in one true-up.

What makes that moment expensive is the timing. The margin that the true-up consumes was already booked, distributed, and in some cases paid out as profit commission. Clawing it back is harder than never having shown it. And the conversation with capacity is no longer about a number. It is about why the reporting was wrong for that long, which is a much worse conversation to have.

Reserve hygiene that keeps the binder's numbers believable

The fix is procedural, not heroic. A reserve is an estimate that has to be defended every reporting cycle, and a desk that treats it that way rarely produces a true-up large enough to surprise anyone.

FleetLedger holds the claims and the policy schedule for each fleet program in one place, so a reserve that has gone quiet shows up as an exception before it becomes a true-up. The point isn't a prettier bordereau. It is that the numbers you send capacity match the losses you actually carry, so the binder you report is the binder you have. See how FleetLedger keeps reserves honest.