Complete HSN Code List for FY 2025-26 with GST Rates

Chapter-wise HSN coverage for FY 2025-26, GST slabs, and practical compliance steps for invoice-ready classification.

What is the HSN Code System?

HSN is the harmonized product language used for tax and trade classification. In India, GST compliance depends heavily on proper HSN mapping because rates, invoice disclosure, and return summaries are tied to product coding. A correct code shortens audit conversations and reduces disputes on rate applicability. A wrong code can affect hundreds of invoices before being noticed.

For example, laptops generally align with HSN 8471, telecom devices often align with HSN 8517, and printed books commonly align with HSN 4901. These references are useful starting points, but teams should still verify chapter notes and exclusion notes before finalizing classification.

HSN Code Structure - 2, 4, 6 and 8 Digits Explained

The first 2 digits indicate chapter, 4 digits indicate heading, and 6 digits indicate internationally recognized subheading. 8-digit extension is usually required in customs and ITC-HS contexts. Businesses should maintain classification depth beyond minimum legal disclosure so future changes do not require remapping the entire master.

In practical implementation, finance teams should decide one internal standard and use it consistently across e-invoice, ERP, and return extraction. Consistency is more valuable than ad hoc detail. High-volume categories such as HSN 3004, HSN 2523, and HSN 8703 should have documented approval notes.

HSN Code List by Chapter (link each chapter)

Chapter browsing gives a strong starting framework. Machinery and computers begin around Chapter 84, electrical goods and telecom around Chapter 85, and vehicles around Chapter 87. Textiles often split across Chapter 61 and Chapter 62. Pharmaceuticals usually start from Chapter 30.

When teams rely only on keyword search, they often miss chapter context. A chapter-first review helps identify nearby codes and legal notes that impact final classification. This is especially useful for products with similar names but different treatment.

How to Download the Official HSN Code PDF

Use CBIC and related official notifications as your source of legal truth. Keep archived versions internally with effective date labels and compare changes before updating ERP masters. Do not replace code mappings in production without approval logs because traceability matters during scrutiny.

For internal use, create a controlled spreadsheet that stores HSN code, description, GST rate, date verified, and verifier. This gives billing and tax teams a shared reference and prevents random code edits.

Recent Changes in HSN Codes for 2025-26

Most practical changes for FY 2025-26 are process changes, not dramatic code system changes. Businesses need better governance on product master updates, notification tracking, and category-level reviews. Errors often come from stale SKU descriptions, duplicate items, and inconsistent naming across marketplaces and ERP.

For electronics and apparel catalogs, monthly top-SKU review is recommended. Validate mapped codes such as HSN 8528 for TVs, HSN 8415 for ACs, and HSN 6109 for t-shirts against current notification logic.

How to Find Any HSN Code Instantly

Use a three-step workflow: search by product term, review chapter candidates, and validate rate context. Finalize only after reading description fit and legal note fit. If uncertain, mark as pending-review and involve a CA before bulk invoicing. This prevents expensive rework after filing cycles close.

Build an internal shortlist of top products with approved mappings, including references like HSN 8471, HSN 8517, HSN 3004, and HSN 2523. This makes daily billing faster and keeps teams aligned.

Practical Compliance Workflow for the FY 2025-26 HSN list

A strong production workflow begins with source control for tax logic. Keep one approved HSN/SAC master, version every change, and include approver name, date, and legal reference. Without this, teams silently overwrite mappings and later fail to explain why one SKU changed rate in a specific month. This single control has the highest impact on audit readiness and protects both finance and operations from repeated correction cycles.

Next, align catalog language with billing language. Product naming in e-commerce or sales CRM is often marketing-led, while invoice naming needs legal precision. Build a mapping layer so teams can search with commercial terms but bill with compliant descriptions. This is especially useful for large catalogs where one family has multiple variants, bundles, accessories, and promotional kits.

Then implement monthly exception checks. Review top-revenue SKUs, top-returned SKUs, and recently added SKUs. Compare code, GST slab, and chapter against prior month and flag all mismatches. Most practical errors are operational drift, not legal complexity. Early detection avoids expensive re-issuance effort and protects return filing timelines.

For internal controls, use maker-checker approval on all tax-master updates. The person creating mapping should not be the final approver. Keep review notes short but explicit: product type, chapter rationale, exclusions considered, and decision date. This gives enough context for future teams and prevents dependency on one individual's memory.

Finally, maintain a quarterly legal review rhythm. Even if the majority of items remain stable, periodic checks reduce confidence risk and catch edge cases before they become departmental issues. If your business operates high-volume categories, store code-level evidence for those top items and review after major notification cycles.

This disciplined approach turns classification from reactive firefighting into predictable operations. Teams invoice faster, reconcile faster, and respond to scrutiny with documented reasoning instead of manual reconstruction. For production-grade compliance programs, process quality is the durable advantage.