By Yair Knijn · February 4, 2025

The RDW runs a register comparison every night. Your fleet spreadsheet doesn't.

The fleet manager who signs a lease for two replacement vans believes the moment they drive off the lot, they are covered. The broker said "I'll add them to the policy," the binder confirms it, and the keys are handed over. That belief is wrong in a way that does not show up until a fine arrives. In the Netherlands a vehicle is not insured because someone intends to insure it. It is insured because the insurer has filed WA cover against the kenteken in the RDW register.

This is the trap. Insurance here is a register state, not a paperwork state. The car can be on the road, the premium can be running, the broker can be certain it is handled, and the RDW's nightly comparison still reads that kenteken as legally uninsured because no cover was filed against it yet.

How the RDW registercontrole actually works: CRWAM, the 28-day filing rule, and the daily comparison against the kentekenregister

When an insurer or authorised agent puts a vehicle on cover, the policy is recorded in the Centraal Register WAM (CRWAM), the RDW's insurance register. The RDW runs a registercontrole that compares the kentekenregister against CRWAM and against the APK inspection register, and it runs that comparison daily through an algorithm, not at renewal and not on request. Any kenteken that is registered, required to carry cover, and has no insurance recorded against it gets flagged.

The window that matters: the insurer has a fixed period to file the cover after it starts. If that filing slips, or never happens because nobody actually pushed the new vehicle through, the kenteken sits in the register as uninsured the whole time. The road reality and the binder both say covered. The register says nothing. The register wins.

The six-week response window and why a fleet manager finds out too late

When a kenteken is flagged, the registered keeper gets a letter and a fine. For uninsured status that fine is currently €400, issued under offence codes A915 or A902. There is a roughly six-week window to show you actually held cover at the moment of detection, usually by getting an Artikel 34 WAM declaration from the insurer confirming the policy was in force on that date.

The problem for a fleet is timing. The detection happens in a nightly batch, the letter is posted to the company address, it lands on a desk weeks after the gap opened, and only then does the fleet manager start chasing the broker for proof. By then several monthly comparisons have already run. If the cover genuinely was filed late, there is no Article 34 declaration that fixes it, because at the moment of detection the register was correct: the vehicle was uninsured.

Why mid-term additions are the highest-risk moment in a fleet's year

A vehicle that has been on the policy for two years is almost never the one that gets flagged. The cover is filed, the kenteken is clean, nothing moves. Risk concentrates at the edges of the fleet, where vehicles enter and leave:

• A lease delivered on a Friday, driven all weekend, filed to CRWAM the following week.
• A van sold or returned where the keeper change lags, so the company is still the registered keeper of a vehicle it no longer insures.
• A replacement swapped in under an assumption that it inherits the old vehicle's cover automatically, which it does not.

Every one of these is a handoff between three parties who each think someone else closed the loop. The fleet manager added it to the spreadsheet, the broker meant to file it, the insurer waited for instruction. Nobody checked the register, which is the only place that decides whether the vehicle is insured.

Reconciling the on-road fleet to the register every day, not every renewal

The fix is not a tighter onboarding checklist and it is not trusting the broker's word faster. It is treating the RDW register as the source of truth and reconciling against it on the same cadence the RDW does. Every vehicle the company is the registered keeper of should be matched against confirmed CRWAM cover, daily, so a missing filing surfaces within a day of the gap opening, while there is still time to act, not six weeks later inside a fine letter.

This is what a fleet program in FleetLedger is built to do: pull the RDW registration data for every kenteken you keep, reconcile it against the cover actually on file, and flag the additions and disposals where the register and the road have drifted apart. The night the RDW runs its comparison, you should already know what it is going to find. See how it works.