Skip to main content

Who Will Be Telling the Truth: Greece, the EFSB, or National Regulators?

Recently the EU set up the European Systemic Risk Board (ESRB). Ok, this is kind of old news (the enacting legislation went into effect in December 2010). Why am I writing about it now?

Well, just the other day EU leaders put together another rescue package that included guarantees and lose-sharing with banks (a partial default). In all of the discussion surrounding the future shape of a sustainable system of EU government financing (here or here for example) there has been little discussion of the need for good information about what is really going on.

In research I'm currently putting together (and mentioned in previous posts) I've found that in order for policymakers to actually choose the level of bank (and I suppose government debt) guarantees that they want they need good information about economic fundamentals (not a huge surprise). But there is a good chance that the ESRB won't be able to give good information. Or more precisely, any information they give will get confused.

Let me hypothesise: Conflicting information is often bad information. Regulators give conflicting information if they have conflicting preferences (see here).

The ESRB is going to be providing information about the health of the financial sector. Well, so are lots of others. There are numerous financial stability boards, regulators, etc. in Europe also providing information. All of these agencies are run by people who (likely) have different preferences from each other and from European decision-makers.

Lets make some assumptions:

  • European decision-makers (presidents, PM, chancellors, and the Commission) want a stable European financial sector at the lowest possible cost.

  • Some national regulators/stability boards, etc. want stable national financial sectors at the lowest possible cost to the country.

  • Other national regulators/stability boards, etc. want to provide accurate information regardless of the policy consequences.

  • Lets not make any assumptions about the ESRB's preferences right now.

Thinking about the Greek debt crisis example: National interest focused regulators want to maintain the stability of their country's banking sector. These regulators likely want to present their country in the best light possible: "our banks aren't that exposed to the Greek debt problem." Hopefully, they can reassure investors and depositors to continue putting money into their country's banks. Painting a rosy picture has the added benefit of making high European guarantees seem like a good idea to European decision-makers (we can regain market confidence by saying we'll cover everything, but the problem isn't too bad so we won't have to actually cover much of anything!).

Accurate information focused regulators will provide good information regardless of the market's and the European response.

Ok, so where am I going with this?

The problem for European decision-makers (like anyone in a signalling game) is to decide which is which. This can be pretty tricky since in reality most regulators likely will be a bit of both. Regulators may want to provide accurate information, but they also don't want to trigger crises by revealing how bad things are. This is probably true of any ESRB.

European decision-makers need good information to make the policy decisions they want. However, when there are many regulators, financial stability boards, and their own ESRB giving them information, all with their own preferences, who can they believe?

This is a key issue to resolve if the EU wants to create a sustainable financial architecture. I also need to think about it more. . .

Labels:

Comments

Post a Comment

Popular posts from this blog

Dropbox & R Data

I'm always looking for ways to download data from the internet into R. Though I prefer to host and access plain-text data sets (CSV is my personal favourite) from GitHub (see my short paper on the topic) sometimes it's convenient to get data stored on Dropbox . There has been a change in the way Dropbox URLs work and I just added some functionality to the repmis R package. So I though that I'ld write a quick post on how to directly download data from Dropbox into R. The download method is different depending on whether or not your plain-text data is in a Dropbox Public folder or not. Dropbox Public Folder Dropbox is trying to do away with its public folders. New users need to actively create a Public folder. Regardless, sometimes you may want to download data from one. It used to be that files in Public folders were accessible through non-secure (http) URLs. It's easy to download these into R, just use the read.table command, where the URL is the file name
51 comments
Read more

Slide: one function for lag/lead variables in data frames, including time-series cross-sectional data

I often want to quickly create a lag or lead variable in an R data frame. Sometimes I also want to create the lag or lead variable for different groups in a data frame, for example, if I want to lag GDP for each country in a data frame. I've found the various R methods for doing this hard to remember and usually need to look at old blog posts . Any time we find ourselves using the same series of codes over and over, it's probably time to put them into a function. So, I added a new command– slide –to the DataCombine R package (v0.1.5). Building on the shift function TszKin Julian posted on his blog , slide allows you to slide a variable up by any time unit to create a lead or down to create a lag. It returns the lag/lead variable to a new column in your data frame. It works with both data that has one observed unit and with time-series cross-sectional data. Note: your data needs to be in ascending time order with equally spaced time increments. For example 1995, 1996
46 comments
Read more

A Link Between topicmodels LDA and LDAvis

Carson Sievert and Kenny Shirley have put together the really nice LDAvis R package. It provides a Shiny-based interactive interface for exploring the output from Latent Dirichlet Allocation topic models. If you've never used it, I highly recommend checking out their XKCD example (this paper also has some nice background). LDAvis doesn't fit topic models, it just visualises the output. As such it is agnostic about what package you use to fit your LDA topic model. They have a useful example of how to use output from the lda package. I wanted to use LDAvis with output from the topicmodels package. It works really nicely with texts preprocessed using the tm package. The trick is extracting the information LDAvis requires from the model and placing it into a specifically structured JSON formatted object. To make the conversion from topicmodels output to LDAvis JSON input easier, I created a linking function called topicmodels_json_ldavis . The full function is below. To
21 comments
Read more