Tech

From D365 to board-ready insights in weeks

February 25, 2026|1:00 PM ET|Past event

With 2026 already underway as the comparative year, thousands of IFRS-reporting companies face a ticking clock to overhaul financial statement presentation under IFRS 18 or risk audit failures and investor backlash in 2027.

Key takeaways

  • IFRS 18 becomes mandatory for periods beginning January 1, 2027, but requires full retrospective restatement of 2026 figures, forcing system and process changes during the current year.
  • Finance teams using legacy ERP setups like Dynamics 365 must reclassify income/expenses into rigid operating/investing/financing categories, often necessitating expensive upgrades or add-ons to produce compliant, board-ready reports without manual patchwork.
  • While the standard promises better comparability, it creates tensions by potentially distorting business-specific performance views and adds compliance burdens amid parallel demands from sustainability reporting rules.

The IFRS 18 Imperative

The International Accounting Standards Board issued IFRS 18 in April 2024 to replace IAS 1, introducing stricter rules for presenting income and expenses in financial statements. Companies must now classify items into defined categories—operating, investing, and financing—with mandatory subtotals including operating profit, and tightly control use of management-defined performance measures through reconciliations.

The urgency stems from the effective date: annual periods starting on or after January 1, 2027, with retrospective application. For most calendar-year entities, this means 2026 serves as the comparative period that must already reflect IFRS 18 rules. Finance systems need reconfiguration now to capture and report data correctly, or companies will struggle to produce reliable 2027 statements with accurate prior-year comparatives.

Affected organizations include publicly listed firms and others using IFRS, particularly in jurisdictions like Canada where it aligns with national standards. CFOs face pressure to deliver faster, more transparent insights to boards and investors, but many legacy ERPs—including aspects of Microsoft Dynamics 365—require customization or external tools to handle the new granularity without slowing period-end closes.

Stakes are high: non-compliance could trigger qualified audit opinions, regulatory penalties, or market penalties via reduced credibility. Implementation costs vary but often include significant consulting fees, IT spend, and internal resource time—potentially millions for complex groups. Inaction also risks extended close cycles and errors in key metrics.

Less discussed is the tension between standardization and relevance: the new structure curbs flexible reporting that some argue better reflected unique business models, potentially forcing awkward classifications. Meanwhile, integration with emerging sustainability standards adds complexity, as both demand high-quality, assured data from the same core systems.

Quality score

7.3/ 10
Speaker
7
Pitch
7
Website
8
Engagement
7

We use cookies to measure site usage. Privacy Policy