Check whether a rental charge landed on the wrong job code

By RentalSpend · October 8, 2026

Use the rental contract, invoice, and AP coding fields to confirm whether the charge belongs to the intended job or project. Then trace any mismatch to the supplier record, your coding setup, or a split between jobs.

To check whether a rental charge was billed to the wrong job or project code, start with the rental contract, the invoice, and your AP coding record, then compare the job or project shown on each one with the dates and equipment actually on rent. If the job code is wrong, the issue usually comes from one of three places: the original rental record, your internal coding or mapping in AP or project accounting, or a supplier-side billing setup that carried the wrong job or project reference forward. Your contract, rate sheet, PO instructions, and coding rules still control the correct answer for your case, so use those documents first and treat supplier portal fields as supporting evidence rather than the final authority.^{[1][2][3][4][5][6]}

Checklist: what to verify on every suspicious rental charge

• Check the invoice line against the rental contract number, purchase order, and any jobsite or project identifier tied to the rental record. In many internal-control processes, the basic check is whether the invoice matches the authorized contract or PO and the supporting receipt or acceptance record.
• Check whether the equipment was actually on the job or project for the full billed period. If the unit moved, was transferred, or sat on a shared yard or standby location, make sure the billed dates still match the project that should bear the cost.
• Check the supplier portal or billing portal for the jobsite, asset ID, contract number, and invoice view. Some supplier systems show the jobsite the equipment is on, the contract number, and invoice or PO-related details together, which helps you see whether the charge was attached to the wrong project context.
• Check the AP distribution or account coding fields in your ERP or invoice workflow. If the invoice imported under the right supplier and contract but the wrong project number, the issue may be in your coding default, approval route, or project mapping. ERP account-coding workflows commonly route invoices for distribution entry, and project number can be one of the fields used in coding.
• Check for extensions, redeployments, or reopenings of the rental that changed the billed period without updating the project reference. A charge can be tied to the right contract but still land on the wrong job if the rental was extended after the original start or if the equipment was reassigned mid-rental.
• Check for duplicate or split coding across more than one job. If one invoice line was split in AP, confirm that the split follows the actual use of the equipment and not just a default allocation.
• Check for missing acceptance or off-rent confirmation. If your process depends on delivery, off-rent, or pickup records, compare those dates to the billed dates and the project code assigned in AP. The correct supporting record depends on your own contract and workflow, but the invoice should still tie back to a recognizable operational event.

Sources: ^{[1][2][3][4][7][8]}

Check the source documents in order

Start with the rental contract because it usually establishes what was ordered, under what number, and under which job or project context the rental should be billed. Sunbelt Rentals notes that the rental contract is the document that sets the specific equipment, terms, and price, while reservation and contract numbers are distinct but linked in the system. That means the contract number alone is not enough; you need to confirm the full job or project reference tied to the rental.^[4]

Next, compare the invoice line to your PO or authorization record. GAO internal-control guidance emphasizes matching the purchase order or contract with the invoice and the receiving or acceptance record before payment. For rental spend, that means the billed job or project code should align with the document that authorized the rental, not just with the supplier name or equipment description.^[1][2][3]

Then check your AP or project accounting coding screen. Oracle’s invoice routing and account-coding documentation shows that invoices can be routed for distribution entry and that project number can be a supported coding field. In practical terms, that means a charge can be correct at the supplier level but still land in the wrong internal project if the coding default, manual entry, or approval workflow is wrong.^{[5][6][9][10]}

Use the jobsite and equipment record as the reality check

After the paperwork check, use the operational record to see where the equipment actually belonged. Supplier portal pages may show the jobsite, asset ID, contract number, invoice details, or PO tracking in one place. That is useful because it lets you compare the billed project against the actual jobsite assignment and see whether the rental was moved, extended, or consolidated under a different job reference.^{[7][8][9][5][6]}

If the equipment served more than one project, do not assume the first job code is automatically right. Split billing, partial periods, and shared equipment arrangements often depend on your own internal rules and the supplier’s billing process. In those cases, the key question is not only whether the charge was billed, but whether it was billed to the correct job for the dates in question.^{[9][10][7][8]}

What usually causes the wrong job code

• The job code was entered incorrectly when the rental was created or changed.
• The supplier carried forward an old project or jobsite reference after the equipment was moved.
• AP default coding mapped the invoice to the wrong project or work order.
• The invoice was correct at the supplier level, but your internal distribution split or cost-center mapping was wrong.
• The rental was extended or reopened, and the later billing cycle did not inherit the updated project reference.
• The contract allows a project change only through a specific process, and that process was not followed. Terms vary by supplier and by agreement, so check your own contract and rate sheet first.

Sources: ^{[4][9][10][5][6]}

What to do when the codes do not match

When the job or project code on the invoice does not match the code on the contract, PO, or operational record, isolate which document is wrong before you ask for a correction. If the contract and jobsite record agree but AP does not, fix the coding in your ERP and review whether the error affected only this invoice or a whole batch of rentals. If the invoice and AP agree but the contract does not, the problem may have started at the branch, in the supplier portal, or in how the rental was set up originally.^{[4][8][9][5][6][7]}

If the supplier record appears wrong, gather the exact invoice line, rental contract number, PO number, jobsite or project name, rental start and off-rent dates, and any delivery or pickup confirmation you use internally. Ask for the billing record to be reviewed against the contract terms and the project reference on file. Keep the request focused on the mismatch and the supporting documents rather than on the reason you think it happened. That approach is usually faster and easier to resolve in AP or supplier billing workflows. Terms and correction methods vary by supplier, so follow the process allowed by your agreement.^{[1][2][3][4][8][9]}

If the problem is in your own coding or cost allocation, correct the project field, reclassify the charge if your policy allows it, and update any recurring mapping so the same invoice or rental type does not keep landing in the wrong job. If the charge should be split across projects, document the split logic clearly so the next invoice follows the same rule. Where your system supports invoice routing or account coding, make sure the project field, worklist assignment, and approval path are set up to catch the same error next time.^{[5][6][9][10]}

Practical next steps

• Pick one questionable rental line and trace it from invoice to contract to PO to project coding.
• Compare the billed job or project against the jobsite and dates on the rental record.
• Decide whether the error is supplier-side, AP-side, or a split-allocation issue.
• Correct the coding or request a supplier review using the documents that show the mismatch.
• Review whether the same error appears on other invoices from the same branch, contract, or project setup.

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

If you want this check to be faster across many invoices, standardize the fields you store for each rental: contract number, PO, project code, jobsite, rental start, off-rent date, and approval owner. RentalSpend can help compare those fields against invoice lines so the mismatches are easier to spot, but the underlying answer still comes from your own contract and coding rules.

How do I tell whether the error came from the supplier or from AP? Compare the invoice line, the contract or PO, and the AP distribution. If the supplier and contract agree but AP does not, the issue is likely internal. If AP matches the invoice but the contract or jobsite record does not, the setup or billing record likely needs review.^{[1][2][3][5][6]}

What records matter most for a job-code review? The contract, PO or authorization, invoice, jobsite or project reference, and any delivery, pickup, or off-rent confirmation you use in your process. Those records create the trail you need to confirm where the charge belongs.^{[1][2][3][4][7][8]}

What if one rental was used on more than one project? Check your contract and internal allocation rules, then split the billed time or cost only if your process supports that split and the dates can be backed up by jobsite records.^{[9][10][5][6]}

Can a portal jobsite label be treated as final proof? Not by itself. Portal fields are useful evidence, but your own contract, PO, and AP coding rules determine how the charge should be booked.^[4][7][8][9]

← All resources