How to Set Approval Rules for Split-Billed Rental Invoices

By RentalSpend · October 13, 2026

Route split-billed rental invoices by the accounting distribution, not just the invoice total. Use ownership, match, and threshold checks so the right job or cost code approves its share.

Set approval rules around the accounting split on the invoice line, not just the invoice header total. For rental invoices that charge multiple jobs or cost codes, the safest setup is to require routing for every affected account, send each share to the right owner, and add amount-based escalation when any one share or the full invoice exceeds your approval limit. In practice, that means the split must match your rental agreement, PO, or coding instructions, every charged job or cost center needs an approver, and any exception should stop auto-approval until AP or the business owner reviews it.^{[1][2][3][4][5]}

1. Start with the invoice distribution fields, not the header total. Identify every job, cost code, cost center, or project on the rental invoice and use those fields to drive approval routing.
2. Require an owner for each affected charge. If an invoice splits across multiple jobs or cost objects, route each share to the manager or approver who owns that budget.
3. Set a threshold rule for the split and for the full invoice. Escalate if any single share is above the approver’s limit or if the total invoice exceeds the limit.
4. Auto-approve only when the split matches your approved coding pattern and the invoice is otherwise matched to the rental agreement, PO, or rate sheet.
5. Define an exception path for closed projects, missing approvers, coding changes, and disputed charges so AP does not have to guess what to do next.

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

1. Build the rule around the accounting split

The most useful approval rule is one that looks at the invoice distribution line by line. Oracle’s AP approval rules can use invoice header, invoice line, and invoice distribution attributes, including distribution cost center and business unit, so a split charge does not have to rely only on the invoice total. SAP Concur’s cost object approval follows the same idea by routing the allocated portion to each affected cost center for review. For rental spend, this matters because the line may be split across several jobs, and the risk is often in the coding, not in the gross amount.^[1][2][3]

2. Use three gates: match, ownership, and threshold

A simple control model works well for rental invoices with split billing. First is the match gate: does the split agree with the rental agreement, PO, dispatch ticket, rental order, or approved coding instruction? Second is the ownership gate: does every charged job or cost code have a named approver? Third is the threshold gate: does any share or the total invoice exceed your delegation of authority? If any gate fails, the invoice should pause for review instead of moving straight to payment.^[1][2][4][5]

3. Route each share to the right owner

Do not send a split-billed invoice to only one person if several budgets are charged. SAP Business ByDesign shows a practical pattern: account assignment can send the document to the cost center manager or the project manager based on the assignment. That is a good model for rental invoices because the person who owns the job should be able to confirm whether the equipment really belonged there. If an invoice touches both a project code and an overhead code, route each portion to the corresponding owner and keep AP in the loop for the final pay decision.^[4]

4. Set a clear escalation rule for large split charges

Split billing creates two kinds of risk: a large invoice total and a large charge against one job. Your rule should cover both. A good policy is to require approval from the affected owner for each share, then add a higher-level approval if any share exceeds that owner’s limit or if the invoice total exceeds a separate cap. Oracle’s sample rules show that approval can vary by distribution cost center and business unit, which makes it practical to combine budget ownership with value limits.^[1][4]

5. Decide what auto-approval is allowed to do

Auto-approval should be narrow. It is reasonable only when the split follows a preapproved allocation pattern, the invoice is matched to the rental agreement or PO, and no share crosses a limit. SAP Ariba supports splitting one invoice line across multiple accounts by percentage, and the percentages for a line need to add to 100. That kind of rule is useful when the allocation is already approved and fixed; it is not a substitute for approval when the split changes or when a job was charged unexpectedly.^[5]

6. Keep the rule set simple enough for AP to operate

If the workflow is too complicated, AP will end up manually fixing every exception. Use a small number of routing patterns: one for single-job invoices, one for two-way splits, one for multiway splits, and one exception path for missing or closed cost objects. In many organizations, the cleanest setup is to keep the approval logic tied to the accounting system’s distribution fields and to let AP review only the mismatches that the system cannot resolve automatically.^[1][2][3][4]

When each approval pattern applies

Use the routing pattern that matches the billing situation, not the one that is easiest to code once. The table below is a practical way to decide which pattern fits the invoice in front of you.^[1][2][4][5]

If the split does not match the approved coding

Do not force the invoice through a normal approval path when the split is wrong. Hold it for correction if the invoice is billed to the wrong job, if the percentages do not match the approved allocation, if a cost code is closed, or if the supplier billed a split that was never authorized. Review the rental agreement, the PO, the dispatch record, the off-rent confirmation, and any coding memo to decide whether AP should request a corrected invoice, a credit memo, or a revised allocation from the business owner. If the supplier terms allow the split but your internal approval is missing, route the invoice back for approval before payment.^[1][2][4][5]

If a cost object has no approver

This is a common failure point. If one of the charged jobs, cost centers, or projects has no active approver, the invoice should not default to payment approval from another owner. Instead, assign a temporary approver, reroute it to the project or cost center manager, or hold it until master data is corrected. SAP Concur’s cost object approval model is useful here because the affected cost centers review their portions directly, which reduces the chance that one missing approver lets an incorrect charge slip through.^[2][3][4]

If the invoice is correct but the split changed

Sometimes the rental charge is valid but the business changed the coding after the work was done. In that case, the workflow should require a documented coding change before approval, because the accounting split is part of the control, not just the bookkeeping. Keep a short record of who approved the change, why the allocation moved, and whether the supplier needs a revised invoice or whether your system can reallocate internally. That keeps the audit trail aligned with the actual job ownership.^[1][4][5]

Practical next steps

Review three things in your own process: the fields your AP system can route on, the approval authority tied to each job or cost code, and the source document that proves the split is valid. Then set one rule for matching allocations, one for multi-owner review, and one for escalation when a share or total crosses a limit. Finally, test the workflow with a few real rental invoices that split across jobs or cost centers and confirm that the right owners see the right share before payment.^{[1][2][3][4][5]}

← All resources