Spot duplicate rental charges after an equipment swap

By RentalSpend · October 10, 2026

An equipment swap can leave two active rental tickets, but that does not automatically mean both charges are valid. Compare the contract, the asset number, ticket status, off-rent proof, and billing dates to see whether the old ticket should have stopped when the swap occurred.

When a swap creates two active rental tickets, treat it as a reconciliation issue, not proof that both charges are valid. The quickest check is to line up the contract terms, the asset or equipment number, the ticket status, the off-rent or pickup confirmation, and the invoice billing dates. If the same unit is still active on the old ticket after the swap, that ticket may keep billing until it is properly called off rent under the supplier’s process; if the new ticket also starts billing before the old one stops, you may have overlap that should be voided, credited, or reissued according to the agreement.^[1][2][3]

Old ticket still active after the swap

This is the most common problem to check first. A swap may have physically moved the equipment, but the supplier system may still show the original ticket open if the off-rent action was never completed or never confirmed. United Rentals’ US terms say rental charges end when the equipment is returned or when the customer calls it off rent and obtains an off-rent confirmation number, and the customer remains responsible until the equipment is returned or picked up. That means a missing off-rent confirmation can leave the old ticket billing longer than expected.^[1]

• Confirm the old ticket has a closed, off-rent, returned, or completed status in the supplier portal or paperwork.
• Match the old ticket’s end date to the pickup time, return time, or off-rent confirmation time shown on the supplier record.
• Check whether the same serial number or unit ID appears on both tickets.
• Look for a credit memo, void, corrected ticket, or reissued invoice if the supplier already accepted the swap as a replacement.
• Hold payment if the old ticket is still billing past the actual off-rent event and no contract language supports that overlap.

Sources: ^[1][2][3]

Both tickets bill the same asset for the same dates

If the old and new tickets both show the same equipment number, or if the dates overlap for the same unit, that is the clearest sign of a duplicate charge. AP duplicate controls often catch exact invoice-number matches, but they can miss rental duplicates when the invoice numbers differ. Oracle’s guidance says duplicate reviews should not rely on invoice number alone and should use periodic audits to find duplicates. For rental spend, the useful match is not just invoice number; it is asset number, site, dates, and billing status.^[3][4]

If the same asset is billed on both lines for the same dates, do not pay both as written. Ask the supplier to explain whether one line should be voided, credited, or reissued under your agreement. The right fix depends on the contract and on how the vendor records the swap, so do not assume the first invoice you see is the correct one.^[1][3]

The swap created a new ticket, but the old one was never called off

This situation can look like two valid rentals in the system even though only one unit should have been billed at a time. Herc’s rental-agreement training shows that users can select equipment to return or call off rent from the rental agreement, which reinforces that the administrative closeout matters as much as the physical move. If the dispatcher, field team, or branch did the swap but nobody completed the off-rent step, the old ticket may stay open until someone fixes it.^[2]

• Check who initiated the swap and whether they also submitted the off-rent request.
• Look for a customer reference, off-rent number, return number, or pickup confirmation tied to the old ticket.
• Verify whether the replacement ticket started on delivery, on rent, or another contract-defined trigger.
• Confirm that the old ticket was not left open because of a missing signature, missing serial number, or incomplete return record.
• If the supplier needs a specific form or portal action to stop billing, make sure your team used it every time.

Sources: ^[1][2]

Invoice number differs, so the duplicate was missed

Many AP systems only flag exact duplicate invoice numbers, which is not enough for rental swaps. Oracle notes that duplicate invoice controls may need to look beyond invoice number because the same invoice can be entered again under a different name or in a different format, and Oracle recommends periodic audits to catch duplicates. That same idea applies to rental tickets: two different invoice numbers can still bill the same asset for the same dates after a swap.^[3][4]

• Search by supplier, site, asset number, and date range instead of invoice number alone.
• Review whether one invoice was reissued after correction and whether the original was voided.
• Compare line-level descriptions, not just totals, because a corrected ticket may split or rename charges.
• Run periodic duplicate checks on active rentals, not only on posted invoices, so overlap is caught before payment.
• Use the supplier’s own terminology, since one vendor may call the event a return and another may call it an off-rent or pickup.

Sources: ^[1][3][4]

How to decide whether to pay, hold, or dispute

Use the same practical test every time: does each charge map to a real period of possession under your agreement? If the old ticket covers dates after the equipment was returned, picked up, or confirmed off rent, that portion should generally not be paid as billed. If the new ticket is for the replacement unit and starts at the correct delivery or on-rent time, it may be valid. If both tickets cover the same unit for the same dates, hold payment and ask for correction before the invoice is released.^[1][3]

1. Match the ticket to the physical equipment movement first.
2. Check whether the old ticket ended on a valid off-rent or pickup event.
3. Check whether the new ticket starts only when the replacement unit actually became available to use.
4. Compare invoice lines against the contract, rate sheet, and any swap-related notes.
5. Release only the amount that fits the verified rental period; dispute the overlap.

Sources: ^[1][2][3]

Illustrative example: a swap with one valid charge and one overlap

To apply the same check to your own invoices, isolate the equipment ID that moved, find the exact off-rent or pickup event, and then recalculate the bill from that point forward. If the old ticket still shows rent after the move, question the overlap. If the supplier can show that your contract required a different stop date, use your agreement and rate sheet to confirm it before paying.^[1][3][4]

What to do when a problem shows up

• If the old ticket is still open: ask the supplier to close it effective the actual off-rent or pickup date.
• If both tickets overlap on the same asset: request a void, credit memo, or corrected invoice for the overlapping period.
• If the replacement ticket starts too early: ask for a reissue that begins on the correct delivery or on-rent date.
• If the supplier says the billing is correct: ask for the contract clause, rate sheet rule, or system record that supports the dates.
• If your system already paid the invoice: reverse or recover only the disputed overlap, not the valid rental period.

Sources: ^[1][3]

The practical goal is simple: pay for the actual rental period that your agreement supports, and no more. When a swap leaves two active tickets, the right response is to verify the event records, not to assume the second line is either valid or invalid without proof. Keep the off-rent record, pickup record, ticket status, and invoice together so the next swap is easier to reconcile.^[1][2][3][4]

← All resources