Three Way Match Exceptions

How to resolve three-way match exceptions your ERP can't explain

New: Solar Mini 4 is live on Console. 50% off through Oct 22 (UTC) Learn more → New: Solar Mini 4 is live on Console. 50% off through Oct 22 (UTC) Learn more →

Solutions

Resources

Company

Pricing

Try demo Try demo Contact us

In short When the ERP matches within tolerance, nobody needs to look. Three-way match exceptions are the lines that fall out, and the reason behind each one sits in the source documents. Slow reviews cost you early payment discounts, while rushed ones let duplicate payments and overpayments slip through. Upstage Studio starts from your ERP exception queue, lines up the PO, goods receipt and invoice, and shows why each line didn't match.

Get a demo Try Studio

Why can't the ERP explain its own exceptions? It's the 27th, and the exception queue has 140 lines in it, the oldest from three weeks ago. You open the first one and the ERP tells you the quantities don't match, but it doesn't tell you the supplier shipped 1,200 bearings and billed for 2,000. The ERP knows something didn't match, but it has no way of knowing why. Matching passes the lines that fit the receipts you selected and the tolerances you set, and real documents rarely fit those settings cleanly. Partial deliveries, unit differences, freight billed separately and item names written differently all end up in the queue. Resolving a three-way match exception means finding the difference between the PO, goods receipt and invoice before someone decides what to pay, and the reason is almost always in the documents.

Where the time goes The supplier invoice arrives as a PDF, a scan or the body of an email. Someone enters the invoice into the system. The system tries to match it to the PO and the goods receipt. Anything that doesn't match drops into the exception queue. Someone opens the three source documents to find out why. They check with purchasing or the supplier and make the correction. Payment is approved.

Steps 5 and 6 are where the day goes, and a lot of those exceptions aren't real mismatches at all. Many are entry errors or wording differences, where the PO calls an item one thing and the invoice calls it something else. What the queue costs When the queue sits, payments go out late, early payment discounts disappear, and close week starts with a backlog nobody wants to own. Clearing it in a hurry creates the opposite problem, because duplicate payments and overpayments go through when nobody has time to look.

The Tennessee Valley Authority's 2024 follow-up audit found that 18 percent of its available early payment discounts, worth $826,252, went unused. Staff didn't know the discount terms, and invoices that arrived after the discount deadline or before the goods receipt were hard to handle. One logistics company in California had already automated invoice entry with RPA and a capture tool, yet people were still the ones working out what didn't match. A trading company's US office faces the same work, matching more than a hundred sets of overseas POs and invoices every month. Which document explains the exception? Here's one exception from a set of sample documents. PO HG-PO-260811 orders 2,000 EA of BEARING 6204ZZ at USD 1.50. The supplier bills for 2,000 EA under the name BEARING 6204-2Z, while the goods receipt dated 08/25/2026 shows only 1,200 EA. Field Purchase order Goods receipt Supplier invoice Item BEARING 6204ZZ BEARING 6204ZZ BEARING 6204-2Z Quantity 2,000 EA 1,200 EA (800 EA open) 2,000 EA Unit price USD 1.50 Not stated USD 1.50

That leaves a gap of 800 EA × USD 1.50, or USD 1,200.00 billed before the goods arrived. The item names line up once you account for the different wording, but that doesn't mean the bearings did. With Upstage Studio , each exception is read against its three source documents and comes back with the reason attached. Most fall into three groups, which are the same item described differently, a partial delivery, or a real difference in quantity or price.

A wording difference only needs a quick confirmation, and a partial delivery means checking what arrived against what was billed. Real quantity and price differences are where your team's time should go, and the decision to ask the supplier for a credit, net it against the next invoice or release payment stays with them. For the AP specialist, the day starts to look different. You no longer pull three documents for every exception. Exceptions caused only by wording get a quick confirmation and move on. Close week no longer starts with a pile on your desk.

Try Upstage Studio What a year of records shows The first gains show up in time per exception and on-time payment. Keep a year of exception records by supplier and by cause, and more starts to come into view. The mix of root causes, whether wording, partial delivery or price, so you can fix the biggest one first. Exception rates by supplier, which give you grounds to ask a supplier to clean up their invoice format. Days from receipt to payment, and how much early payment discount that delay is costing you. Suspected duplicates, where two invoices hit the same PO, caught before the payment goes out. The trend in open exceptions going into each close.

Over time, your team spends less effort clearing exceptions and more of it preventing them. FAQ Our ERP already does three-way matching. How does this connect to its exception queue? Keep using it, tolerances included, because Upstage Studio picks up only the lines that fall out. You can start with an export of the exception list and the documents behind it. Does it connect to our ERP? That depends on your ERP, and we confirm it with you during a technical review. Can suppliers use different invoice formats? Yes, and there's no per-supplier template to set up, so your team can review documents in whatever format they arrive. How much of our queue is actually a real mismatch? It's often less than it looks. Many exceptions turn out to be the same item described two ways, or a delivery that hasn't fully arrived yet. Sort last month's queue by cause and you'll see your own split. What tolerance should I set for three-way matching? Look at the causes before you touch the tolerance, since a wording difference and an unreceived quantity call for different decisions. Is this your queue? You handle thousands of supplier invoices a month....