The GST Network has finalised two major e-Way Bill changes — a mandatory Ship-to GSTIN field for Bill-to/Ship-to transactions, and a new voluntary closure facility — now going live on 1 August 2026 after a deferral from the original mid-June date. Here’s exactly what changes, who is exempt, and how to get your systems ready.
What’s Changing CONFIRMED — 1 AUGUST 2026
GSTN has finalised two significant enhancements to the e-Way Bill ecosystem, effective in production from 1 August 2026:
1. Mandatory Ship-to GSTIN
In Bill-to/Ship-to and “Combination” transactions where the Ship-to party is registered, capturing the Ship-to GSTIN becomes mandatory. Where the consignee is unregistered, “URP” must be entered instead.
2. Voluntary EWB Closure Facility
A new, optional facility lets suppliers, recipients, transporters, or drivers formally close an e-Way Bill once delivery is complete — creating a system record that movement has ended.
In one line: If your business routinely bills one GSTIN but ships to a different registered location — branch, project site, or third-party consignee — you now must capture that destination’s GSTIN explicitly on the e-Way Bill, not just its address.
Timeline: Why the Deadline Moved
| Date | Event |
|---|---|
| 20 May 2026 | Original GSTN advisory announces mandatory Ship-to GSTIN capture and the voluntary closure facility; production go-live proposed for 15 June 2026 |
| 9 June 2026 | Advisory No. 663 extends the implementation timeline from 15 June to 1 August 2026, citing the need for system changes, testing, and ERP/API readiness across stakeholders |
| 17 June 2026 | Advisory No. 664 clarifies that Ship-to GSTIN is also mandatory in the e-Way Bill by IRN API specifically |
| 1 July 2026 | GSTN issues two detailed FAQ sets — one on Voluntary EWB Closure, one on Bill-to/Ship-to transactions, exports, and API impact |
| 1 August 2026 | Both changes go live in production; e-Way Bills failing the new validations will not generate |
The six-week deferral reflects genuine complexity: this change touches ERP systems, GST Suvidha Providers, Application Service Providers, and private Invoice Registration Portals simultaneously, all of whom needed sandbox testing time before a hard production cutover.
Mandatory Ship-to GSTIN — The Details
Until now, a business could generate an e-Way Bill using largely just the billing entity’s GSTIN, often leaving the actual physical destination — the Ship-to location — unverified or simply duplicated from the Bill-to details. From 1 August 2026, that changes materially.
When it applies
The Ship-to GSTIN mandate applies specifically to Bill-to/Ship-to transactions and “Combination” transactions — where the billing party and the physical delivery destination are different registered entities or locations.
When it doesn’t apply
Where the billing address and the shipping address are the same, the mandatory field does not apply — this remains a Regular transaction under the existing flow.
Unregistered consignees
Where the Ship-to party is not registered under GST, the value “URP” (Unregistered Person) must be entered in the Ship-to GSTIN field — the portal will accept this in place of a GSTIN.
System validations applied
GSTN will validate the authenticity of the Ship-to GSTIN, verify that its State Code matches both the GSTIN and the declared PIN Code, and reject any attempt to enter the same GSTIN in both Bill-to and Ship-to fields.
Locked once set via IRN
For B2B/SEZ transactions, Ship-to details entered at the time of IRN (e-Invoice) generation cannot subsequently be overridden when the e-Way Bill is generated through the IRN route — invoice and transport particulars must stay consistent.
Privacy note: GSTN has clarified that the Ship-to GSTIN will not be printed on the e-Way Bill itself, will not be displayed to taxpayers or transporters on-screen, and will not be returned through GET e-Way Bill APIs — the field exists for departmental traceability and audit trail, not for general disclosure.
Who This Doesn’t Apply To
Same Bill-to and Ship-to address
Standard transactions where the billing and delivery address are identical continue under the existing Regular transaction flow — no new mandatory field applies.
Export transactions
Exports are excluded from the strict IRN-lock rule. GSTN permits modification of Ship-to details during e-Way Bill generation for exports, recognising the different logistics involved — and “URP” may continue to be used where there is no domestic registered consignee.
Manual portal entry (with training)
Businesses generating e-Way Bills manually through the portal aren’t blocked by API changes, but still need to train staff on the new mandatory field and correct use of “URP” before 1 August 2026.
Impact on ERP, GSPs, ASPs & API Users
This is fundamentally an API-level and database-level change, which means the burden falls heavily on systems, not just on data-entry staff.
| API / System | Change |
|---|---|
| e-Invoice API | Field ShipDtls.Gstin made conditionally mandatory — required wherever Ship-to details are furnished |
| e-Way Bill by IRN API | New field Gstin added under ExpShipDtls and made mandatory; optional field TrdNm (Trade Name) also added |
| Standalone Generate EWB API | Ship-to GSTIN mandatory for Ship-to and Combination transactions; call fails if missing, wrongly provided in Regular/Bill-from/Dispatch-from cases, or identical to Bill-to GSTIN |
| EWB Closure API | New API requires e-Way Bill number, closure date, and remarks to register voluntary closure |
If the field is left blank, the API call fails
- Businesses relying on ERP or accounting software (Tally, SAP, Oracle, Zoho Books, and similar) must confirm their vendor has released and deployed the update before 1 August 2026.
- Direct API integrators should access the NIC Sandbox environment now — both the mandatory field and the closure API are already available there for testing.
- Untested deployments risk e-Invoice or e-Way Bill generation failures on go-live day, which can stall dispatch for high-volume businesses.
The New Voluntary EWB Closure Facility
Separately from the Ship-to GSTIN mandate, GSTN is introducing a facility to formally “close” an e-Way Bill once the goods have actually been delivered — addressing the long-standing gap where e-Way Bills simply expired without any system record of successful delivery.
Who can close an e-Way Bill: the supplier, the recipient, the transporter, the driver, or any authorised person whose mobile number is registered against the transaction. Closure can be performed EWB-wise or date-wise, and — while currently voluntary with no penalty for not closing — it is a meaningful step toward cleaner records, particularly useful in disputes over whether delivery was actually completed.
Compliance Risk If You Get It Wrong
Beyond the immediate risk of generation failure, there is a second-order compliance risk worth flagging clearly: once the mandatory Ship-to GSTIN regime is live, any mismatch between the Ship-to GSTIN declared on the e-Way Bill and the recipient’s GSTIN on the underlying tax invoice creates a documented discrepancy.
This is not a paperwork-only risk
- A Ship-to GSTIN / invoice recipient mismatch can attract detention proceedings under Section 129 of the CGST Act during transit checks.
- In more serious cases, it can expose the business to confiscation proceedings under Section 130.
- Because the field is now system-validated (State Code vs. GSTIN vs. PIN Code), errors that previously went unnoticed will now surface at the point of generation, not later at a roadside check or during audit.
Readiness Checklist
- Identify every transaction pattern in your business where Bill-to and Ship-to locations differ — branches, project sites, third-party consignees, drop-shipment arrangements
- Update master data to hold a verified Ship-to GSTIN (or “URP” where genuinely unregistered) for each such destination
- Contact your ERP/accounting software vendor and confirm the release status and deployment timeline for the Ship-to GSTIN update
- If using direct API integration, log into the NIC Sandbox and test both the mandatory Ship-to GSTIN field and the new EWB Closure API
- Reconfirm that no transaction currently duplicates the Bill-to GSTIN into the Ship-to field — this will now be rejected by the portal
- Verify Ship-to PIN codes and State Codes are accurate and internally consistent with the corresponding GSTIN for every regular destination
- Review export transaction workflows separately, since Ship-to details remain modifiable at EWB generation for exports
- Train staff who generate e-Way Bills manually through the portal on the new mandatory field and correct “URP” usage
- Decide internally who is responsible for using the new voluntary EWB closure facility, and for which categories of shipment
- Cross-check tax invoices against Ship-to GSTIN entries for a sample of recent transactions to pre-empt Section 129/130 exposure before go-live
- Complete full testing well before 1 August 2026 — avoid making last-minute changes once live business operations depend on the new flow
Quick FAQs
Does the Ship-to GSTIN mandate apply to all e-Way Bills?
No. It applies only to Bill-to/Ship-to and Combination transactions where the Ship-to party is registered. Where the billing and shipping address are the same, the mandatory field does not apply.
What do we enter if the consignee genuinely has no GSTIN?
Enter “URP” (Unregistered Person) in the Ship-to GSTIN field — the portal is designed to accept this value in place of an actual GSTIN.
Can we change the Ship-to GSTIN after generating the e-Invoice (IRN)?
For B2B/SEZ transactions, no — Ship-to details entered at IRN generation cannot be overridden when the e-Way Bill is subsequently generated through the IRN route. Export transactions are an exception and permit modification at the EWB generation stage.
Is closing an e-Way Bill after delivery mandatory?
No, it is currently voluntary, and there is no legal penalty for not closing an e-Way Bill after delivery. It is, however, a useful practice for maintaining a clean system record of completed movement.
What happens if our ERP isn’t updated in time?
If the Ship-to GSTIN field is left blank where mandatory, the API call will fail, and the e-Way Bill will not generate — this can directly stall dispatch. Confirm your vendor’s deployment timeline now, well ahead of 1 August 2026.