Table 12 says your HSN totals don't match. Here's what it's actually comparing
The GSTR-1 Table 12 mismatch warning fires when HSN-wise B2B totals don't match the same supplies' value reported elsewhere in the return — Tables 4A, 4B, 6B, 6C, 8 (registered), 9A, 9B (registered), 9C (registered), 15 (registered) and 15A (registered) — by more than the ±10% tolerance GSTN's GSTR-1 FAQ describes. GSTN runs this as a warning, not a block — you can still file. As of 9 November 2026, only the B2B tab has a hard rule (it can't be left blank when B2B supplies appear in those tables); the B2C tab accepts any value, or blank.
Whatever the exact wording on your screen, the message means the same thing: the HSN-wise totals you've entered in Table 12 don't agree with the B2B or B2C figures sitting in the rest of your GSTR-1. Usually it isn't a formatting bug in Zoho Books or Tally — the tool is reporting a number that was already inconsistent in your register, though a few tool settings can cause it too (covered below). Here's what GSTN's own advisories say the check actually does, and how to close the gap in each tool.
The error, and what it's actually built on
One TaxTMI forum thread quoted the GSTR-1 Table 12 warning this way:
"HSN wise taxable value or tax amounts of B2B Supplies in Table 12 does not match with the other specified B2B tables."
We couldn't independently verify that this is the GST portal's exact, complete string — treat it as one filer's paraphrase of the warning, not a confirmed verbatim quote. What it describes, though, is real and documented, not a vague "please check your numbers" nudge. Per GSTN's own advisory, "Reporting of HSN codes in Table 12 of GSTR-1/1A" (file dated 25 April 2025; the current PDF was generated 10 June 2025), Table 12's B2B tab is checked against the B2B value reported in Tables 4A, 4B, 6B, 6C, 8 (recipient registered), 9A, 9B (registered), 9C (registered), 15 (recipient registered) and 15A (recipient registered) of the same return. The B2C tab gets the equivalent check against Tables 5A, 6A, 7A, 7B, 8 (recipient unregistered), 9A (export), 9A (B2CL), 9B (unregistered), 9C (unregistered), 10, 15 (recipient unregistered) and 15A (recipient unregistered). If you amended an earlier-period invoice, the advisory specifies that only the differential value from the amendment counts toward the comparison — not the original figure again. GSTN's GSTR-1 FAQ (Table-12, Q10) adds a tolerance the advisory doesn't mention: Table 12 validates as long as its B2B or B2C value is within ±10% of the corresponding tables.
Why the rule isn't new, even if the warning is
The digit requirement behind all of this is old, and it's an invoice rule, not a GSTR-1 rule by name. Notification 78/2020-Central Tax dated 15 October 2020 is issued under the first proviso to Rule 46 of the CGST Rules, and sets the HSN-digit requirement for tax invoices: with effect from 1 April 2021, 4-digit HSN for taxpayers with aggregate annual turnover (AATO) up to ₹5 crore in the preceding financial year, and 6-digit for those above it. It never mentions GSTR-1 or Table 12 by name — GSTN's advisories apply the same two thresholds to Table 12 and attribute that requirement to this notification. The notification also has a proviso for B2C invoices: a registered person with aggregate turnover up to ₹5 crore in the previous financial year may omit the HSN digits on a tax invoice issued to an unregistered person. Don't read that as the reason for the Table 12 B2C leniency above: GSTN's advisory gives no reason, and its leniency applies at every turnover, including above ₹5 crore, which the proviso doesn't cover.
GSTN rolled the Table 12 digit mandate out on the portal in phases, and its own advisory text has been inconsistent about naming a date for the later phase. GSTN's 2022 advisory put the first phase live in two parts, from 1 April and 1 August 2022; the current advisory records the second phase as implemented from 1 November 2022. What's covered in this article — the dropdown-only entry and the value-matching check — is the phase after that, and GSTN changed its date across revisions of the same advisory: an 8 January 2025 version said "from January 2025 return period"; a 21 January 2025 revision pushed that to "from February 2025 return period"; a 27 February 2025 re-issue — sitting at the same URL as the original 8 January advisory — dropped the date entirely and said only "will be implemented soon"; the current text says it "is being implemented from May 2025 return period." That phase has applied to every filer since May 2025. So if you're seeing this warning for the first time in November 2026, the rule itself isn't new to you — something else changed: your data, an export you misclassified, or your accounting software's own settings (see the TallyPrime section below for genuine tool-side causes).
- Manual HSN entry is removed. "Manual user entry of HSN will not be allowed. HSN code can be selected from drop down only" — the advisory's own words. Once you pick a code from the dropdown, a new "Description as per HSN Code" field auto-populates — in the advisory's words, "a customized description mentioned in HSN master will auto-populate" there. A separate, optional feature, "My HSN Master," lets you search by your own product names instead; selecting a match there auto-populates the HSN code, that same description field, UQC and quantity together.
- The value-matching check above is introduced, in warning mode, alongside a restructuring of Table 12 itself into two separate tabs — "B2B Supplies" and "B2C Supplies" — that you now have to fill in independently rather than as one combined grid.
The dropdown-only rule is also where a lot of the mismatches start, and TallyPrime's own documentation gives a concrete example: "Sometimes, in the Books, HSN is 851410, but as per the HSN drop-down in the GST portal, it is 85141000 or 8514." That's not really a digit-length mismatch, though — 851410 doesn't appear anywhere in GSTN's own downloadable HSN & SAC code list, which carries 8514, the legacy 8-digit 85141000, and the current split into 851411/851419. It's an obsolete or simply wrong code. The fix is remapping it to a current, valid code at the digit length your turnover requires — not reformatting the same wrong code to a different length.
Fixing it in TallyPrime
Tally maintains dedicated guidance for this family of errors, and the fixes differ by what's actually behind the warning. Per TallyPrime's HSN/SAC resolution page and its general GST errors and resolutions page:
| What's actually wrong | Fix in TallyPrime |
|---|---|
| B2B sales exist but one or more are missing an HSN code, so the B2B tab of Table 12 doesn't carry their value | Find the B2B transactions (including nil-rated and exempt sales) with missing HSN details, correct them at the voucher or stock-item level, regenerate the HSN/SAC summary, and re-export. |
| Only B2C sales exist, with genuinely zero B2B supplies anywhere in the return | Tally's documented error here isn't "cannot be left blank" — by GSTN's own text, that sub-rule only fires if B2B supplies appear in other tables, which by definition they don't for a B2C-only filer. Tally's actual wording is: "HSN wise B2B Supplies are not reported in Table 12. Kindly provide details to proceed further," and Tally attributes it to the portal having "built mandatory B2B HSN validation" — which, for a filer with no B2B supplies, goes further than the advisory's text. Tally's documented workaround, which isn't in GSTN's Table 12 advisory, is a dummy B2B line entered directly on the portal's Table 12 screen: Quantity 1, Taxable Value ₹1, GST Rate 0%, entered as exempted/nil-rated. Tally's pages still document this error as of their September and October 2026 updates; check whether the portal still raises it for your return before adding the line. |
| "Combination of HSN, UQC and Rate cannot be repeated" after you've edited, deleted or renumbered a voucher post-export | Tally's first documented fix is to upgrade to TallyPrime Release 6.1 or later, which refreshes your invoices and resends the latest data. If it persists, reset manually: open the HSN/SAC Summary report, press Alt+V (Alter Summary) and confirm, make the correction, save with Ctrl+A, then press Alt+R (Reset Summary) — Tally's wording is that this restores "the original values", after which "the values are now refreshed" and you can file again. If delete requests were also raised on the portal, there's a separate path: Alt+Z (Exchange) > All GST Options > Upload GST Returns > GSTR-1, then Alt+Q (Reset Delete Request). |
| HSN code rejected as invalid, or flagged against the portal's dropdown | Based on your turnover, keep every HSN entry at one consistent length before upload — 4, 6 or 8 digits per Tally, with at least 4 up to ₹5 crore AATO and at least 6 above it — and check codes against the portal's own HSN/SAC search rather than against what's historically been in your stock master — Tally's guidance is explicit that books and portal dropdown need to match exactly, not just be "close." |
In most of these, the underlying cause is a value sitting in your sales register that doesn't agree with the HSN summary generated from it — either because a voucher changed after the summary was built, or because an HSN code never matched what the portal expects. But it isn't always a register problem. Tally's own documentation lists genuine tool-side causes too: an outdated release (several of the fixes above assume Release 6.1 or later), the "Separate B2B and B2C HSN Summary applicable from" date in F11 company features not set to 1-May-2025 (Tally documents this as a separate "GSTR-1 JSON file structure has changed" error), or the HSN/SAC Summary scope set to "All Sections Except B2C" when it needs to cover all sections. There's also a classification trap that has nothing to do with your register being wrong: GSTN's own Table 12 cross-check places exports (Table 6A) on the B2C side of the comparison, so export HSN values that land in the B2B tab — exports go to a business, but they aren't "B2B" in the GST sense — can trip the B2B mismatch warning (if the gap exceeds the FAQ's ±10% tolerance) on a correctly filled-out register.
Fixing it in Zoho Books
Zoho's knowledge-base index lists no page on the GST portal's Table 12 value warning itself (checked 9 November 2026). Its closest page, "Mismatch in HSN-wise Summary of Outward Supplies in GSTR-1 Report", explains something narrower: why, inside Zoho's own Summary of Outward Supplies (GSTR-1) report, the HSN-wise summary row won't equal the other rows combined. Zoho's formula is supplies to registered businesses plus supplies to consumers, minus the credit notes, debit notes and refund vouchers created for both; and where discounts, shipping charges exclusive of tax, TCS or TDS are associated with transactions, the report's other rows include them and the HSN row doesn't, so you subtract them too. That's an expected difference inside Zoho's report, not by itself a portal mismatch — rule it out before assuming your register is wrong. Per Zoho's "What is HSN-wise Summary in GSTR-1?" page, the HSN-wise summary is auto-generated in Zoho Books, and you verify it and push it to the GST portal for filing — it isn't something you build by hand.
So the fix inside Zoho Books is at the transaction level, not inside the report: confirm every invoice, credit note, debit note and refund voucher is recorded against the right customer and GST treatment — Zoho's formula treats registered-business and consumer customers separately — and that HSN codes are selected from the current dropdown at or above the minimum digit length for your turnover, the same as in Tally.
The step that actually prevents it
Every fix above happens after the portal has already told you something's wrong — at the point you're trying to submit, with a filing deadline sitting right behind it. Checking that your Table 12 HSN-wise totals actually tie to your B2B and B2C invoice lines before you reach the portal at all is painful to do manually on a register of any real size: it means pulling every invoice by HSN code, summing taxable value and tax separately for B2B and B2C, and comparing that against whatever your accounting software generated — for every filing period, not just the one where you happened to get flagged.
How Recoup fits in
Recoup doesn't file GSTR-1, doesn't touch Table 12, and doesn't replace Zoho Books' or TallyPrime's export — that's still the job of the tool you're already using. What Recoup reconciles today is the inward side of your GST position: your bank, your Zoho Books ledgers and bills, and the GST portal's GSTR-2B/IMS feed, invoice by invoice, so the credit you claim matches what your suppliers have actually filed. That's the same register discipline a clean Table 12 needs — invoice lines, codes and totals that agree with each other before you file — just not the HSN-specific, outward-side check itself.
Reconcile the side Recoup already covers
Recoup reconciles your bank, Zoho Books and the GST portal's GSTR-2B/IMS feed continuously, invoice by invoice, so the credit side of your GST position stays clean while you sort out Table 12 on the outward side.
Book a demo →Related guides
Filing GSTR-1 directly from Zoho Books
The API-access step that quietly expires and makes a push start failing for reasons that look nothing like a Table 12 error.
Exporting GSTR-1 as JSON from TallyPrime
Why the HSN/SAC summary is a separate export from the main GSTR-1 JSON — and the other upload errors that trace back to the same register.
GST reconciliation: the 2026 guide for finance teams
The four reconciliations across your books, GSTR-2B and the bank that decide your input tax credit before you ever get to a filing-screen warning.
Input Tax Credit (ITC)
Why the figures a supplier files in GSTR-1 become someone else's credit position, not just their own return.