What Happens When an Automated Invoice Match Fails?
Give every failed invoice match an owner and closure evidence. In Washington, a missing sales tax line is a use tax decision, not a reason to pay the vendor more.
In this guide
If you run accounts payable for a Seattle-area or Washington business, a failed invoice match should become an assigned investigation, with the invoice, purchase order, relevant receipt and discrepancy kept together. The reviewer resolves the underlying difference or records an authorized exception. Changing the data or widening a tolerance simply to obtain a pass can hide the problem the match was meant to reveal. In Seattle, as elsewhere in Washington, check the tax line as well: an invoice for supplies that matches on price and quantity but shows no itemized sales tax is a use tax decision, not just a payment.
In both Oracle and Microsoft finance software, a failed match stops the invoice short of payment. Oracle Payables places a matching hold on an invoice that falls outside the price or quantity tolerances, and the hold must be released before the invoice can be paid. Dynamics 365 Finance flags the discrepancy and lets the invoice be saved until it is approved for posting or the vendor sends a correction. The software stops the money; people still have to settle the difference.
This is a guide to purchase-order invoice exceptions for finance and purchasing teams in Seattle and elsewhere. For the wider implementation decision, start with what to automate first in accounts payable.
Explore an illustrative finance exception and review workflow.
First identify which check failed
Microsoft’s Dynamics 365 Finance documentation distinguishes price checks in two-way matching from the additional receipt-quantity checks in three-way matching. A price match can therefore coexist with a missing or incomplete receipt. These are product-specific controls to inspect in your ERP, not an approval policy for every invoice.
| Matching check | What must agree | Documented in |
|---|---|---|
| Two-way | Invoice price and purchase-order price; Oracle also requires the quantity billed to be no more than the quantity ordered | Microsoft Dynamics 365 Finance, Oracle Payables |
| Three-way | The two-way checks, plus the quantity billed against the quantity received | Microsoft Dynamics 365 Finance, Oracle Payables |
| Four-way | The three-way checks, plus the quantity billed no more than the quantity accepted | Oracle Payables |
| Invoice totals | Invoice totals against the totals expected from the purchase order | Microsoft Dynamics 365 Finance |
| Charges | Charges on the invoice, such as freight, against charges on the purchase order | Microsoft Dynamics 365 Finance |
A tolerance sets how much difference is allowed before a line fails. In Microsoft's example, a legal entity allows a 5 percent net unit price tolerance: against an order price of 1.00 per battery, an invoice at 1.05 passes and one at 1.10 fails. For price totals, the tolerance can be a percentage, an amount (Microsoft calls it a not-to-exceed amount) or both, and exceeding either one creates a discrepancy. Net unit price tolerances can be set for items, item groups, vendors, vendor groups, item and vendor combinations or the whole legal entity. Treat any tolerance change as a policy decision with its own approver, never as a way to clear a queue.
Read the failure at line level. Is the supplier identity wrong, the purchase-order reference missing, the quantity different, the price outside tolerance, or a charge unexpected? Check whether the software compared the intended records before asking someone to authorize the difference. A legitimate invoice associated with the wrong purchase order is a record-selection problem, not a reason to approve a price variance.
Make the next action unambiguous
The following resolution method is a proposed design for your team to adapt, not a client implementation.
Each queue record should show the entity and location, source document, affected order line, original and extracted values, failed rule, current owner, due date and required closure evidence. Keep AP accountable for tracking the item while assigning the factual question to the person who can answer it.
| Exception | Next owner | Evidence needed to close |
|---|---|---|
| Invoice quantity exceeds the selected receipt | Receiving | Confirmed receipt, corrected receipt record, or documented treatment of an incomplete delivery |
| Price differs from the purchase order | Buyer | Supplier correction or authorized purchase-price change with supporting agreement |
| Invoice uses cases; order uses individual units | Purchasing or item-data owner | Verified pack size and approved conversion applied consistently to the records |
| Invoice may duplicate a prior bill | AP duplicate reviewer | Comparison with posted and pending transactions, including corrections and credit notes |
| New freight or service charge appears | Buyer or service approver | Contract or acceptance evidence and the authorized accounting treatment |
| Washington invoice for supplies or equipment shows no itemized sales tax | Whoever prepares the excise tax return | A corrected invoice that itemizes the tax, or use tax reported and noted on the invoice |
Service invoices need service-acceptance evidence where policy requires it. Do not manufacture a goods receipt for a service simply because the software expects a third document. Non-PO invoices also need an explicit alternative approval path.
Walk a short receipt through to closure
This is an illustrative transaction, not a client record: the order and invoice each show 100 units, while the selected receipt shows 80.
AP first verifies that the invoice and order refer to the same item and unit. Receiving checks whether the remaining 20 units arrived in another delivery, whether an existing receipt was omitted, or whether the supplier billed ahead of shipment. Until that question is answered, the system preserves the discrepancy.
If another valid receipt exists, the reviewer links it and reruns matching. If only 80 arrived, the buyer follows the company’s policy for supplier correction, partial invoicing or an authorized exception. The selected treatment and supporting records become part of the history. The software does not silently rewrite the invoice to 80 and describe it as a successful match.
In Washington, a missing sales tax line is its own exception
Washington adds a check that price and quantity matching will not catch. Sellers must separately state retail sales tax on invoices, and if a seller's invoice does not itemize it, the Department of Revenue assumes sales tax was not paid, as its guidance on sales tax not listed on the invoice explains. The first step is to ask the vendor for a corrected invoice; if that fails, the buyer pays use tax directly to the department, reports it on the excise tax return and notes the invoice. The department is explicit that you should not add the sales tax to the invoice or to the amount you pay the seller. This applies to retail purchases, which include what the business buys for its own use, such as supplies and equipment, rather than to goods bought for resale with a reseller permit.
The department's use tax page adds two details that belong in the queue record. Use tax is generally measured on the purchase price including freight, delivery or shipping charges paid to the seller, and the rate is the state's 6.5 percent plus the local rate where the goods are first used. Seattle's combined rate is 10.55 percent for October through December 2026 in the local sales and use tax rate table. Illustrative example: $2,000.00 of shop supplies plus $150.00 freight, first used at a Seattle site and invoiced with no itemized tax, carries $2,150.00 × 10.55% = $226.83 of use tax. The rule is statewide, but the local part follows the site: the same table lists Bellevue at 10.3 percent, so the identical invoice first used at a Bellevue site carries $2,150.00 × 10.3% = $221.45. Other cities have their own rates, so check the table for the site where the goods are first used. That line goes to whoever prepares the excise tax return, not the buyer, and a pass on price and quantity does not close it.
In Chicago, the city adds a use tax of its own
An Illinois AP desk runs the same missing-tax check with different numbers. For businesses that file Form ST-1, the Illinois Department of Revenue requires use tax on purchases where no Illinois tax was paid to the seller, reported on that return at 6.25 percent for general merchandise. Chicago adds its own Use Tax for Non-Titled Personal Property: 1 percent on non-titled goods bought from a retailer outside Chicago for use in the city, with the first $2,500 of purchases each year exempt.
A resolved queue item still needs a controlled handoff
Define separate states for investigation complete, ready for approval, approved for posting and paid. Resolving a match does not itself complete payment authorization. When a corrected document arrives, retain the earlier version and rerun the relevant checks. Reopen the item if the correction introduces a different discrepancy.
For an integration, retain the source invoice identifier and destination transaction identifier. After a timeout, check whether the destination already created the transaction before retrying. Send unresolved failures to an owner; an invisible retry loop is not a recovery process.
AI assistance can propose fields or summarize the discrepancy, with the original document visible. Do not let a confident summary substitute for the receipt, agreement or duplicate investigation needed to settle it.
Judge the queue by its unresolved work
Before a pilot, record exception volume, time awaiting each owner, oldest open item and reopened cases. Test partial shipments, unit changes, duplicate submissions and an unavailable ERP. Inspect a sample of cleared items too: a falling queue is useful only if differences are being resolved correctly.
A practical acceptance requirement is that every failed match remains visible until a named person records the approved resolution and its evidence. Apply the same standard across locations; the finance operations overview shows how this fits a broader improvement effort.
Quick answers
What happens when an invoice fails three-way matching?
The invoice is held back from payment until the difference is resolved. Oracle Payables places a matching hold that must be released before the invoice can be paid; Dynamics 365 Finance flags the discrepancy and lets the invoice be saved until it is approved for posting or corrected. Someone then establishes whether the receipt, the invoice or the order is wrong.
What is the difference between two-way, three-way and four-way matching?
Two-way matching compares the invoice with the purchase order, chiefly on price. Three-way matching adds the quantity received. Four-way matching, as Oracle Payables defines it, also requires the quantity billed to be no more than the quantity accepted.
What is an invoice matching tolerance?
It is the difference allowed before a line fails. In Microsoft's documented example, a 5 percent net unit price tolerance accepts an invoice price of 1.05 against an order price of 1.00 but rejects 1.10.
Should we widen tolerances to reduce matching exceptions?
Only as a deliberate policy decision with its own approver and a later review. Widening a tolerance to clear a queue lets real price and quantity differences through without anyone investigating them.
What should a Washington AP team do with an invoice that shows no sales tax?
Ask the vendor for a corrected invoice that itemizes the tax. If that fails, report use tax on the excise tax return and note the invoice; do not add the tax to the payment.
Sources
- Oracle Payables places a matching hold · docs.oracle.com
- Microsoft’s Dynamics 365 Finance documentation · learn.microsoft.com
- sales tax not listed on the invoice · dor.wa.gov
- goods bought for resale with a reseller permit · dor.wa.gov
- use tax page · dor.wa.gov
- local sales and use tax rate table · dor.wa.gov
- Illinois Department of Revenue · tax.illinois.gov
- Use Tax for Non-Titled Personal Property · chicago.gov
Revision note · October 6, 2026: Headline simplified; the article body is unchanged.
How we research and review these guides
Put the ideas to work in your business.
We provide AI consulting and implementation for finance operations teams. Bring us the process that is slowing your team down and the systems involved. We can assess the problem with you and discuss a practical implementation.
Discuss your project →Still exploring? Explore the Workflow Opportunity Workbook →