Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Restaurant aggregators including Zomato and Swiggy collect 1% TCS under Section 52 of the CGST Act on net taxable supplies, but the credit reaches the restaurant only via the aggregator's monthly GSTR-8 filing, auto-populates into a non-ITC section of the GST electronic cash ledger, and must be claimed and cleared against output GST in GSTR-3B — a multi-step flow that is repeatedly confused with income-tax TCS or treated as ITC, leading to unclaimed credits and incorrect output-tax offset.
Pull the aggregator settlement file with restaurant-wise net taxable supply per month, accrue Section 52 TCS receivable in the cash-ledger sub-account at 1% of net taxable supply with intra-state CGST/SGST split or inter-state IGST, match against the auto-populated GSTR-8A view on the GST portal, accept the entries to flow into the electronic cash ledger, and utilize the cash-ledger balance to offset output GST in the same period's GSTR-3B.
Aggregator settlement-file connector with monthly net-taxable-supply extraction; intra-state vs inter-state TCS classifier with CGST/SGST/IGST split; GSTR-8A reconciliation interface keyed to aggregator GSTIN and month; refund-period reversal logic to adjust net taxable supply across calendar-month boundaries; cash-ledger utilization mapper to offset GSTR-3B output liability.
A reconciled Section 52 TCS receivable that ties every aggregator GSTR-8 entry to a restaurant cash-ledger credit, every refund reversal to the correct calendar month, and every cash-ledger balance to a GSTR-3B utilization line — with no leakage of unclaimed credits and no confusion with income-tax TCS.
A multi-city cloud kitchen running on Zomato and Swiggy notices that its electronic cash ledger has a growing TCS balance that never seems to come down. The accountant has been treating the TCS credit as input tax credit and the GSTR-3B utilization is wrong. This article is for restaurant finance teams reconciling Section 52 CGST Act TCS collected by food aggregators, from the GSTR-8 filing through the electronic cash ledger to the GSTR-3B output-tax offset.
What Section 52 CGST Act TCS Reconciliation Involves
Section 52 of the Central Goods and Services Tax Act 2017 requires e-commerce operators — including restaurant aggregators like Zomato and Swiggy — to collect 1% TCS on the net value of taxable supplies made by their suppliers through the platform. The mechanism is GST-side, separate from income tax, and unchanged by the Income Tax Act 2025. The TCS flows from aggregator to the GST portal, auto-populates into the supplier’s electronic cash ledger, and offsets the supplier’s output GST liability when GSTR-3B is filed.
A point of repeated confusion: this is not income-tax TCS. Section 206C of the Income Tax Act (now mapped to Section 394 of the Income Tax Act 2025 with payment codes 1071 onward) is a separate regime governing different transactional categories. Restaurant aggregator settlements involve only the GST Section 52 TCS. The two regimes share a name and a rate convention; they share nothing else. Reconciling them as one ledger is wrong.
How Section 52 Works on a Restaurant Aggregator Settlement
Net Taxable Supply Base
The TCS base is the net value of taxable supplies made by the restaurant through the platform during the calendar month — gross outward supply less any returns, refunds, or cancellations processed in the same month. Exempt or zero-rated supplies (where applicable to specific menu categories) are excluded from the base. The 1% TCS is split as 0.5% CGST and 0.5% SGST for intra-state supplies, or charged as 1% IGST when the supply is treated as inter-state.
The aggregator computes the figure restaurant-by-restaurant — by GSTIN — and applies the rate to each restaurant’s monthly net taxable supply. The figure appears as a deduction line on the weekly settlement file and is also surfaced in the aggregator partner dashboard.
GSTR-8 Filing by the Aggregator
The aggregator files GSTR-8 by the 10th of the following month. GSTR-8 declares, supplier-by-supplier, the gross supply, the net taxable supply, and the 1% TCS collected. Once filed, the GST portal auto-populates each supplier’s view: the entries appear in the GSTR-8A reconciliation form and propagate into the TCS-specific section of the supplier’s electronic cash ledger.
The restaurant does not file anything in response to GSTR-8 directly. It accepts the auto-populated entries through the GSTR-8A view, after which the credit becomes available in the cash ledger for utilization in GSTR-3B.
Cash Ledger — Not ITC
A common error: the Section 52 TCS credit is not input tax credit. ITC sits in the electronic credit ledger and offsets output tax according to the ITC utilization rules in Sections 49 and 49A of the CGST Act. The Section 52 TCS credit sits in a separate sub-section of the electronic cash ledger and offsets output tax as a cash-equivalent balance. Treating it as ITC produces a wrong GSTR-3B utilization and may trigger a portal mismatch alert during the next reconciliation cycle.
Section 52 TCS Restaurant Aggregator Reconciliation Reference
| Element | Detail |
|---|---|
| Statute | Section 52, CGST Act 2017 (unchanged by Income Tax Act 2025) |
| Rate | 1% — split 0.5% CGST + 0.5% SGST (intra-state) or 1% IGST (inter-state) |
| Base | Net taxable supply through the platform per calendar month |
| Aggregator filing | GSTR-8, by the 10th of following month |
| Supplier view | GSTR-8A (auto-populated reconciliation form) |
| Credit destination | Electronic cash ledger (TCS sub-section) — not ITC ledger |
| Utilization | Offsets output GST in GSTR-3B for the same period |
Refunds, Cancellations, and the Claim-and-Clear Cycle
Within-month refunds are netted by the aggregator before TCS is computed, so the GSTR-8 figure already reflects the reversal. Across-month refunds reduce the next month’s net taxable supply and therefore the next month’s TCS — meaning the supplier’s cash-ledger credit in that later month is smaller than the gross supply would suggest. Reconciliation must therefore match each refund-period reversal back to the original sale period in the books while accepting that the cash-ledger entry follows aggregator processing, not original transaction date.
The claim-and-clear cycle has four steps. First, the aggregator collects 1% TCS at settlement time and reflects the deduction in the partner settlement file. Second, the aggregator files GSTR-8 by the 10th of the following month with restaurant-wise breakdowns. Third, the GST portal auto-populates the entries into the supplier’s GSTR-8A and into the electronic cash ledger. Fourth, the restaurant utilizes the cash-ledger balance against output GST in GSTR-3B for the period.
The cycle takes 30 to 45 days end-to-end. A late or missing GSTR-8 from the aggregator stalls the cash-ledger credit and forces the supplier to either accept the gap or follow up with the platform’s tax desk. Reconciliation must therefore track aged TCS receivables — accrued in the books from settlement files, not yet credited to the cash ledger — and trigger a follow-up after 45 days.
What Section 52 TCS Is Not — The Income-Tax Confusion
The most damaging reconciliation mistake is treating Section 52 GST TCS and income-tax TCS as the same ledger. They are not. Section 52 is GST law, governed by the CGST Act, reported in GSTR-8, credited into the GST electronic cash ledger. Income-tax TCS sits under Section 206C of the Income Tax Act 1961 — now mapped to Section 394 of the Income Tax Act 2025 with payment codes 1071 onward — and applies in transaction categories that do not include restaurant aggregator supplies. The two regimes have separate bases, separate rates in some categories, separate filings, and separate ledgers.
Restaurant aggregator settlements carry only the GST Section 52 TCS. The income-tax TCS regime does not apply to a Zomato or Swiggy restaurant payout. Booking the aggregator’s TCS line as income-tax TCS receivable produces both an unclaimed GST cash-ledger balance and a phantom income-tax credit that will never appear in Form 168.
Finance teams running payment gateway reconciliation workflows typically extend the same logic to aggregator settlements, where the GST TCS layer adds one more reconciliation lane on top of commission, GST on commission, and Section 393 income-tax TDS. Reconciliation software India handles the order-level GSTR-8 ingestion, the cash-ledger sub-account mapping, and the cross-month refund reversal in a single pipeline. The Goods and Services Tax portal is where Section 52 of the CGST Act is published, where the aggregator’s GSTR-8 is filed, and where the supplier’s electronic cash ledger is hosted. For peer cluster context, see Zomato restaurant settlement reconciliation and Swiggy restaurant settlement reconciliation. The restaurant reconciliation India pillar covers the umbrella framework.
For the restaurant chain industry surface, see the Restaurant Chains industry guide. For the buying-intent surface covering this rail, see the restaurant reconciliation software for India overview, and for a head-to-head against the aggregator-side reconciliation tool category, see TransactIG vs Cointab.
The questions below address the most common Section 52 aggregator TCS reconciliation issues raised by Indian restaurant finance teams.