#jsDisabledContent { display:none; } My Account | Register | Help

# Loss given default

Article Id: WHEBN0009035647
Reproduction Date:

 Title: Loss given default Author: World Heritage Encyclopedia Language: English Subject: Collection: Publisher: World Heritage Encyclopedia Publication Date:

### Loss given default

Loss given default or LGD is a common parameter in Risk Models and also a parameter used in the calculation of Economic Capital, Expected loss or Regulatory Capital under Basel II for a banking institution. This is an attribute of any exposure on bank's client. Exposure is the amount that one may lose in an investment.

## Contents

• Definition 1
• How to calculate LGD 2
• Calculating LGD under the foundation approach (for corporate, sovereign and bank exposure) 2.1
• Exposure without Collateral 2.1.1
• Exposure with Collateral 2.1.2
• Calculating LGD under the advanced approach (and for the retail-portfolio under the foundation approach) 2.2
• Downturn LGD 3
• Correcting for different default definitions 4
• Country-specific LGD 5
• Importance 6
• References 8

## Definition

LGD is the share of an asset that is lost when a borrower defaults.

Loss given default is facility-specific because such losses are generally understood to be influenced by key transaction characteristics such as the presence of collateral and the degree of subordination.

## How to calculate LGD

The LGD calculation is easily understood with the help of an example: If the client defaults with an outstanding debt of $200,000 and the bank or insurance is able to sell the security (e.g. a condo) for a net price of$160,000 (including costs related to the repurchase), then the LGD is 20% (= $40,000 /$200,000).

Theoretically, LGD is calculated in different ways, but the most popular is 'Gross' LGD, where total losses are divided by exposure at default (EAD). Another method is to divide Losses by the unsecured portion of a credit line (where security covers a portion of EAD). This is known as 'Blanco' LGD. If collateral value is zero in the last case then Blanco LGD is equivalent to Gross LGD. Different types of statistical methods can be used to do this.

Gross LGD is most popular amongst academics because of its simplicity and because academics only have access to bond market data, where collateral values often are unknown, uncalculated or irrelevant. Blanco LGD is popular amongst some practitioners (banks) because banks often have many secured facilities, and banks would like to decompose their losses between losses on unsecured portions and losses on secured portions due to depreciation of collateral quality. The latter calculation is also a subtle requirement of Basel II, but most banks are not sophisticated enough at this time to make those types of calculations.require('Module:No globals')

local p = {}

-- articles in which traditional Chinese preceeds simplified Chinese local t1st = { ["228 Incident"] = true, ["Chinese calendar"] = true, ["Lippo Centre, Hong Kong"] = true, ["Republic of China"] = true, ["Republic of China at the 1924 Summer Olympics"] = true, ["Taiwan"] = true, ["Taiwan (island)"] = true, ["Taiwan Province"] = true, ["Wei Boyang"] = true, }

-- the labels for each part local labels = { ["c"] = "Chinese", ["s"] = "simplified Chinese", ["t"] = "traditional Chinese", ["p"] = "pinyin", ["tp"] = "Tongyong Pinyin", ["w"] = "Wade–Giles", ["j"] = "Jyutping", ["cy"] = "Cantonese Yale", ["poj"] = "Pe̍h-ōe-jī", ["zhu"] = "Zhuyin Fuhao", ["l"] = "literally", }

-- article titles for wikilinks for each part local wlinks = { ["c"] = "Chinese language", ["s"] = "simplified Chinese characters", ["t"] = "traditional Chinese characters", ["p"] = "pinyin", ["tp"] = "Tongyong Pinyin", ["w"] = "Wade–Giles", ["j"] = "Jyutping", ["cy"] = "Yale romanization of Cantonese", ["poj"] = "Pe̍h-ōe-jī", ["zhu"] = "Bopomofo", }

-- for those parts which are to be treated as languages their ISO code local ISOlang = { ["c"] = "zh", ["t"] = "zh-Hant", ["s"] = "zh-Hans", ["p"] = "zh-Latn-pinyin", ["tp"] = "zh-Latn", ["w"] = "zh-Latn-wadegile", ["j"] = "yue-jyutping", ["cy"] = "yue", ["poj"] = "hak", ["zhu"] = "zh-Bopo", }

local italic = { ["p"] = true, ["tp"] = true, ["w"] = true, ["j"] = true, ["cy"] = true, ["poj"] = true, } -- Categories for different kinds of Chinese text local cats = { ["c"] = "", ["s"] = "", ["t"] = "", }

function p.Zh(frame) -- load arguments module to simplify handling of args local getArgs = require('Module:Arguments').getArgs local args = getArgs(frame) return p._Zh(args) end function p._Zh(args) local uselinks = not (args["links"] == "no") -- whether to add links local uselabels = not (args["labels"] == "no") -- whether to have labels local capfirst = args["scase"] ~= nil

        local t1 = false -- whether traditional Chinese characters go first
local j1 = false -- whether Cantonese Romanisations go first
local testChar
if (args["first"]) then
for testChar in mw.ustring.gmatch(args["first"], "%a+") do
if (testChar == "t") then
t1 = true
end
if (testChar == "j") then
j1 = true
end
end
end
if (t1 == false) then
local title = mw.title.getCurrentTitle()
t1 = t1st[title.text] == true
end


-- based on setting/preference specify order local orderlist = {"c", "s", "t", "p", "tp", "w", "j", "cy", "poj", "zhu", "l"} if (t1) then orderlist[2] = "t" orderlist[3] = "s" end if (j1) then orderlist[4] = "j" orderlist[5] = "cy" orderlist[6] = "p" orderlist[7] = "tp" orderlist[8] = "w" end -- rename rules. Rules to change parameters and labels based on other parameters if args["hp"] then -- hp an alias for p ([hanyu] pinyin) args["p"] = args["hp"] end if args["tp"] then -- if also Tongyu pinyin use full name for Hanyu pinyin labels["p"] = "Hanyu Pinyin" end if (args["s"] and args["s"] == args["t"]) then -- Treat simplified + traditional as Chinese if they're the same args["c"] = args["s"] args["s"] = nil args["t"] = nil elseif (not (args["s"] and args["t"])) then -- use short label if only one of simplified and traditional labels["s"] = labels["c"] labels["t"] = labels["c"] end local body = "" -- the output string local params -- for creating HTML spans local label -- the label, i.e. the bit preceeding the supplied text local val -- the supplied text -- go through all possible fields in loop, adding them to the output for i, part in ipairs(orderlist) do if (args[part]) then -- build label label = "" if (uselabels) then label = labels[part] if (capfirst) then label = mw.language.getContentLanguage():ucfirst(

### Calculating LGD under the foundation approach (for corporate, sovereign and bank exposure)

To determine required capital for a bank or financial institution under Basel II, the institution has to calculate risk-weighted assets. This requires estimating the LGD for each corporate, sovereign and bank exposure. There are two approaches for deriving this estimate: a foundation approach and an advanced approach.

#### Exposure without Collateral

Under the foundation approach, BIS prescribes fixed LGD ratios for certain classes of unsecured exposures:

• Senior claims on corporates, sovereigns and banks not secured by recognized collateral attract a 45% LGD.
• All subordinated claims on corporates, sovereigns and banks attract a 75% LGD.

#### Exposure with Collateral

Simple LGD example: If the client defaults, with an outstanding debt of 200,000 (EAD) and the bank is able to sell the security for a net price of 160,000 (including costs related to the repurchase), then 40,000, or 20%, of the EAD are lost - the LGD is 20%.

The effective loss given default (L_{GD}^*) applicable to a collateralized transaction can be expressed as L_{GD}^* = L_{GD}\cdot\frac{E^*}{E} Haircut appropriate for currency mismatch between the collateral and exposure (The standard supervisory haircut for currency risk where exposure and collateral are denominated in different currencies is 8%)

The *He and *Hc has to be derived from the following table of standard supervisory haircuts:

However, under certain special circumstances the supervisors, i.e. the local central banks may choose not to apply the haircuts specified under the comprehensive approach, but instead to apply a zero H.

### Calculating LGD under the advanced approach (and for the retail-portfolio under the foundation approach)

Under the A-IRB approach and for the retail-portfolio under the F-IRB approach, the bank itself determines the appropriate loss given default to be applied to each exposure, on the basis of robust data and analysis. The analysis must be capable of being validated both internally and by supervisors. Thus, a bank using internal loss given default estimates for capital purposes might be able to differentiate loss given default values on the basis of a wider set of transaction characteristics (e.g. product type, wider range of collateral types) as well as borrower characteristics. These values would be expected to represent a conservative view of long-run averages. A bank wishing to use its own estimates of LGD will need to demonstrate to its supervisor that it can meet additional minimum requirements pertinent to the integrity and reliability of these estimates.

An LGD model assesses the value and/or the quality of a security the bank holds for providing the loan – securities can be either machinery like cars, trucks or construction machines. It can be mortgages or it can be a custody account or a commodity. The higher the value of the security the lower the LGD and thus the potential loss the bank or insurance faces in the case of a default. Banks using the A-IRB approach have to determine LGD values, whereas banks within the F-IRB do only have to do so for the retail-portfolio. For example, as of 2013, there were nine companies in the United Kingdom with their own mortgage LGD models. In Switzerland there were two banks as of 2013. In Germany many thrifts – especially the market leader Bausparkasse Schwäbisch Hall – have their own mortgage LGD models. In the corporate asset class many German banks still only use the values given by the regulator under the F-IRB approach.

Repurchase Value Estimators (RVEs) have proven to be the best kind of tools for LGD estimates. The repurchase value ratio provides the percentage of the value of the house/apartment (mortgages) or machinery at a given time compared to its purchase price.

## Downturn LGD

Under Basel II, banks and other financial institutions are recommended to calculate 'Downturn LGD' (downturn loss given default), which reflects the losses occurring during a 'Downturn' in a business cycle for regulatory purposes. Downturn LGD is interpreted in many ways, and most financial institutions that are applying for IRB approval under BIS II often have differing definitions of what Downturn conditions are. One definition is at least two consecutive quarters of negative growth in real GDP. Often, negative growth is also accompanied by a negative output gap in an economy (where potential production exceeds actual demand).

The calculation of LGD (or Downturn LGD) poses significant challenges to modelers and practitioners. Final resolutions of defaults can take many years and final losses, and hence final LGD, cannot be calculated until all of this information is ripe. Furthermore, practitioners are of want of data since BIS II implementation is rather new and financial institutions may have only just started collecting the information necessary for calculating the individual elements that LGD is composed of: EAD, direct and indirect Losses, security values and potential, expected future recoveries. Another challenge, and maybe the most significant, is the fact that the default definitions between institutions vary. This often results in a so-called differing cure-rates or percentage of defaults without losses. Calculation of LGD (average) is often composed of defaults with losses and defaults without. Naturally, when more defaults without losses are added to a sample pool of observations LGD becomes lower. This is often the case when default definitions become more 'sensitive' to credit deterioration or 'early' signs of defaults. When institutions use different definitions, LGD parameters therefore become non-comparable.

Many institutions are scrambling to produce estimates of Downturn LGD, but often resort to 'mapping' since Downturn data is often lacking. Mapping is the process of guesstimating losses under a downturn by taking existing LGD and adding a supplement or buffer, which is supposed to represent a potential increase in LGD when Downturn occurs. LGD often decreases for some segments during Downturn since there is a relatively larger increase of defaults that result in higher cure-rates, often the result of temporary credit deterioration that disappears after the Downturn Period is over. Furthermore, LGD values decrease for defaulting financial institutions under economic Downturns because governments and central banks often rescue these institutions in order to maintain financial stability.

## Correcting for different default definitions

One problem facing practitioners is the comparison of LGD estimates (usually averages) arising from different time periods where differing default definitions have been in place. The following formula can be used to compare LGD estimates from one time period (say x) with another time period (say y):

LGDy=LGDx*(1-Cure Ratey)/(1-Cure Ratex)

## Country-specific LGD

In Australia, the prudential regulator APRA has set an interim minimum downturn LGD of 20 per cent on residential mortgages for all applicants for the advanced Basel II approaches. The 20 per cent floor is not risk sensitive and is designed to encourage the ADIs to undertake further work, which APRA believes would be closer to the 20 per cent on average than ADIs’ original estimates.

## Importance

LGD warrants more attention than what has been given to it in the past decade, where credit risk models often assumed that LGD was time-invariant. Movements in LGD result in often proportional movements in required economic capital. According to BIS (2006) institutions implementing Advanced-IRB instead of Foundation-IRB will experience larger decreases in Tier 1 capital, and the internal calculation of LGD is a factor separating the two Methods.require('Module:No globals')

local p = {}

-- articles in which traditional Chinese preceeds simplified Chinese local t1st = { ["228 Incident"] = true, ["Chinese calendar"] = true, ["Lippo Centre, Hong Kong"] = true, ["Republic of China"] = true, ["Republic of China at the 1924 Summer Olympics"] = true, ["Taiwan"] = true, ["Taiwan (island)"] = true, ["Taiwan Province"] = true, ["Wei Boyang"] = true, }

-- the labels for each part local labels = { ["c"] = "Chinese", ["s"] = "simplified Chinese", ["t"] = "traditional Chinese", ["p"] = "pinyin", ["tp"] = "Tongyong Pinyin", ["w"] = "Wade–Giles", ["j"] = "Jyutping", ["cy"] = "Cantonese Yale", ["poj"] = "Pe̍h-ōe-jī", ["zhu"] = "Zhuyin Fuhao", ["l"] = "literally", }

-- article titles for wikilinks for each part local wlinks = { ["c"] = "Chinese language", ["s"] = "simplified Chinese characters", ["t"] = "traditional Chinese characters", ["p"] = "pinyin", ["tp"] = "Tongyong Pinyin", ["w"] = "Wade–Giles", ["j"] = "Jyutping", ["cy"] = "Yale romanization of Cantonese", ["poj"] = "Pe̍h-ōe-jī", ["zhu"] = "Bopomofo", }

-- for those parts which are to be treated as languages their ISO code local ISOlang = { ["c"] = "zh", ["t"] = "zh-Hant", ["s"] = "zh-Hans", ["p"] = "zh-Latn-pinyin", ["tp"] = "zh-Latn", ["w"] = "zh-Latn-wadegile", ["j"] = "yue-jyutping", ["cy"] = "yue", ["poj"] = "hak", ["zhu"] = "zh-Bopo", }

local italic = { ["p"] = true, ["tp"] = true, ["w"] = true, ["j"] = true, ["cy"] = true, ["poj"] = true, } -- Categories for different kinds of Chinese text local cats = { ["c"] = "", ["s"] = "", ["t"] = "", }

function p.Zh(frame) -- load arguments module to simplify handling of args local getArgs = require('Module:Arguments').getArgs local args = getArgs(frame) return p._Zh(args) end function p._Zh(args) local uselinks = not (args["links"] == "no") -- whether to add links local uselabels = not (args["labels"] == "no") -- whether to have labels local capfirst = args["scase"] ~= nil

        local t1 = false -- whether traditional Chinese characters go first
local j1 = false -- whether Cantonese Romanisations go first
local testChar
if (args["first"]) then
for testChar in mw.ustring.gmatch(args["first"], "%a+") do
if (testChar == "t") then
t1 = true
end
if (testChar == "j") then
j1 = true
end
end
end
if (t1 == false) then
local title = mw.title.getCurrentTitle()
t1 = t1st[title.text] == true
end


-- based on setting/preference specify order local orderlist = {"c", "s", "t", "p", "tp", "w", "j", "cy", "poj", "zhu", "l"} if (t1) then orderlist[2] = "t" orderlist[3] = "s" end if (j1) then orderlist[4] = "j" orderlist[5] = "cy" orderlist[6] = "p" orderlist[7] = "tp" orderlist[8] = "w" end -- rename rules. Rules to change parameters and labels based on other parameters if args["hp"] then -- hp an alias for p ([hanyu] pinyin) args["p"] = args["hp"] end if args["tp"] then -- if also Tongyu pinyin use full name for Hanyu pinyin labels["p"] = "Hanyu Pinyin" end if (args["s"] and args["s"] == args["t"]) then -- Treat simplified + traditional as Chinese if they're the same args["c"] = args["s"] args["s"] = nil args["t"] = nil elseif (not (args["s"] and args["t"])) then -- use short label if only one of simplified and traditional labels["s"] = labels["c"] labels["t"] = labels["c"] end local body = "" -- the output string local params -- for creating HTML spans local label -- the label, i.e. the bit preceeding the supplied text local val -- the supplied text -- go through all possible fields in loop, adding them to the output for i, part in ipairs(orderlist) do if (args[part]) then -- build label label = "" if (uselabels) then label = labels[part] if (capfirst) then label = mw.language.getContentLanguage():ucfirst(

• Expected loss and its three factors
• Loss given default (LGD) magnitude of likely loss on the exposure, expressed as a percentage of the exposure (This page.)
• Probability of default (PD) probability of default of a borrower
• Exposure at default (EAD) amount to which the bank was exposed to the borrower at the time of default, measured in currency
• For the effects of correlation between PD and LGD see Expected loss

## References

• http://www.bis.org/publ/bcbsca.htm Basel II: Revised international capital framework (BCBS)
• http://www.bis.org/publ/bcbs107.htm Basel II: International Convergence of Capital Measurement and Capital Standards: a Revised Framework (BCBS)
• http://www.bis.org/publ/bcbs118.htm Basel II: International Convergence of Capital Measurement and Capital Standards: a Revised Framework (BCBS) (November 2005 Revision)
• http://www.bis.org/publ/bcbs128.pdf Basel II: International Convergence of Capital Measurement and Capital Standards: a Revised Framework, Comprehensive Version (BCBS) (June 2006 Revision)
• http://www.info.gov.hk/hkma/eng/bank/spma/attach/CA-G-4.pdf Validating Risk Rating Systems under the IRB Approaches,HKMA