Resources / 3 Way Matching Guide
3 Way Matching in Accounts Payable
A complete guide to three-way matching: what it is, why it matters, how to implement it, and how to automate the most time-consuming step in the process.
What is 3 way matching?
Three-way matching (also written as 3-way matching or 3 way match) is an accounts payable control that compares three documents before a payment is approved:
- Purchase Order (PO) — the document your company issued to the supplier, specifying what was ordered, the quantities, and the agreed prices.
- Supplier Invoice — the bill from the vendor requesting payment for goods or services delivered.
- Goods Receipt (GRN) or Delivery Note — the internal record confirming that the goods were physically received at your location, in the correct quantities and condition.
The goal is straightforward: all three documents must agree on the key fields (quantities, unit prices, totals, item descriptions) before AP releases payment. If any document disagrees, the invoice is flagged for manual review.
Why 3 way matching matters
Without matching controls, an AP department is exposed to several risks:
- Overpayment. A vendor invoices for 500 units but only delivered 400. Without comparing the invoice to the goods receipt, you pay for 100 units you never received.
- Price discrepancies. The PO says $12.50 per unit, but the invoice says $14.00. Without matching the invoice to the PO, the price increase goes unnoticed.
- Duplicate invoices. A vendor sends the same invoice twice. Without a matching process that tracks invoice numbers against POs, the duplicate gets paid.
- Fraud. A fictitious invoice from a non-existent vendor. If there is no PO and no goods receipt to match against, the fraudulent invoice can slip through.
- Audit failures. Auditors expect documented matching controls. Organizations without them face material weakness findings in SOX compliance, government contract audits, and financial statement audits.
2 way vs 3 way vs 4 way matching
| Type | Documents compared | Best for |
|---|---|---|
| 2 way match | PO + Invoice | Services, subscriptions, and recurring bills where there is no physical delivery |
| 3 way match | PO + Invoice + Goods Receipt | Physical goods, inventory purchases, materials, supplies |
| 4 way match | PO + Invoice + Goods Receipt + Inspection Report | Regulated industries, government contracts, high-value materials requiring quality inspection |
Most small and mid-size businesses use 3 way matching as their standard AP control. Two-way matching is common for service invoices where there is nothing to physically receive. Four-way matching adds a quality inspection step and is typical in manufacturing, construction, and government procurement.
How 3 way matching works: step by step
Step 1: Issue the purchase order
The purchasing department creates a PO that specifies the vendor, item descriptions, quantities, unit prices, delivery date, and payment terms. This becomes the reference document for the entire matching process.
Step 2: Receive the goods
When the shipment arrives, the receiving team checks the delivery against the PO. They record what was actually received: quantities, item conditions, and any discrepancies. This creates the goods receipt note (GRN), sometimes called a receiving report.
Step 3: Receive the invoice
The supplier sends an invoice, usually by email as a PDF. The AP team needs to extract the data from this invoice: vendor name, invoice number, date, line items, quantities, unit prices, tax, and total amount. This is the step where most manual effort occurs.
Step 4: Match all three documents
Compare the PO, goods receipt, and invoice. The key fields to match are:
- Quantities: PO qty = GRN qty = Invoice qty
- Unit prices: PO price = Invoice price
- Line item descriptions: items match across all three
- Totals: calculated totals agree
- Vendor: same supplier across all documents
Step 5: Approve or flag
If all three documents match within tolerance (most organizations allow a small variance, typically 1-5%), the invoice is approved for payment. If there are discrepancies, the invoice is held for investigation. Common issues include partial shipments, price changes, and quantity errors.
The bottleneck: extracting invoice data
In practice, purchase orders and goods receipts are already digital. Your ERP or accounting system generates the PO, and your warehouse team logs the receipt. Both documents exist as structured data in your system.
The supplier invoice is the problem. It arrives as a PDF, often emailed, sometimes scanned. Before you can match it against the PO and GRN, someone has to manually key in the data: vendor, invoice number, date, every line item description, quantity, unit price, tax, and total.
For a single invoice with 5 line items, this takes 3-5 minutes of careful data entry. For a business processing 200 invoices per month, that is 10-17 hours of pure data entry before the matching process even begins.
This is the step that AI invoice extraction automates.
How SkipEntry automates invoice extraction for 3 way matching
SkipEntry handles the invoice data extraction step of the 3 way matching process. Instead of manually keying in invoice data, you upload the PDF and SkipEntry extracts:
- Vendor name, address, and contact details
- Invoice number and date
- PO number (if printed on the invoice)
- Every line item: description, quantity, unit price, and amount
- Subtotal, tax, shipping, and total
- Payment terms and due date
The extracted data is structured and ready to compare against your PO and goods receipt. SkipEntry also performs automatic math validation: it verifies that line items sum to the subtotal and that tax calculations are correct. Discrepancies are flagged before the data reaches your matching process.
No templates required
Unlike traditional OCR tools that require you to set up extraction templates for each vendor format, SkipEntry uses AI (Google Gemini, via Vercel AI Gateway) to read any invoice layout. A new vendor invoice works on the first upload without configuration.
Batch processing
Upload multiple invoices at once. SkipEntry processes them in parallel and returns structured data for each. For AP teams doing weekly matching runs, this turns hours of data entry into minutes of review.
Export to your accounting system
Extracted data can be exported as CSV, JSON, or directly to QuickBooks Online and Xero. The structured output integrates with whatever system your PO and GRN data lives in.
Common 3 way matching scenarios
Scenario 1: Perfect match
PO says 100 units at $10.00. GRN confirms 100 units received. Invoice bills for 100 units at $10.00, total $1,000.00. All three agree. Payment approved.
Scenario 2: Partial shipment
PO says 100 units. GRN records only 80 units received. Invoice bills for 100 units. The match fails on quantity. AP holds the invoice and contacts the vendor. Either the vendor corrects the invoice to 80 units, or the remaining 20 units are delivered.
Scenario 3: Price discrepancy
PO says $10.00 per unit. Invoice says $10.50 per unit. The match fails on price. AP investigates whether a price increase was negotiated after the PO was issued. If so, the PO may need amendment. If not, the vendor needs to reissue the invoice.
Scenario 4: No PO (non-PO invoice)
Some invoices, like utility bills, subscriptions, or one-time service charges, have no PO. These follow a 2 way match (invoice vs. approval) or go through a separate approval workflow. The invoice still needs to be extracted and validated.
Best practices for 3 way matching
- Set tolerance thresholds. Allow small variances (1-5% or a fixed dollar amount) to avoid flagging every rounding difference. Define thresholds by invoice value: tighter for large invoices, looser for small ones.
- Match at the line item level. Header-level matching (total only) misses per-item errors. Matching each line item to the corresponding PO line and GRN line catches quantity and price issues on specific items.
- Require PO numbers on invoices. Ask vendors to include the PO number on every invoice. This makes the matching lookup automatic instead of manual.
- Automate invoice data extraction. The single highest-ROI improvement is eliminating manual keying of invoice data. AI extraction tools like SkipEntry convert PDF invoices to structured data in seconds.
- Handle exceptions consistently. Define clear escalation paths for mismatches. Who resolves quantity issues? Who approves price variances? Document the process so it does not depend on one person.
- Track match rates. Measure what percentage of invoices match on the first pass. Industry benchmarks for automated matching are 70-85% straight-through processing. If your rate is below 50%, look at PO discipline and vendor compliance.
Frequently asked questions
What is 3 way matching in accounts payable?
3 way matching is an AP control that compares three documents before approving payment: the purchase order (what was ordered), the supplier invoice (what the vendor billed), and the goods receipt (what was actually received). All three must agree on quantities, prices, and totals.
What is the difference between 2 way and 3 way matching?
Two-way matching compares only the PO and invoice. Three-way matching adds the goods receipt to verify that items were physically received. Three-way matching is stronger for preventing overpayment on physical goods.
Can 3 way matching be automated?
Yes. POs and goods receipts are typically already digital in your ERP. The manual bottleneck is invoice data extraction. AI tools like SkipEntry extract structured data from PDF invoices, making the comparison step programmable.
What tolerance should I set for matching?
Common thresholds are 1-5% or a fixed dollar amount ($5-$50 depending on typical invoice size). Tighter tolerances catch more errors but increase exception volume. Start at 2% and adjust based on your exception rate.
Automate invoice data extraction for your 3 way matching process. 25 pages free.
Try SkipEntry freeAutomate the invoice side of 3 way matching
SkipEntry extracts line items, quantities, unit prices, and totals from any PDF invoice. 25 pages free, no credit card required.
Learn more about how SkipEntry works or see sample extractions