This discussion addresses common issues with entering HSN details for export sales in GSTR1. It clarifies that export sales are consolidated within their respective HSN rows in Table 12, without a separate 'Export' checkbox. Modifying auto-populated rows for shipping bill details will remove the visible IRN tag but is valid if saved successfully. It also touches on discrepancies between HSNs entered on export invoices versus shipping bills.
Exports Sales details entered in Table 6A and HSN Details entered in Table 12 But I have received message HSN wise total B2B Value not matching , I am having doubt in Table 12 Particularly no option to select export.
One more doubt after preparing e invoice automatically showing details in GSTR1 Table 6A except shipping bill number date port code , this reason I had edited and entered shipping bill details and saving , einvoice IR Number not showing after that,
Please guide and explain above doubts how to solve
09 July 2026
Consolidate export values within their respective HSN rows in Table 12; there is no separate "Export" checkbox.
Modifying an auto-populated row to add shipping bill details naturally removes the visible IRN tag on the portal screen. If saved successfully, it is perfectly valid for filing.
10 July 2026
Sir, Thank you for your reply, it is helpful to me I am having one more doubt in exports some time we are entered hsn in export invoice is not opening in shipping bill preparation they are entered different HSN as per shipping bill same HSN entering into GSTR1
03 November 2026
To add to the discussion regarding HSN discrepancies:
Primary Source for GSTR-1 & E-way Bill: Always ensure that the HSN code reported in your GSTR-1 (both Table 6A and Table 12) matches the HSN code declared on the Tax Invoice / E-invoice, as GST returns map directly from your outward supply documents.
Customs vs. GST Alignment: Shipping bills are filed via ICEGATE for customs purposes under the Customs Tariff Act, whereas GSTR-1 is governed by the GST Act. While both generally use 6-digit or 8-digit Harmonized System nomenclature, minor discrepancies can occasionally arise due to classification interpretations at the port or system mappings.
Recommended Practice:
If the discrepancy is minor and already processed by customs, reconcile your internal books and ensure that future export invoices align more closely with the intended Custom House Agent (CHA) / shipping bill entries where legally permissible.
For past filed returns where an HSN mismatch exists, keep a proper reconciliation statement internally to defend against any future departmental notices or refund processing queries (since GST refunds on exports via Table 6A are validated against ICEGATE data).