What Acumatica's documentation says
- The Three-Way Match Validation section of Purchase Orders Preferences has a Bill Against Commitments setting, No Validation or Validate with Warning; with Validate with Warning each bill line's Unit Cost, Amount and Quantity are checked against the purchase order line's Unit Cost, Unbilled Amount and Unbilled Qty. Source 1 (opens in a new tab)
- Under Validate with Warning a bill value larger than the purchase order shows a warning on the bill's Details tab; it does not block the bill. Source 2 (opens in a new tab)
- Receipt tolerances are set per vendor in the Receipt Actions section of the Vendors (AP303000) form with Min. Receipt (%), Max. Receipt (%), Threshold Receipt (%) and Receipt Action. Source 3 (opens in a new tab)
Checked against the vendor's documentation on Nov 7, 2026. Products change; the vendor's current help is the final word.
What Acumatica matches
Three-way match means three records agree: the purchase order you sent, the receipt that says the goods arrived, and the bill the supplier sent. In Acumatica the control sits in the Three-Way Match Validation section of Purchase Orders Preferences. The Bill Against Commitments setting has two options, No Validation or Validate with Warning.
With Validate with Warning, each bill line's Unit Cost, Amount and Quantity are checked against the purchase order line's Unit Cost, Unbilled Amount and Unbilled Qty. That is line by line, not document by document. A ten line purchase order can pass on nine lines and warn on the tenth, and the tenth is where the money is.
The warning shows on the bill's Details tab. It does not block the bill. That is the part AP clerks miss. The bill still posts and still gets paid if nobody reads the warning, so the check is only as good as the person reviewing the Details tab before the bill moves on.
Receipts have their own control. Receipt tolerances are set per vendor in the Receipt Actions section of the Vendors (AP303000) form, using Min. Receipt (%), Max. Receipt (%), Threshold Receipt (%) and Receipt Action. So the quantity side of the match is tuned vendor by vendor, which makes sense: a pallet of steel and a box of labels do not over ship by the same percentage.
The Vendor Ref. field on the bill is where the supplier's own invoice number goes. Treat it as a control, not a formality. Re-keyed numbers are the root of most duplicate payments: INV-1043 typed on one bill and 1043 typed on another look like two invoices to any system that only compares the field as text.
Where matching stops
Matching stops at the purchase order. If a bill has no purchase order behind it, there is nothing to match, and the bill goes through on approval alone. Utilities, rent, professional fees, subscriptions and one-off services usually land here. Those are exactly the payments where duplicates and overpayments hide, because no line level check ever runs.
Matching also stops at the receipt. If goods were received but the receipt was never entered in Acumatica, the bill will warn on quantity even though the delivery was real. The fix is to get the receipt entered, not to override the warning. An AP team that habitually clicks past warnings has turned a control into a rubber stamp.
A bill value larger than the purchase order shows a warning, and that is all it does. It does not block the bill. If a supplier bills $5,200 against a purchase order for $5,000, the warning appears and the bill can still be released. Someone has to decide whether the extra $200 is a legitimate freight charge or an overpayment, and that decision belongs to a person, not the setting.
Partial receipts add a quieter problem. When half an order arrives, the unbilled quantity on the purchase order line stays open, and a second bill can be entered against it. If the first bill was already paid in full for the whole order, the second bill is a duplicate that the match will not flag, because the quantities technically line up with the receipts on file.
Tolerances and exceptions
Tolerances exist so that small, expected differences do not stop the queue. The Receipt Actions settings on the Vendors (AP303000) form let you set Min. Receipt (%), Max. Receipt (%) and Threshold Receipt (%), plus a Receipt Action. Set them deliberately for each vendor, and review them once a year. A tolerance set wide to clear a backlog two years ago is still clearing overpayments today.
Work an example. A vendor has Max. Receipt (%) set at 105 and Threshold Receipt (%) at 100. An order for 1,000 units comes in at 1,040 units and the bill covers all 1,040. The receipt falls inside tolerance, so the quantity side passes. The bill line still gets checked against the purchase order's Unbilled Qty, and the 40 extra units have no purchase order behind them. That is the moment to ask the supplier for a credit rather than pay and chase later.
Exceptions need an owner and a reason. When a clerk clears a warning on the Details tab, the reason should be written down: price increase agreed by email on a specific date, freight added after the fact, short shipment accepted. Without that note, the next person cannot tell a legitimate exception from a mistake, and the same vendor keeps producing the same warning month after month.
Watch the vendors that generate most of your warnings. A supplier whose bills routinely exceed the purchase order is either pricing after the order or billing items nobody ordered. Both are worth a conversation, and both cost less to fix at the source than to reconcile after payment.
What matching does not catch
Matching compares a bill to a purchase order and a receipt. It does not compare a bill to other bills. The same supplier invoice entered twice, once as INV-1043 and once as 1043, passes matching both times if both entries tie to open purchase order quantity. Nothing in the three-way check knows the two bills are the same piece of paper.
A supplier set up twice as two vendor records defeats matching and duplicate checking at the same time. The same invoice can be paid once under each record, and reports grouped by vendor will never show the two together. Periodically compare vendor records on name, address, bank details and tax number, and merge or deactivate the duplicates you find.
Statements are another blind spot. Paying a supplier statement as well as the individual invoices behind it is a classic overpayment, and matching has no view of the statement. Reconcile statements to your open payables before you pay anything off a statement, line by line, and note which invoices each statement line refers to.
Credits are the last one. A supplier credit that is never applied sits on the account while the next bill gets paid in full. Matching sees the bill, not the unapplied credit. Review open credits by vendor every month and apply them, or ask the supplier for a refund. Re-sent payment runs cause the same damage: if a run is reissued after a bank file was already sent, the second payment goes out and no match will stop it. Check the bank before reissuing. For anything the settings do not cover, such as what happens to a bill after a void, check Acumatica's own help rather than guessing.
On a bill in Acumatica, the supplier's invoice number goes in the Vendor Ref. field. Any paid-bills export that includes it, the vendor, dates and amounts can be checked for duplicates.
Questions
How do I turn on three-way match in Acumatica?
Open the Three-Way Match Validation section of Purchase Orders Preferences and set Bill Against Commitments to Validate with Warning. With that setting, each bill line's Unit Cost, Amount and Quantity are checked against the purchase order line's Unit Cost, Unbilled Amount and Unbilled Qty. A bill value larger than the purchase order shows a warning on the bill's Details tab but does not block the bill.
Why did my bill pass matching when it was a duplicate?
Matching compares the bill to the purchase order and receipt, not to other bills. If the same invoice was entered twice with the supplier number written differently, such as INV-1043 and 1043, both entries can tie to open purchase order quantity and pass. Compare Vendor Ref. values across the vendor's recent bills and look for the same amount and date before you pay.
Where do I set receipt tolerances for a vendor in Acumatica?
Receipt tolerances are set per vendor in the Receipt Actions section of the Vendors (AP303000) form. The fields are Min. Receipt (%), Max. Receipt (%), Threshold Receipt (%) and Receipt Action. Review them yearly, because a wide tolerance set to clear an old backlog will keep letting over receipts through.
What should I do when a bill warns that it is larger than the purchase order?
Find out why before releasing it. The warning means the bill value is larger than the purchase order, and it does not block the bill, so the decision is yours. If the difference is an agreed price change or freight, note the reason on the bill. If it is not, ask the supplier for a credit or a corrected invoice.
Updated Nov 21, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.