Facts of the Case

The assessee, M/s DCM Technologies Limited, was engaged in the business of software development and export. For Assessment Year 2002-03, it filed its return declaring a loss and claimed expenditure of Rs. 2,93,20,242 towards software development.

The assessee explained that the expenditure consisted of routine business expenses such as employee salaries, travel expenses, conveyance, professional fees, repairs, depreciation and other operational costs incurred during software development activities. It was submitted that software development was an integral part of its regular business operations and the revenue generated by the company arose from marketing the software developed by it.

The Assessing Officer accepted that the expenditure was incurred in the course of business. However, he held that the software developed would possess value beyond the relevant accounting year and would have future marketing potential. On that basis, he treated 25% of the software development expenditure amounting to Rs. 73,30,060 as capital expenditure and disallowed the same.

The Commissioner of Income Tax (Appeals) deleted the disallowance. The Income Tax Appellate Tribunal upheld the order of the CIT(A). Aggrieved, the Revenue filed an appeal before the Delhi High Court under Section 260A of the Income Tax Act.

 

Issues Involved

  1. Whether software development expenditure incurred by a software company constituted revenue expenditure or capital expenditure.
  2. Whether the Income Tax Appellate Tribunal was justified in deleting the disallowance made by the Assessing Officer by treating the expenditure as revenue in nature.
  3. Whether the possibility of future revenue generation from developed software was sufficient to characterize the expenditure as capital expenditure providing enduring benefit.

 

Petitioner’s Arguments (Revenue)

The Revenue contended that:

  • The Tribunal had failed to properly appreciate the facts and had incorrectly relied upon the Supreme Court judgment in Alembic Chemical Works Co. Ltd. v. CIT.
  • Software developed by the assessee possessed future market value and potential to generate income in subsequent years.
  • Such expenditure resulted in an enduring benefit and therefore acquired the character of capital expenditure.
  • The Assessing Officer had reasonably estimated that 25% of the expenditure represented capital outlay and should not have been deleted.
  • The Tribunal, being the final fact-finding authority, erred in affirming the findings of the CIT(A).

The Revenue relied upon:

  • Alembic Chemical Works Co. Ltd. v. CIT (1989) 177 ITR 377 (SC)
  • Jonas Woodhead & Sons (India) Ltd. v. CIT (1997) 224 ITR 342 (SC)
  • CIT v. Krupp Industries India Ltd. (2000) 243 ITR 6 (SC)

 

Respondent’s Arguments (Assessee)

The assessee submitted that:

  • Software development was its core business activity.
  • The expenditure consisted of routine operational expenses such as salaries, allowances, travel, conveyance, repairs, professional fees and depreciation.
  • The expenditure was incurred wholly and exclusively for carrying on business and was therefore allowable as revenue expenditure.
  • No capital asset came into existence through such expenditure.
  • Mere possibility of future earnings from software could not convert ordinary business expenditure into capital expenditure.
  • The Assessing Officer's disallowance was based on assumptions and not supported by evidence.

 

Court Findings

The Delhi High Court observed that:

  • The assessee was primarily engaged in software development and marketing.
  • The expenditure incurred represented routine business expenditure necessary for carrying on its business activities.
  • The Assessing Officer himself accepted that the expenditure was incurred in connection with the business.
  • The disallowance was made solely on the assumption that the software might generate revenue in future years.

The Court reiterated the settled principle that no single test is conclusive for determining whether expenditure is capital or revenue in nature. The tests of “once and for all payment” and “enduring benefit” must be applied in the context of the facts of each case.

The Court noted that:

  • The expenditure did not result in acquisition of any patent, trademark, technical know-how or proprietary rights.
  • There was no creation of an independent capital asset.
  • Any advantage obtained from software development was in the revenue field and not in the capital field.
  • Rapid technological changes make software susceptible to obsolescence and therefore it cannot automatically be regarded as an enduring capital asset.

The Court distinguished the decisions relied upon by the Revenue, particularly Jonas Woodhead & Sons and Shriram Bearings Ltd., on the ground that those cases involved acquisition of technical know-how, enduring rights and long-term business advantages, which were absent in the present case.

 

Important Clarifications by the Court

1. Enduring Benefit Test is Not Conclusive

The Court emphasized that merely because an expenditure may generate benefits in future years does not automatically make it capital expenditure.

2. Software Development Expenses May Be Revenue Expenditure

Where software development constitutes the regular business activity of the assessee and expenditure consists of routine operational costs, such expenditure can be treated as revenue expenditure.

3. Advantage Must Be in Capital Field

Even where some enduring benefit exists, expenditure will not be capital unless the benefit is acquired in the capital field.

4. Guesswork Cannot Justify Disallowance

The Assessing Officer cannot capitalize expenditure merely on assumptions regarding future value or earning potential without proper evidence.

Relevant Sections Involved

  • Section 37(1), Income Tax Act, 1961 – Business Expenditure
  • Section 260A, Income Tax Act, 1961 – Appeal to High Court
  • Section 43(3), Income Tax Act, 1961 (referred in precedents concerning capital assets and plant)

 

Court Order

The Delhi High Court upheld the order of the Income Tax Appellate Tribunal and held that the software development expenditure incurred by the assessee was revenue expenditure.

The Court found that the Assessing Officer had proceeded on mere conjecture and guesswork in treating 25% of the expenditure as capital expenditure.

Accordingly, the appeal filed by the Revenue was dismissed.

Considered technical know-how expenditure resulting in enduring rights as capital expenditure.

Link to download the order -

https://delhihighcourt.nic.in/app/case_number_pdf/2010:DHC:3482-DB/DMA15072010ITA8612010.pdf

Disclaimer

This content is shared strictly for general information and knowledge purposes only. Readers should independently verify the information from reliable sources. It is not intended to provide legal, professional, or advisory guidance. The author and the organisation disclaim all liability arising from the use of this content. The material has been prepared with the assistance of AI tools.