A DRC-01 summary should never be answered with one generic paragraph. Each allegation needs a factual response, legal position, calculation and supporting document.
Quick View
Convert the notice and annexures into an issue matrix, then file a complete DRC-06 response within the stated time.
Download the complete notice and DIN.
Notice, DRC-01 and annexures.
Replying only to the summary.
Why It Matters
DRC-01 is the electronic summary of a show-cause notice under Rule 142. The complete notice, relied-upon documents and computation must be read together.
A reply should distinguish admitted differences, timing differences, legal disputes and factual errors. Voluntary payment or reversal should be mapped separately and should not silently concede unrelated allegations.
Where personal hearing is requested, preserve the request, hearing notice, written submissions and order sheet.
Control Framework
| Area | What to establish | Operating rule |
|---|---|---|
| Notice scope | Section, period, tax head and amount. | Read annexures, not summary alone. |
| Reconciliation | Books, GSTR-1, GSTR-3B, 2B and ledgers. | Explain every difference. |
| Evidence | Invoice, receipt, movement and payment. | Index annexure-wise. |
| Procedure | DRC-06, hearing and acknowledgement. | Control deadlines. |
Action Checklist
- Download the complete notice and DIN.
- Prepare allegation-wise matrix.
- Reconcile tax, interest and penalty.
- Draft factual and legal responses separately.
- Upload indexed evidence in DRC-06.
- Preserve ARN and hearing records.
Practical Example
Evidence to Keep
- Notice, DRC-01 and annexures.
- Return and ledger reconciliation.
- Invoice and receipt evidence.
- Interest and payment working.
- DRC-06 acknowledgement.
- Hearing submissions and order.
Warning Signs
- Replying only to the summary.
- Ignoring relied-upon documents.
- Uploading unreadable bulk files.
- Paying without issue-wise mapping.
- Missing the hearing request.
Detailed Review
GST control should connect five records: commercial contract, tax invoice, movement or service evidence, accounting entry and portal return. A filing that cannot be traced back to all five records is difficult to defend.
Every reconciliation should have a clear opening balance, current-period additions, corrections, reversals, payments and closing balance. Avoid unexplained plugs that make the total match but do not identify the invoice or legal reason.
Portal data is important but not conclusive by itself. GSTR-2B, e-invoice, e-way bill and ledger data should be read with the statute, rules, notifications, contracts and actual supply evidence.
Keep original source files and final filed versions. Screenshots help explain a portal event but should not replace downloaded returns, JSON, signed invoices, acknowledgements or bank records.
For material exposure, prepare a written position memo stating facts, issue, law, alternatives, conclusion, amount and approval. The memo should record uncertainty rather than hide it.
The litigation file should contain the notice, relied-upon documents, reply, evidence index, hearing request, hearing record and order in chronological order. Missing procedural records can be as important as the tax computation.
Separate admitted liability from disputed liability. Payment of one issue should be expressly linked so it is not misunderstood as acceptance of every allegation.
Escalation Route
Start with the GST portal record, responsible business owner and tax working. Where the issue is operational, correct the source system and retain the acknowledgement. Where it is legal or disputed, obtain a reasoned professional position before payment, reply, refund or appeal.
Track the statutory or portal deadline separately from internal approval. Preserve helpdesk tickets, ARN, hearing requests, orders and payment records so a later reviewer can reproduce the entire path.
Transaction Test
Before filing or replying, prepare a one-page issue sheet showing GSTIN, tax period, transaction type, amount, applicable provision, portal form, evidence owner and due date. This prevents different teams from solving different versions of the same problem.
Reconcile tax by CGST, SGST, IGST and cess rather than only by total. A total can match even when the wrong tax head, state or period has been used, which can still create interest, cash-flow and customer-credit consequences.
Build an exception register with five statuses: identified, evidence pending, vendor or customer action, tax treatment approved and closed. Every exception should retain its original amount even after correction so the audit trail remains visible.
Test the position against the counterparty’s records. Customer ITC, vendor GSTR-1, transporter data, marketplace statements and bank receipts can expose differences that are invisible in the taxpayer’s own ledger.
The final approval should record who reviewed the legal position and who approved the return, reply, payment, refund or appeal. Material GST decisions should not remain buried in informal email chains.
Create a chronology beginning with the transaction and ending with the current proceeding. Include every notice, adjournment, hearing, payment, submission and portal acknowledgement.
For each ground, cite the supporting annexure number and the exact page or row. Authorities should not have to search a large unindexed attachment to find the evidence.
Common Questions
Is DRC-01 the full notice?
It is the electronic summary; the complete show-cause notice and annexures must also be reviewed.
Which form is used for reply?
The taxpayer generally responds through FORM GST DRC-06.
Should every difference be paid?
No. First identify admitted, timing and disputed items.
Can additional evidence be filed later?
Procedure depends on the stage; submit a complete file early and preserve any supplementary acknowledgement.
Official Sources
Use the latest Act, Rules, notifications, circulars, portal advisories and transaction documents. GST outcomes depend on facts, dates and the law applicable to the period.