Under U.S. GAAP, every entity must disclose information about accounting standards that have been issued but are not yet effective, and SEC registrants face a more detailed version of that same duty. The new accounting pronouncement disclosure requirements come from two places: ASC 250 in the FASB codification, which applies to all GAAP preparers, and SAB Topic 11.M (the codified form of SAB No. 74), which sets the SEC staff’s expectations for public filers.1U.S. Securities and Exchange Commission. Codification of Staff Accounting Bulletins – Topic 11 Miscellaneous Disclosure The purpose is straightforward: tell readers a standard is coming and help them judge how much it will move the numbers.
Who Has to Disclose, and When It Starts
Any entity preparing GAAP financial statements has to evaluate newly issued Accounting Standards Updates for disclosure. The trigger is simple. The FASB has finalized a standard, that standard is not yet effective for your reporting period, and it could have a material effect on your financial statements. If those conditions are met, you need to say something about it.
The obligation begins in the first reporting period after the FASB issues the standard. For a public company on a quarterly reporting cycle, that could mean addressing a new ASU in a 10-Q filed only weeks after the standard’s release. Private companies carry the same conceptual requirement, though their effective dates typically run a year behind those for public business entities, which gives them more time before the pressure to quantify sharpens.
If management concludes a standard will have no material effect, a brief statement to that effect is enough, but the conclusion has to be supported by documented analysis across recognition, measurement, presentation, and disclosure. Auditors will test the work behind the assertion, and the SEC staff may ask about it in a comment letter.
What SEC Registrants Must Cover for Each Standard
SAB Topic 11.M sets out the disclosure elements a registrant should address for each material standard not yet adopted. These disclosures usually appear in a footnote titled “Recent Accounting Pronouncements” or something similar.
- A brief factual description of the new standard, the date adoption is required, and the date the company plans to adopt if earlier than required.
- The transition methods the standard permits and which method the company expects to use, if that decision has been made. Common options include full retrospective application, which restates prior-period comparatives, and modified retrospective application, which records the cumulative adjustment to retained earnings at the adoption date.
- The impact adoption is expected to have on the financial statements. If the impact is not yet known or reasonably estimable, the company must say so explicitly.
- Other significant consequences beyond the financial statements themselves, such as potential technical violations of debt covenants or planned changes in business practices driven by the new standard.
These elements come directly from the SEC staff’s interpretive guidance.1U.S. Securities and Exchange Commission. Codification of Staff Accounting Bulletins – Topic 11 Miscellaneous Disclosure The guidance recognizes that registrants can only disclose what they know, but it expects the depth of that disclosure to grow as the effective date gets closer.
Judging Materiality Before You Write Anything
The threshold question for every new standard is whether it will be material. Get this wrong in either direction and you have a problem: overstate the impact and you alarm investors, dismiss it too quickly and you invite scrutiny.
A percentage rule of thumb is not the answer. The SEC addressed this in SAB No. 99, stating that “exclusive reliance on this or any percentage or numerical threshold has no basis in the accounting literature or the law.”2Securities and Exchange Commission. Staff Accounting Bulletin No. 99 – Materiality A 5% benchmark can be a starting point, but the analysis has to account for qualitative factors as well: whether the change masks an earnings trend, affects loan covenant compliance, triggers regulatory implications, or concerns a segment that carries disproportionate weight in how investors read the company. A numerically small adjustment can still be material if it changes how readers understand the business.
Disclosure Depth Should Rise Each Period
The SEC staff expects disclosure quality to improve with each successive reporting period. Saying “we are currently evaluating the impact” in the first filing after issuance is fine. Saying the same thing two years later, with the effective date one quarter away, is not.
Early Stage
When a standard is first issued, the disclosure is largely qualitative. Management identifies the ASU, describes what it changes, states the effective date, and explains that an assessment is underway. Identifying which transactions and account balances the standard touches matters more here than producing dollar estimates.
Mid Stage
As the implementation project matures, the disclosure should reflect that progress. Name the transition method the company expects to elect. Describe the status of the effort in concrete terms: contract review completed, system configuration in progress, parallel testing planned. Flag significant hurdles that remain. If preliminary estimates exist, even as ranges, put them in.
Final Period Before Adoption
In the last reporting period before adoption, the SEC expects a refined quantitative estimate tied to specific line items: the expected increase in total assets, the adjustment to retained earnings, or the change in reported expense. Vague qualitative language this late is a red flag and signals that the company may not be ready.
The Parallel MD&A Obligation
SEC registrants have a dual disclosure duty. Beyond the footnotes, Regulation S-K Item 303 requires the Management’s Discussion and Analysis section to address known trends, events, and uncertainties that are reasonably likely to affect future financial condition or results.3eCFR. 17 CFR 229.303 – (Item 303) Managements Discussion and Analysis A material new standard that will reshape revenue, leases, or credit loss reporting fits squarely inside that requirement.
The two pieces serve different jobs. Footnotes cover the mechanics: what the standard changes, which transition method you will use, and the estimated adjustment to specific line items. MD&A covers business implications: how the change may affect reported profitability trends, whether it could tighten or loosen borrowing capacity, and what operational investments the company is making to get ready. A company adopting a standard that meaningfully increases reported liabilities, for instance, should discuss in MD&A whether that affects debt covenant compliance or borrowing costs.
What SEC Comment Letters Flag Most Often
The SEC staff reviews filings and issues comment letters when disclosures fall short. The recurring deficiencies related to SAB Topic 11.M cluster around a few themes.
- Failing to quantify when you can. If a CFO discussed specific numbers at an investor conference, the same information needs to appear in the 10-K. The staff has cited cases where quantitative details shared publicly could not be found in the annual filing.
- Boilerplate “evaluating the impact” language. Stating that adoption will be material without any quantitative estimate or meaningful qualitative context draws a comment. The staff wants either numbers or a substantive explanation of why numbers are not yet available.
- Missing implementation status. Omitting any description of where the company stands in its implementation project is a separate deficiency. The staff expects disclosure of process status and the significant matters still to be addressed.
- No policy comparison. When quantitative impact is not yet available, SEC guidance directs registrants to disclose the accounting policies they expect to adopt under the new standard and how those differ from current policies. Many companies skip this step.
A comment letter is not itself an enforcement action, but it requires a response and often a commitment to revise future filings. Repeated failures can escalate.
Operational Readiness Belongs in the Disclosure
Adopting a major accounting standard is not only an accounting exercise. It often requires changes to internal controls over financial reporting, IT systems, data collection processes, and staff training. Those operational dimensions are part of what the disclosure should convey.
New estimation models need documented assumptions and review procedures. New data feeds need reconciliation controls. If a standard introduces judgment-heavy areas, the audit committee should be briefed on the control design well before the adoption date. Disclosing the status of these control changes helps readers judge whether the company is genuinely prepared or is meeting the deadline on paper.
Early Adoption
Most ASUs permit early adoption, and stating whether the company plans to adopt early is part of the required content under SAB Topic 11.M. Terms vary by standard. Some allow early adoption as of any interim period, others require adoption at the start of an annual period, and a few prohibit it entirely. ASU 2023-06, for example, prohibits early adoption for SEC filers because its effective dates are tied to the SEC’s own regulatory timeline.4Financial Accounting Standards Board. Effective Dates When a company elects early adoption, the disclosure should explain the rationale and present the transition effects in the period of adoption.
Practices That Keep the Disclosure Out of Trouble
The biggest mistake companies make is treating this disclosure as a once-a-year compliance chore that gets refreshed by copying the prior period’s language. SEC comment letters target exactly that behavior. A few habits separate companies that handle this well from those that draw scrutiny.
Assign ownership early. Someone on the accounting team should be tracking new ASUs as they are issued and updating the assessment at least quarterly. Waiting until the annual audit to think about new pronouncements is how stale boilerplate ends up in filings.
Coordinate footnotes with MD&A. The teams drafting each sometimes work in isolation, producing disclosures inconsistent in tone or specificity. If the footnote says the impact is expected to be material, the MD&A should address the business implications. If specific numbers were shared with investors, those numbers need to appear in both places.
Document the materiality assessment even when the conclusion is that a standard is not material. Auditors will test the conclusion, and the SEC may ask about it. A short memo explaining why the standard does not apply to the company’s transactions, or why its effect falls below quantitative and qualitative thresholds, is far easier to produce contemporaneously than to reconstruct later.