HSN codes look like a minor formatting detail until an HSN summary mismatch holds up a GSTR-1 filing, or a wrong code puts the incorrect GST rate on an entire month of invoices. The rules on HSN code on invoices are tied directly to your aggregate turnover, and they apply differently to small businesses, mid-size sellers, and larger enterprises. This guide covers how the digit requirement scales, where the code must appear, and how it flows through into your return.
What HSN and SAC codes are
HSN (Harmonised System of Nomenclature) codes classify goods, and SAC (Services Accounting Code) classifies services, both under an internationally recognised numbering system adapted for GST. Every taxable supply on an invoice needs to carry the relevant code, because the code, not just the product description, is what ties the item to its applicable GST rate and feeds the HSN-wise summary in your GSTR-1.
The digit requirement scales with turnover
GST rules do not require every business to quote the same number of HSN digits. Smaller taxpayers are generally permitted to quote fewer digits, while businesses above higher turnover slabs are required to quote more, up to the full code length for larger enterprises and for specified categories such as imports and exports, which typically need the full code regardless of turnover. Because these turnover slabs and digit requirements have been revised in past notifications, do not rely on a remembered number, confirm your applicable digit requirement on the GST portal or with your GST practitioner based on your current aggregate turnover. A business that grows across a turnover slab mid-year should revisit its HSN digit length at that point rather than waiting for the next audit or notice to catch the gap.
| Business profile (illustrative, verify current slabs) | General direction |
|---|---|
| Smaller taxpayers | Fewer digits typically required, or codes may be optional in narrow cases |
| Mid-turnover taxpayers | A moderate digit length is typically required |
| Larger taxpayers | A longer, more granular code is typically required |
| Imports/exports, regardless of turnover | Full HSN code length is typically required |
Where the code needs to appear
- Against every line item on the tax invoice, not just as a summary at the bottom.
- Consistently for the same product across invoices, so the same item is not classified under two different codes in different months.
- On bills of supply as well, for identification, even though no tax is charged on those documents.
- In the HSN summary table when preparing GSTR-1, which aggregates quantity, value, and tax by HSN code across the return period.
How it flows into your GSTR-1 HSN summary
GSTR-1 includes a dedicated HSN-wise summary table that totals the quantity, taxable value, and tax amount for each HSN/SAC code used during the period. This table is built directly from what is on your invoices, so an inconsistent or missing code at the invoice stage becomes a validation warning or an inaccurate summary at the filing stage. Reviewers and, on occasion, tax officers use this summary to spot-check whether the tax rate applied matches the classification declared. A clean HSN summary also makes your own internal reporting more useful, since it lets you see which product categories actually drive turnover and tax liability without re-deriving that from raw invoice data every time.
Mistakes that are more common than they should be
- Using a shorter code than your turnover requires. This can trigger validation warnings when preparing the return.
- Splitting the same product across two codes because different staff members classified it differently over time.
- Copying a competitor's code without checking it matches your product's actual classification and applicable rate.
- Leaving the code blank on service invoices because SAC feels less familiar than HSN, when it is equally mandatory.
- Not updating codes after a rate notification that reclassifies a product category.
One product, one code, even across marketplaces
Sellers who list the same product on their own site and across Amazon, Flipkart, Meesho, or other marketplaces sometimes end up with different HSN codes for the same SKU, because each channel's catalogue tool suggests its own classification. This is a real problem at GSTR-1 time: when sales from multiple channels are consolidated into one HSN summary, the same physical product showing up under two codes splits the reported quantity and value in a way that does not reflect what actually happened, and can trigger a validation warning. The fix is to treat the HSN/SAC code as a property of the product, decided once, and to override whatever code a marketplace report suggests if it does not match your own master.
HSN code versus product description: which one governs
When there is a conflict between how an item is described in words and the HSN code quoted against it, the code is what determines the applicable GST rate for return and audit purposes, not the free-text description. A vague or generic description paired with a specific, correct HSN code is far safer than a detailed description paired with the wrong code. This is why it is worth periodically spot-checking a sample of invoices against your product master, particularly after any GST rate notification that reclassifies a category you sell in.
Finding and standardising the right code
The safest approach is to fix the correct HSN/SAC code once per product or service line, store it against that item, and reuse it on every invoice rather than typing it fresh each time. This is particularly important for sellers with large catalogues across marketplaces, where the same SKU can otherwise pick up inconsistent codes depending on which channel report it was pulled from. OneBooks GST's inventory software (on our roadmap) is intended to let you attach an HSN/SAC code once at the item-master level so it stays consistent across every sale; today, our accounting software and GSTR-1 automation already carry HSN codes through from invoice entry into the HSN summary table, reducing the risk of a code drifting between the invoice and the return. For a closer look at applying codes consistently across stock items rather than just invoices, see HSN/SAC codes for inventory, and for the rest of the mandatory invoice fields, see GST invoice format and mandatory fields.
A Worked Example: The Cost of a Wrong Code
Suppose a seller lists ceramic tableware under an HSN code that attracts 12% GST, when the correct classification for that specific product actually attracts 18%. Across a month with 200 invoices averaging ₹5,000 in taxable value each (₹10,00,000 in total taxable value), the seller has been charging and reporting ₹1,20,000 in output tax, when the correct liability was ₹1,80,000 — a ₹60,000 shortfall built up from what looked like one small classification choice. Once discovered, the code typically needs correcting immediately going forward, with the shortfall for past periods addressed through the applicable correction route, and interest may apply on the underpaid amount for the intervening period. The scale of the numbers is what makes a small HSN mistake worth catching early rather than after several filing cycles.
Sector Notes: Where Classification Gets Genuinely Difficult
- Manufacturing with near-identical SKUs. Product variants that differ only in size, material grade, or finish can legitimately fall under different HSN codes; treating an entire product line as one code because the items look similar is a common source of under- or over-classification.
- Textile and apparel. Classification has historically depended on factors like value per unit and fabric composition, which makes it one of the categories worth double-checking after any GST rate notification rather than assuming last year's code still applies.
- Composite supplies. When a single supply bundles a principal item with incidental goods or services (for example, a product sold with mandatory installation), the HSN/SAC of the principal supply generally governs the whole transaction rather than splitting the invoice by component — worth confirming for anything you sell as a bundle.
Digit Length in Practice: A Quick Reference
| Scenario | Practical note |
|---|---|
| Domestic B2B invoice, mid-size business | Use the digit length applicable to your turnover slab consistently across every invoice |
| Domestic B2C invoice | Same digit-length rule generally applies, based on your own turnover, not the buyer's |
| Import/export documentation | Full HSN code length is typically required regardless of turnover |
| Product with more than one plausible code | Pick the code matching the item's primary characteristic and use it consistently; document the reasoning if the classification is genuinely borderline |
Frequently asked questions
Do all businesses need to quote HSN codes on invoices?
Most GST-registered businesses need to, though the required number of digits depends on aggregate turnover. Confirm your specific requirement on the GST portal, since thresholds have changed over time.
Is the HSN code requirement different for services?
Services use SAC codes under the same general framework, with a similar turnover-linked digit requirement, so the same discipline around consistency applies.
What happens if I use the wrong HSN code?
It can result in the wrong GST rate being applied, mismatches in your HSN summary during GSTR-1 preparation, and potential scrutiny if the misclassification affects the tax paid.
Do I need HSN codes on a bill of supply?
Generally yes, for identifying the goods or services, even though no tax is charged or shown on a bill of supply.
Can HSN digit requirements change for my business over time?
Yes. As your aggregate turnover crosses different slabs, or as GST notifications revise the applicable thresholds, the number of digits you are required to quote can change, so it is worth rechecking periodically.
What should I do if I realize I have been using the wrong HSN code for months?
Correct the code in your product master immediately so future invoices use the right classification, and address the tax impact for past periods through the applicable correction route. If the shortfall is material, consult a GST practitioner before deciding how to handle the back periods.
How OneBooks GST fits into this
In practice, OneBooks GST creates GST invoices with template and PDF output, and carries those invoices through into GSTR-1 preparation.
Keeping the original source file, the reviewed working copy and the final export together is what makes the same check repeatable next period, and OneBooks GST stores them against the filing period.
