ASU 2024-03 Effective Date: 2026 Compliance Calendar for Public Companies

If you are a CFO or controller at a public company, the ASU 2024-03 effective date is closer than it looks. The standard is live for fiscal years beginning after December 15, 2026, but the two-tier annual/interim structure, the ASU 2025-01 clarification, and the data-collection work required before adoption make 2026 the year to act, not wait.

This article maps the exact compliance calendar to your fiscal year-end, explains what ASU 2025-01 actually changed, and gives you the transition decision framework the Big-4 guides bury in footnotes.

Key takeaway: For a calendar-year-end PBE, the first required ASU 2024-03 disclosures appear in the 10-K for fiscal year 2027, filed in early 2028. Interim disclosures do not kick in until Q1 2029. But retrospective adopters need 2025 comparative data now.

What Is ASU 2024-03 and Who Does It Apply To?

ASU 2024-03, codified as ASC 220-40, requires public business entities to disclose a tabular disaggregation of five natural expense categories within each relevant income statement expense caption. The FASB issued it on November 4, 2024, under the full title "Income Statement, Reporting Comprehensive Income, Expense Disaggregation Disclosures (Subtopic 220-40): Disaggregation of Income Statement Expenses" (DISE).

The standard does not change what appears on the face of the income statement. Functional line items like cost of sales and SG&A stay exactly as they are. The new requirement is footnote-only: a table that breaks those captions down by natural expense type.

The investor rationale is explicit in the FASB's own documentation: "The objective of the amendments is to provide disaggregated information about public business entity's expenses to help investors: (1) Better understand the entity's performance; (2) Better assess the entity's prospects for future cash flows; (3) Compare an entity's performance over time and with that of other entities."

Who Is a Public Business Entity for DISE Purposes?

The PBE definition under the ASC Master Glossary is broader than "SEC registrant," and this catches many companies off guard. You are in scope if you are:

• An SEC registrant (including OTC-traded entities with securities quoted on a public market)
• An entity whose financial statements must be included in another SEC registrant's filing under Reg S-X Rules 3-05 or 3-09
• A target company in a Form S-4 or proxy statement
• An IPO candidate once the registration statement is filed

Private companies, not-for-profit entities, and employee benefit plans are excluded entirely. A PE-backed company that has never touched a public market is out of scope, until it files an S-1 or gets acquired by a public company that needs its financials under Rule 3-05.

For a full breakdown of the five required expense categories and the mechanics of the tabular disclosure, see our practitioner how-to guide.

ASU 2024-03 Effective Date: The Two-Tier Structure

The standard has two separate effective dates, and conflating them is the most common mistake practitioners make.

Source: FASB ASU 2024-03 Project Page; FASB ASU 2025-01 Project Page

The gap between the two dates is intentional. The FASB gave companies an extra year to build the systems needed for quarterly reporting before requiring interim disclosures.

What ASU 2025-01 Changed (and Why It Matters for Non-Calendar-Year Filers)

Just three weeks after issuing ASU 2024-03, the FASB received constituent feedback flagging an ambiguity in the interim effective date language for non-calendar-year-end entities. On November 25, 2024, the FASB published a proposed clarification. On January 6, 2025, it finalized ASU 2025-01.

The problem: the original ASU 2024-03 language could be read as requiring interim disclosures in the first annual period beginning after December 15, 2026, not the first annual period beginning after December 15, 2027. For a June 30 fiscal year-end entity, that reading would have pulled interim requirements forward by a full year.

ASU 2025-01 confirmed the correct reading: interim requirements attach to interim periods within annual periods beginning after December 15, 2027. The FASB's own statement is unambiguous: "Public business entities are required to adopt the guidance in Update 2024-03 in annual reporting periods beginning after December 15, 2026, and interim periods within annual reporting periods beginning after December 15, 2027."

If your team is working from an analysis prepared before January 6, 2025, check whether it reflects this correction.

Effective Date Calendar by Fiscal Year-End

This is the table that no existing SERP result provides. Map your fiscal year-end to your actual compliance dates.

Source: FASB ASU 2025-01

Note the pattern for non-December fiscal year-ends: the interim effective date falls one year after the annual effective date, not two. A June 30 filer's first required interim disclosures arrive in Q1 FY2029 (the quarter ending September 30, 2028), only twelve months after the first required annual disclosures. That is a tight runway to build quarterly reporting capability after the first annual filing.

The Transition Decision: Prospective vs. Retrospective

This is a real operational decision with consequences that start now. The standard permits two transition approaches:

Prospective: Apply the new disclosures only to periods after the adoption date. No prior-period data required. Simpler operationally, but investors lose comparability.

Retrospective: Recast any or all prior periods presented. Provides comparability from day one, which investors and analysts will prefer. The catch: PwC's In Depth guidance is direct on this point: "Entities considering adopting the new standard on a retrospective basis will need to collect data for the comparative years beginning as early as 2025."

If your fiscal year ends December 31 and you plan retrospective adoption for FY2027, you need 2025 natural expense data. That data collection window is open right now. Waiting until 2027 to make this decision means the 2025 data may be gone or prohibitively expensive to reconstruct.

How to Make the Transition Call

Work through these questions in sequence:

1. Do your systems currently track the five natural expense categories at the caption level? If yes, retrospective is feasible. If no, prospective may be the only practical option unless you can reconstruct the data.
2. What do your peer companies plan to do? Investor relations teams should monitor early adopters and peer disclosures. Prospective adoption when peers go retrospective creates a comparability gap that analysts will notice.
3. Is early adoption on the table? If you adopt for FY2026 annual reports, you need the data infrastructure in place before year-end 2026. Early adoption is permitted but requires the same disclosure mechanics as mandatory adoption.
4. Can you use estimates? The standard explicitly allows entities to use accounting estimates or other methods that reasonably approximate the required amounts. This is meaningful relief for retrospective periods where exact data is unavailable, but the estimates need to be documented and defensible to your auditor.

The Five Required Expense Categories

Every relevant expense caption on the income statement must be disaggregated into these five natural categories, to the extent each is present in that caption:

1. Purchases of inventory (using either the expense-incurred or cost-incurred approach)
2. Employee compensation
3. Depreciation
4. Intangible asset amortization
5. Depreciation, depletion, and amortization (DD&A) recognized as part of oil- and gas-producing activities, or other depletion expense

A "relevant expense caption" is any line item on the face of the income statement within continuing operations that contains any of the five categories. Discontinued operations are excluded.

Beyond the five categories, the standard also requires:

• A qualitative description of amounts remaining in relevant expense captions that are not separately disaggregated
• Total selling expenses disclosed at each annual and interim period
• In annual periods only, the entity's definition of selling expenses

The selling expenses definition requirement deserves attention. This is a novel disclosure with significant judgment involved. Companies need to decide now whether they will define selling expenses narrowly (direct selling costs only) or broadly (including marketing, customer support, and related overhead), document that definition, and apply it consistently. Changing the definition later requires recasting prior periods.

For detailed guidance on chart of accounts mapping and ERP system configuration to produce these categories, see our chart of accounts mapping guide.

Scope Edge Cases: Are You In When You Think You Are Out?

Several categories of entities are in scope but do not always realize it.

Reg S-X 3-05 and 3-09 filers. If a private company is acquired and the acquirer must file its historical financial statements under Rule 3-05, those financials must comply with ASU 2024-03 if the filing occurs after the effective date. As PwC notes: "A business entity that is required to file or furnish financial statements with the SEC in accordance with Regulation S-X 3-05 or 3-09 is required to apply the new standard for the filed or furnished financial statements because such an entity is included in the ASC Master Glossary definition of a PBE."

IPO candidates. A company filing an S-1 after the effective date must include ASU 2024-03 disclosures in its registration statement financials. If you are on an IPO track targeting 2027 or 2028, build DISE compliance into the IPO readiness workstream now.

OTC-traded entities. Companies with securities quoted on an over-the-counter market are PBEs and are in scope, even without a full SEC reporting obligation.

Entities that become PBEs mid-cycle. If a private company becomes a PBE partway through a fiscal year, it applies ASU 2024-03 from the beginning of the first annual period in which it qualifies as a PBE after the effective date.

What the May 2026 FASB Roundtable Signals

The FASB held a public roundtable on DISE implementation on May 27, 2026. The meeting minutes are publicly available. This is the FASB's standard post-issuance monitoring mechanism, and the fact that it convened one specifically on DISE, with more than a year still to run before the annual effective date, signals that implementation challenges are real and the FASB is watching.

What does this mean practically? The FASB may issue additional implementation guidance, narrow-scope amendments, or practical expedients before the effective date. It is unlikely to delay the standard entirely, but targeted relief on specific application questions (purchases of inventory mechanics and the selling expenses definition are the most contested areas based on Big-4 FAQ activity) is possible.

The prudent posture: proceed with implementation planning as if the effective date is firm, but monitor the FASB project page for further activity. Do not use potential amendments as a reason to defer data infrastructure work.

2026 Readiness Checklist

As of August 2026, calendar-year-end PBEs are in the final preparation window before the January 1, 2027 annual effective date. Work through this checklist:

Scope and governance

• Confirm which entities in your group are PBEs under the ASC Master Glossary definition
• Identify any Reg S-X 3-05/3-09 subsidiaries or targets that may need DISE-compliant financials
• Assign a cross-functional owner (finance, IT, HR, operations)

Data and systems

• Map each relevant income statement expense caption to the five natural categories
• Identify data gaps: which categories are not currently tracked at the caption level in your ERP?
• Assess whether estimates or approximations will be needed and document the methodology
• Engage IT on chart of accounts changes or reporting layer configuration (see our systems guide)
• Determine whether 2025 comparative data needs to be collected now (retrospective adopters)

Policy and disclosure drafting

• Define "selling expenses" and document the definition formally
• Draft the qualitative description of residual "other items" amounts
• Decide on prospective vs. retrospective transition and document the rationale
• Prepare the SAB 74 (now SAB 74, codified under ASC 250) pre-adoption disclosure for the next 10-K or 10-Q

Audit and controls

• Brief your external auditors on the transition approach and data sources
• Assess whether new controls are needed over the tabular disclosure production process (see our controls guide)
• Confirm XBRL tagging requirements for the new footnote table with your filing agent

Interim readiness (non-December fiscal year-ends)

• Note that your interim effective date may be as early as Q1 FY2029, arriving only twelve months after your first annual filing
• Build quarterly reporting capability into the systems project, not as a phase two afterthought

Warning: PwC's guidance states that "nearly all PBEs will be required to disclose more information about income statement expenses upon adoption" and that "new system and process changes may be required as well as coordination across geographies, business segments, and multiple reporting systems." The companies that treat this as a disclosure-drafting exercise rather than a data infrastructure project are the ones that will be scrambling in early 2028.

FAQ

Does ASU 2024-03 apply to private companies? No. The standard applies only to public business entities as defined in the ASC Master Glossary. Private companies, not-for-profit entities, and employee benefit plans are excluded. However, a private company that files an S-1, gets acquired by a public company requiring Reg S-X 3-05 financials, or has securities traded on an OTC market becomes a PBE and falls in scope.

What did ASU 2025-01 change about the effective date? ASU 2025-01, issued January 6, 2025, clarified the interim effective date specifically for non-calendar-year-end entities. The original ASU 2024-03 language was ambiguous about when interim requirements attached for off-calendar filers. ASU 2025-01 confirmed that interim requirements apply to interim periods within annual periods beginning after December 15, 2027, not the first annual period beginning after December 15, 2026.

Can we early adopt ASU 2024-03? Yes. Early adoption is permitted for any period, including interim periods, for which financial statements have not yet been issued. If you adopt early for FY2026 annual reports, you must apply the full disclosure requirements for that period, including the tabular format and selling expenses disclosure.

Do we have to restate prior periods? Not necessarily. Prospective transition is permitted and requires no prior-period data. Retrospective transition, which recasts prior periods, is also permitted and provides comparability that investors will value. The choice is yours, but retrospective adopters need comparative data from as early as 2025, and that collection window is open now.

What are the five expense categories we must disaggregate? Purchases of inventory, employee compensation, depreciation, intangible asset amortization, and DD&A recognized as part of oil- and gas-producing activities or other depletion. Each must be disclosed within every relevant expense caption on the income statement that contains that category.

Is the standard likely to be delayed or amended after the May 2026 roundtable? The FASB has not signaled a delay. The May 27, 2026 roundtable was a standard post-issuance monitoring exercise. Targeted implementation guidance or narrow-scope relief on contested application questions is possible, but companies should plan for the current effective dates and treat any future relief as a bonus, not a baseline assumption.