The fleet sector has navigated significant policy change before. But the proposed eVED model is different, not because of the rate, but because of the mechanism. For the first time, a mainstream vehicle tax would be structured around real-world usage rather than a fixed annual charge. That shifts the nature of the cost from predictable to variable and it raises practical questions that go beyond data and systems.
Who carries the liability?
Under the current proposals, drivers would estimate mileage in advance, with an annual reconciliation process administered through the DVLA. The principle is straightforward. The contractual implications are not.
If a driver significantly exceeds their estimated mileage, an underpayment arises. In a leased vehicle, someone must absorb that. Most existing agreements were not designed with a usage-based tax liability in mind – so the question of whether that sits with the provider, the customer, or is shared between them will depend entirely on how contracts are written.
This is one of the more immediate challenges for BVRLA members. New contracts may need to define mileage assumptions more precisely, allocate reconciliation liability explicitly, and build in review points that allow estimates to be updated before year-end. For providers managing large portfolios, the potential for underpayments across many vehicles is high.
How will customers experience this?
The previous discussion of eVED has largely focused on providers. But the customer experience deserves equal attention.
Many drivers will be unfamiliar with the concept of estimating mileage for tax purposes. Explaining the process clearly at contract inception, setting realistic assumptions, and communicating what happens at reconciliation will all require deliberate effort. Where customers receive an unexpected charge because their actual mileage exceeded their estimate, the risk is not just financial – it is reputational. Trust built over the course of a contract can erode quickly if the end-of-year reconciliation feels like a surprise.
Providers who develop clear, plain-language communications around eVED will be better placed to manage customer relationships through what could otherwise be a disruptive annual process.
Telematics: one approach among several
Accurate mileage data will clearly matter under the proposed model. Automated telematics would remove most of the estimation risk for providers, the DVLA and end users alike. But it would be simplistic to suggest that telematics is the only or inevitable path for every operator.
Providers will take different approaches depending on fleet type, customer base and existing systems. A large commercial fleet with connected vehicles already in place faces a different decision to a provider managing a mixed portfolio of short-term rentals and longer-term leases. What matters is that each operator understands where their mileage data currently comes from, how reliable it is, and where the gaps are – then makes an informed choice about how to address them.
What should members be doing now?
The implementation date is still some way off, but the practical groundwork takes time. Four areas are worth prioritising:
- Review how mileage is currently captured – and identify vehicles or contract types where data is inconsistent or incomplete.
- Assess whether existing contract wording adequately allocates tax liability – particularly for agreements that will still be live when eVED comes into effect.
- Consider how customer communications will handle annual reconciliations – proactive explanation will reduce friction.
- Map where disconnected systems could create administrative burden – the proposed reconciliation model will amplify gaps that already exist in data flow between vehicle, contract and customer records.
eVED is not yet live. But the gap it will expose already exists.
To find out more about how Key2 supports mileage tracking, contract management and fleet data integration, visit www.jaama.co.uk.