Tax Management India. Com
Law and Practice  :  Digital eBook
Research is most exciting & rewarding
  TMI - Tax Management India. Com
Follow us:
  Facebook   Twitter   Linkedin   Telegram

Home Case Index All Cases Income Tax Income Tax + AT Income Tax - 2005 (12) TMI AT This

  • Login
  • Cases Cited
  • Referred In
  • Summary

Forgot password       New User/ Regiser

⇒ Register to get Live Demo



 

2005 (12) TMI 454 - AT - Income Tax


Issues Involved: Deletion of additions made on account of software development expenses for assessment years 1997-98 and 1998-99.

Issue-wise Detailed Analysis:

1. Nature of Software Development Expenses:
The primary issue revolves around whether the software development expenses incurred by the assessee should be treated as capital expenditure or revenue expenditure. The assessee amortized expenditures of Rs. 1,36,77,664 and Rs. 1,70,68,811 on software and professional expenses as deferred revenue expenditure but claimed the entire amount as revenue expenditure while computing total income. The Assessing Officer (AO) treated these expenses as capital in nature, arguing that the software had an enduring benefit, and thus disallowed the expenses. The AO also denied depreciation on the grounds that it was unclear whether the software was put to use during the relevant year.

2. Assessee's Argument:
The assessee argued that the software technology was rapidly changing and thus had no enduring benefit. The software was installed to enhance business efficiency and did not create any asset generating income. The expenditures were primarily for license fees, technical support, documentation, and professional charges, not for acquiring the software itself. The assessee contended that these expenditures were for upgrading existing systems and should be treated as revenue expenditure.

3. CIT(Appeals) Decision:
The learned CIT(Appeals) considered various judicial decisions and concluded that the expenditures were revenue in nature. The CIT(Appeals) relied on decisions from the Kerala High Court, the Supreme Court, and the Jaipur Bench of the Tribunal, which supported the assessee's claim. The CIT(Appeals) allowed the assessee's claim, noting that no case law favoring the department was presented.

4. Department's Argument:
The department, represented by the learned DR, argued that the expenditures were capital in nature, drawing support from the decision of the Delhi Bench of the Tribunal in the case of Maruti Udyog Ltd. The department contended that even expenses on upgradation should be treated as capital expenditures.

5. Tribunal's Analysis:
The Tribunal examined the facts and the nature of the expenditures. It noted that the software was not attached to any machinery used in production nor was it part of the production process. The software facilitated better management decisions but did not generate income directly. The Tribunal emphasized that the assessee had acquired only the right to use the software and not ownership, which did not create a new asset or source of income.

6. Enduring Benefit Test:
The Tribunal discussed the test of enduring benefit, citing the Calcutta High Court's decision that this test is not conclusive and should not be applied mechanically. It referenced the Madras High Court's decision that expenditures facilitating business operations without affecting fixed capital are revenue in nature. The Tribunal found that the software expenditures facilitated business management and were thus revenue expenditures.

7. Rapid Technological Advances:
The Tribunal acknowledged the Supreme Court's observations on rapid technological advances, noting that the enduring benefit test is less applicable in fast-changing fields like information technology. The Tribunal concluded that the expenditures for upgrading technology should be treated as revenue expenditures.

8. Alternative Plea for Depreciation:
The assessee's cross-objections included an alternative plea for depreciation if the expenditures were treated as capital in nature. Since the Tribunal allowed the expenditures as revenue, this plea was dismissed as infructuous.

Conclusion:
The Tribunal dismissed the department's appeals and the assessee's cross-objections, upholding the CIT(Appeals) decision to treat the software development expenses as revenue expenditures. The expenditures were deemed necessary for business efficiency and did not create any new asset or income source, aligning with judicial precedents and the nature of the expenditures.

 

 

 

 

Quick Updates:Latest Updates