Three-Way Matching in Accounts Payable: How It Works and Why It Matters

What Is Three-Way Matching?

Three-way matching is a verification process in accounts payable that compares three documents before authorizing a payment: the purchase order (PO), the goods receipt (also called a receiving report), and the supplier's invoice. The purpose is straightforward — confirm that the organization received what it ordered, at the price it agreed to, and that the invoice accurately reflects both.

When all three documents align, the invoice is cleared for payment. When they don't, the transaction is flagged as an exception and routed for investigation.

This control exists because paying invoices without verification exposes the organization to overpayment, payment for goods never received, pricing errors, and outright fraud. Three-way matching is one of the most fundamental internal controls in financial operations, and it has been a cornerstone of AP best practices for decades. Understanding how it works — and where it breaks down — is essential for any finance team managing significant payables volume.

The Three Documents

Each document in the three-way match serves a distinct purpose and originates from a different source, which is precisely what makes the control effective.

Purchase Order (PO)

The purchase order is issued by the buying organization to the supplier. It specifies what is being ordered, in what quantity, at what unit price, and under what terms. The PO represents the organization's intent and commitment — it is the authoritative record of what was agreed upon before goods or services were delivered.

Goods Receipt (Receiving Report)

The goods receipt is generated internally when the ordered items are physically received at the warehouse, dock, or delivery point. It records what actually arrived: item descriptions, quantities, condition, and the date of receipt. For services, this may take the form of a service entry sheet or completion confirmation from the project manager.

Supplier Invoice

The invoice is submitted by the supplier requesting payment. It lists the items or services delivered, quantities, unit prices, applicable taxes, and the total amount due. The invoice is the supplier's claim — it represents what they believe they are owed.

The Three-Way Matching Process Step by Step

Step 1: PO Lookup

When an invoice arrives, the AP system (or clerk, in manual environments) identifies the corresponding purchase order using the PO number referenced on the invoice. If no PO number is present, or if the PO number is invalid, the invoice is flagged immediately — this is one of the most common exception types.

Step 2: Goods Receipt Verification

Next, the system checks whether a goods receipt exists for the referenced PO. If the goods have not been received — or if the receipt has not been recorded in the system — the invoice cannot be matched. Invoices that arrive before the goods receipt is posted are a frequent source of processing delays, particularly in organizations where warehouse staff are slow to confirm receipt in the ERP.

Step 3: Line-Item Comparison

The system compares each line item across all three documents. The key fields checked include:

• Item description or part number — Does the invoice reference the same items as the PO and receipt?
• Quantity — Does the invoiced quantity match the ordered quantity and the received quantity?
• Unit price — Does the invoiced price match the PO price?
• Extended amount — Does the line total (quantity x price) calculate correctly?
• Tax and freight — Are taxes and shipping charges consistent with the PO terms?

Step 4: Tolerance Check

Perfect matches are ideal but not always realistic. Minor discrepancies arise from rounding, unit-of-measure conversions, freight estimates, and tax calculations. Rather than flagging every penny-level variance, organizations define tolerance thresholds — acceptable deviation ranges within which the system will auto-approve the match.

Step 5: Exception or Approval

If all line items fall within tolerance, the invoice is approved for payment — often without any human involvement. If one or more items fall outside tolerance, the invoice is routed to an exception queue for manual review and resolution.

Two-Way, Three-Way, and Four-Way Matching Compared

Not all invoices require the same level of verification. Organizations typically use different matching levels depending on the transaction type, risk profile, and dollar amount.

Two-Way Matching

Two-way matching compares only the purchase order and the invoice. It verifies that the invoiced prices and quantities match what was ordered but does not confirm that the goods were actually received. Two-way matching is faster and simpler but offers weaker controls. It is commonly used for services, subscriptions, and low-value repeat purchases where receipt confirmation adds little value.

Three-Way Matching

Three-way matching adds the goods receipt to the comparison, confirming that items were not only ordered and invoiced but actually received. This is the standard for most PO-backed purchases of physical goods and is required by most internal audit frameworks.

Four-Way Matching

Four-way matching introduces a fourth element: the inspection or quality acceptance report. This is used in industries where incoming goods must pass quality inspection before they are accepted — manufacturing, pharmaceuticals, aerospace, and food production, for example. The invoice is not approved until the goods have been received and inspected and accepted.

| Matching Type | Documents Compared | Typical Use Case | |---|---|---| | Two-way | PO + Invoice | Services, subscriptions, low-risk items | | Three-way | PO + Goods Receipt + Invoice | Standard goods procurement | | Four-way | PO + Goods Receipt + Inspection + Invoice | Regulated industries, quality-critical goods |

Tolerance Thresholds: How They Work

Tolerance thresholds define the acceptable variance between matched documents. They prevent minor, immaterial discrepancies from generating exceptions that consume AP staff time without adding control value.

Common Tolerance Configurations

• Absolute amount: The variance must be within a fixed dollar amount (e.g., $10 or $50 per line item).
• Percentage: The variance must be within a percentage of the PO amount (e.g., 2% or 5%).
• Combined: Both an absolute and percentage threshold apply, and the tighter constraint governs.

Setting Appropriate Thresholds

Setting tolerances is a balancing act. Too tight, and the system generates excessive exceptions — false positives that waste AP staff time and create approval fatigue. Too loose, and meaningful discrepancies slip through, undermining the purpose of the control.

Most organizations set tolerances between 1-5% or $5-$50 per line, depending on the commodity category and supplier risk profile. High-value, tightly specified items (precision components, for example) warrant tighter tolerances than office supplies or maintenance materials.

Tolerances should be reviewed periodically. If exception rates are running above 20-25%, the thresholds may be too tight — or the upstream processes (PO accuracy, goods receipt timeliness) may need attention.

Common Three-Way Matching Exceptions

Exceptions are the cost center of the matching process. Each exception requires investigation, communication, and resolution — all of which consume time and delay payment. The most common exception types include:

Quantity Variances

The invoiced quantity doesn't match the received quantity. This happens when suppliers ship partial orders, when receiving staff miscounts, or when the goods receipt hasn't been posted yet. Partial shipments are a particularly common source, especially for large orders fulfilled over time.

Price Variances

The invoiced price differs from the PO price. This may reflect legitimate price changes (raw material surcharges, for example), negotiated amendments that weren't updated in the PO, or simple errors on either side. Price variances are the most contentious exception type because resolving them often requires back-and-forth with both the supplier and the internal buyer.

Missing Goods Receipts

The invoice references a PO, but no goods receipt has been recorded. This is almost always a timing or process issue — the goods arrived but the warehouse hasn't confirmed receipt in the system. It is one of the most frustrating exception types because the AP team cannot resolve it independently; they must chase the receiving team.

PO Not Found

The invoice references a PO number that doesn't exist in the system, or references no PO at all. This typically indicates either a non-PO purchase (which should follow a different approval path) or an error in the PO reference on the invoice.

Manual vs. Automated Three-Way Matching

Manual Matching

In a manual environment, an AP clerk pulls up the PO, locates the goods receipt (possibly a paper document from the warehouse), and compares each line item against the invoice by hand. This process takes an average of 10-15 minutes per invoice for straightforward matches and can take significantly longer for multi-line invoices or those with exceptions.

Manual matching does not scale. As invoice volumes grow, organizations either add headcount or let invoices age in a backlog — both of which are expensive outcomes.

Automated Matching

Automated matching systems perform the three-way comparison instantly upon invoice data capture. The system retrieves the PO and goods receipt from the ERP, compares all relevant fields against configured tolerance rules, and either auto-approves the invoice or routes it to the appropriate exception handler.

The impact is significant. Organizations that automate three-way matching typically see:

• Exception resolution time reduced by 50-70%, because the system provides all relevant context to the reviewer upfront rather than requiring manual document retrieval
• Touchless processing rates of 40-70% for PO-backed invoices, meaning those invoices flow from receipt to payment approval without any human intervention
• Matching cycle time reduced from days to minutes for clean invoices

For a broader view of how matching fits into the full invoice lifecycle, see our accounts payable process guide. For organizations already looking at automation, our analysis of touchless invoice processing covers the technology stack and implementation considerations in detail.

How Automation Handles Exceptions

Automation doesn't eliminate exceptions — it makes them faster and cheaper to resolve. Here's how:

Intelligent Routing

Automated systems route exceptions to the right person based on the exception type, the commodity category, the dollar amount, and the business unit. A price variance on a raw materials invoice goes to the commodity buyer. A missing goods receipt goes to the warehouse supervisor. This targeted routing eliminates the "who should handle this?" delay that plagues manual environments.

Context-Rich Exception Workbenches

Rather than asking the reviewer to pull up multiple documents and compare them manually, automated systems present a consolidated view: the invoice, PO, and goods receipt side by side, with the specific variance highlighted. Supporting documents (contracts, amendment records, delivery notes) are linked directly. This reduces investigation time from minutes to seconds for straightforward cases.

Automated Communication

When exceptions require supplier input — a corrected invoice, a credit memo, a price confirmation — automated systems can generate and send the request directly, track the response, and re-match the invoice once the issue is resolved. This eliminates the email tag and manual follow-up that typically extends exception resolution by days or weeks.

Learning and Pattern Detection

Advanced matching systems track exception patterns over time. If a particular supplier consistently invoices at prices higher than the PO, the system flags the pattern for procurement review. If a specific commodity category generates disproportionate quantity variances, it may indicate a systemic issue with how POs are written or how goods are received. This pattern detection turns exception data from a cost into an intelligence asset.

Building a Better Matching Process

For organizations looking to improve their three-way matching outcomes, the highest-impact actions are:

1. Improve PO compliance. The single biggest driver of matching exceptions is invoices without valid POs. Enforce PO requirements at the requisition stage, not at the invoice stage.

2. Accelerate goods receipt posting. Work with warehouse and receiving teams to ensure goods receipts are posted within 24 hours of delivery. Real-time receipt confirmation via mobile devices eliminates the "missing GR" exception entirely.

3. Right-size your tolerances. Analyze your current exception data. If most exceptions are resolving within tolerance after investigation, your thresholds are too tight. If meaningful variances are slipping through, they're too loose.

4. Automate where the volume is. Start with your highest-volume PO categories. Automating three-way matching for even your top 10 suppliers by volume can eliminate a disproportionate share of manual matching effort.

5. Measure and report. Track your match rate (first-pass matches as a percentage of total PO invoices), your exception rate by type, and your average exception resolution time. These metrics make improvement visible and drive accountability.

Three-way matching is not glamorous. It is, however, one of the most effective controls in the AP toolkit — and one of the areas where automation delivers the most immediate, measurable returns. Organizations that get matching right protect themselves from overpayment, accelerate their invoice cycle times, and free their AP staff to focus on higher-value work.