GSTN Advisory Announces New e-Way Bill Rules: What Taxpayers and Transporters Must Know

The Goods and Services Tax Network ('GSTN'), through its advisory dated 20th May 2026, has introduced three significant changes to the e-Way Bill ('Electronic-Way Bill') system, which are scheduled to come into effect from 15th June 2026 [1]. The proposed changes include the mandatory reporting of the 'Ship-To GSTIN' in Bill-To/Ship-To transactions; the introduction of a voluntary e-Way Bill Closure facility; and updates to the APIs ('Application Programming Interfaces') for ERP ('Enterprise Resource Planning') vendors and system integrators. The proposed changes are aimed at enhancing transparency, improving operational efficiency, and ensuring smoother compliance within the GST framework.

Background of the e-Way Bill Mechanism

The e-Way Bill system was introduced after the implementation of GST to replace India's fragmented state-wise waybill mechanism with a unified digital system for movement of goods. The e-Way Bill was implemented for interstate transportation from 1st April 2018 and later was extended to intrastate movement as well on

Legally, the e-Way Bill is grounded in Section 68 of the CGST Act, 2017 read with Rule 138 of the CGST Rules, 2017 which together govern its generation, validity, and enforcement. E-Way bill is mandatory for any goods movement above Rs. 50,000 in value.

Under Section 122(1)(xiv) of the CGST Act, 2017, a taxable person who transports any taxable goods without being accompanied by the prescribed documents (an e way bill being one such document) is liable to pay a penalty of Rs. 10,000 or an amount equal to the tax evaded, whichever is higher.

Why GSTN Needed These Reforms

Until now, the e-Way Bill system has mainly focused on the transportation stage of goods: once an e-Way Bill was generated and the goods were dispatched, there was no digital mechanism to confirm whether the goods actually reached their destination. In practice, an e-Way Bill had only two outcomes it either expired automatically after its validity period ended or was cancelled if generated incorrectly because there was no formal process to confirm successful delivery. The validity period itself, under Rule 138, depends on the distance to be travelled and the nature of the cargo being transported.

The prescribed validity periods are as follows:

Once the validity period expired, the e-Way Bill became inactive irrespective of whether delivery had actually taken place. This created significant gaps in reconciliation and transaction verification because authorities could track the commencement of movement but not its completion. In transactions involving warehouses, distributors, third-party logistics providers, and Bill-To / Ship-To arrangements, identifying the actual consignee also became difficult. The 2026 reforms directly address these longstanding gaps in delivery verification and transaction traceability.

Major Changes Coming into Effect from 15th June 2026

The GSTN advisory dated 20th May 2026 introduces three changes, these changes will be deployed in production by June 15th, 2026:

Mandatory 'Ship To GSTIN' Requirement

One of the most significant changes introduced by GSTN is the mandatory capture of the 'Ship To GSTIN' in Bill-To / Ship-To transactions. Under the revised system, where the consignee is a registered person under GST, their GSTIN must compulsorily be entered in the 'Ship To GSTIN' field while generating the e-Way Bill. In cases where the consignee is not registered under GST, the value URP ('Unregistered Person') must be entered instead. The portal will not process or generate the e-Way Bill unless either of these details is duly provided.

A Bill-To / Ship-To transaction refers to a situation where the invoice is issued to one party, while the goods are physically delivered to another party or location. Such arrangements are commonly seen in drop-shipping models, distributor and dealer networks, third-party logistics arrangements, and job-work transactions. Earlier, the 'Ship To GSTIN' field was optional, and businesses could generate e-Way Bills without disclosing the GSTIN of the actual consignee. This often resulted in a lack of clarity regarding the real destination of the goods and created difficulties in tracking the movement of goods within the GST system. By making this field mandatory, GSTN aims to improve transparency, strengthen traceability of goods in transit, and reduce the possibility of tax evasion or misuse of the e-Way Bill mechanism.

Introduction of the e-Way Bill Closure Facility

The second major reform introduces a voluntary e-Way Bill Closure facility. Until now, an e-Way Bill had no formal conclusion. Once generated, it remained active in the system until its validity period expired, with no mechanism to record that the goods have actually been delivered. The newly introduced Closure facility addresses this gap by allowing the e-Way Bill to be formally closed once delivery is completed.

The closure of an e-Way Bill may be initiated by the supplier, recipient, transporter involved in the transaction, or a driver/authorised person whose mobile number has been provided for closure. Closure may be carried out by entering the specific e-Way Bill number or through the date-wise selection facility available on the portal. A registered mobile number may also be provided at the time of generating the e-Way Bill specifically for closure purposes, although this facility is presently voluntary. The registered mobile number enables OTP-based authentication, allowing the driver or authorised person handling the delivery to complete the closure process. Such mobile number may also be added subsequently during vehicle updation, consolidated e-Way Bill operations, or extension of validity.

The flowchart below illustrates the e-Way Bill closure process and identifies the persons authorised to initiate the closure.

An API-based closure facility has also been provided for system integrators and API users. For this purpose, the e-Way Bill number, closure date, and remarks are required to be transmitted. The e-Way Bill can be closed on the same day as the delivery or on the immediately succeeding day.

API updates for ERP vendors and system integrators

Another important reform of the advisory relates to API modifications released by NIC in the Sandbox environment. Sandbox environment is a safe isolated an highly controlled space used for testing and experimentation, where ERP vendors, GSPs, ASPs, and system integrators test compatibility and carry out necessary software modifications.

Today, many businesses generate e-Way Bills directly through ERP and accounting software instead of manually using the portal. These systems are integrated with the GST infrastructure through APIs, enabling the automated and bulk generation of e-Way Bills. In this regard, NIC has proposed several necessary changes, which are scheduled to be deployed in the production environment by 15th June 2026. All stakeholders have been strictly instructed to implement the required changes within the prescribed time frame. The advisory further outlines the steps that stakeholders must follow to become familiar with the new system changes and ensure smooth compliance.

From Suppliers to Transporters: Who Needs to Take Action?

• Suppliers and manufacturers must update ERP or billing software to capture Ship To GSTIN at the invoice stage. Drop-shipping and job-work businesses need an immediate process review before 15th June.
• Transporters and drivers must register driver mobile numbers on the portal. Drivers need to understand the OTP-based Closure step a formal part of delivery completion, even if currently voluntary.
• Registered recipients will find their GSTIN captured in more e-way bills. They can also now initiate Closure themselves once goods are received giving them a delivery record too.
• ERP vendors and API integrators must complete Sandbox testing and configuration changes before 15th June. Any delay risks breaking bulk e-way bill generation for all clients simultaneously at the point of rollout.
• Mandatory Ship-to GSTIN ensures that every stage of a multi-party transaction can be tracked and matched with GST returns. The Closure facility provides a verified and time-recorded proof of delivery, making it much more difficult to deny receipt of goods. It also helps reduce mismatches between invoices, transportation records, and GST filings.

Conclusion

To conclude, the new changes introduced by GSTN in the e-Way Bill system are aimed at making the movement of goods more transparent and easier to track. The mandatory 'Ship To GSTIN' requirement will help identify the actual delivery location of goods, while the new Closure facility will allow businesses and transporters to officially confirm delivery. At the same time, ERP vendors and system integrators will need to update their software and APIs before 15th June 2026 to ensure smooth compliance. These changes may require some adjustments in business processes, especially for suppliers, transporters, and logistics operators, but they are expected to reduce mismatches, improve record-keeping, and strengthen overall GST compliance in the long run.

After all better tracking leads to better compliance.

[1]Advisory to Taxpayers and Stakeholders – Enhancements in the e-Way Bill (EWB) Portal