E-way Bill Changes from 15 June 2026: Mandatory Ship-To GSTIN + Voluntary Closure Facility

Reviewed by Jainam Shah, Founder ERPDrive, on 6 June 2026.

If you generate e-way bills for your manufacturing dispatches, two changes are coming on 15 June 2026. We have read the official GSTN Advisory (dated 20 May 2026), spoken to NIC's API documentation team, and broken down what each change means for an Indian manufacturer who runs daily dispatches.

This article is current as of 6 June 2026 - 9 days before the production rollout. If you ship goods regularly, especially in Bill-To/Ship-To scenarios (common in OEM tier-1 supply, multi-warehouse customers, and stock transfers), you have one week to update your customer master and ERP configuration.

What is changing on 15 June 2026 (in one minute)

Change 1: Mandatory 'Ship To GSTIN' in Bill-To/Ship-To transactions

The GSTN Advisory states verbatim: "In cases involving Bill-To/Ship-To scenarios, the field relating to the 'Ship To GSTIN' shall now be captured as a mandatory data element during e-Way Bill generation. Where the consignee is an unregistered person, the value 'URP' shall be entered in the 'Ship To GSTIN' field."

What is a Bill-To/Ship-To transaction?

A Bill-To/Ship-To transaction is one where the buyer (Bill-To) is different from the actual delivery location (Ship-To). These are extremely common in Indian manufacturing:

• Multi-warehouse customers - your buyer is the head office in Mumbai but goods ship to their plant in Pune
• OEM tier-1 supply - your buyer is the OEM's corporate office but goods ship to a tier-1 supplier's location for sub-assembly
• Stock transfers - you transfer goods between your own GSTINs in different states (Bill-To and Ship-To are both your branches)
• Job-work send-out - the buyer instructs you to send raw material directly to their job-worker
• Drop-shipping / direct dispatch - manufacturer bills the trader but ships directly to the trader's end-customer

In all these scenarios, the 'Bill-To GSTIN' (your invoice recipient) and the 'Ship-To GSTIN' (the actual delivery location's registered identity) are different. The advisory now requires both to be captured at EWB generation - no exceptions.

What to do if your consignee is unregistered

If your delivery is to an unregistered person - retail end-customers, exempted entities, or individuals - enter the literal value URP (Unregistered Person) in the Ship To GSTIN field. The portal will accept this value and proceed with EWB generation.

Why this matters: practical impact

The Ship To GSTIN field was earlier captured at the consignee's address detail level - not enforced as a hard data validation. From the deployment date, the EWB portal will reject any Bill-To/Ship-To EWB without this field. Practical consequence:

• Your customer master must store the correct Ship To GSTIN for each customer branch - cleanup is needed for any customer with multiple delivery locations
• Your sales / dispatch user interface must surface the Ship To GSTIN at EWB generation - manual entry on every EWB is error-prone at volume
• For unregistered consignees, the system must auto-fill URP - otherwise users will manually type 'unregistered' or leave it blank, triggering rejection
• Dispatches will be blocked if the field is missing - downstream effect on revenue, customer relationships, and audit posture

Change 2: Voluntary e-Way Bill Closure facility

The advisory introduces a new EWB Closure facility - "on voluntary basis to enable closure of the e-Way Bill once delivery of goods is completed." This is a meaningful operational improvement: today, an EWB simply expires after its validity ends. There is no formal way to mark a transaction as 'completed' once goods reach their destination.

From 15 June 2026, four categories of users can close an EWB:

Closure modes

• EWB-wise: enter a specific EWB number and close it individually
• Date-wise: select a generation date, see all EWBs from that date, close in bulk (highly useful for high-volume dispatchers)

When can closure happen?

The advisory specifies a narrow window: closure can be done on the same day of delivery, OR the immediately succeeding day. Miss the window and the EWB cannot be formally closed - it will simply expire per the validity rules.

The driver-side closure flow (smart innovation)

One of the most useful aspects of the new facility is the driver-based closure. At EWB generation, the supplier (or anyone updating Part B / vehicle / extension) can register a mobile number specifically for closure purposes. Once goods are delivered, the driver:

1. Goes to the EWB portal (mobile or desktop)
2. Clicks Search → Closing Of E-Way Bills
3. Enters the registered mobile number
4. Receives OTP, enters it
5. Sees the list of all active EWBs linked to that mobile number
6. Selects one or more EWBs and clicks 'Close Selected'

This is a meaningful step toward field-level traceability without requiring drivers to have separate portal accounts.

API for ERP and system integrators

For automated closure via your ERP, the new API accepts:

• EWB number - the identifier of the e-way bill to close
• Closure date - same day of delivery or next day
• Remarks - optional narrative (e.g. "Goods received in full at consignee location")

NIC has released the updated API specification in the Sandbox environment. ERP vendors, GSPs, and ASPs have been advised to test in sandbox before the 15 June 2026 production rollout.

Action items by stakeholder

For Indian manufacturers (suppliers / consignors)

1. Customer master cleanup - audit every customer who has multiple delivery locations. Each branch must have a Ship-To GSTIN captured. Complete by 12 June 2026 to leave 3-day buffer.
2. Unregistered customer flagging - tag customers as 'URP' so the system auto-fills the value
3. User training - 30-min session for dispatch and EWB users on the new Ship To GSTIN field and the optional Closure feature
4. ERP vendor confirmation - get written confirmation from your ERP vendor (or in-house IT team) that EWB API integration is updated and sandbox-tested
5. Driver mobile capture - if you plan to use driver-based closure, set up a process to capture driver mobile at dispatch (or use a dedicated dispatch officer's mobile for all closures)

For recipients (consignees / buyers)

1. Confirm your Ship-To GSTINs with all suppliers - if you have multiple delivery locations, make sure your suppliers have the right GSTIN per branch
2. Plan internal closure workflow - if you want to take advantage of voluntary closure, designate someone (storekeeper, dispatch admin) to close incoming EWBs daily

For transporters

1. Train field staff on driver closure - drivers can close EWBs via mobile + OTP without needing a transporter login
2. Update internal SOPs - add EWB closure as a post-delivery step for high-value or long-distance shipments

For ERP vendors, GSPs, and ASPs

1. Download the updated EWB API specification from the NIC Sandbox
2. Test EWB generation with the new mandatory Ship To GSTIN field (including URP)
3. Test the new Closure API (EWB number + closure date + remarks)
4. Update UI screens for EWB generation and dispatch to capture / display the new fields
5. Plan production cutover before 15 June 2026

Penalty for non-compliance

The advisory does not specify a separate penalty for failing to capture Ship To GSTIN - because it is enforced at the EWB portal level. The portal will simply not generate an EWB without the field. The downstream risk is significant though:

• Goods moved without a valid EWB trigger detention under section 129 of the CGST Act
• Penalty is up to 200% of the tax payable on the goods (or up to ₹25,000 even where no tax is payable)
• Vehicle can be detained until penalty is paid
• Customer dispatches get blocked - real revenue impact

The closure feature being voluntary means there is no direct penalty for not using it. But ignoring it forfeits two genuine operational benefits: better internal reconciliation visibility (which EWBs are still 'open' past delivery) and a stronger audit trail (closure with remarks builds defensible documentation).

Which manufacturers are most affected?

Based on our work with Indian manufacturers across sectors, Bill-To/Ship-To scenarios are most common in:

• Auto components and OEM tier-1 suppliers - selling to OEM corporate but delivering to assembly plants
• Fabrication units - selling to project headquarters but delivering to construction sites
• Wire and cable manufacturers - selling to distributors but drop-shipping to end-customers
• Engineering job work - receiving FOC material from one customer branch and returning processed goods to another
• Fastener manufacturers - selling to traders / OEMs and shipping directly to end-users

If your factory falls into any of these categories, the Ship To GSTIN cleanup is urgent.

Frequently Asked Questions

What is changing in the e-way bill portal from 15 June 2026?

Per the GSTN Advisory dated 20 May 2026, two changes are being deployed in production by 15 June 2026: (1) capturing the 'Ship To GSTIN' field becomes mandatory for all Bill-To/Ship-To e-way bill transactions - for unregistered consignees, you must enter 'URP'; (2) a new voluntary e-way Bill Closure facility is added, letting the supplier, recipient, transporter, driver, or authorized person formally close an EWB once delivery is complete.

Is the e-way bill closure mandatory from 15 June 2026?

No. The advisory explicitly states the closure facility is 'on voluntary basis'. However, the 'Ship To GSTIN' field becoming mandatory in Bill-To/Ship-To scenarios IS a hard data-entry requirement - EWB generation without this field will fail. The 15 June date is when the API and portal changes go live in production; the binding compliance date for the mandatory field changes is the notified date of implementation.

Who can close an e-way bill under the new facility?

Four categories can close an EWB: (a) the supplier (consignor), (b) the recipient (consignee), (c) the transporter, or (d) the driver or other authorized person whose mobile number was registered for closure purposes. Suppliers, recipients, and transporters close via login on the EWB portal. Drivers and authorized persons close via the Search menu using mobile + OTP authentication.

When can an e-way bill be closed?

Closure can be performed on the same day of delivery, or the immediately succeeding day. Closure can be done EWB-wise (one at a time) or Date-wise (bulk close all EWBs of a generated date). The closure payload requires the EWB number, closure date, and remarks.

What is 'Ship To GSTIN' and why does it become mandatory?

'Ship To GSTIN' identifies the actual delivery location's GSTIN in Bill-To/Ship-To scenarios - common when a customer buys from one location (Bill-To GSTIN) but goods ship to another branch or warehouse (Ship To GSTIN). Capturing this field reduces ambiguity in goods movement traceability. From the deployment date, the field is mandatory at EWB generation. If the consignee is unregistered, enter URP (Unregistered Person).

How can ERP vendors prepare for the 15 June 2026 deployment?

GSTN has released updated API specifications in the NIC Sandbox environment. ERP vendors, GSPs, and ASPs must: (1) download the updated API specs, (2) test the EWB generation flow with the new mandatory Ship To GSTIN field, (3) test the EWB Closure API which accepts EWB number + closure date + remarks, (4) update internal user interfaces to capture Ship To GSTIN at EWB creation and to display closure status, (5) carry out a full sandbox-to-production cutover before 15 June 2026.

Does ERPDrive support the new EWB compliance requirements?

Yes. ERPDrive's e-way bill module is being updated for the 15 June 2026 rollout. Ship To GSTIN is captured from the customer master automatically (with branch-level GSTIN support for multi-location customers); for unregistered consignees ERPDrive auto-fills 'URP'. The voluntary EWB Closure workflow is built into the dispatch module: one-click closure from the EWB dashboard, bulk closure by generated date, and a driver-side closure flow using the dispatch SMS/WhatsApp link. ERPDrive customers will see the new features in their account by 15 June 2026 with no manual upgrade required.

What is the penalty for failing to capture Ship To GSTIN?

The advisory does not specify a separate penalty - however, since the field becomes a mandatory data element during EWB generation, the EWB portal will simply not allow EWB creation without it. The downstream risk is that goods movement without a valid EWB triggers detention under section 129 of the CGST Act (penalty up to 200% of tax payable, or up to Rs 25,000 even where no tax is payable). The practical impact: dispatches will be blocked until Ship To GSTIN is correctly captured, so master-data cleanup must happen BEFORE 15 June.

Sources & References

This article cites the following primary sources. Click through for the official source documents:

• GSTN Advisory - Enhancements in EWB Portal (20 May 2026)
• NIC E-Way Bill Portal
• CBIC GST portal
• GST Portal (Government of India)
• NIC E-Way Bill API documentation