Zoho Books Multi-Branch Accounting in India: Branches or Separate Organisations?

A business opens a second location and someone asks the obvious question: do we set this up as a branch, or as a whole new Zoho Books organisation? It sounds like a preference. It is not. The answer follows from company law and your GST registrations, and choosing the wrong structure is genuinely painful to unwind six months later — migrating transactions between organisations is a manual job, and your audit trail does not come with you cleanly.

Here is the rule, and then the detail behind it.

The deciding question is PAN, not geography

If the new location belongs to the same legal entity — same PAN, one set of statutory financials, one income tax return — it is a branch. It can have its own GSTIN, its own address, its own invoice numbering, and still sit inside one Zoho Books organisation on one subscription.

If it is a separate legal entity — different PAN, its own board, its own filings, its own balance sheet — it needs its own organisation in Zoho Books, and its own subscription. There is no way around this, and you should not want one. Two legal entities sharing a ledger is a problem you will meet again at audit.

This is general guidance rather than statutory or tax advice. Your CA should confirm the entity structure before you configure anything — we are describing how the software maps to a structure, not recommending a structure.

What a branch actually gives you

Branches in Zoho Books are more than a label on a transaction. Once enabled, each branch can carry:

• Its own GSTIN — you can associate one GSTIN per branch, which is how a single organisation handles multiple state registrations under one PAN
• Its own transaction series, so invoices from the Pune branch do not share a running number with Chennai
• Its own address and contact details on the documents it issues
• User permissions scoped to the branch, so a branch accountant sees their own transactions rather than the whole group
• A branch-level dashboard and branch-wise reporting, so you can see which location is actually profitable

The GST angle is the one that sells it. Filing for several GSTINs from a single organisation, with the underlying transactions already segregated by branch, is materially less work than maintaining separate books per state and reconciling them at the end of every month.

One limitation worth knowing before you design around it: you associate one GSTIN with a branch, not several. If a single location somehow needs multiple registrations, that is a conversation to have before you start creating branches.

Branch limits by plan

Plan prices and branch limits change — verify current pricing and limits on Zoho's official India pricing page before committing. All prices exclude 18% GST, annual billing is typically around 17% cheaper than monthly, and additional branches can be bought as an add-on beyond the included count.

Read that table alongside your five-year plan rather than your current footprint. The jump from Professional to Premium is roughly double the monthly cost, and businesses that open a third location tend to open a fourth. It is usually cheaper to size the plan for where you are heading than to migrate configuration mid-year.

The hidden cost of the separate-organisation route

If you genuinely have multiple PANs, separate organisations are correct — but price the full picture before you are surprised by it:

• Each organisation carries its own subscription; there is no group discount for running three of them
• Users are licensed per organisation, so a group accountant working across all three is paid for three times unless you restructure who touches what
• Chart of accounts, tax rates, templates and workflow rules are configured per organisation — plan to build once and replicate carefully, because drift between entities makes consolidated reporting harder every month
• Consolidation is not automatic. Group-level reporting across organisations generally means exporting into Zoho Analytics or a spreadsheet and combining there

That last point is the one that catches groups out. People assume multiple organisations will roll up into a consolidated P&L inside Zoho Books. They do not. If group-level reporting is a board requirement, budget for the analytics layer at the same time, not a year later when someone asks for a consolidated view.

A structure that works for most Indian SMEs

The common shape we implement is one organisation per legal entity, branches inside each for state registrations and locations, and reporting tags layered on top for the dimensions that cut across branches — product line, cost centre, project. Tags do the analytical slicing; branches do the statutory and operational separation. Mixing those two jobs up, and trying to make branches carry cost-centre reporting, is how people run out of branch allowance for no good reason.

Before you enable branches

• Confirm the entity structure with your CA — PANs and GST registrations, written down
• Decide the invoice numbering convention per branch before the first invoice goes out, because changing series later creates gaps auditors will ask about
• Map which users should see which branch, and configure permissions at setup rather than after someone has seen a number they should not have
• Check the branch count your plan allows against the number of locations you expect within two years

As a certified Zoho partner we set this up regularly for businesses moving off Tally or off spreadsheets, and the configuration itself is rarely the hard part — the hard part is the half-hour conversation that establishes whether you are looking at one entity or three. If you want that scoped before you buy licences, a short call generally settles it.