<?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>CE - Regarding classification of STD/PCO Monitor - Reg.</title>
    <link>https://www.taxtmi.com/circulars?id=615</link>
    <description>STD/PCO call monitors are microprocessor-based devices that total exchange pulses and compute billing by applying programmed time- and distance-based rates; their primary function is that of a calculating machine rather than a simple counter. Accordingly, the Board directs that STD/PCO monitors be classifiable under Heading No. 84.70 as calculating machines to ensure uniform tariff treatment and levy of duty, and instructs Commissioners to circulate the order for implementation.</description>
    <language>en-us</language>
    <pubDate>Mon, 05 Apr 1999 00:00:00 +0530</pubDate>
    <lastBuildDate>Tue, 15 Sep 2009 15:34:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=255256" rel="self" type="application/rss+xml"/>
    <item>
      <title>CE - Regarding classification of STD/PCO Monitor - Reg.</title>
      <link>https://www.taxtmi.com/circulars?id=615</link>
      <description>STD/PCO call monitors are microprocessor-based devices that total exchange pulses and compute billing by applying programmed time- and distance-based rates; their primary function is that of a calculating machine rather than a simple counter. Accordingly, the Board directs that STD/PCO monitors be classifiable under Heading No. 84.70 as calculating machines to ensure uniform tariff treatment and levy of duty, and instructs Commissioners to circulate the order for implementation.</description>
      <category>Circulars</category>
      <law>Central Excise</law>
      <pubDate>Mon, 05 Apr 1999 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/circulars?id=615</guid>
    </item>
  </channel>
</rss>