2023: Week 7 - Flagging Fraudulent Suspicions
Challenge by: Jenny Martin
As in many organisations, sometimes the answer to a question can only be found by combining multiple datasets together. Data Source Bank are looking to find transactions which may possibly be fraudulent. They define potentially fraudulent transactions as:
- Being more than £1,000 in value
- Excluding cancelled transactions
- Platinum Bank Accounts have different rules for identifying fraudulent transactions so we will exclude them from our analysis
What the fraud team need is the ability to make phone calls to customers to double check whether these transactions are genuine.
Inputs
The data is spread across 4 different tables. We've provided an extract for each of these.
Requirements
- Input the data
- For the Transaction Path table:
- Make sure field naming convention matches the other tables
- i.e. instead of Account_From it should be Account From
- For the Account Information table:
- Make sure there are no null values in the Account Holder ID
- Ensure there is one row per Account Holder ID
- Joint accounts will have 2 Account Holders, we want a row for each of them
- For the Account Holders table:
- Make sure the phone numbers start with 07
- Bring the tables together
- Filter out cancelled transactions
- Filter to transactions greater than £1,000 in value
- Filter out Platinum accounts
- Output the data
Output
- 12 fields
- Transaction ID
- Account To
- Transaction Date
- Value
- Account Number
- Account Type
- Balance Date
- Balance
- Name
- Date of Birth
- Contact Number
- First Line of Address
- 476 rows (477 including headers)
You can download all the outputs from here
After you finish the challenge make sure to fill in the participation tracker, then share your solution on Twitter using #PreppinData and tagging @Datajedininja, @JennyMartinDS14 & @TomProwse1
You can also post your solution on the Tableau Forum where we have a Preppin' Data community page. Post your solutions and ask questions if you need any help!