2013 (9) TMI 1127 - AT - Income Tax

Assessee's Appeals Dismissed, Expenses Treated as Capital Expenditure

The Tribunal dismissed all three appeals filed by the assessee for the assessment years 2006-07, 2007-08, and 2008-09, upholding the classification of ... Condonation of delay under section 5 of the Limitation Act - sufficient cause - capital expenditure vs revenue expenditure - enduring benefit test - software development as tangible asset - depreciation on softwareCondonation of delay under section 5 of the Limitation Act - sufficient cause - Whether the delay in filing the appeals before the Tribunal should be condoned. - HELD THAT: - The assessee explained delay by affidavit attributing inaction to transfer of the officer handling tax matters and subsequent belated scrutiny of records by a replacement, which prompted filing. Having considered the explanation and applying the guiding principle in Vedabai alias Vaijayanthabai Baburao Patil v. Shantaram Baburao Patil that 'sufficient cause' must receive a liberal construction and that courts should adopt a pragmatic approach in condoning delay, the Tribunal found the explanation sufficient. The Tribunal noted the distinction between inordinate delays and shorter delays and held that on the facts presented the delay was not wilful or deliberate and warranted condonation in the interest of substantial justice. [Paras 5, 6]Delay in filing the appeals is condoned and the appeals are admitted for hearing.Capital expenditure vs revenue expenditure - enduring benefit test - software development as tangible asset - depreciation on software - Whether the product development expenses claimed as revenue expenditure are in fact capital expenditure and thus not allowable as revenue deduction. - HELD THAT: - The Assessing Officer treated the product development expenditure as capital, observing that the assessee derived enduring benefits and relying on precedents holding acquisition of technical know-how or software can be capital in nature; depreciation at 15% was allowed. The Tribunal, following its earlier detailed decision in the assessee's own case for AY 2003-04, applied the functional and enduring benefit tests: expenditure is capital if it results in an advantage of enduring benefit forming part of the profit-making apparatus. The Tribunal noted instances of acquisition and ownership of software and related divisions, and the authority that computer software can constitute a tangible asset whose use in business justifies capital treatment and depreciation. The assessee did not point to any distinguishing facts for the year under appeal to depart from the earlier Tribunal decision. The alternative submission for higher rate of depreciation was rejected on the same footing as in the earlier year. [Paras 14, 15, 16]Product development expenditure held to be capital expenditure; appeal dismissed and alternative plea for different depreciation rejected.Final Conclusion: The Tribunal condoned the delay in filing the appeals and, on merits, dismissed the appeals for AY 2006-07, 2007-08 and 2008-09, holding the product development expenditure to be capital in nature (allowing depreciation as applied), and rejecting the assessee's claim to treat the expenditure as revenue expenditure or to change the rate of depreciation. Issues Involved:1. Delay in filing appeals2. Classification of product development expenses as capital or revenue expenditure3. Depreciation rate applicable to software development expensesDetailed Analysis:1. Delay in Filing Appeals:The appeals filed by the assessee were delayed by 456 days. The reason provided for the delay was the transfer of the Assistant Vice President handling tax matters to Singapore and the subsequent delay in appointing a replacement. The Tribunal found the explanation satisfactory and cited the Hon'ble Supreme Court's decision in Vedabai alias Vaijayanthabai Baburao Patil v. Shantaram Baburao Patil and Others, which emphasized a pragmatic approach in condoning delays. The Tribunal condoned the delay and admitted the appeals for hearing.2. Classification of Product Development Expenses:The primary issue was whether the product development expenses incurred by the assessee should be classified as capital expenditure or revenue expenditure. The assessee argued that these expenses were routine and should be treated as revenue expenditure. However, the Assessing Officer (AO) and the Commissioner of Income Tax (Appeals) [CIT(A)] treated these expenses as capital expenditure, granting 15% depreciation. The AO relied on the Hon'ble Rajasthan High Court judgment in CIT v. Arawali Construction Co. Pvt. Ltd., which held that acquiring technical know-how is a capital expenditure, and the Hon'ble Supreme Court's decision in Tata Consultancy Services v. State of Andhra Pradesh, which recognized software development as a tangible asset. The Tribunal upheld this classification, noting that the assessee gained enduring benefits from the developed software, which justified treating the expenses as capital expenditure.3. Depreciation Rate Applicable to Software Development Expenses:The assessee alternatively argued for a higher depreciation rate of 60% on software development expenses. However, the Tribunal noted that in the assessment year 2003-04, only 15% depreciation was allowed. Consequently, the Tribunal rejected the alternative ground and maintained the 15% depreciation rate.Conclusion:The Tribunal dismissed all three appeals filed by the assessee for the assessment years 2006-07, 2007-08, and 2008-09, upholding the AO's and CIT(A)'s decisions to classify the product development expenses as capital expenditure and allowing only 15% depreciation. The Tribunal's decision was consistent with prior rulings in the assessee's case and relevant judicial precedents.