Set AP Rental Review Rules Before You Pay

By RentalSpend · October 5, 2026

Set AP to hold every equipment-rental invoice until it matches the agreement, the receipt or delivery proof, and the off-rent or return record. Then route any rate, date, quantity, surcharge, or damage variance to exception review before payment.

Set AP to treat every equipment-rental invoice as a match-controlled payment, not a straight-through invoice. Before payment, require the rental agreement or PO, proof of delivery or receipt, and the off-rent, pickup, or return confirmation that stops billing under the governing terms; then send any rate, date, quantity, surcharge, or damage variance to exception review.^{[1][2][3][4][5][6]}

1. Define the minimum document set AP must have before an invoice can be approved.
2. Make the rental agreement and rate sheet the billing source of truth for that transaction.
3. Hold any invoice that does not match the billed period, rate, quantity, or extra charges.
4. Route each exception to the person who can verify the facts or approve the change.
5. Release payment only after the variance is resolved or approved under your company’s authority.

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

1. Set the documents AP must require

Start by defining the minimum file AP needs before an invoice can be approved for payment. For rental spend, that file should normally include the rental agreement or PO, proof the equipment was received or delivered, and proof the rental stopped when it should have stopped. The Government Accountability Office says key records should be matched before an invoice is approved for payment, and Oracle’s AP guidance describes match controls as requiring the relevant records to agree within tolerance before payment.^[1][2]

• Rental agreement or PO: the commercial basis for the bill.
• Delivery, receipt, or service proof: evidence the equipment or service was actually provided.
• Off-rent, pickup, or return confirmation: evidence the billing period ended.
• Invoice: the supplier’s billed quantities, dates, and charges.
• Any approved change order or written authorization for extra days, extra equipment, or added services.

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

Keep the rule simple: if one of those core records is missing, AP should not pay the invoice automatically. Instead, place it on hold and send it to the person who can confirm the facts on site or in the contract.^[1][2][3][4]

2. Make the contract and rate sheet the source of truth

For rental bills, the agreement matters as much as the invoice. Sunbelt says a fully executed, active agreement intended to govern conflicting terms takes precedence over web terms. United Rentals’ credit application also says the customer agrees to the rental agreement terms in effect at the time and place of the transaction. That means AP should compare each invoice to the specific agreement, rate sheet, and any incorporated rental terms for that transaction, not to a generic vendor profile.^[4][6][7]

• Use the exact agreement tied to the rental transaction.
• Check whether the agreement allows separate charges such as delivery, cleaning, fuel, damage, or surcharges.
• Verify whether the agreement changes billing start and stop timing, or requires a particular off-rent notice process.
• Confirm whether the invoice is governed by a newer signed agreement, not an older one in the file.
• Escalate any conflict between documents instead of letting AP choose a version by habit.

Sources: ^{[3][4][5][6][7]}

3. Build the prepayment checks around the billable period

The most important rental check is whether billing stopped when it should have stopped. United Rentals says rental charges start when equipment leaves the store location and end when it is returned or picked up after the customer notifies the company the equipment is off rent and obtains an off-rent confirmation number. That makes the stop-billing record critical for AP: if the invoice shows days after the documented off-rent date, the extra days should be held for review before payment.^[3]

Use the same logic for other timing-related items. Compare the invoice dates to the delivery date, the off-rent date, and any pickup or return record. If the bill covers a longer period than the approved rental window, require someone with operational knowledge to confirm whether the extra time was authorized, caused by site conditions, or simply billed in error.^[1][2][3][4]

• If the invoice starts before delivery, hold it for review.
• If the invoice continues after off-rent or pickup, hold the extra days.
• If the rental period is correct but the equipment ID is wrong, confirm the unit on site.
• If the bill includes time not supported by a ticket, log, or return record, do not pay that portion until it is explained.

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

4. Review rate, quantity, and line-item variances separately

AP should not treat every variance the same. A wrong daily or weekly rate is a contract problem. A wrong quantity is usually a receipt or usage problem. A surprise fee is often a billing-detail problem that still needs review before payment. Herc says surcharges and other fees, including government-mandated surcharges and pass-through fees, may appear as separate line items on the rental agreement and/or invoice, so AP should check each added charge against the agreement and the approval trail.^[5]

• Rate variance: compare the billed rate to the agreed rate for that equipment and date range.
• Quantity variance: compare billed units, days, weeks, months, or attachments to what was actually received and used.
• Line-item variance: review separate cleaning, fuel, damage, surcharge, pass-through, or similar charges against the contract.
• Tax or fee variance: confirm whether the invoice fee is allowed under the agreement and the jurisdictional setup on the account.
• Damage or cleanup variance: send to operations review before payment if the site condition or return condition is disputed.

Sources: ^[4][5][6][7]

Do not build broad tolerances unless your contract and approval authority allow them. A small rate or date tolerance may be useful for low-risk transactions, but the right threshold depends on the agreement and your internal policy, not on a one-size-fits-all rule.^{[1][2][4][6][7]}

5. Put a written dispute rule into the workflow

Build a dispute deadline into the AP process so invoices do not age past the supplier’s required notice period. Sunbelt says customers must notify it in writing of disputed amounts, including credit card charges, within 15 days after receipt of the invoice or contract or the right to dispute may be deemed waived. That is a supplier-specific rule, but it shows why AP needs a documented process that sends exceptions out quickly and records the dispute date.^[4]

• Assign an owner for each exception type before the invoice reaches AP.
• Set a short internal review deadline so disputes are raised before any contractual notice window closes.
• Require the reviewer to state the exact discrepancy: rate, date, quantity, equipment ID, or added charge.
• Keep evidence of the dispute, including the invoice, the agreement, the matching records, and the supplier response.
• Release payment only for the undisputed portion if your policy and the contract allow partial payment.

Sources: ^[2][4][5]

6. Decide who handles which problem

A clear routing rule reduces back-and-forth. AP should handle document mismatches and coding errors. Project or equipment managers should handle whether the equipment was on site, returned, or used longer than expected. Procurement should handle pricing disputes tied to the agreement. Legal or contract administration should handle conflicts between documents or disputes over which terms govern.^{[1][2][3][4][6][7]}

• AP: missing PO, missing receipt, duplicate invoice, wrong coding, or obvious billing mismatch.
• Project or equipment management: wrong off-rent date, missing pickup record, or uncertain equipment identity.
• Procurement: rate conflicts, unauthorized charges, or change orders that were not approved.
• Legal or contract administration: conflicting terms, disputed notice language, or unclear governing agreement.
• Accounts payable manager: final hold, partial payment approval, or escalation to leadership.

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

7. Document the approval rule in plain language

Your AP policy should say, in plain terms, what must match, who can approve a variance, and what happens when the invoice fails the check. Use the same language in your ERP workflow so approvers see the same rule every time. The goal is not to make AP do contract management; it is to keep payment from going out before the company has the records needed to support the charge.^{[1][2][4][6][7]}

A practical rule set looks like this: if the invoice matches the agreement, the receipt, and the off-rent or return record, AP can route it to normal approval. If any of those items do not line up, AP holds the bill, records the reason, and sends it to the correct owner before payment.^{[1][2][3][4][5]}

What to do when something does not match

• Stop straight-through payment as soon as the mismatch is detected.
• Identify whether the problem is rate, date, quantity, extra charge, or contract language.
• Gather the agreement, invoice, delivery proof, and off-rent or return confirmation.
• Send the issue to the person who can verify the rental period or approve the change.
• Record the supplier dispute date and the internal owner of the exception.

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

If the invoice is correct but your records are incomplete, fix the process gap as well as the bill. Missing off-rent confirmations, late return tickets, and incomplete receiving records are control problems, not just invoice problems. The cleanest AP rule is the one that forces the missing record to be created before payment next time.^[2][3][4]

Practical next step: define your required rental match set, assign an owner for each exception type, and put the hold-and-escalate rule into AP workflow before the next invoice batch is paid.^{[1][2][4][5][6][7]}

← All resources