# Setting tolerance thresholds in Global Shop Solutions

> How to configure quantity and price tolerance thresholds in Global Shop Solutions, and what those thresholds can and cannot catch on a service vendor invoice.

Source: https://valuexpa.com/insights/how-do-you-set-up-tolerance-thresholds-in-global-shop
Publisher: ValueXPA (https://valuexpa.com)
Updated: 2026-10-22

---

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. Global Shop Solutions gives AP a tolerance threshold to catch part of that gap automatically, before a line item ever reaches a human reviewer.

A tolerance threshold is a percentage or dollar band around the purchase order price and quantity. Set it too loose and overbilling slides through. Set it too tight and every invoice stalls in a match exception queue.

## Executive Summary

Tolerance thresholds in Global Shop Solutions sit on the three-way match between purchase order, receipt and invoice. They compare a submitted invoice price and quantity against the PO within a configured band, and route anything outside that band to a hold or exception queue for manual review.

That comparison is useful and narrow. It tests whether the invoice matches the PO it was cut against. It does not test whether the PO itself was cut at the right rate, whether a surcharge on the invoice was ever in the contract, or whether a volume tier should have dropped the unit price weeks ago. Those checks live in the contract, not in the PO, and Global Shop Solutions has no field that reads a contract.

The result: a company can run tight, well-tuned tolerance thresholds and still pay a stale rate for a year, because the PO was wrong at creation and every invoice matched it perfectly.

## 1. What are tolerance thresholds in Global Shop Solutions?

**A tolerance threshold in Global Shop Solutions is a configured percentage or dollar variance allowed between a purchase order line and the matching invoice line, on both price and quantity. An invoice inside the band posts automatically. An invoice outside it routes to a match exception for manual release. The threshold governs one comparison only: invoice against PO. It says nothing about whether the PO price was correct when the buyer entered it, which is a separate question the system.**

Global Shop Solutions applies tolerance at the line level during three-way matching, checking the invoice against the purchase order and the goods or service receipt. The setting typically allows a percentage variance on unit price and a percentage or unit variance on quantity, configured per vendor class or globally depending on how the instance is set up.

The threshold is a gate, not a judgment. It does not know why a price moved. A carrier increase, a data entry error and a genuine overcharge all look identical to the match engine if they fall inside the same band. The system releases all three.

## 2. Where do you configure tolerance settings in Global Shop Solutions?

**Tolerance settings live in the purchasing and accounts payable configuration modules, usually set at a company-wide default with the option to override by vendor or vendor class. An administrator with purchasing configuration access sets the price and quantity variance percentages, then tests them against a sample of recent invoices before rolling the change to production, because a change here affects every invoice processed after it, not just new purchase orders.**

Most Global Shop Solutions instances start with a single default tolerance applied across all vendors, set at implementation and rarely revisited. That default is a blunt instrument: a freight carrier with volatile fuel surcharges and a fixed-price maintenance contractor do not belong under the same variance band.

Vendor-class overrides let AP tighten the band for categories where price should be stable, such as calibration contracts with a fixed annual rate, and loosen it for categories with legitimate, contract-defined variability, such as indexed freight lanes. That split is a configuration decision, not a system default, and it requires someone to have already mapped which vendors belong in which class.

## 3. What should a tolerance threshold actually test?

**A tolerance threshold should test whether the invoice matches the purchase order it references, within a band narrow enough to catch entry errors and duplicate submissions but wide enough not to stall legitimate variance. It is a control against clerical and processing error at the invoice stage. It is not a control against a purchase order that was cut at the wrong price to begin with, because the threshold has no reference point other than the PO itself.**

The PO is the threshold's only anchor. If the PO price is correct, a tight tolerance catches real problems: a keying error, a vendor resubmitting an invoice at a different price, a quantity that does not match what was received.

If the PO price is wrong, a tight tolerance enforces the error consistently. Every invoice that matches the wrong PO price passes clean, and the tighter the band, the more confidently AP trusts a number that was never checked against the contract in the first place.

## 4. How tight should a quantity and price tolerance be set?

**There is no fixed correct setting. The right band depends on how much legitimate price and quantity variance a vendor category carries under its own contract terms, which is a fact about the contract, not about Global Shop Solutions. A category with fixed, contracted pricing supports a near-zero tolerance. A category with indexed or usage-based pricing needs a wider band or it will generate exception volume on invoices that are actually correct.**

Setting the band correctly means reading the contract first: does the rate card allow a fuel surcharge to move, does a rebate clause change the effective price at a volume threshold, is there a minimum or maximum charge built in. None of that lives in Global Shop Solutions.

A tolerance set without that read either lets contract-violating variance through under a wide band, or drowns AP in exceptions on ordinary contract-permitted variance under a narrow one. Neither failure mode is visible in the system itself; both look like normal exception queue activity.

## 5. What does Global Shop Solutions miss even with tolerances configured?

**Global Shop Solutions matches an invoice to a purchase order and a receipt. It does not read the underlying vendor contract, so it cannot test whether a surcharge should have expired, whether a volume tier should have dropped the unit rate, or whether a rebate was ever applied. Those terms typically live in a PDF outside the ERP entirely, and a tight tolerance threshold enforces the PO faithfully whether or not the PO reflects the current contract.**

Three-way matching checks the invoice against the PO and receipt. It does not test a surcharge's expiration condition, a rebate clause's trigger, or a not-to-exceed cap written into the master service agreement. Those are contract facts, and the PO was only ever a snapshot of the contract at the moment someone entered it.

When a contract term changes, freight fuel surcharge language, a labor rate step-down at a renewal date, a volume rebate threshold, nothing in Global Shop Solutions updates the PO automatically. The invoice keeps matching the old number inside tolerance, and the gate stays quiet.

## 6. How do tolerance thresholds interact with contract terms outside the ERP?

**A tolerance threshold and a contract term operate at different layers and do not talk to each other. The threshold enforces agreement between invoice and PO. The contract defines what the PO should have said. Where the two diverge, the ERP has no mechanism to notice, because it was never given the contract to compare against. Closing that gap requires reading the contract against the invoice directly, a step outside three-way matching.**

Some companies try to close the gap by tightening tolerance further, on the theory that a narrower band forces more manual review and more review catches more problems. It catches more PO mismatches. It does not catch a PO that was correctly matched against a contract term that is itself out of date.

Others try to widen the PO update cycle instead, refreshing POs against renegotiated contracts on a set schedule. That helps, but it depends on someone tracking every rate card, rebate clause and surcharge schedule change across every vendor, which is the same work a contract compliance review does directly against the invoice.

## 7. What happens when an invoice fails a tolerance check?

**An invoice that falls outside the configured tolerance band routes to a match exception queue for manual review rather than posting automatically. Someone on the AP team then decides whether to approve the variance, request a corrected invoice, or escalate to purchasing. That decision quality depends entirely on whether the reviewer has the contract in front of them, since the exception queue itself shows only the PO-to-invoice gap, not the contract-to-invoice gap.**

A reviewer working the exception queue without the underlying contract is deciding blind on the question that matters most: is the invoice price correct, or is the PO price correct. Most exception review in practice compares invoice to PO a second time and approves if the vendor confirms the number, because the PO is the only reference document readily available.

That closes the exception without closing the drift, if the PO itself was wrong. The invoice gets approved a second time against the same outdated reference.

## 8. Should you tighten thresholds or add a contract review layer?

**Tighten thresholds when the problem is clerical error and duplicate submission, since that is what the match engine is built to catch. Add a contract review layer when the problem is a stale rate card, an expired surcharge, or an unclaimed rebate, since none of those show up as a PO mismatch. The two are not substitutes. A company usually needs the first to run cleanly and the second to catch what the first structurally cannot see.**

The decision rule is diagnostic, not preferential: pull a sample of paid invoices and check them against the actual vendor contracts, not the POs. Where the PO and contract agree, tolerance tuning is the right lever. Where they diverge, no tolerance setting fixes it, because the threshold was built to protect PO integrity, not contract compliance.

A one-time read of contracts against paid history answers which problem a given company actually has before any configuration change is made.

For the wider pattern this sits inside, start with the [margin drift](/insights/best-invoice-validation-software-smb) guide. See also [the six categories drift hides in](/insights/indirect-spend-audit-categories) and [what is margin erosion? causes and prevention for manufacturers](/insights/what-is-margin-erosion-causes-and-prevention-for).

## 9. Frequently Asked Questions (People Also Ask)

### Does Global Shop Solutions check invoices against the vendor contract automatically?

No. Global Shop Solutions performs three-way matching between the invoice, the purchase order and the receipt. It has no field or module that reads the underlying vendor contract, so a rate card, rebate clause or surcharge schedule is never part of the automated comparison.

### What is the difference between a tolerance threshold and a contract compliance check?

A tolerance threshold compares an invoice to its purchase order within a set variance band. A contract compliance check compares an invoice directly to the contract terms: rate card, volume tier, NTE cap, rebate clause. They test different reference documents and a pass on one says nothing about the other.

### Can a tighter tolerance threshold catch a stale rate card?

No. A stale rate card means the purchase order itself carries the wrong price. A tolerance threshold, however tight, only checks whether the invoice matches that PO. If the PO is wrong, a tight threshold enforces the wrong number consistently rather than catching it.

### Should tolerance thresholds be the same for every vendor category?

Not if the categories carry different legitimate variance under their contracts. A fixed-price maintenance contract supports a narrow band. An indexed freight lane with fuel surcharges needs a wider one, or correct invoices will generate exception volume that adds no value.

### Who should own the tolerance threshold configuration in Global Shop Solutions?

Purchasing or AP configuration access is required to change the setting, but the decision of where to set the band should follow a read of the actual contract terms by category, not a system default left over from implementation.

### Does a match exception in Global Shop Solutions mean the invoice is wrong?

It means the invoice does not match the purchase order within the configured band. That could be a genuine overcharge, a data entry error, or a correct invoice against an outdated PO. The exception itself does not distinguish between these causes.

### How often should tolerance thresholds be reviewed?

There is no fixed schedule in the registry to cite here. The practical trigger is a contract renewal, a rate change, or a shift in exception queue volume, any of which signals the band no longer matches the vendor category's actual variance.

### Is a tolerance threshold enough control on its own for service vendor spend?

It controls one failure mode: invoice-to-PO mismatch. It does not control a PO cut at the wrong contract price, an expired surcharge still being billed, or an unclaimed rebate, because none of those produce a PO mismatch for the threshold to catch.

### Is contract complexity quietly draining your operating margin?

A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit.

**[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)**

## Executive Summary

Tolerance thresholds in Global Shop Solutions sit on the three-way match between purchase order, receipt and invoice. They compare a submitted invoice price and quantity against the PO within a configured band, and route anything outside that band to a hold or exception queue for manual review. That comparison is useful and narrow. It tests whether the invoice matches the PO it was cut against. It does not test whether the PO itself was cut at the right rate, whether a surcharge on the invoice was ever in the contract, or whether a volume tier should have dropped the unit price weeks ago. Those checks live in the contract, not in the PO, and Global Shop Solutions has no field that reads a contract. The result: a company can run tight, well-tuned tolerance thresholds and still pay a stale rate for a year, because the PO was wrong at creation and every invoice matched it perfectly.

## 1. What are tolerance thresholds in Global Shop Solutions?

A tolerance threshold in Global Shop Solutions is a configured percentage or dollar variance allowed between a purchase order line and the matching invoice line, on both price and quantity. An invoice inside the band posts automatically. An invoice outside it routes to a match exception for manual release. The threshold governs one comparison only: invoice against PO. It says nothing about whether the PO price was correct when the buyer entered it, which is a separate question the system. Global Shop Solutions applies tolerance at the line level during three-way matching, checking the invoice against the purchase order and the goods or service receipt. The setting typically allows a percentage variance on unit price and a percentage or unit variance on quantity, configured per vendor class or globally depending on how the instance is set up. The threshold is a gate, not a judgment. It does not know why a price moved. A carrier increase, a data entry error and a genuine overcharge all look identical to the match engine if they fall inside the same band. The system releases all three.

## 2. Where do you configure tolerance settings in Global Shop Solutions?

Tolerance settings live in the purchasing and accounts payable configuration modules, usually set at a company-wide default with the option to override by vendor or vendor class. An administrator with purchasing configuration access sets the price and quantity variance percentages, then tests them against a sample of recent invoices before rolling the change to production, because a change here affects every invoice processed after it, not just new purchase orders. Most Global Shop Solutions instances start with a single default tolerance applied across all vendors, set at implementation and rarely revisited. That default is a blunt instrument: a freight carrier with volatile fuel surcharges and a fixed-price maintenance contractor do not belong under the same variance band. Vendor-class overrides let AP tighten the band for categories where price should be stable, such as calibration contracts with a fixed annual rate, and loosen it for categories with legitimate, contract-defined variability, such as indexed freight lanes. That split is a configuration decision, not a system default, and it requires someone to have already mapped which vendors belong in which class.

## 3. What should a tolerance threshold actually test?

A tolerance threshold should test whether the invoice matches the purchase order it references, within a band narrow enough to catch entry errors and duplicate submissions but wide enough not to stall legitimate variance. It is a control against clerical and processing error at the invoice stage. It is not a control against a purchase order that was cut at the wrong price to begin with, because the threshold has no reference point other than the PO itself. The PO is the threshold's only anchor. If the PO price is correct, a tight tolerance catches real problems: a keying error, a vendor resubmitting an invoice at a different price, a quantity that does not match what was received. If the PO price is wrong, a tight tolerance enforces the error consistently. Every invoice that matches the wrong PO price passes clean, and the tighter the band, the more confidently AP trusts a number that was never checked against the contract in the first place.

## 4. How tight should a quantity and price tolerance be set?

There is no fixed correct setting. The right band depends on how much legitimate price and quantity variance a vendor category carries under its own contract terms, which is a fact about the contract, not about Global Shop Solutions. A category with fixed, contracted pricing supports a near-zero tolerance. A category with indexed or usage-based pricing needs a wider band or it will generate exception volume on invoices that are actually correct. Setting the band correctly means reading the contract first: does the rate card allow a fuel surcharge to move, does a rebate clause change the effective price at a volume threshold, is there a minimum or maximum charge built in. None of that lives in Global Shop Solutions. A tolerance set without that read either lets contract-violating variance through under a wide band, or drowns AP in exceptions on ordinary contract-permitted variance under a narrow one. Neither failure mode is visible in the system itself; both look like normal exception queue activity.

## 5. What does Global Shop Solutions miss even with tolerances configured?

Global Shop Solutions matches an invoice to a purchase order and a receipt. It does not read the underlying vendor contract, so it cannot test whether a surcharge should have expired, whether a volume tier should have dropped the unit rate, or whether a rebate was ever applied. Those terms typically live in a PDF outside the ERP entirely, and a tight tolerance threshold enforces the PO faithfully whether or not the PO reflects the current contract. Three-way matching checks the invoice against the PO and receipt. It does not test a surcharge's expiration condition, a rebate clause's trigger, or a not-to-exceed cap written into the master service agreement. Those are contract facts, and the PO was only ever a snapshot of the contract at the moment someone entered it. When a contract term changes, freight fuel surcharge language, a labor rate step-down at a renewal date, a volume rebate threshold, nothing in Global Shop Solutions updates the PO automatically. The invoice keeps matching the old number inside tolerance, and the gate stays quiet.

## 6. How do tolerance thresholds interact with contract terms outside the ERP?

A tolerance threshold and a contract term operate at different layers and do not talk to each other. The threshold enforces agreement between invoice and PO. The contract defines what the PO should have said. Where the two diverge, the ERP has no mechanism to notice, because it was never given the contract to compare against. Closing that gap requires reading the contract against the invoice directly, a step outside three-way matching. Some companies try to close the gap by tightening tolerance further, on the theory that a narrower band forces more manual review and more review catches more problems. It catches more PO mismatches. It does not catch a PO that was correctly matched against a contract term that is itself out of date. Others try to widen the PO update cycle instead, refreshing POs against renegotiated contracts on a set schedule. That helps, but it depends on someone tracking every rate card, rebate clause and surcharge schedule change across every vendor, which is the same work a contract compliance review does directly against the invoice.

## 7. What happens when an invoice fails a tolerance check?

An invoice that falls outside the configured tolerance band routes to a match exception queue for manual review rather than posting automatically. Someone on the AP team then decides whether to approve the variance, request a corrected invoice, or escalate to purchasing. That decision quality depends entirely on whether the reviewer has the contract in front of them, since the exception queue itself shows only the PO-to-invoice gap, not the contract-to-invoice gap. A reviewer working the exception queue without the underlying contract is deciding blind on the question that matters most: is the invoice price correct, or is the PO price correct. Most exception review in practice compares invoice to PO a second time and approves if the vendor confirms the number, because the PO is the only reference document readily available. That closes the exception without closing the drift, if the PO itself was wrong. The invoice gets approved a second time against the same outdated reference.

## 8. Should you tighten thresholds or add a contract review layer?

Tighten thresholds when the problem is clerical error and duplicate submission, since that is what the match engine is built to catch. Add a contract review layer when the problem is a stale rate card, an expired surcharge, or an unclaimed rebate, since none of those show up as a PO mismatch. The two are not substitutes. A company usually needs the first to run cleanly and the second to catch what the first structurally cannot see. The decision rule is diagnostic, not preferential: pull a sample of paid invoices and check them against the actual vendor contracts, not the POs. Where the PO and contract agree, tolerance tuning is the right lever. Where they diverge, no tolerance setting fixes it, because the threshold was built to protect PO integrity, not contract compliance. A one-time read of contracts against paid history answers which problem a given company actually has before any configuration change is made. For the wider pattern this sits inside, start with the [margin drift](/insights/best-invoice-validation-software-smb) guide. See also [the six categories drift hides in](/insights/indirect-spend-audit-categories) and [what is margin erosion? causes and prevention for manufacturers](/insights/what-is-margin-erosion-causes-and-prevention-for).

## Common questions

### Does Global Shop Solutions check invoices against the vendor contract automatically?

No. Global Shop Solutions performs three-way matching between the invoice, the purchase order and the receipt. It has no field or module that reads the underlying vendor contract, so a rate card, rebate clause or surcharge schedule is never part of the automated comparison.

### What is the difference between a tolerance threshold and a contract compliance check?

A tolerance threshold compares an invoice to its purchase order within a set variance band. A contract compliance check compares an invoice directly to the contract terms: rate card, volume tier, NTE cap, rebate clause. They test different reference documents and a pass on one says nothing about the other.

### Can a tighter tolerance threshold catch a stale rate card?

No. A stale rate card means the purchase order itself carries the wrong price. A tolerance threshold, however tight, only checks whether the invoice matches that PO. If the PO is wrong, a tight threshold enforces the wrong number consistently rather than catching it.

### Should tolerance thresholds be the same for every vendor category?

Not if the categories carry different legitimate variance under their contracts. A fixed-price maintenance contract supports a narrow band. An indexed freight lane with fuel surcharges needs a wider one, or correct invoices will generate exception volume that adds no value.

### Who should own the tolerance threshold configuration in Global Shop Solutions?

Purchasing or AP configuration access is required to change the setting, but the decision of where to set the band should follow a read of the actual contract terms by category, not a system default left over from implementation.

---

ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us