How Kelviz Organizes Parking Tickets, Traffic Tickets, and Toll Invoices
Tolls arrive as structured data; tickets usually arrive as images or PDFs — see how one workflow handles both.

Tolls usually arrive as structured account activity; tickets and non-standard toll invoices usually arrive as images or PDFs instead. The source format is different, but every item needs the same operational answers: which vehicle, which reservation, what incident date, what amount, what deadline, and what outcome.
Bring documents into a structured, filterable queue
Kelviz's Tickets screen supports document upload alongside filters for citation or agency, document type, state, review status, billing status, payment status, incident date range, due date range, and amount range — so a review workload doesn't stay spread across email threads and downloaded PDFs with no way to search across them.
Use OCR as an aid, not an authority
OCR can propose values like citation number, agency, plate, incident date, amount, and due date from a scanned document — see How OCR Turns a Parking Ticket Into Structured Fleet Data for how that extraction actually works. Every material field still gets reviewed against the original document before it's trusted for billing.
Match the reservation, and keep legal status separate from reimbursement status
The incident timestamp and vehicle identify the likely reservation — the document itself never names the Turo guest. And paying or contesting the issuing authority is a separate track from seeking Turo reimbursement; both outcomes need to be preserved on their own, since resolving one doesn't resolve the other. Kelviz doesn't decide legal liability — it organizes the data and workflow, while local law, the issuing authority, Turo's policy, and the actual evidence determine responsibility.
A worked example
A citation and a toll invoice both reference the same reservation, arriving three weeks apart from different sources — one as a mailed PDF, one as structured account data. Kept in a single system with a shared vehicle and reservation match, both surface on the same case timeline automatically. Kept in separate tools, the connection between them depends entirely on someone remembering both exist for the same trip.
Kenneth Elliott operates Elliottz Motors and has managed more than 1,000 Turo trips.