Identify a GST notice by reading its actual form, issuing authority, legal provision, tax period and requested action. Save the complete document and attachments before deciding how to respond. An email subject line or portal alert can help locate the communication, but it does not replace the notice itself.
Locate the complete communication
Sign in through the official GST portal and open the relevant notice or case details. GSTN’s current manual says the former Additional Notices/Orders section has been merged into Notices and Orders. Use the issuance-period and other available filters when an item is not visible in the initial list.
Download the notice, annexures, working sheets and any related order. Preserve the original filenames in an archive while giving working copies clear names. A summary page showing an amount may omit the transaction schedule needed to understand the allegation.
Check whether the communication also arrived by another service channel. Record those facts without assuming that the day someone forwarded it internally is the legally relevant service date.
Identify the stage before the amount
A discrepancy intimation, show-cause notice and demand order are different stages. The response route and available next steps depend on the actual document and governing provision.
For example, ASMT-10 concerns return scrutiny. DRC-01 is a summary associated with a show-cause notice, while DRC-07 is a summary of an order. A registration-cancellation show-cause notice in REG-17 raises another kind of issue altogether.
Read the accompanying substantive notice or order, not merely the form label. If an attachment is missing or unreadable, record that problem and seek the complete material through the appropriate channel while protecting the response deadline.
Build a reference register
| Field | What to capture | Why it matters |
|---|---|---|
| Taxpayer | Legal name and GSTIN | Confirms the affected registration |
| Authority | Office and officer designation | Identifies who issued the communication |
| Document | Form, date and exact reference | Connects every later submission |
| Period | Months and financial year | Defines the records to retrieve |
| Action | Reply, hearing, payment or another step | Directs the immediate workflow |
| Timing | Stated due date and service evidence | Supports deadline review |
Keep RFN, case ID, order number and application ARN in separate columns where they exist. They can identify related records, but they are not interchangeable. A later reply ARN should not overwrite the original notice reference.
Verify the identifier appropriately
CBIC Circular 249/06/2025 clarifies that communications generated through the GST common portal with a verifiable RFN do not require a separate DIN. Do not dismiss such a document simply because a DIN is absent.
Record any DIN or eOffice issue number appearing on other communications and verify through the appropriate official route for that issuing system. Central and State communications may involve different administrative instructions, so avoid applying one identifier rule indiscriminately.
Open official verification services independently instead of following an unexpected payment link. Verification should establish the document details, not require sharing a portal password or OTP with a caller.
An illustrative identification exercise
A Nagpur distributor receives an alert mentioning ₹92,000. The attached working shows ₹72,000 tax, ₹14,400 interest and ₹5,600 penalty, totalling ₹92,000. The subject line alone says only “GST demand.”
The accounts team should record the actual stage and provision before treating ₹92,000 as an admitted payable. It should also preserve the three components separately so an explanation of tax does not accidentally ignore interest or penalty allegations.
Suppose the GSTIN belongs to the distributor’s Maharashtra registration, while the email was forwarded to its Madhya Pradesh branch accountant. The correct file belongs to the Maharashtra registration. Company-wide branding does not justify responding under another GSTIN.
These amounts and circumstances are illustrative; they do not imply that a particular penalty or interest rate applies.
Read every allegation into an issue list
Create one row for each discrepancy, with the notice paragraph, amount, period and documents requested. Separate a sales mismatch from an input-credit query even if both appear in one notice.
Mark items as understood, requiring clarification or requiring additional data. Do not label everything “clerical” before the underlying transactions have been checked. A reference register describes the case; it does not establish the defence.
Where the provision depends on the relevant financial year, have the adviser confirm that legal framework. Avoid using an old notice template as proof that the same demand provisions apply to every later year.
Assign immediate responsibility
Name one internal coordinator, one person responsible for obtaining records and the authorised signatory or representative handling the response. Add a backup contact so a leave period does not stop action.
Record the next action and internal target immediately. Even a notice believed to contain an error should remain on the calendar until the proper response or other action has been completed.
Recent Council recommendations or press reports should not be treated as an automatic reason to ignore a small notice. Any claimed change needs its implementing law, notification and effective date checked against the case.
Preserve the chain after identification
Save the filed reply, attachments, acknowledgement and later communications against the same original reference. Record a new order as a linked document rather than replacing the earlier notice.
A notice has been properly identified when the business knows which registration, issue, period, authority and next action it concerns. That precise starting record makes every later reconciliation and submission easier to control.