Two-way and three-way matching explained

Invoice errors are one of the most common and costly problems in accounts payable. Duplicate payments, overpayments, and fraudulent invoices can slip through when there is no structured process for verifying what was ordered, what was received, and what is being billed. That is exactly where three-way matching and two-way matching come in. These are foundational controls in procurement and accounts payable that ensure every invoice is legitimate before payment is approved. Understanding how each method works, and when to use which, can make a real difference to the accuracy and efficiency of your finance operations.

How two-way and three-way matching work

At its core, invoice matching is the process of comparing key documents in the purchasing cycle to verify that an invoice is accurate and authorised before it gets paid. The number in the name tells you how many documents are being compared.

Two-way matching compares the purchase order (PO) with the supplier invoice. The system checks that the quantities, prices, and line items on the invoice align with what was originally ordered. If the details match within an agreed tolerance, the invoice is approved for payment. This approach is straightforward and works well for services or digital goods where there is no physical delivery to verify.

Three-way matching adds a third document to the comparison: the goods receipt note (GRN) or receiving report. So, the process checks the PO against the invoice and against the confirmation that goods or services were actually received. This additional step provides a much stronger control layer, making sure payment is only released when the order was placed, the goods arrived, and the invoice reflects both accurately.

Key differences between two-way and three-way matching

The most obvious difference is the number of documents involved, but the practical implications go further than that. Two-way matching is faster and simpler, which suits lower-risk purchases or scenarios where receipt confirmation is not practical. Three-way matching takes more steps but gives finance teams significantly more confidence that a payment is valid.

From a risk perspective, 3-way matching is the stronger control. It closes the gap that two-way matching leaves open: the possibility that goods were never delivered but an invoice was still submitted. Without a goods receipt check, a supplier could invoice for items that never arrived, and the invoice might still pass a two-way check. Three-way matching catches this.

There is also a difference in how each method handles exceptions. Two-way mismatches are typically price or quantity discrepancies between the PO and invoice. Three-way mismatches can also include receiving discrepancies, such as partial deliveries or damaged goods, which need to be resolved before payment proceeds.

When to use two-way vs. three-way matching

Choosing the right matching method depends on the nature of the purchase, the value involved, and the level of risk the organisation is willing to accept.

Two-way PO matching tends to work well for:

Service-based contracts where there is no physical delivery
Subscription or recurring payments with predictable amounts
Low-value purchases where the cost of additional verification outweighs the risk
Digital goods or software licences

Three-way matching is generally the better choice for:

Physical goods and inventory purchases
High-value or high-volume transactions
Situations where fraud risk or supplier error is a concern
Industries with strict compliance or audit requirements

Many organisations apply both methods depending on the transaction type, using two-way matching for services and three-way matching for goods. Setting clear policies around which method applies to which category of spend helps accounts payable teams work consistently and reduces the chance of errors slipping through.

Common matching errors and how to resolve them

Even with a well-designed matching process, discrepancies happen. Knowing the most common causes makes it easier to resolve them quickly and prevent them from recurring.

Price discrepancies

These occur when the unit price on the invoice differs from the agreed price on the PO. This can happen due to supplier pricing errors, outdated POs, or contract changes that were not reflected in the system. The resolution usually involves confirming the correct price with the supplier or procurement team and updating the PO before approving the invoice.

Quantity mismatches

A quantity mismatch means the invoice reflects a different number of units than what was ordered or received. In three-way matching, this could indicate a partial delivery or a receiving error. The accounts payable team should check the goods receipt record and coordinate with the warehouse or receiving team to confirm what actually arrived.

Missing or delayed goods receipts

One of the most frequent causes of holds in three-way matching is an invoice arriving before the goods receipt has been recorded in the system. This is not always a sign of a problem, but it does create a bottleneck. Encouraging timely receipt confirmation from operations teams, or setting up automated reminders, can significantly reduce this type of delay.

Duplicate invoices

Duplicate invoice submissions, whether accidental or intentional, are a common source of overpayment. A good invoice matching process should flag invoices with the same supplier, amount, and date automatically, preventing double payments before they happen.

Automating invoice matching in accounts payable

Manual invoice matching is time-consuming and prone to human error, especially as transaction volumes grow. Automating the process transforms what was once a labour-intensive task into a fast, consistent, and auditable workflow.

Automated invoice matching works by pulling data from the PO, invoice, and goods receipt into a central system and running the comparison automatically. Matched invoices are routed straight to payment approval, while exceptions are flagged for human review. This means the accounts payable team spends its time on genuine exceptions rather than manually checking every document.

Beyond speed, automation brings consistency. Rules are applied the same way every time, which reduces the risk of errors and makes it much easier to demonstrate compliance during audits. Every match and every exception is logged, creating a clear audit trail without any additional effort from the team.

We built our transaction matching capability in Aico to handle exactly this kind of complexity. It automates reconciliations and matching across systems, integrates directly with major ERP platforms like SAP, Oracle, and Microsoft Dynamics 365, and gives finance teams real-time visibility into what has been matched, what is pending, and what needs attention. For growing organisations looking to scale their finance operations without scaling their headcount, automated PO matching is one of the highest-impact improvements available.

Getting invoice matching right is not just about preventing errors today. It is about building a procurement and accounts payable process that can grow with the business, maintain strong controls, and free up finance professionals to focus on work that genuinely moves the organisation forward.