Summary

This document is a set of training materials or study notes on banking and financial transactions processes, including daily, fortnightly and monthly reports and e-callback utility. Topics also include large transaction reporting, and various other processes.

Full Transcript

# Ace Banker Journey-Week 3 ## Day 1 - EOD/BOD Reports - Suspense Monitoring - LTR/UAS - **You are here** ## Day 2 - Liability products - Saving account ## Day 3 - Liability products- Savings account ## Day 4 - Documentation of Savings account - UCIS - Current Account ## Day 5 - NRE/NRO -...

# Ace Banker Journey-Week 3 ## Day 1 - EOD/BOD Reports - Suspense Monitoring - LTR/UAS - **You are here** ## Day 2 - Liability products - Saving account ## Day 3 - Liability products- Savings account ## Day 4 - Documentation of Savings account - UCIS - Current Account ## Day 5 - NRE/NRO - PMY schemes ## Day 6 - Fixed Deposit - SSA - Quality Sourcing # Branch Reports ## Objectives - Where to find complete list of reports to be generated by branch - What needs to be checked in these reports and who is responsible for checking them. - Are these reports to be printed or to be verified online # Reports Generation Branches generate reports on different frequencies like: - Daily - Fortnightly - Monthly We will see some of the important reports which are generated by the branches on the above mentioned frequencies. # Importance of Reports Employees play a vital role in a banking system, by ensuring the customer transaction happens smoothly and accurately. It is imperative that there has to be zero error, because any error will result in crediting, or debiting a wrong account. In order to check the correctness of the transactions, many reports are generated and verified by an independent person other than the inputter and authorizer. # What is E-CallBack? The objective of e-CallBack utility is to digitize few reports thus reducing the number of physical reports that are printed. The reports that are on the e-Callback utility can be verified & authorized online. Currently, data can be accessed only if the previous day's data is verified. ## How do we use e-CallBack? **E-Call Back** **Login Page** - Employee Code - Password - Login - Cancel # Stages in e-CallBack Utility **Transaction Report** - Log Out - Dashboard - Batch Control Register - Upload - Verify - Closed Batch Upload - Trade Finance-Imports - Delete Report # e-CallBack Dashboard View - The dashboard shows a table with the following information: - Transaction Date - Upload/Verify - Hardcopy - SystemName - ReportName - ReportDescription - Total Record - Pending for Authorization - Pending for Upload - In Progress - Pending for Regularization - Completed - No report marked for the day # e-CallBack Report Upload option - **Report Upload** - Date: - Report Type: - System: - Report File: - Upload Status - Date: - Report Name: - Report Status: - Total Record(s): - Total Uploaded: - Pending: - Verified: - Rejected: - **TS Authorization / Verification** - Acct No: - Acct. Name: - BeneName: - Chq No: - Amount - Status/Remark - Instrument No: - Authorize - Accept - Save Report - Reject - System: - Report Type - Total Records - From: - Select Report: - Total Rejected: - Total Pending: - Show Data - Selected Record(s): - Search - Clear Search # Large Transaction Reporting-CH106 - LTR portal displays the list of accounts where there is more than 1L debit/credit in the previous day. - LTR is used as a control mechanism to avoid any money mule transactions in the accounts. - For NRE & NRO accounts irrespective of any amount it will be displayed here. - Transactions more than 1L like Cash deposit/withdrawal, FT/CHQ/NEFT/RTGS/IMPS will reflect here. - Maker & Checker ID concept is available based on the role of the employee. - Branch is expected to update the details in this portal on daily basis. - LTR ID has to be created by the Branch Staff through ISAC once they report to the Branch. - LTR ID can be logged in using the same credentials used for Desktop Login. # Large Transaction Reporting (CH 106) - New User / Role Mapping / Location Updation/For ID dormant / Disabled:- Kindly log a call in Information Portal > Integrated System Access Control (ISAC). # Accounts will get queued up here. # Welcome to Large Transaction Reporting - **Account Details** - Branch Code: - Account No: - Txn. Date: - Txn Desc.: - RM Code: - Office Phone No: - Account Type: - Product Code: - Account Opening Date: - Debit/Credit: - Amount: - Txn. Code: - Txn. Amount: - Customer: - Residence Phone No: - NSF: - Ethnic Code: - Mobile No: - Called At No: - GrossIncomeDesc: - Annual TurnoverCA: - Nature_of_Business_Des: - Remarks: # Welcome to Large Transaction Reporting - **Account Details** - Branch Code: - Account No: - Txn. Date: - Txn Desc.: - RM Code: - Office Phone No: - Account Type: - Product Code: - Account Opening Date: - Debit/Credit: - Amount: - Txn. Code: - Txn. Amount: - Customer: - Residence Phone No: - NSF: - Ethnic Code: - Mobile No: - Called At No: - GrossINDesc: - OccDesc: - Remarks: # Welcome to Large Transaction Reporting - Branch Update - Pending for Updation - Pending for Review - Pending for Updation BackDate - Pending for Review BackDate - **REPORTS** - Updated Cases - NRO Credits Report - Transaction Details Report - Pending Cases - Pending Cases Branch - Pending Cases Assigned to RM - Pending Summary Report - RM Code Wise Report - NRE Accounts - SCS Tracking - Mobile App Update - IMP! Mobile App Update - **Account Details** - Branch Code: - Account No: - Txn. Date: - Txn Desc.: - RM Code: - Office Phone No: - Account Type: - Product Code: - Account Opening Date: - Debit/Credit: - Amount: - Txn. Code: - Txn. Amount: - Customer: - Residence Phone No: - NSF: - Ethnic Code: - Mobile No: - Called At No: - GrossINDesc: - Annual TurnoverCA: - Nature_of_Business_Des: - Remarks: - **Review Account For Branch Updation** - Search Criteria - From Date: - To Date: - Search Branch: - Remark: - Select: - Approve - Reject - Srno - Home Branch - Product Code - Account No. - Other Branch - Total No of Records # Welcome to Large Transaction Reporting - **Branch Update** - Pending for Updation - Pending for Review - Pending for Updation BackDate - Pending for Review BackDate - Pending for Review Assignment - **REPORTS** - Updated Cases - NRO Credits Report - Transaction Details Report - Pending Cases - Pending Cases Branch - Pending Cases Assigned to RM - Pending Summary Report - RM Code Wise Report - NRE Accounts - SCS Tracking - Mobile App Update - IMP! Mobile App Update - **Review Account For Branch Updation** - Search Criteria - From Date: - To Date: - Search Branch: - Remark: - Select: - Approve - Reject - Srno - Home Branch - Product Code - Account No. - Other Branch - Total No of Records # Welcome to Large Transaction Reporting - **Branch Update** - Pending for Updation - Pending for Review - Pending for Updation BackDate - Pending for Review BackDate - **REPORTS** - Updated Cases - NRO Credits Report - Transaction Details Report - Pending Cases - Pending Cases Branch - Pending Cases Assigned to RM - Pending Summary Report - RM Code Wise Report - NRE Accounts - SCS Tracking - Mobile App Update - IMP! Mobile App Update - **Large Transaction Reporting Home** - My Profile - User Name - Login ID - Branch Code - Branch Name - Role: - Today's (05 Mar 2020) upload of LTR CH106 files are available # Universal Alert System (UAS) - UAS is used to monitor transactions in the Customer Accounts which is part of KYC. - Any abnormal spurt in the accounts will be highlighted in this portal to the respective branches. - KYC/AML related and even more than 1 Crore Transactions are highlighted in this portal. - Maker & Checker concept is available based on roles. - Branches are expected to review this on regularly basis to meet the KYC norms. - UAS ID has to be created by the Employees once they join the Branches. # Audit Alerts - "UAS should not be used for any marketing/cross selling purpose" - Dashboard - Informative alerts - Search - Report - User Manual - Logout - Dashboard (Legacy) - System Type: - NON KYC - KYC - CAML - Pending / Closed Dashboard - Pending - Closed - Reopen - Pending Alerts Vintage in Days - Total - <=3 - 4~7 - 8~12 - 13~20 - 21~45 - >45 - **Export report in .csv** - **System Name**: NON KYC - ALERT TYPE - HIGH VALUE CHEQUE DEPOSIT - HIGH VALUE TXN IN NEW ACCOUNT - TOTAL - PBA - BOM - BM - CH - CRH - ZH - RH - Export report in .csv # Branch Actionable - Search alerts - Select Alert: - Same customer having multiple CASA - Search by: - Branch Code - LGCode - City - PinCode - Date Of Birth - PAN - Residence No - Mob No - CompanyCode - Ref ID - AssignTo Auditor - kyc_status - Search Value - Close # Status of Alerts - We have 9 types of KYC alerts being raised by Audit team in UAS portal, which needs to be Undiated / Closed within a TAT of 7 days. They are .. - **"Status" and its relevance** - BM - Pending with Branch, Needs to be updated by BM. - CH -- Pending with Branch, Needs to be updated by CH. - Submitted by CH - Pending with Audit, CH reviewed and updated the comments. - Interim Response - Pending with branch for response on additional query raised by Audit. - Alert Closed Actionable Pending -- Alert is temporary closed with future actionable. - (Branch to complete the actionable and confirm Auditor before committed deadlines) - **Note:** For any queries related to the alert branch may speak to the Assigned auditor whose Emp code is mentioned on the alert. # Universal Alert System (UAS) - FAQ - Question: 1. Who can update the transactions in High Value Transaction Portal? - Answer: PBA can update the transactions for non-portfolio customers and PB-RM / Business RM for their respective portfolio-customers. - Question: 2. Who is the reviewer of the Portal? - Answer: For Retail Branch banking, the Branch Manager (or designate with BM ID in UAS) has been given approval / reviewer rights. - Question 3. In case of staff on leave / left the organisation, can any other user update the transactions? - Answer: Yes. # Case Scenario 1 - Mr. Ram Singh is a salaried individual holding savings account with your branch. As per the profile updated in our records, his annual income is Rs 5 lakhs. - His salary gets credited in the HDFC Bank account every month. - Suddenly there is spurt of transactions and that too of high value. - You have received an alert for the Large Value Transactions in the account. - What is the branch actionable in this scenario? ## Branch Actionable 1. Check the profile of the customer 2. Enquire with the customer discreetly about the source and purpose of the large value transactions 3. If required, conduct CPV 4. If there is no justified reason found for the kind of transaction and it appears to be suspicious, then follow the process of STR 5. If during customer interaction, it is found that the customer’s annual income has increased, obtain a fresh profile updation form and send to CPU for updating in the records. # Case Scenario 2 - Mr. Shantanu is proprietor of Kshama Enterprises. He runs business of precious stones and gems. - He regularly receives high value transaction in the account from within and outside India. - Off late there have been transactions of more than 1 crore in the account and at frequent intervals. - How will the branch come to know of 1 crore and above transaction and what is the branch actionable in this case? ## Branch Actionable 1. Branch will be able to get the details of all such transactions in 1 crore section in Universal Alert System 2. Study the customer's profile for kind of transactions 3. Thoroughly check the account of the customer and update additional details 4. Ask the customer for his financials to ascertain that the transactions are in line with the customer's annual income/turnover 5. Branch must file the customer's profiler financial at its end for internal audit checks # Central Alerts Tracking System (CATS), - If an account is blocked with reason code restricted for removal by branches all such request gets rooted to CPU, a new workflow has been created in Central Alerts Tracking System (CATS). **Please Note:** All requests approved prior to 4pm in CATS Utility will be processed on the same day by CPU. Requests approved post 4pm will be processed on the next working day. ## For Branch checkpoints prior to updating case in CATS |Sl. No | Requirement | Accounts to be activated | Dr Freeze to be continued | EDD Negative, however debit freeze to be removed not applicable to 775 and 777 | |-----------|-----------|-----------|-----------|-----------| | 1 | Copy of Annexure 1 | Yes | Yes | Yes | | 2 | CPV Copy | Yes | Yes | Yes | | 3 | Income Documents / Proof | Yes | Yes | Yes | | 4 | Updation of revised profile in account | Yes | No | No | | 5| Review of transactions in account vis-à-vis AML updated in system | Yes | No | No | | 6 | Account Closure form | NA | NA | Yes | | 7 | Notice from competent authority for unfreezing the account | NA | NA | Yes | | 8 | Deatset certificate / Documents for settlement of death claim | NA | NA | Yes | | 9 | Customer Contactability | No | Yes | Yes | | 10 | Reporting to compliance team | Yes | Yes | Yes | ## How to Create User ID in CATS - Raise a request in ISAC: (https://isac.hbctxdom.com/Workflow/Create) > Central Alert Tracking System (CATS) ## Central Alert Tracking System - **Request Flow** - User Id Information - Type of Activity: Create - Application: Central Alert Tracking System (CATS) - (Type 3 characters of the Application) - Emp Code - Password - Login - Cancel ## How to raise Request - Branch View - Login in Centralised Alerts Tracking System (AD ID Login).. Option will be visible to PBA and BOM # Click on CPU Activities >> No Debit/Block Removal Request <b> Pending Cases</b> - **No Debit/ Block Removal Request** - Alert Type - Total - <=3 - 4~7 - 8~12 - 13~20 - 21~4 - **Export report in .csv** <b> Pending For Branch</b> - Alert Type - Total - <=3 - 4~7 - 8~12 - 13~20 - 21~4 - **Export report in .csv** <b> Reopened Cases</b> - Alert Type - Total - <=3 - 4~7 - 8~12 - 13~20 - 21~4 - **Export report in .csv** ** Pending For My Actionable** - Alert Type - Total - <=3 - 4~7 - 8~12 - 13~20 - 21~4 - **Export report in .csv** # Branch needs to enter details as below: - **Activity Name:** - **Customer ID:** - **Account Details** - Acc No - Acc Title - Account Status as per Flexcube - Reason Code and Descriptions - **Date of Receipt of Order:** - **Other Remark:** - **Regulatory Verification Letter:** - Brief Description: - Due Diligence Conducted: - Customer Sign Verification: - **File Upload:** - **Customer Sign In My Presence (CIMP):** - **Original Revocation Order:** - **View Uploaded File** - **Emp Code of BM:** - **Emp Code of CH:** - **Reject Reason:** - **Date of initiation of request:** - If the case is FTR, click on Approve, else Reject. Once the Branch Manager approves the case, the same moves to Cluster Head for approval. # Important Changes in CATS Application effective 24th July '24 - For unfreezing of accounts marked no debits with reason code 775,776,777,778 and 779 branches initiate request in CATS application for unfreezing the account post satisfactory EDD. - Branches post conducting EDD have to recommend one the following action to be taken on the account to the Cluster Head for approval - Account to be Activated - EDD Positive - Dr Freeze to be continued - EDD Negative, however debit freeze to be removed not applicable to 775 and 777 - For the third option branches were having difficulty in indication of unfreezing the accounts for the specific instances of settlement of death claim, account closure, intimation received from regulator for unfreezing the account. - Following changes have now been incorporated in CATS application for branch decision making and for Cluster Head approval. # COMPASS Portal - Let's understand the compass portal # Branch User - Logging In - Compass - Welcome to Compass - Your Anti Money Laundering System - Version: 5.73 - Username: - Password: - Login - Unauthorised use of the HDFC applications is prohibited. - **Branch staff has to raise ISAC request to avail Compass access. Per branch access to be restricted to 2 staff that is BSN and BOM.** - Use Chrome to log into Compass AML System, enter your username and password on the Compass Login Page and then click on the login button. # Dashboard - **Dash Board** - Dashboard - From Date: - To Date: - Search: - Total Cases - Pending Cases - Escalated Cases - **Date: Date range is to be selected by the user.** - **Total cases: Branch User can view the total number of cases assigned to the branch ** - **Pending cases: Branch user can view the total number of pending cases at the branch end.** - **Escalated cases: Branch user can view total number of cases that have been addressed (actioned) by the branch.** # AML Case Workflow - **Dash Board** - Dashboard - From Date: - To Date: - Search: - Pending Cases - Actioned Cases By Self - Raise Suspicion - **The AML Case Workflow allows users to view Pending Cases, Actioned Cases by Self and Raise Suspicious.** # Pending Cases - **Dash Board** - Pending Cases - Pending Cases Result - Show 10 Entries - TSV - CSV - Print - Excel - Search: - Escalate Case - View Comment - Attach Evidence - Reset Columns - Previous - Next - Sr. No - CASENO - Customerld - Customer Name - AccountNo - BranchName - Assigned Date - By clicking on Pending Cases module under the AML Case Workflow module in the main menu tray, the page displays the list of Pending Cases at the branch end. # 3.2 View Comment - **Dash Board** - Pending Cases - Pending Cases Result - Show 10 Entries - TSV - CSV - Print - Excel - Search: - Escalate Case - View Comment - Attach Evidence - Reset Columns - Previous - Next - Sr. No. - CASENO - Customerld - Customer Name - AccountNo - BranchName - Assigned Date - **By selecting a particular case and clicking on the View Comment button user can view comments / queries raised by the central AML function which are to be responded.** # AML User - **View Comment for Case No.** - COMMENTSLOG - Show 10 Entries - TSV - Print - Excel - Search: - View Evidence - Sequence Number - User ID - Case No: - User Role - Terminal - Case Action - SubAction - FIU Reference - **View Evidence** - View/Attach Case Evidences - Upload File - Allowed File Size: 3 MB - Allowed File Type: doc,xls,xlsx,pdf,txt,csv,zip, 7z,jpg,jpeg,png, - Maximum File Select Count: 3 - Upload Enable: No - Select Files - Drop Files - Selected Files - File Name - File Size - File Progress - Action/ Status - Drag & Drop Files Here - Upload - Download File - File Name: - File Size: - Download All - Download - Download Remove - **Comments Log** - By clicking on Comments Log, the branch user can view the trail of pervious conversation that is been done between AML Analyst and Branch as illustrated below. # 3.3 Branch Reverts - **View Comment For Case No-10960963** - COMMENTSLOG - Show 10 Entries - TSV - Print - Excel - Search: - View Evidence - Sequence Number - User ID - Case No: - User Role - Terminal - Case Action - SubAction - Action By - **To capture branch revert/ comments on a particular case, branch user must select a case then click on Escalate Case tab, a new tab will be opened as illustrated below.** # Objectives - Add Comment For Case Faculation" - AMLUSER BRANCHUSER COMMENTSLOG - Add Comments - Account Reviewed Date - Comments - Okay to Close - **User needs to type the comments and proceed further basis the below options:** - Sub- Action: In Sub- action box, by default the option says Okay to Close. - Attach evidence: In Attach Evidence, branch user can attach all the case related evidence/documents. - Comments: In Comment box, the branch user can respond to the query by filling up all the necessary details that has been raised by the AML Analyst. # COMPASS - **Dash Board** - Pending Cases - Pending Cases Result - Show 10 - TSV - CSV - Print - Excel - Search: - View Comment - Attach Evidence - Reset Columns - Previous - Next - Sr. No. - CASENO - Customerld - Customer Name - AccountNo - BranchName - Assigned Date - **Escalate Case** # Objectives - Add Comment For Case Escalation To Compliance Team - AMLUSER BRANCHUSER COMMENTSLOG - Add Comments - Account Reviewed Date - Comments - **Sub-Action** - Okay to Close - Post - Post and Close - Close Window # COMPASS - **Dash Board** - Report A Suspicion - Pending Cases - Raise Suspicion - **Subject Matter of Suspicion** - Reporting On - Name of Account/Person - Account No. - Branch Code - Customer Id - Please Enter AccountNo or Customerid - **Reason For Suspicion** - Alert Type - Alert Indicator - Alert Rating - **To raise suspicion to Centralized AML Function, user need to click on Raise Suspicious tab as illustrated below.** - Create Case - Attach/View - Clear - **Reporting On:** In Reporting On tab there are two options, Customer and Non- Customer. If a person/entity is a customer of bank then select the customer option and if not then select non-Customer option. - In case of bank customer: Branch user needs to add Account Number, rest all details will be auto-fetchen by the system. - **Alert type:** Basis the suspicion appropriate Alert Type has to be selected (Mandatory Field) - **Alert indicator:** In Alert Indicator tab, The *Grounds of Suspicion needs to be Captured. (Mandatory Field) # Grounds of Suspicion - While providing the "Grounds of Suspicion (GOS)" based on the EDD done, th information provided should include (Indicative): - Details of suspicion trigger. - A brief profile of the customer highlighting details of current occupation /business - Details of discreet inquiries carried out, if any - Details of review carried out for other linked accounts of the customer (linked with same customer ID UCIC/PAN/AUS / Mobile Number, e-mail etc.), if found suspicious. - Details of other product/services availed by customer such as Lockers/DEMAT/Credit Card/Prepaid Cards/Wallets etc. to be reviewed and mentioned as part of GoS if found suspicious. - Wherever applicable, copy of CPV to be attached while reporting the cases to FIU-Reporting Desk (Transaction/Pattern of transactions/Typology/ Behaviour etc. found to be suspicious needs to be highlighted. - Copy of necessary documents (like notice from any law enforcement agencies, customer complaint etc.) or any other document to support the suspicion or establish the EDD carried out should be attached along with the Grounds of suspicion being reported to the AML Unit. - Branches can raise a Case to the AML function by inputting the Cust ID wherein the branch id will get selected by default. The Account number and name fields are not a mandatory field while raising a case. By populating the Cust ID, they may choose to do so if available. # COMPASS - **Dash Board** - Pending Cases - Actioned Cases By Self - Report A Suspicion - **Subject Matter of Suspicion** - Reporting On: - Non-Customer - Name of Account/Person: - Address 1: - Address 2: - Branch Code: - CIN Value: - **Reason For Suspicion:** - Alert Type: - Alert Indicator: - Alert Rating: - **Reporting On** - Select Non-Customer, if person/entity is not a bank customer. (Mandatory Field) - **Branch code:** Branch Code will be selected by default. - **Name of the account/person:** Add the Name of the person/entity (Mandatory Field) - **Address:** Add the Address (Non-mandatory, if available then provide it) - **CIN value:** If it's an entity then Customer Identification Number has to be filled (Mandatory Field) - **Alert type:** Basis the suspicion appropriate Alert Type has to be selected (Mandatory Field) - **Alert indicator:** In Alert indicator tab, on the basis of Alert type and suspicion, the Branch user mention add all the necessary details (Mandatory Field) - **View/Attach Case Evidences** - Upload File - Allowed File Size: 3 MB - Allowed File Type: doc,xls,xlsx,pdf,txt,csv,zip, 7z,jpg,jpeg,png, - Maximum File Select Count: 3 - Upload Enable: Yes - Select Files - Drop Files - Selected Files - File Name - File Size - File Progress - Action/ Status - Drag & Drop Files Here - Upload - Download File - File Name: - File Size: - Download All - Download - Download Remove -**Attach evidence:** In Attach Evidence, branch user can attach all the case related evidences/documents. - **By clicking on Create Case button, User can create a new case which will be forwarded to central AML function.** # Actioned cases by self - **Dash Board** - Pending Cases - Actioned Cases By Self - From Date: - To Date: - Account No: - CaseNo - Case Action: - To Branch Name: - To Branch Id - To CaseNo - To Case Action: - To Case Sub-Action: - Show 10 entries - Search: - Clear - Reset Columns - **Actioned cases by self:** By clicking on Actioned Cases by Self, two new tabs will open- Actioned Cases by Self and List of Actioned Cases as illustrated above. - **In Actioned Cases by Self, branch user can search cases through selection of Date, Account number, Customer ID.** - Once a particular field is selected, it will reflect in List of Actioned Cases or by default it will show all the actioned cases. # List of actioned cases: - List of actioned cases: In List of Actioned Cases, branch user can view all the cases that are been actioned by self as illustrated below. - Select a particular case and then click on view comment a new tab will open as illustrated below # Branch User - **View Comment For Case No-10960963** - COMMENTSLOG - Show 10 Entries - TSV - Print - Excel - Search: - View Evidence - Sequence Number - User ID - Case No: - User Role - Terminal - Case Action - SubAction - Action By - Action Date - **By clicking on "Close Window", branch user can move back to Branch User tab, the same as in Figure 19.** - **Branch user: In Branch User tab, Branch user can view all the details submitted.** # Quiz - **Does income tax and GST notice fall under LEA notices for STR filing?** - **After sharing the notice through Compass, do branch need to share it through FIU mail id?** - **Compass application need to be browsed through Internet Explorer or Chrome?** - **Is it mandatory for branch users to attach evidence while reporting a case?** # Exisiting Question - **Q:- Transaction in line with declared profile/Transaction not in line with declared profile** - Option 1 Transaction in line with declared profile - Option 2 Transaction not in line with declared profile - **Q:- What is the Final recommendation on EDD performed** - Option 1 Account to be activated - EDD Positive - Option 2 Debit freeze to be continued - EDD Negative - Option 3 EDD Negative, however debit freeze to be removed (Not applicable to 775 and 777) - Applicable for 775 & 777) - Accounts unblocking for cases where EDD is negative needs to be allowed only in exceptional scenarios of account closures or regulatory orders - This option would not be available for accounts blocked with No debits code 775 and 777. # HDFC Bank - **See You Tomorrow!** # Branch Manager/Cluster Head can view the cases in "Pending For My Actionable" - **Click on Total No (highlighted in red)** - **Central Alert Tracking System (CATS)** - Dashboard - Reports - Search - Logout - **Pending Cases** - Alert Type - Total - <=3 - 4~7 - 8~12 - 13~20 - 21~45 - Export report in .csv - **Pending For Branch** - Alert Type - Total - <=3 - 4~7 - 8~12 - 13~20 - 21~45 - Export report in .csv - **Reopened Cases** - Alert Type - Total - <=3 - 4~7 - 8~12 - 13~20 - 21~45 - **Export report in .csv** - **Pending For My Actionable** - Alert Type - Total - <=3 - 4~7 - 8~12 - 13~20 - 21~45 - **Export report in .csv** # Click on ID number to open the case - **Central Alert Tracking System (CATS)** - Dashboard - Reports - Search - Logout - **Pending Cases** - Alert Type - Total - <=3 - 4~7 - 8~12 - 13~20 - 21~4 - **Export report in .csv** - Pending For Branch - Alert Type - Total - <=3 - 4~7 - 8~12 - 13~20 - 21~4

Use Quizgecko on...
Browser
Browser