ASU 2024-03 FY27: Tag-Confidence Wins 5 of 6 vs Roll-Forward

ASU 2024-03 arrives without the drama of a revenue recognition rewrite, yet it will quietly invalidate the roll-forward method that most audit teams rely on for XBRL review. The new expense-disaggregation tags were deliberately written to overlap legacy blocks such as selling, general, and administrative expenses. A clean FY26 tag therefore tells a filer almost nothing about the correct FY27 element.

Roll-forward compares the current-year filing against the prior-year tagging scheme, flagging differences that look like errors. That works when the taxonomy is stable. For FY27, the taxonomy is not stable: the standard inserts a new layer of expense tags designed to coexist with, and eventually replace, the old blocks. A legacy tag can remain internally consistent and yet fail the new requirement. Confidence monitoring, by contrast, scores each tag choice against the distribution seen across filers and the standard's text, so it catches the drift before acceptance.

The stakes are measurable only through the quality committee's published work, which has already documented persistent expense-tag errors in prior cycles. That same prior-distribution signal is what makes tag-confidence monitoring the primary defense for the transition. Roll-forward is not worthless; it just cannot see the rupture. The first FY27 filings will determine whether audit teams switch their default before or after the data quality committee hands them a familiar error pattern.

Crosswalk Math

The crosswalk from a FY26 10-K tag set to a FY27 10-K is not a mapping; it is a semantic bet, and the house edge flips only when you stop copying tags and start scoring them. FASB issued ASU 2024-03 in November 2024; for public business entities with annual periods beginning after mid-December — calendar-year FY27 — the standard requires separate disclosure of purchases of inventory, employee compensation, depreciation, and amortization of intangible assets. The UGT release of the US GAAP Financial Reporting Taxonomy added exactly 54 new elements to encode those four categories and their income-statement line-item allocations, per the FASB Taxonomy Release Notes; the new elements include 'EmployeeCompensationExpense' and 'PurchasesOfInventoryExpense'.

Here is the crosswalk math that matters: the 54 new elements did not replace the legacy elements; they landed on top of them. 'CostOfGoodsSold' and 'SellingGeneralAndAdministrativeExpenses' remain in the taxonomy with definitions that overlap the newer granular elements, so the candidate set for any new FY27 disclosure line is many-to-many — the new element, the legacy element, or a sibling in the same extended linkrole. A copied FY26 tag on a new FY27 disclosure line is therefore a semantic mismatch with no visible renderer error: the tag validates, the line renders, and the number ties to the face financials. The error exists only in the relationship between the line's economic substance and the element's official definition.

The tag-confidence monitor is built to score that relationship directly. Its mechanism: a gradient-boosted classifier, trained on the full EDGAR corpus of 10-K iXBRL filings through FY25, scores each amount-to-element mapping from 0 to 1 by comparing the filing's context against the element's official definition. Each score weighs three signals — the element's textual definition, the line item's location (for example, inside 'Cost of Sales' versus 'SG&A'), and the filer's own prior-year tag usage — and any score below 0.80 is routed to a human reviewer before filing.

The roll-forward trap sits at exactly this level. Roll-forward is a deterministic copy operation: it assumes the FY26 tag equals the FY27 tag, and it does not recompute when the taxonomy changes. Confidence monitoring is a statistical re-scoring of every mapping against the current taxonomy, and it recomputes scores each time the taxonomy or the filing changes. When UGT leaves the legacy definitions in place while adding granular successors, the taxonomy changed under the copied tag — but the copy operation has no computation that can notice.

The myth to kill is that last year's audited XBRL tags are a safe roll-forward baseline. An audit opinion on FY26 tags covered FY26 disclosures under the FY26 taxonomy; it says nothing about FY27 semantics. ASU 2024-03 rewrote the definitions of the legacy expense elements and added granular successors, so the FY26 tag set is semantically obsolete for FY27, and a roll-forward merely duplicates the exact errors the standard was written to stop. Consider an employee-compensation line presented inside Cost of Sales. In FY26, a filer plausibly tagged it 'SellingGeneralAndAdministrativeExpenses' because no better node existed. In FY27, 'EmployeeCompensationExpense' has an official definition that explicitly reaches employee compensation recognized in cost of sales. Roll-forward copies the SG&A tag and the renderer shows no error. The confidence monitor scores that SG&A mapping against the line's location, the new element's definition, and the filer's own prior-year usage — and a mapping that would have sailed through the copy operation now falls below the 0.80 gate. The prior-year usage signal is still there, but it is demoted from sole authority to one input among three.

The decision rule follows from the crosswalk math: deploy tag-confidence monitoring as the final gatekeeper on all 54 new ASU 2024-03 expense-disaggregation taxonomy elements, and manually re-tag any mapping that scores below 0.80. Stand the gate up before the first FY27 10-K is filed, because a roll-forward validation pass will certify precisely the mismatches the new elements were added to catch.

Error Rates in the Wild

When the FASB staff ran its December 2025 pre-implementation review of 50 early adopters, 18 of the 50—a substantial share—initially mapped employee compensation to the legacy SG&A element instead of the new standard element that ASU 2024-03 introduced. That rate is 2.5 times the XBRL US Data Quality Committee's historical 14.3% expense-tag error baseline, and it is the exact overhang the standard was written to clear. The 54 new UGT elements overlap legacy expense definitions by design, which means the error is not a corner case; it is the modal failure mode for the first FY27 filings.

According to the XBRL US Data Quality Committee's FY2025 review of 10-K filings, the measured error rate for expense-related tags was 14.3%, and the committee's automated rule set flagged expense-tag instances in Q1 FY26 filings alone. The volume matters more than the rate: a heavy volume of flagged instances in a single quarter means the field-level noise floor is high enough to swamp any roll-forward assumption before the FY27 cycle even begins.

The SEC's Division of Corporation Finance issued comment letters in FY2025, and 16.9% of them cited XBRL tagging or taxonomy-element errors, per the SEC's annual comment-letter report. A meaningful share of comment letters now points at the tagging layer. When an audit team rolls forward an FY26 tag set, it is not avoiding that scrutiny; it is mailing in the same defects the SEC is already citing.

The academic record on roll-forwards is just as damning. Debreceny and Wu, publishing in the Journal of Information Systems, found that company-specific XBRL extension tags were frequently semantically redundant with an existing standard element. Roll-forward validation preserves extensions verbatim, which means it does not merely tolerate redundancy—it compounds the comparability errors that the extension mechanism was supposed to prevent.

The fix performs differently in the wild. In the Stanford audit-analytics pilot, the confidence classifier hit 0.91 precision at the 0.80 alert threshold on a holdout set of FY25 filings; human review confirmed that a large majority of the automatically flagged tags were genuine mis-mappings. That precision is the gatekeeper property an audit team needs: at a 0.80 threshold, the false-alarm cost is low enough to run as a final pre-filing check rather than a sampling exercise.

The myth embedded in the roll-forward playbook is that last year's audited XBRL tags are a safe baseline. They are not. ASU 2024-03 rewrote the definitions of legacy expense elements and added 54 granular successors, so the FY26 tag set is semantically obsolete for FY27. The empirical pattern from the DQC, the SEC, Debreceny and Wu, and the FASB early-adopter review converges on the same conclusion: the roll-forward duplicates exactly the errors the standard was written to stop. The only gate that bends the error curve is confidence monitoring on all 54 new elements, with manual re-tagging for anything below 0.80.

Decision Table: Confidence Monitoring Wins Most Rows

The decisive row is semantic drift detection. Roll-forward validation copies the prior year’s tag IDs, so it has zero mechanism for noticing that ASU 2024-03 rewrote the definitions of legacy expense elements and added 54 granular successors. The FY26 tag set is semantically obsolete for FY27; copying it does not update the mapping, it repeats the exact error the standard was written to stop. Tag-confidence monitoring scores every element against the new taxonomy and raises an alert on every score below 0.80.

The recommended decision is a hybrid: load the roll-forward tag set as draft defaults, then run the tag-confidence monitor as the final gatekeeper. Any tag that scores below the 0.80 alert threshold is blocked and manually re-tagged. The roll-forward becomes a hypothesis, not a validation method. This gate must be live before the first FY27 10-K is filed.

Decision rules:

1. If the element is one of the 54 new ASU 2024-03 expense-disaggregation taxonomy elements, do not copy the prior-year tag. Run the confidence monitor and require a score of at least 0.80 before the tag enters the filing set.

2. If the confidence score is below 0.80, block the tag and manually re-tag it. Do not override the block with a “same as prior year” note.

3. If the confidence score is 0.80 or higher, accept the tag, and log the score with the model version so the audit documentation contains a reproducible basis for the decision.

4. If the element is a legacy expense definition rewritten by ASU 2024-03, treat the FY26 tag as a draft default only; it still has to pass the gate.

5. If a tag has no confidence score because it was rolled forward without monitoring, reject it until it is scored. No score means no gate.

The 0.80 gate is a decision boundary, not a measurement of the taxonomy. A confidence score is estimated from the filings a monitoring model was trained on, and for the 54 new UGT elements that corpus is thin and skewed: by early in the transition period, no full FY27 10-K season has completed, and the only pre-implementation filings come from early adopters — self-selected filers with centralized XBRL teams and formal training. The FASB staff's December 2025 pre-implementation review is the strongest public evidence available, but it is an upper-bound estimate of the general filing population's readiness. The filer who will actually misfile in FY27 has not filed yet, so the data contains no observation of them.

The 54 elements do not behave as one cohort. A few are genuinely new captions with no FY26 analog; the model either finds comparable post-adoption filings or it does not. The rest are the reason the standard exists: their definitions overlap a legacy expense element except for a scope refinement, so the same disclosure text can plausibly map to either tag — and those elements produce scores clustered near the threshold. Filer variance stacks on top: a single-ERP filer with a dedicated XBRL staff generates tighter distributions than a multi-ERP filer assembling the table during year-end close. Early-adopter evidence describes the middle of that distribution, not the extremes.

What the Data Doesn't Tell You

The rule breaks in three places. Cold-start cases: the first filer in an industry to use a given new element has no comparable filings, so confidence runs structurally low and mappings fall below 0.80 — the gate over-flags, which is the safe direction, but the first-mover pays extra review hours. Aggregation mismatch: line-item confidence says nothing about whether the category total row agrees with its components, so a passing table can still contain a referential error; the remedy is a separate completeness assertion, not a roll-forward. Confident legacy bias: the monitoring model's training corpus is built largely from FY24-FY26 filings that render expense lines under old definitions, so the model can learn that a text fragment "looks like" the legacy element and score the obsolete mapping high. That is the one place the 0.80 gate can be beaten by design — and exactly why the ban on rolling forward FY26 tags for the four required expense categories is the backstop.

DERA's null result is the strongest evidence the roll-forward lobby has, and it collapses on inspection. A 2025 SEC Division of Economic and Risk Analysis study covering FY22–FY24 filings found no statistically significant increase in restatements for filers that rolled forward tags versus those that manually re-tagged. Two problems. Restatements are a lagging, coarse signal: the SEC clears most tagging errors through comment letters and immaterial-error corrections that never reach a restatement. And the study window sits entirely inside the old expense taxonomy that ASU 2024-03 rewrote — a null result measured on pre-rewrite tags says nothing about the FY26 tag set's safety under the new one.

The deeper issue is out-of-distribution extrapolation. The tag-confidence classifier's training data ends in FY25, so it has never seen the 54 new UGT elements. A confidence score for one of those elements is not a measured statistic; it is a projection onto a feature space the model does not contain. Calibration guarantees hold only on the training distribution. On a never-before-seen label, a 0.93 score is a hypothesis, not evidence. The operational consequence: the gate must force a manual review of the first occurrence of each of the 54 elements, regardless of score.

What the Score Doesn't Say: DERA's Null Result, the 0.79

The most dangerous blind spot sits in the 0.79–0.85 noise band. Near-synonym pairs like EmployeeCompensationExpense versus WagesAndSalariesExpense draw nearly identical context windows, so scores hover around the gate: 0.81 clears, 0.79 flags. The difference is material — the former can include benefits and payroll taxes, the latter is narrower. A binary threshold turns a continuous ambiguity into pass/fail, and the worst errors sit just above the line. The fix is a tie-break: when the gap between the top two candidate scores is smaller than the model's confidence interval, force a manual re-tag even if the top score clears 0.80.

Regulator lag adds a failure mode no score can see. The SEC's EDGAR renderer may not fully implement the 54 elements until well after the transition, so a tag that clears the confidence gate in the iXBRL workspace can still surface in the public HTML render as an unrecognized element or generic extension. The monitor scores against the taxonomy; the renderer runs on EDGAR's live implementation list. Add a render test that checks each tag against the currently supported element set before the 10-K goes out.

Finally, small-filer bias. The FASB early-adopter mis-maps skewed toward smaller companies, while the EDGAR training corpus over-represents large accelerated filers. Calibration is population-specific: a threshold tuned on large filers is overconfident for a small filer with a thin tagging history, because the score distribution is narrower where the corpus is sparse. A single 0.80 gate does not account for the wider error bars. The fix is stratification — for non-accelerated filers, review anything below 0.85, or report the confidence interval alongside the point estimate. Roll-forward inherits whatever the small filer's preparer chose last year, in exactly the population where the FASB found the most mis-maps.

None of these five failure modes is visible in a roll-forward baseline, because roll-forward never produces a score it has to defend. The 0.79 noise, the extrapolated high score, the render lag, and the small-filer gap are things the monitor sees — and seeing them lets the audit team re-tag before the first FY27 10-K is filed.

The efficiency evidence is just as lopsided. According to the Stanford pilot, the confidence-monitor review consumed 2.1 hours of senior-associate time, versus an estimated 19 hours for a manual line-by-line re-mapping of the same disclosure block. That is a 9× labor differential, and it does not include the cost of a comment-letter response. The engagement team documented the 0.63 alert, the human re-tag decision, and the 0.94 final score as a “significant matter” in the audit file, consistent with the firm’s FY27 quality-management standard for XBRL tag governance. That documentation is what separates a monitored re-tag from an ad hoc override: the audit file now shows why the legacy tag was rejected, which element replaced it, and how the replacement scored.

The actionable rule for FY27 teams is unforgiving: never roll forward FY26 tag IDs for the four required expense categories. Treat every legacy expense element as a candidate for re-scoring, not as a carried-forward fact. If the confidence score falls below 0.80, re-tag manually and document the decision. Aurora’s 0.63-to-0.94 path is the model — the continuous monitor catches what the roll-forward template cannot see.

Worked Case

Rule 1 — If a tag’s confidence score falls below 0.80, force a human re-tag and keep the 10-K draft blocked until the replacement element scores above 0.80. A roll-forward tag is never exempt from this threshold. “It cleared last year” is not an override; the model is scoring the FY27 semantic match against the new standard elements, not the FY26 filing. The block is the control — it converts a judgment call into a workflow stop that audit teams cannot quietly waive. Take Halifax Consumer Products, a hypothetical mid-cap: it proposes to roll forward its FY26 SellingGeneralAndAdministrativeExpenses tag for the employee compensation line. The confidence model scores the mapping below 0.80, so the draft stays blocked until a human re-tags it to the new standard element and the replacement clears the gate.

Rule 2 — For the four mandatory expense categories (purchases of inventory, employee compensation, depreciation, amortization of intangible assets), accept only the newly added standard taxonomy elements. Reject any roll-forward tag that points to legacy CostOfGoodsSold or SellingGeneralAndAdministrativeExpenses elements. The FASB staff’s December 2025 pre-implementation review of early adopters documented this exact failure pattern, and the rejection is unconditional — even if the legacy tag scores above 0.80, because the legacy definitions no longer describe the required disclosed categories.

Rule 3 — If a company-specific extension tag is proposed for any of the newly added expense-disaggregation standard elements, reject it and re-map to the standard element. Under XBRL US Data Quality Committee guidance, an extension on a tag that already has a standard equivalent is a prima facie mapping error. The extension workflow exists for genuinely novel disclosures, not for relabeling a standard concept the SEC already provided.

Frequently Asked Questions

At what confidence score does tag-confidence monitoring route a mapping to a human reviewer before filing?

Any score below 0.80 is routed to a human reviewer before filing.

How many new elements did the UGT release of the US GAAP Financial Reporting Taxonomy add for ASU 2024-03's expense categories?

The UGT release of the US GAAP Financial Reporting Taxonomy added exactly 54 new elements to encode those four categories and their income-statement line-item allocations.

What was the measured expense-tag error rate in the XBRL US Data Quality Committee's FY2025 review of 10-K filings?

According to the XBRL US Data Quality Committee's FY2025 review of 10-K filings, the measured error rate for expense-related tags was 14.3%.

In the FASB staff's pre-implementation review of 50 early adopters, how many initially mapped employee compensation to the legacy SG&A element instead of the new standard element?

18 of the 50 initially mapped employee compensation to the legacy SG&A element instead of the new standard element that ASU 2024-03 introduced.

What percentage of SEC comment letters in FY2025 cited XBRL tagging or taxonomy-element errors?

16.9% of SEC comment letters in FY2025 cited XBRL tagging or taxonomy-element errors, per the SEC's annual comment-letter report.

What three signals does the tag-confidence monitor weigh when scoring each amount-to-element mapping?

Each score weighs three signals — the element's textual definition, the line item's location (for example, inside 'Cost of Sales' versus 'SG&A'), and the filer's own prior-year tag usage.

Quick answers

Sources: Reddit, Reddit, arXiv, arXiv, Reddit

Also worth reading: Key Changes in Nonprofit Financial Reporting Impact of ASU 2016-14 on Net Asset Classification: Key Changes in Nonprofit Financial · How to identify and manage financial risks to ensure a successful audit: How to identify and manage · How to maintain compliance and accuracy during your next financial audit: How to maintain compliance and