What Documentation Do Turo Hosts Need for Toll Reimbursement?

A good toll reimbursement record should let another person quickly answer four questions: which vehicle incurred the toll, when and where it happened, how much was charged, and which reservation had the vehicle at that time. Turo determines the official evidence requirements — this checklist helps hosts build a clear, auditable record before using Turo's reimbursement workflow.

Toll evidence checklist

Preserve as many of these fields as the provider supplies: toll-agency/provider name, account or statement reference, transaction date and time, posting date if different, road/plaza/gantry/bridge/location, license plate or transponder number, toll amount, fees shown separately, payment status or receipt, and the original statement, invoice, or transaction page. Don't edit a provider document in a way that obscures context — if you create a summary, keep the source record too.

Reservation evidence checklist

Your internal matching record should include the reservation/trip number, vehicle and plate, guest name or internal reference, trip start and end timestamps, pickup/return details when relevant, and the reason the transaction was matched. When matching by transponder, also preserve which vehicle the transponder was assigned to on the transaction date.

What makes evidence weak

Common problems: a bank/credit-card charge with no toll details, a screenshot with no plate or transponder, a total balance with no individual transactions, a cropped notice missing the agency name, a posting date presented as the travel date, a manually typed list with no source document, or multiple tolls combined without a calculation shown.

Create a guest-readable summary, and store evidence securely

For multiple charges, provide a simple table with date, time, location, and amount, with the total matching the invoice request — a clear presentation reduces confusion without replacing the official evidence. Toll statements can carry account numbers, plates, travel patterns, or personal information, so restrict access to staff who need it, use role-based permissions, and avoid sharing a full account statement when a narrower record satisfies the requirement.

Kelviz workflow

Kelviz organizes imported transactions, reservation matches, review decisions, and recovery records in one place, so operators can use the source data and matching context to prepare a clearer reimbursement case. See Features or Toll Reconciliation.