Ship-to GSTIN Mandatory in e-Invoice & e-Way Bill APIs from 1 August 2026
From 1 August 2026, the GSTN mandates Ship-to GSTIN as a required field in e-Invoice and e-Way Bill APIs whenever ship-to details are present. Unregistered parties must be marked 'URP'. Failure to update your ERP or e-invoicing software before this date will cause IRN and e-way bill generation to fail.
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 17 June 2026, 20 June 2026, and 9 June 2026 published on https://www.gst.gov.in/newsandupdates. Last reviewed by CA Harun Raaj: August 2026.
From 1 August 2026, the GSTN is enforcing a mandatory Ship-to GSTIN) field in the e-Invoice (IRP) and e-Way Bill system APIs. Wherever a document carries ship-to details — meaning goods are delivered to a party different from the buyer — the Ship-to GSTIN must be populated in both the IRN-generation and e-Way Bill API payloads. If the ship-to party is unregistered, you must enter "URP" (Unregistered Person) instead of leaving the field blank. This is a technical/portal change, not a change in GST law, but its operational impact is critical: a failed IRN generation means you cannot issue a valid tax invoice.
What is changing
Per GSTN advisories dated 17 June 2026 and 20 June 2026:
- Ship-to GSTIN becomes mandatory when ship-to details are present. In Bill-to/Ship-to transactions, the Ship-to GSTIN field must be populated in the IRN and e-Way Bill API payloads. The field cannot be blank or null.
- Unregistered ship-to parties use "URP". If the ship-to location is not a registered GST entity, enter "URP" as the value for the Ship-to GSTIN field.
- 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. This is optional housekeeping to reduce open or expired e-way bills on the portal.
Who is affected
Timeline and why the date moved
These API 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 the firm operative date and plan integration testing well before it.
Key point: Ship-to GSTIN becomes a required field in e-Invoice and e-Way Bill APIs from 1 August 2026; unregistered ship-to parties must be coded as "URP".
Your 3-step readiness checklist
- Confirm vendor readiness this week. Contact your ERP, GSP, or e-invoicing software provider immediately. Confirm they will release updated API payloads (Ship-to GSTIN + URP handling) before 1 August 2026, and request a sandbox/test date.
- Audit and clean ship-to master data. Review all ship-to locations in your system. Ensure the correct GSTIN is captured for every registered ship-to party; mark genuinely unregistered parties so your system can auto-populate "URP" in API calls.
- Run User Acceptance Testing (UAT). Before 1 August 2026, generate at least one test Bill-to/Ship-to invoice and one e-way bill on the updated APIs in a sandbox environment. Verify that IRN generation and e-way bill creation succeed with valid Ship-to GSTIN and URP values. Do not wait until 1 August to discover integration failures.
Statutory context
- E-invoicing obligation: 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 (IRN).
- E-way bill requirement: Rule 138, CGST Rules, 2017 — An e-way bill is required for the movement of goods of consignment value exceeding ₹50,000.
- Applicability threshold: Aggregate Annual Turnover (AATO) determines e-invoicing mandatoriness. The e-invoicing rule currently applies to registered persons whose aggregate turnover exceeded ₹5 crore in any financial year from 2017-18 onwards.
I'm CA Harun Raaj, Visakhapatnam. If your business operates a Bill-to/Ship-to supply chain or manages e-invoicing and e-way bill generation, reach out to confirm your systems are ready for 1 August 2026.
---
See Also
Frequently Asked Questions
From when is Ship-to GSTIN mandatory in the e-invoice and e-way bill APIs?+
From 1 August 2026, per GSTN advisories dated 17 June 2026 and 20 June 2026. The go-live was deferred from 15 June 2026 to 1 August 2026 following industry representations on readiness. From that date, wherever ship-to details are present in a Bill-to/Ship-to invoice, the Ship-to GSTIN field becomes a required input in both the IRN-generation and e-Way Bill APIs.
What do I enter if my ship-to party is not registered under GST?+
Enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. You cannot leave the field blank or null. This applies to any location where goods are delivered but no valid GST registration exists.
What happens if my software is not updated by 1 August 2026?+
For Bill-to/Ship-to invoices, IRN generation and e-way bill creation will fail because the mandatory Ship-to GSTIN field is missing or incorrectly mapped in the API payload. Without a valid IRN, you cannot issue a valid e-invoice, which will halt your invoicing and goods movement processes.
Is this a change in GST law or GST rates?+
No. This is a technical change to the GSTN's e-Invoice (IRP) and e-Way Bill APIs. The underlying obligations under Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) of the CGST Rules, 2017 are unchanged; only the API field requirements are being tightened.
Do I have to use the new E-Way Bill Closure feature?+
No — the E-Way Bill Closure feature is voluntary. It is a convenience to close an active e-way bill before its validity expires once the consignment has reached its destination. Use it only if it suits your operations.
I only issue B2C invoices with no separate ship-to. Am I affected?+
The mandatory Ship-to GSTIN requirement applies only where ship-to details are present in the document. If your invoices carry no separate ship-to party (i.e., ship-to and bill-to are the same), this specific change has limited direct impact, though you should confirm with your software vendor that IRN generation remains unaffected after the API update.
Which taxpayers must comply with the mandatory Ship-to GSTIN field?+
All taxpayers covered by mandatory e-invoicing under Rule 48(4) of the CGST Rules, 2017 (currently those with aggregate annual turnover above ₹5 crore in any FY from 2017-18 onwards). Additionally, any taxpayer generating e-way bills for Bill-to/Ship-to transactions must ensure correct Ship-to GSTIN or "URP" mapping.
When should I start testing the updated APIs?+
Contact your ERP, GSP, or e-invoicing vendor immediately to confirm their release date for updated API payloads. Once available, run User Acceptance Testing (UAT) in a sandbox environment before 1 August 2026. Generate at least one test Bill-to/Ship-to invoice and one e-way bill to verify Ship-to GSTIN and URP handling work correctly before the go-live date.
Related Services
Based on this article's category and vertical tag, these services are the most relevant next steps.
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.