Set Up a Rental Rate Sheet Approval Workflow

By RentalSpend · October 10, 2026

Set up the workflow so no new rental rate sheet goes live until the contract basis, the exact pricing, and the effective date are all approved. Keep the old version active for prior rentals and make AP verify the invoice before payment.

Set up the approval workflow so a new rental rate sheet cannot go live until someone has confirmed three things: the change is allowed under the contract, the rates match the signed documents, and the effective date is controlled in your system and communicated to AP and procurement. Keep the person who prepares the rate sheet separate from the person who approves it, and require AP to still compare every invoice to the agreed rate, supporting documents, and approved master file before payment.^[1][2][3]

1. Identify the governing document for the rate change and confirm whether the supplier contract allows changes by signed amendment, notice, or another method.
2. Route the new rate sheet for review by someone with authority, and keep the preparer, reviewer, and approver as separate roles.
3. Check each changed rate line by line against the signed agreement, the vendor master, and the intended effective date.
4. Load the new rates only after approval, while keeping the prior version active for rentals that started before the change.
5. Tell AP, procurement, and the field team which version applies, and hold any invoice that does not match the approved file.

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

Start with the contract and the signed change

The first control is simple: do not treat a revised rate sheet as active just because someone emailed it. In many agreements, the signed contract and any signed amendment control when a price change can take effect. One supplier’s US rental terms state that no amendment or modification is effective unless it is in writing and signed by the parties. Your workflow should therefore require the contract basis for the change before the new sheet can move forward.^[1]

If your contracts allow a different approval path, such as a notice period or an authorized representative’s approval for a specific change order, build that into the workflow. Terms vary by supplier and by document set, so the approval path should follow your own agreement, not a generic rule.^[1]

Separate preparation, review, and approval

A workable workflow has at least three roles. The preparer gathers the proposed rate sheet and supporting documents. The reviewer checks the pricing and compares it to the contract, vendor master, and any class-code, branch, or job-specific pricing. The approver is the person with authority to accept the change and set the effective date. GAO’s internal-control guidance emphasizes approval by authorized people under established policies and procedures, and segregation of duties so one person cannot both create and hide an error.^[2]

If one person has to do more than one of these jobs in a small company, make the review evidence stronger. For example, require a second sign-off on the pricing comparison or a documented manager approval before activation.^[2]

Build the line-by-line rate check

Do not approve a new sheet as a generic bulk update. Compare each changed line to predetermined expectations: base rate, minimum, overtime, weekend, pickup or delivery charge, damage waiver, fuel surcharge, and any other fee that appears in your contract or invoice format. GAO guidance calls for comparing transactions with agreed-upon prices and reviewing exceptions by an authorized approver.^[2]

A good review packet usually includes the current signed rate sheet, the proposed replacement, the contract or amendment that authorizes the change, and a list of the exact lines that changed. If the supplier uses multiple branches, equipment classes, or jobsites, the workflow should force the reviewer to confirm each scope separately. That reduces the risk that a sheet is approved for one branch and applied too broadly.^[2]

Control the effective date and version history

The go-live date is where many process failures happen. The approved new sheet should have a clear effective date, and the old version should stay in the system for rentals that started earlier. That preserves the correct terms for open tickets and avoids mixing old and new pricing on the same rental period. GAO guidance supports matching key records before approval and comparing transactions with approved master files; the same logic applies here.^[2]

Your workflow should also require someone to confirm that the vendor master was updated correctly. If the rate sheet is approved but the master file is not changed, AP may keep paying the old rate or apply the wrong one. A pre-go-live reconciliation between the approved sheet, the vendor master, and a small sample of open rentals helps catch that mismatch before it reaches payment.^[2][3]

Make AP the back-end control

Even a solid approval workflow should not end at go-live. AP needs a final check before payment to confirm the invoice matches the approved rate sheet, the rental dates, and any supporting documents such as pickup records or off-rent confirmations. GAO describes administrative approval as verifying the items or services were received and that the invoice matches the order or agreement, while payment authorization must ensure quantities, prices, and calculations are accurate.^[3]

If an invoice shows the wrong rate, the approver should hold payment and escalate it for correction. That is especially important when the invoice spans dates before and after the effective date. In that case, the invoice may need to be split so the earlier days remain on the old sheet and the later days use the new one.^[3][4]

What to do when something does not match

• If the contract does not clearly authorize the change, stop the workflow and request the signed amendment or other required written approval.
• If the new rate sheet does not match the signed document, return it to the supplier for correction before it is loaded.
• If the vendor master shows the wrong version, update the master file only after the approved effective date and keep evidence of the change.
• If an invoice uses the wrong rate, hold payment, document the exception, and ask for a corrected invoice or credit memo as your contract allows.
• If the rate change affects an open rental, verify which dates belong to the old version and which belong to the new one before approving payment.

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

Practical next steps

Write the workflow as a short internal procedure with named roles, required documents, approval thresholds, version-control rules, and AP checks. Then test it with one real rate-sheet change and one open rental so you can confirm the new version, the old version, and the invoice review all line up the way your contract requires. If you need a control design that connects approvals, versioning, and invoice checks across multiple vendors, RentalSpend can help you think through the process against your own documents.^[1][2][3][4]

← All resources