Receiving Discrepancy

Receiving discrepancy definition: a gap between the receiving record and the invoice quantity or condition. What it means and why it matters for AP.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Receiving Discrepancy

A receiving discrepancy is a mismatch between what the receiving dock recorded as delivered and what the vendor invoice bills for, in quantity, unit of measure, or condition. It shows up at the three-way match step, where accounts payable checks the purchase order, the receipt, and the invoice against each other before releasing payment. When the receipt does not agree with the invoice, the invoice should not clear automatically.

1. What counts as a receiving discrepancy?

A receiving discrepancy is any disagreement between the receiving record and the vendor invoice on quantity received, unit of measure, or condition of goods. It includes short shipments billed as full, partial deliveries invoiced at full quantity, unit of measure conversion errors such as cases billed as eaches, and damaged or rejected goods invoiced as accepted. The common thread is a receipt document that does not match what the invoice charges for.

The discrepancy is defined by the mismatch itself, not by intent. A vendor can bill a wrong quantity by error, and the invoice still qualifies as a receiving discrepancy until someone reconciles it against the dock record.

2. Why does a receiving discrepancy reach the invoice at all?

Three-way matching checks the invoice against the purchase order and the receipt, but only if a receipt record exists and is entered before the invoice is processed. Receiving staff working under time pressure sometimes log a count without opening every case, and the invoice often arrives and gets processed on a separate timeline from the dock, so the two records never get compared before payment.

A purchase order alone cannot catch this. The PO states what was ordered, not what physically arrived on the dock that day.

3. How is a receiving discrepancy different from an accessorial or rate error?

A receiving discrepancy concerns quantity or condition: whether the goods invoiced actually arrived as billed. A rate or contract error concerns price: whether the correct quantity was billed at the agreed rate. The two are caught by comparing the invoice to different reference documents, the receiving record versus the rate card, and each is corrected differently.

Confusing the two in a review can send a genuine rate card dispute to the receiving team, or a genuine dock error to procurement, delaying the actual fix.

A receiving discrepancy is a quantity or condition problem: the invoice bills for goods that were not confirmed as received in that quantity or state. A rate error, by contrast, bills the correct quantity at the wrong price against the contract. Receiving discrepancies are caught by comparing the invoice to the receiving record; rate and contract errors are caught by comparing the invoice to the rate card or contract terms, an entirely separate reference document.

4. How does a company find and prevent receiving discrepancies?

Prevention starts at the dock: recording quantity, unit of measure, and condition at the moment goods arrive, and holding the invoice until that record exists. Detection after the fact means reconciling paid invoices against receiving documentation to find gaps the control missed, then routing confirmed discrepancies back to the vendor for credit before the dispute window closes.

Both steps matter. Prevention stops the leak going forward; reconciliation recovers what already got paid before the process was tightened.

  1. Record at the dock: Capture quantity, unit of measure, and condition for every line at receipt, not from memory later.
  2. Hold the invoice: Do not release payment until a matching receipt record exists for the invoice line.
  3. Reconcile paid invoices: Compare a sample of already-paid invoices against receiving documentation to surface gaps the control missed.
  4. Route disputes early: Send a confirmed discrepancy back to the vendor before the credit memo window closes.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

What is a receiving discrepancy?

A mismatch between the receiving record and the vendor invoice, in quantity, unit of measure, or condition of goods delivered. It means the invoice bills for something the dock never confirmed as received in that form.

Is a receiving discrepancy the same as an invoice error?

Not exactly. An invoice error is the broader category. A receiving discrepancy is a specific type of it, tied to quantity or condition rather than price or contract terms.

Who is responsible for catching a receiving discrepancy?

Typically the accounts payable team, using three-way matching against the purchase order and the receiving record, with the receiving team responsible for the accuracy of the original dock count.

Can a receiving discrepancy happen with a correct price?

Yes. The unit price can match the rate card exactly while the billed quantity does not match what physically arrived, which is what makes this a control gap rather than a pricing gap.

Does unit of measure count as a receiving discrepancy?

Yes. Billing in a different unit of measure than what was received, such as invoicing by the each when the dock received and counted by the case, produces the same quantity mismatch.

How is a receiving discrepancy corrected once found?

The buyer disputes the invoiced quantity with the vendor using the receiving record as documentation, and requests a credit memo or invoice correction for the unconfirmed portion.

Does three-way matching always catch this?

Three-way matching checks the invoice against the purchase order and the receipt. It only catches a receiving discrepancy if an accurate receipt record was entered before the invoice was processed.

What is the difference between a receiving discrepancy and a duplicate payment?

A receiving discrepancy is a quantity or condition mismatch on one invoice line. A duplicate payment is a separate finding entirely: the same invoice or charge paid more than once.

1. What counts as a receiving discrepancy?

A receiving discrepancy is any disagreement between the receiving record and the vendor invoice on quantity received, unit of measure, or condition of goods. It includes short shipments billed as full, partial deliveries invoiced at full quantity, unit of measure conversion errors such as cases billed as eaches, and damaged or rejected goods invoiced as accepted. The common thread is a receipt document that does not match what the invoice charges for. The discrepancy is defined by the mismatch itself, not by intent. A vendor can bill a wrong quantity by error, and the invoice still qualifies as a receiving discrepancy until someone reconciles it against the dock record.

2. Why does a receiving discrepancy reach the invoice at all?

Three-way matching checks the invoice against the purchase order and the receipt, but only if a receipt record exists and is entered before the invoice is processed. Receiving staff working under time pressure sometimes log a count without opening every case, and the invoice often arrives and gets processed on a separate timeline from the dock, so the two records never get compared before payment. A purchase order alone cannot catch this. The PO states what was ordered, not what physically arrived on the dock that day.

3. How is a receiving discrepancy different from an accessorial or rate error?

A receiving discrepancy concerns quantity or condition: whether the goods invoiced actually arrived as billed. A rate or contract error concerns price: whether the correct quantity was billed at the agreed rate. The two are caught by comparing the invoice to different reference documents, the receiving record versus the rate card, and each is corrected differently. Confusing the two in a review can send a genuine [rate card](/glossary/rate-card) dispute to the receiving team, or a genuine dock error to procurement, delaying the actual fix. A receiving discrepancy is a quantity or condition problem: the invoice bills for goods that were not confirmed as received in that quantity or state. A rate error, by contrast, bills the correct quantity at the wrong price against the contract. Receiving discrepancies are caught by comparing the invoice to the receiving record; rate and contract errors are caught by comparing the invoice to the rate card or contract terms, an entirely separate reference document.

4. How does a company find and prevent receiving discrepancies?

Prevention starts at the dock: recording quantity, unit of measure, and condition at the moment goods arrive, and holding the invoice until that record exists. Detection after the fact means reconciling paid invoices against receiving documentation to find gaps the control missed, then routing confirmed discrepancies back to the vendor for credit before the dispute window closes. Both steps matter. Prevention stops the leak going forward; reconciliation recovers what already got paid before the process was tightened. 1. Record at the dock: Capture quantity, unit of measure, and condition for every line at receipt, not from memory later. 2. Hold the invoice: Do not release payment until a matching receipt record exists for the invoice line. 3. Reconcile paid invoices: Compare a sample of already-paid invoices against receiving documentation to surface gaps the control missed. 4. Route disputes early: Send a confirmed discrepancy back to the vendor before the [credit memo](/glossary/missed-credit-memo) window closes. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

What is a receiving discrepancy?

A mismatch between the receiving record and the vendor invoice, in quantity, unit of measure, or condition of goods delivered. It means the invoice bills for something the dock never confirmed as received in that form.

Is a receiving discrepancy the same as an invoice error?

Not exactly. An invoice error is the broader category. A receiving discrepancy is a specific type of it, tied to quantity or condition rather than price or contract terms.

Who is responsible for catching a receiving discrepancy?

Typically the accounts payable team, using three-way matching against the purchase order and the receiving record, with the receiving team responsible for the accuracy of the original dock count.

Can a receiving discrepancy happen with a correct price?

Yes. The unit price can match the rate card exactly while the billed quantity does not match what physically arrived, which is what makes this a control gap rather than a pricing gap.

Does unit of measure count as a receiving discrepancy?

Yes. Billing in a different unit of measure than what was received, such as invoicing by the each when the dock received and counted by the case, produces the same quantity mismatch.

Margin Drift Resources