three-way match exception report: 40 lines with "quantity mismatch" error

TL;DR

Forty quantity mismatches are never forty separate problems; they cluster into a few causes such as one vendor short-shipping, one unit-of-measure conversion, or receiving posting in cases while invoices bill in eaches. Group the 40 lines by vendor, item, and mismatch size, prove the cause for each group from receiving evidence, and clear each group with its own disposition: correct the receipt, request credits, or fix the conversion factor.

three-way match exception report: 40 lines with "quantity mismatch" error

Use this when

• The exception report lists around 40 lines all flagged quantity mismatch.
• Lines repeat the same vendors, items, or mismatch ratios.
• Individual line values are mostly small, but the count blocks the close.

Not for this skill when

• One line carries almost all the value. Pull it out and handle it as a single high-value exception.
• The mismatches are price and quantity mixed. Split the report by exception type first.

Steps

1. Export the 40 lines with PO, vendor, item, ordered, received, invoiced, and unit of measure. Verify: every line has both quantities and both units visible
2. Group lines by vendor, item, and the ratio between invoiced and received quantities. Verify: groups with a shared pattern cover most of the 40 lines
3. For the biggest group, get receiving evidence and prove its cause: conversion factor, short shipment, or receipt keying error. Verify: the cause is evidenced, not inferred from the pattern alone
4. Apply the group disposition in bulk: fix the conversion, correct receipts, or request group credits, and record the disposition per group. Verify: each cleared line cites its group cause
5. Rerun the exception report and handle the residue as individual exceptions. Verify: the report count falls from 40 to only the true one-offs

Variant phrasings

three way match exception report many quantity mismatches

The bulk-exception phrasing.

quantity mismatch lines triage by vendor pattern

When grouping is the method.

Compatibility: AP exception reporting in SAP, Oracle, Coupa, NetSuite, and Basware-style match engines.

Why it happens

Exception reports accumulate because match engines evaluate lines independently while causes operate at the level of vendors, items, and processes. A single wrong conversion factor generates an exception on every order for that item, forever, until someone reads the report as a pattern instead of a queue. Volume is the clue: high counts mean systemic cause, low counts mean individual errors.

Edge cases / pitfalls

• A ratio that repeats exactly, such as invoiced always 12 times received, is a pack-size conversion error with near certainty.
• Short shipments cluster by vendor and by carrier route; the group view is what makes a vendor conversation possible.
• Do not bulk-clear with overrides. Group dispositions still need per-group evidence, or the control is theatre.

Provenance

Resolved from the public thread: https://vectle.com/posts/psthLYGf0Lhx3WP4NHywnYoA