Introduction to the New GST Guidelines for Bill-to/Ship-to Transactions
In a significant move to enhance the audit trail and traceability of goods movement across India, the Goods and Services Tax Network (GSTN) has issued a detailed set of FAQs on 01.07.2026. These guidelines address the treatment of 'Ship-to GSTIN' in complex business models, including Bill-to/Ship-to, Bill-from/Dispatch-from, and Combination transactions. The revised date for the production implementation of these changes is set for 1st August, 2026. Compliance Katta brings you this deep dive to ensure your business and ERP systems are fully aligned with the new requirements.
The Core Objective: Mandatory Ship-to GSTIN
The primary shift introduced by these FAQs is the mandatory requirement to capture the Ship-to GSTIN whenever the Ship-to party is a registered person. For supplies made to unregistered persons, the system allows the entry of 'URP' (Unregistered Person). The objective is to strengthen the system-based verification processes for authorized officers while ensuring that the actual destination of goods is documented accurately within the digital ecosystem.
Key Highlights of the GSTN FAQ Release
- Mandatory Requirement: Ship-to GSTIN is now compulsory for 'Ship-to' and 'Combination' transaction types.
- Implementation Timeline: Changes will be live on production from 1st August, 2026, with sandbox testing already available.
- Trade Secrecy: To protect commercially sensitive information, the Ship-to GSTIN will not be printed on the E-Way Bill PDF nor provided through GET EWB APIs.
- System Validations: Strict API-level validations have been introduced to prevent errors in transaction categorization.
Comparative Analysis of Business Transaction Types
Understanding how the GST portal differentiates between various supply models is crucial for correct data entry. Compliance Katta has summarized the business scenarios as follows:
| Sl. No. | Transaction Type | Billing Flow | Movement of Goods | Ship-to GSTIN Treatment |
|---|---|---|---|---|
| 1 | Regular | Supplier to Buyer | Supplier to Buyer | Not Applicable |
| 2 | Bill-to/Ship-to | Supplier to Buyer | Supplier to 3rd Party | Mandatory (Registered or URP) |
| 3 | Bill-from/Dispatch-from | Supplier to Buyer | 3rd Party to Buyer | Not Required |
| 4 | Combination | Supplier to Buyer | 3rd Party to 4th Party | Mandatory (Registered or URP) |
Expert Advice from Compliance Katta: In a Bill-to/Ship-to transaction, the system expects the Bill-to and Ship-to parties to be distinct. Entering the same GSTIN in both fields will trigger Error Code 618 in the EWB API. For deliveries to your own additional place of business, use the 'Regular' transaction type and specify the delivery address in the Bill-to address field.
Export and Merchant Exporter Scenarios
Export movements often involve logistical hubs like ports or ICDs. The new FAQs clarify how these should be handled to avoid compliance friction:
- Export Bill-to/Ship-to: When billing an overseas buyer but shipping to an Indian port, airport, or CFS, the Ship-to GSTIN should be entered as 'URP' if no domestic registered entity is involved as the consignee.
- Address and PIN Code: For exports, the actual Indian destination address (e.g., the Port or Warehouse) and its corresponding PIN code must be provided.
- Nature of Transaction: Using 'URP' for export-linked movements does not convert an export into a domestic supply; the transaction's nature continues to be determined by the shipping bill and export invoice.
API Impact and System Readiness
For ERP vendors, GSPs, and ASPs, the technical changes are extensive. Compliance Katta highlights the specific API validation codes that must be handled:
1. Standalone E-Way Bill API Changes
- Error Code 608: Triggered if Ship-to GSTIN is missing in Ship-to/Combination transactions.
- Error Code 616: Triggered if Ship-to GSTIN is provided in a Regular transaction.
- Error Code 864: Triggered if Ship-to GSTIN is provided in a Bill-from/Dispatch-from transaction.
2. E-Invoice (IRN + EWB) Flow
In the combined generation flow, the field ShipDtls.Gstin becomes conditionally mandatory. If the ship-to details are provided, the system will validate that the State Code in the GSTIN matches the Ship-to State Code (Error 2325) and that the PIN code is valid for that state (Error 3039).
Compliance Readiness Checklist
To ensure a smooth transition by August 2026, follow this roadmap provided by Compliance Katta:
- Master Data Update: Identify and map GSTINs of all third-party Ship-to locations in your ERP.
- API Testing: ERP and GSP teams must complete testing in the Sandbox environment to handle new mandatory fields and error codes.
- Confidentiality Strategy: If a buyer does not wish to share the final customer's GSTIN with the supplier, the buyer should take responsibility for generating the E-Way Bill as an 'Inward' supply.
- Transporter Coordination: Inform transporters that while they can generate EWBs, they must receive accurate Ship-to GSTIN data from the taxpayer if the taxpayer isn't generating it.
- Validation Checks: Implement pre-submission checks to ensure the Ship-to GSTIN state code matches the PIN code.
Conclusion
The updated FAQ on Bill-to/Ship-to transactions marks a move toward higher transparency in logistics. While the administrative burden of capturing an additional GSTIN might seem high, the protection of trade secrecy through non-printing of these details balances the needs of the industry with the requirements of tax authorities. Stay ahead of the curve by updating your systems before the August 1st deadline. Compliance Katta - Your Compliance Partner is here to assist you in every step of this digital transformation.
Common Questions
Q.Why is the Ship-to GSTIN being captured if it is not printed on the E-Way Bill?
The Ship-to GSTIN is captured for official audit purposes to improve the traceability of goods and strengthen the audit trail in complex transactions. While it is hidden from taxpayers and transporters to protect trade secrecy, it remains visible to authorized officers for verification and enforcement during inspections.
Q.Can I use the same GSTIN for both 'Bill-to' and 'Ship-to' in a Bill-to/Ship-to transaction?
No, the system will reject such an entry with Error Code 618 or 2323. In a Bill-to/Ship-to transaction, the parties are expected to be distinct; if you are shipping to your own registered warehouse, you should select the 'Regular' transaction type instead and update the delivery address fields accordingly.
Q.What should be entered as the Ship-to GSTIN for export transactions moving to a port?
For export transactions involving Bill-to/Ship-to scenarios where goods move to a port, ICD, or airport, the Ship-to GSTIN should be entered as 'URP' (Unregistered Person). You must then provide the actual destination address and PIN code of the export-linked location in India.
Q.What happens if my buyer refuses to share the Ship-to GSTIN due to business confidentiality?
If the buyer chooses not to disclose the final consignee's GSTIN to the supplier, the buyer can generate the E-Way Bill themselves in the system. By generating the E-Way Bill as an 'Inward' supply, the buyer can maintain their customer's confidentiality while still complying with the mandatory data requirements.
Q.Is the implementation of these API changes mandatory for E-Invoice users?
Yes, the requirement extends to all IRN-related flows, including 'Generate IRN and EWB Together' and 'E-Way Bill by IRN'. The field 'ShipDtls.Gstin' becomes conditionally mandatory if ship-to details are provided, and users must ensure their E-Invoicing systems are updated to include this field by 1st August 2026.