2023: Week 12 - Regulatory Reporting Alignment

Challenge by: Jenny Martin

The challenge this week is heavily inspired by a real life scenario and I'm sure many organisations will be able to relate to the quirky rules they have to follow when doing regulatory reporting. Often with the reasoning behind it being "because that's the way it's always been done!" 

Data Source Bank must assign new customers to the next working day, even if they join at the weekend, or online on a public holiday. What's more, they need to report their total new customers for the month on the last working day of the month. This means any customers joining on that last working day will actually be counted in the following month. For example, 31st December 2021 was a Friday. The total number of customers for December would be reported on this day. Any customers joining on the day of 31st December 2021 itself will be counted in January's count of new customers. 

What makes this even more confusing is trying to align with branches in Ireland. Ireland will of course have different Bank Holidays and so the definition of a working day becomes harder to define. For DSB, the UK reporting day supersedes the ROI reporting day. If the UK has a bank holiday where ROI does not, these customers will be reported on the next working day in the UK. If ROI has a bank holiday where the UK does not, the customer count will be 0 for ROI, but it will still be treated as a working day when assigning the reporting month start/end.

Inputs

We have 3 inputs to work with:
  1. UK Bank Holidays 
  2. New Customers (from the UK) 

  3. ROI New Customers (already assigned to the next working day in Ireland) 

Requirements

  • Input the data
  • Fill down the years and create a date field for the UK bank holidays
  • Combine with the UK New Customer dataset
  • Create a Reporting Day flag
    • UK bank holidays are not reporting days
    • Weekends are not reporting days
  • For non-reporting days, assign the customers to the next reporting day
  • Calculate the reporting month, as per the definition above
  • Filter out January 2024 dates
  • Calculate the reporting day, defined as the order of days in the reporting month
    • You'll notice reporting months often have different numbers of days!
  • Now let's focus on ROI data. This has already been through a similar process to the above, but using the ROI bank holidays. We'll have to align it with the UK reporting schedule
  • Rename fields so it's clear which fields are ROI and which are UK
  • Combine with UK data
  • For days which do not align, find the next UK reporting day and assign new customers to that day (for more detail, refer to the above description of the challenge)
  • Make sure null customer values are replaced with 0's
  • Create a flag to find which dates have differing reporting months when using the ROI/UK systems
  • Output the data

Output


  • 7 fields
    • Misalignment flag
    • Reporting Month
    • Reporting Day
    • Reporting Date
    • UK New Customers
    • ROI New Customers
    • ROI Reporting Month
  • 501 rows (502 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

2024: Week 1 - Prep Air's Flow Card

Image
Created by: Carl Allchin Welcome to a New Year of Preppin' Data challenges. For anyone new to the challenges then let us give you an overview how the weekly challenge works.  Each Wednesday the Preppin' crew (Jenny, myself or a guest contributor) drop a data set(s) that requires some reshaping and/or cleaning to get it ready for analysis.  You can use any tool or language you want to do the reshaping (we build the challenges in Tableau Prep but love seeing different tools being learnt / tried). Share your solution on LinkedIn, Twitter/X, GitHub or the Tableau Forums Fill out our tracker so you can monitor your progress and involvement The following Tuesday we will post a written solution in Tableau Prep (thanks Tom) and a video walkthrough too (thanks Jenny) As with each January for the last few years, we'll set a number of challenges aimed at beginners. This is a great way to learn a number of fundamental data preparation skills or a chance to learn a new tool — New Year...
Read more

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 u...
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