Pay for the kilometres driven, not the kilometres claimed.
Vendor Billing prices every trip from GPS kilometres, your contract rates and waiting time, compares it with what the vendor invoiced, and holds the difference until it is resolved.
| Vendor | Trips | Claimed km | GPS km | Payable | Status |
|---|---|---|---|---|---|
| Sai Travels | 12 | 231.6 | 228.9 | ₹8,940 | Matched |
| Metro City Cabs | 9 | 176.2 | 176.0 | ₹6,610 | Matched |
| Ganga Fleet | 8 | 162.0 | 149.3 | ₹5,910 | Disputed |
Ganga Fleet claimed 12.7 km above GPS on 2 trips. Payable held at GPS kilometres until the vendor responds.
Month-end billing without the month-end argument.
Bills are built trip by trip as the month runs, so there is nothing to reconstruct at the end of it.
Contract engine
Per-km, slab, package and dedicated-cab contracts per vendor, cab type and city, with rate revisions dated.
GPS kilometres
Distance from the trip's recorded route, with dead kilometres to and from the first and last stop handled by contract.
Waiting and no-shows
Waiting time from check-in timestamps, no-shows confirmed by the desk, both priced by your rules.
Disputes in one place
Mismatches open a dispute with the trip replay attached. Vendors respond, the desk decides, everything is logged.
Invoice reconciliation
Upload or receive the vendor invoice and match it line by line against Twrides trip records.
Finance-ready export
Approved bills export with cost centre, office and shift for your finance or ERP team.
One billing cycle, start to finish.
Shown for a monthly cycle. Weekly and fortnightly cycles work the same way.
Priced
Each closed trip priced from GPS km and contract.
Vendor invoice
Vendors submit invoices for the previous month.
Matched
Lines matched to trips, mismatches flagged.
Disputes
Vendors answer flagged trips with evidence.
Approved
Final payable approved and exported to finance.
Contracts the way your vendors actually sign them.
Most transport teams have a mix of contract types across vendors and cities. Twrides handles them side by side.
- Contract types
- Per km, slab by km band, trip package, dedicated cab per month
- Adjustments
- Night allowance, toll, parking, escort charges, waiting slabs
- Matching
- Claimed km against GPS km per trip with a tolerance you set
- Disputes
- Trip replay, timestamps and vendor comments on every flagged line
- Output
- Vendor-wise payable with cost centre and office split
Fair to vendors, too
Good vendors benefit from clean records. Billing is built to be checkable by both sides.
- Vendors see the same trip data and GPS kilometres the desk sees
- Every held amount has a reason and a trip attached
- Rate changes are dated so old trips are never repriced by accident
About Vendor Billing
What if GPS drops out during a trip?
Can vendors log in?
Do you pay vendors on our behalf?
Can we use different rates per city?
Close tonight's last trip with a green tick.
Bring one shift roster and your current vendor list. We plan, track and bill that shift on Twrides so your transport desk can compare it against last week.