Fleet account authorization is the process of verifying that a charging session is allowed under a specific fleet contract or corporate account, and then assigning the session’s costs to that fleet account instead of the individual driver. It enables centralized billing, policy control, and reporting across multiple vehicles, drivers, and sites—whether the fleet charges at depots, workplaces, or public networks.
What Is Fleet Account Authorization?
Fleet account authorization connects a driver or vehicle identity to an approved payment responsibility.
– Confirms the user/vehicle belongs to an authorized fleet account
– Checks whether charging is permitted under fleet rules (location, time, vehicle group, limits)
– Starts the session and records it under the fleet account for invoicing and reporting
– Ensures session data (kWh, timestamps, charger ID) is attributed correctly for cost allocation
Fleet authorization can be implemented through the CPMS, an eMSP, or a fleet management platform, depending on the charging ecosystem.
Why Fleet Account Authorization Matters
– Prevents unauthorized charging at the fleet’s expense
– Enables consolidated invoicing and simpler expense handling for drivers
– Supports policy enforcement (who can charge, where, and under what conditions)
– Improves financial control and transparency (cost centers, departments, vehicles)
– Enables analytics: energy use, utilization, CO₂ reporting, and route optimization
– Reduces operational friction for drivers (no personal payment, fast start)
Common Fleet Authorization Methods
RFID-Based Authorization
– Drivers use fleet-issued RFID cards linked to the fleet account
– CPMS verifies card ID against allowed lists or roaming authorization databases
– Works well for depots and mixed-access sites
App or Token-Based Authorization
– Driver uses a fleet-linked mobile app account
– Authorization uses secure tokens, QR initiation, or app-to-CPMS flows
– Enables richer policy control and driver feedback features
Vehicle-Based Authorization (Where Supported)
– Authorization linked to the vehicle identity rather than the driver
– Can be used for shared vehicles or pool fleets
– Often combined with backend rules mapping vehicle ID to cost center
Plug & Charge Fleet Authorization (Advanced)
– Session authorization via vehicle certificates and ISO 15118 mechanisms
– Can simplify driver interaction, but requires certificate and contract management readiness
– Often paired with fleet contract certificates or eMSP contract certificates
Roaming-Based Fleet Authorization
– Fleet uses an eMSP or roaming provider account
– Authorization happens through roaming protocols and settlement systems
– Useful when fleets charge across many public networks and countries
What Fleet Authorization Policies Typically Control
– Who can charge: driver groups, departments, vehicle types
– Where: allowed sites, regions, roaming partners, depot-only rules
– When: time windows, shift-based rules, off-peak incentives
– How much: kWh/session caps, daily/weekly limits, spending limits
– Pricing model: negotiated tariffs, fixed rates, or pass-through pricing
– Charging behavior rules: maximum session duration, idle fee handling, priority users
Data and Reporting Requirements
Fleet authorization is most valuable when paired with strong data capture.
– Session-level data: kWh, start/stop times, location, charger ID, connector ID
– Vehicle/driver mapping and cost center allocation
– Tariff and tax breakdown for invoice reconciliation
– Export APIs for fleet systems, ERP, and sustainability reporting
– Exception reporting: failed authorizations, blocked sessions, anomalous energy use
Operational Considerations
– Onboarding process: issuing RFID cards, creating accounts, mapping vehicles and drivers
– Offboarding and access control: revoking credentials quickly when staff changes
– Customer support: handling lost cards, failed starts, and roaming issues
– Security: preventing credential cloning and enforcing strong identity controls
– Network reliability: depot sites should support local allowlists or offline authorization fallback where required
Common Mistakes to Avoid
– Weak mapping between driver/vehicle IDs and fleet account, causing billing disputes
– No clear policy rules, leading to uncontrolled public charging costs
– Inconsistent tariffs across networks without visibility, breaking cost predictability
– Lack of offline fallback at depots, causing operational disruption during outages
– Poor data hygiene: missing charger IDs, timestamps, or tax fields, complicating reconciliation
– Not defining who owns authorization failures: operator, eMSP, roaming partner, or fleet
Limitations to Consider
– Roaming adds complexity: authorization and billing responsibility may sit with different parties
– Plug & Charge fleet models require mature certificate and contract management
– Some sites require additional compliance for invoicing and fiscal receipts
– Corporate IT and security policies may restrict app-based flows or device management
– Without reliable uptime and monitoring, authorization quality cannot ensure a good charging experience
Related Glossary Terms
Driver Authentication
Charging Access Subscriptions
Roaming Authorization
Plug & Charge
ISO 15118
Driver ID Billing
Fleet Invoicing
CPMS