Module · Aggregator data reconciliation
End the arguments over earnings with an Uber and Bolt discrepancy controller
A driver looks at the Uber app and sees one figure; the balance in the CRM shows another. For a fleet owner that is not an error in a table but a conversation in which you have to prove nobody is being robbed. The discrepancy controller makes sure both figures are the same figure.
crm.fleetsoft.pl
Driver transactions from Uber and Bolt: credits, debits and the balance before and after each one. Personal data hidden.
Why earnings data drifts apart
The driver app and the aggregator's official report are two different sources describing the same working day. The driver sees rides as they happen, the fleet settles on the basis of reports, and between the two sits a whole set of operations that Uber and Bolt correct only after the fact: settlements for rides paid in cash, bonuses added and taken back, adjustments.
The outcome is always the same. A driver turns up with a phone in hand and asks where the difference went. The manager has nothing to answer with, because in the fleet system the amount simply has not arrived yet. The longer this goes on, the more firmly the crew comes to believe the fleet is making something on the side. That is a business problem, not a technical one.
There is a purely technical part on top of that: Uber runs several API versions, which means the cash position in the fleet's system can update with a delay. A difference of that kind reaches about 200 zł. Enough to damage a relationship, and little enough that nobody wants to chase it by hand.
This page is about trust, not about tables
Drivers who once become convinced the fleet is shaving their earnings will not change their minds after one conversation. They move to a competitor and tell a few colleagues on the way. That reputation costs far more than any single difference on a balance.
The discrepancy controller spares managers the job of proving their own honesty. Instead of an argument along the lines of "my app says something else", there is one shared version of the data that both sides see at the same time. The conversation with the driver stops being a confrontation and becomes a check of a line on a list.
It also means less work in support. Every "the amount does not match" ticket ties up a manager who compares the aggregator report with the system by hand. When the data reconciles automatically every hour, that kind of ticket stops coming in.
Frequently asked questions
How often is data from Uber and Bolt updated?–
Synchronisation runs on an hourly cycle. The driver's balance in the CRM does not wait for the weekly settlement close; it keeps up with what is happening on the aggregator's side.
Where do the differences of around 200 zł come from?+
From delays in cash updates caused by the different API versions on Uber's side. Those are exactly the delays the module removes, so the amount in the fleet system does not drift from what the driver sees in the app.
Does the module account for cash and bonuses?+
Yes. Synchronisation covers settlements for rides paid in cash and bonuses that aggregators correct after the fact, adding or withdrawing them once the ride is over.
What happens if the aggregator integration stops working?+
The system automatically switches to backup parsing, an alternative way of collecting the data. Settlements with drivers carry on, with no break in what is credited to them.
Do drivers see the same data as the manager?+
Drivers have a view of their balance, ride history, transactions and credited bonuses in the app, based on the same synchronised set of data the manager works with in the CRM.
