Company Creation and System Configuration

Introduction

A computerised accounting system begins with a correctly designed company file. In Tally, the company file stores the identity of an organisation, its accounting period, reporting currency, ledgers, vouchers, inventory information, tax settings, users and security controls. Company creation is therefore not merely a data-entry task. It is the first stage of establishing the structure within which accounting information will be recorded and reported.

Incorrect configuration can produce misleading financial statements, incorrect tax calculations, duplicate records and weak audit trails. Conversely, a carefully configured company supports accurate transaction processing, efficient reporting and controlled access to financial information. This chapter introduces the practical and conceptual foundations needed to create, alter and secure a company in Tally and to configure essential financial, accounting, statutory and user settings.

Menu names and screen layouts may differ slightly between Tally editions and releases. The underlying principles, however, remain substantially consistent.

Learning Objectives

After studying this chapter, a learner should be able to:

1. Explain the purpose and structure of a company in Tally.
2. Create a company using appropriate identity, address and financial-period information.
3. Configure the financial year, books beginning date and reporting currency.
4. Select suitable accounting, inventory and invoicing features.
5. Configure basic statutory settings responsibly.
6. Alter company information without damaging historical records.
7. Apply user roles, passwords, security controls and backup practices.
8. identify common configuration errors and recommend corrective action.

1. The Company as an Accounting-System Unit

In manual accounting, records are usually organised in books and files. In Tally, the company is the logical container for those records. A company normally represents one legal or operational entity whose transactions are maintained separately from those of other entities.

A company contains several interrelated elements:

A company should generally correspond to the reporting boundary used by management and applicable law. If two legally separate entities are mixed in one company, their income, expenses, assets and liabilities may be incorrectly combined. If one entity is split unnecessarily, consolidated analysis becomes more difficult.

Company, financial year and books beginning date

The financial year is the period for which financial statements are prepared. The books beginning date is the date from which transactions are entered in the company. These dates may coincide, but they need not always do so. For example, an organisation may create a company during the financial year while entering opening balances from an earlier date.

The distinction is important:

• The financial year determines the reporting period and year-end.
• The books beginning date determines the earliest date for transaction entry.
• Opening balances represent positions brought forward from an earlier system or period.

The dates must be selected in accordance with the organisation’s accounting policy and legal requirements. A wrong date can place transactions in the wrong year and distort comparative reporting.

2. Creating a Company

Company creation should be treated as a controlled setup procedure rather than an informal experiment. Before opening the creation screen, gather the organisation’s legal name, address, contact details, tax-registration information, financial-year dates, base currency and opening balances.

A typical creation sequence is:

1. Open the company-selection or company-management area.
2. Choose the option to create a new company.
3. Enter the company name and mailing or registered address.
4. Enter contact details and applicable tax-registration information.
5. Select the financial year beginning date.
6. Select the books beginning date.
7. Set the base currency and currency-symbol preferences.
8. Define security and access options.
9. Accept and save the company configuration.
10. Review the configuration before entering transactions.

Identity and contact information

The company name should be entered consistently with authoritative organisational records. A trading name may be useful for invoices, but the legal name should not be replaced where statutory reports require the legal identity. Address, telephone number, email address and website information should be accurate because they may appear on invoices and correspondence.

The contact details of an accountant or administrator should be maintained separately from the legal identity of the entity. Confusing the two can result in inaccurate documents or inappropriate disclosure of personal information.

Base currency

The base currency is the principal currency used for books and reports. It should normally be the currency in which the entity prepares its financial statements. Currency details may include:

• currency name;
• currency symbol;
• number of decimal places;
• formal name for amounts in words; and
• rules for foreign-currency transactions.

For example, if the base currency is Indian rupees, the company may use ₹ and two decimal places. The choice must be consistent with the entity’s reporting requirements. Currency configuration does not by itself create a bank exchange rate or guarantee correct foreign-currency valuation; those matters require properly maintained rates and accounting policies.

3. Financial Configuration

Accounting period and reporting integrity

Financial statements are meaningful only when transactions are assigned to the correct reporting period. Before entering transactions, verify:

• financial-year beginning and ending dates;
• current period displayed on the gateway or dashboard;
• books beginning date;
• treatment of opening balances; and
• whether comparative figures are required.

A transaction dated before the books beginning date may be rejected or require a change in configuration. Changing dates after transactions have been entered can create serious control and reporting problems. Such changes should be authorised, documented and tested.

Opening balances

Opening balances are the balances brought into the new company from an earlier accounting system or period. They should be supported by an approved trial balance. The basic equality is:

This equality applies to a balanced double-entry trial balance. It does not prove that every account is correctly classified or that all transactions are complete. A trial balance can agree even when an expense has been posted to the wrong ledger.

Opening balances should be entered only after reconciliation of bank accounts, receivables, payables, inventory and fixed assets. For example, the opening receivable balance should agree with an approved customer-wise schedule, not merely with a single unexplained total.

4. Accounting, Inventory and Invoicing Features

Tally provides feature controls that determine the functions available to the company. Enabling every feature is not good practice. Unused functions increase complexity and may permit entries that the organisation does not understand or control.

Accounting features

Accounting features may include maintenance of accounts, bill-wise details, cost centres, interest calculation, budgets, scenarios and other management-accounting functions.

Bill-wise details are useful where receivables and payables must be tracked invoice by invoice. They support outstanding reports, allocation of receipts and identification of overdue balances.

Cost centres allow expenses or income to be analysed by department, project, branch or activity. Before enabling them, management should define a clear coding structure. A cost-centre system without ownership and review can generate detailed but unreliable data.

Budgets and controls can support comparison between planned and actual amounts. They are management tools and do not replace statutory accounting records.

Inventory features

Inventory features are relevant when the organisation purchases, stores or sells goods. Configuration may include stock groups, stock categories, stock items, units of measure, godowns or locations, batches and valuation methods.

Inventory should not be enabled merely because the organisation has occasional purchases. A service organisation may require only accounting and invoicing. A trading organisation normally needs inventory records and reconciliation between stock quantities and financial values.

The chosen inventory valuation method must be consistent with the organisation’s accounting policy and applicable standards. Users should not change valuation methods casually because the change may affect cost of sales, closing stock and profit.

Invoicing and voucher numbering

Sales and purchase invoicing settings affect the information printed on business documents. Configure voucher types, numbering, narration requirements, tax details, payment terms and document titles carefully.

Automatic numbering reduces duplicate numbers, but authorised users should understand how cancellations, deletions and alterations affect the sequence. Where regulations require a continuous or controlled invoice sequence, gaps must be investigated and documented rather than silently ignored.

5. Statutory and Tax Configuration

Statutory settings connect accounting records with legal reporting obligations. They may include tax registration, indirect tax, withholding tax, payroll-related compliance and other jurisdiction-specific requirements. The exact settings depend on the country and the applicable version of Tally.

A responsible setup process includes:

1. identifying the entity’s registrations and obligations;
2. confirming registration numbers from official documents;
3. selecting the correct state, country or tax jurisdiction;
4. entering effective dates;
5. configuring tax ledgers and rates according to current law;
6. testing a representative transaction; and
7. reconciling system reports with statutory returns.

Tax rates and rules change. A software default is not evidence that a rate is legally correct. The accountant or authorised tax professional must verify current requirements. Tally can calculate and report tax according to configured rules, but it cannot replace professional interpretation of legislation.

Tax information is sensitive. Registration numbers, customer details and transaction values should be accessible only to authorised personnel. Statutory reports should be reviewed before submission, including tax classifications, exemptions, reverse-charge treatment where relevant, and credit or debit adjustments.

6. Altering a Company

Company alteration is used to update information such as address, contact details, financial settings, features, tax details or security options. Alteration must be distinguished from editing an individual transaction or master.

A controlled alteration procedure is:

1. identify the reason for change;
2. obtain approval from the responsible officer;
3. take a verified backup;
4. record the old and new values;
5. make the change in the appropriate configuration area;
6. test reports and transaction entry;
7. document the outcome; and
8. communicate the change to affected users.

Changing a company name or address may affect future documents, but it should not rewrite history improperly. If a legal entity changes because of incorporation, merger or restructuring, the accountant should determine whether a new company file, a new financial period or a documented alteration is required. The answer depends on legal continuity, reporting requirements and audit policy.

Avoid deleting a company as a substitute for correcting an error. Deletion may permanently remove records. Where possible, correct the configuration, preserve evidence and maintain an audit trail.

7. Security and User Administration

Accounting data represents financial assets and confidential information. Security is therefore an internal-control responsibility, not merely an information-technology preference.

Users and roles

Users should receive the minimum access necessary for their duties. Typical roles include:

A person who creates vendors, approves payments and alters bank records may have excessive power. Separation of duties reduces the risk of error and fraud. In small organisations, complete separation may not be possible, so compensating review controls should be introduced.

Passwords and authentication

Use individual user accounts rather than shared passwords. Passwords should be difficult to guess, kept confidential and changed according to organisational policy. If the software supports stronger authentication, it should be enabled where practical.

Security controls may include:

• restricting access to company data;
• restricting alteration or deletion of vouchers;
• controlling access to payroll and tax reports;
• using edit logs or audit features;
• locking closed periods; and
• reviewing user access regularly.

Security is effective only when permissions match actual responsibilities. A password-protected company with universal administrator access is not adequately controlled.

8. Backup, Restoration and Data Governance

A backup is a separate copy of company data that can be restored after accidental deletion, hardware failure, malware, corruption or other loss. Saving a second copy on the same computer is not a complete backup strategy.

A practical policy includes:

• scheduled backups;
• at least one copy stored separately from the working device;
• restricted access to backup files;
• clear naming and dating of backups;
• periodic restoration tests; and
• documented responsibility for backup monitoring.

A backup that has never been restored in testing cannot be assumed to be reliable. Restoration should be tested in a controlled environment so that live data is not overwritten accidentally.

Data governance also covers retention, confidentiality, accuracy and disposal. Records should be retained for the period required by law and organisational policy. Exporting reports to spreadsheets can create uncontrolled copies; exported files should be protected and deleted when no longer required.

9. Worked Configuration Example

Illustrative example: Sunrise Office Supplies

Sunrise Office Supplies is a small trading business beginning computerised accounting on 1 April. It sells stationery, maintains inventory and is registered for the applicable indirect tax. Management has approved separate analysis of administration and sales expenses.

The administrator should:

1. create a company using the authorised legal name and address;
2. set the financial year beginning date to 1 April and confirm the books beginning date;
3. select the reporting currency and two decimal places where appropriate;
4. enable accounting, inventory, invoicing and bill-wise receivable/payable functions;
5. create stock groups, units and stock items using an approved naming convention;
6. enable cost centres and create Administration and Sales cost centres;
7. enter verified tax-registration details and configure tax ledgers only after checking current law;
8. create separate user accounts for the operator, supervisor and owner;
9. restrict the operator from altering company configuration and deleting vouchers;
10. import or enter an approved opening trial balance and reconcile customer, supplier and inventory schedules;
11. record a backup before live transaction entry; and
12. test one purchase, one sale, one receipt and one payment, then inspect the resulting reports.

The test should verify that the purchase updates stock and supplier liability, the sale updates revenue and stock records, the receipt reduces the customer balance, and the payment reduces the bank or cash balance. Tax reports, stock reports and the trial balance should also be reviewed. Testing is not complete merely because the voucher was accepted by the software.

10. Common Problems and Corrective Practices

Wrong financial year

Problem: Transactions appear in an unexpected period.

Cause: Incorrect year beginning date or books beginning date.

Practice: Stop entry, take a backup, obtain approval and correct the configuration using a documented procedure. Review affected transactions and reports.

Duplicate company or ledger

Problem: Two similar companies or ledgers create fragmented balances.

Cause: Poor naming discipline or failure to search existing masters.

Practice: Use a naming convention and review existing records before creating new ones. Do not merge or delete records without assessing historical impact.

Excessive features

Problem: Users select incorrect options or reports become confusing.

Cause: Features enabled without operational need or training.

Practice: Enable only required features and document their purpose.

Incorrect tax setup

Problem: Tax is calculated incorrectly or appears in the wrong return.

Cause: Wrong registration, rate, classification, effective date or ledger treatment.

Practice: Verify legal requirements, test representative transactions and reconcile reports with official records.

Uncontrolled administrator access

Problem: Users can alter configuration and delete records without review.

Cause: Shared credentials or excessive permissions.

Practice: Establish named users, role-based access and periodic access reviews.

11. Ethical, Professional and Contemporary Considerations

Accounting-system configuration involves professional judgment. Users must not manipulate dates, tax classifications, descriptions or voucher numbers to conceal transactions or produce a preferred result. Corrections should be transparent and supported by evidence.

Cloud-connected accounting, remote access and automated data exchange can improve efficiency but increase dependence on connectivity, vendor controls and cybersecurity. Artificial intelligence may assist with document capture, classification or anomaly detection, but generated classifications must be reviewed. An automated suggestion is not an accounting authorisation.

Contemporary practice increasingly emphasises audit logs, role-based access, electronic invoicing, bank feeds, data backups and integration with tax platforms. These tools are valuable only when master data, permissions and review procedures are sound. Automation amplifies the quality of configuration: it can accelerate accurate processing, but it can also accelerate repeated errors.

Case Study: Greenfield Services

This is an illustrative case.

Background

Greenfield Services operated a consultancy and a small equipment-rental activity. Its administrator placed both activities in one company file, enabled inventory, used a shared administrator password and entered the consultancy’s opening balances without reconciling the bank account.

Problem

Management could not determine whether profit arose from consulting or rentals. Several invoices displayed an incorrect address, the tax report contained inconsistent classifications and the bank balance did not agree with the statement.

Analysis

The problem was not a single posting error. It resulted from weak company design, inadequate master-data planning, incorrect security and absence of opening-balance verification. Enabling inventory did not solve the lack of an agreed rental-asset policy.

Approach and solution

The owner approved a configuration review. The accountant took a backup, documented existing settings and decided that both activities could remain in one company because they belonged to the same legal entity, but they would be separated through appropriate income, expense, asset and cost-centre structures. Unnecessary inventory features were removed or restricted after assessing operational requirements. The address and tax details were verified against official documents. Separate users were created, the administrator password was changed, and the opening balances were reconstructed from bank, receivable and payable schedules.

Test transactions were entered and reports were reviewed before live processing resumed. A monthly bank reconciliation and quarterly user-access review were introduced.

Outcome

Management obtained activity-wise reports, the bank difference was identified as an omitted outstanding cheque, and tax classifications became reviewable. The system was not made reliable by a single software command; reliability resulted from corrected configuration, reconciled data, controlled access and continuing review.

Learning points

1. A company should reflect legal and reporting boundaries.
2. Features must follow business requirements.
3. Opening balances require evidence and reconciliation.
4. Security controls are part of accounting control.
5. Configuration changes should be approved, backed up and tested.

Chapter Summary

Company creation establishes the identity, reporting period, currency, masters, transactions, features and security environment of an accounting system. Correct financial-year and books-beginning dates are essential for period reporting. Accounting, inventory, invoicing and cost-centre features should be enabled according to genuine business requirements. Statutory settings must be verified against current law and tested through representative transactions.

Altering a company requires approval, backup, documentation and post-change testing. User roles should follow the principle of least privilege, with separation of duties wherever practical. Individual accounts, strong passwords, audit features, backups and restoration tests protect the reliability and confidentiality of accounting information. Finally, technology and automation support good accounting only when the underlying configuration, data and professional review are sound.

Key Terms

Company: The logical accounting unit containing an organisation’s masters, transactions, settings and reports.

Financial year: The annual reporting period for which financial statements are prepared.

Books beginning date: The date from which transactions may be recorded in the company.

Base currency: The principal currency used for accounting records and reports.

Opening balance: An account balance brought forward from an earlier period or system.

Master: A permanent record such as a ledger, stock item, group or unit.

Voucher: A document or entry used to record an accounting transaction.

Ledger: An account used to record transactions relating to a particular item, person, asset, liability, income or expense.

Cost centre: A unit used to analyse income or expenditure by department, project or activity.

Bill-wise details: Invoice-level information used to track receivables and payables.

Inventory: Goods held for sale, production or consumption in business operations.

Statutory settings: Configuration related to legal, tax and regulatory requirements.

Role-based access: User permissions assigned according to job responsibility.

Audit trail: A record of activity, alteration or access that supports review and accountability.

Backup: A separate copy of data used for recovery.

Restoration: The process of recovering data from a backup.

Least privilege: Giving a user only the access necessary for assigned duties.

Reconciliation: Comparing independent records and investigating differences.

Books: The accounting records maintained for an entity.

Review Questions

Short Answer Questions

1. What is the purpose of a company in Tally?
2. Distinguish between the financial year and the books beginning date.
3. Why should accounting features be enabled selectively?
4. What is an opening balance?
5. State two purposes of role-based access.

Long Answer Questions

1. Explain the complete procedure for creating a company and reviewing its initial configuration.
2. Discuss the relationship between accounting, inventory, invoicing and cost-centre features.
3. Explain the controls that should be followed when altering company information.
4. Describe how statutory and tax settings should be configured and tested.
5. Discuss the importance of backup, restoration testing and data governance in an accounting system.

Analytical / Application Questions

1. A company has entered transactions under the wrong financial year. Design a safe corrective procedure, including approvals, backup and review.
2. A small business uses one shared administrator password and allows all staff to delete vouchers. Analyse the risks and propose a practical access-control structure.
3. An organisation sells both goods and services but has enabled every available feature in Tally. Recommend a configuration and testing plan based on business requirements, reporting needs and internal controls.

Multiple Choice Questions with Answers

Question 1

What is the primary purpose of a company in Tally?

A. To store only printed invoices

B. To contain an entity’s accounting records, settings and reports

C. To replace all accounting policies

D. To provide internet access to users

Correct Answer: B. To contain an entity’s accounting records, settings and reports

Question 2

Which date determines the annual reporting period?

A. The voucher date

B. The invoice due date

C. The financial-year beginning date

D. The backup date

Correct Answer: C. The financial-year beginning date

Question 3

What should support an approved opening trial balance?

A. An unverified estimate

B. Reconciled schedules and supporting records

C. A new password

D. A stock-group name

Correct Answer: B. Reconciled schedules and supporting records

Question 4

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

A. Maximum privilege

B. Least privilege

C. Automatic numbering

D. Currency conversion

Correct Answer: B. Least privilege

Question 5

Why are cost centres used?

A. To analyse income or expenditure by activity or department

B. To change the base currency

C. To delete old vouchers

D. To create user passwords

Correct Answer: A. To analyse income or expenditure by activity or department

Question 6

Which action is most appropriate before a major company alteration?

A. Delete the company

B. Share the administrator password

C. Take a verified backup and obtain approval

D. Disable all reports

Correct Answer: C. Take a verified backup and obtain approval

Question 7

What is the main purpose of bill-wise details?

A. Tracking invoices and outstanding receivables or payables

B. Changing the legal name

C. Creating a backup

D. Setting screen colours

Correct Answer: A. Tracking invoices and outstanding receivables or payables

Question 8

Which statement about tax configuration is correct?

A. Software defaults always prove the legal tax rate

B. Tax settings should be verified against current law and tested

C. Tax settings never require review

D. Tax registration details are irrelevant to reports

Correct Answer: B. Tax settings should be verified against current law and tested

Question 9

What is a reliable backup practice?

A. Keeping the only copy on the working computer

B. Making a separate copy and periodically testing restoration

C. Printing one invoice

D. Using one shared password

Correct Answer: B. Making a separate copy and periodically testing restoration

Question 10

Why should features not be enabled indiscriminately?

A. Unused features can increase complexity and control risk

B. Features prevent all accounting errors

C. Features eliminate the need for reconciliation

D. Features automatically interpret tax law

Correct Answer: A. Unused features can increase complexity and control risk