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 parties must be marked as 'URP'. ERP and GSP vendors must update integration before the go-live 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 — GSTN API amendment effective 1 August 2026. Source: GSTN advisory 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 enforcing a mandatory Ship-to GSTIN) field in the e-Invoice (IRP) and e-Way Bill API payloads. Wherever a document carries Ship-to details—separate from Bill-to—the Ship-to GSTIN must be populated. If the ship-to party is unregistered, you must enter "URP" (Unregistered Person); leaving the field blank will cause IRN and e-way bill generation to fail.
This is a technical API change, not a change in GST law, but its operational impact is high. A failed IRN means you cannot issue a valid tax invoice, and a failed e-way bill blocks goods movement. If your ERP, GSP, or e-invoicing software is not updated in time, your dispatch operations will halt.
What is changing on 1 August 2026
Per GSTN advisories dated 17 June 2026 (read with 20 June 2026):
- Ship-to GSTIN becomes mandatory when Ship-to details are present in a Bill-to/Ship-to transaction (goods delivered to a party different from the buyer).
- URP handling: If the ship-to party has no GST registration, enter "URP" in the Ship-to GSTIN field. The field cannot be left blank or populated with a zero or placeholder.
- Voluntary E-Way Bill Closure feature: Taxpayers can now close an active e-way bill before its validity expires, once the consignment reaches its destination—reducing stale e-way bills on the portal.
Why 1 August 2026, and not earlier
These API enhancements 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 firm operative date; plan integration testing and vendor coordination well before it.
Who is affected
- Mandatory e-invoicing taxpayers under Rule 48(4), CGST Rules 2017: registered persons with aggregate annual turnover above ₹5 crore in any financial year from FY 2017-18 onwards.
- All taxpayers using e-way bills, particularly those with Bill-to/Ship-to structures: stock transfers to branches, third-party deliveries, drop-ship orders, and consignments to project sites.
- ERP vendors, GSPs, and e-invoicing software providers must update API integration payloads and test thoroughly before the cut-over.
Key point: IRN and e-way bill generation will fail if the mandatory Ship-to GSTIN is missing or incorrectly formatted after 1 August 2026, halting invoice issuance and goods movement.
The 3-step action plan before 1 August 2026
Step 1: Confirm vendor readiness. Contact your ERP, GSP, or e-invoicing software vendor this week. Request confirmation that they will ship the updated API integration (Ship-to GSTIN + URP handling) by mid-July 2026, and request a sandbox test environment date.
Step 2: Audit and clean Ship-to master data. Review all Bill-to/Ship-to locations in your system. Ensure the correct, active GSTIN is captured for every registered ship-to party; flag unregistered parties clearly so the system can auto-insert "URP" on IRN and e-way bill generation.
Step 3: Run end-to-end UAT. Before 1 August 2026, generate at least one Bill-to/Ship-to e-invoice with IRN and one corresponding e-way bill on the updated APIs in a sandbox environment. Confirm both generate without error and that the API payload includes the Ship-to GSTIN or URP correctly. Do not wait until 1 August to discover a failure.
Statutory backdrop
- E-invoicing (IRN): Rule 48(4), CGST Rules 2017—notified registered persons must prepare invoices by uploading specified particulars to the IRP and obtaining an Invoice Reference Number.
- E-way bill: Rule 138, CGST Rules 2017—e-way bill is required for movement of goods where the consignment value exceeds ₹50,000.
- Aggregate Annual Turnover (AATO): determines e-invoicing applicability. A separate GSTN advisory (dated 1 July 2026) revised the AATO amendment window for FY 2025-26 to 1–31 July 2026.
I'm CA Harun Raaj, Visakhapatnam. If your business operates Bill-to/Ship-to invoicing or e-way bills, reach out to confirm your systems are ready for this API change before 1 August 2026.
---
See Also
Frequently Asked Questions
From when is Ship-to GSTIN mandatory in e-Invoice and e-Way Bill APIs?+
Per GSTN advisories dated 17 June 2026 and 20 June 2026, the Ship-to GSTIN becomes mandatory in the e-Invoice (IRP) and e-Way Bill APIs from **1 August 2026**. This applies whenever a document carries Ship-to details separate from Bill-to details. 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 not GST-registered, you must enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. The field cannot be left blank, and leaving it empty will cause IRN and e-way bill generation to fail.
Will IRN and e-way bill generation fail if my software is not updated by 1 August 2026?+
Yes. For Bill-to/Ship-to documents, if the Ship-to GSTIN field is missing or incorrectly formatted after 1 August 2026, both IRN generation and e-way bill generation will fail. Without a valid IRN, you cannot issue a valid e-invoice. Contact your ERP, GSP, or e-invoicing software vendor immediately to confirm the updated API payload will be live before 1 August 2026.
Is this a change in GST law or only a technical change to the GSTN portal?+
This is a **technical API change only**, 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. The GSTN is simply tightening the mandatory field requirements in the API payload for Bill-to/Ship-to transactions.
Do I need 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 goods have reached the destination—a convenience to reduce stale e-way bills on the portal. You are not required to use it.
I only issue B2C invoices with no separate Ship-to party. Am I affected?+
The mandatory Ship-to GSTIN requirement applies **only where Ship-to details are present** in the transaction. If your B2C documents carry no separate ship-to party, this specific API change has limited direct impact. However, confirm with your software vendor that IRN generation continues to work correctly after the API update on 1 August 2026.
What is the deadline for ERP and GSP vendors to update their systems?+
The GSTN API changes take effect on **1 August 2026**. Vendors must have updated API integration live well before this date to allow taxpayers adequate time for testing. You should confirm your vendor's update timeline by mid-July 2026 and request sandbox access for UAT.
Which taxpayers must comply with mandatory e-invoicing and are therefore affected?+
Registered persons with an aggregate annual turnover above ₹5 crore in any financial year from FY 2017-18 onwards are subject to mandatory e-invoicing under Rule 48(4), CGST Rules 2017. All taxpayers using e-way bills for goods movement, particularly those with Bill-to/Ship-to structures, are affected by the Ship-to GSTIN requirement.
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.