Operations & Best Practices

Ship-To GSTIN Became Mandatory on 1 August: How It Breaks Transit Claim Documentation

From 1 August 2026 the Ship-To GSTIN is a mandatory field on Bill-To/Ship-To e-way bills, and unregistered consignees must be tagged URP. Surveyors already treat the e-way bill as the anchor document for goods-in-transit claims, so any mismatch between the named consignee, the party with insurable interest and the policy's transit clause now surfaces as a documentation dispute at claim stage.

Tarun Kumar Singh
Tarun Kumar SinghStrategic Risk & Compliance SpecialistAIII · CRICP · CIAFP
9 min read

Listen to this article

Audio version • 9 min read

e-way billtransit claimsinsurable interestdocumentationGST3PL

Last reviewed: August 2026

What changed on the e-way bill portal from 1 August 2026

The GSTN e-way bill portal changes that took effect on 1 August 2026 make the Ship-To GSTIN a mandatory data field for applicable Bill-To/Ship-To transactions. Where the consignee receiving the goods is unregistered under GST, the field must be tagged URP (unregistered person) rather than left blank. Until this change, the party physically receiving the goods in a Bill-To/Ship-To movement could pass through the e-way bill with minimal identification, and many ERP integrations simply did not capture it.

GSTN originally set the implementation date at 15 June 2026 and deferred it to 1 August 2026 to give businesses time to upgrade ERP systems, accounting software and API integrations (TaxGuru / Adwani & Co, 2026). That deferral window is now closed. An e-way bill for an applicable Bill-To/Ship-To transaction generated without a Ship-To GSTIN or URP tag will not validate.

Alongside the mandatory field, GSTN opened an optional Voluntary E-Way Bill Closure Facility, also effective 1 August 2026. Suppliers, recipients, transporters and authorised drivers can now formally close a completed e-way bill within the prescribed timeline, creating a portal record that a specific movement ended.

The tax-compliance commentary has treated this as an ERP upgrade problem. For anyone who buys or administers transit insurance, it is also a claims-documentation problem, because the e-way bill now states, in a validated government record, exactly who the goods were shipped to.

Why the e-way bill anchors goods-in-transit claims

Surveyors appointed on goods-in-transit and marine cargo claims work from a standard document set: the invoice, the lorry receipt or consignment note, the e-way bill, the policy or certificate, and the delivery challan or proof of delivery. Among these, the e-way bill has become the anchor, for a simple reason. It is a system-validated record, generated before movement, that ties together the consignor, the consignee, the goods description, the value, the vehicle and the route. Unlike a lorry receipt, it cannot be conveniently redrafted after a loss.

When a claim is intimated, the surveyor reconciles the e-way bill against the invoice and the policy. Three questions get asked in sequence:

  1. Do the goods, value and route on the e-way bill match the invoice and the claimed loss?
  2. Was the movement within the transit insured under the policy, from the named or described origin to the named or described destination?
  3. Is the claimant a party with insurable interest in the goods at the time of loss?

Before 1 August, the Ship-To leg of a Bill-To/Ship-To movement was often documented loosely, and a surveyor reconciling a claim had some interpretive room. Now the portal record names the ship-to party with a validated GSTIN, or expressly tags them URP. Whatever the e-way bill says about who the goods were going to, the claim file must be consistent with it.

Bill-To/Ship-To: three parties, one loss, one policy

A Bill-To/Ship-To transaction has at least three parties: the supplier who dispatches the goods, the buyer who is invoiced (bill-to), and the recipient who physically receives them (ship-to). Taxscan's 2026 analysis of the change lists the typical patterns: manufacturers billing distributors but shipping directly to retailers, e-commerce sellers routing stock through fulfilment centres, and the Bill-To/Ship-To chains common in FMCG, pharma and auto parts distribution.

When a truck overturns on that movement, three separate legal frames decide who can claim:

  • The e-way bill names a consignor, a bill-to party and now, mandatorily, a ship-to GSTIN or URP tag. This is what the surveyor reads first.
  • The sale contract and the Sale of Goods Act, 1930 decide when risk passes. Under Section 26, risk prima facie travels with property in the goods unless the parties agree otherwise, so an ex-works sale puts transit risk on the buyer from the factory gate, while a delivered-duty or FOR-destination sale keeps it with the seller until delivery.
  • The policy insures a named insured for described transits. An annual open cover or sales turnover policy typically covers goods "sold and dispatched by the insured" or "at the insured's risk", within a described geographical scope and transit clause.

These three frames were never automatically aligned. What changed on 1 August is that the first frame stopped being vague. A validated Ship-To GSTIN that belongs to a party outside the policy's insured description is now visible to the insurer and the surveyor on the first document they open.

Where the mismatch surfaces at claim stage

Consider a manufacturer that sells to a distributor on ex-works terms, but ships directly to the distributor's retailer under a Bill-To/Ship-To e-way bill. Risk passed to the distributor at the factory gate. The e-way bill now carries the retailer's GSTIN as the mandatory ship-to party. The manufacturer's open cover insures goods "dispatched by the insured at the insured's risk".

If the consignment is lost in transit, the claim can fail on documentation before anyone argues quantum:

  • The manufacturer intimates the claim because it generated the e-way bill, but on ex-works terms it no longer bore the risk, so its insurable interest at the time of loss is contestable.
  • The distributor bore the risk but appears on the e-way bill only as the bill-to party, and its own policy, if it has one, describes transits "to the insured's premises", which this movement never touched.
  • The retailer is the named ship-to party but has no contract of insurance at all.

The same structure appears with URP tagging. A quick-commerce seller shipping to an unregistered franchisee or collection point must tag the consignee URP. A surveyor reading URP on the anchor document will ask who the unregistered recipient was and what interest the claimant had in goods being delivered to them. If the policy's insured description or transit clause does not reach that delivery point, the URP tag is the first thread the insurer pulls.

Who is exposed: manufacturers, 3PLs and quick-commerce sellers

The exposure concentrates where Bill-To/Ship-To volume is structural rather than occasional.

Manufacturers with distributor networks. Direct-to-retailer dispatch against distributor invoicing is standard in FMCG, pharma and auto parts. Every such dispatch now names the retailer's GSTIN on the e-way bill. If the manufacturer's marine open cover was worded years ago around "dispatches to the insured's distributors", the anchor document now contradicts the insured description on every direct-to-retailer movement.

3PLs and fulfilment operators. E-commerce sellers using fulfilment centres are squarely in the affected class identified by Taxscan. Goods move seller to fulfilment centre, fulfilment centre to customer, sometimes fulfilment centre to fulfilment centre, with the ship-to party changing at each leg. A 3PL's carrier legal liability cover and the cargo owner's transit policy respond to different interests, and the mandatory ship-to field now documents each leg's consignee precisely. A consolidated program along the lines discussed in warehouse and goods-in-transit consolidated cover needs its insured description checked against these actual movement patterns.

Quick-commerce and D2C sellers. Deliveries to unregistered recipients, dark stores operating under a different entity's GSTIN, and marketplace stock transfers all produce ship-to entries (or URP tags) that may not match the entity that bought the insurance.

In each case the operational teams generating e-way bills and the teams buying insurance rarely compare notes. The 1 August change forces the comparison, because the surveyor will make it if the insured does not.

The mapping exercise: reconcile four documents before the next loss

The fix is a one-time mapping exercise across four document sets, repeated whenever distribution patterns change.

  1. Extract your actual movement patterns. Pull 3 to 6 months of e-way bill data and classify movements: straight consignor-to-consignee, Bill-To/Ship-To to registered parties, and movements with URP consignees. Most insureds are surprised by the share of volume in the second and third buckets.
  2. Map each pattern to its risk-transfer point. For every sale term in use (ex-works, FOR destination, delivered), fix where risk passes under the contract and Section 26 of the Sale of Goods Act, 1930. This tells you which party holds insurable interest on each leg of each pattern.
  3. Read the open cover against the map. Check the insured description (does it cover goods sold on terms where the buyer bears risk, if you intend to insure them as agent or under a seller's contingency interest?), the transit clause (does cover run to the ship-to destination actually used, including fulfilment centres and retailer premises?), and any warehouse-to-warehouse wording against where transits genuinely begin and end.
  4. Fix the gaps by endorsement, not by hope. Typical corrections: widening the insured description to cover goods at the insured's risk "howsoever dispatched, including under Bill-To/Ship-To arrangements", adding a seller's interest or contingency clause for ex-works sales, naming associated entities or adding an agent clause where a group entity generates the e-way bill, and extending destination scope to third-party delivery points.

The same discipline that governs marine claim files generally, covered in our marine cargo claim documentation guide, applies here: the file the surveyor sees should tell one consistent story.

Use the voluntary closure facility as claims evidence

The Voluntary E-Way Bill Closure Facility that opened alongside the mandatory field is optional for tax purposes, but it has a claims use. Transit policies terminate cover at a defined point, commonly delivery at the destination named or described in the policy. Disputes about whether goods were still "in transit" at the time of loss, particularly for thefts from parked vehicles or losses during intermediate storage, often turn on when transit ended.

A closure record filed by the supplier, recipient, transporter or authorised driver within the prescribed timeline is a timestamped, portal-validated statement that a movement was completed. Used consistently, it gives the insured contemporaneous evidence of when transit ended for each consignment, and its absence for a given movement flags an open leg worth investigating before an insurer does.

For 3PLs and fleet operators, building closure into the delivery workflow costs little, since drivers can be authorised to close bills at delivery. For cargo owners, asking your transporter or 3PL to adopt closure on your consignments strengthens every future claim file at zero premium cost.

Getting the wording side right requires knowing exactly how each insurer's transit clause, insured description and Bill-To/Ship-To treatment differ, and those differences across the market are wider than most buyers assume. Sarvada gives commercial insurance brokers structured, searchable access to insurer policy wordings and the intelligence around them, so a client's actual e-way bill patterns can be tested against the exact clauses on offer before a loss does the testing. Request Access to bring that wording detail into your transit placements.

About the Author

Tarun Kumar Singh

Tarun Kumar Singh

Strategic Risk & Compliance Specialist

  • AIII
  • CRICP
  • CIAFP
  • Board Advisor, Finexure Consulting
  • Developer of the Behavioural Underinsurance Risk Index (BURI)

Tarun Kumar Singh is a seasoned risk management and insurance professional based in Bengaluru. He serves as Board Advisor at Finexure Consulting, where he advises insurance, fintech, and regulated firms on governance, growth, and trust. His work spans insurance broker regulatory frameworks across India, UAE, and ASEAN, IRDAI compliance and Corporate Agency model reform, VC governance in insurtech, and MSME insurance gap analysis. He is the developer of the Behavioural Underinsurance Risk Index (BURI), a framework applying behavioural economics to underinsurance and insurance fraud risk.

Frequently Asked Questions

What exactly became mandatory on the e-way bill from 1 August 2026?
For applicable Bill-To/Ship-To transactions, the Ship-To GSTIN became a mandatory data field on the e-way bill from 1 August 2026. Where the party physically receiving the goods is not registered under GST, the field must be tagged URP (unregistered person). GSTN had originally set 15 June 2026 as the implementation date and deferred it to 1 August 2026 so that businesses could upgrade ERP systems, accounting software and API integrations. GSTN also opened an optional Voluntary E-Way Bill Closure Facility on the same date, letting suppliers, recipients, transporters and authorised drivers close completed e-way bills within the prescribed timeline.
Does a Ship-To GSTIN mismatch mean my transit claim will be rejected?
Not by itself. Insurable interest is decided by risk transfer under the contract of sale, read with the Sale of Goods Act, 1930, not by who appears on the e-way bill. But the e-way bill is the anchor document a surveyor reconciles first, and a validated ship-to entry that names a party outside the policy's insured description obliges the claimant to prove its interest with the sale contract, invoice terms and payment trail. That is manageable if the file is prepared, and a genuine gap if the policy's insured description or transit clause never contemplated the movement pattern, for example ex-works sales the seller continued to insure, or deliveries to third-party fulfilment centres.
Who bears the transit risk in a Bill-To/Ship-To transaction?
It depends on the sale terms between each pair of parties, not on the e-way bill roles. Under Section 26 of the Sale of Goods Act, 1930, risk prima facie passes with property in the goods unless the parties agree otherwise. On ex-works terms the bill-to buyer typically bears transit risk from the seller's gate even though goods travel to a third-party ship-to location. On FOR-destination or delivered terms the seller bears risk until delivery at the ship-to point. Each party should insure the legs where it bears risk, or the seller should hold a seller's interest or contingency extension where it wants protection on buyer's-risk sales.
What should a 3PL or fulfilment operator do about this change?
Three things. First, confirm your e-way bill workflow captures the Ship-To GSTIN or URP tag correctly on every leg, including inter-warehouse transfers, since a validation failure stops dispatch. Second, check how your carrier legal liability cover and your clients' cargo policies describe the consignee and destination, because the mandatory field now documents each leg's recipient precisely and inconsistencies surface at claim stage. Third, adopt the Voluntary E-Way Bill Closure Facility in the delivery workflow, since drivers and transporters can be authorised to close bills, creating timestamped proof of delivery completion that supports both your clients' claims and your own liability defence.
How does the voluntary closure facility help at claim stage?
Transit cover ends at a defined point, usually delivery at the destination described in the policy, and disputes often turn on whether goods were still in transit when the loss happened. A closure filed on the portal by the supplier, recipient, transporter or authorised driver within the prescribed timeline is a timestamped record that the movement was completed. Filed consistently, it gives contemporaneous evidence of when transit ended for each consignment. An e-way bill left unclosed on a disputed movement proves nothing against the insured, since the facility is voluntary, but a closure record in the claim file shortens the argument.

Related Glossary Terms

Related Insurance Types

Related Industries

Related Articles

Sarvada Intelligence

Ready to see Sarvada in action?

Explore the platform workflow or start a product conversation with our underwriting automation team.

Explore the platform