A restaurant and delivery-platform control covering section 9(5), dine-in/takeaway, ECO tax, platform commissions, cloud kitchens, invoice responsibility and ITC restrictions.
Restaurant food sold directly and restaurant service supplied through an e-commerce operator can have different return and payment mechanics even where the kitchen and customer are the same.
Restaurant service is generally taxed under the notified rate framework, commonly without ordinary input-tax credit under the conditions of the entry.
From 1 January 2022, an e-commerce operator pays GST under section 9(5) on restaurant services supplied through its platform, subject to the notified scope.
The ECO does not collect section 52 TCS on the restaurant service value on which it pays tax under section 9(5), though other platform supplies and seller transactions require separate analysis.
The restaurant’s direct counter, takeaway, catering, packaged-goods and platform supplies should not be merged into one tax rule.
| Check | What to examine |
|---|---|
| Supply | Restaurant service, outdoor catering, packaged goods or other service. |
| Channel | Direct, own website or third-party ECO. |
| Taxpayer | Restaurant or ECO under section 9(5). |
| Invoice | Customer document and platform statement. |
| ITC | Restricted restaurant credit versus other business lines and platform services. |
A cloud kitchen sells meals through an app and packaged sauces through the same app. The ECO may pay tax under section 9(5) on restaurant service, while the sauce sale remains the kitchen’s goods supply with ordinary seller and TCS consequences. The settlement statement must separate them.
Create a product-channel matrix for dine-in, takeaway, catering, packaged goods and each platform. Configure the POS and marketplace mapping accordingly.
Reconcile daily gross orders, cancellations, discounts, delivery charges, platform commission, section 9(5) value and direct sales. Net bank payout is not turnover.
Identify the GSTIN, tax period, transaction, document and exact statutory question. Review supply, channel and taxpayer together. Freeze the source data so that later ERP edits do not destroy the evidence used for the decision.
Start with the contract or commercial event. Move through the invoice, receipt or movement evidence, e-invoice or e-way bill, accounting entry, return and electronic ledger. Classify each difference as timing, error, ineligible amount, statutory exception, disputed position or completed correction. Avoid a plug entry whose only purpose is to make two reports equal.
Prepare a concise position note with facts, authority, amount, alternative view and approval. Preserve the filing acknowledgement and update the responsible master data, vendor rule, invoice workflow or monthly checklist. The objective is not only to survive one review but to prevent the same issue in the next period.
GST positions are strongest when the transaction, legal provision, invoice, physical or service evidence, books, return and electronic ledger agree. A portal match without commercial evidence is not a complete control.
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.