Challenge 1 - Proactive Analysis into Reporting Patterns
This notebook involves proactive analysis into transaction reporting patterns. The structured example involves downloading, processing, exploring data for all reports then analysing for reporting pattern anomolies. The unstructured extension component involves the analysis of transaction reporting delay.
%%capture capt
Explore Data
Leverage a Data Exploration Analysis (EDA) tool - the below example uses sweetviz.
Pandas profiling is another good option.
## Create Daily Count Summary
Identify Anomalies
Process the extracted data to generate an expected pattern of activity (for transaction report counts and amounts). Then identify reporting that falls outside that pattern.
The below two charts illustrate that generally speaking transaction reporting counts and amounts have been slowly increasing over the period - with a few dips for public holidays.
They also identify that for a period in March 2020, reporting volumes drifted well above the expected band, which warrants futher investigation. It may mean some transaction reporting has been duplicated.
Competition Unstructured Extension
Transaction reporting delay (the difference between when a transaction occurs and when the related report is submitted) maybe an indicator of data processing issues at the reporter or other significant issues. Analyse transaction reporting delay over the period and identify any anomalies that have occured. Additionally identify if average reporting delay is uniform across the reporting population.