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 parties must be marked as 'URP'. Businesses using Bill-to/Ship-to structures must update their ERP and e-invoicing software 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 — API implementation changes effective 1 August 2026. Source: GSTN advisories dated 17 June 2026, 20 June 2026, and 9 June 2026 at 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 API specifications. 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 without a valid IRN, you cannot issue a compliant tax invoice.
This is a technical portal change, not a change in GST law—but its operational impact is significant because it sits at the point where invoices are actually generated.
What is changing
Per the GSTN advisory dated 17 June 2026 (read with the advisory dated 20 June 2026), three API enhancements take effect from 1 August 2026:
Key point: Ship-to GSTIN is mandatory wherever bill-to and ship-to parties differ; unregistered parties require "URP" entry, not a blank field.
Timeline and why the date moved
These functionalities were originally scheduled for 15 June 2026. Following industry representations regarding ERP, GSP, and e-invoicing software readiness, the GSTN deferred the go-live to 1 August 2026 via advisory dated 9 June 2026. Treat 1 August 2026 as the operative date and plan integration testing and UAT well before it.
Who is affected
- Every taxpayer covered by mandatory e-invoicing under Rule 48(4) of the CGST Rules (currently: aggregate annual turnover above ₹5 crore in any financial year from 2017-18 onwards).
- Any taxpayer generating e-way bills for movement of goods under Rule 138, CGST Rules 2017 (consignment value exceeding ₹50,000)—especially those using Bill-to/Ship-to structures: stock transfers, third-party/drop-ship deliveries, consignments to project sites, and inter-branch movements.
- ERP, GSP, and e-invoicing software vendors, who must update their API integration code to include the Ship-to GSTIN field and handle the "URP" logic.
Action plan: three steps before 1 August 2026
Step 1: Vendor confirmation (this week). Contact your ERP, GSP, or e-invoicing software provider. Confirm they will ship the updated API payload (mandatory Ship-to GSTIN + URP handling) before 1 August 2026, and lock in a test/UAT date.
Step 2: Clean your master data. Audit and update your Ship-to location master data to ensure the correct GSTIN is captured for every ship-to address. For genuinely unregistered recipients, flag them in your system so it can auto-insert "URP" during invoice generation.
Step 3: Run sandbox testing. Before 1 August 2026, generate at least one Bill-to/Ship-to e-invoice and one e-way bill on the updated APIs in a test environment. Confirm both the IRN is generated successfully and the e-way bill is created without errors. This prevents dispatch halts on the go-live date.
Statutory context
E-invoicing requirement (Rule 48(4), CGST Rules 2017). Notified classes of registered persons must prepare invoices by uploading specified particulars to the Invoice Registration Portal (IRP) and obtaining an Invoice Reference Number (IRN). The Ship-to GSTIN field is now part of those specified particulars when applicable.
E-way bill requirement (Rule 138, CGST Rules 2017). An e-way bill is required for the movement of goods of consignment value exceeding ₹50,000. The updated API now mandates Ship-to GSTIN where ship-to details are supplied.
AATO thresholds. Aggregate Annual Turnover (AATO) determines e-invoicing applicability. Note that a separate GSTN advisory (No. 666, dated 1 July 2026) revised the AATO amendment window for FY 2025-26 to 1–31 July 2026, so businesses crossing the ₹5 crore threshold should confirm their compliance status before 1 August.
I'm CA Harun Raaj, Visakhapatnam. If your business uses Bill-to/Ship-to structures or relies on e-invoicing software, reach out to discuss your readiness for this API change.
---
See Also
Frequently Asked Questions
From when is Ship-to GSTIN mandatory in the e-invoice and e-way bill APIs?+
Per the GSTN advisory dated 17 June 2026, the Ship-to GSTIN becomes a mandatory field in the e-Invoice (IRP) and e-Way Bill APIs with effect from **1 August 2026**. This applies whenever ship-to details (i.e. a delivery address different from the buyer) are present in the invoice. The go-live was originally scheduled for 15 June 2026 but was deferred to 1 August 2026 following industry representations on software readiness.
What should 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; it must be populated with either a valid 15-digit GSTIN or "URP" to indicate an unregistered recipient.
What happens if I don't update my ERP or e-invoicing software before 1 August 2026?+
For Bill-to/Ship-to invoices where ship-to details are present, IRN generation and e-way bill generation may fail because the mandatory Ship-to GSTIN field is missing or improperly formatted. Without a valid IRN, you cannot issue a compliant e-invoice, which can halt your dispatch operations.
Is the E-Way Bill Closure feature mandatory?+
No. The E-Way Bill Closure feature introduced in the 20 June 2026 advisory is **voluntary**. It allows you to close an active e-way bill before its validity expires once the consignment reaches its destination, but using it is optional and for housekeeping purposes.
I only issue B2C invoices with no separate ship-to location. Am I affected by this change?+
The mandatory Ship-to GSTIN applies only **where ship-to details are present**—i.e. when the delivery address differs from the buyer's address. If your B2C invoices have no separate ship-to party, this specific API change has limited direct impact. However, confirm with your software vendor that IRN generation still functions correctly after the API update.
Is this a change in GST law or GST rates?+
No. This is a **technical change to the GSTN's API specifications**, not a change in GST law or tax liability. 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.
Which taxpayers are required to use the updated e-Invoice API?+
Taxpayers covered by **mandatory e-invoicing** under Rule 48(4), CGST Rules 2017, are required to use the updated API. Currently, this includes all registered persons whose aggregate annual turnover is above ₹5 crore in any financial year from 2017-18 onwards. The separate GSTN advisory (No. 666, dated 1 July 2026) allows AATO amendments for FY 2025-26 during 1–31 July 2026.
What should I do now to prepare for this change?+
Take three steps: (1) Contact your ERP, GSP, or e-invoicing software vendor this week and confirm they will ship the updated API payload before 1 August 2026; (2) Audit and clean your Ship-to master data to ensure correct GSINs are captured, and flag unregistered recipients so the system can auto-insert "URP"; (3) Run sandbox/UAT testing of at least one Bill-to/Ship-to e-invoice and e-way bill on the updated APIs before the deadline to catch any integration issues.
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.