Monthly Rental Spend Variance Review for Controllers

By RentalSpend · October 7, 2026

Build a monthly controller review that compares each rental invoice to the contract, receipt, off-rent, and approved charges. Roll exceptions by vendor, project, and variance type so recurring leakage shows up before month-end close.

A monthly rental spend variance review should compare each material invoice to the contract or PO, the delivery or receipt record, the off-rent or return confirmation, and any approved add-on charges, then roll the differences into a monthly report by vendor, project, equipment class, and exception type. That gives controllers a repeatable way to spot rate, date, quantity, fuel, cleaning, damage, delivery, pickup, tax, and surcharge variances before close, while keeping the contract and rate sheet as the control standard because rental terms vary by supplier agreement.^{[1][2][3][4][5][6]}

Build the review around five matching points

The simplest controller workflow is a document match, not a payment-only check. For each material invoice, line up the contract or PO, the supplier invoice, the receiving or delivery evidence, the off-rent or return record, and the approval for any extra charge. Work from the contract and rate sheet first, because those documents define the billed rate and which add-ons are allowed under that account. If your company uses a three-way match for AP, add the operational off-rent record as a fourth control for rentals because billing can continue until the supplier records the return or off-rent notice.^[1][2][3][7]

1. Start with a materiality threshold so the team focuses on invoices and jobs that can actually move the monthly close.
2. Match the invoice to the PO or contract rate sheet and confirm the billed rate, unit of measure, minimum term, and any approved surcharges.
3. Compare the billed dates to the delivery, return, and off-rent evidence to make sure the rental period is right.
4. Check every ancillary line such as delivery, pickup, fuel, cleaning, repair, taxes, environmental fees, and other surcharges against the agreement.
5. Summarize each exception by vendor, project, equipment class, and variance type so repeated issues can be escalated instead of corrected one invoice at a time.

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

What to classify as a variance

A monthly review works best when every exception gets put into a small set of buckets. That keeps the report readable and makes recurring patterns easier to spot across projects and vendors. The most useful buckets for rental spend are rate, period, quantity, ancillary charge, and accounting treatment.^{[4][5][6][7][8][9]}

How to run the month-end review

Controllers usually get the cleanest result when they run the review in the same order every month. First, pull the invoice population for active rentals and any unpaid prior-period items that were received but not yet paid. Then group the invoices by vendor and project. Next, compare each line to the contract, off-rent evidence, and approved add-ons. Finally, post the findings into an exceptions log and summarize the totals for close.^[1][2][8][9]

1. Pull the month’s rental invoices, open accruals, and any credit memos not yet cleared.
2. Sort the population by vendor, project, and equipment class so duplicates and repeats are easy to see.
3. For each invoice, test the rate, billing period, ancillary charges, and tax or fee lines against the contract and support.
4. Mark each exception as a timing issue, pricing issue, pass-through charge needing support, or legitimate charge.
5. Roll the results into a monthly variance report and carry unresolved items into the next close cycle.

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

Where the biggest misses usually show up

Most rental variance reviews uncover the same few problem areas: the unit stayed billed after it was actually off rent, a rate changed without a contract backup, a delivery or pickup fee appeared more than once, or a cleaning or fuel charge was added when the return record suggests the unit met the return condition. Whether those charges are valid depends on the agreement and the supplier’s supporting records, so the controller’s job is to separate legitimate pass-through costs from amounts that should be credited or corrected.^[4][5][6][7]

• Off-rent timing: the invoice runs longer than the documented use period.
• Rate mismatch: the daily, weekly, or monthly rate does not match the agreement.
• Duplicate ancillary charges: delivery, pickup, or other fees appear more than once.
• Condition charges: cleaning, refueling, repair, or damage charges need support from the return condition and agreement.
• Tax or surcharge issues: the charge may be right, but the tax code, jurisdiction, or fee basis needs review.

Sources: ^[4][5][6][7]

How to summarize the month for management

A useful monthly controller report should show total rental spend, total exceptions, and the exceptions by vendor, project, and type. Keep the numbers simple enough for operations leaders to act on. For example, show how much was tied to timing differences versus true pricing issues, and flag vendors or projects with repeat findings so the supplier conversation focuses on root cause rather than one invoice at a time. That approach helps the team improve vendor accountability and reduce administrative churn.^[1][2][8][9]

• Top vendors by exception count and exception value
• Top projects by unresolved variance
• Most common variance types for the month
• Items carried into the next close cycle
• Credits received versus credits still outstanding

Sources: ^[1][2][8][9]

What to do when the review finds a problem

If a variance is supported by the contract and records, book it and move on. If the billed amount does not match the agreement or the evidence, place the invoice or line on hold, request support, and open the dispute or credit process under your company’s policy. Keep the reason code consistent so the monthly trend is meaningful. Because rental terms vary by supplier agreement, never assume an ancillary charge is invalid just because it is unfamiliar; confirm it against the actual contract and rate sheet for that account.^[4][5][6][7]

• Hold the disputed line or invoice before payment if your policy allows it.
• Request the supplier backup: rate sheet, off-rent confirmation, pickup record, or fee support.
• Decide whether the issue is a timing correction, a pricing correction, or a legitimate charge.
• Capture the variance in the monthly log with the same reason code every time.
• Escalate repeat issues to the supplier account team when the pattern appears across multiple invoices or projects.

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

Practical next steps

To make the review stick, pick one month of invoices, define your variance buckets, and standardize the documents you will test every time. Then build a short report that shows vendor, project, invoice value, exception value, and reason code. Once the team can repeat that process consistently, the monthly review becomes a control, not just a cleanup exercise.^[1][2][8][9]

← All resources