What Fleet Wallets Are
Fleet wallets are managed payment and accounting “wallets” used by fleets to pay for EV charging (and sometimes other mobility services) across multiple drivers, vehicles, sites, and networks. A fleet wallet centralizes charging spend into a single controlled account while still tracking costs at the right level (driver/vehicle/cost centre).
Think of it as a corporate charging balance/payment account with rules.
Why Fleet Wallets Matter
Fleet wallets solve a common problem: fleets need centralized control without losing granular reporting. They help:
– Consolidate charging payments across many chargers and roaming networks
– Set budgets, limits, and permissions per driver/vehicle/team
– Simplify invoicing (one bill instead of hundreds of receipts)
– Enable accurate cost allocation and reimbursement workflows
– Reduce fraud and unauthorized charging through policy controls
– Support fast rollout: drivers can charge immediately using approved tokens
How Fleet Wallets Typically Work
A fleet wallet model usually includes:
– A parent fleet account with a funding method (invoice, direct debit, card, prepaid)
– Sub-accounts or rules for drivers/vehicles (limits, allowed sites, time windows)
– Authentication tokens (RFID cards, apps, Plug & Charge certificates) mapped to wallet rules
– Session capture and reconciliation (kWh, price, location, VAT data)
– Reporting exports for finance and fleet ops
Common Fleet Wallet Features
– Role-based access: fleet admin vs dispatcher vs driver
– Spending limits: per day/week/month, per session, per kWh
– Location rules: depot-only, approved public networks only, geo-fencing
– Tariff rules: employee vs contractor pricing groups
– Cost centre mapping: project, department, route, vehicle class
– Fraud controls: anomaly detection, blocked tokens, blacklist/whitelist
– Multi-country billing: VAT-friendly invoicing and settlement (where supported)
Where Fleet Wallets Are Used
– Public charging + roaming: pay across many CPOs with one fleet contract
– Mixed charging ecosystems: depot + workplace + public top-ups
– Employee reimbursement programs: track charging at work/home/public under one policy
– Shared vehicles: allocate charging costs despite driver rotation
– Contractor and temporary driver setups: controlled access without personal payment
Fleet Wallets vs Driver ID Billing
They often work together but aren’t identical:
– Fleet wallet = the account that funds charging and applies spending rules
– Driver ID billing = the method that attributes sessions to a specific driver identity
A fleet wallet can bill per vehicle, per driver, or per department depending on setup.
Key Implementation Considerations
– Decide what identity anchors billing: driver, vehicle, or team
– Define reimbursement and VAT rules (who is the invoice recipient)
– Ensure data quality: consistent IDs across CPMS, telematics, and finance
– Plan offline behavior (local auth caching) for depots
– Align roaming settlement timelines with finance expectations
– Define handling of disputes (wrong tariff, failed session, duplicate charges)
Common Pitfalls
– Shared RFID cards → no accountability and messy cost allocation
– Too many rules → drivers get blocked and operations suffer
– Poor roaming tariff transparency → unexpected bills and disputes
– Weak offboarding process → lost tokens remain active
– Not integrating exports into ERP/accounting → manual reconciliation workload
Related Terms for Internal Linking
– Fleet accounts
– Driver authentication
– Driver ID billing
– Roaming
– Charge Detail Records (CDRs)
– Settlement
– Charging reimbursements
– Fleet billing