Court rules software expenditure as revenue, allows set-off of unit losses against profits.

The court ruled in favor of the assessee, allowing the software expenditure to be treated as revenue rather than capital expenditure. Additionally, the court held that the loss from the non-STP unit should be set off against profits of the STP unit after excluding profits under section 10A, contrary to the approach taken by the assessing officer.

---

---

1. ISSUES PRESENTED AND CONSIDERED

1. Whether expenditure on acquisition of application software and related payments (including one-year license, renewals, upgrades and AMC-linked packages) is capital expenditure resulting in acquisition of a capital asset (allowable only by depreciation) or revenue expenditure deductible in the year of payment.

2. Whether loss of a non-STP (non-10A) unit can be set off against profits of an STP (10A) unit prior to computing deduction under section 10A (i.e., whether exempted 10A income may be included in computation for set-off under section 72 or related provisions).

2. ISSUE-WISE DETAILED ANALYSIS

Issue 1 - Characterisation of software expenditure: revenue v. capital

Legal framework: The distinction between capital and revenue expenditure is governed by tests such as the ownership test and the functional/operational test: whether payment results in acquisition of a capital asset or merely enhances efficiency/productivity of existing operations; whether the expenditure yields an enduring benefit to the business so as to be capitalised and depreciated, or is consumed in the revenue account. The relevance of factors such as duration of license, requirement of annual maintenance contracts (AMC), need for frequent upgrading, and whether software works standalone or only as part of computer systems is considered in applying these tests.

Precedent treatment: Authorities considered include decisions that apply ownership and functional tests to software expenditure and recognise technological realities (e.g., decisions treating application software as revenue where it merely enhances efficiency and requires ongoing upgrades/AMCs; contrasting authorities treating certain software acquisitions as capital where an enduring standalone asset is acquired). The Tribunal explicitly followed the reasoning of a High Court decision holding that modern application software, which must be fitted to computer systems and requires continual updates/AMCs, may produce enduring operational benefit yet not constitute acquisition of a capital asset.

Interpretation and reasoning: The Court examined the nature of the software in question - application/design software used as tools for product design, dependent on AMCs for continued utility, frequently upgraded, and becoming outdated without renewal. Applying the ownership and functional tests and taking into account modern business realities, the Court reasoned that although such software enhances efficiency and enables smooth, profitable operations, it does not function as a stand-alone capital asset; the benefit is operational and contingent on ongoing expenditure (AMC/upgrades). The Court emphasised that the concept of "enduring benefit" must respond to changing technological and economic realities, and that payment for application software that merely increases productivity is revenue in nature.

Ratio vs. Obiter: Ratio - Where application software requires regular renewal/AMC and is inherently linked to continuing upgrades and integration into computer systems (not operating as a standalone capital asset), expenditure on acquisition and related recurring payments is revenue expenditure deductible in the year of payment rather than capital expenditure subject to depreciation. Obiter - Comparative citations noted but the decisive reliance was on the principle regarding contemporary software packages and their operational (non-capital) character.

Conclusion on Issue 1: The software expenditure under challenge is revenue in nature and allowable as revenue expenditure; amounts treated as capital by the lower authority were to be disallowed as capital and treated as revenue deduction.

Issue 2 - Set-off of non-10A loss against 10A (STP) profits before computation of section 10A deduction

Legal framework: Section 10A (or comparable statutory provision) grants exemption/deduction for profits of eligible units (e.g., STP/10A units). The income of a 10A unit is to be excluded at source before arriving at gross total income. Set-off provisions (e.g., section 72) permit business loss of one business to be set off against profits of any other business carried on by the assessee, but only against income that is included in the assessable income.

Precedent treatment: The Court relied on a jurisdictional High Court decision which held that since income of the 10A unit is excluded at source, it is not includible in the assessee's income for the purpose of set-off; consequently the loss of a non-10A unit cannot be set off against profits of a 10A unit. The assessing authority's approach of adding exempted income back and permitting set-off was held to be contrary to the statutory scheme.

Interpretation and reasoning: The Court reasoned that statutory scheme requires exclusion of 10A income at source; therefore such profits are not available as an aggregate head of income against which non-10A business loss can be adjusted under section 72. Further, the sequence for setting off unabsorbed business loss and unabsorbed depreciation (section 72(2) and section 32(2)) presupposes computation of assessable profits; if 10A profits are excluded outright, they do not constitute assessable profits for set-off purposes. The Court found the assessing authority's reduction of loss by including exempted income inconsistent with these provisions.

Ratio vs. Obiter: Ratio - Loss of a non-10A unit cannot be set off against profits of a 10A unit because 10A income is excluded at source and not includible for set-off under section 72; thus the assessing authority's contrary approach is incorrect. Obiter - Application of the statutory sequence for absorption of unabsorbed loss and depreciation is reiterated as supportive statutory context.

Conclusion on Issue 2: The set-off of non-10A loss against 10A profits before computation of the section 10A deduction is not permissible; the assessee is entitled to exclusion of 10A income without reduction by set-off of non-10A losses.

Inter-relation and final disposition

Cross-reference: Issue 1 and Issue 2 are independent; the conclusion on software expenditure turns on classification tests adapted to contemporary software practices, while the conclusion on set-off follows the statutory exclusionary scheme for 10A income and controlling precedent. Both grounds raised by the assessee were allowed by the Court: software expenditure treated as revenue; set-off of non-10A loss against 10A profits disallowed.

---