Debit Memo: What It Is, Examples, and How It Works

A debit memo is one of those accounting documents that means slightly different things depending on who issued it, which is exactly why it causes so much confusion. A seller can send one to a buyer to fix an undercharge, and a buyer can send one to a vendor to claw back an overcharge. Same name, opposite direction. This guide explains what a debit memo is in plain terms, how it differs from a credit memo and a regular invoice, what it means when it comes from a vendor, and how accounts payable teams record one. Real examples are included for each case.

What is a debit memo?

A debit memo is a document that adjusts an existing invoice by increasing the amount one party owes another, without issuing a brand-new invoice. It references the original bill, states the extra amount, and explains why. Sellers use it to correct an undercharge or add a fee; buyers use it to reduce what they owe a vendor.

The word "debit" is what trips people up. A debit memo raises a balance on the account of whoever receives it. When a seller sends a debit memo to a buyer, it adds to the buyer's payable. When a buyer sends one to a vendor, it debits (reduces) the buyer's own accounts payable to that vendor. The direction depends entirely on who issued the memo and why, which is the single most important thing to get straight before reading the rest of this guide.

What is a debit memo in accounting?

In accounting, a debit memo records an adjustment to a previously booked transaction. It posts a debit entry that changes the outstanding balance between a buyer and a seller, tied back to the original invoice. The memo creates an audit trail so both sides can see what changed, by how much, and for what reason.

Because it is linked to an existing invoice rather than standing alone, a debit memo keeps your books clean. You are not voiding the first invoice or creating a duplicate; you are layering a documented correction on top of it. At payment time, accounting systems net the memo against the related invoice, so the vendor or customer pays or receives the adjusted total rather than two separate amounts.

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

A debit memo and a credit memo move money in opposite directions. A debit memo increases the amount owed; a credit memo decreases it. If a seller undercharged a customer, they issue a debit memo to collect the difference. If they overcharged or took a return, they issue a credit memo to give money back.

Here is a worked pair. A distributor invoices a grocery chain $1,000 but should have billed $1,150 because of a missed line item, so it sends a $150 debit memo to recover the shortfall. In the reverse case, half the shipment arrives damaged, so the distributor sends a $500 credit memo to lower the balance. One pulls the total up, the other pushes it down, and both reference the same original invoice instead of replacing it.

What is the difference between a debit memo and an invoice?

An invoice is the original request for payment; a debit memo is an after-the-fact adjustment to that invoice. The invoice establishes the full amount due for goods or services delivered. The debit memo comes later, only when something about that amount needs to change, and it always points back to the invoice it is correcting.

The practical difference is scope. An invoice can stand on its own as a complete bill, but a debit memo cannot. It is meaningless without the invoice it adjusts, because it only states the change, not the whole transaction. Treating a debit memo like a separate invoice is a common bookkeeping mistake that leads to double-counting and inflated payables.

What is a debit memo from a vendor?

A debit memo from a vendor is a notice your supplier sends to increase what you owe them, usually to correct an undercharge on an earlier invoice. It might cover an item left off the original bill, a price that was set too low, or an agreed surcharge. For your accounts payable team, it raises the balance due to that vendor.

Do not confuse this with a debit memo you issue to a vendor, which does the opposite. When the supplier sends it, your payable goes up; when you send it, your payable goes down. The label on the document tells you who created it, but the safest move is to read the reason and confirm the direction before you post anything, because vendors and buyers both use the same term for memos that affect balances in opposite ways.

What is a debit memo in AP?

In accounts payable, a debit memo is most often a document your company issues to a vendor to reduce the amount you owe them. It is raised when an invoice does not match the purchase order, delivery, or contract, such as short shipments, damaged goods, returns, or overbilling. It debits your accounts payable, lowering the liability recorded for that vendor.

This buyer-issued version is the backbone of clean vendor accounts. When AP catches a discrepancy during invoice processing, the team generates a debit memo that documents the deduction and links it to the original invoice. At payment, the memo is netted against open invoices so the vendor is paid the corrected amount. Catching those discrepancies in the first place depends on being able to compare the invoice line by line against what was ordered, which is far easier when the invoice is structured data rather than a flat PDF. Our guide to three-way matching in accounts payable covers how that comparison works in practice.

What is a debit memo on a bank statement?

On a bank statement, a debit memo is a deduction the bank makes from your account for fees or charges, shown separately from your own transactions. Common examples are monthly service charges, overdraft fees, wire transfer costs, and returned-check penalties. It reduces your balance and is the bank's way of telling you why money left the account.

This is the same word used in a different context, and it follows the same logic: a debit memo records a charge against an account. When you reconcile the bank statement, these memos have to be matched and recorded in your books so your cash balance ties out. Spotting them is a routine part of monthly reconciliation, the same way matching vendor charges is part of vendor statement reconciliation.

What is a debit memo request?

A debit memo request is an internal document that asks for a debit memo to be created, used in ERP systems like SAP before the actual memo is issued. It captures the proposed adjustment, the reason, and the reference invoice, then routes for approval. Once approved, it becomes the basis for the posted debit memo.

The request step exists for control. Rather than letting anyone post an adjustment directly, the request creates a checkpoint where a manager confirms the deduction or charge is justified before it hits a vendor or customer account. It is the same separation-of-duties idea that runs through strong accounts payable controls: the person who spots the discrepancy is not always the one who finalizes the money change.

How do you record a debit memo?

To record a debit memo, link it to the original invoice, post the adjustment to the right account, and net it against the invoice at payment. For a vendor debit memo you issue, that means debiting accounts payable to reduce the vendor's balance and crediting the offsetting account, such as inventory or purchase returns. Always document the reason.

The steps are consistent across accounting systems. First, identify the discrepancy during invoice processing by comparing the invoice to the purchase order and receiving records. Second, generate the debit memo and reference the invoice number so the two stay connected. Third, update the vendor account so the outstanding liability reflects the adjustment. Fourth, when you cut the payment, the system nets the memo against open invoices so the vendor receives the corrected total. The faster part of this is the posting; the slow part is finding the discrepancy buried in a stack of PDFs, which is where converting invoices into clean rows pays off. Teams that want the whole match-and-adjust cycle handled automatically move to an accounts payable automation platform, while teams that work in spreadsheets first need the invoice as structured data they can check against the order.

Turn invoices into data you can check

Most debit memos start with a discrepancy someone had to catch: a price that does not match the PO, a line item billed twice, a quantity that is higher than what arrived. You can only spot those when you can read the invoice as numbers in columns, not as a scanned image. InvoiceXLSX does that step. Upload a PDF or image invoice and get clean Excel or CSV with the vendor, invoice number, dates, totals, and every line item already separated, so comparing the bill to your order takes seconds. From there you can extract invoice data to Excel, pull full invoice line item data for line-level checks, or run a backlog through AI invoice data extraction so every discrepancy that should trigger a debit memo is easy to find before you pay.