<?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>2012 (4) TMI 746 - Supreme Court</title>
    <link>https://www.taxtmi.com/caselaws?id=275166</link>
    <description>Taking cognizance is a judicial application of mind to the offence, while issuing summons is a later step requiring the Magistrate to be satisfied that there is sufficient ground for proceeding. The Magistrate is not required to record detailed reasons at the summons stage, because the Code does not mandate a speaking order for issuance of process. A challenge to a summoning order may be raised through inherent jurisdiction in an appropriate case, and maintainability under that route was recognised.</description>
    <language>en-us</language>
    <pubDate>Wed, 04 Apr 2012 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 24 Jul 2023 10:18:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=535168" rel="self" type="application/rss+xml"/>
    <item>
      <title>2012 (4) TMI 746 - Supreme Court</title>
      <link>https://www.taxtmi.com/caselaws?id=275166</link>
      <description>Taking cognizance is a judicial application of mind to the offence, while issuing summons is a later step requiring the Magistrate to be satisfied that there is sufficient ground for proceeding. The Magistrate is not required to record detailed reasons at the summons stage, because the Code does not mandate a speaking order for issuance of process. A challenge to a summoning order may be raised through inherent jurisdiction in an appropriate case, and maintainability under that route was recognised.</description>
      <category>Case-Laws</category>
      <law>Indian Laws</law>
      <pubDate>Wed, 04 Apr 2012 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=275166</guid>
    </item>
  </channel>
</rss>