Second Branch One Tally Licence Gold Data Sync and the Honest Options
A second branch is where the one licence two PCs question stops being a settings question and becomes an architecture question. Gold does not stretch across the internet — here are the three designs that actually work.
✍️ Technical Anshu🧾 TallyPrime📜 Licence Facts
🎥 Full video — the one-licence question, and where branches fit in it
Two desks in one room is a licence question. Two locations are a design question. Offices discover this the hard way when the new branch opens and the LAN-based sharing that worked in the head office simply does not exist there. This page lays out the three honest ways real businesses run Tally across two locations — and the one shortcut that quietly destroys books.
Second Branch — What One Licence Cannot Stretch To
Gold licence serving two offices over the internet as if one LANNot its design
Head office Gold + branch enters locally, data synchronised by designTally feature ✅
Both branches hosted on one cloud server, one licence setWorks ✅
Same data folder copied to both branches, edited in bothBooks split
Branch only views reports — remote access or browser reportsLight route ✅
A branch is not a second desk. The LAN ends at the office wall, and every honest branch plan starts by accepting that.
1
Why a Branch Breaks the LAN Assumption
Everything in the two-PC answers so far leans on one quiet assumption: same network. Silver handover works over a LAN. Gold shares its licence over a LAN. A second branch in another part of the city — or another city — is not on your LAN, so neither licence simply stretches across. This is the point where honest architecture replaces hopeful settings.
2
The Three Honest Branch Designs
One cloud home for both branches — host the licensed Tally on a cloud server; both branches connect to the same installation and the same data. Licence count stays clean, geography stops mattering. With Gold on that server, multiple users across branches can work as the licence allows.
Each location works locally, data synchronises by design — TallyPrime has a built-in data synchronisation feature made exactly for this: branch and head office each maintain their data and exchange it on a schedule through Tallys sync. This is a designed feature with rules to configure — not the same thing as copying folders back and forth.
Branch as a viewer — if the second location only needs to see (stock position, outstanding, day reports), remote report access or scheduled report exports may cover it with no second working setup at all.
3
Licence Reality for Branches
Each design still respects the same foundation: a licence serves the users it is licensed for, where it is activated. A branch that does full local entry on its own installation needs its own licensing arranged for that installation — discuss the exact structure with a Tally partner before opening day, because branch structures (separate companies vs one company with godowns and cost centres) change the right answer. What never works is pretending two locations are one desk.
🔴 The branch mistake to never make: copying the head-office data folder to the branch and letting both sides enter vouchers. Within days there are two truths, and no Tally feature merges casually split books after the fact. Design the branch properly — cloud, sync, or view-only — before the first branch bill is printed.
🎥 Watch the Full Video for the Complete Picture
The video above walks through what actually happens when one Tally licence meets two PCs, step by step, on screen.
Can a Gold licence be shared between head office and branch over the internet?
Gold is licensed and designed for sharing within one local network where it is activated; it is not a two-location internet licence. For two locations, use one of the designed routes: host Tally on a cloud server both locations connect to, or run each location locally with Tally's data synchronisation between them.
What is Tally data synchronisation, in simple words?
It is TallyPrime's built-in feature for multi-location businesses: each location works on its own data, and the locations exchange data on a schedule so head office receives branch transactions. It must be configured as a design — masters, voucher types and rules decided in advance — unlike copying folders, which splits the books with no way back.
Our branch only needs to check stock and outstanding. What is the lightest setup?
A view-only arrangement: the branch uses Tally's remote or browser-based report access, or receives scheduled report exports from head office. No second working installation, no second dataset, and no licence stretching — often all a small branch counter actually needs.
This guide is based on the Technical Anshu video above • Licence rules change over time, so confirm current terms on Tally Solutions official help pages before you buy or upgrade 🙏