A Sector-Wide Reckoning
The Central Board of Direct Taxes has opened one of its most visible sector-specific enforcement actions in recent memory. Per the CBDT press release dated 9 March 2026, transactional data of approximately 1.77 lakh restaurants in the food and beverage sector was analysed using AI-enabled analytical tools. A survey action under Section 133A was conducted on 8 March 2026 covering 62 restaurant establishments across 46 cities in 22 States, with a preliminary estimate of suppressed sales of around Rs. 408 crore. In the first phase of the follow-on "SAKSHAM NUDGE" compliance drive, advisory communications are being sent to about 63,000 identified restaurants asking them to review their records and file updated returns under Section 139(8A) before 31 March 2026. Those figures are from the official release; anything beyond them, including the eventual number of reopening notices, is not yet in the public record.
Why Restaurants, and Why Now
Restaurants sit at the intersection of multiple data trails that the department can now triangulate at scale. Every dine-in bill produces a GST invoice under the CGST/SGST Acts. Every UPI receipt leaves a signed trail with the NPCI and the acquiring bank. And for food ordered through aggregators, the statutory plumbing is unusual and important to understand correctly.
Since 1 January 2022, "restaurant service" supplied through an electronic commerce operator is a Section 9(5) notified service under the CGST Act, which means the ECO (Swiggy, Zomato, etc.) discharges the GST on that supply as if it were the supplier. Per CBIC Circular No. 167/23/2021-GST, the ECO does not collect TCS under Section 52 of the CGST Act on these restaurant services and does not reflect them in GSTR-8. That is a departure from the general ECO regime and must not be confused with it. On the direct tax side, Section 194-O of the Income-tax Act, 1961 requires the ECO to deduct TDS on the gross amount of sale of goods or services facilitated through its platform, subject to the conditions and exclusions in that section. The aggregator-to-restaurant money trail, therefore, is visible to the department primarily through Section 194-O TDS data, the ECO's own GST returns for Section 9(5) supplies, and the restaurant's bank settlements, rather than through a Section 52 TCS credit in the restaurant's own GST portal.
The Data Triangulation Playbook
The datasets the department can now match against each other in one workflow include:
- Aggregator data under Section 194-O: the gross order value reported by the ECO against the restaurant's PAN, reflected in Form 26AS and the Annual Information Statement.
- The ECO's Section 9(5) GST disclosures: the tax discharged by the aggregator on restaurant service supplies, which is a separate trail from the restaurant's own GSTR-1.
- UPI and card settlement data: acquiring bank settlement reports tagged to the merchant's account.
- GSTR-1 outward supplies and GSTR-3B tax payable: declared B2C and B2B supplies for the period.
- POS exports and e-invoice logs: for those crossing the e-invoicing threshold under Rule 48(4) of the CGST Rules.
- The turnover disclosed in the ITR: the final number the restaurant stands behind for income tax purposes.
Where these numbers tell materially different stories for the same period, the file moves into the validation queue. The exercise does not depend on a raid or a tip-off; it depends on datasets the department was already receiving but was, until recently, not matching in an automated, taxpayer-level view.
The Legal Machinery Behind the Drive
The first phase is a "nudge" — advisory messages encouraging voluntary correction through an updated return under Section 139(8A). An updated return carries additional tax under Section 140B, but it is a conditional compliance route, not a safe harbour. The provisos to Section 139(8A) bar an updated return in several situations, including where a search under Section 132 has been initiated, where a survey under Section 133A has been conducted, where a notice has been issued for assessment/reassessment/recomputation/revision, or where prosecution proceedings have been initiated, and in other cases listed in the section. A restaurant considering this route must check its eligibility against the current text of Section 139(8A) before assuming the door is open.
Where voluntary correction is not available or not pursued, the department has two familiar doorways:
- Section 148A — the pre-reopening inquiry procedure. As a general rule the assessing officer conducts an inquiry, provides an opportunity of being heard through a show cause, and passes an order under Section 148A before issuing a reopening notice under Section 148. Section 148A itself contains exceptions where the pre-notice inquiry is not required. Limitation for reopening is governed by Section 149 and has been amended multiple times in recent Finance Acts; practitioners should read the limitation framework as it stands on the date of the notice and the assessment year in question.
- Section 133A survey — the power used in the 8 March 2026 action. A survey is not a search; officers can enter business premises during working hours, inspect books and stock, and record statements, but they cannot break open locked premises or seize cash and stock the way a search under Section 132 permits.
Penalty Exposure if the Mismatch Sticks
Where additional income is ultimately assessed, the restaurant faces an exposure ladder rather than a single penalty. Section 270A imposes a penalty of 50% of the tax on under-reported income and 200% of the tax where the under-reporting is characterised as misreporting, with the categories of misreporting set out in Section 270A(9). Section 271AAC operates separately and more narrowly: where income determined by the assessing officer includes any income referred to in Sections 68, 69, 69A, 69B, 69C or 69D, a penalty equal to 10 per cent of the tax payable under Section 115BBE on such income is leviable, and no penalty under Section 270A is imposed on that same income. Section 276C opens the door to prosecution where the department takes the view that the conduct crosses into wilful attempt to evade tax. Where an updated return under Section 139(8A) is available and appropriate, it is usually a cheaper commercial outcome than a contested assessment, but that is a case-by-case analysis, not a blanket rule.
Reconciliation Checklist for Restaurant Owners
- Pull aggregator statements by PAN: download the full year statements from every food aggregator you work with, reconciled to the TDS credit reflected in Form 26AS and the AIS under Section 194-O.
- Reconcile aggregator-reported supplies: for restaurant service supplied through an ECO, the tax is discharged by the aggregator under Section 9(5) CGST and these supplies are not declared in your GSTR-1 as outward supplies. Keep a separate working tying the aggregator's order value to your bank settlements and your books, because this trail is invisible to your GST portal but very visible to the department.
- Export POS and billing software data: in chronological order, without filters, and verify that the invoice numbering is continuous. Any gap in the sequence should be explainable.
- Match bank and UPI settlements to sales: the acquiring bank settlement report and the UPI merchant statement should tie to daily sales, after adjustments for refunds and chargebacks.
- Reconcile GSTR-1 to GSTR-3B to ITR turnover: the three numbers should move in lockstep. Any reconciliation item should be documented contemporaneously, not reconstructed after a notice arrives.
- Examine cash sales trends: a sudden drop in declared cash sales around return filing dates is exactly the pattern the department is flagging. If your data shows such a drop, investigate before the officer does.
- Document genuine reasons for mismatches: seasonal closures, renovation downtime, a change of ownership, or a new GSTIN mid-year are all legitimate reasons for numbers to look odd. Put them on file in writing.
- Consider an updated return under Section 139(8A): if the reconciliation reveals genuine under-reporting and the eligibility conditions in Section 139(8A) are satisfied for the relevant assessment year, a voluntary updated return within the statutory window is often a cleaner commercial outcome than waiting for a contested proceeding.
If You Receive a Notice
Treat the communication carefully regardless of whether it is styled as an advisory, an intimation, or a formal notice. The following steps hold in almost every case:
- Read the source of data cited. Advisory messages in the current drive typically cite the dataset relied upon (aggregator data, UPI, GST returns). Knowing the source tells you what to reconcile against.
- Do not delete or "clean up" back-end data. Billing software logs, POS exports, and cloud backups may be examined. Post-notice edits convert an assessment dispute into a potential prosecution file.
- File a considered response, not an instinctive one. Draft replies should be backed by reconciliations on record, not by assurances. Where the department's number is wrong, show why with documents.
- Check Section 139(8A) eligibility first, then cost. Confirm that none of the bars in Section 139(8A) apply to the relevant assessment year. If the route is open, compare the additional tax and interest under Section 140B against the likely penalty exposure under Section 270A (and prosecution risk under Section 276C) on the available facts.
- Engage a practitioner before the reply is filed. Statements made at the advisory stage are often quoted back in subsequent Section 148A proceedings. A considered written reply, on file, is better than a phone call with the ward officer.
A Note for Genuinely Compliant Restaurants
Not every mismatch flagged by an automated system is under-reporting. Aggregator data can carry cancelled orders, refund adjustments, and delivery partner incentives that inflate the gross order value from the restaurant's perspective. UPI settlements can include non-sale receipts — owner deposits, refunds to customers routed back, inter-account transfers, and in some cases personal receipts in a proprietor's account. GST turnover can differ from income tax turnover because of schemes like restaurant composition, adjustment for discounts, or reversal of credit notes. A well-prepared reconciliation, with documentary support, is a genuinely compliant restaurant's strongest answer to the drive.
The Larger Signal
The restaurant exercise is less about restaurants specifically and more about a change in the department's posture. Sector-wide data triangulation — where aggregator feeds, bank rails, GST returns and income tax filings are matched at scale against a specific industry — is now a repeatable template. Whichever sector is next, the common thread will be the same: multiple visible data trails that the department can match against each other, and a history of cash-heavy billing. The F&B drive is the first public demonstration of that template; compliance-minded taxpayers in any similar industry should be treating their own reconciliations as a live exercise.
Comments (7)
Would be useful to see a template reconciliation workbook for this. Mapping aggregator 194-O data in 26AS to the restaurant's own bank settlements and books is where most small practitioners struggle.
The penalty section is clean. A lot of writing on 271AAC gets sloppy and says "10% penalty" without linking it back to Section 115BBE and the Section 68 to 69D trigger. That nuance matters in a reply.
From the operator side, the biggest risk factor is POS/billing software that treats cash bill deletion or selective wipe as a feature. If that capability exists in the system, it needs a documented audit trail for every use, or the vendor needs to be replaced.
The Section 139(8A) eligibility check is the step everyone wants to skip. Once a survey under 133A has happened, the updated return route may not even be open for the relevant year. Check the provisos before promising your client a soft landing.
Useful that the piece avoids the trap of citing a specific Finance Act year for the reopening timelines. Section 149 limitation has been amended multiple times and the right answer depends on the AY and the date of the notice.
The aggregator trail being invisible in the restaurant's own GSTR-1 is exactly where reconciliation goes wrong. You have to keep a parallel working tying bank settlements to the aggregator reports.
Good that you flagged the Section 9(5) vs Section 52 distinction. A common error is expecting a TCS credit from Swiggy or Zomato in the restaurant's GST portal for restaurant orders. That is not how it works post 1 Jan 2022, and CBIC Circular 167/23/2021-GST spells it out.