<?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>Erroneous filing of RCM sales under Nil.</title>
    <link>https://www.taxtmi.com/forum/issue?id=120491</link>
    <description>The supplier does not automatically become liable when RCM supplies were filed as nil if the supplier did not charge tax; liability under the Reverse Charge Mechanism remains with the recipient. Invoices stating recipient liability, LR copies, and customer declarations confirming payment under RCM constitute the primary documentary proof. Where an officer rejects the explanation, escalate to higher authorities and produce the assembled records to support the supplier&#039;s position.</description>
    <language>en-us</language>
    <pubDate>Wed, 24 Sep 2025 11:55:21 +0530</pubDate>
    <lastBuildDate>Sun, 28 Sep 2025 16:50:35 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=854186" rel="self" type="application/rss+xml"/>
    <item>
      <title>Erroneous filing of RCM sales under Nil.</title>
      <link>https://www.taxtmi.com/forum/issue?id=120491</link>
      <description>The supplier does not automatically become liable when RCM supplies were filed as nil if the supplier did not charge tax; liability under the Reverse Charge Mechanism remains with the recipient. Invoices stating recipient liability, LR copies, and customer declarations confirming payment under RCM constitute the primary documentary proof. Where an officer rejects the explanation, escalate to higher authorities and produce the assembled records to support the supplier&#039;s position.</description>
      <category>Discussion-Forum</category>
      <law>GST</law>
      <pubDate>Wed, 24 Sep 2025 11:55:21 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/forum/issue?id=120491</guid>
    </item>
  </channel>
</rss>