Jonas Adam Mohamed Osman Abdelghafour

IFRS quantitative finance series

IFRS 9 ECL Backtesting: What Banks Should Test

A single comparison of total provision with realised write-offs cannot validate an IFRS 9 framework. Losses emerge over different horizons, portfolios change, recoveries arrive late and reporting estimates incorporate information that was available at each historical date.

By Jonas Adam Mohamed Osman Abdelghafour · Published 1 September 2026 · Independent educational analysis

Test components and decisions

Backtesting should cover PD calibration, discriminatory power, LGD amount and timing, EAD drawdowns, staging entry, cures, scenarios and overlays. Component tests explain why total ECL differs from outcome and reduce the chance that offsetting errors create a misleading pass.

Use vintage-consistent evidence

A fair test freezes the model, data and information set available at the reporting date, then follows exposures through the relevant horizon. Outcome windows must match twelve-month or lifetime objectives and account for incomplete recovery cycles.

Translate findings into action

Threshold breaches should lead to diagnosis, not automatic recalibration. The response may be monitoring, data correction, segmentation change, parameter redevelopment or temporary adjustment. Validation conclusions should be connected to financial-reporting materiality.

Quantitative expression

Backtest error = realised discounted cash shortfall − reporting-date expected cash shortfall

Implementation controls

Important: This article explains quantitative and reporting architecture. Banks must apply the complete IFRS requirements, relevant jurisdictional rules and entity-specific accounting policies.

Primary references

Related articles