GST Compliance

E-Way Bill Changes Put On Hold: What Happens From 1 August 2026

GST Consultancy Team31 July 202610 min read
E-Way BillShip-To GSTINEWB closureGSTN advisorydeferredAugust 2026
GSTN has put the proposed e-way bill enhancements on hold until further notice. The mandatory Ship-To GSTIN field and the voluntary EWB closure facility do not go live on 1 August 2026, and the earlier advisories and FAQs have been withdrawn from the portal. What the 29 July 2026 advisory says, what stays unchanged, and why you should not undo your ERP work.

Last updated: 31 July 2026. The e-way bill changes due to go live on Saturday, 1 August 2026 are not going live. In an advisory dated 29 July 2026, GSTN kept the proposed e-way bill enhancements — the mandatory Ship-To GSTIN field and the voluntary EWB closure facilityon hold until further notice, and withdrew the earlier advisories and FAQs from the GST portal. Nothing in your e-way bill process needs to change on 1 August 2026. What you should not do is undo the readiness work you have already done.

Applicability Note: This guide reflects the GSTN advisory dated 29 July 2026 and GST provisions applicable as of 31 July 2026. "On hold until further notice" is not a cancellation and carries no new date — GSTN can revive these enhancements through a fresh advisory. Always verify the current position in the News & Updates section of gst.gov.in or on the e-way bill portal before changing how you generate e-way bills.

Who Should Care?

This applies to:

  • Anyone generating e-way bills for Bill-To/Ship-To deliveries — where the buyer's billing GSTIN differs from the delivery location
  • ERP, billing-software and API users — teams that scheduled a 1 August release around the new Ship-To GSTIN and closure APIs
  • Transporters and dispatch teams — briefed to start closing e-way bills after delivery from 1 August
  • Accountants and compliance managers — who need to know there is no exposure for not being ready, and no new date to plan for

1. What the 29 July 2026 Advisory Actually Says

GSTN posted "Advisory on Keeping on Hold the Proposed e-Way Bill Enhancements" in the News & Updates section of the GST portal on 29 July 2026. Four short paragraphs, doing three things: holding the enhancements, telling stakeholders to leave production alone, and withdrawing the earlier guidance.

From the advisory dated 29 July 2026: "It is hereby informed that the implementation of the above-mentioned enhancements has been kept on hold until further notice." And: "all stakeholders are advised that no changes are required to be implemented in the production environment pursuant to the aforesaid advisories until further communication." It adds that "All related advisories, along with the FAQs issued, shall also be withdrawn from the GST Portal."

Three details are worth reading closely. First, the wording is "on hold until further notice" — not withdrawn, not cancelled, and with no replacement date. Second, the instruction is aimed squarely at production: whatever you built, do not switch it on. Third, the earlier advisories and the FAQs are gone from the portal, so the documents your ERP vendor was working from can no longer be downloaded.

All of this was done by advisory, not by notification. No provision of the CGST Rules was ever amended for these enhancements, which is why holding them needed nothing more than a portal notice.

2. What Exactly Is On Hold

Three separate items were scheduled for 1 August 2026, and all three are covered by the hold.

ItemWhat it was going to requirePosition from 1 August 2026
Mandatory Ship-To GSTIN Mandatory in Bill-To/Ship-To and combination transactions wherever the consignee is a registered person ("URP" if unregistered). The portal would not generate the e-way bill without it. On hold. The field is not enforced. Generation behaves as it did before.
Voluntary EWB closure facility Supplier, recipient, transporter or driver could record delivery and close the e-way bill — via portal, an OTP-based mobile facility, or API. On hold. The facility does not go live. There is nothing to close.
Three API changes (advisory dated 17 June 2026) e-Invoice API, e-Way Bill by IRN API and EWB Closure API updated for the above, released in the NIC sandbox for testing ahead of production. On hold. No production change is required, per the 29 July advisory.

The hold covers the whole set, so there is no half-implementation to manage — the IRN route and the portal route both behave as they did yesterday.

3. How We Got Here: Two Deferrals, Then a Hold

This is the second time GSTN has moved this set of enhancements in ten weeks, which is the main reason to treat any future date with a little caution.

DateWhat happened
20 May 2026GSTN advisory (no advisory number) announces both enhancements, with effect from 15 June 2026.
9 June 2026GSTN News & Updates notice defers the go-live for both to 1 August 2026 after representations from trade, GSPs and ERP vendors seeking time for system readiness.
17 June 2026GSTN advisory covers the related e-Invoice API, e-Way Bill by IRN API and EWB Closure API changes, available in the sandbox for testing, for production on 1 August 2026.
2 July 2026GSTN issues detailed FAQs — including that Ship-To GSTIN would be mandatory wherever the consignee is registered, and that closure would only record completion of movement.
29 July 2026GSTN keeps the enhancements on hold until further notice, tells stakeholders not to change production, and withdraws the advisories and FAQs from the portal.

Note the timing: the hold landed three days before go-live, after FAQs had been published and sandbox testing was well under way. Businesses that had already switched their masters and API payloads over were early for nothing on timing — but not on substance, as section 5 explains.

4. What Has Not Changed

The hold affects two portal features and their APIs. It does not touch the e-way bill framework itself, so every existing obligation continues exactly as before:

  • You still need an e-way bill. Movement of goods where the consignment value exceeds ₹50,000 continues to require one under Rule 138 of the CGST Rules, subject to state thresholds and the usual exemptions.
  • Part-A and Part-B, validity and extension work as they did — none of that was in scope.
  • Cancellation is still the only "undo". Under Rule 138(9), an e-way bill can be cancelled within 24 hours of generation where the goods are not transported or not transported as per the details furnished, and not at all once it has been verified in transit under Rule 138B. Cancellation ("this movement did not happen as declared") is a different thing from the closure facility now on hold ("this movement is complete").
  • Mismatch risk is unchanged. Where e-way bill details do not match the invoice, goods can be detained under Section 129 of the CGST Act — 200% of the tax payable on the goods where the owner comes forward (Section 129(1)(a)), and the higher of 50% of the value of the goods or 200% of the tax payable where the owner does not come forward (Section 129(1)(b)), with lesser amounts for exempt goods.

That last point is why the Ship-To accuracy work still pays for itself. For the underlying mechanics, see our 2026 e-way bill guide; our earlier note on the proposed changes now describes a position that is on hold, not one in force.

5. What To Do Now

  1. Do not roll back your ERP changes. A correct Ship-To GSTIN is the field that prevents an invoice-versus-e-way-bill mismatch and a Section 129 detention, whatever the portal enforces. Keep the capability; just do not make it a blocking validation in your own system.
  2. Tell the teams you already briefed. Dispatch and transport partners told to start closing e-way bills from Saturday need to know the facility is not there. A team hunting for a button that does not exist is how workarounds get invented.
  3. Keep your copy of the withdrawn FAQs and advisories. They are coming off the portal. A dated copy in your compliance file shows why you built what you built, and gives your vendor a reference if the enhancements return in the same shape.
  4. Do not build a process that depends on closure. If an internal report, KPI or customer commitment was going to rely on an e-way bill closure status, park it. There is no date to plan around.
  5. Watch News & Updates, not commentary. The go-live has already moved twice, and as of 31 July 2026 much of the published commentary still describes the 1 August go-live as going ahead. Check gst.gov.in News & Updates before acting on any revival.

If you are unsure whether a specific Bill-To/Ship-To flow is reported correctly today, ask our GST experts — that question is worth settling regardless of what the portal enforces.

Key Takeaways

  • GSTN's advisory dated 29 July 2026 keeps the proposed e-way bill enhancements on hold until further notice. Nothing changes on 1 August 2026.
  • All three items are held: mandatory Ship-To GSTIN, the voluntary closure facility, and the related API changes announced on 17 June 2026.
  • The advisory tells stakeholders that no production changes are required, and that the earlier advisories and the FAQs dated 2 July 2026 are being withdrawn from the portal.
  • "On hold" is not cancellation and no new date has been given — a fresh advisory can revive the enhancements, so keep your ERP capability rather than reversing it.
  • Everything else stands: the ₹50,000 threshold under Rule 138, the 24-hour cancellation window under Rule 138(9), and Section 129 detention risk where the e-way bill does not match the invoice.

Frequently Asked Questions

Is Ship-To GSTIN mandatory on e-way bills from 1 August 2026?

No. GSTN kept the enhancement on hold in an advisory dated 29 July 2026, three days before go-live. The portal continues to generate Bill-To/Ship-To e-way bills as it did before, and the earlier advisories and FAQs have been withdrawn from the portal.

Has the e-way bill closure facility been cancelled or just postponed?

Postponed. The advisory says implementation "has been kept on hold until further notice" — it does not cancel the enhancement and gives no new date. Cancellation within 24 hours under Rule 138(9) is unaffected; that is a separate, existing facility.

Do I need to reverse the changes my ERP vendor already made?

The advisory asks that no changes be implemented in the production environment, so the new behaviour should not be switched on. It does not ask anyone to undo development work. Capturing a correct Ship-To GSTIN is worth keeping on its own merits, since an e-way-bill-to-invoice mismatch can lead to detention under Section 129.

Is there any penalty for not being ready by 1 August 2026?

No. No penalty was attached to these enhancements even before the hold — the Ship-To GSTIN requirement was a portal validation on generation, and closure was expressly voluntary. With them on hold, there is nothing to be ready for.

Where can I check whether these e-way bill changes have been revived?

The News & Updates section on gst.gov.in, and the e-way bill portal. As of 31 July 2026 several commentary sites still describe the 1 August go-live as going ahead, so the portal notice is what to rely on.

Disclaimer: This article is for informational purposes only and does not constitute professional tax advice. GST rules are subject to frequent changes through notifications and circulars. Please consult a qualified tax professional or verify the current provisions on the official GST portal (gst.gov.in) before making any compliance decisions.

Not sure whether your Bill-To/Ship-To e-way bills are reported correctly today? Our GST experts can help → gstconsultancy.com

Have questions about your specific situation?

Get a personalised answer from our GST experts — backed by law, delivered within 24 hours.

Ask a Question — Starting ₹199
← Back to all articles