Ship-to GSTIN Mandatory in e-Invoice & e-Way Bill APIs from 1 August 2026
From 1 August 2026, the GSTN is making Ship-to GSTIN a mandatory field in e-Invoice and e-Way Bill APIs. If your ship-to party is unregistered, you must enter "URP". Failure to update your ERP or invoicing software by this date will cause IRN 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 9, 17, and 20 June 2026, 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 APIs. Where a document carries "Ship-to" details — meaning goods are delivered to a party different from the buyer — the Ship-to GSTIN must be populated. If the ship-to party is unregistered, you enter "URP" (Unregistered Person) instead of leaving the field blank. This is a technical portal change, not a change in GST law, but it directly blocks invoice and e-way bill generation if not implemented. Without a valid IRN, you cannot issue a compliant e-invoice.
What is changing
Per GSTN advisories dated 17 June 2026 and 20 June 2026:
- Ship-to GSTIN becomes mandatory whenever a Bill-to/Ship-to transaction is recorded. The field must be populated in both IRN-generation and e-Way Bill API payloads.
- Unregistered parties require "URP" entry. You cannot leave the field blank; the system will reject payloads with a missing or blank Ship-to GSTIN.
- 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 option to reduce stale e-way bills on the portal.
When it takes effect
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). This is the firm deadline; systems must be ready before this date to avoid IRN and e-way bill generation failures.
Who is affected
- Mandatory e-invoicing taxpayers under Rule 48(4), CGST Rules 2017 — currently registered persons with aggregate annual turnover exceeding ₹5 crore in any financial year from 2017-18 onwards.
- All e-way bill users, especially those with Bill-to/Ship-to structures — stock transfers to branches, third-party/drop-ship deliveries, project site consignments, and interwarehouse movements.
- ERP, GSP, and e-invoicing software vendors — API payload updates are non-negotiable before 1 August 2026.
Critical action plan before 1 August 2026
Week 1: Contact your software vendor. Confirm they will release the updated API (Ship-to GSTIN + URP handling) before 1 August 2026. Request a test date and sandbox credentials.
Week 2–3: Audit your ship-to master data. Review all ship-to locations; ensure the correct GSTIN is captured for every registered party. Flag genuinely unregistered parties so your system can auto-insert or prompt for "URP" entry.
Week 4: Run UAT on the updated APIs. Generate at least one Bill-to/Ship-to e-invoice and one e-way bill in sandbox mode on the new API version. Verify IRN generation and e-way bill creation succeed before 1 August.
Key point: A failed IRN generation on or after 1 August 2026 will halt your ability to issue valid tax invoices for Bill-to/Ship-to transactions, so confirm your software is updated well before the deadline.
Statutory backdrop
E-invoicing: Rule 48(4), CGST Rules 2017 requires notified classes of registered persons to prepare invoices by uploading specified particulars to the IRP and obtaining an Invoice Reference Number (IRN).
E-way bill: Rule 138, CGST Rules 2017 mandates an e-way bill for movement of goods with consignment value exceeding ₹50,000.
These obligations remain unchanged; only the API field requirements are being tightened to enforce data quality and traceability.
I'm CA Harun Raaj, Visakhapatnam. If your business relies on Bill-to/Ship-to transactions or operates on the e-invoicing platform, reach out to discuss your API readiness and GST compliance before 1 August 2026.
---
See Also
Frequently Asked Questions
What is Ship-to GSTIN and why is it becoming mandatory from 1 August 2026?+
Ship-to GSTIN is the GST Registration Number of the location where goods are physically delivered, separate from the billing address. Per GSTN advisories dated 17 and 20 June 2026, it becomes a mandatory field in the e-Invoice (IRP) and e-Way Bill APIs from 1 August 2026 to improve invoice accuracy and goods traceability. If your invoices carry Bill-to/Ship-to details, the field must be populated in all API calls.
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; the API will reject the payload. This applies to all unregistered ship-to locations.
What happens if my ERP software is not updated before 1 August 2026?+
IRN generation and e-Way Bill creation for Bill-to/Ship-to documents will fail because the mandatory Ship-to GSTIN field will be missing or blank. Without a valid IRN, you cannot issue a compliant e-invoice, effectively halting your invoicing process for affected transactions.
I only issue B2C invoices with no separate ship-to address. Am I affected?+
The mandatory Ship-to GSTIN applies **where Ship-to details are present**. If your invoices carry no separate ship-to party (single address for billing and delivery), this change has limited direct impact — but confirm with your software vendor that IRN generation works correctly after the API update.
Is the E-Way Bill Closure feature mandatory or optional?+
It is **optional**. The E-Way Bill Closure facility, introduced per the GSTN advisory dated 20 June 2026, allows you to close an active e-way bill before its validity expires once goods reach the destination. You can use it for housekeeping or ignore it if not needed.
Why was the go-live date moved 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 following industry representations on ERP and GSP readiness. This gave vendors and taxpayers additional time to integrate the API changes. 1 August 2026 is the firm effective date.
Is this a change in GST law or GST rules?+
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 remain unchanged; only the API field requirements are being tightened.
What should I do right now to prepare?+
Contact your ERP, GSP, or e-invoicing software vendor to confirm they are releasing the updated API before 1 August 2026. Audit your ship-to master data to ensure correct GSINs are captured and flag unregistered parties. Run a sandbox test of Bill-to/Ship-to invoice and e-way bill generation on the updated API before the deadline.
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.