Someone drove the truck through the charging scheme without paying - but the law does not always chase the driver. For an expanding category of road-user charges and civil contraventions, liability attaches to the vehicle’s registered keeper: the person named at DVLA pays, whoever had the wheel. For fleets, whose vehicles move between drivers daily, keeper liability converts driving behaviour into an accounts problem - and makes the admin system the only line of defence.

The keeper-pays principle

The model scheme is the Dartford Crossing: GOV.UK’s Dart Charge guidance puts the duty to pay on the vehicle’s keeper - pay the charge for the crossing, by the deadline, or receive the penalty charge notice. No driver is identified; the scheme photographs the plate, looks up the keeper, and the liability lands on the record at DVLA. The same architecture runs through the clean air and low emission zones, the congestion schemes, and the camera-enforced moving traffic and parking contraventions: identify the vehicle, charge the keeper.

The principle’s direction of travel matters for fleets: camera-enforced, keeper-liability schemes are how road use is increasingly policed, because they need no traffic stop and no officer. Every new charging zone and camera scheme adds another stream of keeper-liability paperwork to the fleet’s post room.

Where fleets bleed money

The exposure is operational, and the failure modes are clerical. Unpaid charges: the driver crosses, nobody logs it, the payment deadline - short, by design - passes, and the penalty arrives at a multiple of the original charge; a fleet crossing daily without an account or a logging routine generates penalties on an industrial scale. Wrong keeper details: vehicles acquired, leased or disposed of where the DVLA record lags - penalties for a vehicle the fleet sold, or a vehicle the fleet owns but cannot be found to be told about. Missed deadlines: the notice goes to the depot, sits in a tray, and the discount window and then the appeal window close unopened. And driver ambiguity: where liability can be transferred or the driver identified - the hire and lease provisions, the representations process - the fleet that cannot say who had the vehicle pays by default.

The common thread is that none of these is a driving failure: they are all administration failures, priced in penalties.

The admin system that defends it

Keeper liability is beaten with routine, and the routine is short. Accounts for the regular schemes: the crossing and zone accounts with auto-pay where the fleet’s pattern justifies it, converting per-crossing admin into a monthly reconciliation. A crossings log where auto-pay does not fit: the driver’s duty to report the crossing the same day, the office’s duty to pay within the deadline. DVLA hygiene: keeper details updated on every acquisition and disposal, promptly, with the confirmation filed. A notices SLA: every penalty or charge notice logged on arrival, the deadline diarised, pay-or-challenge decided inside the discount window, and the driver identified from allocation records where the scheme allows transfer. And the monthly review: penalties by scheme, by depot, by cause - because a rising penalty line is a process fault with an invoice attached.

The takeaway

Keeper liability makes the registered keeper pay for the vehicle’s road charges and camera-enforced contraventions - whoever was driving. Defend it with scheme accounts, same-day crossing logs, current DVLA records, and a notices process that never sleeps. The camera does not know your driver; it knows your company - make sure your admin knows both.

The representation and transfer routes

Keeper liability is not always final: the schemes provide routes to move or contest it, and the fleet that knows them pays only what it truly owes. Representations against a penalty succeed on defined grounds - the vehicle was sold before the event, the charge was paid, the vehicle was stolen, the keeper details were wrong - and they succeed only inside the window, with evidence. Transfer provisions matter for hire and lease fleets: the hirer can be made liable where the agreement and the scheme’s rules allow, but only if the paperwork exists and is produced in time. The standing rule that protects both routes is record-keeping: allocation records that name who had each vehicle on each day, agreements filed and retrievable, and notices actioned while the window is open. The keeper-pays principle is unforgiving about dates; the defence is being earlier than the deadline, every time.

Finally, fold the topic into driver induction rather than discovering it through penalties: drivers should know which schemes the fleet has accounts for, what to do at an unplanned crossing or zone entry - report it the same day - and why the office asks. Most keeper-liability penalties in real fleets begin not with a driver doing something wrong but with a driver doing something reasonable and nobody being told. The induction line that prevents it costs thirty seconds: if the truck went somewhere that charges, tell the office today. Everything else - the accounts, the deadlines, the representations - is the office keeping its half of the same bargain.

Sources