DISE expense disaggregation lands on the 2027 income statement

What ASU 2024-03 actually requires

FASB issued ASU 2024-03, Disaggregation of Income Statement Expenses, in November 2024. It does not change the face of the income statement. Instead, it adds a note that takes each relevant expense caption - cost of sales, selling, general and administrative, and similar lines - and disaggregates it into specified natural categories, including purchases of inventory, employee compensation, depreciation and intangible asset amortization. Amounts that do not fall into a named category are described qualitatively.

The scope is public business entities. The standard is effective for annual periods beginning after December 15, 2026, and interim periods within annual periods beginning after December 15, 2027, with early adoption permitted. A follow-on ASU clarified the interim effective date. Entities may apply the guidance prospectively or retrospectively, and that election is a real decision rather than a formality.

The practical translation for a December year-end filer: the first DISE note shows up in the FY2027 annual report, and the underlying transaction data has to be tagged correctly starting January 1, 2027. There is no catch-up mechanism that makes bad source data acceptable.

Why this is an ERP problem, not a disclosure problem

Most finance organizations cannot pull inventory purchases, employee compensation, depreciation and amortization by income statement caption without manual mapping. Compensation sits in payroll systems allocated across cost centers. Depreciation sits in fixed asset subledgers keyed to asset class, not to the caption where the expense ultimately lands. Inventory purchases are buried in cost of sales roll-forwards that were never designed to be published.

The gap gets closed one of two ways. Either the general ledger and subledger tagging carries the natural category through to the caption automatically, or someone builds the note in a spreadsheet every period. The second option is survivable in year one and corrosive after that: it is manual, it sits outside the system of record, and it invites a control deficiency finding the first time an auditor traces a number back to source.

The sequencing matters. Chart-of-accounts changes normally go live at the start of a fiscal year. Miss January 1, 2027, and the alternative is a mid-year conversion with two data structures in the same annual period, which is worse than either one alone.

Washington subtracts while FASB adds

The regulatory picture running alongside DISE points the other way. The SEC's reporting framework overhaul proposed in May 2026 would cut disclosure volume across the 10-K. A separate proposal would permit optional semiannual reporting through a new Form 10-S. The Commission has also proposed rescinding the climate disclosure rules. Read together, the direction of travel in Washington is fewer pages and fewer filings.

FASB is not following that arc. The board issued an exposure draft on targeted Codification improvements in September 2026, confirming that technical standard-setting continues at pace. For CFOs, the net effect in 2027 is deregulation on the front half of the filing and re-plumbing in the notes. Headcount freed up by lighter SEC requirements will not automatically cover the accounting work DISE creates, because the two draw on different skills and different systems.

The unit economics your competitors will finally see

The compliance cost is manageable. The strategic exposure is the part boards should be discussing now. A disaggregated cost of sales line reveals how much of gross margin is materials versus labor versus depreciation. A disaggregated SG&A line reveals how much of the operating base is people. Analysts have modeled these splits for years; DISE replaces the estimate with a company-confirmed figure.

That has second-order effects. Customers negotiating renewals gain a view of input costs. Competitors gain a benchmark for labor intensity. Activists gain a cleaner argument about fixed-cost structure. Companies with unusually high depreciation inside cost of sales, or unusually high compensation inside SG&A, will be asked to explain the gap against peers in the first earnings call after the note publishes.

The prospective versus retrospective election feeds directly into this. Retrospective application gives readers a comparative trend from day one, which is helpful if the trajectory is favorable and unhelpful if it is not. Prospective application delays the trend line but invites questions about why.

What to do in the next two quarters

Run a dry run on FY2026 actuals. Build the DISE table from existing data as if the standard were already effective, and document every place where the number had to be derived by hand. That list is the system remediation backlog, and it is more credible with the audit committee than a generic readiness assessment.

Decide the transition method before the ERP work is scoped, because retrospective application requires comparative-period data that may only exist in archived formats. Then pre-brief investor relations. The first DISE note will tell a margin story, and the finance team should decide what that story is before an analyst does it for them on a live call.