AI drafted 200 restaurant GSTR-3B filings — the gotcha

Two hundred draft GSTR-3B returns, run through an AI pre-check before any owner or CA touched the GST portal. That number is illustrative — a batch of test filings, not an audited public dataset — but the pattern it surfaced is real and it's coming for every dine-in restaurant in India filing after the 20th of this month. Most of the 200 didn't fail on the thing CAs usually catch — a missing supplier GSTIN. They failed on a single table most owners have never heard of: Table 3.1.1, Section 9(5).

The April 2026 change: what the ITC Zero Mismatch Policy hard-block actually does

Until this year, an ITC mismatch between your GSTR-3B and your GSTR-2B was a soft problem. You filed anyway, the portal let it through, and you reconciled the gap later — often after a notice, often months later, often with your CA quietly absorbing the awkward conversation. From April 2026, that soft block is gone. Under the new ITC Zero Mismatch Policy inside the Invoice Management System (IMS), if the ITC you claim in GSTR-3B exceeds what's showing in your auto-generated GSTR-2B for the same period, the portal will not let you file. Not a warning banner. Not a "proceed anyway." A hard stop, on the 20th, the day the return is due.

The ECRS tracking layer sitting behind this is also stricter than before — a negative or unreconciled ITC balance can hold up filing on its own, separate from the mismatch check. Two gates now, where there used to be one soft nudge.

The 200-filing experiment: how AI pre-validates each return before portal submission

Here's the workflow that avoided the block across that test batch. GSTR-2B auto-generates on the 14th of every month — the same day, every month, no exceptions. Instead of waiting for the CA to build the return around the 18th or 19th, you feed AI two things the moment the 2B lands: the 2B file itself, and your ITC register (the invoice-level ledger of what you've actually claimed or plan to claim for the period). You can run this pre-check in ChatGPT, Claude, or a purpose-built agent — the tool matters far less than the timing.

AI does the arithmetic the portal will do on the 20th, six days early. It totals claimed ITC against what the 2B actually shows, line by line, and tells you exactly where the two numbers diverge — which invoice, which supplier, which amount. If the totals already match, you know on the 14th that filing on the 20th is a formality. If they don't, you have six days to fix it instead of the zero days a hard block gives you at the portal.

The gotcha pattern AI found most: Section 9(5) aggregator sales mis-reported in Table 3.1.1

The supplier-GSTIN error is the one every CA is trained to hunt for, and most of them do it well. The error that showed up far more often in the test batch was structural, not clerical: restaurants selling through Swiggy and Zomato are required to report that aggregator-routed revenue in Table 3.1.1(ii) of GSTR-3B, at zero tax — because the aggregator itself pays and reports the 5% GST on that order under Section 9(5), in their own Table 3.1.1(i). The restaurant's job is just to show the sale, not the tax.

Plenty of auto-fill tools and rushed manual entries default every sale — dine-in, takeaway, aggregator — into 3.1.1(i), treating aggregator orders as if the restaurant collected and owes the tax on them directly. That single defaulting habit changes the ITC math for the whole return, because ITC eligibility and the output-tax reconciliation are computed against how the sale was classified. Under the old soft-block regime, this drifted for months before anyone noticed. Under the new hard-block, the portal notices on the 20th, mid-filing, with no reconciliation window left. AI catching this on the 14th — because it can hold your full aggregator settlement pattern next to Table 3.1.1 and flag the mismatch mechanically — is the single highest-value check in this workflow.

What happens when the hard-block fires

If the return doesn't go through on the 20th, the cascading cost isn't just the late fee, though that's real: a structure that compounds monthly and is capped around ₹2,000 for a restaurant under ₹1.5 crore turnover, higher above that band. The bigger cost is what a repeated block signals inside ECRS — a pattern of near-monthly reconciliation trouble is exactly what raises visibility for a Rule 88D notice, which auto-triggers when an ITC mismatch crosses ₹25 lakh or 20% in either direction. One late filing is a fee. Three in a row starts to look like a pattern a GST officer wants explained. None of this requires wrongdoing — a Table 3.1.1 classification habit repeated for six months can get there on its own.

AI as the pre-filing checkpoint your CA doesn't see until the 20th

The honest counter-argument here is "my CA already handles this." Most do, well — but look at the actual calendar most small restaurants run on: documents reach the CA on the 18th or 19th, the return gets filed on the 20th because that's the deadline, and there is functionally no buffer between "CA sees the numbers" and "return must go through." If the hard-block fires that day, there's no time left to fix a Table 3.1.1 misclassification before the deadline passes.

Moving the check to the 14th — the day the 2B auto-generates, six full days before the deadline — changes the resolution window from two days to six. That's the entire value of the AI pre-filing step for GST compliance: not replacing the CA's judgment on the return, but giving the CA (and the owner) a clean, pre-flagged packet on day one of the filing window instead of a surprise on the last day of it.

So what now

If you run a dine-in restaurant with any Swiggy or Zomato volume, ask whoever handles your GSTR-3B to pull the 2B on the 14th this month and run it against your ITC register before anything gets sent to the CA — Table 3.1.1 first. This is exactly the kind of pre-filing check the Compliance Manager inside your SideKyk team runs automatically on the 14th, every month, so the mismatch is already resolved days before the CA even opens the file — join the restaurants waitlist at sidekyk.ai/restaurants and we'll WhatsApp you when your slot opens.