Credit Note vs Debit Memo: Fixing a Wrong Invoice

When a supplier bills above the agreed price, the correction runs through one of two instruments, and picking the wrong one leaves the books out of step. A credit note — the same thing most ERPs call a credit memo — comes from the supplier and reduces what you owe, referencing the invoice it adjusts. A debit memo goes the other way: the buyer raises it to charge the supplier back for the overbilled amount or for money owed that never reached a line. Both close the same gap between what was billed and what was agreed. The rule that keeps them clean is the same for either: the document references the original invoice, so the two net to the agreed value and both ledgers reconcile instead of drifting. This entry sits alongside the step-by-step in A Supplier Invoiced the Wrong Price. Now What?.

What a Credit Note and a Debit Memo Each Do

A credit note is the seller correcting its own invoice downward. The supplier issues it, it reduces the amount the buyer owes, and it points back at the invoice it adjusts. It is the standard instrument for a supplier overcharge, because only the supplier can lower its own receivable and the credit keeps the supplier statement and your purchase ledger aligned. Credit memo is simply the name many ERPs give the same document.

A debit memo — also called a debit note — runs from the buyer’s side. The buyer raises it to charge the supplier back, increasing what the supplier owes you. You reach for it when you need to drive the correction yourself: the supplier is slow to credit, or the money owed is a rebate, back-margin or claim that was never billed on a line and so has no invoice line to credit against.

Both instruments correct the same underlying fault — a line that disagrees with the contract, which is an invoice price variance until it is resolved. What differs is direction and who posts the document.

Why correcting a wrong invoice breaks down

Most of the mess comes not from choosing credit note over debit memo but from skipping the instrument entirely, or raising one that references nothing. Short-paying instead of requesting a credit leaves an open item on both sides and an unexplained chargeback the supplier disputes line by line. Paying in full and trusting a later recovery audit to claw the money back means the overpayment has already left the building. And a correction posted as a quiet adjustment — neither a credit note nor a debit memo against the invoice — drifts the supplier statement away from your ledger until someone has to reconcile the gap by hand.

Timing compounds all of this. Payment terms keep running while a correction is argued, so a credit that is agreed but posted late still lets the wrong amount go out the door on the due date — which is why the invoice is blocked for payment first and the instrument settled second. The credit itself then has to be checked, not waved through: a supplier can issue a credit note for the wrong figure just as easily as it billed the wrong figure, and a debit memo the buyer raises can reference the wrong invoice line.

The instrument also has to match the underlying mechanism. A rebate, back-margin or SPA claim treated as a simple price dispute gets the wrong treatment: the accrual is never raised, and the recovery is lost rather than credited. In SAP, a supplier credit memo is posted against the purchase order and runs through the same invoice-verification tolerance checks as the original invoice; SAP issues message M8 478 on a credit memo, whose type is configurable, carrying the same price-variance tolerance text — Price too high (tolerance limit of & % exceeded) — as the message on the invoice it corrects. That is why a credit that is itself priced wrong can block just like the invoice did.

Before and after: ad-hoc adjustment vs matched credit

Which instrument to use when

Deciding between a credit note and a debit memo is a short waterfall, settled before you contact the supplier.

1. Prove the variance against what was agreed. Line up the PO net price, the price-file version in force on the day of supply, and the invoice line. A price list diff turns the billed file against your agreed file into a line-by-line variance list, so you open the dispute with the delta already in hand.

2. Decide who drives the correction. A supplier overcharge on a billed line is cleanest as a supplier credit note — one party posts one document. If you are claiming money that never hit a line, or the supplier will not credit promptly, raise a buyer debit memo instead.

3. Quantify the impact before you push. Work out what the overcharge does to the margin on the line with a margin and markup calculator, so you know whether a line is worth a formal claim or a note on the next order.

4. Reference the original invoice on whichever instrument. The credit note or debit memo must cite the invoice it adjusts, so the two documents net to the agreed value and reconcile without a manual match.

5. Fix the source, not just this invoice. Correct the agreed net price, discount group, SPA or conversion factor in the record every line is checked against, so the next invoice matches and no further credit is needed.

Related

FAQ

What is the difference between a credit note and a debit memo? +

Both correct an invoice that was billed wrong, but they differ in who issues the document and which way it moves the balance. A credit note, issued by the supplier, reduces what the buyer owes. A debit memo, raised by the buyer, charges the supplier back for the overbilled amount. Most supplier overcharges resolve with a credit note because it keeps the supplier statement and the purchase ledger aligned; a debit memo is used when the buyer needs to drive the correction.

Is a credit note the same as a credit memo? +

Yes. Credit note and credit memo are two names for the same instrument — a document the supplier issues to reduce what the buyer owes, referencing the original invoice. Debit memo and debit note are likewise the same thing from the buyer side. The wording varies by ERP and region, not by function.

Who issues a credit note, the buyer or the supplier? +

The supplier issues it. A credit note is the seller correcting its own invoice downward, so it reduces the amount the buyer owes and references the invoice it adjusts. If the buyer wants to initiate the correction rather than wait for the supplier, the buyer raises a debit memo instead, which asks the supplier to credit the difference.

When should I raise a debit memo instead of asking for a credit note? +

Raise a debit memo when you need to drive the correction yourself — the supplier is slow to issue a credit, or your process requires the buyer to record the claim first. It is common for rebate, back-margin and claim recoveries, where the buyer is owed money that was never billed on a line. For a straightforward overcharge, a supplier credit note is usually cleaner because only one party posts a document.

How is a chargeback different from a debit memo? +

A debit memo is an agreed instrument that references the original invoice, so both ledgers reconcile. A chargeback is a unilateral deduction taken at payment, often without an agreed reference, which is why suppliers dispute them line by line. Blocking the invoice and agreeing a credit note or debit memo avoids turning a clean correction into a contested chargeback.

How does Claro help with credit notes and debit memos? +

Claro resolves every invoice line to one trusted record carrying the agreed net price, the active agreement and the right unit, then checks each billed line against it. When a line disagrees with the contract, Claro surfaces the variance with the agreed price, the billed price and the delta already quantified, so the dispute opens with evidence and the right instrument — a supplier credit note or a buyer debit memo — can be raised against the original invoice. Fixing the source record stops the same overcharge recurring.

REVIEW-NOTES

• Sibling Card links are live-broken until the batch ships. The Related block links to glossary/net-net-price and glossary/special-pricing-agreement, both created in this same batch and not yet on disk. They are in <Card> form only (not audit-checked) and relatedSlugs is omitted, so the build stays green; the links resolve once those siblings ship. Add the relatedSlugs entries in the final cross-link commit (brief Workflow step 6).
• Glossary pair is wired. The paired guide guides/supplier-invoiced-wrong-price already carries a Related card to this entry; this entry inline-links back to it. No further action.
• Accuracy check. The only SAP message number used is M8 478 (the credit-memo twin of the price-variance message M8 083), phrased per brief accuracy rule 2 (type configurable). Its short text is quoted verbatim with SAP ampersand placeholders preserved and backticked (Price too high (tolerance limit of & % exceeded)). No Dynamics 365 / Business Central error string is used (none is published). No statistics cited; no Claro figures, so no illustrative label needed. Buyer/seller direction (seller issues the credit note, buyer raises the debit memo) kept generic across ERPs per the brief appendix vocabulary.