Sub-hub: MRO and Class C spend audit

Executive Summary

MRO and Class C spend, the fasteners, safety supplies, gloves, tape, small tools, and shop consumables that keep a plant running, is structured to defeat normal AP review. Individual line items are too small to trigger a hold, purchase orders are often blanket or punch-out orders rather than itemized ones, and the catalog a vendor bills against changes more often than the contract that governs it. The result is not one large error.

It is thousands of small ones that never separately justify investigation.

The mechanism is catalog drift: a vendor's e-procurement punch-out catalog updates on its own schedule, substituting SKUs, adjusting unit prices, and repackaging quantities, while the underlying supply agreement states a fixed price list or a discount off list that nobody re-checks against the live catalog. Three-way matching confirms the invoice matches the purchase order and the receipt. It does not confirm the punch-out price matches the contracted price list, because the contract lives in a PDF outside the ERP and the catalog lives in a vendor-hosted system outside both.

What changes it is treating MRO spend as a distinct audit lane with its own method: pull the full contract price list, pull a invoice sample across a period, and reconcile SKU by SKU rather than by total spend. That is described in the sections below, along with where this lane sits next to the freight, labor, and maintenance lanes covered elsewhere in this guide.

1. What makes MRO and Class C spend a distinct audit lane?

MRO and Class C spend covers fasteners, safety supplies, tape, gloves, small tools, and shop consumables purchased against blanket orders or e-procurement punch-out catalogs rather than itemized purchase orders. Because unit values are low and order volume is high, it sits below the dollar thresholds that trigger manual invoice review, and it is billed against a catalog that can change independently of the contract price list behind it.

A freight invoice has a handful of line items and a rate confirmation to check it against. A contract labor invoice has named workers and a timesheet. An MRO invoice can carry hundreds of SKUs in one shipment, each worth a few dollars, drawn from a punch-out catalog the vendor hosts and updates on its own schedule.

That structure changes what an audit control has to do. Dollar-threshold review, the standard AP practice of routing anything over a set amount for manual look, is built for large individual errors. It does not surface a category where the error is a few cents per SKU repeated across thousands of SKUs.

The contract governing this spend is usually a price list or a percentage discount off a published list, negotiated once and rarely revisited. The catalog the punch-out system serves up is a separate, live artifact. Nothing in the ERP checks one against the other, because the ERP only sees the invoice and the purchase order it was cut against, both of which reflect whatever the catalog said at the moment of order.

2. Why do approved purchase orders still produce the wrong price?

A purchase order approved through e-procurement reflects the punch-out catalog price at the moment the cart was submitted, not the price the master agreement specifies. If the catalog has drifted from the contract, a fully approved, three-way-matched invoice can still be wrong, because approval confirms the order matched the invoice, not that either matched the contract.

Three-way matching checks the invoice against the purchase order and the goods receipt. It confirms the buyer received what was ordered and was billed what was quoted at order time. It does not test whether the quoted price is the contracted price, because the contract price list is not a field the matching engine has access to.

A punch-out catalog can drift from its contract in several ways: a SKU renumbered after a packaging change, a unit-of-measure switched from each to case without a corresponding price adjustment, a promotional price that expired but stayed live, or a new item added to the catalog with no contracted price at all, billed at list.

Each of these produces an invoice that is internally consistent. The order matches the receipt, the receipt matches the invoice, and the approval workflow has nothing to flag. The only way to catch the drift is to compare the catalog price, at the time of the order, against the contract price list directly, which is a step outside the standard three-way match.

3. Which SKU-level patterns should a reviewer look for?

A reviewer working MRO invoices should isolate four patterns: SKU substitution, unit-of-measure changes, minimum order and small-order fees layered on top of contracted unit prices, and rebate or volume-tier thresholds that go untracked because no single order is large enough to trigger them. Each requires comparing the invoice against the contract's price list and terms, not against the purchase order.

These patterns share a cause: the contract's terms are written at a level of detail the catalog and the ERP do not carry forward.

A. SKU substitution

A vendor discontinues a part number and substitutes an equivalent one. The substitute often lands in the catalog at a different price point, sometimes because it is a different manufacturer's part with a different cost basis. Substitution pricing is a distinct and well-documented drift pattern in its own right, worth checking against directly rather than assuming the new SKU inherited the old contract price.

B. Fees layered on unit price

Minimum order charges, small-order fees, and hazardous-material handling fees are frequently absent from the original contract but appear on invoices once a vendor's billing system defaults them in. Each is small. Applied to every order under a threshold, across a year of ordering, the total is not.

C. Untracked rebate and volume tiers

MRO contracts sometimes include a rebate or price break once cumulative annual volume crosses a stated tier. Because MRO purchasing is fragmented across many small orders and often several requesters, nobody is positioned to see the running total, so the tier is never claimed.

4. How does this lane relate to maintenance and calibration spend?

MRO and Class C spend is adjacent to, but distinct from, maintenance and repair invoices and calibration and safety compliance invoices. Maintenance spend is billed against work orders and labor rates; MRO spend is billed against a parts catalog. A plant's total indirect spend audit has to cover both, because a maintenance work order frequently draws parts from the same MRO catalog this lane examines.

A maintenance technician dispatched on a work order often pulls fasteners, gaskets, lubricants, or safety supplies from the same punch-out catalog covered here, and bills them as part of the work order rather than as a separate MRO purchase. That means a catalog price error can surface twice: once on a direct MRO invoice and once buried inside a maintenance invoice's parts line.

Calibration and safety compliance spend is a narrower, more specialized category, usually billed per instrument or per site visit rather than per SKU, and it carries its own contract terms around certification intervals and recall obligations. It is worth auditing separately for that reason, even though a plant's safety supply purchases (gloves, signage, lockout-tagout kits) often route through the same MRO catalog.

A full indirect spend review therefore treats MRO as both a lane of its own and a cross-check against the parts lines inside maintenance invoices, rather than assuming a single review of either category catches everything the other misses.

5. What does a reviewer need before starting an MRO audit?

An MRO audit needs three inputs before it can start: the current contract price list or discount schedule, an invoice export covering a full ordering cycle, and the punch-out catalog's price history if the vendor's e-procurement system retains one. Without the contract price list as a fixed reference point, an invoice review can only compare invoices to each other, not to what was actually agreed.

The contract price list is the hardest of the three to get, because MRO agreements are often folded into a broader supply agreement, referenced by exhibit number, and stored outside the ERP entirely. Locating the actual current exhibit, not an earlier version, is the first real task.

The invoice export should cover enough of an ordering cycle to catch seasonal or promotional pricing changes, not just a single month. A short window understates how much a catalog price can move between review points.

Catalog price history is the input most vendors will not offer unprompted. Some punch-out platforms retain it and will provide it on request; where they do not, the reviewer is limited to comparing the invoice date's price against the contract, without visibility into how long a discrepancy has existed.

6. Should this spend be handled with AP automation or a dedicated review?

AP automation and three-way matching confirm an invoice matches its purchase order and receipt at the point of processing. Neither tests the punch-out catalog price against the contract price list, because the contract terms are not data either system holds. Catching catalog drift requires a review step built specifically to compare the two, run periodically rather than at invoice receipt.

This is not a case against AP automation. Automated matching correctly stops invoices that do not tie to an order or a receipt, and that control should stay in place regardless of what else is reviewed.

What it does not do is interpret a contract exhibit sitting in a PDF and check a live catalog against it. That comparison sits outside both systems' data model, and building it requires someone, or some process, to hold the contract terms as a structured reference and run the invoice or catalog data against it on a recurring basis.

A one-time reconciliation catches the drift that has already accumulated. A recurring one, whether run internally on a schedule or as part of a broader indirect spend audit covering freight, labor, maintenance, and IT services alongside MRO, is what keeps the gap from reopening once closed.

For the wider pattern this sits inside, start with the margin drift guide. See also margin drift vs. legitimate price increases: how to tell them apart and accessorial charge audit: the surcharges nobody validates.

7. Frequently Asked Questions (People Also Ask)

What counts as MRO and Class C spend?

MRO stands for maintenance, repair, and operations. Class C typically refers to low-unit-value, high-transaction-volume items: fasteners, gloves, tape, small tools, safety supplies, and general shop consumables, usually purchased through a blanket order or e-procurement punch-out catalog rather than an itemized purchase order.

Why doesn't three-way matching catch MRO pricing errors?

Three-way matching checks that the invoice matches the purchase order and the goods receipt. It confirms the buyer was billed what the punch-out catalog quoted at order time. It does not check that catalog price against the separate contract price list, which sits outside the ERP and outside the matching engine's data.

How is MRO spend different from maintenance and repair spend?

Maintenance and repair invoices are billed against work orders and labor rates for a specific job. MRO spend is billed against a parts catalog independent of any single job. The two overlap when a maintenance technician pulls parts from the MRO catalog and bills them inside a work order, which is worth checking separately.

What is SKU substitution and why does it matter for pricing?

SKU substitution happens when a vendor discontinues a part number and replaces it with an equivalent one in the catalog. The substitute frequently carries a different price point than the original contracted item, and nothing in standard order processing confirms the new SKU inherited the old contract price.

Can a contract's volume rebate on MRO spend go unclaimed?

Yes. MRO purchasing is often fragmented across many small orders and multiple requesters, so nobody tracks the running annual total against the contract's rebate threshold. The rebate exists in the agreement but is never triggered because the volume is never consolidated and checked.

Do minimum order fees and small-order charges belong on MRO invoices?

Only if the contract specifies them. Some vendor billing systems default in minimum order charges, small-order fees, or handling fees that were never part of the negotiated agreement. Each fee is small individually; applied across a high volume of small orders, the total is worth checking against contract terms.

How far back should an MRO invoice review look?

Long enough to span a full ordering cycle and catch any seasonal or promotional catalog pricing, rather than a single month that may not reflect how much the punch-out price has moved. The exact window depends on order frequency and how often the vendor updates its catalog.

Does this audit require the vendor's catalog price history?

It is useful but not always available. Some punch-out platforms retain price history and will share it on request. Where they do not, the reviewer can still compare the price on each invoice date against the contract price list, without full visibility into when a discrepancy first appeared.

Is MRO spend covered in a broader indirect spend audit?

Yes. MRO and Class C consumables are one of several indirect spend categories, alongside freight and 3PL, contract labor, maintenance and repair, and IT and professional services, that a full audit reviews using a method matched to how each category is actually billed.