Key takeaways
- Ship-To becomes a structured mandatory GSTIN-or-URP value in the announced flows.
- The validation covers standalone EWB, IRN plus EWB, EWB by IRN and combination workflows.
- Use URP only where the ship-to party is genuinely unregistered.
- Closure is voluntary and records completion; it is not cancellation or rejection.
- Test APIs and masters before 1 August and verify the live rollout afterward.
What exactly is changing in Ship-To?
GSTN’s June advisory and July FAQ require the Ship-To field to carry either a valid GSTIN or the prescribed URP value. Free-text or invalid identifiers that previously passed downstream can fail. This affects cases where billing and delivery parties/locations differ and requires reliable customer/location masters.
Which workflows need testing?
| Workflow | Test |
|---|---|
| Standalone EWB | Ship-To validation and error handling |
| IRN plus EWB | IRP payload mapping to EWB fields |
| EWB by IRN | Correct retrieval and Ship-To value |
| Combination/bulk flows | Row-level validation and partial failure handling |
Test registered Bill-To/unregistered Ship-To, unregistered Bill-To/registered Ship-To, branch delivery, job work, transporter generation and export scenarios.
What is voluntary e-way bill closure?
Closure is intended to let the generator mark movement as completed after delivery. It improves status quality but is not cancellation, rejection by the recipient, Part-B vehicle update or extension of validity. Define who may close, what delivery proof is needed and how premature closure is corrected/escalated.
What should ERP teams change?
Make Ship-To party status explicit, validate GSTIN format and active master status, send URP only for unregistered recipients, preserve Bill-To and dispatch-from distinctions, update API schema/error handling, and log the payload/response. Avoid auto-copying Bill-To GSTIN into Ship-To when delivery facts differ.
What should tax teams verify?
Tax should approve scenario mapping, reconcile invoice/e-invoice/e-way bill addresses, review place of supply, and sample production transactions after go-live. A successful API response does not prove the tax treatment is correct.
What are common implementation risks?
Risks include hard-coded URP, stale customer GSTINs, confusion between Ship-To and dispatch-from, premature closure, assuming closure shortens statutory record retention, and failing to monitor a revised GSTN date. Keep a rollback-ready deployment and check release notes on 1 August.
What is the go-live checklist?
Complete sandbox regression, deploy master cleanup, train users, communicate transporter changes, monitor rejection codes, validate the first transactions in each flow, and archive the official release note showing actual production status.
Primary sources
Frequently asked questions
What changes on 1 August 2026?
GSTN’s FAQ schedules mandatory Ship-To GSTIN/URP validation and the voluntary closure facility from 1 August 2026. Confirm the production release at go-live.
What should be entered for an unregistered ship-to party?
Use URP in the prescribed field where the party is genuinely unregistered. Do not use URP to bypass validation for a registered ship-to location.
Which API flows are affected?
The advisory covers standalone e-way bill generation, IRN with e-way bill, e-way bill by IRN and combination/bulk-related flows described in the API material.
Is e-way bill closure mandatory?
The announced closure feature is voluntary. It allows the generator to mark completed movement; it does not replace cancellation rules.
Can closure fix a wrong vehicle or invoice?
No. Use the legally permitted update or cancellation route. Closure records completion and should not be used to conceal incorrect source data.
Should ERP changes wait until the portal goes live?
No. Update masters, validations and API payloads in sandbox first, while retaining a go-live verification step because portal implementation can be revised.
Explore the GST authority library
Research the underlying documents inside your AI assistant
Connect TaxByKK to Claude or ChatGPT to trace provisions, read source pages and build a cited working draft.
View TaxByKK plans