A DRC-01A appeared on his GSTN. ₹3.7 lakh demand. He had no idea what it meant.
💍 Mehul, founder of a small wedding-planning agency in Athwa Gate, Surat, manages events (decorations, catering coordination, mandap logistics) and books vendors. In March 2026, a DRC-01A (Demand Response Check — an intimation before a formal Show-Cause Notice) appeared on his GSTN dashboard with a ₹3.7 lakh demand. He had no idea what it meant. The agency's liquid balance was thin — Diwali-season advances were already out to vendors for a three-day Marwari wedding (the agency's biggest job of the year). The demand could not come from anywhere without pain. 📊
🚨 The problem
The DRC-01A cited two issues: (1) Reverse Charge Mechanism (RCM) — Mehul had been claiming input tax credit (ITC) on purchases from unregistered vendors (banquet halls, caterers, mandap suppliers) who were not fully registered under GST. Under RCM rules, when a registered buyer purchases from an unregistered supplier, the buyer must pay GST directly to the government (not claim ITC). Mehul had it backwards. (2) GSTR-1 to ITR-3 mismatch — his GST outgoing invoices (GSTR-1, showing ₹X total service revenue at 18%) did not align with income declared in his IT Return (ITR-3). The automated cross-matching system flagged the gap as unexplained. The notice read like it was drafted for lawyers and assumed knowledge of RCM rules and ITR-3 reconciliation. Mehul understood neither. His CA quoted ₹15,000 to draft a response. The agency had no liquid cash for that.
🚀 How GabFORGE helped
Nainaben (Mehul's wife) suggested using an AI agent on the phone that their twelve-year-old had installed. Mehul typed in Gujarati-Hindi. The agent, over 15 minutes, broke down the DRC-01A into two clear pieces: (1) RCM issue is valid — he owed tax he didn't pay, (2) ITR-3 mismatch is a timing issue, partially reconcilable. The agent then asked:
- 🔍 Read the purchase register. Mehul called Ramubhai (office manager) and read out 30+ purchase entries. The agent cross-matched them against GSTR-2A (the government's auto-populated record of supplier filings). Found two GSTIN typos in the purchase register — the vendors were real, filed correctly, but the register had wrong digits worth ₹1.38 lakh.
- 💬 Separated the valid liability. RCM liability for unregistered vendors: ₹2.34 lakh (valid, payable). ITR-3 timing gap: ₹1.38 lakh (reconcilable). Original demand of ₹3.72 lakh broke down: ₹1.34 lakh avoidable through typo-correction, ₹2.34 lakh genuinely owed.
- 📞 Used Section 50. The agent advised voluntary payment of the RCM liability under Section 50 (Voluntary Payment), which reduces penalty on the legitimate gap. Mehul paid ₹2.34 lakh + ₹17.2K interest voluntarily, within the 30-day window.
✅ Outcome: Mehul filed a reconciliation (Annexure-A) with the typo corrections and the Section 50 voluntary-payment receipt. His CA charged ₹6,000 instead of ₹15,000 (the reconciliation was already done). Three weeks later, GST officer's revised order: ₹1.38 lakh portion dropped. Final liability ₹2.51 lakh (from ₹3.72 lakh). Diwali advance untouched. Agency remained operational.
🇮🇳 Why this matters
A DRC-01A reads like bureaucratic overreach when you do not understand RCM and ITR-3 rules. The default is panic and the CA fees. An agent that breaks down the notice into constituent issues, identifies which are valid (RCM) and which are timing gaps (ITR-3), and then shows reconciliation pathways (typo-correction, Section 50 voluntary payment) can reduce demand by ₹1.21 lakh without a lawyer.
The long version has Mehul sitting in his car after the CA call, Nainaben's suggestion to try the AI, the Ramubhai phone call reading vendor entries, the moment the GSTIN typos were discovered, and the principle that a DRC-01A is fixable if you read it carefully.