GSTN, through its advisory dated 20 May 2026, introduced two significant operational changes to the e-Way Bill (EWB) system, both linked to the 15 June 2026 API production deadline. First, the “Ship To GSTIN” field has become mandatory for Bill-To/Ship-To transactions, requiring businesses to capture the consignee GSTIN or use “URP” for unregistered recipients. This change affects manufacturers, dealers, e-commerce operators, transporters, and businesses using ERP-based EWB systems. Second, GSTN introduced a voluntary EWB Closure facility allowing suppliers, recipients, transporters, or authorised field personnel to formally close an EWB after delivery confirmation, including through OTP-based mobile verification without portal login. Closure must occur on the delivery date or the immediately succeeding day. GSTN has also released updated API specifications in Sandbox mode, requiring ERP vendors, GSPs, ASPs, and integrators to complete system modifications before 15 June 2026 to avoid disruption in EWB generation and compliance workflows.
Let me give you the short version first
On 20 May 2026, GSTN issued a formal advisory announcing two operational changes to the e-Way Bill portal. These are not portal cosmetics. One change imposes a mandatory new data field that will break EWB generation for businesses running stale ERP templates. The other introduces an entirely new concept to the GST system which is the voluntary closure of an e-Way Bill upon delivery. Both changes converge on the same API production deadline: 15 June 2026.
| Change | What Changed | Who It Hits | Deadline |
| Ship To GSTIN | Mandatory in Bill-To/Ship-To EWBs | Manufacturers, dealers, 3PL operators | 15 June 2026 |
| EWB Closure | Voluntary facility to mark delivery complete | All EWB generators and transporters | Available now (voluntary) |
| API Changes | Sandbox live; production 15 June 2026 | ERP vendors, GSPs, ASPs, integrators | 15 June 2026 (production) |
Change 1: that “Ship to” GSTIN field you have been skipping
In a Bill-To/Ship-To transaction the everyday scenario where invoicing and physical delivery happen at different locations which is the “Ship To GSTIN” field has historically been filled inconsistently, if at all. GSTN has now made it a mandatory data element at the point of EWB generation. No GSTIN on record? You enter “URP” for an unregistered consignee. But the field cannot be left blank.
Think about who this hits hardest. Manufacturers supplying dealer networks where dealer billing and warehouse delivery addresses differ. Businesses running third-party logistics arrangements. E-commerce operators with multiple fulfilment addresses. Anyone whose ERP auto-populates the bill-to party without a corresponding ship-to mapping is about to generate errors in their EWB workflow.
| Immediate check required
Open your ERP’s EWB generation template. Locate the Ship to GSTIN field. Is it mapped? Is it mandatory in your system? If the answer to either question is “no” or “I’m not sure”, immediately escalate to your ERP vendor today, not next week. |
Change 2: the EWB closure facility: A small feature but a larger signal
This is the more consequential change, even though it is voluntary today. Until now, an e-Way Bill expired when its validity ran out. There was no mechanism inside the GST system to formally mark a delivery as completed. A goods movement either expired naturally or was cancelled. Nothing in between. That gap has now been filled.
The new voluntary EWB Closure facility allows authorised parties to formally close an e-Way Bill once delivery is confirmed. The portal now shows an “EWB Close” option in the e-Way Bill section for logged-in users. Closure can be done by individual EWB number or date-wise — which means a transporter handling dozens of deliveries on a given day can batch-close them in one operation.
Four parties can initiate closure: supplier, recipient, transporter, and this is the operationally interesting one that is a driver or authorised field person via mobile OTP, without needing a portal login.
| The mobile number angle: Kindly read this carefully
At the time of EWB generation, you can optionally register a mobile number specifically for closure. Once registered (and it can also be updated during vehicle updation, consolidated EWB operations, or validity extension), all active EWBs linked to that number become visible on the portal’s Search screen. The driver or authorised person enters the mobile number, receives an OTP, and closes the EWB with no login, no portal access, no dependency on the finance team. For field-delivery-heavy businesses, this changes the closure workflow entirely. |
Timing matters: you have a two-day window, not more
The advisory is explicit on this. An EWB can be closed on the same day of delivery or on the immediately succeeding day. After that, the portal will not permit it. This means the entire closure workflow that is the field confirmation, system update, portal action all is required to be happen within 24 to 48 hours of delivery. Businesses without a structured last-mile reporting process will miss this window routinely.
Build the SOP before you need it. Who confirms delivery? Who updates the system? Who triggers the portal closure? These are logistics-finance coordination questions that most companies have never had to answer in the context of GST compliance. Now they do.
For API users and ERP vendors: 15 June is real
NIC has already released the updated API specifications in the Sandbox environment. For EWB closure through API, three fields are required: the e-Way Bill number, the closure date, and remarks. For the Ship to GSTIN change, existing API call structures for EWB generation will need to be updated to include the mandatory field.
The production deployment is scheduled for 15 June 2026. That is not a soft target. All ERP vendors, GSPs, ASPs, and system integrators need to access the updated specs, test in Sandbox, and carry out configuration changes at their end before that date. The advisory uses the phrase “seamless transition prior to production rollout” though which is the polite way of saying: if you are not ready, your clients’ EWB workflows will break.
| If you are a CA advising clients with ERP-based EWB workflows
This is a client communication moment. Your client’s ERP vendor may not have flagged this change. You should. A one-page advisory to key clients and particularly those in manufacturing, trading, or 3PL which are covered under the “Ship To” GSTIN mandate and the 15 June API deadline will be genuinely useful and positions you as ahead of the curve. |
The question no one is asking yet: why is GSTN building this?
GSTN does not introduce infrastructure without a purpose. The voluntary EWB closure facility creates, for the first time, a system-level delivery timestamp linked to a specific e-Way Bill number. When that data is cross-referenced with GSTR-1 invoice dates, GSTR-3B filings, and transporter data, the audit trail in reality becomes considerably more granular.
The pattern is not new. e-invoicing was optional before it became phased-mandatory. HSN reporting was introduced gradually and then tightened. ITC reconciliation has moved steadily toward system-driven verification. Voluntary today reliably becomes mandatory tomorrow in the GST architecture. Businesses that build the closure discipline now will face far less disruption when the mandate arrives.
The mandatory “Ship To” GSTIN requirement tells the same story. GSTN wants to know not just who invoiced and who paid, but where the goods physically went. That is end-to-end traceability. And it is not going away.
What you should do this week
| 1 | Audit your Bill-To/Ship-To EWB templates. Confirm “Ship to” GSTIN is captured or not and “URP” is defaulted for unregistered consignees. This is not optional from 15 June 2026. |
| 2 | Call your ERP vendor or GSP today. Ask them specifically: “Have you tested the updated API in the Sandbox? Will you be live by 15 June?” Accept no vague answer. |
| 3 | Decide your closure policy now. If you are adopting voluntary EWB closure, write an SOP as to who closes, within what window post-delivery, and how exceptions are handled. |
| 4 | Evaluate the mobile number closure feature. For field-delivery businesses, this is a genuine operational lever. Assess whether registering a driver’s mobile at EWB generation time makes sense for your model. |
| 5 | Train your accounts and logistics teams. The portal now has an “EWB Close” option in the e-Way Bill menu. Field staff need to know it exists and what to do with it. |
The EWB system is moving from a transport-document tool to a full-lifecycle transaction record. The delivery closure facility is the final piece of that architecture. Whether your business is ready to operate within it or scrambles to catch up after 15 June is a choice you can still make today.
Source: GSTN Advisory dated 20 May 2026 “Advisory to Taxpayers and Stakeholders: Enhancements in the e-Way Bill (EWB) Portal.” All facts in this article are drawn directly from that advisory. The API production deployment date of 15 June 2026 is as stated therein. Readers should monitor GSTN and NIC portals for subsequent amendments or clarifications.
Author Bio
