2023: Week 9 - Customer Bank Statements

Challenge By: Jenny Martin

Welcome to our first ever advanced month! You've been building your skills over the last couple of months and now you're ready to put your new found data preparation skills to the test. Please don't lose heart if you find this challenge tough, it's designed to be! I'll leave a hint to a previous challenge that uses a similar technique to help you along your way.

Data Source Bank usually waits until the end of the month to let customers know their bank account balance. Customers want more control and the ability to see how their balance changes after each transaction. Let's create bank statements for them!

Inputs

The data for this week should feel very familiar! We used this data already in week 7, but we'll only need 3 of the 4 tables this week.  
  1. Transaction Path 

  2. Transaction Detail 

  3. Account Information 

Requirements

Note: I found doing this in 2022.4.1 caused a bug. However, it worked in 22.3 so consider going back to non-wavey lines for this challenge! Update: the bug is fixed in 2022.4.2!
  • 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
  • Filter out the cancelled transactions
  • Split the flow into incoming and outgoing transactions 
  • Bring the data together with the Balance as of 31st Jan 
  • Work out the order that transactions occur for each account
    • Hint: where multiple transactions happen on the same day, assume the highest value transactions happen first
  • Use a running sum to calculate the Balance for each account on each day (hint)
  • The Transaction Value should be null for 31st Jan, as this is the starting balance
  • Output the data

Output

  • 4 fields
    • Account Number
    • Balance Date
    • Balance
    • Transaction Value
  • 20,378 rows (20,379 including headers)
You can download all the output 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! 

Popular posts from this blog

2023: Week 1 The Data Source Bank

Image
 Created by: Carl Allchin Welcome to a New Year of Preppin' Data. These are weekly exercises to help you learn and develop data preparation skills. We publish the challenges on a Wednesday and share a solution the following Tuesday. You can take the challenges whenever you want and we love to see your solutions. With data preparation, there is never just one way to complete the tasks so sharing your solutions will help others learn too. Share on Twitter, LinkedIn, the Tableau Forums or wherever you want to too. Tag Jenny Martin, Tom Prowse or myself or just use the #PreppinData to share your solutions.  The challenges are designed for learning Tableau Prep but we have a broad community who complete the challenges in R, Python, SQL, DBT, EasyMorph and many other tools. We love seeing people learn new tools so feel free to use whatever tools you want to complete the challenges.  A New Year means we start afresh so January's challenges will be focused on beginners. We will use dif
Read more

2023: Week 2 - International Bank Account Numbers

Image
Challenge By: Jenny Martin For week 2 of our beginner month, Data Source Bank has a requirement to construct International Bank Account Numbers (IBANs), even for Transactions taking place in the UK. We have all the information in separate fields, we just need to put it altogether in the following order: Inputs A list of the transactions, with information about the receiving bank account  A lookup table for the SWIFT Bank Codes  Requirements Input the data In the Transactions table, there is a Sort Code field which contains dashes. We need to remove these so just have a 6 digit string ( hint ) Use the SWIFT Bank Code lookup table to bring in additional information about the SWIFT code and Check Digits of the receiving bank account ( hint ) Add a field for the Country Code ( hint ) Hint: all these transactions take place in the UK so the Country Code should be GB Create the IBAN as above ( hint ) Hint: watch out for trying to combine sting fields with numeric fields - check data types Re
Read more

How to...Handle Free Text

Image
Free isn't always a good thing. In data, Free text is the example to state when proving that statements correct. However, lots of benefit can be gained from understanding data that has been entered in Free Text fields. What do we mean by Free Text? Free Text is the string based data that comes from allowing people to type answers in to systems and forms. The resulting data is normally stored within one column, with one answer per cell. As Free Text means the answer could be anything, this is what you get - absolutely anything. From expletives to slang, the words you will find in the data may be a challenge to interpret but the text is the closest way to collect the voice of your customer / employee. The Free Text field is likely to contain long, rambling sentences that can simply be analysed. If you count these fields, you are likely to have one of each entry each. Therefore, simply counting the entries will not provide anything meaningful to your analysis. The value is in
Read more