Why Are My Two GSTINs Showing Different ITC Amounts?

You pulled the August GSTR-2B for both your GSTINs on the fifteenth of September. Karnataka shows Rs 8.4 lakh in eligible input tax credit. Maharashtra shows Rs 3.2 lakh. Same legal entity, same PAN, same shared vendor master. Purchase volumes across the two states are within a plausible range of each other. Where did the Rs 5.2 lakh gap come from — a misallocation between branches, a vendor who filed against the wrong GSTIN, an e-invoice IRN that got tagged wrong, or a compliance artefact that the controller had never fully mapped?

The finance manager wants an answer before signing off Table 4 of both GSTR-3Bs on the twentieth. Something is uneven — but which portion is by design, and which portion is worth chasing?

The quick answer

Every rupee of ITC-total difference between two GSTINs of the same legal entity almost always decomposes into one of six buckets: Place of Supply under Section 10 or Section 12 of the IGST Act routed the tax leg to a specific state; a vendor filed GSTR-1 against the wrong GSTIN of your PAN; an e-invoice IRN was tagged to a specific GSTIN and cannot be re-routed after the 24-hour cancellation window; a branch-transfer invoice between the two GSTINs applied Rule 28 valuation inconsistently; the Input Service Distributor mechanism distributed common-input-service credit in the wrong ratio; or Rule 42/43 common-credit apportionment computed different reversals for the two GSTINs because turnover-in-the-State differs per registration.

Only Buckets 2, 3, and 5 involve actual misallocations that need correction. Buckets 1, 4, and 6 are by-design divergences that need documentation rather than chase. The finance team’s job during the reply window is to classify each rupee into the right bucket, escalate the misallocation subtotals, and move the by-design subtotals out of the chase queue.

Section 25(4) is the reason the two GSTINs cannot be consolidated

Before working through the six buckets, remember why the two GSTINs even have separate ITC ledgers. Section 25(4) of the CGST Act treats every GSTIN as a distinct person, even where the two GSTINs belong to the same legal entity and the same PAN. Karnataka’s ITC ledger cannot offset Maharashtra’s output tax, and vice versa. Each GSTIN files its own GSTR-1, its own GSTR-3B, and has its own GSTR-2B auto-populated by the portal. The multi-GSTIN reconciliation has to run per-GSTIN, and any consolidation at the entity level is a management-reporting view rather than a compliance view — which is exactly why the two totals diverge in ways that a single-GSTIN reconciliation flow does not surface.

The pillar-level treatment of GSTR-2B reconciliation sets out the general framework; the multi-GSTIN case is where the framework fans out into the six state-specific buckets below.

Bucket 1 — Place of Supply routed the tax leg to the specific state

Under Section 10 of the IGST Act, the Place of Supply for goods is the location where the movement of goods terminates for delivery to the recipient. Under Section 12, the Place of Supply for services with a registered recipient is the location of the recipient. A vendor in Karnataka supplying goods to the Karnataka GSTIN — same state — treats it as intra-State and charges CGST plus SGST. The same vendor supplying identical goods to the Maharashtra GSTIN — different state — treats it as inter-State and charges IGST at the same combined rate. The tax lands in the state-specific GSTIN’s credit ledger.

Illustrative arithmetic on the Rs 5.2 lakh Karnataka-vs-Maharashtra gap — Rs 2.1 lakh is a pure Bucket 1 case. Two national vendors located outside both states billed the Karnataka GSTIN with IGST that landed in the Karnataka ledger; the same two vendors billed the Maharashtra GSTIN with IGST that landed in the Maharashtra ledger. The volumes were different because the Karnataka branch bought more from these two vendors this month. This bucket is not a leak — it is the design of the tax regime. Document it in the working paper and move on.

What to do. Build a Place of Supply reference sheet for the top 50 vendors by spend across the shared vendor master. Any vendor billing both GSTINs where the tax leg splits into IGST for one and CGST plus SGST for the other is a Bucket 1 signature.

Bucket 2 — the vendor filed GSTR-1 against the wrong GSTIN

A vendor supplying the Maharashtra GSTIN reported the invoice on GSTR-1 against the Karnataka GSTIN by mistake — either the AR desk quoted the wrong GSTIN on the tax invoice at billing time, or the correct GSTIN was on the invoice but was mis-keyed on the GSTR-1 upload. The invoice appears in the Karnataka GSTIN’s GSTR-2B (where it does not belong) and does not appear in the Maharashtra GSTIN’s GSTR-2B (where it does).

The fix is a Table 9A amendment on the vendor’s next available GSTR-1, which shifts the invoice from Karnataka’s GSTR-2B to Maharashtra’s GSTR-2B in the tax period the amendment lands. If the Karnataka GSTIN already claimed the ITC in the current-month GSTR-3B, the claim needs reversing via Form DRC-03 with interest under Section 50 at 18 per cent per annum from the claim date to the reversal date. The Wave 1 walkthrough of the GSTR-2B versus purchase register gap covers the mirror case of an invoice missing from a single GSTIN — the multi-GSTIN version is that mirror plus a wrong-GSTIN appearance somewhere else in the same PAN.

Illustrative arithmetic — Rs 0.9 lakh of the Rs 5.2 lakh gap is a Bucket 2 case. Three invoices from a national IT vendor appeared in Karnataka’s GSTR-2B; the underlying supply was to the Maharashtra branch and the invoice quoted the Maharashtra GSTIN correctly. The vendor’s GSTR-1 filing team fat-fingered the recipient GSTIN.

What to do. Extract every invoice in the wrong GSTIN’s GSTR-2B against the shared vendor master and route to a supplier-side chase register for Table 9A amendments. Track the two-month drift and the working-capital cost.

Bucket 3 — the e-invoice IRN was tagged to the specific GSTIN

Under Rule 48(4) of the CGST Rules, the e-invoice IRN is generated against the specific recipient GSTIN quoted on the invoice at IRN generation time. An IRN generated against the Karnataka GSTIN cannot be re-tagged to the Maharashtra GSTIN through a later amendment. The correction inside the 24-hour cancellation window is straightforward — the supplier cancels the wrong-GSTIN IRN and issues a fresh IRN against the correct GSTIN. Beyond the 24-hour window, the correction has to run through a credit note against the wrong GSTIN and a fresh tax invoice against the correct GSTIN — a two-document transaction that lands in the wrong-GSTIN’s GSTR-2B first and reverses only in the following tax period.

Illustrative arithmetic — Rs 0.5 lakh of the gap is a Bucket 3 case. One high-value capital-goods invoice was IRN’d against Karnataka on the twenty-eighth of July; the underlying delivery was to the Maharashtra plant. Discovery happened on the third of August, past the 24-hour window. The supplier issued a credit note against Karnataka and a fresh IRN’d tax invoice against Maharashtra — the correction sits across two tax periods.

What to do. For any Bucket 3 IRN tagged wrongly, escalate to the e-invoice compliance owner. If the discovery is inside 24 hours, force the supplier cancellation; if beyond, run the credit note plus fresh invoice cycle and track the reversal impact on the wrong-GSTIN’s DRC-03.

Bucket 4 — the branch-transfer valuation under Rule 28

Any supply between the two GSTINs of the same PAN is a taxable inter-branch supply under Section 25(4). Rule 28 fixes the valuation — open market value, or the value of like-kind-and-quality goods where open market value is not determinable, or Rule 30/31 fall-back. The proviso to Rule 28 states that where the recipient is entitled to full ITC, the value declared in the invoice shall be deemed to be the open market value.

This is where multi-GSTIN divergences most often surface as valuation gaps. The Karnataka GSTIN transfers stock to Maharashtra and invoices at Rs 40 lakh; the Maharashtra GSTIN books the receipt at Rs 42 lakh because the Maharashtra branch controller applied a different open-market-value methodology on the exact same goods. The tax on the branch-transfer invoice runs on Rs 40 lakh (the invoiced value); the receiving-branch ledger runs on Rs 42 lakh (the booked value). The ITC in Maharashtra’s GSTR-2B ties to the Rs 40 lakh invoice, not the Rs 42 lakh booking.

Illustrative arithmetic — Rs 0.6 lakh of the gap is a Bucket 4 case. Two branch-transfer invoices in the month applied the invoice-value-equals-open-market-value deeming provision inconsistently across the two branches. Both branches had full ITC entitlement, so the proviso holds — but only if the deeming is applied at both ends.

What to do. Document the Rule 28 valuation policy in a single reference note signed off by both branch controllers. Every branch-transfer invoice reconciles against the policy before the receiving branch books the receipt.

Bucket 5 — the ISD distribution under Section 20

Common input services — audit fees, legal fees, corporate insurance, ERP AMC, group insurance policies — must flow through the Input Service Distributor mechanism from 1 April 2025 under Notification 16/2024-Central Tax read with the Finance (No. 2) Act 2024 amendment to Section 20. Before 1 April 2025, the head office had a choice between ISD and cross-charge under Circular 199/11/2023-GST; on or after that date, ISD is compulsory for common input services and cross-charge continues to apply only for internally generated services between distinct persons.

The ISD GSTIN receives the vendor’s tax invoice, distributes the credit to each recipient GSTIN in the ratio of the preceding financial year’s turnover, and files GSTR-6 by the thirteenth of the following month. The recipient GSTINs see the distributed credit in their GSTR-2B under the ISD-inward table, not the regular inbound-supply table. A common-input-service invoice that should have flowed through ISD but went through cross-charge (or vice versa) is a Bucket 5 misclassification that appears as an unexplained gap in the multi-GSTIN comparison.

Illustrative arithmetic — Rs 0.7 lakh of the gap is a Bucket 5 case. The Rs 8 lakh annual ERP AMC invoice was received centrally and distributed via ISD in the previous-year turnover ratio of 65:35 for Karnataka:Maharashtra. The Karnataka GSTIN correctly picked up Rs 5.2 lakh in the ISD-inward table; the Maharashtra GSTIN’s Rs 2.8 lakh landed in a subsequent GSTR-6 cycle and did not appear in the August GSTR-2B pulled on the fifteenth. Timing rather than misallocation — but the working paper has to distinguish the two.

What to do. Add an ISD reconciliation as a separate line to the multi-GSTIN working paper. Verify every common-input-service invoice against the GSTR-6 filing and the turnover-ratio distribution.

Bucket 6 — Rule 42/43 common-credit apportionment

Where a GSTIN makes both taxable and exempt supplies, Rule 42 (for inputs and input services) and Rule 43 (for capital goods spread across 60 tax periods) require the common credit to be apportioned. The formula D1 = E divided by F multiplied by C2 turns on F — the total turnover in the State during the tax period — which is per-GSTIN under Section 25(4). If Karnataka has a materially different exempt-supply exposure from Maharashtra (a state-specific customer mix, a state-specific product line, a state-specific service export), the D1 common-credit reversal computes to different values in the two GSTINs and the eligible-ITC subtotals diverge as a natural consequence.

Illustrative arithmetic — Rs 0.4 lakh of the gap is a Bucket 6 case. Karnataka has a small pharma-export line that runs zero-rated with a higher D1 reversal on common credit; Maharashtra is purely taxable domestic and carries no D1 reversal. The Rule 42 mechanism computed the two D1 subtotals correctly at Rs 0.4 lakh and Rs 0.0 lakh — a design divergence that a controller-level policy note can document and defend against a Section 74 look-back.

What to do. Escalate the Bucket 6 calculation to the controller. The audit-materiality of the common-credit reversal is high and the calculation needs sign-off at the reviewer level rather than at the tax-executive level.

Which bucket to escalate first

Bucket 3 — the e-invoice IRN mis-tagging — is the only one of the six with a same-period rectification window (the 24-hour supplier cancellation) that closes hard. Every hour past discovery inside the 24-hour window that goes unused pushes the correction into a credit-note-plus-fresh-invoice cycle that spans two tax periods and carries a working-capital drag. The bucket 3 sweep should therefore run first — extract every current-month e-invoice IRN against the shared vendor master, verify the recipient GSTIN, and escalate any wrong-GSTIN IRN inside the discovery-plus-24 window.

Bucket 2 (vendor mis-filing) is the largest subtotal in most cases and the second-priority escalation because Table 9A amendments have a two-month drift and the receiving GSTIN’s cash-flow position is exposed until the amendment lands. Buckets 1, 4, 5, and 6 are documentation-and-defensibility work rather than chase work — they need to be classified and signed off before the twentieth so that Table 4 of both GSTR-3Bs can be filed with a defensible audit trail against a future Section 74 look-back.

Where the Section 16(4) time bar still applies

Every ITC line at issue in Buckets 2, 3, and 5 runs against the same Section 16(4) permanent-loss deadline as the single-GSTIN case — the ITC has to be availed in a GSTR-3B filed by the thirtieth of November following the financial year of the invoice date, or it is written off with no recovery route inside the regime. A Bucket 2 vendor-mis-filing case that drifts through the Table 9A amendment cycle for four months and lands in the correct-GSTIN’s GSTR-2B in the following FY has crossed the cliff on that side; a Bucket 3 e-invoice IRN correction that spans two tax periods and slips past November 30 loses the credit on the receiving-branch side. The multi-GSTIN reconciliation adds two-branch complexity to the same cliff — the escalation timeline reverse-calculated from November 30 for both GSTINs.

The Invoice Management System actions taken by either branch (Accept, Reject, Pending) further compound the reconciliation because IMS operates per-GSTIN and an action taken at Karnataka does not surface at Maharashtra — the multi-GSTIN working paper has to consolidate both GSTINs’ IMS action logs alongside the six-bucket classification.

The multi-GSTIN working paper that makes this repeatable

Working through the six buckets manually the first time takes the better part of a working day for a two-GSTIN entity; the same discipline for a four- or six-GSTIN entity crosses the point where it stops being a manual exercise. Terra Insight’s free three-way ITC workbook extends naturally to the multi-GSTIN case — add the recipient GSTIN as a mandatory column on every invoice line, pull the GSTR-2B for every GSTIN on the same date, merge into a single working paper keyed on invoice number plus supplier GSTIN plus recipient GSTIN, and run the six-bucket classification across the merged view.

When the manual match stops holding

The manual six-bucket classification holds for a mid-market finance team up to roughly two or three GSTINs and roughly 200 active suppliers per GSTIN. Above that scale — four or more GSTINs, common-input-service ISD volumes across five or more categories, or exempt-supply exposures in three or more states triggering Rule 42/43 reversals per GSTIN — the multi-GSTIN reconciliation becomes a continuous exception queue rather than a Days 11 to 15 monthly close activity.

At that scale, moving the six-bucket classification and the ISD-plus-Rule-42/43 audit trail onto continuously refreshed detection — where Terra Insight’s GST reconciliation software treats the multi-GSTIN reconciliation as a first-class output with per-GSTIN and consolidated views side by side — is what keeps the multi-branch monthly close inside a twenty-day cadence. Below that scale, the extended three-way workbook is the right tool and the discipline of running the six buckets by hand across the two GSTINs is what builds the reconciler’s judgement for when scale demands the shift.

Go deeper

• Why is my GSTR-2B less than my purchase register? — the single-GSTIN sibling walkthrough
• Section 16(4) ITC time bar — the November 30 permanent-loss deadline that applies per GSTIN
• Invoice Management System reconciliation — the IMS workflow that runs per-GSTIN
• GSTR-2B versus purchase register reconciliation — the pillar-level treatment
• Blocked ITC under Section 17(5) — the classification bucket that carries across all GSTINs
• Three-way ITC workbook — the free download that extends to the multi-GSTIN case
• GST reconciliation software for India

Frequently Asked Questions

My two GSTINs are the same legal entity and same PAN — why is the ITC not just consolidated?

Because Section 25(4) of the CGST Act treats every GSTIN as a distinct person, even where the two GSTINs belong to the same PAN and the same legal entity. Each GSTIN files its own GSTR-1 for outward supplies, its own GSTR-3B for tax payment, and has its own GSTR-2B auto-populated by the portal. The ITC ledger sits inside each GSTIN’s credit ledger separately — Karnataka ITC cannot be used to offset Maharashtra output tax, and vice versa, except through the narrow Input Service Distributor mechanism for common input services. This is the reason the finance team cannot look at company-wide ITC and reconcile to company-wide inbound supply — every reconciliation has to run per-GSTIN, and any consolidation at the entity level is a management-reporting view rather than a compliance view.

The same vendor is billing both my GSTINs. Why does one see IGST and the other CGST plus SGST?

Because Place of Supply under Section 10 of the IGST Act for goods, and Section 12 for services, resolves the tax leg by reference to the recipient’s registered location and the origin of the supply. A vendor located in Karnataka supplying goods to the Karnataka GSTIN — same state — treats the supply as intra-State and charges CGST plus SGST at the combined rate. The same vendor supplying the same goods to the Maharashtra GSTIN — different state — treats the supply as inter-State and charges IGST at the same combined rate. The ITC that lands is the same total value, but it lands as IGST credit for Maharashtra and as CGST plus SGST credit for Karnataka — and the two credits are not fungible across states without invoking the ISD mechanism under Section 20. This is why the same vendor spend across the two GSTINs can produce very different tax-leg splits in the ITC ledger even before you get to any actual misallocation.

The vendor filed GSTR-1 against the wrong GSTIN. How do I get the ITC back?

The vendor has to file an amendment through Table 9A of the next available GSTR-1 to shift the invoice from the wrong recipient GSTIN to the correct one. Once amended, the invoice drops out of the wrong GSTIN’s GSTR-2B in the tax period the amendment lands, and appears in the correct GSTIN’s GSTR-2B in the same tax period. The two-month drift matters — an invoice that appeared in the wrong GSTIN’s July GSTR-2B and gets corrected via the vendor’s September amendment will not show in the correct GSTIN’s GSTR-2B until October. Meanwhile, if the wrong GSTIN already claimed the ITC in the July GSTR-3B, that claim needs reversing via Form DRC-03 with interest under Section 50 at 18 per cent per annum from the July claim date to the reversal date. The alternative — the ITC-availing GSTIN not claiming the ITC at all until the correction lands in its own GSTR-2B — protects against the Rule 88D DRC-01C intimation but pushes a working-capital drag onto the receiving branch.

We just moved onto ISD from 1 April 2025 — how does that change the ITC visibility across our GSTINs?

The move onto Input Service Distributor under Section 20 of the CGST Act, made mandatory by Notification 16/2024-Central Tax read with the Finance (No. 2) Act 2024 amendment, changed the routing of common input services (audit fees, legal fees, corporate insurance, ERP AMC, group insurance policies) from a cross-charge mechanism to a distribution mechanism. Before 1 April 2025, the head office billed each GSTIN for its share of the common input service through a cross-charge invoice under Circular 199/11/2023-GST, and each GSTIN’s GSTR-2B picked up the intra-entity invoice like any other inbound supply. From 1 April 2025, the common input service invoice from the external vendor is received by the ISD GSTIN (a separate registration under Section 24), and the ISD distributes the credit to the recipient GSTINs in the ratio of turnover in the previous financial year through a GSTR-6 filing by the thirteenth of the following month. The receiving GSTINs see the distributed credit in their GSTR-2B under the ISD-inward table rather than the regular inbound-supply table, and the reconciliation has to add the ISD credit as a separate line to the six-bucket classification for the multi-GSTIN comparison to hold.

How do I run the multi-GSTIN reconciliation efficiently without pulling every branch’s ledger separately?

Build a consolidated purchase register at the entity level that carries the recipient GSTIN as a mandatory column on every invoice line — the same column that the vendor should have quoted on the tax invoice at billing time. Pull the GSTR-2B for every GSTIN separately from the portal on the same date (typically the fifteenth of the following month) and merge into a single working paper keyed on invoice number plus supplier GSTIN plus recipient GSTIN. The six-bucket classification runs across the merged view — Place of Supply routing under Bucket 1, vendor mis-filing under Bucket 2, e-invoice IRN mis-tagging under Bucket 3, branch-transfer valuation under Bucket 4, ISD allocation under Bucket 5, and Rule 42/43 apportionment under Bucket 6. Each bucket has different escalation owners: the indirect-tax executive for Buckets 1, 4, and 5; the AP analyst for Bucket 2; the e-invoice compliance owner for Bucket 3; and the controller for Bucket 6 given the audit-materiality of the common-credit reversal calculation.

Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published Invalid Date

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024