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 whenever ship-to details are present. Businesses must update ERP and e-invoicing software, clean master data, and test Bill-to/Ship-to workflows before the deadline to avoid IRN generation failures.
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. API changes per GSTN advisory dated 17 June 2026 and 20 June 2026 — Effective: 1 August 2026. Source: https://www.gst.gov.in/newsandupdates. Last reviewed by CA Harun Raaj: January 2025.
From 1 August 2026, the GSTN is tightening mandatory fields in its e-Invoice (IRP) and e-Way Bill system APIs. Wherever a transaction includes Ship-to details (a delivery address different from the billed-to party), the Ship-to GSTIN) becomes a mandatory field in both 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 — halting the issuance of valid tax invoices.
This is a technical portal change, not a change in GST law itself — but its operational impact is substantial because it sits at the exact point where invoices are electronically 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 Bill-to/Ship-to transactions (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 has reached its destination — a housekeeping convenience that reduces 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 system readiness, the GSTN deferred the go-live to 1 August 2026 (advisory dated 9 June 2026). Treat 1 August 2026 as the operative date and plan integration testing well in advance.
Who is affected
Key point: Ship-to GSTIN becomes a mandatory API field from 1 August 2026 whenever ship-to details are present in a Bill-to/Ship-to invoice or e-way bill.
The 3-step action plan before 1 August 2026
- Contact your ERP, GSP or e-invoicing vendor this week. Confirm they will ship the updated API payload (Ship-to GSTIN + URP handling) before 1 August 2026, and secure a test date for your instance.
- Audit and clean your Ship-to master data. Ensure the correct GSTIN is captured for every ship-to location; clearly mark genuinely unregistered parties so your system can auto-insert "URP" when required.
- Run a UAT or sandbox test of at least one Bill-to/Ship-to invoice and one e-way bill on the updated APIs before the cut-over date. A failed IRN on 1 August will halt your invoice issuance and goods dispatch.
Statutory backdrop
- E-invoicing (IRN): Rule 48(4), CGST Rules 2017 — specified registered persons must obtain an Invoice Reference Number by uploading invoice particulars to the Invoice Registration Portal.
- E-way bill: Rule 138, CGST Rules 2017 — e-way bill required for inter-state or intra-state movement of goods where consignment value exceeds ₹50,000.
- Applicability threshold: determined by Aggregate Annual Turnover (AATO); note the separate GSTN advisory on AATO amendment windows.
Practical implications for three common scenarios
Drop-ship or third-party delivery: Your Bill-to customer is Company A (GST-registered), but goods are shipped to Company A's project site or end customer (Company B, also registered). Company B's GSTIN must now be populated in the Ship-to field; IRN generation will fail without it.
Stock transfer to branches: You are moving goods from your Head Office to a branch location (unregistered in GST, or separately registered). If the branch is unregistered, enter "URP". If separately registered, use its GSTIN.
B2C with delivery to sub-dealer: You invoice a registered retailer, but goods are physically shipped to an end consumer (unregistered). The Ship-to field must show "URP".
I'm CA Harun Raaj, Visakhapatnam. If you manage Bill-to/Ship-to invoicing, stock transfers, or third-party deliveries, reach out to discuss how to prepare your workflows and data 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 a mandatory field in both the e-Invoice (IRP) and e-Way Bill APIs with effect from **1 August 2026**, wherever ship-to details are present in the transaction. The go-live was originally scheduled for 15 June 2026 but was deferred to 1 August 2026 to allow ERP and GSP vendors time to update their systems.
What do I enter in the Ship-to GSTIN field if the ship-to party is unregistered under GST?+
If the ship-to party is unregistered, you must enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. The field cannot be left blank. You should configure your ERP or e-invoicing software to auto-insert "URP" for parties you have flagged as unregistered in your master data.
Is this change a modification to GST law or only a technical API update?+
This is a **technical API change**, not a change to GST law or tax rules. The underlying obligations under Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) of the CGST Rules, 2017 remain unchanged. Only the mandatory fields required in the GSTN's API payloads are being tightened.
What happens if my ERP is not updated before 1 August 2026?+
If your ERP or e-invoicing software is not updated by 1 August 2026, IRN and e-way bill generation will fail for any Bill-to/Ship-to transaction where the Ship-to GSTIN is missing. Without a valid IRN, you cannot issue a valid e-invoice, which can halt your invoice issuance and goods dispatch.
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 option that allows you to manually close an active e-way bill before its validity expires, once the consignment has reached its destination. You can continue issuing and managing e-way bills as before.
Am I affected if I only issue B2B invoices with no separate ship-to location?+
The mandatory Ship-to GSTIN requirement applies **only where ship-to details are present** in the transaction. If your invoices carry no separate ship-to party (Bill-to and Ship-to are the same), this specific change will have limited direct impact, though you should still confirm your software generates IRNs correctly after the API update.
Which taxpayers are covered by mandatory e-invoicing and thus affected by this API change?+
Taxpayers with an aggregate annual turnover exceeding ₹5 crore in any financial year from 2017-18 onwards are covered by mandatory e-invoicing under Rule 48(4), CGST Rules 2017. Any taxpayer generating e-way bills for movement of goods, especially those using Bill-to/Ship-to structures, must also update their systems.
What is the specific action I should take before 1 August 2026?+
Contact your ERP, GSP or e-invoicing vendor to confirm they will ship updated APIs supporting Ship-to GSTIN and "URP" by 31 July 2026; audit and clean your Ship-to GSTIN master data; and run a user acceptance test (UAT) of at least one Bill-to/Ship-to invoice and one e-way bill on the updated APIs before the cut-over date.
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.