Ordered 500 units, received 450, invoiced for 500. Who catches that before it’s paid? In most finance teams, it’s purchase order (PO) matching: one of the quietest but most important controls in Accounts Payable.
In its simplest form, PO matching checks an invoice against its PO before payment.
2-way matching compares the invoice with the PO, while 3-way matching adds the goods receipt to confirm the delivery actually arrived.
3-way matching provides stronger protection against overpayment and fraud but relies on the goods receipt being logged promptly.
PO matching saves your company the cost of overpaying for products or services, and 3-way matching in AP stops you paying suppliers for deliveries that never arrived.
But matching is only as reliable as the data it runs on. Many false exceptions start with manual data entry errors or OCR misreads at intake, which is why accurate invoice capture is critical.
Key takeaways
PO matching, or purchase order matching, is a core AP workflow to make sure your business only pays for what was ordered, at the agreed price and, where required, what was received.
This step sits near the end of the procure-to-pay process, after the invoice is received and before payment is approved.
AP teams or automation software compare transaction documents to check that they align and to catch overpayments and other avoidable losses before money leaves the business.
If there are discrepancies, the invoice can be flagged as an exception for review. If everything falls within set tolerances, it can move to payment.
There are different types of PO matching, including 2-way, 3-way and 4-way, each named for the number of documents involved in the check.
2-way matching compares the PO with the invoice to check that the supplier name, unit prices, quantities and line totals agree within set tolerances.
It can’t confirm what was actually delivered, only that the supplier has billed in line with what was ordered.
2-way matching is well suited to spend with no physical delivery to confirm, such as services and subscriptions, or where the cost and effort of chasing a goods receipt isn’t justified, such as low-value, low-risk purchases.
3-way matching in AP builds on 2-way matching by cross-referencing the goods receipt as well as the PO and invoice.
Where 2-way PO matching gives clarity on what was ordered and the agreed price, 3-way invoice matching also confirms that what actually arrived matches the order.
This method is best suited to physical goods and high-value spend, where overpayment or short delivery could have a significant financial impact on your business.
A goods receipt note (GRN), known in the US as a receiving report, is a document that records exactly what was received in a delivery, giving AP teams proof of what actually arrived.
It’s usually created by the warehouse or receiving team, then used by AP teams and software for 3-way matching.
Information on a GRN can include:
Creating a GRN can hold up the AP process, as it relies on people outside the finance and AP teams to log the delivery.
If the invoice arrives before the GRN is logged, it can be flagged as an exception with nothing to match it against. If the receipt is never logged, the invoice can stay stuck indefinitely.
Once AP teams or software flag the exception, chasing and confirming the GRN can take days or weeks, leading to late payments and strained supplier relationships.
To avoid this, set clear deadlines for logging GRNs and back them up with automated reminders, so missing receipts don’t create a bottleneck of exceptions.
3-way matching within the procure-to-pay process consists of five steps:
| Dimension | 2-way matching | 3-way matching |
|---|---|---|
| Documents | PO and invoice | PO, GRN and invoice |
| What it confirms | The supplier has billed in line with the order | The supplier has billed in line with the order and the goods have been received |
| Best for | Services, subscriptions and low-risk spend | Physical goods, inventory and high-value spend |
| Fraud and overpayment protection | Moderate: can’t detect non-delivery | Strong: catches undelivered goods and short deliveries |
| Processing speed | Faster: fewer documents to wait for | Slower: can be delayed by late or missing GRNs |
| Admin effort | Lower: no goods receipts to chase | Higher: relies on GRNs being logged promptly |
| Typical exception causes | Price and quantity variances | Price and quantity variances, missing or late GRNs and partial deliveries |
Both 2-way and 3-way matching have their place. These three criteria can help you decide which suits each purchase:
3-way matching can still be relevant for service-based purchases if you can justify the extra cost and effort.
In place of a GRN, you can use a service-entry sheet, which records the hours or deliverables completed, or a requester confirmation, where the person who ordered the service confirms it was delivered as agreed.
2-way matching only confirms that the supplier charged what was originally agreed, not what actually arrived.
Inventory purchases require delivery confirmation to ensure that you’ve received the right amount. Without a GRN, you could end up paying for goods that were never delivered or only partially delivered.
2-way matching also provides limited audit assurance. Auditors look for evidence that your AP controls prevent financial leaks and that you only pay for goods you’ve received.
Without GRNs, it’s harder to prove that purchases and inventory are recorded accurately. A 3-way match creates a documented evidence trail for every purchase.
Misreads at intake can trigger false matching exceptions and hold up payments.
Xelix Capture is our invoice intake layer. It extracts invoice data in any layout with 99% extraction accuracy, and sends validated, structured data to the ERP or AP system where your matching runs.
Want to see it with your own invoices? Book your Capture demo today.
Book a demo
What is 4-way matching?
4-way matching goes a step further than 3-way matching by adding a quality inspection report alongside the PO, GRN and invoice.
This extra check is designed to give AP teams reassurance that they are paying for goods that arrived in the agreed condition and specification.
This level of checking is most common where goods are high value or heavily regulated and quality and compliance are critical, such as in pharmaceuticals and manufacturing.
Pre-set tolerances in PO matching allow invoices with small differences between documents to be approved, while anything outside these limits is flagged as an exception.
Tolerances are usually set for price and quantity, as fixed amounts or percentages. If the PO, GRN and invoice differ by less than the tolerance, the invoice isn’t flagged and can be approved despite the slight mismatch.
Getting the range right can be tricky. Set it too tight and small variations create a bottleneck of exceptions. Set it too broad and the business could see leakages.
Rather than using one set tolerance for every invoice, businesses should set separate tolerances for each type of spend and review them regularly.
This keeps the AP team from wasting time on exceptions that don’t materialise as real issues, while preventing overpayments and supplier disputes later down the line.
| Problem | Typical cause | Fix |
|---|---|---|
| Missing or late GRN | Receiving teams don’t record GRNs promptly | Agreed deadlines and automated chasers to receiving teams |
| Price variance | The PO isn’t updated after renegotiation | PO change controls and tolerances set by type of spend |
| Quantity variance | Supplier delivers the order in parts | Line-level matching that allows for partial deliveries |
| Unit of measure mismatch | Supplier bills in cases while the PO lists units | Unit of measure conversions set in item or supplier master data |
| Wrong or missing PO number | PO number is misread by the AP team or rigid OCR at capture or omitted by supplier | Accurate AI-automated capture and PO lookup by supplier and line items |
| Line items not extracted | Template-based OCR can't read varied invoice layouts | AI invoice capture that extracts line items in any layout |
| Duplicate invoice matched twice | Supplier resubmits or reformats an invoice | Automated duplicate checks before payment |
When an invoice falls outside tolerance, a consistent process helps AP teams resolve the exception quickly and avoid paying for errors.
Many failed matches trace back to data errors at intake rather than genuine supplier mistakes.
PO matching automation flags genuine discrepancies and reduces false ones.
That means fewer unnecessary payment delays and more time for AP teams to focus on genuine issues.
Effective automation starts with accurate header and line-level capture. Rather than just reading invoice totals, it reads the context of each line, so small variations in a supplier name, PO number or unit of measure are less likely to create a false mismatch.
AP automation can also look up the correct PO and supplier records in the ERP before matching, so each invoice is checked against the right documents and tolerances.
When a genuine exception arises, intelligent routing sends it straight to the right owner, so it’s resolved swiftly without AP having to chase.
In manufacturing and other high-volume goods environments, invoices often carry many line items, partial deliveries and unit of measure differences. That’s where line-level data quality matters most, because every misread line is a potential false mismatch.
Matching itself runs in your ERP or AP system. Xelix Capture, our invoice intake layer, focuses on the step before it: getting the invoice data right.
It extracts invoice data in any layout with 99% extraction accuracy, and works out of the box, with no training and no per-supplier setup. It sits in front of the ERP and downstream AP systems, so the system that runs your PO matching receives validated, structured data.
Capture also uses AI agents, which your AP team configures in natural language, to resolve exceptions in the extracted data before it reaches the ERP. Matching, and genuine discrepancies such as a short delivery or a price change, stay with your ERP and your team.
Convincing management to move to 3-way matching comes down to one question: are the added cost and effort justified by the losses it prevents?
The strongest argument is that 3-way matching stops businesses paying for goods they never received. 2-way matching checks that the invoice matches the terms agreed on the PO, but it has no way of verifying what actually arrived.
3-way matching checks each invoice against both the PO and goods receipt to catch short deliveries, non-deliveries and overbilling before money leaves the business, rather than relying on suppliers to issue a credit note after the fact.
3-way matching also strengthens records, creating a clear evidence trail for audits.
Automation reduces the extra effort. Invoices within set tolerances are approved automatically and false exceptions are cut, freeing up AP teams for higher-value work and reducing delays in the procure-to-pay process.
Xelix Capture, our invoice intake layer, delivers 99% extraction accuracy and works out of the box, so your PO matching starts from validated, structured invoice data. Find out more about Capture, our automated invoice intake layer or book a demo directly to see it on your own invoices.