AiStaffo

Matching Invoices to Purchase Orders and Receipts Without an ERP

Stock photo: invoices, desk, filing folders
Photo: Zulfugar Karimov / Pexels

To match an invoice to a purchase order and receipt, check three things before paying. First, the supplier name, PO number and unit prices on the invoice must agree with the purchase order. Second, the quantity billed must not exceed the quantity your team recorded as received. Third, the difference between the documents must fall inside the tolerance you set in advance. Invoices that pass go to the payment list. Anything outside tolerance goes to an exception queue, where a named person decides. Without an ERP, you can run this with a PO log and a receiving log in spreadsheets, a shared invoice inbox, and an invoice reader that pulls out the key fields. Automation does the comparison and the routing. A person still approves exceptions and any change to a supplier's bank details.

In short

  • A three-way match checks the invoice against both the purchase order and the goods receipt before any payment is released.
  • Set price tolerance as both a percentage and a fixed amount, and keep quantity tolerance at or near zero for physical goods.
  • Route every mismatch to one exception queue with a reason code, an owner and a review date.
  • Keep a named person on exceptions, bank detail changes, new suppliers and payments above your limit.
  • If receipts are not recorded today, fix the receiving habit before building any automation.

Why unmatched invoices cost money

The first cost is handling. Parseur's 2026 AI invoice processing benchmark, which cites Ardent Partners' 2025 accounts payable research, puts manual processing at $12.88 to $19.83 per invoice and the industry average at $9.40. Those figures include staff time spent chasing exceptions, so the range is a fully loaded cost rather than a bank charge. A business that handles 100 invoices a month would spend roughly $1,288 to $1,983 a month on handling alone, using that benchmark's range.

The second cost is paying for the wrong thing. An invoice can look correct on its own and still be wrong against the order. The supplier may bill for goods that were never delivered, charge a price that was never agreed, or send the same invoice twice under a new number. A two-way match, which compares only the invoice with the purchase order, misses the first case because it never asks whether anything arrived. A three-way match adds the goods receipt, which records what physically came in.

The third cost is time. Bottomline's cost guide, citing Ardent Partners research dated 2024, says manual processing of a single invoice takes more than two business weeks from receipt to payment. Much of that delay is spent waiting for someone to find the PO or confirm delivery. Late payments also create calls and emails from suppliers, which is work nobody budgeted for.

Manual method against automated method

The table below shows where the work sits in each approach. The automated column does not remove the people. It moves the routine comparison into a tool and leaves judgement calls with a person.

StepManual, with email and spreadsheetsAutomated, with checks
Receiving the invoiceSomeone opens each email or photo and saves the fileInvoices arrive in one shared inbox or WhatsApp number and are saved to one folder
Finding the purchase orderSomeone searches old emails or a PO spreadsheet by handThe PO number on the invoice is looked up in the PO log
Checking deliverySomeone asks the warehouse or site whether goods arrivedThe receiving log is compared line by line with the invoice quantity
Price and quantity checkSomeone compares figures visually, usually line by lineA formula compares unit price and quantity against the tolerance rules
ExceptionsProblems sit in inboxes and are raised by chanceEach exception goes to a queue with a reason code, an owner and a date
Approval and paymentApproval by email reply, with no single recordMatched invoices go to a payment list; a named approver signs off and the decision is logged

Set the rules before you automate

Most of the value in a three-way match comes from the tolerance rules, and most of the mistakes come from setting them carelessly. A tolerance is the difference you accept without a person looking at it. Set one for price and one for quantity, and keep duplicate invoices and bank details outside any tolerance at all.

For price, use both a percentage and a fixed amount. A 2% tolerance on a unit price of $10 allows 20 cents a unit, which is harmless. The same 2% on a $50,000 order allows $1,000, which may not be harmless. One AP software vendor publishes a sample rule that auto-approves a price variance within 2% or $250, whichever is lower. That is an example to test against your own invoices, not a standard. A UK distributor and an Indian textile exporter will set different numbers because their unit costs and supplier terms differ.

For quantity, most businesses buying physical goods should allow little or no difference. If you receive 95 units and the supplier bills 100, the difference is real money, and it should go to an exception. For services, such as consulting or maintenance, there is often no physical receipt. In that case the receipt becomes a sign-off that the work was completed, with a date and a named person.

Write the rules on one page, have the person who owns the budget sign it, and keep the page next to the PO log. Changing a tolerance should require the same sign-off as the original rule.

Step by step: running the match without an ERP

An enterprise resource planning system, or ERP, holds purchase orders, receipts and invoices in one database. Without one, you can get most of the same control with a few linked tools. The steps below assume a team of two to ten people handling invoices from several suppliers.

  1. Give every purchase order one number and one home. Keep a PO log as an Excel table or a Google Sheets file. Each row holds the PO number, supplier, date, item, agreed unit price, quantity and approver. Send the PO to the supplier with the number at the top, and ask them to quote it on every invoice.

  2. Record receipts within a day. Use one receiving form, built in Google Forms or Microsoft Forms, or a short WhatsApp message to a receiving number. The person who checks the delivery records the PO number, the quantity received and any damage, and attaches a photo of the delivery note.

  3. Send all invoices to one place. Create a single invoice email address and tell suppliers to use it. For suppliers who prefer WhatsApp, a WhatsApp Business account can route photos of invoices to a shared inbox. Use Microsoft Power Automate or Zapier to save each attachment to a folder and add a row to a tracking sheet.

  4. Read the key fields from each invoice. Google Cloud's Document AI Invoice Parser is a pretrained processor that extracts fields such as invoice number, supplier name, invoice amount, tax amount, dates and line item amounts. For unusual layouts or photos, a large language model can help map the text to fields, but its output should be checked against the original document during the first months.

  5. Compare the documents with lookup formulas. Use a lookup such as XLOOKUP to pull the PO line by PO number and the receipt quantity by PO number. Then calculate the price difference and the quantity difference against your tolerance cells. Add a status column that reads Match, Hold for price, Hold for quantity, No receipt, or Possible duplicate.

  6. Route the results. Rows marked Match go to a payment list that a named person checks before release. Every other row goes to the exception queue.

  7. Record the approval where the books are kept. Post the approved bill to your accounting package, such as Xero, QuickBooks, Zoho Books or, for Indian businesses, Tally Prime, and keep the PO number on the bill so the trail stays intact.

A spreadsheet-based setup works while volume is modest and one person can review the queue each day. When the queue grows faster than it clears, the spreadsheet becomes the bottleneck, and it is time to compare a dedicated accounts payable tool or an ERP.

The exception queue

The exception queue is where the money is protected. Each entry needs four fields: the reason code, the supplier, the amount in dispute, and the owner. Use a small set of reason codes, such as price differs from PO, quantity exceeds receipt, no receipt recorded, no PO number, and possible duplicate. Owners usually follow the reason. Purchasing handles price, the receiving lead handles quantity, and whoever runs accounts payable handles duplicates and missing PO numbers.

Set a rule for how long an item can sit. A common approach is a weekly review for low-value items and a same-day review for anything that would breach a payment date. The number of days is a decision for your business, not a figure the process sets.

What breaks and how to prevent it

  • Receipts are not recorded. Every invoice then holds, and the queue fills with false alarms. Prevention: make the receiving form part of the delivery check and review unrecorded receipts each morning.
  • Suppliers leave off the PO number. The invoice cannot be matched at all. Prevention: state the PO number requirement in the PO itself and reject invoices without it until the supplier complies.
  • Partial deliveries and split invoices. One PO line may be billed in three parts. Prevention: track the received quantity as a running total per PO line rather than a single entry.
  • Tolerance creep. Small variances are approved again and again until the total becomes large. Prevention: review the approved variances by supplier once a month.
  • Misread invoice fields. A reader can confuse a zero with a letter O, drop a decimal point, or pick up the wrong currency. Prevention: check that the line amounts add up to the invoice total, and have a person check every extracted field for the first few months.
  • Bank detail change fraud. A fake invoice or email asks you to pay a new bank account. Prevention: any change to supplier bank details goes to a person, who confirms it by calling a number already on file. No tolerance rule should cover this.
  • Duplicate invoices under new numbers. A supplier resends an invoice with a different number and a slightly different amount. Prevention: flag any invoice from the same supplier with the same amount or the same PO within a set period.

The approval a person keeps

Automation should prepare the payment decision, not make it. Keep a named person as the approver for three things: every exception, every change to supplier bank details, and every new supplier. Set a payment limit above which a second person must sign off, and write the limit down.

Separate the roles where you can. The person who raises the purchase order should not also be the only person who confirms the goods arrived and approves the payment. In a small team this may not be possible for every invoice, so record who did each step. The log then shows the control even when the team is small.

When not to automate

Automation is not worth building in every case. If you receive only a handful of supplier invoices a month, checking each one by hand against the PO and the receipt may take less time than building and maintaining the sheets. Consultants, lawyers and other service providers often send invoices with no physical delivery. A three-way match forces a receipt that does not exist, so a two-way match with a signed completion note is usually better.

Do not automate a process that nobody follows. If receipts are not recorded today, a spreadsheet will not record them for you, and every invoice will land in the queue. Fix the receiving habit first. Handwritten invoices and poor-quality photos will also produce unreliable reads, and contracts with rebates or volume-based pricing are hard to express in a lookup formula. In those cases a person should do the match, and the tool can at most hold the invoice for them. Automation also cannot judge whether a price increase is fair or whether a supplier's delay justifies a late fee. Those decisions stay with people.

What it typically takes

The cost of this setup is mostly time. As a practical estimate rather than a benchmark, the PO log, receiving form and invoice folder can be set up in a few working days by one person who knows the purchasing process. Testing the field reader on 50 to 100 past invoices, and comparing its output with what a person recorded, usually takes longer than the build itself. Expect heavier checking in the first month, then a shorter weekly routine for exceptions and a monthly review of tolerances.

The amount of time you save depends on your own figures: how many invoices you receive, how many exceptions you see, and how long each one takes to resolve. A free automation audit can measure those figures for your business before any build begins, so the decision rests on your numbers rather than on a generic estimate.

How AiStaffo would automate this

AiStaffo would connect the invoice inbox, the PO log, the receiving form and the accounting folder your team already uses, so every invoice is read in one place. An AI worker would extract the invoice fields, compare each line with the PO and the receipt under the tolerance rules you set, and place matched invoices on a payment list. Mismatches would go to a written exception queue with the reason, the supplier and the amount, and the worker would draft the request to the supplier for a corrected invoice. Your team still approves exceptions, bank detail changes and payments above your limit. Book a free automation audit.

Questions people ask

What is the difference between a two-way and a three-way match?
A two-way match compares the supplier invoice with the purchase order only. A three-way match adds the goods receipt, which confirms that the goods or services were actually delivered in the quantity billed. For physical goods, the three-way match is the stronger check because it catches invoices for items that never arrived.
What tolerance should I set for invoice price differences?
There is no single correct figure. One AP software vendor's published sample auto-approves a price variance within 2% or $250, whichever is lower, and that is an example to test rather than a standard. Set a percentage and a fixed amount together so that a small percentage on a large order does not allow a large sum.
Can I do a three-way match in Excel or Google Sheets?
Yes, for a modest volume of invoices. A PO log, a receiving log and a lookup formula can compare the price and quantity on each line and mark the status. Once one person can no longer clear the exception queue each day, a dedicated accounts payable tool or an ERP is worth comparing.
Can an AI tool read invoices sent as photos on WhatsApp?
Some invoice readers can extract fields from photos and PDFs, and the WhatsApp Business platform can receive files from suppliers. Accuracy falls with blurred or handwritten invoices, so a person should check the extracted fields during the first months. Bank detail changes should never be accepted from a message alone.
How much does manual invoice processing cost per invoice?
Parseur's 2026 benchmark, citing Ardent Partners' 2025 research, puts manual processing at $12.88 to $19.83 per invoice, depending on company size and complexity. Your own cost depends on how long your staff spend on each invoice and how many exceptions you see. Count those hours for a month to get your own figure.
Should I automate the match if I receive only a few invoices a month?
Usually not at first. When the volume is small, a careful manual check against the PO and receipt may take less time than building and maintaining the sheets. Revisit the decision when the queue grows or late payments start to add up.

Book a free automation audit

Thirty minutes. We look at one process you run every week and tell you exactly what an AI worker would take off your desk, and what it would not.

We use these details only to reply to this request and prepare your audit, and keep them for up to two years. We send no marketing unless you tick the box above. Privacy policy

three way matchinginvoice matchingpurchase ordersaccounts payableexception handling