For an Australian for-profit entity with a 30 June balance date, the first financial statements prepared under AASB 18 will cover the year ending 30 June 2028. That sounds comfortably distant.
It isn’t. IFRS 18 must be applied retrospectively, so comparatives have to be restated. For a June-year-end entity, that comparative period – 1 July 2026 to 30 June 2027 – is already underway. For December balance dates, it started in January. The data needed to present a restated AASB 18 income statement is being posted to your general ledger right now, under a chart of accounts that was never designed to produce it.
This is the real IFRS 18 deadline, and it has passed.
What IFRS 18 actually changes
IFRS 18 Presentation and Disclosure in Financial Statements replaces IAS 1, issued locally as AASB 18. It does not change recognition or measurement, no asset is revalued, no revenue restated. What changes is structure, and structure has turned out to be the harder problem. Three shifts matter most.
Five mandatory categories, across two statements.
IFRS 18’s changes land in two statement, profit or less and cash flows, and the five categories cut across both. Every item of income and expense must be classified as operating (main business activities, and the default for anything that doesn’t sit elsewhere), investing (returns from assets held largely independently of operations), financing (liabilities that involve only the raising of finance, plus interest on other liabilities), income taxes, or discontinued operations, with distinct rules for entities that have specified main business activities – banks, insurers and investment property groups among them. Two subtotals become mandatory: operating profit, and profit before financing and income taxes. The cash flow statement changes in step: operating profit replaces profit before tax as the starting point for the indirect method, and the policy choices for classifying interest and dividends disappear. The flexibility AASB 101 permitted is gone.
Management-defined performance measures enter the audited accounts, the change most likely to catch teams out.
Adjusted EBITDA, underlying profit and similar measures used in public communications must be disclosed in a single dedicated note, reconciled to the nearest IFRS-defined subtotal, with the tax and non-controlling interest effect of every adjustment made explicit. For the first time these measures sit inside the audited financial statements rather than beside them in a results presentation.
Stricter aggregation and disaggregation.
Describing a material item as ‘other’ no longer passes. Every grouping decision needs a rationale that survives review.
Why Australia’s version of this problem is harder
Most jurisdictions face IFRS 18 alone. Australian finance teams face it inside a compressed stack of concurrent reforms.
The effective dates are staggered by entity type. For-profit entities report from periods beginning on or after 1 January 2027; not-for-profit private and public sector entities and superannuation entities applying AASB 1056 have until 1 January 2028. Separately, Exposure Draft 341 proposes aligning Tier 2 entities under AASB 1060 from 1 July 2030. A group containing a listed parent, a Tier 2 subsidiary and a not-for-profit arm will run two presentation regimes side by side for years, with intercompany balances that still have to reconcile.
Then there is climate. Group 2 entities under AASB S2 began their first mandatory reporting periods on 1 July 2026, with Group 3 following from 1 July 2027 and Scope 3 emissions mandatory from each entity’s second year. The same finance function rebuilding its income statement is simultaneously standing up assured climate disclosure. To a regulator or auditor these are not separate workstreams, climate-related costs still have to land in one of the five categories, and climate scenario assumptions still have to reconcile with the projections underpinning impairment and going concern.
ASIC published its financial reporting, audit and sustainability focus areas for FY 2026–27 in May 2026, with continued emphasis on areas requiring significant judgement. Advisers are already telling clients they should be well progressed on AASB 18. The transition will not stay outside the surveillance frame for long.
Where the pain actually lands
The technical interpretation is not the bottleneck; the guidance is extensive and free. The bottleneck is execution across a portfolio of entities, and it concentrates in four places.
Chart of accounts mapping.
Entity A records depreciation in account 6110; Entity B uses 5420. Both must map to the same IFRS 18 category. Done entity by entity, that becomes dozens of parallel mapping exercises, each an opportunity for divergence.
Comparative restatement.
IFRS 18 requires a reconciliation between restated comparatives and the amounts previously presented under AASB 101 – line by line, showing where each item went. Rebuilt manually, that is one to two days per entity; across fifty entities, a quarter of a person-year of pure rework.
MPM defensibility.
Auditors will ask how each measure was calculated, when the formula last changed, and why. A spreadsheet cannot answer that. A version-controlled system can.
What a fit-for-purpose reporting architecture looks like
This is where the distinction between workflow tools and compliance architecture becomes commercially significant. Automating a broken process faster does not produce classification consistency; enforcing structure does.
ONESOURCE Statutory Reporting is built around that enforcement model. The five categories are defined once in a central template and inherited by every entity in the hierarchy, so classification logic cannot fragment. Chart of accounts mapping is defined once and cascades. Change it centrally and every entity updates, with validation rules flagging mismatches before they reach a reporting pack. Comparative restatement runs as an automated roll-forward that generates the line-by-line AASB 101–to–AASB 18 reconciliation with full traceability. MPM formulas are pre-linked to income statement line items rather than copy-pasted, with an audit trail recording who changed what and when.
For Australian groups, integrating AASB 18 templates with climate disclosure requirements matters more than any single feature: it means one reclassification exercise rather than two disconnected projects competing for the same team.
The proof is operational rather than theoretical. Thomson Reuters runs more than 80 of its own ANZ, India and MENA entities on the platform, and Forrester’s Total Economic Impact study found 68 per cent efficiency gains and a 75 per cent productivity improvement, from eight entities per person to thirteen, with 84 per cent ROI over three years.
What should finance teams do next? Five steps to start now.
- Fix your true deadline. Work back from your balance date to the first day of your comparative period. Confirm which effective date applies to each entity, 2027, 2028, or the proposed 2030 Tier 2 alignment, and identify where regimes will overlap.
- Run a classification gap assessment. Map every current income statement line to the five categories and flag the items where the answer is genuinely arguable. Determine whether any entity has specified main business activities, since that changes the investing and financing rules.
- Inventory and stress-test your MPMs. List every adjusted measure used in results announcements, investor decks and covenant calculations. Document each calculation, draft its reconciliation, and check whether covenants, KPIs or incentive arrangements reference subtotals about to change definition.
- Consolidate chart of account governance. Build one group-level mapping table rather than per-entity mappings, and confirm your platform can apply it consistently and evidence that it did.
- Run a parallel period before it counts. Produce one entity’s statements under both AASB 101 and AASB 18 for a closed period and take the output to your auditor – while there is still time to change your architecture rather than your disclosures.
The organisations that will find 2027 straightforward are not the ones with the best technical papers. They are the ones whose systems already enforce the answer.
