His client paid seven months late. The GST notice arrived anyway. ₹2.55 lakh demand.
📱 Irfan, founder of Kashmir Trails Digital, a five-person tourism-marketing agency in Rajbagh, Srinagar, manages social-media campaigns for the J&K Tourism Department and private houseboat operators. In March 2025, J&K Tourism approved a ₹12 lakh invoice for Q1 social-media work, promising payment "by end of March." It did not arrive. J&K Bank's GST reconciliation system went partially offline. The invoice sat in disbursement queue for seven months. In June, the payment finally arrived. But the GST system showed zero input credit — the supplier invoice was not matched in GSTR-2B. Irfan's accountant filed GSTR-3B anyway, claiming the credit. In August, a notice: ₹2.55 lakh demand plus interest for "mismatched input credit." 📧
🚨 The problem
Under GST, when Irfan invoices a client, he files GSTR-1 (outward supplies). The client receives the invoice and files it in their GSTR-2 (inward supplies). The government reconciles both and produces GSTR-2B (matched inward) for Irfan to see. If GSTR-2B shows the invoice, Irfan can claim input tax credit (ITC) in GSTR-3B (his monthly return). The system works when payment and filing happen quickly. But when J&K Bank went offline for a week and the invoice sat in the disbursement queue for seven months, the sync broke: Irfan filed GSTR-1 (March 31). J&K Tourism eventually filed GSTR-2 (April 30, late). But payment didn't hit Irfan's account until June 19 — after GSTR-2B had already been closed for Q1. GSTR-2B showed zero for the invoice. Irfan claimed the credit anyway in GSTR-3B. The GST notice treated the mismatch as fraud: ₹2.55 lakh demand (₹2.16 lakh ITC + ₹39,000 interest) + the stigma of a tax notice.
🚀 How GabFORGE helped
Shabina, Irfan's accountant, suggested using an AI agent to understand GST Rule 37(1) — a provision that allows manual matching of GSTR-2A (unmatched inward) entries when both parties have filed and there is a technical sync delay. The agent helped Irfan build a reply to the GST notice over two evenings:
- 🔍 Pulled GSTR-2A. The invoice appeared in GSTR-2A (government's record of what J&K Tourism filed) but not GSTR-2B (matched entries). Screenshot attached.
- 💬 Documented the sync gap. Timeline: invoice March 20, GSTR-1 filed March 31, payment received June 19, J&K Tourism's GSTR-2 filed April 30. The sync break occurred because payment and filing were months apart.
- 📞 Cited Rule 37(1). The agent pulled the exact statutory language: "GSTR-2A entries can be matched retroactively if both parties have filed and there is a technical sync delay." Applied it to Irfan's case.
✅ Outcome: Irfan filed the reply with the GST Department within 10 days, requesting manual GSTR-2B reconciliation under Rule 37(1). He included GSTR-2A screenshot, bank transfer slip, original invoice, and email from J&K Tourism confirming their GSTR-2 filing date. Two months later, GST Department order: "Manual reconciliation allowed. GSTR-2A entry matched to GSTR-2B. Demand notice withdrawn. Input tax credit allowed. No interest payable." The ₹2.55 lakh vanished. Kashmir Trails Digital's compliance record remained clean.
🇮🇳 Why this matters
When a small service agency receives a GST notice for a GSTR-2B mismatch, the default assumption is "the government's number is correct, pay it." But GST systems sync. Banks go offline. Suppliers file late. The government's own processes lag. A gap opens: the invoice is real, payment is real, both parties filed — but reconciliation didn't finish. An agent that reads GSTR-2A, cross-references bank statements, and says "this is a sync lag under Rule 37(1), here's how to fix it" prevents ₹2.55 lakh damage and the stress of seeming like a tax cheat.
The long version has Irfan's seven-month wait, J&K Bank's offline period, Shabina's accountant intuition to cite Rule 37(1), and the principle: "GSTR-2A check karte hain. Dekh lete hain ki sync hua ya nai" — let's check GSTR-2A and see if the sync happened.