Vendor Debit Notes — From Rejected Goods to Formal Recovery
Published: April 14, 2026
A shipment arrives with 100 units ordered but only 92 received. Five of the 92 are damaged. The purchase manager calls the vendor, the vendor promises to send replacements, and the matter is tracked in a WhatsApp group. Three months later, the replacements have not arrived, the purchase manager has moved to a different role, and nobody remembers the details. The organisation absorbed the loss without any formal record of the claim.
This pattern repeats across vendor quality issues, under-deliveries, and price discrepancies. The problem is not that organisations do not notice these issues — they do. The problem is that noticing and recovering are different activities, and most organisations have no structured process for the second part.
This article explains how vendor debit notes work as a formal recovery mechanism — from identifying the issue during goods receipt to generating a GST-compliant document and posting the financial adjustment.
1. The Problem: Vendor Issues Handled Informally
When goods arrive with problems, the typical responses are:
- Phone calls and emails. The stores team calls the vendor, explains the problem, and asks for a replacement or credit. The conversation is not linked to the PO or GRN.
- Informal adjustments. The next invoice from the vendor is manually reduced by the disputed amount. No formal document exists for the adjustment.
- Absorbed losses. For small amounts, the effort of following up exceeds the recovery amount. The loss is quietly absorbed — but across hundreds of orders per year, small losses aggregate into significant amounts.
- No quality tracking. Without formal documentation, there is no way to measure vendor performance over time. A vendor who consistently short-ships by 5% appears identical to one who always delivers in full.
2. Four Types of Debit Notes
Different vendor issues require different financial treatments. The system distinguishes four types:
| VDN Type | When Used | Financial Basis |
|---|---|---|
| REJECTION | Goods received but rejected during quality inspection | Full value of rejected quantity at PO rate |
| UNDER_RECEIVED | Fewer goods received than invoiced or ordered | Value of shortfall at PO rate |
| DAMAGE | Goods received in damaged condition | Value of damaged quantity at PO rate |
| PRICE_EXCESS | Vendor invoiced at a rate higher than PO rate | Difference between invoiced rate and PO rate |
Each type references specific GRN lines — the debit note is not created in isolation but traced back to the receipt event where the issue was identified.
3. Creating a VDN from GRN Data
A vendor debit note is created by referencing an existing GRN. The system pulls the relevant data from the receipt:
- Vendor details — name, GSTIN, address — inherited from the PO
- Line items — the specific items with the issue, their PO rates, and received quantities
- GST treatment — intra-state or inter-state, determined by the supplier GSTIN frozen on the PO
The user specifies the VDN type, the affected quantities, and any remarks. The financial calculation — base amount, GST, total claim — is computed automatically from the PO line rates and the quantities in question.
The VDN references the PO-level supplier GSTIN, not the vendor's current GSTIN. This is a deliberate design choice: a vendor with addresses in Karnataka and Telangana may have supplied goods from their Karnataka address (intra-state for a Karnataka buyer). The GST treatment on the debit note must match the original transaction, not the vendor's default address.
4. GST-Compliant PDF Generation
The system generates two types of PDF documents depending on the available GST information:
- Tax Debit Note: Generated when both the buyer's GSTIN and the supplier's GSTIN are available. This document complies with GST invoicing rules — it includes both GSTINs, the HSN/SAC codes, the GST breakup (CGST + SGST for intra-state, IGST for inter-state), and the original invoice/PO reference.
- Plain Debit Note: Generated when GST information is incomplete (for example, an unregistered vendor). This document serves as a formal claim without the GST-specific formatting.
The PDF includes the vendor's legal name, PAN, and address — pulled from the vendor record at the time the PO was created, not from the current vendor master. This ensures the document matches the original transaction even if the vendor's details have since been updated.
5. Approval Workflow
A vendor debit note follows an approval chain before it becomes a formal claim. The workflow ensures that:
- The claim is reviewed by someone with authority to raise financial claims against vendors
- The quantities and amounts are verified against the GRN
- The VDN type is appropriate for the situation (a price discrepancy should not be raised as a rejection)
The approval chain uses the same routing engine as purchase orders and GRNs — the same approval matrix, the same level-based progression, the same audit trail. Each approval or rejection is recorded with the approver's identity, timestamp, and remarks.
6. Clearing PO Quality Flags
When a VDN is raised for rejection or damage, the corresponding PO line is flagged with a quality indicator. These flags serve two purposes:
- Vendor performance tracking: Over time, the flags build a quality profile for each vendor. A vendor with repeated rejection flags across multiple POs presents a pattern that would be invisible without formal documentation.
- Procurement decisions: When evaluating vendors for future orders, the quality flags provide objective data. "Vendor X had 3 rejections in 12 orders" is more useful than "someone mentioned they had problems with Vendor X."
The compliance report aggregates these flags alongside delivery timeliness and other metrics, giving procurement teams a factual basis for vendor evaluation.
7. Tally Posting
When the Tally integration is enabled, approved VDNs generate accounting entries automatically:
- Vendor account is debited — the claim amount reduces the vendor's payable balance
- Purchase return or adjustment account is credited — depending on the VDN type
- GST entries are reversed proportionally — the input tax credit claimed on the original purchase is adjusted for the returned/rejected quantity
These entries are posted as Tally vouchers through the integration layer. The voucher references the VDN number, PO number, and GRN number — creating a complete chain from the original order through receipt to the claim.
8. Frequently Asked Questions
When should a debit note be used instead of a credit note?
A debit note and a credit note represent the same adjustment from opposite perspectives. The buyer issues a debit note saying "we are debiting your account because you owe us." The vendor issues a credit note saying "we are crediting your account because we owe you." In practice, the buyer should issue the debit note first — it formally documents the claim with quantities, reasons, and PO references. The vendor may then issue a corresponding credit note as acknowledgement. Waiting for the vendor to issue a credit note without raising a debit note means the buyer has no formal record of the claim.
Does a vendor debit note block GRN posting?
A vendor debit note does not block GRN posting — the two processes are independent. The GRN records what was physically received. The VDN records claims against the vendor for issues identified during or after receipt. A GRN can be posted even if a VDN exists for the same PO. However, the VDN affects the PO's quality flags — when a VDN is raised for rejection or damage, the corresponding PO line is flagged. These flags appear in vendor performance reports and affect compliance scoring. The VDN creates a financial claim; the GRN records the physical receipt.
How is GST calculated on a vendor debit note?
GST on a VDN mirrors the GST treatment of the original purchase order. The VDN line references the PO line, so the GST rate (CGST+SGST for intra-state or IGST for inter-state) is inherited from the PO. The intra-state versus inter-state determination uses the supplier GSTIN frozen on the PO at the time of order, not the vendor's current GSTIN. This matters because a vendor with multiple GSTINs across states may have supplied from a specific state registration. The generated PDF includes the GST breakup formatted as a Tax Debit Note when both GSTINs are available.
Can a vendor debit note be reversed after approval?
Once a VDN is approved and posted, it represents a formal financial claim against the vendor. Reversing it requires raising a new transaction — the system does not offer an undo for posted VDNs. This is consistent with accounting principles: a debit note is a document with legal and tax implications, and cancelling it requires a counter-document rather than deletion. If the claim was raised in error, the organisation would process a corresponding adjustment through the standard workflow with its own approval chain, ensuring the reversal is documented.
What is the difference between price excess and price mismatch in debit notes?
Price excess applies when the vendor invoices at a rate higher than the purchase order rate. The debit note claims the difference between the invoiced amount and the PO amount — a straightforward overcharge. Price mismatch is identified during three-way invoice matching, where the PO rate, GRN received quantity, and vendor invoice amount are compared. A mismatch may reveal rate differences, quantity discrepancies, or calculation errors. The VDN type PRICE_EXCESS addresses the rate overcharge scenario specifically, while other discrepancies discovered during invoice matching may lead to different VDN types or resolution paths.