Ship-to GSTIN Mandatory in e-Invoice & e-Way Bill APIs from 1 August 2026
From 1 August 2026, the Ship-to GSTIN becomes a mandatory field in e-Invoice (IRP) and e-Way Bill APIs whenever ship-to details are present. If the ship-to party is unregistered, you must enter 'URP'. Businesses must update their ERP and e-invoicing software before the cut-over date to avoid IRN and e-way bill generation failures.
CA Harun Raaj
Chartered Accountant · Harun Raaj & Associates
Legal basis: Rule 48(4) and Rule 138, CGST Rules 2017 — e-invoicing and e-way bill requirements. API implementation per GSTN advisories dated 17 June 2026 and 20 June 2026. Effective: 1 August 2026. Source: https://www.gst.gov.in/newsandupdates. Last reviewed by CA Harun Raaj: August 2026.
What is changing
From 1 August 2026, the GSTN is tightening the e-Invoice (IRP) and e-Way Bill API specifications. Per the GSTN advisories dated 17 June 2026 (read with 20 June 2026):
- Ship-to GSTIN) becomes mandatory wherever a document contains ship-to details. The field must be populated in both the IRN-generation and e-Way Bill API payloads.
- Unregistered ship-to parties: enter "URP" (Unregistered Person) instead of a 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 goods reach the destination—a housekeeping convenience to manage expired or stale e-way bills on the portal.
This is a technical/portal change, not a change in GST law—but its operational impact is high, because it affects the point where invoices and e-way bills are actually generated. Without a valid IRN, you cannot issue a compliant e-invoice.
Why the date moved
These functionalities 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 (per advisory dated 9 June 2026). Treat 1 August 2026 as firm.
Who is affected
Key point: Any IRN or e-way bill generated for a Bill-to/Ship-to transaction without a valid Ship-to GSTIN (or "URP" if unregistered) will fail after 1 August 2026.
The 3-step action plan before 1 August 2026
Step 1: Confirm vendor readiness this week.
Contact your ERP, GSP, or e-invoicing software provider. Request written confirmation that they will deploy the updated API payload (Ship-to GSTIN + URP handling) before 1 August 2026, and secure a test environment date.
Step 2: Clean and map your ship-to master data.
Audit all ship-to locations in your system:
- Capture the correct GSTIN for every registered ship-to party.
- Flag genuinely unregistered parties so your system can auto-insert "URP" when generating invoices and e-way bills.
- Test the data mapping in a sandbox environment.
Step 3: Run end-to-end testing before cut-over.
Generate at least one sample Bill-to/Ship-to e-invoice and one e-way bill on the updated APIs in your vendor's test environment. Verify that both the IRN and e-way bill are generated without error. This prevents dispatch delays on 1 August.
Why this matters for your business
On 1 August 2026, the GSTN's validation rules will reject any e-Invoice or e-Way Bill API request where Ship-to details are present but the Ship-to GSTIN is missing or blank. The IRN generation will fail—and without a valid IRN, you cannot issue a compliant e-invoice under Rule 48(4). For businesses using third-party logistics, drop-ship or consignment models, and inter-branch transfers, this is not an optional exercise.
Even if your software vendor confirms they are "ready", do not assume your configuration is correct. URP handling logic and master-data mapping must be tested in your specific business scenario.
Statutory backdrop
- E-invoicing (Rule 48(4), CGST Rules 2017): Specified classes of registered persons must prepare invoices by uploading particulars to the Invoice Registration Portal (IRP) and obtaining an Invoice Reference Number (IRN). The e-Invoice is the tax invoice.
- E-way bill (Rule 138, CGST Rules 2017): A registered person moving goods of consignment value exceeding ₹50,000 must generate an e-way bill before the goods are despatched.
- This change does not alter those obligations—it only tightens the data fields required by the GSTN's APIs to process them.
I'm CA Harun Raaj, Visakhapatnam. If your business is affected by this API change and you need help preparing your e-invoicing or e-way bill setup, reach out.
---
See Also
Frequently Asked Questions
From when is Ship-to GSTIN mandatory in e-invoicing and e-way bill APIs?+
Effective **1 August 2026**, per GSTN advisories dated 17 June and 20 June 2026. Wherever a document contains ship-to details, the Ship-to GSTIN field becomes mandatory in both the IRN-generation and e-Way Bill API payloads. This date was originally 15 June 2026 but was deferred to allow industry time for ERP and GSP readiness.
What if my ship-to party is not GST-registered?+
Enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. You cannot leave the field blank. Per the GSTN advisory dated 20 June 2026, URP is the standard code for unregistered ship-to parties in the API payload.
What happens if my software is not updated before 1 August 2026?+
IRN and e-way bill generation will fail for any Bill-to/Ship-to document where the Ship-to GSTIN is missing or blank. Without a valid IRN, you cannot issue a compliant e-invoice under Rule 48(4), CGST Rules 2017—which can halt your invoicing and despatch operations.
Is the new E-Way Bill Closure feature compulsory?+
No—it is **voluntary**. The GSTN introduced an optional facility to close an active e-way bill before its validity expires, once goods have reached their destination. You can choose to use it or continue issuing e-way bills as you currently do.
I only issue B2C invoices with no separate ship-to details. Am I affected?+
The mandatory Ship-to GSTIN applies **only where ship-to details are present** in the document. If your B2C invoices carry no separate ship-to party, this specific change has limited direct impact—but confirm with your software vendor that your system still generates IRNs correctly after the API update.
Is this a change in GST law or GST rates?+
No. This is a **technical change to the GSTN's e-Invoice and e-Way Bill APIs**. The underlying obligations under Rule 48(4) and Rule 138 of the CGST Rules 2017 are unchanged; only the API field requirements are being tightened to mandate the Ship-to GSTIN.
Which businesses are affected by this API change?+
Anyone subject to mandatory e-invoicing (annual turnover above ₹5 crore under Rule 48(4)), anyone voluntarily issuing e-invoices on Bill-to/Ship-to documents, and any business generating e-way bills where goods are shipped to a party different from the buyer. ERP, GSP, and e-invoicing software vendors must update their API integration.
What is the action plan before 1 August 2026?+
Confirm your software vendor's deployment timeline for the API update (do this immediately). Clean your ship-to master data to ensure correct GSINs are captured and unregistered parties are flagged for "URP". Run a sandbox test on at least one Bill-to/Ship-to e-invoice and e-way bill before the cut-over to verify there are no generation failures.
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.