<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Financial Accounting Standards Research Initiative &#187; Financial Statement Presentation</title>
	<atom:link href="http://www.fasri.net/index.php/category/standardsettingprojects/fsp/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fasri.net</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Mon, 30 Jan 2012 00:19:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Continued discussion related to the Financial Statement Presentation Roundtable</title>
		<link>http://www.fasri.net/index.php/2010/09/continued-discussion-related-to-the-fiancial-statement-presentation-roundtable/</link>
		<comments>http://www.fasri.net/index.php/2010/09/continued-discussion-related-to-the-fiancial-statement-presentation-roundtable/#comments</comments>
		<pubDate>Wed, 22 Sep 2010 15:24:23 +0000</pubDate>
		<dc:creator>Phil Shane</dc:creator>
				<category><![CDATA[Financial Statement Presentation]]></category>
		<category><![CDATA[Round Table Discussions]]></category>
		<category><![CDATA[Standard Setting Projects]]></category>
		<category><![CDATA[Standard Setting Updates]]></category>

		<guid isPermaLink="false">http://fasri.net/?p=2808</guid>
		<description><![CDATA[One important topic of yesterday&#8217;s very interesting roundtable with Nick Cappiello is the staff draft proposal to include an &#8220;operating-finance&#8221; section in the balance sheet. The staff apparently views some transactions to have characteristics of both operations and financing of those operations. Ideally, I guess most users would like a clear distinction between operating items and items [...]]]></description>
			<content:encoded><![CDATA[<p>One important topic of yesterday&#8217;s very interesting roundtable with Nick Cappiello is the staff draft proposal to include an &#8220;operating-finance&#8221; section in the balance sheet. The staff apparently views some transactions to have characteristics of both operations and financing of those operations. Ideally, I guess most users would like a clear distinction between operating items and items related to the financing of the company&#8217;s operations. Perhaps we have something to offer in conceptualizing the distinction.</p>
<p>I&#8217;ll start the ball rolling with an exercise: Is the net pension liability/asset a financing or operating item? Is the lease liability a financing or operating item? Both appear in the operating-finance category according to the current staff draft.</p>
<p>I&#8217;ll go out on a limb and suggest that the pension obligation belongs in operations because it arises out of the accrual accountinig decision to match labor expense with the periods in which the labor occurs; and the lease liability belongs in the financing section because it&#8217;s an obligation that does not arise out of an accrual accounting decision to match the cost of the underlying asset to periods benefited. What do others think?</p>
<p>Can you think of any items that clearly belong in an operating-finance category, or do you have a concept in mind that clearly separates operating from financing activities?</p>
<p>If there are other lingering questions from yesterday&#8217;s thought provoking presentation, please don&#8217;t hold back. Thanks!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fasri.net/index.php/2010/09/continued-discussion-related-to-the-fiancial-statement-presentation-roundtable/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Contact information for Roundtable on Financial Statement Presentation</title>
		<link>http://www.fasri.net/index.php/2010/09/contact-information-for-roundtable-on-financial-statement-presentation/</link>
		<comments>http://www.fasri.net/index.php/2010/09/contact-information-for-roundtable-on-financial-statement-presentation/#comments</comments>
		<pubDate>Tue, 21 Sep 2010 21:29:38 +0000</pubDate>
		<dc:creator>Phil Shane</dc:creator>
				<category><![CDATA[Financial Statement Presentation]]></category>
		<category><![CDATA[Round Table Discussions]]></category>

		<guid isPermaLink="false">http://fasri.net/?p=2803</guid>
		<description><![CDATA[In case you missed the first roundtable of the semester, we will have a recording available soon.  Meanwhile, you can access the slides for the session HERE.  And, Nick Cappiello, the presenter, has graciously provied his contact information at ntcappiello@fasb.org in case anyone has questions about the slides, the topic, or the presentation and discussion. Thank [...]]]></description>
			<content:encoded><![CDATA[<p>In case you missed the first roundtable of the semester, we will have a recording available soon.  Meanwhile, you can access the slides for the session <a href="http://www.venuegen.com/?q=node/6912">HERE</a>.  And, Nick Cappiello, the presenter, has graciously provied his contact information at <a href="mailto:ntcappiello@fasb.org">ntcappiello@fasb.org</a> in case anyone has questions about the slides, the topic, or the presentation and discussion. Thank you, Nick!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fasri.net/index.php/2010/09/contact-information-for-roundtable-on-financial-statement-presentation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Roundtable today! 4pm ET at VenueGen.com/?q=inv/sreginvitations</title>
		<link>http://www.fasri.net/index.php/2010/09/roundtable-today-4pm-et-at-venuegen-comqinvsreginvitations/</link>
		<comments>http://www.fasri.net/index.php/2010/09/roundtable-today-4pm-et-at-venuegen-comqinvsreginvitations/#comments</comments>
		<pubDate>Tue, 21 Sep 2010 14:30:10 +0000</pubDate>
		<dc:creator>Phil Shane</dc:creator>
				<category><![CDATA[Financial Statement Presentation]]></category>
		<category><![CDATA[Round Table Discussions]]></category>

		<guid isPermaLink="false">http://fasri.net/?p=2795</guid>
		<description><![CDATA[Slides for today&#8217;s session: Click HERE
Go directly to the meeting HERE
At 4pm Eastern time today, we will have our first roundtable for this academic year. Please join us!

See the new FASRI Roundtables WebPage describing how to use VenueGen, our new platform from which you can join the Roundtable discussion.

Nick Cappiello, an FASB Project Manager, will [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><strong><a href="http://fasri.net/wp-content/uploads/2010/09/General-FSP-slides_Sept-21-Webinar.pdf">Slides for today&#8217;s session: Click HERE</a></strong></p>
<p style="text-align: center;"><strong><a href="http://www.venuegen.com/?q=node/6912">Go directly to the meeting HERE</a></strong></p>
<p><strong>At 4pm Eastern time today, we will have our first roundtable for this academic year. Please join us!</strong></p>
<ul>
<li><strong>See the new </strong><a href="http://fasri.net/index.php/officehours/" target="_blank"><strong>FASRI Roundtables WebPage</strong></a><strong> describing how to use VenueGen, our new platform from which you can join the Roundtable discussion.</strong></li>
</ul>
<p>Nick Cappiello, an FASB Project Manager, will join us to discuss the IASB-FASB Financial Statement Presentation Project. This project has potentially enormous implications for our teaching and research. It proposes to change the face of financial statements to promote more rigorous theory-based financial statement analysis. Nick will discuss academic research that has influenced the development of the <a href="http://www.fasb.org/cs/ContentServer?c=Document_C&amp;pagename=FASB%2FDocument_C%2FDocumentPage&amp;cid=1176156966501" target="_blank">staff draft of an exposure draft</a> and research opportunities that can inform the ongoing debate about the nature and effectiveness of the proposed standards. In addition to the <a href="http://www.fasb.org/cs/ContentServer?c=Document_C&amp;pagename=FASB%2FDocument_C%2FDocumentPage&amp;cid=1176156966501" target="_blank">staff draft of the exposure draft</a>, here are some additional suggested sources of information about the issues we will discuss on Tuesday:</p>
<ul>
<li>A <a href="http://fasri.net/index.php/2010/08/did-they-mean-to-say-that/" target="_blank">FASRI conversation initiated by Bob Lipe</a> regarding the 2010 AAA Meetings’ panel discussion of the Financial Statement Presentation Project. </li>
<li>An <a href="http://fasri.net/index.php/2009/09/fasb-friendly-report-on-fsp/" target="_blank">Experimental Study on Financial Statement Presentation</a>, supported by FASRI, and conducted by Rob Bloomfield, Frank Hodge, Pat Hopkins and Kristi Rennekamp.</li>
<li>Steve Orpurt and Yoonseok Zang’s 2009 article in <em>The Accounting Review</em> titled <a href="http://link.aip.org/link/ACRVAS/v84/i3/p893/s1" target="_blank">“Do Direct Cash Flow Disclosures Help Predict Future Operating Cash Flows and Earnings?</a>“</li>
<li>Steve Penman’s <a href="http://fasri.net/index.php/2009/11/penman-on-financial-statement-presentation/" target="_blank">White Paper on Financial Statement Presentation</a>.</li>
</ul>
<p><strong>Don’t forget to see the new </strong><a href="http://fasri.net/index.php/officehours/" target="_blank"><strong>FASRI Roundtables WebPage</strong></a><strong> describing how to join the discussion or simply call in using VenueGen.</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.fasri.net/index.php/2010/09/roundtable-today-4pm-et-at-venuegen-comqinvsreginvitations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Information Complexity and Market Efficiency</title>
		<link>http://www.fasri.net/index.php/2010/09/information-complexity-and-market-efficiency/</link>
		<comments>http://www.fasri.net/index.php/2010/09/information-complexity-and-market-efficiency/#comments</comments>
		<pubDate>Wed, 15 Sep 2010 23:25:04 +0000</pubDate>
		<dc:creator>Jeremy Bentley</dc:creator>
				<category><![CDATA[Financial Statement Presentation]]></category>

		<guid isPermaLink="false">http://fasri.net/?p=2784</guid>
		<description><![CDATA[Jessen Hobson recently posted a paper on SSRN titled &#8220;Do the Benefits of Reducing Accounting Complexity Persist in Markets Prone to Bubble?&#8221;
I thought the title sounded interesting. It seems like a lot of recent research has focused on reducing accounting complexity (e.g. simplify presentation format, make things more transparent, etc). The premise is that reducing [...]]]></description>
			<content:encoded><![CDATA[<p>Jessen Hobson recently posted a paper on SSRN titled &#8220;<a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1676447">Do the Benefits of Reducing Accounting Complexity Persist in Markets Prone to Bubble?</a>&#8221;</p>
<p>I thought the title sounded interesting. It seems like a lot of recent research has focused on reducing accounting complexity (e.g. simplify presentation format, make things more transparent, etc). The premise is that reducing complexity will result in improved efficiency (defined in this case as market value = fundamental value) and improved fairness (defined as novice investors not getting taken advantage of). This has been especially emphasized in recent months as a potential magic bullet for preventing future bubbles. If we could only make the accounting and presentation simpler, we could potentially prevent another dot.com bubble, housing bubble, etc.</p>
<p>So, what if that premise is wrong? What if reducing accounting complexity really doesn&#8217;t help at all? This paper argues that there are two links required for a reduction of complexity to result in greater efficiency: (1) reduction in complexity must result in greater processing of information and (2) greater processing of information must result in greater market efficiency.</p>
<p>So, does it work? Does reducing complexity improve efficiency? To quote from the paper,</p>
<blockquote><p>Consistent with the SEC’s efforts to make accounting information less complex, I find that such measures do indeed lead to greater processing of that information. However,<em> inconsistent</em> with the SEC’s goal to protect (particularly novice) investors, I find that when markets are prone to bubble, greater processing of information <em>does not</em> translate into more efficient markets, and <em>does</em> allow traders choosing to become informed to extract money from other, less informed traders.</p></blockquote>
<p>So, to answer the question posed by the title of the paper: no. Reducing accounting complexity doesn&#8217;t appear to be the magic bullet to prevent another bubble crash.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fasri.net/index.php/2010/09/information-complexity-and-market-efficiency/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Direct Method Cash Flow Statements and Symmetry</title>
		<link>http://www.fasri.net/index.php/2010/08/direct-method-cash-flow-statements-and-symmetry/</link>
		<comments>http://www.fasri.net/index.php/2010/08/direct-method-cash-flow-statements-and-symmetry/#comments</comments>
		<pubDate>Tue, 10 Aug 2010 18:51:51 +0000</pubDate>
		<dc:creator>Robert Bloomfield</dc:creator>
				<category><![CDATA[Cash Flow Reporting]]></category>
		<category><![CDATA[Financial Statement Presentation]]></category>

		<guid isPermaLink="false">http://fasri.net/?p=2693</guid>
		<description><![CDATA[How do we measure the quality of a panel discussion?  If we measure it by the subsequent discussion it generates, the AAA panel on Financial Statement Presentation was definitely a success.  Bob Lipe and I had a chance to talk with a number of people afterward, and I thought I would put in [...]]]></description>
			<content:encoded><![CDATA[<p>How do we measure the quality of a panel discussion?  If we measure it by the subsequent <a href="http://fasri.net/index.php/2010/08/did-they-mean-to-say-that/">discussion </a>it generates, the AAA panel on Financial Statement Presentation was definitely a success.  Bob Lipe and I had a chance to talk with a number of people afterward, and I thought I would put in my own two cents on what we might take away about the benefits of direct method cash flow reporting.  Up front let me emphasize that these thoughts aren’t my own invention; many of them are from analysts who can’t post their own comments or even have comments attributed to them due to their employment contracts.</p>
<p>My key take-away from these conversations is that analysts’ request for the direct method is in part a request for <em>symmetry </em>in how information is displayed/disaggregated across the financial statements, and a way to encourage companies to give equal weight and equal treatment to each of the primary financial statements.  GAAP net income is largely an accrual-based number and the income statement disaggregates that accrual-based number into accrual-based line items.  Total assets, total liabilities, and shareholders’ equity are disaggregated on the balance sheet into the components that constitute those totals.  This lets users identify the sources of those totals and assign different valuations to each asset and liability component if they choose to (especially since many of the line items are measured at historical cost).</p>
<p>For some reason, operating cash flow under the indirect cash flow method does not receive the same treatment.  The total operating cash flow number is the only item in the operating section of the cash flow statement that is a true cash-based number.  The indirect cash flow statement is an itemized list of changes in the other financial statements that are necessary to get from net income to operating cash flow.  As a result, unlike with the income statement, an analyst cannot make judgments about which components belong and don’t belong in a normalized operating cash flow number because the analyst does not know what the operating cash flow cash components actually are!  In that regard, operating cash flow is a bit of a “black box.”</p>
<p>I confess, I still find myself wondering how much effect direct cash flow reporting will have on decision making.  More information is better—free disposal, and all that&#8211;but there are other ways of conveying cash flow information (such as extensive footnote disclosure).  One possibility is that a direct cash flow report would focus more analyst attention on cash flows, which in turn would lead to more and earlier cash flow disclosures in earnings announcements, more discussion of in conference calls, and so on.  Unfortunately, direct cash flow reporting is so rare in the US, and so abbreviated in other countries (compared to what the FASB and IASB are proposing) that it is hard to infer the benefits of the proposals from existing data.</p>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;"><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:DoNotShowComments /> <w:DoNotShowPropertyChanges /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val="&#45;-" /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--><!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:roman; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face 	{font-family:Consolas; 	panose-1:2 11 6 9 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:modern; 	mso-font-pitch:fixed; 	mso-font-signature:-1610611985 1073750091 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin-top:0in; 	margin-right:0in; 	margin-bottom:10.0pt; 	margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoPapDefault 	{mso-style-type:export-only; 	margin-bottom:10.0pt; 	line-height:115%;} @page WordSection1 	{size:8.5in 11.0in; 	margin:1.0in 1.0in 1.0in 1.0in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.WordSection1 	{page:WordSection1;} --><!--[if gte mso 10]> <mce:style><!   /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin-top:0in; 	mso-para-margin-right:0in; 	mso-para-margin-bottom:10.0pt; 	mso-para-margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin;} --> <!--[endif]--></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt; color: #215868;">How do we measure the quality of a panel discussion?<span> </span>If we measure it by the subsequent discussion it generates, the AAA panel on Financial Statement Presentation was definitely a success.<span> </span>Bob Lipe and I had a chance to talk with a number of people afterward, and I thought I would put in my own two cents on what we might take away about the benefits of direct method cash flow reporting.<span> </span>Up front let me emphasize that these thoughts aren’t my own invention; many of them are from analysts who can’t post their own comments or even have comments attributed to them due to their employment contracts.</span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt; color: #215868;"> </span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt; color: #215868;">My key take-away from these conversations is that analysts’ request for the direct method is in part a request for symmetry in how information is displayed/disaggregated across the financial statements, and a way to encourage companies to give equal weight and equal treatment to each of the primary financial statements.  GAAP net income is largely an accrual-based number and the income statement disaggregates that accrual-based number into accrual-based line items.  Total assets, total liabilities, and shareholders’ equity are disaggregated on the balance sheet into the components that constitute those totals.<span> </span>This lets users identify the sources of those totals and assign different valuations to each asset and liability component if they choose to (especially since many of the line items are measured at historical cost). </span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt; color: #215868;"> </span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt; color: #215868;">For some reason, operating cash flow under the indirect cash flow method does not receive the same treatment.  The total operating cash flow number is the only item in the operating section of the cash flow statement that is a true cash-based number.  The indirect cash flow statement is an itemized list of changes in the other financial statements that are necessary to get from net income to operating cash flow.  As a result, unlike with the income statement, an analyst cannot make judgments about which components belong and don’t belong in a normalized operating cash flow number because the analyst does not know what the operating cash flow cash components actually are!  In that regard, operating cash flow is a bit of a “black box.”<span> </span></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt; color: #215868;"> </span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt; color: #215868;">I confess, I still find myself wondering how much effect direct cash flow reporting will have on decision making.<span> </span>More information is better—free disposal, and all that&#8211;but there are other ways of conveying cash flow information (such as extensive footnote disclosure).<span> </span>One possibility is that a direct cash flow report would focus more analyst attention on cash flows, which in turn would lead to more and earlier cash flow disclosures in earnings announcements, more discussion of in conference calls, and so on.<span> </span>Unfortunately, direct cash flow reporting is so rare in the US, and so abbreviated in other countries (compared to what the FASB and IASB are proposing) that it is hard to infer the benefits of the proposals from existing data.</span><span style="font-size: 10.5pt; font-family: Consolas;"> </span></p>
<p class="MsoNormal">
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.fasri.net/index.php/2010/08/direct-method-cash-flow-statements-and-symmetry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Did they mean to say that?</title>
		<link>http://www.fasri.net/index.php/2010/08/did-they-mean-to-say-that/</link>
		<comments>http://www.fasri.net/index.php/2010/08/did-they-mean-to-say-that/#comments</comments>
		<pubDate>Thu, 05 Aug 2010 18:21:11 +0000</pubDate>
		<dc:creator>Robert Lipe</dc:creator>
				<category><![CDATA[Financial Statement Presentation]]></category>

		<guid isPermaLink="false">http://fasri.net/?p=2671</guid>
		<description><![CDATA[Just got back from AAA meeting in San Francisco.  Great meeting.  One session consisted of a panel of preparers and users debating the costs and benefits of the joint IASB/FASB project on financial statement presentation.  In general it was very good. But I think the analysts were so focused on pushing for a direct method [...]]]></description>
			<content:encoded><![CDATA[<p>Just got back from AAA meeting in San Francisco.  Great meeting.  One session consisted of a panel of preparers and users debating the costs and benefits of the joint IASB/FASB project on financial statement presentation.  In general it was very good.<span id="more-2671"></span> But I think the analysts were so focused on pushing for a direct method cash flow statement, that they perhaps gave an erroneous impression to the academics in the audience.</p>
<p>In particular, they kept stating that analysts&#8217; use of earnings in valuation (specifically PE multiples) would probably decrease when the analysts could take the numbers from the direct method cash flow statement, plug them in a spreadsheet, and use those numbers to project future cash flows.  If you listened to their words, it seemed like they preferred a valuation model that did not use any accrual accounting concepts.  Several audience members mentioned this to me later.</p>
<p>I believe that their push for the direct method resulted in the use of short-cut terms like &#8220;cash earnings&#8221;.  Having read some explanations of what analysts do in projecting future profitability, my impression is they start with accrual earnings and then back out a few accruals that they feel might behave in special ways (e.g., special items) which could reduce the predictive ability of their model.  But the majority of accruals are incorporated in the &#8220;cash&#8221; numbers that are the main inputs for their analysis.</p>
<p>If I am wrong, and they really meant what they said, then maybe the direct method cash flow statement is not such a good idea.  Research shows that the accrual numbers are more correlated with stock price performance than cash flow numbers (see Dechow 1994).  Investors might give more weight to the cash and less to the earnings because the cash is now salient and some finance professors seem infatuated with cash.</p>
<p>Did any of the rest of you attend the session?  What was your impression?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fasri.net/index.php/2010/08/did-they-mean-to-say-that/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>SEC Chief Accountant Questions Convergence by June 2011</title>
		<link>http://www.fasri.net/index.php/2010/04/sec-chief-accountant-questions-convergence-by-june-2011/</link>
		<comments>http://www.fasri.net/index.php/2010/04/sec-chief-accountant-questions-convergence-by-june-2011/#comments</comments>
		<pubDate>Wed, 28 Apr 2010 22:58:02 +0000</pubDate>
		<dc:creator>Jeff Wilks</dc:creator>
				<category><![CDATA[Fair Value Accounting]]></category>
		<category><![CDATA[Financial Instruments]]></category>
		<category><![CDATA[Financial Press News and Opinion]]></category>
		<category><![CDATA[Financial Statement Presentation]]></category>
		<category><![CDATA[International Convergence]]></category>
		<category><![CDATA[Leasing]]></category>
		<category><![CDATA[Revenue Recognition]]></category>
		<category><![CDATA[Standard Setting Projects]]></category>

		<guid isPermaLink="false">http://fasri.net/?p=2489</guid>
		<description><![CDATA[A recent Journal of Accountancy article states that the SEC Chief Accountant Jim Kroeker would support the FASB&#8217;s cutting the number of convergence projects due for completion in 2011. Here&#8217;s one excerpt from that article:
“June 30, 2011, is an arbitrary deadline and it’s not one that’s been put in place by the SEC or by [...]]]></description>
			<content:encoded><![CDATA[<p>A recent <a href="http://www.journalofaccountancy.com/Web/20102866.htm"><em>Journal of Accountancy </em>article</a><em> </em>states that the SEC Chief Accountant Jim Kroeker would support the FASB&#8217;s cutting the number of convergence projects due for completion in 2011. Here&#8217;s one excerpt from that article:</p>
<blockquote><p>“June 30, 2011, is an arbitrary deadline and it’s not one that’s been put in place by the SEC or by our road map,” said Kroeker. Citing FIN 46(R) as an example of an accelerated project that later needed to be reworked, Kroeker said that what’s most important is to ensure through the exposure process that the final standards are a “long term, sustainable solution.”</p></blockquote>
<p>I suspect the FASB is not all that surprised by Kroeker&#8217;s view, given how good the lines of communication typically are between the FASB and the SEC. However, I suspect the IASB and other supporters of a single, global accounting standard will be a little surprised and will interpret Kroeker&#8217;s comments as (further) evidence that the US will not be adopting IFRS any time in the near future. They may even increase the volume on their arguments that the IASB should not give so much preferential treatment to the FASB and SEC in its standard setting activities. Should make for some interesting articles over the next few weeks!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fasri.net/index.php/2010/04/sec-chief-accountant-questions-convergence-by-june-2011/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Feedback on Stephen Penman Roundtable</title>
		<link>http://www.fasri.net/index.php/2009/11/feedback-on-stephen-penman-roundtable/</link>
		<comments>http://www.fasri.net/index.php/2009/11/feedback-on-stephen-penman-roundtable/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 19:11:53 +0000</pubDate>
		<dc:creator>Robert Lipe</dc:creator>
				<category><![CDATA[Financial Statement Presentation]]></category>
		<category><![CDATA[Round Table Discussions]]></category>

		<guid isPermaLink="false">http://fasri.net/?p=1667</guid>
		<description><![CDATA[The roundtable discussion with Stephen Penman yesterday was quite good.  Lots of good discussion in both voice and typed chat.  One thing I learned is that Stephen stresses subjectivity as a reason behind his views. While I am convinced that Stephen dislikes some forms of subjectivity, I think his views are more subtle than this.  [...]]]></description>
			<content:encoded><![CDATA[<p>The roundtable discussion with Stephen Penman yesterday was quite good.  Lots of good discussion in both voice and typed chat.  One thing I learned is that Stephen stresses subjectivity as a reason behind his views. While I am convinced that Stephen dislikes some forms of subjectivity, I think his views are more subtle than this.  <span id="more-1667"></span>Specifically, suppose that a machine used in the company’s operations experiences an increase in value during the year, and a highly reliable measure of this change in value exists.  The revised value measure may be less subjective that a measure derived from historical cost, expected useful life, and expected salvage value.  If subjectivity is the key element in determining desirable accounting, we should record the revised value of the machine.</p>
<p>However, what if the company creates value by synergistically combining the machine with a trained workforce and results of its research department?  I see nothing in the deliberations of the IASB or FASB to say they support recording increases in the value of the workforce or research this period, as increases in value of workforce training and basic research do not meet the definition/measurability criteria required for asset recognition.  Thus, anyone who believes that the so-called “balance sheet view” has a goal of equating a company’s book value and market value are complaining about a straw man that is not part of the FASB’s agenda.</p>
<p>But back to Stephen’s views.  I believe he would reject fair valuing the company’s plant asset even if a non-subjective level 1 fair value was available.  He expects reported operating earnings to reflect the enhanced value of a trained workforce or proprietary research over time as the company is able to earn higher margins than its competitors.  He also believes these margins are persistent.  I agree with these views.  Stephen’s concern is that if the company records fair value increases for the plant, the reported margins would include transitory gains and losses.  He would rather use some sort of allocated historical cost for the plant in the belief that using a comparable measurement approach for all operating assets produces operating margins that are easier for analysts to use in predicting earnings and valuing the company.</p>
<p>As a result, the debate seems to be less about subjectivity and more about how mixing measurement attributes for operating assets can reduce the ability of analysts to do their jobs.  I would think some of the propositions underlying Stephen’s views are empirically testable.  What do the other bloggers think?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fasri.net/index.php/2009/11/feedback-on-stephen-penman-roundtable/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Penman on Financial Statement Presentation</title>
		<link>http://www.fasri.net/index.php/2009/11/penman-on-financial-statement-presentation/</link>
		<comments>http://www.fasri.net/index.php/2009/11/penman-on-financial-statement-presentation/#comments</comments>
		<pubDate>Fri, 06 Nov 2009 18:43:56 +0000</pubDate>
		<dc:creator>Robert Bloomfield</dc:creator>
				<category><![CDATA[Financial Statement Presentation]]></category>
		<category><![CDATA[Round Table Discussions]]></category>

		<guid isPermaLink="false">http://fasri.net/?p=1654</guid>
		<description><![CDATA[In preparation for his FASRI Roundtable discussion, Stephen Penman has helpfully shared his CEASA White Paper on Financial Statement Presention, which you can download here.
The paper discusses disaggregation in some depth, providing guidelines for how line items should be disaggregated on both the income statement and the balance sheet.  I need to read more carefully, [...]]]></description>
			<content:encoded><![CDATA[<p>In preparation for his <a href="http://fasri.net/index.php/2009/11/stephen-penman-leads-roundtable-discussion/">FASRI Roundtable discussion</a>, Stephen Penman has helpfully shared his CEASA White Paper on Financial Statement Presention, which you can download <a href="http://fasri.net/wp-content/uploads/2009/11/Financial-Statement-Presentation-WP-061809.docx">here</a>.</p>
<p>The paper discusses disaggregation in some depth, providing guidelines for how line items should be disaggregated on both the income statement and the balance sheet.  I need to read more carefully, but Stephen&#8217;s proposals seem more similar to what the FASB and IASB are proposing than they are different:  disaggregation on the balance sheet should separate items with different risk profiles, while disaggregation on the income statement should allow better prediction of future cash flows.</p>
<p>More novel, to my eyes, is Stephen&#8217;s advocacy of a &#8216;forward looking earnings&#8217; number.  Stephen starts with the problem that comprehensive income includes many highly transitory items, which can be a problem in using earnings to predict the future.  From the paper:</p>
<blockquote><p>We suggest the following solution. Report per-share (comprehensive) Earnings to Common Shareholders but also report a second per-share number that bears on the future. This is not a forecast, but rather current Earnings to Common Shareholders stripped of items reported in the disaggregated income statement that do not bear on the future. Discarded items would include one-time items and transitory gains and losses which, though recurring in the future, do not predict next year’s gain or loss. One way to think about it is as follows: What number would a (diligent) analyst forecast as forward earnings? What income statement line items are omitted from the analyst’s forecasting spreadsheet? Clearly that analyst is not forecasting the one-time items of the previous period that will not repeat, nor components of earnings that are not predictable. The second earnings-per-share number might be called Forward-Looking Earnings (to Common) with the understanding that it is to align with “forward earnings” that analysts forecast. In this way, financial reporting and analysts’ forecasts would align such that analysts’ forecast errors could be determined by comparing their forecast to next year’s realization of Forward-Looking Earnings (and not earnings-per-share that includes gains and losses, write-downs, etc. that they could not be expected to forecast). Not only would a summary number be produced with forward-looking information but a discipline would be imposed on the analyst community, so that investors who use analysts’ forecasts would know just what is being included in their “forward earnings” and in a “forward” P/E ratio.</p>
<p>With its focus on forecasting, our proposed income statement template is designed to identify items to be stripped out in determining Forward-Looking Earnings. The components retained could be presented in a second column in the income statement that totals to Forward-Looking Earnings, or as a supplementary schedule. We are aware that a division between forward-looking and other income invites opportunistic reporting. A requirement that management justify classifications in the accounting policy footnote mitigates, as does rigorous auditing. The FASB-IASB might engage the analyst community on the matter, in the hope that a strong consensus would emerge to which management would then be committed.</p></blockquote>
<p>Well, maybe not <em>that </em>novel.  This sounds to me somewhat similar to the notion of &#8216;headline earnings&#8217; <a href="https://www.saica.co.za/documents/Circ7_2002.PDF">proposed a good 15 years ago by the UK Society of Investment Professionals</a>:</p>
<blockquote><p>UKSIP Headline Earnings has been used in the calculation of the price/earnings ratios of the United Kingdom companies in the Financial Times since 1994 and has also been used by computer bureaus and other intermediaries in the United Kingdom. At the same time Headline Earnings has been adopted in South Africa not only for use by but also as a standard definition for the announcement of company results.</p>
<p>The aim, as set out in Paragraph (vii) of the Summary of SIP 1 is “… to define an earnings figure calculated on a standard basis, which can be used as an unambiguous reference point …”. It should be noted that SIP 1 in defining Headline Earnings in accordance with this aim delineates clearly between such a reference point and an earnings figure calculated <strong>as a measure of the company’s maintainable earning capacity</strong>, which in the view of SIP 1 is a figure which cannot be calculated on a standard basis, but will vary from company to company and in other ways.</p></blockquote>
<p>I will be interested to hear Stephen&#8217;s thoughts on the similarity of these earnings notions, and on how this idea could be made workable &#8212; and also, whether this earnings number would need to be reported as part of GAAP, or could be something outside of accounting standards.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fasri.net/index.php/2009/11/penman-on-financial-statement-presentation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stephen Penman Leads Roundtable Discussion</title>
		<link>http://www.fasri.net/index.php/2009/11/stephen-penman-leads-roundtable-discussion/</link>
		<comments>http://www.fasri.net/index.php/2009/11/stephen-penman-leads-roundtable-discussion/#comments</comments>
		<pubDate>Wed, 04 Nov 2009 15:37:33 +0000</pubDate>
		<dc:creator>Robert Bloomfield</dc:creator>
				<category><![CDATA[Archival Methods]]></category>
		<category><![CDATA[Conceptual Framework Project]]></category>
		<category><![CDATA[Fair Value Accounting]]></category>
		<category><![CDATA[Financial Press News and Opinion]]></category>
		<category><![CDATA[Financial Statement Presentation]]></category>
		<category><![CDATA[Round Table Discussions]]></category>

		<guid isPermaLink="false">http://fasri.net/?p=1646</guid>
		<description><![CDATA[You may know Columbia Business School Professor Stephen Penman as the 14th-most downloaded author on SSRN.  Or you might know him as a Director of the Center for Excellence in Accounting and Security Analysis. Or perhaps as author of Financial Statement Analysis and Security Valuation.
More recently, Stephen has been visible as a critic of the [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft" title="Stephen Penman" src="http://www4.gsb.columbia.edu/ipmedia/shp38/profiles/shp38_110x90.jpg" alt="" width="90" height="110" />You may know Columbia Business School Professor Stephen Penman as the <a href="http://papers.ssrn.com/sol3/cf_dev/AbsByAuth.cfm?per_id=15046">14th-most downloaded author on SSRN</a>.  Or you might know him as a Director of the <a href="http://www4.gsb.columbia.edu/ceasa/about/advisory">Center for Excellence in Accounting and Security Analysis</a>. Or perhaps as author of <a href="http://www.amazon.com/Financial-Statement-Analysis-Security-Valuation/dp/007253317X">Financial Statement Analysis and Security Valuation</a>.</p>
<p>More recently, Stephen has been visible as a critic of the direction of accounting standard setting.  Stephen is a fellow member of the <a href="http://aaahq.org/about/directory2010/committee/fasc.htm">AAA Financial Accounting Standards Committee</a>.  In that role, he has been a primary author on a <a href="http://fasri.net/index.php/2009/08/thinking-about-alternative-conceptual-frameworks/">proposal for a Conceptual Framework </a>for accounting standards that differs substantially from those approved and being considered by the FASB and IASB.  He has also published, through CEASA, a white paper titled <a href="https://www4.gsb.columbia.edu/rt/null?&amp;exclusive=filemgr.download&amp;file_id=73740&amp;rtcontentdisposition=filename%3DSP%20Occasional%20Paper%20-%20Intangible%20Assets%20final2.pdf">Accounting for Intangible Assets:  There is Also an Income Statement</a>, and has a forthcoming CEASA white paper on Financial Statement Presentation.</p>
<p>Join us on Wednesday, November 11th at 11am, when Stephen will lead a Roundtable discussion.  While our first order of business will be to discuss Stephen&#8217;s views on accounting standards, and his thoughts on related research opportunities, we will surely devote some time to Stephen&#8217;s thoughts about the state and future of accounting research more generally, given Stephen&#8217;s extraordinary success and influence in the field.</p>
<p>Details about participation are <a href="http://fasri.net/index.php/officehours/">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fasri.net/index.php/2009/11/stephen-penman-leads-roundtable-discussion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

