{"id":203,"date":"2022-03-10T20:22:46","date_gmt":"2022-03-10T19:22:46","guid":{"rendered":"https:\/\/kaczmarskilegal.pl\/?p=203"},"modified":"2022-03-11T07:31:56","modified_gmt":"2022-03-11T06:31:56","slug":"ongoing-risk-based-customer-due-diligence","status":"publish","type":"post","link":"https:\/\/kaczmarskilegal.pl\/?p=203","title":{"rendered":"Ongoing Risk-based Customer Due Diligence"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

Sometimes we may wonder, what Ongoing Risk-Based Customer Due Diligence means. The easiest answer is that we need to constantly monitor our relationship with a customer bearing in mind the diagnosed risks embedded in this relationship<\/span>. When we translate this model into practice we could consider three variables:<\/p>\n\n\n\n

  1. static customer information<\/span><\/strong> collected, verified and documented at the onboarding of the relationship<\/li>
  2. changes to the static customer information<\/span><\/strong> identified in the course of the relationship, verified and documented and finally <\/li>
  3. understanding of the financial transactions<\/span><\/strong> between us and our customers, or in case of AML\/CFT compliance the known incoming and outgoing transactions of the the customer executed in the course of relationship with the obliged institution<\/li><\/ol>\n\n\n\n

    – and the risks associated with these variables<\/span><\/strong>. More about the risk assessment and risk scoring can be found in the prior blog entries.<\/p>\n\n\n\n

    The simplified model of the static customer information<\/span><\/strong> can be found below:<\/p>\n\n\n\n

    \"\"
    Source: self study<\/figcaption><\/figure>\n\n\n\n

    The static customer information<\/span><\/strong> need to be monitored for changes<\/span><\/strong>. Frequency of change monitoring depends on available technology. It may be performed on regular basis, e.g. annually or biannually, or constantly, in particular in respect to the e.g. sanctions. <\/p>\n\n\n\n

    Possible change monitoring model has been presented in the below table:<\/p>\n\n\n\n

    \"\"
    Source: self study<\/figcaption><\/figure>\n\n\n\n

    On top of the static customer information<\/span><\/strong> and its changes<\/span><\/strong> we will also encounter customer transactions<\/span><\/strong> that we also need to monitor<\/span><\/strong> for consistency with our understanding of the customer’s business relationship with us and our risk appetite<\/span><\/strong> associated with this relationship. Possible sample transaction monitoring model can be found in the below table: <\/p>\n\n\n\n

    \"\"
    Source: self study<\/figcaption><\/figure>\n\n\n\n

    All the above is often performed with application of sophisticated technology platforms, however as you may see the basic concept behind these platforms is pretty simple and for low volume of customers and transactions the DIY approach may suffice. <\/p>\n\n\n\n

    More blog entries to come. thank you for bearing with me \ud83d\ude42 <\/p>\n\n\n\n

    \n
    \"\"
    Initial customer intake<\/figcaption><\/figure>\n\n\n\n
    \"\"
    Change monitoring<\/figcaption><\/figure>\n\n\n\n
    \"\"
    Transaction monitoring<\/figcaption><\/figure>\n<\/figure>\n","protected":false},"excerpt":{"rendered":"

    Sometimes we may wonder, what Ongoing Risk-Based Customer Due Diligence means. The easiest answer is that we need to constantly monitor our relationship with a customer bearing in mind the diagnosed risks embedded in this relationship. When we translate this model into practice we could consider three variables: static customer information collected, verified and documented… Continue reading Ongoing Risk-based Customer Due Diligence<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5,9,8],"tags":[],"class_list":["post-203","post","type-post","status-publish","format-standard","hentry","category-aml","category-cft","category-due-diligence","category-kyc","entry"],"_links":{"self":[{"href":"https:\/\/kaczmarskilegal.pl\/index.php?rest_route=\/wp\/v2\/posts\/203","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kaczmarskilegal.pl\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kaczmarskilegal.pl\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kaczmarskilegal.pl\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kaczmarskilegal.pl\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=203"}],"version-history":[{"count":3,"href":"https:\/\/kaczmarskilegal.pl\/index.php?rest_route=\/wp\/v2\/posts\/203\/revisions"}],"predecessor-version":[{"id":215,"href":"https:\/\/kaczmarskilegal.pl\/index.php?rest_route=\/wp\/v2\/posts\/203\/revisions\/215"}],"wp:attachment":[{"href":"https:\/\/kaczmarskilegal.pl\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=203"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kaczmarskilegal.pl\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=203"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kaczmarskilegal.pl\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=203"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}