<?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>Communication to taxpayers through eOffice - requirement of document Identification Number (DIN)</title>
    <link>https://www.taxtmi.com/circulars?id=68807</link>
    <description>A new verification utility confirms the electronically generated eOffice Issue number and associated metadata; for communications dispatched via eOffice public option the verifiable eOffice Issue number shall be deemed the Document Identification Number, whereas the DIN utility must still be used for communications not dispatched through the eOffice public option. Officers must accurately complete metadata fields when creating eOffice drafts.</description>
    <language>en-us</language>
    <pubDate>Tue, 23 Sep 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 24 Sep 2025 10:57:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=854168" rel="self" type="application/rss+xml"/>
    <item>
      <title>Communication to taxpayers through eOffice - requirement of document Identification Number (DIN)</title>
      <link>https://www.taxtmi.com/circulars?id=68807</link>
      <description>A new verification utility confirms the electronically generated eOffice Issue number and associated metadata; for communications dispatched via eOffice public option the verifiable eOffice Issue number shall be deemed the Document Identification Number, whereas the DIN utility must still be used for communications not dispatched through the eOffice public option. Officers must accurately complete metadata fields when creating eOffice drafts.</description>
      <category>Circulars</category>
      <law>Customs</law>
      <pubDate>Tue, 23 Sep 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/circulars?id=68807</guid>
    </item>
  </channel>
</rss>