Section 52 TCS on Quick Commerce FMCG — 2026 Reconciliation Guide

A national personal-care FMCG brand closes the books on 31 May 2026 with ₹186 crore of net taxable value supplied through quick-commerce platforms across the preceding twelve months — split roughly 38 percent through Blinkit, 27 percent through Zepto, 19 percent through Swiggy Instamart, and the balance through BBNow and a thin slice through Tata 1mg. At the notified 0.5 percent rate, the cumulative Section 52 TCS the four ECOs should have collected works out to ₹93 lakh. The brand’s GSTR-2A Part-C across all four platforms shows ₹89.7 lakh accepted into the electronic cash ledger. The ₹3.3 lakh gap sits in 412 individual order-level lines across the four ECOs — mostly returns and cancellations that flowed through the brand’s settlement file but lagged on the ECO’s GSTR-8 cycle, with a smaller pocket of genuine ECO under-collection on a Mumbai-cluster batch from December 2025. This is Section 52 TCS quick commerce FMCG reconciliation at production scale, and the discipline that resolves it is what separates a clean year-end GSTR-9C from a Section 73 question on output GST utilisation. The article that follows walks the regulatory mechanics, the operational flow, a worked example, and the controls the brand’s tax team uses to keep the credit cycle honest.

Quick reference

What the quick-commerce FMCG supply actually looks like in India

The structural fact that determines the entire reconciliation is the supply mode. When a consumer opens Blinkit and orders a bottle of Saffola oil, a pack of Britannia Tiger biscuits, a tube of Colgate toothpaste, and a four-pack of Maaza, the platform displays the inventory, accepts the order, collects the consideration on its payment rails, and arranges the 10-minute fulfilment from the nearest dark store. The brands (Marico for Saffola, Britannia for Tiger, Colgate-Palmolive for the toothpaste, Coca-Cola India for Maaza) are the suppliers. The platform is the ECO — the electronic commerce operator under Section 2(45) CGST. The relationship between the brand and the ECO is governed by a master listing-and-fulfilment agreement that specifies commission, settlement terms, return policy, and the brand’s responsibility for the underlying tax invoice on the consumer.

The order travels in three parallel data flows. The first flow is the consumer-facing transaction: order placed, payment collected by the ECO, goods delivered. The second flow is the brand-facing settlement file: a daily or weekly file from the ECO listing each order with order ID, brand SKU, net taxable value, gross GST, ECO commission, return/cancellation adjustment, and the net payable to the brand after commission netting. The third flow is the tax-reporting layer: the brand raises its own outward-supply tax invoice on the order (or, in marketplace mode, on the ECO as the buyer who then re-supplies to the consumer); the ECO files GSTR-8 monthly with the cumulative TCS at 0.5 percent of net taxable value; the brand’s GSTR-1 reports the outward supply; the brand’s GSTR-2A Part-C reflects the TCS credit; the brand’s GSTR-3B claims the credit against output liability.

The order volume at a Tier-1 FMCG brand on a single quick-commerce platform routinely runs to 8,000 to 25,000 lines per day across the brand’s portfolio. Aggregated to monthly cumulatives across four platforms, the brand is reconciling between roughly 1 to 3 million order-level rows in its outward-supply register and four consolidated TCS lines on GSTR-2A Part-C. Without a structured reconciliation discipline, the variance between the two sits unreconciled in the cash-ledger reconciliation working papers all the way to year-end. For brands also navigating the broader quick-commerce settlement reconciliation flow — fees, deductions, returns, the daily payout — the TCS line is one of several variance streams that compound if not separated cleanly.

The Section 52 overlay — what TCS is and what it is not

Section 52 of the CGST Act 2017 sits at the intersection of two principles. The first is the convenience-of-collection principle: when a multi-supplier platform collects payment on behalf of many small suppliers, it is administratively efficient for the platform to deduct a small slice at source so the supplier’s GST liability is partly pre-paid in the cash ledger and the tax administration has visibility into platform-mediated supply at the aggregator level. The second is the credit-flow principle: TCS is not the supplier’s tax — it is the supplier’s tax pre-collected by the ECO and surrendered back to the supplier via the GSTR-2A → cash ledger pipeline, against which the supplier draws to discharge output GST on the same supply.

Sub-section (1) of Section 52 lays down the trigger: every ECO that is not an agent of the supplier shall collect TCS at a rate not exceeding 1 percent of the net value of taxable supplies made through it by other suppliers where consideration is collected by the ECO. The “not exceeding 1 percent” framing is critical: 1 percent is the statutory ceiling; the actual rate is whatever the Central Government notifies. The original notification set the rate at 1 percent (0.5 percent CGST + 0.5 percent SGST, or 1 percent IGST inter-state). The CBIC reduced the rate to 0.5 percent (0.25 percent CGST + 0.25 percent SGST, or 0.5 percent IGST) via Notification 15/2024-Central Tax dated 10 July 2024, with the corresponding SGST and IGST notifications carrying the same effective date. Quick-commerce ECOs have applied the reduced 0.5 percent rate from that effective date forward.

The base is “net value of taxable supplies” — defined in Explanation 1 to Section 52 as the aggregate value of taxable supplies of goods or services or both made by the supplier through the ECO during the period reduced by the aggregate value of taxable supplies returned to the suppliers during that period. Returns reduce the base in the period the return is processed, not the period of the original supply. This is the single biggest source of timing-lag variance in the brand-vs-ECO TCS reconciliation: the brand’s settlement file recognises the return on the date the return is logged at the dark store; the ECO’s GSTR-8 may recognise the return in the next monthly cycle if the return cuts across the GSTR-8 filing date.

Sub-section (4) requires the ECO to file GSTR-8 monthly by the 10th of the succeeding month — the same cadence as GSTR-1 for regular suppliers — listing the TCS collected per supplier GSTIN. Sub-section (7) entitles the supplier to claim the TCS credit in the electronic cash ledger on filing of the GSTR-8 by the ECO and acceptance of the line on the supplier’s GSTR-2A. Sub-section (9) provides the matching mechanism: the supplier’s outward supplies as reported in GSTR-1 are matched against the GSTR-8 figure, and unmatched lines route back to the ECO for correction.

Section 9(5) does not cover FMCG goods — the distinction that closes the door

A separate provision, Section 9(5) CGST, deserves careful clarification because brand finance teams occasionally treat it as overlapping with Section 52. Section 9(5) empowers the Central Government to notify categories of services the supply of which by an ECO is to be treated as supply by the ECO itself — turning the ECO into the deemed supplier. Four categories are notified to date: passenger transport (radio-taxi, motor-cab, maxi-cab, motorcycle, and analogous services — the Ola/Uber leg), housekeeping and allied services (plumber/carpenter/electrician — the Urban Company leg), restaurant service including cloud kitchens (the Swiggy/Zomato restaurant leg, effective 1 January 2022 via Notification 17/2021-CT(R)), and hotel accommodation supplied by unregistered persons through the ECO (the OYO leg, with conditions).

FMCG goods — soaps, biscuits, beverages, packaged staples, personal-care SKUs, household consumables — are not within any of these four service categories. Goods are not within Section 9(5) at all. Quick-commerce supply of FMCG goods through Blinkit, Zepto, Swiggy Instamart, BBNow, Tata 1mg’s grocery section, or any other goods-marketplace ECO is therefore not a deemed-supplier scenario. The brand remains the supplier of record. The brand raises its own tax invoice. The brand reports the outward supply on its own GSTR-1. The brand discharges the full output GST liability on its GSTR-3B. The ECO collects TCS at the notified 0.5 percent under Section 52 — and only TCS — and the flow ends there. The Section 9(5) aggregator restaurant liability mechanics are an entirely separate regime that applies to the restaurant/cloud-kitchen leg of a Swiggy or Zomato platform, not to the Instamart grocery leg.

The administrative cleanliness of this distinction matters. A brand that mistakenly assumes the ECO has discharged the GST under Section 9(5) on the FMCG leg will under-report outward supply on GSTR-1 and under-discharge output GST on GSTR-3B — drawing a Section 73 demand for the gap. A brand that correctly treats the FMCG leg as its own outward supply under Section 52 reports the gross outward supply on GSTR-1, discharges full output GST on GSTR-3B, and uses the TCS credit from GSTR-2A Part-C against that liability.

Distinguishing Section 52 TCS from Section 51 TDS and from Section 9(5) deemed supplier

Brand finance teams that handle B2G contracts in parallel sometimes blur Section 52 with Section 51. Section 51 CGST is government-deductee TDS: when a department, public-sector undertaking, local authority, or notified body makes a payment under a contract exceeding ₹2.5 lakh, the deductor deducts 2 percent (1 percent CGST + 1 percent SGST or 2 percent IGST) at source, files GSTR-7 by the 10th of the succeeding month, and the deduction flows to the supplier’s GSTR-2A Part-B for cash-ledger credit. Section 51 is irrelevant to quick-commerce ECO transactions — none of the listed ECOs are government deductees. Section 52 is the operative provision; Section 51 sits parallel and orthogonal.

Section 9(5), as already noted, is the deemed-supplier regime for four notified service categories. It applies to passenger transport, housekeeping, restaurant service, and hotel accommodation supplied through an ECO. Where Section 9(5) applies, the ECO discharges the full output GST on the supply; the underlying supplier (the driver, the carpenter, the restaurant, the unregistered hotelier) does not raise a separate tax invoice on the consumer; and the ECO does not also collect TCS under Section 52 on the same supply (the two provisions do not stack — Section 9(5) carves the supply out of the supplier’s outward register and into the ECO’s). For the FMCG-goods leg of quick commerce, Section 9(5) is not triggered, Section 52 is the only applicable mechanism, and the brand’s reconciliation discipline is the GSTR-2A Part-C cycle.

A worked example — Dabur Real Juice through Blinkit (illustrative)

A consumer-foods brand listing its juice portfolio on Blinkit closes the May 2026 books and pulls the Section 52 reconciliation for the month. The example uses Dabur’s Real Juice listings as a stylised reference. Numbers are illustrative — the brand’s actual disclosed quick-commerce GMV, commission, and TCS lines are not public and the figures here are representative of the operating pattern, not actual brand data. Cross-verify against your own ECO settlement file and GSTR-2A Part-C before action.

The settlement file from Blinkit for May 2026 shows the following at the consolidated level for the brand’s GSTIN across the Delhi NCR cluster.

The variance of ₹2.8 thousand traces to nine return orders processed by Blinkit on 31 May (post 5 pm cut-off) — they appear in the brand’s settlement file for May but flow into Blinkit’s June GSTR-8 cycle as the cut-off determined return-period treatment. The brand accepts the May ₹2.279 lakh on GSTR-2A Part-C; the ₹2.8 thousand timing lag is held in a variance register and reconciles cleanly in the June cycle when Blinkit recognises the returns.

A parallel reconciliation runs for the inter-state cluster — Blinkit’s Bengaluru and Hyderabad dark stores serving an out-of-state consumer base where IGST applies. The 0.5 percent IGST TCS notification carries the same effective date (10 July 2024). For the May 2026 inter-state leg, the brand has ₹186 lakh net taxable value, expected IGST TCS of ₹0.93 lakh, and Blinkit’s GSTR-8 line reflects ₹0.93 lakh — matched. The combined credit accretion to the brand’s electronic cash ledger for May 2026 from the Blinkit leg alone is approximately ₹3.2 lakh; the brand uses this against its output GST liability in the GSTR-3B for May, filed by 20 June 2026.

The reconciliation surfaces three actionable findings for the brand’s tax controller. First, the 31 May cut-off timing lag is a recurring monthly pattern — it crosses every month-end and self-resolves in the next cycle, but the variance register must be tagged “timing — auto-resolve” rather than “variance — investigate” so the controller’s attention is not pulled away from real gaps. Second, the brand’s GSTR-1 outward supply for May at the Blinkit GSTIN-counterparty level must be ₹461.4 lakh (the net of returns), not the gross ₹480 lakh — the TPM accrual versus payout reconciliation discipline that handles credit-note linkage to original invoices applies here too. Third, the post-22 September 2025 GST 2.0 transition matters for the rate-mix on the brand’s Real juice portfolio — the original 12 percent slab on fruit juice is unaffected (juice did not move in the GST 2.0 rate rationalisation), but the brand’s parallel beverage SKUs in the aerated/sweetened category are now in the 40 percent NSAB slab, materially raising the per-order output GST and the per-order TCS base.

The September 2025 GST 2.0 rate transition — what changed for quick-commerce FMCG

CBIC Notifications 09 to 16/2025-CTR dated 17 September 2025, effective 22 September 2025, restructured several FMCG categories. Soaps, shampoos, toothpaste, biscuits (HSN 1905), chocolates, and metal kitchenware consolidated at 5 percent (from various 12 percent and 18 percent slabs). Aerated and sweetened beverages moved to the 40 percent NSAB slab. The HSN-rate master that drives the brand’s outward-supply tax invoice — and therefore the gross GST in the settlement file, and the Section 52 TCS base — must reflect the rate that applied at the time of supply, not the rate at the time of order placement if an order straddles the 22 September 2025 effective date. For the May 2026 reconciliation window referenced above, the transition is fully behind the brand and all SKUs are on the post-22-September rates; for any year-end GSTR-9C work that touches the September 2025 quarter, a straddle filter on the per-order register is non-negotiable.

The TCS rate itself does not move with the rate-of-supply slab. Section 52 TCS is 0.5 percent of the net taxable value irrespective of whether the underlying supply attracts 5 percent, 12 percent, 18 percent, or 40 percent GST. The rate-mix change affects the gross GST line in the settlement file (and therefore the brand’s output GST liability that the TCS credit will be used against), not the TCS calculation.

Common reconciliation breakages

• The brand’s settlement-file register includes order-level returns processed late on the last day of the month; the ECO’s GSTR-8 picks them up in the next month’s cycle — manifests as a recurring small variance that auto-resolves on the next cycle.
• The ECO reports TCS on inter-state supplies at 0.5 percent IGST but the brand’s register splits the same supply as CGST+SGST because the GSTIN-counterparty mapping in the brand’s master was set up as intra-state — fix the master.
• A registered seller flips from the brand’s own GSTIN to a CFA’s GSTIN mid-month; the ECO continues to file GSTR-8 against the old GSTIN — file a correction request and adjust the next cycle.
• Returns processed by Blinkit after 30 days from order date are sometimes treated by the ECO as out-of-period and not netted in the GSTR-8 base — verify the per-return ageing and chase the correction.
• The brand under-reports outward supply on GSTR-1 because the tax team treats some quick-commerce orders as Section 9(5) deemed supply by the ECO — the regulatory fact is FMCG goods are not in Section 9(5); GSTR-1 must report the gross outward supply.

How a reconciliation platform handles this

A purpose-built reconciliation platform ingests the per-order settlement file from each ECO in its native format, ties each order to the brand’s outward-supply tax invoice register by order ID and GSTIN, computes the expected Section 52 TCS at the notified 0.5 percent on net taxable value, parses the ECO’s GSTR-8 cumulative line from the brand’s GSTR-2A Part-C scrape, classifies the variance by code (timing lag — returns straddling month-end, ECO under-collection, brand register over-statement, GSTIN-master error), surfaces ageing buckets on stuck variances, and produces an audit-ready evidence pack that ties the accepted GSTR-2A Part-C line through the electronic cash ledger movement into the brand’s output GST utilisation in GSTR-3B. The same engine carries the year-end GSTR-9C reconciliation between outward supplies and TCS-bearing supplies through ECOs as a roll-forward of monthly closures. The discipline is what FMCG reconciliation software India brings to a category where the daily order volume and the four-ECO fan-out make manual reconciliation untenable past Tier-2 brands.

Cross-cluster bridges and where to read next

For brands navigating the broader quick-commerce settlement variance — fees, deductions, returns, the daily payout — the quick-commerce FMCG settlement reconciliation article walks the operational flow that the Section 52 TCS layer sits on top of. The platform-specific cuts are at Blinkit, Zepto, and Swiggy Instamart. For the trade-spend layer that runs in parallel — distributor schemes, BTL claims, the per-scheme Section 15(2) determination — see the TPM accrual versus payout reconciliation discipline. The category pillar is reconciliation software India, and the commercial anchor for the FMCG vertical is FMCG reconciliation software India.

The five FAQs below address the operational questions Indian FMCG tax controllers ask most often when implementing Section 52 TCS reconciliation across multiple quick-commerce ECOs.

Terra Insight Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 27 June 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024