How to spot overlapping rental charges on the same asset

By RentalSpend · October 5, 2026

The key test is simple: match the asset ID to the rental dates and flag any intersecting periods while both tickets are still open. Then verify off-rent, pickup, and contract terms before you approve the charge.

The fastest way to detect overlapping rental charges is to compare the same asset identifier across open tickets and check whether the billed date ranges intersect while both tickets are still active. Rental charges often begin when equipment leaves the branch or is delivered and end only when it is returned or formally off-rented and picked up, so the control point is the rental period, not just the invoice date. If two tickets show the same unit on the same days, treat it as an exception to review against your contract and off-rent records.^{[1][2][3][4][5][6]}

Same asset appears on two open tickets

This is the clearest overlap signal. Start by confirming whether the same serial number, unit number, fleet number, or other asset key appears on more than one active ticket. Then compare the start and end dates on each ticket and look for intersecting days. SAP supports date-range overlap checks in audit rules, which is the basic logic you want for this review.^[3][4][5]

1. Pull all open rental tickets for the supplier and period you are reviewing.
2. Group the tickets by asset identifier and supplier.
3. Flag any pair where the date ranges overlap.
4. Check the off-rent confirmation, pickup record, return record, and any written transfer or amendment that would justify the overlap.
5. Route any unresolved match to the supplier before payment.

Sources: ^{[1][2][3][4][6]}

If the overlap is real and not just a data issue, the question is which ticket actually owns the rental period. That answer should come from the documents your agreement uses to stop billing, such as off-rent confirmation, pickup timing, return status, or a written amendment if your contract requires one. Terms vary by supplier and by agreement, so use your own signed contract and rate sheet to decide whether a same-day changeover, transfer, or swap is allowed.^[1][2]

Invoice duplicate checks are passing, but the asset is still billed twice

A standard duplicate-invoice control may not catch this problem, because it usually compares invoice-level fields such as vendor, invoice number, date, or amount. SAP’s duplicate controls and Oracle’s invoice audit reports are useful for finding repeated invoices, but they are aimed at header-level matching. They can miss two different invoice numbers or ticket numbers that still charge the same asset during the same period.^[4][5][6][7]

What to do: keep your normal duplicate-invoice report, but add an asset-level rule that compares supplier, asset identifier, and date range. Oracle’s invoice audit listing is intended to review invoices by supplier, amount, and date range, and SAP’s duplicate checks can surface possible duplicate items based on configurable criteria. Use those controls for invoice-level duplicates, then add the overlap test for equipment charges.^[4][5][6][7]

• Supplier, invoice number, invoice date, and amount for invoice-level duplicate checks
• Asset identifier, ticket number, start date, and end date for overlap checks
• Off-rent confirmation, pickup record, and return status to support the rental stop date
• Any written amendment or transfer notice that would justify a second active ticket

Sources: ^{[1][2][3][4][5][6]}

The dates overlap, but one ticket may still be valid

Not every date overlap is an error. Some contracts and branch processes may allow a transfer, swap, or other adjustment, and the exact billing rules depend on your agreement. United Rentals’ terms say charges begin when equipment leaves the store location and end when it is returned or picked up after an off-rent notice and confirmation, while Sunbelt says the rental contract governs the equipment terms and can be modified only by written amendment. Use those kinds of contract controls to decide whether the overlap is actually billable.^[1][2]

How to confirm it: check the off-rent confirmation, pickup record, delivery record, and any written amendment or transfer notice your agreement requires. If the first ticket was not off-rented before the second began, ask the supplier to explain how both tickets can bill the same days. If your contract allows a same-day changeover or another exception, document that support before payment.^[1][2]

The equipment moved, swapped, or was re-rented

A move or swap can create a false overlap if the paperwork is incomplete. The practical check is to line up the equipment history with the invoice history: location, pickup request, return status, delivery date, and any work order or cost-center allocation. If the records show the same unit still out after a pickup request or off-rent notice, the timing needs to be reconciled before the charge is approved.^[1][2][6][7]

What to do: if the asset was swapped, confirm that the old unit was closed before the replacement unit started billing. If the asset was transferred between jobs, make sure the move is documented in a way your contract recognizes. If your system shows the same asset still out after the pickup request or off-rent notice, hold the charge until the billing window is explained.^[1][2][3][6]

A practical overlap test to run each cycle

1. Build a report of all open tickets for the period, using supplier, asset identifier, ticket number, start date, end date, and off-rent or pickup status.
2. Group the tickets by supplier and asset identifier.
3. Flag any pair where the date ranges overlap.
4. Check the off-rent confirmation, pickup record, return record, and any written transfer or amendment that would justify the overlap.
5. Send unresolved matches to the supplier before payment and keep them out of the final approval queue until the billing window is clear.

Sources: ^{[1][2][3][4][6]}

When the overlap is likely a true exception

Treat the overlap as a likely billing exception when the same asset is billed on two open tickets for the same days and you cannot tie one ticket to a valid closeout, transfer, swap, or contract-based exception. In that case, ask the supplier to explain which ticket owns the rental period and to back it with the off-rent or pickup record that supports the billed dates.^{[1][2][4][5][6]}

If the supplier’s record set is incomplete, your own accounting data can still help. Compare the invoice date, ticket date, payment status, and asset history in your AP or rental management system. The goal is to prove whether the unit was genuinely still out, or whether two active tickets are simply charging the same days twice.^[4][5][6][7]

Practical next steps

• Review open tickets for the same asset identifier.
• Compare billed dates to off-rent and pickup records.
• Check whether your contract allows a transfer, swap, or same-day changeover.
• Escalate unresolved overlaps to the supplier before payment.

Sources: ^{[1][2][3][4][6]}

If you want this control to run every cycle, standardize one asset key, one date-range rule, and one review path for exceptions. That keeps the same-asset overlap problem from slipping through when the invoice itself looks normal.^[3][4][6]

← All resources