How to Set Up Data Synchronization in Tally Prime (2026)

If you’re running separate company files for different branches — see our guide on how to manage branch accounting in Tally Prime — manually exporting and importing data between them every time isn’t sustainable. Tally Prime’s Data Synchronization feature automates this, periodically syncing transactions between a head office and one or more branch locations without you running exports by hand each time.

This guide covers setting up synchronization between a head office and branch company files.

What You Need Before You Start

• Tally Prime installed at both the head office and branch locations, with each location’s company already created — see our guide on how to create a company in Tally Prime
• A network or internet connection between locations, since synchronization needs a way to actually transmit data between the two ends
• A clear decision on direction: are branches syncing data up to head office, is head office pushing master data down to branches, or both

How Data Synchronization Works

At a high level, one company (often the head office) is configured as the server side, and other companies (branches) connect to it as clients. When synchronization runs, transactions and/or masters recorded at the branch get sent to the head office company, and depending on configuration, certain masters from head office can also be pushed down to branches — keeping things like a shared chart of accounts consistent without manual re-entry at every location.

Step 1: Decide on Your Synchronization Topology

Common setups include:

• Branches sync transactions up to a central head office company, where consolidated reporting happens
• Head office pushes certain masters (like a standard chart of accounts or stock items) down to branches, so naming and structure stay consistent
• A combination of both, where masters flow down and transactions flow up

Decide which of these fits your business before configuring, since it affects how you set permissions on each side.

Step 2: Configure the Head Office (Server) Side

1. Open the head office company in Tally Prime
2. Gateway of Tally, then look for Data Synchronization settings (commonly found under company features or a dedicated sync configuration screen, depending on your release)
3. Configure this company to act as a synchronization server, accepting connections from branch companies
4. Note the connection details (such as the server’s network address) that branch companies will need to connect

Step 3: Configure Each Branch (Client) Side

1. Open the branch company in Tally Prime
2. Go to the Data Synchronization configuration screen
3. Configure this company to act as a client, pointing to the head office server’s connection details
4. Set the synchronization rules — which voucher types or masters should be sent to head office, and whether any masters should be received from head office

Step 4: Set the Synchronization Frequency

1. Decide whether synchronization should run on a schedule (for example, daily at a set time) or be triggered manually by a user at the branch
2. Configure this within the sync settings — scheduled sync reduces the chance of someone forgetting to run it, but make sure the network connection is reliably available at the scheduled time

Step 5: Run an Initial Test Synchronization

1. Before relying on this for live operations, record a small test transaction at the branch
2. Trigger synchronization manually and confirm the transaction appears correctly at the head office company
3. If masters are also meant to sync, create a small test master (like a test ledger) and confirm it flows in the expected direction
4. Only move to live, regular use once you’ve confirmed the test data appeared correctly and without duplication

Step 6: Monitor for Sync Errors and Conflicts

1. Periodically check the synchronization log or status screen for any failed or rejected entries
2. Common causes of failure include network interruptions during sync, or conflicting changes (for example, the same master edited differently at head office and a branch before syncing)
3. Resolve conflicts promptly, since unresolved sync errors mean head office’s consolidated view is missing data from that branch until fixed

Step 7: Reconcile Periodically Even With Sync Running

Even with automated synchronization in place, it’s worth periodically comparing branch-level totals against what’s reflected at head office — similar in spirit to the inter-branch reconciliation discussed in our branch accounting guide — since automation reduces manual effort but doesn’t eliminate the value of occasionally double-checking that everything genuinely matches.

Common Mistakes to Avoid

• Setting up synchronization without first testing it on non-critical data, risking duplicate or missing entries once live transactions start flowing
• Not deciding clearly on sync direction and rules upfront, leading to confusion about where a particular master should be created and edited going forward
• Ignoring sync failure notifications or logs, letting a branch’s data silently fall out of sync with head office for an extended period
• Relying entirely on automated sync without any periodic manual reconciliation, missing subtle issues that don’t trigger an obvious error
• Running synchronization over an unreliable network connection without retry/recovery awareness, risking partial or corrupted sync runs

FAQs

Does Data Synchronization work over the internet, or only on a local network? Tally Prime’s synchronization feature can generally work over an internet connection between locations, not just a local network, though your specific setup and any firewall/network configuration needs to support the connection.

Can synchronization go both ways — branch to head office and head office to branch? Yes, depending on configuration, you can set up masters to flow from head office down to branches (for consistency) while transactions flow from branches up to head office (for consolidated reporting).

What happens if the same master is edited differently at two locations before syncing? This creates a conflict that synchronization will typically flag rather than silently resolve incorrectly. Review and manually resolve such conflicts to ensure the correct version is retained.

Is Data Synchronization the same as the export/import feature? No. Export/import is a manual, one-time data transfer process. Data Synchronization is designed for ongoing, ideally automated, regular transfer of data between connected companies — see our guide on how to export and import data in Tally Prime for the manual alternative.

Do all Tally Prime editions support Data Synchronization? Feature availability can vary by edition and release. Confirm with an authorized Tally partner whether your specific license supports this feature before planning your multi-branch setup around it.