Direct answer: Record the response deadline immediately, verify the notice on the GST portal, identify the exact period and allegation, freeze the relevant records, and appoint one coordinator. Do not let different teams send partial or inconsistent explanations.
The first working-day checklist
- Save the complete notice, reference number, attachments and portal history.
- Confirm the date of service and the statutory or stated response deadline.
- Identify tax period, registration, issue, amount and legal provision mentioned.
- Separate facts that are agreed, facts needing reconciliation and positions that require legal interpretation.
- Decide whether an extension, personal hearing or immediate protective response should be considered.
Build the evidence file
Bring together filed returns, electronic ledgers, invoices, e-way bills where relevant, contracts, payment records, supplier or customer confirmations, reconciliations and prior correspondence. Create one issue-wise index. A clear evidence trail helps the reviewer see what supports each factual statement and prevents the response from becoming a large unstructured document dump.
Common failure points
- The finance team treats a portal mismatch as only a software issue.
- A response explains the business story but does not reconcile the amount.
- Supporting documents use inconsistent names, periods or totals.
- Teams submit separate replies without one approved position.
- The business waits until the deadline to involve a professional.
What a strong response should do
It should identify the notice precisely, state the relevant facts, respond issue by issue, connect each statement to evidence, distinguish factual reconciliation from legal submissions, and request the appropriate conclusion or opportunity. The language should be calm and exact. Avoid unsupported admissions and avoid claims that the records cannot demonstrate.