e-Invoice Ship-to GSTIN Mandatory From 1 August 2026
From 1 August 2026, the Ship-to GSTIN field in e-invoices and e-Way Bills became conditionally mandatory under GSTN's June 2026 advisory. Businesses with split Bill-to and Ship-to addresses must update ERP integrations or face API rejections and goods movement blocks.
CA Harun Raaj
Chartered Accountant · Harun Raaj & Associates
Legal basis: GSTN Advisory dated 17 June 2026 on e-Invoice API and e-Way Bill by IRN API structural changes — Effective: 1 August 2026. Source: https://tutorial.gst.gov.in/downloads/news/advisory_einvoice_api_ewb_by_irn_approved.pdf. Last reviewed by CA Harun Raaj: January 2026.
On 17 June 2026, GSTN issued an advisory introducing two structural changes to the e-Invoice API and the e-Way Bill by IRN API. These changes went live in production on 1 August 2026. If your ERP, GSP, or accounting software generates e-invoices with split Bill-to and Ship-to addresses, and your integration has not been updated, your goods movement may already be blocked.
What Changed: Two New Structural Requirements
Mandatory Ship-to GSTIN in e-Invoice and e-Way Bill APIs
Previously, the Ship-to GSTIN) field was optional. From 1 August 2026, it is conditionally mandatory:
- If the Ship-to address differs from Bill-to AND an e-Way Bill is required AND the consignee is GST-registered →
ShipDtls.Gstinmust be populated with the consignee's GSTIN. - If the consignee is unregistered → enter
"URP"(Unregistered Person). - In the e-Way Bill by IRN API,
ExpShipDtls.Gstinis now mandatory when generating e-Way Bills from existing IRNs.
Voluntary e-Way Bill Closure Facility
A new optional feature allows suppliers, recipients, transporters, or drivers to formally close an e-Way Bill post-delivery via the GSTN portal or API, creating a clean delivery audit trail.
Who Is Affected
Any business that:
- Has aggregate turnover exceeding ₹5 crore in any preceding financial year from 2017–18 onwards (mandatorily generates e-invoices under Rule 48(4) CGST Rules, 2017)
- Uses ERP or accounting software integrated via API, GSP/ASP, or third-party IRP
- Has Bill-to and Ship-to addresses that differ — supplies to warehouses, job work premises, branch offices, or dealer godowns
Exempt categories — SEZ units (outward supplies), insurance companies, banks, NBFCs, GTAs, and passenger transport operators — are unaffected.
Practical Impact for Your Business
A Mumbai-based MSME manufacturer (aggregate turnover ₹8 crore) supplies goods to a Pune distributor's Chennai warehouse. Bill-to: distributor's Karnataka GSTIN. Ship-to: distributor's Tamil Nadu warehouse. Before 1 August 2026, the Ship-to GSTIN field was optional. After 1 August 2026, the API expects the Tamil Nadu GSTIN — a blank or incorrect value triggers error 2325 and the e-invoice is rejected. Rejected e-invoice means no valid IRN → goods cannot move legally → Section 129 CGST Act detention and penalty risk.
Key point: From 1 August 2026, unpopulated or incorrect Ship-to GSTIN in split-address e-invoices causes API rejection and blocks legitimate goods movement.
Steps to Take Immediately
- Verify ERP readiness: Ask your ERP vendor for the patch release note explicitly referencing the GSTN advisory dated 17 June 2026. Request written confirmation that the update is deployed in production.
- Audit master data: Identify all Bill-to and Ship-to split configurations in your customer and vendor records. Ensure the consignee's GSTIN for each Ship-to state is captured and current.
- Configure unregistered party handling: If the Ship-to party is unregistered (e.g., job worker's unregistered premises), configure your system to pass
"URP"in the Ship-to GSTIN field. - Test in GSTN Sandbox: If your integration is API-based, generate test e-invoices with split addresses and validate the updated payload. Monitor for error codes 2323, 2325, 3039, 2324, and 4074.
- Establish closure workflow: The voluntary e-Way Bill closure facility is optional but recommended for maintaining a clean delivery audit trail.
Risk of Non-Compliance
API rejection halts e-invoice generation. Without a valid IRN, goods cannot be moved under Section 129 CGST Act. Detention and late fee penalties apply. Recovery of consignments in transit becomes an administrative and legal burden.
I'm CA Harun Raaj, Visakhapatnam. If your business generates e-invoices with split delivery addresses and you need an integration audit or clarification on the GSTN advisory, reach out — I help businesses avoid these compliance traps.
---
See Also
Frequently Asked Questions
When did the Ship-to GSTIN requirement come into effect?+
The GSTN advisory was issued on 17 June 2026, and the e-Invoice API and e-Way Bill by IRN API changes went live in production on 1 August 2026. From that date, Ship-to GSTIN became conditionally mandatory for split Bill-to and Ship-to invoices.
Do I need to update my ERP if my Bill-to and Ship-to addresses are the same?+
No. The Ship-to GSTIN requirement applies only when Bill-to and Ship-to addresses differ. If they are identical, the existing e-invoice flow applies and no update is needed.
What should I enter in the Ship-to GSTIN field for an unregistered consignee?+
For unregistered consignees (e.g., job workers, unregistered warehouses), enter `"URP"` (Unregistered Person) in the Ship-to GSTIN field. This satisfies the API requirement while correctly identifying the consignee's GST status.
What happens if I submit an e-invoice with a blank or incorrect Ship-to GSTIN after 1 August 2026?+
The GSTN API rejects the e-invoice with error code 2325 (or related errors 2323, 3039, 2324, 4074). Without a valid IRN, the goods cannot be moved legally under Section 129 CGST Act, and detention or penalty risk arises.
How do I verify that my ERP vendor has updated their system for this change?+
Ask your ERP vendor for the specific patch release note that references the GSTN advisory dated 17 June 2026. Request written confirmation that the patch is deployed in your production environment. Alternatively, test by generating a sample e-invoice with a Ship-to GSTIN populated and confirm that error codes 2325 or 2323 do not appear.
Are SEZ units and banks required to comply with this change?+
SEZ units (outward supplies), insurance companies, banks, NBFCs, GTAs, and passenger transport operators are exempt categories and are unaffected by this requirement.
What is the voluntary e-Way Bill closure facility introduced in the advisory?+
From 1 August 2026, suppliers, recipients, transporters, or drivers can formally close an e-Way Bill post-delivery via the GSTN portal or API. This feature is optional but recommended for maintaining a clean delivery audit trail.
Do export invoices require Ship-to GSTIN to be populated?+
For export invoices with foreign consignees, use `"URP"` in the Ship-to GSTIN field. Ship-to details may be corrected at the e-Way Bill stage. Verify the specific treatment with your IRP or GSP vendor based on the export invoice type and destination.
Go deeper with our hub guides
Statute-cited, section-by-section guides covering the same ground this article does.
Need help with this?
Our team handles the paperwork. You focus on your business.