Enhancements in the e-Way Bill (EWB) Portal

1.  It is hereby informed that certain functional enhancements are being implemented in the e-Way Bill (EWB) system with a view to strengthening data integrity, improving traceability of goods movement, and enabling system-driven closure of transactions. All taxpayers, transporters, ERP/API integrators, and other stakeholders are requested to take note of the following changes and initiate necessary system readiness measures. 

2. Mandatory Capture of “Ship To GSTIN” in Bill-To/Ship-To Transactions a) 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. b) Where the consignee is an unregistered person, the value “URP” shall be entered in the “Ship To GSTIN” field. 

3. Introduction of Voluntary e-Way Bill Closure Facility 

• A new e-Way Bill Closure facility has been introduced in the e-Way Bill system on voluntary basis to enable closure of the e-Way Bill once delivery of goods is completed. 

• The e-Way Bill may be closed by: 

a) Supplier 

b) Recipient 

c) Transporter involved in the transaction 

d) Driver or authorized person whose mobile number has been provided for closure 

• For suppliers, recipients, and transporters, the e-Way Bill Closure option is available after login under the e-Way Bill section of the portal. 

• Closure can be performed: 

a) e-Way Bill-wise, or 

b) Date-wise 

• A mobile number may be entered at the time of e-Way Bill generation specifically for closure purposes. Currently, this option is voluntary in nature.

• If required, the mobile number can also be updated during:

a) Vehicle updation 

b) Consolidated e-Way Bill operations

c) Extension of validity

• The mobile number–based closure facility has been provided under the Search option on the e-Way Bill Common Portal. All active e-Way Bills linked to the concerned mobile number are displayed, enabling closure by the authorized person.

• e-Way Bills can be closed on: 

a) The same day of delivery, or 

b) The immediately succeeding day 

• An API has also been provided for system integrators and API users. For closure through API, the following details are required to be transmitted:

a) e-Way Bill number

b) Closure date

c) Remarks 

• API and System Integration Readiness 

1. Necessary API changes have been released by NIC in the Sandbox environment. The proposed changes will be deployed in production by 15th June,2026. All stakeholders are requested to make necessary changes at their end accordingly.

2. All ERP vendors, GSPs, ASPs, and system integrators are advised to: 

i. Access the updated API specifications. 

ii. Undertake testing in the Sandbox environment. 

iii. Carry out suitable configuration changes at their end. 

3.  Action Required by Stakeholders All concerned stakeholders are advised to: 

i. Familiarize themselves with the revised data entry requirements and closure workflow. 

ii. Update internal processes, ERP configurations, and user manuals accordingly. 

iii. Conduct internal testing and user awareness sessions. 

iv. Ensure compliance from the notified date of implementation.