Fleet management
Every fleet driver, vehicle and session in one place
Set up fleets with their members, vehicles and charging tokens, set the policy the platform enforces at every start, and give each fleet manager a view of their own fleet only. Your drivers charge with the DriEv app, which shows them the fleet’s rules in plain words.
Building blocks
What a fleet is made of
A fleet groups drivers and vehicles under one policy. A company can run several fleets, for example one per depot or per country, each billed to a corporate account.
Fleets
Each fleet has a name, a policy (who pays, where, when and how much) and, when the company pays, a corporate account it bills to.
Members
Drivers are invited by phone number or e-mail and join only when they accept in the driver app. Nobody is added to a fleet without knowing.
Vehicles
Fleet vehicles are linked to the fleet, so sessions can be traced to the car as well as the driver.
Tokens and RFID cards
Drivers start from the app, an RFID card or, where the car and charger support it, Autocharge by vehicle ID. Lost cards can be blocked.
Sessions and charges
Every session, charge record and rated charge for the fleet’s members, with the price lines and VAT behind each one.
Real-time authorisation
Every start is checked by the platform at the moment it is requested: the driver, the token, the fleet policy and the way it will be paid.
Driver and vehicle policies
Four rules, each optional, checked at every start
A fleet policy sets who pays and, for company-paid charging, where, when and how much. Leave a rule empty and it restricts nothing.
Allowed sites
Your depots, offices or the forecourts on your routes. An unknown site is refused when sites are restricted.
Allowed networks
Allow every site of chosen charging operators instead of listing sites one by one.
Charging windows
Weekday windows in a time zone, including overnight windows such as 22:00–05:00.
kWh per session
An energy cap per session; the platform stops the session when it is reached.
Fleet manager access
Clear rules for drivers, a scoped view for managers
Drivers join by accepting an invitation in the app; fleet managers see only their own fleet, enforced by the API.
Drivers see the same rules in the app, in plain words: “Company charging is limited to 3 approved sites”, “Each session stops at 40 kWh”. What the driver reads is what the platform enforces.
A fleet manager works only inside their own fleet; anyone outside it does not exist for them. The table below shows who sees and does what.
- Scoped visibility for fleet managers, enforced by the API
- Invitation by phone or e-mail, accepted in the driver app
- Policy summary in the app, generated from the enforced policy
Fleet invitations: a driver joins a company fleet only by accepting.
- What you see: the invitation with accept and decline
- Why it matters: the company pays only once the driver has agreed
Roles
Who sees and does what
Roles are enforced by the platform on every request, not only hidden in the screens.
| Capability | Fleet manager | Finance | Driver |
|---|---|---|---|
| Drivers, vehicles and tokens | Their own fleet’s members; invite members, add or remove members and vehicles | All accounts | Their own |
| Sessions, charge records and charges | Their members’ only | All, plus collections and refunds | Their own, with receipts |
| Driver wallets | Their members’ balances and wallet entries (read only) | Adjust and reverse entries; approve payouts | Their own |
| Home-charging reimbursements | Their members’ (read only) | Record, approve, reject and pay | Their own: period, kWh, rate, amount and status |
| Fleet policy and corporate account | NoChanged by administrators or operations | Credit limits; prepaid wallet top-ups in US dollars | The fleet’s rules, in the app |
| Statements | Their own account’s (read only) | Issue and manage; finance export | No |
Billing
Two ways to run a fleet
The policy decides who pays. You can change it per fleet.
| Capability | Driver pays | Company pays |
|---|---|---|
| Who is charged | The driver’s wallet or saved card | The fleet’s corporate account |
| Where the cost shows up | The driver’s receipts and CSV export | The corporate account and its monthly statement |
| Site, network and hour limits | NoNot applied | YesChecked at every start |
| kWh limit per session | No | Yes |
| Credit limit check | No | Yes |
| Fleet manager sees the sessions | Yes | Yes |
Connect your systems
Fleet events into your own tools
Signed webhooks per fleet
Subscribe a fleet or telematics system to the events it needs, optionally for one fleet only. Deliveries are signed, retried with backoff and logged, with a test event you can send from the back office.
Finance export
A CSV of every driver charge, payment and refund created in a period, built on request, for your finance team or accounting system.
Real screens
Fleet management in the back office and the app
Captured with fictional demo data. Select a screen to enlarge it.
Fleets with company-pays rules, drivers, vehicles and corporate accounts.
Corporate accounts carry the billing terms and the balance of company-paid charging.
Questions about fleet management
Can one driver be in a fleet and still charge privately?
Yes. Fleet membership adds company charging under the fleet’s rules; the driver’s own wallet and cards stay theirs. Who pays for a session is decided when it starts.
Does this manage our depot chargers?
No. Chargers are run by their charge point operator, which looks after power, load, firmware, connectivity and faults and decides who may use its sites. Getz EMP decides which of your drivers charge on the company account, where, when and how much, and who pays. If your depot sites are published through Getz Hub, you can restrict company charging to them; their status comes from the operator.
See your fleet set up in the back office
Bring your fleet structure, and we will walk through fleets, policies, invitations and statements with demo data.