Update Match Status
This suite of processes is designed to analyze and identify the data de-synchronization between Mambu and ComplyAdvantage for clients and groups and automatically fix problems related to the synchronization of the
There are two available processes:
1. CLIENTS script for sync match_status process is run manually in Mambu Process Orchestrator (MPO) without any input data. It goes through all the clients with a state other than
Exited and a valid
aml_searchId custom field in Mambu. The process compares the
aml_matchStatus custom field value in Mambu with the value in ComplyAdvantage. The analysis determines if the
match_status field from Mambu and ComplyAdvantage is not properly synchronized for each client. It is important to note that the
match_status value from ComplyAdvantage will be used as a reference to fix all the clients in Mambu.
1. GROUPS script for sync match_status process is run manually in MPO without any input data. The process compares the value of the
aml_matchStatus custom field in Mambu with the value in ComplyAdvantage, for all groups with value other than
Rejected in the
aml_stopMonitoring custom field and a valid
aml_searchId custom field in Mambu. It is important to note that the
match_status value from ComplyAdvantage will be used as a reference to fix all the groups in Mambu.
While running either one of these processes, if an entity (client or group) is found to have conflicting data, it is included in the final report, which is stored in the
2. Sync clients/groups data state diagram. This report can be found in the
Reports with mismatch data for clients / groups state and has the following format:
groupIdsListarray, which contains Mambu IDs of groups that were found to have issues, or
clientIdsListarray, which holds Mambu IDs for each client.
We recommend that you run this script outside working hours due to the large number of API calls made for each entity during the diagnosis process.
The fix process can only be triggered by modifying the tasks (diagnosis reports) from the
Reports with mismatch data for clients / groups state in the
2. Sync clients/groups data state diagram and adding the
"apply": true boolean flag.
The process starts by running a list of clients or groups. The purpose of this synchronization is to ensure that the status for each client or group is exactly the same between Mambu and ComplyAdvantage.
If all issues are fixed, a final report is logged in the
Execution status = Completed state and contains the Mambu IDs of the entities that were fixed. If not all fixes were successful, a report is logged in the
Execution status = Partial Completed state and contains the Mambu IDs of the entities that were fixed and entities that still have issues.
Execution status = Partial Completed state contains Mambu IDs that still have issues, you must manually run the
Fix process [by list of clients] process for clients or
Fix process [by list of groups] process for groups to fix the entities.
Fix process [by list of clients] and
Fix process [by list of clients] processes are run manually in MPO with one input parameter:
groupIdsList. The processes go through every client or group from the respective lists and analyze the status between Mambu and ComplyAdvantage, in the same way as the
2. Sync clients/groups data process.