The conversation around fleet electrification is almost entirely about vehicles. Which models are available, what the range looks like, how the charging infrastructure is developing, what the government incentive structure looks like. Those are real questions. But there's a parallel question that barely gets discussed: how are fleet operators actually going to manage the data that comes with a mixed or fully electric fleet?
Most fleet management systems were designed around a diesel operating model. Fuel is measured in litres. Consumption is reported by the litre per mile. Refuelling is a single transaction at a fuel card terminal. Cost is straightforward to allocate.
Electric vehicles break every one of those assumptions. Energy is measured in kWh. Consumption varies with temperature, load, and driving pattern in ways that are more complex than diesel equivalents. "Refuelling" may happen at four different locations -- the depot, a public rapid charger en route, a destination charger at a customer site, and the driver's home -- each with different cost structures, different reporting formats, and different degrees of visibility to the fleet operator.
Home charging is where this gets particularly thorny. When a company car driver charges at home overnight, the electricity comes from their domestic supply. HMRC's advisory electricity rate currently sits at 7p per mile for most electric vehicles, but the actual cost to the driver depends on their tariff, the time of charging, and whether they have a smart meter. Fleet teams trying to calculate their real energy cost per mile have no reliable way to capture this -- and many aren't trying, which means their EV cost figures are systematically understated.
Public charging presents a different problem: fragmentation. The UK has over 60 charging network operators, each with their own app, their own billing system, and their own data format. A fleet vehicle that uses three different public charging networks in a month will generate three separate billing records in three incompatible formats, none of which automatically flows into the fleet ERP.
Some networks have started offering fleet-specific APIs, but coverage is inconsistent and integration requires development effort. The practical reality for most fleet operators right now is that public charging costs are either captured manually (high effort, often incomplete) or written off as an estimate (inaccurate, not auditable).
This isn't just an accounting problem. If you're trying to demonstrate emissions savings to meet a Scope 1 reporting obligation, you need to know the actual grid mix at the time of each charging event. A vehicle charged in the middle of the night from a renewables-heavy grid is genuinely lower-carbon than the same vehicle charged at peak demand. That granularity is available from some networks. Most fleets aren't capturing it.
Diesel vehicles depreciate in broadly predictable ways. Battery electric vehicles have an additional depreciation variable that has no equivalent in traditional fleet finance: battery state of health (SoH).
A vehicle with a battery at 78% SoH is worth materially less than an identical vehicle at 95% SoH, all else being equal. The factors that affect SoH -- charging behaviour, temperature exposure, depth of discharge cycles -- are manageable if you have the data. They're invisible if you don't.
"We've seen operators discover their EVs were charging to 100% every night for eighteen months. That's a battery degradation practice that costs you on residual value. The data was there. Nobody was looking at it." — ExoFleets Team
Fleet ERP systems that were designed for diesel don't have a battery SoH field. They don't have a charging behaviour module. These aren't features that were left out because they were considered unimportant -- they simply didn't exist as a concept when most fleet management software was originally architected.
The fleets that are managing this well have done a few things differently. First, they've established a data standard for EV-specific metrics before deploying vehicles -- not after. Battery SoH tracking, charging event attribution (depot, public, home), and energy cost allocation are defined as requirements, not afterthoughts.
Second, they've invested in depot charging infrastructure that generates clean, fleet-attributed data. Depot chargers that report individual charge sessions with vehicle identification, start/end times, kWh delivered, and cost are the baseline. This isn't technically complex -- most modern OCPP-compliant chargers support it -- but it requires a conscious decision to integrate that data stream into the fleet management system rather than letting it sit in the charger management platform in isolation.
Third, they're using telematics data more aggressively. Modern BEV telematics can report battery SoH, charging events, and energy consumption at the granularity needed for accurate cost and emissions tracking. The data exists. Getting it into a usable form in the fleet ERP requires integration work, but that work pays back quickly when you're managing a fleet of any significant size.
The UK government's Zero Emission Vehicle mandate requires 28% of new car registrations to be electric in 2026, rising steeply through the decade. Fleet composition is going to shift significantly over the next three years regardless of individual operator preferences. The fleet operators who build the data infrastructure to manage EVs properly in 2026 will be significantly better positioned than those who treat it as a problem to solve later.
Later, in our experience, means doing it under pressure, at higher cost, with a backlog of data that's already lost.
ExoFleets's platform is built for mixed-fuel fleets including full BEV data management. Talk to our team about how we handle EV data integration.
