Facts of the Case

The assessee, Flour Daniel India Pvt. Ltd., was engaged in preparing engineering designs and drawings for projects allotted by group entities.

For carrying out its business activities, the assessee used specialised software packages, including Plant Design Software (PDS), obtained through a licensing arrangement from its foreign group company, Flour Intercontinental Inc., USA.

During the relevant assessment year, the assessee claimed software expenses amounting to approximately Rs. 2.75 crores as revenue expenditure.

The Assessing Officer treated the software expenditure as capital in nature and disallowed the claim. Instead, depreciation at the prescribed rate was allowed.

The Commissioner of Income Tax (Appeals) reversed the assessment order and held that the expenditure was revenue in nature. The Income Tax Appellate Tribunal affirmed the findings of the CIT(A).

The Revenue challenged the Tribunal’s decision before the Delhi High Court. 

Issues Involved

  1. Whether payments made for the use of software under a licence arrangement constitute capital expenditure or revenue expenditure.
  2. Whether the assessee acquired any proprietary rights or enduring benefit in the software.
  3. Whether software licence fees paid on a usage basis are allowable as revenue expenditure under the Income Tax Act.
  4. Whether the software licence resulted in transfer of an asset or merely conferred a limited right to use. 

Petitioner’s Arguments (Revenue)

  • The Revenue contended that software constitutes an intangible asset capable of ownership and depreciation under Section 32.
  • Since software is specifically recognised as an asset for depreciation purposes, expenditure incurred for obtaining software rights should be treated as capital expenditure.
  • The payments made by the assessee resulted in acquisition of an enduring advantage.
  • The mode of payment was not decisive for determining the character of expenditure.
  • The Revenue relied upon several judicial precedents concerning acquisition of technical know-how, designs, drawings and intellectual property rights. 

Respondent’s Arguments (Assessee)

  • The assessee argued that it merely obtained a limited right to use the software.
  • No ownership rights, proprietary rights or intellectual property rights in the software were transferred.
  • The software continued to belong to the foreign parent company.
  • Payments were calculated on an hourly usage basis and depended upon actual utilisation of the software.
  • The arrangement did not provide any enduring benefit or permanent advantage.
  • The assessee only used the software as a tool for carrying on business operations and therefore the expenditure was revenue in nature. 

Court Findings

The Delhi High Court carefully examined the terms of the licensing agreement.

The Court noted that:

  • The software remained the property of the foreign parent company.
  • No transfer of ownership or proprietary rights took place.
  • The assessee merely obtained permission to use the software.
  • Payments were linked to actual usage and were calculated on an hourly basis.
  • The software licence did not confer any enduring advantage of a capital nature.
  • The assessee acquired neither the software itself nor the substance of ownership rights.

The Court observed that although software can, in appropriate circumstances, be treated as a capital asset, every software-related payment does not automatically become capital expenditure.

The decisive test is whether the assessee acquires an enduring benefit or proprietary rights.

The Court referred to and relied upon:

Climate Systems India Ltd. v. Commissioner of Income Tax

The Court reiterated that recurring royalty payments for use of technology, software or know-how without transfer of ownership generally constitute revenue expenditure.

Commissioner of Income Tax v. J.K. Synthetics Ltd.

The Court relied upon the principles laid down for determining whether licence-related payments result in acquisition of capital assets or merely facilitate business operations.

The Court found that the assessee only obtained access to software for business use and did not acquire any capital asset.

Court Order / Findings

The Delhi High Court held that:

  • The software licence fees paid by the assessee were revenue expenditure.
  • No ownership rights or proprietary rights in the software were transferred to the assessee.
  • The assessee merely obtained a right to use the software.
  • The payments were usage-based and dependent upon actual utilisation.
  • No enduring benefit of a capital nature accrued to the assessee.
  • The Tribunal correctly treated the software expenditure as revenue expenditure.

Accordingly, the appeals filed by the Revenue were dismissed. 

Important Clarification

The judgment establishes that software-related expenditure is not automatically capital expenditure merely because software is recognised as an intangible asset under Section 32.

Revenue Expenditure

  • Licence fees linked to actual usage.
  • Payments for limited right to use software.
  • No transfer of ownership rights.
  • No transfer of intellectual property rights.
  • No enduring benefit.

Capital Expenditure

  • Acquisition of ownership rights.
  • Transfer of substantial proprietary rights.
  • Enduring advantage creating a capital asset.
  • Transfer of the substance of ownership.

The Court emphasised that the true nature of rights acquired under the agreement determines the tax treatment. 

Sections Involved

  • Section 37(1) of the Income Tax Act, 1961
  • Section 32 of the Income Tax Act, 1961
  • Section 9(1)(vi) and Explanation 2 to Section 9(1)(vi)
  • Section 43(3) of the Income Tax Act, 1961
  • Article 12(2)(a)(iv) of the India-USA Double Taxation Avoidance Agreement (DTAA)

Link to Download the Order https://delhihighcourt.nic.in/app/case_number_pdf/2009:DHC:9338-DB/AKS30112009ITA11192008_145327.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.