Challenge #490: Detecting Money Laundering

[mmontgomery]

C490.

Spoiler

Flashes of AoC

[Carolyn]

That was really fun! It reminded me a bit of an Advent of Code challenge with tracking the paths of the money

Spoiler

[wbasuki]

My Solution

Spoiler

[apmessner]

I really struggled with this challenge, I think because I am not well-versed in macros.

Can you explain where the "Date Check" field comes from in your Iterative Macro? I don't see it in either of the inputs, and then it just sort of appears after the Join tool. I don't see it defined anywhere, like in the workflow constants, or in a formula tool.

Thanks!

[dman2740]

Spoiler

It was a bit difficult to do without an iterative macro where essentially the macro does the processing where it finds the transactions where the sender = receiver then ensures that the transaction amount was the same and the transactions where made on later days and the next transaction comes from the original sender.

[Yoshiro_Fujimori]

Congratulations @gawa ,

As I am working on AML as Day-to-Day business, I tried to report the transaction history as well as the transaction ID😀

Spoiler

Workflow

Macro

Output

[Yanxuliu]

Challenge #490: Detecting Money Laundering

[NothingIsImpossible]

This was a good challenge!  Not terribly difficult, but tricky to get the right order of events!  

Spoiler

Workflow


Macro

[BSilverblatt]

This is my solution:

[olga_strubbe]

Hi @apmessner - the 'Data Check' field is the field that got renamed in the 'Join' tool to that name.  The 'Join' tool gives an option to rename fields like the Select tool does to not have to use 'Select' tool after.  Hope this helps.