High Court rules software expenditure as revenue, not capital for Assessment Years 2000-01 & 2001-02.

The Madras High Court dismissed the appeals regarding the treatment of software expenditure for the Assessment Year 2000-01 and 2001-02, holding that the expenditure should be treated as revenue rather than capital. The court emphasized the rapid obsolescence of software, its off-the-shelf nature, and the necessity for operational activities. Drawing a distinction from a Delhi High Court case, the court ruled in favor of the assessee, citing the principle that not all enduring benefits lead to capital expenditure disallowance. The appeals were dismissed, and no costs were awarded.

---

---

Issues:
1. Whether software expenditure is to be treated as a revenue expenditure or a capital expenditureRs.

Analysis:
The appeals before the Madras High Court were directed against the common order of the Income Tax Appellate Tribunal regarding the treatment of software expenditure for the Assessment Year 2000-01 and 2001-02. The substantial question of law framed in both appeals was whether software expenditure should be considered as a revenue expenditure or a capital expenditure. The assessee claimed that the software used was essential for their banking business and thus should be treated as revenue expenditure. However, the Assessing Officer argued that the expenditure provided an enduring benefit, making it capital in nature. The Tribunal considered the rapid obsolescence of software due to advanced technology, the off-the-shelf nature of the software, and the assessee's right to use it, ultimately deciding in favor of treating the expenditure as revenue. The Tribunal also noted that if the expenditure were treated as capital, depreciation similar to that applicable to computers should be granted.

In a comparative reference to a decision by the Delhi High Court in a similar case involving a telecom operator, the Madras High Court highlighted the importance of analyzing the specific facts and circumstances of each case. The Delhi High Court case involved the treatment of software expenses as revenue or capital based on the nature of the software and its integration with hardware in a lease agreement. The Madras High Court distinguished this case from the present one, emphasizing that the software in question was not customized and was necessary for various operational activities. Citing the principle laid down by the Supreme Court in Empire Jute Co. Ltd. v. CIT, the Madras High Court explained that not all enduring benefits lead to capital expenditure disallowance, especially if the advantage facilitates trading operations or enhances business efficiency without affecting fixed capital. The court agreed with the assessee's argument that software quickly becomes obsolete due to technological advancements, supporting the Tribunal's decision to treat the expenditure as revenue.

In conclusion, the Madras High Court dismissed the appeals, answering the substantial question of law in favor of the assessee and against the revenue. No costs were awarded, and connected miscellaneous petitions were closed.

---