GSTN Advisory 668: The August 1, 2026 e-Way Bill Changes Are On Hold (Ship-To GSTIN and Closure Facility Deferred)
Quick Summary: What GSTN Advisory 668 Changed on July 29, 2026
- The August 1, 2026 e-Way Bill enhancements are on hold. GSTN issued an advisory on the GST portal on July 29, 2026 titled “Advisory on Keeping on Hold the Proposed e-Way Bill Enhancements”, stating that “the implementation of the above-mentioned enhancements has been kept on hold until further notice”.
- Two changes are deferred: the mandatory Ship-To GSTIN validation in Bill-To/Ship-To transactions across the e-Invoice API and the e-Way Bill by IRN API, and the new E-Way Bill Closure facility.
- No production changes are required. The advisory states that “all stakeholders are advised that no changes are required to be implemented in the production environment pursuant to the aforesaid advisories”.
- The earlier advisories and FAQs are being withdrawn from the GST portal. These are the advisories dated June 9, 2026 and June 17, 2026, and the FAQ set released on July 2, 2026.
- No revised go-live date has been announced. GSTN has said only “until further notice”. Do not assume a September or October 2026 date.
What Happened: The August 1, 2026 e-Way Bill Changes Are On Hold
If your ERP team has been working nights to be ready for the e-Way Bill changes on August 1, 2026, stop. On July 29, 2026, the Goods and Services Tax Network published an advisory on the GST portal keeping the entire package of proposed e-Way Bill and e-Invoice API enhancements in abeyance until further notice.
This is a genuine reversal, not another date shift. When GSTN deferred these same enhancements in June 2026 from June 15 to August 1, the changes remained on the roadmap with a firm new date. This time there is no new date at all, the supporting advisories are being pulled off the portal, and taxpayers have been told in terms that nothing needs to go into production.
For a busy finance team, the practical message is short. Your Bill-To/Ship-To invoicing continues exactly as it does today. Your e-Way Bills continue to expire the way they do today. Any ERP change request built solely on the June advisories should be paused, not deployed, and definitely not deployed on August 1.
The Exact Text of the Advisory
The advisory, published on the GST portal under News and Updates dated July 29, 2026, records three operative points:
- GSTN had earlier issued advisories dated 9th June 2026 and 17th June 2026 regarding certain proposed enhancements to the e-Way Bill system, with the scheduled date of implementation as 1st August 2026.
- “It is hereby informed that the implementation of the above-mentioned enhancements has been kept on hold until further notice.”
- “Accordingly, all stakeholders are advised that no changes are required to be implemented in the production environment pursuant to the aforesaid advisories.” All related advisories, along with the FAQs issued on July 2, 2026, are to be withdrawn from the GST portal.
Source: GST portal, News and Updates, gst.gov.in/newsandupdates/read/668, dated July 29, 2026, retrieved July 31, 2026.
What Exactly Was Deferred: The Two Enhancements Explained
The June advisories proposed structural changes to three API surfaces: the e-Invoice API, the e-Way Bill by Invoice Reference Number (IRN) API, and a new E-Way Bill Closure API. Two substantive compliance changes sat inside them.
1. Mandatory Ship-To GSTIN in Bill-To/Ship-To Transactions
In a Bill-To/Ship-To transaction the invoice is raised on one party and the goods physically move to a different party or a different place of business. Today the Ship-To details can be entered in a fairly loose way. The proposed enhancement would have made the Ship-To GSTIN a validated, mandatory field wherever Ship-To information was present, with “URP” (Unregistered Person) to be entered where the consignee has no GST registration.
The compliance consequence was significant. A distributor shipping to a customer’s warehouse would have needed the warehouse GSTIN in its master data, validated at the moment of IRN generation. Trading businesses that deliberately do not disclose the end customer to the manufacturer raised commercial confidentiality objections. Every business with a large, stale customer master faced a data cleanup project with a hard deadline.
2. The E-Way Bill Closure Facility
The second enhancement was more welcome and is now equally on hold. It would have introduced a formal facility to close an e-Way Bill that is still live on the portal even though the movement of goods never happened, the delivery was cancelled, or the invoice was withdrawn. As proposed, the facility would have allowed:
- Closure by the supplier, the recipient, the transporter, the driver, or an authorised representative
- Individual closure and date-based bulk closure of multiple e-Way Bills
- Mobile OTP based authentication for drivers and authorised persons who do not hold portal login credentials
Until this is implemented, the position is unchanged: an unused e-Way Bill simply runs out its validity. There is still no formal “close” button, and the only existing lever is cancellation within 24 hours of generation, subject to the condition that the goods have not been transported.
Deferred Enhancements at a Glance
| Item | Proposed position (from Aug 1, 2026) | Position today after Advisory 668 |
|---|---|---|
| Ship-To GSTIN in Bill-To/Ship-To | Mandatory and validated in e-Invoice and EWB-by-IRN APIs; “URP” for unregistered consignees | No change. Existing validation continues |
| E-Way Bill Closure facility | New facility to close unused or cancelled e-Way Bills, individually or in bulk | Not available. Cancellation within 24 hours remains the only route |
| API specification changes | Revised e-Invoice API, EWB-by-IRN API and new EWB Closure API in production | No production changes required |
| FAQs dated July 2, 2026 | Guidance for implementation | Being withdrawn from the GST portal |
| Go-live date | August 1, 2026 | On hold until further notice. No new date announced |
Why GSTN Pulled Back: The Industry Objections
The deferral followed sustained representations from trade and industry bodies. The recurring themes were practical rather than legal:
- ERP and integration lead time. Businesses would have had to modify ERP logic, update GSP and ASP integrations, and run end-to-end testing in a window measured in weeks.
- Customer master data quality. Ship-To GSTIN validation is only as good as the master data behind it. Many businesses do not capture the consignee GSTIN at all, particularly in third-party and drop-ship models.
- Commercial confidentiality. In multi-tier distribution, disclosing the end consignee GSTIN to the supplier exposes the customer relationship.
- Field realities. Collecting a validated GSTIN for every delivery location, including temporary sites and project locations, is harder in practice than on a specification sheet.
None of this means the enhancements are dead. The Ship-To GSTIN validation in particular closes a real revenue leakage and tracking gap, and it fits the direction of travel of the entire e-invoicing and Invoice Management System architecture. Treat this as a pause, not a cancellation.
What This Means for Different Stakeholders
For CAs and Tax Consultants
Send a short note to every client you advised to be ready by August 1. The risk here is not non-compliance, it is a client deploying a half-tested ERP change on August 1 based on advisories that no longer exist on the portal. That is a live operational risk: a validation change pushed to production against an API that has not changed can break IRN generation entirely.
For Founders and Finance Heads
Do not release the ERP change to production. Hold the code in a branch or in UAT. The specification is not wrong, only the timing. When GSTN reissues the enhancements, you will want that work, and a preserved, tested build is an asset. Also cancel any August 1 war-room or freeze you had scheduled.
For MSMEs and Traders
Nothing changes for you on August 1. Continue generating e-Way Bills and e-invoices exactly as you do today. If your billing software vendor has pushed an update in the last few days that makes Ship-To GSTIN mandatory, ask them to confirm it is optional again, because a locally enforced mandatory field will block your billing even though the portal does not require it.
For ERP Vendors, GSPs and ASPs
Roll back or feature-flag any release scheduled for the August 1 cutover. Communicate proactively to your customer base. The portal APIs are unchanged, so a client-side enforcement of the new validation creates failures that will land on your support desk, not on GSTN’s.
Your Action Checklist for August 1, 2026
- Freeze the deployment. Confirm with your IT or ERP team that no e-invoice or e-Way Bill API change is scheduled to go live on August 1, 2026.
- Check your billing software. Ask your vendor in writing whether they have already enforced mandatory Ship-To GSTIN, and get it reverted to optional if they have.
- Preserve the work. Keep the Ship-To GSTIN mapping and the closure workflow in a tested branch. Document what was built and where it stopped.
- Save your own copy of the June advisories and the July 2 FAQs before they come off the portal. You will want them as a specification reference when the enhancements return.
- Continue the master data cleanup anyway. Capturing consignee GSTINs is good hygiene irrespective of the mandate, and it will make the eventual go-live a configuration exercise rather than a project.
- Set a portal watch. Assign someone to check the GST portal News and Updates section weekly. There is no notified date, so the only warning you will get is a fresh advisory.
- Do not relax the rest of your e-Way Bill discipline. Rule 138 of the CGST Rules, 2017 read with Section 68 of the CGST Act, 2017 continues to apply in full. This advisory changes a proposed portal enhancement, not the statutory obligation to carry a valid e-Way Bill.
Frequently Asked Questions
Is the Ship-To GSTIN mandatory from August 1, 2026?
No. GSTN Advisory dated July 29, 2026 kept the proposed enhancement on hold until further notice. The existing e-Invoice and e-Way Bill validations continue unchanged, and no production change is required.
Has the e-Way Bill closure facility gone live?
No. The closure facility was part of the same deferred package. As of July 31, 2026, an unused e-Way Bill can only be cancelled within 24 hours of generation, provided the goods have not been transported. Otherwise it runs out its validity period.
Where can I read the advisory?
It is on the GST portal under News and Updates, titled “Advisory on Keeping on Hold the Proposed e-Way Bill Enhancements”, dated July 29, 2026, at gst.gov.in/newsandupdates/read/668.
When will the enhancements be implemented?
GSTN has not announced a date. The advisory says “until further notice”. Any specific future date circulating on social media or in vendor communication is speculation until GSTN publishes a fresh advisory.
Do I still need to generate e-Way Bills normally?
Yes, absolutely. The statutory framework under Rule 138 of the CGST Rules, 2017 and Section 68 of the CGST Act, 2017 is untouched. Detention, seizure and penalty exposure for moving goods without a valid e-Way Bill is exactly what it was yesterday.
What happens to the FAQs GSTN issued on July 2, 2026?
They are being withdrawn from the GST portal along with the June 9 and June 17, 2026 advisories. Download a copy now if you want a record of the proposed specification.
My software vendor has already made Ship-To GSTIN compulsory. What should I do?
Ask them to make it optional again, or at least to stop blocking invoice generation when it is blank. A client-side mandatory field that the portal does not require will stop you billing customers whose consignee GSTIN you do not hold.
The Bigger Picture
This is the second deferral of the same package in seven weeks. Read alongside the June 2026 deferral from June 15 to August 1, the pattern is clear: GSTN is willing to move on implementation timing when industry demonstrates genuine readiness constraints, but the architectural direction, tighter transaction-level validation and better lifecycle control over e-Way Bills, is not changing.
That has a planning implication. Businesses that treat each deferral as a reason to stop work end up doing the same panic project again in six months. Businesses that keep the master data cleanup running quietly, without a deadline, will find the eventual go-live is a switch rather than a scramble. The same logic applied to the hard-locking of GSTR-3B and the Invoice Management System, and to the AATO amendment window that closes today, July 31, 2026.
Talk to an Expert
If your e-invoicing or e-Way Bill setup needs a review, or you are unsure whether a vendor update has quietly changed your validations, a short conversation usually saves a lot of rework. Book a quick call to discuss your GST compliance position.
Disclaimer: This article is for general information only and does not constitute professional advice. It is based on the GSTN advisory dated July 29, 2026 available on the GST portal and on publicly available reports, retrieved on July 31, 2026. Positions on the GST portal can change without notice. Please verify the current position on gst.gov.in and consult a qualified professional before acting on anything stated here. Tax Update India accepts no liability for any action taken on the basis of this article.
You can reach out to the author on : info@asbanka.com
www.asbanka.com
- RBI A.P. (DIR Series) Circular 19 of 2026: One Consolidated Rulebook for Special Rupee Vostro Accounts (SRVA) - July 31, 2026
- GSTN Advisory 668: The August 1, 2026 e-Way Bill Changes Are On Hold (Ship-To GSTIN and Closure Facility Deferred) - July 31, 2026
- FEMA (Authorised Persons) Regulations 2026: How RBI Notification FEMA 401/2026-RB Overhauls Forex Licensing - July 24, 2026