How to Audit a First-Time IFRS Adoption Under IFRS 1

You’re signing off on a Dutch mid-market client that just transitioned from Dutch GAAP to IFRS. The opening balance sheet was restated six months ago, but nobody documented why four of the fourteen optional exemptions were applied and two mandatory exceptions were ignored. The partner review is in two weeks. Your file has a gap the size of the transition adjustments themselves.

We see this pattern constantly. IFRS 1 gives entities over thirty optional exemptions designed to make transition cheaper, but each exemption carries conditions that create audit work. In our experience, most mid-market entities treat those exemptions as free passes rather than conditional relief, and that disconnect is where transition files fall apart. The standard trades accounting complexity for documentation complexity, and the documentation side almost always loses.

IFRS 1 requires a first-time adopter to prepare an opening IFRS statement of financial position at its date of transition, apply all effective IFRS standards retrospectively with specific mandatory exceptions and optional exemptions listed in IFRS 1.13 to 1.31, and disclose the impact of the transition on reported financial position and performance.

Key takeaways

How to verify the completeness of IFRS 1 transition adjustments against the mandatory exceptions in IFRS 1.14 to 17 and optional exemptions in IFRS 1 .D1 to D39
How to audit the opening IFRS balance sheet and reconciliation disclosures required by IFRS 1.24
How to document your assessment of which exemptions were applied and why that selection was appropriate
How to test the transition date adjustments that flow through to retained earnings under IFRS 1.11

What IFRS 1 actually requires from the entity and from you

Here is the mistake we see most often: an entity treats the opening IFRS balance sheet as a restatement exercise performed for convenience. It is not. IFRS 1.10 requires retrospective application of every IFRS standard effective at the end of the first IFRS reporting period, as if those standards had always applied. Every asset and liability gets remeasured. Equity components adjust accordingly. Miss this, and your transition file starts with the wrong premise.

IFRS 1 governs the first set of financial statements in which an entity adopts IFRS. IFRS 1.6 sets the core requirement: prepare and present an opening IFRS statement of financial position at the date of transition. That date is the beginning of the earliest comparative period presented. For a December 2025 year-end with one comparative year, the transition date is 1 January 2024. All cumulative adjustments hit opening retained earnings under IFRS 1.11 , or where IFRS 1 specifies, another category of equity.

What actually happens is that audit work on the opening balance sheet gets treated as a formality. It should not. ISA 510.6 requires sufficient appropriate evidence that opening balances contain no misstatements materially affecting the current period. For a first-time adopter, that means auditing the transition adjustments themselves, not just the closing balances. If the entity switched from Dutch GAAP to IFRS, every recognition difference becomes a transition adjustment you need to test: leases under IFRS 16 that were off-balance sheet under RJ 292, expected credit losses under IFRS 9 that were incurred-loss under RJ 290.

The timeline you need to understand

Most first-time adoptions follow a predictable timeline, and each stage creates specific audit evidence you should obtain. Twelve to eighteen months before the transition date, the entity runs a diagnostic phase to identify accounting differences between previous GAAP and IFRS. That diagnostic produces a gap analysis. Get it. It tells you which standards management considered and which adjustments they expect. If the entity skipped this step and went straight to preparing the opening balance sheet, your risk of missing adjustments is higher.

In the second stage, management makes its exemption elections, engages valuers for deemed cost measurements, recalculates lease liabilities under IFRS 16 , runs IFRS 9 expected credit loss models, and quantifies every adjustment. Each workstream should produce a working paper you can test. In theory, every exemption election gets a documented rationale before the opening balance sheet is finalised. In practice, most entities make elections informally and document after the fact, because IFRS 1 does not prescribe a format for the election record. We always request the election schedule before starting fieldwork, because reconstructing it later means you are reverse-engineering decisions that should have been contemporaneous.

Stage three is restating the full comparative year under IFRS and preparing the reconciliation disclosures. IFRS 1.21 requires at least one year of comparative information under IFRS. Not optional.

What the disclosures must show

A single-line “IFRS adjustments: €2.4M” entry in the reconciliation is the most common disclosure failure we see, and regulators have started rejecting it. IFRS 1.23 to 1.33 requires reconciliations of equity at the transition date and at the end of the last period reported under previous GAAP, plus a reconciliation of total comprehensive income for the last period under previous GAAP. Each adjustment needs a standard reference, an amount, and a plain-language label explaining what changed and why.

IFRS 1.23 also requires an explanation of how the transition affected reported financial position, financial performance, and cash flows. If the cash flow statement reclassifies items (operating to financing, for example, when IFRS 16 lease payments move to the financing section), that reclassification needs separate disclosure.

Mandatory exceptions you cannot waive

Hindsight adjustments are the single biggest red flag in transition files. An entity that changed an asset’s useful life from eight years to six at the transition date, using information that was not available when the original estimate was made, has violated IFRS 1.14 (b). That is not an IFRS correction. That is an error. Yet we see it in roughly one in three files, because the temptation to “clean up” old estimates during transition is strong, and the line between a genuine IFRS-required modification and a hindsight adjustment is thin enough that preparers cross it without realising.

IFRS 1.14 lists four categories of mandatory exception where retrospective application is prohibited. These exist because retrospective application would either require impossible reconstructions of historical data or allow entities to cherry-pick accounting outcomes using information they did not have at the time. You cannot accept a transition file that applies full retrospective treatment in any of these areas.

Derecognition ( IFRS 1 .B2 to B3) requires prospective application of IFRS 9 derecognition requirements from the transition date. Financial assets and liabilities derecognised under previous GAAP before the transition date stay derecognised. This matters for entities that factored receivables or transferred financial assets under less restrictive Dutch GAAP derecognition rules. In theory, no derecognised items get reinstated. In practice, we have seen entities attempt reinstatement because their new IFRS 9 analysis concluded that control was not transferred, without recognising that the mandatory exception prohibits revisiting that conclusion. Ask management to confirm no derecognised items were reinstated. If receivable factoring arrangements exist, obtain the pre-transition derecognition analysis and verify it was not revisited.

Hedge accounting ( IFRS 1 .B4 to B6) must be assessed at the transition date under IFRS 9 criteria. Hedging relationships that qualified under previous GAAP but fail to meet IFRS 9.6 .4 requirements at transition cannot be carried forward. Where hedging relationships do qualify, measure them at fair value at the transition date; any cumulative gain or loss goes to OCI or retained earnings depending on the hedge type.

Estimates ( IFRS 1.14 (b) and IFRS 1.16 ) cannot be revised with hindsight. Use the estimates made under previous GAAP at the relevant date, adjusted only where those estimates need modification under IFRS. The practical test: look at the date the estimate was originally made, and if the information used to change it was not available at that date, the change is hindsight. IFRS 1.16 contains a narrow exception where new information triggers a genuine correction, for example evidence that an estimate was an error under previous GAAP, but the burden of proof sits with the entity.

Classification and measurement of financial instruments ( IFRS 1 .B8 to B8C) requires the entity to assess business model and contractual cash flow characteristics at the transition date based on facts and circumstances at that date, not at original recognition. This avoids the impossible exercise of reconstructing historical intent for instruments that may have been on the books for years.

Optional exemptions and the audit risk they create

Most transition files we review have the same problem: the entity applied four or five exemptions but documented the rationale for none of them. IFRS 1 .D1 to D39 contains over thirty optional exemptions. Your job is to verify two things: that each applied exemption actually qualifies under its conditions, and that a documented rationale exists for applying or not applying each one. The file should tell a story about why this entity, with its specific fact pattern, made each election. Without that story, you are signing off on decisions you cannot reconstruct.

Deemed cost for PP&E ( IFRS 1 .D5 to D8B) is the most commonly applied exemption in European mid-market transitions because many Dutch GAAP entities lack historical cost records going back decades for real estate holdings. Fair value at the transition date substitutes for reconstructed historical cost under IAS 16 . Your audit risk: the fair value used as deemed cost needs an IFRS 13 fair value measurement that you can test. If the entity used an external valuation, assess the valuer under ISA 500.8 and ISA 620.12 . If management produced the valuation internally, test their assumptions. We have seen internal valuations that relied on a single comparable transaction from three years before the transition date; that is not a current fair value measurement, and IFRS 13.61 to 66 will not support it.

Business combinations ( IFRS 1 .C1 to C4) allow the entity not to restate past acquisitions under IFRS 3 . For entities acquired under Dutch GAAP pooling or purchase methods, this avoids what would often be an impossible exercise of retrospective fair value allocation. But IFRS 1 .C4 attaches conditions: acquisition classification must still be assessed under IFRS 3 , and any goodwill recognised under previous GAAP must be tested for impairment under IAS 36 at the transition date. Many files miss that impairment test. Goodwill from a 2015 acquisition amortised under Dutch GAAP gets frozen at its carrying amount, but IAS 36 impairment still applies. The AFM has flagged this gap repeatedly since 2022.

Cumulative translation differences ( IFRS 1 .D12 to D13) can be deemed zero at transition. Low-risk for entities with foreign operations. Verify the cumulative translation adjustment was reclassified to retained earnings and that all subsequent translation differences after the transition date follow IAS 21 .

Exemptions the entity chose not to apply also matter, and in our experience this is where the real risk hides. If an entity with significant lease liabilities decided not to apply the IFRS 16 exemption in IFRS 1 .D9B, which would have allowed measurement of lease liabilities at present value of remaining payments at transition with right-of-use assets measured at an equal amount, it must instead apply IFRS 16 fully retrospectively. That means reconstructing lease calculations from inception for every lease on the books. Verify the entity understood the implications of its exemption choices before accepting the transition file.

Employee benefits ( IFRS 1 .D10 to D11) permits recognising all cumulative actuarial gains and losses in retained earnings at the transition date, resetting the IAS 19 measurement. For entities with defined benefit pension obligations, common in Dutch and German subsidiaries, this can produce a large retained earnings adjustment. Obtain the actuary’s report at the transition date, verify the discount rate and mortality assumptions against IAS 19.83 to 86, and recalculate the net defined benefit liability. One common error: the entity uses the same actuarial valuation for both the transition date and the annual IAS 19 measurement without adjusting for the different measurement dates.

How the exemptions interact with each other

Some exemptions interact in ways that create compounding audit risk, and this is the kind of problem you will not find by testing exemptions in isolation. An entity that applies the deemed cost exemption for PP&E under IFRS 1 .D5 and also applies the business combinations exemption under IFRS 1 .C1 may end up with a mix of measurement bases: acquired PP&E from a 2016 business combination carried at Dutch GAAP cost, frozen under the business combinations exemption, while the parent’s own PP&E is carried at fair value under the deemed cost exemption. Permitted, but it creates a disclosure obligation under IFRS 1.29 . Users need to understand why different assets of the same class carry different measurement bases.

Cumulative translation differences interact with the business combinations exemption too. If the entity deems CTA zero at transition but the foreign operation was acquired in a past business combination, IFRS 1 .C2(f) requires treating the goodwill and fair value adjustments from that acquisition as assets and liabilities of the parent, not the foreign operation, for subsequent currency translation. Getting this wrong affects how disposal gains or losses are calculated if the foreign operation is subsequently sold. This is exactly the kind of second-order interaction that SALY with a methodology shield will not catch, because firms copy the transition policy template without modelling how exemption elections compound across standards.

Worked example: auditing a Dutch GAAP-to-IFRS transition

Client: Vermeer Coating Technologies B.V., a specialty coatings manufacturer based in Eindhoven. €68M revenue, December 2025 year-end. First IFRS financial statements. Transition date: 1 January 2024. Previously reported under Dutch GAAP.

1. Identify the transition date and confirm the opening balance sheet exists.

Vermeer’s first IFRS reporting period ends 31 December 2025 with one comparative year. Transition date: 1 January 2024. Verify the client prepared an opening IFRS balance sheet at that date.

Documentation note: record the transition date, the basis for determining it under IFRS 1.6 , and obtain the opening IFRS balance sheet as audit evidence. Cross-reference to the engagement letter confirming the first IFRS reporting period.

2. Obtain the exemption schedule.

Vermeer applied four optional exemptions: deemed cost for PP&E under IFRS 1 .D5, the business combinations exemption under IFRS 1 .C1, cumulative translation differences deemed zero under IFRS 1 .D12, and the IFRS 16 transition exemption under IFRS 1 .D9B. They did not apply the IFRS 9 classification overlay.

Documentation note: obtain management’s written schedule of exemptions applied and not applied, with rationale for each election. If no such schedule exists, request one before proceeding. This is the anchor document for your IFRS 1 work.

3. Test the deemed cost exemption for PP&E.

Vermeer owns a production facility in Eindhoven carried at €11.2M under Dutch GAAP, historical cost less accumulated depreciation. Management engaged Cushman & Wakefield, who assessed fair value at 1 January 2024 at €14.8M. The €3.6M uplift hits opening retained earnings.

Test the valuation: review the Cushman & Wakefield report against ISA 620.12 for competence, capability, and objectivity. Verify the valuation date matches the transition date. Check the methodology against IFRS 13.61 to 66 for level 2 or level 3 inputs. Test key assumptions including comparable transactions, discount rate, and remaining useful life. Recalculate the retained earnings adjustment.

Documentation note: file the valuation report, your ISA 620 assessment of the valuer, your review of key assumptions with cross-references to IFRS 13 , and the recalculated retained earnings impact of €3.6M.

4. Test the business combinations exemption and goodwill impairment.

Vermeer acquired a Belgian subsidiary, Claessens Pigments NV, in 2019 for €5.1M under Dutch GAAP purchase method. Goodwill of €1.8M was recognised and amortised to €0.9M at 1 January 2024. Under IFRS 1 .C1, Vermeer freezes this at €0.9M but must test for impairment under IAS 36 at the transition date.

Review management’s IAS 36 impairment assessment for the Claessens CGU. Value in use based on a five-year DCF at 9.2% WACC produced a recoverable amount of €4.1M versus a carrying amount of €3.7M including the €0.9M goodwill. Headroom of €0.4M is thin.

5. The complication: a customer concentration problem emerges.

During your testing, you discover that 38% of the Claessens CGU revenue comes from a single automotive customer whose contract expires in Q3 2025. Management’s DCF assumed stable revenue over the projection period. This is exactly the kind of judgment call that separates a filed impairment test from a tested one. You have two legitimate options. First, require management to run a scenario excluding that customer or modelling a 30% revenue decline in year two, which would likely eliminate the €0.4M headroom. Second, accept the base case but require expanded disclosure under IAS 36.134 (f) explaining the sensitivity to customer concentration. In our view, option one is the right answer because IAS 36.33 (b) requires assumptions that reflect the asset’s current condition, and a known contract expiry is a current condition. Reasonable practitioners disagree: some argue that the contract may be renewed and that modelling non-renewal is overly conservative rather than realistic. Both positions have merit, but the burden should fall on the entity to demonstrate why renewal is the reasonable assumption.

Documentation note: file the IAS 36 impairment model, your WACC verification, your sensitivity analysis on the terminal growth rate and customer concentration, and your conclusion on the €0.4M headroom. Flag both the thin headroom and the customer concentration risk for the subsequent period’s annual impairment test.

6. Verify the reconciliation disclosures.

IFRS 1.24 (a) requires an equity reconciliation at 1 January 2024 and at 31 December 2024, and a comprehensive income reconciliation for the year ended 31 December 2024. Verify Vermeer’s reconciliations are disaggregated by standard: IFRS 16 adjustment, IFRS 9 ECL adjustment, PP&E deemed cost uplift, goodwill amortisation reversal. Each line should identify the relevant IFRS standard and the amount.

Documentation note: obtain the reconciliation schedules, agree each adjustment to the underlying working papers, verify arithmetic, and confirm the total agrees to the difference between previous GAAP equity and IFRS equity at each date.

A completed transition file shows a reviewer that every exemption election was documented and tested, each linking to the specific IFRS 1 paragraph governing it, with reconciliation disclosures tying back to individual adjustment working papers. That is what a clean file looks like. Most do not start there, and that is fine, because the point of this work is to get them there before sign-off.

Practical checklist for your engagement file

Confirm the transition date per IFRS 1.6 and verify an opening IFRS balance sheet exists at that date
Obtain and file management’s written schedule of exemptions applied and not applied, with rationale for each election; request this document if it does not exist, and do not proceed without it
For each optional exemption applied, verify the conditions in IFRS 1 .D1 to D39 are met and the amounts are supportable: test valuations, review business combination classifications, recalculate lease liabilities
For each mandatory exception in IFRS 1.14 to 17, verify that retrospective treatment was not applied where prohibited, with particular attention to hindsight on estimates and reinstatement of derecognised financial instruments
Test the retained earnings impact by reconciling total transition adjustments to the difference between previous GAAP equity and IFRS equity at the transition date
Verify IFRS 1.24 reconciliation disclosures are disaggregated by standard, each line ties to a working paper, and total comprehensive income for the last previous GAAP period is reconciled
Check exemption interactions: when multiple exemptions are applied, verify that the combined effect does not create undisclosed mixed measurement bases or translation difference errors

Common mistakes

These are the three failures we encounter most frequently, ranked by how often they result in regulatory comment or restatement risk.

Missing the goodwill impairment test at transition: applying the business combinations exemption under IFRS 1 .C1 freezes goodwill at its carrying amount but does not exempt from IAS 36 impairment testing at the transition date. In theory, every firm knows this. In practice, teams just roll it forward from the Dutch GAAP carrying amount without running the IAS 36 test, because the exemption language feels like it covers everything. It does not.
Hindsight adjustments disguised as IFRS corrections: IFRS 1.14 (b) prohibits revising estimates with hindsight. Changing a useful life or a provision estimate at the transition date using information unavailable when the original estimate was made is not an IFRS adjustment. It is an error. The reason this keeps happening is that transition creates a perceived “clean slate” opportunity, and preparers conflate correcting historical mistakes with applying a new framework.
Incomplete reconciliation disclosures: IFRS 1.24 requires reconciliations of equity and comprehensive income, disaggregated with sufficient detail for users. A single-line “IFRS adjustments” entry without standard references and individual amounts fails this requirement. We flag this in nearly half the files we review.

Fair value measurement glossary entry: covers the IFRS 13 hierarchy relevant to deemed cost valuations under IFRS 1 .D5
IFRS 16 lease calculator: use this to verify lease transition adjustments when the entity applies IFRS 16 retrospectively instead of the IFRS 1 .D9B exemption

Related guides:

Put audit concepts into practice with these free tools:

Frequently asked questions

What is the transition date under IFRS 1 ?

The transition date under IFRS 1 is the beginning of the earliest comparative period presented in the entity’s first IFRS financial statements. For a December 2025 year-end with one comparative year, the transition date is 1 January 2024. The entity must prepare an opening IFRS statement of financial position at this date.

What are the mandatory exceptions under IFRS 1 ?

IFRS 1.14 lists four categories of mandatory exception where retrospective application is prohibited: derecognition of financial instruments, hedge accounting, accounting estimates (no hindsight adjustments), and classification and measurement of financial instruments. The entity cannot choose to apply full retrospective treatment in these areas.

Can an entity use fair value as deemed cost under IFRS 1 ?

Yes. The deemed cost exemption for property, plant and equipment under IFRS 1 .D5 to D8B allows an entity to use fair value at the transition date as deemed cost instead of reconstructing historical cost under IAS 16 . This is the most commonly applied optional exemption in European mid-market transitions.

What reconciliation disclosures does IFRS 1 require?

IFRS 1.24 requires reconciliations of equity at the transition date and at the end of the last period reported under previous GAAP, plus a reconciliation of total comprehensive income for the last period under previous GAAP. Each adjustment needs a label, a standard reference, and an amount.

Does the business combinations exemption exempt goodwill from impairment testing?

No. Applying the business combinations exemption under IFRS 1 .C1 freezes goodwill at its carrying amount at the transition date, but IAS 36 impairment testing must still be performed at the transition date. Many files miss this requirement, which the AFM has flagged in several first-time adoption files reviewed since 2022.