Fleet spend leaks because there is no container for it. A driver takes a vehicle, charges it, runs through a toll, maybe fills the tank, and each of those costs lands in a different system, reconciled hours or days later against a booking nobody can cleanly match it to. DIMO ties spend to the vehicle session: a cap is set at checkout, every charge is attributed to the session that incurred it, and reconciliation happens automatically instead of in a Monday-morning spreadsheet.
Why spend leaks today
The core problem is that spend is not connected to the vehicle access event. Booking lives in one tool, telematics in another, charging in a third, tolls in a fourth. When a charge appears, matching it back to “which rental, which driver, which vehicle” is manual detective work. Multiply that across a fleet and it is several hours a week of reconciliation plus a steady trickle of costs that never get attributed at all.
The three EV reimbursement problems, at once
Electrification makes this sharper, because an EV fleet runs three reimbursement problems simultaneously:
- Home charging: a driver charges at home and has to be reimbursed at the right rate for the right kWh.
- Public charging: sessions across a dozen networks, each with its own app, receipt format, and pricing.
- Tolls and parking: incurred mid-session, billed later, rarely tied to the trip that caused them.
Handled separately, these are three integrations and three reconciliation headaches. Handled as part of the session, they are one capped, attributed line item.
Plug-and-charge as a per-session service
Tying spend to the session also unlocks revenue, not just savings. Imagine getting plug-and-charge on your next rental, so you do not have to download six apps to charge on a business trip. Today that is a $0 line item because there is no session to attach it to. With a session container, charging, insurance, and other per-trip services become things an operator can actually offer and bill, priced per session rather than buried in a daily rate.
How it works
When a vehicle session is created, it carries a spend cap alongside identity, the digital key, and the data scope. Charges incurred during the session are attributed to it automatically and bounded by the cap; when the session ends, the spend is reconciled and sealed into the same verifiable record as the rest of the session. The operator sees one number per session instead of four feeds to reconcile.
This is the spend capability of the broader session model. See vehicle session infrastructure, the pay product, and how it fits rental operations.