How to track maverick rental vendors that bypass preferred suppliers

By RentalSpend · October 9, 2026

Use AP and procurement data to spot rental spend that goes around your preferred supplier list, then rank the vendors, sites, and business units causing the leakage so you can fix the process.

Track maverick rental vendors by comparing actual rental invoices against your preferred supplier list, approved contracts, and PO records, then breaking the results down by supplier, site, business unit, and equipment category. The clearest signal is spend that appears from a nonpreferred vendor or an approved vendor used outside the expected contract or PO process, because that shows where your controls are leaking.^[1][2][3]

1. Load your preferred supplier list, approved contract references, and exception rules into one master view.
2. Match AP invoice lines, PO data, and rental agreements to the approved supplier list.
3. Flag any rental vendor with no approved contract, no PO, a missing supplier match, or spend outside the approved category or business unit.
4. Rank the flagged vendors by dollars, invoice count, and repeat frequency so you can see which ones matter most.
5. Review the top exceptions each month with AP, procurement, and operations, then decide whether to contract, block, or formally approve them.

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

1) Build one rental-vendor view before you look for exceptions

Start by cleaning the supplier master so every rental vendor has one consistent name, parent company, category, and status on the preferred list. If your contract repository or supplier file is incomplete, your results will overstate maverick spend because legitimate vendors may look out of contract when the system simply cannot match them. Oracle and SAP both emphasize comparing spend against contract and supplier data, which only works when the master data is usable.^[1][2][3]

• Preferred or nonpreferred status
• Contract number or agreement reference
• Category or equipment class
• Business unit, branch, or site
• Approved exception flag, if your company allows one

Sources: ^[1][2]

2) Match invoices, POs, and rental agreements line by line

Do not stop at vendor name alone. Rental spend can look compliant at the supplier level and still be off-contract at the line level if the equipment class, branch, or rate does not match the agreement. SAP’s supplier analysis reporting specifically calls out invoice spend, off-PO spend, and off-PO spend percentage, which makes it useful for spotting rental transactions that bypass the normal process.^[2]

3) Separate true maverick vendors from normal exceptions

Not every nonpreferred rental vendor is a problem. Some are legitimate emergency, specialty, or local-availability exceptions. The goal is to separate approved exceptions from unapproved bypasses, because otherwise you will waste time arguing over transactions that were allowed. Keep a simple exception code or comment field so operations can explain the reason for the off-list rental at the time of review.^[3][4][5]

• Emergency replacement needed to keep a job moving
• Specialty equipment not available from preferred suppliers
• Temporary local availability issue
• Approved project-specific supplier
• Data or coding error that should be corrected

Sources: ^[3][4][5]

4) Rank the vendors by dollars, frequency, and repeat behavior

The most useful ranking is not just who spent the most, but who keeps appearing. A vendor with a few large emergency rentals may need a contract exception, while a vendor with many small off-list invoices may point to habit, weak enforcement, or a missing local supplier agreement. Compare current spend with prior periods so you can tell whether maverick activity is growing or shrinking.^[1][2]

5) Review the patterns that point to control gaps

Once you have a ranked list, look for patterns by branch, project, and equipment class. If one site repeatedly uses a nonpreferred rental house, the issue may be local convenience, poor catalog coverage, or a missing supplier in the system. If the same equipment type keeps appearing off-contract across several sites, the issue may be a weak preferred supplier offering or an incomplete agreement that does not cover the items people actually need.^[1][2][4]

• One branch or project drives most of the bypasses
• The same equipment class appears off-list repeatedly
• Invoices arrive without PO numbers or with generic descriptions
• The vendor is approved but the wrong contract is used
• Many exceptions are coded the same way, which hides real maverick spend

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

What to do when a vendor does not match

If a rental vendor does not match the preferred list, start with the basics: confirm the supplier name, the invoice coding, the contract reference, and the PO status. Then ask whether the transaction was an approved exception or a true bypass. If the record is simply miscoded or the contract was missing from the system, fix the master data and rerun the report. If it is a real bypass, decide whether to add the vendor, renegotiate the lane, or block future spend until the approved process is followed.^{[1][2][3][4][5]}

• Correct supplier and contract master data when the transaction was legitimate but misclassified
• Document approved exceptions so they do not keep showing up as unexplained leakage
• Escalate repeated bypasses to procurement and operations for supplier rationalization
• Use the findings to update buying rules, catalogs, or branch-level guidance

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

Practical next steps

Begin with a 60- to 90-day review of rental invoices, PO data, and approved supplier records. Build one report that shows off-list vendors, off-PO rentals, contract references, and spend by site. Then meet monthly with AP, procurement, and operations to decide which vendors should be approved, corrected, or stopped. The goal is not just to find maverick rental vendors, but to keep them from becoming the easy default on the next job.^[1][2][3][5]

← All resources