Skip to main content
Symptom · 5 min read

Why Does the HSN Summary in My GSTR-1 Not Match My Sales Report?

The HSN summary in Table 12 of GSTR-1 totals sales by HSN or SAC code, unit and value. It drifts from the sales report when credit notes are netted differently, units differ, codes are missing or invoices sit in another period.

Terra Insight
Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 14 October 2026
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops
Knowledge Card
Problem

A junior accountant finds the GSTR-1 HSN summary total does not equal the sales report for the month.

How It's Resolved

Table 12 totals net supplies by HSN or SAC, unit and B2B or B2C split. Differences come from credit-note netting, units, missing codes, period cut-off and rounding.

Configuration

A monthly bridge from sales report total to Table 12 total listing credit notes, period shifts, non-GST items and rounding, with codes picked from the item master.

Output

Table 12 explained to the rupee before filing, and consistent with the GSTR-1 invoice tables.

The HSN summary in GSTR-1 adds up your month’s sales by HSN or SAC code, unit and value. It often differs from your sales report because the two count different things: one may net off credit notes and the other may not, items can share a code, units may not match, or some invoices fall in a different month. The difference is usually explainable line by line.

The HSN summary is Table 12 of GSTR-1, due by the 11th of the following month (or the 13th after the quarter for QRMP filers).

What usually causes the mismatch?

CauseWhat you seeFix
Credit notes netted in one report onlyHSN total lower than sales reportDecide one basis; Table 12 shows net supplies
Two items share one HSN codeFewer HSN rows than itemsNothing wrong; compare at code level, not item level
Units differ (pieces vs kilograms)Quantity off, value fineUse the unit code the portal expects, from the item master
B2B and B2C split wrongTotals right, tabs wrongTag each invoice by buyer GSTIN
Missing or invalid code on itemsValue missing from Table 12Add codes to the item master from the portal list
Non-GST or exempt items in the sales reportSales report higherReport exempt supplies in Table 12 with their code; keep non-GST items out
Invoices dated in another monthTiming gapCheck the cut-off for the last two days of the month
Rounding on each lineGap of a few rupeesAccept; round at line level consistently

Why does the HSN summary now separate B2B and B2C sales?

From 2025, GSTN’s Phase III of HSN reporting split Table 12 into a B2B tab (sales to registered buyers) and a B2C tab (sales to unregistered buyers). Codes are picked from a drop-down instead of typed. If your GSTR-1 has B2B invoices, the B2B tab cannot be blank. This change caught many businesses whose software sent one combined summary.

Should the HSN totals equal the invoice tables of GSTR-1?

They should agree, after allowing for credit and debit notes and advances. The invoice tables (B2B, B2C large, B2C others, exports) less the net of credit and debit notes should equal the Table 12 total. The portal now checks this, initially as a warning. A gap you cannot explain is worth fixing before filing.

Worked example: a ₹48,000 gap

A Nagpur electronics trader’s October sales report shows ₹14,60,000 of taxable sales. The Table 12 summary shows ₹14,12,000.

ItemAmount
Sales report, taxable value₹14,60,000
Less credit notes issued in October (netted in Table 12, not in the sales report)₹48,000
Expected Table 12 total₹14,12,000
Actual Table 12 total₹14,12,000
Unexplained differenceNil

₹14,60,000 minus ₹48,000 equals ₹14,12,000. The fix is not to change either figure but to keep this bridge on file. If the trader had found, say, ₹14,05,000 in Table 12, the remaining ₹7,000 would point to a missing code or an invoice in the wrong month.

A five-minute check before filing

  1. Export the sales report and the Table 12 preview for the month.
  2. Subtract credit notes and add debit notes.
  3. Compare at code level and list any code only in one report.
  4. Check the B2B and B2C tabs against buyer GSTINs.

Key rules to remember

  • HSN digits follow Notification 78/2020: 4 digits up to ₹5 crore of turnover, 6 digits above ₹5 crore.
  • Credit notes reduce Table 12 in the month issued; under Section 34 they must be declared by 30 November following the financial year.
  • Tax paid late carries interest at 18 percent a year under Section 50 of the CGST Act.
Primary reference: GST portal user manuals — the GSTN tutorial site, which explains how Table 12 (HSN-wise summary) of GSTR-1 is filled, including the B2B and B2C tabs..

Frequently Asked Questions

What is Table 12 of GSTR-1?
The HSN-wise summary of outward supplies: for each HSN or SAC code, the unit, quantity, taxable value and tax.
Why does Table 12 now have B2B and B2C tabs?
Under Phase III of HSN reporting, introduced by GSTN in 2025, supplies to registered and unregistered buyers are summarised separately, and codes are chosen from a drop-down.
Should credit notes be netted in the HSN summary?
Yes. The HSN summary reflects net supplies for the period, so credit notes issued in the month reduce the value under the relevant code.
Will GSTR-1 be rejected if HSN totals differ from the invoice tables?
The portal runs validations between Table 12 and the other tables. These were introduced in warning mode, but a mismatch is a red flag for scrutiny.
How many digits should the HSN in Table 12 have?
4 digits if last year's aggregate turnover was up to ₹5 crore, 6 digits above ₹5 crore.

See how TransactIG handles reconciliation for your industry

Configuration takes 2–4 weeks. No code development required. ISO 27001:2022 certified.