How to Handle Tolls Between Back-to-Back Turo Trips

A toll recorded between two close reservations is one of the easiest charges to assign incorrectly. The scheduled trip windows may not reflect actual possession, and the vehicle may have been moved by the host, a cleaner, a delivery driver, or the previous guest.

Use the actual travel timestamp, and build a boundary timeline

Don't match from the statement date — obtain the toll event time and confirm its time zone; if the provider reports only a date, confidence should be lower. Record the first reservation's scheduled end, actual return and check-in evidence, vehicle location after return, cleaning/fueling/charging/maintenance/delivery movement, the second reservation's release and scheduled start, and the toll transaction time and location.

Identify actual possession, and use geography as a consistency check

The guest whose reservation is closest isn't automatically responsible — review trip messages, check-in/checkout records, delivery assignments, and lawful vehicle data rather than relying on memory. Compare the toll location with the return site, next pickup, and known vehicle movement; an impossible route can reveal a wrong timestamp, plate, or proposed reservation.

Route ambiguity to review, and reduce future boundary ambiguity

If evidence can't distinguish the trips, don't force an automated match — mark the charge unresolved, document what was checked, and follow Turo's current evidence requirements. Capture actual handoff times, standardize delivery logs, import reservations promptly, record late returns, and avoid broad matching buffers that cause overlapping candidates. Kelviz can identify possible reservations from plate, tag, and time-window data while sending boundary conflicts to human review.

A worked example

Trip A ends at 2:00 PM. Trip B, a different guest, begins at 2:15 PM on the same vehicle. A toll posts at 2:08 PM. Absent other evidence, this falls in the 15-minute gap between trips — likely a host or cleaning-crew movement, not either guest's responsibility. Check delivery logs and check-in photos for that window before defaulting to "nearest trip"; a toll in a genuine handoff gap usually isn't billable to either guest.