Anti Money Laundering Back Office System
AML Back Office System will be used by AML Officer and AML Manager from Pintek to review borrower background related to money laundering and terorism checking.
Project Overview
About this project, I didn’t start from scratch, because Pintek already have the design system and template for the back office design. And most important part, the PRD already very clear to inform me about the logic, user stories, flow and business details regarding all the requirements. So, i design the back office uset main template and create new components based on the PRD and make sure the flow are clear.
Product Requirement Document
Vision Validation
Although the primary focus of this project is the users, I thought it was also important to get some insights and think about the business goals of this applications. So I can identify what will make a product a success not only from what user's needs but also from the business side.
Business Goals
- Collaboration with each public transport company
- Wide market with quiet competitors
- High amount of users
- High retention rate
User Needs
- Schedule of arrival and departure
- One-gate payment system
Products Opportunity
- Booking and purchasing tickets can be done directly
- Ticket purchase packages for many types of transportation according to the route of departure
The Product Requirement Document (PRD) is written by Product Manager.
Context
This PRD is made to be the baseline of the AML Integration on the Revamp System as a need to comply with the regulation from OJK.
Problem Statement & Business Impact
Our current revamp system didn’t include the newly required AML/CFT process by OJK, as a move to comply with the regulatory we will need to implement the AML/CFT process into our system. This process will include the integration of 3rd party vendor as a part of our AML/CFT screening process and will change the flow of our account and loan approval flow in the revamp system.
User Story
As a System, I should be able to Capture the details of Ultimate Beneficiary Owner
As an AML Officer, I should be able to perform Batch Periodic Check through Sijitu
As a System, I should be able to Send the details to Sijitu for DTTOT & PEP verification
As an AML Officer, I should be able to Review the result of Sijitu for further verification
As an AML Manager / Head of AML, I should be able to Review the result of AML Officer analysis
As a System, I should be able to Perform Risk Based Analysis for every loan request
As an AML Officer, I should be able to Perform EDD Analysis based from the RBA Result
As an AML Manager / Head of AML, I should be able to Review the result of AML Officer EDD analysis
As an AML Officer, I should be able to Perform Suspicious Transaction analysis
As an AML Manager / Head of AML, I should be able to Review the result of AML Officer Suspicious Transaction analysis
As System, I should be able to Identify the Basic Information Update
Each user story already provided with the logic, business insight and all the details required about each feature. So I just need to start develop the design.
Sitemap
Since the PRD contains all the details, the first step that i took was creating a sitemap so everyone can see the whole structure of the dashboard. This sitemap is very useful to see how big the scope is and also as my guide when designing the pages. When the sitemap is done, i sent it to PM and Legal for approval before continuing to develop the wireframe.
If we looking back to the user stories, there is two roles on this project, AML Officer and AML Manager. I tried to differentiate the sitemap by each roles.
AML Officer
Basically, there is two layer verification. After the AML Officer decide each documents hit or no hit and suspicious or not suspicious, the data will be transferred to AML Manager dashboard for the final decision. Except for the UBO, all the components between AML Officer and AML Manager are almost same.
AML Manager
Vision Validation
Although the primary focus of this project is the users, I thought it was also important to get some insights and think about the business goals of this applications. So I can identify what will make a product a success not only from what user's needs but also from the business side.
Business Goals
- Collaboration with each public transport company
- Wide market with quiet competitors
- High amount of users
- High retention rate
User Needs
- Schedule of arrival and departure
- One-gate payment system
Products Opportunity
- Booking and purchasing tickets can be done directly
- Ticket purchase packages for many types of transportation according to the route of departure
Wireframe
Vision Validation
Although the primary focus of this project is the users, I thought it was also important to get some insights and think about the business goals of this applications. So I can identify what will make a product a success not only from what user's needs but also from the business side.
Business Goals
- Collaboration with each public transport company
- Wide market with quiet competitors
- High amount of users
- High retention rate
User Needs
- Schedule of arrival and departure
- One-gate payment system
Products Opportunity
- Booking and purchasing tickets can be done directly
- Ticket purchase packages for many types of transportation according to the route of departure
Because there is only slightly difference between AML Officer and AML Manager dashboard, for the next step I will only show the wireframe and design of the AML Officer Back Office.
Ultimate Beneficiary Owner (UBO) Check
Ultimate Beneficiary Owner (UBO) is selected by AML Officer from all the majority shareholder of the company borrower.
DTTOT
Daftar Terduga Teroris dan Organisasi Teroris (DTTOT) is a list we got from PPATK and AML Officer regularly check the updated DTTOT list with Pintek borrower list. The system will receive help from Sijitu to check the data.
Sijitu
On Sijitu page, almost the same like DTTOT. The difference is that on DTTOT page, the check will be done regularly once there is updated DTTOT list from PPATK. But on Sijitu page, we check for one person each time they apply for new loan.
EDD Review
Enhance Due Diligence (EDD) Review will be done parallely while the application of the borrower being reviewed by the risk team. By performing this, AML Officer can decide suspicious and not suspicious borrower and report it to PPATK.
Transactional Review
Transactional review page, let AML Officer to review borrower who trying to paid the installment all at once (there is a lot of condition). By performing this, AML Officer can also decide suspicious and not suspicious borrower and report it to PPATK.
Design V1
Vision Validation
Although the primary focus of this project is the users, I thought it was also important to get some insights and think about the business goals of this applications. So I can identify what will make a product a success not only from what user's needs but also from the business side.
Business Goals
- Collaboration with each public transport company
- Wide market with quiet competitors
- High amount of users
- High retention rate
User Needs
- Schedule of arrival and departure
- One-gate payment system
Products Opportunity
- Booking and purchasing tickets can be done directly
- Ticket purchase packages for many types of transportation according to the route of departure
After the wireframe is done, I present it to PM and Legal team to gaining feedback before start to turn it into high fidelity design. There is only few revision from the wireframe so you may find a few differences between the wireframe and high fidelity design.
Ultimate Beneficiary Owner (UBO) Check
DTTOT
Sijitu
EDD Review
Transactional Review
Design Feedback
Vision Validation
Although the primary focus of this project is the users, I thought it was also important to get some insights and think about the business goals of this applications. So I can identify what will make a product a success not only from what user's needs but also from the business side.
Business Goals
- Collaboration with each public transport company
- Wide market with quiet competitors
- High amount of users
- High retention rate
User Needs
- Schedule of arrival and departure
- One-gate payment system
Products Opportunity
- Booking and purchasing tickets can be done directly
- Ticket purchase packages for many types of transportation according to the route of departure
After finishing all the high fidelity design, I present it again to the PM and Legal team to check the flow of the prototype and the components. There is some major feedback on the DTTOT page but overall on the other pages only got small revision about the microcopy, data items, etc.
Design Changes
Vision Validation
Although the primary focus of this project is the users, I thought it was also important to get some insights and think about the business goals of this applications. So I can identify what will make a product a success not only from what user's needs but also from the business side.
Business Goals
- Collaboration with each public transport company
- Wide market with quiet competitors
- High amount of users
- High retention rate
User Needs
- Schedule of arrival and departure
- One-gate payment system
Products Opportunity
- Booking and purchasing tickets can be done directly
- Ticket purchase packages for many types of transportation according to the route of departure
The major changes only for the DTTOT page, so here I can show you the differences between previous and latest design.
Layout of the page
Detailed Result
Final Statement
Vision Validation
Although the primary focus of this project is the users, I thought it was also important to get some insights and think about the business goals of this applications. So I can identify what will make a product a success not only from what user's needs but also from the business side.
Business Goals
- Collaboration with each public transport company
- Wide market with quiet competitors
- High amount of users
- High retention rate
User Needs
- Schedule of arrival and departure
- One-gate payment system
Products Opportunity
- Booking and purchasing tickets can be done directly
- Ticket purchase packages for many types of transportation according to the route of departure
Working on this project is very challenging because I jump into field that I've never known before. In this example, I have to learn all about anti money laundering things such as UBO, DTTOT, EDD, etc and logic about how to prevent the risk.
I do realize that there is some miscommunication which make me change the layout of the design very late when all the design is complete. Because if we talk about layout, it should have been approved after we check on the wireframe. This happen because the Senior PM couldn't attend the wireframe approval meeting so he couldn't review it first. I believe this won't happen if we try to communicate it before. This will be a valuable lesson from my side to communicate better in the future.
What is the next step?
The final design already approved, so the next step will be grooming session with frontend team to discuss about the possibility in terms of logic and design component. After all finish the QA team will test the live site and doing UAT with the user.
%202.svg)
%201.svg)