You are currently browsing the Chetan Shah’s Blog weblog archives for the day 28 Jan 2008.
- AML (14)
- Foundation (4)
- Personal Finance (21)
- Technology (22)
- 7 Dec 2009: Move securities to Roth Account
- 28 Nov 2009: Leverage Checksum to determine identical files
- 4 Oct 2009: CAMS Certification Preparation
- 30 Aug 2009: Section 311 etc. (ACAMS Notes)
- 24 Aug 2009: FATF Membership Points (ACAMS Notes)
- 22 Aug 2009: Internet Casinos and Prepaid Cards/E-Cash (ACAMS Notes)
- 5 Aug 2009: Spousal IRA
- 15 May 2009: Buying Call Options.
- 7 Jan 2009: Watchlist filtering white paper
- 31 Oct 2008: Autonumber in Microsof Excel (works after inserting rows)
Archive for 28 Jan 2008
OFAC/SDN Watchlist Software Application Axiom #1
28 Jan 2008 by Chetan Shah.
Never try to find out whether a company has a bad guy on their books by just matching a SDN list entry with the company customer data on basis of just first name and last name. You will be surprised how many “Jose Luis” you will find in your company database.
A better approach is to use date of birth in addition to the first name and last name. This rule will generate more accurate matches and your risk analysts will thank you for not generating “False Positive”
Posted in AML | 1 Comment »
Data Analysis
28 Jan 2008 by Chetan Shah.
This might sound too much like software engineering but for any software application’s life cycle, data collection, metrics and analysis should be part of an ongoing process and different aspects of application data should be continuously harvested to understand which business rules have been really effective and which rules are not so effective. Requirements are typically written at a very initial stage of the application development and lot of business rules are perceived to be really effective and hence directly translated into technology requirements without having any solid metrics backing the requirements up.
A continuous loop back cycle (by doing data analysis) enables the application support team to come up with metrics and relevant data which they can present it back to business owners of the application and highlight what aspects of the application need to be improved and what aspects of the application can be sunsetted. This data can also be leverage for future generations of application or can also be used as input to organization’s multi generation plan.
Certainly this is not a very “cool” exercise from a developer perspective as it involves too much “SQL” but my definition of “cool” is : the system in context adds value to the business it supports. If an application uses state of art technology but does not do any good to the business partners, I think it is a waste of company’s limited/precious resources.
Posted in Technology | No Comments »
