{"id":613,"date":"2016-04-18T14:22:53","date_gmt":"2016-04-18T18:22:53","guid":{"rendered":"https:\/\/seci.wpenginepowered.com\/?p=613"},"modified":"2016-04-18T14:22:53","modified_gmt":"2016-04-18T18:22:53","slug":"get-the-message-sec-enforcement-case-deals-with-evaluating-icfr-weaknesses","status":"publish","type":"post","link":"https:\/\/seciblog.pli.edu\/index.php\/get-the-message-sec-enforcement-case-deals-with-evaluating-icfr-weaknesses\/","title":{"rendered":"Get the Message: SEC Enforcement Case Deals With Evaluating ICFR Weaknesses!"},"content":{"rendered":"

By sending a clear message through the enforcement process, the SEC has come full circle in their concerns about whether ICFR audits are finding material weaknesses. The staff has said on numerous occasions that they see too many situations where a company identifies a control deficiency but the company\u2019s analysis fails when assessing whether the control deficiency is in fact a material weakness<\/strong>.<\/p>\n

Over the last few years the SEC Staff have emphasized their concerns in numerous speeches and other public settings. As they sometimes do when they don\u2019t see companies listening, they have also emphasized this issue through enforcement<\/strong>.<\/p>\n

This enforcement is dramatic, involving:<\/p>\n

The company<\/p>\n

Two company officers<\/p>\n

The audit partner<\/p>\n

The ICFR consulting firm partner (a surprise here!)<\/p>\n

 <\/p>\n

This excerpt from a December 2015 speech by Deputy Chief Accountant Brian Croteau summarizes the SEC\u2019s concerns:<\/p>\n

Still, given the frequency with which certain ICFR issues are identified in our consultations with registrants, I\u2019d be remiss not to remind management and auditors of the importance of properly identifying and describing the nature of a control deficiency<\/strong> and understanding the complete population of transactions that a control is intended to address in advance of assessing the severity of any identified deficiencies. \u00a0Then, once ready to assess the severity of a deficiency, it\u2019s important to remember that there are two components to the definition of a material weakness – likelihood and magnitude.\u00a0 The evaluation of whether it is reasonably possible that a material misstatement could occur and not be prevented or detected on a timely basis requires careful analysis that contemplates both known errors, if any, as well as potential misstatements for which it is reasonably possible that the misstatements would not be prevented or detected in light of the control deficiency.\u00a0 This latter part of the evaluation, also referred to as analysis of the so called \u201ccould factor,\u201d often requires management to evaluate information that is incremental to that which would be necessary, for example, for a materiality assessment of known errors pursuant to SAB 99. The final conclusions on severity of deficiencies frequently rest on this \u201ccould factor\u201d portion of the deficiency evaluation; however, too often this part of the evaluation appears to be an afterthought in a company\u2019s analysis.\u00a0 Yet consideration of the \u201ccould factor\u201d is very important.\u00a0<\/strong><\/p>\n

The issue is clear; too often companies are finding a control deficiency but not appropriately evaluating the severity of the issue to determine if it is a material weakness.<\/p>\n

In a \u201cclassic\u201d example this SEC enforcement involves a company that performed its annual ICFR evaluation and stated in its form 10-K that ICFR was effective at year-end. Then, shortly after that report in their Form 10-K, the company restated its financial statements and disclosed the existence of a material weakness. It is very unlikely that the material weakness arose between the year-end of the Form 10-K and the date of the restatement.<\/p>\n

You can read about the enforcement in this press release, which also has links to the SEC Enforcement Orders for the company and the individuals involved:<\/p>\n

www.sec.gov\/news\/pressrelease\/2016-48.html<\/u><\/a><\/p>\n

 <\/p>\n

The fact that the company and auditor were named is not surprising. What is surprising is that the firm the company retained to provide SOX 404 services, which included assisting \u201cmanagement with the documentation, testing, and evaluation of the company\u2019s ICFR\u201d and no external report, was included in the enforcement.<\/p>\n

This is a loud and clear message to all participants in the process! Be thorough and complete in your evaluation of control deficiencies!<\/strong><\/p>\n

If you would like to delve a bit deeper into this issue one of our follow-up posts to this year\u2019s Form 10-K Tune-Up One Hour Briefing focused on ICFR issues, including the issue raised in this enforcement case.<\/p>\n

You can read our post at:<\/p>\n

seciblog.pli.edu\/?p=530<\/u><\/a><\/p>\n

 <\/p>\n

As always, your thoughts and comments are welcome and appreciated!<\/strong><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

By sending a clear message through the enforcement process, the SEC has come full circle in their concerns about whether ICFR audits are finding material weaknesses. The staff has said on numerous occasions that they see too many situations where a company identifies a control deficiency but the company\u2019s analysis fails when assessing whether the … Continue reading Get the Message: SEC Enforcement Case Deals With Evaluating ICFR Weaknesses!<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"_wpas_customize_per_network":false},"categories":[1],"tags":[149,142,111,32,156,76,157,33,100,121,103,4,133],"coauthors":[163],"class_list":["post-613","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-10-k","tag-am-100","tag-am-law","tag-audit","tag-audit-committees","tag-auditors","tag-enforcement","tag-icfr","tag-pli","tag-pli-free-fridays","tag-pli-securities-regulation","tag-sec","tag-sox"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/seciblog.pli.edu\/index.php\/wp-json\/wp\/v2\/posts\/613","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/seciblog.pli.edu\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/seciblog.pli.edu\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/seciblog.pli.edu\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/seciblog.pli.edu\/index.php\/wp-json\/wp\/v2\/comments?post=613"}],"version-history":[{"count":0,"href":"https:\/\/seciblog.pli.edu\/index.php\/wp-json\/wp\/v2\/posts\/613\/revisions"}],"wp:attachment":[{"href":"https:\/\/seciblog.pli.edu\/index.php\/wp-json\/wp\/v2\/media?parent=613"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/seciblog.pli.edu\/index.php\/wp-json\/wp\/v2\/categories?post=613"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/seciblog.pli.edu\/index.php\/wp-json\/wp\/v2\/tags?post=613"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/seciblog.pli.edu\/index.php\/wp-json\/wp\/v2\/coauthors?post=613"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}