Debit Memo vs Credit Memo: The Difference Explained

A credit memo reduces the amount owed on an invoice. A debit memo increases it. That is the whole difference in one line, though which party issues the document and what it does to your books depends entirely on which side of the transaction you sit on. In accounts payable, a credit memo from a vendor lowers your liability to them. A debit memo you issue to a vendor tells them you are paying less than they billed, and why.

Both documents exist because invoices are wrong often enough that reissuing them every time would be chaos. Instead of voiding an invoice and starting over, the parties adjust it with a memo that references the original. The audit trail stays intact and the correction is visible.

Debit memo vs credit memo at a glance

What is a credit memo?

A credit memo, sometimes written credit memorandum or credit note, is a document a seller issues to reduce the amount a buyer owes on a previously issued invoice. It always references the original invoice number and states the amount and reason for the reduction. The vendor is acknowledging that you owe less than they originally billed.

The usual triggers are returned goods, a shipment that arrived damaged, a billing error where the vendor charged the wrong price or quantity, or a discount agreed after the invoice was already cut. If you ordered 100 units at $40 and 12 arrived broken, the vendor issues a credit memo for $480 against the original invoice. You then pay $3,520 instead of $4,000.

What is a debit memo in accounts payable?

A debit memo, or debit note, is a document that increases the amount owed on a transaction, or formally notifies the other party that you are charging them for something. In accounts payable, a debit memo is most often something you issue to a vendor: you received 88 usable units of the 100 you were billed for, so you send a debit memo for the shortfall and pay the reduced amount.

Vendors also issue debit memos to buyers. If a supplier undercharged you, forgot to bill freight, or applied the wrong tax rate, they can issue a debit memo that adds the difference to your balance rather than reissuing the whole invoice. Banks use the same term for account charges, which is a source of endless confusion but the same underlying idea: a document that increases what one party owes another.

Is a credit memo a refund?

No. A credit memo reduces an outstanding balance. A refund returns cash. If you have already paid the invoice in full and the vendor issues a credit memo, you now hold a credit you can apply against a future invoice from that vendor. You get money back only if you specifically request a refund and the vendor agrees to cut a check or reverse the payment.

This distinction matters at year end. Unapplied vendor credits sitting on your books are an asset you have already paid for. AP teams that never reconcile them effectively hand the vendor an interest-free loan. Pulling open credits during vendor statement reconciliation is how most companies find them.

Who issues a debit memo?

Either party can, which is what makes the term slippery. The buyer issues a debit memo to claim money back from a vendor for short shipments, damaged goods, quality failures, or overcharges. The seller issues a debit memo to add a charge the original invoice missed. Some industries have strong conventions. In retail and consumer goods, buyers routinely issue debit memos, called chargebacks, against suppliers for compliance failures like late delivery or bad labeling.

The practical rule in AP: if the document increases the amount you owe, treat it as a debit memo from the vendor and route it through the same approval path as an invoice. If you are the one raising it, make sure someone with authority to dispute a vendor charge signs off before it goes out.

Does a credit memo reduce accounts payable?

Yes. A vendor credit memo debits accounts payable and credits whichever account the original charge hit, typically an expense account or inventory. The net effect is that your liability to that vendor drops by the credit amount.

The journal entry is the mirror image of the original invoice. If the invoice debited Inventory $4,000 and credited Accounts Payable $4,000, a $480 credit memo debits Accounts Payable $480 and credits Inventory $480. Your payable to that vendor is now $3,520. If you are unsure how the original entry was booked, our guide to the accounts payable journal entry walks through both sides.

When to use a debit memo instead of a credit memo

Use whichever document matches the direction of the correction and the party making it. If your vendor made the mistake and agrees to fix it, ask them for a credit memo. It is cleaner, because the reduction flows from the party that issued the original invoice and both sets of books reconcile automatically.

Issue a debit memo when the vendor disputes the problem, is slow to respond, or when your industry convention expects the buyer to raise the claim. You are documenting a short payment. Expect the vendor to either accept it, issue an offsetting credit memo, or dispute it. Either way you have a written record of why the remittance did not match the invoice, which is exactly what an auditor will ask for.

How memos break automated matching

Credit and debit memos are a common source of AP exceptions because they do not look like invoices. They carry negative amounts, they reference an invoice number rather than a purchase order, and they often arrive by email weeks after the original document. Systems that expect a clean invoice to PO to receipt match choke on them.

Two problems follow. First, the memo sits unprocessed and the credit is never applied, so you pay the vendor the full invoice amount and lose the money. Second, when the same memo arrives twice, or when a vendor reissues a corrected invoice alongside a credit memo for the original, you get the conditions that produce duplicate payments. Anyone who has had to find duplicate invoices after the fact knows how much cheaper prevention is.

Handling memos in an automated AP workflow

Good AP automation treats a credit memo as a first-class document type rather than a broken invoice. The system reads the document, recognizes the negative amount and the referenced invoice number, links it to the original, and holds the credit against the vendor until it is applied to a payment run. Modern invoice data capture handles this by extracting header fields and line items from the memo the same way it does from an invoice, so nothing depends on someone opening the PDF. Teams that process high volumes of vendor documents often pair that with dedicated AI invoice data extraction to structure the line items before they ever reach the ERP.

The workflow rules are straightforward. Route memos above a threshold for approval, just like invoices. Never apply a credit to a vendor until the referenced invoice is located. Reconcile open vendor credits monthly, not annually. And flag any vendor whose credit memo volume is climbing, because a rising memo count usually means something upstream is broken, whether that is a receiving process that keeps recording the wrong quantities or a pricing agreement that never made it into the purchase order.

Getting the memos right is unglamorous work. It is also where a surprising amount of cash hides, sitting as unapplied credits on vendor accounts that nobody has reconciled since the last audit. Building the process into accounts payable software means the credits get applied before the check goes out, which is the only point where they are worth anything.