The engine that decides which reservation a charge belongs to.
A toll transaction only has a plate or transponder number and a timestamp — it doesn't say which guest or reservation it belongs to. Kelviz's matching engine figures that out by checking which vehicle was on an active reservation at that exact time, and how confident it is in the result.
Multiple signals, not just one
Plate match, transponder match, and reservation time-window overlap are each checked independently and combined into a single confidence score — so a charge isn't matched on a single coincidental signal alone.
Confidence, not certainty
High-confidence matches are applied automatically. Lower-confidence matches go to a review queue instead of being silently accepted or silently dropped, so you stay in control of anything the engine isn't sure about.
Configurable per organization
Matching behavior can be tuned per organization — useful if your fleet's vehicles are more likely to share plates across time (e.g. reassigned transponders) than another operator's.
Frequently asked questions
What happens when two reservations could both match a charge?
The engine scores each candidate reservation and picks the strongest match; ambiguous cases are routed to the review queue rather than guessed at.
Related reading
How to Match E-ZPass Transactions to Turo Trips
A step-by-step walkthrough for turning a raw E-ZPass statement into toll charges matched to the exact Turo reservation and guest responsible for each one.
How to Match SunPass Tolls to Turo Trips
A practical workflow for matching SunPass or Toll-by-Plate transactions to the correct Turo vehicle, reservation, and guest.
How Toll Reconciliation Actually Works
What happens between uploading a toll export and a guest-ready reimbursement case: plate matching, transponder matching, and confidence scoring.
What Happens When a Toll Has the Wrong License Plate?
Investigate plate-entry errors, misreads, historical plate transfers, and possible plate cloning before assigning a toll to a Turo guest.
How a Turo Fleet Can Use a Data-Quality Review Queue
A completed import doesn't mean the data is correct — see how a categorized queue turns inconsistencies into resolvable work.
How to Fix "No Matching Vehicle" in Turo Fleet Data
A "no matching vehicle" issue means a transaction can't be reliably tied to a fleet vehicle — how to fix it safely.
How to Fix Overlapping Turo Reservations
Two reservations on one vehicle can't both prove possession at a toll timestamp — how to find and resolve the overlap.
How to Fix Missing Trip History in a Turo Fleet
Toll matching needs to know which reservation had a vehicle at a given time — how to fix a gap in trip history.
Let the matching engine do the reconciling.
Create an account and see your first toll export matched automatically.