| Field | Controlled entry |
|---|---|
| Date | 1 February 2026 |
| System | E-Invoice |
| Legal anchor | Notification 20/2025-Central Tax and IRP production validation |
| Official source | einvoice6.gst.gov.in |
Operational effect
IRIS IRP records relaxation of selected item-value and tax mismatch validations for notified RSP-based invoices from 1 February 2026. This is an operational validation change tied to the notification.
Implementation controls
- Confirm the notified HSN and RSP computation.
- Update API, web form, utility and JSON validation tests.
- Do not treat suppressed error codes as a tax-law exemption.
- Retain IRN, signed JSON, QR code and classification evidence.
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.