This is part 3 of a guest post by British Bondora investor ‘ParisinGOC’.

Read part 1 and part 2 first.

Investments Decisions using the Tree(s)

Using the Data

Using the output is as simple as looking at the visualisation to see how the Decision Tree splits down from the Root Node and comparing this with a Bondora loan application that I see as a potential target for investment. (Illustration 2 and Illustration 3) At the end of the set of branches that I follow dependant upon the data in the loan application, I end up at a “leaf node”- the end of the tree. (Illustration 4)  This node simply states how many previous loans match the one I am looking at, showing how many of the previous loans defaulted and how many have not.

I treat the Decision Tree as the first step in choosing whether to invest. If the performance record of previous loans like the one I am now considering suggest a default rate of 5% or less, I look further into the loan application. Continue reading →

This is part 2 of a guest post by British Bondora investor ‘ParisinGOC’.

Read part 1 first.

Data Mining the Bondora data.

The initial process.

To help understand the specific data cleansing that the Bondora Data Set needed, I first made use of the RapidMiner metadata view – a summary of all the attributes presented to the software – showing Attribute name, type, statistics (dependant on type, includes the least occurring and most occurring values, the modal value and the average value), Range (min, max, quantity of each value for polynominal and text attributes) and, most critically, “Missings” and “Role”.

“Role” is the name given by RapidMiner to the special attributes that are needed to allow certain operations. In my case, the Decision Tree module needed to know which Attribute was the “Target”, that is the attribute that is the focus of the analysis and to which the Decision Tree has to relate the other attributes in its processing.  My “Target” was the “Default” attribute – a “Binominal” (called as such by RapidMiner and meaning an attribute with just 2 values) attribute – 1 if the loan had defaulted, 0 if not.

“Missings” is easy – this is the number of times this attribute has no valid value. For example, my import of the raw Bondora input data has 150 attributes.  Only half of these attributes have no missing values.  The remainder have between 13 and 19132 rows with missing values from a data set of 20767 rows.

To know whether these “missings” would impact my analysis, I needed to get to know the data in more detail.

I knew that Bondora had started to offer loans in Finland in summer 2013 with Spain following in October of that year and Slovakia in the first half of 2014.

I therefore decided not to bother with any loan issued prior to 2013. Continue reading →

This is a guest post by British Bondora investor ‘ParisinGOC’.

Introduction

Financial institutions across the world have many ways of assessing whether a loan is worth making.  A simple search on the web reveals that many use Data Mining.  More specifically, “Decision Trees” are a particular tool within Data Mining that has been analysed and I quickly found at least 2 papers (Mining Interesting Rules in Bank Loans Data and Assessing Loan Risks: A Data Mining Case Study) amongst many pointing in this direction.

Having had some experience of Data Mining in a financial environment, I believed I could use these same techniques in my own P2P lending which, after over 12 months activity, I felt could be improved.

In this document, I explore the use of the freely available Data Mining Software “RapidMiner” and its Decision Tree capabilities when applied to the data available to investors from Bondora, a peer-to-peer (P2P) lending site.

Bondora

Bondora is a P2P lending site based in Estonia that “unites investors and borrowers from all corners of the world”, allowing investors to invest funds to satisfy advertised borrowing needs.

Fundamentally, Bondora also provides comprehensive data to investors, allowing detailed data downloads of the individual loans held by the investor, as well as data on every application made to Bondora (originally known as Isepankur) since the first application on 21^st February, 2009.

It is the complete Bondora data set that I have used as the raw data for analysis as it is the best data available to find out which potential borrowers are the right match to the potential lenders.  Only if enough lenders feel that a loan application is worth investing in will the loan be fulfilled.  Self-selection is taking place in both elements of the loan fulfilment and this data is the result of that interaction.

Also shown in this data are some elements of loan performance post-drawdown.  Crucially, it shows those loans that subsequently defaulted (failed to make any payments for a period in excess of 60 days).  Although Bondora will chase the debt on behalf of the investor and have a track record of some success, there is no guarantee that the investment, or any part of it, will be returned.

Decision Trees

www.investopedia.com/terms/d/decision-tree.asp states: A schematic tree-shaped diagram used to determine a course of action or show a statistical probability.

In this case, I am using the data provided by Bondora on all its previous applications to reveal how the resulting loans that share similar characteristics have performed.

Specifically, I am using this data to show the percentage of those previous loans that have defaulted and using this to indicate how a similar, new application may perform should the application succeed in attracting enough investors.

In other words, I am using past performance data to show how future investments may perform – I feel sure I have seen this phrase somewhere before! Continue reading →