How-to · SAP multi-GSTIN tax GL determination

SAP picked the OB40 dummy GL, not your business-place tax GL — and your GSTR-3B won't tie to the GL until someone notices

The short answer

Per SAP's own KBAs, GST tax accounts in a multi-GSTIN company code are meant to come from J_1IT030K_V, the India view that assigns a tax GL by chart of accounts, transaction key, tax code and business place. When that determination doesn't happen, the account maintained in OB40 is used instead — KBA 2460396 documents this on outbound GST billing documents and KBA 2500703 on FBCJ cash-journal postings, and KBA 2420891 documents the FB60/MIRO case, with error FF709 from missing business-place-wise GL determination and the wrong GL being selected. A missing J_1IT030K_V entry is one documented cause, not the only possible one, and each KBA's full cause and resolution sits behind SAP's login.

If you run more than one GSTIN out of one SAP company code, SAP is supposed to post input and output GST to a tax GL account that's specific to the business place — not a single shared account. Three of SAP's own knowledge base articles describe the same failure mode across three different posting paths: the system quietly falls back to the dummy GL maintained in OB40 instead.

Three SAP knowledge base articles, one symptom

SAP has published separate KBAs for the same symptom on three different posting paths — the tax account isn't determined by business place:

SAP KBAWhere it shows upWhat SAP's own symptom text says
2460396Outbound GST invoice (billing document)"The system chose OB40 GL in Invoice rather than table J_1IT030K_V."
2420891Invoice processing — FB60, MIRO"Business place wise GL account determination is missing for Chart of Account and transaction key, which is to be maintained mandatorily in case of GST." Error FF709 ("Error in account determination: table & key & & &") on FB60 and MIRO "because of above missing configuration"; or "When posting an invoice, system selected the wrong GL."
2500703FBCJ (cash journal posting)"Business Place wise GL Determination not happening while FBCJ." "Tax account is wrong in the accounting document: Tax account from OB40 is used instead of J_1IT030K_V."

The full cause-and-resolution text for all three sits behind SAP's support-portal login (SAP for Me), so treat the configuration direction below as the documented shape of the fix, not a transcription of SAP's internal steps — confirm the exact IMG path against the live note for your release before you change anything in a production client. These previews are symptom-level (retrieved 5 November 2026) and don't establish that all three share one cause. Only 2420891's preview names one, missing business-place-wise GL determination. The other two list different objects in their keywords — 2460396 the condition-type field T685A-KNTYP, 2500703 the function modules FCJ_CHECK_FWBAS and J_1IG_DETERMINE_PASS_BUPLA — so the fix on those paths may involve more than a J_1IT030K_V entry.

Why SAP even has a business-place-specific tax GL

SAP's GST India localisation determines the tax account from table J_1IT030K_V (the maintenance view over India localisation table J_1IT030K), keyed by chart of accounts, transaction key, tax code and business place together. OB40 is the standard, country-independent tax-account-determination transaction (table T030K) — it knows transaction key and tax code, not business place. SAP's design makes the business-place-aware table the first lookup and OB40's account the fallback when that lookup has nothing to return. KBA 2420891's symptom text says business-place-wise GL determination is "to be maintained mandatorily in case of GST," so the fallback is a failure, not a harmless default: the GL that comes out of OB40 isn't wrong in the sense of being invalid — it's wrong because one shared account is standing in for what should be several business-place-specific ones.

That design exists because, in SAP, business place is how a company code represents a GSTIN. One company code with operations across states typically carries one business place per registration. Keeping each business place's GST on its own GL account is what lets the general ledger answer "what GST did registration X report" without reconstructing it from a tax-code filter after the fact.

What actually breaks when the fallback fires

Whenever business-place determination fails on one of these paths (a missing J_1IT030K_V entry is the cause 2420891 names), GST lands in the OB40 account instead of the business-place-specific one, and the KBAs' symptoms describe documents that posted that way with no error: the posting succeeds, the amount is correct, only the account is wrong. KBA 2420891 ties the visible error (FF709) to the same missing configuration, but a silent misroute is the more dangerous case precisely because nothing flags it.

The downstream effect is a general ledger that no longer segregates by registration. If your company code holds three business places for three GSTINs and the tax GL for all three collapses into the OB40 dummy account, the GL balance for that account is now input or output GST for three registrations, blended. Each GSTIN still files its own GSTR-3B and still has its own electronic credit ledger — that doesn't change on the GST-portal side. What changes is that your SAP general ledger can no longer be trusted to tell you, account by account, which registration's filed numbers it's supposed to tie to. Tying a specific GSTIN's Table 3.1 outward liability or Table 4 ITC claim back to "the GL account that's supposed to hold that registration's GST" stops being a lookup and becomes an allocation exercise — someone has to re-split the blended account back out by invoice before the GL-to-return tie-out means anything.

This is a GL-segregation problem inside SAP; it does not change what each registration files. Under Section 25(4) of the CGST Act, a person with more than one registration, "whether in one State or Union territory or more than one State or Union territory", is treated as a distinct person "in respect of each such registration". Each regular registration therefore furnishes its own GSTR-3B (Section 39(1), Rule 61(1)) and has its own electronic credit ledger (Section 49(2), Rule 86(1)). What the misroute costs depends on how you build the return. If each GSTIN's GSTR-3B is prepared from document-level reports keyed on business place, the return can be right while the GL is wrong. If it is prepared from tax-GL balances, a blended account can move one registration's input tax credit into another registration's return, but a supplier invoice addressed to one GSTIN is communicated only in that GSTIN's GSTR-2B (Rule 60(7)), and credit needs that communication (Section 16(2)(aa) read with Rule 36(4)).

How to tell you're hitting this before month-end finds it for you

  • Visible signal: error FF709 ("Error in account determination") on FB60 or MIRO, per KBA 2420891 — this one at least stops the posting and gets noticed.
  • Silent signal: a multi-business-place company code where the OB40 dummy GL account carries a non-trivial, growing balance across periods. If that account is supposed to be a placeholder and it isn't staying near zero, GST that should have gone to a business-place-specific account is landing there.
  • Confirming it's this specific cause: pull the FI document for a recent invoice, note the business place and the tax code on the line item, then check table J_1IT030K_V (maintained through SM30) for an entry matching that exact chart-of-accounts/transaction-key/tax-code/business-place combination. No matching row is the signature of this fallback. If the line item carries no business place, or the wrong one, the table isn't your problem — SAP KBA 2448047 separately documents "Wrong business place is getting populated while posting incoming invoice." If a matching row exists and the OB40 account still posted, the cause is elsewhere; open the full KBA for that posting path.

The documented fix, and what to confirm before you touch it

SAP's own KBA titles state the direction plainly — 2420891 is literally titled "GST India: Maintenance of Business Place wise GL Determination." For the FB60/MIRO case, KBA 2420891's title and symptom give the direction — maintain the missing combination of chart of accounts, transaction key, tax code and business place in J_1IT030K_V, so the business-place-aware lookup has an entry to return before OB40's fallback fires. For billing documents (2460396) and FBCJ (2500703), the public previews don't show the resolution; the J_1IT030K_V entry is necessary but may not be sufficient. Keep OB40's own dummy GL maintained too — SAP's design still uses it as the catch-all for any combination you haven't (or shouldn't need to) enter in J_1IT030K_V.

Before you touch config in a live client: open the current text of KBA 2420891 (and 2460396 or 2500703, depending on which posting path you're fixing) through your own SAP for Me login — the full cause-and-resolution steps, including any release-specific caveats, sit behind that login and this article isn't reproducing them. Separately, SAP KBA 3513669 announces that the Digital Compliance Service for India — SAP's GST reporting service on BTP Neo — will be deprecated effective 31 December 2027, with GST reporting planned in SAP Document and Reporting Compliance (as of November 2026); its public preview says nothing about J_1IT030K_V or OB40.

Where this leaves the GST reconciliation, not just the GL

Fixing J_1IT030K_V stops new postings from blending registrations. It does nothing for GST that already landed in the OB40 fallback account in a prior period — that has to be identified invoice by invoice and reclassified, the same kind of invoice-level work SAP's own GSTR-2B matching screens hand back to a person rather than resolving automatically. And it's a separate problem from whether your e-invoicing setup is generating IRNs under the correct GSTIN in the first place — a business place that's wrong in both places compounds, not cancels.

Re-splitting a blended tax GL account back to the business place — and GSTIN — it actually belongs to, across however many periods it went unnoticed, invoice by invoice, is exactly the kind of work that's painful to do manually: it's not a formula, it's a judgment call on each line, repeated for every misrouted posting. Recoup reconciles your books against IMS and GSTR-2B for every GSTIN, invoice by invoice, so you know which registration each credit belongs to before you file — the per-registration record a re-split has to start from. The reclassification itself still happens in SAP.

Know which GSTIN every credit belongs to before you file

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