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 and e-Way Bill APIs for Bill-to/Ship-to transactions. If your ERP or e-invoicing software isn't updated, IRN and e-way bill generation will fail. Here's what you must do now.
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 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 Ship-to GSTIN) a mandatory field in the e-Invoice (IRP) and e-Way Bill system APIs. Wherever a document carries Ship-to details — because goods are delivered to a party different from the buyer — the Ship-to GSTIN must be populated in 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, which means you cannot issue a valid tax invoice.
This is a technical/portal change to the GSTN system, not a change in GST law itself — but its operational impact is significant because it touches the point where invoices are actually generated and validated.
What is changing
Per the GSTN advisories dated 17 June 2026 and 20 June 2026:
- Ship-to GSTIN is now mandatory when Ship-to details are present. In a Bill-to/Ship-to transaction, the Ship-to GSTIN must be populated in both the IRN and e-Way Bill API payloads.
- Unregistered ship-to party? Enter "URP" (Unregistered Person) in place of the GSTIN. The field cannot be left blank.
- New voluntary "E-Way Bill Closure" feature. You can now close an active e-way bill before its validity expires, once the consignment has reached its destination — a housekeeping option that reduces open or expired e-way bills sitting on the portal.
Timeline and why it 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 (advisory dated 9 June 2026). Treat 1 August 2026 as firm and plan integration testing well before that date.
Who is affected
- Every taxpayer under mandatory e-invoicing under Rule 48(4), CGST Rules, 2017 (currently those with aggregate annual turnover above ₹5 crore in any financial year from 2017-18 onwards).
- Any taxpayer generating e-way bills for movement of goods, especially those using Bill-to/Ship-to structures — stock transfers, third-party and drop-ship deliveries, consignments to project sites, and shipments to branches.
- ERP vendors, GSPs (Goods and Services Tax Practitioners), and e-invoicing software vendors, who must update their API integration payloads before the cutover.
Key point: If you move goods to a location different from the invoice buyer and your software doesn't support the Ship-to GSTIN field by 1 August 2026, your IRN generation will fail and you will not be able to issue valid e-invoices or e-way bills.
Before 1 August 2026: what you must do
1. Confirm your software vendor's readiness. Contact your ERP provider, GSP, or e-invoicing software vendor this month and confirm they will ship the updated API payload (Ship-to GSTIN + URP handling) by 1 August 2026. Request a test date so you can validate the changes in your environment.
2. Audit and clean your Ship-to master data. Review all Bill-to/Ship-to transactions in your system. Ensure the correct GSTIN is captured for every ship-to location. For genuinely unregistered parties, mark them clearly so your system knows to insert "URP" automatically.
3. Run sandbox testing before go-live. Generate at least one Bill-to/Ship-to invoice and one e-way bill on the updated APIs in your test environment. Confirm that the IRN is generated and the e-way bill is created without errors. A failed IRN on 1 August can halt your dispatches.
Why this matters for your business
The mandatory Ship-to GSTIN field tightens data governance for GST compliance. It ensures that:
- The tax authority can track goods movement to unregistered locations (via URP).
- Bill-to/Ship-to transactions are properly documented in the IRP and e-Way Bill system.
- Your e-invoicing setup scales for complex supply chains (drop-ships, third-party logistics, project deliveries).
The E-Way Bill Closure feature is optional but useful: once goods reach their destination, you can close the e-way bill and free up the consignment record, reducing clutter and improving reporting.
Statutory backdrop
- E-invoicing: Rule 48(4), CGST Rules, 2017 — registered persons in notified classes must upload invoice particulars to the IRP and obtain an Invoice Reference Number (IRN).
- E-way bill: Rule 138, CGST Rules, 2017 — required for movement of goods of consignment value exceeding ₹50,000.
- Applicability by turnover: the threshold for mandatory e-invoicing is determined by aggregate annual turnover and may change year to year; confirm your applicability status with your CA or GST department.
I'm CA Harun Raaj, Visakhapatnam. If your business issues e-invoices or e-way bills with Ship-to details, reach out to discuss your readiness plan before 1 August 2026.
---
See Also
Frequently Asked Questions
From when is Ship-to GSTIN mandatory in the e-invoice and e-way bill APIs?+
Per the GSTN advisory dated 17 June 2026, Ship-to GSTIN becomes mandatory in the e-Invoice (IRP) and e-Way Bill APIs with effect from **1 August 2026**. The original go-live date of 15 June 2026 was deferred to 1 August 2026 (advisory dated 9 June 2026) to allow vendors and businesses time to integrate the change. After 1 August 2026, if Ship-to details are present in a document, the Ship-to GSTIN field must be populated; failure to do so will cause IRN and e-way bill generation to fail.
What should I enter in the Ship-to GSTIN field if the ship-to party is unregistered?+
If the ship-to party is unregistered under GST, enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. You cannot leave the field blank. The URP entry allows the system to process the invoice and e-way bill while flagging that the destination party is not a registered GST taxpayer, per the GSTN advisories dated 17 and 20 June 2026.
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**, not a change in GST law or rates. 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 make Ship-to GSTIN mandatory where Ship-to details are present.
What happens if my ERP or e-invoicing software is not updated by 1 August 2026?+
For Bill-to/Ship-to documents where Ship-to details are present, IRN generation and e-way bill generation will fail because the mandatory Ship-to GSTIN field is missing. Without a valid IRN, you cannot issue a valid e-invoice. This can halt your invoicing and goods dispatch operations. Contact your ERP or software vendor immediately to confirm their update timeline and schedule sandbox testing before 1 August 2026.
Do I have to use the new E-Way Bill Closure feature?+
No — the **E-Way Bill Closure feature is voluntary**. Per the GSTN advisory dated 20 June 2026, it allows you to close an active e-way bill before its validity expires, once goods have reached the destination. Using it is optional and intended as a convenience to manage e-way bill records and reduce open or expired bills on the portal.
Am I affected if I only issue B2C invoices with no separate ship-to party?+
The mandatory Ship-to GSTIN requirement applies **only where Ship-to details are present** in a document. If your invoices carry no separate ship-to party (the Bill-to and Ship-to are the same), this specific change has limited impact on your invoicing. However, confirm with your software vendor that your system generates IRNs correctly after the API update on 1 August 2026.
Who must comply with this change?+
Every taxpayer under **mandatory e-invoicing** under **Rule 48(4), CGST Rules, 2017** must comply — currently those with aggregate annual turnover above ₹5 crore in any financial year from 2017-18 onwards. Additionally, any business generating e-way bills for movement of goods, especially those using Bill-to/Ship-to structures (stock transfers, drop-ship deliveries, project site shipments), must ensure their software is updated by 1 August 2026.
What is the difference between Bill-to and Ship-to, and why does it matter?+
Bill-to refers to the party being invoiced (the buyer); Ship-to refers to the party receiving the goods, which may be different from the buyer (e.g., a third-party drop-ship location, a project site, or a branch). When they differ, the e-Invoice and e-Way Bill APIs now require the Ship-to GSTIN to be explicitly populated (or "URP" if unregistered) from 1 August 2026. This ensures proper tracking of goods movement and tax compliance for complex supply chains.
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.