Getting Started with Kelviz
A first-time walkthrough: create your organization, add your vehicles, and import your first toll export.
What you'll need before you start
A Turo host account you can export reservation history from; either a login for your toll agency's account (E-ZPass, SunPass, TxTag, or similar) or a CSV/Excel export already downloaded from it; and each vehicle's license plate and issuing state. No API key or agency integration is required for a first import — Kelviz works from the same export file your toll agency's own website already produces. For a small fleet, expect the full sequence below — organization, vehicles, reservations, first import, review, first billed guest — to take under an hour, most of it spent in the review step, not the setup itself.
1. Create your organization
After signing up, you'll create an organization — this is the account your vehicles, reservations, and toll data belong to. If a teammate invited you instead, you'll see a pending invite to accept rather than a new-organization form. See Set Up Your Organization for the field-by-field walkthrough.
2. Add your vehicles
Add each vehicle in your fleet with its license plate (and transponder ID, if it has one). This is what the matching engine uses to link a toll or ticket charge back to a specific vehicle. See Add Your First Vehicle for what each field is used for.
3. Import your reservations
Import your Turo reservation history so Kelviz knows which guest and trip was associated with each vehicle at any given time — this is the other half of what the matching engine needs. See Import Reservations for supported formats.
4. Import a toll export
Upload a CSV or Excel export from your toll provider. Kelviz walks you through mapping its columns (plate, transponder, amount, timestamp) to what it needs — see Reservation Matching for how matching actually works once this data is in, or Add a Toll Account for connecting the account itself first.
5. Review matches
Most charges match automatically. Anything the matching engine isn't confident about lands in a review queue for you to confirm — check that queue before moving a charge into guest billing.
6. Bill your first guest
Once a matched charge clears review, it's ready for guest billing — Kelviz carries the vehicle, reservation, and evidence straight into a reimbursement case instead of making you re-enter anything. A typical first week looks like: day one, add vehicles and import reservation history; day two, import your first toll export and work through the review queue; by the end of the week, your first guest-ready case. See Guest Billing for what happens after a match is confirmed.
First-import checklist
Before you import your first toll export, confirm: your vehicles are added with the exact plate printed on the toll bill, not a personalized nickname you use for the car; your reservation import covers the same date range as the toll export, not just upcoming trips; the file is an itemized transaction export (one line per toll) rather than a monthly statement summary — see Supported Import Formats; and you know which state issued each plate, since two states can issue the same plate number to different vehicles.
Common mistakes to avoid
The most common first-import issues are self-inflicted, not a Kelviz limitation: importing reservations for one date range while the toll export covers a different one, so charges have no reservation to match against; entering a plate with different spacing, a hyphen, or vanity formatting than the toll agency printed on the bill; and uploading a summary statement instead of an itemized transaction export. If a batch lands in the review queue with a "no matching vehicle" reason, see Fix "No Matching Vehicle" Errors before re-importing rather than re-running the same import repeatedly.
Where to go next
The Help Center has the step-by-step version of every stage above, plus Upload Your First Ticket if you're tracking parking and traffic tickets in addition to tolls.