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 API payloads whenever ship-to details are present. Unregistered ship-to parties must be marked as 'URP'. Failure to update your ERP or e-invoicing software in time risks IRN generation failure and invoice invalidity.
CA Harun Raaj
Chartered Accountant · Harun Raaj & Associates
Legal basis: Rule 48(4) and Rule 138, CGST Rules 2017 — e-Invoice and e-Way Bill API changes 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: 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 touches the precise point where invoices are generated and validated.
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 orphaned or expired e-way bills on the portal.
Key point: Failure to supply Ship-to GSTIN (or "URP" for unregistered parties) in API payloads from 1 August 2026 will cause IRN and e-way bill generation to fail, preventing issuance of valid e-invoices.
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 per the advisory dated 9 June 2026. Treat 1 August 2026 as firm and plan integration testing well before it.
Who is affected
- 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 and drop-ship deliveries, and consignments to project sites or branches.
- ERP, GSP and e-invoicing software vendors, who must update their API integration payloads to support the new mandatory fields and URP handling.
The 3-step action plan before 1 August 2026
- Confirm your software vendor's readiness this week. Contact your ERP, GSP or e-invoicing provider and confirm they will deploy the updated API payload (Ship-to GSTIN + URP field handling) before 1 August 2026. Request a test sandbox date.
- Clean your ship-to master data. Ensure the correct 15-digit GSTIN is captured for every registered ship-to location. Flag genuinely unregistered parties so your system can auto-populate "URP" during API submission.
- Run UAT on the updated APIs. Generate at least one Bill-to/Ship-to e-invoice and one corresponding e-way bill on the sandbox environment before cut-over day. Confirm IRN generation succeeds and e-way bill creation is accepted. A failed generation on 1 August will halt your dispatches.
Statutory backdrop
- E-invoicing / IRN: Rule 48(4), CGST Rules 2017 — notified classes of registered persons must prepare invoices by uploading specified particulars to the IRP and obtaining an Invoice Reference Number (IRN).
- E-way bill: Rule 138, CGST Rules 2017 — e-way bill required for movement of goods of consignment value exceeding ₹50,000.
- Aggregate Annual Turnover (AATO): determines e-invoicing applicability. Note the separate GSTN advisory revising the AATO amendment window for FY 2025-26 to 1–31 July 2026; if your AATO changes, it may affect your e-invoicing liability from 1 August onward.
I'm CA Harun Raaj, Visakhapatnam. If your business is affected by this API change and you need help validating your e-invoicing and e-way bill setup before 1 August 2026, reach out to discuss how we can support your GST compliance.
---
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, Ship-to GSTIN becomes mandatory in the e-Invoice (IRP) and e-Way Bill APIs with effect from **1 August 2026**. This applies whenever a document contains ship-to details (Bill-to/Ship-to structure). The go-live was deferred from 15 June to 1 August 2026 following industry representations on system readiness.
What do I enter if my ship-to party is unregistered under GST?+
Enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. Per the GSTN advisory dated 20 June 2026, the field cannot be left blank. Your ERP or e-invoicing software must be configured to auto-populate or allow manual entry of "URP" for unregistered ship-to parties.
What happens if I don't update my software before 1 August 2026?+
For Bill-to/Ship-to documents where ship-to details are present, IRN generation and e-way bill creation may fail because the mandatory Ship-to GSTIN field will be missing or invalid. Without a valid IRN, you cannot issue a valid e-invoice, which will halt your invoicing and dispatch processes.
Is this a change in GST law or rates?+
No. This is a technical change to the GSTN's e-Invoice and e-Way Bill API payloads, 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.
Do I have to use the new E-Way Bill Closure feature?+
No — the E-Way Bill Closure feature is **voluntary**. It is a convenience to close an active e-way bill once goods have reached the destination before the e-way bill's validity expires, reducing portal clutter.
I only issue B2C invoices with no separate ship-to. 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 (Bill-to = Ship-to), this specific change has no direct impact. However, confirm your ERP or e-invoicing software vendor has tested the API update to ensure IRN generation continues to work correctly.
What is the current threshold for mandatory e-invoicing?+
Under Rule 48(4) of the CGST Rules, 2017, e-invoicing is mandatory for registered persons whose aggregate annual turnover exceeded ₹5 crore in any financial year from 2017-18 onwards. Separate thresholds may apply to specific business segments; consult your CA for your applicability.
Which advisories do I need to reference for this change?+
The primary advisories are: GSTN advisory dated 17 June 2026 (e-Invoice and e-Way Bill API changes), GSTN advisory dated 20 June 2026 (Ship-To GSTIN field and E-Way Bill Closure feature), and GSTN advisory dated 9 June 2026 (deferral of go-live from 15 June to 1 August 2026). All are available on https://www.gst.gov.in/newsandupdates.
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.