Debit notes and claims in Indian modern retail

You invoiced for a full vehicle. The payment that lands is smaller. Somewhere in the vendor portal there is a document explaining the difference, raised weeks ago, and the window to argue about it may already have closed.

A debit note is a ledger entry, not a request

A debit note is the chain’s formal statement that it owes you less than your invoice says. It is posted into their accounts payable ledger and netted off your next payment run. That is the structural fact everything else follows from: the money leaves before the conversation happens. You are not being asked to approve a deduction, you are being told one has already been applied, and the work of getting it reversed is yours.

The reversal instrument is a credit note the chain raises once it accepts your evidence. Until that credit note exists in the ledger, nothing has been resolved, whatever was agreed on a call.

The categories a chain raises them under

Labels differ between chains but the substance is consistent.

• Quantity shortage. The goods receipt records fewer units than the invoice. This is the highest-volume category and often the most winnable.
• Damage. Cases found damaged at the distribution centre, or damaged stock returned from stores.
• Quality or specification rejection. Residual shelf life below the norm on arrival, an unscannable barcode, an MRP or net quantity that does not match the article master, batch or labelling non-compliance.
• Scheme and promotion claims. The chain funded a consumer offer and is billing you the agreed share of it.
• Expiry and returns. Near-expiry or unsold stock taken back under whatever return provision your terms contain.
• Contractual charges. Handling, distribution or agreed allowances that appear as a note rather than as a line on an invoice.

Classify every note into one of these on the day it appears. A brand that only knows its total deduction number cannot fix anything, because these categories have different causes and different owners inside your own business.

The proof was captured at dispatch or it does not exist

The asymmetry is simple. The chain holds a goods receipt signed inside its own warehouse. You hold an invoice. Where those two disagree, the receipt is the default truth unless you can produce something from the moment the stock left you.

That evidence has to be captured routinely, by the dispatch team, on every vehicle, long before anyone knows which shipment will be disputed. In practice that means sealed carton count and seal number recorded against the invoice, dated photographs of the loaded and sealed vehicle, the transporter document showing case count, the gate pass, and the batch and residual shelf life picked, recorded against the invoice number rather than only against a production date. Rejections at the gate have their own administrative causes worth understanding separately.

Scheme claims fail for a different reason. The offer genuinely ran, so the note is not wrong in principle, but nobody kept the written approval stating the mechanic, the rate, the funding split and the exact period. Without it you pay whatever the claim says. Treat every promotion approval as a document to file, not an email to reply to. Its rates come out of the same schedule of trade terms you agreed at listing, so the two should reconcile line for line.

Contest the note, then fix what generated it

Every note deserves two questions, and most brands ask only the first. Can I win this one, and what produced it.

The second question is where the money actually is. Shortages concentrated on one distribution centre are usually a loading or palletisation problem at your end rather than dishonesty at theirs. Damage concentrated on one SKU is packaging, not handling. Repeated shelf life rejections mean your dispatch discipline is releasing stock too late in its life. A quality note that keeps recurring on the same article is frequently a master data error that was never corrected: a case configuration or an MRP recorded once, wrongly, and reapplied to every receipt since.

Winning individual notes while the generator runs untouched is how a small leak becomes a permanent percentage of the account. Track deductions as a rate on dispatch value, split by category and by site, and treat a rising line as an operations defect with an owner rather than a finance problem to absorb.

Ageing, and why silence becomes acceptance

Every chain has a window inside which a note can be contested. It is short and specific to that chain, so read it out of your own terms document rather than assuming. Once it closes the note is settled by default, and nobody will write to tell you the window has passed.

Keep an ageing view of open notes by date raised, not by the date you discovered them, because the clock started when they raised it. Uncontested notes also change how you are treated over time. A supplier that accepts everything is a supplier whose next claim gets less scrutiny before it goes out.

Reconcile against the remittance, not the invoice

The reason this surfaces late is that these do not arrive as claims. They arrive as a smaller payment. If your finance process only checks whether invoices were raised correctly, you will meet the deduction at year end, when every window has already closed.

Tie the rhythm to the payment cycle instead. On every remittance, pull the vendor ledger from the portal, match each note to the invoice it relates to, classify it, and either accept it with a stated reason or contest it with the dispatch evidence attached. Keep one register holding note number, category, amount, evidence status, date raised and days remaining. It costs a couple of hours per cycle once the habit exists, and it is the only version of this that works, because the alternative is reconciling a year of notes against shipments nobody remembers. It also connects straight to the working capital you have tied up in the account, since an uncontested deduction is a permanent reduction in what that account was ever going to pay you.