How do you set up tolerance thresholds in Epicor Kinetic?

Executive Summary

Epicor Kinetic's tolerance setup lives in two places: company-level defaults under Company Configuration and, above them, tolerance percentages or amounts set per supplier or per part class. Both control how far an invoice's unit price and quantity can deviate from the receiving PO line before Kinetic holds the invoice for review instead of posting it.

That control answers one question: does this invoice match this PO? It cannot answer whether the PO itself was cut at the contracted rate, whether a volume tier discount applied, or whether a surcharge on the invoice has a contract basis at all. Three-way matching in Kinetic checks invoice against PO and receipt.

It does not read the underlying contract document, because the contract usually is not a structured object inside Kinetic.

The practical setup path below gets tolerance fields configured correctly. The section after it names exactly where that configuration stops being useful, so the reader is not left assuming PO tolerance is a substitute for contract compliance.

1. Where do you configure tolerance thresholds in Epicor Kinetic?

Tolerance thresholds sit in two layers in Epicor Kinetic. Company-level defaults are set in Company Configuration under the Modules > All Modules > Purchasing tab, as a percentage or fixed amount applied to unit price and quantity. Supplier-specific or part-class overrides are set on the Supplier or Part Class record and take precedence over the company default when an invoice is matched to its receiving PO.

Both layers feed the same three-way match check at invoice entry.

Start at the company level. The default tolerance percentage applies to every PO unless a more specific record overrides it. Most Kinetic implementations set separate price and quantity tolerance fields, because a quantity variance and a price variance usually need different review paths.

Supplier-level overrides matter for vendors with volatile pricing, freight carriers with fuel surcharges being the clearest case, where a company-wide tolerance is either too loose for stable vendors or too tight for ones with legitimate variance.

Part class overrides matter less for indirect spend categories and more for stocked materials, since indirect vendor invoices (freight, contract labor, maintenance) frequently do not carry a part number at all.

A. Company-level default

Set once, applies everywhere a more specific rule does not exist. This is the fallback, not the control most AP teams actually rely on day to day.

B. Supplier-level override

Set per vendor, useful where price volatility differs meaningfully by supplier. This is where a freight carrier's fuel surcharge tolerance would live, separate from a stable MRO vendor's tolerance.

2. What does the tolerance check actually compare?

The tolerance check compares the invoice line to the receiving PO line, not to a contract, rate card, or rebate schedule. If the PO was cut correctly and the invoice matches the PO within the configured percentage or dollar threshold, the invoice posts. Kinetic has no field that stores a vendor's contracted rate independent of the PO, so there is nothing in the match logic that can flag an invoice matching a PO that was itself priced wrong.

This is a structural fact about three-way matching, in Kinetic or any ERP built the same way. The match has three legs: purchase order, receipt, and invoice. Each leg confirms the next agrees with the one before it.

A rate card sits outside all three legs. If the PO for a maintenance service call was entered at last year's hourly rate because nobody updated the buyer's reference sheet, the PO, the receipt, and the invoice can all agree with each other and still be wrong against the actual contract.

Tolerance thresholds catch the case where someone typed the invoice differently from the PO. They do not catch the case where the PO was typed correctly against outdated information.

3. Which invoice types slip past PO tolerance entirely?

Service invoices tied to a blanket PO, a not-to-exceed cap, or a recurring contract often bypass line-level tolerance matching altogether, because the PO carries a dollar ceiling rather than a unit price and quantity to match against. Freight invoices priced by accessorial and surcharge line items frequently arrive with no PO at all. Both categories post through AP with the tolerance check either not applicable or not engaged.

A not-to-exceed PO authorizes spend up to a ceiling. Kinetic's match logic confirms the invoice total stays under that ceiling. It does not confirm the labor rate, the materials markup, or the individual line items inside that ceiling reflect the contract terms behind the NTE cap.

Freight is a distinct case. Many freight invoices post through AP without ever generating a PO, since freight is typically requisitioned by shipment rather than by purchase order. Tolerance thresholds require a PO to compare against; an invoice with no PO has nothing to be checked against.

4. How should tolerance settings differ by vendor category?

Tolerance settings should be tightened for categories where a PO line maps cleanly to a contracted rate, such as stocked MRO parts with a published price list, and treated as a secondary control for categories where the PO itself is a poor proxy for the contract, such as freight, contract labor, and calibration services billed against master agreements rather than line-item POs.

Setting one tolerance percentage across every vendor category treats a stocked-parts PO and a freight accessorial invoice as the same kind of document. They are not. The parts PO has a real unit price to compare against. The freight invoice usually does not have a PO line with a comparable unit price at all.

Tightening tolerance on categories where the PO is a genuine proxy for the contract, and treating PO tolerance as a secondary control everywhere else, keeps the review workload pointed at variances that are actually informative.

• Stocked MRO and parts: PO price should mirror the price list closely, so a tight tolerance is a meaningful signal rather than noise.
• Freight and 3PL: Accessorials and surcharges rarely map to a PO line at all, so tolerance thresholds are not the control that matters here.
• Contract labor and staffing: Rate schedules and NTE overruns live in the staffing agreement, not the PO, so tolerance checks the wrong reference point.
• Calibration and safety compliance: Recurring service agreements are often billed against a blanket PO, so a unit-price tolerance rarely applies line by line.

5. What closes the gap tolerance thresholds leave open?

Closing the gap requires checking the invoice against the underlying contract document itself, the rate card, the volume tier schedule, the NTE cap and its scope, rather than against the PO Kinetic generated from someone's reading of that contract. That check happens either manually against the contract file or through a control built specifically to hold contract terms as structured data separate from the PO.

The contract document, whether a rate card, a master service agreement, or a carrier tariff, typically exists as a PDF outside Kinetic. Kinetic's tolerance fields have nothing to read that document against, so the check has to happen somewhere else in the process.

A retrospective audit of historical AP data can identify where POs were cut against outdated rates, where rebate clauses went unclaimed, and where surcharges persisted past their contract expiration condition. A forward control does the same comparison at the point of invoice receipt, going forward.

Either approach starts from the same requirement: someone has to convert the contract's rate card, volume tiers, and NTE scope into a structured reference Kinetic's tolerance logic was never built to hold.

6. Should you tighten tolerance or fix the underlying contract data first?

Tighten tolerance only after the reference data it checks against is accurate, because a tight tolerance against a stale PO price simply rejects invoices that are correctly billed at the current rate. Fixing the PO's underlying rate reference comes first. Tolerance is a threshold around a number; if the number itself is wrong, a tighter threshold produces more false holds, not more accurate ones.

A buyer's rate sheet that has not been updated in a year will keep generating POs priced to that stale sheet. Tightening the tolerance percentage around that PO increases the number of correctly-priced invoices flagged as variances, since they now diverge further from an already-wrong reference.

This is a sequencing question, not a settings question. Confirm the PO reference data reflects the current contract terms first, category by category, before adjusting how tightly Kinetic checks invoices against it. A diagnostic pass through recent invoices against actual contract documents, ahead of any tolerance change, shows which categories have stale PO pricing and which do not.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and what is margin erosion? causes and prevention for manufacturers.

7. Frequently Asked Questions (People Also Ask)

Does Epicor Kinetic support tolerance by percentage and by fixed dollar amount?

Yes. Kinetic's tolerance fields can be configured as a percentage of unit price, a fixed dollar amount, or both, at the company level and at the supplier or part class level. Most implementations use percentage tolerance for high-value lines and a fixed-amount floor for low-value lines, so small-dollar rounding differences do not generate holds.

Can tolerance thresholds be set differently for price versus quantity variance?

Yes. Kinetic separates price tolerance from quantity tolerance as distinct fields, so a shipment that arrives short can be held under a different threshold than an invoice priced above the PO. Setting both fields deliberately, rather than leaving one at a system default, is part of a correct setup.

Why does an invoice that matches its PO still turn out to be wrong?

Because the PO itself can be cut at the wrong rate. Kinetic's three-way match confirms the invoice agrees with the PO and receipt. It has no mechanism for confirming the PO was priced against the current contract, rate card, or volume tier, since that document usually is not structured data inside Kinetic.

Do freight invoices go through PO tolerance matching in Kinetic?

Often not. Freight is commonly requisitioned and invoiced without a purchase order, since shipments are billed by carrier tariff and accessorial schedule rather than by PO line. Where no PO exists, there is nothing for the tolerance check to compare the invoice against.

What is the difference between PO tolerance and contract compliance?

PO tolerance checks whether an invoice matches the purchase order it was cut against. Contract compliance checks whether the purchase order, and the invoice, match the actual rate card, volume tier, rebate clause, or NTE cap in the vendor contract. Kinetic's native tolerance fields perform the first check, not the second.

Should tolerance thresholds be tightened to catch more contract drift?

Tightening a threshold makes the match stricter against the existing PO reference; it does not make the PO reference more accurate. If the PO price is stale, a tighter tolerance increases false holds on correctly priced invoices rather than catching more drift. Fixing the reference data comes first.

Where do NTE caps fit into Kinetic's tolerance setup?

An NTE cap authorizes total spend up to a ceiling on a blanket or service PO. Kinetic's match confirms the invoice total stays under that ceiling. It does not check whether the line items inside the ceiling, labor rate, materials markup, or hours billed, reflect the contract terms behind the cap.

Is a diagnostic review still useful if Kinetic's tolerance fields are already tight?

Yes, because tight tolerance and correct pricing are different things. A diagnostic checks historical invoices against the actual contract documents, independent of how the PO was priced, and finds drift that tolerance settings were never built to detect, regardless of how tightly they are configured.

Can Kinetic hold rate cards or volume tier schedules as structured data?

Not natively as a contract object separate from the PO. Rate cards and volume tier schedules typically live as PDFs or spreadsheets outside Kinetic. Building that data into a structured reference for ongoing checking requires either a manual process or a control designed specifically to hold contract terms apart from the PO.