Not every e-commerce TCS dispute is straightforward. Some involve a food delivery platform that simultaneously operates as a marketplace (Section 52 TCS) and a deemed supplier (Section 9(5) direct liability). Others involve an ONDC network transaction where three separate ECOs touched the payment chain, and the demand notice landed on the wrong one.
These are the edge cases - the disputes where the standard playbook does not work, where CBIC circulars are ambiguous, and where the stakes justify a GSTAT appeal.
This guide walks through five real-world complex e-commerce TCS scenarios, explains the legal provisions that created the confusion, and shows how each was identified, challenged, and resolved. If your business faces a non-standard TCS dispute, this is your reference.
What Are Complex E-Commerce TCS Scenarios and Why Do They End Up at GSTAT?
Complex e-commerce TCS scenarios are GST disputes involving non-standard applications of Section 52 (TCS by e-commerce operators) or Section 9(5) (direct GST liability on notified services) of the CGST Act, 2017, where the factual matrix does not fit neatly into the standard compliance framework and where the First Appellate Authority's order fails to address the nuance.
These edge cases arise because India's e-commerce ecosystem has evolved far beyond the single-platform marketplace model that Section 52 was originally designed for. The ONDC network introduced multi-ECO transactions. Hybrid platforms (like Swiggy operating as both a food delivery aggregator under Section 9(5) and a marketplace for grocery under Section 52) created classification grey areas. The TCS rate reduction via Notification 15/2024 in July 2024 created transition-period computation disputes.
Businesses dealing with these non-standard disputes benefit from GSTAT e-commerce appeal services (know more) that understand both the technical GST provisions and the practical realities of e-commerce operations. The GSTAT, as the highest fact-finding authority, can examine transactional evidence that the First Appellate Authority may have overlooked.
Key Terms You Should Know
Multi-ECO Transaction: A single supply of goods or services where more than one e-commerce operator is involved - one on the buyer side and another on the seller side (e.g., ONDC network). CBIC Circular 194/06/2023-GST clarifies TCS responsibility in such cases.
Section 9(5) Services: Notified services (restaurant/food delivery, hotel accommodation, passenger transport, housekeeping) where the e-commerce operator pays GST directly as if it were the supplier, regardless of the actual supplier's registration status.
Section 52 TCS: Tax Collected at Source by e-commerce operators on the net value of taxable supplies made through the platform by other suppliers. Rate: 0.5% post Notification 15/2024 (10 July 2024).
Split-Period TCS: A dispute arising from the TCS rate change mid-financial year - from 1% to 0.5% effective 10 July 2024. Demands spanning the transition require bifurcated computation.
GSTR-8 vs GSTR-2A Mismatch: A discrepancy between TCS reported by the e-commerce operator in GSTR-8 and the TCS credit reflected in the seller's GSTR-2A/2B. This mismatch can trigger demand notices against both parties.
Hybrid Platform: An e-commerce operator that simultaneously functions under both Section 52 (marketplace model for goods/grocery) and Section 9(5) (deemed supplier for restaurant/food delivery services) - creating dual compliance obligations and classification risks.
Who Faces These Edge Cases Under GST E-Commerce Provisions?
Complex TCS scenarios do not affect every e-commerce business equally. The following entities face the highest risk of non-standard disputes:
- ONDC network participants (buyer-side and seller-side apps) facing TCS liability disputes under Circular 194/06/2023-GST
- Hybrid food delivery and grocery platforms (Swiggy Instamart, Zepto) operating under both Section 9(5) and Section 52 simultaneously
- Multi-state e-commerce operators with 10+ GSTINs where TCS collected in one state is mismatched against seller credits in another
- Sellers operating on multiple platforms (Amazon + Flipkart + Meesho) whose aggregate TCS credit in GSTR-2A does not reconcile with GSTR-3B claims
- Aggregator platforms transitioning from the old 1% TCS rate to the new 0.5% rate, with demands spanning the pre- and post-Notification 15/2024 period
For a detailed walkthrough of the filing process itself, read our guide on how to file a GSTAT appeal (know more).
Legal Framework: Provisions That Create E-Commerce TCS Disputes
| Provision | What It Governs | Edge Case It Creates |
|---|---|---|
| Section 52 | TCS by ECO on net taxable supplies | Multi-ECO TCS liability in ONDC; split-period rate transition |
| Section 9(5) | ECO pays GST on notified services as deemed supplier | Hybrid platform dual classification - restaurant vs grocery |
| Circular 194/06/2023-GST | TCS liability when multiple ECOs in single transaction | Demand on wrong ECO (buyer-side vs seller-side) |
| Notification 15/2024 | TCS rate reduction from 1% to 0.5% (10 July 2024) | Split-period computation errors; retrospective demands at old rate |
| Section 122(1B) | Penalty specific to ECOs liable for TCS under Section 52 | Penalty applied to ECOs operating under Section 9(5) instead of Section 52 |
| Section 112 | GSTAT appeal against first appellate/revisional orders | Pre-deposit computation on complex multi-GSTIN demands |
How to Identify and Build Your GSTAT Appeal for E-Commerce Edge Cases: Step-by-Step
1. Map the Transaction to the Correct Legal Provision. Before drafting grounds of appeal, determine whether the disputed transaction falls under Section 52 (TCS), Section 9(5) (deemed supplier), or both. For hybrid platforms, prepare a transaction-level classification matrix showing which supplies attract TCS and which attract direct GST liability.
2. Identify the Specific Edge Case Category. Classify your dispute: (a) Multi-ECO TCS - cite Circular 194/06/2023-GST; (b) Section 9(5) misclassification - cite Notification 17/2017-CT(Rate); (c) Split-period TCS rate - cite Notification 15/2024; (d) GSTR-8 vs GSTR-2A mismatch - cite Rule 67 and Section 52(5). Each category requires different documentary evidence.
3. Compute the Correct Pre-Deposit. For complex multi-GSTIN demands, the pre-deposit must be calculated separately for each GSTIN. Use GSTAT pre-deposit calculation (know more) services for disputes spanning multiple states and rate periods.
4. Draft Scenario-Specific Grounds of Appeal. Do not use generic grounds. Reference the specific Circular, Notification, or GST Council FAQ that supports your position. For multi-ECO disputes, include the ONDC transaction flow diagram as an annexure.
5. Collect Platform-Level Transactional Evidence. Standard GSTR-8 data is insufficient for edge cases. Obtain API-level transaction logs from the platform, showing the exact payment chain, TCS deduction point, and settlement to each party. Businesses using e-commerce GST return filing (know more) services will have structured data ready.
6. Prepare a Technical Brief for the GSTAT Bench. GSTAT Members may not be familiar with ONDC architecture or multi-ECO payment flows. Prepare a 2-3 page technical brief (separate from the Statement of Facts) explaining the e-commerce business model and why the standard TCS framework does not apply in your scenario. Refer to our Form APL-05 filing guide (know more) for structuring the upload documents.
7. File on the GSTAT Portal with Complete Annexures. Upload all evidence as indexed, paginated PDFs. Include the technical brief as a separate annexure. Authenticate with DSC and ensure the filing is within the 3-month limitation (or 30 June 2026 for backlog cases).
Documents and Records Needed for Complex E-Commerce TCS Appeals
In addition to the standard GSTAT appeal documents (Form APL-05, certified copies of orders, SCN, Vakalatnama, pre-deposit proof - see our GSTAT e-commerce documents checklist (know more) for the complete list), edge cases require:
- Transaction classification matrix: spreadsheet mapping each supply line to Section 52 or Section 9(5) with HSN codes, supplier registration status, and applicable rate
- ONDC network transaction flow diagram (for multi-ECO disputes): showing buyer-side ECO, seller-side ECO, payment flow, and TCS deduction point
- Platform API-level settlement data: raw transaction logs showing consideration collected, TCS deducted, commission retained, and net payout per transaction
- Split-period TCS computation: bifurcated calculation showing TCS at 1% (before 10 July 2024) and 0.5% (after 10 July 2024) for the same supplier and GSTIN
- GSTR-8 vs GSTR-2A reconciliation report: month-wise comparison with variance analysis at supplier-GSTIN level
- CBIC Circular 194/06/2023-GST printout: as supporting authority for multi-ECO TCS liability arguments
- Technical brief on business model: 2-3 page document explaining platform architecture, payment chain, and why the standard TCS framework does not apply
- Comparative GSTR-1 and GSTR-3B filings: showing how Section 9(5) and Section 52 supplies were segregated in returns
- Notification 15/2024 transition period analysis: computation showing the rate applicable on each transaction date
- Expert opinion / CA certificate: where the classification dispute requires professional interpretation of law
Five Real E-Commerce TCS Edge Cases and How They Were Resolved
Edge Case 1: ONDC Multi-ECO - Demand Served on Wrong Operator.
A buyer-side app on the ONDC network received a TCS demand for Rs 12 lakh. However, per Circular 194/06/2023-GST, the seller-side ECO was responsible for TCS collection because the seller-side ECO released the final payment to the supplier. The First Appellate Authority upheld the demand, stating both ECOs are jointly liable. At the GSTAT appeal, the transaction flow was demonstrated using API settlement data, showing the buyer-side app never released payment to the supplier. The demand was directed to the correct (seller-side) ECO.
Edge Case 2: Hybrid Food and Grocery Platform - Section 9(5) vs Section 52 Misclassification.
A food delivery platform also sold grocery items through its app. The department treated all supplies as Section 9(5) (restaurant services) and demanded direct GST instead of recognising the grocery supplies as Section 52 TCS supplies. The platform had Rs 3.8 crore at stake. At the GSTAT appeal, the classification matrix showing HSN-level segregation - restaurant services (HSN 9963) under Section 9(5) and grocery goods (relevant goods HSN) under Section 52 - was presented. The Tribunal accepted the bifurcation and reduced the demand to Rs 85 lakh relating only to correctly classified restaurant services.
Edge Case 3: Split-Period TCS Rate Demand - Notification 15/2024 Transition.
An e-commerce operator received a TCS demand computed entirely at 1% for the full FY 2024-25, ignoring the rate reduction to 0.5% effective 10 July 2024. The excess demand was Rs 48 lakh. The First Appellate Authority partially allowed the appeal but applied the rate change from August instead of July. At the GSTAT appeal, Notification 15/2024 was cited with its exact effective date (10 July 2024), and a day-wise TCS computation was filed. The Tribunal corrected the rate application from 10 July onward.
Edge Case 4: Multi-State GSTR-8 Mismatch - Seller's TCS Credit Denied.
A seller operating on Amazon with GSTINs in Maharashtra, Karnataka, and Tamil Nadu found that TCS collected by the operator against the Maharashtra GSTIN was incorrectly reflected against the Karnataka GSTIN in GSTR-2A. The seller's Maharashtra ITC claim was denied, and a demand of Rs 22 lakh was raised. The first appeal was rejected. At the GSTAT appeal, Amazon's supplier-GSTIN-wise settlement reports were presented alongside the GSTR-8 vs GSTR-2A mismatch report showing the state-level error. The Tribunal directed the department to accept the credit against the correct GSTIN.
Edge Case 5: Penalty Under Section 122(1B) Applied to Section 9(5) Operator.
A ride-hailing platform (operating under Section 9(5) for passenger transport) received a penalty notice under Section 122(1B), which applies only to ECOs required to collect TCS under Section 52. The penalty was Rs 15 lakh. The platform did not collect TCS at all - it paid GST directly under Section 9(5). The first appeal upheld the penalty. At the GSTAT appeal, the amendment history of Section 122(1B) (retrospectively restricted to Section 52 ECOs by Finance Act 2024) was cited. The Tribunal quashed the penalty entirely.
Note: These scenarios are illustrative composites based on common dispute patterns observed in practice. Specific case details and parties have been anonymised.
Common Mistakes to Avoid in Complex E-Commerce TCS Appeals
Mistake 1: Using generic grounds of appeal for edge cases. Standard TCS appeal grounds ("demand is excessive", "calculation error") do not work for complex scenarios. Each edge case requires specific citation of the relevant Circular, Notification, or GST Council recommendation. Without specific grounds, GSTAT appeal filing services (know more) note that the Registrar may treat the appeal as defective.
Mistake 2: Not preparing a technical brief on the business model. GSTAT Members deal with diverse GST issues. A food delivery platform's hybrid model or an ONDC multi-ECO payment chain is not self-evident. Failing to explain the business architecture means the Tribunal must rely solely on the department's characterisation - which is usually adverse.
Mistake 3: Computing pre-deposit on the consolidated demand instead of GSTIN-wise. For multi-state e-commerce operators, each GSTIN's demand is a separate appeal. The pre-deposit must be computed per GSTIN, not on the total. Overpayment blocks working capital unnecessarily. Read our guide on GSTAT pre-deposit rules (know more) for the correct computation method.
Mistake 4: Ignoring the retrospective effect of Section 122(1B) amendment. The Finance Act 2024 restricted Section 122(1B) to Section 52 ECOs only, retrospectively from 01 October 2023. Many penalty notices issued between October 2023 and July 2024 to Section 9(5) ECOs are invalid - but the penalty stands if you do not challenge it at GSTAT.
Mistake 5: Not including platform-level transactional evidence. GSTR-8 and GSTR-2A data show aggregated figures. For edge cases, the Tribunal needs transaction-level proof - specific order IDs, payment chain timestamps, TCS deduction points. Without this, the appeal rests on assertions rather than evidence.
Penalties at Stake in E-Commerce TCS Disputes
Under Section 52(6) read with Section 73/74 of the CGST Act, 2017, failure to collect TCS or short-collection results in a demand equal to the uncollected amount plus interest at 18% per annum. For high-volume platforms processing lakhs of transactions monthly, even a 0.25% calculation error can result in demands running into crores.
Under Section 122(1B) (as amended retrospectively by Finance Act 2024 to apply only to Section 52 ECOs), the penalty for contravention of TCS provisions can be substantial. However, post-amendment, this penalty cannot be imposed on ECOs operating exclusively under Section 9(5) - this is a critical ground of appeal for ride-hailing and food delivery platforms.
Under Section 52(5), late filing of GSTR-8 attracts a late fee of Rs 200 per day (Rs 100 CGST + Rs 100 SGST). For operators registered in 20+ states, a single delayed GSTR-8 filing can trigger parallel late fee demands across all GSTINs.
Under Section 73 (non-fraud) or Section 74 (fraud/suppression), the department can raise demands for TCS not collected, with penalties ranging from 10% (Section 73) to 100% (Section 74) of the tax amount. Edge cases where the classification itself is disputed often see demands under Section 74, even though the non-compliance may be due to genuine interpretive ambiguity.
How E-Commerce TCS Edge Cases Connect with Broader GST Provisions
The TCS mechanism under Section 52 does not operate in isolation. When an e-commerce operator collects TCS and reports it in GSTR-8, the corresponding credit flows into the seller's GSTR-2A and then into the Electronic Cash Ledger. If the operator files GSTR-8 incorrectly - wrong GSTIN, wrong period, wrong rate - the seller loses credit. The seller then faces a demand under Section 73/74 for short-payment of output tax (because the TCS credit that should have offset the liability was never available). This creates a cascading dispute: one error by the operator results in demands against both the operator and the seller, often in different states.
For hybrid platforms, the Section 9(5) and Section 52 obligations interact with GSTR-1, GSTR-3B, and GSTR-8 in distinct ways. Section 9(5) supplies are reported in GSTR-1 Table 15 and GSTR-3B Table 3.1.1(i). Section 52 TCS is reported separately in GSTR-8. Misallocation between these tables triggers automated mismatch notices. Businesses seeking assistance in navigating these overlapping obligations can explore GSTAT e-filing portal assistance (know more) services.
The GSTAT has exclusive jurisdiction over fact-finding in these disputes. Unlike the High Court (which only hears substantial questions of law), the Tribunal can examine transactional evidence, platform settlement data, and API logs to determine whether the classification, rate, or TCS liability was correctly applied. This makes the GSTAT the most effective forum for resolving e-commerce edge cases.
Standard TCS Dispute vs Complex Edge Case: Key Differences
| Parameter | Standard TCS Dispute | Complex Edge Case |
|---|---|---|
| Nature | Calculation error, late deposit, filing delay | Classification ambiguity, multi-ECO liability, rate transition |
| Legal Basis | Section 52 straightforward application | Section 52 + Section 9(5) + Circular 194 + Notification 15/2024 |
| Evidence Needed | GSTR-8, bank challan, ECL extract | API logs, ONDC flow diagram, transaction classification matrix |
| First Appeal Success | High - straightforward computation review | Low - requires fact-intensive examination |
| GSTAT Relevance | Optional - may resolve at first appeal | Essential - Tribunal's fact-finding power is critical |
| Preparation Time | 2-4 weeks | 6-12 weeks (platform data, technical brief) |
| Typical Demand | Rs 5-25 lakh | Rs 50 lakh to Rs 5+ crore |
Key Takeaways
Complex e-commerce TCS scenarios - including ONDC multi-ECO TCS disputes, Section 9(5) vs Section 52 misclassification, and split-period rate transition errors - require GSTAT-level appeals because the First Appellate Authority typically lacks the infrastructure to examine transactional-level evidence.
CBIC Circular 194/06/2023-GST is the primary authority for multi-ECO TCS liability disputes; it designates the seller-side ECO (not the buyer-side) as responsible for TCS when the supplier-side ECO is not the actual supplier.
Hybrid platforms operating under both Section 9(5) (food delivery) and Section 52 (marketplace goods) must maintain HSN-level classification matrices to defend against blanket reclassification demands.
The Section 122(1B) penalty was retrospectively restricted to Section 52 ECOs only by Finance Act 2024; penalty notices issued to Section 9(5)-only operators between October 2023 and July 2024 are challengeable at GSTAT.
Every complex e-commerce GSTAT appeal should include a technical brief explaining the business model, platform architecture, and payment chain - standard grounds of appeal are insufficient for edge cases.
Need Help with a Complex E-Commerce TCS Appeal?
Resolving e-commerce TCS edge cases at the GSTAT requires deep understanding of Section 52, Section 9(5), CBIC Circular 194/06/2023-GST, and the practical mechanics of ONDC, multi-state TCS, and hybrid platform operations. Standard appeal preparation is insufficient - these cases demand transactional-level evidence, technical briefs, and scenario-specific grounds.
Explore our GSTAT e-commerce appeal services (know more) for end-to-end support - from edge case identification through GSTAT hearing preparation and representation.
For queries, reach out at +91 945 945 6700 or WhatsApp us directly.
