Check out the latest edition of our “Timely Takes” Podcast featuring John’s discussion with J.T. Ho, partner at Orrick, Herrington & Sutcliffe LLP. John and J.T. are planning on J.T.’s “Fast Five” being a new monthly podcast feature, which piggybacks off of a brief monthly email that J.T. prepares for clients. I think our members will love this format since it gives a quick take on timely securities law and corporate governance hot topics. In this 9-minute podcast, John and J.T. discuss varied and timely topics, including:
– The SEC’s Cybersecurity Disclosure Rules – Recent Changes to the Delaware General Corporation Law
– Potential Advantages of Self-Reporting to the SEC
– Board Oversight of Corporate Political Statements
– Topics to Watch Over the Coming Months
If you have insights on a securities law, capital markets or corporate governance issue, trend or development that you’d like to share, we’d love to hear from you. Just shoot us an email at mervine@ccrcorp.com or john@thecorporatecounsel.net.
On September 19, at our “2nd Annual Practical ESG Conference” — which you can attend virtually as a standalone event or bundle with our PDEC Conferences and save — our very own Dave Lynn and Lawrence Heim and an amazing group of ESG practitioners from diverse backgrounds will deliver usable, practical guidance on the hottest ESG topics, in a candid and conversational format.
On September 20-21, we’ll help you prepare for the upcoming proxy season with the “2023 Proxy Disclosure Conference.” This conference is timed to give you the very latest action items that you’ll need to prepare for the flurry of year-end and proxy season activity.
On September 22, we’ll discuss all things executive compensation at the “20th Annual Executive Compensation Conference.” A wide range of panelists will address hot topics in executive compensation today — from ESG metrics to clawbacks.
Here’s the full agenda – and all of our experienced speakers. It is not too late to register! You can sign up online, by emailing sales@ccrcorp.com, or by calling 1-800-737-1271. You can still bundle the Conferences together to get a discounted rate.
If you have already signed up to attend our Conferences next week, please be on the lookout for an email from info@ccrcorp.com with instructions for logging on to the Conference platform.
Next week, you will receive additional attendee communications with your unique direct link to access the Conferences for which you have registered. We will be sending the direct access link the day before the applicable event. So, for the “2nd Annual Practical ESG Conference,” attendees will receive their direct access link on Monday, September 18th, and attendees will receive the direct access link for the “Proxy Disclosure & 20th Annual Executive Compensation Conferences” on Tuesday, September 19th.
If you have friends who aren’t already members but would appreciate our curated content — including checklists, handbooks, filtered content libraries/practice areas, quick-take podcasts, timely webcasts & transcripts, benchmarking surveys, blogs on key updates, and our community Q&A forums — we are offering a referral program that gets you 15% off any new CCRcorp product or membership and your friend 15% off their first CCRcorp purchase.
Since they’re right around the corner, keep in mind that you can use this promotional discount on our “Proxy Disclosure & 20th Annual Executive Compensation Conferences” and “2nd Annual Practical ESG Conference.” With potential implications of the SEC’s ambitious regulatory agenda continuing to loom large in the minds of public companies & their advisors, you can’t afford to miss them this year! Do yourself (and your friends) a favor and take advantage of this offer! Email sales@ccrcorp.com today – or call 1-800-737-1271.
We got word last week that NYSE sent an email blast to listed issuers regarding the new clawbacks listing rules. After reminding companies that issuers must adopt a Dodd-Frank clawback policy no later than December 1st, NYSE noted that it is also requiring each listed issuer to confirm via Listing Manager either that it adopted a policy by that date or that it is relying on an applicable exemption. NYSE plans to require such confirmation for initial listing applications as well for companies applying to list their securities on or after October 2nd. The email noted a subsequent communication with more details would be sent in the fourth quarter.
On a related note, at the “Dialogue with the Director” session on Friday at the ABA’s Business Law Section Fall Meeting, Corp Fin Director Erik Gerding was asked who should field interpretive questions regarding Dodd-Frank clawback requirements — the SEC or the stock exchanges. While “both” may not be the answer we wanted to hear, Erik’s suggestion — that interpretive questions first be directed to the relevant stock exchange and then its response be conveyed to the Commission — makes a lot of sense.
Also during the “Dialogue with the Director” session on Friday at the ABA’s Business Law Section Fall Meeting, Jay Knight, Chair of the Federal Regulation of Securities Committee, asked Corp Fin Director Erik Gerding about the SEC’s current areas of focus. While Erik noted that his discussion was not exhaustive, one of the topics he highlighted was disclosures by bank issuers, stating that the SEC was looking at the following areas in particular:
– Liquidity disclosures under Item 303 of Regulation S-K, including liquidity risks, available sources, key provisions or parameters of those sources and actions taken to ensure liquidity
– Interest rate risk, including whether interest rate sensitivity disclosures under Item 305 of Regulation S-K would benefit from additional explanation of the key assumptions underlying that disclosure
The WSJ previewed these topics in June, noting that this was an area of focus for SEC comments on registration statements filed by regional banks after the bank failures we saw this spring.
This summer, I blogged about FASB’s Exposure Draft to solicit public comment on proposed changes to ASU Topic 740: Income Taxes, which was FASB’s third attempt at tackling this topic. As reported in the WSJ, in late August, FASB unanimously approved the update to require “public and private companies to break out the income taxes paid to authorities at the federal, state and foreign levels for the full year in their annual financial reports.” Here’s more from the article giving a high-level summary of the new requirements:
If a particular jurisdiction represented more than 5% of these taxes for the year, businesses will have to identify that jurisdiction and specify the amount in their annual reports.
Public companies will need to share more detail on how they reconcile their domestic statutory rate with the rate they actually paid. The actual rate is usually lower because it includes the effects of tax credits and other breaks.
These companies will also have to present a standardized table showing how categories such as state and local income taxes, foreign taxes, tax credits and the enactment of new tax laws contribute to the difference between the two rates, the statutory rate and the actual one, by providing the percentages and dollar amounts.
This article from CFO Dive details the compliance dates as follows:
The new rules will be effective for public companies for fiscal years beginning after Dec. 15, 2024, and for private companies and other companies beginning after Dec. 15, 2025.
I confess that my eyes glaze over when I see anything relating to XBRL, and I suspect I’m not the only one who suffers from this weakness. Apparently, the Corp Fin Staff has noticed that “structured data” is getting short shrift, because they posted a wake-up call yesterday in the form of a sample comment letter.
Corp Fin has been providing guidance in the format of “Dear Issuer” letters on a somewhat regular basis since at least 2021. The letters tend to be issued when the Staff notices an emerging disclosure or market-related issue that is affecting a lot of companies. Topics have included market volatility, China-based disclosure requirements, and crypto fallout. But for this instance of sample comments, with XBRL being required since 2009 and Inline XBRL since 2018, you might wonder, “Why now?” The Staff gives a couple of reasons:
1. Comments on the pay versus performance rule provided increased evidence that this data format is useful to investors.
2. The Financial Data Transparency Act (FDTA) became law at the end of last year and requires the SEC to establish a program to improve the quality of the corporate financial data filed or furnished by companies under the ’33 and ’34 Acts.
In addition, new XBRL requirements have accompanied several recent SEC rulemakings (clawbacks, pay vs. performance, repurchases, insider trading), so there actually are new practices to watch out for right now. The sample comment letter flags these issues:
1. Item 405 of Regulation S-T: Your filing does not include the required Inline XBRL presentation in accordance with Item 405 of Regulation S-T. Please file an amendment to the filing to include the required Inline XBRL presentation.
2. Cover Page: The common shares outstanding reported on the cover page and on your balance sheet are tagged with materially different values. It appears that you present the same data using different scales (presenting the whole amount in one instance and the same amount in thousands in the second). Please confirm that you will present the information consistently in future filings.
3. Pay versus Performance: Disclosure under Regulation S-K Item 402(v) must be in Inline XBRL, in accordance with Item 405 of Regulation S-T and the EDGAR Filer Manual. Please ensure that you have provided the appropriate Inline XBRL tagging for all the required Item 402(v) data points.
4. Pay versus Performance: Refer to the [relationship disclosures] graph. Although it is permissible to combine one or more sets of relationship disclosures under Regulation S-K Item 402(v)(5) into one graph, table, or other format, note that you must still provide separate XBRL tags for each required item. Please ensure that you have provided the appropriate Inline XBRL tagging for all the required Item 402(v) data points.
5. Financial Statements and Supplementary Data: You have used different XBRL elements to tag the same reported line item on the income statement from period to period. Please provide us your analysis as to how you concluded that the results reported necessitated the change in the element. Alternatively, if you conclude that the change from period to period was not necessary to communicate a change in the nature of the line item, confirm that you will ensure that your choice remains consistent for line items from period to period.
6. Financial Statements and Supplementary Data: We note that instead of using an XBRL element consistent with current U.S. GAAP in your income statement, you instead used a custom tag. Custom tags are to be used by filers when an appropriate tag does not exist in the standard taxonomy. See Item 405(c)(1)(iii)(B) of Regulation S-T. Please tell us why the current U.S. GAAP tag is not applicable, or alternatively revise your disclosure, beginning with your next filing, to correctly tag this disclosure.
Yesterday’s sample comment letter says that more investors are using XBRL data, but they aren’t the only ones: Corp Fin is also putting this info to work. In the SEC’s most recent “Semi-Annual Report to Congress on Machine Readable Data for Corporate Disclosures” – which John flagged in July – the Staff gave a heads up that they had been issuing comment letters about tagging requirements. In addition, the report says that Corp Fin is using the data in these ways:
– To help identify issuers that are subject to the disclosure and submission requirements of, and potentially subject to a trading prohibition under, the Holding Foreign Companies Accountable Act (Commission-Identified Issuers). Specifically, the staff uses data in Forms 10-K, 20-F and 40-F identifying the auditor (or auditors) who provided opinions related to the financial statements presented in the registrant’s annual report, the location where the auditor’s report has been issued, and the Public Company Accounting Oversight Board (PCAOB) ID Number(s) of the audit firm(s) or branch(es) providing the opinion(s).
– To identify, count, sort, compare, and analyze registrants and their disclosures (e.g., to identify more readily and accurately issuers that are listed on a specific exchange or that have identified themselves as well-known seasoned issuers), based on several items of machine-readable data that appear on the cover pages of registrants’ annual reports (Forms 10-K, 20-F, and 40-F).
– To make preliminary assessments of compliance with the Commission’s recently adopted pay-versus performance disclosure requirements.
With XBRL creeping in to proxy statements, will it also come for ESG? Only time will tell.
I have to say that I never thought I would write three blogs in one day on the topic of XBRL, but if the Staff thinks it is important, I will do my part to get on board. And here is something that truly caught my eye from the SEC’s 2023 Semi-Annual Report to Congress on structured data disclosures:
Enforcement utilized risk-based data analytics to uncover potential accounting and disclosure irregularities caused by, among other things, earnings management practices. Machine-readable data enabled Enforcement staff to review the financial data of thousands of public issuers in order to detect indicia of earnings management or other types of financial misconduct. The initiative resulted in charges against six public companies and several related individuals for violations of the federal securities laws for engaging in certain practices that gave the appearance of meeting or exceeding consensus earnings-per-share (EPS) estimates.
I blogged about the latest of those cases back in February – and I pointed out that the SEC’s data analytics tools are now sensitive enough to flag potential “earnings management” situations even when the adjusted dollar amounts are small. That’s because of XBRL! Now that the SEC has a solid dataset in its toolbox, it is becoming easier for the Enforcement Division to detect and pursue accounting issues.
