Installation, Licensing and Company Configuration

Introduction

Tally.ERP 9 is an enterprise accounting and business-management application used to record transactions, maintain ledgers, prepare financial statements, manage inventory, calculate taxes, and produce management reports. Although the software is comparatively easy to operate, the quality of its output depends substantially on the decisions made before the first transaction is entered. Installation, licensing, company creation, financial-year configuration, security, statutory settings, and backup procedures form the control environment within which accounting data is processed.

For a Chartered Certified Accountant, these activities are not merely technical tasks. They affect the reliability, completeness, confidentiality, auditability, and legal compliance of financial information. An incorrectly configured financial year may produce misleading reports; an inappropriate currency setup may distort transactions; and inadequate backup procedures may expose the entity to serious business-continuity risks.

This chapter presents a systematic approach to installing and activating Tally.ERP 9, configuring companies, managing company data, and establishing appropriate controls. Menu names may vary slightly according to the release, operating system, localization, and enabled statutory modules. Users should therefore verify release-specific procedures against the official documentation and applicable law.

Learning Objectives

After completing this chapter, the learner should be able to:

1. Explain the architecture and operating requirements of Tally.ERP 9.
2. Install, activate, and manage a licensed Tally.ERP 9 environment.
3. Create, alter, select, shut, and delete companies appropriately.
4. Configure financial years, books beginning dates, currencies, accounting features, and statutory options.
5. Design reliable backup, restoration, security, and access-control procedures.
6. Evaluate configuration decisions from accounting, governance, audit, and compliance perspectives.

1. Tally.ERP 9 as an Accounting Information System

Tally.ERP 9 should be understood as an accounting information system rather than simply a ledger-writing program. It receives source information, applies configured rules, stores accounting records, and generates reports. A simplified information flow is:

Source documents → vouchers → ledgers and registers → financial statements and statutory reports

The configuration layer determines how this flow operates. For example, enabling inventory integration allows stock items and quantities to be associated with accounting transactions. Enabling taxation features introduces tax ledgers, rates, classifications, and statutory reporting requirements. Enabling cost centres permits transactions to be analysed by departments, projects, branches, or responsibility areas.

The principal configuration levels are:

A crucial professional principle is that configuration should precede transaction entry. Changing fundamental settings after transactions have been recorded can create inconsistent reports, duplicate masters, or difficult-to-audit adjustments.

2. Installation Planning

2.1 Preliminary assessment

Before installation, the organisation should document:

• the number of users and workstations;
• whether the system will be standalone, networked, or accessed remotely;
• the company or companies to be maintained;
• the applicable country and statutory regime;
• the required modules, such as accounting, inventory, payroll, or taxation;
• the intended data location and backup destination;
• user roles and approval responsibilities; and
• the migration requirements from an earlier accounting system.

Installation should be performed using an authorised installer obtained from a trusted source. The organisation should record the release number, installation date, licence details, responsible administrator, and data directory. This documentation supports future troubleshooting and audit enquiries.

2.2 Operating environment

The computer should satisfy the release-specific hardware and operating-system requirements. In practice, the administrator should verify adequate storage, stable power, supported operating-system versions, network connectivity where relevant, printer compatibility, and permission to write to the selected data directory. Antivirus software and endpoint-security controls should be configured so that they do not corrupt or block legitimate application and data files.

The data path deserves particular attention. Program files and company data need not be located on the same drive. A controlled data location should be accessible to authorised users, included in the backup plan, and protected against accidental deletion. Storing live accounting data in an unmanaged personal folder or removable drive is poor practice.

2.3 Installation procedure

A conventional installation sequence is as follows:

1. Close other applications and log in with appropriate administrative permission.
2. Run the authorised Tally.ERP 9 installer.
3. Select the installation directory and, where applicable, the data directory.
4. Select the required country, language, and interface preferences.
5. Complete installation and start the application.
6. Confirm the release number and data path.
7. Create or open a test company before introducing live data.
8. Record installation and licence information in the organisation’s IT register.

A test company is valuable because it permits validation of printing, date formats, currency symbols, tax settings, user access, backup, and restoration without risking production data.

3. Licensing and Activation

3.1 Licensing concepts

Tally.ERP 9 licensing generally distinguishes between licensed use and educational or demonstration use. A licensed installation may be configured for single-user or multi-user operation depending on the purchased entitlement. The licence is not merely a commercial formality: it establishes the permitted scope of use and supports lawful, supported, and update-eligible operation.

Activation normally requires licence-related information such as a serial number, activation key, and administrator credentials. The exact process depends on the release and licensing arrangement. The user should follow the official activation workflow rather than attempting to modify files or bypass licence controls.

3.2 Activation controls

A sound activation procedure includes:

• confirming that the licence belongs to the organisation;
• using an authorised administrator email address;
• recording licence and renewal information securely;
• restricting licence credentials to responsible personnel;
• verifying the number and type of licensed users; and
• testing operation after activation.

If internet connectivity is unavailable, an authorised offline or assisted activation procedure may be available, subject to the product release. Licence status should be checked after hardware replacement, server migration, major software changes, or renewal.

3.3 Ethical and governance considerations

Unauthorised copies, shared credentials, licence circumvention, and installation from unknown sources create legal, cybersecurity, and data-integrity risks. They may also make the organisation unable to obtain updates or technical support. The accountant should treat software licensing as part of corporate governance and internal control.

4. Creating a Company

A company in Tally.ERP 9 is a logical accounting data set representing an entity, branch, project, or other reporting unit. It contains its own masters, vouchers, configuration, and financial reports.

From the Company Info menu, the user normally selects Create Company and supplies information such as:

• company name and mailing name;
• address and contact details;
• country and state or province;
• base currency symbol and formal currency name;
• number of decimal places for the currency;
• financial year beginning date;
• books beginning date; and
• security and user-access preferences.

4.1 Financial year beginning

The financial year beginning date establishes the reporting period structure. For example, if the reporting year begins on 1 January, the financial year may run from 1 January to 31 December. If it begins on 1 April, the relevant period may run from 1 April to 31 March, subject to local law.

4.2 Books beginning date

The books beginning date indicates the date from which accounting entries are maintained in the company. It may be the same as the financial year beginning date, but it can differ when opening balances are introduced or when the system is implemented partway through a year. The distinction must be documented because it affects which transactions can be entered.

4.3 Currency configuration

The base currency is the currency in which the company’s principal accounting reports are presented. Configuration normally includes the currency symbol, formal name, and decimal places. The selected decimal precision should agree with local accounting practice and the organisation’s source documents.

Foreign-currency transactions require additional controls. The user must establish the relevant foreign currency, exchange rate, date of rate, and treatment of exchange differences. Exchange-rate settings do not eliminate the need for review: rates should be supported by approved sources and checked at reporting dates.

5. Selecting, Altering, Shutting, and Deleting Companies

5.1 Selecting a company

The Select Company function opens an existing company for use. More than one company may be loaded where comparison, consolidated analysis, or inter-company work is required. Users must confirm the active company before entering a voucher. Entering a transaction in the wrong company is a common operational error.

Useful controls include displaying the company name prominently, restricting simultaneous company access where inappropriate, and requiring users to verify the financial year and date before transaction entry.

5.2 Altering a company

Company alteration permits changes to details such as address, contact information, financial year settings, security controls, or features, depending on the release and data status. Changes should be authorised and documented. A company name or address change may be legitimate, but changing fundamental dates after transactions exist can affect reporting and should not be treated as a routine correction.

Before altering a live company, the administrator should:

1. perform a verified backup;
2. record the existing settings;
3. obtain approval from the responsible finance officer;
4. test the proposed change where possible; and
5. review reports after alteration.

5.3 Shutting and deleting

Shutting a company removes it from the active session but does not delete its data. This is appropriate when moving between companies or ending a work session. Deleting a company is fundamentally different: it can permanently remove accounting data and should be subject to formal approval, retention policy, and a verified archive.

Deletion should never be used as a substitute for correcting an accounting mistake. Errors should ordinarily be corrected through authorised voucher alteration, reversal, or adjustment so that an audit trail is preserved.

6. Accounting Features and Configuration

The F11 Features menu controls broad capabilities. Common feature groups include accounting, inventory, statutory taxation, payroll, cost centres, bill-wise details, budgets, orders, and security.

6.1 Accounting features

Important accounting options may include:

• maintaining accounts only or accounts with inventory;
• integrating inventory with accounts;
• maintaining bill-wise details for receivables and payables;
• enabling cost centres and cost categories;
• using interest calculations;
• enabling budgets and scenario management; and
• permitting multiple currencies.

Each option should be enabled because of a defined business requirement. Excessive activation can complicate menus, increase configuration effort, and create unused masters. Insufficient activation can prevent accurate analysis.

6.2 Inventory features

Where inventory is relevant, the organisation may configure stock groups, categories, units, godowns or locations, batches, expiry dates, reorder levels, and inventory valuation methods. Inventory integration should be reconciled with the general ledger. Differences between physical stock, stock reports, and accounting records require investigation rather than automatic adjustment.

6.3 Bill-wise accounting

Bill-wise details allow receivables and payables to be tracked against individual invoices, advances, or adjustments. This supports ageing analysis and collection management. The feature is useful only when users consistently allocate receipts and payments to the correct outstanding references.

6.4 Cost centres and budgets

Cost centres classify income and expenditure by department, branch, project, or responsibility area. Budgets provide planned values against which actual performance can be compared. A budget is a management-control tool, not a replacement for accounting evidence. It should be approved, version-controlled, and reviewed for material variances.

7. Statutory Settings

Statutory configuration depends on the jurisdiction and the organisation’s legal status. It may include taxation registration details, tax type, registration number, state or province, tax rates, invoice requirements, payroll regulations, and electronic filing parameters.

The following control principles are essential:

1. Statutory settings must be based on current law and official guidance.
2. Registration numbers and legal names must be entered exactly.
3. Tax ledgers and rates should be reviewed by a qualified tax professional.
4. Changes in law should be reflected through controlled configuration updates.
5. Reports should be reconciled to returns and source documentation.

Software configuration does not determine legal liability. The entity remains responsible for correct classification, tax treatment, filing, payment, and retention of records. A tax module can calculate a value incorrectly if the underlying rate, classification, place of supply, exemption, or master data is wrong.

8. Security, Users, and Auditability

Security should follow the principle of least privilege: each user receives only the access required for assigned duties. Typical roles may include data-entry operator, accounts supervisor, finance manager, auditor, and system administrator.

Controls may include:

• unique user IDs;
• strong and confidential passwords;
• role-based permissions;
• restrictions on altering or deleting vouchers;
• separate administrator and accounting responsibilities;
• periodic review of inactive users; and
• logging or audit features where available.

Segregation of duties is particularly important. The person who creates a supplier should not necessarily be the only person who approves payments. The system cannot replace organisational control, but it can support it.

9. Backup and Restoration

9.1 Backup principles

A backup is a recoverable copy of company data made independently of the live working environment. Copying data to another folder on the same physical disk is not sufficient protection against disk failure, malware, theft, or physical damage.

A practical policy may combine:

• daily operational backups;
• periodic full backups;
• an off-site or cloud-protected copy where permitted;
• retention periods based on legal and business needs; and
• periodic restoration testing.

The familiar principle of maintaining multiple copies on different media and, where feasible, in different locations is more reliable than relying on a single backup.

9.2 Backup procedure

Before backup, users should close active companies or ensure that the application supports a consistent backup state. The administrator should identify the correct data path, select the company or companies, choose a controlled destination, and record the date, time, operator, release, and backup location. Backup files should be protected against unauthorised alteration.

9.3 Restoration procedure

Restoration should be performed carefully because it may overwrite or replace current data. A controlled process is:

1. stop transaction entry;
2. preserve the current data as a separate backup;
3. identify the required restoration point;
4. restore into a test or clearly designated data location;
5. verify company names, financial years, ledgers, vouchers, and reports;
6. obtain management approval; and
7. return the restored data to production only after validation.

Restoration is successful only when the data is usable, not merely when a file-copy operation completes. The organisation should periodically conduct a restoration drill and document the outcome.

10. Worked Configuration Example

Assume that Meridian Office Supplies is implemented in Tally.ERP 9 on 1 July 2024. Its statutory financial year begins on 1 April 2024, but management wants to enter transactions from 1 July 2024 onward. The correct configuration requires careful distinction:

• Financial year beginning: 1 April 2024.
• Books beginning: 1 July 2024, if the system is intended to maintain books only from implementation date.
• Base currency: the entity’s domestic currency.
• Accounting basis: the basis required by the entity and applicable reporting framework.
• Inventory: enabled because the entity sells physical goods.
• Bill-wise details: enabled because customers and suppliers are managed invoice by invoice.
• Cost centres: enabled for the wholesale and retail divisions.
• Statutory features: enabled only after registration details and tax requirements are verified.

The accountant should not assume that setting the books beginning date to 1 July eliminates the need to account for opening balances. Opening receivables, payables, inventory, cash, bank balances, fixed assets, capital, and loans must be supported by reconciled schedules and entered through an approved opening-balance process.

11. Illustrative Case: Northstar Engineering Services

Background

Northstar Engineering Services, a medium-sized service business, replaces spreadsheets with Tally.ERP 9. It has two branches, approximately 20 users, multiple service contracts, and statutory reporting obligations.

Problem

During the first month, users enter transactions into different companies and use inconsistent customer names. The company also stores its only backup on the same laptop used for accounting. Management reports do not agree with the spreadsheet opening balances.

Analysis

The problem is not simply user error. It reflects weak governance at three levels: company structure was not designed before implementation; master-data standards were absent; and business-continuity controls were inadequate. In addition, opening balances were not independently reconciled.

Approach and solution

The finance manager establishes one company with branch-wise cost centres, defines a naming convention for customer and supplier masters, and assigns user roles. A controlled opening-balance schedule is prepared and approved. Daily backups are sent to a protected location, with weekly restoration tests during the first month. A configuration register records financial-year dates, currency, statutory settings, enabled features, and authorised changes.

Outcome

Branch reporting becomes consistent, receivable balances can be traced to customer accounts, and management receives reliable monthly reports. The restoration test confirms that the organisation can recover data without depending on the original laptop.

Learning points

1. Configuration is an accounting-control activity, not merely an IT activity.
2. Master-data governance is essential for meaningful reporting.
3. Opening balances require reconciliation and approval.
4. Backup effectiveness must be demonstrated through restoration.
5. User training and segregation of duties reduce operational risk.

12. Common Challenges and Limitations

Incorrect financial-year settings

Incorrect dates can place transactions in the wrong period or make comparative reporting difficult. The remedy is controlled planning before company creation and documented approval for changes.

Duplicate or inconsistent masters

Different spellings of the same customer or supplier fragment balances. Naming conventions, search procedures, and periodic master review are necessary.

Overdependence on software defaults

Defaults may not reflect the organisation’s accounting policy or local law. Every significant default should be reviewed.

Weak migration controls

Data imported from spreadsheets may contain duplicates, invalid dates, unbalanced opening balances, or unsupported tax classifications. Migration should include cleansing, mapping, trial balances, reconciliations, and sign-off.

Inadequate version and compatibility management

Legacy software may not be supported indefinitely. Organisations should monitor operating-system compatibility, statutory updates, licence status, security exposure, and migration options. Tally.ERP 9 is a legacy product in many environments; release-specific support and current alternatives should be evaluated before deployment.

Privacy and cybersecurity risks

Accounting data contains personal, commercial, payroll, and tax information. Access, backups, removable media, remote access, and data transfer should be governed by privacy policies and applicable data-protection law.

13. Best-Practice Implementation Checklist

Before going live, the responsible team should confirm:

• authorised software and licence status;
• supported installation and documented data path;
• correct company identity and legal details;
• financial year and books beginning date;
• base and foreign-currency settings;
• accounting, inventory, cost-centre, and bill-wise requirements;
• statutory registration information;
• user roles and segregation of duties;
• opening balances and migration reconciliations;
• printer and report testing;
• backup and restoration testing; and
• management approval of the configuration register.

A post-implementation review should be conducted after the first reporting cycle. It should examine unusual balances, tax reports, receivable and payable ageing, inventory reconciliation, user access, backup logs, and configuration changes.

Chapter Summary

Installation and company configuration establish the foundation of Tally.ERP 9 accounting. The implementation process begins with planning the operating environment, data path, users, licence, statutory regime, and reporting requirements. Activation must be lawful and documented. Company creation requires accurate legal identity, financial-year dates, books beginning date, currency, and security settings.

Company selection, alteration, shutting, and deletion have different consequences and must be controlled. F11 features and F12 configuration should be enabled according to documented business needs. Statutory settings require professional review because software cannot replace legal interpretation or accounting judgement. Backup is effective only when restoration is possible and tested. Finally, access controls, master-data standards, opening-balance reconciliation, and configuration documentation transform a software installation into a reliable accounting information system.

Key Terms

Company: A logical Tally data set representing an entity or reporting unit.

Activation: The authorised process of enabling licensed software use.

Data path: The location where company data is stored.

Financial year beginning: The date on which the entity’s reporting year starts.

Books beginning date: The date from which accounting records are maintained in the company.

Base currency: The principal currency used for company accounting and reporting.

Foreign currency: A currency other than the company’s base currency.

F11 Features: Broad functional options controlling accounting, inventory, taxation, payroll, and related capabilities.

F12 Configuration: Detailed settings controlling application behaviour and presentation.

Ledger: An account used to record transactions of a particular type or party.

Master data: Relatively stable records such as ledgers, stock items, customers, and suppliers.

Voucher: A structured record of an accounting transaction.

Bill-wise details: Tracking of receivables and payables against individual references.

Cost centre: A classification used to analyse transactions by department, project, branch, or responsibility area.

Statutory settings: Configuration relating to legal, tax, payroll, or regulatory requirements.

Backup: A recoverable copy of accounting data.

Restoration: The process of returning backed-up data to an operational state.

Segregation of duties: Division of responsibilities to reduce error and fraud risk.

Configuration register: An authorised record of important system settings and changes.

Opening balances: Account balances transferred into the system at the beginning of implementation or a reporting period.

Review Questions

Short Answer Questions

1. Distinguish between the financial year beginning date and the books beginning date.
2. What is the difference between shutting a company and deleting a company?
3. Identify four matters that should be planned before installing Tally.ERP 9.
4. Why should statutory settings be reviewed by a qualified professional?
5. What is the purpose of a restoration test?

Long Answer Questions

1. Explain the complete process of installing and activating Tally.ERP 9, including licensing and governance controls.
2. Discuss the principal decisions involved in creating and configuring a new company.
3. Explain how F11 Features and F12 Configuration affect accounting information processing.
4. Describe a robust backup, restoration, and business-continuity policy for a medium-sized organisation.
5. Evaluate the importance of user security, segregation of duties, and master-data governance in Tally.ERP 9.

Analytical / Application Questions

1. A company begins using Tally.ERP 9 on 1 October, while its statutory year began on 1 April. Recommend appropriate financial-year and books-beginning settings and explain the required opening-balance controls.
2. A business discovers that identical suppliers were created under three different names. Analyse the reporting and control consequences and propose a corrective procedure.
3. A finance manager claims that copying the Tally data folder to another folder on the same laptop is an adequate backup. Critically evaluate the claim and design a stronger backup and restoration arrangement.

Multiple Choice Questions with Answers

Question 1

Which setting establishes the date on which the entity’s reporting year starts?

A. Books beginning date

B. Financial year beginning date

C. Voucher date

D. Backup date

Correct Answer: B. Financial year beginning date

Question 2

What is the principal purpose of activating Tally.ERP 9?

A. To create duplicate companies

B. To enable authorised licensed use

C. To calculate all taxes automatically

D. To eliminate the need for backups

Correct Answer: B. To enable authorised licensed use

Question 3

Which action removes a company from the active session without deleting its data?

A. Shutting the company

B. Deleting the company

C. Altering the company

D. Reinstalling the software

Correct Answer: A. Shutting the company

Question 4

Which feature is most directly associated with tracking receivables against individual invoices?

A. Cost centres

B. Bill-wise details

C. Stock categories

D. Payroll units

Correct Answer: B. Bill-wise details

Question 5

Why should a restoration test be performed?

A. To increase the licence period

B. To verify that backup data can actually be recovered and used

C. To change the company currency

D. To remove inactive ledgers

Correct Answer: B. To verify that backup data can actually be recovered and used

Question 6

Which principle gives users only the access required for their duties?

A. Maximum privilege

B. Least privilege

C. Universal access

D. Unrestricted administration

Correct Answer: B. Least privilege

Question 7

Which setting is most relevant when a business wants departmental expenditure analysis?

A. Cost centres

B. Currency symbol

C. Company mailing name

D. Data path

Correct Answer: A. Cost centres

Question 8

What is a major risk of entering transactions into the wrong company?

A. Improved consolidation

B. Misstatement of company-specific reports

C. Automatic data encryption

D. Shorter backup time

Correct Answer: B. Misstatement of company-specific reports

Question 9

Which statement about statutory configuration is correct?

A. Software settings replace professional tax judgement

B. Statutory settings should be based on current law and verified registration information

C. Tax rates never require review after installation

D. All organisations should enable every statutory module

Correct Answer: B. Statutory settings should be based on current law and verified registration information

Question 10

Which practice provides the strongest evidence that a backup policy is effective?

A. Renaming the backup file

B. Storing every copy on the same laptop

C. Periodically restoring a backup and validating reports

D. Printing the Company Info menu

Correct Answer: C. Periodically restoring a backup and validating reports