Unmatched reason
The classified explanation for why an invoice line could not be matched to a contracted price.
An audit that reports 'no match' without a reason is unusable — someone still has to open every line and work out what happened. A reason taxonomy turns that pile into a work queue.
The common reasons: the SKU appears in no price list; the SKU exists but no price was in effect on the invoice date; the unit of measure differs between contract and invoice; the line is a substitution for a contracted item; the line is not a product at all (freight, fuel surcharge, pallet deposit); or the line is one half of a credit and rebill pair.
Each reason routes differently. Unit mismatches are a mapping fix. Expired prices are a contract-administration fix. Unknown SKUs are a supplier conversation. Non-product lines should be excluded from the unmatched rate entirely, or the metric lies.
Related terms
- SKU stemming — Reducing a part number to a comparable core so distributor-specific variants match the contracted item.
- Unit of measure normalization — Converting contract and invoice quantities to a common unit before any price comparison.
- Credit and rebill pairing — Linking a credit memo line to the corrected invoice line that replaced it so a single correction is not counted twice.
See this on your own invoices
Audit your first 500 invoice lines free. No card, no sales call.