Monitor status: index,follow. This page defines the review method; individual changes are published only after source authentication.
| 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.