Blog · Nov 17, 2026
Three-Way Matching: Invoice, Purchase Order and Receipt
Nace.AI
Nace Document Intelligence, the layer that reads your files
Generally available. Top-tier parsing accuracy at about half the cost.
Three-way matching is the accounts payable check that compares a supplier's invoice with the purchase order and the goods receipt, also called a receiving report. It checks whether the business is being billed for what it ordered and received, at the agreed price, before an invoice goes forward for approval.
PO
Purchase order
What was authorized?
- Supplier
- Items
- Quantities
- Agreed prices
- Terms
Receipt
Goods receipt
What arrived?
- PO reference
- Items
- Quantities delivered
- Receipt date
Invoice
Invoice
What does the supplier want paid?
- Invoice number
- Line items
- Quantities
- Unit prices
- Charges and total
Compared between each pair
PO and Invoice
- Supplier
- Items
- Quantity
- Unit price
Receipt and Invoice
- Items
- Quantity received vs. billed
PO and Receipt
- PO reference
- Items
- Quantity ordered vs. received
What the three documents tell you
- Purchase order (PO): the supplier, items, quantities, agreed prices and terms approved by the buyer.
- Goods receipt or receiving report: the items and quantities the receiving team recorded as delivered, with the receipt date and PO reference. Here, “receipt” means evidence of delivery, not proof of payment.
- Invoice: the supplier's request for payment, including invoice number, line items, quantities, unit prices, charges and total.
Match the supplier and PO reference first, then compare each line. Check units of measure too: ten boxes and ten individual items are not necessarily the same quantity. Review tax, freight and other charges separately against the agreed terms. Matching totals alone can conceal an overcharge on one line offset by an undercharge on another.
Two-way vs. three-way vs. four-way matching
Two-way matching
Checks: Invoice and purchase order.
AddsDoes the bill agree with the order?
Three-way matching
Checks: Invoice, purchase order and goods receipt.
AddsWere the billed goods received?
Four-way matching
Checks: Those three plus inspection or acceptance evidence.
AddsWere the received goods accepted after inspection?
Two-way matching does not independently confirm delivery. Three-way matching adds that evidence. Four-way matching is useful when delivery alone is insufficient, such as when goods need a quality inspection before acceptance. The appropriate control depends on what you buy and your approval policy.
A three-way matching example
Suppose a PO covers paper and folders. The receiving team records the full delivery. The invoice uses the agreed price for paper but a higher price for folders. These illustrative amounts exclude tax and freight.
Paper
- Purchase order
- 20 boxes × $25$500
- Receiving report
- 20 boxesreceived
- Invoice
- 20 boxes × $25$500
- Result
- Match
Folders
- Purchase order
- 10 packs × $8$80
- Receiving report
- 10 packsreceived
- Invoice
- 10 packs × $9$90
- Result
- Price mismatch$10 over PO
- Order total
- $580
- Invoice total
- $590
- Difference
- $10 over PO; invoice held
The invoice totals $590 against a $580 order. All quantities match; the folder price does not. With no permitted price variance, AP holds the invoice for review. The buyer checks whether a price change was authorized. If not, AP requests a correction through its normal supplier process. The reviewer records the resolution before approving the invoice.
Tolerances: decide what counts as a mismatch
A tolerance is a documented allowance for a difference, such as a small rounding variance. It should specify the field, the permitted amount or percentage, and who can authorize an exception. There is no single tolerance suitable for every purchase.
For example, a policy might allow a line-price difference only when it is both below a percentage limit and below a currency limit. Specify whether the check applies to each line or the whole invoice. Otherwise, several small differences can add up without attracting attention.
Tolerances don't have to be symmetric. Many companies accept an invoice priced below the PO without review but hold anything above it. Quantities need the same thought: some suppliers ship a few extra units at no charge, so the receipt can show more than the PO while the invoice bills only what was ordered. Decide whether that over-receipt is accepted or reviewed.
Keep price and quantity tolerances separate. A price allowance should not excuse an unreceived quantity, a missing receipt or a suspected duplicate.
Control who can change the tolerances. An auditor will ask who approves an exception, and also who can edit the tolerance values in the system. Restrict that to a few administrators, keep it separate from the people who process invoices, and log every change with who made it and when.
Do clean matches need a person to approve them?
It is a policy choice. Clean matches within documented tolerances can be posted automatically. Exceptions, non-PO invoices and anything over set value limits go to a person. In practice, mid-size and larger companies running ERP systems such as SAP or Oracle often post matched invoices and release them for payment automatically, blocking only those outside tolerance. Smaller teams often post every invoice by hand and resolve even small differences themselves.
Common mismatches and what to check
Price mismatch. The invoice unit price differs from the PO. Check the latest authorized order revision, discounts and units of measure. Do not change the PO merely to make the invoice pass.
Quantity mismatch. The supplier bills for more units than the receipt supports. Check whether another delivery was recorded elsewhere, whether goods were returned, and whether the invoice uses different pack sizes.
Missing receipt. The invoice and PO agree, but there is no receiving record. Ask the receiving team to confirm delivery and record the evidence. The supplier's invoice alone is not confirmation that your business received the goods.
Invoice before delivery. Suppliers often invoice when they ship, so the invoice can arrive before the goods are received. Hold the invoice rather than paying it, and rematch it when the receipt is recorded. If no receipt appears within a set period, treat it as a missing receipt and confirm with receiving and the buyer. Watch payment terms while it waits, so a valid invoice isn't paid late.
Partial delivery. A PO for 100 units may have a receipt for only 60. An invoice for those 60 can match that delivery; an invoice for 100 needs review. Track cumulative receipts and quantities already invoiced so the next bill does not reuse the same 60 units as evidence.
Duplicate invoice. A bill can match the PO and receipt and still have been submitted before. Check invoice history separately, using supplier identity, invoice number, amount and dates. Formatting changes in an invoice number should not hide a possible duplicate. A repeated amount alone does not prove duplication.
The workflow: capture, extract, match, review and approve
- Capture the documents. Bring together the invoice, authorized PO and relevant receiving records. Keep the originals and their references together.
- Extract the fields. Read supplier details, document numbers, dates, currencies and line items. Preserve a link from each extracted value to its source so someone can verify it.
- Match the records. Compare corresponding lines, prices and received quantities under the agreed tolerances. Include prior invoices, partial receipts and returns where relevant. Run a separate duplicate check.
- Flag exceptions. Name the difference precisely: “invoice says 100; receipt supports 60” is more useful than “match failed.” Route missing receipts to receiving, price questions to purchasing and suspected duplicates to AP.
- Have a person resolve exceptions. The responsible team checks the source documents and resolves the discrepancy. Record any corrected invoice, approved order change or authorized exception, then repeat the affected checks.
- Approve. Follow company policy: clean matches within tolerance can be posted automatically, while exceptions, non-PO invoices and anything over set value limits need an authorized person. Keep the approval, or the rule that approved it, with the supporting records. Payment remains a separate process.
Documents and checks
- CaptureInvoice, PO and receiving records
- ExtractEach value linked to its source
- MatchLines, prices and quantities
- Flag exceptionsName the exact difference
Exceptions go to their owner
- Missing receipt goes to Receiving
- Price question goes to Purchasing
- Suspected duplicate goes to AP
People
- Human reviewResolve and record, then recheckPerson
- ApproveExceptions and over-limit invoicesPerson
Later, separately
Payment
Payment remains a separate process.
Where manual matching breaks down
The arithmetic is often straightforward. Finding the right evidence is harder. An invoice arrives by email, the PO lives in the purchasing system and the receipt sits in a warehouse record. AP then has to decide whether a blank field means “not received” or simply “not entered yet.”
Rekeying adds another failure point. A wrong decimal, lost invoice reference or box-to-unit conversion can create a false mismatch. Spreadsheets also make it difficult to see which receipts have already supported earlier invoices against the same order.
During a transactional audit, a reviewer needs to reconstruct why an invoice was approved. A spreadsheet cell marked “OK” is weak evidence on its own. Keep the underlying documents, differences found, reviewer decisions and approval history connected to the transaction. For invoices posted automatically, keep the tolerance rule that applied and the log of changes to it.
How automation helps, with people owning the exceptions
Start with document extraction, then apply matching checks. These are separate jobs: reading a price correctly does not establish that the price was authorized.
Nace Document Intelligence can parse, split, classify, extract and ground document information with source citations. For an AP reviewer, that means an extracted value can be checked against the place it came from. Missing or ambiguous values should go to review rather than become assumed matches.
Drex for Document Processing checks the document reading against the page image. The linked guide explains that reading and correction process; it is distinct from comparing an invoice with a PO and receipt.
For the matching stage, Nace's accounting workflow describes invoice, PO and receipt extraction and comparison, with Drex scoring three-way matches and flagging exceptions for the team to review. Clean matches are queued for approval. See what a decision model is for how Drex returns probabilities over defined options.
Use those capabilities within a workflow that gives a person the original evidence, the specific discrepancy and responsibility for resolving it. Keep arithmetic and tolerance rules explicit, set in policy which matches can post without review, and keep a person on every exception. Automation is most useful when it reduces the time spent finding and reading documents while leaving a clear record of the decision.
Frequently asked questions
Is three-way matching the same as invoice approval?
No. Matching checks whether the invoice agrees with the order and receiving evidence. Approval is the authorized decision to accept the invoice under company policy. A successful match supports that decision. Many companies let clean matches within documented tolerances post automatically, but that is an approval policy the company sets, not something matching decides on its own.
Can you three-way match without a purchase order?
Not in the usual sense: one of the three records is missing. Route a non-PO invoice through your documented non-PO approval process instead of treating it as a successful three-way match.
How do you match service invoices?
Use evidence that the service was delivered, such as approved timesheets, milestone acceptance or a service entry record, in place of a warehouse receipt. Compare it with the order or agreement and the invoice under your service approval policy.
What happens when goods arrive in several deliveries?
Match each bill against the relevant receipts and the remaining order balance. Track what has already been invoiced, plus returns or credits, so that one delivery does not support multiple bills for the same goods.
Does three-way matching catch every duplicate or fraudulent invoice?
No. A duplicate can agree with a real PO and receipt, and a perfectly matched invoice can still be paid to the wrong account if the supplier's bank details were changed fraudulently. Matching needs other controls alongside it: invoice-history checks for duplicates, verification of any change to supplier bank details through a known contact (not the email or letter requesting it), restricted and logged access to supplier records, and separation of purchasing, receiving and approval responsibilities.
Where should an AP team start with automation?
Choose a recurring invoice type with reliable POs and receiving records. Agree on tolerances and exception owners, then compare automated results with the team's review. Expand only when reviewers can verify the evidence and explain the outcomes.
