Procurement Supplier Invoice-to-Receipt Exception Lag

A supplier invoices for a full order, but receiving recorded only a partial delivery. Procurement supplier invoice-to-receipt exception lag measures how long an unmatched invoice waits for a documented owner and resolution path.

Define the first exception timestamp as an invoice validation failure, a receiving discrepancy notice or a manual match review, using a reliable trigger rather than the date somebody finally opens a ticket. Microsoft describes three-way matching of invoice, purchase order and product receipt quantities under selected policies, though the exact match and tolerance rules vary by organisation.

Define the endpoint as qualified triage or full resolution and name which one the metric measures, because a fast assignment is not the same as a corrected payable amount. Link invoice number, supplier entity, PO line, receipt, quantity, price and currency, since a header-level match can hide a single disputed item.

Distinguish goods not received from goods received but not posted, because the former may require supplier follow-up while the latter may be a receiving backlog. Check whether the supplier billed freight, tax or service charges under separate contract rules, as not every mismatch is a physical quantity problem.

For partial deliveries, compare invoiced units with accepted receipts at the invoice date, since a second shipment expected next week should not be counted as received today. If a product failed inspection, clarify whether the receipt is recorded but blocked, rejected or returned, because those statuses affect the invoice review differently.

Check units of measure, since a case invoice matched to an individual-unit receipt may appear tenfold wrong if the conversion was lost. If the PO was changed after supplier shipment, keep the relevant version and acknowledgment, as a mismatch may arise from a timing difference between systems, and if an invoice duplicates one already posted, route it as a duplicate-payment risk, not a receiving shortage.

Assign responsibility to procurement, receiving, accounts payable or the supplier based on evidence, because copying all teams without an owner can lengthen the delay. When a supplier sends a corrected invoice, retain the original and the credit or cancellation link, since quietly replacing the original file makes later audit difficult.

Keep payment hold and due date visible, because an unresolved invoice may create late-payment fees or supplier friction, but payment should not bypass needed checks, and if a mismatch falls within an approved tolerance record the rule applied, since tolerance acceptance is not proof that the data was exact. Define the denominator as invoice lines with receipt-related exceptions during the period, so clean invoices do not dilute the result, and track the median, a high percentile and the oldest open cases, because one major invoice stuck for months can disappear behind routine fast resolutions.

Classify shortage, overreceipt, price, missing PO, tax, duplicate and data-entry causes separately, and for services use the contract milestone or service acceptance evidence rather than pretending a warehouse receipt exists. If the supplier disputes the receiving count obtain physical and carrier evidence, audit selected exceptions from original invoice and PO through receipt, owner action and final disposition, and report financial exposure and critical supplier relationships alongside lag, so genuine discrepancies are resolved without paying unsupported amounts or leaving valid suppliers waiting indefinitely.