What a driver settlement actually is
A settlement is the weekly reconciliation of everything a driver earned and owes, reduced to one number: what you pay them (or occasionally, what they owe you). In a fleet running on Uber, Bolt or FreeNow, that means merging money that arrives in three different shapes:
- Platform money — gross fares, minus each platform’s commission, plus tips and bonus campaigns, per platform.
- Cash — street fares and cash trips the driver already has in their pocket.
- Fleet-side items — car rent, fuel cards, damage deductions, advances, bonuses.
Every fleet computes some version of this. The difference between professional and chaotic fleets is whether it’s computed systematically — same rules, every driver, every week — or reinvented each Monday in a spreadsheet.
The inputs: where the numbers come from
A clean settlement starts with clean inputs, gathered per driver per week:
- Platform statements. Uber, Bolt and FreeNow each report gross fares, their commission, tips and campaign bonuses — on their own schedules, in their own formats. Keep them separated by platform in your records; blended totals make errors undiscoverable.
- Shift data.Hours worked and kilometres driven, from clock-in to clock-out. This is what makes per-hour and per-km sanity checks possible — and it’s free if drivers already clock in through an app (live tracking).
- Cash declared.The driver’s cash takings, declared per shift, not reconstructed from memory a week later.
- Standing items. Weekly car rent, fuel card bills, repayment instalments — the recurring lines that should never depend on anyone remembering them (adjustments).
Pay schemes: the rules of the split
On top of the inputs sits the pay scheme — the agreement that says how the pot divides. Common shapes in taxi and rideshare fleets:
- Percentage split — driver keeps, say, 40–60% of net fares; the split may differ for tips (often 100% to the driver) and campaigns.
- Rent model — driver keeps everything but pays a fixed weekly rent for the car.
- Hybrids — a lower split plus reduced rent, guarantees for new drivers, different rates per platform.
Two rules keep schemes from becoming a source of warfare. First, write the scheme down per driver— “the usual deal” is not a contract. Second, apply it mechanically. The moment a split is negotiated per-week, every week becomes a negotiation. In Rovora, schemes are saved as presets and assigned per driver, so the same rules run every settlement automatically (flexible pay).
A worked example
Take a driver on a 50% net-fare split, 100% of tips, €0 rent, one week:
- Uber: €820 gross fares, €205 commission, €38 tips → net fares €615
- Bolt: €540 gross fares, €135 commission, €22 tips → net fares €405
- Cash trips: €180 (already in the driver’s pocket)
- Fuel card: €95 · Damage deduction agreed: €40
Driver’s share: 50% × (615 + 405 + 180) = €600, plus €60 tips = €660 earned. They already hold €180 cash, and owe €95 fuel + €40 damage. Payout: 660 − 180 − 95 − 40 = €345.
Nothing here is hard maths. It’s bookkeeping under time pressure, ×15 drivers, ×52 weeks— which is why it’s where fleets most often leak money and goodwill. The payslip should show every line above, so the driver can verify it in thirty seconds (weekly settlements).
The five classic mistakes
- Splitting gross instead of net (or vice versa) — be explicit about whether commission comes out before the split; this is the #1 source of disputes.
- Blending platforms — one merged total means a platform’s reporting error silently becomes your error.
- Forgetting standing deductions — un-invoiced fuel weeks and skipped rent, discovered months later, are unrecoverable in practice.
- Settling from memory-cash — cash declared at shift end is data; cash recalled on Friday is fiction.
- Paying without a payslip — a bank transfer with no breakdown converts every rounding doubt into a dispute.
If reading that list felt uncomfortably familiar, the fix isn’t more discipline — it’s a system where the discipline is built in. That’s the case we make in spreadsheets vs fleet management software.
