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. Unregistered ship-to parties must be marked as 'URP'. Your ERP and e-invoicing software must be updated before this date, or IRN and e-way bill generation will fail.
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, available at https://www.gst.gov.in/newsandupdates. Last reviewed by CA Harun Raaj: January 2025.
From 1 August 2026, the GSTN is enforcing a mandatory Ship-to GSTIN) field in the e-Invoice (IRP) and e-Way Bill system APIs. Whenever a Bill-to/Ship-to transaction is recorded—that is, when goods are delivered to a location different from the invoice buyer—the Ship-to GSTIN must be populated 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, which blocks you from issuing a valid tax invoice.
This is a technical portal change, not a change in law, but its operational impact is critical because it directly affects the point where invoices are issued.
What is changing
Per the GSTN advisory dated 17 June 2026 (read with the advisory dated 20 June 2026):
- Ship-to GSTIN becomes mandatory when Ship-to details are present in an invoice or consignment. In a Bill-to/Ship-to transaction, the Ship-to GSTIN must be included in the IRN and e-Way Bill API payloads.
- Unregistered ship-to party? Enter "URP" (Unregistered Person) in the Ship-to GSTIN field. The field cannot be left blank.
- New voluntary E-Way Bill Closure feature allows you to close an active e-way bill before its validity expires, once the consignment reaches its destination—a housekeeping option to reduce open or expired e-way bills on the portal.
When this takes effect and why the date moved
These API changes 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 firm and plan integration testing well ahead of it.
Who is affected
Key point: If Ship-to details are present in your transaction but the updated API is not live in your software, IRN and e-way bill generation will fail and you cannot issue a valid e-invoice or move goods legally.
Three-step action plan before 1 August 2026
- Contact your ERP, GSP, or e-invoicing vendor this week. Confirm they will release the updated API payload (Ship-to GSTIN + URP handling) before 1 August 2026 and get a concrete test date from them.
- Audit and clean your Ship-to master data. Ensure the correct GSTIN is captured for every ship-to location in your system. Flag genuinely unregistered ship-to parties so your system can auto-populate 'URP' without manual intervention.
- Run User Acceptance Testing (UAT) on sandbox. Generate at least one Bill-to/Ship-to invoice and one e-way bill using the updated APIs before the cut-over date, so a failed IRN doesn't halt your dispatches on 1 August.
Statutory backdrop
- 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 — An 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 each financial year.
I'm CA Harun Raaj, Visakhaputnam. If your business is affected by this API change or you need help ensuring your e-invoicing and e-way bill systems are ready, reach out to discuss your GST compliance setup.
---
See Also
Frequently Asked Questions
Is the Ship-to GSTIN mandate a change in GST law or a technical portal change?+
It is a technical portal change to the GSTN's e-Invoice and e-Way Bill APIs. 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 are being tightened to require Ship-to GSTIN where Ship-to details are present.
What happens if my ERP or e-invoicing software is not updated by 1 August 2026?+
For Bill-to/Ship-to transactions where Ship-to details are present, IRN generation and e-way bill generation may fail because the mandatory Ship-to GSTIN field is missing. Without a valid IRN, you cannot issue a valid e-invoice or legally move goods that require an e-way bill.
What should I enter in the Ship-to GSTIN field if the ship-to party is unregistered under GST?+
Enter 'URP' (Unregistered Person) in the Ship-to GSTIN field. The field cannot be left blank. URP is the prescribed code to handle unregistered consignees 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 is a convenience option to close an e-way bill before its validity expires, once goods have reached the destination. You are not required to use it.
Am I affected by this change if I only issue B2C invoices with no separate ship-to location?+
The mandatory Ship-to GSTIN applies only where Ship-to details are present. If your invoices do not carry a separate ship-to party (all goods delivered to the buyer's address), this specific change has limited operational impact. However, confirm that your e-invoicing software still generates IRNs correctly after the API update.
Why was the go-live date moved from 15 June 2026 to 1 August 2026?+
Following industry representations on ERP and GSP readiness to integrate the updated APIs, the GSTN deferred the go-live from 15 June to 1 August 2026 (advisory dated 9 June 2026). The new date is firm.
What should I do right now to prepare for the 1 August 2026 cut-over?+
Contact your ERP, GSP, or e-invoicing vendor to confirm their update timeline. Audit and clean your Ship-to GSTIN master data, flagging unregistered parties for 'URP'. Before 1 August, run User Acceptance Testing (UAT) on sandbox to generate a test Bill-to/Ship-to invoice and e-way bill using the updated APIs.
Which registered persons are required to use e-invoicing and therefore affected by this API change?+
Registered persons whose aggregate annual turnover is above ₹5 crore in any financial year from 2017-18 onwards are covered by the mandatory e-invoicing regime under Rule 48(4), CGST Rules, 2017. Any such person issuing Bill-to/Ship-to invoices must comply with the Ship-to GSTIN mandate from 1 August 2026.
Related Services
Based on this article's category and vertical tag, these services are the most relevant next steps.
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.