Gana Misra
By Gana Misra•CEO, Finrep
Mon Oct 12 2026

ASU 2024-03 Materiality and Disaggregation Judgment: A CFO's Decision Framework

Share
ASU 2024-03 Materiality and Disaggregation Judgment: A CFO's Decision Framework

ASU 2024-03 Materiality and Disaggregation Judgment: A CFO's Decision Framework

Every top-ranking article on ASU 2024-03 tells you what the standard requires. None of them tell you how to make the hard calls it leaves entirely to you. This guide fills that gap.

FASB issued ASU 2024-03 on November 4, 2024, adding Subtopic 220-40 to require public business entities to disaggregate specified expense categories in tabular footnote disclosures. The standard is deliberately principle-based. That means no bright-line materiality thresholds, no prescribed definition of "selling expenses," and no safe harbor for your estimation methodology. The judgment is yours, and it goes on the record in your 10-K.

If you need a grounding in what DISE requires before working through the judgment layer, start with DISE Disclosure Explained. For industry-specific application, see the ASU 2024-03 Industry Application walkthrough. This article focuses on the six judgment decisions your controller and CFO must make, and how to make them defensibly.

Key takeaway: FASB held a public post-issuance roundtable on May 27, 2026, nearly 18 months after the ASU was issued, confirming that significant implementation questions remain unresolved. Your SAB 74 disclosure obligation, however, is already live.

Who Is In Scope for ASU 2024-03 Disaggregation Requirements?

ASU 2024-03 applies to all public business entities (PBEs). Private companies, not-for-profit entities, and employee benefit plans are exempt. But the scope edges are where finance teams get tripped up.

The following entity types are explicitly out of scope, per Deloitte's FAQ:

  • Entities with only debt securities trading publicly (conduit bond obligors)
  • Broker-dealers under ASC 940
  • Investment companies under ASC 946
  • Registered insurance separate accounts under ASC 944
  • Companies in the process of going public via IPO
  • Companies whose financials appear in another entity's SEC filing under Reg S-X Rules 3-05, 3-09, or 3-14
  • SPAC targets in a Form S-4 or proxy statement

The M&A implication is real: if your subsidiary's standalone financials are filed under Rule 3-05 in an acquirer's registration statement, those financials are exempt. But once the transaction closes and the entity becomes a consolidated PBE filer, the clock starts. Build that into your deal integration checklist.

For the effective date calendar, see the ASU 2024-03 effective date compliance guide.

Judgment Call 1: Which Expense Captions Are "Relevant"?

A relevant expense caption is any line item on the face of the income statement, within continuing operations, that contains at least one of the five mandated categories. The five categories are: (1) purchases of inventory, (2) employee compensation, (3) depreciation, (4) intangible asset amortization, and (5) DD&A from oil-and-gas or other depletion activities.

The catch: there is no explicit materiality threshold in the standard. If your SG&A line contains even a small amount of depreciation, it is technically a relevant expense caption subject to full disaggregation.

Here is the practical decision process:

  1. Pull every expense line item presented on the face of your income statement within continuing operations.
  2. For each line, ask: does it contain any of the five categories, even partially?
  3. If yes, it is a relevant expense caption and must be disaggregated in the tabular footnote.
  4. Apply the standard's general materiality principle: immaterial amounts do not require disaggregation. But document why an amount is immaterial, because your auditor will ask.

The edge case that trips teams up: a single combined "operating expenses" line. If that line contains employee compensation and depreciation, the entire caption is relevant. Companies with highly aggregated income statement presentations may find they have fewer relevant captions than expected, but each one requires more granular disclosure.

Key takeaway: The "relevant expense caption" determination is your first audit exposure point. Document the analysis for every income statement line item, not just the obvious ones.

Judgment Call 2: Can You Use Estimates, and What Makes One Defensible?

Yes, estimates are explicitly permitted. The FASB's Basis for Conclusions states explicitly that "the FASB did not intend to exclude all expense amounts that require estimates," a point confirmed by PwC's Financial Statement Presentation guide. The standard allows "accounting estimates or other methods that reasonably approximate the required disclosure amounts."

What makes an estimation methodology defensible in practice:

  • Consistency: Apply the same methodology across all periods presented. Changing your allocation approach mid-stream triggers the recast requirement (see Judgment Call 5).
  • Documentation: Write down the methodology before you apply it, not after. Your auditor will want to see the rationale, not a post-hoc reconstruction.
  • Reasonableness: The estimate must "reasonably approximate" the actual amount. A headcount-based allocation of shared employee compensation is generally supportable. An allocation based on revenue for a cost that has no logical revenue relationship is harder to defend.
  • Auditability: The inputs to your estimate must be traceable to underlying records. If your GL does not currently tag depreciation by income statement caption, you need either a system change or a documented allocation methodology that your auditor can test.

The data gap here is significant. Many companies do not currently capture employee compensation or depreciation at the income-statement-caption level in their ERP systems. The estimation question and the systems question are the same question. For a deeper look at chart-of-accounts mapping, see the ASU 2024-03 chart of accounts mapping guide.

Judgment Call 3: How Do You Define "Selling Expenses"?

This is the highest-stakes judgment in the standard, and FASB provides no definition. The ASU requires entities to disclose total selling expenses in every interim and annual period, and to disclose their own definition of selling expenses in annual periods. The definition is entirely up to you.

The risks this creates:

RiskWhy It Matters
ComparabilityTwo companies in the same industry may define selling expenses differently, making analyst comparisons unreliable
Audit scrutinyYour auditor must evaluate whether your definition is consistently applied and appropriately disclosed
Investor relationsAnalysts will ask why your selling expenses ratio differs from peers, especially in year one
Recast obligationIf you change the definition later, you must recast prior periods unless impracticable

Practical guidance for setting your definition:

  1. Start with your existing internal definition. Many companies already segment selling costs from G&A internally. Use that as your baseline.
  2. Survey peer disclosures. As early adopters file their first DISE disclosures, their definitions will become public record. Monitor them before you finalize yours.
  3. Align with your segment reporting. If your ASC 280 segment disclosures already allocate selling costs, your DISE definition should be consistent with that allocation logic.
  4. Document the rationale. The annual definition disclosure is a formal accounting policy. Treat it with the same rigor as your revenue recognition or inventory costing policy.

The comparability risk is real and will be most acute in the first year of adoption, when no market practice has yet formed. Companies that define selling expenses narrowly (direct sales force costs only) will show lower selling expense ratios than companies that include marketing, customer success, and channel costs. Investors will notice.

Judgment Call 4: How Do You Handle Expense Reimbursements?

Entities with expense reimbursements included in a relevant expense caption must make an explicit presentation election. Per Deloitte's FAQ, two alternatives are available:

  • Gross presentation: Separately disclose the amount of the expense reimbursement as a line item in the tabular disclosure.
  • Net presentation: Disclose the required expense categories net of any reimbursement effects.

Whichever alternative you elect, you must also disclose: (a) the elected alternative in the tabular format, and (b) a qualitative description of the expense categories to which the reimbursement relates.

This matters most for companies with shared services arrangements, joint venture cost-sharing agreements, or collaborative R&D contracts where one party reimburses another for specified expenses. The election must be applied consistently, and a change in election triggers the recast requirement.

Judgment Call 5: Prospective or Retrospective Transition?

The transition choice is a CFO-level strategic decision, not a technical accounting default. The ASU offers two paths:

  • Prospective: Apply the new disclosures to periods after the effective date only. Operationally simpler, but you will have no prior-period comparatives in your first year of adoption.
  • Retrospective: Recast any or all prior periods presented. Provides year-over-year comparability from day one, but requires reconstructing historical data under the new framework.

The trade-offs:

FactorProspectiveRetrospective
Operational burdenLowerHigher (data reconstruction required)
Investor comparabilityLimited in year oneFull from adoption date
Audit effortLowerHigher (prior periods must be audited under new framework)
Early adopter advantageFaster to implementMore informative disclosure

If your GL systems already capture the required categories historically, retrospective adoption is worth considering. If you need to build estimation methodologies from scratch, prospective is the pragmatic choice. Decide this in Phase 2 of your implementation, once you know what data you actually have.

On a subsequent change in accounting policy (such as redefining selling expenses), the standard requires you to: disclose the reason for the change in the period of the change, and recast prior periods unless impracticable. The ASU states: "If it is impracticable to do so, the entity shall disclose that fact and explain why it is impracticable to recast prior periods." The "impracticable" standard is not further defined, which means your auditor will apply judgment to your judgment. Document the impracticability analysis thoroughly if you invoke it.

Judgment Call 6: What Do You Disclose in Your SAB 74 Footnote Right Now?

This is the most immediately actionable obligation, and it is already live. SEC registrants are required under SAB 74 (Staff Accounting Bulletin Topic 11.M) to disclose in their current 10-K filings the status of their adoption of standards not yet effective. ASU 2024-03 is mandatory for annual periods beginning after December 15, 2026, meaning calendar-year companies first apply it in their fiscal year 2027 annual 10-K. But the SAB 74 disclosure must appear in your 10-K filings now.

The four required elements of a SAB 74 disclosure for ASU 2024-03, per Deloitte's FAQ:

  1. A brief description of the standard and the required adoption date
  2. The method of adoption expected (prospective or retrospective), if determined
  3. The anticipated impact on financial statements, or a statement that it is not yet known or estimable
  4. Disclosure of other significant matters expected to result from adoption

The SEC reviews SAB 74 disclosures and issues comment letters when they are vague or boilerplate. A disclosure that says only "we are evaluating the impact" without any substantive analysis is increasingly likely to draw a comment as the 2027 effective date approaches. Start building your SAB 74 language now, and update it each quarter as your implementation progresses.

The Three-Phase Implementation Roadmap

Deloitte's implementation framework provides a useful structure for sequencing the work:

Phase 1: Understanding, Education, and Planning

  • Read the ASU 2024-03 full text and the FASB In Focus summary
  • Brief accounting, finance, operations, IT, investor relations, and internal audit
  • Review current income statement presentation and existing disclosure policies
  • Assess current data flows and GL/ERP tagging capabilities

Phase 2: Assessment and Gap Analysis

  • Identify every relevant expense caption on your income statement
  • Determine which of the five required categories are present in each caption
  • Assess data availability: can your systems produce the required amounts, or do you need estimates?
  • Identify existing disclosures (pension costs under ASC 715, lease costs under ASC 842) that must be folded into the new tabular format
  • Determine the transition method and document the rationale
  • Produce an implementation roadmap with milestones, resource requirements, and system change specifications

Phase 3: Implementation and Policy Documentation

  • Draft accounting and disclosure policies: estimation methodology, selling expenses definition, reimbursement presentation election
  • Build or modify internal controls over financial reporting (ICFR) to cover the new disclosures. These are SOX 302 and 404 considerations that your audit committee needs to understand
  • Develop the tabular disclosure template and test it against your actual data
  • Draft the SAB 74 footnote language and update it each reporting period
  • Brief investor relations on the selling expenses definition and the first-year comparability limitations

For the controls dimension specifically, see the ASU 2024-03 DISE controls guide.

What the May 2026 FASB Roundtable Signals

FASB held a public post-issuance roundtable on May 27, 2026, approximately 18 months after the ASU was issued. The existence of this roundtable is itself significant: it confirms that practitioner uncertainty is substantial enough that FASB felt compelled to convene a formal discussion before the mandatory effective date.

The meeting minutes are publicly available and should be on the reading list of every controller and technical accounting team implementing DISE. If FASB issues additional guidance or a narrow-scope amendment before December 2026, it will most likely emerge from the issues surfaced at this roundtable. Monitor the FASB project page for any post-roundtable publications.

FAQ

Is ASU 2024-03 effective for private companies? No. ASU 2024-03 applies only to public business entities. Private companies, not-for-profit entities, and employee benefit plans are exempt. However, a private company preparing for an IPO or that will be required to file financial statements with the SEC as a result of an acquisition should assess whether it will need to comply.

What are the two bases for disclosing inventory-related expenses under ASU 2024-03? The standard provides two approaches: the expense-incurred basis (recognizing inventory costs as they flow through the income statement) and the cost-incurred basis (recognizing costs when inventory is acquired). Entities must apply one consistently and disclose which basis they use.

Do we have to disaggregate expenses within discontinued operations? No. The relevant expense caption definition is limited to expense captions presented within continuing operations. Discontinued operations are outside the scope of the disaggregation requirements.

When do interim disclosures begin for calendar-year companies? Interim period disclosures begin for periods within annual periods starting after December 15, 2027, meaning Q1 2028 10-Q filings for calendar-year companies. Annual disclosures begin with the fiscal year 2027 10-K.

Should we early adopt ASU 2024-03? Early adoption is permitted. The case for early adoption: more time to refine disclosures, get ahead of investor questions, and influence emerging market practice on selling expenses definitions. The case against: being an outlier before peer practice develops, and the operational burden of accelerating system and process changes. The right answer depends on your data readiness and your investor relations strategy.

How do leased employees factor into the employee compensation disclosure? A leased individual counts as a common law employee of the lessee, and their compensation is subject to the employee compensation disaggregation requirement, only if specific conditions are met: the lessor must be contractually required to remit payroll taxes; the lessee must have exclusive rights to grant compensation, hire, fire, and control the individual; the individual must be eligible for lessee benefit plans; and the lessee must remit sufficient funds to cover complete compensation including payroll taxes. If those conditions are not met, the leased worker's costs are not employee compensation for DISE purposes.