India's indirect tax infrastructure has underwent a massive structural evolution, transitioning from manual books scrutiny by jurisdictional tax officers to automated surveillance driven by real-time data triangulation on the GST portal. Today, the digital tax network can instantly reconcile what a business declared in one compliance return against what was actually paid in another, raising flags on mismatches without any human intervention.
One of the most critical automated enforcement checkpoints introduced recently is Form DRC-01B. This automated tool was established specifically to monitor and flag major discrepancies between the outward tax liability declared in GSTR-1 (or through the Invoice Furnishing Facility) and the actual tax paid during the filing of GSTR-3B. When the portal detects that your reported sales liability significantly outpaces your monthly tax payment, it does not wait for a manual audit. Instead, it triggers an immediate system-generated intimation under Rule 88C of the CGST Rules, 2017, demanding a formal explanation or differential payment within seven days.
For any operating business, understanding this mechanism is vital because failing to respond to a DRC-01B notice has severe operational impacts. Your subsequent GSTR-1 or IFF filing is automatically blocked by the system, bringing your ability to pass on Input Tax Credit (ITC) to your direct business clients to a complete standstill. In extreme cases of non-compliance, the unresolved amount is categorized as self-assessed tax, allowing recovery officers to bypass standard adjudication hearings and launch direct recovery actions under Section 79.
What is Form DRC-01B in the GST Regime?
Form DRC-01B is an automated, system-generated compliance notice issued under Rule 88C of the CGST Rules, 2017. It officially notifies a registered business that their tax liability declared in GSTR-1 (or IFF) exceeds the actual tax discharged in GSTR-3B for that specific tax period by an amount that surpasses the configured threshold limits.
To understand this simply, if you inform the tax network via GSTR-1 that you collected and owe ₹10 lakh in tax on your outward sales, but only deposit ₹7 lakh while filing your GSTR-3B, the core engine detects a ₹3 lakh deficit. This automatically triggers the generation and delivery of a DRC-01B notice to your digital ledger.
The standard operating lifecycle of this form is structured as follows:
- The Automated Trigger: The GST portal continuously compares the absolute liability figures from GSTR-1/IFF against GSTR-3B payments for every tax period.
- System-Defined Thresholds: The notice does not fire for minor rounding off errors. It is designed to trigger only when the discrepancy exceeds both a specific percentage and absolute monetary threshold set confidentially by the GST Council.
- Dual Structure: The form is split into two sections. Part A is the system-populated intimation that highlights the exact calculated discrepancy broken down by specific tax heads, namely IGST, CGST, SGST, and Cess. Part B is the taxpayer's designated response area, where they must submit either payment details or a structural explanation.
- Strict Seven-Day Deadline: Taxpayers must file their response in Part B within exactly 7 days of receiving the notice via email or registered phone alerts.
- The Core Blocking Consequence: Failure to submit Part B within the stipulated 7 days leads to the automatic system blocking of the subsequent GSTR-1/IFF.
Why Do Taxpayers Receive a DRC-01B Intimation?
While the mathematical trigger is simple, the underlying reasons for such mismatches are highly diverse and frequently stem from genuine clerical errors or timing issues rather than deliberate tax evasion. Understanding these common real-world compliance scenarios is essential to preventing them:
A frequent error is forgetting invoices in GSTR-3B. A business might upload all sales invoices in GSTR-1 to help buyers claim their ITC, but during GSTR-3B filing, they may accidentally leave out the tax liability of a few invoices. Timing differences also play a huge role. For instance, an invoice is declared in the GSTR-1 of Month 1 (e.g., October), but the actual tax is paid in the GSTR-3B of Month 2 (e.g., November). The portal will immediately flag the deficit for Month 1 and send an automated notice.
Typographical or clerical errors are another major driver. A simple extra zero during data entry, such as typing ₹5,00,000 instead of ₹50,000 as the taxable value in GSTR-1, artificially inflates the declared liability, leading to a massive mismatch. Similarly, mismatches can occur when credit notes are adjusted to reduce GSTR-3B liability but are not reported in GSTR-1, or when a transaction is amended from B2C to B2B without aligning the corresponding GSTR-3B figures. Prior period excess adjustments, where excess tax paid in earlier periods is adjusted against the current GSTR-3B liability, also trigger the system since the GSTR-1 for the current month continues to reflect the full gross liability.
The Genesis and Role of Rule 88C
Rule 88C was introduced into the CGST Rules in December 2022 to counter a prevalent practice where taxpayers would upload massive sales details in GSTR-1 to allow their buyers to immediately claim ITC via GSTR-2B, while delaying or entirely avoiding the payment of the corresponding tax in GSTR-3B. This created significant cash leaks for the exchequer. By empowering the portal to auto-detect these gaps, Rule 88C removed the need for manual officer review, shifting the compliance burden directly onto the taxpayer to either clear the dues or justify the discrepancy within a strict time limit.
The Mystery of Configurable Thresholds
The GST portal does not trigger a DRC-01B notice for every minor discrepancy. The GST Council has configured specific percentage and absolute value limits to prevent notices from being sent for nominal differences or rounding-off errors. These thresholds are deliberately kept confidential by the system administrators to prevent taxpayers from intentionally managing their filings to stay just below the radar. While similar parameters in DRC-01C have been discussed around a 20% and ₹25 lakh deviation limit, the DRC-01B limits are managed independently. Consequently, businesses must rely on monthly data reconciliations rather than counting on these hidden thresholds as a safety buffer.
How to File a Reply in Form DRC-01B Part B
Filing a comprehensive reply in Part B of the form is the only way to resolve the notice and unblock your GSTR-1 filing options. Taxpayers have two pathways to choose from: they can either pay the calculated tax deficit (Option A) or submit a formal explanation justifying the mismatch (Option B).
Step 1: Locate the Notice on the Portal
First, log in to the official GST Portal using your registered corporate credentials. Go to Services, click on Returns, and select Return Compliance. From there, select the Liability Mismatch (DRC-01B) tile. You can search for your specific notice using the reference number received in your email/SMS alerts or search by selecting the relevant tax return period and setting the status to pending. Clicking on the active notice will display the Part A details showing the head-wise tax differences.
Step 2: Pay the Differential Tax (Option A)
If your internal audit reveals that the mismatch is valid and that there was indeed an underpayment in GSTR-3B, the appropriate resolution is to pay the tax along with interest. Under Section 50 of the CGST Act, interest is levied at 18% per annum for the period of delay.
To execute this, pay the differential tax using Form DRC-03. While filling the DRC-03 on the portal, select "Liability Mismatch - GSTR-1 to GSTR-3B" as the cause of payment and ensure you enter the correct tax period. Once you complete the payment and file the DRC-03, return to the DRC-01B Part B page. Select the option "Paid the differential tax" and enter the Acknowledgement Reference Number (ARN) of your DRC-03 payment. The system will run a validation check to confirm the ARN matches the correct tax period and cause. If there is a mismatch, the portal will display an error.
For context on interest calculations, if a tax amount of ₹1,00,000 was due on November 20th but was actually settled on December 15th, interest at 18% per annum is payable for the 25 days of delay. The interest is calculated as: ₹1,00,000 × 18% × (25 / 365) = approximately ₹1,233.
Step 3: Provide a Detailed Explanation (Option B)
If the mismatch is not a result of actual unpaid tax but was caused by a reporting error, a timing discrepancy, or prior adjustments, you can choose to submit an explanation.
In Part B, select the option "Difference in liability is due to". You will be presented with a dropdown list of pre-defined compliance reasons. These reasons include options such as "Excess liability paid in earlier period" or "Form GSTR-1 filed with incorrect details". If none of the standard reasons apply, select "Any other reason" and write a precise narrative in the text box, which is limited to 500 characters. For example: "Invoice INV-2024-0456 dated 15-Oct-24 for ₹2,50,000 was declared in Oct-24 GSTR-1, but the tax was paid in Nov-24 GSTR-3B due to a delay in payment confirmation. There is no tax loss to the exchequer."
Please note that the DRC-01B portal interface currently does not support direct document uploads. Because of this restriction, you should keep all your reconciliation workpapers, ledger files, and other supporting evidence ready. If a tax officer reviews your response and demands documentation, you can share it via the "Communication with Taxpayer" tab or through official letters. Additionally, once Part B is filed, it cannot be edited or revised. You must double-check all information before clicking the submit button.
Consequences of Ignoring a DRC-01B Notice
Ignoring a DRC-01B notice can lead to immediate operational disruptions and severe legal actions, as the system is fully automated to enforce compliance.
Subsequent GSTR-1 and IFF Blocking
The most immediate operational impact of ignoring a DRC-01B notice is the automated blocking of your GSTR-1/IFF filing capability for the next tax period. Rule 59(6) of the CGST Rules has been amended to specify that if a taxpayer does not file Part B of DRC-01B within 7 days, the portal will prevent them from uploading their next sales return. This blocking disrupts your supply chain as your corporate buyers will not see their eligible ITC in their GSTR-2B, which can damage your commercial relationships and lead to withheld payments.
Direct Recovery Actions Under Section 79
Beyond portal restrictions, if a DRC-01B notice remains unresolved, the tax department can categorize the disputed amount as "self-assessed tax" that has been declared but not paid. This classification allows tax officers to directly initiate recovery proceedings under Section 79. This provision allows the department to attach your bank accounts, seize physical assets, or demand payment from third parties who owe you money. Because this is classified as self-assessed tax, the department can bypass the lengthy process of issuing a Show Cause Notice and holding formal hearings under Sections 73 or 74, moving directly to recovery.
Comparing Form DRC-01B and Form DRC-01C
Although both DRC-01B and DRC-01C are automated notices generated by the GST portal, they address entirely different compliance mismatches. Understanding their distinct functions is essential to managing your tax filings correctly.
The key differences between the two forms are outlined below:
- Basis of Mismatch: Form DRC-01B monitors and flags differences in output tax liability, whereas Form DRC-01C focuses on mismatches in Input Tax Credit (ITC).
- Returns Compared: DRC-01B compares GSTR-1/IFF details against GSTR-3B payments. Conversely, DRC-01C compares GSTR-2B/2A data against the ITC claimed in GSTR-3B.
- Trigger Condition: DRC-01B is triggered when GSTR-1 liability is higher than GSTR-3B payments. DRC-01C is triggered when the ITC claimed in GSTR-3B is higher than the ITC available in GSTR-2B.
- Legal Provision: DRC-01B is governed by Rule 88C, while DRC-01C is governed by Rule 88D.
- Shared Characteristics: Both forms require a response within exactly 7 days, feature a two-part structure (Part A for system details and Part B for the reply), and result in the automatic blocking of your GSTR-1/IFF if ignored.
Simplifying GST Compliance with Razorpay GST Prime
Reconciling GSTR-1 and GSTR-3B manually using spreadsheets is a tedious and error-prone process. A single data entry error, a misplaced decimal point, or a missed invoice can trigger an automated DRC-01B notice, causing business disruptions that are disproportionate to the mistake.
Razorpay GST Prime is designed to mitigate these compliance risks by offering a comprehensive tool for both pre-filing prevention and post-filing resolution:
- Pre-Filing Auto-Reconciliation: The platform automatically compares your GSTR-1 and GSTR-3B data before you file, highlighting any discrepancies by tax head (IGST, CGST, SGST, Cess) so you can fix errors before submitting your returns.
- Real-Time Exception Alerts: It provides instant notifications for unusual variances, timing differences, or missing invoices, allowing your finance team to address discrepancies proactively.
- Unified Compliance Dashboard: The platform offers a single interface where you can track tax payments, download detailed reconciliation reports, monitor filing statuses, and keep track of any pending intimations.
- Seamless Tax Payments: If you need to make a differential tax payment to resolve a mismatch, the platform lets you generate challans and complete DRC-03 payments easily without needing to switch between different portals.
Conclusion
Form DRC-01B is a key element of the automated GST compliance system, where data accuracy is critical and discrepancies are flagged in real time. The system operates on objective data matching and requires immediate attention when a mismatch is detected. Promptly responding to a DRC-01B notice within the 7-day window—whether by making a payment via DRC-03 or submitting a valid explanation in Part B—is essential to keep your GSTR-1 active and maintain smooth business operations. Conducting regular monthly reconciliations of your sales and payment data remains your best defense against receiving these automated notices.
