FAQs on Mandatory Capture of Ship-to Field and Voluntary Closure of E-Way Bill, 2026
GST
Dated:- 2-7-2026
“Dear Stakeholders,
It is informed that various doubts, queries and representations received from taxpayers, trade, GST Suvidha Providers (GSPs) and other stakeholders regarding the mandatory capture of the Ship-to field in E-Way Bills and the voluntary closure of E-Way Bills have been examined. Accordingly, a comprehensive set of Frequently Asked Questions (FAQs) has been prepared to provide necessary clarifications on the applicable system validations, procedural requirements and manner of compliance. The stakeholders are requested to go through the FAQs for familiarisation with the applicable requirements, system validations and procedure to be followed.
GOODS AND SERVICES TAX NETWORK
(A Government Enterprise)
4th Floor, World Mark-1, East Wing, Asset 11, Hospitality
District, Aerocity, New Delhi 110037
Tel: 011-49111200, Fax: 011-49111210
E-Mai
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
of implementation is 1st August, 2026.
Q4. Are the changes available in Sandbox?
The relevant changes have been released in Sandbox for testing. Taxpayers, ERP vendors, GSPs, ASPs, private IRPs and other system integrators are advised to complete testing and readiness before production implementation.
Q5. Why is Ship-to GSTIN being captured?
Ship-to GSTIN is being captured to improve traceability of goods movement, strengthen the audit trail in Bill-to/Ship-to transactions, and enable system-based verification by authorised officers.
2. Business Transaction Types
Sl. No.
Transaction Type
Billing Flow
Movement of Goods
Ship-to GSTIN Treatment
1
Regular
Between supplier and buyer
From supplier to buyer
No. Ship-to GSTIN is not applicable to regular transactions
2
Bill-to/Ship-to
Between supplier and buyer
From supplier to third party as instructed by buyer
Mandatory where Ship-to party is registered. URP may be entered for supp
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
.
Q8. What is a Bill-from/Dispatch-from transaction?
A Bill-from/Dispatch-from transaction is one where billing is between the supplier and the buyer, but goods are dispatched from a third-party location. For example, A Ltd. bills B Ltd., but goods are dispatched from C Ltd. to B Ltd.
Q9. What is a Combination transaction?
A Combination transaction involves both Bill-to/Ship-to and Bill-from/Dispatch-from features. Billing is between the supplier and buyer, but goods are dispatched from a third party and delivered to a fourth party. For example, A Ltd. bills B Ltd., but goods move from C Ltd. to D Ltd. on the instruction of B Ltd.
Q10. Can Bill-to GSTIN and Ship-to GSTIN be the same in a Bill-to/Ship-to transaction?
No. In a Bill-to/Ship-to transaction, the Bill-to party and Ship-to party are expected to be distinct persons. Accordingly, the same GSTIN as mentioned in the Bill-to field should not be entered in the Ship-to GSTIN field.
Example 1 – Correct Bill-to/Sh
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
No. Ship-to GSTIN shall not be printed on the e-Way Bill generated on the e-Way Bill portal.
Q12. Will Ship-to GSTIN be provided through GET e-Way Bill APIs?
No. Ship-to GSTIN shall not be provided through the GET e-Way Bill APIs.
Q13. What will continue to be visible on the e-Way Bill?
The relevant Ship-to address and PIN code shall continue to be shown as per the existing practice.
Q14. Who will be able to view the Ship-to GSTIN?
Ship-to GSTIN will be captured in the system for official purposes. It will be visible only to authorised officers for verification and enforcement purposes.
Q15. How is trade secrecy protected?
Trade secrecy is protected by ensuring that Ship-to GSTIN is captured in the system backend but is not printed on the e-Way Bill, is not displayed to taxpayers or transporters, and is not shared through GET e-Way Bill APIs.
4. Role-wise Generation Scenarios
Q16. If the supplier generates the EWB, how will Ship-to GSTIN be entered?
W
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
sed officers.
5. Export and Merchant Exporter Scenarios
Q20. How does Bill-to/Ship-to arise in export transactions?
In export transactions, the goods may be billed to an overseas buyer, while the goods are physically moved from the supplier's premises in India to a port, airport, ICD, CFS, customs area, freight forwarder location, CHA-nominated premises, or any other export-linked location.
Q21. What should be entered as Ship-to GSTIN in export Bill-to/Ship-to cases?
In export sub-supply type involving Bill-to/Ship-to transactions, Ship-to GSTIN is proposed to be entered as “URP”, where the Ship-to location is export-linked and no domestic registered Ship-to GSTIN is applicable.
Q22. Does entering URP mean that the transaction is treated as a domestic supply to an unregistered person?
No. Entry of URP is a system-level treatment for EWB generation in export-related movement. The nature of export shall be determined based on export invoice, shipping bill, customs do
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
ns.
Sl. No.
Validation / Requirement
System Treatment / Error Code
1
Ship-to GSTIN mandatory in Ship-to and Combination transactions
Error Code: 608
2
Ship-to Trade Name
May be sent but optional
3
Ship-to GSTIN should not be sent in Regular transactions
Error Code: 616
4
Ship-to GSTIN should not be sent in Bill-from/Dispatch-from transactions
Error Code: 864
5
Bill-to GSTIN and Ship-to GSTIN should not be same in Ship-to and Combination transactions
Error Code: 618
Q26. Will Ship-to GSTIN field be rejected in Regular transactions?
Yes. Ship-to GSTIN should not be sent in Regular transactions. Error Code 616 is applicable.
Q27. Will Ship-to GSTIN field be rejected in Bill-from/Dispatch-from transactions?
Yes. Ship-to GSTIN should not be sent in Bill-from/Dispatch-from transactions. Error Code 864 is applicable.
Q28. Is Ship-to Trade Name mandatory in standalone EWB API?
No. Ship-to Trade Name may be sent but it is o
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
Ship-to GSTIN should not be same if ship details are provided
Error Code: 2323
3
Ship-to State Code should match SHIP TO GSTIN State Code
Error Code: 2325
4
Ship-to PIN Code should belong to Ship-to State Code
Error Code: 3039
Q32. Which e-Invoice field is proposed to be made conditionally mandatory?
In the Generate IRN payload schema, “ShipDtls.Gstin” shall be made conditionally mandatory where e-Way Bill generation is required.
Q33. What is the treatment where Ship-to GSTIN is not available in IRN + EWB flow?
Where GSTIN is not available, “URP” may be provided, wherever applicable.
Q34. Can the same GSTIN be entered in Bill-to and Ship-to fields in IRN + EWB flow?
No. If ship details are provided, Bill-to GSTIN and Ship-to GSTIN should not be the same.
8. Impact in e-Way Bill by IRN API
Q35. What is the change in e-Way Bill by IRN API?
GSTIN and Trade Name have been added in ExpShipDtls, and GSTIN has been made mandatory.
Sl. No.
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
stage, can it be provided during EWB by IRN?
Yes. If GSTIN is not provided during IRN generation, it can be provided during e-Way Bill by IRN.
Q38. Will Ship-to GSTIN be printed in EWB generated through IRN?
No. Ship-to GSTIN shall not be printed in the EWB and shall not be provided through GET EWB APIs.
9. Common Questions Raised by Stakeholders
Q39. Is the mandatory Ship-to GSTIN requirement applicable only to standalone EWB generation?
No. The requirement is also being extended to IRN-related flows, namely Generate IRN and EWB together and e-Way Bill by IRN, as per the respective API changes.
Q40. When will the e-Invoice API changes be implemented in production?
The proposed date of implementation is 1st August, 2026.
Q41. Will Ship-to GSTIN and Ship-to Trade Name be available in Get EWB Details API?
Ship-to GSTIN shall not be provided through GET e-Way Bill APIs.
Ship-To Trade name will also not be provided in E Way Bill details.
Q42. Will a revi
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
rdinate with taxpayers for required details, especially where EWB is generated by transporter.
6
All stakeholders
Complete Sandbox testing before 1st August, 2026.
11. Business Transaction scenarios:
Q. No.
Transaction Type
Description
Example
Whether “Ship-To GSTIN” is Required?
Q6
Regular
A transaction where the invoice is issued to the buyer (Bill-to), and the goods are delivered to a Same person.
A Ltd. sells goods to B Ltd. and the goods move directly from A Ltd. to B Ltd.
No. This is not treated as a Bill to Ship to transaction.
Q7
Bill-to / Ship-to Transaction
A transaction where the invoice is issued to the buyer (Bill-to), but the goods are delivered to a third party(Ship-to) as per the buyer's instructions.
A Ltd. raises the invoice on B Ltd., but ships the goods directly to C Ltd. on the instruction of B Ltd.
Yes. The GSTIN of C Ltd. (Ship-To party) should be entered in the Ship-To GSTIN field, where the consignee
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
on of B Ltd.
Yes. The GSTIN of D Ltd. (Ship-To party) should be entered in the Ship-To GSTIN field, where D Ltd. is a registered person. The Dispatch-From details should also be provided for C Ltd.
FAQs on Voluntary Closure of e-Way Bill: Business Scenarios, API Impact and Portal Behaviour
(FAQs for stakeholder guidance and system readiness)
Date: 01.07.2026
1. Scope and Implementation
Q1. What is the Voluntary e-Way Bill Closure facility?
The Voluntary e-Way Bill Closure facility enables closure of an e-Way Bill after delivery of goods has been completed. It is intended to record completion of movement in the system.
Q2. Is closure of EWB mandatory?
No. Closure of EWB is voluntary in nature.
Q3. What is the revised implementation date?
The revised date of implementation is 1st August, 2026.
Q4. When can an EWB be closed?
An E-Way Bill may be closed after completion of delivery of goods. It is advised that such closure should be ca
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
ier, recipient and transporter?
For suppliers, recipients and transporters, the closure option is available after login under the e-Way Bill section of the portal.
Q7. What are the portal modes for closure?
Closure can be performed EWB-wise or date-wise for logged-in users.
Q8. What is EWB-wise closure?
EWB-wise closure means that a specific e-Way Bill number is selected and closed after delivery is completed.
Q9. What is date-wise closure?
Date-wise closure allows the logged-in user to view EWBs for a particular date and close eligible EWBs after delivery.
Q10. Can multiple EWBs be closed through date-wise closure on the portal?
Yes, the option is available.
Q11. Can a driver or authorised person close an EWB?
Yes. A driver or authorised person can close an EWB through the portal-based mobile number closure facility, where the mobile number has been provided for closure purposes.
Q12. How does mobile number-based closure work?
All active EWBs lin
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
ulk closure?
No, the current API does not support date-wise bulk closure.
Q18. Is there any API to retrieve EWBs marked as closed, including date-wise retrieval?
No. Currently, no separate API has been introduced to retrieve EWBs that have been marked as closed, including date-wise retrieval of closed EWBs. Such functionality may be considered in future after the closure module is stabilised and based on operational requirements emerging from field usage.
Q19. Will Get EWB Details API show a separate Closed status or closed date?
At present, no separate provision has been introduced in the Get EWB Details API to return a Closed status or Closed Date. For the initial stabilisation period, the existing status framework is being continued. A separate status of “Closed” is proposed to be introduced in due course.
Q20. Can APIs capture the mobile number for closure by driver or authorised person?
No. At present, there is no provision in the APIs to capture or specify th
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
s existing status framework is being continued so that trade and system users are not adversely impacted during the transition phase.
Q26. If an EWB is marked as closed, will it immediately show as “Closed”?
During the initial stabilisation period, a separate “Closed” status may not be reflected in the existing status framework. However, closure details will be captured in the system.
Q27. Can user actions be performed after an EWB is marked as closed?
Yes. As of now, user actions such as Update Transporter, Extend Validity, Vehicle Updation and other permitted modifications will continue to remain available even after the EWB has been marked as closed.
Q28. Why are post-closure actions allowed initially?
This relaxation is being provided for the benefit of users during the initial stabilisation period.
Q29. Will post-closure actions be restricted later?
Yes. Once the system is stabilised, necessary restrictions will be introduced and post-closure actions will b
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
very of goods has been completed.
Q34. Is closure the same as expiry of EWB?
No. Expiry is based on the validity period of the EWB, whereas closure is a user action to record completion of delivery.
5. Impact in e-Invoice API and e-Way Bill by IRN
Q35. Is there any impact of voluntary closure on e-Invoice API?
The e-Invoice API facilitates only the generation of the e-Way Bill. After generation, all further operations relating to the e-Way Bill are handled exclusively through the EWB APIs. Accordingly, no impact is envisaged on the e-Invoice API.
Q36. Is there any impact of voluntary closure on Generate IRN and EWB together flow?
There is no impact.
Q37. Is there any impact of voluntary closure on e-Way Bill by IRN API?
There is no impact.
Q38. Can an EWB generated along with IRN be closed?
Yes, it can be closed.
Q39. Can an EWB generated using IRN be closed?
Yes, it can be closed.
6. Business Scenarios
Scenario 1: Supplier closes EWB after
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
updation. The driver or authorised person may then close the EWB through the portal-based mobile number closure facility.
Scenario 6: Closure through API by ERP-integrated taxpayer
An ERP-integrated taxpayer closes EWBs through API after delivery by transmitting the EWB number, closure date and remarks.
Scenario 7: Date-wise closure by transporter
A transporter handles multiple EWBs generated on a single date. After delivery of goods, the transporter uses date-wise closure on the portal to identify and close eligible EWBs.
Scenario 8: EWB marked as closed but vehicle update attempted
During the initial stabilisation period, vehicle updation and other permitted actions will continue to remain available even after closure. After stabilisation, such post-closure actions may be suitably restricted.
Scenario 9: API user wants date-wise list of closed EWBs
At present, no separate API has been introduced for date-wise retrieval of closed EWBs. Such functionality may b
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
closure through API
Not available currently; portal only
12
Remarks character limit / fixed reason code
Upto 100 characters
13
ClosedBy in API / Get Details response
Not available currently
14
Closure date and remarks in EWB print
Not available currently
8. Action Required from Stakeholders
Sl. No.
Stakeholder
Action Required
1
Taxpayers
Create internal process to close EWB after delivery wherever the facility is used.
2
Transporters
Familiarise operational teams with EWB-wise/date-wise closure and driver-based closure.
3
Drivers / authorised persons
Use portal-based mobile number closure where mobile number has been provided.
4
ERP/GSP/ASP/API users
Implement closure API using EWB number, closure date and remarks.
5
All stakeholders
Note that post-closure actions are temporarily allowed during initial stabilisation period but may be restricted later.
Thank you,
Team GSTN
=============
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =