Allocating equipment-rental charges to the right job code

By RentalSpend · October 4, 2026

The safest way to code rental charges is to carry the job or project number from the rental documents into the invoice line or project distribution before posting. That keeps job costs aligned with the agreement and makes later review much easier.

Allocate equipment-rental charges to the correct job code or project number by matching each invoice line to the project identifier on the rental documents, then entering that same identifier in your AP or project system before the charge is posted. In practice, the cleanest approach is to tie the invoice line to the signed rental agreement and the jobsite details, then code it as a project-related line or distribution rather than as a generic AP invoice. If your ERP supports project accounting, put the project number on the invoice line or distribution so the cost rolls into the right project record and can be transferred into project costing for review.^[1][2][3][4]

What has to match before you code the charge

Start with the documents that control the rental: the agreement, reservation or order details, delivery or pickup information, and the supplier invoice. United Rentals’ materials say the agreement defines the site as the customer’s job site, worksite, or project location, and their credit application points back to the rental agreement in force for the transaction. That is a reminder that the coding should follow the documents tied to the specific rental, not a generic company default.^[3][4]

• The job or project number on the rental order, reservation, or invoice line.
• The site or project location shown on the agreement or delivery record.
• Any separate line items that may need different treatment under your contract, such as add-ons or other contract-defined charges.
• The PO, cost code, or project dimension your internal system requires for posting.

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

If those items do not line up, pause before posting and resolve the mismatch with your project team or supplier contact. That is usually faster than reversing a posted charge later, especially when a statement includes multiple sites or mixed charges.^[1][2]

A practical coding workflow

That sequence matters because project systems often create a project actual or project cost transaction when the invoice is posted. Oracle documents that project-related invoice distributions transfer into Project Costing, and Microsoft documents that a pending vendor invoice can be attributed directly against a project and then posted as a project actual cost transaction. If your team skips the project field until after posting, the invoice may land in the wrong place and require cleanup.^[1][2]

Where to put the project number in the system

Put the project number in the place your system uses for cost allocation. In Oracle, project information can be entered on the invoice line, on a distribution set with project information, or on the invoice distribution. Microsoft also allows the AP clerk to select the project ID in line details when recording a vendor invoice. Sage notes that invoices in Accounts Payable can update jobs managed using Project and Job Costing, and it distinguishes between job-related and non-job-related invoices.^[6][1][2]

• Use the invoice line when your system supports line-level project coding.
• Use the distribution or accounting split when one invoice line needs to be allocated across more than one project.
• Use the project or job field your ERP treats as the posting field, not just an internal note.
• Do not rely only on free-text comments if the posting rules require a coded project field.

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

If your AP process separates job-related and non-job-related invoices, keep them separate before posting. Sage says an invoice in Accounts Payable can be either job-related or not job-related, and you cannot enter a mixed invoice. That means a rental invoice with both project work and non-project charges may need to be split or reviewed before it is entered, depending on how your system is configured.^[6]

How to handle invoices with more than one project

A common issue is a statement or monthly invoice that covers more than one site or project. The right response is to split the charge into the correct project distributions before posting, using the invoice line, distribution, or AP split tool your system provides. If one invoice covers two jobs, allocate each line to the project that actually used the equipment, and keep the source documents that support the split.^[1][2][7]

That review should also catch charges that may not belong on the same project as the base rental. Your agreement or reservation details may define special items differently, so compare each line against the contract and supporting ticket before assigning the project number. United Rentals’ terms, for example, say the reservation details set a replacement fee for mats not returned or returned damaged, which shows why contract-defined items deserve separate review rather than automatic coding.^[3]

What to review before posting

• Does the rental agreement or reservation show the same job number your project team expects?
• Does the invoice line description match the equipment, date range, and site used on the job?
• Are delivery, pickup, or off-rent records consistent with the project dates?
• Do any extra charges need separate approval, separate cost codes, or a different project?
• Does the posted invoice create the correct project actual cost or project transaction in your ERP?

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

Project managers and project accountants can help here. Microsoft’s project invoicing overview notes that the project manager manages the billing backlog and the project accountant creates the invoice document, while the project contract line defines the billing method for the associated project transactions. In practical terms, that means AP should not guess at coding when the project team already controls the billing structure.^[5]

Using supplier tools when they are available

If your supplier offers invoice viewing, consolidated billing, PO tracking, or jobsite allocation tools, use them to reduce manual coding work. United Rentals describes tools that provide invoice viewing and payment, lien release management, purchase order tracking, consolidated billing, and jobsite allocation visibility. Those tools can help your team confirm which project a rental belongs to before the invoice reaches AP.^[7]

Even then, treat the tool output as support, not a substitute for your own controls. The project number still needs to match your internal coding rules, and your own contract, PO, and approval workflow should remain the source of truth for posting.^{[1][2][3][4][7]}

Controls that reduce miscoding later

• Require the project number on the rental order or reservation before the job starts, when your process allows it.
• Make the project field mandatory in AP for rental vendors.
• Keep job-related and non-job-related charges separate in the invoice workflow.
• Attach the rental agreement and source ticket to the invoice record.
• Reconcile posted project costs back to the rental invoice during month-end review.

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

Those controls matter because once the charge is posted, the cleanup work shifts from simple coding to reclassification. It is usually easier to prevent a miscoded rental than to move it after project reporting has closed.^[1][2][5]

Practical next steps

Before the next rental invoice is approved, confirm which field in your AP or ERP system actually drives project posting, then require that field on every rental line. Align that field with the job number on the rental agreement, reservation, and support tickets, and split any mixed or multi-project statement before posting. If your team is unsure whether a charge belongs to the job, hold it for review against the contract and supporting documents rather than coding it to a default account.^{[6][1][2][3][4]}

If you want a faster internal workflow, map your invoice review steps to the documents your team already keeps: rental agreement, invoice, delivery or pickup record, off-rent confirmation if you use it, and project accounting entry. That gives AP, project accounting, and equipment management the same reference point when a charge needs to be allocated or questioned.^{[1][2][5][3][4]}

From there, the basic rule is simple: if the rental belongs to the job, the project number should travel with the charge from source document to posting record; if it does not, it should not be forced onto the job. Use your own agreement, PO, and project coding rules to decide the final treatment.^{[6][1][2][3][4]}

← All resources