| Field | Controlled position |
|---|---|
| Category | GSTAT |
| Legal anchor | GSTAT Procedure Rules |
| Official operating source | www.efiling.gstat.gov.in |
Finin2min summary
Identify the application category, jurisdiction and supporting evidence.
End-to-end workflow
- Identify taxpayer type, GSTIN, tax period, form or transaction and responsible owner.
- Open the current Act, Rule, notification or procedure that creates the obligation.
- Download portal data and reconcile it to books, source documents and external systems.
- Resolve exceptions with documented reasons; do not overwrite source data without an audit trail.
- Prepare maker-checker review, authorised-signatory approval and payment or pre-deposit.
- File or generate the document through the correct portal/API version.
- Save acknowledgement, JSON/PDF, ledgers, screenshots and system logs.
- Monitor later portal processing, defects, notices, recipient impact and supersession.
Evidence file
- Act/Rule/notification and current manual
- Books-to-portal reconciliation
- Source invoices and supporting documents
- Maker-checker sign-off
- Filed JSON/PDF and acknowledgement
- Payment, ledger or IRN/EWB evidence
- Exception and helpdesk log
Failure points
- Using portal data as a substitute for legal eligibility
- Missing effective date or taxpayer class
- Relying on stale API fields or validation checks
- Ignoring recipient, transporter or customs impact
- Failure to preserve evidence before a portal screen changes
Practical example
A taxpayer completes the underlying legal test first, reconciles its ERP and books to portal-populated information, investigates differences, files after approval and retains a complete digital evidence pack for audit and litigation.
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.
Finin2min practical control layer
Law vs system
This GSTAT procedure route must be reconciled to the Act, Rules and notified forms. Portal behaviour or an advisory can explain implementation but cannot override a statutory provision or Gazette instrument.
Evidence pack
Retain source records relevant to the step: acknowledgement/reference number, submitted JSON/PDF, ledgers, invoice/e-invoice/e-way-bill records, notices/orders, screenshots only where needed, and system/error tickets.
Reconciliation
Cross-check the portal result with books/ERP, return period, GSTIN, document identifiers, tax head, tax amount and downstream return/ledger effect.
Exception workflow
- Identify the legal deadline or condition independently of the portal display.
- Reconcile master data and transaction values before submission.
- Save acknowledgement and the exact filed/generated artefact.
- Investigate any mismatch, rejected record, blocked action or missing auto-population; do not overwrite the audit trail.
- Escalate through the official grievance/help route where the system prevents a legally required action and preserve evidence of the attempt.
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