If your business raises an invoice to one company but ships the goods to a completely different address, you're running a Bill-To/Ship-To transaction, whether you've labelled it that way or not. And starting 1st August 2026, GSTN is no longer letting you leave that "Ship To" field blank on the e-Way Bill portal. This is the Ship To GSTIN mandatory rule 2026, and it's about to change how a lot of finance and logistics teams do their daily filings.
Here's the short version: fill it in correctly, or your e-Way Bill simply won't generate.
What Exactly Is Changing
GSTN issued an advisory on 21st May 2026 announcing two updates to the e-Way Bill system. Originally the compliance date was set for 15th June 2026, but GSTN pushed it out to 1st August 2026, giving businesses a bit more breathing room to update their systems.
The first change is the big one: the Ship-To GSTIN field becomes compulsory for every Bill-To/Ship-To e-Way Bill. No more skipping it. No more generating an EWB with that field empty and hoping nobody notices.
The second change is smaller and, for now, optional: a new EWB closure facility that lets suppliers, recipients, transporters, or drivers mark a delivery as complete once goods actually reach their destination.
Why Does the Ship To GSTIN Field Even Matter?
Picture a fairly ordinary supply chain scenario. Company A sells materials to Company B, but Company B tells Company A to deliver the goods straight to Company C, maybe a project site, maybe a warehouse Company B doesn't even own. The invoice goes out in Company B's name. The truck, though, goes to Company C.
That's a Bill-To/Ship-To transaction, and under Section 10(1)(b) of the IGST Act, 2017, it's treated in a specific way: Company B is deemed to have received the goods, and the place of supply is Company B's principal place of business, not wherever the truck actually unloaded.
The e-Way Bill portal has always had a field for this split, one side for the billing party, one side for the actual delivery point. But that delivery-side field was optional. And a lot of businesses simply left it blank, especially when goods were headed to a site or location that didn't have its own GSTIN.
That created a real gap for GSTN. Without a reliable Ship-To record, the department couldn't properly match e-Way Bill movements against what showed up later in GSTR-1 and GSTR-3B. Goods were moving, invoices were being raised, but there was no clean trail connecting the two. The Ship To GSTIN mandatory rule 2026 exists to close that gap.
What You Need to Enter (And When URP Applies)
The rule isn't asking for the impossible. If the delivery address is a GST-registered location, you enter that location's GSTIN. Simple enough.
But a huge number of Bill-To/Ship-To deliveries go to places that aren't registered at all: a construction site, a customer's home, an unregistered warehouse. For these, the portal accepts "URP", which stands for Unregistered Person. That single detail matters a lot, because it means businesses delivering to project sites or end consumers aren't stuck. They just need to remember to type URP instead of leaving the field empty.
Sounds minor, but for teams used to skipping that field entirely, it's a habit that needs to change before 1st August.
Who Actually Gets Hit by This
Not every business runs Bill-To/Ship-To transactions, but a lot more do than you'd expect. Three sectors stand out:
Construction and infrastructure companies, where materials routinely go to project sites that were never going to have their own GSTIN in the first place.
Manufacturing and wholesale businesses, where a head office places the order but the actual goods land at a factory or a regional warehouse.
E-commerce and logistics operations running drop-ship models, where the seller never sees the goods and they go straight from a supplier to the end customer or a fulfilment centre.
If any part of your ordering process looks like "bill one place, ship somewhere else," this rule applies to you.
What Happens If You Get It Wrong
Two separate risks are worth flagging here.
The first is purely operational: if the Ship-To GSTIN field isn't populated in your source data, whatever API call generates your e-Way Bill will fail. No EWB, no movement of goods, no exceptions. Your ERP or accounting software has to be configured to enforce this before 1st August, which means the update needs to come from your vendor and then actually get deployed and tested on your end.
The second risk is a compliance one, and it's the one that should worry finance teams more. Once the mandatory Ship-To GSTIN rule is live, any mismatch between the Ship-To GSTIN on your e-Way Bill and the recipient GSTIN on your tax invoice can trigger scrutiny under Section 129 of the CGST Act, 2017, potentially leading to detention of goods, or in more serious cases, confiscation proceedings under Section 130. This isn't a rule you want to get technically right but practically sloppy on.
The New EWB Closure Facility: Optional, But Worth Adopting Early
Alongside the mandatory Ship-To GSTIN change, GSTN has also rolled out a way to formally close an e-Way Bill once goods are delivered. Until now, an EWB just sat there until its validity expired, whether or not the delivery actually happened. Cancelled invoices, failed shipments, returned goods, all of it left "open" EWBs floating around with no confirmation either way.
Now, the supplier, the recipient, the transporter, or even the driver can close it. Suppliers, recipients, and transporters do this by logging into the portal. Drivers or authorised representatives can close it without logging in at all, using a mobile number and an OTP that was registered at the time the EWB was created.
There are two ways to close it: search for a specific EWB number, or close every EWB generated on a given date, which is far more practical if you're processing dozens of deliveries a day.
The window to do this is tight: closure has to happen either on the same day as delivery or the day right after, according to GSTN Advisory No. 661. Businesses running API integrations can already test this against NIC's Sandbox environment, which asks for the EWB number, the closure date, and a remark.
It's optional right now. But there's a decent chance this becomes mandatory down the line, the same way Ship-To GSTIN did. Getting your team into the habit of closing EWBs now means cleaner audit records later, and one less scramble if the rule tightens.
What to Do Before 1st August 2026
If you're relying on ERP or accounting software to generate e-Way Bills, reach out to your vendor now, not in July. Ask directly whether the Ship-To GSTIN field has been made mandatory in their EWB workflow, and get a firm date for when the update lands in your system.
If you're on a direct API integration, get into the NIC Sandbox and start testing against the updated specs for both the mandatory field and the closure API.
If your team still generates e-Way Bills manually through the portal, a short training session covering what qualifies as a Bill-To/Ship-To transaction and when to use URP will save a lot of confusion later. A one-page SOP is genuinely enough here.
And for logistics or accounts teams sitting on messy master data, this is a good moment to go through your Ship-To addresses and confirm which ones actually have a GSTIN attached and which need to be marked URP. It's tedious work if your supply chain is complex, but doing it now beats discovering the gaps after 1st August.
The Bottom Line
The
Ship To GSTIN mandatory rule 2026 isn't a complicated concept. It just asks businesses to fill in a field that many of them have been ignoring for years. The real work isn't understanding the rule, it's making sure your ERP, your API integration, and your team all catch up before the deadline. Given the compliance risk tied to mismatches under Section 129, this is one deadline worth treating seriously rather than leaving for the last week of July.
Frequently Asked Questions
When does the Ship-To GSTIN become mandatory?
From 1st August 2026, after GSTN extended the original 15th June 2026 deadline.
Does this apply to every e-Way Bill?
No, only to Bill-To/Ship-To transactions, where the invoice and the delivery address belong to different parties.
What do I enter if the delivery location isn't GST-registered?
Enter "URP" in the Ship-To GSTIN field. The portal accepts this as a valid entry.
Is EWB closure mandatory too?
Not yet. It's currently voluntary, though early adoption is a smart move given the direction GSTN seems to be heading.
What happens if my ERP isn't updated in time?
E-Way Bill generation will fail for any Bill-To/Ship-To transaction where the Ship-To GSTIN field is left blank.