How-to · SAP GST statutory reporting migration

Your legacy SAP GSTR-1/3B/6 reports have an expiry date. 2608 deprecates them, 2708 kills them off entirely.

The short answer

SAP deprecates its legacy GSTR-1, GSTR-3B and GSTR-6 reports — report categories IN_GSTR1_DCL, IN_GSTR3B_DCL and IN_GST_GSTR6 — from S/4HANA Cloud Public Edition release 2608, and they cease to function from release 2708 (SAP KBA 3780253). SAP recommends moving to the new GSTR-1, GSTR-3B and GSTR-6 reports, which need SAP Document and Reporting Compliance, Cloud Edition and additional licenses. Until then, where a GSTR-1 run is stuck after the 2608 upgrade and you still need the legacy GSTR-1 activities, or a legacy GSTR-1 or GSTR-3B activity is missing because its parameter isn't maintained, SAP's interim fix is to maintain IN_GSTR1_NEW_ACTY_IND (GSTR-1) or IN_GSTR3B_NEW_ACTY_IND (GSTR-3B), with blank Low/High, in Setting Up Your Statutory Reporting (SSCUI 101071) (SAP KBAs 3796537, 3796247, 3700912). That keeps the legacy report running — it is not the migration, and it stops helping once 2708 lands.

This guide works from six SAP knowledge base articles on the GSTR1, GSTR3B and GSTR6 reports — two deprecation notices and four fix KBAs. In S/4HANA Cloud Public Edition the legacy reports carry a hard expiry, deprecated in release 2608 and non-functional from release 2708. The window to migrate without a filing gap is narrower than the KBA titles suggest, and the fix KBAs are each specific to one report, not interchangeable.

Two unrelated things are both called "DRC" here. SAP's "Document and Reporting Compliance" (DRC) is the SAP product the legacy GSTR reports live in — KBA 3780253 deprecates them from DRC, and the new GSTR1/GSTR3B/GSTR6 reports that replace them work with its Cloud Edition. It has nothing to do with GST's own DRC-01C intimation (Rule 88D) or DRC-03 payment intimation (Rule 142(2)–(3), CGST Rules) — same three letters, two completely different systems. Every "DRC" in this article means SAP's product.

What's deprecated, what's obsolete, and when

Per SAP KBA 3780253 ("The GSTR (Legacy) reports will be deprecated from SAP Document and Reporting Compliance," S/4HANA Cloud Public Edition), three legacy India GST reports — five report definitions across three report categories — are being retired in Public Edition on a two-stage timeline, deprecated in release 2608 and non-functional from release 2708. Its Private Edition counterpart, KBA 3786072, gives no release numbers in its public preview (see below).

Legacy reportReport category (definition IDs)Deprecated fromCeases to function fromReplacement
GSTR1 (Legacy)IN_GSTR1_DCL (V0, V1, V2)Release 2608Release 2708New GSTR1 report
GSTR3B (Legacy)IN_GSTR3B_DCL (V0)New GSTR3B report
GSTR6 (Legacy)IN_GST_GSTR6 (V1)New GSTR6 report

"Deprecated" and "ceases to function" are not the same event — SAP's own wording in KBA 3780253 is that the legacy definitions are deprecated from release 2608 and, "starting with the 2708 release, these report definitions will cease to function," with SAP ending "all support for them" from the same release. Two things are easy to miss in that sentence. First, the "Manage Tax Items for Legal Reporting" activity will not be available for the new India GST Reports (KBA 3780253's own wording) — if your process relies on that screen today, it doesn't carry over; check what the New GSTR1/3B/6 reports' own screens do instead before you assume feature parity. Second, the new reporting path "will work with SAP Document and Reporting Compliance, Cloud Edition integration," and KBA 3780253 says plainly "this would require additional licenses" — confirm entitlement with your account executive before you plan a cutover date, not after.

The deprecation is published twice because it hits two different S/4HANA Cloud flavours separately — KBA 3780253 for Public Edition, KBA 3786072 for Private Edition. Both state the same symptom (legacy reports "being deprecated and replaced by the New GSTR1, GSTR3B and GSTR6 reports"). Of the two, only the Public Edition KBA, 3780253, gives the release pair — 2608 and 2708. KBA 3786072's public preview shows the symptom only, with no release numbers anywhere in it; don't assume 2608/2708 applies identically to Private Edition on the strength of this article alone — confirm against your own KBA 3786072 login, behind SAP for Me, before you change anything in a transportable client. Everything past this paragraph is scoped to Public Edition — every fix KBA cited below is a Public Edition KBA — unless stated otherwise.

Status as of 6 November 2026. SAP's knowledge base articles are living documents and their public preview doesn't show a visible last-updated date — re-confirm every KBA number, parameter and release number here against the live article on SAP for Me before acting, especially if you're reading this more than a few weeks after publication.

Where it bites first: three KBAs, two parameters, not interchangeable

Three SAP fix KBAs cover the legacy-activity symptoms around the 2608 change — two on the GSTR1 side, one on the GSTR3B side, and only KBA 3796537 ties its symptom to the 2608 upgrade itself — and the parameter names differ by one word, easy to transpose if you're moving fast. All three fixes keep the legacy report running; none of them is the migration:

  • GSTR1 side, stuck run — KBA 3796537 ("GSTR1 report not working after 2608 upgrade"). Symptom: the run gets stuck in "Submitted to Authority," the New Run button is greyed out, a manual status update fails with "Manually updating the Submission Status is not permitted," the Reconcile and File GSTR1 activity "remains in 'Not Started' status," and separately, the reporting task "may remain overdue." Cause: 2608 introduces new GSTR1 activities, and if your configuration in "Setting Up Your Statutory Reporting" (SSCUI 101071) doesn't match the new activity setup, the old run has nowhere to land. Fix, in the KBA's own words, if "the legacy GSTR1 reporting activities must still be used before release 2708": in SSCUI 101071, select or create the reporting entity, add report category IN_GSTR1_DCL, set its periodicity, and add parameter IN_GSTR1_NEW_ACTY_IND with a Valid-From date — leave Low and High blank. SAP's own framing is explicit that this is "an interim option for those who need to continue with the legacy GSTR1 reporting activities," and that it is "recommended to migrate to and use the new GSTR1 reporting activities introduced with release 2608" instead.
  • GSTR1 side, missing from the list — KBA 3796247 ("Legacy GSTR1 reporting activity/key/id is not visible in 'Run Statutory Reports'"). Symptom: the Legacy GSTR1 reporting activity simply isn't offered in the app. Cause: "the required parameter IN_GSTR1_NEW_ACTY_IND is not maintained." Fix: "to continue using the Legacy GSTR1 report," add the same parameter in SSCUI 101071 with a Valid-From date, blank Low/High, save and transport if your landscape requires it.
  • GSTR3B side — KBA 3700912 ("Legacy GSTR3B reporting activity/key/id is not visible in 'Run Statutory Reports'"). Symptom: the GSTR3B activity key you need simply isn't offered in the app. Cause, per the KBA's own text: "the required parameter IN_GSTR3B_NEW_ACTY_IND is not maintained." Fix: "to continue using the Legacy GSTR3B report," maintain the parameter in the same config app, SSCUI 101071 — type it in manually if the list doesn't offer it, set a Valid-From date, leave Low/High blank, save, and transport to your quality and production systems if your landscape requires it.
Note the asymmetry: IN_GSTR1_NEW_ACTY_IND is the GSTR1 parameter, IN_GSTR3B_NEW_ACTY_IND is the GSTR3B one. None of the three KBAs documents a corresponding parameter for GSTR6 — if your GSTR6 run breaks the same way, treat that as a gap to raise with SAP rather than assuming the GSTR1/3B pattern transfers.

The "earlier periods not completed" trap — a fourth KBA, a different cause

A fourth fix KBA documents a failure mode that shows up independently of the activity-indicator parameters: KBA 3731553 covers a GSTR3B run in "Run Statutory Reports" that throws "reports are not completed for earlier period(s)". The KBA states the cause directly, in its own Symptom text, not just the error string: the run fails "as the previous reporting task has not been completed." The fix is procedural: mark the prior period's task complete, and maintain the "Use as of" date per SAP Help Portal's "Setting Up the GSTR3B Report" page. This KBA's public preview carries no visible version date and never mentions 2608 or 2708 — assume it can fire on either report version, pending confirmation, rather than asserting it does.

This is a check inside SAP's own task tracking, not the GST portal's sequential-filing rule — don't conflate the two. But they can compound in a different way than SAP's own error suggests: if a half-finished migration leaves a period genuinely unfiled on the GST portal, the portal applies its own bars, independent of anything SAP's task tracker shows. You can't furnish a later GSTR-1 while an earlier period's GSTR-1 is outstanding (Section 37(4), CGST Act), and you can't furnish it while the preceding period's GSTR-3B is unfiled either (Rule 59(6)(a)–(b), CGST Rules). Your next GSTR-2B won't generate until the previous period's GSTR-3B is filed, per GSTN's advisory of 16 November 2024 on GSTR-2B and IMS. None of this is SAP's task-completion flag — it's the periods genuinely not having been filed on the portal in sequence.

What the KBAs don't confirm — and what's the research framing, not SAP's text

It's tempting to assume the new GSTR1/3B/6 reports simply add capability the legacy ones lacked — a finer HSN split on outward supplies, or validations the legacy screens didn't run. None of the six KBAs cited in this article state that (for KBA 3786072, in its public preview — the full text is behind SAP for Me login). They document the deprecation (two KBAs, of which only 3780253 gives the release timeline) and four specific error fixes; they say nothing about Table 12 B2B/B2C HSN reporting, about any GSTR-1A linkage, or about HSN reporting-phase changes. Any claim along those lines — including anything you read elsewhere framing this migration as a feature upgrade — should be treated as unverified and checked against the actual New GSTR1/GSTR3B/GSTR6 report documentation on SAP Help Portal, not assumed from the deprecation notice. What the KBAs do establish is narrower and, for a migration plan, more useful: the legacy activity disappears on a fixed timeline, two specific config parameters gate the interim workaround for GSTR1 and GSTR3B respectively, and an unrelated task-completion check can independently block a run.

The same caution applies to the "Manage Tax Items for Legal Reporting" line in KBA 3780253. It states only that the activity "will not be available for the new India GST Reports" — it does not say what replaces that workflow, if anything, inside the new report screens. If your current close process leans on that activity to adjust individual tax line items before submission, confirm with SAP (or your implementation partner) what the New GSTR1/3B/6 equivalent is before you're relying on it mid-period. Don't assume it's a like-for-like swap just because the KBA names a successor report — the KBA is silent on that specific screen.

A migration sequence that doesn't double-count or drop a period

Because the two activity-indicator parameters are maintained per reporting entity — and SAP KBA 3673309 states that "multiple business places are not supported for the same reporting entity in the India GSTR statutory report" — a company code whose registrations each sit on their own business place may not have to cut over all of them on the same day. Confirm in SAP Help's "Setting Up the GSTR1 Report" / "Setting Up the GSTR3B Report" pages before relying on a staggered per-GSTIN cutover as a plan rather than a possibility:

  • Inventory first. List every reporting entity still running IN_GSTR1_DCL, IN_GSTR3B_DCL or IN_GST_GSTR6, and which release wave each landscape (sandbox, quality, production) is currently on relative to 2608 and 2708.
  • Rehearse the 2708 upgrade in a non-production system, not just 2608. Many Public Edition tenants already have 2608 — the live risk ahead is 2708, when the legacy definitions stop functioning outright. KBA 3796537's stuck-run symptom and KBAs 3796247/3700912's missing-activity symptom are config gaps a sandbox run will surface before a live filing period depends on it.
  • If you must stay on legacy for now, maintain the interim parameter for that report only — IN_GSTR1_NEW_ACTY_IND or IN_GSTR3B_NEW_ACTY_IND, in SSCUI 101071, with a Valid-From date and blank Low/High. This is, in SAP's own words, "an interim option for those who need to continue with the legacy GSTR1 reporting activities" — not a migration step.
  • Move to the new reports, as SAP recommends. KBA 3796537 states it is "recommended to migrate to and use the new GSTR1 reporting activities introduced with release 2608." Confirm your SAP Document and Reporting Compliance, Cloud Edition license first (KBA 3780253) — the new reports need it.
  • Close out every open reporting task before cutover. KBA 3731553's error fires on an incomplete earlier period; assume it can fire on either report version, pending confirmation, and clear that backlog first so it can't collide with a mid-migration cutover.
  • Migrate one reporting entity at a time where you run several GSTINs, and reconcile the period it crosses by hand rather than trusting that a partially-migrated landscape counted it once. None of the six KBAs' public text documents what happens when a legacy and a new run both exist for overlapping periods — reconcile the switch-over period by hand rather than assuming SAP's screens will catch a double-count or a drop for you.

None of this changes what each GSTIN still owes the portal. Whichever report version generates your GSTR-1 and GSTR-3B numbers inside SAP, your actual GSTR-2B and the credit it supports are decided on the GST portal, invoice by invoice (Rule 60(7); Rule 36(4) as substituted w.e.f. 1 January 2022) — and a migration that drops or double-counts a period inside SAP is a gap between your books and the portal. SAP's own inward GSTR-2B reconciliation still hands Partial and Probable Matches back to a person, and it only sees the ITC side — same as any other mismatch there. It's also a separate question from whether your e-invoicing setup is attaching the right GSTIN to every IRN in the first place — a report-version gap and an e-invoicing GSTIN error don't cancel each other out, they stack.

Finding the exact period and invoices a half-migrated report run missed or duplicated — reconstructing it invoice by invoice against what the portal actually has on file — is painful to do manually. On the input-tax-credit side, whichever SAP report version produced the number, Recoup reconciles your books against IMS and GSTR-2B for every GSTIN, invoice by invoice, so you can see which credits you claim are actually in your 2B. An outward GSTR-1 gap is a different check — books against what you filed — and an inward IMS/2B reconciliation won't surface it.

Know every invoice your claimed ITC rests on, SAP report version aside

Recoup reconciles your books against IMS and GSTR-2B for every GSTIN, invoice by invoice, and names the vendor behind every gap before you file.

Book a demo →

Related guides