Skip to content
Tutorials Center
My learning

Topics

Lesson 35 of 38 ยท Advanced Features

Security, Backup, Restore and Data Management in Tally Prime

Protect your Tally Prime books with user roles and passwords, audit trail, backup and restore, company split, data repair and import/export, with practical routines.

Accounting data is valuable and sensitive. Tally Prime gives you tools to control who can do what, to keep a trail of what changed, to back up and restore data and to keep very large companies manageable. This lesson covers each and ends with a simple routine you can adopt.

Tally is a desktop product that cannot run on this site. Screens are described and Python stand-ins illustrate the logic; no real passwords or data are involved.

Security control and user roles

Gateway of Tally > Alt+K (Company) > Security, or in many releases F3 > Alter > Security Control: enable Use Security Control and create Security Levels (roles) and Users.

  1. Tally.NET user / Local user: a username and password. A local user belongs only to this company's data, while a Tally.NET user is an Account ID tied to Tally.NET services.
  2. Security level (role): a named set of permissions, such as Owner, Data Entry, Auditor, Accountant. Define for each voucher type and each report whether the role can create, display, alter, delete or is denied.
  3. Assign each user to a level. The Owner/Administrator has all rights, so keep that account for the owner only.

Use the principle of least privilege: data entry staff create vouchers but cannot see profit and loss; auditors view everything but cannot change.

Python Stand-in: a tiny role-permission check

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Passwords and the audit trail

  • Company password: protects opening the company (and optionally separate passwords for alter/repair). Choose strong passwords and store them safely: a lost company password is hard to recover.
  • Edit log / Audit trail: turn on Maintain edit log (F11 > Accounting features or under security control). Tally records every voucher change with user, date, and the previous values; view it in Display More Reports > Exception Reports > Audit trail (Edit log). In regulated settings, this audit trail must be kept on and not turned off; the Companies Act rules for accounting software expect a working audit trail.
  • Lock vouchers by date: set a security level restriction or Use voucher locking to prevent entry before a date.

Backup and restore

Back up regularly. In Tally Prime:

  1. Gateway of Tally > Alt+Y (Data) > Backup (the Data menu is under Alt+Y).
  2. Select the company or companies, a destination folder (preferably on a different drive or a cloud/storage folder), and press Enter. Tally creates a compressed .001-style backup file named with the company number and date.
  3. To restore: Alt+Y > Restore, pick the backup file and the destination data folder. Restored data replaces the company with the same number in that folder, so be sure of the target.

Good practice is the 3-2-1 rule: three copies, on two kinds of media, with one off site. Verify a backup occasionally by restoring it to a test folder.

Python Stand-in: which backups can I delete? (keep daily 7, weekly 4)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Data maintenance

  • Split company data (Alt+Y > Split): create a new data set from a given date and carry forward the closing balances, so the active company stays fast. Keep the original as an archive.
  • Verify / Repair (Alt+Y > Verify or Repair): checks data files for corruption and repairs them. Take a backup first. Run it after power failures or if reports behave oddly.
  • Import and export: export reports to Excel, PDF or HTML with Alt+E; import masters and vouchers from Excel (or XML/JSON) using Tally's import tools. Always test on a copy first.
  • Data location: use a dedicated data folder, not the program folder, and avoid saving data on a network share that may drop.
  • Multi-user: in networked use, one machine acts as the data server; do not let two copies of the same company be edited from different folders.

Never rename, move or delete files inside a company data folder by hand. Use Tally's own backup, restore and split functions.

A simple routine

  1. Daily: back up to a second drive when you finish work.
  2. Weekly: copy a backup off site (cloud or external drive).
  3. Monthly: restore one backup to a test folder to prove it works; review the audit trail and user list.
  4. Yearly: split the data at year end and keep the old company read-only.

Common mistakes

  1. Using one shared login for everybody, so the audit trail cannot say who changed what.
  2. Keeping the only backup on the same drive as the data.
  3. Turning off the audit trail to "speed things up".
  4. Running repair without a backup.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does least privilege mean for Tally users?

    Roles should be restricted to what each person must do.
  2. 2. Why use the audit trail (edit log)?

    The edit log keeps a history of changes to vouchers and masters.
  3. 3. Which backup plan best follows the 3-2-1 rule?

    The rule is three copies, two kinds of media, one location away from the original.
  4. 4. What should you do before running Repair?

    Repair modifies data files, so always back up first.

Summary

  • Enable security control and give each person a user and a role.
  • Keep the audit trail on; it records edits with user and date.
  • Back up often, off the data drive, and test restores.
  • Split large companies at year end; verify or repair data after failures, after a backup.
  • Do not manipulate data files by hand.

Next: Project: a trading company's year