DISE and IFRS 18 Reporting Technology: What Your Stack Must Do Before 2027

If your team is still mapping IFRS 18 compliance in spreadsheets, the problem is not effort. It is architecture. Two parallel standards, IFRS 18 and FASB ASU 2024-03 (DISE), are mandatory from January 2027 and both require retrospective application. That means your systems must be capturing 2026 data correctly right now, not next year.

This guide is for CFOs, group controllers, and finance transformation leads who already understand what the standards require and now need to answer a harder question: does our current technology stack actually support compliance, or are we building manual bridges between disconnected systems while the clock runs out?

Key takeaway: The technology selection window for IFRS 18 and DISE compliance is effectively closing in late 2026. Systems must be operational during 2026 to capture comparative period data. Delay means restatement risk.

What IFRS 18 and DISE Actually Demand from Your Systems

The regulatory requirements translate into specific data and workflow demands that most legacy systems were never designed to meet. Understanding the gap starts with being precise about what each standard requires operationally, not just legally.

IFRS 18, issued by the IASB on April 9, 2024, replaces IAS 1 and is mandatory for annual periods beginning on or after January 1, 2027, with full retrospective application. IASB Chair Andreas Barckow called it "the most significant change to companies' presentation of financial performance since IFRS Accounting Standards were introduced more than 20 years ago." IFRS applies in more than 140 jurisdictions, so the scope is global.

From a systems perspective, IFRS 18 creates three distinct technology demands:

1. Five-category income statement classification. Every P&L line item across every subsidiary must be classified into one of five mandatory categories: operating, investing, financing, income taxes, or discontinued operations. This is not a one-time mapping exercise. It is an ongoing classification engine that must run consistently across entities with different ERPs, charts of accounts, and local standards.
2. Two mandatory profit subtotals. Operating profit and profit before financing and income taxes must be calculated and presented consistently. Companies that already report an operating profit subtotal often calculate it differently. IFRS 18 standardizes the definition, which may require recalculating historical figures.
3. MPM disclosure governance. Management-defined performance measures (MPMs) such as adjusted EBITDA or adjusted operating profit, previously disclosed informally, must now appear in the audited notes with a full reconciliation to the nearest IFRS subtotal. For the first time, these metrics are inside audit scope. That means your adjusted EBITDA calculation needs an approval workflow, a version history, and documentation that satisfies an external auditor.

FASB ASU 2024-03 (DISE), issued November 2024, is effective for US public companies for fiscal years beginning after December 15, 2026, also with retrospective application. DISE does not restructure the income statement face. Instead, it requires granular footnote disaggregation of expense captions, breaking out components such as employee compensation, depreciation, amortization, and inventory within existing line items like cost of goods sold and SG&A.

The operational demand from DISE is different but equally data-intensive: your consolidation system must be able to pull component-level expense data from source ERPs and map it into the required footnote categories. If your chart of accounts does not capture that granularity today, you have a data gap.

For a precise side-by-side of how the two standards compare, see our IFRS 18 vs ASU 2024-03 comparison.

Why Legacy Tools Fail: Four Specific Failure Modes

Spreadsheets, ERP consolidation modules, and disconnected planning tools share a common flaw: they were built for single-framework, single-period reporting. IFRS 18 and DISE require something fundamentally different.

Here are the four failure modes that surface in practice:

1. No Parallel Framework Support

During 2026, you must run IAS 1 reporting for your current-year close while simultaneously capturing data under the IFRS 18 structure for comparative period purposes. Spreadsheets cannot do this from a single dataset without duplicate data entry, version control failures, and reconciliation errors. Legacy consolidation tools face the same problem: they were designed for one framework at a time.

2. No MPM Governance Capability

Adjusted EBITDA calculated in a spreadsheet tab, approved by email, and pasted into the notes is no longer adequate. Auditors will test the MPM reconciliation as part of the financial statement audit. They will want to see a defined calculation methodology, a reconciliation to the IFRS subtotal (including tax effects and non-controlling interest impacts), an approval trail, and evidence that the methodology was applied consistently across periods. None of that exists in a spreadsheet or a standard ERP consolidation module.

3. Inconsistent Group-Wide Classification

Classifying every P&L item into operating, investing, or financing across a group with 20 subsidiaries running SAP, Oracle, and local ERPs is a coordination problem as much as a technical one. Without a centralized rules engine, each subsidiary finance team makes its own judgment calls. The result is classification inconsistency that creates audit findings and restatement risk. IFRS 18 implementation touches at least six departments simultaneously: Corporate FP&A, Treasury, Legal, HR, IT, and Investor Relations, plus all subsidiary finance teams. Disconnected systems make consistent implementation nearly impossible.

4. Retrospective Restatement Without a Data Trail

Both IFRS 18 and DISE require retrospective application. That means your 2027 financial statements must show 2026 comparatives under the new frameworks. If your systems are not capturing 2026 data at the required granularity today, you will not be able to reconstruct those comparatives from summary ledger data. Finance teams that delay technology implementation until 2027 will face a restatement crisis.

The Six Non-Negotiable Technology Capabilities

Any platform you evaluate for IFRS 18 and DISE compliance must deliver all six of the following capabilities. Partial coverage means manual workarounds, which means audit risk.

The sixth capability deserves emphasis. The practical architecture question for most multi-entity groups is: do we reclassify at the ERP level or at the consolidation layer? Reconfiguring transaction systems is expensive, risky, and slow. The recommended approach is to extract granular data from existing ERPs and apply IFRS 18 classification rules at the consolidation layer. This preserves your source systems and avoids a complete chart-of-accounts redesign, while still giving you the category-level data IFRS 18 requires.

For the chart-of-accounts granularity question specifically, including how to support both IFRS 18 five-category classification and DISE footnote disaggregation simultaneously, see our ASU 2024-03 chart of accounts mapping guide.

What Auditors Will Actually Test on MPM Disclosures

This is the gap that most technology assessments miss. Finance teams understand that MPMs are now audited. Fewer teams have thought through what that means for their governance workflows and system design.

Auditors reviewing MPM disclosures under IFRS 18 will test:

• Completeness: Are all MPMs that management communicates publicly included in the notes? This includes metrics used in earnings releases, investor presentations, and analyst calls.
• Reconciliation accuracy: Does the reconciliation from the MPM to the nearest IFRS subtotal correctly account for each adjustment, including tax effects and non-controlling interest impacts?
• Methodology consistency: Is the MPM calculated the same way as in prior periods? If the methodology changed, is the change disclosed and explained?
• Approval trail: Is there documented evidence that the MPM calculation was reviewed and approved before inclusion in the financial statements?

A spreadsheet-based MPM calculation with email approval does not satisfy any of these tests at scale. Your technology platform needs a dedicated MPM workspace that captures the calculation inputs, the reconciliation steps, the approver sign-off, and the version history, all in a single auditable environment.

For a step-by-step guide to building the MPM reconciliation note itself, see our IFRS 18 MPM reconciliation practitioner guide.

Handling Dual Compliance: IFRS 18 and DISE for Multinationals

If your group reports under both IFRS and US GAAP, you face overlapping but non-identical requirements. The two standards create partial convergence on expense granularity but diverge significantly in approach.

For a multinational with US-listed debt or US subsidiaries, the data demands overlap but do not align perfectly. DISE requires component-level expense data (employee compensation broken out of SG&A, for example) that IFRS 18 does not explicitly require in the same form. IFRS 18 requires MPM governance that DISE has no equivalent for.

The practical implication: your consolidation platform must be able to produce both outputs from the same underlying dataset without running two separate close processes. A platform that handles IFRS 18 but cannot produce DISE-compliant footnote disaggregations, or vice versa, forces your team into manual reconciliation between frameworks.

A Vendor Evaluation Checklist for IFRS 18-Ready Platforms

Use these questions in RFP processes and vendor demonstrations. A credible platform should answer all of them without qualification.

Parallel reporting and data architecture

• Can the platform run IAS 1 and IFRS 18 reporting simultaneously from a single dataset, without duplicate data entry?
• Does it apply IFRS 18 classification at the consolidation layer, leaving source ERP systems unchanged?
• How does it handle entities with different ERPs (SAP, Oracle, local systems) within the same group?

MPM governance

• Does the platform provide a dedicated MPM workspace with calculation inputs, reconciliation steps, and approval workflows?
• Does it maintain a version history of MPM methodology changes?
• Can it produce the full reconciliation note, including tax effects and NCI impacts, directly from the workspace?

Classification rules engine

• Can group-wide classification rules be defined centrally and applied consistently across all subsidiaries?
• How does the platform handle entities whose main business activity is financing or investing (banks, insurers, real estate), where the classification rules differ from the general model?
• What happens when a transaction requires judgment rather than a rule? Is there a workflow for escalation and documentation?

Retrospective restatement

• Can the platform restate comparative period data automatically when classification rules or MPM methodologies change?
• What granularity of historical data does it retain, and for how many periods?

Disclosure management

• Does the platform integrate consolidation data directly into disclosure templates, or does it require manual export and re-keying?
• Can it produce DISE-compliant footnote disaggregations alongside IFRS 18 disclosures from the same dataset?

Planning alignment

• Can budget structures be built on IFRS 18 categories so that variance analysis uses consistent subtotal definitions?

The 2026 Implementation Timeline: When You Actually Need to Act

The retrospective application requirement compresses the timeline in a way that is easy to underestimate. Here is what the milestones actually mean in practice:

• Now through Q4 2026: Systems must be operational and capturing 2026 data under the IFRS 18 structure. This is not a future state. The 2026 reporting year is simultaneously the last full year under IAS 1 and the first comparative period that must be restated under IFRS 18.
• Q3-Q4 2026: 2027 budgets must be built on IFRS 18 categories. If your planning system is not aligned to the new structure before the 2027 budget cycle closes, your variance analysis will be misaligned from day one of the new standard.
• Q4 2026 - Q1 2027: Parallel close under both IAS 1 (for 2026 year-end) and IFRS 18 (for 2026 comparative data). This is the highest-risk period for teams running manual or disconnected processes.
• Q1 2027 onward: First statutory reporting period under IFRS 18. MPM disclosures are in the audited notes. Auditors are testing the governance workflows.

For a full phase-by-phase transition roadmap including stakeholder mapping and covenant risk, see our IFRS 18 transition plan. For the internal audit perspective on IFRS 18 and DISE implementation risk, see our internal audit risk assessment guide.

FAQ

Can we use our existing ERP consolidation module for IFRS 18 compliance? Probably not without significant customization. ERP consolidation modules were designed for single-framework reporting. They lack native support for multi-framework parallel reporting, MPM governance workspaces, and group-wide classification rules engines. The customization cost and timeline for retrofitting a legacy module typically exceeds the cost of an integrated platform built for the new requirements.

What is an MPM governance workspace and why does audit care about it? An MPM governance workspace is a structured environment within your reporting platform where management-defined performance measures (such as adjusted EBITDA) are calculated, reconciled to IFRS subtotals, approved, and version-controlled. Auditors care because IFRS 18 brings MPMs inside the audited financial statements for the first time. Without a governed workspace, there is no audit trail to satisfy the completeness, accuracy, and consistency tests auditors will apply.

Do we need to reconfigure our ERP chart of accounts for IFRS 18? Not necessarily. The recommended architecture for multi-ERP groups is to apply IFRS 18 classification at the consolidation layer, extracting granular data from existing ERPs without changing transaction systems. This avoids a costly and risky chart-of-accounts redesign while still producing the category-level data IFRS 18 requires. Some additional granularity may be needed at the source level to support DISE footnote disaggregation.

What is the difference between IFRS 18 and DISE for a multinational reporting under both frameworks? IFRS 18 restructures the income statement face and mandates MPM disclosures in the audited notes. DISE operates entirely in the footnotes and has no MPM equivalent. Both require retrospective application with similar effective dates. A multinational needs a platform that can produce both outputs from the same dataset, since the data demands overlap but are not identical.

Should we consider early adoption of IFRS 18? Early adoption is permitted under the standard. The strategic case is straightforward: the earlier your systems are operational under IFRS 18, the more comparative period data you capture correctly, and the less restatement risk you carry into 2027. Companies with complex group structures or significant MPM disclosure obligations have the most to gain from moving early.

What primary sources should our technology team reference when designing IFRS 18 system architecture? Start with the IASB's IFRS 18 Project Summary, which includes an illustrated P&L structure showing the five categories and two mandatory subtotals. PwC Viewpoint, KPMG Financial Reporting View, EY, and Deloitte IAS Plus all publish detailed implementation guidance. These are the most authoritative practical references available and should be the foundation for any chart-of-accounts mapping or consolidation redesign project.