<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.taxtmi.com/rss_sitemap/rss_feed_blog.xsl?v=1750492856"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>2017 (5) TMI 70 - ITAT HYDERABAD</title>
    <link>https://www.taxtmi.com/caselaws?id=342332</link>
    <description>The Tribunal reiterated that CUP was the appropriate benchmarking method for the assessee&#039;s medical transcription services, relying on its earlier year view and finding no material factual distinction to justify reopening that issue. It declined the Revenue&#039;s attempt to re-argue the same factual appreciation, and directed a fresh ALP computation after giving the assessee due opportunity. TNMM was retained only for the separate software development/ITES segment, in line with the earlier-year reasoning.</description>
    <language>en-us</language>
    <pubDate>Fri, 28 Apr 2017 00:00:00 +0530</pubDate>
    <lastBuildDate>Tue, 02 May 2017 09:08:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=467299" rel="self" type="application/rss+xml"/>
    <item>
      <title>2017 (5) TMI 70 - ITAT HYDERABAD</title>
      <link>https://www.taxtmi.com/caselaws?id=342332</link>
      <description>The Tribunal reiterated that CUP was the appropriate benchmarking method for the assessee&#039;s medical transcription services, relying on its earlier year view and finding no material factual distinction to justify reopening that issue. It declined the Revenue&#039;s attempt to re-argue the same factual appreciation, and directed a fresh ALP computation after giving the assessee due opportunity. TNMM was retained only for the separate software development/ITES segment, in line with the earlier-year reasoning.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Fri, 28 Apr 2017 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=342332</guid>
    </item>
  </channel>
</rss>