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 when ship-to details are present. Unregistered parties must be marked as "URP". Businesses using Bill-to/Ship-to structures must update ERP and software integrations 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 — 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. Where 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 by then, IRN and e-way bill generation can fail — and a failed IRN means you cannot issue a valid tax invoice.
This is a technical/portal change, not a change in GST law — but its operational impact is high because it affects 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):
- Ship-to GSTIN is now mandatory when Ship-to details are present. In a Bill-to/Ship-to transaction (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. The field cannot be left blank.
- For unregistered ship-to parties, enter "URP" (Unregistered Person). This explicitly codes the receiving party as not GST-registered, and prevents API rejection.
- 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 — a housekeeping option to reduce open/expired e-way bills on the portal.
When it takes effect
These changes 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 implementation date and plan integration testing well ahead of it.
Who is affected
Key point: The Ship-to GSTIN mandate applies only where a document contains separate ship-to details; Bill-to-only invoices are unaffected.
The 3-step action plan before 1 August 2026
- Talk to your ERP/GSP/e-invoicing vendor this week. Confirm they will ship the updated API payload (Ship-to GSTIN + URP handling) before 1 August 2026, and agree a test date. Ask for a signed commitment if you rely on their software for daily invoicing.
- Clean your Ship-to master data. Ensure the correct GSTIN is captured for every ship-to location in your system. Flag genuinely unregistered parties so the system can auto-populate "URP" and prevent blank-field errors.
- Run a UAT / sandbox test of at least one Bill-to/Ship-to invoice and one e-way bill on the updated APIs before 1 August, so a failed IRN doesn't halt your dispatches on go-live day.
Statutory backdrop
- E-invoicing / IRN: Rule 48(4), CGST Rules 2017 — specifies that a notified class of 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 — an e-way bill is required for movement of goods of consignment value exceeding ₹50,000.
- Aggregate Annual Turnover (AATO) threshold: determines e-invoicing applicability; note the separate GSTN advisory revising the AATO amendment window for FY 2025-26.
No law change, only API tightening
The underlying obligations under Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) remain unchanged. This is a technical refinement to the GSTN's API specifications to ensure data completeness for e-way bill closure and shipment tracking. The Ship-to GSTIN field has always been part of the invoice schema; it is now being enforced as mandatory (rather than optional) where ship-to details are present.
I'm CA Harun Raaj, Visakhapatnam. If your business relies on Bill-to/Ship-to invoicing or e-way bills and you need help validating your software readiness before 1 August 2026, reach out to discuss your setup.
---
See Also
Frequently Asked Questions
From when is Ship-to GSTIN mandatory in 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 wherever a document contains Ship-to details (i.e., Bill-to and Ship-to are different parties).
What do I enter if my ship-to party is not GST-registered?+
Enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. The field cannot be left blank; URP is the coded way to indicate an unregistered receiving party. This coding prevents API rejection and ensures e-way bill and IRN generation proceed correctly.
Is this a change in GST law or just a technical portal update?+
This is a **technical/portal change**, not a change in GST law or compliance obligations. Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) of the CGST Rules 2017 remain unchanged. The GSTN is only tightening the API field requirements to enforce data completeness.
What happens if my ERP software is not updated before 1 August 2026?+
For Bill-to/Ship-to documents, IRN and e-way bill generation may fail because the mandatory Ship-to GSTIN field is missing from the API payload. Without a valid IRN, you cannot issue a valid e-invoice. Vendors must update their software before the go-live date.
Why was the implementation date moved from 15 June to 1 August 2026?+
The GSTN deferred the go-live from 15 June to 1 August 2026 (per advisory dated 9 June 2026) following industry representations on ERP and GSP system readiness. The August date is now firm.
Is the new E-Way Bill Closure feature mandatory?+
No — the **E-Way Bill Closure feature is voluntary**. It allows you to close an active e-way bill before its validity expires once the consignment has reached its destination. Using it is optional and is a housekeeping convenience.
Do I need to update my software if I only issue B2C invoices with no separate ship-to?+
The mandatory Ship-to GSTIN applies **only where Ship-to details are present** in a document. If your B2C invoices carry no separate ship-to party (Bill-to and Ship-to are the same), this API change has limited direct impact. However, confirm with your software vendor that your IRN generation works correctly after the API update.
Who must comply with this Ship-to GSTIN mandate?+
Every taxpayer covered by **mandatory e-invoicing** under **Rule 48(4)** (currently: aggregate annual turnover above ₹5 crore in any FY from 2017-18 onwards) and any taxpayer generating e-way bills, especially those using Bill-to/Ship-to structures for stock transfers, third-party deliveries, or consignments to project sites.
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.