How to route rental invoices when job code, PO, and contract conflict

By RentalSpend · October 9, 2026

When the job code, PO, and contract do not match, route the invoice by the document that controls the charge first, then send the mismatch to the owner of the wrong field for correction. Do not auto-approve until the rental period, rate, and support documents reconcile.

When the job code, PO, and contract do not all match, route the invoice by the document that actually controls the charge for that line item, not by whichever field is easiest to code. In most rental situations, the signed rental terms or contract control the billing rules, while the PO and job code are internal routing fields; if there is a conflict, send the invoice to the owner of the controlling document, keep the mismatch visible, and do not approve payment until the rental period, rate, and support records reconcile.^{[1][2][3][4][5]}

Symptom: the contract and PO point to different jobs

If the rental agreement is tied to one job but the PO carries a different job code, treat that as a routing exception, not an automatic approval. The contract owner or procurement should review the charge first, because some supplier terms say inconsistent PO language does not become part of the rental contract unless the lessor agrees in writing. Your AP team can hold the invoice in exception and route the mismatch to the buyer or contract owner for correction of the PO or for written confirmation that the billing belongs on the contract job.^[2][3][4][6]

• Check the signed rental agreement and any incorporated terms for the job name, PO reference, and precedence language.
• Check whether the invoice line item follows the contract rate, rental start date, and off-rent date.
• Send the mismatch to the buyer, procurement lead, or contract owner if the PO is wrong.
• If the contract is right and the PO is wrong, do not rewrite the contract-side billing terms to match the PO without written agreement from the supplier.
• If your system allows it, keep the invoice on hold while the PO is corrected or an approved coding override is documented.

Sources: ^[2][3][4][6]

What to do if the job code is the only field that is wrong: route the invoice to the project, job, or cost-center owner for recoding, but leave the contract rate review with procurement or the contract owner if the billing terms are still in dispute. Job codes are internal controls, so they help with allocation, but they do not usually change what the supplier is allowed to bill under the rental terms.^[3][6][7]

Symptom: the invoice matches the PO but the rental dates do not match the field record

This usually means the invoice may be right on paper but wrong in timing, or the field team did not send off-rent confirmation in time. For rental equipment, the billing end point often depends on the equipment being returned, picked up, or marked off rent through the process required by the supplier, so AP should compare the invoice dates with the off-rent notice, pickup record, or equivalent stop-use evidence before approving.^[1]

• Compare the invoice start and end dates with the rental agreement and any off-rent confirmation number or pickup record.
• Ask whether the equipment was still onsite, still in use, or already available for pickup when billing continued.
• Route the line to the project manager or equipment manager if the field record says the machine was off rent earlier than the invoice shows.
• Route the line to procurement or the contract owner if the supplier is billing days beyond the agreed rental end point and the issue appears contractual.
• If the timing dispute is unresolved, hold payment until the supplier issues a corrected invoice or written explanation.

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

A practical rule is to treat the invoice date range as a claim that must be backed by a stop-use record. United Rentals’ terms, for example, say rental charges end when the equipment is returned or picked up after the customer notifies the supplier it is off rent and obtains an off-rent confirmation number, so the approval path should reflect that control point when your own agreement uses similar language. Terms vary by supplier, so check your contract and current rental terms.^[1]

Symptom: the invoice matches the contract rate but has extra charges

Extra items such as delivery, cleaning, damage, fuel, weekend use, or transportation charges often need a separate review route because they may not follow the base rental approval path. Some rental terms allow additional cleaning, repair, restoration, or transportation-related costs, so the question is not only whether the amount is large; it is whether the charge is supported by the agreement, the condition of the equipment, and any documented event that triggered the fee.^[1]

• Separate base rental charges from add-on charges on the invoice.
• Check whether the agreement or rate sheet authorizes the fee category.
• Route base rental to the job or project owner, but route disputed extras to procurement or the contract owner.
• If a damage or cleaning charge is involved, ask for photos, inspection notes, return condition records, or repair detail.
• If the supplier billed a fee the contract does not clearly support, dispute that line before approving the undisputed portion.

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

If your approval workflow supports line-level matching, use it. Many AP systems can combine matching rules and exception handling so a clean base rental can move forward while the disputed add-on stays blocked. That is usually better than forcing one approver to absorb the whole invoice when only one line is in question.^[3][4][5][7]

Symptom: the invoice is blocked because AP cannot decide who owns the exception

When no single field obviously controls the invoice, route by exception type. Contract mismatch goes to procurement or the contract owner. PO mismatch goes to the buyer or PO owner. Job code or cost-center mismatch goes to the project, job, or cost-center owner. Quantity, rate, or receipt mismatch goes to AP with the field owner or supplier added to the loop. This keeps the exception visible and prevents AP from becoming the default owner of business decisions.^[3][4][6][7]

If your company has a formal approval matrix, follow it. Many organizations route invoices by amount, cost center, project, or match exception, and some systems allow approval even with exceptions while others block submission or approval until the issue is resolved. The right setting depends on how much risk your company is willing to accept for that invoice type.^[3][4][7]

What to do when the mismatch is caused by a company policy gap

Sometimes the problem is not the supplier invoice; it is that the company never defined who owns rental billing exceptions. In that case, create a simple routing rule set that names the first reviewer for each mismatch, the evidence needed to clear it, and the fallback if the first reviewer cannot resolve it. For public-sector or federal-style work, also check whether prompt-payment or receipt-date rules apply when there is a billing disagreement, because payment timing can be affected when the invoice is not fully accepted.^[8]

• Define who owns contract disputes, PO corrections, and job-code changes.
• Define what counts as valid off-rent evidence for your company.
• Decide whether rental add-ons follow the same approval path as the base rental or a separate exception path.
• Set a hold code or workflow status for disputed rental lines so AP can see why payment is delayed.
• Make sure the designated billing office records receipt dates if your public or government contract requires it.

Sources: ^[3][4][8]

If the invoice spans multiple jobs or phases, split the route by line or by coding segment instead of forcing one approver to sign for all of it. That is often the cleanest way to preserve accountability when one rental ticket covers more than one cost object.^[3][6][7]

Practical next steps: review one recent disputed rental invoice and map each mismatch to a reviewer, using contract owner for billing terms, buyer for PO errors, and project or equipment management for job and off-rent questions. Then update your workflow so the same exception is routed the same way every time, with the support packet attached before approval.^[3][4][6][7]

← All resources