GST credit notes for returns: the workflow sellers miss

The refund is only half the transaction

A customer returns a Rs 2,400 order. Your team approves the refund, the payment gateway reverses it, the ticket closes. In the books, the sale is still there and so is the GST you charged on it. Unless a credit note is raised, declared and matched, you have refunded the customer out of your own margin and paid tax on revenue you no longer have.

At a 12 to 20 percent return rate, which is ordinary for apparel and accessories, this is not a housekeeping issue. On Rs 5 crore of annual sales with an 18 percent rate and 15 percent returns, the tax sitting on reversed sales is well over Rs 11 lakh. Sellers rarely lose all of it, but they lose a slice every month through returns that never became credit notes.

What a credit note is, and what it is not

Under section 34 of the CGST Act, a credit note is the instrument a supplier issues when the taxable value or tax charged in a tax invoice exceeds what is actually payable. Goods returned by the buyer and deficient supplies are both covered. It is not a refund voucher, not a debit memo from the marketplace, and not the settlement adjustment line in your payout report. Those three things are evidence that a return happened. The credit note is the document that changes your tax position.

Two conditions matter in practice. The reduction in liability is not available where the tax has effectively been passed on to another person and not reversed, which is why the recipient side matters for B2B sales. Since the Invoice Management System went live, credit notes flow to the registered buyer for acceptance, and the supplier’s liability reduction is tied to the buyer reversing the corresponding input credit. For B2C ecommerce, which is most of what a D2C brand sells, there is no recipient action to wait for, so the discipline is entirely internal.

The 30 November wall

The single hardest rule to recover from is the time limit. Details of a credit note must be declared in a return no later than 30 November following the end of the financial year in which the original supply was made, or the date of filing the relevant annual return, whichever is earlier. Miss it and the tax adjustment is gone permanently.

This bites hardest on late-March sales. A festive or year-end order shipped on 28 March, returned in April, sitting in a warehouse bay through a busy quarter and written up in September, still belongs to the previous financial year. Build one control for this: a report every October listing all returns received against invoices from the prior financial year with no matching credit note. Clear it before the November filing, not during it.

Marketplace returns and the TCS interaction

Marketplaces collect tax at source under section 52 on the net value of taxable supplies, meaning gross supplies through the platform minus supplies returned. The current rate is 0.5 percent, split across CGST and SGST for intra-state supplies. That netting is the reason marketplace returns need a tighter loop than your own website returns.

Three figures have to tie every month: returns recorded in your order system, return debits in the platform settlement report, and credit notes in your GSTR-1. In practice they never match on the first pass. The usual causes are timing, where a return is credited by the platform in one month and received physically in the next, and partial returns on multi-unit orders where the platform nets the whole order value. Reconcile on the return ID, not on the amount, and keep an ageing list of unmatched items rather than forcing a plug entry.

The TCS credit itself appears in your electronic cash ledger after the operator files its statement. If your credit notes are late, the netting and the credit will drift apart, and you will spend the next quarter explaining a difference that started as a filing delay.

E-invoicing changes the sequence

If e-invoicing applies to you, and it now covers businesses above Rs 5 crore of aggregate annual turnover, credit notes are not exempt. A credit note must be reported to the invoice registration portal and carry an IRN, exactly like the original invoice. A credit note raised only inside your billing software, without an IRN, is not a valid document for that reduction.

Sequencing matters here. Some teams issue the customer refund first and generate the credit note days later, which is workable, but for larger businesses there is a reporting window on the portal for documents, and once it lapses the IRN cannot be generated for that document date. The safe pattern is to generate the credit note and its IRN on the day the return is accepted at the warehouse, and to treat the refund as the downstream event. Where goods move, the e-way bill and delivery challan for the return leg should reference the same return ID so the physical and tax trails agree.

A monthly close that actually holds

The close is four steps, and it works better as a standing checklist with named owners than as a project.

• Returns received in the warehouse, matched to original invoice numbers, with any unmatched units listed rather than ignored.
• Credit notes generated for every matched return, with IRNs where applicable, before the GSTR-1 cut-off for the period.
• Reconciliation of platform settlement debits and your own credit notes, tracked on an ageing report with a 45-day escalation.
• A prior-year exception list, reviewed monthly from July onward and cleared before the November limit.

None of this is sophisticated. It is the same reconciliation habit that makes settlement and inventory reporting reliable, applied to the one area where a missed month becomes permanent. Sellers who run it properly recover a point or more of net margin, and they recover it without selling anything extra.