Cost Accounting, Budgets and Responsibility Reporting

Introduction and context

Cost accounting converts financial transactions into information about the resources consumed by products, services, departments, projects and managers. In a computerised accounting environment, the usefulness of cost information depends not only on correct ledger entries but also on a carefully designed classification and allocation structure. Tally.ERP 9 supports this structure through cost centres, cost categories, allocation features, budgets, scenarios and variance-oriented reports.

For a Chartered Certified Accountant, the objective is not merely to operate menus. It is to design information that supports planning, control, accountability and managerial decisions. A cost-centre report is valuable only when the centre has a responsible manager, a defined purpose, reliable allocation rules and a reporting frequency appropriate to the decision being made.

Tally.ERP 9 normally records financial transactions through ledgers and vouchers while simultaneously permitting relevant income and expenditure to be assigned to cost centres. The resulting information can be analysed by department, branch, product line, project, employee group or any other organisational dimension. Configuration names and report availability may vary slightly according to the release, localisation and enabled features; therefore, an organisation should test its configuration before relying on reports for external reporting or major decisions.

Learning objectives

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

1. explain the role of cost accounting in responsibility accounting;
2. distinguish cost centres from cost categories and allocation bases;
3. configure and use cost centres in Tally.ERP 9;
4. apply suitable allocation methods to shared costs;
5. prepare budgets and interpret budget-versus-actual information;
6. use scenarios for provisional or alternative analysis;
7. evaluate variances and assign responsibility fairly;
8. identify control, ethical and implementation risks; and
9. design a practical cost-management system for managerial decision-making.

1. Cost accounting and responsibility accounting

Cost accounting classifies, measures and assigns costs to objects of management interest. A cost object may be a product, customer, project, department, contract or service. Responsibility accounting extends this idea by relating financial results to managers who can influence them.

A responsibility centre may be:

A manager should normally be evaluated only on controllable items. A production manager may control overtime and material usage but not a centrally imposed insurance charge. Allocating that insurance charge may be useful for product costing, but it should not automatically be used to judge the production manager’s performance.

The central distinction is therefore between:

• cost assignment, which identifies where a cost is recorded; and
• performance responsibility, which identifies who can influence the cost.

Confusing these purposes produces unfair reports and dysfunctional decisions.

2. Cost centres in Tally.ERP 9

A cost centre is a unit, person, activity or location for which costs or revenues are collected. Examples include Administration, Production, Sales–North, Project A and Maintenance. In Tally.ERP 9, cost-centre accounting is generally enabled through F11: Accounting Features, where the organisation selects cost-centre accounting and, where required, the option to allocate income as well as expenditure.

Cost centres are generally created through the Accounts Info area. A hierarchy can be used where a parent centre contains subsidiary centres, such as:

• Sales Department
• Domestic Sales
• Export Sales
• Production Department
• Assembly
• Finishing

A good cost-centre master should have:

1. a stable and unambiguous name;
2. a defined managerial owner;
3. a clear inclusion and exclusion rule;
4. a relationship to the chart of accounts and organisation structure; and
5. a review date.

During voucher entry, the user records the transaction in a ledger and then enters the amount against one or more cost centres in the cost-centre allocation screen. For example, a salary payment may be allocated between Administration and Sales according to employee deployment. A single voucher can contain multiple allocations, provided the allocation total agrees with the relevant voucher amount.

Cost centre versus ledger

A ledger answers the question, “What type of transaction occurred?” A cost centre answers, “For which organisational unit or activity did it occur?” Rent Expense is a ledger; Branch A is a cost centre. Both dimensions are necessary for useful analysis.

Cost centre versus cost category

A cost centre is normally a single dimension of analysis. A cost category permits parallel classification through multiple dimensions. For example, a company may analyse salary costs simultaneously by:

• department: Production, Sales and Administration; and
• employee type: Permanent, Contract and Trainee.

The first dimension may be represented by cost centres and the second by a cost category. Cost categories are particularly useful when management requires independent views of the same transaction. They should not be created merely because the software permits them; excessive dimensions increase data-entry effort and the risk of inconsistent coding.

3. Allocation methods and cost-driver logic

Direct costs should be assigned directly whenever reliable evidence exists. For example, material issued exclusively to Project A should be charged directly to Project A. Shared or common costs require an allocation basis.

Common bases include:

The allocation percentage for centre i under a chosen driver can be expressed as:

The allocated amount is:

Here, driver units must be measured consistently for all centres, and the denominator must include every centre receiving the shared cost. The formula applies when the cost is allocated proportionally to a single driver and the total allocation equals the original cost.

Worked example: allocating rent

A company pays monthly rent of ₹120,000. The occupied areas are:

Production receives 120,000 × 600 ÷ 1,000 = ₹72,000. Sales receives ₹36,000 and Administration receives ₹12,000. The allocated amounts total ₹120,000, so there is no unexplained residual.

The allocation is mathematically correct, but managerial validity depends on the assumption that occupied area is a reasonable proxy for rent consumption. If rent is driven by market location rather than area, a more refined method may be appropriate.

Allocation and absorption

Allocation distributes a common cost among receiving centres. Absorption applies an accumulated cost to a product, service or output unit. For example, a factory overhead cost may first be allocated to production departments and then absorbed into products using machine hours.

An absorption rate can be calculated as:

The activity base may be machine hours, labour hours or units, depending on the causal relationship. The rate is meaningful only when the activity base is defined consistently and the relevant capacity assumptions are stated.

4. Practical configuration and control in Tally.ERP 9

A disciplined implementation follows a sequence rather than creating masters ad hoc.

Step 1: define the reporting purpose

Management should decide whether the system is intended for departmental control, project costing, product profitability, branch comparison or several purposes. Each purpose may require a separate category or hierarchy.

Step 2: design the master structure

Create cost-centre groups and centres that mirror responsibility and operational activity. Avoid temporary labels such as “Miscellaneous” unless a documented review process exists.

Step 3: enable relevant features

Use the accounting features to enable cost-centre accounting and, where appropriate, income allocation and cost categories. Security controls should restrict feature changes to authorised personnel.

Step 4: create and test masters

Enter sample transactions and verify that the cost-centre allocation totals equal the ledger amount. Test reversals, credit notes, transfers and year-end transactions.

Step 5: establish coding rules

A written policy should specify which expenses are direct, which are shared, the approved allocation basis, the person responsible for coding and the evidence required for changes.

Step 6: reconcile and review

The total of cost-centre allocations should reconcile with the related ledger balance. Differences may arise from omitted allocations, incorrect dates, cancelled vouchers, opening balances or transactions posted without the required cost-centre classification.

Useful reports commonly include cost-centre break-ups, category summaries, group-wise analysis, budgets and variance views. Report labels and navigation can differ by release, so the accountant should verify the underlying ledger totals rather than relying on the appearance of a report alone.

5. Budgets and planning control

A budget is a quantified plan for a specified period. In Tally.ERP 9, budgets may be defined for groups, ledgers and cost centres, depending on the organisation’s configuration and reporting needs. Budgets can support control over expenditure, sales, production-related costs and other financial expectations.

A sound budget system has three levels:

1. strategic assumptions, such as expected demand and capacity;
2. operating budgets, such as sales, labour, materials and overheads; and
3. responsibility budgets, assigned to managers and cost centres.

A fixed budget is prepared for one activity level. A flexible budget adjusts expected cost to the actual activity level. A simple mixed-cost model is:

This model assumes that fixed cost remains constant within the relevant range and variable cost per unit is stable. It is unsuitable when step costs, nonlinear behaviour or major price changes are material.

Budget variance

For a cost item, a basic variance is:

A positive value indicates spending above budget and is commonly called adverse; a negative value indicates spending below budget and is commonly called favourable. However, favourable cost variance is not automatically good: it may result from poor quality, delayed maintenance or uncompleted work.

For meaningful control, actual cost should often be compared with a flexible budget rather than a fixed budget. For example, if actual production is higher than planned, material cost may reasonably be higher. The relevant question is whether cost per unit or usage efficiency was controlled.

Worked example: flexible budget

A service department has monthly fixed cost of ₹50,000 and variable cost of ₹80 per service call. The original budget was 1,000 calls, but actual activity was 1,200 calls. The fixed budget is 50,000 + 80 × 1,000 = ₹130,000. The flexible budget for actual activity is 50,000 + 80 × 1,200 = ₹146,000.

If actual cost is ₹150,000, the fixed-budget variance is ₹20,000 adverse, whereas the flexible-budget variance is only ₹4,000 adverse. The second comparison gives a more useful measure of cost control because it recognises the higher activity level.

6. Scenarios and provisional analysis

A scenario is a temporary or alternative set of accounting information used for analysis without permanently changing the company’s principal books. Scenarios may be useful for provisional vouchers, forecasts, revised budgets, acquisition assumptions or proposed transactions. They permit management to examine possible outcomes before deciding whether to make the entries permanent.

Scenarios should not be treated as a substitute for approved accounting records. Each scenario should have:

• a stated purpose;
• an author and approval status;
• a creation date and expiry date;
• a clear distinction from actual books; and
• a documented process for acceptance, rejection or deletion.

A scenario labelled “Forecast–Q4” should not be mixed with actual transactions in a management report without an explicit reconciliation. Otherwise, users may interpret a projection as an accounting fact.

7. Responsibility reporting and variance analysis

Responsibility reporting combines accounting data with organisational accountability. A report should identify the centre, budget, actual result, variance, responsible manager and explanatory comment. The report should distinguish controllable from uncontrollable items and material from immaterial differences.

Important variance categories include:

• price variance: difference caused by a change in input price;
• usage or efficiency variance: difference caused by using more or fewer resources than expected;
• volume variance: difference caused by activity differing from plan;
• mix variance: difference caused by a changed combination of products or inputs; and
• timing variance: difference caused by transactions occurring earlier or later than budgeted.

For a simple material cost model, if standard price is SP, actual price is AP, standard quantity allowed for actual output is SQ, and actual quantity is AQ, then:

These formulas use a sign convention in which a positive cost difference is adverse and a negative difference is favourable. They apply to a standard-cost setting where the standard price and standard quantity are defined for the relevant output. If an organisation uses the opposite sign convention, the labels must be changed consistently.

Worked example: material variances

Standard data for actual output are 2,000 kg at ₹10 per kg. Actual consumption is 2,200 kg at ₹11 per kg.

Price variance = 2,200 × (11 − 10) = ₹2,200 adverse.

Usage variance = 10 × (2,200 − 2,000) = ₹2,000 adverse.

Total material cost variance = (2,200 × 11) − (2,000 × 10) = ₹4,200 adverse, which agrees with the sum of the two component variances.

Tally.ERP 9 can provide the underlying actual and budget information, but detailed standard-cost variance analysis may require carefully structured ledgers, spreadsheets, external analytics or an integrated costing system. The accountant must not imply that a standard variance report exists merely because a budget report is available.

8. Illustrative case: Meridian Components Ltd.

Background. Meridian Components manufactures electrical assemblies. Its management wants to compare the Assembly, Finishing, Sales and Administration functions. Rent, shared information-technology costs and maintenance are currently posted to general ledgers without consistent departmental attribution.

Problem. The production manager is criticised for rising overhead, although a large part of the increase results from centrally negotiated software and insurance costs. At the same time, project profitability cannot be assessed because customer-specific engineering labour is posted to a general salary ledger.

Analysis. The accountant maps direct costs to projects and departments. Engineering hours are recorded against project cost centres. Rent is allocated using occupied area, IT using authorised users, and maintenance using machine hours. Centrally controlled insurance is reported separately from controllable production costs.

Approach. Tally.ERP 9 is configured with a departmental cost-centre hierarchy and a project cost category. Allocation rules are documented. A monthly budget is entered for each responsibility centre. A provisional scenario is created for a proposed second shift, but it is excluded from actual performance reports. Monthly reports reconcile cost-centre totals to the general ledger.

Outcome. Management discovers that Assembly’s controllable cost per unit is stable, while the apparent increase was caused by centrally allocated costs and a temporary fall in production volume. The second-shift scenario shows an additional fixed cost of ₹180,000 per month and expected contribution of ₹240,000, but the decision is made conditional on achieving the forecast volume. The project analysis also identifies an unprofitable customer contract whose engineering effort had previously been hidden in general salaries.

Learning points. The case demonstrates that software cannot correct a defective responsibility model. Allocation bases must reflect causation, managers should be judged on controllable factors, and scenarios must remain clearly separate from actual results.

9. Governance, ethics and limitations

Cost accounting involves judgement and can influence bonuses, transfer prices and resource allocation. The following controls are important:

• document allocation bases and review them periodically;
• prevent unauthorised alteration of cost-centre masters;
• retain evidence for reallocations and journal corrections;
• reconcile cost-centre totals to the general ledger;
• maintain audit trails and user access logs;
• disclose material changes in budget assumptions;
• prevent managers from shifting costs to another centre to improve reported performance; and
• protect payroll, customer and project information through role-based access.

Allocation can create behavioural problems. Managers may reject shared services if charges appear arbitrary, delay necessary expenditure to meet a monthly target, or maximise a local result at the expense of the organisation. This is why performance evaluation should combine financial indicators with quality, delivery, safety, compliance and customer measures.

Budgets also have limitations. They may become obsolete in volatile markets, encourage short-termism and create budgetary slack. Rolling forecasts, driver-based planning and periodic reforecasting can supplement—though not automatically replace—the annual budget.

Artificial intelligence and analytics can assist with anomaly detection, driver discovery and forecast revision. They should be used with human review, explainable assumptions, data-quality controls and protection against automated propagation of incorrect classifications. AI-generated allocations should never bypass accounting approval or audit evidence.

10. Best-practice implementation framework

A mature Tally.ERP 9 cost-control environment should adopt the following principles:

1. Purpose before configuration: design reports around decisions and responsibilities.
2. Direct before allocated: assign costs directly where reliable evidence exists.
3. Causation before convenience: choose drivers that approximate resource consumption.
4. Controllability in evaluation: separate managerial accountability from full-cost information.
5. One source of truth: reconcile sub-analyses to the general ledger.
6. Materiality and proportionality: do not create costly detail that has no decision value.
7. Documented assumptions: record budget bases, rates, capacity and scenario status.
8. Periodic review: close obsolete centres, revise unrealistic drivers and investigate recurring variances.
9. Segregation of duties: separate master creation, transaction entry, approval and review.
10. Decision orientation: require managers to explain significant variances and propose corrective action.

Chapter Summary

Cost accounting in Tally.ERP 9 provides a second analytical dimension beyond the general ledger. Cost centres collect costs and revenues by responsibility unit, activity, project or location, while cost categories permit parallel views of the same transactions. Direct costs should be assigned directly; shared costs should be allocated using documented, causally defensible drivers. Budgets provide planned benchmarks, and flexible budgets improve interpretation when activity differs from plan. Scenarios support provisional and alternative analysis but must remain separate from actual books. Responsibility reports should distinguish controllable from uncontrollable costs and should explain, rather than merely display, variances. Effective implementation requires master-data discipline, reconciliation, access controls, ethical judgement and periodic review. The ultimate purpose is better planning, performance control and managerial decision-making—not merely more detailed reports.

Key Terms

Cost accounting: The measurement and assignment of costs for planning, control and decision-making.

Cost object: A product, service, project, customer or other item for which costs are measured.

Cost centre: An organisational unit or activity used to collect costs or revenues.

Cost category: A parallel analytical dimension used to classify transactions across cost centres.

Responsibility accounting: A system that reports results according to managers’ areas of responsibility.

Controllable cost: A cost that a particular manager can influence within a relevant period.

Direct cost: A cost traceable economically and reliably to a cost object.

Indirect cost: A cost shared by more than one cost object and requiring allocation.

Cost driver: A factor that causes or explains the consumption of resources.

Allocation: Distribution of a shared cost among receiving cost objects.

Absorption: Application of accumulated overhead to products or services.

Budget: A quantified plan for a specified period.

Flexible budget: A budget adjusted to the actual level of activity.

Budget variance: The difference between actual and budgeted or flexed results.

Scenario: A provisional or alternative set of information used for analysis.

Responsibility centre: A unit whose manager is accountable for specified results.

Price variance: A variance caused by a difference between actual and standard input price.

Usage variance: A variance caused by actual input quantity differing from the standard quantity allowed.

Budgetary slack: Deliberate understatement of expected performance or overstatement of expected cost.

Transfer pricing: Pricing of goods or services exchanged between organisational units.

Review Questions

Short Answer Questions

1. What is the difference between a ledger and a cost centre?
2. Why should a manager generally be evaluated on controllable costs?
3. State two suitable allocation bases for shared costs.
4. What is the purpose of a scenario in Tally.ERP 9?
5. Why may a flexible budget be more informative than a fixed budget?

Long Answer Questions

1. Explain the role of cost centres and cost categories in responsibility accounting, using an organisational example.
2. Describe a controlled procedure for configuring and using cost centres in Tally.ERP 9.
3. Discuss the principles governing the allocation of shared costs and the risks of arbitrary allocation.
4. Explain how budgets, scenarios and variance reports support managerial planning and control.
5. Evaluate the ethical and governance issues involved in using cost-centre reports for performance evaluation.

Analytical / Application Questions

1. A company pays ₹200,000 rent for premises occupied by Production, Sales and Administration in the ratio 5:3:2. Calculate each centre’s allocation and explain whether occupied area is necessarily an appropriate driver.
2. A department has fixed cost of ₹70,000 and variable cost of ₹50 per unit. Budgeted activity is 2,000 units, actual activity is 2,400 units and actual cost is ₹195,000. Calculate the fixed-budget and flexible-budget variances and interpret the difference.
3. Design a Tally.ERP 9 cost-centre and cost-category structure for a consulting firm serving three projects through two offices. Identify one direct-cost rule, two allocation bases and two governance controls.

Multiple Choice Questions with Answers

Question 1

Which feature primarily identifies the organisational unit or activity to which a cost relates?

A. Cost centre

B. Ledger group

C. Scenario

D. Voucher type

Correct Answer: A. Cost centre

Question 2

A company allocates ₹120,000 rent according to occupied area. Production occupies 600 of 1,000 square metres. What amount is allocated to Production?

A. ₹36,000

B. ₹60,000

C. ₹72,000

D. ₹120,000

Correct Answer: C. ₹72,000

Question 3

Which is the strongest reason for assigning a cost directly rather than allocating it?

A. Direct assignment is more traceable and usually more reliable

B. Allocated costs are never recorded in ledgers

C. Direct costs do not require supporting evidence

D. Allocation is prohibited in responsibility accounting

Correct Answer: A. Direct assignment is more traceable and usually more reliable

Question 4

What is the principal purpose of a cost category?

A. To replace all general ledgers

B. To permit parallel analytical classification of transactions

C. To convert actual data into a scenario

D. To remove the need for budgets

Correct Answer: B. To permit parallel analytical classification of transactions

Question 5

A department has fixed cost ₹50,000 and variable cost ₹80 per call. At 1,200 calls, what is its flexible budget?

A. ₹96,000

B. ₹130,000

C. ₹146,000

D. ₹150,000

Correct Answer: C. ₹146,000

Question 6

Which item should normally be excluded from a production manager’s controllable-cost evaluation if the manager cannot influence it?

A. Unauthorised overtime in the production department

B. Excess material usage caused by production methods

C. Centrally imposed insurance allocated by head office

D. Machine maintenance approved by the production manager

Correct Answer: C. Centrally imposed insurance allocated by head office

Question 7

What is the main control purpose of keeping a forecast scenario separate from actual books?

A. To prevent projected information being mistaken for recorded results

B. To ensure all forecasts are deleted immediately

C. To prevent any budget from being prepared

D. To eliminate the need for ledger reconciliation

Correct Answer: A. To prevent projected information being mistaken for recorded results

Question 8

Standard material usage is 2,000 kg, actual usage is 2,200 kg and standard price is ₹10 per kg. Using the chapter’s convention, what is the usage variance?

A. ₹2,000 favourable

B. ₹2,000 adverse

C. ₹2,200 adverse

D. ₹4,200 favourable

Correct Answer: B. ₹2,000 adverse

Question 9

Which allocation basis is generally most defensible for machine maintenance in a factory?

A. Number of sales invoices

B. Machine hours or service usage

C. Number of shareholders

D. Equal allocation regardless of use

Correct Answer: B. Machine hours or service usage

Question 10

Why should cost-centre totals be reconciled to the general ledger?

A. To verify completeness and agreement between analytical and financial records

B. To ensure all costs become direct costs

C. To remove the need for authorisation controls

D. To guarantee that every variance is favourable

Correct Answer: A. To verify completeness and agreement between analytical and financial records