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 all Bill-to/Ship-to transactions. If your software isn't updated, IRN and e-way bill generation can fail. Here's what you need to do before the deadline.
CA Harun Raaj
Chartered Accountant · Harun Raaj & Associates
Legal basis: Rule 48(4) and Rule 138, CGST Rules 2017 — Technical API change effective 1 August 2026. Source: GSTN advisories dated 17 June 2026, 20 June 2026, and 9 June 2026 (https://www.gst.gov.in/newsandupdates). Last reviewed by CA Harun Raaj: August 2026.
Key point: From 1 August 2026, every Bill-to/Ship-to invoice and e-way bill must populate Ship-to GSTIN) or "URP" in the API payload, or IRN and e-way bill generation will fail.
What is changing
From 1 August 2026, the GSTN is tightening the e-Invoice (IRP) and e-Way Bill API specifications. Per the GSTN advisory dated 17 June 2026 (read with the advisory dated 20 June 2026):
- Ship-to GSTIN becomes mandatory whenever a document carries Ship-to details — that is, when goods are delivered to a location different from the invoice-to buyer.
- Unregistered Ship-to parties require "URP" — if the Ship-to party is not GST-registered, you must enter "URP" (Unregistered Person) in the mandatory Ship-to GSTIN field; blank entries are no longer accepted.
- New voluntary e-Way Bill Closure feature — you can now close an active e-way bill before validity expires once the consignment reaches destination, reducing the backlog of expired e-way bills on the portal.
This is a technical change to the API specifications, not a change in GST law. The underlying obligations under Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) remain unchanged; only the data structure required by the IRP and e-Way Bill portals is being tightened.
Timeline and original deferment
These changes were originally scheduled for 15 June 2026. Following representations from industry on ERP, GSP (Government Service Provider), and e-invoicing software readiness, the GSTN deferred the go-live to 1 August 2026 (advisory dated 9 June 2026). Treat 1 August 2026 as the firm effective date and plan your integration testing accordingly.
Who is affected
If you issue invoices with a separate Ship-to location, or if your e-way bills show a delivery address different from the buyer's registered address, you are directly affected.
Your action plan before 1 August 2026
Step 1: Verify your software vendor's readiness.
Contact your ERP, GSP, or e-invoicing software vendor immediately and confirm they will release an updated API integration (supporting Ship-to GSTIN + URP handling) before 1 August 2026. Request a test environment and a scheduled sandbox test date.
Step 2: Audit and clean your Ship-to master data.
Review all Ship-to locations in your system. Ensure every registered Ship-to party has the correct GSTIN captured. For genuinely unregistered recipients (e.g. consumers, unregistered traders), flag them so the system can auto-populate "URP" during invoice generation. A missing or incorrect GSTIN will cause IRN generation to fail after 1 August.
Step 3: Run a pre-cutover test.
Generate at least one full Bill-to/Ship-to e-invoice and one corresponding e-way bill in your vendor's sandbox or test environment using the updated API before 1 August. Confirm both the IRN and e-way bill are generated successfully. A failed IRN means no valid tax invoice can be issued, so this testing is critical.
Why this matters
Without a valid IRN (Invoice Reference Number), you cannot legally issue an e-invoice under Rule 48(4). If your software fails to generate an IRN because Ship-to GSTIN is missing or invalid, your dispatch documentation becomes non-compliant. This can expose you to:
- Inability to issue a valid tax invoice, affecting your supply chain and customer relationships.
- Potential notice or demand under the CGST Act if the tax authority views the missing IRN as non-compliance with Rule 48(4).
- Difficulty closing e-way bills and tracking consignments.
The good news: the change is technical and manageable. The bad news: it requires coordination between you, your software vendor, and your finance team, and that coordination must happen now.
Statutory backdrop
- E-invoicing (IRN): Rule 48(4), CGST Rules 2017 — registered persons in a notified category must prepare invoices by uploading specified particulars to the IRP and obtaining an Invoice Reference Number.
- E-way bill: Rule 138, CGST Rules 2017 — required for movement of goods of consignment value exceeding ₹50,000.
- Aggregate Annual Turnover (AATO): determines e-invoicing applicability thresholds. Note that the GSTN's separate advisory (dated 1 July 2026) revised the AATO amendment window for FY 2025-26; if you are borderline on the ₹5 crore threshold, confirm your filing status well before 1 August.
I'm CA Harun Raaj, Visakhapatnam. If you operate a Bill-to/Ship-to supply chain or use e-invoicing for multiple locations, reach out — we can help you and your software vendor prepare before the deadline.
---
See Also
Frequently Asked Questions
When does the mandatory Ship-to GSTIN requirement take effect?+
The requirement takes effect **1 August 2026**, per GSTN advisories dated 17 June and 20 June 2026. The go-live was deferred from the original date of 15 June 2026 following industry representations on system readiness (advisory dated 9 June 2026).
What do I enter for Ship-to GSTIN if the party is unregistered?+
Enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. You cannot leave the field blank; it is mandatory whenever Ship-to details are present in the invoice.
What happens if my software is not updated before 1 August 2026?+
IRN and e-way bill generation for Bill-to/Ship-to documents will fail because the mandatory Ship-to GSTIN is missing. Without a valid IRN, you cannot issue a compliant e-invoice under Rule 48(4), CGST Rules 2017, which can halt your invoicing and dispatch process.
Is this a change in GST law or just a technical API change?+
This is a **technical change to the GSTN API specifications only**. The underlying GST obligations under Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) of the CGST Rules 2017 remain unchanged. The change tightens which data fields are mandatory in the API payload.
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 reaches destination. Using it is optional and a matter of housekeeping convenience.
I issue only B2C invoices with no Ship-to location. Am I affected?+
The mandatory Ship-to GSTIN requirement applies **only where Ship-to details are present** in the invoice. If your invoices carry no separate Ship-to party (e.g., consumer sales to a single location), this specific API change has limited direct impact — but confirm your software still generates IRNs correctly after the vendor's API update.
Who must comply with this API change?+
All taxpayers covered by **mandatory e-invoicing under Rule 48(4)** (aggregate annual turnover above ₹5 crore in any financial year from 2017-18 onwards) who issue Bill-to/Ship-to invoices, and all taxpayers generating e-way bills for movement of goods under Rule 138.
What is a "Bill-to/Ship-to" transaction?+
A Bill-to/Ship-to transaction occurs when goods are invoiced to one party (the buyer) but physically delivered to a different location or party (the Ship-to address). Examples: stock transfers, third-party drop-ship deliveries, consignments to project sites, or inter-branch transfers.
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.