How to Check Supplier Invoices for Overcharges Before You Pay

To check a supplier invoice for possible overcharges, compare each billed item with the relevant agreed terms, verify quantities using the records appropriate to the purchase and explain any additional charges. Keep the source evidence for each question.

A difference deserves investigation. It does not by itself establish an error, an unauthorized charge or fraud. A revised order, accepted price change, partial invoice or documented unit conversion may explain it.

This guide focuses on checking documents and organizing the follow-up. It does not determine contractual rights, tax treatment or when payment may legally be withheld.

Start with the agreement you are actually checking

Gather the invoice, relevant PO revision and any accepted amendments. Add the supplier confirmation, receiving record, agreed price list or contract where needed.

Identify which record establishes the terms your authorized reviewer has accepted. A supplier confirmation may introduce a change. An invoice agreeing with that confirmation does not, by itself, show the buyer accepted the change.

Keep every version. The purpose of checking is to explain the history and current basis, not to edit older documents until all numbers look alike.

Check identity before arithmetic

Confirm the supplier, buyer, invoice number, PO reference and currency. A correct calculation against the wrong order still produces an unusable result.

Then check whether the invoice concerns the full order, a delivery stage or a partial quantity. The total for an entire PO is not necessarily the expected amount for one partial invoice.

For repeat invoices, your payment and billing records are also relevant. The two files on your desk cannot establish whether an item has already been billed or paid elsewhere.

Work through the amounts at line level

For each item, record the agreed quantity, unit and price beside the invoiced values. Keep units explicit. Ten cases and ten each are different quantities unless the underlying conversion is known.

Check whether a line amount incorporates a discount, surcharge or other calculation. Recalculate using the terms shown and explain any difference. When the source is unclear, record the question instead of substituting an assumed value.

Review added charges separately: freight, handling, rush fees or other services. Look for the document or acceptance record supporting each one. Avoid spreading an unexplained charge across item prices just to make the totals agree.

A lower invoice can still contain higher charges

The fictional sample used throughout this guide has a PO total of $1,640.00 and an invoice total of $1,512.00 before tax. The invoice is $128.00 lower, but the line check produces several questions.

Finding	Document difference	What remains to be established
AX-100 price changed from $4.00 to $4.20 on 100 each	+$20.00	Was the higher price accepted?
FX-600 increased from 10 to 12 each at $12.00	+$24.00	Were the additional units authorized and received?
Freight added despite “included” on the PO	+$28.00	What supports the extra charge?
BX-200 price changed from $8.00 to $7.60 on 50 each	−$20.00	Does the lower price reflect an agreed adjustment?
EX-500’s 30 each do not appear on the invoice	−$180.00 in this document comparison	Is the item on a different invoice or still to be supplied?

The positive differences total $72.00. The lower price and absent item explain −$200.00, giving the overall difference of −$128.00.

The $72.00 is a set of positive document differences to investigate. It is not a confirmed recoverable amount. The missing $180.00 line is not a credit, and the lower invoice total is not proof that all charges are correct.

Download the fictional documents to follow the numbers yourself.

Distinguish an explainable difference from an unresolved one

The sample also contains two useful counterexamples.

CX-300 is ordered as four cases at $60.00 per case and invoiced as 48 each at $5.00 per each. The PO explicitly states 12 each per case. The quantities and amounts agree after that documented conversion: four times 12 is 48, and both line amounts are $240.00.

DX-400 appears once on the PO and twice on the invoice. The two invoice rows contain 12 and eight each at $15.00, totaling the ordered 20 each and $300.00. The repeated SKU requires grouping and review; it does not automatically establish duplicate billing.

These examples show why the follow-up should identify the precise issue. A changed unit label or repeated item code may be explainable even when a simple spreadsheet flags it.

Ask for the record that would settle the question

For a detailed walkthrough of these two cases, see case-versus-each price comparisons and matching split invoice rows. If several invoices relate to the same order, maintain a cumulative billing balance as well as checking each document.

For a price change, request the accepted revised PO, applicable agreement or other authorization. For an extra quantity, consult the order amendment and receiving record. For added freight, ask for the agreed basis of the charge.

For an absent item, ask whether the supplier intends to bill it separately and check the corresponding delivery information. Do not infer nondelivery solely from the absence of an invoice row.

Receipt verification requires receipt evidence. Microsoft’s invoice-matching overview distinguishes order and price checks from matching that also uses product receipts.

Send a consolidated, factual query

Give the supplier the invoice and PO references, the affected items, both values and a clear request. For the fictional price discrepancy:

We are reviewing INV-8821 against PO-1042 revision 1. AX-100 is listed at $4.20 per each on the invoice and $4.00 on the PO. For 100 each, the difference is $20.00. Please provide the accepted price revision or advise whether an updated invoice is required.

This wording states the evidence without assuming the explanation. Include the relevant page or extract, taking care not to share unrelated commercial information.

Use the email templates for quantity, freight and multi-issue versions. Apply your organization’s approved process for payment timing while the question is being resolved.

Record how the discrepancy was resolved

A complete record identifies the source documents, question, responsible reviewer, supporting reply and outcome. An outcome might be an accepted amendment, a corrected invoice, a separately documented adjustment or a referral for further review.

Keep the original invoice alongside any correction and make the relationship clear. Ask the supplier which document is current and ensure your accounting process avoids treating both as separate payable invoices.

The Excel workbook includes a discrepancy log you can adapt. It does not update accounting or payment records; that remains a controlled step in your process.

Common questions

Can I check an invoice without a purchase order?

You need another appropriate basis, such as an accepted quote, contract, approved work order or price agreement. If that evidence is missing, record the limitation and obtain authorization rather than treating the invoice as self-verifying.

Should I request a credit for every positive difference?

First establish the agreed basis. An accepted change can explain a positive difference. Ask the supplier and your authorized reviewer which correction or adjustment is appropriate when an error is confirmed.

Does an AI check establish that I have been overcharged?

A generated comparison can help organize evidence. The conclusion still depends on complete documents, correct interpretation and the relevant agreement. It cannot supply missing authorization or receipt history.

Make the next invoice easier to review

A repeatable method is more useful than remembering where the last discrepancy appeared. Preserve the accepted basis, compare all rows, keep unresolved questions explicit and save the response.

For an immediate process, use the Excel matching template. For a developing file-based approach to the same recurring task, explore LineRecon early access.