The AML (Anti-Money Laundering) check is a mandatory process that ensures that the payments comply with the requirements of the CTF (Counter-Terrorism Financing) policies and financial sanctions regulations.
The AML check is a part of outgoing and incoming payment processing:
For outgoing payments, the AML check is the next step after the payment initiation.
For incoming payments, the AML check is the first step. And it takes place before crediting the payment to the beneficiary account.
When the payment is under AML review, the status automatically changes to AML_REVIEW. After the AML check is completed, there are two possible outcomes:
The payment passed the AML check.
The payment status changes to AML_APPROVED.
The automated payment processing continues in the following way:
The outgoing payment moves to the payment settlement step.
The incoming payment is credited to the beneficiary's account.
The payment did not pass the AML check.
The payment remains in the AML_REVIEW status.
The payment processing stops.
The payment will be available for resolution under the payment dashboard item Payments for AML approval.
To find the payments that did not pass the AML check:
Click on the Tuum logo in the upper left corner to access the home page.
On the payments dashboard, select the Payments for AML approval option.
Find the payment in question and click the Payment identifier to view the payment details page.
On the payments view page, you can choose the intended action:
Click the AML approve/AML decline button.
Write a comment about the decision and click the Go button.
You can find more information about suspicious payments in the AML service provider interface.
If you have an integration with Hawk.ai, you can access the AML information by clicking AML processes > AML detection identifier.
There are two scenarios of how the AML suspicious payments are handled:
The payment is approved.
The automated payment processing continues in the following way:
The outgoing payment moves to the payment settlement step.
The incoming payment is credited to the beneficiary's account.
The payment is declined.
The payment status changes to CANCELLED.
The payment processing stops.
In Tuum, there are two more steps where the automatic processing of incoming payments can get stopped:
Before the AML check, if you have an additional confirmation for incoming payments enabled.
After the AML check, when automated crediting of the beneficiary account fails.
If you enable additional confirmation for incoming payments, the automatic processing gets stopped before the AML check. Then, depending on the configuration, one or many persons must approve the payment to allow automated payment processing to continue.
If the automatic crediting payment to the beneficiary account fails, the processing is stopped. The Tuum system updates the information on the payment dashboard. Below you can find instructions on how to resolve this case.
Payments that failed in the crediting beneficiary's account process are visible on the Payments dashboard - Payments for clarification.
To find the payments that need clarification:
Click the Tuum logo on the upper left corner to open the home page.
On the home page, find the Payments block.
In the Payments block, click the Payments for clarification option.
Look for the payment in question, and click the Payment identifier to view the detailed information.
On the payment details page, there are three options for proceeding with the payment:
Add document,
Return,
Credit to account,
View/add comments.
Click on the Return button.
Fill in the return details and choose the return reason and click the Save button.
To credit the payment to an account:
Click the Credit to account button.
Enter the account number where the payment should be sent and click the Go button.
After the AML check, Tuum sends the payment data to the service provider-specific module responsible for generating the message based on the provider requirements and sending it to the provider system.
Tuum offers connectivity options with the following payment service providers:
SEPA is the connection to the Centrolink system.
LHV is the connection to the LHV bank.
BC is the connection to the Banking Circle bank.
CurrencyCloud is the connection to the CurrencyCloud system.
SWIFT is the connection to any bank capable of communicating via SWIFT.
Below you will find more information on monitoring the settlement processes.
The payment settlement consists of four steps:
Creating a payment instrument - credit transfer.
Compiling a payment file.
Sending a payment file to the settlement service provider.
Receiving settlement results from the settlement service provider.
Click the Payment identifier to view the payment details page.
Check the status in the Payment and related messages section.
If the settlement status is SETTLED, the payment settlement process is completed successfully.
However, any other credit transfer status means the payment settlement is incomplete. You can click on the Events option to view which steps of the payment settlement are already completed.
You can find payments that failed the settlement process:
Click the Tuum logo on the upper left corner to open the home page.
On the home page, find the payments dashboard.
Choose the option matching your search request:
Failed SEPA files,
Failed LHV files,
Failed BC files,
Failed SWIFT files,
Failed CurrencyCloud files.
Click the File ID to view the payment file.
Click the Tuum logo on the upper left corner to open the home page.
On the home page, find the payments dashboard.
Choose the option matching your search request:
Rejected SEPA messages,
Rejected LHV messages,
Rejected BC messages.
Click the Payment ID to view the payment details.
On the payment details page, you can:
View/add comments (located under the Payment details section) - Add and view custom comments.
Re-execute rejected message (located under the Payment details section) - Re-try processing a failed message.
Recall payment (located under the Payment details section) - Recall a payment by choosing one of the recall reasons:
Duplicate payment,
Fraud,
Technical reason,
Wrong IBAN,
Wrong amount,
Customer Decision.
the payment in question.
In Tuum, the processing of outgoing payments after initiation and incoming payments is fully automated. Therefore, if the processing goes without issues, there is no need for the to take action. However, if automatic payment processing stops due to some issues, the payment operator must investigate and take corrective action.
In this section, you will find information about the following:
