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. If your software isn't updated, IRN and e-way bill generation for Bill-to/Ship-to transactions 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 — e-invoicing and e-way bill requirements. GSTN API changes effective: 1 August 2026. Source: GSTN advisories dated 9 June 2026, 17 June 2026, 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 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 IRN-generation and e-Way Bill API payloads. If your ERP or e-invoicing software is not updated before this date, IRN and e-way bill generation can fail — halting your ability to issue valid tax invoices and despatch goods.
This is a technical/portal change, not a change in GST law — but its operational impact is high because it sits at the precise point where invoices are generated and goods are moved.
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 remain blank.
- 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 convenience to manage stale e-way bills on the portal.
Timeline 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 per the advisory dated 9 June 2026. Treat 1 August as firm and plan integration testing well in advance.
Who is affected
Key point: The mandatory Ship-to GSTIN applies only where Ship-to details are present; if your invoices carry no separate ship-to party, this change has limited operational impact.
The 3-step action plan before 1 August 2026
- Contact your ERP/GSP/e-invoicing vendor this week. Confirm they will ship the updated API payload (Ship-to GSTIN + URP handling) before 1 August 2026, and request a test date and sandbox access.
- Audit and clean your Ship-to master data. Ensure the correct GSTIN is captured for every ship-to location; mark genuinely unregistered parties so your system can auto-populate "URP" without manual intervention.
- Run a UAT / sandbox test of at least one Bill-to/Ship-to invoice and one e-way bill on the updated APIs before the cut-over, so a failed IRN does not disrupt your dispatch operations after 1 August.
Why this matters for your business
Under Rule 48(4), CGST Rules 2017, registered persons in the mandatory e-invoicing class must upload specified particulars to the IRP and obtain an Invoice Reference Number (IRN) before issuing an invoice. Under Rule 138, e-way bills are required for movement of goods exceeding ₹50,000 in value.
The API field tightening does not alter these underlying obligations — but it does mean the GSTN's acceptance criteria are stricter. If your system cannot populate Ship-to GSTIN (or "URP" for unregistered parties), the API will reject the request. No IRN means no valid invoice; no valid e-way bill means goods cannot legally be in transit.
For businesses using Bill-to/Ship-to structures — such as stock transfers between branches, drop-shipping arrangements, or consignments to project sites — this change is non-negotiable. Separately, the new voluntary E-Way Bill Closure feature is a housekeeping convenience; you are not obliged to use it, but it helps manage expired e-way bills cluttering your portal.
I'm CA Harun Raaj, Visakhapatnam. If your business uses Bill-to/Ship-to invoicing or relies on e-way bills for goods movement, reach out to discuss your readiness plan before 1 August 2026.
---
See Also
Frequently Asked Questions
When does Ship-to GSTIN become mandatory in the e-Invoice and e-Way Bill APIs?+
Per the GSTN advisory dated 17 June 2026, Ship-to GSTIN becomes mandatory in IRN-generation and e-Way Bill API payloads from **1 August 2026**. This applies wherever a document contains Ship-to details (a Bill-to/Ship-to transaction). The go-live was originally scheduled for 15 June 2026 but was deferred to 1 August 2026 following industry representations on system readiness.
What do I enter in the Ship-to GSTIN field if the party is unregistered?+
If the ship-to party is unregistered under GST, enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. The field is mandatory and cannot remain blank; URP is the designated placeholder for genuinely unregistered recipients.
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 API requirements. The underlying legal obligations under Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) of the CGST Rules 2017 are unchanged; only the API field requirements and validation rules are being tightened.
What happens if my software is not updated before 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 is missing from the API payload. Without a valid IRN, you cannot issue a valid e-invoice. This will halt your ability to issue tax invoices and despatch goods legally.
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 active e-way bill before its validity expires, once the consignment has reached its destination. Use it if it helps manage your e-way bill portal; it is not a legal requirement.
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**. If your invoices carry no separate ship-to party (i.e., the buyer and recipient are the same), this specific change has limited impact. However, confirm with your software vendor that your IRN generation continues to work correctly after the API update.
Which taxpayers are required to update their systems before 1 August 2026?+
Taxpayers covered by mandatory e-invoicing under Rule 48(4), CGST Rules (aggregate annual turnover ₹5 crore+) who use Bill-to/Ship-to invoice structures must ensure their ERP, GSP, or e-invoicing software is updated. All e-way bill users, particularly those using stock transfers, drop-shipping, or project consignments, must also verify their Ship-to GSTIN or URP master data.
What is the action I should take right now?+
Contact your ERP, GSP, or e-invoicing software vendor immediately to confirm their API update timeline and request sandbox/test access. Clean your Ship-to master data to ensure correct GSINs for each location and flag unregistered parties for URP auto-population. Run a UAT test of at least one Bill-to/Ship-to invoice and one e-way bill before 1 August 2026.
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.