Welcome to TRUSTLINK
Ship-To GSTIN became a mandatory field on e-way bills and e-invoices for Bill-To/Ship-To transactions from 1 August 2026. If your business invoices one GSTIN but delivers goods to a different registered location, you must now capture that recipient’s GSTIN correctly in both the IRN API and the e-way bill API, or your shipment risks detention under Section 129 of the CGST Act.
This change has already caused delays for distributors, e-commerce fulfillment centers, and manufacturers who route goods through warehouses different from the billing address. Here’s what changed, who it hits hardest, and the exact steps to get your systems compliant before your next shipment leaves the dock.
Table of Contents
What Changed on 1 August 2026
GSTN first announced this update through an advisory on 20 May 2026 and originally planned to roll it out on 15 June 2026. Vendors, ERP providers, and GST Suvidha Providers pushed back, saying they needed more time to update their systems. GSTN agreed and pushed the live date to 1 August 2026, giving businesses roughly six extra weeks.
The core change is simple to state and harder to implement: when your invoice bills one GSTIN but the goods physically move to a different registered address (a warehouse, a branch office, a job-worker’s premises), you must now report the Ship-To GSTIN as a mandatory field in both the Invoice Registration Portal (IRP) API and the e-way bill API. If the recipient at the delivery point isn’t GST-registered, you report “URP” (unregistered person) instead of leaving the field blank or guessing.
For B2B and SEZ transactions, whatever Ship-To detail you capture at the point of IRN generation becomes final. You can’t quietly edit it later in the e-way bill without triggering a fresh validation.
GSTN also introduced a second, smaller change alongside this: a voluntary e-way bill closure facility. This lets you formally mark an e-way bill as closed once goods reach their destination, instead of letting it sit open until it expires on its own. It’s optional, but it tightens your audit trail if you ever face a GST scrutiny notice.
Why This Matters More Than It Looks
On paper, this is one mandatory field. In practice, it exposes a gap that a lot of Indian businesses have been quietly living with for years: billing systems and dispatch systems that don’t talk to each other cleanly.
Take a common scenario. A Mumbai-based distributor bills a retail chain’s head office GSTIN in Delhi but ships stock directly to the chain’s regional warehouse in Pune, which holds its own separate GSTIN. Before August 2026, many ERPs picked up the Ship-To address as free text, not as a validated GSTIN. Now that field has to match a real, active GSTIN on the GST portal, or the e-way bill generation fails outright.
If your dispatch team has been manually typing addresses into a shipping label field without cross-checking the GSTIN, you now have a compliance gap that stops goods from moving. And once a truck is on the road with an incomplete or mismatched e-way bill, GST enforcement officers have the authority to detain the vehicle and the goods under Section 129, with release conditional on payment of tax and penalty.
Who Is Most Exposed
Not every business feels this equally. You’re at higher risk of disruption if you operate in any of these categories.
Distribution and FMCG businesses that bill a central purchasing office but ship to multiple regional depots under separate GSTINs. Every depot needs to be mapped correctly in your master data.
E-commerce sellers and marketplace fulfillment operations where goods move from a seller’s warehouse to a marketplace fulfillment center registered under a different GSTIN before reaching the end customer.
Manufacturers using job workers, where raw material or semi-finished goods move to a job worker’s premises that carries its own GST registration separate from the principal manufacturer.
Businesses with multiple GSTINs under one PAN, where inter-branch stock transfers are common and Ship-To and Bill-To addresses rarely match by default.
If none of these describe your operation, and you invoice and deliver to the same registered address in nearly every transaction, this update changes very little for you day to day.
The Compliance Checklist: What to Fix Before Your Next Dispatch
1. Audit your customer master data. Pull every customer record where Ship-To and Bill-To addresses differ. For each one, confirm the correct GSTIN registered against that delivery address using the GST portal’s search facility. Don’t assume the address on file is still accurate. Businesses relocate warehouses and open new depots without always notifying every vendor.
2. Update your ERP or billing software. Check with your ERP vendor or accounting software provider on whether their latest release captures Ship-To GSTIN as a validated, mandatory field rather than free text. Most major providers pushed updates in June and July 2026 specifically for this change. If you’re on an older version, this is the moment to upgrade.
3. Train your dispatch and billing teams separately. The people who raise invoices and the people who physically dispatch goods often work in different departments and sometimes different cities. Both need to understand that the Ship-To GSTIN field is no longer optional and that errors here can stop a shipment mid-route.
4. Build a URP protocol. Decide now how your team flags shipments going to unregistered recipients, so “URP” gets entered correctly instead of being left blank or filled with a guess.
5. Reconcile before generating the e-way bill, not after. Because B2B and SEZ Ship-To details lock in at IRN generation, fix errors before you generate the invoice reference number. Correcting after the fact is far more painful than getting it right the first time.
6. Consider the voluntary closure facility for high-value shipments. If you regularly move high-value goods or operate in a sector prone to GST scrutiny, closing e-way bills formally on delivery strengthens your documentation trail.
What Happens If You Get It Wrong
An incorrect or missing Ship-To GSTIN on a shipment that should have carried one can result in the e-way bill being flagged as invalid. If your goods are intercepted while in transit under an invalid e-way bill, Section 129 allows tax authorities to detain both the conveyance and the goods. Release typically requires payment of the applicable tax and a penalty, and disputing the detention afterward eats time and legal cost that most businesses would rather avoid entirely.
Beyond the immediate transit risk, mismatched Ship-To data creates downstream reconciliation headaches. GSTR-2B, GSTR-1, and your e-way bill records need to tell a consistent story. When they don’t, it becomes a red flag during GST audits and increases your odds of receiving an ASMT-10 scrutiny notice.
How This Interacts With Your Broader GST Compliance
The Ship-To GSTIN requirement doesn’t sit in isolation. It connects directly to the invoice-level ITC validation and reconciliation rules that GST authorities now apply more strictly across the board. When your Ship-To data is wrong, the mismatch doesn’t stay contained to the e-way bill. It shows up later when the recipient tries to reconcile their GSTR-2B against their books, and it can flag your supply chain for closer scrutiny even if every other part of your filing is accurate.
This is worth internalizing because businesses sometimes treat e-way bill compliance and GST return filing as two separate workstreams handled by two separate teams. In practice, a dispatch error in July shows up as a reconciliation problem in August and a scrutiny notice in September. Building a single accurate source of truth for customer GSTIN and delivery address data, shared between your billing, dispatch, and GST filing teams, removes this chain of downstream problems at the point where it’s cheapest to fix.
A Practical Timeline for Getting Compliant
If you haven’t started yet, here’s a realistic sequence to follow rather than trying to fix everything at once.
Week one: Pull a full list of customers and locations where Ship-To and Bill-To addresses differ. Cross-check each against the GST portal’s active GSTIN search.
Week two: Confirm your ERP or billing software update is installed and that the Ship-To GSTIN field is validated, not free text. Run a handful of test transactions before going live on real dispatches.
Week three: Train dispatch and billing staff together in one session, not separately, so both sides understand how a single shipment flows from invoice to e-way bill to delivery.
Ongoing: Review any rejected or flagged e-way bills weekly for the first two months after go-live, since this is when data gaps in your master records tend to surface. After that, a monthly spot check is usually enough to catch new customer locations before they cause a problem in transit.
Frequently Asked Questions
Is Ship-To GSTIN mandatory for every e-way bill? No. It’s mandatory specifically for Bill-To/Ship-To transactions, meaning cases where the billing GSTIN and the delivery location’s registered GSTIN are different. If you bill and ship to the same registered address, this requirement doesn’t add a new field for you.
What do I enter if the delivery address isn’t GST-registered? Enter “URP” (unregistered person) in the Ship-To GSTIN field. Leaving it blank or entering an incorrect GSTIN can cause the e-way bill or IRN generation to fail.
Can I edit the Ship-To GSTIN after generating the e-way bill? For B2B and SEZ transactions, the Ship-To details captured at IRN generation are treated as final. This is why accuracy at the point of billing matters more than it did before August 2026.
When did this rule actually take effect? GSTN originally scheduled it for 15 June 2026, then deferred it to 1 August 2026 to give ERP vendors and businesses more time to prepare their systems.
Does this apply to intrastate movement of goods too, or only interstate? The requirement applies wherever a Bill-To/Ship-To structure exists and an e-way bill is required, regardless of whether the movement is intrastate or interstate, as long as the standard e-way bill threshold and rules apply to that shipment.
What is the voluntary e-way bill closure facility? It’s an optional feature introduced alongside the Ship-To GSTIN change that lets you mark an e-way bill as closed once goods are delivered, rather than letting it remain open until natural expiry. It’s not compulsory but strengthens your compliance records.
Get Your Systems Ready Before It Costs You a Shipment
Fixing this properly means auditing your customer master data, updating your ERP, and retraining two different teams, all before your next truck leaves the warehouse. If you’d rather have a compliance team handle the GSTIN mapping, ERP checks, and e-way bill process review for you, TRUSTLINK’s GST Compliance team works with businesses across distribution, manufacturing, and e-commerce to get this right the first time. Reach out for a consultation before your next shipment is on the road.