How to Handle a Duplicate Turo Reimbursement Request

A duplicate reimbursement request can happen even when the underlying toll appears only once — the same transaction gets added to two cases, a corrected invoice coexists with the original it was meant to replace, or two team members submit independently. This is a different problem from duplicate *transactions* entering an import; see How to Prevent Duplicate Toll Charges in a Turo Fleet for that side of it.

Confirm it's actually a duplicate before touching anything

Compare the provider transaction or citation ID, vehicle and plate, date, time, location, amount, reservation, original invoice number, and submission or payment status — two tolls with the same amount aren't automatically duplicates.

Use Turo's official cancel-and-resubmit process

Turo's current guidance lets a host cancel an invoice and send a corrected one from the trip's Details page under Create or view invoices. Don't submit a second, separate invoice while a known duplicate is still active — cancel the wrong one first, and contact Turo support if the duplicate has already been paid or falls outside the self-service window.

Communicate plainly if the guest was actually charged twice

Acknowledge the error and use the authorized Turo process to correct it, rather than asking the guest to sort out an internal bookkeeping problem outside the platform.

Fix the cause, not just the invoice

Identify whether the duplication came from a reimported source file, a statement-and-mailed-notice overlap, manual entry alongside an automated import, two staff members working the same case, or a cancelled invoice that wasn't reflected internally — then add the corresponding safeguard. Kelviz can track transaction-to-case relationships and billing status so an already-submitted charge is visible before it's added to a second invoice; confirm current enforcement behavior before making a specific product guarantee to a guest.