What counts as price tolerance?

Glossary definition of price tolerance in vendor contract auditing: how the variance band is set, why it exists, and where it hides margin drift.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
What counts as price tolerance?

Price tolerance is the allowable variance a buyer sets between a contracted rate and the rate actually billed before a line item is flagged for review. Finance teams set it inside AP automation and audit workflows to separate rounding noise from real margin drift, and the threshold they choose decides how much leakage passes through invisible. A tolerance set wide enough to reduce match exceptions also widens the range in which a stale rate card, an unapplied rebate, or a misapplied volume tier can sit unnoticed.

A width chosen without reference to the contract's own variance clause has no defensible basis, which is why the diagnostic checks invoices against contract terms line by line rather than trusting the tolerance band alone.

1. What is price tolerance?

Price tolerance is a set percentage or dollar band around a contracted price. When an invoiced rate falls inside the band, matching software approves it automatically. When it falls outside, the system holds the invoice for manual review.

The tolerance exists because minor rounding, currency conversion, and unit-of-measure differences produce small variances that are not worth investigating individually.

A tolerance is configured once and applied across many invoices, so its width matters more than its existence.

2. Why does a tolerance band exist at all?

A zero-tolerance match would stop nearly every invoice for review, because rounding at the unit level and small unit-of-measure conversions create variance even when the vendor billed correctly. A tolerance band lets three-way matching pass invoices that are functionally correct while still catching charges that deviate for a real reason: a stale rate card, a missed rebate, or an unapplied volume tier.

The band is a filter, not a judgment on whether a vendor is honest.

3. How wide should a price tolerance be set?

There is no single correct width. A band wide enough to absorb rounding but narrow enough to catch a rate card error depends on the category, the unit price, and how the contract itself defines acceptable variance. A band set too wide lets small overcharges repeat invoice after invoice without ever surfacing for review.

Contracts with a stated variance clause should drive the tolerance, not a default setting.

  • Rate card categories: Categories with frequent SKU-level pricing, like MRO and Class C consumables, often need a tighter band because small per-unit errors compound across volume.
  • Contract silence: Where a contract states no variance clause, the tolerance should default narrow rather than wide, since a wide default has no contractual basis.
  • Periodic review: A band set once at implementation and never revisited stops reflecting current contract terms as rates and rebates change.

4. What happens when a charge falls outside tolerance?

An invoice line outside the tolerance band is held rather than paid automatically, and someone compares the billed rate against the underlying rate card or contract clause. That comparison either confirms a legitimate price increase or identifies a drift condition such as a stale rate, a missed credit, or a volume tier applied incorrectly. The hold is the control point; what happens next is the investigation.

A tolerance band only works if the holds it generates are actually reviewed, not cleared in bulk.

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

5. Frequently Asked Questions (People Also Ask)

Is price tolerance the same as margin drift?

No. Price tolerance is a configuration setting that decides which invoices get reviewed. Margin drift is the gap between what a contract says and what an invoice charges. A tolerance band can hide margin drift when it is set wider than the contract's actual terms allow.

Who sets the price tolerance in an AP system?

Typically the AP or procurement team configures it inside the ERP or matching software, often as a default percentage applied across vendors rather than a value drawn from each contract's own variance clause.

Does a tighter tolerance always catch more drift?

A tighter band reduces the range of unexamined variance, but it also increases manual review volume. The goal is a band that matches what the contract actually permits, not the narrowest possible setting.

Can a price tolerance be different for each vendor or category?

Yes. Nothing about the mechanism requires a single global setting. Categories with frequent per-unit pricing changes can carry a different band than categories billed at a flat contracted rate.

What is the difference between a price tolerance and a rate card?

A rate card states the contracted price for each item or service. A price tolerance is the variance allowed around that stated price before the difference is flagged for review.

Does a legitimate price increase get flagged by a tolerance check?

It can, if the increase falls outside the configured band. That flag does not mean the increase is wrong; it means the variance needs to be checked against the contract's escalation terms before the invoice is paid.

Should a tolerance band be reviewed periodically?

A band set once at implementation and never revisited stops reflecting current contract terms as rates change, rebates get added, or volume tiers shift, so periodic review against the underlying contracts keeps the band meaningful.

What is a stated basis for setting a tolerance width?

A stated basis means the width traces to something written, such as a contract's variance clause or a documented rounding policy, rather than an unexamined system default carried over from setup.

1. What is price tolerance?

Price tolerance is a set percentage or dollar band around a contracted price. When an invoiced rate falls inside the band, matching software approves it automatically. When it falls outside, the system holds the invoice for manual review. The tolerance exists because minor rounding, currency conversion, and unit-of-measure differences produce small variances that are not worth investigating individually. A tolerance is configured once and applied across many invoices, so its width matters more than its existence.

2. Why does a tolerance band exist at all?

A zero-tolerance match would stop nearly every invoice for review, because rounding at the unit level and small unit-of-measure conversions create variance even when the vendor billed correctly. A tolerance band lets three-way matching pass invoices that are functionally correct while still catching charges that deviate for a real reason: a stale rate card, a missed rebate, or an unapplied volume tier. The band is a filter, not a judgment on whether a vendor is honest.

3. How wide should a price tolerance be set?

There is no single correct width. A band wide enough to absorb rounding but narrow enough to catch a rate card error depends on the category, the unit price, and how the contract itself defines acceptable variance. A band set too wide lets small overcharges repeat invoice after invoice without ever surfacing for review. Contracts with a stated variance clause should drive the tolerance, not a default setting. - Rate card categories: Categories with frequent SKU-level pricing, like [MRO and Class C consumables](/glossary/mro-and-class-c-consumables-audit), often need a tighter band because small per-unit errors compound across volume. - Contract silence: Where a contract states no variance clause, the tolerance should default narrow rather than wide, since a wide default has no contractual basis. - Periodic review: A band set once at implementation and never revisited stops reflecting current contract terms as rates and rebates change.

4. What happens when a charge falls outside tolerance?

An invoice line outside the tolerance band is held rather than paid automatically, and someone compares the billed rate against the underlying rate card or contract clause. That comparison either confirms a legitimate price increase or identifies a drift condition such as a stale rate, a missed credit, or a volume tier applied incorrectly. The hold is the control point; what happens next is the investigation. A tolerance band only works if the holds it generates are actually reviewed, not cleared in bulk. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

Is price tolerance the same as margin drift?

No. Price tolerance is a configuration setting that decides which invoices get reviewed. Margin drift is the gap between what a contract says and what an invoice charges. A tolerance band can hide margin drift when it is set wider than the contract's actual terms allow.

Who sets the price tolerance in an AP system?

Typically the AP or procurement team configures it inside the ERP or matching software, often as a default percentage applied across vendors rather than a value drawn from each contract's own variance clause.

Does a tighter tolerance always catch more drift?

A tighter band reduces the range of unexamined variance, but it also increases manual review volume. The goal is a band that matches what the contract actually permits, not the narrowest possible setting.

Can a price tolerance be different for each vendor or category?

Yes. Nothing about the mechanism requires a single global setting. Categories with frequent per-unit pricing changes can carry a different band than categories billed at a flat contracted rate.

What is the difference between a price tolerance and a rate card?

A rate card states the contracted price for each item or service. A price tolerance is the variance allowed around that stated price before the difference is flagged for review.

Margin Drift Resources