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 and e-Way Bill APIs. If your software isn't updated, IRN and e-way bill generation for Bill-to/Ship-to transactions will fail. Here's what you need to 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 9 June 2026, 17 June 2026, and 20 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 tightening the e-Invoice (IRP) and e-Way Bill system APIs. Wherever a document carries Ship-to details, the Ship-to GSTIN) becomes a mandatory field 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 — and a failed IRN means you cannot issue a valid tax invoice.
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 are actually generated.
What is changing
Per the GSTN advisory dated 17 June 2026 (read with the advisory dated 20 June 2026):
- Ship-to GSTIN is now mandatory when Ship-to details are present. In a Bill-to/Ship-to transaction (where goods are delivered to a party different from the buyer), the Ship-to GSTIN must be populated in 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.
When it takes effect — and 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 (advisory dated 9 June 2026). Treat 1 August 2026 as the firm implementation date and plan integration testing well before it.
Who is affected
The mandatory Ship-to GSTIN field applies to:
- Every taxpayer covered by mandatory e-invoicing under Rule 48(4) of the CGST Rules 2017 (current threshold: 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 or drop-ship deliveries, and consignments to project sites or branches.
- ERP, GSP and e-invoicing software vendors, who must update their API integration payloads by 1 August 2026.
The 3-step action plan before 1 August 2026
- Confirm vendor readiness. Contact your ERP, GSP, or e-invoicing software vendor this week. Confirm they will deploy the updated API payload (Ship-to GSTIN + URP handling) before 1 August 2026 and request a test date.
- Clean your Ship-to master data. Ensure the correct GSTIN is captured for every ship-to location. Mark genuinely unregistered parties so the system can auto-insert "URP" where needed.
- Run sandbox testing. Generate at least one Bill-to/Ship-to invoice and one e-way bill on the updated APIs before the cut-over. A failed IRN on or after 1 August could halt your dispatches.
Key point: Ship-to GSTIN is mandatory where ship-to details are present; unregistered parties must be coded as "URP" — leaving the field blank will cause IRN and e-way bill generation to fail.
Statutory context
- E-invoicing (IRN): Rule 48(4), CGST Rules 2017 — registered persons in a notified class must prepare invoices by uploading specified particulars to the IRP and obtaining an Invoice Reference Number.
- E-way bill: Rule 138, CGST Rules 2017 — e-way bill is required for movement of goods of consignment value exceeding ₹50,000.
- Aggregate Annual Turnover (AATO): determines e-invoicing applicability. The GSTN separately manages the AATO amendment window for each financial year.
The API change does not alter these underlying obligations. It tightens the data validation rules that the GSTN applies to incoming API requests.
I'm CA Harun Raaj, Visakhapatnam. If your business issues Bill-to/Ship-to invoices or e-way bills, reach out to confirm your software is ready before 1 August 2026.
---
See Also
Frequently Asked Questions
From when is Ship-to GSTIN mandatory in e-Invoice and e-Way Bill APIs?+
Per the GSTN advisory dated 17 June 2026, the Ship-to GSTIN field becomes mandatory in e-Invoice (IRP) and e-Way Bill API payloads with effect from **1 August 2026**. The go-live was deferred from the original date of 15 June 2026 following industry representations on software readiness.
What do I enter if my ship-to party is unregistered under GST?+
Enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. You cannot leave the field blank; the GSTN API will reject the request if Ship-to details are present and the GSTIN field is empty or missing.
What happens if my software is not updated before 1 August 2026?+
For Bill-to/Ship-to documents, IRN generation and e-way bill generation may fail because the mandatory Ship-to GSTIN is missing from the API payload. Without a valid IRN, you cannot issue a valid e-invoice under Rule 48(4), CGST Rules 2017.
Is this a change in GST law or rates?+
No. This is a technical change to the GSTN's API field requirements. 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 data validation rules 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 allows you to close an e-way bill before its validity expires, once goods have reached the destination. Using it is optional and does not affect any compliance obligation.
I only issue B2C invoices with no separate ship-to party. Am I affected?+
The mandatory Ship-to GSTIN applies **where Ship-to details are present**. If your invoices carry no separate ship-to party (e.g., the bill-to and ship-to are the same), this specific change has limited impact — but confirm your software vendor has tested the updated API integration for your transaction types.
Who needs to update their systems — my ERP, GSP, or both?+
Your **ERP (if it integrates directly with GSTN APIs)** or your **GSP (if your ERP submits data to the GSP, which then calls the GSTN APIs)** must update their API payloads to include and validate the Ship-to GSTIN field. Confirm with your vendor which layer they operate in and get their timeline for the update.
Can I defer compliance if my software vendor misses the 1 August 2026 deadline?+
No. From 1 August 2026, the GSTN will enforce the mandatory Ship-to GSTIN field in the APIs. If your software has not been updated and you attempt to generate an IRN or e-way bill with Ship-to details, the request will fail. There is no grace period; plan your testing and vendor coordination now.
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.