Sample case study: one payment record for 1,200 vehicles

Silver Top Taxis runs 1,200 vehicles across Melbourne. Until last year its fares, acquirer settlements and driver payouts lived in three systems, and the month closed nine days late.

What changed

Every fare now books a pending receivable the moment the terminal captures it. The acquirer's bulk deposit, one to six days later, matches against those receivables line by line through the bank feed, and the net payable to each driver is worked out after splits, fees and withholdings.

One trip record

The fare taken in the back seat, the settlement from the acquirer, the split by agreement and the payout to the driver all sit on one trip record. Nobody retypes anything, and a dispute is answered from the record rather than reconstructed.

"We closed September in two days. The finance team spent the other seven on the business instead of the bank feed."

Where the time went

Most of the nine days were spent matching deposits by hand against three acquirer portals, then explaining the differences to drivers.

What the finance team does now

Exceptions only. The bank feed does the matching; the team works the handful of lines that do not reconcile.

Results

• Month-end close from nine days to two.
• Three acquirers reconciled through one bank feed.
• Driver payout queries down by two thirds.

Lease fees, affiliate subscriptions and invoice payments go through the same three steps, so the network's finance team works one process rather than four.