The supplier invoice does not match: resolve the difference without rewriting the order

The invoice is for 120 units. The purchase order is also for 120. The receiving record shows 108. Someone suggests changing the receipt so the invoice can be processed. That would make the figures agree while leaving the business less certain about what actually arrived.

Invoice matching is an established accounting control. Its purpose is to compare the supplier's claim with the agreed purchase and, where applicable, the goods received. A mismatch is a reason to investigate. It is not, by itself, proof that the supplier is wrong or that payment must be withheld indefinitely.

The business should decide its matching policy, tolerances and approval responsibilities in advance. Accounts payable applies that policy during routine processing. Purchasing owns commercial terms, receiving owns the physical delivery record, and an authorised manager decides any genuine exception.

Know which records you are comparing

Two-way matching compares the invoice with the purchase order. Three-way matching also checks the receipt. Microsoft's invoice-matching overview explains both approaches and separates unit-price, quantity and additional-charge checks. The important principle is to compare like with like, using the correct documents and units.

A receipt of ten cases can match an invoice for 120 units if each case contains 12. It cannot be judged from the number ten alone. The same applies to price units: a quotation per hundred pieces should not be compared directly with an invoice price per piece without conversion.

Before investigating the commercial difference, confirm the supplier account, invoice number, order reference, item, currency and unit of measure. Check for duplicate invoices and whether a document is a statement, proforma or credit note rather than a new invoice requiring payment.

Decide whether the difference is real or a missing entry

In the opening example, the outstanding 12 units might still be travelling. They might have arrived but not been recorded. They might have been short-shipped. Those explanations look similar on an accounts-payable screen but require different resolutions.

Ask receiving for the relevant delivery record and actual count. If stock arrived and the receipt was omitted, the authorised receiving colleague corrects the record with the appropriate evidence and date. Accounts payable should not invent the receipt on that colleague's behalf.

If only 108 arrived, preserve that fact. Purchasing or the agreed claims owner contacts the supplier about the missing balance and the invoice treatment. Depending on the agreement, the supplier may send the remainder, issue a correction or provide a credit. Record what was agreed and who will follow it through.

Separate price, quantity and charges

Consider a purchase for 120 units at 5 each. The invoice charges 5.30 per unit, all 120 units and an extra 25 for delivery. The receiving record shows 108 units. There are at least three questions: was the higher price agreed, what happened to the balance, and was the delivery charge authorised?

Do not resolve the whole invoice with a single explanation such as “supplier increase”. The price difference may be valid for a new order but invalid for this protected order. The delivery charge may be correct even though the quantity is not. Each line of reasoning needs its own evidence.

Net prices also deserve attention. A familiar headline price can hide a changed discount or a line charge. Compare the agreed net amount and relevant charges, not just the largest number printed on the invoice.

Use tolerances for routine differences

A business can set proportionate tolerances for small differences such as rounding, while routing larger or unusual discrepancies for review. Microsoft's configuration guidance describes separate matching rules and tolerances rather than one universal approval switch.

The policy should state which differences are acceptable automatically, who may approve an exception and when repeated small differences need investigation. A discrepancy within tolerance does not necessarily mean the data is correct; the threshold determines how the process handles it.

Use both percentage and absolute impact where appropriate. A small percentage on a very large invoice can still be material. Conversely, spending an hour arguing over an immaterial rounding difference may cost more than resolving it under an approved policy. Finance should set those boundaries according to the business's circumstances.

Keep correction and exception separate

A correction restores the record to what actually happened or what was agreed. An exception authorises a departure from the normal policy. Treating them differently makes later review much easier.

For example, entering a genuinely omitted receipt is a correction. Approving a disputed additional transport charge to settle a commercial issue is an exception. The latter may be justified, but the approver should see the amount, reason, alternatives and whether the decision creates any future commitment.

Microsoft's three-way matching examples illustrate how missing receipts and price differences can be routed through defined approval policies. The lesson is to establish ownership before exceptions arise, so staff know when they can proceed and when they need a decision.

Manage the payment deadline while the issue is open

Log the discrepancy promptly and tell the supplier what needs resolving. Include the invoice reference, affected lines, evidence and requested action. Keep the due date visible rather than allowing the query to become an unmonitored hold.

Where only part of an invoice is disputed, finance should decide the payment treatment under the contract and applicable rules. Do not assume the entire balance may be withheld merely because one line is under discussion. An agreed partial payment also needs a clear remittance explanation so the supplier can allocate it correctly.

Track promised credits to completion. A supplier email saying “we will credit that” is not the same as a received and correctly applied credit note. Assign an owner and follow-up date, then reconcile the adjustment to the original invoice.

Finally, look for recurring causes: missing order references, ambiguous pack sizes, receipts posted late or price changes never communicated to finance. Resolving those upstream problems reduces the queue more effectively than repeatedly overriding the same warnings. A matched invoice should mean the business understands the transaction, not merely that somebody has made the screen turn green.

Related guidance: writing a clear purchase order.

AI-generated editorial illustration.