How-to · Tally & multi-GSTIN

Running several GST registrations in one Tally company. The report that quietly blends them

The short answer

Since TallyPrime Release 3.0, one company can hold multiple GSTINs, with each voucher type tagged to a registration. But per Tally's own documentation, the GSTR-2B Reconciliation report "shows consolidated data for all registrations by default" — press F3 to scope it to one GSTIN before trusting a "Reconciled" count, because each registration is a distinct person under GST law with its own filing obligation.

TallyPrime can hold several GST registrations in one company and tag every voucher to the right one. What its own documentation also says, in plain words, is that the GSTR-2B Reconciliation report doesn't follow that split by default — it shows one combined number across every registration until you tell it otherwise.

One Tally company, several GST registrations

A business with branches in more than one state, or more than one registration within a single state — which the proviso to Section 25(2) of the CGST Act, read with Rule 11 of the CGST Rules, permits — often ends up running several GSTINs out of what is, in Tally terms, a single company. Since TallyPrime Release 3.0, Tally supports this natively: you can create multiple GST registrations inside one company, mark each Active or Inactive, and tag voucher types — sales invoices, purchase orders, and so on — to a specific registration, so transactions of that type are assigned to the right GSTIN automatically. Per Tally's own documentation, the upgrade to Release 3.0 "is free if you have an active TSS subscription" — this is a release feature, not a separately licensed add-on.

Tally presents multi-registration support in one company as a Release 3.0 feature. If you're on an earlier release, don't follow the steps below as if they apply — check how your own installation is structured (for example, a separate company per registration) first.

Group Company is a different feature, and it doesn't do what the name suggests here

It's easy to assume "Group Company" is how pre-3.0 Tally handled multiple GSTINs, because it's the feature that links separate companies together. It isn't built for GST reconciliation at all: per Tally's own documentation, Group Company lets you link branches, subsidiaries or sister companies as member companies and view their Balance Sheet, Profit and Loss A/c and Trial Balance together — a financial-statement consolidation, with each member company's own transactions left untouched. Nothing in Tally's documentation ties Group Company to GST returns, GSTR-2B, or registration-level filing at all. If your business ran separate pre-3.0 companies per GSTIN and used Group Company to see them together, what you were consolidating was the accounts — each company still had to file, and still had to reconcile, its own GSTR-2B separately. Group Company was never a workaround for that.

Tagging vouchers to the right GSTIN

Inside a Release 3.0+ multi-registration company, the mechanism that actually routes a transaction to a GSTIN is the voucher type. You can run a separate voucher type per registration, or share one common voucher type across registrations and let the registration field on the voucher itself decide — either way, Tally's documentation notes that Release 3.0 lets you create voucher series for different tax units, each with its own numbering, which it says helps prevent the cross-utilisation of vouchers between registrations. Zoho Books' multi-GSTIN setup has a transaction-series clash of its own; get the tagging backwards in either tool, and every return a transaction counts toward is wrong from the first voucher.

Tally's documentation also confirms that returns themselves are generated per GSTIN — you don't get one combined GSTR-1 or GSTR-3B across registrations — and that you can view and export GST returns for a single registration or for several at once, with a separate "Combined Return and Reports view" offered specifically for comparing across them. Returns, in other words, already assume one registration is one filing unit. The gap is somewhere else.

Where it breaks: the GSTR-2B Reconciliation report defaults to blended

Here is the line worth reading twice, because it runs against what the rest of the multi-GSTIN setup trains you to expect. Tally's own GSTR-2B Reconciliation documentation states it plainly: "If you have multiple GST registrations, the report shows consolidated data for all registrations by default." (per Tally's help documentation as of 14 Oct 2026). Not per-GSTIN by default, with an option to combine — the other way around. Every registration's reconciliation status is pooled into one view unless you act to narrow it.

The narrowing control is F3 ("Company/Tax Registration"), the same key Tally uses elsewhere to switch which registration a report is built against. Tally's documentation names this as the control for selecting which registration you want, but it does not spell out, in so many words, whether F3 filters the existing report down or re-runs the comparison for the registration you pick — treat it as a hard switch either way and confirm which registration is selected before reading a result, not after. The same care applies at three other points Tally's documentation calls out specifically for multi-registration companies: importing a saved GSTR-2B file ("in case of multiple GST registrations, select the required one"), setting a default registration for the download step, and choosing the registration in the Recompute GSTR-2B configuration screen. Four separate places to confirm you're looking at the registration you think you are — and the one that does the most damage silently is the summary report itself, because a consolidated "Reconciled: 412" looks exactly as tidy as three separate clean counts would.

Why this is the opposite of safe-by-default: a blended view can hide one registration's real gap behind another registration's surplus of clean matches — the combined total still looks healthy. Reconciling each GSTIN's GSTR-2B separately, and checking F3 before trusting a count, is the one step that turns Tally's multi-registration convenience back into an accurate, registration-level picture instead of a number that's painful to untangle after the fact.

Why the registration boundary isn't just a Tally setting

The reason a blended view is a real problem, and not a cosmetic one, is that each GSTIN is a separate legal filer, not a label. Under Section 25(4) of the CGST Act, every registration held under one PAN — across states, or more than one within a single state — is a "distinct person" for GST purposes, and paragraph 2 of Schedule I treats a supply between those distinct persons as a supply even when made without consideration, if made in the course or furtherance of business — taxed at whatever rate applies to the goods or services, and valued under Rule 28(1). Each registration's claimed input tax credit has to be matched against its own GSTR-2B — the statement Rule 60 of the CGST Rules generates separately per GSTIN — because Section 16(2)(aa) of the CGST Act, read with Rule 36(4), ties ordinary vendor credit to invoices the supplier has furnished against that registration's GSTIN in GSTR-1 (as amended in GSTR-1A) or the IFF, and that are communicated in that registration's own GSTR-2B under Rule 60(7). One GSTIN's clean reconciliation says nothing about whether a second GSTIN's claim is actually covered; Rule 36(4)'s ambit doesn't reach import IGST, ISD credit or reverse-charge self-invoices either way, so those categories need their own check regardless of which registration they sit under.

How Recoup fits in

Recoup doesn't change how registrations get tagged inside Tally — that happens at the voucher-type level, the way it's described above. What Recoup does is take the same purchase register and the same GSTR-2B export and reconcile them per GSTIN every time, so reconciling each GSTIN's GSTR-2B separately never depends on remembering to press F3 before you trust a count. A blended total that looks clean is not the same claim as three registrations that are each actually clean, and that's the difference a report built to default to consolidated can't make for you.

One Tally company, several GSTINs, zero blended totals

Recoup reconciles your Tally purchase register against GSTR-2B separately for every registration you run — never collapsed into the one combined view Tally's own report defaults to.

Book a demo →

Related guides