Common mistakes when auditing MRO consumables

Executive Summary

MRO and Class C consumables audits fail for a structural reason: the dollar value per line is too small to justify manual review, so most companies review nothing and trust the catalog price. The vendor's price file, not the purchase order, becomes the de facto contract, and price files change without anyone re-approving them.

The mechanism is substitution, unit-of-measure mismatch, and vending replenishment running ahead of any check against the agreed price list. Each of these produces a small variance per transaction. None of them shows up as a single alarming invoice. They show up only when a full year of purchase history is matched against the contracted price list line by line.

What changes it is treating the price file itself as the audit object, not the invoice. A rate card enforcement discipline built for labor and freight applies just as directly to a fastener SKU: catch the drift at the point the price changes, not a year later when someone finally adds up the SKUs.

1. What should you look for in MRO and Class C consumables invoices?

Look for four things: SKU-level price against the current contracted price list, not last year's; unit-of-measure consistency between the PO and the invoice; substituted part numbers billed at a different price than the original; and vending or VMI replenishment quantities matched against actual consumption. Any one of these can drift silently because each transaction is too small to trigger manual review, and the price file itself is rarely re-verified after initial setup.

Start with the price file. Most MRO contracts specify pricing by SKU or by category discount off list, refreshed on a schedule. Pull the vendor's current price file and compare it against what invoices actually charged for a sample of your highest-volume SKUs. A mismatch here means every order since the last check has been wrong in the same direction.

Then check unit of measure. A box of 100 billed as a box of 50 doubles the effective unit price without changing the line item description.

Finally check substitutions. When a specified part is out of stock, the vendor ships an equivalent. The replacement's price sometimes carries a premium that the original contract never authorized.

2. How does substitution pricing get invoices wrong?

A contract prices a specific part number. When that part is unavailable, the vendor substitutes an equivalent and invoices it at the substitute's list price rather than the contracted price for the original item. The invoice still shows a plausible line for a plausible product, so it clears three-way matching against the purchase order description without anyone comparing the substitute's price to the original agreement.

Three-way matching checks the invoice against the purchase order and the receipt. It does not check whether a substituted item is priced against the original contract line or against the vendor's open-market rate for the replacement.

The fix is a substitution log: every time a part number on an invoice does not match the part number on the PO, flag it and price-check the substitute separately. This is a mechanical control, not a judgment call, and it catches the exact pattern that ordinary matching misses.

3. What goes wrong with vending machine and VMI programs?

Vendor-managed inventory and vending programs replenish stock automatically, and the invoice reflects what the vendor's system says it dispensed, not an independent count. Because the client rarely audits dispensed quantity against actual consumption, a miscalibrated machine or an inflated replenishment count bills for parts that were never used. The visibility trade in these programs is real: convenience for the client, less independent verification of quantity.

A vending machine tracks dispensing through its own sensor or badge-swipe log. That log is also the basis for the invoice. There is no independent party confirming the count.

Request the raw dispense log, not just the summary invoice, and compare a sample period against physical bin counts or against a department's actual work order volume for that period. A gap between dispensed quantity and plausible usage is the signal, not a specific percentage, because no dataset exists to say how often this occurs across vendors.

Ask also whether the replenishment par levels were ever renegotiated after the initial setup. Par levels set for a production ramp-up often stay in place after volume drops, and the vendor keeps restocking to the old level.

4. How do you catch unit-of-measure and packaging errors?

Unit-of-measure errors happen when the contract specifies price per each, per box, or per case, and the invoice silently switches the unit while keeping the same price, effectively changing the per-item cost. Catch this by re-deriving the per-each price from every invoice line, using the pack quantity printed on the line, and comparing that derived figure against the contracted per-each rate rather than trusting the invoice's stated unit price.

The contract says $12 per box of 100. The invoice line says $12, quantity 1, but the pack size printed on the line has quietly changed to a box of 50. The unit price looks identical to the contracted rate and passes a cursory check.

The only reliable check is arithmetic: total price divided by actual unit count, not the box or case count as labeled. Build this as a standing calculation against every recurring SKU rather than a one-time spot check, because packaging changes are made by the vendor's fulfillment system, not by anyone who tells you it happened.

5. Does the commodity index matter for MRO contract pricing?

Some MRO and general-purpose machinery and equipment contracts include index-linked pricing clauses tied to a published producer price series. Per the US Bureau of Labor Statistics Producer Price Index for Machinery and equipment, general purpose (series WPU114), the July 2026 index value was 379.724, up 5.6% year over year (read September 6, 2026). If your contract references an index, an increase that size should be traceable to a specific clause, not an unexplained catalog reprice.

An index-linked clause typically caps how much a vendor can raise prices, or ties an increase to a published benchmark instead of the vendor's own discretion. If your contract has this clause, the vendor's price increase should match the referenced index period, not run ahead of it.

When a price increase shows up on an invoice that exceeds what the referenced index actually moved, that is a checkable discrepancy: pull the index value for the contract's specified period and compare it directly against the increase applied.

This only applies where the contract actually references a published index. Most Class C consumable contracts do not, and absent that clause there is no benchmark to hold a general-purpose price increase against.

6. What should an MRO audit checklist actually include?

A usable checklist has five concrete steps: pull the current contracted price file, sample the top 20 SKUs by annual spend and compare invoiced price to contracted price, flag every substituted part number for separate price verification, re-derive unit price from pack quantity on every recurring line, and reconcile vending dispense logs against physical counts for at least one sample period per quarter.

Each step above produces a specific, checkable output: a price variance list, a substitution log, a unit-of-measure exception report, and a vending reconciliation. None of them requires a portfolio-wide benchmark or an industry average. Each compares your own invoice against your own contract or your own physical count.

1. Pull the current price file: Get the vendor's active contracted price list, not a version from initial setup, and confirm it was actually approved at its last update.
2. Sample top SKUs by spend: Compare invoiced unit price against contracted price for your highest-volume 20 to 50 SKUs, since that is where drift compounds fastest.
3. Log every substitution: Flag any invoice line where the part number does not match the purchase order, and price-check the substitute against the original contract line separately.
4. Re-derive unit price: Divide total line price by actual unit count printed on the line, not the labeled case or box size, for every recurring SKU.
5. Reconcile vending logs quarterly: Pull raw dispense logs and compare against physical bin counts or plausible department usage for at least one sample period each quarter.

7. Where does this fit inside a broader indirect spend audit?

MRO and Class C consumables is one of several categories where margin drift accumulates, alongside freight, contract labor, maintenance, and IT services. Each category has its own mechanism: substitution and unit-of-measure errors in MRO look nothing like rate card violations in staffing or accessorial charges in freight. A full diagnostic checks all of them against the underlying contract, because a control built for one category will not catch drift in another.

MRO consumables rarely gets audit attention because each transaction is small. That is exactly why it compounds: a control gap here persists for years without ever generating a single invoice large enough to draw scrutiny.

The checks above (price file verification, substitution logging, unit-of-measure recalculation, and vending reconciliation) are specific enough to run without outside help, once someone owns them. Where they are not currently owned by anyone, that ownership gap is itself the finding worth fixing first.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and accessorial charge audit: the surcharges nobody validates.

8. Frequently Asked Questions (People Also Ask)

How often should we re-check the MRO price file against invoices?

Tie the check to whenever the vendor's price file updates, not to a calendar. Most MRO contracts specify a refresh schedule (often annual or quarterly); pull invoices from the period right after each refresh and confirm the new prices match what the contract actually authorized before the next cycle starts.

Is a small per-unit price variance worth investigating?

Check the total exposure across volume before deciding, not the per-unit figure alone. A $0.04 variance on a fastener ordered thousands of times a year is a material line once multiplied; the same variance on a part ordered twice is not worth the review time.

Who typically owns MRO invoice accuracy inside a manufacturer?

Ownership is often split between procurement, which negotiates the contract, and accounts payable, which pays the invoice, with neither side comparing the two against each other. Naming a single owner for the price-file-to-invoice check is a prerequisite for any of the controls in this article to hold.

Can vending and VMI programs be audited without vendor cooperation?

Partially. You can reconcile physical bin counts and work order volume against invoiced quantities using only your own records. A full reconciliation of the vendor's dispense log requires the vendor to provide raw data, which the contract should specify as an access right up front.

What is the difference between a substitution and a pricing error?

A substitution is a legitimate part swap when the original SKU is unavailable. It becomes a pricing error only when the substitute is billed at a rate the original contract never authorized. The distinction matters because the fix for one is a contract amendment and the fix for the other is a credit memo.

Does an index-linked pricing clause apply to most Class C consumables?

No. Most Class C consumable contracts price by flat SKU rate or category discount rather than referencing a published index. Index-linked clauses appear more often in general-purpose machinery and equipment contracts, where the underlying commodity cost is volatile enough to justify one.

What documentation should we request from an MRO vendor before an audit?

Request the current signed price file, the substitution policy in writing, raw vending dispense logs if applicable, and the purchase order history for the period under review. Without the signed price file, there is no baseline to compare invoices against.

How does this category compare to freight or labor for audit priority?

Each indirect spend category carries its own drift mechanism and needs its own checklist; none can be ranked as bigger or smaller without a dataset broken out by category, which does not exist. Prioritize based on your own spend concentration and control gaps rather than an assumed industry pattern.