Ship-to GSTIN Mandatory in e-Invoice & e-Way Bill APIs from 1 August 2026
From 1 August 2026, the GSTN's e-Invoice and e-Way Bill APIs require Ship-to GSTIN as a mandatory field whenever ship-to details are present. Unregistered parties must be marked as URP. If your ERP or e-invoicing software is not updated, 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 17 June 2026, 20 June 2026, and 9 June 2026 at https://www.gst.gov.in/newsandupdates. Last reviewed by CA Harun Raaj: December 2024.
From 1 August 2026, the GSTN is tightening the e-Invoice (IRP) and e-Way Bill system APIs. Whenever a document carries Ship-to details, 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 — and without a valid IRN, you cannot issue a lawful tax invoice.
This is a technical API change, not a change in GST law — but its operational impact is critical because it sits at the moment your invoices are actually generated.
What is changing
Per the GSTN advisories dated 17 June 2026 and 20 June 2026:
- Ship-to GSTIN is 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 be left blank.
- New voluntary E-Way Bill Closure feature. You can now close an active e-way bill before its validity expires once the consignment reaches its destination — a practical housekeeping option to reduce expired e-way bills on the portal.
When it 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 the firm effective date and complete vendor integration testing well before it.
Key point: Ship-to GSTIN becomes mandatory in e-Invoice and e-Way Bill APIs from 1 August 2026; software not updated by this date will fail to generate IRNs for Bill-to/Ship-to transactions.
Who is affected
- Every taxpayer under mandatory e-invoicing under Rule 48(4), CGST Rules — currently those with aggregate annual turnover above ₹5 crore in any financial year from 2017-18 onwards.
- Any taxpayer generating e-way bills for movement of goods, especially those using Bill-to/Ship-to structures: stock transfers, drop-ship deliveries, consignments to project sites, or branch deliveries.
- ERP vendors, GSPs, and e-invoicing software providers, who must update API integration payloads to include Ship-to GSTIN validation and URP handling.
Action plan before 1 August 2026
- Contact your ERP/GSP/e-invoicing vendor immediately. Confirm they will release updated API payloads (Ship-to GSTIN + URP handling) well before 1 August 2026 and request a test window.
- Audit and clean your Ship-to master data. Ensure the correct GSTIN is captured for every ship-to location; clearly flag genuinely unregistered parties so the system can auto-insert "URP".
- Conduct sandbox testing. Generate at least one Bill-to/Ship-to invoice and one e-way bill on the updated APIs before 1 August 2026, so a failed IRN does not halt your business on the go-live date.
Regulatory context
E-invoicing / IRN: Rule 48(4), CGST Rules 2017 — specified registered persons must prepare invoices by uploading 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 with consignment value exceeding ₹50,000.
Aggregate Annual Turnover (AATO): Determines e-invoicing applicability. Note that GSTN separately manages the AATO amendment window annually; confirm your threshold status with your professional advisor.
I'm CA Harun Raaj, Visakhapatnam. If your business relies on Bill-to/Ship-to transactions or e-way bill generation, reach out to confirm your compliance readiness 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 the GSTN advisories dated 17 June 2026 and 20 June 2026, Ship-to GSTIN becomes a mandatory field in both the e-Invoice (IRP) and e-Way Bill API payloads with effect from **1 August 2026**, when a document contains Ship-to details. The original go-live date of 15 June 2026 was deferred to 1 August 2026 following industry representations on system readiness (advisory dated 9 June 2026).
What do I enter in the Ship-to GSTIN field if the party is unregistered under GST?+
If the ship-to party is unregistered under GST, you must enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. The field cannot be left blank; it is mandatory to explicitly mark unregistered recipients.
What happens if I don't update my ERP before 1 August 2026?+
For documents with Ship-to details, IRN generation and e-way bill generation will fail because the mandatory Ship-to GSTIN field is missing. Without a valid IRN, you cannot issue a valid e-invoice. This can disrupt your invoicing and dispatch operations from 1 August 2026.
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 goods reach the destination, but you are not obligated to use it.
Does this apply to B2C invoices with no separate ship-to party?+
The mandatory Ship-to GSTIN applies **where Ship-to details are present**. If your B2C documents carry no separate ship-to party, this specific change has limited direct impact. However, confirm with your software vendor that all IRN generation functions correctly after the API update on 1 August 2026.
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 GST obligations under Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) of the CGST Rules 2017 remain unchanged; only the API payload structure is being tightened.
Who must comply with the Ship-to GSTIN requirement?+
Every taxpayer covered by mandatory e-invoicing under Rule 48(4), CGST Rules (currently those with aggregate annual turnover above ₹5 crore in any prior financial year from 2017-18 onwards) and any taxpayer generating e-way bills for movement of goods must comply when their documents contain Ship-to details.
What should I do now to prepare for 1 August 2026?+
Contact your ERP, GSP, or e-invoicing software vendor this week to confirm their updated API release timeline. Clean your Ship-to master data to ensure correct GSINs are captured and unregistered parties are flagged. Conduct sandbox testing of Bill-to/Ship-to invoice and e-way bill generation 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.