FINANCIAL REPORTING & IFRS
IFRS 18 readiness starts in the reporting data
Treat the transition as a controlled reporting project: connect accounting judgments, ledger detail, comparative information and disclosure ownership.
By CA Tony Thomas · Chartered Accountant · 5 minute read
Published
FINANCE · JUDGMENT · TECHNOLOGY / 04 OF 04
The deadline is also a data question
IFRS 18 Presentation and Disclosure in Financial Statements applies to annual reporting periods beginning on or after 1 January 2027, with earlier application permitted. It replaces IAS 1. For a calendar-year entity first applying it in 2027, the practical challenge includes preparing the 2026 comparative information, rather than waiting until the 2027 year-end to redesign the reporting pack. Source: IFRS Foundation announcement.
As at 21 October 2026, my proposed starting point is a reporting-data assessment. Can the existing ledger, consolidation process and disclosure files produce the required presentation consistently, with an explanation of each material judgment? A polished new statement layout will not resolve missing source attributes or unsupported mappings.
The roadmap below is an implementation approach for finance teams, not a complete interpretation of IFRS 18. Confirm the reporting framework, reporting period and applicable jurisdictional requirements for your entity before using it.
Translate requirements into owned decisions
The statement of profit or loss uses five categories: operating, investing, financing, income taxes and discontinued operations. IFRS 18 introduces defined subtotals including operating profit and profit or loss before financing and income taxes, with specific requirements and exceptions for certain business activities. Classification requires assessment of whether investing in assets or providing financing to customers is a main business activity; account names alone do not settle the answer. Source: IFRS 18 Taxonomy Update, presentation requirements.
Create a decision register before changing account mappings. For each material reporting stream, record the reporting entity, transaction type, underlying asset or liability, proposed presentation, standard reference, rationale and reviewer. Assess group and separate financial statements on their own facts where relevant.
Use a controlled mapping table outside the ledger if that is sufficient. Adding accounts is not automatically necessary. Add source attributes where the same account genuinely contains items requiring different treatment. Keep ambiguous balances in a visible exception list until the accounting decision is approved.
An illustrative mapping problem
Consider a fictional trading group with one “finance income and expense” account containing bank interest, borrowing costs and exchange differences on both trade payables and financing liabilities. Moving the entire account into one category because of its name would embed an untested assumption.
The project team should identify the underlying transactions, separate the populations and document the applicable treatment under IFRS 18, including relevant guidance for foreign exchange and the entity’s business activities. An automated mapping can apply approved decisions; it should not invent them.
The useful deliverable is a reproducible link from transaction or consolidation adjustment to reporting line. Test it with mixed accounts, reversals and late adjustments. Compare the old and proposed presentations and explain each movement. The illustration identifies a data-design issue; it intentionally does not prescribe a category for every instrument or exchange difference.
Build the comparative bridge now
Transition is retrospective. IFRS 18 also requires a line-item reconciliation for the immediately preceding comparative period between the restated profit-or-loss presentation and the amounts previously presented under IAS 1. For a calendar-year 2027 adopter, that makes 2026 a working dataset for transition. Check the standard’s transition provisions, including relevant interim requirements, for the entity’s circumstances. Source: IFRS 18, Appendix C; full text may require access.
Preserve the approved prior presentation, a versioned mapping and the restated output. Explain movement by movement rather than relying on a spreadsheet that merely happens to balance. Tie both views to the same controlled consolidation population, including eliminations and manual reporting adjustments.
Run a dry close using available 2026 data. Assign owners to missing attributes and quantify the remaining data gaps. If a mapping changes, rerun the comparative bridge and preserve the earlier approved version. This is an opportunity to make reporting lineage more reliable beyond the transition itself.
Bring performance measures into the control framework
Inventory the measures used in public communications outside the financial statements. An MPM is a subtotal of income and expenses meeting the standard’s definition, including communicating management’s view of an aspect of the entity’s financial performance as a whole. Not every KPI or management dashboard measure is an MPM. Assess each measure against the definition and exclusions rather than classifying it from its label. Source: IFRS Foundation key terms.
For measures within scope, prepare the required single-note disclosures, including calculation and usefulness explanations and reconciliation to the most directly comparable specified total or subtotal. Capture income-tax and non-controlling-interest effects for reconciling items as required. Source: IFRS Foundation effects analysis.
Suppose management publicly presents “adjusted operating profit” excluding a restructuring charge. Do not assume that the name establishes the appropriate reconciliation or that the adjustment receives a standard tax rate. Document the definition, assess whether it is an MPM, trace the adjustment, and have the relevant specialists establish its tax and ownership effects. Give each approved measure an owner and version so public reporting and financial statements stay aligned.
Use transformation to strengthen disclosure controls
Assess whether existing cost-centre and expense data can support the required aggregation, disaggregation and relevant expense disclosures. Keep that assessment separate from changing the primary statement format. A missing attribute may require a source-system change, a controlled reporting adjustment or a new data collection process.
In the next four weeks, I would prioritise three outputs: an approved issues register, a dry-run comparative bridge and an inventory of potentially relevant performance measures. Then resolve data gaps, draft disclosures and perform a full reporting rehearsal with reviewers. This is a suggested project sequence, not a standard-mandated timetable.
AI may help compare mapping versions, identify missing attributes or draft questions for review. Use approved data and require links to the underlying evidence. Accounting conclusions, disclosure completeness and approval remain with the finance team.
Finally, maintain a technical update log. The IASB announced in July 2026 that it planned to propose amendments concerning specific tax charges. That announcement is not an issued amendment. Verify the status of proposals, implementation materials and agenda decisions at the date of sign-off, and distinguish tentative discussions from applicable requirements. Source: IASB July 2026 decisions.
The strongest outcome is more than a compliant layout: it is a reporting process in which every significant number has a clear origin, an approved treatment and an accountable owner.
Personal educational perspective, independent of my employer. All business examples are fictional and illustrative. Proposed workflows are not claims of completed deployments or measured results. Apply professional judgment and your organisation’s policies. Technical overview checked against linked IFRS Foundation materials on 21 October 2026; not a complete statement of IFRS requirements or accounting advice. Read the applicable standard and current authoritative materials, and obtain entity-specific advice before implementation.