<?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>Invoice issued from inactive gst, but return filed from active gst no.</title>
    <link>https://www.taxtmi.com/forum/issue?id=116766</link>
    <description>The operative remedy for a GST registration identifier mismatch between issued invoices and filed returns is administrative correction: request the supplier to revise invoices and update their ERP to reflect the active GST number, and if portal-level amendments are required, approach the jurisdictional GST Range Officer to coordinate corrections through the GSTN/Common Portal, retaining documentary evidence of revised invoices and communications for reconciliation.</description>
    <language>en-us</language>
    <pubDate>Sat, 03 Oct 2020 16:02:32 +0530</pubDate>
    <lastBuildDate>Thu, 23 Jan 2025 15:54:39 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=623970" rel="self" type="application/rss+xml"/>
    <item>
      <title>Invoice issued from inactive gst, but return filed from active gst no.</title>
      <link>https://www.taxtmi.com/forum/issue?id=116766</link>
      <description>The operative remedy for a GST registration identifier mismatch between issued invoices and filed returns is administrative correction: request the supplier to revise invoices and update their ERP to reflect the active GST number, and if portal-level amendments are required, approach the jurisdictional GST Range Officer to coordinate corrections through the GSTN/Common Portal, retaining documentary evidence of revised invoices and communications for reconciliation.</description>
      <category>Discussion-Forum</category>
      <law>GST</law>
      <pubDate>Sat, 03 Oct 2020 16:02:32 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/forum/issue?id=116766</guid>
    </item>
  </channel>
</rss>