The classification codes that decide your GST rate — and the most common reason an e-invoice is rejected.
HSN (Harmonised System of Nomenclature) codes classify goods; SAC (Services Accounting Code) codes classify services. Under GST they determine the applicable tax rate and must appear on tax invoices. The number of digits required depends on your aggregate annual turnover, and the code must be correct at the line level rather than assumed at the item group.
Classification is treated as a master-data chore and then causes problems everywhere downstream. The code sets the rate, so an incorrect one produces an incorrect tax amount, which produces a return mismatch, which produces a customer whose input tax credit does not reconcile. It is also validated at the Invoice Registration Portal, so errors surface as rejections at the point of invoicing.
The code belongs on the item master, set when the item is created and reviewed by someone who understands the product, not defaulted.
Smaller taxpayers report fewer digits; larger ones report more. Confirm the current requirement for your turnover band.
The GST rate should derive from the classification rather than being entered independently, so the two cannot disagree.
Run the full item master through validation before the first e-invoice, not after the first rejection.
Rate notifications and reclassifications happen. A periodic review against the current schedule is cheaper than a reassessment.
A business sells an industrial fitting. Two people in the company have classified it over the years: one by what it is made of, one by what it does. The item master ends up with two codes carrying different rates, and both have been used on invoices.
The consequences compound in three directions. Customers receive invoices with inconsistent tax treatment for the same product, which generates queries and credit notes. Returns carry a mix that does not reconcile cleanly against sales. And if the lower-rated classification turns out to be the wrong one, the exposure is the differential on every unit sold under it, plus interest, across the whole period — not just going forward.
The preventable part is the duplicate. One item should carry one code, maintained centrally and not editable at invoice entry. Where genuine ambiguity exists — and for many engineered goods it does — the answer is to document the reasoning for the code chosen and keep it with the item record. A documented, consistently applied position is defensible. An undocumented inconsistency is the thing that attracts attention in the first place.
| Term | What it means |
|---|---|
| HSN | Harmonised System of Nomenclature — the international classification for goods, used to determine rate and reporting. |
| SAC | Services Accounting Code, the equivalent classification for services. |
| Digit level | How many digits you must report, which depends on turnover. More digits means a narrower, more specific classification. |
| Chapter and heading | The hierarchical levels of HSN. The first two digits are the chapter, the next two the heading, and so on. |
| Classification dispute | A disagreement about which code applies. Usually about function versus material, and usually expensive. |
Classification is specific. A nearly-right code produces a confidently wrong rate.
Groups contain items that classify differently. The code belongs on the item.
Businesses that mainly sell goods often leave service lines — freight, installation — unclassified.
Classification drifts unless somebody is accountable for it. Assign the responsibility explicitly.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Items with missing or short codes | Direct e-invoicing and return rejection risk, item by item. | Counting blanks only, which misses codes with too few digits for your slab. |
| Duplicate codes for similar items | Classification drift, usually caused by codes being set at entry rather than centrally. | Comparing codes without comparing descriptions, so genuine differences look like drift. |
| Rate mismatches against the master | Invoices carrying a rate that disagrees with the item's classification. | Checking only current invoices rather than the back catalogue where exposure sits. |
| Classification change frequency | How often codes are edited. Frequent edits suggest nobody owns the decision. | Bulk corrections recorded as many individual changes. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.