<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What is the XBRL Cloud Report?</title>
	<atom:link href="http://blog.rivetsoftware.com/2010/03/03/xbrl-cloud-report/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.rivetsoftware.com/2010/03/03/xbrl-cloud-report/</link>
	<description>Comply. Control. Communicate.</description>
	<lastBuildDate>Fri, 03 Feb 2012 09:37:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Charlie Hymer</title>
		<link>http://blog.rivetsoftware.com/2010/03/03/xbrl-cloud-report/comment-page-1/#comment-8529</link>
		<dc:creator>Charlie Hymer</dc:creator>
		<pubDate>Fri, 04 Feb 2011 21:37:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rivetsoftware.com/?p=1253#comment-8529</guid>
		<description>Dear Preparer,  &lt;br&gt;&lt;br&gt;The Cloud Report looks at all rules as well as best practices even though at this time following best practices is not cause for the filing to be rejected.  With the 2 year furnishing rule at an end for the Wave 1 filers come June, these best practices will need to be scrutinized in more detail.  If the SEC required these best practices, these filings would not have been accepted.  &lt;br&gt;&lt;br&gt;Your XBRL provider should have a validation tool that looks at SEC requirements as they pertain to XBRL 2.1 and EDGAR Filing Manual as well as items that will not cause a filing to be rejected, but would improve the quality of the filing.  If you are outsourcing with a third party, they should be evaluating this for you and implementing the best practices, if possible.  If you are doing the work yourself, it is important, but not required, that you address these best practices.  &lt;br&gt;&lt;br&gt;Therefore, I understand why companies may evaluate vendors based on the XBRL Cloud.  Here at Rivet, we prefer to think of it as a collaboration tool.  We hold our clients’ filings in the highest regard and as you can see, through this collaboration, our error rate on the XBRL Cloud has dropped significantly.  If companies want to use the XBRL Cloud as an evaluation tool, it would be best to look at the error rate over time for all filings.  This would somewhat alleviate the spike for self filers not wanting to clear best practice errors.  It will be interesting to see what happens with the Wave 1 XBRL Cloud errors come June.  I would anticipate a further drop in the numbers.&lt;br&gt;&lt;br&gt;Best,&lt;br&gt;Charlie</description>
		<content:encoded><![CDATA[<p>Dear Preparer,  </p>
<p>The Cloud Report looks at all rules as well as best practices even though at this time following best practices is not cause for the filing to be rejected.  With the 2 year furnishing rule at an end for the Wave 1 filers come June, these best practices will need to be scrutinized in more detail.  If the SEC required these best practices, these filings would not have been accepted.  </p>
<p>Your XBRL provider should have a validation tool that looks at SEC requirements as they pertain to XBRL 2.1 and EDGAR Filing Manual as well as items that will not cause a filing to be rejected, but would improve the quality of the filing.  If you are outsourcing with a third party, they should be evaluating this for you and implementing the best practices, if possible.  If you are doing the work yourself, it is important, but not required, that you address these best practices.  </p>
<p>Therefore, I understand why companies may evaluate vendors based on the XBRL Cloud.  Here at Rivet, we prefer to think of it as a collaboration tool.  We hold our clients’ filings in the highest regard and as you can see, through this collaboration, our error rate on the XBRL Cloud has dropped significantly.  If companies want to use the XBRL Cloud as an evaluation tool, it would be best to look at the error rate over time for all filings.  This would somewhat alleviate the spike for self filers not wanting to clear best practice errors.  It will be interesting to see what happens with the Wave 1 XBRL Cloud errors come June.  I would anticipate a further drop in the numbers.</p>
<p>Best,<br />Charlie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Preparer</title>
		<link>http://blog.rivetsoftware.com/2010/03/03/xbrl-cloud-report/comment-page-1/#comment-8512</link>
		<dc:creator>Preparer</dc:creator>
		<pubDate>Tue, 25 Jan 2011 05:32:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rivetsoftware.com/?p=1253#comment-8512</guid>
		<description>This is good information - I may have formed some impressions about the various vendors based on what I saw in the Cloud feeds.  I was unaware that &#039;errors&#039; were only &#039;warnings&#039;.  I assumed it was because the SEC was not rejecting filings with errors (yet), but that they still represented true &quot;errors&quot; that would have caused the documents to be rejected if the SEC was fully enforcing based the rules of the Edgar Filer Manual. Is that not the case?</description>
		<content:encoded><![CDATA[<p>This is good information &#8211; I may have formed some impressions about the various vendors based on what I saw in the Cloud feeds.  I was unaware that &#39;errors&#39; were only &#39;warnings&#39;.  I assumed it was because the SEC was not rejecting filings with errors (yet), but that they still represented true &#8220;errors&#8221; that would have caused the documents to be rejected if the SEC was fully enforcing based the rules of the Edgar Filer Manual. Is that not the case?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

