Chartered Certified Accountant (CCA)
Tally ERP 9
•
Post Graduate
Inventory and Order Management
Introduction and Context
Inventory is the bridge between purchasing, production, sales and financial reporting. In Tally.ERP 9, inventory management is not merely the recording of quantities. It involves designing a stock master structure, recording movements, linking quantities with accounting values, controlling locations and batches, and producing information for operational and statutory decisions.
For a Chartered Certified Accountant, the central issue is integration. A purchase receipt affects stock quantity and may also create a liability; a sales delivery reduces stock and may precede invoicing; a return reverses part or all of an earlier movement; and the selected valuation method affects reported gross profit and closing inventory. Tally.ERP 9 permits these processes to be represented through inventory vouchers, accounting vouchers, or integrated inventory-accounting transactions, depending on company configuration.
The exact menu labels and available features may vary with release, licensing, localisation and enabled company features. Therefore, users should verify the configuration in the particular Tally.ERP 9 environment before implementation.
Learning Objectives
By the end of this chapter, the learner should be able to:
design stock groups, categories, items and units;
configure godowns, locations and batch-wise inventory;
create and interpret price lists;
process purchase and sales orders, receipts, deliveries and returns;
record physical stock adjustments;
select and evaluate inventory valuation methods;
reconcile physical, book and financial inventory records;
assess control, audit and governance risks in inventory processing.
1. The Inventory Master Architecture
A reliable inventory system begins with disciplined master-data design. Tally.ERP 9 separates the description of an item from its classification, location, measurement and commercial terms.
1.1 Stock groups
A stock group classifies items according to a common characteristic, such as product family, department, material type or reporting requirement. Examples include “Finished Goods”, “Electronic Components” and “Office Supplies”. Stock groups may be created hierarchically, allowing a parent group such as “Finished Goods” to contain subgroups such as “Laptops” and “Printers”.
Groups support summarised reporting, but they should not be used to store every attribute of an item. Excessive or inconsistent grouping creates duplicated classifications and weakens analysis. A group should answer a meaningful reporting question.
1.2 Stock categories
A stock category provides an additional, parallel classification. For example, products may be grouped by brand in stock groups and by technical specification in stock categories. Categories are useful when management needs cross-classification without changing the primary group hierarchy.
The distinction is important:
Master
Main purpose
Example
Stock group
Primary hierarchical classification
Finished Goods → Printers
Stock category
Parallel classification
Laser, Inkjet
Stock item
Actual inventory unit
HP LaserJet 4100
Godown
Physical or logical location
Main Warehouse
Unit
Quantity measurement
Nos., kg, litre
Batch
Lot or traceability identity
Batch B24-07
1.3 Stock items
A stock item is the lowest practical level at which quantities and values are recorded. Item creation normally includes the item name, group, category where relevant, unit of measure, opening balance, tax-related details and valuation settings. Item names should be unambiguous and should follow a documented naming convention.
For example, “Cable” is inadequate if the business sells cables of different lengths and specifications. “USB-C Cable, 1 m, 60 W” is more informative. Poor naming produces duplicate items, inaccurate reorder analysis and difficulty in physical verification.
1.4 Units of measure
Tally.ERP 9 supports simple units, such as numbers, kilograms and litres, and compound units, such as “dozen of pieces” or “box of 24 pieces”, subject to configuration. The unit selected should represent the basis on which quantities are purchased, stored and sold.
Where conversion is used, the relationship must be stable and documented. If one box always contains 24 units, then:
1 box = 24 pieces
If the contents vary by package, a single fixed conversion is inappropriate; the organisation may need separate stock items, batch information or supplementary packaging records.
2. Locations, Batches and Traceability
2.1 Godowns and locations
A godown is a physical or logical inventory location. It may represent a warehouse, shop, production store, consignment location, damaged-goods area or vehicle. Godowns can be organised hierarchically, for example:
Main Warehouse → Finished Goods Store → Dispatch Section.
Location-level records allow management to identify where stock exists, distinguish usable from quarantined inventory, and control transfers. A transfer between godowns changes location, not necessarily total company inventory. It should not be treated as a purchase or sale.
2.2 Batch-wise details
Batch management is important for pharmaceuticals, food, chemicals, spare parts and any product requiring expiry or recall control. A batch may carry a manufacturing date, expiry date and quantity. Batch control enables the organisation to identify affected customers when a product recall occurs.
Batch information is not a substitute for inventory valuation. It identifies a lot; the valuation method determines how cost is assigned when units are issued. In practice, batch selection should follow operational policy, often first-expiry-first-out (FEFO) for perishable goods. FEFO is a physical issue policy and should not be confused with the accounting method FIFO.
2.3 Control implications
Godown and batch data are valuable only when users are required to enter them consistently. Controls should include:
restricted creation and alteration of masters;
approval for new items and units;
mandatory batch and expiry fields for regulated items;
separation between warehouse custody and accounting approval;
periodic reconciliation of location records with physical counts.
3. Inventory Valuation and Quantitative Reasoning
Inventory valuation determines the cost assigned to closing inventory and the cost transferred to expense or cost of goods sold. A basic inventory identity is:
Opening inventory + Purchases − Cost of goods sold = Closing inventory
This identity assumes that adjustments such as write-downs, production transfers and abnormal losses are separately incorporated where applicable.
For a periodic trading operation:
Cost of goods sold = Opening inventory + Net purchases − Closing inventory
Net purchases generally mean purchases after adjusting for purchase returns, relevant direct costs and other applicable adjustments. The exact accounting treatment depends on the reporting framework and the organisation’s policy.
Common cost-flow methods include:
FIFO: earliest-cost units are assumed to be issued first;
Weighted average: issue cost reflects an average of available costs;
Specific identification: the actual cost of an identifiable unit is assigned;
Standard cost: issues are recorded at a predetermined standard, with variances tracked separately where the system and policy support it.
For weighted average cost:
Weighted average cost per unit = Cost of units available ÷ Units available
The formula applies when the relevant units are homogeneous and the costs included are measured on a consistent basis. It excludes taxes or charges that are recoverable and includes costs that the applicable accounting framework treats as inventory cost.
Worked example: weighted average valuation
Assume a business has 100 units at CU 10 each and purchases 50 units at CU 14 each. There are 120 units available for sale during the period after issuing 30 units.
Cost available is:
(100 × CU 10) + (50 × CU 14) = CU 1,700
Units available are 150. The weighted average cost is:
CU 1,700 ÷ 150 = CU 11.3333 per unit, approximately
If 30 units are issued at this average cost, issue cost is approximately CU 340. Closing quantity is 120 units and closing value is approximately CU 1,360. The small rounding difference must be controlled through the system’s costing and rounding policy.
Tally.ERP 9 reports may display stock value according to the configured valuation method and report date. The accountant must ensure that the chosen method is consistently applied and agrees with the entity’s accounting policy. A software-generated value is not automatically compliant merely because it appears in a report.
4. Price Lists and Commercial Control
A price list defines selling prices or price levels for specified stock items, often according to quantity slabs, customer classes, dates or rates. It can support retail, wholesale, distributor and institutional pricing.
A price list should be controlled through:
effective dates;
price levels or customer categories;
minimum and maximum quantity slabs where applicable;
discount policy;
authorisation for changes;
review of obsolete prices.
Price lists are commercial tools, not valuation methods. A selling price does not determine inventory cost. Mixing these concepts can produce incorrect margin analysis.
5. The Inventory and Order Cycle
The order cycle separates commitment from actual movement. A purchase order records an intention or commitment to buy; a receipt records goods physically received. A sales order records a customer commitment; a delivery note records goods dispatched.
A simplified control flow is:
Inventory order and movement cycle
Figure: Inventory order and movement cycle
Figure: Relationship between orders, physical movement and invoicing.
5.1 Purchase orders and receipts
A purchase order records supplier, item, quantity, rate, expected delivery and other terms. It normally does not by itself increase physical inventory. A receipt or goods receipt records the actual quantity accepted into a godown. Differences between ordered and received quantities should be investigated rather than silently overwritten.
A purchase invoice records the supplier’s claim and the accounting effect. Depending on the organisation’s process, the receipt and invoice may be recorded separately or combined. Separate recording provides stronger three-way matching:
Purchase order quantity → Receipt quantity → Invoice quantity
The three quantities need not be identical, but differences should be authorised and documented.
5.2 Sales orders and deliveries
A sales order records the customer’s order and may reserve or commit stock operationally. It does not necessarily reduce stock. A delivery note records dispatch and reduces available inventory when the system is configured to update stock at delivery. The sales invoice records revenue, receivable and tax effects according to the accounting process.
The accountant must understand whether the organisation recognises revenue at dispatch, delivery, acceptance or another point required by its reporting framework. Tally configuration should reflect, not replace, that policy.
5.3 Returns
Purchase returns send rejected or excess goods back to a supplier. Sales returns bring goods back from a customer. Returns should reference the original transaction wherever possible, identify the condition of returned goods and distinguish resalable, damaged and quarantined stock.
A returned item is not automatically available for resale. Inspection and quality status are operational controls that may require separate godowns or stock categories.
5.4 Physical stock
A physical stock voucher records the result of a count when physical quantity differs from book quantity. It should be used only after a controlled count, not as a routine method of correcting careless entries.
A proper count process includes count sheets, independent counters, cut-off procedures for receipts and dispatches, investigation of variances and approval of adjustments. Material discrepancies may indicate theft, damage, recording errors or process failure.
6. Practical Configuration Sequence
A robust implementation sequence is:
Activate inventory features and relevant integrated accounting options.
Define units of measure and conversion rules.
Create godowns and location hierarchy.
Design stock groups and optional categories.
Create stock items with consistent naming.
Enable batch-wise details and expiry tracking where required.
Enter opening balances only after agreeing them to approved schedules.
Configure valuation and invoice/order settings.
Define price lists and approval responsibilities.
Test purchase, sales, transfer, return and physical stock scenarios.
Reconcile inventory reports with the general ledger and physical records.
This sequence reduces the risk of creating transactions before the underlying masters and policies are properly defined.
7. Applied Case: Meridian Medical Supplies
The following is an illustrative case.
Background
Meridian Medical Supplies operates one central warehouse and two branches. It sells medicines and diagnostic consumables. Before implementation, it used spreadsheets and recorded purchases only when invoices arrived. Expiry dates were not consistently recorded, and branch managers could not identify stock held at each location.
Problem
The business experienced expired stock, unexplained differences between warehouse and accounting records, and incorrect gross margins caused by inconsistent purchase costs. Customer returns were mixed with saleable inventory.
Analysis
The control weaknesses arose from four design failures: no location hierarchy, no batch discipline, inadequate separation of receipt and invoice, and no approved valuation policy. The problem was therefore not simply a lack of reports; it was a deficient transaction model.
Approach and solution
Meridian created godowns for the central warehouse, each branch, damaged stock and quarantine stock. Stock groups classified medicines and consumables, while stock items captured strength, pack size and unit. Batch-wise details with manufacturing and expiry dates were enabled for regulated products.
Purchase orders were approved centrally. Goods receipts recorded actual quantities and batch details. Supplier invoices were matched with receipts. Sales orders were entered by branches, and deliveries selected batches using an expiry-focused issue policy. Customer returns entered quarantine until inspection. A documented weighted-average valuation policy was applied consistently, and monthly physical counts were introduced.
Outcome
Management could identify stock by branch, batch and condition. Expired inventory was isolated earlier, invoice discrepancies were investigated before payment, and gross-margin reporting became more reliable. The system did not eliminate judgement: management still had to approve write-downs, investigate variances and review the reasonableness of valuation results.
Learning points
The case demonstrates that inventory software creates value only when master data, physical processes, accounting policy and user responsibilities are aligned. Traceability, valuation and order processing are interconnected but distinct control objectives.
8. Audit, Governance and Professional Issues
Inventory is susceptible to overstatement, fictitious purchases, premature revenue recognition, duplicate items, unauthorised price changes and manipulation of physical counts. Important controls include role-based access, audit trails, maker-checker approval, sequential voucher review and periodic backup.
Accountants should examine:
whether all godowns are included in stock reports;
whether negative stock is permitted and properly explained;
whether inactive or duplicate items remain in use;
whether stock valuation agrees with policy;
whether goods received but not invoiced are identified;
whether sales orders are incorrectly treated as sales;
whether returns and damaged goods are separately controlled;
whether batch and expiry data are complete.
Data integrity is also an ethical issue. Users must not alter dates, quantities or rates merely to obtain a preferred profit figure. Access rights should be proportionate to job responsibilities, and sensitive reports should be protected from unauthorised disclosure.
9. Technology and Contemporary Developments
Although Tally.ERP 9 is a desktop-oriented ERP platform, inventory management increasingly interacts with barcode systems, handheld counting devices, electronic purchase documents, cloud backups and business-intelligence tools. Integration can reduce duplicate entry, but it introduces interface risks such as duplicated transactions, failed synchronisation and inconsistent item codes.
Artificial intelligence may assist with demand forecasting, anomaly detection and reorder recommendations. It should not autonomously alter accounting records without review. Forecasts depend on clean historical data and may fail during structural changes, product discontinuation or supply disruption. Professional judgement, documented approvals and an auditable source trail remain necessary.
10. Challenges and Best Practices
Common challenges include excessive item creation, inconsistent units, unrecorded transfers, negative stock, incomplete batch data, delayed receipts and mismatch between commercial and accounting processes.
Best practices are to:
maintain a formal master-data policy;
use standard naming and coding conventions;
limit creation and alteration rights;
reconcile quantity, location and value regularly;
document valuation and return policies;
investigate negative stock rather than normalising it;
conduct cycle counts in addition to annual counts;
match orders, receipts and invoices;
separate damaged and returned goods;
retain evidence for material adjustments;
test reports after every significant configuration change.
Chapter Summary
Inventory and order management in Tally.ERP 9 combines master-data design, physical control, transaction processing and valuation. Stock groups, categories, items, units, godowns and batches provide the structure through which inventory is identified and reported. Purchase and sales orders record commitments, while receipts and deliveries record physical movements. Returns and physical stock vouchers require controlled investigation. Inventory valuation methods determine the allocation of cost between closing inventory and cost of goods sold, but selling price lists serve a separate commercial purpose. Effective implementation depends on consistent policies, authorisation, reconciliation, auditability and ethical use of system access.
Key Terms
Stock group: Hierarchical classification of inventory items.
Stock category: Parallel classification used for cross-analysis.
Stock item: Individual inventory master for which quantity and value are recorded.
Unit of measure: Standard basis for measuring inventory quantity.
Compound unit: Unit combining two measurement levels, such as box and pieces.
Godown: Physical or logical location where inventory is stored.
Batch: Identifiable lot of inventory used for traceability.
Expiry date: Date after which a batch may no longer be saleable or usable.
Purchase order: Authorised request or commitment to purchase goods.
Sales order: Customer order recorded before dispatch or invoicing.
Receipt: Record of goods physically received.
Delivery note: Record of goods dispatched to a customer or location.
Purchase return: Goods returned to a supplier.
Sales return: Goods returned by a customer.
Physical stock voucher: Entry used to record verified physical quantity differences.
FIFO: Cost-flow assumption assigning earliest available costs to issues.
Weighted average: Costing method based on average cost of available units.
Price list: Approved schedule of selling prices or price levels.
Three-way matching: Comparison of purchase order, receipt and supplier invoice.
Negative stock: Book condition in which recorded issues exceed recorded available quantity.
Review Questions
Short Answer Questions
Distinguish a stock group from a stock category.
Why is batch-wise inventory important for medicines and food products?
What is the difference between a purchase order and a goods receipt?
State the inventory identity linking opening inventory, purchases, cost of goods sold and closing inventory.
Why should returned goods be placed in a quarantine or separate location before inspection?
Long Answer Questions
Explain the complete inventory master architecture in Tally.ERP 9 and discuss the consequences of poor master-data design.
Compare FIFO, weighted-average and specific-identification costing, including their control and reporting implications.
Describe the purchase and sales order cycles from commitment through receipt, delivery and invoicing.
Discuss the role of godowns, batches and physical stock procedures in inventory control.
Design an internal-control framework for inventory management in a multi-location organisation.
Analytical / Application Questions
A company’s purchase order is for 1,000 units, its receipt is for 960 units and its supplier invoice is for 1,000 units. Analyse the accounting and control steps that should follow.
A warehouse reports 500 units physically, while the system reports 560 units. Develop a procedure to investigate, document and correct the discrepancy.
A business uses selling price lists but reports inconsistent gross margins across branches. Identify possible causes involving valuation, units, returns, discounts and master data, and recommend tests.
Multiple Choice Questions with Answers
Question 1
Which Tally.ERP 9 master primarily represents an individual product for quantity and value recording?
A. Stock group
B. Stock category
C. Stock item
D. Godown
Correct Answer: C. Stock item
Question 2
A transfer of goods from one godown to another normally changes which factor without changing total company inventory?
A. Customer liability
B. Location
C. Sales revenue
D. Purchase cost
Correct Answer: B. Location
Question 3
Which document normally records a commitment to purchase rather than an actual receipt of goods?
A. Purchase order
B. Receipt note
C. Physical stock voucher
D. Purchase return
Correct Answer: A. Purchase order
Question 4
A business has 100 units costing CU 10 each and 50 units costing CU 14 each. What is the weighted average cost per unit before any issue?
A. CU 10.00
B. CU 11.33 approximately
C. CU 12.00
D. CU 14.00
Correct Answer: B. CU 11.33 approximately
Question 5
Which information is especially relevant to batch-wise inventory?
A. Customer credit limit
B. Expiry date
C. Ledger closing balance
D. Salesperson commission
Correct Answer: B. Expiry date
Question 6
What is the principal purpose of a price list?
A. To determine physical stock quantity
B. To classify godowns
C. To define approved selling prices
D. To replace inventory valuation
Correct Answer: C. To define approved selling prices
Question 7
Three-way matching commonly compares which set of documents?
A. Sales order, delivery and sales return
B. Purchase order, receipt and supplier invoice
C. Price list, godown and batch record
D. Journal, trial balance and bank statement
Correct Answer: B. Purchase order, receipt and supplier invoice
Question 8
Which transaction most directly records a verified difference between physical and book quantity?
A. Stock journal only
B. Physical stock voucher
C. Sales order
D. Price list alteration
Correct Answer: B. Physical stock voucher
Question 9
Under the inventory identity, if opening inventory and purchases are known, closing inventory is reduced when:
A. Cost of goods sold increases
B. Sales order quantity increases without dispatch
C. Price list rates increase
D. A godown is renamed
Correct Answer: A. Cost of goods sold increases
Question 10
Why should returned goods often be placed in quarantine before resale?
A. To increase their selling price
B. To avoid recording the return
C. To determine their condition and resale status
D. To convert them automatically into purchases
Correct Answer: C. To determine their condition and resale status