IFRS 9 vs IAS 39: Key Differences in Classification, Impairment and Hedge Accounting

For CFOs, finance controllers, and risk teams at banks and corporates in the GCC and beyond — how these two standards diverge, what it means for your P&L, and why getting it wrong costs more than you think.

✓ Written by Prima Consulting’s advisory team  ·  ✓ Serving GCC, Europe & APAC  ·  ✓ Actuaries + CPAs + CFAs

TL;DR

The debate over IFRS 9 vs IAS 39 comes down to one idea: when do you recognize a loss? IAS 39 waited for proof. IFRS 9 requires you to anticipate it. This article covers seven concrete differences — classification logic and the business model test, the SPPI test, the expected credit loss framework, hedge accounting changes, reclassification rules, available-for-sale treatment, and transition impact on capital. It also covers what these shifts mean for GCC banks operating under SAMA and CBUAE oversight, and what the UAE’s expired prudential filter means for balance sheets right now. ACCA and CFA candidates studying financial instrument accounting will find the classification and impairment sections directly applicable to exam-level questions. Read it through once, then pass it to your team before the next reporting cycle.

This article covers seven concrete differences between IFRS 9 and IAS 39 — from classification logic and the SPPI test, to the expected credit loss framework and hedge accounting changes. It also covers the specific regulatory implications for banks operating under SAMA and CBUAE oversight, including the capital impact of the UAE prudential filter that expired at end-2024.

IFRS 9 vs IAS 39: Side-by-Side Comparison

Before going into each difference, here’s the full picture in one place. This table is what most comparison searches are actually looking for.

The sections below go through each row in detail — with numbers, worked examples, and the GCC-specific context that generic IFRS explainers skip entirely.

What Did IFRS 9 vs IAS 39 Actually Change?

IAS 39 governed financial instruments for nearly two decades. It had structure, categories, and also one critical flaw: it forced banks to wait for a loss to happen before they could fully book it.

The 2008 financial crisis made that flaw impossible to ignore. Regulators watched institutions carry loans at full value right up to default. The G20 pushed hard for change. The IASB responded with IFRS 9, published in its final form in July 2014 and mandatory from January 1, 2018.

Here’s what this article covers:

• How financial asset classification went from four categories to three, and why the logic changed completely
• Why the impairment model shift is the biggest operational change for any bank — and why some GCC institutions are still not fully through it
• Where hedge accounting got simpler, and where a critical IAS 39 carve-out still applies to GCC bank portfolios today
• What happened to retained earnings on January 1, 2018 — and what UAE banks face now that the CBUAE prudential filter is gone

Prima Consulting’s IFRS 9 advisory services team has worked through this transition with banks and corporates across the GCC and Europe. The differences below aren’t just accounting mechanics — they hit your P&L, your capital ratios, and your conversations with regulators.

IFRS 9 vs IAS 39: Financial Asset Classification

Under IAS 39, your finance team had to classify financial assets into one of four buckets: Fair Value Through Profit or Loss (FVTPL), Held-to-Maturity (HTM), Loans and Receivables, and Available-for-Sale (AFS). The tainting rules alone — where selling a single HTM asset could force reclassification of your entire HTM portfolio — made the system punishing.

IFRS 9 cuts that down to three categories: amortized cost, fair value through other comprehensive income (FVOCI), and FVTPL. But the real shift isn’t the number of categories. It’s how you get there.

How the Business Model Test Works

IFRS 9 starts with a question: how are you managing this asset? If you’re holding it to collect contractual cash flows, it goes to amortized cost. If you’re holding it to collect and to sell, it goes to FVOCI. Everything else defaults to FVTPL.

This sounds clean. In practice, the business model assessment requires documented intent and consistent application. That’s where smaller GCC banks often get caught — regulators ask for evidence of the assessment, not just an assertion of the outcome.

What the SPPI Test Actually Checks

After the business model test, IFRS 9 introduces the SPPI test: do the contractual cash flows represent solely payments of principal and interest? If yes, the asset can qualify for amortized cost or FVOCI. If no, it lands at FVTPL by default.

This gate didn’t exist under IAS 39. Under the old standard, financial instrument classification was largely driven by management intent. You decided where an asset went based on purpose and holding period. The contractual terms weren’t the primary gate.

Now they are. And for Islamic finance instruments — Sukuk, Mudarabah structures, profit-sharing contracts common across Saudi Arabia and the UAE — the SPPI test creates real classification ambiguity that conventional IFRS guidance doesn’t resolve cleanly. More on that in Difference 6.

For a full breakdown of how financial asset classification connects to impairment calculation, see IFRS 9 Financial Instruments explained.

IAS 39 Incurred Loss vs IFRS 9 Expected Credit Loss

This is the one. No other difference between IFRS 9 and IAS 39 hit bank P&Ls harder on day one.

A study covering 53 GCC banks from 2012 to 2020 found that loan loss provisions rose significantly after IFRS 9 adoption, even as nonperforming loan ratios decreased. That’s not a contradiction. It’s exactly what forward-looking provisioning looks like — you book more before things go wrong, so the spike at default is smaller.

IAS 39 Incurred Loss Model: Why It Failed

Under IAS 39, you could only recognize impairment when “objective evidence” existed. A missed payment. A borrower downgrade. A restructuring event. Before that trigger, the loan stayed clean on your books.

The problem is that credit deterioration starts months, sometimes years, before a default event. Regulators watching banks in 2008 saw portfolios that looked healthy right until they collapsed. IAS 39’s incurred loss model didn’t cause the crisis — but it made losses less visible, longer. The IASB’s own post-crisis review called it “too little, too late.”

IFRS 9 Expected Credit Loss: The Three-Stage Approach

IFRS 9 replaced the incurred loss model with a 3-stage ECL framework. The staging logic is straightforward; the calibration is where the work lives.

Stage 1 assets performing loans with no significant increase in credit risk, carry a 12-month ECL provision from day one. No trigger needed. No loss event required. That’s the core difference from IAS 39: under the old standard, a Stage 1 loan would carry zero provision as long as it was performing.

Stage 2 is where most of the controversy sits. IFRS 9 doesn’t define exactly when a “significant increase in credit risk” (SICR) occurs. You define it. But regulators will scrutinize that definition hard, particularly in the GCC, where SAMA and CBUAE have both issued guidance on minimum SICR indicators.

For teams building or reviewing ECL models, IFRS 9 impairment calculation resources walk through the PD, LGD, and EAD mechanics in detail.

Also worth flagging: as of September 2025, the Bank of England’s PRA identified model risk as still elevated across major banks applying IFRS 9. The concern isn’t the standard itself — it’s how banks apply judgment within it. GCC regulators are watching the same pattern.

See how Prima Consulting’s IFRS 9 advisory team approaches ECL model validation and SICR threshold calibration for GCC institutions.

Hedge Accounting: How IFRS 9 Changed the Effectiveness Test

Here’s where most summaries of IFRS 9 vs IAS 39 get lazy: they say hedge accounting “improved.” That’s true but incomplete.

IAS 39’s hedge accounting requirements were notoriously rigid. The 80–125% effectiveness test — where a hedge had to demonstrate retrospective effectiveness within that band at every reporting date — disqualified hedges that were economically sound but mathematically imperfect. Many real-world risk management strategies simply couldn’t qualify.

What Changed With Effectiveness Testing

IFRS 9 replaced the 80–125% retrospective test with an objectives-based test. The question is no longer “does this hedge fall inside a numerical band?” It’s “is there an economic relationship between the hedging instrument and the hedged item, and does that relationship reflect the entity’s actual risk management strategy?”

That’s genuinely better. More corporate treasury teams can now apply hedge accounting to strategies they’ve been running for years without the accounting benefit. Non-financial items — a commodity purchase, a construction contract — can now be designated as hedged items for specific risk components. IAS 39 didn’t allow that.

What didn’t change: hedge accounting under IFRS 9 still requires formal designation and documentation. And here’s the detail that catches GCC bank teams off guard. Portfolio hedging of interest rate risk — which most GCC banks use — still falls under IAS 39’s carve-out mechanism, not IFRS 9’s hedge accounting chapter. That carve-out remains active today. IFRS 9 allows entities to elect continuing use of IAS 39 hedge accounting requirements for portfolio fair value hedges, and many GCC banks have made exactly that election.

So when you’re asking whether your bank is under IFRS 9 or IAS 39 hedge accounting — the answer may legitimately be both, depending on the hedge type.

For context on how IFRS 9’s hedging model interacts with insurance contract accounting, the comparison in IFRS 17 vs IFRS 9 is worth reading.

IAS 39 Available-for-Sale vs IFRS 9 FVOCI: What Actually Changed

You might think the elimination of the Available-for-Sale category is a small technical change. It isn’t.

Under IAS 39, AFS was a catch-all: unrealized gains and losses went to other comprehensive income (OCI) and recycled to profit or loss when you sold the asset. This gave banks flexibility to hold equity and debt securities without P&L volatility during the holding period.

Fair Value Through OCI Under IFRS 9

IFRS 9 replaces AFS with two distinct treatments. Debt instruments that pass the SPPI test and are held under a mixed business model go to FVOCI — and gains and losses do recycle to P&L on disposal, similar to IAS 39.

Equity instruments are different. You can elect FVOCI for equity holdings not held for trading, but those gains and losses do not recycle to P&L. Ever. They stay in equity permanently. That’s a material change for any bank or corporate with a large equity portfolio, because impairment gains recognized in OCI under IAS 39 could eventually flow back to income. Under IFRS 9, that route is closed.

One more difference that often gets missed: under IAS 39, AFS debt instruments were subject to impairment testing, and impairment losses recycled from OCI to P&L on trigger. Under IFRS 9 FVOCI for debt, ECL is recognized through P&L directly — the OCI balance stays clean, reflecting fair value movements only. The accounting mechanics are genuinely different, not just a renaming exercise.

Reclassification of Financial Assets: IAS 39 vs IFRS 9

IAS 39 allowed reclassification in certain circumstances — moving assets out of the FVTPL category, or out of HTM under specific conditions. The tainting rules made this expensive, but the option existed.

Under IFRS 9, reclassification of financial assets is only permitted when the business model changes. That’s it. Not a change in market conditions. Not a management decision to shift strategy temporarily. The business model itself must change in a way that is significant and demonstrable to external parties.

In practice, such changes are rare. IFRS 9 expects that once you’ve documented your business model, it stays. This reduces opportunistic reclassification — which is intentional. But it also means that strategic pivots, like shifting a bank’s lending book from hold-to-collect to a more active sales strategy, trigger a full reclassification event with P&L and disclosure consequences.

Reclassification of financial liabilities under IFRS 9 isn’t permitted at all. That matches IAS 39’s treatment and won’t surprise most teams.

The SPPI Test: What IFRS 9 Added That IAS 39 Never Required

We touched on the SPPI test under Classification. It deserves its own section because it’s the element of IFRS 9 vs IAS 39 that catches teams off guard most often, and causes the most audit exposure in GCC portfolios specifically.

Under IAS 39, classification was largely driven by intent. The contractual terms of the instrument weren’t the primary gate. IFRS 9 changed that. Now, even if your business model points to amortized cost, the asset fails classification unless its cash flows are solely payments of principal and interest on the outstanding principal amount.

Any feature that modifies time value of money, introduces leverage, or creates exposure to non-credit risk can knock an instrument to FVTPL. That introduces income volatility that most CFOs would prefer to avoid.

Here’s a question worth sitting with: how many instruments in your current portfolio have you formally run through the SPPI test? Not the ones originated after 2018 — the ones that were already on the books when you transitioned.

SPPI Test and Islamic Finance Instruments

For GCC institutions, the SPPI test creates real classification problems that generic IFRS guidance doesn’t address. The instrument-level outcomes break down like this:

• Ijarah Sukuk — typically pass the SPPI test, provided the profit rate mechanism mirrors conventional interest on the outstanding balance. Amortized cost classification is usually achievable.
• Wakala Sukuk — outcome depends on structure. Where returns are fixed and tied to an underlying pool of assets generating conventional-style cash flows, SPPI pass is generally supportable. Where returns are variable and linked to asset performance, the test gets harder.
• Murabaha receivables — usually pass, as the deferred profit is economically equivalent to interest on principal.
• Mudarabah and Musharaka instruments — typically fail the SPPI test. Returns depend on profit-sharing rather than fixed contractual cash flows. That means FVTPL, which introduces P&L volatility most finance teams don’t want. If your GCC portfolio includes these structures and you haven’t formally documented the SPPI outcome for each, that’s an audit exposure waiting to surface.

Zero competitor content covers Islamic finance SPPI classification at instrument level with this specificity. It’s also one of the questions Prima’s GCC clients ask most often, because the consequences of getting it wrong are immediate and visible on the income statement.

See IFRS 9 compliance process architecture for how to build the SPPI review into your standard origination workflow so new instruments get tested before booking, not during the audit.

IFRS 9 Transition: Day-One Capital and P&L Impact

When banks moved from IAS 39 to IFRS 9 on January 1, 2018, most applied the modified retrospective approach — no restatement of prior periods, but an opening adjustment to retained earnings and equity on transition date.

That opening hit was real. The move from incurred to expected loss provisioning meant booking provisions that under IAS 39 wouldn’t have been recognized yet. For some banks, that single day-one adjustment wiped out a noticeable portion of retained earnings.

IFRS 9 Transition: How the Day-One Adjustment Was Booked

Most banks applied the modified retrospective method, which means no restatement of prior periods. The entire transition adjustment hit retained earnings on January 1, 2018 — one date, one entry.

The journal entry is straightforward:

Dr Retained Earnings [Opening ECL provision amount]
Cr Loss Allowance [Same amount]

For a bank with a large retail loan portfolio, that single entry could represent hundreds of millions in retained earnings reduction. No P&L impact on transition date — but the equity hit was immediate and visible to regulators, investors, and rating agencies from day one.

How GCC Banks Felt the Day-One Hit

Research across 53 GCC banks confirmed that loan loss provisions rose materially post-transition, with direct effects on solvency ratios and capital adequacy. European regulators offered a five-year phase-in to allow banks to add back ECL transition adjustments to CET1 capital gradually. About 70% of European banks used this arrangement through 2020–2021.

In the UAE, the CBUAE implemented a similar mechanism. The prudential filter allowed banks to phase in IFRS 9 transition impacts on regulatory capital over five years — 100% add-back in 2020, tapering through 75%, 50%, and 25% in subsequent years, down to zero by January 1, 2025. The CBUAE’s own rulebook confirms the filter applied to Stage 1 and Stage 2 ECL provisions only, and expired fully at end-2024.

That filter is now gone. UAE banks no longer have a regulatory buffer softening the capital impact of IFRS 9 provisioning. Full ECL recognition flows directly through balance sheets. If your UAE operation was relying on that phase-in to manage capital ratios, that relief is gone — and your CET1 ratios should already reflect it.

I’ll admit the data on how individual GCC banks have managed the post-filter position is patchy — the disclosure quality varies too much across jurisdictions to make a clean aggregate statement. What’s clear is that SAMA and CBUAE are asking harder questions about provisioning adequacy, and the answers need to be model-backed.

Prima Consulting’s advisory team has supported IFRS 9 transition and ongoing ECL validation for financial institutions across Saudi Arabia, the UAE, and the wider GCC. Learn more at IFRS 9 advisory firms.

Why IFRS 9 vs IAS 39 Still Matters for GCC Banks in 2026

Most articles on IFRS 9 vs IAS 39 treat the comparison as settled history. That’s the wrong way to read it.

Yes, the transition happened in 2018. But the ongoing challenge of operating under IFRS 9 — model validation, SICR calibration, scenario weighting, ECL documentation for auditors — is a live problem for every bank in the region. The ECB reviewed 51 banks in late 2023 and found widespread variation in how institutions capture emerging risks inside their IFRS 9 frameworks. GCC regulators are tracking the same patterns, and regulatory scrutiny in Saudi Arabia and the UAE has intensified since 2024.

SAMA, CBUAE, and What Regulators Now Expect

SAMA requires Saudi banks to run probability-weighted ECL scenarios. base, optimistic, pessimistic with documented macroeconomic overlays. The guidance issued in 2016–17 during the IFRS 9 consultation process made scenario documentation a governance requirement, not an optional best practice.

The CBUAE expects stage transfer criteria to be formally defined, independently validated, and consistently applied across portfolios. SICR criteria must be documented at the instrument level. Back-testing results need to be maintained and available for inspection. The days of treating IFRS 9 as a one-time implementation project are over — it’s a permanent, recurring governance obligation.

The EBA and Bank of England have both flagged concerns about banks using model overlays to delay full ECL recognition. GCC regulators are tracking the same risk. If your overlays aren’t connected to stage transfer methodology, expect questions.

For GCC banks still running IFRS 9 calculations on spreadsheets, the audit risks in IFRS 9 spreadsheets are worth reviewing. Version control failures and formula integrity gaps create material audit exposure that purpose-built systems eliminate. Most institutions I’ve seen struggle with ongoing IFRS 9 compliance aren’t struggling because the standard is hard. Their tools can’t keep up with what the standard requires.

That’s a fixable problem. But it requires a choice — between a purpose-built IFRS 9 software solution and a manual process that grows more fragile every quarter. The build vs buy IFRS 9 software TCO analysis is a useful starting point for that decision.

The shift from IAS 39 wasn’t just a standard change. It was a shift in philosophy, from reactive to anticipatory. Banks that internalized that in 2018 built better credit risk frameworks. The ones that treated it as a compliance box are now retrofitting culture into systems that weren’t designed for it.

What You Now Know

• Classification changed from four to three categories, driven by the business model test and the SPPI test — a fundamentally different logic than IAS 39’s intent-based approach. The SPPI test is the gate IAS 39 never had, and it catches GCC Islamic finance instruments that weren’t designed with IFRS 9 in mind.
• The ECL model replaced the incurred loss model, requiring banks to recognize expected losses across three stages from origination — not after a trigger event. SICR definition and scenario weighting are where GCC bank compliance actually lives.
• Hedge accounting got genuinely simpler for most entities, but the IAS 39 portfolio fair value hedge carve-out still applies to many GCC banks’ interest rate risk management — so IFRS 9 and IAS 39 hedge accounting can both be active on the same balance sheet.
• For UAE banks, the transition impact is now fully absorbed: the CBUAE prudential filter expired at end-2024. There’s no phase-in buffer left. CET1 ratios reflect the full ECL provisioning requirement from January 2025 onward.

The Difference Between Knowing and Doing

Most finance teams can now describe IFRS 9 vs IAS 39 at a headline level. The gap between knowing and doing is where reporting quality diverges — and where regulators find problems.

The right IFRS 9 approach for a GCC bank in 2026 isn’t about getting compliant once. It’s about building a framework that stays compliant as portfolios shift, as macro conditions change, and as regulators raise expectations. That’s a system design problem as much as an accounting one.

See how Prima Consulting’s IFRS advisory team handles IFRS 9 ECL model validation and ongoing compliance for banks across the GCC. Or, if you’re evaluating software, start with IFRS 9 compliance software options built specifically for the standard’s requirements.

Frequently Asked Questions

What is the main difference between IFRS 9 and IAS 39?

The biggest difference is impairment. IAS 39 used an incurred loss model — you recognized a loss only after a trigger event occurred. IFRS 9 replaced that with an expected credit loss model, requiring banks to provision for anticipated losses across three stages from origination onward. This changes P&L timing, capital ratios, and disclosure requirements in ways that remain live issues for GCC banks in 2026.

How did IFRS 9 change financial instrument classification from IAS 39?

IAS 39 had four classification categories with complex tainting rules. IFRS 9 simplified this to three categories — amortized cost, FVOCI, and FVTPL — determined by two objective tests: the business model test and the SPPI test. Classification under IFRS 9 reflects contractual cash flow characteristics and documented portfolio management intent, not management discretion alone.

What is the SPPI test under IFRS 9 and why does it matter?

The SPPI test checks whether contractual cash flows represent solely payments of principal and interest. Any instrument that fails this test must be measured at FVTPL, regardless of business model — introducing P&L volatility the entity may not want. This gate didn’t exist under IAS 39 and directly affects how Islamic finance instruments, structured products, and instruments with non-standard cash flow profiles are classified in GCC portfolios.

Why did IFRS 9 replace IAS 39 for GCC banks?

IAS 39’s incurred loss model delayed credit loss recognition until default evidence appeared — often far too late. After the 2008 financial crisis, the IASB designed IFRS 9 to require forward-looking provisioning. For GCC banks, SAMA and CBUAE have both made IFRS 9 compliance mandatory, with specific guidance on ECL scenario requirements, SICR documentation, and stage transfer criteria that go beyond the base standard.

How does IFRS 9 hedge accounting differ from IAS 39?

IAS 39 required an 80–125% retrospective effectiveness test at every reporting date, disqualifying many economically sound hedges. IFRS 9 replaced this with an objectives-based test focused on whether an economic relationship exists between the hedging instrument and hedged item. More real-world strategies now qualify. However, GCC banks that use portfolio fair value hedges for interest rate risk may elect to continue under IAS 39’s hedge accounting requirements — so both standards can apply simultaneously.

Is IAS 39 still applicable anywhere under IFRS 9?

Yes, in one specific area. IFRS 9 permits entities to continue applying IAS 39’s hedge accounting requirements for portfolio fair value hedges of interest rate risk — a strategy common at GCC banks. This carve-out remains active and is not automatically superseded by IFRS 9’s hedge accounting chapter. For all other areas — classification, measurement, impairment, derecognition — IAS 39 is fully replaced.

What specifically changed in the impairment calculation between IAS 39 and IFRS 9?

IAS 39 required a loss event before any provision. IFRS 9 eliminated that trigger entirely. A performing Stage 1 loan now carries a 12-month ECL provision from origination — no event needed. Stage 2 loans carry lifetime ECL once significant credit risk increase is identified. The practical result is front-loaded provisioning: balances look lower early in a loan’s life, which reduces the sharp spike at actual default that characterized IAS 39 portfolios.

How did the IFRS 9 transition affect GCC bank capital ratios?

The day-one ECL adjustment on January 1, 2018 reduced retained earnings, which lowered CET1 capital ratios for most GCC banks. In the UAE, the CBUAE’s prudential filter allowed banks to phase in this impact over five years — 100% add-back to capital in 2020, tapering to zero by January 1, 2025. That filter has now fully expired. UAE banks absorb the complete provisioning impact through their balance sheets with no regulatory buffer remaining. SAMA did not implement the same phase-in structure for Saudi banks.