· 1 min read
The expense-report case against booking your own rideshare
The fare is only part of the cost. Processing, variability and duty of care are the rest — and they are where the arithmetic changes.
Finance teams compare ground transport on fare alone, which is the one number that flatters the app. It is worth looking at the whole cost, because the fare is often the smallest part.
Processing cost
Every self-booked trip becomes a receipt, an expense line, an approval and a reimbursement. Estimates of what it costs an organisation to process a single expense claim vary, but nobody credibly puts it at zero — and a travelling team generates a great many of them. A monthly consolidated invoice replaces all of that with one document.
Variability
A budget is easier to hold when the number does not move. Surge pricing means the same trip costs different amounts depending on weather and demand, and it surges hardest exactly when travel is most disrupted — which is to say, when your people most need to get somewhere.
Duty of care
If an employee travelling on company business is picked up by an unknown driver in an unrecorded vehicle, the organisation has no record of the journey. With a booked account there is one: assigned chauffeur, vehicle, route, timestamps. Whether that matters depends on your sector, but where it matters, it matters a great deal.
Where rideshare genuinely wins
Ad-hoc short trips, single travellers, low-stakes journeys in fair weather. We are not arguing it has no place. We are arguing that the airport run for a client-facing executive at 6am in February is not that trip.
The practical answer
Most of our corporate clients use both, with a policy line: booked cars for airport transfers, client movements and anything before 7am or after 9pm; rideshare for everything else. See corporate accounts.
