TallyPrime Multi-Site License Setup & Configuration Guide

For growing enterprises operating across multiple offices, factories, retail outlets, and warehouses, licensing costs can quickly escalate if each location maintains separate individual software accounts. To optimize expenses, Tally Solutions offers a Multi-Site Licensing model.

A Multi-Site license allows a corporate group to purchase multiple single-user (Silver) or multi-user (Gold) licenses and link them under a single corporate account, managed by a designated administrator. This centralized structure makes it easy to share TSS validity, manage users, and deploy branch-specific profiles. This guide covers the installation, setup, and connection troubleshooting for TallyPrime Multi-Site deployments.

1. Understanding the Multi-Site Architecture

In a standard Tally installation, each serial number functions as its own independent licensing account. In a Multi-Site deployment:

• Corporate Account (Account-level Admin): The parent entity manages all sub-licenses (Sites) through a single login on the Tally portal. The admin can allocate, revoke, or transfer site licenses between locations.
• Site License (Branch-level Seat): Each location is designated as a "Site" with its own serial number and activation parameters. These sites can be Silver (single user) or Gold (multi-user on LAN).
• Tally Gateway Server (Local Handshake): Each branch location runs its own Tally Gateway Server locally to service workstations in that office, but logs transaction sync reports back to the central corporate account.

2. Step-by-Step: Setting Up a Multi-Site Account

To establish a Multi-Site license framework, you must first register your parent corporate account:

1. Go to the Tally Solutions website and log into your corporate portal account using your main Tally .NET ID credentials.
2. Navigate to the Control Centre > Account Management > License Management dashboard.
3. Select the option to Create Site. Enter details for your first branch (e.g. Site ID: "Mumbai Branch", Location: "Mumbai Office").
4. Repeat this process to configure Site IDs for all branch locations (e.g., "Delhi Warehouse", "Bangalore Factory").
5. Assign a specific site administrator email address for each branch. They will receive the site activation emails.
6. Save the site configuration details. Tally Solutions will issue site-specific activation keys via email.

3. Step-by-Step: Activating Site Licenses at Branch Offices

With the sites registered centrally, proceed to install and activate TallyPrime at each physical branch location:

1. Download and run the TallyPrime setup file on the main machine at the branch office.
2. Right-click TallyPrime, select Run as Administrator, and select Activate New License.
3. Select the option Activate Multi-Site License.
4. Enter your main corporate account Account ID (provided in your registration documents).
5. Enter the specific Site ID configured for this location (e.g. Mumbai Branch) and the Activation Key sent to the site admin.
6. Enter the site administrator email ID. This will act as the local Tally .NET login for that branch.
7. Press Enter. TallyPrime will connect to the central licensing server, associate the new serial number with your corporate account, and activate the local site license.

4. Managing License Allocation in Control Centre

The corporate administrator can manage license states from the central portal:

• TSS Sharing: If one branch's TSS has expired, the administrator can allocate active credits or validity blocks from a central pool to keep that location compliant during transaction periods.
• Site Surrender & Re-allocation: If you close a warehouse in Chennai, you can log into the Control Centre, surrender the site license remotely, and allocate the single-user license to a new sales depot in Pune without needing local physical key registration.

5. Multi-Site Configuration Best Practices

6. Synchronizing Multi-Branch Ledgers via Tally Sync

Deploying multi-site licensing is usually the first step toward building a unified corporate financial database. The next step is configuring Tally Synchronization (Tally Sync). This allows branches to operate on local databases offline and automatically upload transaction batches to the corporate headquarters server at scheduled intervals (e.g. nightly or hourly).

Tally Sync uses the same underlying licensing gateway configurations to secure branch data transfers, ensuring that ledger codes and taxes align across all locations.

7. Corporate Account Auditing Controls

With all branch licenses linked under a single corporate account, internal audit teams can easily monitor software usage and security behaviors across the entire group. From the Tally Control Centre, the central administrator can audit:

• Login History: Review the timestamps and IP addresses used to access branch databases.
• Password Age: Check if branch administrators are adhering to corporate security guidelines by updating their passwords regularly.
• Version Distribution: Ensure all branch locations are running the same TallyPrime release version to prevent data structure mismatches.

8. Setting Up Dedicated License Port Mappings for VPNs

When linking branch offices using corporate virtual networks, assign a distinct licensing port to each location to avoid network conflicts. Configure the local gateway server to listen on unique port ranges like 9001 or 9002. This ensures that the licensing traffic resolves correctly through the central VPN interface.

9. Administrative Controls in Tally Control Centre

The corporate administrator can check site activation logs, manage license allocations, and update TSS subscriptions centrally from the Tally Solutions portal. This eliminates the need to visit branch offices physically to perform standard licensing administrative tasks.

10. Migrating Sites from One Account to Another

If your company undergoes a corporate restructure, site licenses can be migrated to a new parent Account ID. Submit a transfer request via the Tally Control Centre. The admin must surrender the license at the branch first, after which it can be activated under the new corporate credentials. This migration requires checking your active TSS subscription status to ensure there are no validation conflicts when transferring ownership blocks.