<?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>PROVIDER OF GTA SERVICE AND RESELLER OF HARDWARE GOODS UNDER SAME GSTN</title>
    <link>https://www.taxtmi.com/forum/issue?id=119210</link>
    <description>A single GSTIN may cover both GTA services subject to Reverse Charge Mechanism and resale of hardware goods subject to Forward Charge Mechanism; RCM liability depends on the nature of the supply, not the GSTIN. The registrant should amend registration core fields (for example additional place or trade name) on the common portal where required so the GSTIN reflects both business activities, and maintain distinct tax treatment and records for each type of supply.</description>
    <language>en-us</language>
    <pubDate>Tue, 16 Jul 2024 19:51:32 +0530</pubDate>
    <lastBuildDate>Fri, 24 Jan 2025 10:40:20 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=760324" rel="self" type="application/rss+xml"/>
    <item>
      <title>PROVIDER OF GTA SERVICE AND RESELLER OF HARDWARE GOODS UNDER SAME GSTN</title>
      <link>https://www.taxtmi.com/forum/issue?id=119210</link>
      <description>A single GSTIN may cover both GTA services subject to Reverse Charge Mechanism and resale of hardware goods subject to Forward Charge Mechanism; RCM liability depends on the nature of the supply, not the GSTIN. The registrant should amend registration core fields (for example additional place or trade name) on the common portal where required so the GSTIN reflects both business activities, and maintain distinct tax treatment and records for each type of supply.</description>
      <category>Discussion-Forum</category>
      <law>GST</law>
      <pubDate>Tue, 16 Jul 2024 19:51:32 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/forum/issue?id=119210</guid>
    </item>
  </channel>
</rss>