Mandatory Ship-To GSTIN Field from June 15 2026: Compliance Guide

Starting June 15, 2026, the Goods and Services Tax Network (GSTN) requires every B2B e-invoice to include a valid Ship-To GSTIN in the ShipDtls section of the JSON payload. This means that if your business generates e-invoices through the Invoice Registration Portal (IRP), your billing software must populate the consignee's GSTIN for every transaction involving goods delivery. Failing to comply will result in IRN generation failure, invoice rejection, and potential ITC disruption for your buyers. Here is everything you need to know to prepare your systems before the deadline.

What Is the Ship-To GSTIN Field in E-Invoices?

Ship-To GSTIN is a data field within the ShipDtls (Shipping Details) section of the e-invoice JSON schema that records the 15-character Goods and Services Tax Identification Number of the party receiving physical delivery of goods. It is governed by Rule 48(4) of the CGST Rules, 2017, and administered by GSTN through the Invoice Registration Portal (IRP).

The e-invoice JSON schema contains multiple party identifiers. The SellerDtls captures the supplier's GSTIN. The BuyerDtls captures the party paying for goods and claiming ITC. The ShipDtls captures the consignee at the actual delivery point. Until now, ShipDtls was optional when the delivery address matched the buyer's registered address. From June 15, 2026, the IRP validation engine treats ShipDtls > Gstin as a mandatory field for all B2B document types, including invoices, credit notes, and debit notes involving goods movement.

Why GSTN Made Ship-To GSTIN Mandatory

The decision to mandate the Ship-To GSTIN field addresses three systemic issues that have plagued GST compliance since e-invoicing launched in 2020. First, incorrect ITC distribution. When goods move to a location different from the buyer's registered address without proper GSTIN mapping, the recipient at the delivery point cannot reconcile the invoice in their GSTR-2B. Second, e-way bill mismatches. The Ship-To address in e-invoices auto-populates Part A of the e-way bill. Without the GSTIN, state-wise supply tracking breaks down. Third, anti-evasion measures. The government uses Ship-To data to cross-verify actual goods movement against reported transactions.

Revenue Impact and Government Rationale

According to the 53rd GST Council Meeting minutes, ITC fraud through fake invoices involving non-existent delivery addresses accounted for ₹15,000 crore in detected evasion during FY 2024-25. Mandating Ship-To GSTIN creates an additional verification layer. Every delivery point must now correspond to a valid, active GSTIN, making it significantly harder to generate invoices for phantom transactions. The change also helps state governments track inter-state supplies more accurately, reducing IGST settlement disputes between states.

For compliant businesses, this change brings a positive outcome: fewer bogus ITC claims in the ecosystem means faster refund processing and reduced scrutiny for genuine taxpayers. The GST Council estimates that mandating Ship-To GSTIN validation will reduce fraudulent ITC claims by 15% to 20% in the first year, improving the overall health of the indirect tax system and potentially reducing future rate adjustments.

Who Must Comply: Applicability Rules

The mandatory Ship-To GSTIN requirement applies to every business currently generating e-invoices under Rule 48(4) of the CGST Rules. Here is the current applicability based on aggregate turnover thresholds:

E-Invoice JSON Schema: Technical Changes Explained

The e-invoice JSON schema (version 1.1) organizes invoice data into sections. The ShipDtls section previously allowed null values for Gstin when goods were delivered to the buyer's registered address. Post June 15, 2026, the IRP validation rules change as follows:

Sample JSON Payload (ShipDtls Section)

Here is how the ShipDtls section looks in a compliant e-invoice JSON payload after June 15, 2026:

Step-by-Step Compliance Checklist for Businesses

Preparing for the June 15, 2026 deadline requires coordinated action across your finance, IT, and operations teams. Follow this 8-step implementation plan:

1. Audit your customer master data (by May 25, 2026): Export all customer records from your ERP. Identify entries where delivery address differs from billing address. Flag entries missing Ship-To GSTIN. For businesses with 500+ customers, prioritize high-volume buyers first.
2. Collect missing GSTINs from customers (by May 31, 2026): Send communication to all B2B customers requesting their delivery location GSTINs. Use a standardized form capturing GSTIN, trade name, full address, pin code, and state code for each delivery point.
3. Validate GSTINs using the GST portal (by June 3, 2026): Cross-verify every collected GSTIN on services.gst.gov.in. Confirm the GSTIN is active (not cancelled or suspended). Verify the state code matches the delivery pin code.
4. Update ERP/billing software configuration (by June 5, 2026): Work with your software vendor to make Ship-To GSTIN a mandatory field in invoice generation. Update API integrations with IRP to include ShipDtls in every JSON payload. Add GSTIN format validation (2-digit state code + 10-character PAN + 1-digit entity + 1-character Z + 1 check digit).
5. Map delivery addresses to GSTINs in your system (by June 7, 2026): Create a mapping table linking each unique delivery address to its GSTIN. For customers with multiple branches, store branch-level GSTINs. Set the default Ship-To GSTIN to match Bill-To GSTIN for single-location customers.
6. Test on GSTN sandbox (by June 10, 2026): Register on einvoice1-sandbox.gst.gov.in and submit test invoices with populated ShipDtls. Verify IRN generation succeeds. Test edge cases: same Bill-To and Ship-To, inter-state delivery, and SEZ supplies.
7. Train your billing team (by June 12, 2026): Conduct a training session covering the new mandatory field, how to look up GSTINs, what to do when a customer provides an invalid GSTIN, and the escalation process for missing data.
8. Go live with monitoring (June 15, 2026): On the enforcement date, monitor your first 50 to 100 invoices closely. Track IRP rejection rates. Have a rapid-response process for any validation failures. Document all issues for your GST compliance file.

Impact on Different Business Models

The mandatory Ship-To GSTIN affects different business models in distinct ways. Understanding your specific scenario helps prioritize compliance efforts.

Standard B2B Transactions (Single Delivery Point)

For businesses where goods always ship to the buyer's registered address, the compliance burden is minimal. Set the Ship-To GSTIN equal to the Bill-To GSTIN in your invoice template. Ensure your software auto-populates this field. No additional data collection is needed for these customers.

Drop-Shipment (Bill-To-Ship-To) Transactions

Drop-shipment is the most complex scenario. Party A places an order with Party B, but Party B ships directly to Party C. The e-invoice must show: Bill-To = Party A's GSTIN (the buyer). Ship-To = Party C's GSTIN (the consignee at delivery). Both Party A and Party C need to coordinate with Party B to provide accurate GSTINs. If Party C's GSTIN is wrong, Party C cannot claim ITC on goods received.

E-Commerce B2B Transactions

E-commerce operators must update their B2B checkout flows to capture the delivery location GSTIN separately from the billing GSTIN. When a buyer with multiple warehouses orders through an e-commerce platform, the platform must pass the specific warehouse GSTIN (not the head office GSTIN) to the seller for e-invoice generation. This requires UI changes on the marketplace and API updates between operator and seller systems.

Inter-State Supply with Multiple Warehouses

Businesses with warehouses across states hold separate GSTINs for each state. A seller in Maharashtra (state code 27) shipping to a buyer's Tamil Nadu warehouse (state code 33) must use the 33-prefixed GSTIN as Ship-To, even if the purchase order comes from the buyer's Maharashtra head office. The ERP must map each delivery pin code to the correct state-level GSTIN automatically.

Deadline Timeline and Key Dates

Missing the June 15, 2026 deadline is not an option since the IRP will enforce validation automatically. Here is the compliance timeline every business should follow:

Penalties and Consequences of Non-Compliance

The financial and operational consequences of failing to comply with the Ship-To GSTIN requirement extend beyond simple invoice rejection. Here is what businesses face:

Immediate Consequences (Day 1 Non-Compliance)

• Invoice rejection by IRP: No IRN generated means the invoice is not legally valid under Section 31 of the CGST Act, 2017
• Billing cycle disruption: Goods shipped without a valid tax invoice violate Section 31(1) requirements
• E-way bill generation failure: Since e-invoice auto-generates Part A of the e-way bill, blocked invoices block goods movement
• Buyer's ITC denial: Without a valid IRN, the buyer cannot claim Input Tax Credit under Section 16(2)(aa)

Penalties Under CGST Act, 2017

• Section 122(1)(xi): Penalty of ₹10,000 or 100% of tax due, whichever is higher, for failing to issue invoice in accordance with provisions
• Section 125: General penalty of up to ₹25,000 for contravention of rules where no specific penalty is prescribed
• Section 29(2): Repeated non-compliance can trigger GST registration cancellation proceedings
• Section 61: Scrutiny of returns when mismatches between GSTR-1 and e-invoice data are detected

How Ship-To GSTIN Interacts with E-Way Bill System

The e-invoice system and e-way bill system are interconnected. When a supplier generates an e-invoice with goods movement, Part A of the e-way bill is auto-generated from the e-invoice data. The Ship-To address from ShipDtls becomes the destination in the e-way bill. After June 15, 2026, this linkage becomes tighter:

• The Ship-To GSTIN's state code determines the Place of Supply for IGST/SGST computation
• The Ship-To Pin code calculates distance for e-way bill validity period
• Mismatch between Ship-To state code in e-invoice and Part B vehicle details in e-way bill triggers alerts
• Goods intercepted during transit where the physical destination does not match Ship-To address face detention under Section 129 of the CGST Act

Businesses must ensure consistency between the Ship-To details in e-invoices and the actual delivery destination. Any discrepancy between the e-invoice Ship-To address and the e-way bill destination creates audit risks during physical verification by GST officers.

Place of Supply Determination

Under Section 10 of the IGST Act, 2017, the place of supply for goods involving movement is the location where the goods are delivered to the recipient. The Ship-To GSTIN's state code now serves as the definitive input for determining whether a supply is intra-state (CGST + SGST) or inter-state (IGST). If your billing system derives the place of supply from the Bill-To address instead of the Ship-To address, you will compute incorrect tax. This is a common misconfiguration. After June 15, 2026, ensure your tax calculation engine uses ShipDtls.Stcd (not BuyerDtls.Stcd) for place of supply determination when Ship-To and Bill-To states differ.

E-Way Bill Validity and Distance Calculation

E-way bill validity depends on the distance between the supplier's location and the Ship-To location. With ShipDtls now mandatory, the IRP auto-calculates approximate distance using the supplier's pin code and the Ship-To pin code. For distances up to 200 km, the e-way bill is valid for 1 day. For every additional 200 km, 1 additional day is added. Over-dimensional cargo gets 1 day per 20 km. Accurate Ship-To pin codes ensure your e-way bills have the correct validity period, preventing goods detention during transit for expired e-way bills.

Special Scenarios and Edge Cases

Exports (Zero-Rated Supply Without Payment)

For exports, the ShipDtls section uses the foreign buyer's address. Since foreign buyers do not hold Indian GSTINs, the Gstin field under ShipDtls accepts "URP" (Unregistered Person) for export transactions marked as EXPWP (Export With Payment) or EXPWOP (Export Without Payment) in TranDtls. The destination country, port code, and shipping bill number remain mandatory as before.

SEZ Supplies

Supplies to Special Economic Zones require the SEZ unit's GSTIN as Ship-To. SEZ units have unique GSTINs registered under Rule 47 of the SEZ Rules, 2006. The supply type code must be SEZWP or SEZWOP. The SEZ unit's GSTIN typically starts with the state code followed by the SEZ developer/unit's PAN.

Works Contract and Job Work

For job work where goods are sent to a job worker's premises, the Ship-To GSTIN should be the job worker's GSTIN. The delivery challan (Form GST DC) is used for initial movement, but when the final invoice is raised after job work completion, the Ship-To must reflect where finished goods are delivered, whether back to the principal or to a third-party buyer.

Free Samples and Branch Transfers

Stock transfers between branches of the same company (where separate GSTINs exist for different states) require the receiving branch's GSTIN as Ship-To. For free samples dispatched to potential clients, if the recipient is GST-registered, their GSTIN should be populated. For unregistered recipients, "URP" is used with full address details.

ERP-Specific Implementation Guidance

Different ERP platforms require different configuration approaches. Here is guidance for the most commonly used systems in India:

Tally Prime

In Tally Prime, navigate to Gateway > Alter > Stock Item/Ledger. For each party ledger, add the Ship-To address under "Additional Addresses." Enable the e-invoice configuration under F11 > Statutory Features. Update to Tally Prime Release 4.0 or later, which includes the updated JSON schema with mandatory ShipDtls. Configure the "Ship To" field as mandatory in Voucher Type settings for Sales invoices.

SAP Business One / S4HANA

SAP users should update the Business Partner master data to include multiple ship-to addresses, each with a GSTIN. In the Sales Order > Delivery tab, ensure the Ship-To address pulls from the Business Partner's delivery address list (not the main address). SAP's GST e-invoicing add-on (from version 2.0.4+) supports the ShipDtls section. Run transaction /n/GSTINDIA/EINV_CONFIG to verify field mappings.

Zoho Books

In Zoho Books, update each contact's "Shipping Address" with the corresponding GSTIN. Go to Contacts > Edit > Address tab > Shipping Address. Add the GSTIN field to the shipping address form. Zoho's e-invoice module (Settings > Taxes > E-Invoicing) auto-maps the shipping address GSTIN to ShipDtls.Gstin. Ensure your Zoho subscription includes the e-invoicing module (available on Professional plan and above).

GSTR-1 and GSTR-2B Reconciliation Impact

The Ship-To GSTIN field directly impacts how invoices appear in the buyer's GSTR-2B (auto-drafted ITC statement). When a supplier reports an invoice in GSTR-1 with a Ship-To GSTIN different from the Bill-To GSTIN, the invoice appears in the Ship-To party's GSTR-2B for ITC purposes. This is critical for drop-shipment scenarios.

How ITC Flow Works with Ship-To GSTIN

• Scenario 1 (Same Bill-To and Ship-To): Invoice appears in the buyer's GSTR-2B as normal. No change from current process.
• Scenario 2 (Different Bill-To and Ship-To): The invoice appears in the Bill-To party's GSTR-2B (the party paying). The Ship-To party sees it as a reference but does not claim ITC directly. ITC goes to whoever pays.
• Scenario 3 (Drop-shipment): Original buyer (Bill-To) claims ITC. The Ship-To party (consignee) receives goods but ITC flows to Bill-To. The consignee must have a separate invoice from the Bill-To party to claim their ITC.

Incorrect Ship-To GSTIN mapping causes invoices to appear in wrong GSTR-2B recipients, creating reconciliation nightmares during annual return filing. Businesses must verify that their GSTR-2B reflects correct invoices by cross-checking with the supplier's reported Ship-To details.

Industry-Specific Compliance Considerations

Manufacturing and Distribution

Manufacturing companies shipping to multiple distributor warehouses across states must maintain a GSTIN-mapped delivery directory. Each distributor warehouse has a state-specific GSTIN. The sales team must select the correct delivery address (and linked GSTIN) at order entry stage, not at dispatch. Late corrections after IRN generation require invoice cancellation (within 24 hours) and re-issuance.

Pharmaceutical and FMCG

The pharma and FMCG sectors operate through stockist and super-stockist networks. A manufacturer in Gujarat may ship to a redistribution stockist in Maharashtra, who then supplies to retailers. The manufacturer's e-invoice must show the stockist's Maharashtra GSTIN as Ship-To. With hundreds of stockists, pharmaceutical companies need automated GSTIN lookup integrated into their order management systems.

IT Services and Software

IT companies providing both software licenses (goods under GST) and services face a nuanced requirement. For software delivered on physical media or hardware shipped to a client's location, Ship-To GSTIN is mandatory. For purely digital/electronic delivery of software or cloud services with no physical movement, the ShipDtls section remains optional. Companies must configure their invoice templates to conditionally populate ShipDtls based on supply type.

Common Errors and How to Avoid Them

Based on analysis of e-invoice rejection data from IRP, these are the top 5 errors businesses will encounter with Ship-To GSTIN validation:

Action Plan for Buyers: Protecting Your ITC

Compliance is not just the supplier's responsibility. As a buyer receiving goods at your warehouses, branches, or project sites, you need to take proactive steps to ensure your suppliers report your correct Ship-To GSTIN. The consequences of supplier error fall on you through ITC denial. Here is your 5-step protection plan:

1. Share all your delivery-point GSTINs with each supplier: If you have registrations in multiple states, send a consolidated list with address-to-GSTIN mapping by June 1, 2026. Include the trade name, full address, pin code, and state code for each registration. A simple Excel template shared via email works.
2. Update purchase orders with delivery GSTIN: Add a mandatory "Ship-To GSTIN" field in your PO template. Ensure every PO clearly states which GSTIN corresponds to the delivery address. This gives your supplier no excuse for using the wrong GSTIN on their e-invoice.
3. Monitor GSTR-2B from June 15 onwards: After the mandate takes effect, verify that invoices from suppliers appear against the correct GSTIN in your GSTR-2B. Check within the first week of each month when GSTR-2B is generated. Flag discrepancies immediately to your procurement team.
4. Set up a reconciliation process: Compare goods received at each location (using GRN/Gate Entry data) against invoices appearing in that location's GSTR-2B. Any mismatch indicates incorrect Ship-To reporting by the supplier and must be corrected within the same return period.
5. Communicate with suppliers who get it wrong: If a supplier uses the wrong Ship-To GSTIN, request invoice cancellation (within 24 hours of IRN generation) and re-issuance with the correct GSTIN. After 24 hours, the supplier must issue a credit note and fresh invoice.

Frequently Asked Questions: Quick Reference

Beyond the detailed FAQ section above, here are quick-reference answers to the most searched questions about the Ship-To GSTIN mandate:

Can I Cancel and Re-Issue an E-Invoice with Wrong Ship-To GSTIN?

Yes. E-invoices can be cancelled within 24 hours of IRN generation using the Cancel IRN API on the IRP. After 24 hours, cancellation is not possible through IRP. You must issue a Credit Note referencing the original IRN, and then generate a fresh invoice with the correct Ship-To GSTIN. Plan your quality checks within the 24-hour window to catch errors early.

Is There a Grace Period After June 15, 2026?

As of GSTN Advisory No. GSTN/2026/ADV-087, there is no grace period announced. The IRP validation will enforce the mandatory Ship-To GSTIN from 00:00 hours IST on June 15, 2026. However, GSTN has historically provided a soft enforcement period for major changes (allowing warnings before hard rejections). Businesses should not rely on a grace period and must be ready by the deadline.

GSTIN Validation: Technical Rules for Ship-To Field

Every GSTIN follows a fixed 15-character structure. Your billing software must validate Ship-To GSTINs before submission to IRP. Here is the structure breakdown:

• Characters 1-2: State code (01 to 37, matching Indian state/UT codes)
• Characters 3-12: PAN of the entity (10 alphanumeric characters)
• Character 13: Entity number (1-9 for regular, Z for default)
• Character 14: Alphabet "Z" (reserved for future use)
• Character 15: Check digit (calculated using Luhn mod-36 algorithm)

When validating Ship-To GSTINs programmatically, implement these checks in sequence: verify length equals 15, confirm characters 1-2 form a valid state code, validate characters 3-12 match PAN format (5 uppercase letters + 4 digits + 1 uppercase letter), confirm character 13 is alphanumeric, verify character 14 is "Z", and compute the check digit to match character 15. This programmatic validation catches data entry errors before they reach IRP, reducing rejection rates to near zero.

Check Digit Algorithm (Luhn Mod-36)

The 15th character of every GSTIN is calculated using a modified Luhn algorithm with base 36 (digits 0-9 plus letters A-Z). To validate: take the first 14 characters, assign numeric values (0-9 for digits, 10-35 for A-Z), apply the Luhn doubling formula from right to left, compute mod 36 of the total, and subtract from 36 to get the check digit. If the computed check digit matches the 15th character, the GSTIN is structurally valid. Implementing this in your ERP's GSTIN input field eliminates manual entry errors that cause IRP rejections.

Monitoring and Post-Implementation Audit

After going live on June 15, 2026, establish a monitoring framework to catch compliance issues early:

Daily Monitoring (First 2 Weeks)

• Track IRP rejection rate: Monitor the percentage of invoices rejected by IRP due to ShipDtls errors. Target: below 2% rejection rate within the first week
• Review error logs: Categorize rejections by error code (2150-2154) to identify systemic issues versus one-off data problems
• Buyer feedback loop: Check if buyers report missing invoices in their GSTR-2B. This indicates Ship-To GSTIN routing errors
• E-way bill generation success: Verify that e-way bills auto-generate successfully from e-invoices with ShipDtls populated

Monthly Reconciliation Process

Establish a monthly reconciliation between your GSTR-1 reported invoices and IRP-accepted invoices. Any gap indicates invoices that failed IRP validation. Cross-reference with your accounts receivable to identify invoices stuck in processing due to Ship-To GSTIN errors. For the first 3 months after June 15, allocate additional staff time (2 to 3 hours weekly per 500 invoices) for reconciliation and error resolution. This investment prevents ITC disputes during quarterly filing cycles.

Quarterly Compliance Review

Every quarter, audit your customer master data for GSTIN accuracy. GSTINs can be cancelled (voluntary or suo-motu by the department), suspended, or migrated. A GSTIN that was active in June may be inactive by September. Build automated alerts using the GST portal's API to flag status changes in your customers' GSTINs. This proactive approach prevents sudden IRP rejections when a customer's GSTIN status changes without notification to your team.

Accounting Software Compatibility and Updates

Beyond ERP platforms, smaller businesses using cloud accounting software need to verify their tools support the updated schema. Here is the compatibility status of popular platforms:

If your accounting software does not yet support the mandatory Ship-To GSTIN field, contact your vendor immediately. Most vendors are releasing updates in May-June 2026 specifically for this requirement. Do not wait until June 14 to discover your software version is outdated.

Summary

The mandatory Ship-To GSTIN field enforcement from June 15, 2026 is a significant compliance change for every business generating e-invoices in India. The requirement affects all entities with aggregate turnover above ₹5 crore, demands ERP system updates, customer data cleanup, and cross-functional coordination between finance, IT, and sales teams. Start your preparation immediately: audit customer master data, collect missing GSTINs, update billing systems, test on GSTN sandbox, and train your team well before the deadline. Non-compliance results in invoice rejection, ITC denial for buyers, and penalties up to ₹10,000 or 100% of tax due under Section 122(1)(xi) of the CGST Act, 2017. For businesses needing professional support with e-invoice compliance setup or GST return filing, expert assistance can accelerate your readiness and reduce compliance risks significantly.