IAS 37 vs IFRS 9: When a Financial Liability Provision Meets ECL
Author
Sai Manikanta Pedamallu
Published
Reading Time
18 min read
Table of Contents
IAS 37 vs IFRS 9: When a Financial Liability Provision Meets ECL
By Sai Manikanta Pedamallu (ACCA, CMA US, CSCA US, CGMA, ACMA, Dip IFRS, M.Com, MBA, MA)
Lead Instructor, Global Fin X | www.globalfinx.in/manikanta
Two standards. Two recognition thresholds. One obligation. The interaction between IAS 37 and IFRS 9 creates some of the most technically demanding classification questions in IFRS, particularly around financial guarantees, loan commitments, and obligations that sit on the boundary between a provision and a financial instrument.
The threshold difference matters enormously in practice. IAS 37 recognises a provision only when outflow is probable, meaning more than 50%. IFRS 9's ECL model recognises a loss allowance from day one, probability-weighted across all possible outcomes, without requiring any single outcome to be probable. The same economic obligation, classified under different standards, can produce materially different liability amounts on the balance sheet at the same reporting date.
This post covers the scoping hierarchy that determines which standard applies, the key instruments sitting at the boundary, the measurement consequences of the classification choice, and why the IFRS Interpretations Committee addressed this in 2025.
The Scoping Hierarchy: Which Standard Governs?
IAS 37 applies only when no other IFRS standard covers the specific obligation. Paragraph 5 of IAS 37 explicitly excludes obligations covered by IFRS 9, IFRS 15, IFRS 16, IAS 12, IAS 19, and IFRS 17.
The priority sequence for a guarantee or credit-related obligation:
Step 1: Is it a financial guarantee contract under IFRS 9?
Step 2: If not, is it an insurance contract under IFRS 17?
Step 3: If not, is it within any other specific IFRS standard?
Step 4: Only if none of the above: IAS 37 applies.
Getting Step 1 right is where most of the complexity sits.
Financial Guarantee Contracts: IFRS 9 Definition
A financial guarantee contract is defined in IFRS 9 as a contract that requires the issuer to make specified payments to reimburse the holder for a loss it incurs because a specified debtor fails to make payment when due in accordance with the original or modified terms of a debt instrument.
Three elements matter:
Specified payments to reimburse a loss: The guarantee pays out based on a credit event, not based on any other performance condition.
A specified debtor failing to make payment: The trigger is credit default, not commercial underperformance or breach of a non-financial obligation.
A debt instrument: The underlying obligation that the debtor fails to service must be a debt instrument, not a trade payable, lease, or performance obligation.
If all three are present, IFRS 9 governs. If any element is absent, the guarantee is assessed under IFRS 17 or IAS 37.
What Qualifies as a Financial Guarantee Contract
A parent company guaranteeing its subsidiary's bank loan: the parent will pay the bank if the subsidiary defaults on a debt instrument. This is a financial guarantee contract under IFRS 9.
An Indian NBFC providing a credit enhancement guarantee on a securitised loan pool: the NBFC reimburses investors for credit losses on the underlying debt instruments. IFRS 9.
A company guaranteeing another entity's debenture issuance: the guarantor will pay holders if the issuer defaults on the debt. IFRS 9.
What Does Not Qualify
A performance guarantee to a client: the guarantor pays if the entity fails to complete a construction project or deliver services. The trigger is performance failure, not credit default on a debt instrument. This is not a financial guarantee contract under IFRS 9. IAS 37 applies if the obligation qualifies as a provision, or IFRS 17 if it meets the insurance contract definition.
A letter of credit issued by a bank on behalf of a buyer: depends on whether the underlying obligation is a debt instrument or a trade payable. The IFRS Interpretations Committee discussed this boundary at its April 2025 meeting, noting that the term "debt instrument" in the financial guarantee contract definition has produced diversity in practice. Some entities include trade payables within the definition; others do not.
The IASB discussed this diversity in April 2024 and the IFRIC concluded its deliberations in March 2025, noting that judgment is required in applying the definition to specific facts. The agenda decision confirmed the priority of IFRS 9 where the guarantee meets its definition, and IAS 37 as the fallback where it does not.
Measurement Consequences: The Threshold Difference
The difference between IFRS 9 and IAS 37 is not just taxonomic. The measurement of the liability differs fundamentally.
Under IFRS 9: ECL from Day One
A financial guarantee contract is initially measured at fair value. Where the guarantee is issued at arm's length, fair value at inception is typically the premium received (or its present value if paid over time). Where the guarantee is issued for no consideration or nominal consideration (common in intragroup arrangements), initial fair value reflects the economic benefit of the guarantee to the guaranteed party, which may be significant.
Subsequently, the financial guarantee is measured at the higher of:
The ECL amount determined under IFRS 9's impairment model, and the amount initially recognised less any cumulative amortisation under IFRS 15.
The ECL calculation treats the guarantee as a credit exposure. Even in Stage 1 (no significant increase in credit risk), a 12-month ECL is recognised from day one. If the guaranteed entity's credit quality deteriorates, the guarantee moves to Stage 2 (lifetime ECL) or Stage 3 (credit-impaired).
Critically, the ECL is probability-weighted. If there is a 20% probability of the guaranteed entity defaulting and the guarantee exposure is Rs. 100 crore with 40% LGD, the ECL is Rs. 8 crore (20% × Rs. 100 crore × 40%). This ECL is recognised even though the most likely outcome (80% probability) is no loss at all.
Under IAS 37: Provision Only When Probable
If the same guarantee were classified under IAS 37, no provision would be recognised unless the outflow became probable (>50%). A 20% probability of default produces no provision under IAS 37; it produces a contingent liability disclosure.
At 55% probability of default with the same Rs. 100 crore exposure and 40% LGD, IAS 37 would recognise a provision at the best estimate of the expected outflow. The best estimate for a large population would be the expected value: Rs. 22 crore (55% × Rs. 100 crore × 40%). For a single unique guarantee, it would be the most likely outcome adjusted for risks, potentially different from the expected value.
The IAS 37 provision could be higher or lower than the IFRS 9 ECL at any given probability level. At low probabilities of default, IFRS 9 produces a positive ECL while IAS 37 produces nothing. At high probabilities with concentrated exposure, the best estimate under IAS 37 might exceed the IFRS 9 ECL if the most likely outcome is a full loss.
The EFRAG analysis of IFRS 9's post-implementation review explicitly noted this timing mismatch: under IAS 37, a reimbursement asset is recognised in a different period than the ECL for the related financial instrument, creating a timing difference that does not faithfully reflect the economic substance.
Intragroup Guarantees: A Specific Indian Context
Indian parent companies routinely provide guarantees for subsidiary borrowings. The accounting in the parent's separate financial statements depends on the classification.
If the guarantee is a financial guarantee contract (IFRS 9):
Initial recognition: at fair value. For an intragroup guarantee issued at no premium, fair value reflects the economic benefit to the subsidiary, which is the difference between the interest rate the subsidiary can borrow at with the guarantee versus without it, discounted over the loan term. The debit entry is an investment in the subsidiary (a capital contribution) in the parent's separate financial statements.
Subsequent measurement: higher of ECL and amortised amount.
ECL: the parent assesses the subsidiary's credit quality, stages the guarantee (Stage 1 to Stage 3 as credit quality deteriorates), and recognises ECL accordingly.
If the guarantee is not a financial guarantee contract (IAS 37):
No initial recognition if the outflow is not probable. Disclosed as a contingent liability.
Provision recognised if outflow becomes probable, at the best estimate of the expected outflow.
The classification has a second-order effect: the initial recognition entry for a financial guarantee creates a capital contribution to the subsidiary, increasing the investment in subsidiary in the parent's books. Under IAS 37, no such entry exists. The parent either provisions or discloses, but no asset is recognised for the right to recover from the subsidiary on payment.
Intragroup Guarantees in Indian Conglomerate Practice
Tata Sons providing guarantees for Tata Group subsidiary borrowings, Reliance Industries guaranteeing obligations of its subsidiaries, or Mahindra & Mahindra supporting its financial services subsidiary are all situations where this classification matters.
The Indian regulatory context adds complexity. RBI regulations require Indian banks to obtain parental guarantees for certain lending to subsidiaries or affiliates. These guarantees are typically financial guarantee contracts under IFRS 9. The guarantee issuer (parent) must measure the guarantee at fair value at inception and subsequently at the higher of ECL and amortised amount.
For many Indian conglomerates that historically provided intragroup guarantees with no accounting entry, the transition to Ind AS 109 required recognition of these guarantees as financial liabilities and simultaneous recognition of the fair value benefit as a capital contribution to the guaranteed subsidiary.
Loan Commitments: Also Under IFRS 9
Undrawn loan commitments that are not measured at FVTPL are within IFRS 9's ECL scope, not IAS 37. A bank that has committed to lend Rs. 500 crore to a corporate borrower under a revolving credit facility has a credit exposure from the commitment date, not just from the drawdown date.
IFRS 9 requires ECL to be recognised on the loan commitment using the same three-stage framework as drawn loans. The EAD (exposure at default) for undrawn commitments uses a credit conversion factor (CCF) to estimate how much of the undrawn facility is likely to be drawn before any default.
The interaction between drawn loan ECL and undrawn commitment ECL is important for Indian banks and NBFCs: both the outstanding loan balance and the undrawn commitment carry ECL provisions. The portfolio ECL is the sum of provisions on drawn and undrawn portions.
When a Loan Commitment Becomes IAS 37 Territory
Loan commitments issued below market rate may have an element that is closer to a subsidy or a below-market arrangement. In those cases, the below-market element may need IAS 37 assessment. However, the credit risk component of the loan commitment remains under IFRS 9.
Government-directed lending in India, where banks are required to lend at below-market rates to priority sectors, involves elements that are part commercial banking (IFRS 9 ECL applies to the credit risk) and part public policy obligation. The public policy obligation element, if it creates an unavoidable obligation to lend at a loss, may involve IAS 37 considerations. In practice, Indian banks have not generally treated priority sector lending obligations as IAS 37 provisions; they apply IFRS 9 to the credit risk of the resulting loans.
Written Options on Financial Instruments
A written put option on a financial asset (the entity must buy the asset at a specified price if the counterparty exercises the option) is a financial instrument under IFRS 9. Its fair value is measured at FVTPL or FVOCI depending on classification. It is not an IAS 37 provision.
The distinction becomes practically important when an entity writes a put option on the shares of an associate or subsidiary (granting a third party the right to sell shares to the entity at a specified price). This creates a financial liability under IFRS 9, measured at fair value through profit or loss. It is not a contingent liability under IAS 37.
Indian PE-backed companies frequently contain put option arrangements: the PE investor has the right to put shares back to the promoter at a predetermined price. From the promoter's perspective, this is a financial liability under IFRS 9, not a provision under IAS 37. The liability is at fair value each reporting period. As the put option's fair value increases (because the guaranteed return becomes more valuable), the promoter's financial liability increases, with the change going through profit or loss.
The Reimbursement Asset Asymmetry
IAS 37 allows recognition of a reimbursement asset (the right to recover from a third party) when recovery is virtually certain. IFRS 9 requires recognition of the ECL on the original instrument regardless of any right of recovery.
The timing mismatch arises when a guarantor has provided a financial guarantee. Under IFRS 9, the guarantor recognises ECL on the guarantee from day one. But the reimbursement right from the guaranteed party (the right to recover if the guarantor pays) is recognised under IAS 37 only when virtually certain. This creates an asymmetry: the ECL liability appears before the recovery asset, producing a net expense in the income statement earlier than the economic substance might suggest.
EFRAG's review of IFRS 9 implementation noted this mismatch as a genuine application challenge, particularly for intragroup guarantees where recovery from the guaranteed subsidiary is highly probable but not virtually certain.
ECL on Trade Receivables: IAS 37 Does Not Apply
This point trips up students and preparers. Trade receivables impairment falls entirely under IFRS 9's ECL model, using either the general approach or the simplified approach (provision matrix). IAS 37 does not apply to trade receivables because they are financial instruments within IFRS 9's scope.
Provisions for doubtful debts under old Indian GAAP operated conceptually like IAS 37 provisions: recognise when probable. Under Ind AS 109, the entire approach shifts to ECL: forward-looking, probability-weighted, recognised from day one on the simplified approach. This is one of the most consequential differences between old Indian GAAP and Ind AS for entities with large trade receivable portfolios.
Ind AS 37 vs IAS 37: Interaction with Ind AS 109
| Area | IAS 37 / IFRS 9 | Ind AS 37 / Ind AS 109 |
|---|---|---|
| Financial guarantee contracts | IFRS 9 takes priority | Ind AS 109 takes priority |
| Loan commitments ECL | IFRS 9 | Ind AS 109 |
| Performance guarantees | IAS 37 | Ind AS 37 |
| Written put options on shares | IFRS 9 financial liability | Ind AS 109 |
| Trade receivable impairment | IFRS 9 ECL only | Ind AS 109 ECL only |
| Reimbursement asset threshold | IAS 37: virtually certain | Ind AS 37: same |
| ECL vs provision threshold difference | IFRS 9: probability-weighted from day one; IAS 37: probable (>50%) threshold | Same difference |
| Intragroup guarantees: fair value at inception | IFRS 9 requires fair value; capital contribution debit | Ind AS 109 same; Indian conglomerates face transition challenges on unrecognised intragroup guarantees |
| IFRIC 2025 agenda decision on guarantees | Confirms hierarchy; judgment required on debt instrument definition | Ind AS follows IFRIC conclusions; MCA notification where Ind AS formal amendment required |
What Big 4 Auditors Focus On
Classification of guarantee obligations. Auditors test whether guarantees issued by the entity have been correctly classified as financial guarantee contracts (IFRS 9), performance guarantees (IAS 37), or insurance contracts (IFRS 17). The classification turns on whether the underlying obligation is a debt instrument and whether the trigger is credit default. Misclassifying a financial guarantee contract as an IAS 37 provision allows the entity to apply the higher probability threshold, potentially deferring recognition.
ECL on financial guarantees. Where guarantees are correctly within IFRS 9, auditors test the ECL calculation: the credit quality assessment of the guaranteed party, the staging determination, the PD/LGD/EAD estimates, and whether forward-looking information has been incorporated. A financial guarantee issued by a parent to a financially stressed subsidiary carries Stage 2 or Stage 3 ECL, not Stage 1.
Intragroup guarantee initial recognition. For Indian conglomerates, auditors verify that intragroup financial guarantee contracts issued at no premium have been recognised at fair value at inception, with the capital contribution recognised in the investment in subsidiary. Guarantees issued for years without any accounting entry, reclassified to Ind AS 109 on transition, require specific transition-date accounting.
Reimbursement asset timing. Where a guarantor has a right of recovery from the guaranteed party, auditors test whether the reimbursement asset has been recognised only when recovery is virtually certain (IAS 37), not merely probable. Recognising a reimbursement asset prematurely offsets an ECL charge that should be flowing through profit or loss.
Written put option classification. For entities with put option arrangements (common in PE-backed structures), auditors verify that written puts on financial assets are classified as IFRS 9 financial liabilities at FVTPL, not as IAS 37 contingent liabilities. The former requires ongoing fair value measurement; the latter would allow deferral until probable.
Dip IFRS Exam Angle
This topic is advanced and more likely to appear in scenario-based discussion questions than pure calculation. The exam tests whether candidates understand the boundary between IFRS 9 and IAS 37.
Most tested areas:
Classification of guarantees: given a description of a guarantee, determine whether it is a financial guarantee contract (IFRS 9) or a performance guarantee (IAS 37). Know the three elements of the IFRS 9 definition.
Threshold difference: explain why an obligation classified under IFRS 9 produces a different balance sheet liability than the same obligation under IAS 37. IFRS 9 is probability-weighted from day one; IAS 37 requires probable outflow.
Intragroup guarantee accounting: given a parent providing a free guarantee for a subsidiary's bank loan, identify that this is a financial guarantee contract under IFRS 9, measured at fair value initially with the capital contribution debited to the investment.
ECL on loan commitments: know that undrawn loan commitments within IFRS 9's scope carry ECL provisions using the same three-stage framework as drawn loans. IAS 37 does not govern these.
Common traps:
Applying IAS 37's probable threshold to a financial guarantee contract. Once classified under IFRS 9, the ECL model applies from day one regardless of the probability of loss.
Treating trade receivable impairment as an IAS 37 provision. Trade receivables are financial assets under IFRS 9. Their impairment is ECL, not a provision under IAS 37.
Classifying a written put option on shares as an IAS 37 contingent liability. Written options are financial instruments; IFRS 9 governs and the liability is at fair value.
FAQ
If a financial guarantee is issued at arm's length for a premium, how is it initially measured?
At fair value, which is typically the premium received. The premium is recognised as a financial guarantee liability and amortised over the guarantee period under IFRS 15 principles, while ECL is also recognised. The carrying amount is the higher of ECL and the remaining unamortised amount.
Can an entity elect to apply IAS 37 to a financial guarantee contract instead of IFRS 9?
Only where the issuer has previously asserted that it regards the contract as an insurance contract and has applied insurance accounting. In that case, the entity can irrevocably elect to apply either IFRS 9 or IFRS 17 on a contract-by-contract basis. Otherwise, IFRS 9 governs all financial guarantee contracts.
What is the accounting in the guaranteed party's books?
The guaranteed party (the borrower whose debt is guaranteed) does not recognise anything for the guarantee in its own books. The guarantee is an arrangement between the guarantor and the lender. The borrower may benefit from a lower interest rate (because the lender's credit risk is reduced by the guarantee), but that is a commercial benefit, not an accounting entry.
Does the IFRS 9 ECL on a financial guarantee get recognised even if the guaranteed entity is financially healthy?
Yes. Stage 1 ECL (12-month) is recognised from initial recognition of the guarantee, even if the guaranteed entity is currently creditworthy. The ECL reflects the probability-weighted expected loss over 12 months, which is greater than zero for any counterparty.
How does a performance guarantee differ from a financial guarantee in practice?
A performance guarantee pays out if the entity fails to deliver goods or services as agreed. The trigger is non-performance, not credit default on a debt instrument. Common in construction, infrastructure, and IT services contracts. These are IAS 37 obligations: provision if probable outflow, contingent liability if possible.
Does the interaction between IAS 37 and IFRS 9 affect how Indian companies disclose related party guarantees?
Yes. IAS 24 requires disclosure of the terms and conditions of transactions with related parties, including guarantees. Where the guarantee is a financial guarantee contract under IFRS 9, the disclosure includes the carrying amount of the liability and the ECL recognised. Where it is a performance guarantee under IAS 37, the disclosure includes whether it is provisioned or a contingent liability, and the estimated financial effect.
Enroll with Global Fin X
The IAS 37 and IFRS 9 boundary is one of the more technically demanding areas in the Dip IFRS syllabus. It requires understanding both standards precisely and knowing which takes priority in specific situations. Our programme covers this interaction alongside the full IAS 37 and IFRS 9 series with detailed lectures, exam-style MCQs, and a dedicated LMS for working professionals.
Enroll Now: Dip IFRS Programme
Faculty profile: www.globalfinx.in/manikanta
This is Post 44 of the Global Fin X IFRS Series. Previous: IAS 37: Contingent Liabilities, Contingent Assets, Onerous Contracts and Restructuring. Next: Post 45: IFRIC 21 Levies: When to Recognise a Liability and How It Works.