TallyPrime has made data synchronisation between multiple branch offices and the head office easy. The process of tally data synchronisation includes replicating or consolidating tally data between two or more locations i.e. from the head office to the branches, warehouses or factories. This makes it easy for the branch offices to send data to the head office and vice versa. The entire process of sharing data is done over the Internet or a private network irrespective of the usage of data, based on the type of work done at each location.The frequency of updating data at various locations also differs and largely depends on the volume of data generated at each location or the availability/urgency of having the latest updates at each location. The new features available with TallyPrime has further simplified this process making it an ideal system for various organisations.Read more:Why update Tally.ERP to the Latest Version
For data synchronisation in TallyPrime, you can use either of the licenses - TallyPrime Silver (Single user) or TallyPrime Gold (multi-user). The system that initiates the synchronisation is referred to as the ‘Client,’ whereas the receiving system (with which the synchronisation is performed) is called the ‘Server.’ Being a two-way process, to transfer data, you need to have the same release of TallyPrime at both locations.
To ensure accurate tally data synchronisation, you need to activate the same (F11) features on both the client and the server company. If the features are not the same, some information may not get synchronised. For instance, if tracking numbers are enabled at one end and disabled at the other, there will be errors in the sales/purchase bills pending reports.
If there is any alteration in default voucher type names, the same will be altered during data synchronisation based on the voucher type configurations that are made in the server/client rules to Ignore modified voucher type masters.If the Ignore modified voucher type masters is enabled in rules, it will restrict the data from getting synchronised.In this case, under the default voucher types, you need to create new voucher types. Here, you can create location-wise voucher types if needed. Also, if required, you can specify the method of voucher numbering with prefix or suffix. This will ensure seamless data synchronisation across locations.Also, it is best to create the required voucher types at the client and server end, as the use of automatic voucher numbering can make it difficult to trace vouchers after synchronisation. This is because, during synchronisation, each voucher is allotted a new incremental voucher number, which makes it difficult to trace.
Manual correction is needed on both the server and the client systems when accounting or inventory masters are altered as a new master gets created at the other end of the synchronising data.
Implementation of tally data synchronisation for multiple locations will not be available if two or more companies have the same GUID.
Since the masters created at multiple locations may differ during data synchronisation, it is important to understand the requirements for master level information like the name of the masters and opening balances. For example, you can maintain one main group for ‘conveyance’ and create multiple ledgers at various locations to account for ‘conveyance expenses.’ These multiple ledgers can then be grouped under the main conveyance group.
Those with the owner credentials can set access rights for different users to ensure only authorised users can perform certain tasks. This is one of the essential features to protect tally data while working remotely. The new set of security controls for TallyPrime data synchronisation include:
Request a Tally Prime Demo now and experience seamless data management for streamlining your business operations.