Guides

How to Handle an Incomplete Toll or Reservation Import

An incomplete import is dangerous because the rows that did load can look correct — check source coverage directly.

By Kenneth Elliott
Kelviz Imports page showing toll-file uploads with row counts and upload timestamps
File-level history helps establish what was actually uploaded, when, and how its rows were classified — the starting point for checking coverage.

An incomplete import is dangerous precisely because the records that did load can look entirely correct on their own — the missing rows are invisible unless the fleet specifically checks source coverage and totals against what was actually expected, rather than just confirming the import didn't throw an error.

Compare source and imported counts, and check date coverage

Record the source row count, expected transaction count, accepted rows, duplicate rows, rejected rows, and ignored rows, and account for every difference between them. Then separately confirm the earliest and latest transaction or reservation date actually present — a file named "August" can quietly contain only part of the month if the export itself was cut short.

Check financial totals, and review import history

Compare the provider's stated totals against your accepted, duplicate, rejected, and excluded amounts — but avoid comparing a raw statement balance against raw toll totals if that balance also includes payments, adjustments, or fees mixed in. File-level import history helps establish what was uploaded, when, and how its rows were ultimately classified.

Pause conclusions until coverage is confirmed complete

Don't trust match rates, unmatched counts, or reimbursement totals from a period you haven't confirmed is fully imported — a low match rate might just mean half the reservations for that period never made it in. Once you've obtained a fresh export, import the missing period, review how duplicates were handled, and reconcile the totals again before drawing any conclusions from the numbers.

A worked example

A file named "August-tolls.csv" imports successfully with 340 rows and zero errors — but the source provider's actual August statement had 412 transactions. Nothing about the successful import would reveal the missing 72 rows on its own; only comparing the source total (from the provider's own summary page or PDF) against what actually landed catches it. A clean import log is not the same thing as a complete one.

KE

Kenneth Elliott

Kenneth Elliott operates Elliottz Motors and has managed more than 1,000 Turo trips.

#troubleshooting#imports#data-quality#turo-hosts

Frequently asked questions

Can the import system detect every incomplete file on its own?

Not always — it generally can't know what a provider omitted from their own export. Source coverage and total reconciliation remain something a person has to actually check.

Should reports exclude periods with known incomplete coverage?

Label them clearly as incomplete, or delay drawing conclusions from that period until full coverage is restored — don't present a partial period as if it were complete.

Related reading

Ready to put this into practice?

Create an account and see how Kelviz handles your own fleet's tolls and tickets.

Kelviz uses analytics cookies to understand how the site is used. Your session stays logged in either way — this only affects analytics. Cookie Policy