From 15 June 2026, businesses must enter the Ship-To GSTIN on e-Way Bills whenever the billing address and delivery location are different. This change affects Bill-To/Ship-To transactions where goods are delivered to a location other than the invoiced entity. It directly impacts e-Way Bill generation, invoicing workflows and GST compliance.
Until now, the Ship-To GSTIN field on the e-Way Bill portal was optional. Based on GSTN Advisory No. 661 dated 21 May 2026, it now becomes mandatory in applicable cases. Missing or incorrect Ship-To GSTIN details can block e-Way Bill generation and may trigger scrutiny under Sections 129 and 130 of the Central Goods and Services Tax (CGST) Act, 2017, if the details on the invoice and e-Way Bill do not align.
What are the seven business scenarios where the new ship-to GSTIN rule applies?
Below are the seven most common business situations in which this rule applies, along with what businesses in each scenario must do.
Scenario 1: Head office billing, branch or warehouse delivery
This scenario applies when goods are billed to a head office GSTIN but delivered directly to a branch, depot or warehouse registered under another GSTIN.
Many companies centralise procurement through their head office but move goods directly to one of their branches, depots or warehouses in another city. Under the new rule, the GSTIN of the receiving branch or warehouse becomes mandatory in the Ship-To field. Businesses with multi-location GST registrations need to ensure their e-Way Bill software can pull and populate the correct GSTIN for the facility receiving a given consignment.
Scenario 2: Retailer or trader drop-shipping to a customer
This scenario applies when a retailer or trader issues an invoice but instructs the supplier to deliver the goods directly to the customer.
A retailer places an order with a wholesaler or manufacturer and instructs the wholesaler or manufacturer to dispatch the goods directly to the retailer’s customer. If the customer is a registered business, their GSTIN must appear in the Ship-To field of the e-Way Bill. If the customer is an individual or an unregistered entity, the drop-shipping business must enter “URP”. Either way, leaving the field blank is no longer an option.
Scenario 3: Inter-company or related-party transfers
This scenario applies when goods are billed to one entity but delivered to a related entity operating under a different GSTIN.
A parent company places an order with a vendor and directs delivery to a subsidiary, or a holding company directs goods to an associate firm. These transactions already require valuation under CGST Rules 28, 30 and 31 where the parties are related. The GSTIN of the receiving related entity must also be captured at the e-Way Bill stage, adding another layer of documentation.
Scenario 4: Job work send-outs
This scenario applies when goods are sent to a job worker for processing rather than directly to the principal’s location.
A principal manufacturer sends raw materials or semi-finished goods to a job worker for processing. Job work movements are governed by Section 143 of the CGST Act. When an e-Way Bill is required for such movement, the job worker’s GSTIN must now be entered in the Ship-To field. If the job worker is unregistered, the principal enters “URP”.
Scenario 5: Delivery to a project site or construction location
This scenario applies when goods are delivered directly to a project site rather than the company’s registered office or billing address.
A company orders construction materials, equipment or goods from a supplier and requests delivery directly to the project site. If the site is registered under the company’s GSTIN, that GSTIN becomes the correct Ship-To entry. If the site is registered under a separate state, that GSTIN applies. Where the site has no GST registration, “URP” must be entered.
Scenario 6: Dealer-to-dealer delivery at the buyer’s instruction
This scenario applies when goods are billed to one dealer or distributor but delivered directly to another dealer, sub-distributor or channel partner.
A distributor places an order with a manufacturer but directs the goods to one of its dealers or sub-distributors. From 15 June 2026, the dealer’s GSTIN must be entered as the Ship-To GSTIN on the e-Way Bill. Businesses running these arrangements through ERP or API integrations should ensure systems capture the receiving dealer’s GSTIN at dispatch.
Scenario 7: Delivery to an unregistered recipient
This scenario applies when goods are delivered to someone who does not have a GST registration.
Sometimes the delivery address belongs to a small trader, an individual customer or an exempt entity, while billing is done to another party. Where the consignee is unregistered, taxpayers must enter “URP” in the Ship-To GSTIN field. Leaving it blank or using another placeholder will cause validation errors from 15 June 2026 onwards.
Conclusion
The Ship-To GSTIN mandate changes how businesses capture and validate delivery information, especially in Bill-To/Ship-To transactions across multiple locations, customers and supply chains. Businesses that review customer master data, update invoicing workflows and test e-Way Bill processes before 15 June 2026 are more likely to avoid dispatch delays and compliance disruptions.
For businesses handling high transaction volumes or complex delivery networks, using a business management solution such as TallyPrime can make it easier to maintain accurate GST records, reduce manual errors and keep e-Way Bill generation aligned with changing compliance requirements.
