NetSuite · Matching bills to POs

Three-way match in NetSuite: bills, purchase orders and receipts

Three-way match in NetSuite compares a vendor bill with its purchase order and item receipt before payment, so quantity, price and receipt problems surface before the money leaves.

What NetSuite's documentation says

  1. NetSuite's 3 Way Match Vendor Bill Approval Workflow, part of the NetSuite Approvals Workflow SuiteApp, checks a vendor bill against its purchase order and item receipt and routes bills with discrepancies to a supervisor. It does not support partially received item receipts. Source 1 (opens in a new tab)
  2. The workflow's tolerance fields are VB-PO Amount Tolerance and VB-PO Quantity Difference: a bill within the amount tolerance is approved automatically, one beyond the quantity difference goes for approval. Source 2 (opens in a new tab)
  3. With Advanced Receiving, purchase order lines marked Match Bill to Receipt compare receipt lines with bill lines for quantity, price and exchange rate, and the variances are posted at Transactions > Payables > Post Vendor Bill Variances. 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 NetSuite matches

Three-way match ties three records together: the vendor bill, the purchase order behind it and the item receipt that shows what arrived. In NetSuite, the 3 Way Match Vendor Bill Approval Workflow, part of the NetSuite Approvals Workflow SuiteApp, checks a vendor bill against its purchase order and item receipt and routes bills with discrepancies to a supervisor. The point is simple: did we order it, did we receive it, and did the supplier bill what we agreed?

With Advanced Receiving, purchase order lines marked Match Bill to Receipt compare receipt lines with bill lines for quantity, price and exchange rate. The variances are posted at Transactions > Payables > Post Vendor Bill Variances. That gives AP a place to see price and exchange rate differences instead of burying them in the bill.

The workflow's tolerance fields are VB-PO Amount Tolerance and VB-PO Quantity Difference. A bill within the amount tolerance is approved automatically, while one beyond the quantity difference goes for approval. When you export bills, the supplier invoice number sits in Reference No. Treat that field as a duplicate-check field, not a formality: INV-1043 and 1043 are different strings even though they are the same supplier invoice.

Where matching stops

The workflow does not support partially received item receipts. That is a hard stop, not a tolerance setting. If a receipt is partial, do not assume the match has covered the bill. Check NetSuite's own help for how your setup should handle that bill, and keep the PO, receipt and bill together for whoever reviews it.

A match only compares what is in the receipt record. If someone keys a receipt for the wrong quantity, or a purchase order line is not marked Match Bill to Receipt, the comparison you expected may not happen. A receipt posted after the bill can also leave the bill unmatched or sent for approval. Do not edit the receipt to agree with the bill just to clear the exception. Fix the receiving record first, then let the match run again.

Three-way match also depends on there being a purchase order and a receipt. Service bills, rent, utilities and other non-PO spend do not have that chain, so the workflow is not a control for them. They still need an approval path and a duplicate check against the vendor record. The match is one control, not the whole payables process.

Tolerances and exceptions

Tolerances decide what passes without a person looking. VB-PO Amount Tolerance lets a bill within the amount tolerance go through automatically. VB-PO Quantity Difference sends a bill beyond the quantity difference for approval. Those settings are useful for small price rounding and ordinary quantity movement, not for changing the PO after the fact.

A bill for INV-1043 can sit within VB-PO Amount Tolerance and clear automatically. If the same supplier invoice is keyed again as 1043, the workflow may still pass it when the PO has open quantity and the amount is within tolerance. The string in Reference No. is different, so the match has no reason to stop. Catch that with a duplicate check on vendor, amount and date windows before the payment run, not with a wider tolerance.

When a bill goes for approval, send the reviewer the PO, the receipt, the bill and the supplier statement. If the bill is beyond the quantity difference because the receipt is wrong, the fix is in receiving. If the supplier billed a price that is not on the PO, ask for a credit before you pay the difference. A tolerance is not a reason to pay first and investigate later.

What matching does not catch

Three-way match does not know an invoice was already paid. The same invoice keyed as INV-1043 and 1043 can pass matching twice if the PO still has room. A supplier set up twice can hide the earlier payment because the vendor record looks new. A statement paid as well as the invoices on it, a re-sent payment run, and a credit that was never applied all produce overpayments that a bill-to-PO-to-receipt match will not see.

Statement reconciliation is where many of these surface. Match the statement lines to the vendor record, the bill and the payment history on vendor, amount and date windows. If the statement total was paid as well as the individual invoices, the same bill appears twice under different reference strings. If a credit memo is sitting unapplied, the statement may show it as open while your payment run pays the gross amount.

Ask the supplier for a credit or refund when you find a duplicate or an overpayment. Do not net it against a future bill without a clear record. Keep the supplier invoice number in Reference No. consistent, so INV-1043 and 1043 do not become two invoices in your history. Matching protects the quantity and price on the PO. It does not replace a duplicate payment check, a statement reconciliation or a credit review.

To review paid bills outside NetSuite, export them: Export paid bills from NetSuite. The supplier's invoice number is in the Reference No. column.

Questions

What is three-way match in NetSuite?

It compares a vendor bill with its purchase order and item receipt before payment. NetSuite's 3 Way Match Vendor Bill Approval Workflow, part of the NetSuite Approvals Workflow SuiteApp, checks the bill against the purchase order and item receipt and routes discrepancies to a supervisor. The workflow uses VB-PO Amount Tolerance and VB-PO Quantity Difference to decide what passes automatically and what goes for approval.

Why did my NetSuite bill go to approval?

A bill usually goes to approval because it falls outside the match rules or beyond VB-PO Quantity Difference. A bill within VB-PO Amount Tolerance is approved automatically. If the receipt is partial, the workflow does not support partially received item receipts, so check the receipt and NetSuite's own help for your setup.

Does NetSuite match partially received item receipts?

The 3 Way Match Vendor Bill Approval Workflow does not support partially received item receipts. Do not treat a partial receipt as a normal match exception. Check NetSuite's own help for how your setup should handle the bill, and keep the PO, receipt and bill together for review.

How do I find duplicate supplier invoices in NetSuite?

Export the bills and use Reference No. as the supplier invoice number. Normalize INV-1043 and 1043 so they are treated as the same invoice, and check for a supplier set up twice, a statement paid as well as its invoices, a re-sent payment run and a credit never applied. Match on vendor, amount and date windows, then ask the supplier for a credit or refund if you find a duplicate.

Updated Nov 11, 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.