| Field | Controlled entry |
|---|---|
| Date | 22 May 2026 |
| System | E-Way Bill |
| Legal anchor | CGST Rules 138-138E and current API schema |
| Official source | docs.ewaybillgst.gov.in |
Operational effect
The E-Way Bill API release notes make Ship-To GSTIN mandatory in Bill-To Ship-To transactions and state that three different parties should be involved; otherwise the transaction should be treated as a regular transaction.
Implementation controls
- Classify Bill-To and Ship-To parties before JSON generation.
- Reconcile invoice, e-invoice and e-way bill party fields.
- Update ERP validations and API schema.
- Retain dispatch, delivery and contractual 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.