GSTN has announced two significant functional changes to the e-Way Bill (EWB) portal — mandatory Ship-To GSTIN capture and a new voluntary EWB Closure facility. Production deployment is scheduled for 15 June 2026. All taxpayers, transporters, ERP vendors, GSPs, and ASPs must prepare their systems now.
Why Is GSTN Upgrading the EWB System?
The Goods and Services Tax Network (GSTN), in its Advisory No. 661 dated 20 May 2026, has announced key functional enhancements to the e-Way Bill portal. These changes are driven by a clear mandate: strengthen data integrity across the supply chain, improve traceability of goods movement, and enable systematic closure of completed transactions.
Since the launch of the e-Way Bill system, a persistent challenge has been the lack of accurate destination data — particularly in Bill-To/Ship-To scenarios where goods are invoiced to one party but physically delivered to another. This gap created discrepancies in GSTIN-level tracking, audit trails, and tax enforcement. Simultaneously, there was no formal mechanism for taxpayers to signal the completion of a delivery against a generated EWB, leaving a large number of "ghost" EWBs floating in the system even after goods were delivered.
The two enhancements announced by GSTN directly address these pain points.
The "Ship To GSTIN" field in Bill-To/Ship-To transactions will now be a required data element during EWB generation — closing a critical data gap.
A brand new facility enabling suppliers, recipients, transporters, and drivers to voluntarily close an EWB once delivery of goods is completed.
Mandatory Capture of "Ship-To GSTIN" in Bill-To/Ship-To Transactions
This is the more immediately impactful change for businesses involved in multi-party supply chains — particularly manufacturers, distributors, and e-commerce operators who regularly handle Bill-To/Ship-To transactions.
What Is a Bill-To/Ship-To Transaction?
A Bill-To/Ship-To scenario arises when the party to whom a tax invoice is raised (the Bill-To party) is different from the party to whom the goods are physically delivered (the Ship-To party). This is extremely common in:
- Dealer/distributor arrangements where an OEM invoices the dealer but goods go directly to the sub-dealer or end customer.
- Drop shipments arranged through e-commerce marketplaces.
- Procurement-on-behalf arrangements in large corporate groups.
- Export-oriented units where billing and physical delivery locations differ.
What Has Changed?
Under the revised EWB generation framework, the "Ship To GSTIN" field will be treated as a mandatory data element in all Bill-To/Ship-To transactions. Previously, this field was either absent or optional, leading to a situation where the actual recipient's GSTIN was not captured in the system.
In cases involving Bill-To/Ship-To scenarios, the field relating to the "Ship To GSTIN" shall now be captured as a mandatory data element during e-Way Bill generation.
— GSTN Advisory No. 661, dated 20 May 2026Special Rule for Unregistered Consignees
Where the party receiving the goods does not hold a GST registration (i.e., an unregistered person or consumer), taxpayers must enter the value "URP" (Unregistered Person) in the "Ship To GSTIN" field. This ensures the field is never left blank while distinguishing unregistered recipients from registered ones.
→ Registered consignee : Enter consignee's valid GSTIN
→ Unregistered consignee: Enter "URP"
→ Field left blank : ❌ EWB generation will FAIL
Why Does This Matter?
This change directly tightens the loop between e-Way Bill data and GSTR-1/GSTR-3B returns. By mandating Ship-To GSTIN, GSTN can now systematically cross-verify whether the declared recipient in the EWB matches the Input Tax Credit (ITC) claimed by that GSTIN in their returns. It also helps tax authorities track the physical movement of goods more accurately, making it harder for fraudulent transactions to go unnoticed.
| Scenario | Bill-To GSTIN | Ship-To GSTIN | Status |
|---|---|---|---|
| Goods billed and delivered to same party | Party's GSTIN | Same as Bill-To | Standard |
| Goods billed to A, delivered to B (registered) | A's GSTIN | B's GSTIN (mandatory) | New Rule |
| Goods delivered to unregistered consumer | Supplier's GSTIN | "URP" | New Rule |
| Drop-ship to dealer's customer | Dealer's GSTIN | Customer's GSTIN or URP | New Rule |
The second major enhancement is entirely new in concept — the introduction of a formal EWB Closure mechanism. Until now, there was no structured way in the EWB system for a taxpayer or transporter to signal that goods had been delivered and the EWB's purpose was fulfilled. This led to a proliferation of "open" EWBs in the system long after the underlying transactions were completed.
Who Can Close an EWB?
The closure facility has been made available to multiple parties involved in the supply chain:
1. Supplier — The party who generated the EWB and dispatched the goods.
2. Recipient — The party to whom the goods were delivered (the Bill-To party).- 3. Transporter — The logistics provider involved in the movement of goods.
- 4. Driver / Authorised Person — A driver or other authorised individual whose mobile number has been linked to the EWB at the time of generation for closure purposes.
How Can EWBs Be Closed? Three Methods Available
Method A — Portal Login (Logged-in Users)
For suppliers, recipients, and transporters, the EWB Closure option is available directly after logging in to the e-Way Bill Common Portal under the e-Way Bill section. Closure can be performed in two modes:
- EWB-wise closure:Search and close a specific e-Way Bill by its number.
- Date-wise closure:Close all EWBs generated on or before a specified date, useful for batch reconciliation at the end of the day.
Method B — Mobile Number-Based Closure (Drivers / Authorised Persons)
A mobile number may be entered at the time of EWB generation specifically for closure purposes. This is currently voluntary and can be updated during vehicle updation, consolidated EWB operations, or validity extension processes.
The mobile number-based closure facility has been placed under the Search option on the EWB Common Portal. All active EWBs linked to the concerned mobile number are displayed, enabling the authorised person (e.g., a delivery driver) to close them directly without needing to log in with a GSTN username.
Method C — API-Based Closure (System Integrators)
For businesses using ERP systems or API integrations, a dedicated API has been provided.
Important Time Rule for Closure
EWBs can only be closed:
- On thesame day of delivery, or
- On theimmediately succeeding day(i.e., the day after delivery).
This time restriction ensures that the closure is tied as closely as possible to the actual delivery event, preserving the integrity of the system.
The EWB Closure facility is currently voluntary. However, GSTN's broader objective of enabling "system-driven closure of transactions" strongly suggests that mandatory EWB closure may be introduced in future phases. Early adoption now will prepare your business for that eventuality.
API & System Integration — What You Need to Do
The National Informatics Centre (NIC) has already released the updated API specifications in the Sandbox environment. Production deployment is confirmed for 15 June 2026. This gives ERP vendors, GSPs, ASPs, and system integrators approximately three weeks to test and certify their integrations.
Implementation Timeline at a Glance
GSTN publishes the official advisory announcing the two enhancements — mandatory Ship-To GSTIN and EWB Closure facility.
NIC releases updated API specs in the Sandbox environment. ERP vendors, GSPs, and ASPs can begin integration testing immediately.
Businesses must update their internal ERP configurations, train users, revise workflows, and conduct UAT (User Acceptance Testing) for both changes.
GSTN deploys both changes in production. Ship-To GSTIN becomes a mandatory field. EWB Closure goes live for all users. Non-compliant EWB generation attempts will fail.
Action Points by Stakeholder Category
| Stakeholder | Actions Required | Priority |
|---|---|---|
| Registered Taxpayers (Suppliers) | Familiarise with Ship-To GSTIN field; update master data with GSTINs of Ship-To parties; train invoicing staff; start using EWB Closure on delivery. | High |
| Recipients / Consignees | Communicate GSTIN to suppliers for accurate EWB generation; leverage closure facility to confirm receipt of goods. | Medium |
| Transporters / Logistics | Ensure drivers' mobile numbers are captured during EWB generation for closure purposes; train drivers on mobile-based closure workflow. | High |
| ERP Vendors | Update Ship-To GSTIN as mandatory field in EWB generation forms; integrate EWB Closure API; release patch before 15 June 2026; notify all customers. | Critical |
| GSPs & ASPs | Test updated API specs in Sandbox; carry out configuration changes; ensure production readiness; coordinate with client businesses on timelines. | Critical |
| Tax Practitioners / CAs | Advise clients on the mandatory Ship-To GSTIN requirement; help update EWB generation procedures; review implications for ITC matching. | Medium |
Frequently Asked Questions
1. Is the EWB Closure facility mandatory from 15 June 2026?
No. As per the advisory, the EWB Closure facility is being introduced on a voluntary basis. However, GSTN's stated objective of "enabling system-driven closure of transactions" suggests this may become mandatory in a future phase. Businesses are encouraged to adopt it now to build compliance readiness.
2. What happens if I forget to close an EWB on the delivery day?
EWBs can be closed on the same day of delivery or on the immediately succeeding day. If neither window is used, the EWB will remain in "open" status in the system. While there is no immediate penalty (given the facility is currently voluntary), unresolved open EWBs may create reconciliation challenges in future audits or when GSTN introduces mandatory closure.
3. What if the Ship-To party is a consumer with no GST registration?
In such cases, enter "URP" (Unregistered Person) in the Ship-To GSTIN field. This is the prescribed approach for all unregistered consignees and must not be left blank.
4. Can the closure mobile number be changed after EWB generation?
Yes. The mobile number linked for closure purposes can be updated during vehicle updation, consolidated EWB operations, or validity extension. This provides flexibility for situations where a different driver takes over a delivery mid-route.
5. Where can ERP vendors access the updated API specifications?
The updated API specifications are available in the Sandbox environment of the EWB Common Portal managed by NIC. Vendors are advised to access these immediately and complete testing well before the 15 June 2026 production cutover. For implementation queries, GSTN's designated helpdesk channels should be contacted.
6. Does the Ship-To GSTIN need to match GSTR-1 data?
Yes, the intent of the Ship-To GSTIN requirement is precisely to enable cross-verification between EWB data and GST returns (GSTR-1 and GSTR-3B). Businesses should ensure that the GSTIN entered as Ship-To GSTIN is the party actually claiming ITC on those goods, as mismatches will likely trigger notices or flags in the GSTN reconciliation system.
What This Means for the GST Ecosystem
GSTN's Advisory No. 661 represents a meaningful step forward in the maturation of India's e-Way Bill infrastructure. The mandatory Ship-To GSTIN requirement closes one of the most significant data gaps in the current system — the inability to track who actually receives goods as distinct from who is billed for them. Combined with the voluntary EWB Closure facility, the overall health of transaction data on the portal is set to improve substantially.
For businesses, the immediate priority is ensuring that ERP systems are updated, master data for Ship-To GSTINs is in order, and teams are trained on the new workflows before 15 June 2026. For transporters and logistics companies, activating the mobile number-based closure mechanism for drivers represents a simple yet effective way to bring supply chain closure data into the GST system in real time.
Tax professionals and GST consultants should proactively reach out to their clients — particularly those in multi-party supply chain arrangements — to assess the impact and ensure seamless compliance from day one of production rollout.
The enhancements are being implemented to strengthen data integrity, improve traceability of goods movement, and enable system-driven closure of transactions.
— GSTN Advisory No. 661, 20 May 2026This blog is based on GSTN Advisory No. 661 dated 20 May 2026 — "Advisory to Taxpayers and Stakeholders – Enhancements in the e-Way Bill (EWB) Portal." For the complete official document, refer to tutorial.gst.gov.in or the EWB Common Portal. For implementation queries, contact the GST Helpdesk at the designated helpdesk channels provided by GSTN.
