Some tax disputes are footnotes. Others become landmarks. The Oracle Systems Corporation case, decided by the Income Tax Appellate Tribunal (ITAT), Delhi in March 2026, belongs firmly in the second category. Seven assessment years, two decades of corporate history in India and one of the most aggressive transfer pricing positions ever taken by the Indian Revenue and at the end of it all, Oracle walked away with a comprehensive win. For anyone who works in Indian international taxation, this ruling deserves careful reading.
The controversy occurred between the Oracle Systems Corporation (OSC), which was the parent organization in the US, and the Oracle India Private Limited (OIPL), which was the daughter concern in India held entirely by OSC. This controversy emerged during the period when OIPL began using its development centers in Bangalore and Hyderabad after 1993. The controversy raised by the Revenue was based on the following two arguments; first, that the transfer between the two concerns should be deemed as royalty received by OSC and second, that the office of OIPL in India was the PE of OSC as per DTAA.
The Setup: Two Companies, Two Contracts, One Long Fight
Understanding why this case matters requires understanding how Oracle's Indian operations were actually structured. OIPL and OSC operated under two separate agreements. The first, the Software Duplication and Distribution License Agreement (SDDLA), governed OIPL's right to duplicate and sublicense Oracle software within India. Under this arrangement, OIPL paid royalty to OSC at 30% of list price, later revised to 56% and OSC duly paid tax on these receipts as royalty income.
The second agreement, the Software Support Services Agreement (SSSA), was where the trouble began. This contract governed transfers of revenue from OIPL to OSC in connection with global deals situations where multinational clients based outside India purchased Oracle software or services and OIPL facilitated support. The Assessing Officer decided that these transfers, too, should be characterized as royalty and not just at 56%, but at 30% initially, which the CIT(A) then escalated to a remarkable 100% of all revenues, including those from training and consultancy.
The sheer overreach of that position is worth pausing on. OIPL had already declared the entire revenue from global deals as its own taxable income in India. The Revenue was now seeking to tax it again this time in OSC's hands as royalty. That is not a transfer pricing adjustment. That is double taxation engineered through recharacterization and the ITAT did not let it stand.
No Contract, No Royalty: The Tribunal's Core Holding
The legal foundation of the ITAT's ruling on royalty is straight forward but important: income accrues to a non-resident only when there is a legally enforceable right to receive it. Royalty, specifically, can only arise under Section 9(1)(vi) of the Income Tax Act if the right to receive it is created by a contractual arrangement. When the Tribunal examined the SSSA the actual agreement governing global deal revenues it found no such clause. OIPL was not duplicating software for multinational clients outside India. It was providing support services. The contractual right to receive royalty simply did not exist.
There was a regulatory dimension as well. RBI Circular No. 6 dated March 10, 1993, permitted royalty payments only where software was being duplicated or reproduced. Since neither condition was met under the SSSA, any payment styled as royalty would have been impermissible under exchange control law. The Revenue's position was therefore untenable on two independent grounds no contractual right and a regulatory bar on payment.
The Tribunal also drew on the Supreme Court's ruling in Engineering Analysis Centre of Excellence Pvt. Ltd., which had held that a transaction granting only the right to use software without any right to reproduce or sublicense does not constitute royalty under a tax treaty. Applying that reasoning, the ITAT also deleted transfer pricing adjustments on training and consultancy revenues, holding that no use of intellectual property or copyright was involved in those transactions either.
The entire notional royalty addition running into substantial sums across seven years was deleted in full.
Three PE Theories, Three Failures
The PE allegations were where the Revenue's case was perhaps most ambitious and where its evidentiary foundations were thinnest. The Revenue invoked three separate limbs of Article 5 of the India-USA DTAA to argue that OIPL's operations constituted OSC's PE in India.
The Fixed Place PE argument rested on the claim that OIPL's Bangalore and Hyderabad offices were "at the disposal" of OSC a phrase that carries specific legal weight after the Supreme Court's decisions in Formula One World Championship Ltd. and Hyatt International. The disposal test asks whether the foreign enterprise has a right of access to, or control over, the premises in question. The ITAT found no evidence of this. OIPL leased its own offices, owned its own equipment, claimed its own depreciation. There was nothing to suggest that OSC employees could walk into those facilities and occupy space as of right. The Revenue pointed to Oracle's Form 10-K filed with the US Securities and Exchange Commission as evidence of OSC's Indian activities but the Tribunal was unimpressed a consolidated group disclosure does not establish the specific footprint of a particular entity within the group.
The Tribunal also rejected the broader argument that OSC's use of OIPL for outsourced functions created a Fixed Place PE by association. Citing the Supreme Court and Delhi High Court decisions in E-Funds, the ITAT held that even where a foreign enterprise reduces costs by routing operations through an Indian subsidiary, that does not turn the subsidiary's premises into the foreign enterprise's own place of business. The business of OIPL was OIPL's business not OSC's.
On Service PE, the DTAA requires the foreign enterprise to furnish services through employees physically present in India for more than 90 days. The Revenue produced no credible evidence that any OSC employee had spent 90 days or more in India. This is a hard numerical threshold, and the Assessing Officer simply did not meet it.
The Agency PE argument fared no better. Under Article 5(4) of the DTAA, a dependent agent PE requires proof that the agent habitually concludes contracts, maintains stocks or secures orders on the foreign enterprise's behalf. The Revenue argued that OIPL's exclusive relationship with OSC made it a dependent agent. The ITAT disagreed. Exclusivity, on its own, says nothing about whether an entity habitually exercises authority to bind a foreign enterprise. The factual conditions were not demonstrated.
What finished the PE case entirely was the principle drawn from the Supreme Court's ruling in Morgan Stanley. Where a subsidiary's transactions with its foreign parent have been benchmarked and accepted as arm's length under transfer pricing law, no additional profit can be attributed to any alleged PE. OIPL's transactions had been so benchmarked. That finding pulled the rug from under the Revenue's profit attribution exercise before it even began.
The Rate Cap and the Interest Question
Once the PE findings were resolved in Oracle's favour, two further questions needed answering. The first was the rate at which OSC's royalty income whatever remained taxable should be assessed. The Assessing Officer had applied an effective domestic rate of 42.23%, premised on the existence of a PE. With no PE, the correct framework was Article 12(2) of the India-USA DTAA, which caps the tax on royalties paid to a US resident at 15% of the gross amount.
The more interesting issue was whether domestic surcharge and health and education cess could be imposed over and above that 15% cap. The ITAT held that they could not. The treaty rate is a ceiling it is the maximum that India can charge, inclusive of all levies. Layering domestic surcharges and cess on top of a treaty-prescribed rate would effectively override the treaty, which Indian courts have consistently held is impermissible. This ruling aligns with earlier ITAT decisions in JC Decaux S.A., Marubeni Corporation, DIC Asia Pacific and Capgemini SA and it is now the settled position at the tribunal level.
On interest under Section 234B, the ITAT followed the Supreme Court's ruling in Mitsubishi Corporation. For years prior to FY 2012-13, the advance tax liability must be reduced by the amount of TDS that should have been deducted at source even if the payer failed to actually deduct it. The Assessing Officer was directed to recompute accordingly. One year also involved an erroneous refund adjustment that had inflated the demand, which the CIT(A) had overlooked. That issue was sent back for fresh consideration.
Conclusion
What makes this ruling worth returning to is not just the outcome, but the discipline with which the ITAT reached it. At every turn, the Tribunal insisted on evidence over assertion, contractual reality over notional reconstruction and treaty text over administrative convenience. The Revenue had built an elaborate case across seven assessment years and the ITAT dismantled it brick by brick, applying consistent reasoning drawn from the Supreme Court's own precedents.
Three principles emerge from this case that will matter well beyond Oracle's specific facts. First, royalty cannot be imputed to a non-resident in the absence of a contractual right to receive it the Revenue cannot engineer a tax liability by rewriting what the parties actually agreed. Second, a PE cannot be conjured from a subsidiary relationship alone. The disposal test for Fixed Place PE, the 90-day threshold for Service PE and the habitual authority requirement for Agency PE all demand real factual proof, not inference from corporate proximity. Third, treaty-prescribed tax rates mean what they say surcharges and cess cannot be piled on top of a ceiling that the DTAA has already fixed.
For practitioners, this case is a detailed checklist of what proper documentation, arm's-length benchmarking, and clearly drafted intercompany agreements can achieve when tested under sustained Revenue scrutiny. For multinationals with Indian subsidiaries operating on a captive or cost-plus model, it is a reminder that the legal framework, when correctly applied, does protect well-structured arrangements. Oracle spent the better part of two decades establishing that point. The rest of the industry now has the benefit of that effort and a much clearer map of where the boundaries lie.