Invoice Discrepancy

An invoice discrepancy is any mismatch between what a supplier's invoice says and what your purchase order or receiving record shows, such as a wrong price, quantity, or tax amount. It is the most common reason an invoice cannot be paid on time, because until the difference is explained you do not know whether you owe the full amount billed, a smaller amount, or nothing at all. Last updated July 2026.

This guide explains what an invoice discrepancy is, the types accounts payable teams run into most, real examples, and the exact steps to resolve one, including an email you can send to the vendor. It is written for US AP teams, bookkeepers, and controllers who want to clear held invoices faster and stop the same discrepancies from coming back.

What is an invoice discrepancy?

An invoice discrepancy is a difference between the details on a vendor invoice and the supporting documents you match it against, usually the purchase order and the goods received note. During three-way matching, AP compares the invoice to the PO (what you agreed to buy) and the receipt (what actually arrived). When any of the three disagree on price, quantity, tax, or terms, the invoice is flagged as a discrepancy and held until someone resolves it.

A discrepancy is not an accusation. Most are honest differences: a supplier billed last quarter's price, shipped part of an order, or added tax you did not expect. The job of AP is to find the exact difference, decide which document is correct, and either get the invoice corrected or approve the variance within an agreed tolerance. Left unresolved, discrepancies pile up as held invoices, trigger late fees, and strain the vendor relationship.

What are the most common types of invoice discrepancies?

Most discrepancies fall into a handful of repeatable categories. Knowing the type tells you where to look and who to ask. The table below lists the ones AP sees most often, what each means, and what usually causes it.

Type	What it means	Typical cause
Price discrepancy	The unit price billed differs from the PO price	Expired pricing, a missed contract discount, or an unannounced rate change
Quantity discrepancy	The quantity billed differs from what was ordered or received	Partial shipment, over-delivery, backorder, or a short count at receiving
Tax discrepancy	Sales tax charged is wrong, missing, or unexpected	Wrong jurisdiction, an exempt purchase taxed, or a stale rate
Duplicate invoice	The same invoice is billed more than once	Vendor resends it, or it is entered against both a PO and a non-PO route
Missing or wrong PO	The invoice has no PO number or the wrong one	Maverick spend, a typo, or the buyer never issued a PO
Terms discrepancy	Payment terms or the due date differ from the agreement	Vendor default terms applied instead of the negotiated ones
Unit of measure mismatch	Billed per each when ordered per case, or a similar unit gap	UOM not aligned between the buyer and vendor systems

Price and quantity discrepancies together account for the large majority of what AP holds. Duplicates are the most expensive to miss, because a paid duplicate is real cash out the door that then has to be clawed back.

Invoice discrepancy examples

A price example: your PO lists a widget at 4.00 per unit because you have a negotiated contract rate, but the invoice bills 4.50, the vendor's list price. The 0.50 gap across 500 units is a 250 discrepancy. The PO is correct, so the vendor owes a corrected invoice or a credit for the difference.

A quantity example: you ordered 100 cases, the supplier shipped 80 and backordered 20, but the invoice bills all 100. Receiving logged 80. The invoice should be reduced to the 80 actually delivered, with the remaining 20 billed when they ship.

A tax example: you sent the vendor a valid resale or exemption certificate, but the invoice still adds 8.25 percent sales tax. The tax line is the discrepancy, and the vendor needs to reissue the invoice without it or credit the tax back.

How do you resolve an invoice discrepancy?

Resolving a discrepancy is a short, repeatable process: pinpoint the difference, decide who is right, and get either a correction or an approved variance. Work it in this order so nothing gets paid on a guess.

Pinpoint the exact difference. Put the invoice, the PO, and the goods received note side by side and identify the specific field that disagrees and by how much. Vague notes like "amount is off" slow everyone down.
Categorize it. Label it as price, quantity, tax, duplicate, PO, terms, or unit of measure. The type points you to the right source of truth and the right person to contact.
Decide which document is correct. Check the contract or price list for price, the receiving record for quantity, and your exemption status for tax. The PO reflects what you agreed to; the receipt reflects what you got.
Contact the vendor with specifics. Send the invoice number, the field in question, the figure they billed, the figure you expected, and the supporting reference. Specific requests get corrected fast.
Get a correction or a credit memo, or approve within tolerance. The vendor either reissues the invoice or sends a credit memo for the difference. If the gap is tiny and inside your matching tolerance, approve the variance and note why.
Document and post. Record what changed and why, then post the corrected invoice. A clean audit trail is what protects you if the same line is questioned later.

Invoice discrepancy email template

A good discrepancy email is short, names the invoice, and states the expected figure. Copy and adapt this:

Subject: Discrepancy on Invoice [#12345] - correction requested

Hi [Vendor contact],

We are processing invoice [#12345] dated [date] and found a difference
against our purchase order [PO #6789].

  Line: [item / description]
  Amount billed: [$4.50 per unit]
  Amount expected per our PO: [$4.00 per unit]
  Difference: [$0.50 per unit x 500 units = $250.00]

Please review and send a corrected invoice or a credit memo for the
difference so we can release payment. Happy to share the PO if helpful.

Thanks,
[Name], Accounts Payable

Keep the tone matter of fact. You are not accusing anyone; you are giving the vendor exactly what they need to fix the bill quickly.

What is the difference between an invoice discrepancy and an invoice dispute?

A discrepancy is a data mismatch you find internally during matching; a dispute is a formal disagreement you raise with the vendor, often withholding payment until it is resolved. Most discrepancies never become disputes because the vendor simply corrects the invoice. A discrepancy escalates into a dispute when the two sides disagree about who is right, for example the vendor insists the higher price is correct. The full escalation path is covered in our guide to handling an invoice dispute.

How do you prevent invoice discrepancies?

You prevent most discrepancies with tight three-way matching, clean master data, and clear terms agreed up front. When every invoice is matched automatically to its PO and receipt, price and quantity gaps surface the moment the invoice arrives instead of at payment time. Keeping vendor pricing, tax status, and payment terms current in your system removes the stale data that causes the rest.

The other half is capture. Discrepancies hide when line items are keyed by hand, because a typo looks exactly like a real difference. Pulling the invoice header and every line into structured data automatically means the figures you match are the figures the vendor actually sent. You can upload an invoice above and extract the fields in seconds, then feed them straight into matching with our invoice data entry software. For teams that want the whole flow automated, accounts payable automation software matches and routes exceptions without manual keying, and once your payables data is clean it also makes month-end close and producing accurate financial statements far less painful.

Clear invoice discrepancies faster

Discrepancies are unavoidable, but the time they cost is not. The teams that clear them fastest capture invoice data cleanly, match it automatically, and handle the exceptions that remain with a defined process instead of a scramble. To go deeper on the mechanics, see what three-way matching is and how to run invoice exception handling so held invoices do not sit for weeks.

PDF, JPG, PNG, BMP, HEIC, TIFF