Section 52 TCS for E-commerce Sellers: Handbook

Section 52 of the CGST Act requires every e-commerce operator — Amazon, Flipkart, Meesho, Myntra, JioMart, Nykaa, and others — to collect Tax Collected at Source at 1% (0.5% CGST + 0.5% SGST for intra-state, or 1% IGST for inter-state) on the net taxable supplies made through its platform. Sellers reclaim the TCS as credit in their electronic cash ledger by reconciling GSTR-8 against GSTR-2X each month. This handbook walks through every step — registration, money flow, GSTR-2X claim, and the Section 194-O confusion that catches many sellers.

This guide is part of our Business Courier Solutions in India: The Complete Guide pillar, written for online sellers shipping at scale.

What Section 52 TCS means and who it applies to

Section 52 of the CGST Act, 2017 obligates every e-commerce operator collecting consideration on behalf of suppliers to deduct TCS at the prescribed rate from the net value of taxable supplies made through its platform. The TCS sits separately from regular output GST — it is a cash-flow mechanism that helps the department cross-validate marketplace sales against seller filings.

Who counts as an e-commerce operator for Section 52 purposes:

• Marketplaces: Amazon, Flipkart, Meesho, Myntra, JioMart, Nykaa, Snapdeal, Ajio
• Vertical platforms: BookMyShow (ticketing), Urban Company (services)
• Restaurant aggregators for restaurant supplies: Swiggy, Zomato
• Open-network apps under ONDC (the entity meeting the operator definition)

Who is the supplier: any GST-registered seller listing goods or services on these platforms.

Crucial distinction from Section 194-O of the Income Tax Act: Section 52 is a GST collection at 1% on the net taxable supply value, deposited via GSTR-8. Section 194-O is an income tax deduction at 1% on the gross sale value, deposited via TDS challans and reflected in Form 26AS. Both can apply to the same sale, deducted by the same marketplace, but they are governed by different laws and reconciled in different ledgers. Mixing them up is the most common compliance error among new sellers — and a frequent driver of help-desk tickets. For the broader GST picture, see our GST Compliance Shipping Guide.

TCS for online sellers: how it actually works (cash flow view)

The cleanest way to understand Section 52 is to walk through a single transaction.

Worked example: ABC Crafts sells a Rs 1,000 product on Flipkart

ABC Crafts also has its own output GST liability on the Rs 1,000 sale (say 18% = Rs 152.54 on the taxable value of Rs 847.46), which it pays separately via GSTR-3B. The Rs 10 TCS deducted by Flipkart sits in ABC Crafts’ electronic cash ledger after GSTR-2X reconciliation, and can be used to offset GSTR-3B liability.

Cash flow impact: the seller loses 27-30 days of working capital on the TCS amount (deducted at sale, claimable the following month). For high-volume D2C and SMB sellers shipping 500+ orders a month, the locked working capital adds up — automated monthly reconciliation is the only way to recover it without leakage. See our Marketplace Listing Logistics & Payments India for the full payment-cycle picture.

TCS rate for ecommerce sellers and threshold

The current Section 52 rate is 1% on the net value of taxable supplies. The split:

• Intra-state supply: 0.5% CGST + 0.5% SGST = 1%
• Inter-state supply: 1% IGST = 1%

“Net value of taxable supplies” is defined as the aggregate value of supplies of goods or services made by all suppliers through the operator during a month, minus the value of supplies returned. Returns reduce the TCS base — which is why the GSTR-8 reflects a netted figure.

No turnover threshold for sellers. TCS applies from the very first sale once a supplier is registered and active on a TCS-collecting operator. The general Rs 40 lakh / Rs 20 lakh GST registration threshold (Section 22) does not apply — Section 24 mandates registration for marketplace suppliers regardless of turnover.

Composition scheme exclusion. Composition taxpayers (paying a flat slab rate without input credit) cannot supply through TCS-collecting e-commerce operators. This is a hard legal block under Section 10 of the CGST Act. A composition seller wanting to list on Amazon or Flipkart must first opt out of the composition scheme and shift to the regular scheme.

Registration requirements

Two distinct registrations come into play under Section 52:

Seller side:

• Mandatory GST registration regardless of turnover (Section 24)
• Composition scheme is not permitted
• GSTIN is verified at marketplace onboarding — sellers cannot list without it

Operator side:

• Separate TCS registration via Form GST REG-07 for each state of operation
• Distinct from the marketplace’s regular GSTIN
• The TCS GSTIN is what appears on GSTR-8 filings

For sellers operating from MSME hubs like Jaipur-based marketplace sellers shipping handicrafts and bandhani textiles on Amazon Karigar and Meesho, the registration step is non-negotiable from day one. There is no “test the waters first” path on a TCS-collecting platform.

GSTR-8: what the marketplace files and what the seller sees

GSTR-8 is the monthly return filed by every e-commerce operator collecting TCS. The filing window is the 10th of the following month.

What goes into GSTR-8:

• Supplier-wise GSTIN
• Gross value of supplies made through the platform
• Value of supplies returned
• Net taxable supplies (gross minus returns)
• TCS collected (1% of net taxable supplies)
• TCS split into CGST/SGST or IGST

What the seller sees:

Once the operator files GSTR-8, the supplier-wise TCS data auto-populates into the supplier’s GSTR-2X on the GST portal. GSTR-2X is the read-only view of all TCS and TDS credits available to the supplier for that period.

To view GSTR-2X:

1. Log in to gst.gov.in
2. Returns Dashboard > Select period
3. Click “TDS and TCS Credit Received” tile
4. Filter by “TCS Credit Received” — view operator-wise (Amazon, Flipkart, Meesho, etc.) entries

This is also where reconciliation begins.

How to claim TCS credit step-by-step

The TCS credit claim is a 5-step monthly workflow. Done cleanly, it takes 30-45 minutes per month for a multi-marketplace seller. Done poorly, unclaimed credit accumulates and is increasingly hard to chase as time passes.

1. Log in to gst.gov.in with your seller GSTIN credentials.
2. Navigate to Returns Dashboard > Select the relevant period > Click “TDS and TCS Credit Received”.
3. Open the GSTR-2X view. It will show operator-wise (Amazon, Flipkart, Meesho, etc.) entries with the TCS amounts they have deposited against your GSTIN.
4. Reconcile against marketplace settlement reports. Download the monthly settlement report from each seller dashboard, match the TCS deducted line items against the GSTR-2X entries. Accept entries that match; reject mismatches.
5. File the action. Once accepted, the TCS amounts credit to your electronic cash ledger. Use the credited amount to discharge GST liability when filing GSTR-3B for the same or future period.

Handling discrepancies:

• Match the gross sales reported in marketplace settlement reports against your GSTR-1 outward supplies. They should agree.
• If the marketplace reports a higher figure than your GSTR-1, you have under-reported — fix the GSTR-1 in the same period or via amendment.
• If the marketplace reports a lower figure, raise a dispute with the marketplace’s seller support and reject the entry in GSTR-2X.
• Rejected entries flow back to the marketplace for revision in the next GSTR-8 amendment cycle.

For sellers integrated via API, this reconciliation is often automated by the marketplace integration platform. See our Marketplace Integration Guide for integration-level reconciliation patterns and our E-commerce Fulfillment Strategies for the broader operational stack.

Common mistakes that cost sellers money

Five recurring issues account for the vast majority of TCS-related losses among small and mid-tier sellers.

• Not reconciling GSTR-2X monthly. Unclaimed credit piles up; after 12-18 months, chasing the marketplace for old data is much harder. Make it a fixed monthly close-of-books step.
• Ignoring rejections in GSTR-2X. Entries auto-default to acceptance after the prescribed window if not actively rejected. That means a mismatched entry gets locked in as accepted, and the credit becomes harder to dispute.
• Filing GSTR-1 with mismatched values vs marketplace-reported sales. GSTN cross-validates GSTR-1, GSTR-3B, and GSTR-2X. Mismatches trigger department queries.
• Composition dealers listing on TCS-collecting platforms. This is legally prohibited. The marketplace may de-list and the department can issue notices for the period of non-compliance.
• Mixing up Section 52 TCS (GST) with Section 194-O TDS (income tax). They appear in different ledgers (electronic cash ledger vs Form 26AS) and need separate reconciliation. Treating them as one number causes both reconciliations to fail.

Penalties for non-compliance (operator and seller side)

Operator side:

• Short collection or non-remittance attracts penalty under Section 122 of the CGST Act
• Interest under Section 50 on delayed remittance
• Filing GSTR-8 late attracts a late fee per day until filed

Seller side:

• Direct penalty under Section 52 is rare — the law primarily targets the operator
• Indirect loss via unclaimed credit (working capital permanently leaked)
• Audit risk on under-reported turnover — GSTR-8 is third-party evidence of seller sales, and any GSTR-1 mismatch invites scrutiny
• For composition dealers caught listing on TCS platforms, retrospective scheme withdrawal and recovery of differential tax

System-side cross-validation between GSTR-1, GSTR-3B, GSTR-2X, and GSTR-8 is automated. Mismatches surface as ASMT-10 notices, which then require a written response within the prescribed timeline.

Recent changes and what to track

The Section 52 ecosystem evolves as marketplace models evolve.

• E-invoicing threshold linkage: sellers above the e-invoicing turnover threshold must generate IRNs, which then cross-validate against marketplace-reported sales for tighter audit trails.
• ONDC and open-network e-commerce: the rule under latest notifications is that the entity meeting the operator definition (typically the seller-side app facilitating the supply) is responsible for Section 52 TCS. The seller’s claim mechanics remain the same — TCS lands in GSTR-2X regardless of which operator deposited it.
• Marketplace reconciliation API improvements: GSTN periodically expands the data downloadable from GSTR-2X to make matching against settlement reports easier.

Reference the latest circulars on the official CBIC portal at cbic.gov.in before relying on older operational practice.

Frequently Asked Questions

What is the current TCS rate under Section 52 for e-commerce sellers?

The TCS rate is 1% on the net value of taxable supplies — 0.5% CGST plus 0.5% SGST for intra-state supplies, or 1% IGST for inter-state supplies. The e-commerce operator (Amazon, Flipkart, Meesho, etc.) deducts this before paying the seller and remits it to the government via GSTR-8 filings monthly.

Do I need GST registration to sell on Amazon, Flipkart, or Meesho?

Yes. Section 24 of the CGST Act mandates GST registration for any supplier making taxable supplies through an e-commerce operator that collects TCS under Section 52, regardless of turnover. The general Rs 40 lakh / Rs 20 lakh threshold does not apply to such sellers. Meesho’s no-GST sellers programme operates only for specific exempted categories.

How do I claim TCS deducted by the marketplace as credit?

Log in to gst.gov.in, go to Returns Dashboard, open TDS and TCS Credit Received, view the GSTR-2X for the period, verify operator-wise entries against your marketplace settlement reports, accept the entries, and the amount credits to your electronic cash ledger. Use it to discharge GST liability in GSTR-3B.

What is the difference between Section 52 TCS and Section 194-O TDS?

Section 52 TCS is collected under GST law at 1% on net taxable supplies and remitted via GSTR-8. Section 194-O TDS is deducted under income tax law at 1% on gross sales (sellers’ PAN-based, with thresholds and exemptions). They are separate deductions, often both applied to the same sale by the same marketplace.

Can composition scheme sellers list on Amazon or Flipkart?

No. The CGST Act prohibits composition taxpayers from supplying goods or services through e-commerce operators required to collect TCS under Section 52. A composition seller must opt out of the scheme and switch to the regular scheme before listing on such platforms, and update their GSTIN status accordingly.

What happens if marketplace GSTR-8 data does not match my records?

Reject the mismatched entry in GSTR-2X before the prescribed window closes and raise a dispute with the marketplace through their seller support. Maintain your own dispatch and settlement reconciliation. Unresolved mismatches can trigger department queries because GSTN cross-validates GSTR-1, GSTR-3B, and GSTR-2X.

Is TCS deducted on returned orders?

No. TCS under Section 52 applies only to the net value of taxable supplies, which is gross supplies minus returns. The marketplace adjusts the net figure in its GSTR-8 filing. If a return happens after the TCS was already deducted in a prior month, the adjustment flows through the next month’s GSTR-8 filing.

Does Section 52 apply to ONDC and open-network e-commerce?

Applicability on ONDC depends on which entity meets the definition of electronic commerce operator — the buyer-side app, seller-side app, or the protocol. As per latest notifications, the entity facilitating the supply (typically the seller-side app) is treated as the operator for TCS purposes. Verify with current CBIC guidance.

Reconcile every rupee, ship from one place

Section 52 TCS is fully recoverable if the monthly reconciliation runs cleanly. The mistakes that cost sellers money — mixing TCS with TDS, ignoring GSTR-2X, listing under composition scheme — are operational, not financial. Set the monthly close-of-books rhythm, integrate marketplace settlement reports, and the working capital comes back. Selling on multiple marketplaces? Centralize your shipping with a CourierBook seller account and reconcile GSTR-2X against real dispatch data from every platform — see our D2C Shipping Best Practices Guide for the broader playbook.