Have SFAS 166 and SFAS 167 improved the financial reporting for securitizations?

Minkwan Ahn, Samuel B. Bonsall, Zahn Bozanic, Yiwei Dou, Gordon Richardson, Dushyantkumar Vyas

JOURNAL OF BUSINESS FINANCE & ACCOUNTING(2020)

Cited 5|Views9
No score
Abstract
Critics have alleged that securitization accounting prior to 2010 was among the causes of the recent financial crisis. In response to this criticism, the Financial Accounting Standards Board (FASB) implemented two new accounting standards, SFAS 166 and SFAS 167, to improve the financial reporting for securitizations. Bank regulators have stated their belief that SFAS 166/167 will result in a consolidated balance sheet (and risk-based capital ratios based thereupon) that better reflects a bank's exposure to risk related to securitized assets. We document that, by ceding retained power or influence through the servicing/special servicing functions to third parties, SFAS 166/167 resulted in real effects to the extent that banks (particularly those that were weakly capitalized) achieved their accounting objectives in the post-SFAS 166/167 period through legitimate transaction structuring in line with the intent of the new rules. Further, we use capital market participants' assessments of risk retention by sponsoring banks as a benchmark, and provide evidence consistent with bank regulators' beliefs. In particular, following SFAS 166/167, equity investors of sponsoring banks do not consider (consider) as risk relevant securitized assets that receive off-balance sheet (on-balance sheet) treatment. Securitized assets that are consolidated under SFAS 166/167 exhibit the same risk relevance as assets that are not securitized, despite contractual provisions that would seem to imply substantial risk transfer.
More
Translated text
Key words
FASB,financial reporting,off-balance sheet,real effects,risk relevance,securitization,securitization accounting,SFAS 166 and 167
AI Read Science
Must-Reading Tree
Example
Generate MRT to find the research sequence of this paper
Chat Paper
Summary is being generated by the instructions you defined