This article is part of our RPA blog series and deals with the underlying potentials of RPA for the digitization of financial institutions’ KYC (Know Your Customer) processes. In this regard, the article will provide you with useful insights on:
1. Which drivers are requiring the digitization of KYC processes;
2. Why the implementation of RPA within the KYC domain is becoming a crucial success factor and competitive differentiator;
3. Which processes can be automated;
4. How it can be approached.
1. What are the drivers requiring the digitization of KYC processes?
Increasing regulatory requirements raise complexity of KYC and sanction landscape
With rising and “scope broadening” regulatory requirements, an ever-increasing number of sectors and lists have to be screened against a financial institution’s clients’ names, counting millions of names, from ‘political persons’ to ‘state-owned companies’ to ‘dual-use materials’. At the same time, financial institutions are exposed to significant remediation costs and potential fines in case they fail to comply with the regulations in force. Between 2009 and 2015 for instance, the breach of US Financial Rules only had already imposed banks a total fine of $16.5 billion .
Time consuming onboarding and post-matching processes drive operational expenses
Currently, 75%-85% of daily alerts are false positives while up to 25% are reviewed by level-two senior analysts. The alert review process is very time and cost intensive at an average cost of £20 per review, cumulating to a huge amount considering that a bank has millions of customers to screen .
This leads financial institutions to the crucial dilemma between bearing the risk of huge penalties and the unbearable cost of manual alert investigations. Hence, the consequential challenge is to reduce this to a manageable number through moving the post-matching process towards further algorithmic process automation.
Extended identity checks strain bank-customer relationships and customer experience
With the enforcement of the 4th AML Directive  customers who have previously been considered as low-risk are now to be treated as potentially high-risk customers. As a result, obtaining products becomes a more time-consuming process since passports will have to be presented more frequently and a range of questions will have to be answered to meet the requirements for KYC identity verification. In conclusion, the onboarding process becomes lengthier, customers must respond to questions that might appear intrusive and costs increase.
Facts & Figures underlining the necessity of RPA technologies for the KYC digitization :
2. What makes RPA become a crucial success factor and competitive differentiator?
The implementation of RPA embraces three dimensions which can be leveraged to release both qualitative and quantitative benefits affecting the long-term success of financial institutions’ core banking processes and client relationships.
3. For which processes can RPA be used to increase operational efficiency and compliance?
Customer Identification Program (CIP)
Risk-based KYC can tremendously reduce the need for manual CIP processes. More than 80% of the CIP functions can be automated:
- Document tracking, follow-up and reminder notifications
- Identification of incomplete or inconsistent information
- Sourcing of commercial registers
(Enhanced) Customer Due Diligence (CDD/EDD)
Complementary to the automation potential of CIP processes RPA has the potential to analyze far more data points compared to traditional risk assessments (from 50 to > 3000 data points) which proves to be a clear differentiator when it comes to risk profiling and transaction monitoring:
- Collection and screening of customer information from external and internal sources
- Download, scan and update of client databases in case of new watch list entries
- Customer background check against thousands of sources, national and international sanctions lists
- Transaction monitoring against thresholds, customer profile, internal and external data
4. Which approach would suit the implementation of RPA for your KYC processes?
In my experience, alignment, preparation and coordination are key for a successful kick-off and execution of any project. In this respect, several dimensions should be considered:
1) Governance & Strategy
- Which stakeholders should be involved and aligned with upfront?
- Does the implementation of RPA and KYC target operating model fit the overall corporate strategy? And which (corporate) functions does it imply?
2) Processes & Resources
- Which KYC processes and functions should be automated, and which are most suitable to start with or should be prioritized?
- Are there enough internal resources to support the transformation process and what is the intensity of training required to adapt to the new target operating model?
3) Clients & Geographies
- What is the amount of data cleansing needed prior to migration for existing clients and what is the status of the client relationship?
- What is the country business volume? And which country proves most suitable for a pilot / proof of concept (PoC)?
Capgemini Consulting has established an agile approach to digitize KYC processes by leveraging client specific assets in combination with RPA KYC specific best practices.
Find out more about this topic:
- Part 1: Center of Excellence & Operating Models: Why RPA is more than just a software
- Part 2: Value for money with RPA. Lessons learned from RPA audits.
- Part 3: The robot user-ID: handling RPA within existing rights & permissions structures
- Part 4: From digitization to algorithmisation: How a Chatbot can combine RPA, AI and ERP
This article was written by Lea Krämer.