Eight units appear on the invoice. The purchase order covers ten, and the warehouse has recorded eight. It looks like a match until you find a previous bill for three units against the same receipt. Only five received units are left to bill, and a check that compares each PDF with the original order will never see it.
Invoice matching comes down to comparing the right lines, in the right units, against the quantity still available after earlier bills.
What each match level compares
| Method | Records compared | Question it answers | Use when |
|---|---|---|---|
| Two-way | Invoice and PO | Does the charge agree with what we approved? | Policy lets AP verify the charge against the order alone |
| Three-way | Invoice, PO, and receipt | Does it agree with the order and with what we received? | The reviewer needs to check what was delivered |
| Four-way | Invoice, PO, receipt, and inspection acceptance | Does it agree with what passed inspection? | Payment depends on which units were accepted |
Oracle Fusion Cloud Procurement documents two-, three-, and four-way match approval levels, with the four-way level using accepted quantities from inspection (Oracle’s match approval documentation). Oracle also separates the approval level from the setting that decides whether Payables matches to the PO or to the receipt, so verify both (Oracle’s Procurement implementation guide).
In Dynamics 365 Finance, three-way matching compares invoice unit price with the PO and invoice quantity with matched product receipts (Microsoft’s invoice matching overview). Check the policy configured in your own system before assuming it tests both.
Pick the evidence by purchase type
- Inventory and direct materials. Match quantity to the warehouse receipt. Three-way at minimum.
- Inspected materials. Four-way when quality acceptance gates payment.
- Services. Decide who confirms the work and which record they use. A service-entry or approval record plays the role of the receipt.
- Non-PO bills. No match is possible. Route through the expense approval policy with the contract or other support attached.
Worked examples (illustrative)
Figures exclude tax and freight unless stated.
Example 1: where two-way passes and three-way stops
You ordered 100 filters at $12. The warehouse received 80. The supplier invoiced 100 at $12, for $1,200.
A two-way match passes: price and quantity agree with the PO. A three-way match exposes the 20 units not yet received, worth 20 × $12 = $240. If the 20 are in transit, the difference stays with receiving. If receiving missed an entry, the authorized owner corrects it before the bill advances. Whether AP can process the supported $960 (80 × $12) now depends on your policy.
Example 2: a total that hides two errors
The supplier bills two parts on the same order. There are no prior bills against these receipts.
| Line | PO price | Received | Invoice line | What AP sees |
|---|---|---|---|---|
| Brackets | $10 | 10 | 10 × $11 = $110 | $1 per unit over the PO price |
| Clamps | $5 | 10 | 8 × $5 = $40 | Billed for 8; 2 received units remain available |
| Total | $150 | Equals the value of all received goods at PO prices (10 × $10 + 10 × $5) |
A total-only check passes this invoice. The bracket line goes to the buyer, who confirms whether a price change was approved. The clamp line is a partial bill; confirm that is allowed and keep two units available for the next invoice.
Example 3: the receipt already used
Back to the opening case. PO for 10 units, receipt for 8, an earlier bill for 3, and a new invoice for 8.
- Available to bill: 8 received − 3 already billed = 5
- New invoice: 8
- Unsupported: 8 − 5 = 3
The reviewer needs the receipt quantity and the earlier bill side by side. The cause could be a duplicate, a missed credit, or the earlier bill matched to the wrong receipt. AP checks before anyone asks the supplier.
Example 4: four-way, inspection rejects part of a delivery
Receiving logs 100 units. Quality accepts 90. The supplier bills 100. Show the reviewer all three quantities and the inspection outcome, and send the 10 rejected units to the person who can confirm their disposition: return, replacement, or credit.
How to run the match, line by line
- Confirm the supplier, buying entity, and PO number. Oracle’s Payables guide notes that the purchase orders available on its Match Invoice Lines page share the invoice’s legal entity (Oracle’s Using Payables Invoice to Pay guide).
- Find the PO line or schedule. An order can contain the same item at different prices or for different locations.
- Convert units. If the supplier bills cases and the warehouse receives eaches, check the conversion against the item record before calling it a shortage.
- Compare price and quantity separately. They have different owners and different tolerances.
- Keep freight and tax visible if your policy treats them differently. Otherwise freight can look like a price increase, or an unrelated credit can hide one.
- Subtract earlier bills from the receipt quantity before comparing.
When two PO lines look right
“Filter assembly” is the only description on an invoice that lists a PO number. The order has two filter assembly lines at the same price, one per plant. A match on description and price can pick either.
| If the candidates differ by | Give the reviewer |
|---|---|
| Plant | Ship-to address, packing slip, receipt location |
| Delivery schedule | Shipment reference and quantities still open per schedule |
| Price or pack size | Invoice units, approved conversion, both PO prices |
| Job or department | Order distribution and the document that identifies the work |
If the evidence still points to two lines, keep the match open and have receiving or purchasing confirm. A wrong line can consume the receipt for the wrong plant and leave the right one open for the next invoice. Oracle also documents that matching to a schedule with several distributions can spread the amount across them, so check the accounting lines after the match.
Setting tolerances
Set price and quantity tolerances separately. For each, record whether it is a percentage, an absolute amount, or both, whether it applies per line, per invoice, or across invoices, and what happens exactly at the boundary. Keep missing receipts and suspected duplicates as their own cases. Passing a price tolerance answers neither.
Illustrative tolerance check. Policy: price variance allowed up to 2 percent or $0.25 per unit, whichever is smaller. PO price is $10.00.
| Invoice price | Variance | Percent | Result |
|---|---|---|---|
| $10.20 | $0.20 | 2.0% | Passes (exactly at the 2% limit, under the $0.25 cap) |
| $10.30 | $0.30 | 3.0% | Fails both tests |
Now the repeat problem. The supplier bills 1,000 units in each of five installments, each at $10.20. Every invoice passes, and $0.20 × 1,000 × 5 = $1,000 of price variance clears without a buyer ever seeing it. Have the matching rule surface repeated small variances by supplier, with price history attached. The purchase price variance guide covers how this lands in the ledger.
Microsoft documents separate invoice price and product receipt quantity checks in Dynamics 365 Finance matching setup (Microsoft’s matching setup guide). Confirm whether a discrepancy in your configuration requires approval before posting.
Send each exception to the person who can fix it
| What the match found | What the reviewer receives | Who acts |
|---|---|---|
| Receipt missing | PO line, billed quantity, delivery reference | Receiving confirms delivery or explains |
| Price above PO | Billed and ordered prices, any approved change | Buyer |
| Receipt already used | Receipt quantity and earlier bills against it | AP checks for duplicate, credit, or allocation error |
| Different units of measure | Invoice unit, receipt unit, conversion | Item master owner |
| Material rejected after receipt | Inspection or return record and original receipt | Quality and receiving |
| Bill without a PO | Invoice and proposed account | Budget owner |
Save the explanation and who approved any release. Rerun the match when a receipt, credit, or approved order change arrives. A successful match does not release payment by itself; keep posting and payment approval as separate rules. The invoice holds and payment blocks guide covers clearing a hold once the owner acts.
When a receipt changes after the match
The warehouse recorded 40 parts and AP matched the invoice. Next morning receiving corrects the count to 38. The invoice still shows as matched.
Oracle Fusion documents a Payables Matched and Modified Receipts report for finding receipts changed after a match, including quantity corrections and returns (in the same Oracle Payables guide linked above). Find the equivalent report or change history in your ERP and run it every period.
| Receiving event | What AP checks |
|---|---|
| Count corrected from 40 to 38 | Whether the bill now exceeds the receipt, and who resolves it |
| Two parts returned after acceptance | Return reference, expected credit or replacement, whether the bill was paid |
| Receipt moved to another PO line | Which bill used the original line |
| Credit arrives in a later period | Which invoice and return it settles |
If the bill is unpaid, apply a hold under your policy. If it was paid, track the expected credit and match it to the original bill and return when it arrives. Receipts that stay open at month-end belong in the GR/IR and receipt accrual reconciliation.
Microsoft documents that Dynamics 365 Finance can automatically match posted product receipts to invoice lines under configured conditions (Microsoft’s invoice workflow documentation). Test what happens when a partial receipt posts after the invoice arrives.
Test batch before you automate matching
Set the expected result for each case before running it.
- Clean match: links to the right PO line and receipt, reaches the right approver
- Price just inside tolerance, and just outside
- Partial receipt with a prior bill against it
- One bill covering several receipts
- Two plausible PO lines
- Cases versus eaches
- Receipt reversed after the match
- Supplier resends the bill
- Posting times out and is retried: one bill in the ledger
- Track bills matched correctly, routed for review, and incorrectly cleared
For plant-floor cases such as returns and rejected material, see manufacturing AP automation. For keeping PO revisions aligned with what AP matches against, see purchase order automation.