Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Section 52 of the CGST Act requires e-commerce operators to collect 1% TCS (0.5% CGST plus 0.5% SGST intra-state or 1% IGST inter-state) and file GSTR-8 by the 10th of the following month. Sellers on Amazon, Flipkart, Meesho, Swiggy, and Zomato cannot claim TCS credit in GSTR-3B until the operator's GSTR-8 auto-populates the GSTR-2B — any over-claim triggers scrutiny.
Three-source reconciliation matches (1) TCS deducted in the operator settlement report, (2) TCS auto-populated in seller's GSTR-2B Part II from GSTR-8, and (3) TCS in Form 26AS Part F. Matching keys are operator GSTIN plus seller GSTIN plus tax period plus net taxable value. Unmatched TCS is parked as deferred credit until the operator files or corrects GSTR-8.
Per-operator settlement-report ingestion, GSTR-8 filing-status tracker (10th-of-month cut-off), and 14th-of-month GSTR-2B readiness check.
Claimable TCS schedule aligned to GSTR-2B for GSTR-3B offset, deferred TCS carry-forward register, seller-support ticket list for GSTR-8 corrections, and Form 26AS Part F cross-check for income tax.
Sellers on Amazon, Flipkart, and Meesho have a GST compliance obligation that domestic-only businesses do not: every rupee of TCS deducted by the operator in the settlement report must reconcile against the GSTR-2B entry auto-populated from the operator’s GSTR-8 filing. A mismatch between the settlement TCS and the GSTR-2B credit cannot be claimed without follow-up — the operator must file a correction. TCS ecommerce reconciliation in India is not optional for sellers who want to maintain a clean GST credit position across multiple platforms.
What TCS E-Commerce Reconciliation Is
Section 52 of the CGST Act requires every registered e-commerce operator — Amazon, Flipkart, Meesho, Swiggy, Zomato, and others — to collect TCS at 1% of the net value of taxable supplies facilitated through their platform. For intra-state sales, this is 0.5% CGST + 0.5% SGST. For inter-state sales, it is 1% IGST. The operator deducts this TCS from the seller’s settlement proceeds and remits it directly to the government.
The operator files GSTR-8 by the 10th of the following month, reporting the TCS collected from each seller (identified by GSTIN). This GSTR-8 filing auto-populates the seller’s GSTR-2B with the corresponding TCS credit. The seller then claims this credit in GSTR-3B to offset output GST liability.
TCS ecommerce reconciliation is the three-source matching process: settlement report (source 1) → GSTR-2B (source 2) → GSTR-3B claim (source 3). Discrepancies at any step produce either an overstated credit claim or an understated credit claim — both of which create compliance exposure.
How TCS E-Commerce Reconciliation Works
Step 1: Extract TCS from the Settlement Report
The settlement report from each e-commerce operator includes a TCS line item showing the amount deducted per settlement cycle. Sellers operating across multiple platforms — for example, both Amazon and Meesho — must extract TCS from each platform’s settlement separately, since GSTR-8 is filed by each operator independently.
The settlement TCS is the ground-truth figure: it is the amount actually withheld from the seller. This becomes the comparison benchmark for GSTR-2B and GSTR-3B.
Step 2: Verify GSTR-2B Auto-Population from Operator’s GSTR-8
After the operator files GSTR-8 by the 10th of the following month, the TCS credit auto-populates in the seller’s GSTR-2B. Sellers should check GSTR-2B after the 14th of the following month when auto-population is typically complete. The GSTR-2B entry shows the TCS credit by operator GSTIN, the period, and the amount.
The reconciliation compares the GSTR-2B credit to the settlement TCS. If the operator filed GSTR-8 with a lower value — because of an error in their records, a mismatch in the seller GSTIN, or a timing difference — the GSTR-2B credit will be less than the settlement deduction. The seller cannot claim the full settlement TCS in GSTR-3B until the operator files a correction.
Step 3: Claim the Confirmed TCS Credit in GSTR-3B
Only the TCS credit that appears in GSTR-2B can be safely claimed in GSTR-3B. The credit is applied to offset output GST liability for the filing period. Any shortfall — where settlement TCS exceeds GSTR-2B credit — is carried forward as an open item pending operator correction. The reconciliation must track this open amount per operator per period until it resolves.
TCS Reconciliation Workflow by Step
| Step | Data source | Field to match | Common mismatch | Resolution |
|---|---|---|---|---|
| Extract settlement TCS | Operator settlement report | TCS amount per settlement period | TCS line absent or aggregated differently by operator | Request detailed settlement from operator support |
| Verify GSTR-8 filing | GST portal GSTR-2B (auto-populated) | TCS credit by operator GSTIN and period | GSTR-8 not filed by 10th; incorrect seller GSTIN used by operator | Follow up with operator to file or correct GSTR-8 |
| Match GSTR-2B to settlement | GSTR-2B vs settlement report | Amount + period + operator GSTIN | Amount mismatch if operator filed different value | Request GSTR-8 amendment from operator |
| Claim in GSTR-3B | GSTR-3B filing | TCS credit in Table 9 | Seller claims more than GSTR-2B shows (scrutiny risk) | Claim only matched GSTR-2B amount; carry forward remainder |
| Verify Form 26AS Part F | Income tax portal | TCS amount per operator | Operator filed correct GSTR-8 but 26AS shows different value | Flag for income tax reconciliation separately |
India-Specific Compliance Context
Section 52 of the CGST Act creates a compliance dependency between the seller and the operator: the seller’s GST credit position is directly determined by what the operator files in GSTR-8. This is structurally different from ITC on purchases, where the supplier’s GSTR-1 filing determines the buyer’s GSTR-2B. In the TCS context, the operator is both the collector and the filer — and errors in their filing directly constrain the seller’s credit claim.
TCS under Section 52 also appears in Form 26AS Part F for income tax tracking. This creates a second reconciliation track: sellers must verify TCS in both GSTR-2B (for GST purposes) and Form 26AS (for income tax advance tax and TCS credit). The two systems are not automatically synchronised — a GSTR-8 amendment by the operator updates GSTR-2B but may not immediately update Form 26AS.
Multi-platform sellers — those operating simultaneously on Amazon, Flipkart, and Meesho — face this reconciliation for each operator independently. The TCS collected by Amazon appears in Amazon’s GSTR-8, and only Amazon’s entry auto-populates in the seller’s GSTR-2B. Meesho’s TCS is a separate GSTR-8 from Meesho. Finance teams managing seller accounts across three or more platforms must maintain a per-operator TCS register to track open items.
Structured payment gateway reconciliation that incorporates TCS tracking allows multi-platform sellers to monitor GSTR-8 filing status per operator. Reconciliation software India automates the three-way match — settlement report, GSTR-2B, GSTR-3B claim — and surfaces open TCS items before the GSTR-3B filing deadline.
RBI payment system regulations govern the settlement infrastructure through which e-commerce operators remit proceeds to sellers — the Reserve Bank of India framework within which operator settlements and TCS deductions are administered.
The five FAQs below address the TCS rate, GSTR-8 deadlines, mismatch resolution, and multi-platform scenarios that matter most to sellers managing this reconciliation.