Does IFRS 18 change recognition and measurement?

IFRS 18 is about presentation and disclosure. It replaces IAS 1 and changes the structure, subtotals, aggregation and disaggregation, MPM disclosures, comparatives, and digital-reporting work around financial statements.

What should finance teams build first for IFRS 18?

Finance teams should build a governed performance dataset that maps source ledger facts to IFRS 18 categories, public performance measures, comparative restatement, XBRL tags, and audit evidence.

IFRS 18 gives finance teams a cleaner ERP performance-data control layer.

The opportunity: build one trusted performance-data layer.

The best implementation plan starts before the reporting team redesigns the statement of profit or loss. Finance can define a reusable ERP and reporting data contract now: every income and expense fact should be classifiable under IFRS 18, traceable to the relevant management-defined performance measure conclusion, reusable for 2026 comparatives, and supportable in XBRL and audit review.

The deadline is close enough to matter. The IFRS Foundation says IFRS 18 is effective for annual reporting periods beginning on or after January 1, 2027, with earlier application permitted. ESMA is more direct about the operating burden: the standard may require changes to IT systems, management reports, communication strategy, and policies, and it must be applied retrospectively.

What changed, exactly.

IFRS 18 replaces IAS 1. The IASB focused especially on the statement of profit or loss: defined subtotals, categories for income and expenses, disclosures for management-defined performance measures, and stronger aggregation and disaggregation principles. The standard does not change recognition and measurement, but that does not make implementation light. Presentation logic still has to be fed by governed data.

The core output changes are concrete. Companies need new defined subtotals including operating profit and profit before financing and income taxes. They need to classify income and expenses across IFRS 18 categories. They need notes for management-defined performance measures, including how those measures compare with IFRS-defined measures. They also need comparative information, which makes 2026 data quality a live 2026 problem.

The 2026 market signal

The EU adopted IFRS 18 through Commission Regulation (EU) 2026/338, and the UK Endorsement Board approved IFRS 18 for UK use on December 10, 2025. ESMA then issued a public statement warning issuers to start early because 2026 comparative figures will need to be provided. This is now implementation work, not horizon scanning.

Market signals.

These public X posts are useful timing context: ESMA is pushing implementation discipline, the IFRS Foundation is pointing to EU and UK adoption, and the Interpretations Committee is already handling IFRS 18 application questions. The operative facts in this article rely on the cited IFRS, ESMA, EU, and UKEB sources.

ESMA post on its IFRS 18 implementation statement

Public X post: ESMA post on its IFRS 18 implementation statement.

IFRS Foundation post on IFRS 18 adoption in the EU and UK

Public X post: IFRS Foundation post on IFRS 18 adoption in the EU and UK.

IFRS Foundation post on June 2026 IFRIC agenda decisions involving IFRS 18

Public X post: IFRS Foundation post on June 2026 IFRIC agenda decisions involving IFRS 18.

The finance-ops implication: the P&L becomes a governed output.

IFRS 18 implementation works best when presentation, MPMs, comparatives, XBRL, and audit evidence are outputs of one governed performance dataset.

Under old habits, the chart of accounts carries too much meaning. One account implies department, function, expense nature, reporting caption, internal KPI treatment, and sometimes tax logic. IFRS 18 exposes why that is brittle. The same ledger fact may need legal-entity, segment, nature, function, main-business-activity, MPM, comparative, and XBRL meaning without polluting the statutory posting itself.

The better architecture is a classification layer above the ledger. The ledger remains the system of record for double-entry accounting. The IFRS 18 performance dataset becomes the controlled reporting product: versioned mapping rules, policy conclusions, source run IDs, public-communication references, reconciliation logic, and review evidence.

The data model finance actually needs.

An IFRS 18-ready row is not just an account balance. It carries the accounting source, the IFRS 18 category conclusion, the rule that produced that conclusion, whether a public MPM uses the fact, the comparative-restatement batch, the XBRL element or extension decision, and the evidence reference. That is what lets finance rerun the same logic for comparatives, filing, audit, and investor-question follow-up.

Example performance dataset row

{
  "performance_fact_id": "pf_2026_q4_004812",
  "entity_id": "uk_group_parent",
  "period": "2026-Q4",
  "source_system": "erp_gl",
  "journal_entry_id": "je_2026_12_31_01944",
  "gl_account": "7350",
  "functional_area": "sales_and_marketing",
  "expense_nature": "employee_compensation",
  "ifrs18_category": "operating",
  "ifrs18_mapping_rule_id": "ifrs18_map_v7_rule_031",
  "mpm_in_scope": true,
  "mpm_measure_id": "adjusted_operating_profit",
  "comparative_restatement_batch": "ifrs18_2026_dryrun_03",
  "xbrl_element": "ifrs-full:EmployeeBenefitsExpense",
  "amount_minor": 248901100,
  "currency_code": "GBP",
  "evidence_ref": "s3://close-evidence/ifrs18/2026-q4/pf_2026_q4_004812/"
}

The IFRS Foundation has already incorporated IFRS 18 changes into the IFRS Accounting Taxonomy 2025. ESMA also warns that the transition affects XBRL mapping and extension taxonomy elements. If tagging is treated as a filing-team afterthought, classification problems surface too late.

Control design for IFRS 18 readiness.

Risk	Control	Evidence
P&L category drift	Classify income and expense facts into operating, investing, financing, income taxes, and discontinued operations through a controlled mapping layer.	Mapping version, policy owner, effective date, approval, impacted accounts and dimensions.
Main business activity ambiguity	Document whether financing, investing, leasing, insurance, or similar activities change classification rules for the reporting group.	Accounting memo, entity scope, segment review, audit committee or controller approval.
MPM inventory gap	Maintain an inventory of public communications that contain subtotals of income and expenses and screen each measure against the IFRS 18 MPM definition.	Investor-deck archive, press release log, earnings script, measure owner, conclusion.
MPM reconciliation failure	Generate MPM reconciliations from the same reporting dataset used for financial statements and preserve tax and non-controlling-interest effects.	Reconciliation table, source report IDs, calculation rule, reviewer sign-off.
2026 comparative restatement scramble	Run a 2026 comparative data capture and restatement workstream before the first 2027 interim reporting cycle.	Dry-run package, exceptions, remediation tickets, restated comparative bridge.
Operating expense disaggregation weakness	Capture nature/function attributes at source or through reviewed allocation rules instead of late close spreadsheet tagging.	Attribute dictionary, allocation rule, source extract, exception approval.
XBRL extension churn	Review extension elements, anchors, and templates against IFRS 18 taxonomy changes before the first filing build.	Taxonomy mapping workbook, extension decision log, validation output, filing reviewer notes.
Uncontrolled manual reclasses	Force manual IFRS 18 presentation adjustments through reason-coded journals or reporting adjustments with owner and reversal status.	Adjustment ID, reason code, preparer, reviewer, recurring/non-recurring flag.

The MPM control is the one most teams underestimate. The June 2026 IFRIC Update shows live implementation questions around hypothetical income and expenses, public communications, labels of subtotals, and operating expense presentation. That means the control cannot be a one-time accounting memo. Finance needs an inventory, a review cadence, and evidence that public communications and financial-statement disclosures agree.

Implementation checklist before the 2027 reporting cycle.

Freeze the target statement of profit or loss architecture before redesigning reports: required subtotals, categories, main-business-activity logic, and industry-specific policy choices.

Create an IFRS 18 mapping table that sits above the chart of accounts and dimensions instead of hard-coding presentation logic into one report.

Inventory external communications that may contain management-defined performance measures: investor presentations, results releases, roadshow decks, annual-report front half, and website financial highlights.

Build a 2026 comparative dry run early enough to reveal missing attributes, uncontrolled reclasses, MPM gaps, and XBRL extension changes.

Separate internal management metrics from public MPMs, but keep enough metadata to prove why a measure is or is not in scope.

Add source-level attributes for operating expense by nature or function where the current ERP only captures a generic department or account.

Tie every IFRS 18 presentation adjustment to a close task, source extract, owner, timestamp, and reviewer evidence.

Test the filing pipeline: primary statement layout, note disclosures, MPM reconciliation, comparative restatement, taxonomy mapping, and validation output.

The operational target is simple: the first 2027 filing cycle should not be the first time finance sees an IFRS 18 P&L, MPM note, comparative bridge, or XBRL mapping. Run the dry run during 2026, while missing source attributes can still be fixed upstream.

Risks to clear early.

Treating IFRS 18 as a report-writer exercise after the chart of accounts, consolidation rules, and investor-reporting measures have already hardened.

Assuming operating profit is just the old internal subtotal with a new label.

Ignoring entities with specified main business activities until group consolidation, where classification evidence is hardest to reconstruct.

Letting investor relations publish adjusted subtotals without a finance-owned MPM inventory and reconciliation control.

Running 2026 comparatives through ad hoc Excel bridges that cannot be repeated or audited during 2027 reporting.

Waiting for tagging teams to discover that extension taxonomy elements and anchors need rework.

Keeping classification logic inside a report instead of making it a governed data contract.

All seven failures share one root cause: the company treats financial-statement presentation as a format decision instead of a controlled data-production process. Once 2026 comparative data, MPM reconciliations, and XBRL mappings enter the same workflow, that shortcut stops working.

What ERP buyers should ask vendors right now.

Can the ERP or reporting layer classify one income or expense fact into IFRS 18 categories without changing the legal ledger posting?

Can classification rules vary by reporting entity, segment, or specified main business activity while remaining version-controlled and auditable?

Can public performance measures be inventoried, approved, reconciled, and linked to external communications in one controlled workflow?

Can 2026 comparative information be rerun using the same rules that will produce 2027 reporting?

Can XBRL mappings, extensions, anchors, and validation evidence be stored alongside the disclosure dataset instead of in a separate filing-team workspace?

If the answer is mainly "export the trial balance and rebuild the P&L in reporting," the product is not handling the IFRS 18 control problem. It is shifting classification, MPM reconciliation, comparative restatement, and tagging evidence to late close.

Practical takeaway.

IFRS 18 can become a useful forcing function for cleaner performance data. The teams that do this well will build one controlled layer that maps ledger facts to IFRS 18 categories, public measures, 2026 comparatives, XBRL tags, and audit evidence. That gives controllers, reporting teams, investor relations, and auditors a shared version of performance truth before the 2027 filing cycle begins.