| Field | Control |
|---|---|
| Source class | Tribunal filing |
| Official source | www.efiling.gstat.gov.in |
| Frequency | Daily during filing windows |
| Scope | Filing, fees, tokens, defects and help |
Monitoring procedure
- Check the official source at the assigned frequency.
- Compare title, number, date, attachment and effective clause to the prior snapshot.
- Archive the PDF or page, URL, timestamp and SHA-256 hash.
- Map affected sections, Rules, forms, rates, workflows and website pages.
- Prepare a legal and operational redline.
- Apply reviewer sign-off and update publication dates.
- Track withdrawal, corrigendum, litigation and implementation.
Escalation triggers
- Changed due date or limitation
- New mandatory field or validation
- Rate, exemption or RCM change
- System outage near statutory deadline
- Portal behaviour inconsistent with law
- Security or authentication change
Finin2min Q&A
Can a portal advisory amend the GST Act or Rules?
No. It explains system operation. The Act, Rules, valid notification and binding judgments prevail.
What evidence should be saved?
Official page or PDF, URL, date, access timestamp, hash, screenshots, filing acknowledgements, error logs and helpdesk tickets.
What if the portal and law appear inconsistent?
Preserve evidence, escalate promptly and protect the legal deadline through the available statutory or judicial route.
When can an operational page be indexed?
Only after its source, date, current status, legal anchor, implementation steps and supersession position are reviewed.
Source and review trail
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.
- Official starting point
- www.gstcouncil.gov.in
What this monitor must verify
Download the controlling Procedure Rules
| Change surface | Verification test | Dependent pages |
|---|---|---|
| Filing window | Capture the notification/order number, issue date, covered orders and operative deadline. | Section 112 guide, APL-05/APL-07 and limitation tools. |
| Portal release | Record the form, taxpayer class, mandatory fields, payment path and known validation limits. | Forms hub, defect workflow and user instructions. |
| Procedure rule | Compare Gazette text, commencement, amendment or corrigendum and affected rule/form. | All hearing, application, service and evidence pages. |
| Bench/registry direction | Identify issuing authority, bench coverage, effective date and whether it is case-specific. | Jurisdiction, cause-list and filing guidance. |
Release-control workflow
- Capture
Archive the official page/PDF, URL, timestamp and hash. - Compare
Redline against the last authenticated source, including annexures and forms. - Map
List every affected route, deadline, field and evidence instruction. - Publish
Apply legal review, link testing and supersession notes before changing guidance.
Escalation example
The portal blocks an attachment that the Procedure Rules require. Preserve the error, file size/type, timestamp and helpdesk ticket; do not rewrite the legal requirement to match the screen. Protect the deadline through the available official route and record the response.
Current source boundary
The official GSTAT website publishes the institutional and procedure layer, while the e-filing portal carries transaction controls. A blog, search snippet or cached portal page is discovery evidence only until matched to the official release.
Official sources: GSTAT | GSTAT e-filing | Finin2min GSTAT hub.
A monitoring page records the verification method; it does not itself extend a deadline or amend a statutory form.