Returns for E-Commerce Seller

Returns for E-Commerce Seller

If you sell goods or services through Amazon, Flipkart, Zomato, or any other marketplace in India, your GST compliance has two moving parts: the operator's obligations and your own. In FY 2026-27, the e-commerce operator collects Tax Collected at Source (TCS) at 1% on every settlement and reports it in a monthly GSTR-8. You, the seller, report the same sales in GSTR-1 and GSTR-3B, claim the TCS credit from your electronic cash ledger, and reconcile the two records every single month. Miss any step, and you either overpay tax in cash or invite an automated scrutiny notice under Section 61 of the CGST Act.

Who Qualifies as an E-Commerce Operator and Who Is a Seller?

Under Section 2(45) of the CGST Act 2017, an e-commerce operator (ECO) is any person who owns, operates, or manages a digital or electronic facility or platform for the supply of goods or services — and either collects consideration on behalf of the supplier or facilitates the collection. Amazon India, Flipkart, Myntra, Meesho, Nykaa, Zomato, Swiggy, Urban Company, Ola, and BookMyShow are all ECOs. The seller or supplier is the registered (or registerable) person who lists products or services on that platform.

The ECO is not an agent under Section 52 — that distinction matters because an agent's principal pays tax, whereas an ECO collects TCS from the consideration it remits to the seller, and the seller remains the taxable person for the underlying supply.

Registration: Under Section 24(ix), any supplier of goods through an ECO must register for GST regardless of turnover. The Rs. 40 lakh threshold (or Rs. 20 lakh for special category states) that applies to other businesses simply does not apply here. A first-time seller of handloom sarees grossing Rs. 2.5 lakh a year on Flipkart still needs a GSTIN before the first sale. ECOs themselves must also register mandatorily under Section 24(x). Service providers selling through ECOs have the same mandatory registration obligation, with a narrow exception for persons supplying only those services notified under Section 9(5) — covered separately below.

Returns Filed by the E-Commerce Operator

GSTR-8: The Monthly TCS Return

GSTR-8 is filed exclusively by ECOs. It discloses:

• Net value of taxable supplies made through the platform by third-party sellers (gross supplies minus returns and cancellations)
• TCS collected, broken down by GSTIN of each seller and by CGST/SGST/IGST head
• Amendments to previously filed GSTR-8 data (Table 4 of the form)

Due date: 10th of the month following the tax period. For October 2026 supplies, GSTR-8 must be filed by 10 November 2026, without exception. There is no quarterly option for GSTR-8.

The operator does not report its own commission, advertising fees, or logistics revenue in GSTR-8. Those go into its own GSTR-1.

GSTR-1 and GSTR-3B for the Operator's Own Supplies

An ECO earns platform fees, commission, sponsored listing revenue, and sometimes fulfilment or logistics charges. These are taxable services supplied by the ECO, not through it, and are reported in:

• GSTR-1 — outward supply statement, filed by the 11th (monthly filers) or 13th (QRMP) of the following month
• GSTR-3B — monthly summary return with output tax, ITC claim, and net tax payable, due by the 20th of the following month for monthly filers

Annual Returns

ECOs with aggregate turnover above Rs. 2 crore must file GSTR-9 (annual return) by 31 December following the financial year end. Those above Rs. 5 crore also file GSTR-9C (self-certified reconciliation). For FY 2026-27, these are due by 31 December 2027.

Returns Filed by the Marketplace Seller

GSTR-1

Every outward supply — B2B invoices (with buyer GSTIN), B2C large invoices above Rs. 2.5 lakh for inter-state supplies, and B2C summary — must be reported in GSTR-1. Sales through Amazon or Zomato are reported here exactly like direct sales; the marketplace route does not create any separate reporting table.

Monthly vs QRMP: If your aggregate turnover in FY 2025-26 was up to Rs. 5 crore, you may opt for the QRMP scheme — quarterly GSTR-1, with monthly tax payments via IFF (Invoice Furnishing Facility) for the first two months. If your platform settles weekly, buffer your invoices accurately before the quarterly GSTR-1 filing; mismatches with the operator's monthly GSTR-8 are harder to explain retrospectively.

GSTR-3B

The monthly summary return captures output tax liability, ITC claimed, TCS credit available, and net cash to be paid. TCS received from the operator flows into your electronic cash ledger (not your ITC ledger), reducing cash outflow rather than adjusting input credit. A seller with both a strong ITC position and significant TCS credits is effectively pre-financing two pools of credit.

GSTR-9 and GSTR-9C

Sellers with annual aggregate turnover above Rs. 2 crore must file GSTR-9. Above Rs. 5 crore, GSTR-9C is also mandatory. Reconstructing twelve months of multi-channel sales data in December is painful if monthly TCS reconciliation has been skipped — treat the annual return as the audit of your monthly discipline.

How TCS Works Under Section 52: A Worked Example

Section 52 mandates that every ECO (not acting as agent) collect TCS at a rate not exceeding 1% on the net value of taxable supplies — taxable value net of returns and cancellations, excluding the GST component itself.

Current notified rate: 0.5% CGST + 0.5% SGST for intra-state supplies; 1% IGST for inter-state supplies.

Worked Example — Raghav Textiles on Flipkart (October 2026)

Raghav Textiles is a Gujarat-registered seller. All supplies in October 2026 are intra-state (Gujarat buyer, Gujarat seller).

Flipkart files GSTR-8 by 10 November 2026. Raghav's GSTIN is included with net value Rs. 9,60,000 and TCS of Rs. 9,600. The GST portal auto-credits Raghav's electronic cash ledger: Rs. 4,800 under CGST and Rs. 4,800 under SGST. When Raghav files GSTR-3B for October (due 20 November 2026), he uses this Rs. 9,600 to offset his output tax liability. If his CGST + SGST liability is Rs. 90,000, he pays Rs. 80,400 in cash — the TCS credit covers the rest.

Claiming Your TCS Credit: Step-by-Step on the GST Portal

1. Log in at www.gst.gov.in with your credentials.
2. Go to Services → Returns → TDS and TCS Credit Received.
3. Select the tax period (e.g., October 2026) and click Prepare Online.
4. The portal displays TCS details auto-populated from each operator's GSTR-8. Verify each row against your marketplace settlement report.
5. If the figures match, click Accept. The credit moves to your electronic cash ledger.
6. If figures are incorrect, click Reject and contact the operator to file an amendment in Table 4 of GSTR-8.
7. Accepted TCS credit appears automatically in the tax payable calculation in GSTR-3B.

Do not skip this step. Unaccepted TCS sits in a pending state — invisible to GSTR-3B — and you will overpay tax in cash.

The Three-Way Monthly Reconciliation You Cannot Skip

CBIC's analytics engine cross-checks GSTR-8 (what the operator says you sold) against GSTR-1 (what you say you sold) and GSTR-3B (what you declared as your liability). Any gap triggers automated scrutiny under Section 61. Run this three-way match before filing GSTR-3B every month:

Common mismatch reasons and fixes:

• Date mismatch: Your GSTR-1 uses invoice/dispatch date; the platform's settlement report uses payment date. Flipkart's October settlement may include invoices dated September. Always map to invoice date in GSTR-1, and trace settlement-period differences in a monthly carry-forward register.
• Returns timing: Returns processed by the platform in November that relate to October invoices reduce the operator's October GSTR-8 net value. You may have already declared those sales in your October GSTR-1. Issue a credit note and report it in the November GSTR-1 to align.
• Interstate vs intrastate misclassification: If the operator books a supply as intra-state but you invoiced it as inter-state, the TCS appears in the wrong head (CGST/SGST vs IGST). These credits cannot be used interchangeably. Fix the classification at invoice level before filing.

Section 9(5): When the Platform Pays GST, Not the Seller

Section 9(5) of the CGST Act empowers the GST Council to designate certain services where the ECO — rather than the actual supplier — is liable to pay GST. The current notified categories most relevant to practice are:

Restaurant services through food aggregators (Zomato, Swiggy): The ECO pays GST at 5% (no ITC) on the net value of restaurant food orders. The restaurant does not pay GST on those aggregator-mediated orders. However, the restaurant must still:

• Maintain GST registration
• File GSTR-1 and GSTR-3B for walk-in sales, catering, and any other non-aggregator revenue
• Issue tax invoices for its own supplies

A restaurant that does only Zomato/Swiggy deliveries has near-zero GSTR-3B cash liability for those orders. But "my aggregator pays my GST" does not mean "I have no GST filing obligation at all" — a dangerous misconception that results in missed GSTR-1 filing and late fees.

Passenger transport (radio-taxi, motorcab, motorcycle) through apps: ECOs like Ola and Uber pay GST on ride-hailing services. Individual driver-partners are not liable for GST on those platform-mediated trips.

Housekeeping services (plumbers, carpenters, electricians) through ECOs: Where such services are supplied by individuals (not body corporates) through an ECO, the ECO is liable to pay GST. Urban Company is the standard example.

What changes and what stays the same: For suppliers covered by Section 9(5), the payment obligation shifts to the ECO, but the registration obligation does not disappear. The supplier still files returns; the tax line for Section 9(5) covered supplies will simply show zero liability.

Common Pitfalls and How to Fix Them

Treating TCS as final tax. TCS is an advance, not a discharge of liability. You must still declare the full taxable value in GSTR-1 and GSTR-3B. The TCS just reduces the cash you need to pay.

Opting for the composition scheme while selling on a marketplace. Under Section 10(2)(d), any person who supplies goods through an ECO required to collect TCS is ineligible for composition. If you have listed products on Amazon or Flipkart while under composition, you are non-compliant. Immediately apply to cancel composition registration, shift to the regular regime, and file GSTR-3B from the date your marketplace sales started. The penalty for collecting composition-rate tax while ineligible is the difference in tax rate on the entire turnover, plus interest.

Filing GSTR-1 on settlement date, not invoice date. This creates a systematic one-to-two-week lag between your GSTR-1 and the operator's GSTR-8, generating mismatches that appear as under-reporting in automated analytics.

Missing TCS from one operator when selling on multiple platforms. Each operator — Amazon, Flipkart, Meesho — files a separate GSTR-8 for your GSTIN. Accept TCS from every operator individually in the TDS/TCS Credit Received tile. Missing even one operator's credit leaves cash in the system that you have already economically borne.

Not following up on operator GSTR-8 errors. If an operator incorrectly maps a supply to another GSTIN (a not-uncommon error in large platforms), your TCS credit disappears. You must raise a discrepancy with the operator and get Table 4 of GSTR-8 amended. There is no mechanism for you, the seller, to directly correct the operator's return.

Penalties and Late Fees: What Non-Compliance Actually Costs

Late Filing of GSTR-8 by the Operator

Late fee: Rs. 200 per day (Rs. 100 CGST + Rs. 100 SGST), capped as per CBIC notification for the relevant turnover slab. On a 20-day delay:

> Rs. 200 × 20 days = Rs. 4,000 in late fees — plus interest at 18% per annum on the TCS amount withheld.

For a large operator handling thousands of sellers, even a 5-day delay in GSTR-8 filing creates working-capital strain across the entire seller ecosystem. A seller doing Rs. 50 lakh a month has Rs. 50,000 of TCS locked up per month — a 30-day delay means Rs. 50,000 unavailable for a full cycle.

Non-Collection of TCS by the Operator

Section 122(1)(ix): Failure to collect TCS as required under Section 52 attracts a penalty equal to the amount not collected. An operator that processes Rs. 1 crore of third-party supplies without collecting TCS owes Rs. 1,00,000 in penalty (the TCS not collected) plus interest under Section 50 at 18% per annum on the TCS due from the date it was payable.

Suppression Under Section 52(14)

GSTN now receives data from ECOs' own financial systems as part of data-sharing arrangements with CBIC. Reporting a lower net taxable value in GSTR-8 to reduce TCS is detectable. Action under Section 52(14) — penalty up to the tax not paid — is increasingly being triggered through these analytics-based audits.

For Sellers: Under-Reporting Detected via Cross-Checking

If your GSTR-1 declares Rs. 8 lakh but the operator's GSTR-8 shows Rs. 9.5 lakh for your GSTIN, an automated mismatch notice under Section 61 is generated. You will be asked to explain or correct. Unexplained gaps lead to best-judgment assessment under Section 62 and demand under Section 73 or 74.

Multi-Platform and D2C Sellers: Managing Consolidated Compliance

If you sell on Amazon, Flipkart, Meesho, and also run a Shopify D2C store, your GST compliance has four layers:

• Amazon, Flipkart, Meesho: Each ECO files GSTR-8 separately. Accept TCS from all three operators every month. Reconcile each platform's settlement report independently.
• Your Shopify D2C store: You are not an ECO; you collect payment directly from buyers. No TCS applies. Report D2C sales in GSTR-1 under the standard regime.
• GSTR-9 consolidation: Your annual return requires a single consolidated view of all four channels. Build a monthly multi-channel workbook from April — trying to reconstruct twelve months in December is a compliance risk.
• FBA and fulfilment centre stock transfers: Shipping inventory to Amazon FBA warehouses in other states constitutes an inter-state branch transfer. If the destination state warehouse operates under a different GSTIN, raise a tax invoice and generate an e-way bill for consignments above Rs. 50,000. If it is the same GSTIN (branch), use a delivery challan, still with an e-way bill.
• Income-tax TCS vs GST TCS: Marketplaces deduct TCS under Section 194-O of the Income-tax Act 1961 at 1% on gross sales to e-commerce participants. This is a completely separate deduction from GST TCS under Section 52. The income-tax TCS appears in your Form 26AS / AIS and is credited against your income-tax liability — not your GST liability. Never confuse the two ledgers.

Key Takeaways

• ECOs file GSTR-8 by the 10th of every month — no turnover threshold, no quarterly option. One missed filing blocks TCS credit for every seller on the platform.
• Sellers have mandatory GST registration the moment they list goods on an ECO platform, regardless of turnover. The Rs. 40 lakh threshold does not apply.
• TCS at 1% (0.5% CGST + 0.5% SGST intra-state; 1% IGST inter-state) is calculated on net taxable value — gross supplies minus returns. It is an advance, not a discharge of your GST liability.
• Accept TCS credits before filing GSTR-3B via the TDS/TCS Credit Received tile. Unaccepted credits do not appear in your cash ledger and you will overpay in cash.
• Run a three-way reconciliation every month — marketplace settlement report versus GSTR-8 versus your GSTR-1 — before touching GSTR-3B. Use invoice date, not settlement date, as the common time reference.
• Section 9(5) shifts the tax payment obligation to the ECO for restaurant services (Zomato/Swiggy), ride-hailing (Ola/Uber), and housekeeping services (Urban Company). The underlying supplier is insulated from the tax payment but still must register and file returns.
• Composition scheme is categorically barred for goods sellers on ECO platforms. If you are listed on a marketplace and still on composition, correct this immediately — the penalties and back-tax demand apply from the date of your first marketplace sale.