What Driver ID Billing Is
Driver ID billing is a charging billing method where each EV charging session is linked to a specific driver identity (Driver ID) so costs can be assigned, invoiced, or reimbursed to the correct person, team, or cost centre. The Driver ID can be an RFID card, app account, employee number, or another unique identifier used during driver authentication.
Why Driver ID Billing Matters
Driver ID billing is essential when multiple people use shared chargers or shared vehicles and you need accurate cost allocation:
– Enables fair reimbursement for workplace or home charging (if tracked)
– Supports internal cost allocation by driver, department, or project
– Reduces misuse and unauthorized charging (clear accountability)
– Simplifies reporting for fleet managers and finance teams
– Improves dispute resolution with traceable session records
How Driver ID Billing Works
A typical flow looks like this:
– Driver authenticates (RFID/app/QR/Plug & Charge where applicable)
– The CPMS records the session with: Driver ID, charger ID, timestamp, meter values
– Pricing rules are applied (tariff, time windows, discounts, contracts)
– Costs are allocated to the driver account or mapped to a cost centre
– Invoices, payroll deductions, or internal chargebacks are generated (depending on policy)
Common Driver ID Types
Driver ID billing can be implemented with different identity sources:
– RFID UID mapped to a driver profile
– App account (email/phone login)
– Employee ID / badge number integrated via SSO or HR systems
– Vehicle-linked IDs (driver identity inferred via assigned vehicle)
– Temporary guest IDs (visitors, contractors)
Typical Use Cases
– Fleet depots: allocate energy cost per driver or per route/shift
– Workplace charging: employee charging billed back or reimbursed
– Multi-tenant sites: assign charging to specific tenants and users
– Service fleets: track charging cost by technician/team
– Shared vehicles: link usage to driver accountability even when vehicles rotate
Billing Models Enabled by Driver ID
Driver ID billing supports different commercial setups:
– Direct billing to the driver (invoice or card on file)
– Employer-paid with reporting only (cost centre allocation)
– Chargeback to departments/projects (internal accounting)
– Hybrid (free allowance, then paid)
– Reimbursement (home charging tracked, reimbursed via Driver ID rules)
What Needs to Be Defined Clearly
To avoid disputes and data mess, define these upfront:
– Who pays: driver, employer, tenant, or department
– Which tariff applies per Driver ID group (employee, visitor, contractor)
– VAT and invoicing requirements (invoice recipient, tax point, evidence)
– Identity lifecycle: onboarding, lost cards, leavers, temporary access
– Offline behaviour: what happens if backend is down (local whitelist + later reconciliation)
– Data privacy: who can see driver-level consumption and for how long
Common Pitfalls
– Driver IDs not mapped consistently (duplicate cards, shared cards)
– Vehicle-based reporting mixed with driver billing → disputes
– App-only Driver ID in low-signal depots → auth failures and operational friction
– No process for leavers and card revocation → unauthorized charging risk
– Incomplete metering/audit trail → finance rejects invoices or chargebacks
Related Terms for Internal Linking
– Driver authentication
– Chargeback protection
– Charging reimbursements
– Fleet accounts
– Charge Point Management System (CPMS)
– RFID authentication
– Local authorization
– Metering (MID/Eichrecht)