ITA No. 3853/Mum/2025 | ITAT Mumbai, 'J' Bench | AY 2016-17 | Pronounced: 12 January 2026
First, Some Context on How These Cases Usually Go
If you have spent any time tracking transfer pricing litigation in India, you already know the pattern. The TPO raises an adjustment. The assessee objects. DRP cuts it down a bit. ITAT cuts it down further, or restores it to the TPO with directions. The TPO ignores those directions. The assessee goes back to ITAT. And the whole thing runs for years.
The Red Hat India case is not unusual in that regard. What makes it worth writing about is the ending — and more specifically, the reason the entire Rs. 4.24 crore adjustment was deleted.
It was not a dramatic legal argument. There was no novel interpretation of statute. It came down to something the Tribunal had already told the TPO to do in 2022. The TPO simply did not do it properly. And when the matter came back to ITAT in 2026, the bench deleted the adjustment outright.
The lesson is not subtle.
What Red Hat India Actually Does
Before getting into the numbers, it helps to understand the business.
Red Hat India is the Indian subsidiary of Red Hat Inc., USA — now owned by IBM. The Indian entity provides open-source software solutions and related services. What is important here, and what the ITAT itself flagged, is that Red Hat does not sell software in the conventional sense. Customers do not pay a one-time licence fee. They pay for subscriptions — ongoing access to updates, support, patches, and enterprise solutions built around products like Red Hat Enterprise Linux.
Why does this matter for transfer pricing? Because when you are benchmarking a company that pays royalty to its parent for a subscription-based product, you cannot apply a generic software-company comparable set without understanding how this model actually works. The ITAT noted this specifically. The business model is not just background — it is directly relevant to how the intercompany transactions should be priced and tested.
The Transactions That Got Scrutinised
For AY 2016-17, Red Hat India had five categories of international transactions with its AEs — primarily Red Hat Inc., USA and Red Hat Limited, Ireland. All were benchmarked using TNMM.
|
Transaction |
Associated Enterprise |
Amount (INR) |
Method |
|
Royalty & service fee — Subscription segment |
Red Hat Inc., USA |
94,99,29,936 |
TNMM |
|
Royalty & service fee — Services segment |
Red Hat Inc., USA |
13,43,704 |
TNMM |
|
Software Development Services |
Red Hat Inc., USA |
55,82,40,145 |
TNMM |
|
IT Enabled Services |
Red Hat Inc., USA |
83,76,55,778 |
TNMM |
|
IT Enabled Services |
Red Hat Ltd., Ireland |
20,94,13,945 |
TNMM |
The Long Road to Rs. 4.24 Crore
The TPO's original order in October 2019 proposed a combined adjustment of Rs. 32.51 crore across all four issue heads — royalty fees (subscription segment), royalty fees (services segment), software development services, and IT enabled services. A rectification order the following month trimmed this to Rs. 30.31 crore, but the dispute was far from over.
The assessee went to DRP. DRP gave its directions. A final assessment order was passed in March 2021. Red Hat India challenged that before ITAT.
In February 2022, the Tribunal partly allowed the appeal. On working capital adjustment specifically, it held clearly that the assessee was entitled to it, and directed the TPO to go back, check the computations submitted in the transfer pricing study, and grant the adjustment in accordance with law.
That is about as clear a direction as a Tribunal can give.
In remand, the TPO came back with a revised adjustment of Rs. 6.09 crore. DRP then restricted the surviving addition to only the subscription segment royalty and service fee — Rs. 4.23 crore. That was the figure in the Order Giving Effect dated 31 December 2024. Red Hat India came back to ITAT a second time.
What the TPO Did (and Did Not Do) in Remand
This is where it gets frustrating, if you are on the assessee's side. The Tribunal had said: verify the working capital adjustment computation, grant it if correct.
The TPO's response in remand was essentially to raise the same objections again — daily working capital balances were not available, cost of capital differed between the assessee and comparables, and so on.
The ITAT's reaction in the January 2026 order is blunt. The bench noted that these were not new objections. They had been considered and rejected before, by multiple judicial forums. The lower authority was not exercising independent judgment — it was simply refusing to follow a direction.
There is a broader point here that practitioners need to keep in mind. When a Tribunal restores a matter to the TPO with specific directions, those directions are binding. The TPO cannot treat them as suggestions. If the information needed to compute an adjustment is not available in the public domain — as is the case with daily working capital balances of comparable companies — that cannot be used as a reason to deny the adjustment entirely. The assessee cannot produce data that does not exist.
Working Capital Adjustment — What It Is and Why It Keeps Coming Up
For anyone not working in transfer pricing day-to-day: a working capital adjustment is made to correct for differences in how the tested party and its comparables manage their working capital.
If a company carries higher trade receivables than its comparables — meaning it is effectively giving longer credit to customers — its net margin will be lower than a comparable that collects faster. This difference has nothing to do with whether the intercompany pricing is at arm's length. It is just a function of different business practices. To compare margins without adjusting for this leads to a distorted result.
Rule 10B of the Income Tax Rules explicitly allows for adjustments to eliminate differences that materially affect prices or margins. Working capital is one of the most commonly accepted bases for such adjustments. The Bangalore Bench's ruling in Huawei Technologies India (P.) Ltd. [(2019) 101 taxmann.com 313] laid out the methodology in detail. The Mumbai Tribunal had already followed it in Red Hat India's own cases for AY 2016-17 and AY 2017-18 before this order. By the time this case came back for a second round, there was no real jurisprudential question left. It was a matter of arithmetic.
The Margin Numbers That Closed the Case
Once the Tribunal directed that working capital adjustment be applied using the methodology the assessee had already submitted, the comparison looked like this:
|
Company |
WC-Adjusted NCP Margin |
|
Sonata Information Technology Limited |
2.20% |
|
Dynacons Technologies Limited |
-1.53% |
|
Virtual Galaxy Inftech Private Limited |
4.21% |
|
Arm's length arithmetic mean |
1.626% |
|
Red Hat India's margin |
1.40% |
|
Tolerance band under Section 92C(2) |
±3% → Range: -1.374% to 4.626% |
Red Hat India's margin of 1.40% sits inside the arm's length range. The Rs. 4.23 crore adjustment had no leg to stand on. The Tribunal deleted it in full.
The Other Grounds — Mostly Left Open
With the transfer pricing adjustment gone, several other grounds became academic. The validity challenge under CBDT Circular No. 19 of 2019 (on document identification numbers), the limitation ground under Section 153 read with Section 144C(1), the comparable selection challenge, and the additional ground about absence of digital signature — all left open, not decided.
The grounds on credits — TDS credit of Rs. 4.91 crore, MAT credit under Section 115JAA of Rs. 1.70 lakh, foreign tax credit under Section 90 of Rs. 3.61 lakh, self-assessment tax of Rs. 10 crore, and interest under Section 244A — were directed to the AO for verification and allowed for statistical purposes.
What This Case Actually Tells You
- The TPO cannot re-litigate what the Tribunal has settled. When an appellate forum gives a direction, the lower authority's job in remand is to implement it — not to find new reasons to avoid it. Doing otherwise wastes years and ends in the same place.
- Working capital adjustment claims need to be documented properly from the start. Red Hat had submitted its computation in the original transfer pricing study. When the Tribunal directed verification, that computation already existed. Assessees who do not build this into their TP documentation upfront lose time arguing the principle before they even get to the numbers.
- Business model context belongs in your TP documentation. The Tribunal specifically noted that Red Hat's subscription-based open-source model cannot be viewed in isolation. If your entity has a distinctive operating structure, make sure your documentation explains why that matters for benchmarking, not just what method you used.
- Section 92C(2) tolerance is real protection when you are close to the range. Red Hat's margin came in at 1.40% against a mean of 1.626% — well within the ±3% band. The working capital adjustment was not large, but it was enough. Knowing where you stand relative to the tolerance band, and what adjustments can bring you inside it, is practical knowledge that saves crores in litigation.
Final Thought
This case went on from the original TPO order in October 2019 to the final ITAT order in January 2026. Over six years, across two rounds of assessment, DRP directions, and ITAT hearings — the final outcome turned on a working capital adjustment that the Tribunal had already approved in 2022.
That is a lot of time and cost for something that could have been resolved much earlier. For companies with similar profiles — Indian subsidiaries paying royalty or service fees to foreign parents, using TNMM, with working capital structures that differ from their comparable set — the Red Hat case is a clear signal. Build the working capital adjustment in. Document it thoroughly. And if a Tribunal upholds it, make sure the remand proceedings actually implement it.