3-Way Matching in Accounts Payable

3-way matching is an accounts payable control used to verify supplier invoices before payment. It compares three documents: the purchase order, the supplier invoice, and the goods receipt note, also known as a GRN or receiving report.

The purchase order shows what the business approved for purchase. The GRN confirms what was actually received. The supplier invoice shows what the vendor is requesting payment for.

A 3-way match confirms that all three records agree before the invoice is approved.

In simple terms, the business is checking three questions.

Was it ordered?

Was it received?

Was it billed correctly?

If the answer is yes, the invoice can move forward. If the answer is no, accounts payable needs to investigate the discrepancy before payment is released.

This process is especially important for businesses handling physical goods, inventory, freight, materials, spare parts, project purchases, or any procurement workflow where received quantity matters.

Most invoice errors are not dramatic. They are usually small differences that become expensive when they repeat across hundreds or thousands of transactions.

A supplier may invoice for 100 units when only 80 were received. A price may differ from the approved PO. A GRN may be missing. A duplicate invoice may enter the workflow. Freight, tax, or additional charges may not match the agreed terms.

3-way matching gives accounts payable teams a structured way to catch these issues before payment.

It helps businesses reduce overpayments, avoid duplicate payments, catch billing errors, prevent invoice fraud, and maintain better control over cash flow. It also gives finance teams a clearer audit trail because each payment decision is backed by source documents.

The benefit is not only financial control. It is also operational control.

When AP teams know exactly why an invoice is approved, held, or rejected, fewer issues disappear into email threads. Procurement, receiving, operations, and finance can work from the same record instead of chasing separate versions of the truth.

Not every invoice needs the same level of validation. The right matching method depends on the purchase type, risk level, document availability, and internal control policy.

2-way matching compares the supplier invoice with the purchase order. It checks whether the vendor billed the agreed items, quantities, and prices. It is often suitable for service-based suppliers or lower-risk purchases where a receiving document is not required.

3-way matching adds the goods receipt note. This makes it more reliable for goods-based transactions because it confirms that the company actually received what the vendor billed.

4-way matching adds an inspection report. This is useful when goods must pass a quality check before payment. It is common in regulated industries, manufacturing, pharmaceuticals, or other environments where condition and compliance matter as much as quantity.

For most AP teams, 3-way matching is the practical middle ground. It provides stronger protection than 2-way matching without adding the heavier quality-control requirements of 4-way matching.

A clean 3-way match depends on accurate document capture and consistent data.

The purchase order includes supplier details, item descriptions, quantities, agreed prices, payment terms, delivery details, and the PO number. It is the baseline for what the company authorized.

The goods receipt note confirms delivery. It records what was received, when it was received, and sometimes whether the goods were complete, damaged, partial, or accepted under certain conditions.

The supplier invoice contains the amount the vendor wants to be paid. It includes invoice number, vendor information, PO reference, line items, quantities, unit prices, taxes, freight, discounts, and total amount due.

During matching, AP teams compare shared fields across these documents. The most common fields include PO number, vendor name, item description, quantity, unit price, tax, freight, total amount, and receipt status.

A typical 3-way matching process begins when the supplier invoice arrives.

First, AP captures the invoice and identifies the PO number. Then the corresponding purchase order is retrieved from the ERP, procurement system, or purchasing record. The receiving report or GRN is also retrieved, usually from operations, warehouse, logistics, or inventory.

Next, the invoice is compared against the PO and GRN. If the supplier billed the same items, quantities, and prices that were ordered and received, the invoice can proceed for approval.

If something does not match, the invoice becomes an exception.

For example, if the invoice quantity is higher than the received quantity, AP may route the issue to receiving or operations. If the invoice price differs from the PO price, procurement may need to review the supplier agreement. If the invoice lacks a valid PO, admin or finance may need to investigate.

The process usually ends in one of four outcomes: approval, hold, rejection, or correction.

A mature AP process records each action so the business can see who reviewed the invoice, what was changed, what was approved, and why the final decision was made.

Most 3-way matching issues fall into predictable categories.

Quantity mismatches happen when the invoice bills for more or fewer items than were received. This is common with partial deliveries, backorders, damaged goods, or delayed receiving updates.

Price mismatches occur when the invoice unit price does not match the PO. This may be caused by supplier error, outdated pricing, freight adjustments, discounts, or contract changes.

Missing GRNs create delays because AP cannot confirm whether the goods were received. In some cases, the goods have arrived but the receiving document has not been posted yet.

Duplicate invoices occur when a supplier resubmits an invoice or sends the same invoice through multiple channels.

PO mismatches happen when the invoice references the wrong PO, no PO, or multiple POs

Tax, freight, and additional charge mismatches also create review work, especially when these charges are handled differently across vendors or regions.

None of these problems are unusual. They are part of normal AP operations. The issue is how quickly the business can identify, assign, and resolve them.

A tolerance is an approved variance between documents.

For example, a company may allow a small price variance between the PO and invoice, or a small quantity variance depending on the item category. Tolerances prevent harmless differences from blocking payment while still flagging material discrepancies.

Common tolerance rules include:

Tolerance rules need balance. If they are too strict, AP teams spend too much time reviewing minor issues. If they are too loose, payment risk increases.

Exception handling is the next layer. When an invoice falls outside tolerance, the system or AP team should route the issue to the right owner.

A quantity issue may go to operations. A price issue may go to procurement. A duplicate invoice may stay with finance. A missing document may go to admin or receiving.

This routing matters because AP often identifies the issue but does not always own the answer.

Manual matching becomes difficult as invoice volume grows.

At low volume, AP teams can search for documents, compare line items, and follow up manually. At higher volume, the same process creates bottlenecks.

Documents may sit across inboxes, shared drives, ERP exports, physical files, and supplier portals. GRNs may be delayed. POs may be updated after the invoice arrives. Approvers may lack context. Exceptions may be discussed outside the system, leaving gaps in the audit trail.

Manual processing also carries a direct cost, on an average around $12 to $30 per invoice. It also points to common issues such as delays, human error, misplaced documents, late payments, and increased AP workload.

The hidden cost is attention.

AP teams spend time checking documents that already match instead of reviewing the invoices that actually need judgment. That is where automation starts to create value.

Automated 3-way matching does not change the control principle. It changes the workload.

Instead of AP manually comparing every document, automation captures invoice data, retrieves PO and GRN data, applies matching rules, checks tolerances, and flags exceptions.

Clean invoices can move forward faster. Exceptions are easier to review because the mismatch is already identified.

A strong automated matching workflow should support invoice capture from PDFs, emails, scans, and uploads. It should extract key fields from invoices and receiving documents. It should retrieve PO and GRN data from connected systems. It should compare fields at header and line-item level. It should apply tolerance rules, detect duplicates, route exceptions, maintain an audit trail, and prepare approved data for ERP or finance system updates.

This is where automation becomes more than OCR.

OCR reads the invoice. Matching validates it. Exception routing moves the issue to the right person. Audit trails preserve the decision. Reconciliation closes the loop after payment.

Wend AI helps AP teams validate invoices before payment by connecting invoices, purchase orders, and receipts in one structured workflow.

It scans supplier invoices and GRNs, extracts key data, compares invoice details with PO and receipt records, and flags discrepancies before approval.

For simple PO checks, Wend AI supports 2-way matching. For goods-based workflows, it supports 3-way matching by validating the invoice against both the purchase order and the goods received document.

Wend AI can help AP teams manage:

When a discrepancy appears, Wend AI can notify the appropriate department, such as procurement, operations, receiving, finance, admin, or sales, depending on who needs to resolve it.

That matters because invoice validation is rarely owned by one team alone. AP may control the payment process, but procurement owns supplier terms. Receiving confirms delivery. Operations may know why quantities differ. Finance needs the final record to be clean.

Wend AI helps connect those steps so clean invoices move forward and exceptions do not sit unresolved