taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit af071c70817285ed21f6fafddcda277a8b8db539
parent 6c795f39a1a61617d2b55b758236224643545e54
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Tue, 18 Mar 2025 14:33:42 +0100

clarify that we escalate to management if there are concerns, not always

Diffstat:
Mdeployments/tops.rst | 13+++++++------
1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/deployments/tops.rst b/deployments/tops.rst @@ -51,12 +51,13 @@ Establishing a Business Relationship then processed manually. 4. When all the required data has been provided, it is in any case checked - manually by the AML officer. Finally, the AMLO officer must define - risk-based rules for monitoring the business relationship. The money - laundering reporting officer makes a recommendation to the management as to - whether the business relationship can be opened from the money laundering - reporting officer's point of view or not. The management decides on - acceptance or rejection. + manually by the AML officer. Finally, the AML officer must categorize + the customer to to derive a risk profile. Based on the risk profile, + risk-based rules are set for monitoring the business relationship. If + the AML officer has concerns about the business, they + escalate the case to the management as to whether the + business relationship can be opened. + The management can then make a final decision on acceptance or rejection. Monitoring a Business Relationship ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^