20,000 Hours to Comply With SOX?
Anecdotal evidence of the immense cost of complying with Sarbanes-Oxley, particularly the internal controls provision in Section 404, is starting to surface as next year's deadlines grow nearer. According to this article in USA Today, the CEOs of Fortune 500 companies Affiliated Computer Services and Steelcase say it will take their companies 20,000 staff hours to comply, the equivalent of 10 people working full time for a year. Other companies such as Dell estimate that compliance will take closer to 5,000 hours.
As discussed here previously, the SEC's Final Rule regarding Section 404 estimated an average 383-hour workload per company, a figure that was raised from the SEC's original estimate of just 5 hours after strong comments such as this one from Intel's Cary Klafter advised the SEC that its had "underestimated the time and effort involved in complying with these rules by at least a factor of 100, if not a greater order of magnitude." The numbers in the USA Today article suggest that Klafter could have added another zero to the end of that prediction and still have been correct.
| Permalink | Print Article | Back To Top |











TrackBack
TrackBack URL for this entry:
http://blog.riskmetrics.com/cgi-bin/mt-tb.cgi/214
Listed below are links to weblogs that reference 20,000 Hours to Comply With SOX?:
» Today's links from ProfessorBainbridge.com
I wonder what Hugh Hewitt thinks about this? This is strangely addictive (link via Anthony). A very bad idea: A SOX II to tackle executive compensation. (Go here for my comp posts.) Update: Corp Law Blog is on the case, [Read More]
Tracked on October 23, 2003 3:43 PM
» Today's shareholder access question: What will it cost? from ProfessorBainbridge.com
As part of our continuing coverage of the SEC's shareholder access proposal, today's SEC question is # A.2:What would be the cost to companies if the Commission adopted proxy rules requiring companies to include security holder nominees in company proxy [Read More]
Tracked on October 23, 2003 3:44 PM