<?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>2009 (2) TMI 722 - CESTAT NEW DELHI</title>
    <link>https://www.taxtmi.com/caselaws?id=128954</link>
    <description>The Tribunal analyzed issues including jurisdictional authority, service classification, registration status, pre-deposit requirements, and potential coercive actions. It emphasized verifying centralized registration, examining service agreements, and maintaining status quo until clarification on registration status. The Tribunal cautioned against coercive action without informing the Bench. The judgment aimed for a comprehensive review to address legal infirmities and ensure fairness in the proceedings.</description>
    <language>en-us</language>
    <pubDate>Thu, 26 Feb 2009 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 15 Apr 2013 16:10:20 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=165823" rel="self" type="application/rss+xml"/>
    <item>
      <title>2009 (2) TMI 722 - CESTAT NEW DELHI</title>
      <link>https://www.taxtmi.com/caselaws?id=128954</link>
      <description>The Tribunal analyzed issues including jurisdictional authority, service classification, registration status, pre-deposit requirements, and potential coercive actions. It emphasized verifying centralized registration, examining service agreements, and maintaining status quo until clarification on registration status. The Tribunal cautioned against coercive action without informing the Bench. The judgment aimed for a comprehensive review to address legal infirmities and ensure fairness in the proceedings.</description>
      <category>Case-Laws</category>
      <law>Service Tax</law>
      <pubDate>Thu, 26 Feb 2009 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=128954</guid>
    </item>
  </channel>
</rss>