Few areas of AP have more terminology confusion than the credit space. Credit notes, debit memos, credit memos, vendor credits, supplier credits, customer credits. The same instrument is called different things by different parties, and different instruments are sometimes called the same thing.
The confusion is not academic. Posting a credit note as a debit memo, or treating a customer credit memo as a vendor credit, produces ledger errors that take weeks to unwind during audit prep.
This article defines each instrument clearly, explains how they show up in common ERPs, and lays out the standardization that most finance teams need but rarely formalize.
The Three Core Instruments
Despite the proliferation of terms, there are only three core instruments in play. Everything else is a label variation.
Credit note (issued by the supplier)
A credit note is a document issued by a supplier to a buyer reducing the amount the buyer owes. It functions as the inverse of an invoice. If the supplier originally invoiced $10,000 and later issues a credit note for $1,500, the buyer now owes $8,500.
Credit notes typically carry their own document number, are issued in the same format as the supplier's invoices, and reference the original invoice or transaction they relate to. From the buyer's AP perspective, a credit note is the most common form of supplier credit.
Debit memo (issued by the buyer)
A debit memo is a document the buyer issues to a supplier, asserting that the supplier owes the buyer money. It is the buyer initiated equivalent of a credit note.
Debit memos are common in disputed billing situations where the buyer wants to formally reduce the amount owed before the supplier has issued a credit note. The buyer creates the debit memo, posts it against the invoice, and pays the net amount. The supplier may later acknowledge the debit memo by issuing a matching credit note, or may dispute it.
The direction is the key thing to understand. A debit memo originates with the buyer. A credit note originates with the supplier. Both reduce what the buyer owes, but the documentation comes from different parties.
Customer credit memo (different context entirely)
A customer credit memo is what a company issues to its customer when reducing what the customer owes for sales transactions. This sits in accounts receivable, not accounts payable.
The confusion arises because credit memo and credit note are sometimes used interchangeably. In the AR context, credit memo is the standard term. In the AP context, credit note is more common but credit memo is also used. Treating an AR credit memo as a vendor credit produces an immediate ledger error.
Why the Language Creates Errors
Most posting errors in credit processing trace back to one of three confusions.
Direction confusion
An AP clerk receives a document titled credit memo from a vendor and assumes it functions like a customer credit memo (the AR concept). They post it incorrectly, reducing the wrong account.
The fix is to focus on who issued the document, not what it is called. If a supplier issued it and it reduces what you owe them, it is a vendor credit regardless of whether the supplier titled it credit memo, credit note, or adjustment.
Document type mismatch in the ERP
Most ERPs have distinct document types for credit notes versus debit memos. Posting a credit note as a debit memo triggers a different workflow and creates reconciliation issues later. AP clerks often default to one document type because it is the one they remember, regardless of which one is actually correct.
Reason code conflation
Credits come for many reasons. Returns, billing errors, rebates, dispute resolutions, service level penalties. The reason code matters for analytics and root cause work later. Lumping every credit into a generic adjustment code makes trend analysis impossible.
How the Major ERPs Handle This
Standardization across ERPs is imperfect, but a few patterns are consistent enough to be worth knowing.
SAP
SAP uses the term credit memo for both AR and AP, with different document types distinguishing them. Vendor credit memos are typically document type KG. Subsequent credits and subsequent debits are separate document types again. The terminology overlap with AR is one of the most common sources of confusion in SAP shops.
NetSuite
NetSuite uses vendor credit as the AP term and credit memo as the AR term, which is helpful for clarity. The vendor credit can be applied against vendor bills directly through the application workflow.
Oracle and Oracle Fusion
Oracle uses credit memo for AP credits, with document subtypes distinguishing them from invoices. Debit memos are a separate transaction type. Reason codes are well supported but rarely fully used in practice.
Microsoft Dynamics
Dynamics uses purchase credit memo for AP credits and sales credit memo for AR credits. The naming convention is helpful but the configuration of credit memo journals varies significantly between implementations.
What to Standardize Internally
The language confusion is unavoidable at the vendor side because suppliers use whatever their own systems generate. What finance teams can control is internal language and posting discipline.
- Adopt one term internally for AP credits and use it consistently. Vendor credit is the cleanest because it has no overlap with AR terminology.
- Train AP clerks to identify the instrument by who issued it, not by what it is called. Supplier issued and reducing your payable is a vendor credit, regardless of label.
- Maintain a small set of reason codes (returns, billing correction, rebate, dispute resolution, SLA penalty, duplicate payment recovery) and require one on every posting.
- Reserve debit memo as a distinct instrument used only when the buyer is initiating the credit assertion before a supplier credit note arrives.
- Document the standardization in the AP procedures and review it during onboarding for new AP staff.
Start Here
Pull a sample of 20 credit postings from the last quarter. Look at the document type used, the reason code (if any), and the GL account affected. The variance in how similar transactions get posted is usually larger than expected, and that variance is the gap to close.
Define the internal standard, train the AP team, and review postings monthly for the first quarter to make the change stick.
