How Do You Set Up Tolerance Thresholds in Sage Intacct?

Executive Summary

Sage Intacct's tolerance thresholds work at the transaction level: they compare an invoice line to a purchase order line, or to a receipt, and flag or block the difference once it crosses a configured limit. That configuration lives in purchasing and AP settings, applied by transaction definition, and it can be set as a dollar amount, a percentage, or both.

The mechanism is narrow by design. It tests the invoice against the PO it was cut against. It does not test the PO against the underlying vendor contract, so a PO built from a stale rate card passes every tolerance check the system offers, because the invoice matches the PO it was compared to.

That distinction matters for anyone configuring this. Tolerance settings protect against clerical and pricing errors relative to the PO on file. They do not protect against a PO that was never updated when the contract changed, a rebate that went unclaimed, or a surcharge with an expired trigger condition.

Those require checking the invoice against the contract directly, a step outside what tolerance settings are built to do.

1. What does a tolerance threshold actually compare in Sage Intacct?

A tolerance threshold in Sage Intacct compares an AP invoice line against the purchase order line or receipt it references, then flags or blocks the transaction once the variance crosses a limit you configure. The comparison is always relative to the PO, not to a contract, rate card, or rebate schedule. If the PO price is wrong, the invoice can match it exactly and still clear every tolerance check the system runs, because the check never looks past the PO.

The comparison runs during three-way matching, where Intacct checks the invoice against the purchase order and, where receiving is used, against the goods or services receipt. Tolerance settings determine how much variance between those documents is acceptable before the system routes the transaction for review or stops it from posting.

This is a document-to-document check. It asks whether the invoice agrees with the PO, not whether the PO agrees with the contract that was supposed to generate it. A price increase that never made it from the vendor's rate card into the PO will not surface here, because the PO itself becomes the reference point the invoice is judged against.

Understanding that boundary before configuring anything prevents a common mistake: treating tolerance setup as if it were contract enforcement. It is invoice-to-PO enforcement, and the PO's accuracy is a separate problem entirely.

2. Where do you configure tolerance settings in Sage Intacct?

Tolerance thresholds are configured in Sage Intacct's Purchasing and Accounts Payable application settings, typically under the matching or transaction rules for purchase order and bill workflows. You set a threshold per transaction definition, meaning different PO types or vendor categories can carry different limits. The settings accept a fixed dollar amount, a percentage of line value, or both, and the system applies whichever combination is configured for that transaction path.

Configuration happens at the application level rather than on an individual purchase order, so the limits you set apply consistently across every transaction using that definition. This is useful for separating, for example, a freight PO from an MRO purchase order, since the two carry different pricing volatility and might reasonably need different limits.

Both an amount and a percentage can be active simultaneously. In that setup, a transaction typically has to pass both tests, or fail on whichever one is stricter for that line value, depending on how the rule is written.

Because the setting lives at the transaction definition level, changing it affects every future transaction on that path immediately. It does not retroactively re-check invoices that already posted under the old threshold.

3. What happens when an invoice exceeds the configured tolerance?

When an invoice line falls outside its configured tolerance, Sage Intacct routes the bill into an exception state rather than letting it post automatically. Depending on how the workflow is built, that means it lands in an approval queue, gets flagged with a variance notation, or is held until someone manually confirms or corrects the mismatch. The system does not resolve the variance itself; it surfaces it and waits for a person to act on it.

The exception handling is a routing decision, not a judgment call. Intacct does not evaluate whether the variance is legitimate, such as a documented price increase, or a mistake, such as a keying error. It simply stops the transaction at the point the rule defines and hands it to a reviewer.

That reviewer needs a reference beyond what Intacct shows them. The system displays the PO price and the invoice price side by side. It does not display the vendor contract clause that would explain whether the new price is contractually valid. Someone still has to pull the contract to make that call.

This is the point where a tolerance exception becomes either a two-minute approval or a research project, depending on whether the underlying contract terms are easy to locate.

4. Can tolerance thresholds catch a rate card that changed without a new PO?

No. A tolerance threshold only compares the invoice to the purchase order already on file, so if a vendor's rate card changed and the invoice reflects the new rate while the PO still reflects the old one, the variance is exactly what the tolerance rule is designed to catch, and it will flag correctly. The gap opens instead when a PO gets recreated or amended to match the new rate before anyone confirms the new rate against the actual contract.

There are two different failure modes here, and they behave differently inside Intacct. In the first, the PO is stale and the invoice reflects a genuine price change: tolerance checking works exactly as intended and flags the variance for review.

In the second, someone updates the PO to match what the vendor is now charging, without first checking whether the new charge is what the contract actually allows. Once the PO carries the new number, every subsequent invoice at that price passes tolerance cleanly, because the invoice now agrees with the PO.

The second failure mode is the one tolerance settings cannot reach by design. It requires comparing the PO itself, not just the invoice, against the contract's rate schedule, volume tiers, and any negotiated caps. That comparison sits outside purchasing and AP matching entirely.

5. How do tolerance rules interact with rebates, NTE caps, and surcharge schedules?

Tolerance rules do not interact with rebates, not-to-exceed caps, or surcharge schedules at all, because those terms typically do not live inside a structured PO field the system can compare against. A tolerance threshold tests a price variance on a line item. It has no mechanism for tracking whether a rebate tied to volume was applied, whether a surcharge's trigger condition already expired, or whether a not-to-exceed cap was breached across multiple invoices.

A. Rebate clauses

Rebates are typically owed back to the buyer after a volume threshold is crossed, often on a delayed schedule. Nothing in a tolerance rule tracks cumulative volume against a rebate tier or checks whether a credit memo should have arrived.

B. Not-to-exceed caps

An NTE cap limits total spend on a contract line across many invoices, not a single line's price. Tolerance thresholds evaluate one transaction at a time, so a cap breach that only becomes visible in aggregate falls outside what any single tolerance check is built to see.

C. Surcharge schedules

A fuel or accessorial surcharge often has a trigger condition and an expiration built into the contract text, not the PO. If the surcharge keeps applying past its contractual end date, the PO and invoice can still agree with each other, and tolerance checking has nothing to flag.

6. Should you rely on tolerance settings alone, or add a separate contract check?

Tolerance settings should stay in place, since they catch genuine clerical and matching errors cheaply and automatically. But relying on them alone leaves the categories described above, stale rate cards baked into a PO, unclaimed rebates, expired surcharges, and NTE breaches, unchecked, because none of those show up as a PO-to-invoice variance. Closing that gap means checking invoices against the underlying vendor contract directly, on a cadence separate from routine three-way matching.

The decision is not whether tolerance settings are worth configuring. They are, and they cost little to maintain once set. The decision is whether they are treated as the complete control or as one layer of one.

A retrospective review of historical invoices against actual contract terms, run independently of the PO matching workflow, is what surfaces the gap tolerance settings cannot reach. That review looks at the contract document itself: the rate card, the volume tiers, the rebate clauses, and the surcharge conditions, and checks the invoice against those terms rather than against whatever the PO happened to say.

Whether that review is worth running depends on the volume and complexity of service vendor spend passing through Sage Intacct. A finance team can estimate it directly: take total service vendor spend, multiply by the share running through contracts complex enough to include rebates, NTE caps, or surcharge terms, and that is the population a PO-matching tolerance rule was never going to cover.

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 Sage Intacct tolerance checking replace the need for a contract review?

No. Tolerance checking compares an invoice to its purchase order. A contract review compares the invoice, or the PO, to the actual vendor agreement, including rate cards, rebate clauses, and surcharge terms. The two checks answer different questions, and neither substitutes for the other.

Can tolerance thresholds be set differently for different vendors?

Tolerance settings are configured at the transaction definition level in Sage Intacct, which can be structured by PO type or category rather than by individual vendor directly. Different transaction definitions can carry different dollar or percentage limits, giving indirect control over vendor-level variance handling.

What is the difference between a dollar tolerance and a percentage tolerance?

A dollar tolerance sets a fixed variance amount, such as a flat difference allowed regardless of line size. A percentage tolerance scales with the line value instead. Many Sage Intacct configurations use both together, so a small line and a large line are each held to a proportionate standard.

Will a tolerance rule catch a duplicate payment?

Not directly. Tolerance rules test price variance between an invoice and its PO. Duplicate payment detection is a separate check, usually comparing invoice number, vendor, amount, and date across the AP ledger rather than against a purchase order.

Why would a PO price be wrong in the first place?

A PO can be generated from an outdated rate card, entered manually with a keying error, or rolled forward from a prior period without checking whether the underlying contract changed. None of these causes are visible inside a tolerance rule, since the rule only ever sees the PO as the reference truth.

Does three-way matching in Sage Intacct check contract terms automatically?

Three-way matching checks the invoice against the purchase order and the receipt. It does not read the vendor contract document, so terms that live only in the contract, such as a rebate clause or a surcharge expiration date, are outside what three-way matching evaluates.

How often should tolerance thresholds be reviewed once configured?

Sage Intacct does not prompt a review cadence on its own. A reasonable practice is to revisit thresholds whenever purchasing volume, vendor mix, or contract terms change materially, since a threshold set for one spend profile may be too loose or too tight for another.

Can a tolerance exception be approved without checking the contract?

Yes, and this is where drift often gets baked in. Nothing in Sage Intacct forces a reviewer to pull the contract before approving a flagged variance. An approver who checks only whether the new price looks reasonable, without confirming it against the contract, can approve a rate that was never authorized.