How-to · Zoho & multi-GSTIN

Multiple GSTINs in Zoho Books. The Branches setup, and the decision you can't undo

The short answer

In Zoho Books, Branches lets one organisation hold several GSTINs — either several branches sharing one GSTIN, or a separate GSTIN per branch. Each GSTIN needs its own transaction series, and branches sharing a GSTIN cannot reuse a prefix across series. Once Branches is switched on it cannot be switched off (individual branches can only be deleted or marked inactive; Zoho's newer Locations feature offers a migration path instead). Each GSTIN still has to be reconciled to its own GSTR-2B separately — it is a distinct registration, not a filter on one shared number.

Zoho Books lets one organisation run several GST registrations side by side under Branches — but the feature is a one-way door (you can enable it, not disable it), and the two things people get wrong first are which GSTIN a branch actually belongs to, and whose transaction numbers clash with whose. Neither mistake shows up until a return is due.

One Zoho organisation, several GST registrations

Zoho Books is built around a single organisation, but a business with more than one place of business — or more than one GST registration in the same state, which the proviso to Section 25(2) of the CGST Act, read with Rule 11 of the CGST Rules, permits — often needs to run several GSTINs out of that one organisation. Zoho's answer is Branches. Per Zoho's own Branches documentation, the feature has a hard prerequisite before you can touch it at all: your organisation needs a registered GSTIN with GST Settings already enabled. Branches is not how you get your first GSTIN into Zoho Books — it's how you add the rest.

As of 7 October 2026: Zoho has begun offering Locations as "an upgraded version of the existing Branches feature", with an in-product migration banner (Settings > Organization > Warehouses/Branches > Migrate to Locations) for organisations that want to move. Zoho's own documentation doesn't say whether Branches continues unchanged for organisations that don't migrate, or for how long — check which screen your organisation is actually on before following the Branches-specific steps below. All screen names, field labels and menu paths in this guide are per Zoho's documentation as of this date; Zoho can change its own screens without notice, so verify against your own account.

The decision you can't undo: enabling Branches

Branches is switched on from Settings > Organization > Branches > Enable Branches, and only an organisation admin can do it. Zoho's documentation states this plainly, and it's the single most important line on the page: "Once you enable Branches, you will not be able to disable it in Zoho Books." There is no undo button and no downgrade path back to a single-branch organisation. Zoho does leave two narrower escape hatches once Branches is on — an individual branch can be deleted or marked inactive — but Zoho's documentation states no way to turn the feature itself back off. Decide deliberately, not by clicking through a setup wizard to see what the screen looks like.

Creating a branch, and the GSTIN question people get backwards

Branches are created from Settings > Organization > Branches > Add Branch, and each one asks for a name and address, a primary contact, a transaction series, and — the field that actually answers the pain point most setups stall on — a GSTIN to associate with the branch (or + New GSTIN). Per Zoho's documentation, the mapping runs both ways and you choose which one you need: "You can choose to associate one GSTIN to multiple branches or add new GSTINs and associate them with each branch."

What you're actually modellingBranch/GSTIN setup
One registered office, several physical locations billing under the same registration (e.g. two warehouses in the same state)Multiple branches, one shared GSTIN associated with all of them
Separate GST registrations — different states, or more than one registration within the same state — that each file their own returnsOne branch per GSTIN, each associated with its own, distinct GSTIN

Zoho Books doesn't infer which model you need from your company structure — you choose it explicitly, branch by branch, the moment you create each one. Get this backwards (multiple GSTINs squeezed under one branch, or one real registration split across branches that are all tagged with the wrong GSTIN) and every downstream number — the return a transaction counts toward, the series it gets numbered under — is wrong from the first invoice.

Transaction series: the clash the forums keep asking about

Each branch is assigned a Transaction Series, configured from Settings > Organization > Branches > Transaction Series Preferences: a name, the branch(es) it applies to, and a prefix/suffix for each transaction module (invoices, bills, credit notes, and so on). A per-branch series isn't mandatory — Zoho's documentation allows one default series associated with several branches at once — but if you run more than one GSTIN, Zoho's documentation says it is important that the series be unique for each GSTIN. Set up correctly, the right series is then applied automatically: "the transaction series will be selected automatically based on the branch chosen."

The clash shows up at setup, not at use. Zoho's own FAQ on this — titled, tellingly, "Why I am not able to use the same prefix for branches under the same GSTIN?" — answers it in three short lines: "Each prefix should be unique. You cannot use the same prefix for multiple transaction series within branches sharing the same GSTIN. You need to modify the prefix for all the modules listed in the configuration page in a way that it differs from the prefixes used in other transaction series." That restriction, in Zoho's own wording, is scoped to branches sharing one GSTIN. Zoho requires a distinct series per GSTIN, and within one GSTIN no two series can share a prefix — using a branch- or GSTIN-specific prefix convention everywhere is a sensible habit, not a documented Zoho-wide rule. Pick that convention before you create the second branch, not after you've issued invoices under a clash you only notice when the series picker starts behaving unexpectedly.

Why the GSTIN boundary matters more than the Zoho setting does

It's easy to treat "which GSTIN is this branch tagged with" as a Zoho configuration detail. It isn't — it's a tax-law boundary that Zoho's setting is only reflecting. Under Section 25(4) of the CGST Act, each registration held under one PAN — whether in different states, or more than one registration within a single state — is treated as a "distinct person" for GST purposes, not a branch office of one taxpayer in the GST law's eyes; Schedule I, para 2 then treats a supply between those distinct persons, when made in the course or furtherance of business, as a supply even without consideration. That status is what makes the Branches/GSTIN distinction load-bearing rather than cosmetic: each GSTIN you associate with a branch in Zoho Books is a separate registration that has to file its own GSTR-1 and GSTR-3B, and reconcile its claimed input tax credit against its own GSTR-2B — the auto-generated statement the portal produces separately for each GSTIN under Rule 60 of the CGST Rules. For ordinary supplier invoices, that credit is available only once the invoice has been communicated in that registration's own GSTR-2B (Section 16(2)(aa) CGST Act, read with Rule 36(4) CGST Rules) — one GSTIN's clean 2B says nothing about whether a sibling GSTIN's claim is covered, and the Rule 36(4) condition doesn't reach every category of credit (import IGST, ISD credit, and reverse-charge self-invoices sit outside it) either way. Cross-charge and Input Service Distributor mechanics for services shared across these GSTINs are a real part of running a multi-registration business, but they're governed by a separate set of rules (valuation under Rule 28(1) CGST Rules; ISD under Section 20 CGST Act) and are outside what this setup guide covers — don't let a Zoho branch structure substitute for getting that separately right.

The practical upshot: "I reconciled GSTR-2B" is not a complete sentence for a multi-GSTIN business — it has to be "I reconciled this GSTIN's GSTR-2B", repeated once per registration. A Zoho Books setup that correctly tags every branch with its real GSTIN gives you the raw data to do that; it doesn't do the reconciling for you.

What Zoho's own documentation doesn't say: whether reports blend GSTINs by default

Zoho's Branches documentation we've drawn on here covers enabling the feature, creating branches, and configuring transaction series — it does not state, one way or the other, whether a standard Zoho Books report (an ITC summary, a GSTR-2B comparison, a tax liability view) defaults to a consolidated, organisation-wide figure across every branch and GSTIN, or breaks out each registration automatically. If your organisation runs more than one GSTIN, the safer assumption until you've confirmed the behaviour on your own account is to actively filter every reconciliation-relevant report down to one GSTIN at a time before relying on its numbers — rather than discovering, at return time, that a total you treated as "this registration's position" was quietly blended across two or three.

How Recoup fits in

Recoup doesn't replace the Branches setup above — getting each branch tagged to the right GSTIN and each transaction series numbered without a clash happens inside Zoho Books, the way it's described here. What Recoup does downstream is reconcile GSTR-2B per GSTIN, matching how the law conditions each registration's credit on its own GSTR-2B — never one blended, organisation-wide view that happens to look tidy but can't tell you whether a specific registration's claim is actually covered. That's the difference that matters once you're running more than one registration: a clean combined number is not the same thing as three clean registrations.

One organisation, several GSTINs, zero blended numbers

Recoup reconciles your Zoho Books ITC against GSTR-2B separately for every GSTIN you run — never collapsed into one organisation-wide figure that hides which registration is actually clean.

Book a demo →

Related guides