3
Shared Docs
3
Same-Page
3 / 3
Mentions
an review to determine if the ACU can be closed out without a KYC update. b) For the HRIP meeting report: The High Risk in Person Meeting field in DBForce pulls from the ACU. In order to record that a meeting took place, it needs to be included in an ACU even if the ACU isn't "due" yet. This is the o
way to get it off the report. If a client meeting is not possible, you need to work with AML compliance for an exception or extension. c) For the TempExceptions report: If the Temporary Exception should be closed, please email us the case 8, explanation and resolution so that we can close it. (See attached
be completed b) "KYC in Progress" it means that the KYC must be completed 2) For the HRIP Meeting report: The High Risk in Person Meeting field in DBForce pulls from the ACU. In order to record that a meeting took place, it needs to be included in an ACU even if the ACU isn't "due" yet. This is the o
way to get it off the report. If a client meeting is not possible, you need to work with AML compliance for an exception or extension. 3) For the TempExceptions report: If the Temporary Exception should be closed, please email us the case #, explanation and resolution so that we can close it. (See attached
be completed b) "KYC in Progress" it means that the KYC must be completed 2) For the HRIP Meeting report: The High Risk in Person Meeting field in DBForce pulls from the ACU. In order to record that a meeting took place, it needs to be included in an ACU even if the ACU isn't "due" yet. This is the o
way to get it off the report. If a client meeting is not possible, you need to work with AML compliance for an exception or extension. 3) For the TempExceptions report: If the Temporary Exception should be closed, please email us the case I, explanation and resolution so that we can close it. (See attached
Entities connected to both DBForce and TempExceptions