
IFRS 18 replaces IAS 1, but it does more than rename a financial statement. The standard reduces flexibility in income statement presentation, strengthens disaggregation and provides a framework for management-defined performance measures.
What does not change
IFRS 18 mainly addresses presentation and disclosure. On its own, it does not fundamentally change transaction recognition and measurement. The underlying accounting data therefore remains largely the same.
What changes compared with IAS 1
- classification of income and expenses into operating, investing and financing categories;
- mandatory presentation of operating profit;
- presentation of profit before financing and income taxes;
- specific disclosures for MPMs;
- strengthened aggregation and disaggregation principles;
- related changes to certain IAS 7 requirements.
Impact on the consolidation model
Under IAS 1, many groups build the income statement mainly from an account hierarchy. IFRS 18 may require additional attributes: nature of the activity, type of asset, financing characteristics or destination of certain expenses.
The target model should clearly separate source data, IFRS 18 classification rules and reporting. This separation facilitates exceptions, future changes and the audit trail.
Impact on data collection
Reporting packages may need new details. Data previously collected in a single account may need to be broken down to determine its category or explain a material item. Collection controls must be adapted accordingly.
Impact on reporting
Statutory reports, dashboards, Excel statements, narrative reports and digital tagging must be aligned. IFRS 18 operating profit must not be confused with EBITDA or an adjusted operating result used for management purposes.
Impact on processes
- new mappings to maintain;
- validation of exceptions by accounting standards teams;
- reconciliation between old and new presentations;
- review of alternative performance measures;
- production of comparatives;
- updates to documentation and internal controls.
Recommended architecture
A robust solution is based on a centralized, versioned and documented rules table. Automated processing should cover most cases, while exceptions are managed through a controlled workflow. Users must be able to trace a published subtotal back to the original data.
A transformation to manage as an EPM project
Success depends less on formatting the final report than on the quality of the data and rules feeding it. IFRS 18 should therefore be treated as a cross-functional project involving accounting standards, consolidation, management control, tax, IT and financial communication.
When properly prepared, the transition can reduce manual adjustments and bring statutory and management reporting closer together. If poorly anticipated, it may instead add another layer of files and controls at the end of the close.