| Field | Controlled entry |
|---|---|
| Date | 1 June 2025 |
| System | E-Invoice |
| Legal anchor | GSTN IRP validation advisory |
| Official source | einvoice6.gst.gov.in |
Operational effect
IRP systems treat document numbers as case-insensitive and convert them to uppercase for duplicate detection and IRN generation.
Implementation controls
- Normalise invoice numbers in ERP before IRN calls.
- Prevent ABC101 and abc101 from being issued as separate documents.
- Reconcile IRP response with books and GSTR-1.
- Test credit/debit note numbering separately.
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.