https://www.taxtmi.com/news?id=73400 Mandatory capture of Ship-to GSTIN has been introduced across specified e-Invoice API, e-Way Bill by IRN API and EWB Closure API flows, with URP permitted where GSTIN is not available. The revised framework requires a valid and distinct Ship-to GSTIN in Bill-to/Ship-to transactions, together with state code and PIN code validations, while export and B2B/SEZ scenarios are subject to specific treatment for ship details. A voluntary closure facility for e-Way Bills has also been introduced, with portal and API-based closure available using the EWB number, closure date and remarks. en-us Wed, 17 Jun 2026 18:50:05 +0530 Fri, 03 Jul 2026 11:30:00 +0530 TaxTMI RSS Generator https://www.taxtmi.com/news?id=73400 Mandatory capture of Ship-to GSTIN has been introduced across specified e-Invoice API, e-Way Bill by IRN API and EWB Closure API flows, with URP permitted where GSTIN is not available. The revised framework requires a valid and distinct Ship-to GSTIN in Bill-to/Ship-to transactions, together with state code and PIN code validations, while export and B2B/SEZ scenarios are subject to specific treatment for ship details. A voluntary closure facility for e-Way Bills has also been introduced, with portal and API-based closure available using the EWB number, closure date and remarks. News - Wed, 17 Jun 2026 18:50:05 +0530 https://www.taxtmi.com/news?id=73400