MRO and Class C Controls in Epicor Kinetic

Executive Summary

Epicor Kinetic's three-way match ties an MRO invoice to its purchase order and its receipt in Receipt Entry, and it will hold a voucher when quantity or unit cost falls outside the tolerance set on the PO line. That control is real and it catches the invoices that disagree with what was ordered and received.

It does not catch the invoices that agree with a stale PO line. If the vendor's price list changed and nobody updated the part's unit cost or the open blanket PO, the match clears clean because Kinetic is comparing the invoice to its own outdated reference, not to the contract. Minimum order charges, freight-on-small-order fees, and off-catalog surcharges on Class C items also sit outside the match because they are not modeled as PO lines at all.

The fix is not a bigger tolerance band. It is a periodic check of the part cost table and the vendor's actual current price list against what the PO assumes, done on a cycle the AP team's daily match never runs.

1. What does Epicor Kinetic actually match on an MRO invoice?

Kinetic's AP invoice entry links each invoice line to a purchase order line and a receipt record from Receipt Entry, comparing quantity received against quantity invoiced and the PO's unit cost against the invoice's unit cost. A variance beyond the tolerance percentage set on the PO line or the part class puts the voucher on hold for review rather than posting it automatically. This is the three-way match: PO, receipt, invoice.

It is Kinetic's core AP control and it runs.

For MRO and Class C consumables, this means a fastener, gasket, or safety-supply invoice that carries a different unit cost than the PO line will not post silently. The hold queue is where a controller finds the invoice that priced a box of bolts higher than the PO said, or shorted the quantity received against what was billed.

The match is line-level, which matters for MRO because these purchase orders often carry many low-value lines in a single release. Kinetic evaluates each line independently rather than netting a total invoice amount against a total PO amount, so a single mispriced line among forty does not get buried in an average.

The control depends entirely on the PO line being right in the first place. Kinetic checks the invoice against the PO, not the invoice against the vendor's actual current contract terms, which live outside the system in a price agreement or a signed rate sheet.

• Quantity match: Invoiced quantity is checked against the quantity recorded in Receipt Entry for that PO line.
• Unit cost match: Invoiced unit cost is checked against the PO line's unit cost, within a set tolerance percentage.
• Line-level hold: A variance on one line holds that voucher for review; it does not average across the PO.

2. Why does a stale part cost record clear the match anyway?

The three-way match compares an invoice to the PO, and the PO's unit cost usually comes from the part's cost record at the time the PO was cut. If a vendor's price list moved and nobody updated that cost record or the open blanket PO release, every invoice at the new, higher price matches the old PO cleanly. The match was never built to check the PO's assumption against the vendor's current published price; it only checks the invoice against.

This is the mechanism, not a flaw in the software. Kinetic's job in AP is document matching, and a document that has gone stale is still a document. The system has no independent source for what the vendor should be charging today; it trusts the PO line because that line was presumably correct when someone entered it.

MRO consumables are exposed to this more than most categories because blanket POs for fasteners, safety supplies, and shop consumables are often cut once and released against for months. Producer input costs for general purpose machinery and equipment moved up 5.6% year over year through July 2026, per the US Bureau of Labor Statistics PPI series WPU114 (read 2026-09-06). A PO cost record entered before that move and never refreshed will pass every subsequent invoice at the old, lower price it expects, even as the vendor bills the new one.

Catching this requires comparing the part cost table itself against the vendor's current price agreement on a schedule, not waiting for a match exception that will never fire.

3. Can Kinetic catch a minimum order fee or small-order surcharge?

Not as a line the three-way match evaluates against contract terms. A minimum order charge or small-order freight surcharge on a Class C consumables invoice typically appears as its own invoice line with no corresponding PO line, so Kinetic either routes it to a miscellaneous charge code for manual approval or rejects the match outright because there is nothing to match it against. Either way, whether the fee was actually earned under the vendor agreement is a judgment the system.

Class C consumables purchasing generates these fees more than higher-value categories because order sizes are small and frequent. A vendor agreement might waive the minimum order charge above a stated order value, or cap the small-order surcharge at a set number of occurrences per year. None of that logic lives in a PO line.

When Kinetic cannot match a charge to a PO line, the invoice typically routes for manual coding rather than posting automatically, which means a person decides whether to approve it. That person is looking at an invoice, not the underlying contract clause, unless someone hands them both.

This is not a gap Kinetic hides. It is a gap in what a PO-based match was designed to check in the first place: quantity and price against an order, not a fee against a waiver clause.

4. Does Kinetic enforce volume tier pricing on consumables?

Kinetic supports price break structures on purchase contracts, where unit cost can step down as ordered quantity crosses a threshold defined on that contract. Where that structure is configured and the contract is loaded correctly, Kinetic will apply the corresponding break. Where the tier is defined by cumulative annual volume across many small releases rather than a single order quantity, the system has no native mechanism to track spend against that rolling threshold and trigger the price change.

This distinction matters for MRO because most volume commitments on fasteners, shop supplies, and safety equipment are annual or quarterly aggregates, not single-order thresholds. A vendor agreement promising a lower unit cost after $50,000 in cumulative purchases is a contract clause, not a PO field.

Kinetic's price break functionality works well for the case it was built for: an order large enough on its own to cross a quantity threshold. It was not built to watch a running total across releases spread over a blanket PO's life and flag the point where the next invoice should reprice.

A company relying on the tier taking effect automatically is relying on someone remembering to check cumulative volume and update the contract record manually, which is a process control, not a system one.

A. Single-order price breaks

Configured on the purchase contract against a specific quantity ordered in one PO line, these apply automatically when Kinetic evaluates the order at entry. This is the scenario Kinetic handles well.

B. Cumulative volume tiers

Defined against total purchases across a period rather than one order, these require someone to track spend outside the PO line and manually update pricing once the threshold is crossed. Kinetic has no native trigger for this.

5. What should an AP team check that the system won't?

Three things sit entirely outside Kinetic's match logic: whether the part cost table still reflects the vendor's current price agreement, whether minimum order and small-order fees on recent invoices were actually earned under the contract's waiver terms, and whether cumulative volume has crossed a tier threshold the PO never tracked. None of these produce a system exception, because none of them are conditions Kinetic was built to test. They surface only through a periodic comparison against the contract itself.

The practical approach is a quarterly pull of the part cost table for MRO and Class C categories, checked line by line against the vendor's current published price list or signed rate agreement. Where the vendor's list moved and the cost record did not, every invoice since the price change is worth a second look.

The same pull should flag any invoice carrying a fee code, minimum order or small-order surcharge, and route those specifically for a contract check rather than a routine approval. And any blanket PO active for more than a quarter is worth a cumulative-volume check against its contract's tier schedule.

None of this needs new software. It needs someone treating the contract, not the PO, as the reference document, on a schedule the daily match will never run on its own.

6. When does this gap justify a dedicated audit instead of a manual check?

A manual quarterly check works when MRO and Class C spend is small enough for one person to compare a short vendor list against the part cost table by hand. It stops working once the vendor count, the blanket PO count, or the SKU count grows past what a spreadsheet review can reasonably cover in the time available, which is exactly when the dollar exposure from a missed price change or an unearned fee also grows.

The math is simple and worth doing before deciding which approach fits. Take the annual MRO and Class C consumables spend running through blanket POs, multiply by the share of vendors whose price agreements have changed since the PO's cost records were last checked, and that product is the exposure a stale part cost table can carry silently.

Where that number is small, a disciplined quarterly review by the AP team is proportionate and sufficient. Where the SKU count and vendor count have grown to the point that a manual review cannot realistically cover the full contract set each quarter, a structured audit that reconciles every open PO's cost basis against the current contract is the more reliable option, precisely because it does not depend on someone remembering to run the check.

• Vendor count: More MRO vendors means more price agreements to track against the part cost table, and less time per vendor in a manual review.
• Blanket PO age: A blanket PO open for a year has had a year of opportunity for its cost basis to drift from the current contract.
• SKU density: Class C categories carry many low-value SKUs per PO, which is exactly the pattern a line-level manual review is slowest at covering.

For the wider pattern this sits inside, start with the margin drift guide.

7. Frequently Asked Questions (People Also Ask)

Does Epicor Kinetic automatically update part costs when a vendor's price list changes?

No. Kinetic's part cost record updates when someone enters a new cost, typically from a new PO or a manual change. It does not monitor a vendor's published price list or contract for changes and will keep matching invoices against the old cost until the record is corrected.

What happens when an MRO invoice fails the three-way match in Kinetic?

The voucher is placed on hold rather than posted. It sits in an exception queue until someone reviews the quantity or cost variance and either corrects the PO or receipt, or approves the variance manually.

Can Kinetic track cumulative volume across multiple releases on a blanket PO?

Kinetic tracks quantities released and received against a blanket PO, but it does not natively evaluate that cumulative total against a contract's volume tier threshold to trigger a price change. That comparison has to be done separately against the contract.

Are minimum order fees and small-order surcharges matched against the contract in Kinetic?

Not automatically. These charges usually have no corresponding PO line, so they route to manual coding or approval. Whether the fee was actually owed under the vendor's waiver terms is a manual judgment, not a system check.

Is this gap specific to Epicor Kinetic, or does it apply to other ERPs?

The mechanism is common to PO-based three-way matching generally: the match checks the invoice against the PO, not against the underlying contract. Kinetic's specific tolerance and hold behavior differs by ERP, but the blind spot around stale cost records and untracked fees applies broadly.

How often should we check part cost records against vendor price agreements?

A quarterly check is a reasonable starting cadence for MRO and Class C categories, since blanket POs in this category often stay open for months without a new PO event that would refresh the cost record.

Does a tighter cost tolerance setting in Kinetic fix the stale price issue?

No. Tolerance settings only govern how much variance between the invoice and the existing PO cost triggers a hold. If the PO cost itself is wrong, a tight tolerance just holds more invoices at the wrong reference point rather than correcting it.

What data does an AP team need to check MRO pricing against contracts?

The current part cost table for MRO and Class C parts, the vendor's current signed price agreement or rate sheet, and a list of open blanket POs with their last cost-update date. Comparing these three directly answers whether the PO basis is still current.