A notice response should answer the department’s allegation, not merely upload the company’s entire archive.
GST owner with legal review
Per notice, tracked weekly
Create a notice chronology.
Notice and portal history.
Identify the document type, tax period, authority, section, allegations, amount and deadline. A portal communication, intimation, show-cause notice and order have different legal consequences.
Build an issue matrix: department figure, company figure, difference, explanation, evidence and legal position. Reconcile GSTR-1, GSTR-3B, GSTR-2B, e-invoices, e-way bills, books and financial statements only to the extent relevant.
Place decisive evidence on record before the order. An appeal is not a safe substitute for a weak first response, and later admission of evidence can face procedural restrictions.
| Control | What it covers | Operating rule |
|---|---|---|
| Notice identification | Type, section, period and deadline are recorded. | Download the complete notice. |
| Issue matrix | Every allegation and amount is mapped. | Avoid narrative-only replies. |
| Evidence file | Returns, invoices, contracts and ledgers are indexed. | Use numbered annexures. |
| Submission | Response and attachments are filed on the correct portal route. | Save acknowledgement. |
Use an adjournment or extension route only when available and genuinely needed. Continue preparing the response until an extension is formally granted.
Track the next stage after filing. A reply acknowledgement does not close the proceeding; monitor hearing, additional query and order.
Document the decision, owner, due date and evidence expected. A verbal explanation should be converted into a board note, approved working, contract amendment, portal acknowledgement or reconciliation before the item is treated as closed.
Rules, forms, thresholds and interpretations can change. The operating team should use the latest official source and the actual company facts instead of copying a control from another entity or prior year.
Ask four questions: Is the obligation or accounting treatment applicable? Has the underlying transaction been completely recorded? Does the evidence agree with the books and portal? Has an independent reviewer challenged the exception?
The review should distinguish a timing difference from an error, a judgement from a missing document, and a control failure from a one-time operational delay. Repeated small exceptions deserve root-cause action because they often become material during audit, fundraising, notice or distress.
The operating record should connect the control stages—notice identification, issue matrix, evidence file, submission—to the same transaction population. If the source list, accounting ledger, tax return, board record and management dashboard use different populations, the review can appear complete while exceptions remain outside the test.
Management should define an exception threshold, but the threshold must not hide repeated failures. A small error occurring every month can signal weak master data, unclear ownership or a broken interface. The reviewer should record root cause, immediate correction and preventive action separately.
Closure requires evidence. At minimum, the file should show who prepared the work, who reviewed it, which source documents were used, what differences remained and when the next follow-up is due. Screenshots without context or spreadsheets without source references are not a durable control record.
Tag every working with the legal entity, tax period and governing law. The filing date alone does not decide which Act, rate, form or limitation period applies, especially during the 2026 income-tax transition or where a notice covers earlier GST periods.
Portal data should be downloaded and preserved with the filing version. Later supplier corrections, updated statements or portal changes can otherwise make it difficult to prove what information management used when the return or response was approved.