Summary: The GST Network (GSTN) has clarified that Ship-to GSTIN will become a mandatory field from 1 August 2026 for Bill-to/Ship-to and Combination transactions where the Ship-to party is registered. Where the Ship-to party is unregistered or the GSTIN is unavailable, taxpayers must enter “URP”. The requirement applies to Standalone e-Way Bill generation, Generate IRN + e-Way Bill, and e-Way Bill by IRN APIs, with corresponding validation checks and error codes. The FAQs explain that the requirement does not apply to regular supplies or Bill-from/Dispatch-from transactions, and the Bill-to and Ship-to GSTINs cannot be identical. For export-related movements to ports, ICDs, CFSs, or other export-linked locations, “URP” may be used where no registered Ship-to GSTIN exists. GSTN also clarifies that Ship-to GSTIN will remain confidential and visible only to authorized officers. Stakeholders are advised to update ERP systems, master data, API integrations, and complete Sandbox testing before the implementation date.
Ship-to GSTIN Mandatory from 1st August 2026
Bill-to/Ship-to Transactions, Export Scenarios & API Impact — Explained in Q&A
Based on GSTN FAQs on Bill-to/Ship-to Transactions, Export Scenarios and API Impact, dated 01.07.2026
Mandatory Capture of Ship-to Field & Voluntary Closure of E-Way Bill: FAQs
A. The Change at a Glance
| Particulars | Position |
| What is changing? | Ship-to GSTIN becomes a mandatory data element in Bill-to/Ship-to and Combination transactions where the Ship-to party is registered |
| If Ship-to party is unregistered / GSTIN not available | Enter “URP” (not case-sensitive), wherever applicable |
| Effective date | 1st August, 2026 (revised date; also applies to e-Invoice API changes) |
| Testing environment | Already released in Sandbox — complete testing before production |
| Flows impacted | (i) Standalone Generate EWB API,
(ii) Generate IRN + EWB together, (iii) e-Way Bill by IRN |
| Objective | Traceability of goods movement, stronger audit trail, system-based verification by authorised officers |
B. Understanding the Transaction Types — Q&A
Q1. Which transactions require Ship-to GSTIN and which do not?
Answer: The applicability depends entirely on the transaction type, summarised below:
| Transaction Type | Example
(Billing / Movement) |
Ship-to GSTIN Required? | Treatment |
| Regular | A bills B;
goods move A → B |
NA | Not applicable; must not be sent (Error 616) |
| Bill-to / Ship-to | A bills B;
Goods move A → C on B’s instruction |
Yes — GSTIN of C if registered; “URP” if unregistered | Mandatory (Error 608 if missing) |
| Bill-from / Dispatch-from | A bills B;
Goods move D → B |
NA — buyer is already the Bill-to party | Must not be sent (Error 864); only Dispatch-from details required |
| Combination | A bills B;
Goods move D → C on B’s instruction |
Yes — GSTIN of C if registered; “URP” if not available | Mandatory (Error 608); Dispatch-from details of D also required |
Q2. Can Bill-to GSTIN and Ship-to GSTIN be the same?
Answer: No. The Bill-to party and Ship-to party are expected to be distinct persons. The same GSTIN mentioned in the Bill-to field should not be entered in the Ship-to GSTIN field (Error 618 — standalone EWB; Error 2323 — IRN + EWB flow).
Q3. Goods are delivered to the buyer’s own warehouse / additional place of business — is it Bill-to/Ship-to?
Answer: No. Since Bill-to and Ship-to GSTIN would be the same, do not select Bill-to/Ship-to. Enter it as a regular supply and mention the actual delivery address in the Bill-to address/place of delivery field, as applicable.
- Correct Bill-to/Ship-to: A Ltd., Chennai sells to B Ltd., Bengaluru; B Ltd. directs delivery to C Ltd., Mysuru — different persons.
- Not Bill-to/Ship-to: A Ltd. sells to B Ltd.; goods delivered to B Ltd.’s own warehouse — same GSTIN.
C. Confidentiality of Ship-to GSTIN — Q&A
Q4. Will my customer’s GSTIN be visible on the e-Way Bill?
Answer: No. Trade secrecy is expressly protected:
| What taxpayers/transporters will SEE | What they will NOT see |
| Ship-to address and PIN code on the EWB (existing practice continues) | Ship-to GSTIN — not printed on the EWB (including EWB via IRN) |
| Normal EWB print and GET API responses as at present | Ship-to GSTIN and Ship-to Trade Name — not provided through GET e-Way Bill APIs |
| — | Backend-only capture; visible exclusively to authorised officers for verification and enforcement |
Q5. What if the buyer does not want to share Ship-to GSTIN with the supplier or transporter?
Answer: The buyer may generate the e-Way Bill themselves (as an inward e-Way Bill) and directly enter the Ship-to GSTIN in the system. The transporter may otherwise generate the EWB if the required details are provided.
D. Export & Merchant Exporter Scenarios — Q&A
Q6. What is entered as Ship-to GSTIN when goods move to a port/ICD/CFS for export?
Answer: In export sub-supply type Bill-to/Ship-to transactions, “URP” is proposed to be entered where the Ship-to location is export-linked (port, airport, ICD, CFS, customs area, freight forwarder, CHA-nominated premises, etc.) and no domestic registered Ship-to GSTIN is applicable. The actual Indian destination address and PIN code should be entered.
Q7. Does entering “URP” make it a domestic supply to an unregistered person?
Answer: No. URP entry is only a system-level treatment for EWB generation in export-related movement. The nature of export is determined from the export invoice, shipping bill, customs documents, transport documents and other applicable records.
Q8. How are merchant exporter transactions handled?
Answer: Where goods are billed to a registered merchant exporter and moved directly to an export-linked location: Bill-to GSTIN = merchant exporter’s GSTIN; Ship-to GSTIN is mandatory wherever the Ship-to location is registered, and “URP” may be entered where GSTIN is not available.
E. API Impact — Validation & Error Code Matrix
Q9. What changes are in the Standalone Generate EWB API?
| Sl. | Validation / Requirement | Treatment / Error Code |
| 1 | Ship-to GSTIN is mandatory in Ship-to and Combination transactions | Error 608 |
| 2 | Ship-to Trade Name | Optional (may be sent) |
| 3 | Ship-to GSTIN should not be sent in Regular transactions | Error 616 |
| 4 | Ship-to GSTIN should not be sent in Bill-from/Dispatch-from transactions | Error 864 |
| 5 | Bill-to GSTIN and Ship-to GSTIN should not be the same in Ship-to and Combination transactions | Error 618 |
| 6 | GSTIN must match State Code; PIN code must correspond to State Code | Validation applies |
| 7 | Bulk generation — record with error fails; other valid requests continue to generate EWBs | Existing behaviour continues |
Q10. What changes in the e-Invoice API (Generate IRN + EWB together)?
Answer: “ShipDtls.Gstin” in the Generate IRN payload schema becomes conditionally mandatory where e-Way Bill generation is required:
| Sl. | Validation / Requirement | Treatment / Error Code |
| 1 | “ShipDtls.Gstin” conditionally mandatory where ship details are provided and EWB is required; “URP” where GSTIN not available | Error 5002 (with JSON parameter display name) |
| 2 | Bill-to GSTIN and Ship-to GSTIN should not be the same if ship details are provided | Error 2323 |
| 3 | Ship-to State Code should match Ship-to GSTIN State Code | Error 2325 |
| 4 | Ship-to PIN Code should belong to Ship-to State Code | Error 3039 |
Q11. What changes in the e-Way Bill by IRN API?
| Sl. | Validation / Requirement | Treatment / Error Code |
| 1 | GSTIN and Trade Name added in ExpShipDtls; GSTIN mandatory | Error 5001 (with JSON parameter display name) |
| 2 | Export EWBs — ship details (incl. GSTIN) provided during IRN generation can be replaced | Allowed |
| 3 | B2B and SEZ — ship details provided during IRN generation cannot be replaced | Error 2324 |
| 4 | If GSTIN was not provided at IRN stage — can be provided during EWB by IRN | Allowed |
| 5 | Ship-to State Code should match Ship-to GSTIN State Code | Error 4074 |
| 6 | Ship-to PIN Code should belong to Ship-to State Code | Error 3039 |
Q12. Is the requirement limited to standalone EWB generation?
Answer: No. It extends equally to the IRN-related flows — Generate IRN + EWB together and e-Way Bill by IRN — as per the respective API changes. The e-Invoice API changes also go live on 1st August, 2026.
Q13. In bulk EWB generation, will one defective record fail the entire batch?
Answer: No. Existing behaviour continues — only the request with the error fails; other valid requests continue to generate e-Way Bills.
F. Readiness Checklist — Who Must Do What Before 1st August 2026
| Sl. | Stakeholder | Action Required |
| 1 | Taxpayers | Identify Bill-to/Ship-to and Combination transactions; start capturing Ship-to GSTIN/URP; update ERP and master data; map third-party ship-to locations |
| 2 | ERP / GSP / ASP / IRP | Update API payloads for standalone EWB, IRN + EWB and EWB by IRN flows |
| 3 | Business users | Ensure Ship-to address and PIN code are correctly maintained |
| 4 | Exporters/merchant exporters | Identify export-linked Ship-to locations where URP treatment may apply |
| 5 | Transporters | Coordinate with taxpayers for required details, especially where EWB is generated by the transporter |
| 6 | All stakeholders | Complete Sandbox testing before 1st August, 2026 |
G. Key Takeaway
This is not merely a portal-field change — it is a system-driven traceability measure that will hard-stop e-Way Bill and IRN generation where ERP systems and master data are not ready. ERP reconfiguration, vendor/customer master updates and Sandbox testing should commence immediately.
*******
Author’s Note: The views expressed in this article are personal and based on current GSTN functionalities and legal interpretations. Readers are encouraged to refer to the specific facts of their case and the latest circulars before proceeding. While due care has been taken in preparing this article, certain mistakes and omissions may creep in. The author does not accept any liability for any loss or damage of any kind arising out of any inaccurate or incomplete information in this document nor for any actions taken in reliance thereon.
Author Bio
