Date of Advisory: May 21, 2026 | Production Go-Live: June 15, 2026
The Problem GSTN Is Actually Solving
India’s GST framework has always rested on one foundational principle — every rupee of tax must be traceable, from the seller’s invoice to the buyer’s return. Yet for years, a quiet gap has existed inside the e-Way Bill system that allowed that chain of traceability to break at a critical point: the moment goods physically changed hands at a location different from the billing address.
Think about how modern commerce actually works. A manufacturer in Ludhiana bills a distributor in Delhi, but instructs the transporter to deliver the goods directly to a retailer’s warehouse in Gurugram. Three parties. Two addresses. One e-Way Bill — and until now, no mandatory field capturing where the goods actually landed.
GSTN’s Advisory No. 661, issued on May 21, 2026, is designed to close precisely this gap. It introduces two reforms that, taken together, give the e-Way Bill a genuine beginning, middle, and end for the first time since the system launched.
Reform No. 1 — Making the “Ship-To” Address Non-Negotiable
The Gap That Existed
In Bill-To/Ship-To transactions — the kind that form the backbone of distributor networks, e-commerce fulfilment, and third-party logistics — the e-Way Bill portal historically captured who was billed but not always who received the goods. The “Ship-To GSTIN” field existed but was optional, meaning businesses could leave it blank without any system-level consequence.
What Changes Now
Under the revised framework, capturing the Ship-To GSTIN in every Bill-To/Ship-To transaction becomes mandatory at the time of EWB generation. Where the actual recipient is an unregistered person, the system requires the value “URP” to be entered — not a blank, not a dash, but a positive declaration that the consignee is unregistered.
Why This Matters Beyond Compliance
This is not merely a data-entry requirement. Consider what becomes possible once this field is consistently populated:
The tax department can now cross-verify whether the entity receiving goods at a given GSTIN has declared inward supply in its GSTR-2B. Discrepancies between EWB ship-to data and ITC claimed become detectable at scale. Fraudulent schemes involving fake bill-to parties and untraceable physical deliveries become significantly harder to execute without leaving a footprint in the system.
For businesses, it also means that the risk of receiving a notice for a mismatch between your purchase register and the department’s EWB data has materially increased if your systems are not updated. The time to audit your Bill-To/Ship-To workflows is now, not after go-live.
Reform No. 2 — The e-Way Bill Finally Gets a Formal Closing Chapter
What Was Missing Until Now
An e-Way Bill, once generated, could expire, get extended, or simply be abandoned in the system after goods were delivered. There was no formal mechanism for any party to declare: “These goods have reached their destination. This EWB is done.” The lifecycle of every e-Way Bill was, in a sense, incomplete by design.
The New Closure Facility
GSTN has now introduced a voluntary EWB Closure facility — a dedicated mechanism through which an e-Way Bill can be formally closed after delivery. The parties authorised to initiate closure are:
- The supplier who generated the EWB
- The recipient of the goods
- The transporter assigned to move the consignment
- The driver or authorised person operating the vehicle
Closure can be done in two modes — EWB-wise (closing a specific bill) or date-wise (closing all bills delivered on a particular date), giving businesses handling high volumes of daily transactions the operational flexibility they need.
Importantly, the window for closure is tight by design: it may be exercised on the day of delivery or the immediately following day. This near real-time closure expectation signals GSTN’s intent to eventually use closure data as a verification checkpoint in the compliance ecosystem.
A mobile-number-based closure option is also available, meaning even transporters and drivers without constant access to a desktop portal can participate in the process. A dedicated mobile number can be specified at EWB generation and updated at the time of vehicle updation, consolidated EWB operations, or validity extension.
The Technology Angle: What ERP Teams Must Do Before June 15
GSTN has not left technology integration as an afterthought. NIC has already deployed the necessary API changes in the Sandbox environment, and all stakeholders — ERP vendors, GST Suvidha Providers (GSPs), Application Service Providers (ASPs), and in-house API integrators — have been given a clear runway to test, configure, and certify their systems before the production cutover on June 15, 2026.
The checklist for technical teams is straightforward but non-trivial:
First, the Ship-To GSTIN field must be treated as a mandatory input in all EWB generation workflows that involve Bill-To/Ship-To transactions. Validation rules must be updated to reject EWB generation attempts where this field is left empty.
Second, the EWB Closure functionality requires new API endpoints and corresponding UI triggers, whether on internal portals, logistics management systems, or mobile apps used by transporters.
Third, historical data flows — such as ERP-to-EWB integrations that were built when Ship-To GSTIN was optional — must be audited and corrected. The risk of integration failure at go-live is real for organisations that defer this work.
A Compliance Perspective: Who Should Pay Closest Attention
Manufacturing and distribution companies operating through multi-tier channel structures will feel the Ship-To GSTIN change most directly. Every third-party delivery, every depot transfer, and every drop-shipment arrangement needs to be reviewed against the new mandatory field requirement.
E-commerce operators and 3PL providers who manage deliveries on behalf of multiple sellers should ensure their fulfilment systems are updated to capture and transmit Ship-To GSTIN at the point of EWB generation.
Chartered Accountants and tax practitioners advising clients on GST compliance should proactively audit client EWB generation workflows, particularly for those in sectors such as pharmaceuticals, FMCG, and industrial goods where Bill-To/Ship-To arrangements are the norm rather than the exception.
Transporters and logistics companies gain both a responsibility and an opportunity from the new Closure facility. For the first time, they can formally sign off on a delivery within the GST system, creating a verifiable record of completion that can serve as evidence in disputes.
Reading Between the Lines: The Larger Policy Direction
Advisory No. 661 is not an isolated tweak. It fits into a clear and consistent direction that GSTN has been charting over the past year — most visibly with the launch of the E-Way Bill 2.0 portal in July 2025, which introduced dual-portal architecture and real-time synchronisation to ensure business continuity during technical downtimes.
The pattern is one of steadily tightening the link between physical goods movement and its digital representation in the GST system. The mandatory Ship-To GSTIN strengthens the front end of that link — the origin and routing of a consignment. The EWB Closure facility strengthens the back end — the confirmed delivery. Together, they make the e-Way Bill a far more complete instrument of traceability than it has ever been.
The underlying message to businesses is clear: the era of optional data fields and open-ended EWB lifecycles is ending. The GST system is moving toward a model where every significant event in a goods transaction — generation, transit, delivery, and closure — is captured, timestamped, and available for audit.
Key Dates and Action Points at a Glance
| What | When |
|---|---|
| Advisory issued (No. 661) | May 21, 2026 |
| API changes in Sandbox | Already available |
| Production deployment | June 15, 2026 |
| Ship-To GSTIN becomes mandatory | From go-live date |
| EWB Closure facility available | From go-live date |
For businesses: Review all Bill-To/Ship-To transaction workflows and update master data, ERP configurations, and user training before June 15.
For technology teams: Access the updated API specifications in the Sandbox, complete integration testing, and raise any issues through GSTN’s helpdesk channels before the production cutover.
For tax professionals: Factor these changes into ongoing GST compliance reviews and advise clients to conduct readiness assessments ahead of the go-live date.
Conclusion: A Smaller Field With a Larger Purpose
At its surface, making a GSTIN field mandatory and adding a closure button may seem like minor portal housekeeping. But the implications run deeper. GSTN is systematically eliminating the grey spaces in goods movement data — the unmapped destinations, the open-ended EWBs, the ambiguous consignee records — that have historically limited the effectiveness of GST enforcement and complicated honest taxpayer reconciliations alike.
Businesses that treat Advisory No. 661 as a prompt to modernise their logistics compliance infrastructure will find themselves better positioned — not just for June 15, but for a GST regime that is visibly moving toward end-to-end transaction verification. Those who treat it as just another advisory to file away may find the gap between their data and the department’s data becoming harder to explain.
Recent Comments