| Field | Controlled entry |
|---|---|
| Date | From September 2025 return period |
| System | GST Portal |
| Legal anchor | GSTR-7/GSTR-8 credit-received portal implementation |
| Official source | tutorial.gst.gov.in |
Operational effect
The portal includes invoice-level TDS fields and requires accept/reject action followed by Generate Summary before filing the TDS/TCS credit-received statement.
Implementation controls
- Match deductor or operator records to invoices.
- Accept or reject every item.
- Generate summary before filing.
- Reconcile accepted amounts to the electronic cash ledger.
Evidence checklist
- Official advisory or release page
- Publication and effective dates
- Related notification or Rule
- Portal/API screenshot or response
- ERP change ticket and testing evidence
- Supersession and later-update check
Practical example
A finance team identifies the change, verifies its legal anchor, updates the ERP or filing SOP, tests the change in a controlled environment and archives the official source before the next transaction or return cycle.
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.