
Ind AS 109 requires expected credit losses to reflect reasonable and supportable information about future economic conditions, not merely historical average losses. For many portfolios, this means linking credit outcomes to macroeconomic variables and considering more than one possible economic path when non-linearity is material. Operationalising the requirement requires clear ownership, stable data, documented judgements and a link between the technical conclusion and the amounts presented in the financial statements. Forward-looking sophistication adds little value unless scenario design, weights and model responses are transparent and governed. A robust approach connects commercial substance, the Ind AS 109 decision criteria, measurement evidence and presentation consequences in one coherent file.
Choose relevant economic drivers
The principle. Macroeconomic variables should have an economic and empirical relationship with the credit behaviour of the portfolio rather than being selected because data are easy to obtain. For a review-ready file, different portfolios may respond to different drivers such as growth, interest rates, unemployment, commodity prices, property values or exchange rates. The risk to avoid is forcing one enterprise-wide macro model onto portfolios whose risk channels differ materially. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.
Use multiple scenarios where needed
The technical anchor. A single central forecast may not capture expected losses when the relationship between economic outcomes and credit losses is non-linear. In application, entities should determine a reasonable set of scenarios that span plausible outcomes without treating scenario count as a mechanical compliance target. A frequent failure mode is adding scenarios that are merely scaled copies of the base case and do not change the risk distribution meaningfully. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.
Set probability weights with evidence
The accounting logic. Scenario weights should represent the entity's view of the likelihood of the selected economic paths and should be updated when evidence changes. Operationally, governance can combine external forecasts, internal economics, market indicators and structured judgement with documented approvals. The main judgement risk is back-solving weights to achieve a desired allowance. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.
Define the forecast and reversion horizon
The decision point. Detailed forecasts are most supportable over a finite horizon, after which the entity may need a documented technique to converge toward longer-run conditions. For implementation, the approach should avoid abrupt discontinuities in PD, LGD or other model outputs at the end of the forecast period. Where errors often arise is projecting short-term stress indefinitely or reverting instantly without economic rationale. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.
Prevent double counting
The core requirement. Macroeconomic effects embedded in modelled PDs, LGDs or collateral values should not be added again through overlays unless the incremental risk is clearly distinct. In a controlled close process, a model inventory should identify where each risk factor enters the ECL calculation and how overlays interact with model outputs. A common weakness is applying both a stressed scenario and a separate blanket percentage for the same economic risk. Where the conclusion is sensitive to a contractual clause or estimate, the file should show the alternative outcome and why the selected treatment is more appropriate.
Practical illustration
Assume an unsecured retail portfolio has losses that rise sharply when unemployment exceeds a threshold. A probability-weighted base, upside and downside framework may produce an expected loss different from the loss calculated using the average unemployment forecast because the relationship is non-linear. The scenario architecture should capture that effect rather than merely averaging macro variables first. The illustration is deliberately simplified: its purpose is to show how the accounting conclusion follows the underlying facts rather than to prescribe a single mechanical answer for every entity. Before posting an entry, the preparer should reconcile contractual terms, management's commercial intent, relevant estimates and system data to the specific accounting requirement. Where the outcome is sensitive, the file should show the key judgement and explain why the selected assumption is reasonable at the reporting date.
Documentation and control points
Professional application depends as much on process quality as technical knowledge. For this topic, a minimum control set should cover macro-driver selection; scenario approval; weighting methodology; forecast-horizon governance; and double-counting review. Ownership should be clear between the business, finance and any legal, tax, valuation, credit-risk or other specialists whose evidence is required. Source data should be dated and version-controlled; manual adjustments should show preparer, reviewer, rationale and approval. The final accounting memorandum should connect the conclusion to the general ledger or relevant subledger, presentation and disclosures. If facts or estimates change, the entity should reassess the conclusion when required and preserve an audit trail explaining the change.
Closing perspective
Forward-looking ECL is credible when the economic story, statistical linkage and management judgement all point in the same direction. The most useful way to apply Ind AS 109 is to treat the requirement as a decision framework rather than a compliance slogan. When the facts, accounting criteria, measurement evidence, controls and disclosure implications are considered together, the result is more consistent across reporting periods and easier to explain to management, auditors and users of the financial statements.
Continue learning on JUMOQ
Turn this guidance into practical capability
Explore focused courses, worked examples and activities related to this topic.
Explore related courses →References
- Ind AS 109, Financial Instruments — ICAI Compendium of Indian Accounting Standards 2025-2026
- Ind AS 107, Financial Instruments: Disclosures — ICAI Compendium of Indian Accounting Standards 2025-2026
