Try it now, capture a real invoice
Free plan · No credit card · Your data stays yours
An invoice discrepancy is any mismatch between an invoice and the documents that should support it, usually the purchase order, the goods receipt, or the contract. When the price, quantity, tax, or terms on the bill do not agree with what was ordered or received, accounts payable cannot approve it as-is, and the invoice becomes an exception that someone has to research and clear before payment. Discrepancies are the single biggest reason invoices sit unpaid, so resolving them quickly protects both your cash controls and your supplier relationships.
This guide covers what an invoice discrepancy means, the most common types with examples, why they happen, and a step-by-step way to resolve them, including how automation keeps most of them from reaching a human at all.
What is an invoice discrepancy?
An invoice discrepancy is a difference between what a supplier billed and what the buyer expected based on the purchase order, the goods received, or the agreed terms. It can be as small as a rounding difference on tax or as large as a bill for goods that never arrived. During invoice matching, the AP system or clerk compares the invoice to its supporting documents; any field that does not agree is flagged as a discrepancy and held until it is explained, corrected, or approved as a deliberate exception.
What are common invoice discrepancies?
Most discrepancies fall into a handful of repeat offenders. Recognizing the type is the first step to fixing it fast. The table below lists the common ones and what typically causes each.
| Discrepancy type | What it looks like | Common cause |
|---|---|---|
| Price discrepancy | Unit price billed is higher than the PO price | Price change not reflected on the PO, or a pricing error |
| Quantity discrepancy | Billed quantity exceeds what was received | Partial delivery, short shipment, or over-billing |
| Missing PO or receipt | No purchase order or goods receipt to match against | Off-contract buying or a receipt not yet posted |
| Tax or freight discrepancy | Tax, shipping, or surcharge lines that were not on the order | Uncoded add-on charges or wrong tax rate |
| Duplicate invoice | Same invoice billed twice under different numbers | Supplier resend or manual re-entry |
| Terms discrepancy | Payment terms or discount differ from the contract | Outdated terms in the vendor record |
Why do invoice discrepancies happen?
Discrepancies usually trace back to information that got out of sync somewhere between ordering and billing. A price is renegotiated but the purchase order is never updated. A shipment arrives short but the supplier bills the full quantity. A receipt is not posted before the invoice lands, so there is nothing to match against. Manual data entry adds its own errors, transposing figures or keying the wrong PO. And some discrepancies are not accidents at all: inflated prices, phantom line items, and duplicate bills are classic invoice fraud examples that hide inside routine mismatches, which is exactly why the matching control exists.
How do you resolve an invoice discrepancy?
Resolving a discrepancy is a short, disciplined loop. Work it in order and document what you find so the same issue does not recur.
- Identify the exact mismatch. Compare the invoice against the PO and goods receipt and pinpoint which field is off: price, quantity, tax, terms, or a missing document.
- Find the source of truth. Check whether the PO, the receipt, or the invoice is correct. A renegotiated price means the PO is stale; a short shipment means the invoice is over-billed.
- Contact the right party. If the supplier billed wrong, request a corrected invoice or credit memo. If the internal record is wrong, update the PO or post the missing receipt.
- Apply tolerances where allowed. Small, pre-approved variances such as minor freight or rounding can be auto-accepted under a matching tolerance instead of escalated.
- Document and close. Record the cause and resolution, then release the invoice for approval and payment or reject it cleanly.
For the mechanics of the check itself, see our guide to three-way matching, and for how much variance to let through automatically, read about matching tolerance.
What is an invoice discrepancy email?
An invoice discrepancy email is the note AP sends a supplier to flag a mismatch and request a fix. Keep it specific: reference the invoice number and PO number, state exactly what does not agree (for example, "billed 100 units at $12, PO shows 100 units at $10"), and say what you need, a corrected invoice or a credit memo, and by when. A clear, factual email resolves discrepancies faster than a vague "there is a problem with your invoice," because the supplier can act on it without a second round of questions.
How to prevent invoice discrepancies
The cheapest discrepancy is the one that never happens. Keep purchase orders current when prices or terms change, require a PO for spend above a threshold so there is always something to match against, and post goods receipts promptly. Maintain clean vendor records so terms and tax default correctly, and screen every incoming bill for duplicates. Capturing invoice data accurately at intake matters too: much of the noise comes from manual keying, so using reliable document data extraction to read invoice fields removes a whole class of errors before matching even starts.
Automate discrepancy handling with AP software
AP automation flips discrepancy work from find-them-by-hand to handle-only-the-exceptions. The software captures each invoice, matches it to the purchase order and receipt, auto-approves anything within tolerance, and routes only genuine mismatches to a person with the PO, the receipt, and the discrepancy already highlighted. That cuts the research time on each exception and stops clean invoices from waiting behind them. See how the workflow runs in our overview of accounts payable software, or upload a real invoice at the top of this page to watch capture and matching flag discrepancies on your own document.