Zoho Books' "E-Commerce Operator" field reports that you sold through a marketplace. It doesn't tell you whether your Section 52 TCS was collected right
Zoho Books' E-Commerce Operator field (Settings > Invoices > Field Customization) marks an invoice as routed through a marketplace, which GSTR-1 reports under its "Supplies through ECO" section — split since the January 2024 tax period into Table 14(a) for ordinary Section 52 TCS sales and Table 14(b) for Section 9(5) supplies, where the platform itself pays the tax instead. Zoho's own documentation describes the field's GSTR-3B link (Table 3.1.1) only for the 9(5) case; it doesn't say how an ordinary goods sale gets routed between 14(a) and 14(b), so check a real invoice rather than assume. Either way, the field reports that a sale happened through a marketplace — it does not track whether the platform actually collected the right TCS, or whether that amount has reached your electronic cash ledger.
Sell on Amazon, Flipkart or Meesho and two different things happen to the same invoice — the platform collects Tax Collected at Source under Section 52, and Zoho Books has a field literally called "E-Commerce Operator" that looks like it should track exactly that. It doesn't track the amount or the credit, and the gap between what the field reports and what sellers assume it does is where reconciliation quietly breaks.
Two "e-commerce" mechanisms, one misleading field name
GST treats a sale made through a platform two completely different ways, and which one applies decides who pays the tax. Under Section 52 of the CGST Act, the platform collects a small amount at source on the seller's behalf and remits it — this is Tax Collected at Source (TCS), and it is what applies to an ordinary goods seller on Amazon, Flipkart or Meesho. Under Section 9(5), for a short, specifically notified list of services — passenger transport by radio-taxi, motorcab, maxicab, motor cycle, omnibus or any other motor vehicle; accommodation in hotels, inns, guest houses and similar, and housekeeping services such as plumbing or carpentry, in each case unless the supplier is itself liable to register under Section 22(1); restaurant services (other than at specified premises); and, from 22 September 2025, local delivery services, again unless the supplier is liable to register (Notification 17/2017-Central Tax (Rate), as amended, most recently by Notification 17/2025-Central Tax (Rate)) — the platform itself becomes liable for the entire tax, standing in for the supplier. No TCS, no GSTR-8, nothing collected at source at all, because the platform is paying it directly.
Zoho Books' own help documentation for the E-Commerce Operator field on an invoice — enabled under Settings > Invoices (under Sales) > Field Customization, then marking the field Active — ties it to GST return reporting generally: entered details appear under the "Supplies through ECO" section of GSTR-1. Since the January 2024 tax period, that section of GSTR-1 is itself split in two (inserted by Notification 26/2022-Central Tax, per GSTN's advisory on new Tables 14 & 15): Table 14(a) is where an ordinary Section 52 seller reports an ECO-GSTIN-wise summary of TCS-collected sales — a reconciliation summary that doesn't change your tax liability, because those sales already sit in GSTR-1's ordinary outward-supply tables — and Table 14(b) is where Section 9(5) supplies get reported, which does auto-populate GSTR-3B Table 3.1.1(ii). Zoho's own KB page describes the field's GSTR-3B link only in 9(5)/3.1.1 terms; it does not document how an ordinary goods sale through a marketplace gets routed to 14(a) instead. Confirm on a real invoice that your marketplace goods sales land in 14(a), not quietly in 14(b)/3.1.1 — misrouting a normal sale into the 9(5) table would misreport a supply you're actually liable for, not just miss a summary line.
The rate: 0.5%, not 1% — and it changed over two years ago
Section 52(1) itself fixes no rate — it caps the CGST leg at "not exceeding one per cent" and lets the Council set the actual figure by notification. The 53rd GST Council (22 June 2024) recommended cutting the collected amount in half, and two separate notifications did it: Notification 15/2024-Central Tax (10 July 2024) cut the CGST leg from 0.5% to 0.25%, and Notification 01/2024-Integrated Tax (10 July 2024) cut the IGST leg from 1% to 0.5%. The SGST/UTGST leg rests on each State's own notification. [verify] GSTN applied the combined 0.5% total on the portal from 10 July 2024 (advisory, 2 August 2024), but we have not independently checked every State's own instrument or effective date — if your State's notification post-dated the Centre's, that leg is worth a direct check rather than an assumption. Per GSTN's 2 August 2024 advisory, the rate ran at 1% for supplies made 1–9 July 2024 and at the new combined 0.5% from 10 July 2024 onward: 0.25% CGST + 0.25% SGST on an intra-State platform sale, or 0.5% IGST inter-State — half of what several guides, including some dated well into 2026, still quote.
Don't expect every period to reconcile to exactly 0.5% in July 2024 specifically — GSTN's own GSTR-8 FAQ (Q20) sets a portal validation band starting with that transition month, not a different legal rate: "For tax periods prior to July'24, Total Amount of tax collected at source (IGST+CGST+SGST) must be exactly 1% of Net amount liable for TCS... From July 2024 tax period onwards, Total Amount of tax collected at source (IGST+CGST+SGST) must be between 0.5% to 1%." GSTN doesn't state why the band stays open past July 2024 — treat it as a portal tolerance, not evidence the rate is anything but 0.5% for later periods. A July 2024 GSTR-8 legitimately blends the 1% and 0.5% supplies per the 2 August 2024 advisory above; a later period reconciling meaningfully off 0.5% is worth investigating, not waved through as "within the band."
What "net value of taxable supplies" actually excludes
TCS is never due on your full settlement value — the Explanation to Section 52(1) nets it down, and three exclusions are the ones sellers most often miss:
- Returns reduce the base. CBIC's 2017 GST Sectoral Series e-commerce FAQ (Q8) is explicit: "the value of supplies which are returned are adjusted in the aggregate value of taxable supplies" — a heavy-return category (apparel, footwear) should show TCS collected on net dispatches, not gross ones, and a mismatch here is often just unreconciled returns, not a platform error.
- Section 9(5) supplies are carved out. The Explanation to Section 52(1) defines "net value of taxable supplies" as taxable supplies made through the operator by other registered persons, other than services notified under sub-section (5) of Section 9 — because the platform already pays tax on those directly, taxing the same supply again at source would double up. This is the same boundary the field-routing question above sits on.
- Exempt or nil-rated goods don't attract it at all. Per the same 2017 CBIC FAQ (Q23): "When the supply itself is not taxable, the question of TCS does not arise" — a seller of GST-exempt or nil-rated goods through a marketplace should expect zero TCS on that line. (A zero-rated supply — an export or an SEZ sale — is a different, taxable thing at a 0% rate and isn't what that FAQ answer is about.)
One more case worth naming because it looks like TCS and isn't: if you sell your own products through your own website, you are technically an "electronic commerce operator" by Section 2(45)'s definition — but Section 52 only taxes supplies made by other suppliers through you. Selling your own stock on your own site attracts ordinary GST at the prevailing rate, never TCS, because there is no "other supplier" in the transaction for you to collect from.
Getting the credit: GSTR-8, matching, and the cash ledger
The platform — not you — files FORM GSTR-8 by the 10th of the following month, reporting what it collected against your GSTIN. Section 52(7) lets you claim that amount in your electronic cash ledger — not your credit ledger, and not automatically. Rule 87(9) of the CGST Rules credits it once you claim it: on the portal, that claim is the TDS and TCS Credit Received statement — you accept or reject each auto-populated entry and file it, and only accepted, filed amounts reach usable cash-ledger balance; a rejected entry flows back to the operator's own GSTR-8 for correction.
Section 52(8)-(11) also provides for a matching step: the operator's statement is to be matched against the outward supplies you declared, and a discrepancy "shall be communicated" to both sides. Where the operator's reported value exceeds yours and neither side rectifies it in the month it is communicated, Section 52(10)-(11) add the discrepancy to your output liability for the following month, with interest under Section 50(1). But Rule 79 of the CGST Rules — which prescribed how that discrepancy was communicated (FORM GST MIS-3/MIS-4) and added to your liability — was omitted with effect from 1 October 2022 by Notification 19/2022-Central Tax; only Rule 78 (the matching itself) remains. So as things stand there is no prescribed portal step that adds the gap automatically — but the statutory provision is still on the books, so treat an unreconciled excess as a real exposure, not a harmless one.
Reconciling what you actually see
In practice this comes down to three numbers that should agree and rarely do on first look: the TCS line in the platform's settlement report, the TCS your own sales register implies at the current 0.25%/0.25%/0.5% split, and what has actually posted to your electronic cash ledger on the GST portal. A seller on several marketplaces runs this three-way check once per operator per month — Amazon's settlement TCS figure is not Flipkart's, and neither is the portal's cash-ledger entry, until all three are confirmed to match.
Zoho's e-commerce invoice field doesn't close this loop for you — it feeds GSTR-1's ECO reporting tables, not a TCS-amount or cash-ledger reconciliation (above), and nothing in a standard bank feed import tells you which settlement deposit corresponds to which operator's GSTR-8 filing. Matching marketplace-deducted TCS to the electronic cash ledger, invoice by invoice, instead of trusting the settlement report's own total, is exactly the kind of reconciliation that's painful to do by hand across more than one platform and more than a few hundred SKUs a month.
Collected ≠ credited. Confirm it, invoice by invoice.
Recoup reconciles marketplace payouts and GSTR-8 TCS against your own sales register, operator by operator, so you can see which collected TCS has, and hasn't, reached your cash ledger.
Book a demo →Related guides
TCS under Section 52
The governing provision, the current rate and how the credit reaches your cash ledger.
GST reconciliation: the 2026 guide for finance teams
Why matching your platform payouts to your own sales register is one of four reconciliations that decide your credit.
Connecting Zoho Books to your Indian bank feed
Getting the marketplace settlement deposits into Zoho before you try to reconcile what was actually collected.
Auto-categorising bank transactions in Zoho Books
The rule pattern that can silently net a marketplace settlement against the wrong account.