By Yair Knijn · April 22, 2025
The claim the insurer refused: an APK lapse the risk manager never tracked
The risk manager ran a tight register. Every policy renewal date, every premium installment, every green-card expiry sat in a tracked column with a reminder attached. The assumption underneath it was that cover is the thing you monitor, and cover was continuous. APK validity lived somewhere else entirely, in the workshop's planning, treated as a maintenance task rather than an insurance one.
Then a delivery van rear-ended a car at a roundabout. The driver was at fault, the third-party damage was modest, and the claim should have been routine. The handler pulled the RDW record, saw the APK had expired six weeks earlier, and the tone of the conversation changed.
The legal link: APK keuringsplicht, RDW enforcement, and policy roadworthiness conditions
The APK keuringsplicht is statutory, not advisory. A vehicle without a valid periodic inspection is not legally roadworthy, and the RDW enforces this independently of any insurer: you may not drive on a public road once the APK has lapsed, and after the standstill window the registration must be inspected or suspended. The RDW even sends a reminder roughly six weeks before the expiry date, which is exactly why a missed renewal reads as negligence rather than oversight.
Most fleet policies carry a condition that the vehicle be in a roadworthy and legally compliant state. An expired APK hands the insurer a clean factual hook against that condition. They do not have to prove the lapse caused the collision. They have to show you were operating a vehicle that the law says should not have been on the road.
How an APK lapse moves a routine claim into dispute
Once the lapse is on the file, the insurer's question stops being "what happened" and becomes "was there a causal link" — the Dutch causaal verband test. They look for any defect that a timely inspection would have caught and that could have contributed to the loss: worn brakes, a steering fault, bald tyres. If they find one, they can reduce the payout proportionally or decline it outright. Even when no such defect exists, the burden has quietly shifted to you, and a claim that would have closed in a week now needs a defence.
The financial shape of this is ugly. A €4,000 third-party claim you expected to be fully covered becomes an exposure you may carry yourself, plus the handling time, plus a black mark on the loss history that follows the fleet program into its next renewal.
Why fleets track APK in the workshop but not in the risk register
The split is organisational, not technical. Maintenance owns the APK because it happens in a garage, on a lift, with a stamp. Insurance owns policy dates because they arrive as broker emails and invoices. The two systems rarely talk, so the risk manager sees a fleet that is fully insured on paper while the workshop sees vehicles that are a few weeks overdue on inspection. Each function is doing its job. Nobody owns the join.
- Cover dates come from the broker schedule and renewal notices.
APKvalidity comes from RDW per registration, on a per-vehicle cycle that never aligns with the policy year.- The risk register tracks the first and assumes the second is handled downstream.
Wiring APK expiry into the same monitoring as cover and registration
Treat APK status as a claim-eligibility control with the same severity as a lapsed premium. That means pulling inspection validity from the RDW record per kenteken, holding it against the live vehicle list, and raising the alert well before the date — not when a handler pulls the record after a crash. The reminder window the RDW already gives you is enough lead time if something is actually watching it.
A fleet program is only as insurable as its worst-tracked vehicle. FleetLedger reconciles RDW registration and inspection data against the policy schedule continuously, so an approaching APK expiry surfaces as a risk-register item next to cover and registration, not as a surprise the insurer finds first. See how the reconciliation works.