A quantity or receipt mismatch is raised when the quantity billed on an invoice does not agree with the quantity recorded as received. The invoice fails the quantity check in three-way matching and stops until someone confirms what actually arrived.
Alongside price variances, it is one of the two exceptions that come straight out of the match, and it is usually a timing problem rather than a billing error.
The receipt decides whether an invoice can pay
The match compares three numbers: the quantity ordered on the purchase order, the quantity confirmed on the goods receipt, and the quantity billed on the invoice. When the billed quantity is higher than the received quantity, the system flags it, because paying for more than arrived is the risk the control exists to prevent. A billed quantity lower than what was received also breaks the match, though it carries less risk.
Partial deliveries flag correct invoices
The most common cause is a partial delivery. A supplier ships an order across two or three deliveries, invoices for the full amount or for the first shipment, and the receipt only reflects what has landed so far. The invoice itself is accurate; it has just arrived ahead of the goods. Over-shipments are the reverse, where more arrives than was ordered and the invoice follows the larger amount.
A late receipt makes a correct invoice look wrong
Just as often, the goods arrived and the invoice is correct, but the goods receipt was never entered or was entered late. The warehouse confirmed the delivery on paper, or in a separate system, and the record the match reads still shows nothing received. From the system's point of view the goods do not exist yet, so a correct invoice is flagged for a quantity the receipt does not support.
Cases and eaches break the match quietly
A quieter cause is a unit-of-measure difference. The order is in cases, the invoice is in eaches, and the raw numbers do not line up even though the quantities agree once converted. The same happens with weight-based or length-based goods where the supplier and the buyer measure the same delivery differently.
Resolve quantity mismatches at the source
The clerk checks whether the goods receipt is complete and current. If a delivery is still outstanding, they hold the invoice or pay the received portion. If the receipt is simply missing, they chase the warehouse or the requester to post it, then re-run the match. This is slow because the answer lives in the receiving process, not on the invoice, and the person clearing it has to reach into another team to confirm what happened on the dock.
Fragment reconciles quantity and receipt mismatches autonomously by reading the order, the goods receipt, and the delivery history together, without ripping out or replacing your existing systems. See how it works or request a demo.