The FleetLedger blog
Where motor-fleet programs leak, and the management traps behind them.
Premium reconciliation, bordereaux, RDW drift and naverrekening — written for the volmacht office, the broker, and the fleet owner who carries the number at year-end.
- Counted twice: how replacement vehicles overstate the fleet and inflate every premium calculation A fleet manager added each replacement vehicle but left the outgoing one on the schedule for the overlap, and over a year the systematic double-count overstated the fleet, inflating premium and corrupting the loss-ratio the insurer used to renew.
- The bordereau balanced in the wrong currency, and settlement broke for three months A claims manager submitted bordereaux with inconsistent currency and tax fields against the Lloyd's reporting standard; the technical account wouldn't reconcile, settlement stalled, and the relationship with the syndicate frayed.
- The capacity pulled out mid-term, and the fleet director found out at renewal An operations director relied on a single insurer for the whole fleet; when the carrier downgraded its motor appetite and declined to renew, there was no alternative market lined up and the fleet scrambled for cover under time pressure.
- The cross-border job the Green Card didn't cover: a territorial gap the risk manager assumed away A risk manager sent vehicles on a long-term contract into a territory outside the policy's standard cover, assuming the Green Card sorted it; an incident abroad revealed a territorial exclusion and a months-long uninsured operation.
- One policy, four legal entities: the intercompany allocation that failed the audit A finance controller ran four group companies' vehicles under one fleet policy and split the cost by headcount; the external auditor rejected the allocation because premium and claims couldn't be traced to the entity that bore the risk.
- The van classified as a car: a use-class error that voided the claim A fleet manager listed several commercial vehicles under the wrong use class to fit a simpler schedule; after a loaded vehicle's accident, the insurer voided the claim for misdescription of risk.
- The renewal quote came back loaded because the exposure data was a year stale A broker submitted last year's vehicle and claims data into renewal because reconciling it was too slow; the insurer loaded the premium for the uncertainty, and a better-prepared competitor won the account.
- The self-insured retention that ate the budget: when the fleet's small claims were never aggregated A CFO chose a high deductible to cut premium, then watched dozens of small fleet claims pile up below the retention with no one tracking the aggregate against the budgeted ceiling.
- Stale claims reserves on the bordereau, and the true-up that wiped out the binder's margin A claims manager reported open claims with reserves that hadn't moved in months; when the syndicate reconciled, the under-reserving forced a true-up that made the binder look unprofitable overnight.
- The telematics data that priced the fleet became a GDPR problem the risk manager never assessed A risk manager fed driver telematics and location data into the insurer's pricing without a lawful basis or DPIA for the drivers; an employee complaint turned a premium discount into a data-protection investigation.
- The fleet manager left, and the spreadsheet that held the whole policy together left with them When the fleet manager resigned, the only reconciliation between vehicles, drivers, and cover lived in a personal spreadsheet and their memory; the next renewal exposed nine vehicles whose status nobody could confirm.
- IDD made the broker responsible for the add-on cover they bolted onto the fleet policy An account manager bundled a gap-cover add-on across a fleet without checking target-market fit; under IDD product oversight and governance, the broker — not just the insurer — owned the suitability failure when a regulator asked.
- Premium leakage hides in the endorsements nobody priced: the mid-term adjustments that quietly cost a fleet A finance controller discovered the fleet had been paying for two written-off vehicles for eight months and under-declaring three high-value additions — net leakage in both directions because mid-term adjustments were emailed, not tracked.
- The claim the insurer refused: an APK lapse the risk manager never tracked A risk manager assumed cover was continuous, but a delivery van's APK had expired weeks before a collision; the insurer leaned on the policy's roadworthiness condition and the claim handling turned hostile.
- The technical-account bordereau the finance team scrutinises most, and the discrepancy that triggers a DA review An operations director at a coverholder shipped months of bordereaux with mismatched premium totals and stale vehicle data; the syndicate's finance team flagged the technical account, and a full delegated-authority audit followed.
- Three lists, one fleet: how the broker's schedule, the insurer's pricing, and the road drift apart in a quarter A broker account manager handed the insurer a vehicle schedule that hadn't been reconciled in months; by renewal, eleven vehicles were double-insured across two binders and four were on the road with no live cover at all.
- The naverrekening nobody budgeted for: when year-end premium is charged on a fleet that no longer exists A finance controller signed off a flat monthly premium all year, then received a five-figure naverrekening invoice because the insurer reconciled premium against the declared fleet size — including vehicles sold in Q1 and cover upgrades nobody flagged.
- The RDW runs a register comparison every night. Your fleet spreadsheet doesn't. A fleet manager sold three vans but left them on the policy and pulled two replacements onto the road before the broker registered them. The RDW's daily registercontrole flagged the gap, and the WAM fines landed at the company address six weeks later.