What is PO price tolerance, and how do I set it?
PO price tolerance is the allowed variance between a purchase order's price and a vendor invoice's price before three-way matching flags it for manual review instead of auto-approving. Systems typically let you set it as a percentage, an absolute amount, or both, and configure it at different levels — NetSuite allows subsidiary, item, and vendor-level tolerances that can differ from each other.
By Zuny Fester, Head of Operations and MarketingPart of the accounts payable and invoice processing guide.
| What it controls | How much an invoice's unit price or line total can differ from the PO before it's flagged |
|---|---|
| Configuration types | Percentage tolerance and absolute difference limit — systems support one or both |
| Example from Microsoft Dynamics 365 | One legal entity set an 8% net unit price tolerance and 15% price-totals tolerance for asset items |
| NetSuite's structure | Tolerance (percentage) and Difference (absolute quantity/amount) limits, each settable at subsidiary, item, and vendor level |
| What happens outside tolerance | The line fails matching and routes to manual approval rather than posting automatically |
Why an exact match is the wrong default
Requiring an invoice to match a PO to the exact cent would flag nearly every invoice for manual review — rounding, small freight adjustments, and minor pricing updates between order and invoice are routine, not fraud. Price tolerance exists so three-way matching can auto-approve the genuinely-fine variances and only escalate the ones worth a human looking at.
Two different kinds of limit, and why systems offer both
NetSuite's own documentation on tolerance and difference limits draws a clear line between the two: a tolerance limit is percentage-based, and a difference limit is an absolute quantity or amount. Both are configurable at three levels — subsidiary, item, and vendor record — which matters because a 2% tolerance on a $500 line item and a 2% tolerance on a $50,000 line item represent very different dollar exposure. A difference limit set alongside a tolerance percentage catches the case where a small percentage variance still represents a large absolute dollar swing on a high-value line.
What a real configuration looks like
Microsoft Dynamics 365 Finance's own documentation walks through a concrete example: one legal entity sets net unit price tolerance to 8% and price-totals matching tolerance to 15% for three-way-matched asset items, while a different division in the same example sets unit price tolerance to 2% and totals tolerance to 10% for a broader set of items — tighter tolerances for lower-volume, higher-risk purchases from vendors with a history of delivery problems. There's no universal correct number; the tolerance should reflect how much variance is actually normal for that item and vendor relationship, not a single company-wide default copied from elsewhere.
Next step
Map the finance workflow with the most exposure and prove the automation path.
Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.
Field mapping
Two real tolerance configurations, side by side
| Setting | Example A (asset items) | Example B (broader item set) |
|---|---|---|
| Net unit price tolerance | 8% | 2% |
| Price-totals tolerance | 15% | 10% |
| Matching level | Three-way (item, on asset purchases) | Two-way default, three-way override for specific item/vendor pairs |
Frequently Asked Questions
Sources
Related
Topic
AP & Invoice Processing
Accounts payable and invoice processing is the set of steps a vendor bill goes through between arriving at a company and turning into a payment: capturing what the vendor sent, checking it against wha…
Read moreDiagnostic
What causes a three-way match failure between the PO, receipt, and invoice?
A three-way match compares the PO, the receipt (what was actually delivered), and the invoice on quantity, price, and charges. A failure means one of those three disagrees beyond tolerance — usually because the invoice bills a quantity that isn't fully receipted yet, the unit price differs from the PO, or the invoice adds a charge, like freight, the PO never included.
Read moreHow-to
How do I apply a vendor credit memo in AP?
Enter the vendor credit as its own record, then apply it against a specific open bill at the point of payment rather than netting it manually. Both QuickBooks and NetSuite require an open bill from that vendor to apply the credit to — a credit with nothing outstanding to apply against just sits unapplied until a new bill arrives.
Read moreHow-to
How do I maintain segregation of duties in an automated AP approval workflow?
Keep three roles distinct in the workflow itself: who can create or edit a vendor record, who can enter or submit a bill, and who can approve it for payment. Institutional guidance is explicit that authorizing a payment and the person who executes it shouldn't be the same individual — automation makes it easy to collapse these into one click, which is exactly the risk to design against.
Read more