By Yair Knijn · September 15, 2025

The self-insured retention that ate the budget: when the fleet's small claims were never aggregated

A CFO signs a renewal with a high self-insured retention because the premium line drops and the saving is visible on the first page of the binder. The assumption underneath that signature is the dangerous one: that a lower premium is a lower cost. It is not. The retention does not remove the loss, it moves the loss off the insurer's books and onto yours, one small claim at a time, into a layer that no one in finance is watching.

The premium saving is booked on day one. The retained losses arrive over the next twelve months, undated and unannounced, and that asymmetry is the whole trap.

How retention and deductible trade premium for retained risk in fleet motor

A self-insured retention is not a discount. Under an SIR the insured is its own insurer below the retention amount: you investigate, you reserve, you settle, you pay, with no carrier involvement until a loss pierces the layer. A deductible looks similar from the driver's seat but behaves differently in the ledger, because the insurer usually pays the claim and then bills you back. Both are the same trade dressed two ways: you take premium off the income statement and put retained risk onto it.

For a fleet, that risk is not one big number. It is the bumper taps, the kerbed alloys, the third-party windscreen, the low-speed reversing dents that never reach the carrier at all. Each one sits below the retention. Each one is a real cash payment out of the operating budget. None of them generate the insurer paperwork that finance has been trained to treat as the signal that a loss occurred.

The aggregation blind spot: many small claims, no running total

The structure almost always carries an aggregate retention, an annual cap on how much retained loss you are meant to absorb before the policy starts catching the overflow. That cap is the entire economic case for the high retention. And it is the one number nobody is summing.

Claims below the line are handled in the field. A workshop invoice here, a third-party settlement there, a hire-car cost booked to operations rather than to insurance. The money leaves through fleet, maintenance and accounts payable, scattered across cost centres that each look reasonable in isolation. There is no running aggregate, so the moment retained losses cross the line the premium was meant to justify passes completely unseen. You discover the breach when the year is closed, not while you can still act on it.

Why the savings story collapses without a retained-loss ledger

Here is the arithmetic that gets skipped at renewal. Suppose the high retention saved a clean, defensible amount on premium. If the aggregate of below-deductible claims over the year quietly lands above that saving, you have not saved money. You have paid the same total, lost the carrier's claims-handling on dozens of files, and carried the cash-flow drag yourself. On a churning fleet with frequent low-severity incidents, that crossover is not an edge case. It is the expected outcome of a frequency book sitting under a severity-shaped retention.

• The premium saving is one number, fixed and visible at bind.
• The retained losses are many numbers, variable and invisible until totalled.
• Comparing them only works if something keeps the second total live all year.

Tracking retained losses against budget the way you track premium

You already track premium to the cent because it is one invoice on a known date. Retained losses deserve the same rigour, and they get the opposite. The fix is structural: every claim that falls below the retention is captured against the policy, tagged to a vehicle and a date, and added to a single accumulating figure measured against the aggregate ceiling and the budget line. Not a quarterly reconciliation. A live total, the way you watch cash.

FleetLedger treats the retained-loss layer as a first-class number inside the fleet program rather than a residue scattered through operations. Below-deductible claims accumulate against the aggregate as they happen, so the controller sees the running total climb toward the cap in time to renegotiate the retention or change driver behaviour, instead of explaining the overrun after the books close. A retention only saves money when someone owns the aggregate, and ownership starts with making the number visible.