What is 3-way matching in accounts payable?

Three-way or 3-way matching is a control process in accounts payable (AP) that verifies three documents before approving an invoice for payment: the purchase order (PO), the goods receipt or delivery confirmation and the vendor invoice.

When all three documents agree, the invoice proceeds to approval. When they don’t, a discrepancy is flagged before money leaves the business. 3-way matching is one of the most effective controls for preventing overpayments, duplicate payments and payments for goods or services never received.

Why 3-way matching matters

A vendor submits an invoice for 500 units at $12 each totaling $6,000. The purchase order on file is for 400 units at $11.50 each. The goods receipt shows 380 units were actually delivered. Without a matching process, that invoice gets approved and paid at $6,000. The company overpays for units it didn’t order, at a price it never agreed to, for items it hasn’t fully received.

Without 3-way matching, AP teams rely on manual review and individual judgment – which creates control gaps that scale with invoice volume. With 3-way matching, every payment is validated against a procurement record and a receipt confirmation before money leaves the business.

How 3-way matching works

Each document in a 3-way match plays a distinct role – and the control only works when all three are accurate, timely and reconciled against each other.

The purchase order

The purchase order is issued by the buyer to the vendor, authorizing the purchase of specific goods or services at an agreed price and quantity. It establishes the contractual baseline against which the invoice and receipt are compared. If no PO exists for an invoice, the invoice is typically flagged as an exception requiring additional authorization.

The goods receipt

The goods receipt records that the ordered items were actually received by the buyer. It confirms quantity, condition and delivery date. In service-based purchases, a service confirmation or acceptance document serves the same purpose. The goods receipt is what prevents payment for items that were ordered but never arrived.

The vendor invoice

The vendor invoice is the billing document submitted by the supplier. In a 3-way match, the invoice amount, item descriptions and quantities are compared against both the PO and the goods receipt. Discrepancies – a price that differs from the PO, a quantity that exceeds what was received – trigger an exception that must be resolved before payment is released.

2-way vs. 3-way matching

A few of the core differences between 2-way matching and 3-way matching is that 2-way matching compares only the purchase order and the vendor invoice while 3-way matching adds the goods receipt.

2-way matching is simpler and works well for recurring service payments or low-risk vendors, 3-way matching provides stronger control for physical goods, large purchases or high-fraud-risk vendor categories.

Many companies use both: 3-way matching for goods-based purchases above a dollar threshold and 2-way matching for pre-approved service contracts or small-dollar invoices.

Why teams struggle with 3-way matching

Manual matching works at low volume. As invoice counts grow, the gaps tend to multiply faster than headcount can cover them.

• POs are missing or created after the fact. When purchasing bypasses the PO process, AP has nothing to match against. Retroactive POs undermine the control entirely.
• Goods receipts aren’t recorded at the time of delivery. If receiving teams log receipts days or weeks late, invoices arrive before the match data exists and AP is forced to approve on incomplete information.
• Line-item mismatches require manual investigation. A price variance of a few cents or a quantity off by one still triggers an exception. When every mismatch lands in an inbox, small discrepancies consume time that should go toward resolving real problems.
• Tolerance thresholds aren’t defined. Without agreed variance limits, every minor discrepancy escalates to a human. Teams end up reviewing invoices that should auto-approve.
• ERP data is fragmented or inconsistently structured. Matching requires that PO, receipt and invoice data share common fields and formats. When they have different unit descriptors, mismatched vendor IDs or inconsistent coding, automated matching breaks down.‍
• Exception handling lacks context. An invoice flagged for mismatch is only useful if the reviewer can see the relevant PO, the receipt record and the variance in one place. When that context is spread across systems, resolution slows and errors happen.

How teams improve 3-way matching

Improving 3-way matching means making the control systematic rather than manual. Here’s how finance teams build a reliable AP process:

1. Require POs for all goods-based purchases above a threshold: Establish a policy that no invoice above a defined dollar amount can be processed without a corresponding purchase order in NetSuite.
2. Record goods receipts in the ERP at the time of delivery: Train intake teams to enter goods receipts into NetSuite when items arrive, so the matching data exists before the invoice arrives.
3. Automate the match between invoice, PO and receipt: Use invoice capture tools that compare invoice line items against open PO and goods receipt records automatically, flagging discrepancies without manual review of every transaction.
4. Define tolerance thresholds for minor discrepancies: Set acceptable variance ranges – for example, within 2% of the PO amount – so invoices with minor discrepancies can be approved automatically rather than requiring human review for every small difference.
5. Route matched invoices directly to the approval workflow: Invoices that pass matching should proceed to approval automatically, without an additional manual step by the AP team.
6. Handle exceptions in a structured queue with context visible: Invoices that fail matching should route to an exception queue that shows the discrepancy, the relevant PO and receipt data and suggested resolution steps – not just a flag in an inbox.

How ZoneCapture automates 3-way matching

ZoneCapture automates 3-way matching directly inside NetSuite. Invoices are captured via OCR, matched automatically against NetSuite PO and goods receipt records, and exceptions are routed to a structured queue for review. Matched invoices proceed directly to the approval workflow without manual intervention. Key features include:

• OCR invoice capture: Extracts line-item data from invoices automatically, with no manual data entry required
• Automated 3-way matching: Compares invoice amounts, quantities and item descriptions against open POs and goods receipts in NetSuite
• Exception queue with context: Flags discrepancies and surfaces the relevant PO and receipt data alongside each exception, so reviewers can resolve issues without switching systems
• Configurable tolerance thresholds: Sets acceptable variance ranges so minor discrepancies approve automatically rather than routing to a human
• Native NetSuite workflow integration: Matched invoices feed directly into NetSuite approval workflows, with no middleware or external handoff
• Duplicate detection: Identifies duplicate invoices based on transaction patterns before payment is released

‍Book a demo to walk through how ZoneCapture works inside NetSuite.