A Supplier Invoiced the Wrong Price. Now What?
A supplier billed above the agreed price. Here is how to block the invoice, prove the variance against the contract, and resolve it with a credit note or debit memo — without short-paying.
A supplier’s invoice lands and the line totals are higher than you expected. You pull the purchase order and the agreed price file, and the gap is real: the unit price billed sits above the standard list price you negotiated, or a quantity break was ignored, or a surcharge you never agreed to has been added. The amount is wrong, the goods are already in the building, and payment terms are running. The instinct is to pay it and sort it out later, or to short-pay and let the supplier chase the difference — both create more work than the error itself. The correct move is narrow and process-driven: block the invoice, prove the variance against what was actually agreed, and resolve it with the right financial instrument, so the books, the supplier statement, and your spend data all end up telling the same story. Here is how to run that from first flag to closed credit.
Where a wrong-price invoice actually hides
The overcharge rarely looks like an error. It looks like a well-formed line that happens to disagree with the contract.
| Where the overcharge originates | What the invoice shows | Why it slips through |
|---|---|---|
| Contract price compliance | Billed at standard list price, not the negotiated net price | Matching confirms the PO was fulfilled, never that the price was the agreed one |
| SPA / Special Pricing Agreement not applied | Full list price on a line that carries a claim-back | The SPA lives in a separate agreement the AP clerk cannot see on the invoice |
| Rebate / back-margin missed | Line correct at gross, but the rebate accrual was never raised | Off-invoice rebates never appear on the line at all |
| Surcharge added off-file | Alloy, metal or small-order surcharge outside the price file | Surcharges are legitimate line items, so nothing looks malformed |
| Unit / price-unit mismatch | Price right per unit but billed against the wrong order price quantity | Reads as a price variance even though the per-unit figure is correct |
Three-way match only proves the PO, receipt and invoice agree on quantity and existence — it never checks the billed price against the contract, which is the single most common source of off-contract spend and silent spend leakage. When the figure drifts from the agreed price, that gap is an invoice price variance; and sometimes, when a wrong order price quantity is in play, the error says price when the cause is units.
Before and after: paying first vs. disputing first
| Pay now, reconcile later | Block, prove, resolve |
|---|---|
| Overpayment leaves the building and sits in the ledger until a recovery audit finds it | The variance is caught at matching, before any cash moves |
| A short-payment opens an unexplained chargeback the supplier disputes line by line | A credit note references the original invoice, so both ledgers reconcile cleanly |
| The agreed net price, SPA claim or rebate is never applied and quietly becomes off-contract spend | Contract price compliance is proven per line against the price file in force |
| The error recurs every cycle because nothing upstream changed | The price file or agreement is corrected once, so the next invoice matches |
| Spend data overstates true net-net cost and distorts every downstream margin figure | Spend reflects the real net-net cost the moment the credit posts |
Dispute it properly — do not just short-pay the difference
- 1Document the variance against what was agreed
Line it up side by side: the PO net price, the price-file version in force on the day of supply, and the invoice line. Quantify the delta and its extended value before you contact anyone. A price list diff turns the billed file against your agreed file into a line-by-line variance list in seconds.
- 2Block the invoice for payment — never short-pay
A short-payment creates an open item on both sides and an unexplained chargeback the supplier will dispute. Hold the invoice instead. If the overcharge never even tripped a block, your price-variance tolerance may be set too wide.
- 3Raise the discrepancy with evidence
State the agreed price, the billed price, the delta, and the mechanism you expect. A specific claim with the price-file version attached resolves far faster than “the invoice looks high”.
- 4Agree the instrument, not a quiet adjustment
Settle on a supplier credit note (credit memo) for the difference, or a debit memo you issue — each referencing the original invoice. Do not let the correction become a silently adjusted payment that neither statement explains.
- 5Post it and close the accrual
Clear the block, match the credit to the original invoice, and if a rebate, SPA claim or back-margin sat behind the overcharge, raise the accrual so the recovery lands in your spend data rather than waiting for a recovery audit.
Build a wrong-price checklist into your AP process
Why identity resolution is the real fix
A supplier billing the wrong price is rarely a one-off keying mistake; it is a sign that two systems disagree about what was agreed. Your contract, price file or SPA says one thing and the supplier’s billing engine says another, and three-way match — which only proves the PO was fulfilled — never arbitrates between them. The durable fix is to resolve every invoice line to one trusted record that carries the agreed net price, the active agreement and the right unit, so each billed figure is checked against the price that was genuinely in force. That is the whole job of reconciling invoices against trusted catalog data: the dispute becomes the exception, not the monthly routine.
Related
Free tool
Price List Diff (Old vs New File)
Diff the billed file against your agreed file to produce a line-by-line variance list for the dispute.
Tool
Margin & Markup Calculator
Quantify what an overcharge does to the margin on a line before you decide how hard to push the claim.
Tool
Product Record Diff
Compare two records to confirm the billed item is the one your price file was negotiated against.
Guide
The Error Says Price. The Cause Is Units.
When a wrong order price quantity makes a correct price look like a variance.
Guide
SAP Price Variance Tolerance Is Not Working: Why
Why a wrong price slips through the block, and how tolerance key PP actually behaves.
Guide
Margin Leakage in Supplier Price Files
The mismatches and mis-mapped lines that erode margin before an invoice ever arrives.
Playbook
Map Supplier Attributes to Your Schema
Resolve supplier prices, units and agreements onto one canonical product model.
Glossary
Credit Note vs Debit Memo
Which instrument corrects a wrong invoice, who issues it, and how each one posts.
FAQ
What counts as a supplier invoicing the wrong price?
It is any line billed at a price other than the one you agreed and that was in force on the day of supply — not just an obvious typo. In industrial distribution the common cases are being billed at the standard list price instead of your negotiated net price, a quantity break or discount group that was not applied, a Special Pricing Agreement whose claim-back was ignored, a surcharge added outside the price file, or a per-unit price that is correct but billed against the wrong quantity. The goods and the total may look plausible; the fault is that the line disagrees with the contract. That gap is an invoice price variance, and it is off-contract spend until it is corrected.
Should I short-pay an invoice that's priced wrong, or pay in full and claim it back?
Neither. Short-paying opens an unexplained chargeback the supplier disputes line by line, and paying in full means the overpayment leaves the building and only a later recovery audit might claw it back. Block the invoice for payment while the dispute is open, prove the variance against the agreed price, and resolve it with a credit note from the supplier for the difference — or a debit memo you issue — so both ledgers reference the original invoice and reconcile cleanly. The block is the control that keeps cash from moving before the price is agreed.
What's the difference between a credit note and a debit memo when correcting a supplier invoice?
Both correct an overcharge; they differ in who issues the document and which direction it adjusts. A credit note — also called a credit memo — is issued by the supplier and reduces what you owe them for the difference, referencing the original invoice. A debit memo is raised by you, the buyer, to charge the supplier back for the overbilled amount. Most disputes resolve with a supplier credit note because it keeps the supplier’s statement and your purchase ledger aligned; a debit memo is used when you need to drive the correction yourself. Whichever instrument is used, it should point at the original invoice so the two documents net to the agreed value.
Does three-way matching catch a wrong price?
Usually not. Three-way matching confirms that the purchase order, the goods receipt and the invoice agree on quantity and that the goods exist — it proves the PO was fulfilled, not that the price was the one you negotiated. A line billed at list price instead of your net price, or with an unapplied SPA or rebate, passes a quantity-based three-way match untouched. Catching a wrong price needs a separate check of each line against the agreed price file and contract record, which is contract price compliance, not PO reconciliation.
How do I stop the same supplier billing the wrong price every month?
Fix the error at its source rather than disputing each invoice. A recurring overcharge almost always means two systems disagree about what was agreed: your price file or contract record says one thing and the supplier’s billing engine says another. Correct the agreed net price, discount group, SPA or conversion factor in the record every line is checked against, so the next invoice matches on its own. If the variance never even triggered a block, the tolerance is likely set too wide and needs tightening before the fix will show.
REVIEW-NOTES
- Glossary pair deferred (not a content error). The
## Relatedblock links to the glossary pairglossary/credit-note-vs-debit-memo, which does not exist yet. It is in<Card>form only (not audit-checked) andrelatedSlugsis omitted, so the build stays green; the link is a live broken link until that sibling ships. Add the inline cross-link and therelatedSlugsentry in the final cross-link commit (brief Workflow step 6) once the glossary entry exists, and have it link back here. - Accuracy check. The only ERP message numbers used are M8 083 (price variance, type configurable — phrased per brief accuracy rule 2) and M8 478 (its credit-memo twin). Both trace to the brief appendix (SAP price-variance section). No ERP error string is quoted verbatim; no Dynamics 365 / Business Central message text is used. No statistics are cited. No Claro figures appear, so no “illustrative” label is needed.
Claro
Stop maintaining this by hand
Claro keeps product and supplier data trusted as catalogs change — matching, deduplication, enrichment, and validated write-back into the systems you already run.
Book a demo