SEC charges director with proxy violation for failing to disclose personal relationship bearing on independence
Last week, the SEC announced settled charges against James R. Craigie, a former CEO, Chair and board member of Church & Dwight Co. Inc., an NYSE-listed “manufacturer of consumer-packaged goods,” for “violating proxy disclosure rules by standing for election as an independent director” without advising the board that maybe he really wasn’t quite so independent after all. This omission, the SEC alleged, caused the company’s proxy statements “to contain materially misleading statements.” Maybe you guessed that we’re not talking here about any of the NYSE-enumerated relationships that vitiate independence? No, we’re talking about something closer to the concept of “social independence”—something more amorphous than conventional, stock-exchange-defined independence—that some suggest can be even more compromising at times than the conventional variety. Craigie was alleged to have a “close personal friendship with a high-ranking Church & Dwight executive,” including paying more than $100,000 for the executive and his spouse to join Craigie and his spouse on “six trips that spanned eight countries on five continents.” Because Craigie never disclosed the relationship to the board and encouraged the executive to do the same, the SEC charged, the board was not aware of the relationship and the company’s proxy statements characterized Craigie incorrectly as an independent director. According to the Associate Director of the SEC’s Division of Enforcement, “[s]hareholders expect independent directors to exercise autonomous judgment in their decision making, free from undisclosed conflicts….By concealing his relationship with a company executive, Mr. Craigie undermined the board’s director independence process and compromised the company’s disclosures.” Craigie agreed to a five-year officer-and-director bar and to pay a civil penalty of $175,000. The case raises the thorny question of where to draw the line on personal relationships. Is an occasional dinner acceptable? If so, what about a weekend trip? A vacation trip? How many trips is too many? Just how thick do the personal connections have to be to taint independence? Caution seems to be the prescription here.
Last term SCOTUS gave the administrative state quite a thumping. Does it still have the urge to curb? [Updated 10/21]
If you thought that SCOTUS’ decision in Loper Bright last term tolling the bell for the 70-year old Chevron doctrine was the end of SCOTUS’ drubbing of the administrative state, look again—you may well be sorely mistaken. (See this PubCo post.) You might remember that, at a recent Ninth Circuit judicial conference, Justice Elena Kagan, expanding on her dissent in Loper Bright in response to a question, suggested that one reason the Court abandoned stare decisis in the case was plain hubris: in her view, the Court just believed that there was too much agency regulation and thought that the courts needed to step in. (See the Sidebar in this PubCo post.) And perhaps that conclusion didn’t require a giant leap. As far back as 2013 in his dissent in City of Arlington v. FCC (2013), Chief Justice Roberts worried that “the danger posed by the growing power of the administrative state cannot be dismissed.” Is there any reason to think that the urge to curb the administrative state has suddenly abated? Or will we perhaps see a temporary pause while agencies and court watchers catch their breath? As it turns out, there certainly could be opportunities for SCOTUS to continue the onslaught this term. The nondelegation doctrine—which SCOTUS studiously avoided addressing in Jarkesy v. SEC, its looming presence in the lower court decision notwithstanding—has once again reared its head, this time in Consumers’ Research v. FCC out of the Fifth Circuit. A petition for cert has just been filed in that case. And the concept of agency independence as established in a 1935 case, Humphrey’s Executor v. United States, may also be on the chopping block, as SCOTUS considers whether to take up the petition for cert in a Fifth Circuit decision, Consumers’ Research v. Consumer Product Safety Commission, in which the panel practically begged SCOTUS to review the case.
SEC brings securities fraud charges against Cassava Sciences
The SEC announced last week that it had filed a complaint against Cassava Sciences, Inc., a “pharmaceutical company with one primary drug candidate, PTI-125, a potential therapeutic for the treatment of Alzheimer’s disease,” for misleading statements about the results of a Phase 2 clinical trial for the potential therapeutic. Also charged in the complaint were the company’s founder and former CEO and its former Senior Vice President of Neuroscience. The complaint highlights and analyzes a number of misleading statements and omissions—an analysis that could be instructive for companies reporting on clinical trial results. In a related Order, the SEC also charged an associate medical professor at the CUNY, who was a consultant and the co-developer of the therapeutic, with manipulating the reported clinical trial results. The company agreed to pay a civil penalty of $40 million. The former CEO and former Senior VP agreed to pay civil penalties of $175,000 and $85,000, respectively, and to officer-and-director bars of three and five years. The consultant agreed to pay a civil penalty of $50,000. They were all charged with violating the antifraud provisions of the federal securities laws; the company was also charged with violating the reporting provisions. It’s been widely reported that, after the announcement of the settlement, the stock price fell by almost 11%. PTI-125 is now reported to be in Phase 3 clinical trials.
SEC Enforcement sweep picks up multiple companies and insiders with late filings under Section 16 and 13(d), (g) and (f) [RESEND]
[We are resending this post from Friday because, for reasons well beyond my technical capacity, it was apparently not distributed to all subscribers. Hopefully, everyone that is supposed to receive it will receive it this time.]
Can we call it a year-end tradition yet? It’s almost the end of the SEC’s fiscal year, and, as it did last year around this time, the SEC has just announced a big Enforcement sweep of multiple companies and some individuals—23 in total—for failing to timely file Section 16(a) short-swing trading reports (Forms 3, 4 and 5) and Schedules 13D and G (reports by beneficial owners of more than 5%) on a timely basis. Two public companies were charged with failing to make filings on behalf of insiders after having volunteered to do so, and then failing to report the delinquencies in their own filings, as required by Reg S-K Item 405. Surprisingly, the sweep also captured a public company that was charged with failure to timely file Forms 13F—reports that institutional investment managers are required to file regarding certain large securities holdings. The SEC used data analytics to identify those charged in the sweep. The penalties aggregated over $3.8 million and ranged from $10,000 to $750,000. According to the Associate Regional Director of the SEC’s Division of Enforcement, “[t]o make informed investment decisions, shareholders rely on, among other things, timely reports about insider holdings and transactions and changes in potential controlling interests….Today’s actions are a reminder to large investors that they must commit necessary resources to ensure these reports are filed on time.” It appears that the SEC is continuing to send messages that late filings are not ok…and lots of late filings are really not ok. It’s also clear that the SEC views companies that do volunteer to make filings on behalf of their insiders—a common practice—and that don’t follow through to be potentially contributing to their insiders’ filing failures; the SEC will hold the companies responsible if the insiders’ filings are not timely.
SEC adopts EDGAR Next
In September last year, the SEC proposed changes to the EDGAR system designed primarily to enhance EDGAR security, specifically related to EDGAR filer access and account management. (See this PubCo post.) While the SEC has updated EDGAR several times, it’s been over ten years since the SEC updated EDGAR login, password and other account access protocols in any significant way. On Friday, the SEC adopted the proposal with some changes. As summarized in the press release, “[t]he amendments require EDGAR filers to authorize identified individuals who will be responsible for managing their accounts, and individuals acting on behalf of EDGAR filers will need to present individual account credentials obtained from Login.gov to access those EDGAR accounts and make filings. Form ID, the application for access to EDGAR, will be modernized to make the form more user-friendly.” Filers will also be able to use optional Application Programming Interfaces (APIs), described as “a machine-to-machine method of making submissions, retrieving information, and performing account management tasks that will improve the efficiency and accuracy of filers’ interactions with EDGAR.” According to SEC Chair Gary Gensler, “[t]he public and the SEC long have benefited from the EDGAR electronic filing system….Today’s amendments are an important next step for EDGAR account access protocols.” In his statement, he added that, “[u]nder previous requirements, registrants had one login per company. This is like having a family passing around one shared login and password for a movie streaming app. You know where that can lead. That’s simply not the most secure system—for filers and the Commission alike—when it comes to information relating to financial disclosure. By contrast, today’s amendments further secure login protocols by requiring every person filing something into EDGAR to login with individual credentials and to use multi-factor authentication.” The rule and form amendments will become effective March 24, 2025. On the same date, the new dashboard will go live, and compliance with the amended Form ID requirements will be required. The compliance date for all other rule and form amendments is September 15, 2025. I know you’ll be excited to study the new EDGAR filer manual and here’s a blackline copy to help with that undertaking. Will the new system put the kibosh on fake SEC Form 4s, fake Forms 8-K, fake Schedules 13D, fake SEC correspondence and other fake SEC filings?
SEC Enforcement sweep picks up multiple companies and insiders with late filings under Section 16 and 13(d), (g) and (f)
Can we call it a year-end tradition yet? It’s almost the end of the SEC’s fiscal year, and, as it did last year around this time, the SEC has just announced a big Enforcement sweep of multiple companies and some individuals—23 in total—for failing to timely file Section 16(a) short-swing trading reports (Forms 3, 4 and 5) and Schedules 13D and G (reports by beneficial owners of more than 5%) on a timely basis. Two public companies were charged with failing to make filings on behalf of insiders after having volunteered to do so, and then failing to report the delinquencies in their own filings, as required by Reg S-K Item 405. Surprisingly, the sweep also captured a public company that was charged with failure to timely file Forms 13F—reports that institutional investment managers are required to file regarding certain large securities holdings. The SEC used data analytics to identify those charged in the sweep. The penalties aggregated over $3.8 million and ranged from $10,000 to $750,000. According to the Associate Regional Director of the SEC’s Division of Enforcement, “[t]o make informed investment decisions, shareholders rely on, among other things, timely reports about insider holdings and transactions and changes in potential controlling interests….Today’s actions are a reminder to large investors that they must commit necessary resources to ensure these reports are filed on time.” It appears that the SEC is continuing to send messages that late filings are not ok…and lots of late filings are really not ok. It’s also clear that the SEC views companies that do volunteer to make filings on behalf of their insiders—a common practice—and that don’t follow through to be potentially contributing to their insiders’ filing failures; the SEC will hold the companies responsible if the insiders’ filings are not timely.
NYSE withdraws proposal to extend time period for completion of de-SPAC transaction
In April, the NYSE proposed a rule change that would have amended Section 102.06 of the Listed Company Manual to allow a SPAC to “remain listed until forty-two months from its original listing date if it has entered into a definitive agreement with respect to a business combination within three years of listing.” (See this PubCo post.) The current rule imposes a three-year deadline for a SPAC to complete its de-SPAC merger. At the end of last week, the SEC posted a notice that the NYSE had withdrawn the proposal to extend the period that the SPAC can remain listed if it has signed a definitive de-SPAC merger agreement. Why?
SEC’s Investor Advisory Committee discusses tracing in §11 litigation and shareholder proposals—will they recommend SEC action?
Last week, at the SEC’s Investor Advisory Committee meeting, the Committee discussed two topics described as “pain points” for investors: tracing in §11 litigation and shareholder proposals. In the discussion of §11 and tracing issues, the presenting panel made a strong pitch for SEC intervention to facilitate tracing and restore §11 liability following Slack Technologies v. Pirani. The panel advocated that the Committee make recommendations to the SEC to solve this problem. With regard to shareholder proposals, the Committee considered whether the current regulatory framework appropriately protected investors’ ability to submit shareholder proposals or did it result in an overload of shareholder proposals? Was Exxon v. Arjuna a reflection of exasperation experienced by many companies? No clear consensus view emerged other than the desire for a balanced approach and a stable set of rules. Recommendations from SEC advisory committees often hold some sway with the staff and the commissioners, so it’s worth paying attention to the outcome here.
PCAOB spotlight on auditor independence outlines considerations for audit committees
The PCAOB has released a new Spotlight on auditor independence, which provides observations from PCAOB inspections regarding independence issues and identifies considerations for both auditors and audit committees. Auditor independence has, for years, been a major focus of the SEC’s Office of the Chief Accountant, and current Chief Accountant Paul Munter has addressed the issue in a number of statements, characterizing auditor independence as a concept that is “foundational to the credibility of the financial statements.” (See, for example, this PubCo post and this PubCo post.) But auditor independence is not just an issue for auditors. It’s important for companies to keep in mind that violations of the auditor independence rules can have serious consequences not only for the audit firm, but also for the company as the audit client. For example, an independence violation may cause the auditor to withdraw the firm’s audit report, requiring the audit client to have a re-audit by another audit firm. What’s more, auditor independence violations can sometimes even result in charges against the company; for example, Lordstown Motors was charged with several Exchange Act violations in connection with misrepresentations and failures to include financial statements audited by independent auditors required in current and periodic reports. Munter has long recognized that the responsibility to monitor independence is a shared one: “[w]hile sourcing a high quality independent auditor is a key responsibility of the audit committee, compliance with auditor independence rules is a shared responsibility of the issuer, its audit committee, and the auditor.” As a result, in most cases, inquiry into the topic of auditor independence should certainly be a recurring menu item on the audit committee’s plate. Fortunately, the Spotlight offers advice, not only for auditors, but fortunately, also for audit committee members.
You must be logged in to post a comment.