AP rental invoice coding checklist before payment

By RentalSpend · October 10, 2026

Use a prepayment checklist that ties each rental invoice to the agreement, the off-rent record, and the right cost object. That keeps AP from coding charges that do not belong on the job.

Build the AP checklist around one rule: do not code or release a rental invoice until the invoice ties back to the rental agreement, the off-rent or return record, and the correct cost object. Then verify the rental period, equipment identity, rate basis, and every billed add-on against your own contract and rate sheet before the invoice is approved for payment. Because supplier terms vary, any mismatch in dates, quantities, surcharges, fuel, taxes, delivery or pickup, damage, or repair charges should go to exception review first.^{[1][2][3][4][5][6]}

• Confirm the supplier name, agreement number, and equipment description match the rental authority or approved quote.
• Check the invoice dates against the off-rent notice, return ticket, pickup record, or confirmation number before coding any rental charge.
• Verify the billing basis in your agreement: daily, weekly, monthly, 24-hour, minimum-day, weekend, or continuation billing.
• Review every add-on line separately for delivery, pickup, transportation, fuel, refueling, environmental fees, surcharges, taxes, cleaning, damage, and repair charges.
• Assign the invoice to the correct job, project, WBS, cost center, or internal order before payment, and split the charge if the equipment served more than one cost object.
• Hold any invoice without a matching reference object, missing off-rent proof, or unexplained variance for manual review instead of auto-approving it.

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

What the checklist should verify first

The first control is document identity. AP should confirm that the invoice belongs to the same supplier agreement, quote, or rental ticket that authorized the equipment. Check the supplier name, agreement number, equipment description, and unit or asset ID on every supporting document. If the invoice cannot be matched to a rental authority, it should not be coded as a routine payable.^[1][5][6]

Check the rental period before you code the charge

The billing dates matter as much as the rate. United Rentals says rental charges start when equipment leaves the store and end when it is returned or picked up after an off-rent notice and confirmation number. That means AP should compare the invoice start and end dates to the off-rent record, return ticket, pickup record, or confirmation. If the invoice continues past the off-rent date, or starts before delivery, the invoice should be held for review until the dates are reconciled.^[1][7]

Build separate checks for rate, extras, and coding

A good checklist does not treat every rental invoice the same way. It should force the reviewer to confirm the rate basis and the add-on charges separately, then send each item to the right account. That keeps a base rental from being mixed with delivery, fuel, tax, or damage costs that may belong in different buckets or require different approval paths.^{[1][2][3][4][5][6]}

Use the checklist to separate ordinary rent from special charges

Damage and repair items need special handling because they often do not belong with routine rental coding. Herc and United both note that cleaning, restoration, repair, or other recovery costs may be billed in addition to base rent. AP should not assume those items are automatic. The checklist should require an attachment showing the incident, inspection, or return condition, plus the internal approval path for any charge that looks like damage rather than normal rental use.^[1][2]

Match the invoice to the ERP coding field before posting

Before payment, the invoice must land in the correct accounting bucket. SAP guidance shows invoices without a reference object can be assigned a G/L account, cost center, and WBS element, and one line can be split across multiple accounts. Oracle also notes that invoice distributions can include account code combinations and cost center overrides. Your checklist should require the reviewer to choose the correct job, project, cost center, or other field your ERP uses, and to split the line if the equipment served more than one project.^[5][6]

What to do when something does not match

If any check fails, the checklist should tell AP exactly where to stop. Common hold reasons include no matching rental agreement, missing off-rent confirmation, billed days beyond the return date, an unsupported surcharge, a damage charge without backup, or a cost object that does not belong to the job. In those cases, AP should route the invoice to the responsible buyer, project manager, equipment manager, or supplier contact for correction before payment. If your company allows partial payment, post only the undisputed portion and track the remainder as an open exception under your normal process.^{[1][2][3][4][5][8]}

Illustrative example: a backhoe invoice with separate extra charges

Practical next steps

• Build the checklist into your AP workflow as a required pre-payment review, not an optional note.
• Use the same fields every time: agreement, dates, rate basis, add-ons, and cost object.
• Set a clear exception route for unmatched invoices, unsupported charges, and damage or repair items.
• Align the checklist with your ERP coding fields so reviewers know exactly where each rental charge should post.
• Review the checklist periodically against your own contracts and supplier rate sheets, since rental terms vary by agreement.

Sources: ^[1][2][5][6]

← All resources