What’s Changing and Why It Matters to You

The GST Network (GSTN) has made the “Ship-To GSTIN” a mandatory data field for all Bill-to/Ship-to e-Way Bill transactions, effective 1 August 2026 — whether the e-Way Bill is generated directly on the portal or through e-Invoice/API integrations. Where the consignee (the party actually receiving the goods) is unregistered, taxpayers must enter “URP” in the Ship-to GSTIN field.

This is a data-capture and traceability reform, not a new tax or a new document format. But it directly affects day-to-day dispatch practice for any business where the invoice party and the delivery party are not the same — depot transfers, project-site supplies, third-party deliveries, e-commerce fulfilment, job-work dispatches, branch deliveries and consignment arrangements all fall within its scope.

The Key Nuance Most Businesses Get Wrong

Ship-to GSTIN must be captured in the backend as a mandatory field — but it will NOT be printed as a separate line on the e-Way Bill, and will NOT appear in the standard GET e-Way Bill API response.

This means compliance cannot be judged by looking at the printed copy. Many businesses will wrongly assume the field is optional simply because it isn’t visible on the document — it is mandatory for generation even though it’s invisible on the output.

The Confidentiality Question

A frequent concern is whether entering a customer’s GSTIN in the Ship-To field exposes that customer’s identity to the original supplier further up the chain.

Q: If I enter my customer’s GSTIN in the Ship-To field, will my supplier see who my customer is?

A: No. Ship-to GSTIN and Ship-to Trade Name will not be printed on the e-Way Bill, will not be displayed to taxpayers or transporters, and will not be provided through the GET e-Way Bill APIs. It remains visible only to authorised tax officers for verification — trade confidentiality between commercial parties is preserved.

Practical Scenarios Relevant to Client Businesses

Direct delivery to buyer’s customer:

A supplier bills a dealer, but the dealer instructs delivery straight to its own customer at a different location. The dealer is Bill-to; the customer is Ship-to. If the customer is registered, that GSTIN must be captured — even though the printed e-Way Bill will still show only the standard Bill-to GSTIN and the Ship-to address.

Delivery to an unregistered site:

Goods are billed to a registered contractor but delivered to a temporary, unregistered site office. Here the Ship-to GSTIN field must contain “URP” — it cannot be left blank merely because there is no GSTIN to enter.

Head office billing, branch/factory delivery (different GSTINs):

Invoice is raised on a company’s head-office GSTIN, but goods are delivered to a factory or branch holding a separate GST registration. Because separate registrations are distinct “persons” under GST, the factory/branch GSTIN must be captured as Ship-to — treating it as “same company, so it doesn’t matter” is a common and avoidable error.

Third-party logistics / warehouse delivery:

A principal supplies a dealer but directs delivery to a registered 3PL warehouse. If that warehouse GSTIN is the actual consignee, it must be captured as Ship-to — taxpayers should distinguish between a warehouse acting merely as a transporter’s stop versus one acting as the actual consignee.

Important Clarification for Branch/HO Structures Under ONE GSTIN

Where the Bill-to and Ship-to are the same legal person under the same GSTIN (e.g., head office billed, goods delivered to that same entity’s branch or additional place of business), this is treated as a REGULAR transaction — not a Bill-to/Ship-to transaction.

In this case, continue as today: Bill-to GSTIN is the company’s GSTIN, and the branch location is entered simply as the Ship-to address (not a separate GSTIN). Once the new validations go live, Bill-to GSTIN and Ship-to GSTIN cannot in fact be identical in a true Bill-to/Ship-to-type e-Way Bill — so same-GSTIN HO-to-branch movements should not be forced into that structure.

The rule genuinely ‘bites’ only where two different registered persons are involved in the chain — drop-shipments, 3PL/warehouse deliveries to a separately-registered party, and project-site deliveries under a distinct project GSTIN.

Common Mistakes to Avoid

• Copying the Bill-to GSTIN into the Ship-to GSTIN field merely because delivery is on the customer’s instruction — once new validations are live, the two cannot be identical in a genuine Bill-to/Ship-to case.
• Leaving Ship-to GSTIN blank on the assumption that it’s optional because it doesn’t print on the e-Way Bill.
• Updating the Ship-to address correctly but forgetting to update the consignee GSTIN in ERP master data.
• Not using “URP” for an unregistered Ship-to party.
• Treating project sites, warehouses or branches as plain addresses instead of recognising them as separate GST registrations where applicable.
• Assuming the change applies only to manual portal users and not to e-Invoice/API-integrated billing systems — it applies to both.

Why This Also Matters for Future Scrutiny

Ship-to GSTIN becomes another backend data point tying a movement of goods to a specific consignee registration. Where invoices, e-Way Bills, transport documents, stock records and recipient books are all consistent, this strengthens a taxpayer’s position in any later verification. Where they are inconsistent, the mismatch can itself become a ground for departmental scrutiny — relevant to matters such as genuineness of delivery, input tax credit conditions, and general movement-verification checks. A related Voluntary e-Way Bill Closure facility is being introduced the same date, allowing formal closure of an e-Way Bill once delivery is complete, which further strengthens the end-to-end movement trail available to the department.

Action Checklist Before 1 August 2026

For your business/accounts team

• Map out all recurring Bill-to/Ship-to movements — dealer drop-ships, branch deliveries, project sites, warehouse/3PL arrangements.
• Separate out which Ship-to parties are registered (capture GSTIN) versus unregistered (use “URP”).
• Update customer master, consignee master and branch master data with correct GSTIN mapping.
• Brief dispatch and billing staff — the Ship-to registration status must be confirmed before generating the e-Way Bill, not assumed from the invoice party alone.
• Run a few test transactions in the run-up to 1 August 2026, especially for high-volume dispatch patterns.

For ERP / API-integrated billing systems

• Review and update field mapping so Ship-to GSTIN is correctly pushed to the e-Invoice and e-Way Bill-by-IRN APIs.
• Add validation so the field cannot remain blank in genuine Bill-to/Ship-to cases.
• Build in GSTIN / state code / PIN code consistency checks to reduce API rejection risk.
• Complete Sandbox testing of the Generate-IRN + e-Way Bill flow ahead of the production rollout.

On correcting errors: treat this as a prevention issue rather than a post-dispatch fix. Once goods are already moving, correcting a wrong Ship-to GSTIN can create practical and documentation complications, so validation before generation is the safer route.