TheCorporateCounsel.net

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.

The Staff cautions that this is not an exhaustive list of XBRL issues that companies should consider. Check out our “XBRL” Practice Area and the SEC’s Office of Structured Disclosure for more guidance on this topic. And here’s a handy “form check” resource!

– Liz Dunshee