12.07.2015 Views

Tracking Financial Performance Standards of ... - Sa-Dhan

Tracking Financial Performance Standards of ... - Sa-Dhan

Tracking Financial Performance Standards of ... - Sa-Dhan

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Tracking</strong> <strong>Financial</strong> <strong>Performance</strong> <strong>Standards</strong> <strong>of</strong> Micr<strong>of</strong>inance Institutions5.1.2.6 Are Repayment Rates indeed reliable and valid indicators <strong>of</strong> asset quality?F While they are indeed useful, repayment rates are not reliable and valid indicators <strong>of</strong> asset (portfolio)quality.F As evident from the example given in Table 12, it is possible to have a very high repayment rate and yet avery high portfolio at risk - in excess <strong>of</strong> 80% (illustration is given at end <strong>of</strong> this section).F While many MFIs use repayment rates to measure default risk in a portfolio, it must be remembered thatrepayment rates primarily express the amount paid by clients as a percentage <strong>of</strong> the amounts due fromthem.F They do not measure default risk in a portfolio.F In fact, the portfolio outstanding does not appear in the numerator or denominator in the repayment rateformula. Therefore, using repayment rates to get a measure <strong>of</strong> the default risk is inappropriate.Calculation from Table 12 (see table below) demonstrates as to why Repayment Rates are not a Reliable/Valid Indicator <strong>of</strong> Portfolio QualityIndicator Formula Value(in %)Cumulative Repayment Rate (CRR)PAR (Portfolio at Risk)Portfolio at Risk AdjustedColumn IX Total – Column XI TotalColumn VI Total 99.66%Column XIII TotalColumn XII Total 38.79%Column XIII TotalColumn XII Total - (Sum <strong>of</strong> Row 13+14, Column XII) 81.19%86

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!