CUBE Refresher

When was the corrected Nationality done for CUBE WLF Alerts?

• 31 Dec 2021

• 01 April 2021

• 31 Dec 2016

• Was there an issue?

Are we able to revive deactivated customer party keys?

• Yes

• No

Are we able to use Nationality as a sole justification to dismiss a WLF alert?

• Yes

• No

• Depends

Can we dismiss a WLF alert if there is a match between customer’s and hit alias?

• Yes

• No

Which countries do not allow dual nationalities, please choose where applicable.

• Singapore

• China

• Malaysia

• United Kingdom

FO wants to add a new product for an existing customer.

However, there is an already an open review alert that was triggered within the past 12 months.

What are the correct actions to take?

• A) Close it and open a brand new alert.

• B) Check if there is any on-going refresh/periodic review.

• C) Ignore it. Use a new alert for each new request in CUBE.

• D) Continue using the same alert, but add a note in the alert.

• E) Email to Singapore CDD + Reviewer that an existing alert is being used.

Whilst performing Periodic Review, FO would like to add a new director after receiving an updated ACRA. Upon checking, you found out that there are 3 duplicated parties.

What should you consider or do?

• Keep the party key with the latest information.

• Check which party key has the most connected parties.

• Create a new party key and indicate all the rest “To be deleted"

• Keep the party key that has the nicest number.

FO wants to on-board a new customer that is a major shareholder of our existing customer.

What should you do?

• Request CS team to trigger an OB form for this new customer

• Create a new party key for this new customer and mark the REL_ENTITY entry as “To be deleted”

• Find the shareholder’s party key and convert it to ‘Customer’