Mandatory Reporting of HSN Code

Mandatory Reporting of HSN Code in GSTR-1: A Practical Guide for FY 2026-27

Every taxable supplier in India must tag each supply with a correct HSN (Harmonized System of Nomenclature) code or SAC (Service Accounting Code) and summarise that data in Table 12 of GSTR-1. For FY 2026-27, the rule is straightforward: aggregate turnover up to ₹5 crore in the preceding financial year requires 4-digit HSN for B2B supplies; above ₹5 crore requires 6-digit HSN for all supplies. A wrong code is not a clerical footnote — it can flip the applicable tax rate, deny your buyer's ITC claim, and put you squarely in the line of a demand notice under Section 73 or 74 of the CGST Act 2017.

What HSN Is — and Why the Code Controls Your Tax Rate

The Harmonized System of Nomenclature is a globally standardised commodity classification maintained by the World Customs Organization (WCO). India uses the HSN architecture as the foundation of its GST rate schedule. The structure works in layers:

• 2-digit Chapter — broad product category (e.g., Chapter 62: articles of apparel)
• 4-digit Heading — narrower product group (e.g., 6203: men's suits, ensembles)
• 6-digit Sub-heading — specific product variant (e.g., 6203 42: trousers and shorts, of cotton)
• 8-digit Tariff item — India's extended classification for customs and detailed indirect tax administration

The critical point: each HSN sub-heading or tariff item maps directly to a GST rate entry in one of the rate schedules notified under the CGST Act. When you report HSN 6203 42 in your GSTR-1, the GST department's system cross-references the rate for that code. If you have reported and collected 5% but the correct rate for the code is 12%, you have an underpayment — even if you genuinely believed 5% was right.

This is why HSN is never a back-office formality. The code you assign to a product at the master-table level determines what rate your billing software applies to every invoice for that product.

HSN for Goods, SAC for Services — and Why the Distinction Matters

Goods use HSN codes. Services use SAC codes, which are India's domestic classification maintained by CBIC and aligned (though not identical) to the WCO's Central Product Classification.

SAC codes are 6-digit. For example:

• 998311 — Management consulting services
• 998314 — Information technology (IT) design and development services
• 996331 — Restaurant services with liquor licence
• 996334 — Outdoor catering services

Why does the distinction matter in practice? Because many businesses supply both goods and services, and an ERP that is not configured to distinguish the two at the line-item level will attempt to apply an HSN to a service or vice versa. The GST portal's validation engine now checks the structure of the code against its master list — it will reject returns where a goods HSN (which starts with the relevant chapter number) is applied to a service line that should carry a SAC.

For service businesses, the SAC also has direct rate implications. Management consultancy services (SAC 998311) attract 18% GST. Certain advisory services to the government may attract different rates. Using a generic or incorrect SAC shifts your rate — and your recipient's ITC eligibility — without any obvious warning at invoice generation.

HSN Reporting Thresholds in GSTR-1 for FY 2026-27

The current mandatory HSN reporting framework was notified under Notification No. 78/2020 – Central Tax dated 15 October 2020, operative from 1 April 2021. For FY 2026-27 (AY 2027-28), the same threshold structure applies:

"Aggregate turnover" here means your combined turnover across all registrations under the same PAN, computed as defined in Section 2(6) of the CGST Act — not just the turnover of one GSTIN.

A manufacturer with multiple GSTINs across states must aggregate all of them to determine the threshold, even if each individual registration has turnover below ₹5 crore.

For QRMP (Quarterly Return Monthly Payment) scheme filers: The HSN summary is required in the quarterly GSTR-1, not in the monthly IFF (Invoice Furnishing Facility). The IFF is limited to B2B invoice details and does not carry a Table 12 requirement. If you are on QRMP and file IFF for Month 1 and Month 2, ensure your cumulative HSN-wise totals are correctly aggregated into Table 12 when the quarterly GSTR-1 is filed.

Table 12 of GSTR-1: Structure and How to Fill It Correctly

Table 12 is the HSN-wise summary of outward supplies in GSTR-1. It is a consolidated table — you do not replicate invoice-level data here. Instead, you aggregate all invoices for the period under each unique HSN/SAC code and report a single row per code.

Each row in Table 12 requires:

1. HSN/SAC — the applicable 4-digit, 6-digit, or 8-digit code
2. Description — a brief description of the goods or services (free text, but must be accurate and consistent with the code)
3. UQC (Unit Quantity Code) — the official unit from CBIC's UQC list. Common codes include: NOS (numbers), KGS (kilograms), MTR (metres), LTR (litres), SQM (square metres), PRS (pairs), SET (sets), OTH (others)
4. Total Quantity — aggregate quantity of all supplies under this HSN for the tax period
5. Total Value — gross invoice value
6. Taxable Value — value net of discount, on which tax is computed
7. IGST amount, CGST amount, SGST/UTGST amount, and Cess — tax breakup

Two common filing mistakes in Table 12:

• Using OTH as the UQC for every product, irrespective of the actual unit of measure. This defeats the purpose of quantity analytics and can create mismatches when the department cross-references with e-way bill data (which captures weight and dimensions).
• Leaving the Description field generic ("goods" or "services") rather than matching the description that corresponds to the HSN entry in the rate schedule. An audit officer comparing your return to the rate notification will immediately notice the mismatch.

The data you enter in Table 12 must reconcile with the invoice-level data in Tables 4, 5, 6, 7, 8, and 9 of the same GSTR-1. The taxable value and tax in Table 12 should equal the sum of all invoice values under that HSN across the other tables. The GSTN system does not currently enforce a hard block on this reconciliation, but your internal reconciliation process must catch discrepancies before filing — because GSTR-9 (the annual return) will expose them.

Worked Example: The Cost of Getting HSN Wrong

Scenario: A footwear trader in Pune has an aggregate turnover of ₹9.5 crore in FY 2025-26 and is therefore required to report 6-digit HSN for all supplies in FY 2026-27.

The business sells leather footwear with MRP above ₹1,000 per pair, correctly classified under HSN 6403 59 10, which attracts 18% GST.

Due to an ERP configuration error, the billing team has been using HSN 6402 19 10 (rubber/plastic footwear, value ≤ ₹1,000) for all footwear invoices — a code that attracts 5% GST.

Over April–September 2026 (six months), the taxable value of footwear supplied is ₹60 lakh.

Interest on short payment (Section 50 of CGST Act): At 18% per annum, for 200 days: ₹7,80,000 × 18% × (200 ÷ 365) = ₹77,096 (approx.)

Penalty under Section 73 (non-fraud demand): 10% of tax or ₹10,000, whichever is higher: 10% of ₹7,80,000 = ₹78,000

Total exposure: ₹7,80,000 + ₹77,096 + ₹78,000 = ₹9,35,096

And this is the conservative scenario — where the department accepts it as a genuine error under Section 73. If the officer concludes the mismatch was deliberate (suppression of turnover at the higher rate), Section 74 applies and the penalty rises to 100% of the tax amount, making the total exposure well above ₹16 lakh.

The footwear trader also faces a practical problem: every buyer who claimed ITC at 5% (₹3 lakh) will face a partial ITC reversal demand for the differential, because the correct ITC they were entitled to was ₹10.8 lakh — but at the correct rate, not the rate on the incorrect invoice.

Common Mistakes and How to Fix Them

1. Using 4-digit HSN when 6-digit is mandatory Triggered when turnover crosses ₹5 crore but ERP master is not updated. Fix: Set up an automated alert in your billing system when trailing-twelve-month turnover crosses ₹4.5 crore, giving you time to update the master before the new financial year.

2. Inconsistent HSN across tax periods for the same product HSN 8471 in April, HSN 8473 in June for the identical SKU — this flags a risk-based audit selection. Fix: Lock HSN at the SKU level and require a documented approval workflow (with effective date) to change it.

3. Using the customs 8-digit tariff code in GSTR-1 when only 6-digit is required An importer accustomed to 8-digit customs classification carries that habit into GSTR-1. The portal may accept it, but it creates downstream reconciliation issues. Fix: Maintain separate columns in your product master for "Customs Tariff Code" and "GST HSN" with validation rules.

4. Applying a goods HSN to a composite supply that is predominantly a service A software company sells an annual maintenance contract. If the invoice carries HSN 8523 (storage media) instead of SAC 998314 (software services), the rate and ITC character of the supply change. Fix: Classify composite supplies under the "principal supply" rule (Section 8 of the CGST Act) and document the classification rationale.

5. Reporting SAC at 4-digit level when 6-digit is mandatory SAC codes are inherently 6-digit — there is no 4-digit SAC equivalent. A service provider above ₹5 crore turnover who reports SAC at 4 digits is technically in breach. Some portals accept the shorter form, but GSTR-9 reconciliation will surface the gap. Fix: Train your accounts team that for services, 6-digit SAC is always required regardless of which turnover bracket you fall in.

6. Leaving Table 12 blank or partially filled Some taxpayers fill invoice-level details in Tables 4-9 and skip Table 12 entirely, assuming it is auto-populated. It is not auto-populated from invoice data. Fix: Build Table 12 population into your monthly return preparation checklist as a mandatory, signed-off step.

Penalties for Incorrect HSN Reporting

The CGST Act provides a layered penalty framework that applies to HSN non-compliance:

Section 125 — General Penalty: Where the Act prescribes no specific penalty for a contravention, Section 125 applies — up to ₹25,000 per contravention. Reporting the wrong HSN code or digit-length is a contravention of Rule 59 read with the HSN notification. Each return period with wrong HSN can be treated as a separate contravention.

Section 73 — Demand without fraud: Where wrong HSN leads to short payment of tax (as in the footwear example above), a demand is raised under Section 73 — tax + interest + penalty up to 10% of tax. The demand window is three years from the due date of the annual return for the relevant financial year.

Section 74 — Demand with fraud / suppression: If the officer concludes the wrong HSN was used deliberately to suppress tax liability, Section 74 applies — tax + interest + penalty up to 100% of tax. The demand window extends to five years.

Practical risk beyond statutory penalties: The GSTN risk-scoring system uses HSN-wise data to identify taxpayers with inconsistent classification patterns. A high risk score from repeated HSN errors increases the probability of comprehensive GST audit under Section 65, which is far more intrusive and time-consuming than responding to a notice under Section 73.

Building HSN Discipline: Master Table, ERP Lock, and Vendor Onboarding

The root cause of almost every HSN error is a weak product master or a billing system that allows overrides. Here is a step-by-step approach to eliminate both:

Step 1 — Build a Centralised HSN/SAC Master Table Create a master with columns: SKU/Service Code, Description, HSN/SAC (6-digit), GST Rate, UQC, Effective Date, and the CBIC notification reference that supports the classification. Assign ownership of this master to your head of finance or a designated tax analyst.

Step 2 — Lock HSN at the SKU Level in Your ERP The HSN field on an invoice line should be auto-populated from the SKU master and non-editable by the sales or accounts team. If your ERP allows invoice-level HSN override, disable that permission for all roles except the tax administrator.

Step 3 — Build a Change-Control Workflow Any change to an HSN in the master table requires: (a) a written request with the rationale and CBIC circular/notification reference, (b) approval by the designated tax analyst or CFO, and (c) an effective date that is not backdated. Prior-period invoices must remain unaffected by the new mapping.

Step 4 — Vendor Onboarding Checklist When onboarding a new product category sourced from a vendor, require the vendor to declare the HSN in their purchase order and invoice. Cross-reference it against the CBIC HSN master before adding to your product catalogue. Do not default to the vendor's stated HSN blindly — your GST liability is your own.

Step 5 — Subscribe to CBIC Rate-Rationalisation Notifications The GST Council periodically revises rates and moves products between HSN headings or rate schedules. After each Council meeting, reconcile your product master against the notification. Implement changes with a precise effective date — products invoiced before the date of change remain under the old rate.

Quarterly Reconciliation and the GSTR-9 Link

Table 12 of your monthly or quarterly GSTR-1 feeds directly into Table 17 of GSTR-9, the annual return. Table 17 requires you to declare HSN-wise summary of outward supplies for the entire financial year. If your monthly GSTR-1 Table 12 entries are inconsistent — different HSNs for the same product, missing entries, or UQC changes mid-year — Table 17 in GSTR-9 will reflect all those inconsistencies in aggregated form, making the annual return difficult to certify.

Practical quarterly reconciliation steps:

1. Export HSN-wise sales register from your ERP for the quarter
2. Extract Table 12 data from the filed GSTR-1 returns for the same quarter
3. Match taxable value and tax amounts, HSN code by HSN code
4. Investigate any variance above ₹1,000 per HSN — document the cause
5. If there is an error in a filed GSTR-1, use the GSTR-1A amendment for the relevant month/quarter to correct it before the due date of the annual return

Do not wait until March to do this. Errors discovered in March require retroactive amendments across multiple months — a far more time-consuming process than catching and correcting one month's error in the month immediately following.

Key Takeaways

• Threshold for FY 2026-27: Turnover up to ₹5 crore in the preceding year = 4-digit HSN for B2B; above ₹5 crore = 6-digit HSN for all supplies (B2B and B2C).
• Table 12 of GSTR-1 is not auto-populated — it must be deliberately prepared as an HSN-wise aggregate of all outward supplies for the period; blank or partial Table 12 is a compliance failure.
• The UQC matters — using OTH for every product undermines your quantity audit trail; use the correct CBIC-prescribed unit for each product.
• Wrong HSN = wrong rate = Section 73/74 demand — the footwear example above shows how a six-month coding error can create a ₹9+ lakh exposure when interest and penalty are included.
• Section 125 general penalty of up to ₹25,000 applies per return period where HSN digit-level obligations are not met — a ₹1.5 lakh exposure across a six-month period is entirely avoidable.
• Lock HSN at SKU level in your ERP and build an approval workflow for any master-table change — this one control eliminates the vast majority of classification inconsistencies.
• Reconcile Table 12 with books quarterly and carry that discipline forward into GSTR-9 Table 17 — annual return preparation becomes a sign-off, not a fire drill.