Table of Contents
A GST notice rarely arrives alone. For a large enterprise operating across multiple locations, notices can arrive at different times, from different tax jurisdictions, with separate response deadlines and varying amounts proposed or determined.
Tracking notices through spreadsheets and email threads may work at lower volumes, but the process becomes difficult to control as the number of matters grows. An AI-powered litigation management system can give tax teams a single, structured view of every notice, helping them capture what the notice means, prioritise the matter, and track the actions required before each deadline.
Why GST notice management becomes difficult at enterprise scale
A business with GST registrations across ten or fifteen states may need to manage matters across multiple tax jurisdictions, registrations, officers, and procedural timelines. Either the Central or the State authority can start proceedings, because Section 6 of the CGST Act, 2017 makes officers under one Act proper officers under the other. Notices on issues such as ITC mismatches, tax short payment, classification, or valuation can arise across several registrations. The form changes at each stage: an intimation in DRC-01A under Rule 142(1A), a scrutiny notice in ASMT-10 under Section 61, an audit notice in ADT-01 under Section 65, a show cause notice in DRC-01, an order in DRC-07, and then the appeal window. Nearly all of these are served on the common portal under Section 169, and a fair number are missed because they sit under the ‘Additional Notices and Orders’ tab rather than in the main notices list. As these matters accumulate, the number of live cases can quickly become difficult to manage through spreadsheets and email alone.
Manual tracking becomes difficult because it relies on teams consistently capturing every notice, recording the relevant dates and provisions, assigning ownership, and following up on each action. Not every slip costs the same. A late reply can usually still be repaired at the hearing, since Section 75(4) requires an opportunity of hearing where the taxpayer asks for one in writing or where an adverse order is proposed, and Section 75(5) allows up to three adjournments. A late appeal usually cannot be repaired. Section 107(1) gives three months from communication of the order, Section 107(4) allows one further month on sufficient cause, and that is the end of it: as a few courts have held that delay beyond the period the statute itself allows cannot be condoned. Litigation management therefore becomes a data and process challenge long before it becomes a question of legal strategy alone.
The information contained in notices and supporting documents
Every GST notice carries information that determines what happens next. This includes the applicable legal provision, the relevant tax period, the amount proposed or determined, the issue under dispute, and the response or hearing deadline specified in the notice. The provision also fixes the limitation clock. For FY 2023-24 and earlier, Section 73 gives the department three years from the due date for furnishing the annual return to pass the order, with the notice issued at least three months before that date, and Section 74 gives five years and six months where fraud, wilful misstatement or suppression of facts is alleged. From FY 2024-25, Section 74A replaces both. It was inserted by the Finance (No. 2) Act, 2024 with effect from 1 November 2024, and it allows forty-two months from the due date for furnishing the annual return to issue the notice and twelve months from the notice to pass the order, extendable by six months. Penalty still varies depending on whether fraud or suppression is established. Supporting documents, including statements of demand and annexures, provide further detail on the discrepancy identified by the department, whether it relates to ITC, valuation, classification, tax payment, or another issue.
This information is what a litigation management system needs to capture accurately at the point of intake. If the applicable provision, tax period, deadline, or amount proposed or determined is recorded incorrectly, every downstream decision, from prioritisation through response preparation, starts from a flawed base. Capturing these details consistently across registrations, jurisdictions, and matters creates the foundation for effective GST litigation management.
Limitation runs against the department too. A notice or order issued beyond the period allowed by Section 73, 74 or 74A can be challenged on that ground alone, and the challenge turns on dates the system already holds: the due date of the annual return for that registration and period, and the date of the notice. Comparing the two at the point of intake flags a possibly time-barred proceeding when the matter is first logged, instead of leaving it to be spotted years later in appeal.
How a litigation management system creates a central case view
When notice data is recorded consistently, a litigation management system can organise it into a single case view. Each matter becomes part of one case record that authorised team members can access without reconstructing the history from scattered emails and documents.
This central view becomes particularly important when a matter moves through multiple stages. A show cause notice can lead to a reply, personal hearing, adjudication order and subsequent appeal. Each stage will introduce new documents, actions, hearings and deadlines, which become harder to trace when the case history is spread out across spreadsheets, emails and individual team members. With this centralised view, a team member or legal counsel entering into a matter mid-case can see the entire sequence of events, arguments already made, documents submitted and actions still pending without starting from scratch.
The role of AI in classifying deadlines, values, issues, and risk
Once notices are captured in a central system, AI has a specific and practical role to play in transforming unstructured notice and supporting-document text into structured information that tax teams can act on. AI can draw key information (like the response or hearing deadline, disputed tax period, amount proposed or determined, and underlying issue) from the notice and its annexures. It can also work out the dates the notice does not state on its face, such as the outer limit for the adjudication order and the appeal window running from the date of communication.
It can also classify the matter based on indicators such as ITC, valuation, classification, tax payment, or other issues identified in the document. These classifications can then facilitate a risk-prioritisation workflow, subject to the approval of the tax team.
This is where AI-powered litigation management can add value over purely manual tracking: it can help ensure that matters are captured, classified, prioritised, and assigned consistently even as notice volumes increase.
How evidence, reviews, responses, and case history remain connected
GST matters rarely conclude with a single document. They can involve reconciliation statements, supporting invoices, vendor confirmations, internal review notes, formal responses, personal hearings, and subsequent orders or communications.
Keeping these records connected to the original notice makes the case easier to review and reuse later. A well-structured litigation management system can link evidence, internal review comments, filed responses, hearings, and orders to the specific case and issue they relate to. This becomes particularly valuable when a similar issue arises in another registration, jurisdiction, or financial year.
When a similar issue arises again, the team can refer to how the matter was handled previously, what evidence supported the position, and what outcome followed. Past cases can therefore become a working reference rather than simply a closed file.
Tracking the appellate stage, including the GST Appellate Tribunal
Deadline tracking does not end with the adjudication order. An appeal to the Appellate Authority under Section 107 has to be filed within three months of communication of the order, and the appellant has to pay the admitted liability in full plus ten per cent of the tax in dispute, capped at twenty crore rupees each under the CGST and SGST Acts after the amendment by the Finance (No. 2) Act, 2024. A further appeal to the Goods and Services Tax Appellate Tribunal under Section 112 needs another ten per cent of the remaining tax in dispute, subject to the same cap. For a group with matters spread across registrations, the total pre-deposit falling due in a quarter is a cash number the tax team is usually asked for at short notice, and it can only be assembled from case-level data.
The Tribunal becoming operational has also created a transitional deadline. Notification S.O. 4220(E) dated 17 September 2025, issued under Section 112(1), set 30 June 2026 for appeals against orders communicated before 1 April 2026, and Section 112(6) allows the Tribunal to admit an appeal within a further three months on sufficient cause. Working out which orders across the group fall inside that window is a case-level exercise, and a central repository answers it far quicker than a set of spreadsheets.
The impact of centralised litigation data on exposure and decision-making
When notice data, case history, and outcomes are consolidated in one system, tax leadership gains a view of total litigation exposure that is difficult to obtain from individual case records. This can include the amounts proposed or determined, disputed exposure, recurring issue types, registrations or jurisdictions generating the most matters, procedural stages, and outcome trends over time.
This view changes decision-making in a practical way. It helps tax leadership identify matters that require senior review, spot recurring issues that may indicate an upstream process weakness, and understand where disputed tax exposure is concentrated. It can also support decisions around provisioning, resource allocation, remediation priorities, and litigation strategy, subject to the business’s accounting and legal assessment. It is also where litigation data feeds the provisions and contingent liability disclosures under the requirements of the relevant Ind AS, since whether a matter is probable, possible or remote is judged on the same case-level facts the system already holds.
Centralised litigation data turns tax litigation management from a reactive, notice-by-notice process into a measurable business function that can inform compliance priorities, resource allocation, risk management, and future decision-making.