How-to · SAP GSTR-1 HSN summary

Your GSTR-1 HSN summary comes back blank. SAP's KBAs document two causes outright; its master data hides two more

The short answer

A blank or rejected GSTR-1 HSN summary in SAP traces to several independent causes, not one bug. Two are documented outright in SAP's own KBAs: GST condition types never classified against the pricing procedure (KBA 3634623), and, before GSTN's May 2025 rollout, a reporting activity SAP had named for February 2025 that ran ahead of what GSTN's production portal supported (KBA 3586906). Two more are master-data checks: the material master's plant-level Control Code (MARC-STEUC), and a shared HSN/SAC code-list gap (table T604F) that can leave both the material and service masters' lookups empty for country IN. Each needs its own fix, not a single HSN re-entry.

A blank Table 12, a rejected JSON, or a B2B tab that stays empty while B2B invoices sit in every other table of the same return — none of these is one SAP bug with one fix. SAP's own knowledge base documents some of the causes outright; another sits in a field SAP maintains per material per plant, where nothing in SAP's data model stops the same material from carrying a different HSN code depending on which plant it shipped from.

Three different symptoms, not one

The KBAs behind this article span four SAP product lines, and a fix that exists in one often doesn't exist in another: the material-master cause below (Cause 1) spans all three ERP lines — classic SAP ERP/ECC, S/4HANA on-premise and S/4HANA Cloud Public Edition — though its two cited KBAs are specifically on-premise; the shared material/service HSN-SAC code-list gap (Cause 2) is documented with classic SAP ERP/ECC and S/4HANA on-premise objects, though S/4HANA Cloud Public Edition carries an equivalent code-list prerequisite; SAP S/4HANA Cloud Public Edition separately carries the condition-type and reporting-activity causes, plus one of the narrower B2B KBAs; and SAP Digital Compliance for India/DCS carries the other narrower KBA, and the B2B/B2C split itself. Confirm which product line you're actually running before applying any fix here.

Search for this problem and the symptoms blur together, but what finance teams running SAP for GST actually report splits into at least three distinct shapes: the GST portal rejects the GSTR-1 JSON outright for an HSN code SAP exported that the portal won't take — GSTN has required 4 or 6 digits by turnover since Phase 2 (November 2022), and since Phase 3 accepts HSN "from drop down only"; the Table 12 B2B tab comes back completely empty even though B2B invoices are sitting in every other table of the same return; or the HSN-wise summary SAP generates simply disagrees with the invoices behind it — and if the same material ships from more than one plant, SAP's data model allows it a different HSN code in each (Cause 1). Each of these has a different SAP-side cause, and SAP's knowledge base documents several of them separately — not one symptom with three names.

Section 61 of the CGST Act lets the proper officer scrutinise a return "to verify the correctness of the return and inform him of the discrepancies noticed". CBIC's only published list of scrutiny parameters (as of November 2026) — Annexure B to Instruction No. 02/2022-GST (22 March 2022), the SOP for FY 2017-18 and 2018-19 — doesn't mention HSN. For FY 2019-20 onwards, Instruction No. 02/2023-GST (26 May 2023) modified that SOP: returns are selected on risk parameters identified by DGARM and shown on the officer's ACES-GST scrutiny dashboard, and the instruction itself publishes no parameter list — but the officer "may also consider any other relevant parameter, as he may deem fit" (para 5.2). A Table 12 that disagrees with the rest of your GSTR-1 is an inconsistency on the face of the return.

The GSTN side, briefly — this article assumes it

None of this starts with SAP. GSTN's Table 12 advisory for the May 2025 return period onward — Phase 3 of its HSN rollout — removed manual HSN entry from the portal ("HSN code can be selected from drop down only," in the advisory's own words), split Table 12 into separate B2B and B2C tabs, and added a value-match check between the B2B tab and the other B2B-carrying tables of the same return, run in warning mode only as of 9 November 2026 — a mismatch warns, it doesn't block filing, except for the one hard rule: if B2B supplies appear anywhere else in the return, the B2B tab of Table 12 itself cannot be left blank. GSTN applies the same digit thresholds from Notification 78/2020-Central Tax (4 digits up to ₹5 crore aggregate turnover in the preceding financial year, 6 above it) to Table 12 that the notification itself sets for tax invoices under Rule 46. Table 13 (documents issued) became a separate, harder error from the same return period — leaving it blank stops you proceeding to file when B2B or B2C supplies exist. That's the whole GSTN-side mechanism in outline; the sibling article covers it in full, including the ±10% tolerance and the amendment rule, and isn't repeated here. What follows is specific to what SAP does with that mechanism on the way in.

Cause 1: HSN lives at material-plant level (SAP ERP/ECC, S/4HANA on-premise and S/4HANA Cloud Public Edition)

SAP's material master stores the field SAP's GST India KBAs treat as HSN/SAC — labelled Control Code — as MARC-STEUC: table MARC, field STEUC. MARC is SAP's data-dictionary table for Plant Data for Material, keyed by material number and plant, which means nothing in the data model stops the same material number from carrying a different Control Code in Plant A than in Plant B. SAP's own knowledge base confirms the field gets maintained and mass-updated at that level: KBA 2974421 is a how-to for mass-updating it, titled, verbatim, "Mass update the field Control Code MARC-STEUC" — it documents how the field is maintained, not a failure cause by itself. A separate KBA, 3436518, documents the same field (as STEUC) showing up disabled in the purchasing-side India tab of the purchase-order transactions ME21N and ME22N — again a behaviour report, not a cause of a blank HSN summary. Both KBAs are specifically on-premise (ECC / S/4HANA on-premise); the underlying per-plant structure isn't, though — SAP's "Maintain HSN/SAC Codes" help page for S/4HANA Cloud Public Edition has you open the product in Manage Product Master Data, go to the Plants tab to pick a plant, then the International Trade tab's Taxes in International Trade field — the same plant-keyed assignment as MARC-STEUC, through a different app, on the newer product line.

Whatever the reason, a per-plant difference for the same goods is a master-data question to settle with whoever owns classification, not a variant to report around. A plant extended with a stale, mistyped or blank Control Code is one way it happens. None of the KBAs above documents this as a cause of a blank or wrong HSN summary — that link is our own reading of what SAP's data model permits, not a failure mode SAP's support content states outright. We found no SAP documentation of a cross-plant consistency check on this field: each plant's billing documents draw on the Control Code that plant's record carries. If your HSN-wise totals don't tie to your invoice register and the business sells the same SKU out of more than one plant, comparing the Control Code across plants for that material number is the first thing to check — before assuming the summary report itself is wrong.

Cause 2: the material and service masters share one HSN/SAC code list — and it can come up empty for India (classic SAP ERP/ECC and S/4HANA on-premise, with an S/4HANA Cloud Public Edition equivalent)

Materials and services don't use separate lookup mechanisms for India HSN/SAC — they share one: table T604F (view V_T604F). KBA 2430349, "GST India: Maintenance of HSN/SAC Codes," names its own symptom as one problem across both masters: "F4 help for the field HSN/SAC (Control Code in Material Master and Tax Tariff Code in Service Master) does not contain any value for the country key IN" — and documents the same consequence either side: entering a code by hand that isn't in T604F throws error 00058, quoted verbatim: "Entry & & & does not exist in &4 (check entry)." SAP's own "Maintain HSN/SAC" help documentation describes the same list being configured for country IN before a master record can "choose the HSN/SAC code from the list maintained in the previous configuration" — so if that configuration is incomplete for IN, both masters' lookups come up empty, not just one. 2430349's own Product field also lists SAP S/4HANA Cloud Public Edition, alongside the on-premise lines — and on Cloud, SAP's "Maintain HSN/SAC Codes" page makes an equivalent list a prerequisite in its own terms: you assign to your products "the HSN/SAC codes you've maintained in the Maintain HSN and SAC (ID: 101332) configuration activity".

The two fields aren't interchangeable, though, and conflating them sends you to the wrong master for an outward-facing problem. The Tax Tariff Code maintained via transaction AC01 — per KBA 2469458, "GST India: Tax Tariff Code Field not available in Service Master," which SAP files under its service-master component MM-SRV-MD alongside India MM and SD localization tags — is, by SAP's "External Services Management (MM-SRV)" help documentation, the SAC field for services you procure — service purchase orders, service entry sheets, invoice verification via MIRO — not services you sell. Services (and goods) you sell draw their HSN/SAC from the material/product master's Control Code instead (Cause 1), or, on S/4HANA Cloud, from the item-level HSN/SAC field SAP's "Creating Customer Invoices" help page documents on customer invoices posted directly in its Create Outgoing Invoices app. So a missing SAC line in your outward HSN summary isn't a service-master/AC01 problem to chase first — that field feeds purchasing, not billing. On the master-data side, look instead at the selling material's Control Code (Cause 1) or, if neither master's F4 lookup returns anything at all for country IN, the shared T604F list itself — and if the master data is clean, check the configuration and reporting causes below (Causes 3 and 4) for the product lines they cover. Linking either field to a blank or wrong outward summary beyond what SAP's own symptom text says is our own reading of how the two masters connect, not a failure mode SAP's support content states outright. Both KBAs cited in this section are gated previews — cause and resolution detail need an SAP for Me login; the KBA points above come only from their public symptom text and metadata.

Cause 3: the GST condition types were never classified against the pricing procedure (SAP S/4HANA Cloud Public Edition)

This is the cause with the clearest SAP-documented fix. KBA 3634623, "HSN Code Not Reflect In GSTR1 Report," states the cause in one line: "The HSN related configuration was not completed in the activity Classify Condition Types." Its resolution: "Classify the pricing procedure against the GST condition types in SSCUI 101934 Classify Condition Types." In other words, a billing document can have a perfectly correct HSN code sitting in the material master and still never surface it in the GSTR-1 report, because the GST output condition types in the pricing procedure that fed that billing document were never mapped against their condition names in SSCUI 101934. The KBA names them: "JOCG,JOSG,JOIG,JOUG are the condition types that need to be classified against the pricing procedure to get the HSN code populated." SAP's help page for the same activity lists those four as the delivered A/R CGST, SGST, IGST and UTGST conditions and adds that "Any new GST tax condition type created must be classified in this view", so any custom GST output condition in your pricing procedure needs the same classification. What's confirmed, from the KBA itself, is the mechanism: the HSN summary is downstream of condition-type classification, not just of the material master — and this is a documented failure cause in SAP's own words, not our inference.

Cause 4: SAP's reporting activity and GSTN's rollout date fell out of step (SAP S/4HANA Cloud Public Edition; SAP Digital Compliance for India for the B2B/B2C split itself)

GSTN's Table 12 Phase 3 change is a portal-side rule, but SAP had to build a corresponding activity to generate it — and, separately, had to update the Digital Compliance Service product to produce the new B2B/B2C split. GSTN itself kept moving the Phase 3 date across re-issues of the same advisory: a 21 January 2025 version said "from February 2025 return period"; a 27 February 2025 re-issue dropped the date entirely and said only "will be implemented soon"; the current text settled on "from May 2025 return period." SAP's own activity, named for the February 2025 date, ran ahead of what GSTN's production environment actually supported when the KBA below was issued. KBA 3586906 documents this directly: an SAP activity named "GSTR1 Reporting India - Feb 2025 onwards", built for the new B2B/B2C HSN segregation, that "will not be supported by the Tax Authority" because, per the KBA's own cause line, "the Tax Authority has not yet rolled out the new HSN legal changes to production" at the time the KBA was issued — the fix was to fall back to the older "GSTR1 Reporting India July 2020 Onwards" activity and set validity dates between the two activities in the Setting Up Your Statutory Reporting configuration activity (SSCUI 101071). A second KBA, 3588050, "Changes in HSN summary reporting in DCS," documents the separate B2B/B2C split itself shipping as part of DCS release 1.14.11, "as per legal change". KBA 3586906 describes the window before GSTN's rollout — its cause line says the Tax Authority had "not yet rolled out" the change — and SAP's own GSTR1 report documentation now says the B2B/B2C segregation "applies from the reporting period starting May 2025." As of November 2026, the out-of-step case worth checking is the reverse one: a system still pointed at the older "GSTR1 Reporting India July 2020 Onwards" activity that KBA's workaround told users to fall back to.

The practical point: if your HSN summary was working and then broke specifically around a Table 12 structure change, check which of SAP's statutory-reporting activities your system is pointed at and which DCS release you're on before assuming the data is wrong — the activity itself may simply be running ahead of, or behind, what GSTN's production environment and your SAP release actually support at the same moment.

Other documented failure shapes

Two more KBAs describe narrower, separately-diagnosed symptoms worth knowing by name rather than guessing at. SAP KBA 3617015, "HSN B2B Summary of GSTR1 has few missing invoices" (SAP Digital Compliance for India), documents exactly that — a partial gap, not a fully blank tab; its cause and resolution sit behind an SAP for Me login and this article does not speculate on them. SAP KBA 3668512, "Error in B2B Section while generating GSTR1 report from Run Statutory Reports App" (SAP S/4HANA Cloud Public Edition), documents a narrower rule: "positive values are permitted in the B2B section of the GSTR1 return" — the invoices-to-registered-customers section, which "reflects actual invoice values without any negative adjustments." That is the B2B invoice section, not the HSN summary: SAP's own list of GSTR1 report sections carries "Invoice from registered customers (B2B)", "Credit Note/Debit Note from registered customers (CDNR)" and "HSN B2B Summary Details (HSN B2B)" separately. Don't read this KBA as a reason to strip credit notes out of Table 12: GSTN's advisory checks the Table 12 B2B tab against tables that include 9B (registered), the credit/debit-note table.

Don't read several SAP KBAs on adjacent symptoms as confirmations of one bug. A plant-level Control Code mismatch, an unclassified condition type, a missing invoice in the summary, and a negative-value line in the B2B invoice section are different things that all show up as "the HSN summary looks wrong." Match your own symptom to the KBA that actually describes it before applying a fix built for a different one. Of the KBAs cited across this article, 2974421, 3436518, 2430349, 2469458, 3588050 and 3617015 are gated previews — cause/resolution detail needs an SAP for Me login; 3634623, 3586906 and 3668512 are public in full.

Checking it before the portal does

Every KBA above assumes you already know something's off — usually because the portal rejected a JSON or a Table 12 tab came back empty, with a filing deadline close behind it. Confirming, before upload, that every HSN code behind every billing document resolves to the same value across every plant that bills the same material, that the material and service masters' HSN/SAC lookups actually return a value for country IN, and that the condition types feeding each billing type are classified the way SSCUI 101934 expects — across a GSTIN with more than a couple of plants and any real invoice volume — is painful to do by hand every single filing cycle, which is one reason these errors tend to surface on the portal instead of before it.

Recoup doesn't touch SAP's billing documents, its material master, or its condition-type configuration — those stay SAP's to fix, per the KBAs above. What Recoup reconciles is the other side of the same GST position: your books, your bank, and the GST portal's GSTR-2B/IMS feed, invoice by invoice, so the inward credit you claim matches what's actually been filed — the same register discipline a clean outward HSN summary needs, just on the other side of the return. Recoup doesn't check the outward HSN summary, and as of November 2026 its documented connections are Zoho Books, Tally, bank statements and the GST portal — not SAP.

Reconcile the side Recoup already covers

Recoup reconciles your bank, books and the GST portal's GSTR-2B/IMS feed continuously, invoice by invoice, while you sort out the HSN summary on the outward side.

Book a demo →

Related guides