GST Update | e-Way Bill Portal Changes | GSTN Advisory 661
e-Way Bill Portal Changes: Ship To GSTIN and Closure Facility Explained – Updated for 1 August 2026
GSTN Advisory 661 dated 21 May 2026 has proposed important e-Way Bill portal changes relating to Ship To GSTIN capture, voluntary e-Way Bill Closure, mobile number usage and API readiness.
The implementation timeline was earlier proposed as 15 June 2026. As per GSTN Advisory 663 dated 9 June 2026, the revised implementation date is now 1 August 2026. Businesses, transporters, ERP/API users and GST professionals should use the extended timeline to complete system changes, testing and operational readiness.
Update: Implementation Timeline Extended to 1 August 2026
GSTN has issued Advisory No. 663 dated 9 June 2026 extending the implementation timeline for mandatory “Ship To GSTIN” in Bill-To/Ship-To transactions and the voluntary e-Way Bill Closure functionality.
These functionalities were earlier proposed to be implemented from 15 June 2026. As per the latest advisory, the revised implementation date is now 1 August 2026.
Taxpayers, GSPs, ERP providers and other stakeholders should complete the necessary system changes, testing, API/ERP readiness and operational preparedness before the revised implementation date.
What are the proposed e-Way Bill portal changes?
GSTN has proposed e-Way Bill portal changes for better data quality, traceability and operational control. The key proposed changes include mandatory Ship To GSTIN capture in Bill-To/Ship-To transactions, use of URP for unregistered consignees, a voluntary e-Way Bill Closure facility after delivery completion and API updates for ERP/system integrators.
- Ship To GSTIN: Proposed mandatory capture in Bill-To/Ship-To transactions.
- Unregistered consignee: “URP” should be entered in the Ship To GSTIN field.
- Closure facility: Voluntary e-Way Bill Closure facility after delivery completion.
- Who can close: Supplier, recipient, transporter, driver or authorised person whose mobile number is provided.
- Closure timing: Same day of delivery or immediately succeeding day.
- API readiness: API requires e-Way Bill number, closure date and remarks.
- Testing: NIC sandbox changes have been released.
- Timeline extension: The earlier implementation date of 15 June 2026 has been extended to allow system changes, testing, API/ERP readiness and master data updation.
- Revised implementation date: 1 August 2026, as per GSTN Advisory 663 dated 9 June 2026.
Why are these e-Way Bill portal changes important?
These proposed changes affect businesses and professionals who generate e-Way Bills through the GST portal, ERP systems or API-based integrations. The practical impact is mainly on Bill-To/Ship-To transactions, consignee data, mobile number control, delivery completion tracking and system readiness.
GSTN Advisory 661 should be used as the official reference point, but businesses should focus on the operational changes rather than only the advisory number.
Key Takeaway for Businesses and GST Professionals
The proposed e-Way Bill portal changes mainly require businesses to capture accurate Ship To GSTIN details, use URP for unregistered consignees, prepare for voluntary e-Way Bill Closure after delivery and test ERP/API changes before the revised implementation date of 1 August 2026.
What is changing in Ship To GSTIN for Bill-To/Ship-To transactions?
One of the important proposed changes is mandatory capture of Ship To GSTIN in Bill-To/Ship-To transactions.
In many business cases, the billing party and the delivery location may be different. For example, goods may be billed to one GSTIN but shipped to another location, branch, project site or consignee. The proposed requirement is intended to improve identification of the actual delivery destination.
Important: Where the consignee is unregistered, GSTN has stated that “URP” should be entered in the Ship To GSTIN field.
Practical impact
- Businesses should review Bill-To/Ship-To transactions.
- Customer and consignee GSTIN data should be verified.
- Unregistered consignee cases should be identified properly.
- ERP/API systems should be checked for Ship To GSTIN and URP handling.
- Billing, dispatch and logistics teams should be trained before implementation.
What is the voluntary e-Way Bill Closure facility?
GSTN has also proposed a voluntary e-Way Bill Closure facility. This facility is intended to allow closure of an e-Way Bill after delivery completion.
As per the advisory, closure may be done either e-Way Bill-wise or date-wise. The e-Way Bill can be closed on the same day of delivery or on the immediately succeeding day.
E-Way Bill-wise Closure
Individual e-Way Bills may be closed after delivery completion.
Date-wise Closure
Closure may also be performed date-wise, depending on the portal facility and user workflow.
Since this facility is described as voluntary, users should not treat it as a mandatory compliance step unless GSTN or the relevant authority clarifies otherwise.
Who can close an e-Way Bill?
As per the advisory, the e-Way Bill closure facility may be used by the following persons:
- Supplier
- Recipient
- Transporter
- Driver
- Authorised person whose mobile number is provided
A mobile number can be entered for closure purposes during e-Way Bill generation. GSTN has also mentioned that the mobile number may be updated during vehicle updation, consolidated e-Way Bill operations or extension of validity.
Suggested internal control: Businesses should avoid using random or unmanaged mobile numbers. The number should belong to a responsible person such as a dispatch manager, transporter contact, driver or authorised logistics coordinator.
Mobile number capture is voluntary: Entering a mobile number specifically for closure purposes during e-Way Bill generation, vehicle updation, consolidated e-Way Bill operation or validity extension should be treated as voluntary as per the proposed process. If it is not entered, closure should still remain available to primary portal stakeholders such as supplier, recipient or transporter, subject to final portal implementation.
How will logged-in users, drivers and authorised persons close an e-Way Bill?
Based on the proposed process, closure access may differ depending on the person closing the e-Way Bill.
Logged-in portal users
Supplier, recipient and transporter may use the closure facility from their respective logged-in e-Way Bill portal access, subject to the final portal implementation.
Driver or authorised person
Driver or authorised person may use the public mobile OTP-based closure facility where the designated mobile number is provided for closure purposes.
Practical point: The driver or authorised person should not require full taxpayer portal login credentials merely for OTP-based closure. However, businesses should confirm the final portal behaviour after implementation.
What should ERP and API users prepare?
GSTN has stated that API has been provided for system integrators and API users. Based on the technical specification, the closure API requires the e-Way Bill number, closure date and remarks. ERP/API users should ensure that their systems can capture and transmit these values correctly after testing in the sandbox environment.
API caution: Businesses should not directly change production workflows without sandbox testing. Field names, validation behaviour and rejection messages should be checked against the latest NIC/GSTN API documentation before production use.
Key timeline points
- NIC sandbox changes have been released.
- ERP/API users should conduct testing in the sandbox environment wherever applicable.
- The earlier implementation date was 15 June 2026.
- As per GSTN Advisory 663 dated 9 June 2026, the revised implementation date is 1 August 2026.
ERP/API users should check
- Ship To GSTIN field handling
- URP handling for unregistered consignees
- Mobile number capture and update flow
- e-Way Bill closure API flow
- Closure date and remarks fields
- Validation changes after production deployment
What Businesses and Transporters Should Prepare
Businesses and transporters should use the extended timeline up to 1 August 2026 to review their internal e-Way Bill process, update master data, complete ERP/API testing and train billing, dispatch and logistics teams.
1. Review Bill-To/Ship-To cases
Identify cases where billing and delivery locations are different.
2. Update master data
Review customer, branch, warehouse and consignee GSTIN details.
3. Train billing and dispatch teams
Ensure teams understand Ship To GSTIN and URP usage.
4. Decide closure responsibility
Define whether supplier, recipient, transporter, driver or authorised person will close e-Way Bills.
5. Manage mobile number usage
Use controlled mobile numbers for closure-related operations.
6. Test ERP/API flow
Conduct sandbox testing wherever applicable before the revised implementation date of 1 August 2026.
What should GST professionals tell clients?
GST professionals, CAs and consultants should guide clients in a practical and non-alarming manner. Clients should be informed that GSTN has proposed changes in the e-Way Bill portal and that the focus should be on preparation, data accuracy and system readiness.
- Review Bill-To/Ship-To transactions.
- Keep Ship To GSTIN data ready.
- Use URP correctly for unregistered consignees.
- Coordinate with ERP/API vendors.
- Define responsibility for e-Way Bill closure.
- Inform clients that the earlier 15 June 2026 timeline has been extended by GSTN Advisory 663.
- Test the process before the revised implementation date of 1 August 2026.
- Avoid last-minute changes in live business operations.
This advisory should not be presented as a legal opinion or as a guarantee of compliance. It is a portal-process and system-readiness update based on the GSTN advisory.
TaxPower GST Readiness Note
GSTN had earlier proposed these e-Way Bill portal enhancements with reference to Advisory 661. As per GSTN Advisory 663 dated 9 June 2026, the implementation timeline for mandatory Ship To GSTIN and voluntary e-Way Bill Closure has now been extended to 1 August 2026.
Once these changes are implemented and stabilized on the portal, TaxPower GST will be updated accordingly to support users as required.
Businesses using ERP, API-based workflows or structured billing data should continue reviewing their Bill-To/Ship-To data, consignee GSTIN mapping, URP handling and closure-related workflows during the extended preparation period.
Note: Users should continue to verify e-Way Bill data carefully before generation, updation, closure or API-based use. Final responsibility for data accuracy and compliance remains with the taxpayer, business or professional handling the transaction.
FAQs on e-Way Bill Portal Changes
1. Has GSTN extended the implementation date for Ship To GSTIN and e-Way Bill Closure?
Yes. GSTN Advisory 663 dated 9 June 2026 has extended the implementation timeline for mandatory Ship To GSTIN in Bill-To/Ship-To transactions and voluntary e-Way Bill Closure functionality to 1 August 2026.
2. What was the earlier implementation date?
The earlier implementation date mentioned with reference to Advisory 661 was 15 June 2026. This has now been extended to 1 August 2026 as per GSTN Advisory 663.
3. What are the proposed e-Way Bill portal changes?
GSTN has proposed e-Way Bill portal changes relating to Ship To GSTIN capture, voluntary e-Way Bill Closure, mobile number usage, API readiness and sandbox testing.
4. Is Ship To GSTIN proposed to be mandatory in e-Way Bill?
Yes. In Bill-To/Ship-To transactions, GSTN has proposed mandatory capture of Ship To GSTIN.
5. What should be entered if the consignee is unregistered?
If the consignee is unregistered, the advisory states that “URP” should be entered in the Ship To GSTIN field.
6. What is the e-Way Bill Closure facility?
The e-Way Bill Closure facility is a proposed voluntary facility to close an e-Way Bill after delivery completion.
7. Is e-Way Bill Closure mandatory?
The advisory describes the e-Way Bill Closure facility as voluntary. Users should wait for final portal implementation and further clarification before treating it as mandatory.
8. Who can close an e-Way Bill?
As per the advisory, an e-Way Bill may be closed by the supplier, recipient, transporter, driver or authorised person whose mobile number is provided.
9. When can an e-Way Bill be closed?
The advisory states that e-Way Bills can be closed on the same day of delivery or on the immediately succeeding day.
10. What details are required for the e-Way Bill closure API?
The API requires the e-Way Bill number, closure date and remarks.
What is the revised implementation date?
The revised implementation date is 1 August 2026. The earlier date of 15 June 2026 has been extended by GSTN Advisory 663 dated 9 June 2026.
12. What should ERP/API users do now?
ERP/API users should review the advisory, test sandbox changes, update system fields, check Ship To GSTIN and URP handling, verify closure API fields and prepare before the revised implementation date of 1 August 2026.
13. Can a driver close an e-Way Bill without taxpayer login credentials?
Based on the proposed process, a driver or authorised person may use a public mobile OTP-based closure facility where the designated mobile number is provided. They should not require full taxpayer portal login credentials for such OTP-based closure, subject to final portal implementation.
14. Is entering mobile number for e-Way Bill closure mandatory?
Entering a mobile number for closure purposes should be treated as voluntary as per the proposed process. If it is not provided, closure may still be available to primary portal stakeholders such as supplier, recipient or transporter, subject to final portal implementation.
15. Should ERP users test e-Way Bill closure API before production deployment?
Yes. ERP/API users should test the closure API in the sandbox environment and verify the e-Way Bill number, closure date, remarks and validation response before the revised implementation date of 1 August 2026.
Final Note
This article was originally prepared with reference to GSTN Advisory 661 regarding proposed enhancements in the e-Way Bill portal. It has now been updated to include GSTN Advisory 663 dated 9 June 2026, which extends the implementation timeline to 1 August 2026.
The changes should be treated as implementation-linked until they are live and stabilized on the portal. Businesses, transporters, GST professionals and ERP/API users should verify the latest portal behaviour and official GSTN updates before making final operational or compliance decisions.
This article is for general awareness and practical preparedness only. It should not be treated as legal advice, tax opinion or a guarantee of compliance. Final e-Way Bill generation, data accuracy, API use and compliance responsibility remains with the taxpayer, business or professional handling the transaction.
Official reference: GSTN Advisory 663 dated 9 June 2026
