Track Uber, Bolt, cash and card revenue in one place

A driver finishes a week having taken some fares in cash, some on the card terminal, some through Bolt and some through Uber, plus a couple of account journeys to be invoiced. Revenue-wise it is one number. Cash-wise it is four completely different situations.

The cash sits in the driver's pocket until they hand it over. The card takings landed in the company account, minus the acquirer's cut, on a settlement delay. The Bolt and Uber earnings arrive from the platform on their own schedule, net of platform commission. The invoiced journeys have not been paid at all yet.

A spreadsheet that stores one weekly total loses all of that. And once it is lost, the driver balance computed from it is wrong in a way that is very hard to argue about later, because the underlying detail no longer exists.

In Tomcabs the payment method is part of the race, not an afterthought. When a driver encodes a journey they select how it was paid: cash, card, Bolt, Uber, or invoice. It takes one tap and it happens while the driver still remembers.

Because that attribute exists on every record, every aggregate the system produces can be split by it. Revenue for a shift, for a driver's week, for a vehicle, or for the whole company can be shown as a breakdown rather than a single figure.

It is a small piece of data that determines whether the rest of the finance picture is usable. Without it, everything downstream is an estimate.

The weekly driver balance answers one question: at the end of this week, does the driver owe the company money, or does the company owe the driver? Getting that right requires knowing which revenue physically passed through the driver's hands.

Tomcabs computes the balance from the recorded races and their payment methods, together with the commission arrangement and any expenses the driver logged during their shifts — fuel, a car wash, a parking fee. Cash held by the driver reduces what the company owes them; platform revenue that never touched the driver does not.

The result is a balance a driver can read and check line by line, which is worth more than a balance that happens to be correct. Disputes about money are usually disputes about visibility.

Platform earnings recorded at the point of the race are gross of commission and arrive later than the work. When the payout lands, a manager wants to know whether it matches what the drivers recorded.

Tomcabs gives you the recorded side of that comparison in a form you can total per platform and per period, which is the part that used to require reading back through paper slips. Comparing that against the platform's own statement is then a single check rather than a reconstruction.

Where the two disagree, the discrepancy is attributable — you can see which driver and which shift the difference came from, instead of knowing only that the week is short by ninety euros.