Feature
Description
Flexible Synchronisation
Send sync requests from server or client at any given time, without having to worry about connectivity at both ends.
Tally.NET Server
Data is synchronised using Tally.NET Server, which connects the client and the server.
Sync direction
You can choose the direction for synchronising masters and transactions as:
● Send only
● Receive only
● Both
For example, the branch offices can only send or/and only receive transactions from head office. The direction depends on the rule created.
The table below shows the direction of synchronisation for transactions and masters:
Client Rule |
Transactions |
Masters |
Send only |
|
|
Receive only |
|
|
Both (send and receive) |
|
X |
Safety and security
On-demand synchronisation ensures safety and security of data within the Tally.NET Server. After data is synchronised at the receiving end, Tally.NET Server deletes it.
Note: If the synchronising party does not accept or perform synchronisation within 7 days, a new synchronisation request has to be sent.
For example,
● A company ABC synchronising data from the head office (HO) accepts the request initiated by the branch office (BO) on Monday.
● The Tally.NET server deletes the data after the synchronisation is complete.
● If the data is not accepted in 7 days, it is automatically deleted.
● BO now has to resend the data to the HO by initiating a new sync request.