How-to · SAP stock transfers (STO)

Your own IGST, sitting unclaimed — because SAP never finished posting the other half of the stock transfer

The short answer

SAP KBA 3233315 documents error J_1IG_MSGS006 ("No data for the selection criteria") when an inbound GST invoice is posted or displayed in transaction J_1IG_INV; KBA 2435112 lists more than a dozen other J_1IG_INV errors. Their causes and fixes sit behind an SAP login, and this guide does not guess at them. Whatever the cause, until the inbound GST invoice posts, the IGST from your own interstate stock transfer sits in GSTR-2B with no ledger entry claiming it.

A stock transfer between two plants under different GST registrations isn't a free internal move — it's a deemed supply, with a real tax invoice and a real input tax credit at the other end. SAP posts that credit through a second, separate transaction, J_1IG_INV. When that step errors out — and SAP's own knowledge base lists a long, ordinary list of ways it can — the IGST you charged yourself keeps showing up in your own GSTR-2B. Nobody ever claims it in the books.

An interstate stock transfer isn't a free move — it's a supply, with its own invoice

Move goods from your Maharashtra plant to your own Karnataka plant and nothing has been sold to anyone outside the company. Under GST law that doesn't matter. Schedule I, para 2 of the CGST Act treats a supply of goods between distinct persons as specified in section 25 as a supply even without consideration, when made in the course or furtherance of business — and section 25(4) makes two registrations under one PAN "distinct persons," whether they sit in different States or are simply two registrations within the same State. A stock transfer order (STO) between two plants carrying different GSTINs is exactly that: not a loan of goods to yourself, a deemed supply to a separate taxable person who happens to share your PAN.

That has a direct, practical consequence: because section 15(1)'s ordinary transaction value is unavailable between related or distinct persons, value falls to Rule 28(1) of the CGST Rules — open market value, then the value of goods of like kind and quality, then Rules 30/31 in that order, with the sending plant free to opt (first proviso) for 90% of the price the receiving plant charges an unrelated customer for like goods, where the goods are intended for further supply as such. For taxable goods, a genuine deemed supply also means a genuine tax invoice under section 31(1) is due at or before removal (exempt goods take a bill of supply under section 31(3)(c) instead) — and Rule 55(1)(c)'s delivery-challan route covers transportation of goods "for reasons other than by way of supply", which this is not, so there's no challan escape here. One stock transfer, one outbound GST invoice, charging real IGST (or CGST/SGST if both GSTINs sit in the same State — unless one of them is an SEZ unit or developer, since the proviso to section 8(1) of the IGST Act never treats a supply of goods to or by one as intra-State) — and, because it's a real invoice between two real GSTINs, one matching credit sitting at the other end, same as any vendor bill.

SAP posts that credit through a second, separate transaction

In SAP the workflow has two halves: one outbound GST invoice at the sending plant, and a second step at the receiving plant — what SAP's KBAs call the inbound GST invoice — to record the matching credit in the books. On the classic side that second step is transaction J_1IG_INV; on S/4HANA Cloud Public Edition it's the app "Create Inbound Invoice for STOs – India" — SAP's own KBA on reversing it (3755777) treats the two as one process, pointing app users to "the journal entry that corresponds to the inbound GST invoice created via J_1IG_INV" even when it was the app, not the transaction code, that created it. Either way, this inbound invoice is what posts the FI document — the actual GL entry that puts the IGST your sending plant charged into the receiving plant's input tax credit in the books, not just on the GST portal.

That second step is also the one that can simply not happen. The outbound side — the delivery, the GST invoice, the GSTR-1 filing — can complete cleanly while the inbound side errors out, gets skipped, or never gets run at all.

Where it breaks: five KBAs, three documented failures — not one shared cause

SAP's own support knowledge base carries a specific KBA for the exact error in this article's title, two more for other J_1IG_INV failures, and two How-To KBAs — one on the overall STO process, one on reversing and recreating an inbound invoice. Four of the five are login-gated previews that stop at the title and symptom — the cause and resolution sit behind an SAP S-user login, and this article has not read them and does not claim to know what they say. Treat the three failure KBAs as separately-documented ways the inbound invoice can fail, not one diagnosis with three names (previews as fetched on 13 November 2026):

SAP KBAWhat SAP's own preview actually showsCause/resolution visible?
3233315Transaction J_1IG_INV throws "No data for the selection criteria (J_1IG_MSGS006)" when posting or displaying an inbound GST invoice.No — preview ends at the symptom; login required.
2435112A list of common J_1IG_INV errors SAP documents together: fiscal year not allowed, a required balancing field not filled, tax code or vendor number not transferred to the accounting interface, a G/L account not defined in the chart of accounts, a payment-terms field missing on a G/L account, a syntax error in SAP include J_1IG_STO_GET_DATA for the VBFA document-flow table, a transaction key or condition type that doesn't exist, and — again — "no data for the selection criteria."No — preview ends at the symptom list; login required.
2849505J_1IG_INV can create a duplicate inbound invoice for the same outbound invoice when two users (or two parallel sessions of the same user) post against it at the same time.No — symptom only; login required.
2916747Title only: "GST IN : Inter-Company STO Process in India" — a How-To whose preview shows just the one-line symptom "How to Carryout Inter-Company STO in India" (Materials Management; SAP ERP / S/4HANA). The preview doesn't say whether it covers transfers between two GSTINs of the same company.No — a How-To; its procedure is login-gated.
3755777Public, not login-gated: how to reverse and recreate an inbound GST invoice that was already created — see below.Yes, in full (its Cause section is blank).
Don't read five KBAs on the same transaction as five confirmations of one root cause. SAP's own previews name different objects for different errors — a missing G/L account assignment is not the same failure as a VBFA lookup syntax error, and neither is the same as two users racing to post the same outbound invoice. The honest statement is "J_1IG_INV fails in several independent, SAP-documented ways," not "J_1IG_INV has one bug." If your own error message matches one of the first three rows, that KBA number is where to start — not a general assumption that fixing one fixes all.

The one fully readable KBA: reversing and recreating an inbound invoice that did post

KBA 3755777, "How to Reverse and Recreate Inbound GST Invoice for STO – India," is the one SAP KBA in this group that isn't gated behind a login. It is written for SAP S/4HANA Cloud Public Edition, for a user who has created an inbound invoice in the app and wants to cancel it and run it again — so it applies when an inbound invoice posted and needs redoing, not when J_1IG_INV never posted one (for that, start from the KBA that matches your error message). Its resolution, in order:

  1. Open the Reverse Journal Entries app.
  2. Locate the journal entry that corresponds to the inbound GST invoice created via J_1IG_INV (from the STO process), and post the reversal for it.
  3. Return to Create Inbound Invoice for STOs – India.
  4. Re-enter the same selection parameters as the original run — company code, sending plant and receiving plant; Invoice Type JSTO, with Display and GST Invoice selected; the GST outbound invoice number; and its creation date.
  5. Run the selection and choose Create Inbound GST Invoice again.
  6. If any error occurs during the reversal or the re-creation, capture the exact message and repeat the steps to verify the reversal is posted before attempting re-creation.

Why "it'll show up eventually" is the wrong assumption

The failure here is entirely on your side of the books — not on the GST portal's. The sending plant's GST invoice was real, and its GSTR-1 filing already carried it; that invoice lands in the receiving GSTIN's GSTR-2B the same way any supplier's invoice would, whether or not SAP ever successfully posts the inbound side. Section 16(2)(aa) and Rule 36(4) make that 2B entry a precondition for claiming the credit (one of several cumulative conditions in section 16(2), alongside actual receipt of the goods under section 16(2)(b), which matters for stock still in transit) — but 2B showing it as available is not the same as your general ledger showing it as claimed. A J_1IG_INV error doesn't stop the credit from appearing on the portal; until it's fixed, it stops your books from recording that you took it.

That gap doesn't resolve itself by waiting. GSTR-2B itself is not a static, one-time feed — it drafts on the 14th, and under IMS a record you never act on is simply deemed accepted into it regardless of whether your own FI document exists (GSTN portal behaviour as of 13 November 2026). Nothing in that mechanism checks your SAP postings. Left alone, a stranded STO credit is either never claimed — real money, quietly given up, as the Input Tax Credit cut-off in Section 16(4) (30 November after that financial year ends, or the annual return's filing if earlier) keeps approaching on that year's invoices — or claimed anyway, off the 2B figure, by someone matching the portal total without a matching GL entry behind it. The second path is worse: it closes GSTR-3B clean while leaving a book-to-return gap that a GSTR-9C reconciliation, or an auditor, finds later — at which point it reads as a discrepancy, not as a known, named SAP error with its own KBA number.

Finding it before it becomes a year-end problem

One way to find a stranded STO credit is to pull two lists and compare them: every outbound STO invoice your sending plants issued for the period, against every inbound GST invoice your receiving plants actually posted through J_1IG_INV or the Fiori app — then checking which outbound invoices have no matching inbound posting at all, GSTIN by GSTIN, period by period. For a company running more than a handful of plants across States, that's genuinely painful to do by hand every single filing cycle, and it's exactly the kind of invoice-level gap that's easy to miss precisely because GSTR-2B never flags it — the credit is sitting there looking perfectly normal.

Recoup doesn't touch SAP's J_1IG_INV posting itself — that's SAP's own transaction to fix, per the KBAs above. What Recoup is built for is the comparison: your books against your GSTR-2B and IMS, invoice by invoice, so a credit that's present on the portal but never shows up as claimed in your books gets named before Section 16(4)'s 30 November cut-off time-bars it. As of November 2026, Recoup's documented connections are Zoho Books, Tally, bank statements and the GST portal, so confirm how your SAP data would get in before relying on it.

Don't let your own stock transfers become unclaimed credit

Recoup reconciles your ITC against GSTR-2B continuously and names the exact invoice behind each gap it finds — including the ones your own plants created.

Book a demo →

Related guides