Credit Memo vs Debit Memo: Meaning, Direction, and AP Use

A credit memo usually reduces a balance. A debit memo may increase or reduce one, depending on who issued it and which account the document affects. In seller billing and accounts receivable, a debit memo generally increases the customer’s balance; in buyer accounts payable, a buyer-created debit memo can reduce the amount owed to a supplier.

That qualification is the key to credit memo vs debit memo comparisons. The words credit and debit do not provide a safe posting instruction by themselves.

Perspective	Typical issuer	Document	Balance affected	Usual effect
Seller / accounts receivable	Seller	Credit memo	Customer receivable	Decreases the customer’s balance
Seller / accounts receivable	Seller	Debit memo	Customer receivable	Increases the customer’s balance
Buyer / accounts payable	Supplier	Credit memo	Supplier payable	Decreases the buyer’s payable
Buyer / accounts payable	Buyer	Debit memo	Supplier payable	Can decrease the payable by recording a claim against the supplier
Bank statement	Bank	Credit or debit memo	Bank account	Credit usually increases the account balance; debit usually decreases it

A credit memo is an adjustment document that usually lowers the balance on the account being corrected. A debit memo is also an adjustment document, but its direction depends on the document flow. This is why an AR definition can say that a debit memo raises an amount due while an AP system uses a debit memo to reduce a payable. Both can be correct within their stated perspectives.

Before assigning a sign or posting treatment, identify four facts: who issued the memo, who received it, which balance or open item it adjusts, and how the ERP defines that document type.

Why the same memo label can move balances in opposite directions

From a seller’s accounts-receivable perspective, the direction is usually straightforward. A credit memo reduces the customer’s outstanding balance, perhaps after returned goods, an overcharge, or a post-sale allowance. A seller-issued debit memo increases the receivable, commonly to correct an underbilling or add a charge that was omitted.

That convention is documented in Ohio's accounts-receivable process manual: within the state’s AR correction process, a debit memo increases a customer’s balance and a credit memo decreases it. This is a useful example of an AR convention, not a rule that determines how every AP system uses the same labels.

The view changes when the account being adjusted is a buyer’s payable:

• A supplier-issued credit memo acknowledges that the buyer owes less. The buyer applies it against the supplier’s open balance.

• A buyer-created debit memo records the buyer’s claim that the supplier balance should be reduced. Reasons include a shortage, damaged goods, a return, a price discrepancy, or another deduction that the buyer initiates.

In that AP convention, both documents can reduce the payable. The practical distinction is who initiated the adjustment: the supplier issued the credit memo, while the buyer created the debit memo. Some organizations send the buyer-created document to the supplier; others use it primarily as an internal ERP document while the discrepancy is resolved.

This also answers who issues a debit memo: the seller may issue one to increase a customer receivable, or the buyer may create one to support a claim against a supplier. The document title cannot identify the issuer reliably across systems.

Nor is a debit memo inherently positive or negative. A seller’s system may display a debit memo as a positive addition to the customer balance. A buyer’s AP system may display a debit memo as a negative document because it reduces the payable. An imported document might show its face amount as positive while the ERP document type supplies the negative accounting effect.

For posting purposes, ask whether the memo increases or decreases the relevant open balance, rather than treating the printed sign as the answer. The ERP’s configuration determines whether that effect is represented by a positive amount, a negative amount, or a separate transaction type.

---

Memo and note terminology: where the words match and where they do not

Credit memo is common US accounting language for what many other markets and systems call a credit note. Both usually name a document that reduces an existing customer or supplier balance. The vocabulary differs, but the underlying downward adjustment is generally the same.

The relationship between debit memo and debit note is less dependable. A system may use the terms interchangeably for the same adjustment flow. Another may reserve debit memo for a buyer-created supplier claim while using debit note for a seller-issued increase. Regional practice, trading-partner terminology, and ERP configuration all influence the label.

The safe distinction is between name and effect:

• The name identifies the document type within a particular business or system.

• The effect comes from the issuer, transaction flow, affected account, and system configuration.

For example, receiving a document titled “debit note” does not establish whether AP should add to or subtract from the supplier balance. AP still needs to determine who raised it, what prior transaction it references, and how that document type is configured.

This terminology map should not be stretched into adjacent questions. The separate comparison of how credit notes differ from invoices covers the invoice boundary, while debit note definitions and journal entries provides the broader debit-note treatment. For a memo-versus-memo decision, the relevant point is narrower: credit memo and credit note commonly match, while debit memo and debit note require a system and document-flow check before their direction is known.

---

What AP should verify before posting a memo

Treat the memo as an adjustment to a source transaction, not as a standalone amount to enter from its title and face value.

1. Locate the referenced invoice or purchase order. Confirm that the supplier, invoice number, PO number, currency, and legal entity correspond to an open transaction in the AP system.

2. Validate the reason and amount. Compare quantities, prices, tax, freight, returns, or allowances with the supporting records. The adjustment should agree with the approved discrepancy, not merely with the amount printed on the memo.

3. Identify the document flow. Determine whether the supplier issued a credit or the buyer raised a claim against the supplier. This establishes the commercial meaning before ERP signs and transaction codes are considered.

4. Confirm the ERP document type and sign convention. Check how that type changes the open payable. Do not add a minus sign automatically because the document is called a credit memo, or retain a positive sign simply because the source document prints a positive face amount.

5. Apply the adjustment to the correct open item. Link it to the invoice or invoices it changes so that the supplier account, payment proposal, and aging report retain the relationship.

6. Preserve the audit trail. Keep the memo, approval, discrepancy evidence, and source-transaction reference together. If the data is exported, retain a document-type field and the source reference so the amount’s direction remains intelligible outside the ERP.

Sign normalization deserves particular attention when adjustment documents move from PDFs into spreadsheets or import files. A supplier may print “500.00” on a credit memo, while the AP system expects the document type to make that amount reduce the payable. Converting every visible amount to a negative value without considering the target system can reverse the adjustment twice. Teams processing documents outside the ERP can use the same distinction described in credit note data extraction and sign handling: preserve the document type, define the intended accounting direction, and apply one consistent export convention.

Send the memo for exception review when it:

• covers several invoices without allocating the amount;

• has no usable invoice or PO reference;

• appears to duplicate an adjustment already posted;

• conflicts with receiving, return, pricing, or approval records; or

• names an entity or currency that does not match the source transaction.

A four-question test for any credit or debit memo

When a memo label is unfamiliar or conflicts with a definition found elsewhere, work through these questions in order:

1. Who issued it? A supplier credit and a buyer-created debit memo can support the same reduction in AP, but they originate on opposite sides of the transaction. A seller-issued debit memo usually belongs to an AR flow that increases the customer balance.

2. Who received it? Confirm whether the document was sent by a supplier to a customer, raised by a buyer against a supplier, or created by a bank. The recipient helps locate the accounting perspective.

3. Which account or open item changes? Identify the customer receivable, supplier payable, bank account, or specific invoice being adjusted. The direction must be stated against that balance, not as an unqualified positive or negative.

4. How does the ERP define the document type? Check the transaction code, posting rule, and expected amount sign. Two systems may use the same label for different flows, or different labels for the same flow.

The combined answers produce a defensible direction. A seller-issued debit memo in AR generally increases the receivable. A seller-issued credit memo reduces it. In AP, a supplier credit memo reduces the payable, and a buyer-created debit memo may also reduce the payable by recording the buyer’s claim.

Bank statements use the terms differently from vendor-document workflows. A bank debit memo records an adjustment that reduces the account balance, such as a fee or correction; a bank credit memo records one that increases the balance. Those entries adjust the bank account and should not be used to infer how an ERP treats a supplier debit or credit memo.

If the issuer, source transaction, affected balance, or system convention cannot be established, leave the memo unposted and resolve the exception. The label is evidence about the document, not the posting instruction.