7 ms·
As someone who had to deal a lot with SOX compliance throughout my career, I would love to see the regulations loosened. They are overly onerous and in many ca
by jedberg 10y ago
As someone who had to deal a lot with SOX compliance throughout my career, I would love to see the regulations loosened. They are overly onerous and in many cases downright bad, because they are so broadly written. At the same time, enforcement is terrible, because of the same broadly written rules.
Basically, you and your auditor work together to come up with an overly complex set of rules that somewhat meets the requirements, then your auditor brings in a bunch of consultants to help you implement their rules, which usually just means checking a lot of boxes, and then everyone calls it a day.
So really all it does is create a lot of work for a lot of people for very little gain. In a lot of cases we were going to do some of that stuff anyway, but now we had to slow down and show the auditor all the work. An auditor who usually doesn't care -- all they want to do is be able to say "yep I watched their presentation on this".
So I was quite surprised by the headline, that the auditor firms would want to roll it back. It's basically just a huge money maker for them.
And then I saw what they want to change -- they want to make the rules looser on how the auditors are audited. Basically they want to be able to keep being lazy.
SOX had great intentions but was one of the most poorly implemented regulations ever.
- Shivetya 10y agoI would not want to know what my employer spends but I know it takes my team of five plus a director four to six days to get through it all. the amount of seemingly useless documentation is what irks me . I am sure there is value there but the whole thing comes across as a pointless exercise in compliance with whatever whims they have this year added onto previous requirements
- lavezzi 10y agoA lot of the additional requirements year on year are driven by mandates from the PCAOB. If the audit firms do not comply then they are hit hard during the PCAOB reviews of their audit files.
- hbharadwaj 10y agoI currently work in Tech Strategy at a Big 4 - the reason why Big 4s want to roll it back is because over the last few years, their revenue in audit is steadily decreasing. Especially with automated tools, outsourcing, RPA taking over and making a lot of the grunt work significantly cheaper. At the same time, the consulting revenues are significantly going up. SOX limits the scope of work the Big 4 can execute at firms they audit (nothing related to financially significant systems etc.). The best client relationships are with the firms the Big 4 audit! Hence, the push!
- oblio 10y agoThe good ol' "channel 1" versus "channel 2" conflict, or whatever it's called nowadays. Basically Big 4 "have to" audit but what they really want is to offer consulting services. There's a huge conflict of interest regarding these two parts and every few decades the Big 4 are forced to spin off consulting divisions. Not that stops them from trying again :)
- blawson 10y agoIsn't this why Sarbanes-Oxley was introduced to begin with? Auditors getting too cozy with the companies they are meant to be impartially auditing, because most of their revenue actually comes from consulting. The book The Number talks about this quite a bit: https://www.amazon.com/Number-Quarterly-Earnings-Corrupted-Corporate/dp/0812966252/ref=pd_lpo_sbs_14_t_1?_encoding=UTF8&psc=1&refRID=6BMATSRA0QTS7VHKT429 https://www.amazon.com/Number-Quarterly-Earnings-Corrupted-C...
- ubernewb 10y agoThis. I'm a former Big Four auditor, and I can tell you that the consulting-auditing dichotomy is very clear in the industry. Auditing is on the downswing revenue-wise, and consulting will always rake in the dough. My issue is that the consulting relationships (and the big money they bring in) will necessarily impact the independence of the auditors, which is one of the main reasons there is the whole 'Channel 1' - 'Channel 2' split in the first place, and the major reason SOx passed. The Enron debacle was almost entirely because of the fact that Arthur Andersen didn't want to lose out on the major consulting revenue they made from Enron, but were pressured to fudge audit findings or they would lose that client for everything. SOx was an absolute b*h to implement and deal with on the audit and client side, but it made perfect sense from a regulatory perspective. Still, when the clients are paying for their own audits, that's its own ethical issue. tldr; It's complicated.
- kbenson 10y agoMy first question is how much of a burden is it really? Are we hearing the squeaky wheels, or is it actually pretty bad? My second question is how much does it help. It's fine to say that it codifies practices that companies mostly do anyways (and if so, how bad can it be), but it was also a response to some troubling behavior in the market. How many problems does it prevent for the burden it exacts?
- jedberg 10y ago> My first question is how much of a burden is it really? Are we hearing the squeaky wheels, or is it actually pretty bad? It's pretty bad. It was bad enough that we had to hire multiple full time people on our side just to deal with the interactions, people with engineering backgrounds who basically just did paperwork, who could have been doing much more useful things given their knowledge and experience. > My second question is how much does it help. It's fine to say that it codifies practices that companies mostly do anyways (and if so, how bad can it be), but it was also a response to some troubling behavior in the market. How many problems does it prevent for the burden it exacts? It's important to remember that there are two aspects to SOX: Operational and financial. I don't have a lot of experience with the financial side, other than to say they have just as much overhead, but perhaps it prevented a lot of things. But from the operational side, it made us do things in bad ways so that we could show the auditors, and also slowed us down. For example, production access to financial data must be limited so that it can't be modified in production after the transaction but before it gets to the financial systems. Sounds like a good idea, but then when you have an outage, you have to scramble to find multiple people to unlock the access keys and watch over your shoulder while you make fixes on production systems. Or instead you rearchitect your entire system so that only a few machines are actually handling financial transactions and keeping the rest out of scope. Either way, it's a huge burden. Another great example is password rotation. The law demands you have a password rotation policy. It doesn't say what that policy should be. Most auditors have settled on 90 days. Most researchers have shown that forced password rotation is bad. Without SOX, I would just follow the recommendation of the people who actually used science to figure out that password managers are better than password rotation. But with SOX, I either just follow the auditor's redone checklist, or spend a whole bunch of time convincing them that my policy is better than rotation. Either way, a bunch of overhead either for me or for all my coworkers.
- lavezzi 10y agoI mean, this is hilarious if that's the approach you have been taking throughout your career but for anyone else reading this comment it's wholly inaccurate.
- jedberg 10y agoI've personally been part of it at two public companies, and my friends have been in many other public companies, and we've all had the same experience. So sure, maybe it's different elsewhere, but amongst the people I know, that's how it works.
- lavezzi 10y agoYou may have been part of it but you clearly do not have a good comprehension of it. In another comment you stated "Another great example is password rotation. The law demands you have a password rotation policy.". This is completely false, Section 404 deals with the adequacy of the company's internal control on financial reporting (ICFR), it does not contain such specific IT mandates or requirements. As you mentioned, Sarbanes-Oxley is written at a very high level but that is meant to provide flexibility for a wide range of companies and their associated IT systems. It can be implemented badly if neither party truly understand the requirements, which looks to be the case here.
- jedberg 10y ago> It can be implemented badly if neither party truly understand the requirements, which looks to be the case here. On that I totally agree with you. But my main point is that the law is so poorly written, almost no one, including most auditors, don't understand it, and you end up with a lot of "better safe than sorry". If you're someone who truly understands the law then I applaud you and I wish you were my auditor, but is seems that almost no one is as well informed as you, which is the crux of the problem.
- BenchRouter 10y agoFWIW I've been part of it at two public companies as well, and my experience nicely lines up with yours. Incredibly vague mandates that result in extremely complex rules and systems. Lots of things being marked as "financially sensitive" even though they weren't at all - because better safe than sorry. In both instances it quite literally cost the company several employees who were assigned to put the SOX systems in place, because it was so incredibly frustrating (and, well, boring), that they ended up quitting down the road and directly attributing their leaving to SOX compliance.
- arethuza 10y agoI've seen some very strange things done in the name of SOX compliance. I was involved in the potential acquisition in the UK of a subsidiary of a US public company and they used to print out their AD group memberships (as screenshots) and have someone sign (wet sign - with a pen!) the printouts every week/month. When I asked whether SOX compliance really required this they basically said they didn't really know but had to play safe as the regulations were just so vague.
- maxxxxx 10y agoReminds me a little of the medical device industry. We do a lot of things that from an engineering perspective result in worse products but since nobody understands the regulations fully we do them. Until a new guy comes in, re-reads the rules and says we can do it differently now.
- arethuza 10y agoIf you think SOX is bad try finding someone to tell you exactly what you need to do to be ITAR compliant!
- refurb 10y agoI work in the biotech industry and it's the exact same way. We have legions of lawyers who try and decipher the regulations. A great example is price reporting to the gov't. You're supposed to report your net price across all sales to CMS on a quarterly basis. Problem is, the regulations are so vague that it falls on companies as to how to interpret them. Naturally, companies err on the conservative side (at least most of them). My old company probably had 20 FTE's dedicated to this one regulation. And if you reach out to the regulatory body for clarification, that's a multi-year process. A great example is the AMP rule (average manufacturer price). I think CMS was supposed to role out the clarification back in 2012, but only finalized it last year. And there are still unanswered questions.
- supergeek133 10y agoI used to work in the ecommerce space.. along with PCI our security/compliance people made us do lots of vague things with our delivery pipeline with the broad excuse of "SOX compliance" When asked for the specific rule we had to follow, there was never any response.
- guelo 10y agoI don't know enough to be sure of cause-and-effect but there hasn't been any major accounting fraud such as Enron and Worldcom since SOX passed, so that's one point in favor of the regulations.
- clarkmoody 10y agoThe primary issue with onerous regulation is that which is unseen. How many companies and entrepreneurs choose not to act or take risk when faced with a future full of ridiculous regulations. Or perhaps the regs simply codify the business model of the larger players, keeping out smaller competitors.
- diggernet 10y agoSome years back I was looking into forming a non-profit to do some donation-funded environmental cleanup (not huge - probably on the order of a few tens of thousands of dollars a year). What I learned is that while SOX doesn't apply to non-profits, there are similar SOX-inspired rules that do. The advice from everyone I talked to at various non-profits about how to get set up: Just drop it. The regs require so much paperwork and oversight that it would easily cost 10x that much in compliance and auditing. If you aren't making a BIG non-profit, it's not worth the trouble any more, the overhead will crush you.
- Pokepokalypse 10y agoSounds A LOT like how FISMA is implemented. Only you can't find any two auditors who will agree on how to apply these overly complex set of rules.
- adrianratnapala 10y agoSOX had great intentions but was one of the most poorly implemented regulations ever. SOX was a law passed in a hurry after a big scandal. It's intention was to allow politicians to be seen to be doing something. The more painful that something is in practice, then the more they are seen to have done something. SOX as implemented is therefore working just as intended. The trouble is that the intentions were bad in the first place.