Tribunal confirms software payments as royalty, assessee liable for tax deduction failure

The Tribunal upheld the orders passed by the CIT(A) and AO, dismissing all appeals filed by the assessee and the revenue. The classification of software payments as royalty under section 9(1)(vi) was confirmed, holding the assessee liable under sections 201(1) and 201(1A) for failure to deduct tax at source. The Tribunal emphasized the importance of following binding precedents and applying correct legal principles, affirming the legality of the authorities' decisions.

---

---

Issues Involved:
1. Validity of the order passed by the CIT(A).
2. Jurisdiction and validity of notice, proceedings, and order.
3. Liability under sections 201(1) and 201(1A) of the Income Tax Act.
4. Declaration of the assessee as in default under section 201(1).
5. Jurisdiction, legality, and limitation of orders passed under sections 201(1) and 201(1A).
6. Legality of passing a single order for multiple assessment years.
7. Violation of judicial discipline by disregarding previous judgments.
8. Analysis of various explanations and clauses under section 9(1)(vi) of the Act and provisions of Double Taxation Avoidance Agreements (DTAA).
9. Confirmation of liability against the appellant contrary to the provisions of the IT Act and DTAA.
10. Classification of payments for software licenses as royalty payments.
11. Application of Explanation 4 to section 9(1)(vi) and retrospective default.
12. Retrospective default in tax deduction at source based on retrospective amendment.

Detailed Analysis:

1. Validity of the Order Passed by the CIT(A):
The Tribunal noted that the CIT(A) had passed a common order for multiple assessment years, which was challenged by the assessee. The Tribunal held that there was no prohibition in law for passing a common order for common questions of law. The grounds of appeal raised by the assessee were similar across all assessment years, and thus, a common order was deemed appropriate.

2. Jurisdiction and Validity of Notice, Proceedings, and Order:
The assessee contended that the notices and proceedings were without jurisdiction and invalid. The Tribunal, however, upheld the jurisdiction of the authorities, stating that the proceedings were initiated correctly under the provisions of the Income Tax Act.

3. Liability Under Sections 201(1) and 201(1A) of the Income Tax Act:
The assessee denied liabilities under sections 201(1) and 201(1A). The Tribunal held that the payments made by the assessee to foreign entities for software purchases were in the nature of royalty under section 9(1)(vi) and thus subject to tax deduction at source. The failure to deduct tax at source made the assessee liable under sections 201(1) and 201(1A).

4. Declaration of the Assessee as in Default Under Section 201(1):
The Tribunal confirmed the CIT(A)'s decision declaring the assessee as in default under section 201(1) due to non-deduction of tax at source on payments for software licenses, which were classified as royalty.

5. Jurisdiction, Legality, and Limitation of Orders Passed Under Sections 201(1) and 201(1A):
The assessee argued that the orders were without jurisdiction, not as per law, and barred by limitation. The Tribunal held that the orders were within the jurisdiction and not barred by limitation, referencing the decision in the case of Google where a six-year limitation period was applied for non-resident payees.

6. Legality of Passing a Single Order for Multiple Assessment Years:
The Tribunal rejected the assessee's contention that a single order for multiple assessment years was unsustainable. It was held that there was no legal prohibition against passing a common order for multiple years when the issues involved were common.

7. Violation of Judicial Discipline by Disregarding Previous Judgments:
The assessee claimed that the CIT(A) and AO violated judicial discipline by disregarding previous judgments in the assessee's own case. The Tribunal acknowledged the binding nature of previous decisions but emphasized the need to follow the correct legal principles, referencing the jurisdictional High Court's decisions in similar cases.

8. Analysis of Various Explanations and Clauses Under Section 9(1)(vi) of the Act and Provisions of DTAA:
The Tribunal found that the CIT(A) had conducted a detailed analysis of the relevant explanations, clauses under section 9(1)(vi), and DTAA provisions. However, it was necessary to apply the correct legal principles as established by higher judicial authorities.

9. Confirmation of Liability Against the Appellant Contrary to the Provisions of the IT Act and DTAA:
The Tribunal upheld the CIT(A)'s decision confirming the liability against the appellant, stating that the payments for software licenses were correctly classified as royalty under both the Income Tax Act and relevant DTAAs.

10. Classification of Payments for Software Licenses as Royalty Payments:
The Tribunal confirmed that payments made by the assessee for software licenses were royalty payments under section 9(1)(vi) and relevant DTAAs, thus subject to tax deduction at source.

11. Application of Explanation 4 to Section 9(1)(vi) and Retrospective Default:
The Tribunal held that Explanation 4 to section 9(1)(vi), inserted by the Finance Act, 2012 with retrospective effect from 1-6-1976, was applicable. The assessee's argument against retrospective default was rejected, and the Tribunal emphasized the binding nature of legislative amendments.

12. Retrospective Default in Tax Deduction at Source Based on Retrospective Amendment:
The Tribunal dismissed the assessee's contention that there could not be a retrospective default in tax deduction at source based on retrospective amendments. The orders passed by the authorities were upheld as being in accordance with the law.

Separate Judgments:
The Tribunal delivered a single judgment for all issues raised, without separate judgments by individual judges.

Conclusion:
All appeals filed by the assessee and the revenue were dismissed, and the orders passed by the CIT(A) and AO were upheld. The Tribunal emphasized the need to follow binding precedents and correctly apply legal principles, confirming the classification of software payments as royalty and the assessee's liability under sections 201(1) and 201(1A).

---