<?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>Income Tax Business Application (ITBA) - BPU roles to access 360° view screen - Procedure of Role Assignment</title>
    <link>https://www.taxtmi.com/circulars?id=68262</link>
    <description>Procedure requires RCC Admin to assign BPU roles in ITBA only after receiving the officer&#039;s posting order from the competent authority and confirmation that the officer has taken charge (taking over report), and to revoke the previous incumbent&#039;s BPU role on new postings; assigned BPU users may access the 360 view screen showing PAN details, ITR history, processing, tax payment, TDS, ITS and e-filed non ITR forms.</description>
    <language>en-us</language>
    <pubDate>Thu, 12 Apr 2018 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 22 Mar 2025 12:35:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=808048" rel="self" type="application/rss+xml"/>
    <item>
      <title>Income Tax Business Application (ITBA) - BPU roles to access 360° view screen - Procedure of Role Assignment</title>
      <link>https://www.taxtmi.com/circulars?id=68262</link>
      <description>Procedure requires RCC Admin to assign BPU roles in ITBA only after receiving the officer&#039;s posting order from the competent authority and confirmation that the officer has taken charge (taking over report), and to revoke the previous incumbent&#039;s BPU role on new postings; assigned BPU users may access the 360 view screen showing PAN details, ITR history, processing, tax payment, TDS, ITS and e-filed non ITR forms.</description>
      <category>Circulars</category>
      <law>Income Tax</law>
      <pubDate>Thu, 12 Apr 2018 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/circulars?id=68262</guid>
    </item>
  </channel>
</rss>