Ship-to GSTIN Mandatory in e-Invoice & e-Way Bill APIs from 1 August 2026
From 1 August 2026, the GSTN requires Ship-to GSTIN as a mandatory field in e-Invoice (IRP) and e-Way Bill APIs whenever ship-to details are present. Unregistered parties must be marked as 'URP'. Businesses must update ERP and GSP integrations before the deadline or face 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 — 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 mandating a critical change to the e-Invoice (IRP) and e-Way Bill system APIs: 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. If your ERP or e-invoicing software is not updated in time, IRN and e-way bill generation can fail — and without a valid IRN, you cannot issue a lawful tax invoice.
This is a technical change to the portal infrastructure, not a change in GST law — but its operational impact is substantial because it directly affects the point where invoices are generated and bills of lading are created.
What is changing
Per the GSTN advisories dated 17 June 2026 and 20 June 2026, three key modifications are being introduced:
- Ship-to GSTIN is mandatory when Ship-to details are present. In transactions where goods are delivered to a party different from the invoice-to (bill-to) party, the Ship-to GSTIN must now be populated in both the IRN and e-Way Bill API payloads. Leaving this field blank will cause API submission to fail.
- Unregistered ship-to parties use 'URP'. If the ship-to location is operated by an unregistered person or entity, you must enter 'URP' (Unregistered Person) in the Ship-to GSTIN field. The field cannot be omitted.
- New optional E-Way Bill Closure feature. GSTN has introduced a voluntary facility to close an active e-way bill before its validity expires, once the consignment has reached its destination — reducing clutter from open or expired e-way bills.
Timeline: Why 1 August 2026 (not 15 June)
These changes were originally scheduled for 15 June 2026. Following industry representations on ERP integration and GSP readiness timelines, the GSTN deferred the go-live to 1 August 2026 (advisory dated 9 June 2026). The 1 August date is now firm; plan your integration testing and UAT well in advance.
Who is affected
Three-step action plan before 1 August 2026
Step 1: Contact your software vendor now.
Reach out to your ERP, GSP, or e-invoicing platform vendor this week. Confirm in writing that they will release updated API payloads (supporting Ship-to GSTIN mandatory field and URP entry) before 1 August 2026. Request a test/sandbox environment date so you can validate the integration.
Step 2: Audit and clean your Ship-to master data.
Review all Ship-to locations in your master data. For each location, confirm the correct GSTIN is captured. For genuinely unregistered locations (small retail outlets, informal dealers, or recipients not registered under GST), ensure your system is flagged to auto-insert 'URP' in the Ship-to GSTIN field during IRN and e-way bill generation.
Step 3: Run user acceptance testing in sandbox.
Before 1 August 2026, generate at least one IRN and one e-way bill in the updated sandbox environment using a Bill-to/Ship-to structure. This will expose any gaps in your data or integration before go-live, so a failed IRN does not halt your dispatches on 1 August or shortly after.
Statutory context (Rule 48(4) and Rule 138, CGST Rules 2017)
E-invoicing under Rule 48(4) applies to a notified class of registered persons (currently those with AATO exceeding ₹5 crore from FY 2017-18 onwards). These persons must prepare invoices by uploading specified particulars to the IRP (Invoice Registration Portal) and obtaining an Invoice Reference Number (IRN). The IRN is proof that the invoice has been registered and is legally valid.
E-way bills under Rule 138 are required whenever goods (excluding specified exempted categories) are moved with a consignment value exceeding ₹50,000. The e-way bill must be generated before movement begins.
The Ship-to GSTIN mandate is a tightening of the API field requirements, not a change to the underlying filing obligations or exemptions. Taxpayers already providing Ship-to details in their invoices will now simply be required to also populate the GSTIN for that location in the API payload.
Key point: The Ship-to GSTIN mandatory field takes effect 1 August 2026; failure to populate it (or enter 'URP' for unregistered parties) will cause IRN and e-way bill generation to fail, preventing issuance of valid invoices and bills of lading.
Common scenarios and how they are handled
- Direct B2B invoice with ship-to: If Invoice Party A is billed to Company B at its registered office, but goods are shipped to Company B's branch (a different GSTIN), the Ship-to GSTIN for the branch must be populated.
- Drop-ship or third-party logistics: If goods are shipped directly from Supplier A to End-Customer C on the instruction of Distributor B, the Ship-to GSTIN for Customer C must be provided. If Customer C is unregistered, enter 'URP'.
- Stock transfer between company locations: If goods move between two locations of the same company (each with a separate GSTIN under Rule 2(105)), the Ship-to GSTIN of the receiving location must be populated.
- E-way bill for movement to unregistered retail outlet: When goods are dispatched to an unregistered dealer or small outlet for resale, the Ship-to field receives 'URP'.
I'm CA Harun Raaj, Visakhapatnam. If your business is preparing for the 1 August 2026 e-Invoice and e-Way Bill API changes, reach out to discuss your ERP integration and data readiness.
---
See Also
Frequently Asked Questions
From when is Ship-to GSTIN mandatory in the e-invoice and e-way bill APIs?+
Per the GSTN advisories dated 17 June 2026 and 20 June 2026, Ship-to GSTIN becomes a mandatory field in the e-Invoice (IRP) and e-Way Bill API payloads from **1 August 2026**. Originally scheduled for 15 June 2026, the go-live was deferred to 1 August 2026 to allow ERP and GSP vendors time to update their systems. This date is firm.
What do I enter in the Ship-to GSTIN field if the ship-to party is unregistered?+
If the ship-to location is operated by an unregistered person or entity, you must enter **'URP' (Unregistered Person)** in the Ship-to GSTIN field. You cannot leave the field blank; the API will reject the submission if the field is empty or missing when ship-to details are present.
Is this a change in GST law or just a technical portal change?+
This is a **technical change to the GSTN's e-Invoice and e-Way Bill API infrastructure**, not a change in GST law. 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 to enforce mandatory population of Ship-to GSTIN.
What happens if I do not update my ERP or e-invoicing software before 1 August 2026?+
For invoices and e-way bills containing ship-to details, IRN generation and e-way bill generation will fail if the mandatory Ship-to GSTIN field is not populated or correctly populated. Without a valid IRN, you cannot issue a lawful tax invoice. This can disrupt your dispatch and invoicing operations from 1 August 2026 onwards.
Who is affected by the Ship-to GSTIN mandatory field requirement?+
Taxpayers covered by mandatory e-invoicing under Rule 48(4) (aggregate annual turnover exceeding ₹5 crore from FY 2017-18 onwards) and all taxpayers subject to e-way bill requirements under Rule 138 are affected, especially those using Bill-to/Ship-to structures, stock transfers, drop-shipping, or third-party logistics. ERP, GSP, and e-invoicing software vendors must also update their API payloads.
Do I have to use the new E-Way Bill Closure feature?+
No. The E-Way Bill Closure feature is **entirely voluntary**. It allows you to close an active e-way bill before its validity expires once the consignment has reached its destination. It is a housekeeping convenience to reduce open or expired e-way bills sitting on the portal; you are not required to use it.
I issue only B2C invoices with no separate ship-to location. Am I affected?+
The mandatory Ship-to GSTIN applies **only where ship-to details are present on the invoice**. If your B2C invoices carry no separate ship-to party (i.e., bill-to and ship-to are the same), this specific change has limited direct impact. However, confirm with your software vendor that your IRN and e-way bill generation continues to work correctly after the API update on 1 August 2026.
What should I do right now to prepare for 1 August 2026?+
Three immediate steps: (1) Contact your ERP, GSP, or e-invoicing vendor to confirm they will release updated API payloads supporting mandatory Ship-to GSTIN and URP entry before 1 August 2026, and request a test date; (2) Audit your ship-to master data to ensure correct GSINs are linked to each location and flag unregistered locations for 'URP' entry; (3) Run a sandbox test of at least one Bill-to/Ship-to invoice and one e-way bill on the updated APIs before go-live to identify any gaps.
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.