What is a debit note?

The buyer's version, which is the common one

Something arrived short, damaged, late or wrong, and the buyer has already been invoiced for it. Rather than paying and hoping, the buyer raises a document setting out what happened, what it cost and how much they are withholding, and sends it with the supporting evidence. It is a claim, not a correction, because a buyer cannot amend a seller's ledger. The seller reviews it and either issues a credit note, which is the correction, or pushes back. Manufacturing and hospitality use these constantly, and the good ones are specific: a delivery docket number, the quantity short, the date, the consequence and a figure. The bad ones say short delivery, four hundred dollars, and start an exchange that takes a month.

The seller's version, which causes more confusion

An invoice went out too low. A rate was applied from an expired price list, a line was omitted, freight was left off. Some sellers raise a debit note to signal the shortfall and follow it with a supplementary invoice; others simply issue the second invoice with a note explaining it. Either is defensible, and the second is usually cleaner, because a debit note is not a tax invoice and the buyer cannot claim tax credits against it. Where the undercharge is material, telling the customer before the document arrives is worth more than the document itself, since an unexpected extra charge is the fastest route into a dispute over work that was otherwise finished and accepted.

Why it is not an invoice

An invoice charges for a supply. A debit note asserts that a figure already recorded is wrong. That distinction matters in the accounts, because a buyer's debit note does not create a receivable in their books in the way an invoice does, and a seller's debit note does not create a taxable supply. Both are notifications that sit outside the sales and purchase ledgers until the other party acts. Treating one as an invoice is the classic error: a buyer posts their own debit note as revenue, the seller ignores it, and two ledgers drift apart by an amount neither side can find at year end without going through the correspondence line by line.

What a good one contains

A clear heading saying debit note, so nobody processes it as an invoice. Your own reference number from a separate sequence. The other party's invoice number, purchase order number and date, since matching is the whole purpose. An itemised breakdown, with the direct amount and any consequential cost shown separately so the seller can accept one and argue about the other. The evidence attached rather than referred to, which usually means a photograph, a delivery docket or a weighbridge ticket. A date by which a response is expected. And a plain statement of what you want, which is almost always a credit note rather than a payment, because a credit is easier for the seller to issue and lands faster.

How to keep these out of a dispute

Raise it early. A claim made within days of delivery, while the goods and the driver's paperwork still exist, is settled quickly; the same claim made when the invoice falls due looks like an excuse for late payment and is treated as one. Deal with each claim separately rather than accumulating them into a quarterly reckoning nobody can unpick. Never simply short pay an invoice without a document, because the seller's system records a partial payment with no explanation and their collections process starts automatically. And agree the mechanism in the supply terms up front, naming the window for claims and the evidence required, so the conversation is about the facts rather than about whether the claim is admissible at all. Keep a simple log of claims raised and settled per supplier as well. Patterns show up quickly, and a supplier with a recurring shortfall is a supply problem to fix at the contract review rather than a paperwork problem to keep processing every month.

Questions people ask