GST E-Way Bill Portal Changes from 15 June 2026: Ship To GSTIN, URP and Closure Workflow

GSTN issued a 20 May 2026 advisory for e-way bill portal enhancements that move into production by 15 June 2026 (GSTN, 2026). The change is operational, not cosmetic: bill-to/ship-to dispatches need better recipient data, and delivery teams get a new voluntary closure workflow.

For small manufacturers, traders, distributors, and D2C brands, this is the dispatch-process update to fix before the next busy shipping cycle. If your invoice, ERP, or warehouse team still treats e-way bill generation as a last-minute transport task, June is the month to clean it up.

What changes on the e-way bill portal from 15 June 2026?

GSTN's advisory says the proposed e-way bill changes will be deployed in production by 15 June 2026, with APIs already released in the NIC sandbox (GSTN, 2026). The two important workflow changes are mandatory Ship To GSTIN capture in bill-to/ship-to cases and a voluntary closure facility after delivery.

The business impact is simple. Your billing team, dispatch team, transporter, and ERP vendor must agree on who captures final consignee details and who closes the e-way bill after delivery. If that ownership is unclear, mistakes will show up in transit checks and GST audit trails.

What is mandatory Ship To GSTIN capture?

GSTN says the Ship To GSTIN field must be captured in bill-to/ship-to e-way bill transactions, and "URP" must be entered where the consignee is unregistered (GSTN, 2026). This matters when the buyer and delivery location are not the same tax identity.

A common example is a distributor billing a head office but shipping to a branch, warehouse, project site, or third-party customer location. Your sales invoice and transport document must tell the same story. If they don't, the truck may carry valid papers but still create a mismatch.

How does voluntary e-way bill closure work?

GSTN says an e-way bill can be voluntarily closed after delivery by the supplier, recipient, transporter, driver, or authorised person whose mobile number is provided for closure (GSTN, 2026). Closure can be e-way-bill-wise or date-wise, and can happen on delivery day or the next day.

This is useful for businesses with frequent short-haul deliveries. Instead of leaving active e-way bills open until validity expires, the delivery person or logistics desk can mark completed movement. That creates a cleaner trail for delivery completion, returns, and transporter reconciliation.

Who should update systems before rollout?

GSTN specifically asks ERP vendors, GSPs, ASPs, and system integrators to access updated API specifications, test in sandbox, and make configuration changes before production (GSTN, 2026). Small businesses using Tally, Zoho, custom ERPs, or logistics software should not assume the vendor has already handled it.

Ask your software partner for two confirmations: whether Ship To GSTIN or URP is supported in the e-way bill flow, and whether closure API support is available. If you create e-way bills manually, update your dispatch SOP and add one person responsible for closure checks.

What should Indian SMBs do this week?

Build a 5-step rollout plan. First, list all bill-to/ship-to order types. Second, update your customer and warehouse master data. Third, add driver or authorised-person mobile capture where closure will be used. Fourth, test one sandbox or dummy process. Fifth, brief the dispatch team before 15 June 2026.

If this exposes broader filing or reconciliation gaps, pair it with your monthly GST workflow. Our e-way bill rules guide explains the base threshold and validity rules, and our monthly GST return filing service can help clean the connected GSTR-1 and GSTR-3B records.