Most enterprises reconcile vendor invoices against bookings rather than against trips that actually ran. Automated reconciliation compares every invoice line to GPS-verified trip data (actual route, distance, duration and passengers) and flags any line that does not match before payment is approved.

Why manual reconciliation fails

A transport invoice for a large site can carry tens of thousands of line items a month. Finance teams typically sample a few, check them against the booking sheet, and approve the rest. Three problems follow:

• Bookings are not trips. A booked trip that nobody took still appears as billable unless something proves otherwise.
• Distance is self-reported. Without GPS, the kilometres on the invoice are the vendor’s figure.
• Volume defeats sampling. Errors at 2–3% of line items are invisible in a sample and material in aggregate.

How automated reconciliation works

Every trip on the platform generates a verified record: GPS route, start and end time, distance travelled, employees on board and their check-ins. When the vendor invoice arrives, each line is matched against that record.

The system flags the following concerns:

Flagged lines route to an exception queue for approval or dispute. Clean lines pass through. The output is an audit trail showing what was paid and why.