<?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>FAKE ITC REVERSE</title>
    <link>https://www.taxtmi.com/forum/issue?id=114204</link>
    <description>Mere appearance of invoices in auto populated GSTR 2A does not constitute availment or utilization of ITC by the recipient; liability for incorrect B2B invoice entries rests with the supplier who uploaded them in GSTR 1. If the recipient has not debited the electronic credit ledger or used the credit, they are not responsible for the fake ITC. Practically, the recipient should ask the supplier to amend their GSTR 1 so the correct person receives eligible ITC, and may notify the jurisdictional officer with GSTR 2A proof.</description>
    <language>en-us</language>
    <pubDate>Thu, 04 Oct 2018 08:30:43 +0530</pubDate>
    <lastBuildDate>Thu, 23 Jan 2025 15:55:17 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=536946" rel="self" type="application/rss+xml"/>
    <item>
      <title>FAKE ITC REVERSE</title>
      <link>https://www.taxtmi.com/forum/issue?id=114204</link>
      <description>Mere appearance of invoices in auto populated GSTR 2A does not constitute availment or utilization of ITC by the recipient; liability for incorrect B2B invoice entries rests with the supplier who uploaded them in GSTR 1. If the recipient has not debited the electronic credit ledger or used the credit, they are not responsible for the fake ITC. Practically, the recipient should ask the supplier to amend their GSTR 1 so the correct person receives eligible ITC, and may notify the jurisdictional officer with GSTR 2A proof.</description>
      <category>Discussion-Forum</category>
      <law>GST</law>
      <pubDate>Thu, 04 Oct 2018 08:30:43 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/forum/issue?id=114204</guid>
    </item>
  </channel>
</rss>