Accounting Structure and Master Data

Introduction and context

In Tally.ERP 9, accounting quality depends less on the speed of voucher entry than on the quality of the structure created before transactions are recorded. The accounting structure determines how transactions are classified, reported, controlled and reviewed. Master data—groups, ledgers, cost centres, cost categories, voucher types, currencies, bill-wise references and opening balances—forms the operational foundation of that structure.

A poorly designed chart of accounts may still permit transactions to be entered, but the resulting reports can be misleading. For example, if freight inward is recorded under general administrative expenses, gross profit is distorted. If customer ledgers are created without bill-wise details, receivable ageing becomes unreliable. If opening balances are entered without reconciliation, the first period’s financial statements may contain errors that are difficult to trace.

For a Chartered Certified Accountant, master-data design is therefore a governance activity, not merely a software-operation task. It requires understanding accounting principles, organisational reporting needs, internal controls, tax and statutory requirements, and the capabilities and limitations of Tally.ERP 9.

Learning objectives

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

1. Explain the relationship between groups, ledgers and reports in Tally.ERP 9.
2. Design a fit-for-purpose chart of accounts.
3. Create and govern groups, ledgers, cost categories and cost centres.
4. Configure voucher types and numbering controls.
5. Apply currencies and exchange-rate principles correctly.
6. Use bill-wise details and opening balances to support reliable working-capital reporting.
7. Evaluate master-data risks and design suitable controls.

1. The architecture of accounting master data

Tally.ERP 9 separates relatively stable classification information from individual transactions. A useful conceptual model is:

Company → Groups → Ledgers → Vouchers → Reports

Cost categories and cost centres provide an additional analytical dimension, while currencies, bill-wise references and opening balances add transaction and period context.

1.1 Groups and ledgers

A group is a classification level used to organise ledgers. A ledger is the account in which transactions are recorded. For example, “Current Assets” is a group, while “ABC Bank—Current Account” is a ledger. A ledger normally belongs to one group, and its group determines where its balance appears in statements such as the Balance Sheet or Profit and Loss Account.

A group is not itself a transaction account. It is a reporting and classification container. A ledger, by contrast, carries balances and receives voucher entries.

Tally.ERP 9 provides predefined groups and permits users to create additional groups. The predefined Primary group is the highest-level parent for groups that are not placed under another group. Groups may be:

• Primary groups, which represent major accounting classifications; or
• Sub-groups, which are placed under a parent group for more detailed reporting.

The distinction between a group and a ledger is essential. Creating “Office Expenses” as a ledger may be acceptable for a very small entity, but creating “Office Expenses” as a group with ledgers such as stationery, printing and utilities generally produces better analysis.

1.2 Accounting classification and the accounting equation

The basic accounting identity remains:

Revenue and expenses affect capital through profit or loss. In a simplified period model:

Here, all amounts are expressed in the same accounting currency and the equations assume that the relevant balances have been completely and consistently recorded. Tally.ERP 9 does not replace these accounting principles; it applies them through groups, ledgers and vouchers.

The normal classification is:

The classification should reflect economic substance rather than the wording used in an invoice. A refundable security deposit is ordinarily an asset, even though it may be described as a “deposit expense” by a department.

2. Designing a chart of accounts

A chart of accounts is the organised list of groups and ledgers used by an entity. Its design should satisfy four requirements:

1. Faithful classification: accounts should reflect the nature of transactions.
2. Reporting usefulness: management and statutory reports should be obtainable without extensive manual reconstruction.
3. Consistency: similar transactions should be treated similarly across periods and branches.
4. Maintainability: the design should allow growth without excessive duplication.

2.1 A design method

A professional design process can follow these stages:

Stage 1: Understand the reporting environment. Identify the legal entity, branches, business segments, currencies, tax registrations, inventory requirements, departments and reporting periods.

Stage 2: Identify reporting outputs. Determine the required financial statements, trial balance, receivable and payable ageing, tax reports, cost-centre reports, branch reports and management dashboards.

Stage 3: Define the group hierarchy. Decide which distinctions belong in groups and which should be analysed through cost centres, inventory dimensions or other features.

Stage 4: Establish ledger naming standards. Names should be unique, descriptive and stable. “Rent—Head Office” is generally more useful than “Rent 1”.

Stage 5: Map legacy accounts. Existing accounts should be reviewed for duplicates, inactive accounts, incorrect classifications and incompatible opening balances.

Stage 6: Test with representative transactions. Enter sample sales, purchases, receipts, payments, adjustments, credit notes and journal entries. Review the resulting reports before migration or live use.

2.2 Avoiding excessive detail

Over-detailed charts of accounts create maintenance costs and increase miscoding. Suppose management needs expenses by department but not by every individual employee. Creating separate ledgers for “Salary—Sales Employee 1”, “Salary—Sales Employee 2” and so forth is poor design. A single salary ledger combined with department cost centres is more scalable.

Conversely, excessive aggregation can hide material information. Recording rent, insurance and repairs in one “General Expenses” ledger weakens analysis and may impair tax or statutory disclosure.

A useful principle is to place a distinction in the chart of accounts only when it changes accounting treatment, statutory reporting or an important management decision. Use cost centres when the distinction is primarily organisational or responsibility-based.

2.3 Naming and coding policy

Tally.ERP 9 permits meaningful ledger names; organisations may also use internal codes. A governance policy should specify:

• permitted abbreviations;
• treatment of punctuation and legal names;
• branch or location identifiers;
• rules for customer and supplier names;
• treatment of inactive ledgers;
• duplicate-check procedures; and
• approval authority for new masters.

For example, a customer ledger may follow the convention CUST—Legal Name—Location. Names should not be changed casually after transactions exist, because users may fail to recognise the revised account and external reconciliations may become confusing.

3. Creating groups and ledgers in Tally.ERP 9

Groups and ledgers are generally created through the Accounts Info area. Depending on the installation and security configuration, they may be created individually or in multiple mode. The exact screen labels can vary by release, but the underlying decisions remain the same.

3.1 Group creation decisions

When creating a group, the user normally specifies:

• the group name;
• the parent group;
• whether it is a primary group or a subgroup; and
• settings relevant to accounting behaviour where available.

The parent group should be chosen according to the economic nature of the balances, not according to the department that uses the account. A “Loan from Director” is a liability even if the finance department administers it.

Groups should be kept reasonably stable. Frequent restructuring changes comparative reporting and may require careful interpretation of prior-period data. If an account is moved to another group, the effect on financial statements and ratios should be reviewed.

3.2 Ledger creation decisions

A ledger typically requires:

• ledger name;
• group or parent classification;
• opening balance, where applicable;
• tax or statutory details where relevant;
• inventory or quantity settings where relevant;
• bill-wise tracking for applicable receivables and payables; and
• cost-centre allocation settings where relevant.

The ledger’s group should be selected before considering its opening balance. A debit opening balance in a customer account and a credit opening balance in a supplier account are not interchangeable merely because both are “party balances”.

Particular care is needed with common ledgers:

• Cash: normally placed under Cash-in-Hand.
• Bank accounts: placed under Bank Accounts and named by bank and account type.
• Customers: normally under Sundry Debtors.
• Suppliers: normally under Sundry Creditors.
• Sales and purchases: classified according to the nature of goods or services and reporting requirements.
• Taxes: classified according to the relevant tax receivable, payable or expense treatment.
• Fixed assets: placed under appropriate fixed-asset groups, with depreciation handled according to the organisation’s accounting policy.

The software’s classification does not by itself determine legal or accounting compliance. The entity’s accounting policy and applicable law remain authoritative.

4. Cost categories and cost centres

Financial accounting answers questions such as “What was the total salary expense?” Cost accounting additionally asks “Which department, project or employee-related responsibility incurred it?” Tally.ERP 9 supports this analysis through cost categories and cost centres.

A cost centre is a unit, person, project, activity or location for which costs or revenues are accumulated. Examples include Sales Department, Factory, Project Alpha and Branch South.

A cost category is a parallel classification structure that permits the same transaction to be analysed through more than one independent dimension. For example, a salary payment can be allocated simultaneously by department and by project. One category might contain Administrative, Sales and Production cost centres; another might contain Project A, Project B and Support Services.

The distinction can be summarised as follows:

4.1 Allocation logic

If a voucher amount is allocated among cost centres, the allocation should satisfy:

The summation applies to all allocations within the relevant allocation structure. If a salary expense of CU 100,000 is allocated as CU 60,000 to Sales and CU 40,000 to Administration, the total is CU 100,000. If the amounts do not reconcile, the voucher should not be accepted without correction.

Where percentages are used, the required condition is:

This assumes that all cost centres receiving the relevant amount are included and that rounding differences are handled under an approved policy.

4.2 Design and controls

Cost centres should represent responsibility or analytical units that management can define and maintain. A centre should have an owner, an activation date and, where appropriate, a closure date. Dormant projects should not remain available for unrestricted selection.

A cost-centre hierarchy can be useful: Region → Branch → Department → Project. However, a deep hierarchy may make voucher entry slow and increase coding errors. The organisation should decide whether an analysis belongs in a ledger, a cost centre, an inventory dimension or an external reporting system.

5. Voucher types and transaction discipline

A voucher is the transaction record through which entries are posted. Tally.ERP 9 includes standard voucher types such as payment, receipt, contra, journal, sales, purchase, debit note and credit note. Users can configure or create voucher types to support organisational requirements.

A voucher type may control or influence:

• voucher numbering method;
• prefix and suffix;
• numbering restart period;
• effective date and transaction date behaviour;
• printing configuration;
• narration and supplementary details; and
• whether the type is used for a particular transaction purpose.

5.1 Designing voucher types

A voucher type should correspond to a clear business event and approval route. Creating separate voucher types for “Payment—Cash” and “Payment—Bank” may be useful if the organisation requires distinct numbering and authorisation; otherwise, the distinction may be unnecessarily complex.

Voucher numbering should support completeness testing. A controlled sequential system makes missing numbers visible, although a missing number may reflect a cancelled voucher rather than an omitted transaction. Cancellation reasons and authorisation should therefore be retained.

Voucher types should not be used to disguise incorrect accounting classification. A custom voucher type called “Miscellaneous Adjustment” can become a control weakness if it permits users to bypass normal documentation. Exception voucher types should have restricted access and periodic review.

6. Currencies and foreign-currency accounting

Tally.ERP 9 supports transactions in currencies other than the company’s base currency, subject to configuration. The company’s base currency is used for primary accounting and reporting, while foreign currency can be selected for relevant ledgers and vouchers.

Exchange rates may be quoted as base currency units per one unit of foreign currency. Under that convention:

For example, if an invoice is USD 1,000 and the applicable rate is CU 83 per USD, the base amount is:

The formula assumes the rate is quoted as CU per USD. If the system or policy uses the inverse quotation, the calculation must be adjusted accordingly. Rate quotations must never be mixed without identifying their direction.

When settlement occurs at a different rate, an exchange difference may arise. If a USD 1,000 payable initially recorded at CU 83,000 is settled when the rate is CU 84, the settlement amount is CU 84,000 and the CU 1,000 difference is recognised according to the entity’s applicable accounting policy.

Foreign-currency controls should include:

• approved rate sources;
• date-specific rate recording;
• review of unrealised exchange differences;
• reconciliation of foreign-currency balances; and
• clear distinction between transaction currency and reporting currency.

The accounting treatment of exchange differences is governed by applicable financial reporting requirements; software configuration should implement, not replace, that policy.

7. Bill-wise details and receivable/payable control

Bill-wise details link receipts, payments, credit notes and adjustments to individual invoices or reference documents. They are essential when an entity needs invoice-level outstanding balances, ageing, collection follow-up or supplier settlement analysis.

The main reference types generally include:

• New reference: creates an outstanding invoice or bill.
• Against reference: settles or adjusts an existing bill.
• Advance: records an amount received or paid before the related invoice.
• On account: records a balance without assigning it to a specific bill.

The choice must reflect the commercial event. A receipt that settles Invoice 104 should be recorded against that reference, not merely as an on-account receipt. An advance should remain identifiable as an advance until applied to the relevant invoice.

7.1 Ageing logic

Ageing reports classify outstanding amounts according to dates and approved ageing buckets. If the reporting date is 31 March and an invoice dated 15 February remains unpaid, its age depends on the organisation’s policy and the system’s calculation convention. Credit terms may also be relevant. The policy should specify whether ageing is based on invoice date, due date or another approved date.

Bill-wise discipline supports the following control relationship:

This is a control relationship, not a substitute for reconciliation. It assumes that all relevant invoices, settlements and adjustments have been recorded and that returns, discounts and credit notes are correctly linked.

7.2 Governance risks

Common weaknesses include duplicate invoice references, use of on-account entries to avoid bill selection, failure to clear advances, and alteration of party names that obstructs matching. Periodic review should identify old advances, negative outstanding bills, unapplied receipts and credit balances in customer accounts.

8. Opening balances and migration controls

Opening balances represent the closing balances transferred from a prior period or another accounting system. They should be supported by an approved trial balance and detailed schedules.

A sound opening-balance process includes:

1. Freeze the source period and obtain an authorised closing trial balance.
2. Reconcile bank, cash, receivables, payables, inventory, loans, taxes and fixed assets.
3. Map source accounts to Tally groups and ledgers.
4. Decide whether party balances require bill-wise detail.
5. Load balances with correct debit or credit signs.
6. Enter foreign-currency balances with approved rates and currency details.
7. Validate the trial balance and financial statements.
8. Obtain documented sign-off before live posting.

The trial-balance control is:

This equality is necessary but not sufficient. A balanced trial balance can still contain a customer classified as a supplier, an omitted invoice, or an incorrect opening stock valuation.

Opening receivable and payable balances require special care. A single aggregate balance may produce a correct general ledger total but an unusable ageing report. Where bill-wise reporting is required, individual open invoices and credit balances should be loaded or reconstructed with appropriate references.

9. Master-data governance and internal control

Master data should be governed through a controlled lifecycle:

Request → Review → Approve → Create → Use → Monitor → Amend or Deactivate

The requester should provide the business rationale, proposed classification, tax or statutory details, reporting purpose and effective date. An authorised reviewer should check for duplicates and confirm the group or analytical dimension. Access should be restricted so that ordinary voucher-entry users cannot freely create or alter sensitive masters.

Important controls include:

• maker–checker approval for new ledgers and changes;
• periodic duplicate and dormant-master reviews;
• restricted alteration of opening balances;
• audit trail or change-log review where available;
• controlled user roles and passwords;
• backup before major restructuring or migration;
• reconciliation between master data and external schedules; and
• documented retention of supporting evidence.

A ledger should be deactivated rather than deleted where historical transactions or audit evidence must be preserved. Before deactivation, the organisation should confirm that no future transaction requires the ledger and that reporting implications have been considered.

Ethical and regulatory considerations

Master-data choices can influence reported profit, tax liabilities, covenant ratios and management performance. Deliberately placing expenses in inappropriate groups, creating fictitious vendors, suppressing voucher numbers or using on-account entries to conceal overdue balances is an ethical and control violation. Accountants must preserve completeness, neutrality, accuracy and traceability.

Privacy and security also matter. Party masters may contain bank details, tax identifiers and contact information. Access should follow the principle of least privilege, and exports should be protected. Software capability does not justify unrestricted access to confidential accounting data.

10. Worked application: implementing a chart for Meridian Components

Illustrative case. Meridian Components is a medium-sized manufacturer with a head office, one factory and two sales branches. Management requires statutory financial statements, branch profitability, department costs, customer ageing and foreign-currency supplier reporting.

Background and problem

The existing system contains 146 ledgers, including duplicate customer names, a single “General Expenses” ledger, supplier balances without invoice references and no distinction between factory and sales costs. Management cannot reliably compare branch performance, and the accounts team frequently posts receipts on account.

Analysis

The reporting needs show that several dimensions are being confused. Nature-based classifications belong primarily in the chart of accounts; responsibility and location belong in cost centres; invoice settlement belongs in bill-wise details; and foreign transactions require currency controls.

Approach and solution

The redesign creates:

• separate groups for sales, purchases, manufacturing expenses, selling expenses and administrative expenses;
• customer ledgers under Sundry Debtors and supplier ledgers under Sundry Creditors;
• cost centres for Head Office, Factory, Branch North and Branch South;
• a project cost category for two major installation projects;
• voucher types for standard sales, export sales, purchase, receipt, payment and controlled adjustments;
• bill-wise details for all material receivables and payables; and
• USD as an additional currency, with approved daily rates.

Factory electricity is posted to an appropriate expense ledger and allocated to the Factory cost centre. A sales promotion payment is posted to the relevant selling-expense ledger and allocated to the responsible branch. A supplier invoice is recorded as a new reference; its later payment is recorded against that reference. Customer receipts are similarly matched to invoices.

Outcome

The redesigned structure produces branch and department reports without creating hundreds of duplicate ledgers. Ageing reports identify genuinely overdue invoices, while advances remain visible. The finance manager can review foreign-currency exposure separately from base-currency financial statements. Monthly review detects inactive masters and unmatched bill-wise entries.

Learning points

1. The chart of accounts should reflect economic nature and reporting needs.
2. Cost centres are not substitutes for correct ledger classification.
3. Bill-wise detail is a control mechanism, not merely an optional convenience.
4. A balanced opening trial balance must be supported by reconciled schedules.
5. Governance is necessary to preserve the value of a well-designed structure.

11. Limitations and contemporary considerations

Tally.ERP 9 can support disciplined accounting, but it cannot determine whether a transaction is economically genuine, whether a tax treatment is legally correct, or whether a user has intentionally misclassified an entry. Reports are only as reliable as the masters and vouchers beneath them.

Organisations increasingly integrate accounting systems with banking, payroll, inventory, tax platforms and analytical tools. Integration can reduce duplicate entry but introduces risks such as duplicate masters, inconsistent identifiers, unauthorised interfaces and incomplete error handling. A master-data policy should define which system is the source of truth for each field.

Automation and AI-assisted data capture may suggest ledger classifications or extract invoice information, but suggestions require human review. Professional responsibility cannot be transferred to an automated recommendation. Exception reports, confidence thresholds, audit trails and approval controls are necessary whenever automated imports are used.

Best-practice checklist

Before going live or closing a period, confirm that:

• every ledger has an appropriate group;
• duplicate and inactive masters have been reviewed;
• cost-centre hierarchies have owners and clear purposes;
• voucher numbering and cancellation procedures are documented;
• currency rates are approved and consistently quoted;
• receivables and payables are maintained bill-wise where required;
• opening balances agree to authorised schedules;
• trial balance totals agree, and subsidiary ledgers reconcile to control accounts;
• user access matches job responsibilities; and
• changes are backed up, documented and approved.

Chapter Summary

Accounting structure in Tally.ERP 9 is built through a hierarchy of groups and ledgers, supported by voucher types and enriched by analytical and settlement dimensions. Groups classify accounts for reporting, while ledgers receive transactions and carry balances. A chart of accounts should be economically faithful, useful for reporting, consistent and maintainable.

Cost centres analyse responsibility, location, project or activity. Cost categories permit parallel analytical views when one transaction must be examined through independent dimensions. Voucher types support transaction discipline, numbering and approval. Currency configuration requires clear exchange-rate conventions and appropriate treatment of exchange differences. Bill-wise details connect settlements to invoices and support reliable ageing. Opening balances must be migrated from reconciled, authorised schedules rather than entered as unsupported totals.

The central professional lesson is that master-data design is an accounting-control function. Access governance, naming standards, duplicate prevention, reconciliations, audit trails and periodic review are necessary to ensure that Tally reports represent the entity’s underlying economic activity faithfully.

Key Terms

Accounting structure: The organised arrangement of groups, ledgers, vouchers and analytical dimensions used to record and report transactions.

Chart of accounts: The complete list and hierarchy of groups and ledgers used by an entity.

Group: A classification or reporting container for related ledgers.

Primary group: A top-level group not placed under another user-created parent group.

Sub-group: A group positioned below a parent group for more detailed classification.

Ledger: An account master that receives transactions and carries a balance.

Cost centre: A unit, project, person, location or activity for which costs or revenues are accumulated.

Cost category: A parallel structure used to analyse allocations through an independent dimension.

Voucher: A transaction record that posts accounting entries.

Voucher type: A configuration defining the purpose and controls of a class of vouchers.

Base currency: The currency used for primary books and financial reporting.

Exchange rate: The conversion relationship between a foreign currency and the base currency.

Bill-wise details: Invoice-level references used to track outstanding amounts and settlements.

New reference: A bill-wise entry that creates a new outstanding invoice or bill.

Against reference: A bill-wise entry that settles or adjusts an existing bill.

On-account entry: An entry recorded without linking it to a specific bill.

Opening balance: The balance brought forward at the beginning of an accounting period.

Master-data governance: Policies and controls governing creation, amendment, use and deactivation of masters.

Trial balance: A statement listing ledger balances to test the equality of total debits and credits.

Review Questions

Short Answer Questions

1. Distinguish between a group and a ledger in Tally.ERP 9.
2. What is the purpose of a cost category?
3. State two reasons for using bill-wise details.
4. What is meant by a voucher type?
5. Why is a balanced opening trial balance not sufficient evidence of correct migration?

Long Answer Questions

1. Explain the principles and stages involved in designing a chart of accounts for a medium-sized organisation.
2. Compare cost centres and cost categories, using an example in which both are required.
3. Discuss the controls that should govern creation and modification of ledgers and groups.
4. Explain the accounting and control implications of foreign-currency transactions in Tally.ERP 9.
5. Describe a comprehensive procedure for migrating opening balances, including bill-wise receivables and payables.

Analytical / Application Questions

1. A company has separate ledgers for salary by employee but wants departmental profitability. Analyse whether the current design is appropriate and propose a better structure.
2. A customer receipt is recorded on account even though it clearly settles three invoices. Explain the reporting consequences and design a corrective procedure.
3. During migration, the trial balance agrees but the receivables ageing report is empty. Diagnose the likely master-data problem and recommend controls for future migrations.

Multiple Choice Questions with Answers

Question 1

Which Tally.ERP 9 object primarily receives transactions and carries an account balance?

A. Group

B. Ledger

C. Cost category

D. Voucher type

Correct Answer: B. Ledger

Question 2

Which design best supports analysis of salary expense by department without creating one ledger for every employee?

A. Create a separate company for each department

B. Use one salary ledger with department cost centres

C. Record all salary in the cash ledger

D. Create a new voucher type for each employee

Correct Answer: B. Use one salary ledger with department cost centres

Question 3

A cost-centre allocation of CU 100,000 assigns CU 60,000 to Sales and CU 40,000 to Administration. What is the allocation total?

A. CU 60,000

B. CU 40,000

C. CU 100,000

D. CU 140,000

Correct Answer: C. CU 100,000

Question 4

If USD 1,000 is recorded at CU 83 per USD, what is the base-currency amount?

A. CU 830

B. CU 8,300

C. CU 83,000

D. CU 830,000

Correct Answer: C. CU 83,000

Question 5

Which bill-wise reference should normally be used when a receipt settles an identified existing invoice?

A. New reference

B. Against reference

C. On account

D. Opening balance

Correct Answer: B. Against reference

Question 6

What is the principal purpose of a voucher type?

A. To replace the chart of accounts

B. To define the purpose and controls of a class of vouchers

C. To convert all foreign currencies automatically

D. To reconcile inventory quantities

Correct Answer: B. To define the purpose and controls of a class of vouchers

Question 7

Which statement about a trial balance is correct?

A. If it balances, all ledger classifications must be correct

B. It tests equality of total debits and credits but does not prove complete accuracy

C. It contains only customer and supplier balances

D. It replaces bank reconciliation

Correct Answer: B. It tests equality of total debits and credits but does not prove complete accuracy

Question 8

A supplier invoice of USD 1,000 is initially recorded at CU 83,000 and settled at CU 84,000. What is the difference before applying the entity’s policy?

A. CU 100 gain

B. CU 1,000 difference

C. CU 83,000 difference

D. No difference

Correct Answer: B. CU 1,000 difference

Question 9

Which practice is strongest from a master-data governance perspective?

A. Allow every user to create unrestricted ledgers

B. Delete ledgers with historical transactions

C. Require review and approval for new or changed masters

D. Use on-account entries for all receipts

Correct Answer: C. Require review and approval for new or changed masters

Question 10

What is the most likely reason that a balanced migrated trial balance produces no useful receivables ageing?

A. The cash ledger is under Cash-in-Hand

B. Party balances were not loaded with bill-wise invoice references

C. A voucher type has a prefix

D. Cost centres were created

Correct Answer: B. Party balances were not loaded with bill-wise invoice references