<?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>DRP&#039;s TNMM method for software consultancy transfer pricing reversed; TPO directed to use CUP method instead.</title>
    <link>https://www.taxtmi.com/highlights?id=68609</link>
    <description>TP Adjustment - International transactions with its AEs for providing software consultancy services - Selection of MAM - DRP without appreciating the above facts, has simply upheld TNMM as most appropriate method and upheld the TP adjustment as suggested by the TPO. Hence, we reverse the findings of the DRP and direct the TPO to consider CUP as most appropriate method to bench mark international transactions with its AEs. - AT</description>
    <language>en-us</language>
    <pubDate>Mon, 06 Mar 2023 11:18:33 +0530</pubDate>
    <lastBuildDate>Mon, 06 Mar 2023 11:18:33 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=706904" rel="self" type="application/rss+xml"/>
    <item>
      <title>DRP&#039;s TNMM method for software consultancy transfer pricing reversed; TPO directed to use CUP method instead.</title>
      <link>https://www.taxtmi.com/highlights?id=68609</link>
      <description>TP Adjustment - International transactions with its AEs for providing software consultancy services - Selection of MAM - DRP without appreciating the above facts, has simply upheld TNMM as most appropriate method and upheld the TP adjustment as suggested by the TPO. Hence, we reverse the findings of the DRP and direct the TPO to consider CUP as most appropriate method to bench mark international transactions with its AEs. - AT</description>
      <category>Highlights</category>
      <law>Income Tax</law>
      <pubDate>Mon, 06 Mar 2023 11:18:33 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/highlights?id=68609</guid>
    </item>
  </channel>
</rss>