By Yair Knijn · February 23, 2025
The naverrekening nobody budgeted for: when year-end premium is charged on a fleet that no longer exists
The controller booked the fleet premium as a fixed monthly line and moved on. Twelve equal direct debits hit the account, each reconciled cleanly against the budget, and the number never moved. So when the naverrekening invoice landed in February for the prior policy year, it read as an error. It was not an error. It was the bill for twelve months of nobody checking.
This is the controller's specific blind spot. The monthly debit is not the premium. It is the voorschotpremie — the advance, charged on the fleet you declared at renewal. The real premium gets settled once a year against the vehicles that were actually on cover, and the gap between those two numbers is the true-up. Treating the advance as the final cost is the entire trap.
What naverrekening actually reconciles: declared exposure vs. priced schedule vs. real fleet-days
Three things have to agree and rarely do. There is the fleet you declared at renewal, the schedule the insurer priced the advance on, and the fleet-days you actually ran — every vehicle, every day it sat on the policy. Naverrekening reconciles all three down to a single figure. Insurers running a wagenparkverzekering on this basis regularise the advance once per year against the vehicles effectively covered, and they typically do not issue a per-vehicle endorsement when a car is added or removed. So mutations do not generate paperwork that lands on your desk. They accumulate silently and surface as one line at year-end.
Three drift sources that inflate the true-up: late removals, silent cover upgrades, and double-counted replacements
The drift is rarely one big event. It is dozens of small ones, and they almost always push the true-up up, not down.
- Late removals. A van is sold in March, the operational team stops thinking about it, and nobody tells the broker until the year-end data request. That vehicle was rated on cover for nine months it was not on the road.
- Silent cover upgrades. A vehicle moves from third-party to all-risk when a new lease starts, or a higher catalogue value resets the rating basis. No invoice changes, no endorsement, so the cost stays invisible until it is summed.
- Double-counted replacements. A replacement vehicle goes on cover the day it arrives while the old one is still on the schedule waiting to be deregistered. For a few weeks you are paying for both, and across a busy fleet those overlaps add real fleet-days.
Why a flat monthly premium hides a growing liability on the balance sheet
A fixed line that never moves feels controlled. It is the opposite. Every month the advance was charged on a fleet that no longer matched reality, an unbooked liability grew, and nothing in the monthly close exposed it. The controller had no accrual for it because there was no signal that it existed. That is the real failure: not the size of the invoice, but that a five-figure obligation built up off the books for a year and surfaced only after the period it belonged to had closed.
Running a rolling premium reconciliation so the year-end number is a confirmation, not a shock
The fix is to reconcile monthly instead of annually. Hold the declared schedule against actual registration status, recompute the implied premium each month, and carry the difference between that and the advance as an accrual. When a vehicle is sold, its deregistration date drops off the rated days immediately. When cover upgrades, the new rating basis flows through that month. Year-end stops being a true-up you discover and becomes a number you already booked.
FleetLedger runs that reconciliation continuously for each fleet program: it holds the declared schedule against RDW registration status, recomputes the implied premium as vehicles and cover change, and tracks the running difference against the advance so the accrual stays current. The naverrekening still arrives in February. It just matches the number you already have. See how it works.