Ship-to GSTIN Mandatory in e-Invoice & e-Way Bill APIs: 1 August 2026
From 1 August 2026, GSTN makes Ship-to GSTIN a mandatory field in e-Invoice and e-Way Bill APIs wherever Ship-to details are present. Unregistered parties must be marked as 'URP'. Your ERP and invoicing software must be updated before this date or IRN 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 17 June 2026, 20 June 2026, and 9 June 2026 published on 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 APIs. Where a document carries Ship-to details — meaning the goods are delivered to a party different from the invoice buyer — that Ship-to GSTIN must be populated in full. If it is missing, IRN generation and e-way bill generation will fail, and you cannot issue a valid e-invoice. This is a technical portal change, not a change in GST law, but its operational impact is critical because it affects the point where invoices are actually generated and validated.
What has changed
Per GSTN advisories dated 17 June 2026 and 20 June 2026:
- Ship-to GSTIN is now mandatory whenever Ship-to details are present in the invoice or consignment document. The field cannot remain blank.
- Unregistered ship-to parties must be coded as "URP" (Unregistered Person) in the API payload. This is the prescribed alternative when no GSTIN exists.
- 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. This reduces stale e-way bills on the portal but is entirely optional.
The go-live was originally scheduled for 15 June 2026 but was deferred to 1 August 2026 (advisory dated 9 June 2026) following industry representations about ERP and GSP readiness. Treat 1 August as the firm deadline.
Who is affected
The 3-step action plan before 1 August 2026
- Contact your ERP, GSP, or e-invoicing software vendor immediately. Confirm the delivery timeline for the updated API payload that handles Ship-to GSTIN and URP coding. Request a dedicated test environment and test date.
- Audit and cleanse your Ship-to master data. Identify all Bill-to/Ship-to transaction patterns in your business (branch transfers, consignments, project deliveries, third-party logistics). Ensure the correct GSTIN is captured for each ship-to location. For unregistered recipients, flag them clearly so your system auto-populates "URP" when generating the IRN or e-way bill.
- Run a sandbox test before the cut-over. Generate at least one complete Bill-to/Ship-to invoice and one e-way bill on the updated APIs in your test environment. Confirm both IRN generation and e-way bill generation succeed. Do not wait until 1 August to discover a failure.
Key point: Ship-to GSTIN becomes a mandatory API field from 1 August 2026; failure to populate it will cause IRN and e-way bill generation to fail, halting your invoice issuance.
Statutory backdrop
E-invoicing (IRN): Rule 48(4) of the CGST Rules 2017 requires a notified class of registered persons to prepare invoices by uploading specified particulars to the IRP and obtaining an Invoice Reference Number. This rule is unchanged; only the API field structure is being tightened.
E-way bill: Rule 138 of the CGST Rules 2017 requires an e-way bill for movement of goods of consignment value exceeding ₹50,000. The mandatory Ship-to GSTIN field applies to the e-way bill API payload from 1 August 2026.
Aggregate Annual Turnover (AATO): The threshold that determines e-invoicing applicability. Note that GSTN issued a separate advisory (No. 666, dated 1 July 2026) revising the AATO amendment notification window for FY 2025-26 to 1–31 July 2026. If your AATO status is borderline, confirm your compliance calendar in parallel with this API update.
What this is NOT
This is not a change to GST law, GST rates, or invoice content rules. The underlying obligations under Rule 48(4) and Rule 138 remain unchanged. It is a tightening of the technical requirements for the API payloads that feed the GSTN's systems — a housekeeping change that formalizes what many compliant businesses already do (capturing the ship-to party's GSTIN or marking them as unregistered).
I'm CA Harun Raaj, Visakhapatnam. If your business issues Bill-to/Ship-to invoices or is uncertain about your e-invoicing readiness before 1 August, reach out to our GST team so we can review your setup and help you avoid a costly IRN generation failure.
---
See Also
Frequently Asked Questions
What is Ship-to GSTIN and when does it become mandatory?+
Ship-to GSTIN is the GST registration number of the party to whom goods are physically delivered — which may differ from the invoice buyer. Per GSTN advisory dated 17 June 2026, it becomes mandatory in the e-Invoice (IRP) and e-Way Bill APIs from 1 August 2026 whenever Ship-to details are present in the document. If the field is missing, IRN and e-way bill generation will fail.
What do I enter if my ship-to party is not GST-registered?+
Enter "URP" (Unregistered Person) in the Ship-to GSTIN field as prescribed in the GSTN advisory dated 20 June 2026. Do not leave the field blank; the system requires either a valid GSTIN or the URP code.
Why was the implementation date moved from 15 June to 1 August 2026?+
Per GSTN advisory dated 9 June 2026, the go-live was deferred from 15 June to 1 August 2026 to allow ERP vendors, GSPs, and taxpayer systems adequate time to integrate the API changes. 1 August 2026 is now the firm implementation date.
What happens if my software is not updated by 1 August 2026?+
For invoices and e-way bills with Ship-to details, IRN generation and e-way bill generation will fail because the mandatory Ship-to GSTIN field will be missing or invalid. This will prevent you from issuing a valid e-invoice and complying with GST law, so update your software before the deadline.
Is the e-way bill closure feature mandatory?+
No. The new voluntary e-way bill closure feature introduced per the 20 June 2026 advisory allows you to close an active e-way bill before its validity expires once goods reach the destination. It is optional and purely a convenience for housekeeping.
Am I affected if I only issue B2C invoices with no separate ship-to address?+
The mandatory Ship-to GSTIN requirement applies only where Ship-to details are present in the document. If your invoices carry no separate ship-to party (all goods go to the buyer at one address), this specific API change has limited impact. However, confirm your software still generates IRNs 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 e-Invoice and e-Way Bill API field requirements. The underlying legal obligations under Rule 48(4) and Rule 138 of the CGST Rules 2017 are unchanged; only the API payload structure is being tightened.
What should I do before 1 August 2026 to prepare?+
Contact your ERP, GSP, or e-invoicing vendor to confirm they will release the updated API payload by 1 August 2026. Cleanse your master data to ensure Ship-to GSTIN is captured for all Bill-to/Ship-to locations, and mark unregistered parties. Run a sandbox test of IRN and e-way bill generation in your updated system before the cut-over date.
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.