Tax Tribunal: Software License Expenses as Revenue Expenditure vs. Capital Expenditure Decision

The Tribunal upheld the ld. CIT(A)'s decision to allow software license expenses as revenue expenditure, except for one-time software for indexing operations, which was treated as capital expenditure. The software did not meet the tests for capitalization as it did not provide enduring benefit, was essential for routine operations, and did not alter fixed capital. The Tribunal found that the software expenses were correctly treated as revenue expenditure, in line with relevant case law. The Revenue's appeal was dismissed, and the decision was pronounced on 30th June 2015.

---

---

Issues:
Challenge to the action of the ld. CIT(A) in allowing software license expenses as revenue expenditure.

Analysis:
In this appeal, the assessee contested the action of the ld. CIT(A) in permitting the expenses of &8377; 63,92,692/-, spent on software license acquisition, as revenue expenditure. The assessee, engaged in pre-employment screening, claimed deduction of &8377; 69,59,572/- for software license fees, treating them as deferred revenue expenditure in its books. The A.O. disallowed this deduction, but the ld. CIT(A) allowed it, leading to the Department's appeal. The Department argued that the ld. CIT(A) erred in not considering the A.O.'s observations. Conversely, the assessee's counsel contended that the software expenditure was not capital, did not provide enduring benefit, and was essential for routine operations, citing a relevant High Court decision.

The expenses claimed during the year were detailed, showing a total of &8377; 67,04,692/- incurred. The assessee treated these expenses as deferred revenue expenditure, part of which was from earlier years. The A.O. considered it capital expenditure, disallowing the deduction and depreciation. The Special Bench's tests for capital expenditure were discussed, and it was found that the software did not meet the ownership, enduring benefit, or functionality test for capitalization. The software was not owned, did not provide lasting benefit, and was essential for efficient operations, not altering the fixed capital. The ld. CIT(A) correctly held it as revenue expense, except for one-time software for indexing operations, which was treated as capital expenditure.

The ld. CIT(A) correctly analyzed the factors, including the enduring benefit and nature of the software, in line with relevant case law. The Tribunal upheld the ld. CIT(A)'s decision, dismissing the Revenue's appeal. The order was pronounced on 30th June, 2015.

---