Systems and records
Procurement three-way match exceptions: what explains a failed match?
By SourceX Editorial · Updated
9 sections
Short answer
A failed three-way match is explained by records linked to the transaction, not by the variance fields: purchase order change history, contract price terms, later receipts, receiving notes, specification and supplier approvals, correspondence, and the payment or credit that closed it. Capture each exception as a task pack with starting state, linked evidence, applicable rule, decision and authority, and a verified outcome, so the reason is provable.
Value drivers
Procurement three way match
Key takeaways
- Variance codes say which comparison failed; the reason lives in change logs, contracts, receipts, approvals and correspondence.
- Status and release codes describe the workflow, and an invoice can stay blocked after its reason has gone away.
- Every common exception has an obvious resolution and a constraint that can make it wrong; keep those counterexamples.
- Separate the decision (who released it, on what authority and why) from the outcome (payment, credit, dispute, reconciliation).
- Record the matching policy and tolerance per line, because policies differ by item, vendor and company.
What evidence explains a failed three-way match beyond the structured fields?
The structured fields record that a match failed, not why. A price variance flag, a quantity mismatch or a blocking code tells you which comparison broke; the explanation sits in linked records around the transaction: purchase order change history, contract price terms, receiving notes, specification revisions, supplier approvals, emails about substitutes and the credit memo or payment that finally closed the item.
That gap matters for anyone using procurement three-way match exceptions to train or test an AI agent. A model that sees only the invoice line and the variance code learns to guess the most common resolution. A model that sees the evidence chain can learn the reasoning a buyer or payables analyst actually used, and can be graded on whether it reached a decision the records support.
This page builds that evidence chain into a reusable task pack: a starting state, the linked evidence, the rule that applied, the decision and the person with authority to make it, and the record that proves the outcome. It complements a schema for linked match data by focusing on the rationale for each exception rather than the match itself.
How does three-way matching decide pass or fail?
Three-way matching compares price on the invoice with price on the purchase order, and quantity on the invoice with quantity on the receipts selected for it; a line fails when a difference exceeds the tolerance the company configured. Microsoft's Dynamics 365 Finance documentation describes exactly this, and its own example shows how small the margin can be: a policy that allows a 5 percent net unit price tolerance accepts an invoice price 5 percent above the purchase order price but flags one 10 percent above it.
Other ERP systems express the same idea differently. Oracle's E-Business Suite Payables reference guide shows the ladder in its data model: the quantity received is checked for three-way matching only when receipt is required, and the quantity accepted is checked for four-way matching only when inspection is required. SAP invoice verification blocks an invoice for payment when variances exceed tolerance limits, and lists price, quantity, schedule and quality inspection among the blocking reasons alongside manual and random blocks.
Policy also varies inside one company. The BPI Challenge 2019 purchase-to-pay event log, published for process mining research, distinguishes items under three-way matching with the invoice after the goods receipt, three-way matching with the invoice before the goods receipt, two-way matching and consignment. A dataset that omits the matching policy per line cannot tell an agent which comparison should have been run.
Why do the status fields mislead?
Status fields describe the state of the workflow, not the state of the business problem. SAP's documentation is explicit: for quantity, price and schedule variances and quality inspection blocks, an invoice may still be blocked although the blocking reason is no longer valid, and it stays blocked until someone releases it. Its example is a purchase order for 100 pieces where 80 arrive but 100 are invoiced; the missing 20 arrive the next day, yet the invoice still waits for release.
The reverse also happens. A release code says the item was released, not whether the release was right. A manual release with a generic reason, a tolerance widened to clear a backlog or a short payment that the supplier later disputes all produce the same tidy closed status as a correct resolution.
So when you extract exception history, treat status and release codes as starting clues. The training label should be the decision supported by the evidence and confirmed by what happened afterward, which may differ from the final status in a meaningful share of cases. Measure that share on your own records before you rely on status codes; it is a property of each company's process.
Which constraint makes the obvious resolution invalid?
Every common exception has an obvious resolution and at least one constraint that makes it wrong. The table pairs them with the record that proves which applies. Use it as the counterexample list for the task pack: each row is a case where an agent that follows the obvious rule should fail.
The pattern behind every row is the same: the purchase order is a snapshot of an agreement, and agreements move. Prices are renegotiated, parts are substituted, delivery splits across receipts and services are accepted outside the warehouse. When the ERP record lags the agreement, the match fails even though nothing went wrong commercially. When the agreement never changed, the same failure is a real error. Only the linked record tells the two apart, which is why each row names one.
| Exception | Obvious resolution | Constraint that invalidates it | Record that proves it |
|---|---|---|---|
| Invoice price above PO price | Short-pay to the PO price and notify the supplier | A signed price escalation or index clause made the higher price contractual | Contract amendment or price agreement effective before the invoice date |
| Invoiced quantity above received quantity | Hold or short-pay the unreceived quantity | The remaining goods were received after the invoice was entered | Later goods receipt for the same PO line |
| Item on invoice differs from PO item | Return the invoice as wrong item | An approved substitute was agreed in advance because the original part was unavailable | Approved substitution or change notice and the buyer's approval |
| Charges not on the PO | Reject the charges line | The PO terms or a buyer email accepted expedited freight for a customer deadline | PO terms, change order or written buyer approval |
| Receipt but no invoice match for a service | Wait for a goods receipt that will never come | Services are accepted by sign-off, not by a warehouse receipt | Service entry sheet, timesheet approval or acceptance document |
| Possible duplicate invoice | Block the second invoice | The second invoice is a legitimate partial or a corrected rebill that supersedes the first | Credit memo against the first invoice and supplier correspondence |
| Supplier not approved for the part | Pay as normal because goods arrived | Quality rules require supplier approval for that specification revision before payment or use | Approved supplier list entry and specification revision history |
What should the PO, receipt, invoice and exception rationale task pack include?
The task pack is the asset: one record per exception that holds everything a reviewer needs to reach and check the decision. Each component below names the fields to capture, where they usually live and why the component is there. Label every pack as real (from approved, de-identified records) or illustrative, and never mix the two in one evaluation set.
Keep the pack small enough to review by hand. A reviewer should be able to read one pack and agree or disagree with the label in a few minutes; if that takes an hour, the linked evidence is too broad and should be cut to the records that bear on the decision.
| Component | Fields to capture | Typical source record | Why it is in the pack |
|---|---|---|---|
| Starting state | PO line, receipts, invoice line, matching policy, tolerance, block or hold code, dates | ERP purchasing, receiving and payables tables | Defines what the agent sees when the exception is raised |
| PO version history | Every change to price, quantity, item or delivery date with timestamp and user | PO change log or audit table | Shows whether the PO or the invoice was out of date |
| Linked evidence | Contract terms, change notices, specification revision, supplier approval status, receiving notes | Contract repository, quality system, receiving system | Holds the reason the fields do not show |
| Correspondence | Supplier and buyer messages tied to the PO or invoice number | Email, supplier portal messages, ticket system | Captures agreements made outside the ERP |
| Applicable rule | The policy, tolerance or contract clause that governs the decision, with version | Payables policy, delegation of authority, contract | Lets a grader check the decision against a rule, not a guess |
| Decision and authority | Release, short-pay, return, credit request or escalation; who decided and their approval limit | Release log, approval workflow | Separates a correct decision from one made by someone without authority |
| Outcome check | Payment, credit memo, supplier dispute, statement reconciliation, clearing entry | Payments, GR/IR clearing, supplier statements | Confirms the decision held up after the item closed |
| Counterexample flag | Whether the obvious resolution would have been wrong, and which constraint applies | Reviewer annotation | Tests reasoning instead of the majority resolution |
| Provenance and handling | Real or illustrative label, de-identification method, fields removed, reviewer | Preparation log | Makes the pack auditable and safe to share |
Illustrative worked case: a price variance that was not an overcharge
This case is illustrative; the company, items and amounts are invented to show how the pack is filled in. A manufacturer issues a purchase order for 400 machined brackets. The invoice arrives with a unit price 5 percent above the purchase order price, the receipt shows 400 received, and the three-way match fails on price because the variance is outside the configured tolerance. The invoice is blocked.
The obvious resolution is to short-pay at the purchase order price. The linked evidence says otherwise. The PO change log shows the buyer had not updated the price after a contract amendment, and the contract repository holds an amendment signed two months earlier that ties the bracket price to a published steel index, with the new price effective from the first of the month. Supplier correspondence includes the index calculation.
The applicable rule is the amended contract, not the PO. The decision is to release the invoice at the contract price and correct the PO, made by the category buyer within her approval limit and recorded in the release log with a reason that cites the amendment. The outcome check is the payment record at the amended contract price with no supplier dispute and a clean statement reconciliation at month end.
The counterexample in the same pack is a second invoice from the same supplier, also 5 percent above its purchase order price, for a part number the amendment does not cover. There the obvious resolution is correct: short-pay and request a credit. An agent that learned only that this supplier's price variances get released will fail it.
How do you pull the evidence chain out of the systems that hold it?
Start from the exception, not from the invoice table. Pull every invoice line that was ever blocked, held or released with a reason, then walk outward along keys: purchase order number and line, receipt document, vendor id, contract id and the user ids on approvals. Each hop should be a join you can repeat, not a manual search.
Change history is the hop most often missed. ERPs keep it in audit or change-document tables that ordinary reports do not show, and without it you cannot tell whether the purchase order was wrong at the time of the invoice or corrected afterward. Export it with timestamps and the user who made each change.
Correspondence is the hardest hop. Supplier emails and portal messages rarely carry a structured key, so match them on PO and invoice numbers mentioned in the subject or body, and keep the match method with each link so a reviewer can see which links are certain and which are inferred.
Finally, fix a cutoff. Include only exceptions whose outcome window has closed, so every pack has a verified outcome, and keep open items aside for a later refresh rather than labeling them early.
- Exclude exceptions with no linked evidence beyond the variance code; they teach the majority resolution and nothing else.
- Exclude or separately label exceptions resolved by mass release, tolerance changes or year-end clean-up, because the release reason is administrative.
- Keep exceptions where the decision was later reversed; label the reversal and the evidence that caused it.
- Record which systems were unavailable for a period, so missing links are not mistaken for missing evidence.
Which records prove a release decision and its payment outcome?
The decision is proven by the release or approval record that names the person, their authority and the reason; the outcome is proven by what happened after the item closed. Keep the two apart in the data, because a decision can be properly made and still turn out wrong.
At a glance
Which records prove a release decision and its payment outcome
In public-sector buying the evidence trail is written into rules. FAR 32.905 makes payment depend on a proper invoice and a receiving report or other payment-authorizing document that records, among other things, the quantities accepted and the date of acceptance. Commercial companies set their own rules, but the same idea applies: acceptance evidence, not the invoice, is what authorizes payment.
- Decision evidence: release log entry with reason, approval workflow record, buyer's written instruction, credit request sent to the supplier.
- Outcome evidence: payment record and amount, credit memo received, supplier dispute or its absence after a set period, supplier statement reconciliation, GR/IR clearing entry.
- Maturity rule: label an outcome only after a fixed window during which disputes, credits or reversals would normally appear, and record the window you used.
- Conflict rule: when the decision and the outcome disagree, keep both labels and the evidence; those cases are often the most useful for evaluation.
Preparing procurement three-way match exceptions for licensing
Exception history with its evidence chain is the part of payables data that is hardest to recreate synthetically, which is why AI developers ask for it. Agents that handle payables exceptions need to learn when the obvious resolution is wrong, and only real exception histories with their evidence show that at the frequency and variety a business actually meets. Preparing it is mostly linkage work: joining PO, receipt and invoice keys to change logs, contracts and correspondence, then de-identifying supplier names, people and bank details while keeping the joins intact.
Keep four questions separate. Access means your team can export the records. Privacy permission concerns the personal data inside them, such as employee names and supplier contacts. Ownership concerns who holds rights in documents such as supplier contracts, which may carry confidentiality clauses. Contractual licensing rights are what a data agreement grants. De-identification addresses privacy; it does not by itself create the right to license, so counsel should review supplier contract terms before any records leave the company.
Procurement teams that want to license their match-exception history can use SourceX, which manages qualification, rights review, contracting, preparation, delivery and payment for the records a company selects. On volume, AI buyers tend to look for at least two years of steady history and tens of thousands of records in one ERP, while rarer exception work may qualify with less; every dataset is weighed on its own. Eligibility is settled through a short company assessment, and no PO, receipt or invoice data has to be uploaded for it.
Frequently asked questions
What are procurement three-way match exceptions?
They are invoices or invoice lines that fail the comparison of purchase order price, received quantity and invoiced price and quantity within the tolerances a company configured. The ERP blocks or holds them until someone resolves the difference.
What are the most common reasons a three-way match fails?
Price differences between invoice and purchase order, invoiced quantities above what was received, items or charges not on the purchase order, services without a receipt and possible duplicates. The underlying reason is often an outdated purchase order or an agreement made outside the ERP.
Does a released invoice mean the exception was resolved correctly?
No. A release code records that the block was lifted, not that the decision was right. Confirm the outcome with the payment, any credit memo, the absence of a supplier dispute after a set period and the supplier statement reconciliation.
Can three-way match exception data be used to train AI agents?
It can, when the company has the rights to license the records and the data is prepared with its evidence chain intact and personal and confidential details handled. Exceptions linked to contracts, change logs and correspondence are more useful than variance codes alone.
What is the difference between three-way and four-way matching?
Three-way matching compares the invoice with the purchase order and the receipt. Four-way matching adds inspection or acceptance, so quantities that failed inspection are not paid even if they were received.
Sources
- Microsoft's Dynamics 365 Finance documentation defines three-way matching as matching invoice price to the purchase order and invoice quantity to product receipts, with a worked 5 percent tolerance example. Source
- Microsoft's three-way matching policy examples show policies set by legal entity, item and item-vendor combination so invoices are paid only after matching purchase orders and receipts. Source
- Oracle's E-Business Suite 12.1 Payables Reference Guide says Payables checks quantity received (three-way matching) only when receipt is required and quantity accepted (four-way matching) only when inspection is required. Source
- SAP documentation describes blocking invoices for payment when variances exceed tolerances, with blocking reasons including price, quantity, schedule and quality inspection. Source
- SAP documentation says an invoice blocked for quantity, price, schedule or quality reasons may stay blocked after the reason is no longer valid, until it is released. Source
- FAR 32.905 bases payment on a proper invoice and a receiving report or other authorizing document that records quantities accepted and the acceptance date. Source
- The BPI Challenge 2019 purchase-to-pay event log distinguishes three-way matching with invoice after goods receipt, three-way with invoice before goods receipt, two-way matching and consignment items. Source
See if your company qualifies
A short company assessment. No data uploads are needed.