Voluntary e-Way Bill Closure from 1 August 2026: Everything You Need to Know

GSTN has introduced a new Voluntary e-Way Bill Closure facility, and it goes live from 1 August 2026. In simple terms, it gives the supplier, the recipient, the transporter, or the driver a way to formally mark an e-Way Bill as closed once the goods have actually reached their destination.

This GSTN New Update 2026 touches almost everyone in the movement chain, from the person who generated the EWB to the ERP team pushing closure data through an API. If your business regularly ships goods worth more than Rs. 50,000 across state lines, this change is going to show up in your compliance routine sooner or later, whether you use it or not.

This guide covers what the Voluntary e-Way Bill Closure facility actually does, who is allowed to use it, how the e-Way Bill Portal and API sides work, and what your team should check before 1 August 2026 arrives.

What is the Voluntary e-Way Bill Closure Facility?

The Voluntary e-Way Bill Closure facility lets a supplier, recipient, transporter, or driver mark an e-Way Bill as closed after goods are delivered. It records that the movement is complete inside the GSTN system. It is a tracking feature, not a compliance requirement, and using it stays entirely optional.

Right now, once an EWB is generated, the system has no clean way of knowing whether the goods actually reached the recipient. It just sits there until it expires or gets cancelled. This new e-Way Bill Closure option fixes that gap by letting the parties involved confirm delivery has happened.

It does not replace anything in your existing e-Way Bill process. Generation, extension, and cancellation all continue exactly as before. Closure is simply an additional step you can take once the consignment has arrived.

When Will the New Facility Start?

The revised implementation date for this GSTN July 2026 Update is 1 August 2026. Sandbox testing is already open for taxpayers and API users who want to try the closure workflow before it goes live on the production e-Way Bill Portal.

If your business runs a lot of interstate movement, it is worth testing the sandbox now rather than waiting for the last week of July.

Is e-Way Bill Closure Mandatory?

No. Closure of an EWB is entirely voluntary. Nothing stops you from running your business exactly as you do today, generating, extending, and cancelling e-Way Bills without ever touching the closure option.

GSTN introduced this e-Way Bill Closure Guide feature purely to improve movement tracking on its end. Businesses that adopt it early get cleaner records of completed deliveries, but there is no penalty, notice, or compliance risk for skipping it altogether.

Who Can Close an e-Way Bill?

A supplier, recipient, transporter, driver, or any authorised person can close an e-Way Bill once delivery is complete. Suppliers, recipients, and transporters do this after logging into the portal. Drivers and authorised persons need a registered mobile number to access the same closure option.

Notice that the driver row comes with a condition. A driver can only close an EWB if their mobile number was registered against it, either at the time of generation or later, during a vehicle update.

When Should You Close an e-Way Bill?

An e-Way Bill should ideally be closed on the day of delivery, or the day right after. The closure window does not end there, though. GSTN allows closure up to one day after the EWB's validity has expired, as long as the delivery date falls within the original generation-to-expiry period.

The date you enter for closure has to be the actual delivery date, and that date must fall somewhere between when the EWB was generated and when it expired.

Here's a working example. Say a transporter generates an EWB on 12 August 2026, and its validity runs out on 22 August 2026. If the goods are actually delivered on 18 August 2026, the closure option stays open from 18 August right through to 23 August 2026, which is one day past expiry. Miss that window and you simply lose the option to close that particular EWB, nothing else changes.

How to Close an e-Way Bill on the Portal

Method 1: EWB-wise Closure

EWB-wise closure means picking one specific e-Way Bill number and closing it individually after confirming delivery. It works well when you only have a handful of EWBs to close on a given day.

1.     Log in to the e-Way Bill Portal with your credentials.

2.     Open the e-Way Bill section and select the closure option.

3.     Select the specific EWB you want to close.

4.     Enter the actual delivery date.

5.     Add remarks, up to 100 characters.

6.     Submit to mark the EWB as closed.

Method 2: Date-wise Closure

Date-wise closure is built for volume. Instead of hunting for one EWB number at a time, you pull up every eligible EWB generated on a particular date and close whichever ones have actually been delivered, all in the same session. Transporters running multiple consignments a day will find this the faster route.

Can Drivers Close the e-Way Bill?

Yes, drivers can close an e-Way Bill directly through the portal, provided their mobile number is linked to that EWB. Once linked, every active EWB tied to that number shows up under the portal's search option, ready to be closed after delivery.

Providing a mobile number at the time of generation is optional. If you want the driver to be able to close the EWB themselves, though, that number has to be on record. It can also be added later, during a vehicle update, a consolidated EWB step, or a validity extension, so you are not stuck if it was missed at the start. You can check your GST filing status in the same portal ecosystem once your compliance calendar syncs with these EWB updates.

One thing worth flagging: drivers cannot close an EWB through the API. That path is a portal only, at least for now.

API Changes for ERP Users

GSTN has added a new Closure API for ERP and system integrators. It needs three fields: the EWB number, the closure date, and remarks. There is no bulk, date-wise closure API yet, and remarks are capped at 100 characters.

●        A new Closure API has been introduced for system integrators and ERP teams.

●        The API requires the EWB number, closure date, and remarks.

●        Bulk date-wise closure through the API is not available. Each closure call is EWB-specific.

●        Remarks are capped at 100 characters, so keep them short and specific.

●        There is currently no API to retrieve EWBs that have already been marked as closed, and the API response does not indicate who performed the closure.

If your development team is planning the integration, budget extra time for this last point. You will need your own internal log of who closed what, since the API will not hand that back to you.

What Happens After Closing an e-Way Bill?

During this initial stabilisation period, closing an EWB does not lock it down. You can still update the vehicle, update the transporter, or extend validity even after marking it closed. GSTN has confirmed these permissions will get tighter once the system settles.

This is a temporary relaxation, not a permanent design choice. GSTN has been fairly direct about the fact that once the closure module stabilises, these post-closure actions will be restricted.

Difference Between Closure, Cancellation and Expiry

Closure happens after delivery and is optional. Cancellation applies when an EWB was generated incorrectly or the movement never took place, and it follows specific rules. Expiry is automatic, triggered by the system once the validity period runs out.

 These three terms get mixed up constantly in client queries, so it helps to keep this distinction handy. Closure confirms something happened. Cancellation says something should not have been generated at all. Expiry is just the clock running out.

Does This Impact e-Invoice?

No, e-Invoice remains unaffected. IRN generation, the e-Invoice API, and the combined IRN-plus-EWB flow all continue to work exactly as before. Voluntary e-Way Bill Closure only touches the e-Way Bill side of things.

The e-Invoice API is limited to generating the e-Way Bill in the first place. Everything that happens afterward, including closure, runs through the separate EWB APIs. So whether your EWB was generated standalone, alongside an IRN, or through the e-Way Bill by IRN route, it can still be closed the same way.

Real Business Examples

Example 1: Supplier closes EWB after delivery

A Chennai-based fabric exporter ships a consignment to a buyer in Bengaluru. Once the buyer confirms receipt, the supplier logs in and closes the EWB the same evening.

Example 2: Transporter closes EWB

A logistics company carrying machinery parts from Pune to Hyderabad completes the delivery and closes the EWB through its own portal login, without waiting on the supplier or recipient to act.

Example 3: Driver closes EWB

A driver whose mobile number was registered at the time of EWB generation delivers the goods, opens the portal's search option using that number, and closes the relevant EWB directly from the road.

Example 4: ERP software closes EWB through API

A mid-sized manufacturer with an ERP-integrated GST setup automates the process entirely. Once a delivery is confirmed in the ERP, a scheduled job pushes the EWB number, closure date, and remarks to GSTN through the Closure API.

What Businesses Should Do Before 1 August 2026

Before the rollout, update your ERP for the new Closure API, train staff on the portal steps, inform your transporters, and register driver mobile numbers wherever driver-side closure will be used.

●        Update your ERP to support the new Closure API fields.

●        Train staff who handle logistics and compliance on both closure methods.

●        Inform transporters so they know closure is available and optional.

●        Test the sandbox API before the production rollout.

●        Prepare an internal SOP for when and how EWBs get closed.

●        Register driver mobile numbers wherever driver-side closure will actually be used.

If you are updating internal workflows anyway, it is a reasonable moment to also review how this fits alongside your regular GST return filing schedule, so the two processes do not end up running on separate tracks. For businesses that want their SOP checked against current compliance requirements, professional legal guidance can help make sure the internal process actually holds up.

Key Highlights of the GSTN Update

●        Starts from 1 August 2026.

●        Completely voluntary, with no penalty for not using it.

●        New Closure API for ERP and system integrators.

●        Full portal support for supplier, recipient, and transporter logins.

●        Driver support through registered mobile numbers.

●        Date-wise closure for handling multiple EWBs together.

●        EWB-wise closure for single, specific EWBs.

●        A separate Closed status is proposed for a future update, once the module stabilises.

Frequently Asked Questions

Q1: Is Voluntary e-Way Bill Closure mandatory in 2026?

No. It is completely optional. Businesses can continue generating, extending, and cancelling EWBs exactly as before, without ever using the closure option.

Q2: What is the implementation date for e-Way Bill Closure?

The revised implementation date is 1 August 2026. Sandbox testing is already available for businesses and API users who want to try it beforehand.

Q3: Who can close an e-Way Bill?

The supplier, the recipient, the transporter, and the driver or authorised person can all close an EWB, provided the driver's or authorised person's mobile number is registered against it.

Q4: Can a transporter close an e-Way Bill?

Yes. A transporter can log in to the e-Way Bill Portal and close the EWB after delivery, using either EWB-wise or date-wise closure.

Q5: Can a driver close an e-Way Bill without portal login credentials?

A driver still uses the portal, but through a mobile number based search rather than a full login. Their registered mobile number needs to be linked to the EWB first.

Q6: What is EWB-wise closure and date-wise closure?

EWB-wise closure lets you close one specific e-Way Bill at a time. Date-wise closure lets you view and close multiple eligible EWBs generated on a particular date in a single session.

Q7: When should you close an e-Way Bill after delivery?

Ideally on the day of delivery or the day after. The system keeps the closure option open until one day after the EWB's validity expires, as long as the delivery date falls within the original validity window.

Q8: Is there an API available for e-Way Bill Closure?

Yes. GSTN has introduced a Closure API that requires the EWB number, closure date, and remarks. Bulk date-wise closure through the API is not supported yet.

Q9: What is the character limit for closure remarks?

Closure remarks are limited to a maximum of 100 characters, whether entered on the portal or submitted through the API.

Q10: Will a Closed status appear immediately on the EWB?

Not during the initial stabilisation period. The existing status framework of Active, Cancelled, and Discarded continues for now, though closure details are recorded in the background. A separate Closed status is planned for later.

Q11: Is e-Way Bill Closure the same as cancellation?

No. Cancellation applies when an EWB was generated wrongly or the movement never happened. Closure applies after delivery has genuinely been completed.

Q12: Can you extend e-Way Bill validity after closure?

Currently, yes, as a temporary relaxation during the initial rollout period. GSTN has indicated this and similar post-closure actions will be restricted once the system stabilises.

Q13: Does e-Way Bill Closure affect e-Invoice or IRN generation?

No. IRN generation, the e-Invoice API, and the combined IRN-plus-EWB flow are unaffected. Only e-Way Bill operations are impacted by this update.

Conclusion

Voluntary e-Way Bill Closure is a small, optional addition to an already familiar process, and there is no reason to overthink it before 1 August 2026. Update your ERP if you run one, register driver mobile numbers where it makes sense, and let your transporters know the option exists.

Nothing about your current EWB generation or cancellation process changes because of this update. The businesses that get the most out of it early will be the ones with a clean internal SOP and a team that already knows the difference between EWB-wise and date-wise closure. Everyone else can simply watch how the stabilisation period plays out and adopt it once the Closed status becomes official.