Mon–Sat · 10:30 am–07:30 pm Firm Regn. No. 107147Ring Road, Surat+91 98250 56839
CA India Ankit Shah and Co. Chartered Accountants
Project FinanceServicesCalculatorKnowledgeAboutગુજરાતીEnquire
← Knowledge bank GST

Bill one party, ship to another? From 1 August, your e-way bill has to say so

A GSTN change that was due to go live in June, then got pushed back once already, finally lands on 1 August — and it bites hardest on exactly the kind of three-party billing that Surat's diamond and textile trade runs on every day.

By CA Ankit Shah27 July 20266 min read
In brief
  • From 1 August 2026, the e-way bill and e-invoice (IRN) systems will not accept a Bill-To/Ship-To transaction unless the Ship-To GSTIN is entered — "URP" if the consignee is unregistered — under a GSTN advisory that was originally due to take effect on 15 June 2026 and was deferred once already.
  • This lands hardest on exactly the pattern common in Surat's diamond and textile trade: goods billed to one party (a buyer, a principal) but physically shipped to another (a job worker, a consignment stockist, a second unit) — a routine arrangement, not an edge case.
  • A separate, more welcome change arrives the same day: a voluntary e-way bill closure facility, letting the supplier, recipient, transporter or driver mark an e-way bill "delivered" once goods actually reach the consignee, instead of leaving it open until it lapses on its own.
  • The government portal isn't the only thing that needs updating — ERP software, billing tools and any API integration used to generate e-way bills need their own patch, tested before the 1st, not after a truck is stopped at a check-post with an incomplete e-way bill.
Five days out — what actually changes GSTN's e-way bill portal update, due once already on 15 June, now live from 1 August 2026 1 Ship-To GSTIN becomes mandatory Any e-way bill or IRN for a Bill-To/Ship-To transaction is rejected without it Applies at the point of generation — not something to fix afterwards 2 Unregistered consignee? Enter "URP" A blank Ship-To field is no longer read as "not applicable" — it is read as incomplete 3 Voluntary e-way bill closure goes live Supplier, recipient, transporter or driver can mark delivery — no need to wait for expiry 4 Your software needs the patch too ERP, billing tools and API integrations must be tested — the portal update alone isn't enough GSTN advisory, 20 May 2026 — rollout originally set for 15 June 2026, deferred once to 1 August 2026 after industry representations on integration time. No further deferral has been indicated.
One GSTN advisory, one deferral, one live date. Four things actually change on 1 August 2026 — most of the confusion comes from treating them as one thing.

A Surat diamond unit sells a parcel to a trading house in Mumbai, but the goods move straight from the cutting-and-polishing unit to a third party's godown for onward job work. A textile manufacturer bills a distributor in Ahmedabad, but ships the fabric directly to the distributor's dyeing unit two streets away from the mill. Both are ordinary Bill-To/Ship-To transactions — the invoice names one party, the delivery challan and e-way bill name another. From 1 August 2026, the e-way bill and e-invoice systems will not let either of those transactions through unless the Ship-To party's GSTIN is entered correctly. It sounds like a small field. For businesses that run on exactly this pattern, it is the difference between goods moving on schedule and a shipment stuck without a valid e-way bill.

A date that has already moved once

GSTN's advisory dated 20 May 2026 announced a set of enhancements to the e-way bill and e-invoice (IRN) APIs, aimed at improving data quality and traceability of goods movement — chief among them, mandatory capture of the Ship-To GSTIN wherever a transaction follows the Bill-To/Ship-To model. The production rollout was originally scheduled for 15 June 2026. It didn't happen on that date. Trade bodies and software vendors flagged that the lead time was too short to update ERP systems, test API integrations and retrain billing staff, and GSTN pushed the live date to 1 August 2026. That is the date now approaching. Nothing in the reporting around this deferral suggests a second postponement is coming, and a business that treated the June slip as reason to wait is now five days from the change actually landing.

The invoice already answers who is being billed and who is receiving the goods. From 1 August, the e-way bill has to answer the second half of that question too — or it doesn't get generated at all.

Why this is a Surat problem, not a niche one

Bill-To/Ship-To transactions are often treated, in general GST commentary, as an edge case worth a footnote. In practice, for a trading city built on job work, consignment stockists and multi-unit manufacturing, they are closer to routine. A diamond exporter routing rough or semi-finished stones through a job-work cutting unit before the polished goods reach the buyer; a textile trader whose fabric is billed to the buyer's head office but shipped to whichever of the buyer's units is running that week; a manufacturer supplying a distributor who then has the goods forwarded straight to a retailer or a second processing unit — all of these involve a Bill-To party who never touches the goods and a Ship-To party who does, and both parties usually hold their own GSTIN. Under the new rule, the e-way bill has to name the Ship-To GSTIN explicitly. Where the actual recipient is not GST-registered — a smaller job worker below the threshold, for instance — the field cannot be left blank either; "URP" (unregistered person) has to be entered. A transaction that used to generate cleanly with only the billed party's details will now be rejected at the point of generation if this second GSTIN, or the URP marker, is missing.

Supplier Issues invoice + e-way bill Surat unit Bill-To party Named on the invoice GSTIN already required Ship-To party Actually receives the goods Job worker, consignee, second unit NEW FROM 1 AUGUST 2026 Ship-To GSTIN mandatory — "URP" if unregistered The Bill-To party's GSTIN was already a mandatory e-way bill field. What changes on 1 August is the Ship-To side — the party that never appears on the invoice but is the one actually signing for the delivery.
Three parties, one shipment. The e-way bill has always captured who is billed — from 1 August, it must also capture who physically receives the goods.

The change that actually helps: voluntary closure

The same advisory brings in something businesses have informally asked for: a voluntary e-way bill closure facility. Today, an e-way bill stays "active" until it naturally expires based on the validity period calculated from distance — regardless of whether the goods were actually delivered days earlier. That gap between actual delivery and system expiry is where genuine confusion creeps in during any departmental scrutiny of goods movement, since an open e-way bill can read as goods still in transit. From 1 August, the supplier, the recipient, the transporter or the driver will be able to mark the e-way bill as closed once delivery has actually happened, rather than leaving that mismatch sitting on record until the validity period runs out on its own. It is optional, not mandatory — but for any business that wants its e-way bill trail to actually reflect what happened on the ground, it is worth building into the standard delivery-confirmation process rather than treating as an afterthought.

What to check before 1 August

Start by identifying which of your regular transactions actually follow the Bill-To/Ship-To pattern — most businesses can list these from memory: the job workers, the consignment arrangements, the multi-unit dispatches. For each one, confirm you hold the Ship-To party's correct GSTIN on file, and know which counterparties are unregistered so "URP" gets entered rather than the field being left blank by habit. If e-way bills or e-invoices are generated through accounting software, a billing portal, or a direct API integration rather than typed manually on the government portal, check with that vendor now whether their system has already been updated for the mandatory field — a "we'll get to it" answer five days before the deadline is not a comfortable place to be standing. And if your business plans to use the new voluntary closure facility, decide who is responsible for marking deliveries closed — a driver, a warehouse clerk, the transporter — before the first shipment moves under the new rule, not after the first one is questioned for staying open too long.

Key takeaways

  • From 1 August 2026, Ship-To GSTIN becomes mandatory for any Bill-To/Ship-To e-way bill or e-invoice (IRN) — "URP" if the consignee is unregistered — under a GSTN advisory that was already deferred once from 15 June 2026.
  • This lands squarely on job work, consignment stockist and multi-unit dispatch arrangements — routine, not rare, in Surat's diamond and textile trade.
  • A separate voluntary e-way bill closure facility also goes live the same day, letting delivery be marked complete instead of waiting for the e-way bill to expire on its own.
  • ERP software, billing tools and API integrations need their own testing before 1 August — the government portal being ready does not mean your system is.

Sources

  1. Goods and Services Tax Network, advisory dated 20 May 2026 — functional enhancements to the e-Way Bill and e-Invoice (IRN) systems, including mandatory capture of Ship-To GSTIN for Bill-To/Ship-To transactions; as reported by TaxO.
  2. Goods and Services Tax Network, advisory extending the rollout of mandatory Ship-To GSTIN and the voluntary e-way bill closure facility from 15 June 2026 to 1 August 2026; as reported by Taxscan and A2Z Taxcorp.
  3. GST e-Way Bill System, official portal, for current advisories and API specifications.
  4. Practical implementation guidance on Bill-To/Ship-To e-way bill changes, as reported by Tally Solutions.

This article is general information, not professional advice. Rules change; verify current provisions or contact the office for advice on your situation.

Discuss your situation

A short call is usually enough to tell you what you need.

WhatsApp More articles