What auditors miss in MRO and Class C consumables

Executive Summary

MRO and Class C spend looks too small to matter until the line count is added up. Fastener kits, gloves, sealants and shop supplies price against a catalog that changes without an amendment, get substituted at the SKU level without repricing, and roll through vending machines that few AP teams reconcile line by line. Standard AP review checks that a PO exists and the invoice total matches the receipt.

It does not check whether the SKU shipped is the SKU quoted, whether a catalog price increase was authorized, or whether a vending replenishment count matches what the machine actually dispensed.

The mechanism is catalog drift plus substitution plus low per-line dollar value. Each invoice line is too small to trigger a manual review threshold, so the control that would catch a $4,000 freight overcharge never fires on a $40 pricing error repeated across 600 SKUs a year. Input costs for general purpose machinery and equipment rose 5.6% year over year as of July 2026 per the BLS Producer Price Index, which is exactly the kind of increase that gets passed through on the next catalog refresh without a corresponding contract amendment.

What changes it is checking the mechanism, not the total: matching invoiced SKU to quoted SKU, testing catalog price changes against the effective date in the agreement, and reconciling vending dispense counts against replenishment invoices on a sample basis.

1. Why does SKU substitution slip past a matched invoice?

A vendor substitutes an equivalent part number when the exact SKU is out of stock, and the invoice lists the new part at a different price. Three-way matching checks that the invoice total agrees with the PO and receipt; it does not check that the SKU on the invoice is the SKU the contract priced. If the substitute carries a higher unit price with no cross-reference back to the original quote, the increase clears review with the receiving document as.

A purchase order names a part number and a unit price. Receiving confirms a quantity arrived. Neither step compares the part number on the packing slip to the part number in the pricing agreement.

When a distributor substitutes a functionally equivalent item, often noted only in a footnote or a code on the packing slip, the new SKU can carry a list price rather than the contracted price. The invoice still balances against the PO in dollar terms if the quantity and total look plausible.

A checkable control: pull a sample of invoice lines where the SKU does not exactly match the PO line, and confirm the substitute was cross-referenced against the master price list before payment, not after.

2. What counts as unauthorized catalog price drift?

Catalog price drift is a unit price increase that takes effect before the date the contract allows, or that exceeds the ceiling the contract sets for annual adjustments. Most MRO agreements tie pricing to a catalog with a stated review cycle and an effective date for changes. When the vendor's system updates the catalog on its own schedule rather than the contract's, invoices can carry the new price for weeks before anyone checks whether the change was due.

MRO contracts typically reference a vendor catalog by version or date rather than listing every SKU's price individually. That structure works only if someone checks the catalog version cited on the invoice against the version the contract currently authorizes.

Input costs for general purpose machinery and equipment rose 5.6% year over year in the Producer Price Index reading for July 2026, per the US Bureau of Labor Statistics (read 2026-09-06). A catalog refresh timed to a cost increase like that is a normal business decision. Whether it was applied on the date the contract permits is a separate, checkable question.

A checkable item: request the vendor's catalog effective-date log for the audit period and compare it line by line to invoice dates, not to invoice totals.

3. How do minimum order and small-order penalties get missed?

Many MRO agreements charge a small-order or minimum-quantity fee when a line falls below a stated threshold, and the fee is meant to apply per order, not per line item. AP review confirms a fee appears on an invoice that has one; it rarely confirms the fee was calculated against the contract's stated threshold rather than the vendor's own default, or that it was not charged twice on a single consolidated order.

A minimum order fee exists to recover a vendor's fixed cost of processing a small transaction. The contract states a dollar or unit threshold below which it applies, and it should apply once per order.

Two checkable failure points recur. First, the fee calculated against a threshold different from the one in the current agreement, often because the vendor's ERP still references an earlier contract version. Second, the same fee applied to each line within a consolidated order rather than once for the order as a whole.

A checkable control: for every invoice carrying a minimum order or small-order fee, confirm the order-level total against the contracted threshold, and confirm the fee was not duplicated across lines within the same order number.

4. What does a vending or VMI program hide from the invoice?

Vending and vendor-managed inventory programs replenish stock based on a sensor or bin-count trigger, and the replenishment invoice reflects what the vendor's system reports was dispensed, not an independently counted quantity. Without a periodic physical reconciliation, an invoice can bill for a replenishment quantity that exceeds what the machine actually released, and there is no PO line to catch it because the program was set up to remove the PO step entirely.

Vending and VMI arrangements trade purchase-order friction for visibility. That trade is often worth making, but it removes the one document that would otherwise let AP compare an ordered quantity to a billed quantity.

The invoice in these programs is generated from the vendor's own dispense or bin-refill data. If that data overstates consumption, whether from a sensor error or a manual count entered incorrectly, the resulting invoice has no independent quantity to check it against.

A checkable item: schedule a physical bin count against the vendor's reported dispense log on a sampling basis, at minimum quarterly, and reconcile any variance before the next replenishment invoice is approved rather than after several cycles have passed.

5. Which contract terms should an MRO audit actually pull?

An MRO audit needs five documents pulled together before any invoice is tested: the current catalog version and its effective date, the SKU cross-reference list for approved substitutes, the minimum order threshold, the freight or fuel surcharge schedule if the vendor bills shipping separately, and the rebate or volume tier schedule if one exists. Testing invoices against anything less leaves the reviewer unable to tell a legitimate charge from drift.

A. A. Catalog and substitution documents

The catalog version cited on the invoice and its stated effective date are the baseline for every unit price test. Alongside it, the SKU cross-reference list shows which substitute part numbers the vendor is authorized to ship at the original contracted price, so a substitution can be verified rather than assumed.

B. B. Fee and rebate schedules

The minimum order threshold and any freight or fuel surcharge schedule determine which add-on charges are legitimate and at what amount. A rebate or volume tier schedule, where one exists, sets the purchase level at which a credit is owed back, which is the item most often left unclaimed because no one recalculates it against actual annual spend.

6. How should you prioritize what to test first in a large MRO file?

Start with the SKUs that appear most frequently across invoices, since a small pricing error on a high-frequency item compounds faster than a large error on a one-time purchase. Then test every line carrying a minimum order fee, every line with a substituted SKU, and every vending or VMI replenishment above a materiality threshold you set before starting. This order finds compounding errors before isolated ones.

An MRO file can run to thousands of lines a year, and testing every line is not realistic within a fixed-scope engagement. The lines worth testing first are the ones where an error repeats, not where a single error is largest.

A recurring SKU billed $0.40 over its contracted price 500 times a year produces more leakage than a single one-off order billed $150 over price. Ranking by frequency and unit-price variance, rather than by invoice size, surfaces that pattern.

After frequency, test every fee line and every flagged substitution, since both categories were identified above as having no independent control checking them. Vending reconciliation comes last only because it requires a physical count to execute, not because it matters less.

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.

7. Frequently Asked Questions (People Also Ask)

Does three-way matching catch MRO pricing errors?

Three-way matching confirms the invoice total agrees with the purchase order and the received quantity. It does not compare the SKU on the invoice to the SKU quoted in the pricing agreement, so a substituted part billed at a different price can still pass the match.

What is a small-order or minimum order fee?

It is a fee an MRO vendor charges when an order falls below a dollar or unit threshold stated in the contract, meant to recover the fixed cost of processing a small transaction. It should apply once per order, calculated against the current contract's threshold.

Why does vending equipment create an audit gap?

Vending and VMI programs remove the purchase order step and generate invoices from the vendor's own dispense data. Without a periodic physical bin count to compare against that data, there is no independent figure to check the billed quantity against.

How often should a catalog price list be checked against contract terms?

The check should happen whenever the vendor issues a new catalog version, since that is when a price change take effect. Confirming the invoice date falls within the currently authorized catalog version, rather than checking annually, catches an unauthorized change closer to when it starts.

Can a rebate be owed on MRO spend even if no one requested it?

Yes, where the contract sets a volume tier or rebate schedule. The credit is typically owed automatically once a purchase threshold is met within the period, but it requires someone to recalculate actual spend against the schedule since most vendors do not apply it without a claim.

Is MRO spend worth auditing given the low dollar value per line?

The value is in the repetition, not the line size. A pricing error on a frequently ordered SKU or a duplicated minimum order fee compounds across hundreds of invoices a year, which is a different question from whether any single invoice is large.

What documentation should a vendor provide to support a catalog price increase?

The vendor should be able to provide the catalog version number, its effective date, and the contract clause authorizing that adjustment cycle. An increase without a stated effective date tied to the contract terms cannot be verified against the agreement.

Does this audit require legal review of the MRO contract?

Testing invoice mechanics against stated contract terms does not require legal interpretation in most cases. Where a contract clause is ambiguous about effective dates or fee calculation, that is a legal question, and this is general information, not legal advice.