Blog · Procurement and supply chain · Procurement
Separate invoice price, receipt quantity and document-link exceptions so a procurement review explains what evidence each discrepancy needs.
Explain a three-way match exception at the invoice line where it occurs. Show the purchase-order price, relevant receipt quantity and applicable rule, rather than placing every mismatch into one undifferentiated failure bucket. Missing document evidence deserves its own lane.
Microsoft's invoice matching documentation describes three-way matching as comparing invoice price with purchase-order price and invoice quantity with selected product receipts. It also describes configurable tolerances. The analysis below uses reviewed policies rather than assuming that every organization follows the same configuration.
Use one invoice line as the primary reporting row. Link it to the applicable order line and one or more receipt allocations through stable document keys. Retain separate relation rows where a receipt covers several invoices or an invoice covers several receipts.
Record company, supplier, invoice and order keys, line numbers, product, quantity units, document dates, receipt timestamps, net price basis, charges, currency, policy version and cutoff time. Confirm whether service invoices use an approved service-acceptance record instead of a product receipt.
The PO, invoice and paid-spend guide owns the broader population differences. This method evaluates evidence within a defined matching population and does not treat matching as proof of settlement.
Distinguish no order link, multiple unresolved order links, no eligible receipt evidence, quantity discrepancy, price discrepancy, charge discrepancy and policy unknown. A row can carry several flags, so report both distinct exception lines and flag counts.
For comparable unit prices, a simple review measure is invoice price minus order price, divided by order price. A zero or missing order price makes that percentage unavailable. Netting tax, discounts or freight inconsistently can create an apparent variance with no comparable basis.
Use pack-size and unit comparisons when units differ. Do not compare dollars per case with dollars per individual item or invent a product conversion to close the exception.
The records below are synthetic as of October 6, 2026. All quantities are in the same reviewed unit, amounts are USD, and taxes and charges are excluded consistently. The demonstration policy flags price differences above 2%; receipt allocations are dedicated to each illustrated line.
| DEMO line | Ordered quantity | Receipt quantity | Invoiced quantity | Order unit price | Invoice unit price | Review result |
|---|---|---|---|---|---|---|
| A | 100 | 60 | 60 | $10.00 | $10.00 | No measured discrepancy |
| B | 100 | 60 | 80 | $10.00 | $10.00 | 20 units above recorded receipt |
| C | 50 | 50 | 50 | $20.00 | $21.00 | Price difference 5% |
A's $600 invoice is supported by its allocated 60-unit receipt even though the entire order is not received. B's $800 invoice includes 20 units, or $200 at the invoice price, above the allocated receipt evidence. C's $1,050 invoice differs by $50 from 50 units at $20; $1 ÷ $20 = 5%, exceeding the synthetic 2% rule.
The decision is to request B's missing receipt or allocation evidence and review C's price authorization. These are distinct review amounts, not confirmed losses or instructions to withhold payment.
When several invoices consume one receipt, maintain allocations and reconcile total allocated units to available receipt units. Giving every invoice the full receipt quantity can make unsupported quantities appear matched. Joining raw invoice lines to all receipts can also multiply invoice dollars.
Retain partial receipts, returns and correction events with their signed quantities and dates. A later receipt can change the evidence available at a later snapshot; preserve the original cutoff instead of silently rewriting what was known during the earlier review.
Use the effective approved matching policy for the company, supplier, product and order where relevant. Separate a descriptive analytical flag from an actual ERP validation status; the two can differ because of configuration, timing or additional source fields.
The contracted-price comparison addresses entitlement under an applicable agreement. Matching an invoice to a PO does not establish that the PO itself used the entitled contract price.
Reconcile line counts and invoice amounts before and after linking. Sample matched as well as unmatched lines, disclose missing policies, and assign exception evidence checks to the authorized reviewer.
Use the procurement review example as a model for presenting a bounded question and reconciled rows. Contact Covirage to discuss a scoped exception analysis; posting and payment decisions remain in the responsible process.
No. It identifies a discrepancy in the available evidence. Late receipts, partial deliveries and incorrect links must be reviewed before the responsible team decides the disposition.
No. Use the applicable approved policy and effective date. A demonstration tolerance is not a recommendation for every organization or item.