from m diff fferent t prospe pecti ctive ve
play

From m diff fferent t prospe pecti ctive ve 1 Maleka Ali, - PowerPoint PPT Presentation

Educat ucator or Fina nancia cial l Insti titut tutio ion Maleka Ali, CAMS-AUDIT Myrna Olvera, CAMS Director of Consulting/Education SVP/Operations Risk Manager Bankers Toolbox, Inc . City National Bank Exami amine ner Con onsu


  1. Educat ucator or Fina nancia cial l Insti titut tutio ion Maleka Ali, CAMS-AUDIT Myrna Olvera, CAMS Director of Consulting/Education SVP/Operations Risk Manager Banker’s Toolbox, Inc . City National Bank Exami amine ner Con onsu sult ltant ant Elizabeth Slim, CAMS Robert Casares, CAMS SVP/BSA Officer Managing Director 1 st Enterprise Bank SentryNet, LLC From m diff fferent t prospe pecti ctive ve 1

  2. Maleka Ali, CAMS-AUDIT Director of Consulting & Education Banker’s Toolbox, Inc. maleka@bankerstoolbox.com 2

  3.  Tough exams  Tougher expectations 3

  4. Last st Year: ear:  Senate Banking Committee examined state of affairs following a string of large- bank BSA violations  Since then regulators are under pressure to improve BSA/AML regime.  “This pattern of violations is disturbing. . . To address this threat we must understand how banks’ safeguards malfunction and assess the way the government enforces our AML rules.” 4

  5. Emphasis on Efficiency How well are you equipped? Processes and Procedures and Systems Are they How are making those an tools impact? working? Are they being used properly? 5

  6.  Area of growing attention & expense — is BSA/AML data validation  Examiners suggest audits on BSA/AML activity monitoring systems to ensure they are performing correctly — producing reliable alerts & accurate reports of potential criminal activity  Data integrity from end to end is one concern, but there’s more to the validation process 6

  7.  Many institutions have proactively had efficiency reviews/evaluations done before exams to catch issues before examiners visit.  Examiners want to see what banks have done with the systems they purchased • Automation brings you powerful tools, but are they all turned on? • If they have been, have the rules of the system been kept up-to-date in recognition of evolving money-laundering patterns? 7

  8. FFIEC EC Manual: l: Evalu Ev luating ing the Pr Program ram Under der Tran ansacti saction Mon onitor torin ing: g:  “Management should periodically evaluate the appropriateness of filtering criteria and thresholds used in the monitoring process. Each bank should Evaluations evaluate and identify filtering criteria most are addressed appropriate for their bank. The programming of in Transaction the bank’s monitoring systems should be and independently reviewed for reasonable filtering Surveillance criteria.” Monitoring sections Under der Sur urveil eillan lance e Mon onit itorin ing: g:  “Management should also periodically review the filtering criteria and thresholds established to ensure that they are still effective. In addition, the monitoring system’s programming methodology and effectiveness should be independently validated to ensure that the models are detecting potentially suspicious activity.” 8

  9. Program Evaluations Evaluate/identify filtering criteria most appropriate for your institution “Is your program sufficient for the risk level of your institution” 9

  10. Program Evaluation Review & test system  capabilities & thresholds on a periodic basis Focus on specific  parameters or filters in order to ensure that suspicious or unusual activity will be captured Understanding the filters in your system and how your system works is critical to assessing the effectiveness of your monitoring program 10

  11. Program Evaluation  Consider higher-risk products & services, customers & entities, & geographies • Filters should be based on what is reasonable & expected for each type of account 11

  12. 12

  13. Quantitative method, system, or approach That applies statistical, economic, financial, mathematical theories, techniques and assumptions To process input data into quantitative estimates 13

  14. Information/Input Processing Reporting 14

  15.  Development  Implementation  Use  Validation 15

  16.  Fundamental Design & Implementation Errors  Data Quality  Applicable Data Inputs  Incorrect or Inappropriate Data  Optimization 16

  17. Conceptual Syntax Data Quality & Model Validation & Soundness Validation Integrity Performance Sustainability • Does Model logic • Does the code • Is data completely & • Is the model • Is proper properly account for capture data without accurately passed to performing as governance in place institutional risk? errors? monitoring platform intended (i.e. to manage approval capturing the process and model • Are assumptions • Testable through • Review of controls desired behavior? changes? sound and code replication or or analysis of data appropriate for the control data extracts • Validation cycle? environment? • Out of cycle? • Assumptions may have to be tested 17

  18.  When is a Rule/Scenario Effective? ◦ Effective is measured by “meaningful” investigations ◦ A “meaningful’ investigation could result in a “no - SAR” decision ◦ Effectiveness will differ based on intended purpose of the scenario  Results driven by individual scenario threshold testing 18

  19. Approval of your Model?  Authority to establish or change filters should be clearly defined  Should require approval of BSA officer or senior management  Document and be able to explain filtering criteria, thresholds used, & how both are appropriate for your risks 19

  20.  Examiner evaluation of scenarios ◦ System capabilities  Scenarios available  Transaction/data feeds in the system  Scenarios selected by Financial Institution ◦ Criminal Typologies ◦ Incorporation of the Risk Assessment  Higher Risk Customers 20

  21.  Use of Default Settings  No below/above the line testing  Lack or Insufficient documentation supporting scenarios or thresholds  Scarce Evidence of threshold Validation  Unsupported Sampling Methodology  Exclusion of Customers, Products, Services 21

  22.  Validation is a living and breathing lifecycle which has matured with age and doesn’t have to be cumbersome  I ndustry has moved into taking a risk based approach to validation and this makes perfect sense; adopt a proficient risk management methodology 22

  23.  For years many institutions took the approach that in order to satisfy regulatory expectations, everything should be validated all of the time, this is simply not the case  in most instances validating everything, every-time is just a waste of time, money, human resources and the various rain forests of the world.  Take a Risk Based Approach  Determine what information is important  And focus on quality 23

  24.  Not all institutions are the same  Just like your BSA program- your validation should also be risk based 24

  25. Can I expect to catch everything? 25

  26. High Level Assessment Full Model Validation 1. C Conce ceptua ptual l Soundne dness ss of AML Models Qualitative analysis of the current rule set to assess risk coverage; analysis of rules to assess model logic. Analysis and testing of underlying model assumptions to establish validity -Assess documentation around -Analyze rule set to assess risk the genesis of the rule set and the coverage and industry conformance. underlying model assumptions Conduct formal hypotheses tests of assumptions 26

  27. High Level Assessment Full Model Validation 2. 2. Assessme sessment nt of Da Data Integrit ity y and Quality ty Assess the data requirements of the AML models and assist the Bank in determining whether these requirements are fully met or whether any relevant information appears lost or corrupted in the data flow from source systems to monitoring systems -Review documentation on -Perform testing of sample data systems, intermediate obtained from all source systems to warehousing, and transformations assess the integrity of all data feeds for data feeds, and assess quality -Perform data quality and of controls in place to determine comprehensive testing for all critical effectiveness of the data inputs. elements. 27

  28. High Level Assessment Full Model Validation 3. S Syntax tax Validati tion on of C Current rent Transa nsacti ction on Monitor oring ing Syste tems Assess the accuracy of the code used to implement the scenarios N/A -Validate rules syntax by code review -Validate rules by independent replication 28

Recommend


More recommend