Ship-to GSTIN Mandatory in e-Invoice & e-Way Bill APIs from 1 August 2026
From 1 August 2026, the GSTN makes Ship-to GSTIN a mandatory field in e-Invoice and e-Way Bill APIs wherever ship-to details are present. Unregistered parties must be marked as 'URP'. Businesses must update their ERP and e-invoicing software before the deadline to avoid IRN generation failures.
CA Harun Raaj
Chartered Accountant · Harun Raaj & Associates
Legal basis: Rule 48(4) and Rule 138, CGST Rules, 2017 — Effective: 1 August 2026. Source: GSTN advisories dated 9 June 2026, 17 June 2026, and 20 June 2026 (https://www.gst.gov.in/newsandupdates). Last reviewed by CA Harun Raaj: December 2024.
From 1 August 2026, the GSTN is making a mandatory change to the e-Invoice (IRP) and e-Way Bill APIs: wherever a document contains Ship-to details, the Ship-to GSTIN) field becomes mandatory in the IRN-generation and e-Way Bill API payloads. If your ERP or e-invoicing software has not been updated by then, invoice reference number (IRN) and e-way bill generation for Bill-to/Ship-to transactions will fail — and a failed IRN means you cannot issue a valid tax invoice.
This is a technical/portal change, not a change in GST law — but its operational impact is substantial because it sits at the exact point where invoices are issued.
What is changing
Per the GSTN advisory dated 17 June 2026 (read with the advisory dated 20 June 2026):
- Ship-to GSTIN is now mandatory when Ship-to details are present. In a Bill-to/Ship-to transaction (where goods are delivered to a party different from the buyer), the Ship-to GSTIN must be populated in all IRN and e-Way Bill API payloads.
- Unregistered ship-to party? Enter "URP" (Unregistered Person) in place of the GSTIN. The field cannot remain blank.
- New voluntary "E-Way Bill Closure" feature. You can now close an active e-way bill before its validity expires, once the consignment reaches its destination — a housekeeping convenience that reduces open or expired e-way bills on the portal.
When it takes effect — and why the date moved
These changes were originally scheduled for 15 June 2026. Following industry representations on ERP and GSP readiness, the GSTN deferred the go-live to 1 August 2026 (advisory dated 9 June 2026). Treat 1 August 2026 as firm and plan integration testing well ahead of the deadline.
Who is affected
Key point: Any taxpayer generating e-invoices or e-way bills for transactions with a ship-to party different from the buyer must ensure their software captures and transmits the Ship-to GSTIN (or 'URP' for unregistered parties) by 1 August 2026 to avoid IRN generation failure.
The 3-step action plan before 1 August 2026
- Contact your ERP/GSP/e-invoicing vendor this week. Confirm they will deploy the updated API payload (Ship-to GSTIN + URP handling) well before 1 August 2026, and request a test environment date.
- Audit and clean your Ship-to master data. Ensure the correct GSTIN is captured for every ship-to location in your system. Flag genuinely unregistered ship-to parties so your system can auto-insert "URP" when IRNs are generated.
- Run a User Acceptance Test (UAT) on sandbox. Generate at least one Bill-to/Ship-to e-invoice and one e-way bill on the updated APIs before 1 August, so a failed IRN does not halt your dispatches on or after that date.
Statutory backdrop (for context)
- E-invoicing (IRN mandate): Rule 48(4), CGST Rules, 2017 — registered persons in the notified class must prepare invoices by uploading specified particulars to the IRP and obtaining an Invoice Reference Number.
- E-way bill generation: Rule 138, CGST Rules, 2017 — an e-way bill is required for movement of goods of consignment value exceeding ₹50,000.
- Aggregate Annual Turnover (AATO): determines e-invoicing applicability. A separate GSTN advisory (dated 1 July 2026) sets the AATO amendment window for FY 2025-26 as 1–31 July 2026, so confirm your liability before the August deadline.
I'm CA Harun Raaj, Visakhapatnam. If your business uses Bill-to/Ship-to transactions or generates e-way bills, reach out to ensure your systems are ready before 1 August 2026.
---
See Also
Frequently Asked Questions
From when is the Ship-to GSTIN field mandatory in the e-Invoice and e-Way Bill APIs?+
Per the GSTN advisory dated 17 June 2026, the Ship-to GSTIN field becomes mandatory in the e-Invoice (IRP) and e-Way Bill APIs from **1 August 2026**. The change applies wherever Ship-to details are present in a transaction (that is, where goods are delivered to a party different from the buyer).
What do I enter in the Ship-to GSTIN field if the ship-to party is unregistered under GST?+
If the ship-to party is unregistered under GST, you must enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. The field cannot be left blank — it must contain either a valid 15-digit GSTIN or 'URP'.
Why was the Ship-to GSTIN mandate deferred from 15 June to 1 August 2026?+
Per the GSTN advisory dated 9 June 2026, the go-live was deferred from 15 June to 1 August 2026 to allow ERP vendors, GSPs, and e-invoicing software providers additional time to integrate and test the updated API payloads.
What happens if my ERP is not updated before 1 August 2026 and I have Bill-to/Ship-to transactions?+
If your ERP or e-invoicing software is not updated by 1 August 2026, IRN generation and e-way bill generation for Bill-to/Ship-to documents will fail because the mandatory Ship-to GSTIN field will be missing. Without a valid IRN, you cannot issue a valid e-invoice, which stops your billing and dispatch process.
Is this a change in GST law or just a technical change to the GSTN portal?+
This is a **technical/portal change**, not a change in GST law. The underlying obligations under Rule 48(4) and Rule 138 of the CGST Rules, 2017 remain unchanged; only the API field requirements are being tightened to capture Ship-to GSTIN data.
I only issue B2C invoices with no separate ship-to party. Am I affected by this change?+
The mandatory Ship-to GSTIN applies only **where Ship-to details are present** in a transaction. If your documents carry no separate ship-to party (that is, the bill-to and ship-to are the same), this change has limited direct impact, but you should confirm your software still generates IRNs correctly after the 1 August 2026 API update.
What is the new 'E-Way Bill Closure' feature, and must I use it?+
The new E-Way Bill Closure feature, introduced per the GSTN advisory dated 20 June 2026, allows you to voluntarily close an active e-way bill before its validity expires, once the consignment has reached its destination. Use of this feature is **optional** — it is a convenience to manage expired e-way bills on the portal.
Who needs to update their systems before 1 August 2026 — only businesses or also software vendors?+
Both must act. Businesses must ensure their ERP, GSP, or e-invoicing software vendor has deployed the updated API changes and has tested Ship-to GSTIN and URP handling. Software vendors must update their API integration and make the changes available to their users before 1 August 2026.
Go deeper with our hub guides
Statute-cited, section-by-section guides covering the same ground this article does.
Need help with this?
Our team handles the paperwork. You focus on your business.