<?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: Rebuilding Public Trust: The Case for Compliant Financial Data</title>
	<atom:link href="http://xbrlblog.com/rebuilding-public-trust-the-case-for-compliant-financial-data.html/feed" rel="self" type="application/rss+xml" />
	<link>http://xbrlblog.com/rebuilding-public-trust-the-case-for-compliant-financial-data.html</link>
	<description>it is about improving the way information is shared</description>
	<lastBuildDate>Tue, 09 Mar 2010 07:33:34 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter Boritz</title>
		<link>http://xbrlblog.com/rebuilding-public-trust-the-case-for-compliant-financial-data.html/comment-page-1#comment-2248</link>
		<dc:creator>Peter Boritz</dc:creator>
		<pubDate>Tue, 30 Jun 2009 22:27:58 +0000</pubDate>
		<guid isPermaLink="false">http://xbrlblog.com/?p=869#comment-2248</guid>
		<description>Financial transparency does not come without a price. Accuracy is only one of many subjects that need to be addressed with XBRL filings. How does the filer verify that what is described in the instance document and extension match what he/she thinks it does? How does the filer validate that the filing matches the paper/html filing? Are the extended labels correct? Is the filing properly mapped to respective dimension segments?

Not specifying a dimension segment will result in a mapping to a dimension default. This is not is not necessarily what is desired. For more complex reports, such as the statement of shareholders equity it would be syntactically acceptable, but would represent incorrect information in the filing.

What procedures and verification would an internal auditor be required to follow in order to minimize liability? How does the filing meet with SOX compliance?

XBRL is still in the birth stages of development. These are questions that must be address for it to be successful. Many preparers are not equipped to deal with these issues. This will change over time. Transparency and its many authentication issues are yet to be taken under consideration. There are many pioneers. Filers must ask the right questions and seek solutions as they move into the XBRL filing process.</description>
		<content:encoded><![CDATA[<p>Financial transparency does not come without a price. Accuracy is only one of many subjects that need to be addressed with XBRL filings. How does the filer verify that what is described in the instance document and extension match what he/she thinks it does? How does the filer validate that the filing matches the paper/html filing? Are the extended labels correct? Is the filing properly mapped to respective dimension segments?</p>
<p>Not specifying a dimension segment will result in a mapping to a dimension default. This is not is not necessarily what is desired. For more complex reports, such as the statement of shareholders equity it would be syntactically acceptable, but would represent incorrect information in the filing.</p>
<p>What procedures and verification would an internal auditor be required to follow in order to minimize liability? How does the filing meet with SOX compliance?</p>
<p>XBRL is still in the birth stages of development. These are questions that must be address for it to be successful. Many preparers are not equipped to deal with these issues. This will change over time. Transparency and its many authentication issues are yet to be taken under consideration. There are many pioneers. Filers must ask the right questions and seek solutions as they move into the XBRL filing process.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
