Voluntary e-Way Bill Closure: What Businesses Need to Know Before 1 August 2026

Based on the GSTN FAQ document "FAQs on Voluntary Closure of e-Way Bill: Business Scenarios, API Impact and Portal Behaviour," dated 01.07.2026.

If you generate, receive, or transport goods under GST, you've likely dealt with the e-Way Bill (EWB) system for years but only for starting a movement. Soon, you'll also be able to formally end one. The Goods and Services Tax Network (GSTN) has rolled out a new Voluntary e-Way Bill Closure facility, and it's set to go live on 1 August 2026.

Here's a plain-language breakdown of what it is, who it affects, and what your team should do to get ready.

What exactly is changing?

Until now, an e-Way Bill's life cycle ended one of three ways: it stayed Active, it was Cancelled, or it simply expired. There was no formal way to say "this delivery happened, and the EWB has served its purpose."

The new closure facility fixes that gap. It lets a supplier, recipient, transporter, or an authorised driver mark an EWB as closed once the goods have actually reached their destination creating a clean digital record that the movement is complete.

Importantly, this is optional, not compulsory. Businesses that don't use it won't face any penalty; the EWB will simply continue behaving as it does today until it expires.

When can an EWB be closed?

GSTN recommends closing an EWB on the date of delivery, or the day right after. But the system is more flexible than that in practice the closure window stays open until one day after the EWB's validity expires.

The one hard rule: the closure date you enter (i.e., the actual date goods were received) must fall somewhere between the EWB's generation date and its expiry date.

Example: An EWB generated on 20 June 2026, valid till 30 June 2026, where goods are actually delivered on 25 June 2026 can be closed any time from 25 June up to 1 July 2026 (one day past expiry).

Who can close an EWB?

Four categories of people are authorised to close an EWB:

• Supplier - Logs into the portal and closes the EWB after dispatch is confirmed as delivered.
• Recipient - Logs into the portal and closes the EWB after receiving the goods.
• Transporter - Logs into the portal and closes the EWB after completing delivery.
• Driver / authorised person - Uses a portal-based mobile-number closure facility, no separate login needed.

For the driver route to work, a mobile number must already be linked to the EWB. That's optional at the time of generation, but can also be added later during vehicle updates, consolidated EWB actions, or validity extensions.

Two ways to close on the portal

Once logged in, businesses get two options under the e-Way Bill section:

• EWB-wise closure - pick a specific e-Way Bill number and close it individually.
• Date-wise closure - pull up all EWBs generated on a particular date and close the eligible ones together. Useful for transporters juggling several shipments dispatched on the same day.

What does this mean for API users and ERP-integrated businesses?

If your systems talk to the GST network through APIs, here's what to build for:

• A closure API is available, requiring just three inputs: the EWB number, the closure date, and remarks (capped at 100 characters).
• Bulk, date-wise closure is not supported via API only through the portal for now.
• There is currently no API to retrieve a list of closed EWBs, date-wise or otherwise.
• The Get EWB Details API doesn't yet return a "Closed" status or closure date that's expected to come later, once the feature stabilises.
• APIs cannot capture a driver's mobile number, and a driver cannot close an EWB through the API that path remains portal-only.
• The API response won't tell you who closed the EWB there's no "closed by" field yet.

In short: for now, treat closure as primarily a portal-and-simple-API feature, not a fully-featured bulk-automation one.

Does this touch e-Invoicing?

No. The e-Invoice API only handles generating an EWB (whether standalone, alongside an IRN, or via the "e-Way Bill by IRN" route). Everything that happens to the EWB afterwards including closure is handled entirely by the EWB APIs. So your e-Invoicing integration doesn't need any changes because of this update.

A temporary grace period read the fine print

This is arguably the most important part for compliance teams: during the initial stabilisation period, closing an EWB doesn't lock it down.

• The EWB's visible status will still show as Active, Cancelled, or Discarded there's no separate "Closed" tag in the system yet (though one is planned).
• Even after closure, users can still update the transporter, change vehicle details, or extend validity actions you'd normally expect to be blocked once a shipment is "done."

Why allow this? GSTN has framed it as a deliberate cushion so that trade and system users aren't caught off guard while everyone adjusts to the new workflow. But it's explicitly temporary once the system stabilises, these post-closure actions will be restricted, and a formal "Closed" status will be introduced.

Closure vs. Cancellation vs. Expiry - don't confuse the three

• Cancellation - The EWB was wrongly generated, or the movement never happened. Used before or shortly after generation, subject to existing rules.
• Expiry - The EWB's validity period has simply run out. Automatic, based on time.
• Closure - The movement happened and delivery is confirmed. Used anytime after actual delivery, voluntarily.

They're not interchangeable, and the FAQ is careful to draw this line closure is a record of successful completion, not a correction or a lapse.

Common business scenarios

• A supplier shipping from Chennai to Bengaluru closes the EWB themselves once delivery is confirmed.
• A recipient who receives goods closes the EWB on their end to log completion.
• A transporter running a Pune-Hyderabad route closes it through portal login post-delivery.
• A driver whose mobile number is linked to the EWB opens the portal's mobile-number closure screen and closes it after dropping off the goods.
• An ERP-integrated business fires off the closure API with the EWB number, date, and remarks as part of its automated delivery workflow.
• A transporter handling multiple deliveries on one date uses date-wise closure to clear several EWBs in one sitting.

What should you actually do before 1 August 2026?

• Taxpayers - Set up an internal process to close EWBs promptly after delivery, if you plan to use the facility.
• Transporters - Train operations staff on EWB-wise, date-wise, and driver-based closure.
• Drivers / authorised persons - Make sure your mobile number is linked, and know how to use the portal closure screen.
• ERP / GSP / ASP / API integrators - Build the closure API call (EWB number, date, remarks) into your delivery-confirmation workflow.
• Everyone - Remember that post-closure edits are allowed for now but expect that flexibility to tighten once the system stabilises.

The bottom line

Voluntary e-Way Bill Closure is a genuinely useful housekeeping tool it gives businesses a clean way to mark deliveries as done in a system that previously had no concept of "finished." It's optional, low-friction to adopt, and the API footprint required is small. The one thing to watch closely is the stabilisation-period leniency: the rules around what you can still edit after closing an EWB will get stricter, so it's worth building your processes around the eventual, tighter version of the rules rather than today's relaxed one.

This article is a plain-language summary prepared for knowledge-sharing purposes, based on the official GSTN FAQ document dated 01.07.2026. For binding compliance decisions, always refer to the original GSTN circular/FAQ and applicable GST law.