GST Section 9(5): When the Aggregator Pays GST and the Restaurant Does Not

A hospitality group in Hyderabad operates four standalone QSR outlets, two cloud kitchens, and one restaurant inside a hotel where the highest published room tariff is ₹9,500. All seven supply through Zomato and Swiggy. The first six fall under Section 9(5) of the CGST Act — the aggregator pays GST on those supplies. The seventh does not — being inside a hotel above the ₹7,500 threshold, the restaurant pays its own 18% GST and claims ITC. The same legal entity holds one Telangana GSTIN. This article is for finance teams reconciling Section 9(5) liability across mixed-portfolio F&B operations.

What GST Section 9(5) Aggregator Restaurant Liability Involves

Section 9(5) of the CGST Act is a reverse-liability mechanism that shifts GST payment responsibility from the actual supplier to the e-commerce operator for notified categories of service. By Notification 17/2017 (Central Tax Rate) as amended, restaurant services supplied through e-commerce operators were brought under Section 9(5) effective 1 January 2022. From that date, Zomato, Swiggy, and similar operators became liable to pay 5% GST on restaurant supplies through their platforms — the restaurant is not the supplier of record for GST purposes on these specific supplies.

The complication for Indian F&B operators is that Section 9(5) does not apply uniformly. Standalone restaurants and cloud kitchens fall under it. Hotel-restaurants where any room category is published at ₹7,500 or above per unit per day are explicitly carved out. A single operator running both types within one GSTIN must segregate the two streams in GSTR-3B reporting and ITC eligibility tracking — and Section 9(5) of the CGST Act is unchanged by the new Income Tax Act 2025.

How Section 9(5) Applicability Works

Standalone Restaurants and Cloud Kitchens — Aggregator Pays

For a standalone restaurant or a cloud kitchen supplying through Zomato or Swiggy, Section 9(5) applies and the aggregator pays 5% GST to the exchequer through its own GSTR-3B. The restaurant records gross revenue in its books but does not remit output tax on these supplies. The restaurant cannot claim ITC on inputs attributable to Section 9(5) supplies — rent, ingredients, equipment, aggregator commission, and ad spend all flow to expense gross of GST. The 5% no-ITC regime that already applies to standalone restaurants reinforces this — there is no parallel ITC stream to recover input tax.

Hotel-Restaurants Above the ₹7,500 Threshold — Restaurant Pays

Restaurants located in a hotel where any unit of accommodation has a declared tariff of ₹7,500 or above per unit per day are explicitly excluded from Section 9(5). These continue to charge 18% GST with full ITC on their own supplies, whether dine-in, takeaway, or routed through aggregators. The aggregator does not pay Section 9(5) GST for these supplies — the restaurant is the supplier of record and remits output tax through its own GSTR-3B. The threshold test is the published tariff, not the discounted rate actually charged.

Direct Dine-In and Takeaway — Restaurant Pays Regardless

Section 9(5) is triggered only by supplies through an e-commerce operator. Direct dine-in, walk-in takeaway, brand-website orders, and own-app orders are outside Section 9(5) regardless of the restaurant’s regime. The restaurant remits output tax on these supplies in its own GSTR-3B at 5% no-ITC or 18% with-ITC depending on classification. Mixing direct and aggregator channels through the same outlet is the most common reporting trap in monthly filings.

Section 9(5) Applicability Reference

India Compliance Angle: GSTR-3B Reporting and ITC Blocking

For a restaurant under Section 9(5), the value of supplies made through the e-commerce operator is reported in Table 3.1.1 of GSTR-3B as an outward supply where tax is paid by the operator. The tax amount is not paid by the restaurant — Zomato or Swiggy reports and pays it through their own GSTR-3B in the corresponding Section 9(5) supplier-side table. The restaurant’s books record gross revenue, but the GST liability sits entirely with the aggregator. Misreporting Section 9(5) supplies as direct outward supplies in Table 3.1.a double-counts tax and surfaces in GSTR-9C annual reconciliation, often years after the error. The parallel discipline is ITC blocking: inputs attributable to Section 9(5) supplies cannot be claimed as input tax credit, and a mixed-portfolio operator must apportion shared inputs between Section 9(5) and non-9(5) streams under Rule 42 or Rule 43 of the CGST Rules. For broader rate-regime context, see restaurant GST reconciliation 5% vs 18% which covers the rate matrix that interacts with Section 9(5).

Multi-outlet F&B groups using GST reconciliation software configure outlet-to-Section-9(5)-applicability mapping at the master data level, segregate aggregator supplies into 9(5) and non-9(5) buckets, and apportion shared inputs under Rule 42 across the two streams. Reconciliation software India extends the same logic to direct-channel supplies and reconciles gross revenue in the books against aggregator-reported Section 9(5) tax in the same filing period. The GST Portal publishes Notification 17/2017 (Central Tax Rate), its 2022 amendment bringing restaurant services under Section 9(5), and the GSTR-3B Table 3.1.1 reporting framework. For the cloud-kitchen variant of this workflow, see cloud kitchen multi-brand reconciliation, and for the pillar overview see restaurant reconciliation India.

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 9(5) reporting issues raised by Indian restaurant finance teams.