Skip to content

Branch Isn't Following OFAC Procedures

Answered by: 

Question: 
One of our branches has a customer (a builder) writing large checks to their employees on a weekly basis ($5k-$7k). The builder comes in with the employee to cash the check. The employee endorses first, then the builder endorses and cashes the check. The builder is a known customer, so the tellers do not get identification on him and since he endorses after the payee they are not getting the payee's identification. They are, however, checking the payee/employee against OFAC. Bank policy states that we check OFAC on all non-customer payees over $1000 and record identification on non-customers and payees over $3000. I am getting a match on two of the three employees. I am 90% sure that it is a false positive, but I cannot confirm or deny it is a valid hit unless I can compare their identification information to the hit. The branches administrator was notified that the branch is not following bank policy and that identification needs to be obtained on the payees. The branch defends their actions stating that, technically, they are not making an exception since the employee and builder are presenting on-us checks we are able to verify funds and also that the last endorser is vouching for the non-customer. I understand their concern because it is technically true, but as the Compliance Officer I also understand that, per OFAC, banks must block transactions that are by or on behalf of a blocked individual or entity. If this branch continues to willfully ignore the intent of the customer, which is to give money to this employee, we will end up with severe penalties if the payee is found to be a blocked individual. This is a risk I would rather the bank not take. Can you shed some light on the subject?
Answer: 

Make them follow your policy. If your OFAC risk assessment indicates that in order to properly mitagate OFAC risks the checking of OFAC when cashing checks for non-customers is a prudent action, then you have no choice. The fact that the check is transfered to a third party first does not mitigate this risk.

First published on BankersOnline.com 6/04/07

First published on 06/04/2007

Filed under: 
Filed under compliance as: 
Filed under security as: 

Search Topics