Many businesses sell goods to one customer but deliver them to another person or place on that customer's instructions. During 2026, GSTN announced that the GSTIN of the Ship-to party would become mandatory in such e-way bills, along with a new facility to close an e-way bill after delivery. Both changes were later kept on hold. This article explains what was proposed, where things stand, and what the e-way bill rules still require today.
Key takeaways
- GSTN had announced mandatory capture of the Ship-to GSTIN in Bill-to/Ship-to e-way bills and a voluntary e-way bill closure facility, finally scheduled for 1 August 2026.
- By its advisory dated 29 July 2026, GSTN kept both enhancements on hold until further notice. As on the review date, we did not find any later advisory announcing a new date.
- The existing e-way bill framework under section 68 and rule 138 continues unchanged. Bill-to and Ship-to details must still be filled correctly.
- For one physical movement in a Bill-to/Ship-to arrangement, only one e-way bill is required.
- Cancellation of an e-way bill within 24 hours under rule 138(9) continues. It is different from the proposed closure facility, which is not live.
- ERP teams should not enforce the held validations in production. Development work can be kept ready in case the changes are re-notified.
1. What is a Bill-to/Ship-to transaction?
A Bill-to/Ship-to transaction usually involves three parties:
- Supplier: the person who issues the invoice and dispatches the goods.
- Bill-to party: the buyer who places the order and is billed.
- Ship-to party: the person or place that physically receives the goods, on the buyer's instructions.
There is one physical movement of goods, but usually two supplies: supplier to buyer, and buyer to the final consignee. The e-way bill system already provides for this through the transaction types Regular, Bill To - Ship To, Bill From - Dispatch From and Combination of the two.
2. How the 2026 proposal developed
| Date | What happened |
|---|---|
| 20 May 2026 | GSTN advisory announced two enhancements: mandatory Ship-to GSTIN in Bill-to/Ship-to transactions, and voluntary closure of e-way bills, from 15 June 2026. |
| 9 June 2026 | Implementation date extended to 1 August 2026. |
| 17 June 2026 | Advisory on corresponding changes to the e-Invoice API, e-Way Bill by IRN API and a new EWB Closure API. "URP" to be used where the Ship-to party is unregistered. Changes made available in the sandbox for testing. |
| Early July 2026 | FAQs issued on Ship-to GSTIN in different transaction scenarios. |
| 29 July 2026 | GSTN advisory (GST portal News and Updates) kept the enhancements on hold until further notice. Production changes under the earlier advisories are not required until further communication. |
Much material published between May and July 2026 says that Ship-to GSTIN "is mandatory from 1 August 2026". That statement is no longer correct and should not be relied on.
3. What is the current position?
As on the review date of this article:
- The Ship-to GSTIN field is not a mandatory field under the held proposal. The new validations between Bill-to and Ship-to GSTINs are not in production.
- The voluntary e-way bill closure facility is not available.
- No revised implementation date has been announced in the official updates we checked.
The proposal was a change in system validations and APIs, not an amendment of section 68 or rule 138. A field announced in an API advisory is not a legal requirement merely because the advisory existed. If GSTN re-notifies the changes, the new advisory and its effective date will govern.
4. What the existing rules still require
- When an e-way bill is needed: under rule 138, generally for movement of goods of consignment value exceeding Rs. 50,000, subject to the exemptions in the rule and to special cases where it is required irrespective of value (for example, inter-State movement for job work).
- Who generates it: in a Bill-to/Ship-to arrangement, the CBIC clarification of April 2018 says either the supplier or the buyer who ordered the goods may generate the e-way bill, but only one e-way bill is required for the movement.
- What goes in it: where the supplier generates it, the "Bill To" field carries the buyer's details, the "Ship To" field carries the consignee's address, and the invoice details are those of the supplier's invoice on the buyer. Where the buyer generates it, the fields are filled with reference to the buyer's own invoice, as explained in the same clarification.
- Documents with the goods: the invoice, bill of supply or delivery challan, as the case may be, and the e-way bill number.
The hold does not cure any other defect. Wrong parties, wrong addresses, a missing e-way bill or an expired e-way bill remain issues under the existing rules.
5. A simple illustration
A registered manufacturer in West Bengal receives an order from a registered buyer in Maharashtra. The buyer asks the manufacturer to deliver the goods directly to its customer in Odisha.
| Item | Position (manufacturer generates the e-way bill) |
|---|---|
| Transaction type | Bill To - Ship To |
| Bill From / Dispatch From | Manufacturer, West Bengal |
| Bill To | Buyer, Maharashtra |
| Ship To | Consignee's address, Odisha |
| Invoice details | Manufacturer's invoice on the Maharashtra buyer |
| Number of e-way bills | One, for the single movement from West Bengal to Odisha |
| Ship-to GSTIN | Not mandatory at present under the held proposal |
On the tax side, section 10(1)(b) of the IGST Act deems the buyer who directed the delivery to have received the goods. The place of supply of the manufacturer's invoice is therefore the buyer's principal place of business (Maharashtra), and the supply from West Bengal is inter-State. The buyer's onward supply to the Odisha customer is a separate supply with its own invoice and place of supply.
This is a hypothetical illustration. The actual tax treatment depends on the facts, for example where the consignee is a branch of the buyer, is unregistered, or is outside India.
6. Cancellation is not the same as the proposed closure
| Concept | Current position |
|---|---|
| Generating a valid e-way bill | Required under rule 138, as before. |
| Cancellation under rule 138(9) | Where goods are not transported, or not transported as per the e-way bill, it may be cancelled within 24 hours of generation. It cannot be cancelled if it has been verified in transit under rule 138B. |
| Validity and extension | Governed by rule 138(10), as before. |
| Voluntary closure after delivery | Proposed facility. On hold and not available. |
Teams should not treat the proposed closure as a substitute for cancellation, or as a way to deal with duplicate or unused e-way bills.
7. What ERP and billing teams should check
| Area | What to check |
|---|---|
| Production validations | Is any invoice or e-way bill being blocked only because the Ship-to GSTIN is blank? |
| Transaction type | Is "Bill To - Ship To" selected only where the delivery is to a different party or place, and not by default for every "deliver to" address? |
| Ship-to address and PIN | Do they match the actual delivery location? |
| Duplicate e-way bills | Are both the supplier and the buyer generating e-way bills for the same movement? |
| Development work | Is the Ship-to GSTIN and closure development parked in test, ready if the changes are re-notified? |
| Update monitoring | Is one person responsible for checking GST portal and e-way bill portal updates? |
8. Action points for businesses
- Check that production is not enforcing the held rule.Now
Ask your ERP or GSP vendor whether any Ship-to GSTIN validation or closure call was switched on for 1 August 2026. If yes, assess it against the current position before keeping it. - Keep Ship-to details accurate.Every movement
Fill the consignee's name, address and PIN correctly. Where the consignee's GSTIN is known, it may still be captured in the master for internal records. - Generate only one e-way bill per movement.Every movement
Agree with your buyer or supplier who will generate it, so that two e-way bills are not created for one consignment. - Check the tax type on Bill-to/Ship-to invoices.This month
Review a sample of invoices where the buyer and the delivery State differ, and confirm IGST or CGST/SGST as per section 10(1)(b). - Keep the buyer's delivery instruction on file.Ongoing
A purchase order or written instruction naming the delivery party supports the arrangement if questioned. - Train dispatch teams on cancellation.This month
Wrong or unused e-way bills should be cancelled within 24 hours. There is no closure option to fall back on. - Assign responsibility for updates.Ongoing
If GSTN re-notifies the changes, there will be a new effective date and testing window.
9. Action points for GST professionals
- Correct client understanding.
Many clients and vendors still believe Ship-to GSTIN became mandatory from 1 August 2026. Share the 29 July 2026 hold advisory. - Test samples of Bill-to/Ship-to e-way bills.
Check transaction type, parties, invoice linked, and that only one e-way bill exists for each movement. - Review place of supply.
Wrong tax type in Bill-to/Ship-to invoices is a common error. Check section 10(1)(b) cases, including branch transfers and unregistered consignees. - Examine interception or detention cases carefully.
Where an objection rests only on a blank Ship-to GSTIN, check whether it relies on a requirement that was never implemented. Other defects must be examined on their own facts. - Advise on documenting the vendor position.
Keep a note of which validations are active in the client's system and why, with the advisory relied on. - Track re-notification.
If the changes return, clients will need master data clean-up, URP handling and testing before the new date.
10. Five-minute self-check
Ask your dispatch, accounts or ERP team to answer YES, NO or NOT SURE:
| # | Question | Response |
|---|---|---|
| 1 | Do we handle Bill-to/Ship-to transactions? | |
| 2 | Do we know who generates the e-way bill in each such arrangement? | |
| 3 | Is only one e-way bill generated for each physical movement? | |
| 4 | Is the correct transaction type selected? | |
| 5 | Do Bill-to and Ship-to details match the invoice and the actual delivery? | |
| 6 | Is the tax type on these invoices checked against section 10(1)(b)? | |
| 7 | Has our ERP enforced any Ship-to GSTIN validation from 1 August 2026? | |
| 8 | Does the team know that the closure facility is not available? | |
| 9 | Are wrong or unused e-way bills cancelled within 24 hours? | |
| 10 | Is one person responsible for tracking GSTN updates? |
A NO or NOT SURE is a signal to review, not an established GST default.
11. Documents to keep ready
- Purchase orders or delivery instructions naming the buyer and the delivery party.
- Tax invoices of the supplier on the buyer, and of the buyer on the consignee.
- Delivery challans, where applicable.
- E-way bills with Part A and Part B details, and cancellation records.
- Transport documents: lorry receipt, vehicle details and transporter ID.
- Proof of delivery or acknowledgement from the consignee.
- ERP validation settings currently active in production.
- Copies of the relevant GSTN advisories, including the 29 July 2026 hold advisory.
12. What if you find a problem?
| Situation | Suggested next step |
|---|---|
| ERP rejects documents only for blank Ship-to GSTIN | Ask the vendor to align production with the current position after testing. |
| Two e-way bills for one movement | Cancel the extra one if still within 24 hours and not verified; otherwise document the facts and fix the process. |
| Bill-to and delivery details differ across documents | Reconcile the purchase order, invoice, e-way bill and proof of delivery. |
| Wrong tax type charged | Take advice on correction through credit note and fresh invoice or amendment, as the facts allow. |
| Old "mandatory from 1 August" note is circulating | Replace it with the 29 July 2026 hold position. |
| Team expects to close e-way bills after delivery | Explain that the facility is not available and cancellation rules apply. |
13. Official sources
- CGST Act, 2017: section 68.
- CGST Rules, 2017: rule 138, including sub-rules (9) and (10), and rule 138B.
- IGST Act, 2017: section 10(1)(b).
- CBIC clarification dated 23 April 2018: e-way bill in Bill-to/Ship-to transactions.
- GSTN advisories dated 20 May 2026, 9 June 2026 and 17 June 2026: proposed Ship-to GSTIN and closure enhancements (historical context only).
- GSTN advisory dated 29 July 2026: proposed e-way bill enhancements kept on hold until further notice.
The Acts and Rules are available on taxinformation.cbic.gov.in and cbic-gst.gov.in. GSTN advisories are under News and Updates on www.gst.gov.in, and e-way bill updates on ewaybillgst.gov.in.
Scope of this article: the article explains the position as on the review date. Individual transactions, contracts and ERP configurations have not been examined. If GSTN issues a fresh advisory, that advisory will prevail.
One small step for today: pick one recent Bill-to/Ship-to dispatch and check its invoice, delivery instruction, e-way bill and tax type together. Then confirm with your ERP vendor that no held validation is active.
Need help with Bill-to/Ship-to compliance?
GST DOST offers a focused Bill-to/Ship-to and e-Way Bill Health Check. The review covers:
- Sample testing of invoices, e-way bills and delivery records
- Place of supply and tax type on Bill-to/Ship-to invoices
- Duplicate and cancelled e-way bills
- ERP validation settings against the current official position
The objective is correct documentation for each movement. It is not a guarantee against verification in transit.
Disclaimer: This article is for general information only and reflects the position as understood on the review date mentioned above. It is not legal advice and does not create a professional relationship. The treatment depends on the facts of each case. Please obtain professional advice before acting on this article.
GST DOST | GST Movement Documentation, Reconciliation and Professional Advisory
