Ship-To GSTIN in E-way bill: 2026 Bill-To/Ship-To Compliance Guide 

Picture a common supply chain scenario: a distributor in Mumbai orders ₹8 lakh of industrial equipment from a manufacturer in Pune. The invoice is billed to the distributor’s Mumbai address, which serves as the Bill-To GSTIN. But the goods don’t go to Mumbai — they go directly to the distributor’s client’s construction site in Nagpur, making the client’s Ship-To GSTIN relevant for accurate GST invoicing and compliance.

On the e-way bill, the “Bill To” section shows the distributor’s Mumbai GSTIN and address. The “Ship To” section shows the Nagpur delivery address — but historically, many businesses either left the Ship-To GSTIN field blank or entered only the physical address without the registered GSTIN at that location.

The result: a persistent gap in the GST audit trail. GSTN could see that goods went to Nagpur, but had no reliable way to link that delivery to a registered GST entity and cross-verify it against GSTR-1 and GSTR-3B filings. The system had no confirmation of who actually received the goods.

The Ship-To GSTIN in E-way bill rule closes this gap permanently. For every Bill-To Ship-To e-way bill transaction, the GST registration at the actual delivery location must now be captured — or the e-way bill will not generate at all. This makes the Ship-To GSTIN Mandatory for applicable transactions under the E-way bill Ship-To GSTIN Rule 2026.

What Is a Bill-To/Ship-To Transaction?

A Bill-To/Ship-To transaction involves three distinct parties:

Party	Role
Supplier	Manufactures or sells the goods; issues the tax invoice
Bill-To Party (Buyer)	Places the order; receives the invoice; pays the supplier
Ship-To Party (Consignee)	The location or entity where goods are physically delivered

The defining feature: the invoice goes to one party, the goods go to another.

This structure is common across:

• Distributors and dealers directing goods to end customers
• Manufacturers shipping directly to buyer’s warehouses or project sites
• E-commerce operators fulfilling orders from seller stock to buyer addresses
• Businesses with multi-state branches — invoice raised at HQ, goods delivered to a branch GSTIN in another state
• Traders who don’t hold stock and instead direct suppliers to ship to their customers

The Legal Basis: Section 10(1)(b) of the IGST Act

Bill-To/Ship-To transactions under GST are governed by Section 10(1)(b) of the IGST Act, 2017. The provision states that where goods are delivered by a supplier to a recipient on the direction of a third person (the Bill-To party), the third person is deemed to have received the goods, and the place of supply is the principal place of business of that third person (the Bill-To party) — not the physical delivery location.

This has a critical tax implication: the applicable GST type follows the Bill-To party’s location, not where goods physically arrive.

Example:

Supplier A (Maharashtra) is directed by Buyer B (Gujarat) to ship goods to End Customer C (Karnataka).

• Supply 1 (A → B): Place of supply = Gujarat (B’s principal place of business). Maharashtra → Gujarat = inter-state → IGST charged by A on B’s invoice.
• Supply 2 (B → C): Place of supply = Karnataka (C’s location). Gujarat → Karnataka = inter-state → IGST charged by B on C’s invoice.

This means only one e-way bill is required for the physical movement of goods (from A in Maharashtra to C in Karnataka), but two invoices are raised for the two supplies.

The August 1, 2026 Change: What Exactly Is New

What Changed

The Ship-To field on the e-way bill form has always existed. Businesses could enter a delivery address in the “Ship To” section of the eway bill. What was not mandatory until now: capturing the GSTIN registered at that delivery location when the Ship-To party is a registered GST entity.

Ship-To GSTIN Mandatory requirements apply for all Bill-To Ship-To E-way bill transactions:

Scenario	What to Enter in Ship-To GSTIN Field
Ship-To party is GST-registered	Their valid, active GSTIN
Ship-To party is unregistered	“URP” (Unregistered Person)
Export transactions	Exempt — not required
B2B/SEZ transactions (e-invoice mandated businesses)	GSTIN set at IRN generation; cannot be overridden at E-Way Bill stage

How the E-way bill Form Works for Bill-To/Ship-To

The eway bill form has a dedicated “TO” section with two sub-sections:

BILL TO	SHIP TO
GSTIN of Buyer	GSTIN of Consignee ← NEW
Name of Buyer	Name of Consignee
Address (Billing)	Address (Delivery)
State	State
PIN Code	PIN Code

Before The New E-way bill Rule: The Ship-To GSTIN field was optional. Many businesses entered only the delivery address without the GSTIN, or left the Ship-To section partially blank.

After The New E-way bill Rule: The Ship-To GSTIN Mandatory requirement comes into force under the E-way bill Ship-To GSTIN Rule 2026. A blank field or invalid GSTIN will block eway bill generation — both via the portal interface and API.

Compliance Scenarios in Detail

Scenario 1 — Distributor Directing Supplier to Customer’s Warehouse

Distributor (Delhi, GSTIN: 07XXXXX) buys goods from Supplier (Pune, GSTIN: 27XXXXX) and directs delivery to Customer’s warehouse (Chennai, GSTIN: 33XXXXX).

• Invoice: Supplier → Distributor (Delhi GSTIN)
• Physical delivery: Pune → Chennai
• E-way bill Bill-To: Distributor’s Delhi GSTIN
• E-way bill Ship-To: Customer’s Chennai GSTIN ← mandatory from Aug 1

✅ One E-WAY BILL; two invoices; Ship-To GSTIN = 33XXXXX

Scenario 2 — Company Delivering to Its Own Branch in Another State

HQ (Bengaluru, GSTIN: 29XXXXX) purchases goods invoiced to its Bengaluru GSTIN but directs delivery to its branch office (Hyderabad, GSTIN: 36XXXXX) for internal use.

• E-way bill Bill-To: HQ’s Bengaluru GSTIN (29XXXXX)
• E-way bill Ship-To: Branch’s Hyderabad GSTIN (36XXXXX) ← mandatory from Aug 1

✅ Both Bill-To and Ship-To GSTINs are known and registered. Update ERP master data to store branch GSTINs at the delivery location level to comply with the Ship-To GSTIN in E-way bill requirement.

Scenario 3 — Goods Delivered to an Unregistered Project Site

A construction equipment supplier (Mumbai) invoices a contractor (registered, GSTIN: 27XXXXX) but delivers to a project site in Nashik — the site has no GST registration.

• E-way bill Bill-To: Contractor’s GSTIN (27XXXXX)
• E-way bill Ship-To: “URP” ← mandatory entry when delivery location is unregistered

✅ “URP” is the correct entry. The Ship-To address (Nashik site details) should still be accurately entered in the address fields.

Scenario 4 — E-Invoice Mandated Business (B2B/SEZ)

A manufacturer (₹25 crore turnover) generates an IRN for a B2B supply. The Ship-To GSTIN was entered at IRN generation.

• When generating the eway bill from the IRN, the Ship-To GSTIN flows from the IRN and cannot be changed
• Any discrepancy between the Ship-To GSTIN on the eway bill and the recipient GSTIN on the invoice will attract scrutiny under Section 129

✅ Ensure Ship-To GSTIN is accurate at IRN generation — correction at the eway bill stage is not possible for B2B/SEZ transactions.

Scenario 5 — Export Transactions

An exporter (Mumbai) raises a tax invoice on a foreign buyer and ships goods from Mumbai to Nhava Sheva port for export.

• Export transactions are excluded from the mandatory Ship-To GSTIN requirement
• Normal export eway bill generation process applies

✅ No change for export transactions.

ITC Implications in Bill-To/Ship-To Transactions

The mandatory Ship-To GSTIN in E-way bill rule is not just an operational change — it has direct ITC consequences.

Under Section 16 of the CGST Act, goods are treated as received by the Bill-To party (registered buyer) even when delivered to a third location — a legal fiction that allows the Bill-To party to claim ITC on the supplier’s invoice.

Key ITC rules for Bill-To/Ship-To:

Party	ITC Eligibility
Supplier (A)	Charges GST to Bill-To party; output tax liability
Bill-To Party (B)	Eligible to claim ITC on A’s invoice (goods deemed received under Sec 16)
Ship-To Party (C)	Eligible to claim ITC on B’s invoice when B raises its own invoice to C

The Ship-To GSTIN mandate directly protects ITC:

• A mismatch between the Ship-To GSTIN on the eway bill and the GSTIN on the invoice will create a reconciliation discrepancy in GSTR-2B.
• The Ship-To party may face ITC denial if the delivery cannot be verified to their registered premises.
• Post-August 1, GSTN will cross-verify Ship-To GSTIN in E-way bill data against the corresponding return filings — any gap weakens the ITC claim.

ERP and API Impact: What Your Team Must Do Before August 1

This is where the operational weight of the rule falls. For most businesses, the Ship-To GSTIN is not just a manual entry — it flows from master data in your ERP into the API payload submitted to the eway bill portal.

Changes Required in ERP Systems

1. Customer/Delivery Location Master Data

Your customer master must store GSTINs at the delivery location level, not just at the customer/bill-to level. A single buyer may have multiple GSTINs across states. Each delivery address must have its corresponding GSTIN mapped.

Action: Audit your customer master data. For every customer with multiple delivery locations (warehouses, branches, project sites), collect and verify the GSTIN for each location. Update your ERP with location-level GSTIN mapping to comply with the Ship-To GSTIN Compliance Guide.

2. Sales Order and Invoice Workflow

The Ship-To GSTIN must be captured at order/invoice creation, not added retroactively before dispatch. Most ERP sales order forms have “Bill To” and “Ship To” address fields — the Ship-To GSTIN field must now be treated as mandatory at order entry.

Action: Make the Ship-To GSTIN Mandatory field in your ERP’s sales order/invoice form whenever Bill-To and Ship-To addresses differ.

3. API Payload Update

The eway bill API specification has been updated by NIC to include the Ship-To GSTIN as a required field. Any API call for a Bill-To Ship-To E-way bill transaction that omits this field will fail.

Action: Confirm with your ERP vendor / GSP / ASP that the updated API specifications have been deployed to production. Test in the GSTN sandbox.

4. Validation Logic

Your system should validate the Ship-To GSTIN before submission:

• Is the GSTIN format correct (15 characters)?
• Is the GSTIN active (not cancelled or suspended)?
• Does the state code in the GSTIN match the Ship-To state?

Any of these validation failures will block eway bill generation on the portal even after August 1 if the GSTIN is incorrect.

For ERP Vendors, GSPs, and ASPs

The NIC upgraded API specifications in the sandbox, with the production date planned for deployment before August 1, 2026. ERP vendors, GSPs, ASPs, and system integrators must be aware of the updated API specifications, test them in the sandbox, and configure their systems according to the E-way bill Ship-To GSTIN Rule 2026.

If your ERP vendor has not communicated this change or released an update, contact them immediately.

Common Errors to Avoid After August 1

Error	Consequence	Fix
Ship-To GSTIN field left blank in API payload	API call fails; e-way bill not generated	Make field mandatory in ERP; populate from delivery location master
“URP” not entered for unregistered Ship-To party	API call fails; e-way bill not generated	Configure ERP to default to “URP” when delivery location has no GSTIN
Ship-To GSTIN state code doesn’t match Ship-To state	Validation failure on portal	Verify state code (first 2 digits of GSTIN) against delivery state in master data
Cancelled or inactive Ship-To GSTIN	Portal blocks generation	Run periodic GSTIN validation checks on your customer/location master
Attempting to override Ship-To GSTIN at e-way bill stage for B2B/SEZ	Override blocked — field is locked	Correct Ship-To GSTIN at IRN generation; it flows through to e-way bill unchanged
Ship-To GSTIN mismatch with invoice recipient	Audit flag under Section 129	Ensure Ship-To GSTIN in E-way bill exactly matches the GSTIN on the tax invoice

Compliance Checklist: Ship-To GSTIN (Before August 1, 2026)

• Have you audited your customer master data for delivery locations that have a separate GSTIN from the billing GSTIN?
• Have you collected and verified GSTINs for all active Ship-To locations (warehouses, branches, project sites, customer delivery points)?
• Is the Ship-To GSTIN field mapped at the delivery location level (not just customer level) in your ERP, as recommended in this Ship-To GSTIN Compliance Guide?
• Have you confirmed with your ERP vendor / GSP / ASP that the updated NIC API specifications are deployed or scheduled before August 1?
• Does your sales order / invoice workflow require Ship-To GSTIN mandatory field when Bill-To and Ship-To addresses differ?
• Have you configured “URP” as the default value for Ship-To GSTIN when the delivery location is unregistered?
• For e-invoice-mandated businesses: is your Ship-To GSTIN entered accurately at IRN generation (since it cannot be changed at eway bill stage for B2B/SEZ)?
• Have you run a validation check on all Ship-To GSTINs in your master — checking for active status and state code match?
• Has your logistics/dispatch team been briefed that eway bills will fail if Ship-To GSTIN is blank?

Conclusion

The Ship-To GSTIN in E-way bill mandate is not a paperwork change — it is a supply chain data change. The businesses most at risk are those that have delivery locations in their ERP without GSTIN mapping, and those whose ERP vendors have not yet released the API update. Both are solvable before August 1. Neither is solvable at a GST checkpoint after goods have been detained.

Following this Ship-To GSTIN Compliance Guide and implementing the E-way bill Ship-To GSTIN Rule 2026 in your ERP and dispatch processes will help businesses avoid shipment disruptions, ensure GST compliance, and maintain seamless logistics operations.

Frequently Asked Questions