Require rental receipts and delivery tickets before approval

By RentalSpend · October 5, 2026

Put a hard stop in AP: no equipment-rental invoice gets approved until the contract, delivery proof, and return or off-rent record are attached and matched to the bill.

The cleanest way to require rental receipts and delivery tickets before approving an equipment-rental invoice is to make them part of the approval gate: AP should not release payment until it has the rental agreement or PO, the delivery or receiving record, and the final pickup or off-rent record tied to the same equipment and site. That follows GAO’s payment-control sequence of authorization, evidence of delivery and acceptance, and then the invoice, and it fits supplier terms that treat delivery and receipt documents as part of the rental transaction.^{[1][2][3][4][5][6]}

Set the approval rule in the right order

1. Start with authorization: require the signed rental agreement, purchase order, or other approved rental authorization before the invoice can enter approval.
2. Require proof of delivery or receipt: attach the delivery ticket, receiving report, or other record that shows the equipment arrived at the site and was accepted.
3. Require proof of return or off-rent for the final bill: hold the invoice until the pickup record, off-rent confirmation, or return receipt supports the billed stop date.
4. Match the invoice to the supporting records before approval: confirm the equipment identity, site, rental dates, and any extra charges against the contract and the delivery or return records.
5. If a mismatch exists, park the invoice in exception status until the requester and supplier resolve it and close the issue.

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

What the approver should verify on every invoice

The approver should check whether the invoice lines up with the documents that prove the rental actually happened. At a minimum, that means the equipment description matches the contract, the billed dates match the delivery and return or off-rent records, and any added charges are allowed by the agreement or rate sheet. If your billing packet also includes serial numbers, unit numbers, or location details, use those to make the match tighter and reduce disputes.^[6][7][8]

• Equipment identity: unit type, asset number, serial number, or other identifier that links the bill to the rented item.
• Dates: delivery date, start date, pickup date, off-rent date, and the billing period.
• Location: site or project where the equipment was delivered and used, if your records include it.
• Charges: base rent plus any additional charges your agreement lists, such as delivery-related or other add-on items.
• Acceptance evidence: a signature, electronic acknowledgment, or receiving record if your contract requires it or your process uses it.

Sources: ^{[4][5][6][7][8][9]}

How to build the workflow in AP and operations

Make receipt and return proof a prepayment requirement, not a post-payment cleanup task. The workflow should force AP to collect the contract, delivery or receiving record, and off-rent support before the invoice can move to approval. That way, the approver is checking whether the bill matches the rental event, not trying to reconstruct the event after money has already gone out.^{[1][2][3][6][7]}

• Create a required-document checklist in the invoice workflow so AP cannot mark a rental invoice ready for approval unless the contract and delivery or receiving record are attached.
• Assign one owner for each exception: AP for document completeness, the project or equipment owner for date and usage confirmation, and procurement or contract management for supplier disputes.
• Set a standard rule for off-rent support on final invoices so the bill stays on hold until the pickup or return record confirms the end date.
• Use the same file name or reference number across the contract, delivery ticket, and invoice so the records can be matched quickly.
• Keep the hold until the vendor resolves the mismatch and the internal requester closes the exception.

Sources: ^{[1][2][3][6][7][10]}

If the delivery ticket is missing

If the delivery ticket is missing, do not approve the invoice just because the equipment was expected on site. Ask the requester or site contact for the receiving record, driver copy, or signed acknowledgment your contract calls for, and compare it to the rental agreement before moving the bill forward. If your supplier’s terms allow delivery without a written receipt, that is a contract question to confirm rather than a reason to skip control.^[4][5][9]

If no receipt can be produced, treat the invoice as an exception and hold payment until the organization can establish that the equipment was actually delivered and accepted. GAO’s control logic supports verifying receipt and acceptance before payment, not after it.^[1][2][3]

If the invoice does not match the dates or equipment

When the invoice dates do not match the delivery or return record, or the equipment description does not match the contract, stop approval and send the packet back for correction. A final invoice should not move forward until the billed period matches the actual rental period and the equipment identity lines up with the supporting record set.^{[6][7][8][10]}

This is especially important on open-ended rentals, monthly bills, and jobs with equipment swaps. In those cases, the approval rule should force the approver to verify the billed start and stop dates against the delivery and off-rent records before payment.^[6][7]

If extra charges are on the bill

If the invoice includes fuel, delivery, cleaning, damage, or other extra charges, require the approver to check whether the contract or rate sheet allows them and whether the supporting documents explain the charge. Do not assume every add-on belongs on the invoice just because the equipment was on site.^[6][7]

When the charge is allowed, the support should show what triggered it and when. When it is not allowed or cannot be explained, hold it for correction or dispute resolution before the invoice is approved.^[1][2][10]

A simple control standard that reduces rework

• Make receipt and return proof a prepayment requirement.
• Use one invoice packet per rental event so AP does not have to chase separate documents across systems.
• Require the approver to sign off on the document match, not just the dollar amount.
• Route mismatches to one exception queue instead of letting different departments handle them separately.
• Keep the control tied to your own contract and rate sheet, because rental terms vary by supplier, site, and product line.

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

In this example, the arithmetic is complete, but the approval is not. The invoice packet still lacks the record that proves the equipment came off rent, and the extra charge needs a document or agreement clause that explains why it belongs. The practical check is not whether the total adds up; it is whether every billed item is supported by the contract and the rental event records.^{[1][2][6][7][10]}

Practical next steps

Start by updating your invoice-approval rule so every equipment-rental invoice needs three things: authorization, delivery or receipt evidence, and return or off-rent support for the final bill. Then train AP and project owners on the specific documents your suppliers use, map the exception path for missing tickets or mismatched dates, and make the hold release depend on documented resolution rather than verbal confirmation. Finally, compare the rule against your own contracts so the workflow follows the terms you actually agreed to.^{[1][2][3][4][5][6]}

If you want the control to stick, keep the rule simple: no contract, no delivery proof, no approval; no off-rent record on the final bill, no payment. That gives AP a clear gate, gives operations a clear responsibility, and gives the company a cleaner record when rental spend is reviewed later.^{[1][2][3][6][7]}

← All resources