E-Way Bill New Rules 2026: Mandatory Ship-To GSTIN and Closure Facility Explained

Introduction

If your business ever bills one party and ships the goods to a different location, a change is coming to how you generate e-way bills. Starting 1 August 2026, the GST Network is rolling out two e-way bill new rules 2026 at once: the Ship-To GSTIN becomes mandatory for every Bill-To/Ship-To transaction, and a new voluntary closure facility lets you officially mark delivery as complete instead of letting the e-way bill simply expire on its own.

This was originally supposed to kick in on 15 June 2026, but GSTN pushed the date back after businesses, ERP vendors, and GST Suvidha Providers asked for more time to update their systems. That extra runway is useful, but only if you actually use it to prepare rather than wait until the last week of July.

At GST Registration, we help businesses stay ahead of exactly this kind of portal-level change, the ones that do not make front-page news but can quietly stop a shipment at the gate if missed. This guide explains what Bill-To/Ship-To actually means in plain terms, how the new closure facility works, who this rule affects, and what you need to check before August arrives.

What Is the Ship-to GSTIN Change, Exactly?

Until now, generating an e-way bill for a delivery to a different location than the billed party only required an address in the Ship-to field. From 1 August 2026, that address alone will not be enough. The portal will also require the actual GSTIN of the party receiving the goods, wherever such a party exists and is registered.

Alongside this, GSTN is also introducing a voluntary e-way bill closure facility, letting the supplier, recipient, transporter, or driver mark an e-way bill as closed once delivery is actually complete, rather than letting it sit active in the system until its validity simply expires on its own.

What Is a Bill-To/Ship-To Transaction, in Plain Terms?

This is the part most coverage of this change skips, and it is exactly where confusion tends to start.

A Bill-To/Ship-To transaction is simply any case where the entity you are invoicing is not the same entity physically receiving the goods. The most common everyday example is a company with a head office that places the order and pays the invoice, while the goods are actually delivered to one of its branch offices, a warehouse, or a construction site.

If your billing address and your delivery address are always the same single party, this change does not affect you at all. The mandate only applies the moment those two parties are different.

A Simple Example to Make This Concrete

Say a Jaipur-based electronics distributor sells a batch of inverters to a retail chain headquartered in Mumbai. The invoice is raised on the Mumbai head office, since that is who places the order and pays the bill. But the actual inverters are shipped directly to the chain's warehouse in Pune, skipping Mumbai entirely.

Today, the e-way bill for that shipment only needs the Pune warehouse address in the Ship-to field. From 1 August 2026, the distributor will also need the Pune warehouse's own GSTIN, assuming it is separately registered, entered in that same field. If the Mumbai head office and the Pune warehouse share a single GST registration, this becomes less of an issue since they are effectively the same registered entity. The complexity shows up specifically when the billing party and the receiving location hold separate GST registrations, which is common across retail chains, manufacturing groups, and multi-state distributors.

Common ERP and Software Questions Businesses Are Asking

A large share of the early confusion around this change is coming from businesses that generate e-way bills through accounting software or ERP systems rather than logging into the government portal directly. A few practical points are worth knowing before August.

Will My Existing Software Update Automatically?

Not necessarily, and not without you checking. Software vendors need to update their own systems to match the new API specification that GSTN has released for the Ship-to GSTIN field. Established platforms with dedicated GST compliance teams, such as Tally, are already rolling out updates ahead of the deadline, but smaller or custom-built billing tools may lag behind unless someone specifically asks the vendor about it.

What If My Software Has Not Been Updated by August?

If your billing software cannot capture the Ship-to GSTIN field, any Bill-To/Ship-To e-way bill generated through that software is likely to fail validation on the GSTN side once the mandate takes effect, since the field will be missing entirely rather than simply left blank. The safer approach is to confirm with your vendor now, with enough time to either wait for an update or temporarily switch to generating the affected e-way bills directly through the government portal.

Does This Affect E-Way Bills Generated Through the IRN for E-Invoices?

Yes, and with one extra detail worth knowing. For businesses above the e-invoicing turnover threshold, Ship-to details entered at the time of generating the e-invoice will carry forward into the e-way bill automatically, and in B2B and SEZ transactions, those details cannot be changed later at the e-way bill stage. This makes it more important to get the Ship-to GSTIN right at the invoice stage itself, rather than treating it as something to fix later when the e-way bill is generated.

Is There an Exception for Export Shipments?

Yes, and exporters should take note of this specifically. For B2B and SEZ transactions, GSTN has locked the Ship-to details once they are entered at the e-invoice stage, so they cannot be edited later while generating the e-way bill. Export transactions get an exception to that lock.

Where goods are being exported, businesses are allowed to modify the Ship-to details at the e-way bill generation stage even after the e-invoice has already captured different information. GSTN has recognised that export logistics often involve last-minute changes, a different forwarding agent, a port handover, or a consolidation point, that simply do not fit the same rigid Bill-To/Ship-To structure used for domestic deliveries. For export shipments where no domestic registered consignee exists at all, URP remains valid here as well.

The Implementation Timeline So Far

It is worth tracking this timeline carefully because the date has already moved once. While 1 August 2026 is the current confirmed date, the practical lesson from the first postponement is that the safest approach is to be ready well before the deadline rather than assuming a further delay will happen again.

What Happens If the Recipient Is Not Registered Under GST?

This is one of the most common questions businesses are likely to run into once this rule goes live. Not every delivery location belongs to a GST-registered entity.

GSTN has addressed this directly. Where the actual recipient does not hold a GST registration, the Ship-to GSTIN field should simply be filled with the value URP, meaning unregistered person. The portal will accept this entry, so the rule does not block deliveries to genuinely unregistered consignees, it only requires you to declare that status clearly instead of leaving the field blank or guessing.

What Validation Checks Will the Portal Run on This Field?

Knowing the validation rules in advance can save you from a rejected e-way bill at the worst possible moment, right when a shipment is ready to leave.

• The system will verify that the Ship-to GSTIN entered is a real, active registration, not just a correctly formatted number

• It will check that the State Code embedded in the GSTIN matches the PIN code of the delivery address, so a Rajasthan GSTIN paired with a Maharashtra delivery address will likely be flagged

• It will not allow the same GSTIN to appear in both the Bill-to and Ship-to fields of a single transaction, since that would defeat the purpose of declaring two separate parties in the first place

The practical takeaway is to treat this as a data-hygiene exercise, not just a software update. Even a fully updated ERP system will still reject the entry if the underlying GSTIN on file for a branch or warehouse is outdated, inactive, or simply mistyped somewhere in your master data.

What Is the New Voluntary E-Way Bill Closure Facility?

This is the second half of the e-way bill new rules 2026, and most businesses focus only on the Ship-To GSTIN change while missing this one entirely.

Today, once goods reach their destination, an e-way bill does not get marked as delivered in any active way. It simply stays valid in the system until its validity period runs out and it expires on its own. There is no record confirming the goods actually arrived, only a record that the document was issued. From 1 August 2026, GSTN is introducing an option to close an e-way bill once delivery is genuinely complete.

Who Can Close an E-Way Bill?

Closure is not limited to the person who generated it. The supplier, the recipient, the transporter, or the driver can close it, as long as their mobile number is the one linked to that e-way bill. This flexibility matters in practice, since it is often the recipient or the driver, not the original supplier, who knows the exact moment goods were physically handed over.

How and When Do You Close It?

The closure option appears on the e-way bill portal once you select the relevant e-way bill number, and a closure request can also be raised through the mobile-number based search, or through an API for businesses using system integration. The window is tight by design, closure is only allowed on the date of delivery itself or on the day immediately after, and the option lapses once that window passes.

Is Closure Mandatory, or Can I Skip It?

It is voluntary for now, so there is no immediate penalty for not closing an e-way bill. That said, treating it as optional in the long run is a risk worth thinking about carefully. An e-way bill left open with no closure record can invite an adverse assumption during a department audit, almost as if the movement was never fully accounted for, even when the delivery itself was completely genuine. Building closure into your standard delivery process now, while it is still voluntary, is a simple way to stay ahead of what is likely to matter more during future verification.

Who Needs to Prepare Before 1 August 2026?

Not every business needs to scramble, but several categories should treat this as a genuine action item rather than a footnote.

• Businesses with branch offices, warehouses, or project sites that receive goods on behalf of the head office or main billing entity

• Manufacturers and distributors who regularly ship to dealers or franchisees under a different billing arrangement

• Businesses using ERP software or accounting systems that generate e-way bills automatically through API integration, since the underlying system needs to support the new mandatory field

• Anyone using e-invoicing above the applicable turnover threshold, since Ship-to details entered at the e-invoice stage will now carry through to the e-way bill without being overridden later, in B2B and SEZ transactions

If none of these describe how your business operates, this change will likely pass without disrupting anything. If even one does, it is worth a conversation with whoever manages your billing software well before the August deadline.

What Should You Do Right Now to Prepare?

1. Identify every regular Bill-To/Ship-To arrangement your business currently has, including branch deliveries, project sites, and third-party consignees.

2. Confirm the GSTIN of each regular recipient location in advance, so it is on file rather than something your team has to chase down mid-shipment after August.

3. For unregistered consignees, make sure your billing staff knows to use URP rather than leaving the field incomplete.

4. If you use ERP or accounting software for e-way bill generation, confirm with your vendor that the system has been updated to support the new mandatory field before the deadline.

5. Run a few test e-way bills using the new field if your software allows it, rather than discovering an issue for the first time when a shipment is waiting to move.

6. Build the closure facility into your delivery process from day one, even though it is voluntary, so your team has a habit of confirming delivery rather than treating it as a future problem.

How Does This Connect to General E-Way Bill Compliance?

This Ship-to GSTIN requirement sits on top of the existing e-way bill framework, it does not replace it. The standard rules around the ₹50,000 value threshold, required documents, validity periods, and penalties under Section 129 remain exactly as they were. If you need a refresher on those fundamentals, our complete e-way bill rules and penalties guide covers the full process, including the 180-day invoice rule and what happens at a check post.

Where this new rule adds the most risk is precisely at the intersection of the two. A mismatch between the Ship-to GSTIN on the e-way bill and the actual invoice details is the kind of small data error that, as the existing penalty rules already make clear, tends to draw scrutiny under Section 129 even when the underlying transaction was completely genuine.

Trust and Authority: Why This Deserves Attention Now, Not in July

In our experience helping businesses stay compliant with GST portal changes, the pattern repeats almost every time. A change gets announced months in advance, gets postponed once, and then a large share of affected businesses still end up scrambling in the final week because the postponement created a false sense that there is no real urgency.

The Ship-to GSTIN mandate is a structural change to how the portal validates data, not a minor tweak. Businesses that rely on ERP or API-based e-way bill generation are particularly exposed if their software provider has not pushed the necessary update, since the failure shows up only when a shipment is already being prepared to move.

Conclusion: Key Takeaways

1. From 1 August 2026, two e-way bill new rules 2026 go live together: the Ship-to GSTIN becomes mandatory for every Bill-To/Ship-To e-way bill, with URP used for unregistered consignees, and a voluntary closure facility lets you confirm delivery instead of letting the document simply expire.

2. This deadline was already postponed once from 15 June 2026, so businesses should prepare well ahead of August rather than assuming a further delay.

3. The rules affect anyone with branch deliveries, project-site shipments, or dealer networks where the billed party and the receiving party are different, and they work alongside, not instead of, the existing e-way bill threshold and penalty rules.

 

Getting your Ship-to GSTIN data ready and building the closure habit now, rather than in the final week of July, is the difference between a routine system update and a shipment stuck at the check post.

Frequently Asked Questions

When does the Ship-to GSTIN become mandatory for e-way bills?

From 1 August 2026. This was originally set for 15 June 2026 but was postponed by GSTN to give businesses, ERP vendors, and GST Suvidha Providers more time to update their systems.

Does this rule apply to every e-way bill, or only certain transactions?

It applies only to Bill-To/Ship-To transactions, where the entity being billed is different from the entity actually receiving the goods. If your billing party and delivery location are always the same, this change does not affect you.

What should I enter if the recipient does not have a GST registration?

Enter URP, which stands for unregistered person, in the Ship-to GSTIN field. The portal is designed to accept this entry, so deliveries to genuinely unregistered consignees are not blocked.

Is the e-way bill closure facility mandatory?

No, closure is voluntary for now. There is no immediate penalty for skipping it, but it creates a clear delivery-confirmed record that can help during a future audit or dispute, so building it into your process early is a sensible precaution.

Will my accounting software handle this automatically?

Only if your ERP, accounting software, or API integration has already been updated to support the new mandatory field. It is worth confirming this directly with your software vendor rather than assuming it will work without checking.

What happens if there is a mismatch between the Ship-to GSTIN and the invoice details?

A mismatch between the e-way bill's Ship-to GSTIN and the recipient details on the invoice can draw scrutiny under Section 129 of the CGST Act, the same provision that governs general e-way bill penalties, even where the underlying transaction is genuine.

 

Need Help Reviewing Your E-Way Bill Process Before August?

If your business regularly ships to branches, project sites, or dealer networks, our GST compliance team can help you review your billing setup before the Ship-to GSTIN mandate takes effect.

 

About the Author

Rohit is a Digital Marketing Executive and GST content specialist with hands-on experience tracking GSTN advisories, CBIC notifications, and portal-level compliance changes for business audiences across India. He holds a B.Com degree and a digital marketing certification from Raj Skill Digital Institute, and has authored detailed compliance guides on GST registration, input tax credit, and e-way bill compliance for GST Registration.