Ride-hailing, taxi, rental and leasing
Know your charging cost per kilometre, per vehicle
In a mobility business the margin is in the cost per km. Getz EMP records the kWh and cost of every session against the driver and the vehicle, and lets you decide per fleet whether the company or the driver-partner pays.
The operator’s problem
Why charging cost is hard to pin down in mobility fleets
Several drivers per car
Shift drivers and driver-partners share vehicles, so cost per driver and cost per vehicle diverge.
Who pays varies
Employed drivers charge on the company; driver-partners and rent-to-own drivers pay their own way.
Estimates instead of measurements
Business cases rest on assumed kWh per km until the fleet measures it.
Cost per km
Work out your energy cost per kilometre
Cost per km: enter your own figures
Nothing is pre-filled and nothing is sent anywhere. Use your vehicles’ measured energy use and the prices you actually pay; the result is simple arithmetic, not a quote or a promise of savings.
| Per vehicle | Electric | Fuel |
|---|---|---|
| Cost per km | — | — |
| Cost per week | — | — |
| Energy per week | — | — |
Enter the energy use and charging price to see a result.
Two operating models
Company pays, or the driver-partner pays
Set it per fleet. Many operators run both: company-paid for employed drivers, driver-paid for partners and rent-to-own.
| Capability | Driver pays | Company pays |
|---|---|---|
| Who is charged | The driver’s wallet or saved card | The fleet’s corporate account |
| Before the start | The estimated cost is reserved in the wallet | Policy and credit-limit checks |
| Site, network and hour limits | NoNot applied | YesChecked at every start |
| kWh limit per session | No | Yes |
| Fleet manager sees the sessions | Yes | Yes |
| Where the cost shows up | The driver’s receipts and CSV export | The corporate account and its monthly statement |
How Getz EMP handles it
Mobility requirements, mapped to settings
| Capability | Getz EMP setting |
|---|---|
| Charging only in shift gaps | Charging windows per fleet, including overnight |
| Cards that stay with the car | RFID cards per vehicle; Autocharge where car and charger support it |
| Driver-paid sessions reserved up front | Wallet holds: the estimate is reserved before the start, the rest released after |
| Card-free top-ups for drivers | Cards, plus SnapScan and Zapper QR payments |
| Events in dispatch or telematics | Signed webhooks per event type, optionally per fleet |
Evidence
When the driver pays, the wallet reserves the estimated cost
When a driver-partner pays, the wallet reserves the estimated cost before the charger starts. When the operator’s charge record arrives, the real cost is taken and the rest is released, and the driver sees both amounts in the app.
If the wallet does not cover the estimate, a saved card pays the rest. With no card, nothing is sent to the charger and the driver is asked to top up or add a card. A refusal at the charger (an RFID card, for example) is kept with its reason in the authorisation log, which the fleet manager sees for their own members.
- Wallet holds and the payment logic behind them
- Itemised receipts with VAT for every session
The wallet: balance, amounts reserved for charging and payment preferences.
- What you see: available and reserved rand
- Why it matters: drivers always know what they can spend
Running a larger driver base?
Fleet tools, or your own charging app
Fleet tools
Your drivers charge with the DriEv app, and you manage policies, accounts and statements in the back office.
Your own branded driver app?
If you want to run a charging app under your own brand for your drivers, Getz EMP is also a white-label platform.
Talk through your operating model
Tell us how your drivers are engaged and paid. We configure a demo fleet to match and show where the cost per session is recorded.