Invoice tolerance thresholds in an ERP system are the variance limits that decide which supplier invoices clear matching automatically and which get held for human review. You set an acceptable range of difference between an invoice and its purchase order (and, where applicable, the goods receipt), and the software enforces it on every line. Set the limits too loosely and overbillings slip through; set them too tightly and your AP queue fills with holds over pennies. The configuration below is what separates a matching engine that pays cleanly from one that generates constant noise.
Percentage Limits, Fixed Amounts, and Which One Wins
Most ERPs let you express a tolerance two ways: as a fixed currency amount or as a percentage of the purchase order value. A ten-dollar fixed tolerance allows up to ten dollars of variance no matter the invoice total. A two-percent tolerance on a ten-thousand-dollar contract permits up to two hundred dollars of difference before the system flags it.1SAP Ariba Support. How Are the Absolute and Percentage Tolerances Evaluated to Trigger Invoice Exceptions?
You can define both at once. In Oracle Cloud Financials you specify separate percentage and amount tolerances for each tolerance category, and the system evaluates both.2Oracle Help Center. Invoice Tolerances When both are active, the tighter of the two governs. On a two-thousand-dollar invoice, a five-percent tolerance would allow a hundred dollars of variance while a five-dollar cap would not; the fixed amount holds the line, which is the behavior you want on higher-value orders.
One configuration trap catches administrators regularly. In Oracle Payables, an active tolerance with the value field left blank means infinite variance is allowed, and the system will never hold the invoice for that check.2Oracle Help Center. Invoice Tolerances That is the opposite of what most people expect. If you want zero tolerance, enter zero explicitly.
Which Direction the Check Runs
A common question during setup: does the tolerance work both ways? If you ordered a hundred units and the vendor billed for ninety-five, does the system care? In most ERP platforms, standard matching tolerances are designed to catch overbilling, not underbilling. Oracle’s tolerance definitions check whether the billed amount or quantity exceeds the ordered or received figure by more than the allowed variance.2Oracle Help Center. Invoice Tolerances An invoice that comes in below the PO generally posts without a matching hold.
That works fine for routine AP, but it can leave unreceived goods stranded on prematurely closed POs. If underbilling matters to your business, build the check outside the standard framework, usually as a report comparing open PO balances against received quantities.
SAP handles rounding and tiny residuals through the tolerance key BD, which posts small leftover balances to a “small differences” expense account instead of blocking the invoice. When the remaining balance falls below the BD threshold, the system zeroes it out and posts.3SAP Learning. Entering Invoices with Variances Configure this and your queue stops filling with holds over fractions of a cent.
Two-Way, Three-Way, and Four-Way Matching
The number of documents the ERP compares determines how many places a tolerance can trip. What you choose depends on what you buy and how much verification the purchase warrants.
Two-Way Matching
Two-way matching compares the invoice against the purchase order. The system checks whether the invoiced unit price and total fall within tolerance of what was authorized. This fits services, subscriptions, and anything without a physical receipt. Faster, fewer exceptions, but it will not catch a vendor billing you for goods that never showed up.
Three-Way Matching
Three-way matching adds the goods receipt. Now the system verifies price and total against the PO and quantity billed against quantity received. If a vendor ships eighty units and invoices for a hundred, the quantity tolerance flags it. This is the standard for physical goods and it is where tolerance settings earn their keep: three documents create more places for small discrepancies to appear.
Four-Way Matching
Four-way matching adds a quality inspection record on top of the PO, goods receipt, and invoice. The invoice will not clear until someone confirms the received goods passed inspection and records the accepted quantity. If a hundred units arrived but only ninety were accepted, the invoice sits until the billed quantity aligns with the accepted quantity. Pharmaceutical, aerospace, and food manufacturing environments typically require this level.
Setting Tax Tolerances Separately
Sales tax discrepancies belong on their own tolerance settings because they follow different logic from price or quantity checks. When a vendor calculates tax slightly differently than your ERP does, the variance is not a procurement issue and should not route to a buyer. Most systems handle this through a dedicated tax tolerance that compares invoice tax against system-calculated tax.4Oracle Help Center. Invoice Tolerances
In Oracle Payables, the system validates the tax amount on invoice distributions against the expected amount based on the applied tax code. If the implied rate differs from the rate on file by more than the tolerance, the system places a Tax Variance hold.4Oracle Help Center. Invoice Tolerances A separate Tax Difference hold fires when the tax code on the invoice does not match the tax code on the PO at all.5Oracle Help Center. Types of Holds
Keep tax tolerances narrow. A one-dollar tax discrepancy on a five-hundred-dollar invoice is a rounding difference. A twenty-dollar discrepancy on that same invoice means someone applied the wrong rate, and letting it through means recording an incorrect tax liability.
Configuring at the Global Level and at the Supplier Level
Setup starts with mapping the PO fields the system will compare against incoming invoices: line quantities, unit prices, extended amounts, and freight or miscellaneous charges. You also identify which GL codes and tax identifiers interact with the tolerance logic so the system posts variances to the right accounts. In SAP, tolerance keys such as PP (price variance), DQ (quantity variance), and AN (amount check for non-PO invoices) each control a specific comparison, and you set upper and lower limits at the company code level.3SAP Learning. Entering Invoices with Variances Oracle uses named tolerance templates that you build once and assign to individual supplier sites.2Oracle Help Center. Invoice Tolerances
Supplier-level assignment is where a lot of the value lives. A vendor with a long-term contract and stable pricing warrants tight tolerances because deviations signal a real problem. A commodities supplier whose prices move weekly needs wider tolerances or you will block every invoice. Most ERPs let you override global defaults at the vendor or vendor-site level for exactly this reason.2Oracle Help Center. Invoice Tolerances
What Happens When an Invoice Fails a Check
When matching fails, the system applies a hold code that names the specific tolerance breached. Oracle Payables distinguishes among more than a dozen matching hold types. A Price hold means the weighted average unit price across matched distributions exceeded the PO price by more than the percentage tolerance. A Qty Ord hold means the billed quantity exceeded the ordered quantity beyond the allowed percentage. MAX AMT ORD fires when the billed amount exceeds the ordered amount plus a fixed dollar tolerance.5Oracle Help Center. Types of Holds The hold code points the reviewer straight to the problem.
Resolution depends on the variance type. Price discrepancies route to the buyer who negotiated the PO, who confirms whether a price increase is legitimate, whether a contract amendment applies, or whether the invoice is wrong. Quantity discrepancies route to receiving to verify what arrived. The reviewer either corrects the underlying data (amends the PO, posts a missing receipt) or rejects the invoice back to the vendor.
A held invoice cannot generate accounting entries or be included in a payment run until the hold is released.6Oracle Help Center. Invoice Holds and Releases Every release should document who approved it, what evidence was reviewed, and when. Where someone approves an invoice despite the breach, that record is the audit trail proving the control was exercised deliberately rather than bypassed.
What Auditors Expect Under SOX
For public companies, invoice tolerance settings sit inside the internal control environment that Sarbanes-Oxley Section 404 requires management to maintain and assess annually. Annual reports must contain management’s assessment of the effectiveness of internal controls over financial reporting, and the external auditor must attest to that assessment.7Office of the Law Revision Counsel. 15 USC 7262 – Management Assessment of Internal Controls SOX does not prescribe specific dollar or percentage thresholds, but whatever controls you define must be documented, consistently applied, and tested.
Auditors reviewing AP tolerance controls typically look at three things: whether the thresholds were formally documented in the control narrative before the testing period began, whether the documented thresholds were applied uniformly across all transactions without ad hoc deviations, and whether invoices that exceeded tolerances and were still approved carried a secondary approver’s sign-off with appropriate authority. A common finding is inconsistent application: the control description says two percent, but testing reveals some reviewers applied five percent while others applied one percent with no documented rationale.
Segregation of duties reinforces the control. The person who configures thresholds in the ERP should not be the person who approves invoices that breach them. The person who initiates a PO should not approve the matching exception when the invoice comes in higher than expected. Where team size makes full separation impractical, a compensating control such as detailed supervisory review of exception approvals can satisfy the requirement. No single person should be able to both set the rules and decide when to break them.
Federal Vendors and the Prompt Payment Clock
If your organization does business with the federal government, tolerance-related holds run against strict payment deadlines. Under the Prompt Payment Act, a federal agency that receives an invoice it considers improper must return it to the vendor within seven days, specifying every reason it does not meet requirements.8Office of the Law Revision Counsel. 31 USC 3903 – Regulations Two categories have shorter deadlines: meat and seafood products within three days, and perishable agricultural commodities and dairy products within five days.9eCFR. 5 CFR Part 1315 – Prompt Payment
Missing these deadlines has a direct cost. If an agency takes twelve days to notify a vendor about a defective invoice instead of the required seven, five days are lost from the payment window before the clock resets on the corrected invoice. Late payments accrue interest at the Prompt Payment rate, which for the first half of 2026 is 4.125 percent annually.10Bureau of the Fiscal Service. Prompt Payment Blocking an invoice for a minor price variance is the right control decision, but letting the hold sit for two weeks can convert a legitimate exception into an interest penalty. Many states impose similar prompt payment requirements on state agencies, at rates that can run considerably higher than the federal rate.