GSTN Introduces Mandatory Ship-to GSTIN in Bill-to/Ship-to Transactions from 1 August, 2026
The Goods and Services Tax Network (GSTN) has released detailed FAQs regarding the mandatory capture of Ship-to GSTIN in specified e-Way Bill and e-Invoice transactions. These changes are aimed at improving the traceability of goods movement, strengthening audit trails, and enabling better system-based verification by tax authorities.
The new requirements will come into effect from 1 August 2026, and GSTN has already made the changes available in the Sandbox environment to allow taxpayers and software providers to complete testing.
Why has GSTN introduced Ship-to GSTIN?
GSTN has made Ship-to GSTIN mandatory in applicable transactions to:
• Improve traceability of movement of goods.
• Strengthen audit trails in Bill-to/Ship-to transactions.
• Enable system-based verification by authorised officers.
• Enhance compliance without compromising business confidentiality.
Importantly, Ship-to GSTIN will not be printed on the e-Way Bill and will not be available through GET e-Way Bill APIs. It will remain visible only to authorised officers for verification purposes.
Which transactions are affected?
1. Regular Transactions
Where billing and delivery happen between the same supplier and buyer.
Example:
A Ltd. sells goods directly to B Ltd.
Ship-to GSTIN Required? - No
2. Bill-to / Ship-to Transactions
Invoice is issued to one party, while goods are delivered to another party on the buyer's instructions.
Example:
A Ltd. bills B Ltd. but ships goods directly to C Ltd.
Ship-to GSTIN Required? - Yes
--> If the consignee is registered → Enter Ship-to GSTIN.
--> If unregistered → Enter URP.
3. Bill-from / Dispatch-from Transactions
Invoice is issued by the supplier, but goods are dispatched from a third-party location.
Example:
A Ltd. bills B Ltd., while goods move from C Ltd. to B Ltd.
Ship-to GSTIN Required? - No
Since delivery is made to the buyer himself, no separate Ship-to GSTIN is required.
4. Combination Transactions
Both Bill-to/Ship-to and Dispatch-from concepts exist simultaneously.
Example:
A Ltd. bills B Ltd., goods move from C Ltd. to D Ltd.
Ship-to GSTIN Required? - Yes
Can Bill-to GSTIN and Ship-to GSTIN be the same? - No
• If goods are delivered to the buyer's own warehouse or additional place of business under the same GSTIN, the transaction should not be treated as a Bill-to/Ship-to transaction.
• Instead, it should be reported as a regular supply transaction by mentioning the actual delivery address.
• Confidentiality is Protected
• One concern raised by businesses was whether their customer information would become visible.
GSTN has clarified that:
• Ship-to GSTIN will not appear on the e-Way Bill.
• Ship-to GSTIN will not be shared through GET e-Way Bill APIs.
• Transporters and taxpayers will continue to see only the Ship-to address and PIN code.
• Only authorised officers can access Ship-to GSTIN for verification purposes.
• This ensures business confidentiality while improving tax administration.
Who should generate the e-Way Bill?
• GSTN has clarified different practical situations:
• Supplier generates EWB
• Supplier may enter Ship-to GSTIN if provided by the buyer.
• Buyer wants confidentiality
• Buyer may generate the e-Way Bill himself without sharing Ship-to GSTIN with the supplier.
• Transporter generates EWB
• Possible if all required details are available. Otherwise, the buyer may generate the e-Way Bill.
• Special provisions for Export Transactions
• Exports frequently involve movement of goods to ports, airports, ICDs, CFSs or freight forwarders.
GSTN has clarified:
• Where no domestic registered Ship-to GSTIN exists, URP may be entered.
• Entering URP does not convert the export into a domestic supply.
• Export nature will continue to be determined based on export invoice, shipping bill, customs documentation and other supporting records.
• Actual Indian export-linked destination (Port/Airport/ICD/CFS etc.) should be mentioned as Ship-to address.
• Merchant exporter transactions are also covered under these rules.
API Changes:
GSTN has introduced changes across multiple systems.
• Standalone e-Way Bill API
• Key validations include:
• Ship-to GSTIN mandatory for Bill-to/Ship-to and Combination transactions.
• Ship-to GSTIN should not be entered in Regular transactions.
• Ship-to GSTIN should not be entered in Bill-from/Dispatch-from transactions.
• Bill-to GSTIN and Ship-to GSTIN cannot be identical.
GSTN recommends immediate preparation:
• Update ERP and accounting software.
• Capture Ship-to GSTIN wherever applicable.
• Map third-party delivery locations.
• Update API payloads (ERP/GSP/ASP/IRP).
• Verify Ship-to address and PIN code master data.
• Complete Sandbox testing before production rollout.
• Train operational and logistics teams.
• Quick Readiness Checklist
• Identify Bill-to/Ship-to and Combination transactions.
• Start collecting Ship-to GSTIN or URP wherever applicable.
• Update ERP, API integrations and master data.
• Review export and merchant exporter processes.
• Coordinate with transporters regarding new requirements.
• Complete Sandbox testing before 1 August 2026.
Please read the official GSTN FAQs and click on the link below to understand all scenarios, validations and implementation details regarding the mandatory Ship-to GSTIN requirements.
Disclaimer: This article is for informational purposes only and should not be construed as legal or professional advice. Taxpayers should consult their tax advisor based on the facts of their specific case before taking any action.
