Situation 1 — Regular Marketplace Seller (Amazon, Flipkart, Meesho, Myntra)

You sell goods or general services through a marketplace. You are the supplier of record — your GSTIN is on the invoice, you charge GST at applicable rates, and you collect and remit GST on your sales. The marketplace collects TCS at 1% of net taxable supplies on your behalf and deposits it with the government.

Returns, refunds, and credit notes are entirely your responsibility — the marketplace does not handle the GST adjustment for you. They adjust the TCS deduction, but the credit note and GSTR-1 amendment are yours to file.

Situation 2 — Section 9(5) Service Provider (Drivers on Ola/Uber, Restaurants on Swiggy/Zomato, Service providers on Urban Company)

Here’s where most people get confused. For notified services — passenger transport, restaurant services, accommodation, housekeeping — the platform (ECO) is the deemed supplier for GST purposes. The platform issues the invoice, charges GST, and pays it. You as the service provider do NOT charge GST on these supplies. And importantly, TCS under Section 52 does NOT apply because the platform is the supplier, not you.

For returns or cancellations in this category, the platform handles the GST adjustment — not you.

Situation 3 — Your Own Website / App (Direct-to-Consumer)

You sell through your own website, app, or social media — no marketplace involved. TCS does not apply. You are fully responsible for all GST compliance including returns, credit notes, and refunds to customers. Regular GST rules apply without any platform intermediary.

Under normal GST rules, registration is mandatory only when your annual turnover crosses ₹40 lakh (goods) or ₹20 lakh (services). Marketplace sellers don’t get this luxury.

If you sell goods through any e-commerce marketplace — Amazon, Flipkart, Meesho, Nykaa, or any other platform collecting TCS — you must register for GST from your very first sale, regardless of turnover. Even a seller grossing ₹2.5 lakh per year on Flipkart needs a GSTIN before listing a single product.

Why? Because TCS applies to marketplace transactions, and TCS can only flow through a registered GSTIN. The platform will not activate your seller account without GST registration for goods sales.

Service providers on marketplaces follow the normal ₹20 lakh threshold — unless the service falls under Section 9(5), in which case a different registration rule applies.

Tax Collected at Source under Section 52 confuses a lot of sellers because the name suggests it is an additional tax. It is not. Think of TCS as an advance payment mechanism — the platform collects 1% of your taxable sales and deposits it with the government on your behalf. You claim it back as a credit against your GST liability.

The rate: 1% of net taxable value — split as 0.5% CGST + 0.5% SGST (for intra-state supplies) or 1% IGST (for inter-state supplies). And here is the important word: net. Returns reduce the base on which TCS is computed.

Claiming TCS Credit

After the marketplace files its GSTR-8 for a given month, the TCS credit appears in your GSTR-2B automatically. You claim it in GSTR-3B Table 6.1. This credit directly reduces your GST cash outflow — if your output tax liability is ₹5,000 and you have ₹3,000 TCS credit, you pay only ₹2,000 in cash.

If TCS credit exceeds your liability in a month, it carries forward in your electronic cash ledger. If it persistently accumulates — which happens for sellers with high return rates — you can claim a refund through the GST portal.

When a customer returns goods, you need to issue a credit note under Section 34 of the CGST Act. The credit note reverses the original supply — reducing your output tax liability and requiring the buyer to reverse the ITC they may have claimed on the original purchase.

What a Valid Credit Note Must Contain

• The word “Credit Note” prominently displayed
• A unique serial number for the credit note
• Date of issue
• Name, address, and GSTIN of the supplier
• Name, address, and GSTIN of the recipient (if registered)
• Original tax invoice number and date against which the credit note is issued
• Taxable value and GST amount being reversed
• Reason for the credit note — “goods returned,” “post-supply discount,” “deficiency of service”

The Time Limit — Do Not Miss This

A credit note for supply made in FY 2025-26 must be issued by the earlier of:

• September 30, 2026 (last day of the month following the end of the financial year), OR
• The date of filing the Annual Return (GSTR-9) for FY 2025-26

Miss this window and you lose the right to issue the credit note for that supply. The GST already paid on the returned goods cannot be adjusted — it becomes a cost.

Where to Report Credit Notes in GSTR-1

For most e-commerce returns — which are typically to unregistered individual consumers — the credit note goes in Table 10. The net effect reduces your total output tax liability for the month.

Let me walk you through exactly what should happen when a customer returns a product ordered from your Flipkart store. I’ll use my Chandni Chowk client’s situation as the example.

Step 1 — The Return Request: Customer returns a ₹2,000 saree (GST 5% = ₹95.24 tax on ₹1,904.76 taxable value). The marketplace processes the return and refunds the customer directly.

Step 2 — Marketplace Settlement Adjustment: Flipkart reduces your settlement for that month by ₹2,000. The TCS base for the month is also reduced by the return amount — so your TCS credit in GSTR-2B will be lower than if the return had not happened.

Step 3 — Issue a Credit Note: You issue a credit note referencing the original invoice, showing ₹1,904.76 taxable value being reversed and ₹95.24 GST being credited back. This reduces your output tax liability.

Step 4 — Report in GSTR-1: The credit note goes in Table 10 (since the buyer is an unregistered individual). This flows to GSTR-3B and reduces the month’s output tax.

Step 5 — Update Books: In your accounting records, reverse the original sale entry and create the credit note entry. Your GST liability for the month should net down by ₹95.24.

For specific notified services, the GST liability shifts from the service provider to the marketplace platform. The currently notified categories include passenger transport services (Ola, Uber, Rapido), restaurant and food delivery services (Swiggy, Zomato), accommodation services (Oyo, Airbnb-type platforms), and housekeeping services (Urban Company).

If you are a restaurant listed on Swiggy, for example, Swiggy issues the tax invoice to the customer, charges GST (5% without ITC for restaurant services), and pays it to the government. You do not charge GST on these orders. You do not issue a GST invoice to the customer for Section 9(5) supplies. And TCS under Section 52 does not apply — because the platform is the supplier, not a facilitator.

For order cancellations or refunds in the Section 9(5) world — the platform handles the GST adjustment. Your responsibility as the service provider is limited to reconciling the platform’s settlement statements with your own books.

Here’s the thing about e-commerce GST — the actual sales and the platform’s reports often don’t match perfectly, especially in months with heavy returns. The reconciliation between your GSTR-1, GSTR-3B, and the platform’s GSTR-8 is where most automated notices originate.

The most common mismatches I see in practice:

Mismatch 1 — Gross vs Net Reporting: Some sellers mistakenly report only the net settlement amount (after platform commission, returns, and TDS deductions) as their turnover in GSTR-1. This is wrong. You must report gross sales as turnover — returns are adjusted through credit notes, not by reducing the headline turnover figure. The platform commission is a separate expense — not a deduction from sales.

Mismatch 2 — Timing Difference on Returns: A return initiated in March may be processed and settled by the platform in April. If you report it as a March credit note but the platform nets it out in April’s GSTR-8, the two records will conflict. Always align your credit note date with when the return is actually processed and confirmed — not when the customer initiates it.

Mismatch 3 — TCS Credit Not Matching GSTR-2B: If you claim TCS credit in GSTR-3B that does not appear in your GSTR-2B (because the platform filed GSTR-8 late or incorrectly), the system flags a mismatch. This generates an automated Section 61 scrutiny notice. Match your TCS claims to what is actually in GSTR-2B — do not claim on the basis of platform statements alone.

Mistake 1 — Reporting net settlement instead of gross sales:
Report gross sales in GSTR-1. Returns go as credit notes. Commission and TCS are not deducted from turnover — they are separate entries. A seller reporting only ₹60,000 net settlement when gross sales were ₹1,00,000 will have GSTR-1 that does not match the marketplace’s GSTR-8, triggering automated scrutiny.

Mistake 2 — Not issuing credit notes at all for marketplace returns:
Many sellers assume the marketplace handles everything. It does not handle your GST. Every returned item needs a credit note from you — reported in GSTR-1 — to reduce your output liability. Skipping this means you pay GST on goods you gave back.

Mistake 3 — Claiming TCS credit before it appears in GSTR-2B:
Some sellers estimate their TCS based on platform dashboards and claim it in GSTR-3B before the operator files GSTR-8. This creates a mismatch that the system catches. Only claim TCS credit that is visible in your GSTR-2B.
GST LUT vs Bond — Export Compliance Guide

Mistake 4 — Missing the Section 9(5) vs Section 52 distinction:
A restaurant selling on Swiggy does not issue GST invoices for those orders or file credit notes for cancellations — Swiggy handles it. The same restaurant selling packaged food on Amazon does issue invoices and must handle returns independently. Getting this distinction wrong creates double-counting or gaps in GST filing.