Home

Mantas Interface User Manual

image

Contents

1. Lupioad You can specify the following details Received Date The system displays the global application date However you can modify it Click Upload button to upload the response of the risk details The response will be stored as two files customer and account o Note the following e The file names for upload should be as given below gt CustomerSupplementalAttribute txt gt AccountSupplementalAttribute txt The folder name should be the date for which the above files are uploaded If the file contains any invalid records then it will be moved to the error log table IFTB ERROR LOG and the valid records will be moved to the respective data stores maintained and this is applicable for both customer and account 3 3 ORACLE 3 1 5 Viewing the Risk Score The response from Mantas pertaining to the customer number and its related account can be viewed in the Risk Score screen You can invoke this screen by typing IFDMTSRD in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Risk Score Customer Details Customer No Customer Name Address Risk Score Account Risk Score 1061 L From Date To Date Click History of Customer button to view the risk history details of the customer and click History of Accounts button to view the risk history details of the accounts 3 4 ORACLE 4 Screen Glossary 4 1 Function ID List
2. Transaction Input screen 2 11 ORACLE 2 3 8 For more details refer to the section Capturing the details of payment collection transactions in the Payments and Collections User Manual Settlement Instructions You need to capture the country location of the following parties in the Settlement Instructions screen e Intermediary e Intermediary Reimbursement Institution e Receivers Correspondent e Account with Institution e Receiving Intermediary e Beneficiary Institution e Beneficiary Institution for Cover For more details refer to the section Capturing Settlement Preferences for a Customer in the Settlements User Manual 2 4 Performing the Data Hand Off 2 4 1 The extraction of the data at the various branches and the writing of the hand off file data are handled through batch processes The data files handed off to Mantas can be broadly classified as follows e Reference Data e Transaction Data e Change Log Reference Data Reference Data consists of the details related to the following entities e Account the details of all the accounts of type Nostro Savings Current and Deposits e AccountAddress the address details associated with an account e AccountToCorrespondent the details of all the accounts of type Nostro and Current related to banks only e AccountBalance the account number and the current available balance e AccountCustomerRole the different roles of a customer which ca
3. Details You need to capture the country location of the ultimate beneficiary in the Ultimate Beneficiaries screen For more details refer to the section Maintaining ultimate beneficiary details in the Settlements User Manual Instrument Transaction Details You need to capture the country location of the remitter in the Instrument Transaction Details screen For more details refer to the section Entering Instrument Transactions in the CASA User Manual Funds Transfer Transaction Details You need to capture the country location of the ordering customer the ultimate beneficiary and the account with institution in the Funds Transfer Contract Details screen For more details refer to the section Invoking the FT Contract Detailed Screen in the Funds Transfer User Manual Clearing Transaction Details You need to capture the country location of the remitter and the beneficiary in the Clearing Transaction Input screen For more details refer to the section Entering Clearing Transactions in the Clearing User Manual TD Redemption Renewal You need to capture the country location where a check is issued in the TD Redemption Renewal screen For more details refer to the section Maintaining details for redeeming term deposits in the Core Entities User Manual PC Transaction Input You need to capture the country location of the customer and the counterparty in the PC
4. The following table lists the function id and the function description of the screens covered as part of this User Manual Forener o rnesa 4 1 ORACLE ORACLE Mantas Interface April 2014 Version 11 3 83 02 0 Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon East Mumbai Maharashtra 400 063 India Worldwide Inquiries Phone 91 22 6718 3000 Fax 91 22 6718 3001 www oracle com financialservices Copyright 2005 2014 Oracle and or its affiliates All rights reserved Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government This software or hardware is developed for general use in a variety of information management applications It
5. is not developed or intended for use in any inherently dangerous applications including applications that may create a risk of personal injury If you use this software or hardware in dangerous applications then you shall be responsible to take all appropriate failsafe backup redundancy and other measures to ensure its safe use Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing This software or hardware and documentation may provide access to or information on content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party con
6. of the bank This happens during pre EOD where both reference and transaction data for the branch is extracted as per the Branch parameterization and the Frequency and hand off type parameterization The extracted data is written to a common data store For data extraction IFMNTSEX batch needs to be maintained at post EOFI level in the function id EIDMANPR The extraction should be maintained as a mandatory program as part of the branch s End of Cycle activity Writing the Batch Data The branch designated as the File Write branch for a particular Mantas code also will extract data for itself during pre EOD and then write the hand off file to the File Write destination specified in the Mantas Code maintenance The files would be picked up by Mantas from this location For file write IFMNTFWR batch needs to be maintained at post EOFI level in the function id EIDMANPR The File Write program should be maintained as a mandatory program as part of the file write branch s End of Cycle activity 2 5 File Naming Convention and File Formats The hand off file name will be generated as lt Datafile gt lt FileWriteDate YYYYMMDD gt lt BatchName gt lt n gt DAT n 1 e Datafile indicates the name of the data file for example Customer Account AccountBalance etc e FileWriteDate indicates the date on which the data was written to the hand off file The date is specified in the YYYYMMDD format e BatchName a predefi
7. 3 Mantas Response Maintenance Branch Code Read Destination Maker Date Time Checker Date Time Mod No Record Status Authorization Status You can specify the following details Branch Code Specify the branch code of the bank to read the Mantas response about the customer risk Read Destination Specify the location where the response file has to be placed Viewing the Summary Details of Mantas Response Maintenance You can view the summary details of the Mantas response maintenance in the Mantas Response Maintenance Summary screen To invoke this screen type IFSMTSRWM in the field at the top right corner of the Application tool bar and click the adjoining arrow button Authorization Status Record Status pranchcode i mm Authorization Status Record Status LBL FILERD DEST Maker Id Maker Date Stamp Checker Id Checker Date ta hl e In this screen you can query based on any combination of the following fields e Authorization Status 3 2 ORACLE e Record Status e Branch Code After specifying the parameters for the query click Search The system displays all the records matching the parameters specified Uploading Mantas Response Mantas response can be uploaded using the Mantas Response Upload screen You can invoke this screen by typing IFDMTSFU in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Received Date
8. Date Time Mod No Record Status Authorization Status You can specify the following details in this screen Branch Code The Branch Code will be defaulted from the logged in branch Description The description for the branch is also defaulted from the Branch maintenance File Write Role Check this option to specify that file write role should be designated to write the extracted data on behalf of all the other branches and itself Mantas Code Select the Mantas Code corresponding to the branch from the option list provided 2 2 6 Specifying the Data Extraction Details In the Data Extraction Monitor screen you can specify details pertaining to data extraction To invoke this screen type IFDMTSEM in the field at the top right corner of the Application tool bar and click the adjoining arrow button 2 9 ORACLE 2 2 1 Data Extraction Monitor Branch Code Refresh Extraction Branch Code 10f1 B eraren O sets d You can specify the following details Branch Code Select the branch code which has got the file write role from the list of options Click Refresh button to view the extraction status pertaining to the branch The status will be C or N which indicates the completed and not completed status of data extraction Note the following e The Data Extraction Monitor screen is accessible only to the branch which has file write role and an error message is displ
9. Mantas Interface Oracle FLEXCUBE Universal Banking Release 11 3 83 02 0 April 2014 Oracle Part Number E53607 01 ORACLE FINANCIAL SERVICES Mantas Interface 1 Table of Contents POO UT ATS NNN 1 2 1 1 NR PIN 1 2 1 1 1 Audience a eee 1 2 1 1 2 Acronyms and Abbreviations orrrrrvrnnnnnrrorrrrrnnnnnnrrrrrnnrnnnnnnrrrrrrnnnnnnnerrnnnnnnnnneeennennnnnnnseennnnnnnnnnneesnsen 1 2 1 1 3 VENN 1 2 1 1 4 RD 1 3 ORACLE FLEXCUBE MANTAS INTEGRATION sessessssssssssssvsssssvsvsvsnessnsnnsnsesesessnnsnsnnnsnnnsnnnnsnsnensnsseneee 2 1 2 1 TINE ODUCT vvs 2 1 2 2 MAINTAINING DETAILS FOR DATA HAND OFF TO MANTASG ccccceccececeececececccecececcecececcceeeeeeeeeeeeeeeeeess 2 1 221 Maintaining Mantas Installation Parameters eernnrnnnnnnnnnnnnnnnnnnrrnnrnnnnnnnnnrrnnnnnnnnnnnrrnnnnnnnnnnnnnersensnnnn 2 1 222 Viewing the Mantas Code Parameter Details rrrnnnnrnrrnnnnnnnnnnnnrrrnrrnnnnnnnnrrnnrnnnnnnnnrrrnnvnrnnnnnennnrnnnnnnnn 2 3 223 Maintaining Data File Parameters rrrnnnnnnnrnnnnnnnnnnnnrrrnnnnrnnnnnnnnrrrnnrnnnnnnnnrsnnnrnnnnnnessrnnnrnnnnnsessrnnnnnnnnn 2 3 2 2 4 Maintaining Frequency and Hand Off Type Parameters rrrrrrvrnnnnnnnnnnnnnnnnnnnnnnnvnnvnnnvvnnnnnnnnnnnnnnnnnnnre 2 7 2235 Maintaining Branch Parameters v sesisagasmsnienersrmiessjessieanrsarievvjsvitsmimepiinae e 2 8 2 2 6 Specifying the Data Extraction Details rrrrrnnnnrnnrrrnrrnnnnnnrnrrnnrrnnnnnrnrrrnnrnnnnnnnnnnrrrnnrnnnnnen
10. a Transaction Data Change Log Change Log 1Of1 mei Donon Maker Date Time Checker Date Time Mod Na Record Status Authorization status You can specify the following details here Entity The list of the entities which qualify for hand off are displayed Option You can specify whether you want to include or exclude a particular entity for the hand off Maintaining Frequency and Hand Off Type Parameters Frequency and hand off type parameterization provides the bank the option to choose the frequency and the type of hand off This option is available only for the hand off files related to Reference Data Frequency and or hand off type parameterization will not be available for Change Log and Transaction hand off files You can specify these details in the Mantas Handoff Parameters screen You can invoke the Mantas Handoff Parameters screen by typing IFDMTSFH in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 2 7 ORACLE Mantas Handoff Parameters Bank Code Description Mantas Handoff parameters 10f1 E Maker Date Time Checker Date Time Mod No Record Status Authorization Status You can capture the following details in this screen Bank Code The Bank Code is defaulted from the Bank maintenance File Name This is the name of the hand off data file All the hand off files related to Reference data type are displayed Fr
11. ayed if it is accessed from other branches o By default all the branches will have extraction role once the branch is saved using the branch parameter screen Further one of the branches will be given the file write role Maintaining UDF s Specific attributes related to a Customer Account and Oracle FLEXCUBE User need to be provided to Mantas in the corresponding files The following User defined fields will be maintained for Account Customer and Oracle FLEXCUBE user e MNIS BUS DOMAIN which indicates the Mantas business domain e MNTS_ JURISDICTION which indicates the Mantas jurisdiction The extraction will pick up these values from the Customer Account and User maintenances and provide the same in the corresponding field for the relevant file 2 3 Capturing Country Information The country location involved in a transaction is crucial for Mantas to analyze the transactions The following input screens in Oracle FLEXCUBE have been modified to capture the country information This information capture is only for Mantas handoffs and will not have any other impact 2 10 ORACLE 2 3 1 2 3 2 2 3 3 2 3 4 2 3 5 2 3 6 2 3 7 Maintaining Customer Account You need to capture the country information of the customer account in the Customer Accounts Maintenance screen For more details refer to the section Maintaining Customer Accounts in the Core Entities User Manual Maintaining Ultimate Beneficiary
12. e 2 12 2 4 1 MND 2 12 2 4 2 VNR 2 13 2 4 3 NNN 2 13 2 4 4 Face the Barch D uavssasamassdses ed eGe Gad 2 13 2 4 5 VNR 2 13 2 5 FILE NAMING CONVENTION AND FILE FORMATS esnnnnnnnnnvnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnne 2 13 20 DATA SEE RE A E EE eee EE E 2 14 KYC KNOW YOUR CUSTOMERS 3 1 3 1 ANDE CTO EEE E E A E E E E TE E E E T 3 1 3 1 1 LO a E EAEE A TEE E 3 1 3 1 2 Maintaining Mantas Response rrrvrrnnrnrrnrnnnnrnrrnvrnnnnrrrnrnnnenrnnnnnnensnnnnnnensnnrnnnsesnnnnnnessenrnnnnsesensnnnnessennn 3 3 1 3 Viewing the Summary Details of Mantas Response Maintenance annnnnnnrnnnnnnnnnnnnnnnnnnnnnnnnnnnnrrnnnnnnnn 3 2 3 1 4 Uploading Mantas Response rrrnnrrnnnnnnnnnnnnrrnnvnnnnnnnnrrrnnrnnnnnnnnnrrnnnnnnnenensrnnnnnnnnnnessssennnnnnnneesnsnnnnnnnnesnnene 3 3 3 1 5 Viewing the RISK SO Bees Rii 3 4 SCREEN GLOSSARY c e e AR arn oreE ne er eee 4 1 4 1 DP a E E EEE E E er nt rte ere cr er re 4 1 1 1 ORACLE 1 About this Manual 1 1 Introduction This document is designed to help you acquaint with the enhancements and changes provided in Oracle FLEXCUBE to interact with Mantas an AML application This manual explains the various maintenances required for the exchange of data between Oracle FLEXCUBE and Mantas to track money laundering activities It also gives you an insight into the type of data to be transferred to Mantas to perform AML activities Besides this User Manual while maintaini
13. equency This is the handoff frequency type The frequency value will be displayed as As Needed for the Country and AccountCustomerRole files All the other files will have the frequency set as Daily Extract Type Specify the type of extract for the handoff indicating whether a file is to be sent as Full or Incremental For files with frequency specified as As needed the extraction type will always be Full A Full extraction takes place only if any modification happens to the data If there are no modifications for a day no file will be handed off for that day For all other frequencies an empty file would be handed off for the day if there is no data for hand off 2 2 5 Maintaining Branch Parameters Every branch of a bank extracts the reference and the transaction data for itself and writes the data into a data store as one of its mandatory pre EOD programs Only one branch will be designated to write the hand off file on behalf of all the other branches and itself for a particular Mantas code The Extraction and the File Write roles can be assigned to the branches using the Mantas Branch Parameters screen 2 8 ORACLE You can invoke the Mantas Branch Parameters screen by typing IFDMTSBR in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Branch Parameters Maintenance Branch Code Mantas Code Description File Write Role Maker Date Time Checker
14. he system displays all the records matching the parameters specified Maintaining Data File Parameters You can maintain the file parameters for the following types of data e Reference Data file parameters e Transaction Data file parameters e Change Log file parameters 2 3 ORACLE These parameters can be captured using the Mantas File Parameters screen You can invoke the Mantas File Parameters screen by typing IFDMTSFFP in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button gt Mantas File Parameters Bank Code Source ID Reference Data Transaction Data ChangeLog Transaction Data 10f1 L Maker Date Time Checker Date Time Mod No Record Status Authorization Status You can capture the following details here Bank Code The Bank Code will be defaulted from the Bank maintenance Source ID Specify the Source ID which is a unique identifier representing the Oracle FLEXCUBE instance which hands off data to Mantas The Source ID can be only three characters long 2 2 3 1 Specifying Reference Data file Parameters Reference data file parameterization provides the bank an option to include or exclude a particular data file in the data hand off 2 4 ORACLE Mantas File Parameters Bank Code Source ID Reference Data Transaction Data ChangeLog Reference Data 1071 BJ Fie name option O LI Maker Da
15. ill be a part of the hand off file name This pre defined string should be unique across all Mantas codes to which the bank is handing off files Base Currency Select the base currency into which the amount involved in a transaction has to be converted to be sent to the hand off files Sron There can be only one base currency associated with a Mantas Code 2 2 ORACLE 2 2 2 2 2 3 Rate Code The rate codes are maintained by Oracle FLEXCUBE for a base and reporting currency pair Select the Rate Code to be used for the base and reporting currency conversions Rate Code Type Select the Rate Code Type that specifies if it is a Buy rate Sell rate or Mid rate This will also be used in the base and reporting currency conversions Viewing the Mantas Code Parameter Details You can view the Mantas code parameter details in Mantas Code Parameters Summary screen To invoke this screen type IFSMTSCD in the field at the top right corner of the Application tool bar and click the adjoining arrow button Authorization Status Record Status Mantas Code File Write Batch Name f Toril Authorization Status Record Status File Write Batch Name File Write Destination E hi gt In this screen you can query based on any combination of the following fields e Authorization Status e Record Status e Mantas Code e File Write Batch Name After specifying the parameters for the query click Search T
16. n be primary secondary partner etc associated with an account e AccountToCustomer the specific role a customer plays in an account This will be picked up from linked entities captured at account level e Country the country code and its description as maintained in Oracle FLEXCUBE e Customer the details related to the customer e MatchedEntity outcome of an SDN match e WatchList single record file which maps to Oracle FLEXCUBE s watchlist e WatchListEntry list of the Specially Designated Nationals which will be picked up from SDN maintenance e Employee the details related to the Oracle FLEXCUBE user 2 12 ORACLE 2 4 2 2 4 3 2 4 4 2 4 5 Transaction data Transaction data consists of details related to the following e Front office transactions which involve any movement of funds into or out of the financial institution and the reversed front office transactions e Front office transaction parties e Back office transactions which involve any internal movement of funds within the financial institution and reversed back office transactions Change Log Change log consists of the details of the changes in specific fields related to Account Account Address Customer and Account to Customer entities Any modification happening to these fields needs to be sent as a part of the change log file Extracting the Batch Data The data extraction routines will run on the Oracle FLEXCUBE database for each branch
17. ned Mantas value which will be picked from the Mantas Code maintenance and used for naming all the files generated for that Mantas Code e n indicates the sequence number of the data file When there are multiple instances created for a data file the sequence number would indicate the number of the data file Example The files generated on 30 March 2007 will be named as follows e AccountBalance 20070330 lt BatchName gt 1 DAT e AccountCustomerRole 20070330 lt BatchName gt 1 DAT e Account 20070330 lt BatchName gt 1 DAT Data Types Table given below explains the various data types in the data hand off Text These fields would be as per the length specified for the field Numeric Amounts These fields will contain digits 0 9 and a decimal separator The number of digits following the decimal separator would be driven by the currency maintenance of Oracle FLEXCUBE Numbers without decimals These fields will contain only digits 0 9 Numbers with decimals These are number fields which are not amounts e g ea rates These fields will contain only digits 0 9 and a decimal separator Date Date fields will be represented in the format YYYYMMDD For instance 30 March 2007 would be represented as 20070330 2 14 ORACLE 3 KYC Know Your Customer 3 1 Introduction Oracle Mantas KYC solution helps you to identify customer risk in all lifecycle stages of the customer Oracle FLEXCUBE hands off data
18. ng the interface related details you can invoke the context sensitive help available for each field This help encapsulates the purpose of each field within a screen Placing the cursor on the relevant field and striking the lt F1 gt key on the keyboard can obtain information specific to a particular field Audience This manual is intended for the following User User Roles Back office data entry Clerks Input functions for maintenance related to the interface Back office Managers Officers Authorization functions Acronyms and Abbreviations System Unless and otherwise specified it shall always refer to Oracle FLEXCUBE Corporate FCC system AML Anti Money Laundering UDF User Defined Field Bank Identification Code Organization This manual is organized into the following chapters Chapter 1 Oracle FLEXCUBE Mantas Integration talks about the maintenances required for exchanging data to Mantas the hand off files and batch process for extracting and writing the hand off data Chapter 2 Annexure explains the file formats and the data types used in the data hand off 1 2 ORACLE 1 1 3 1 Conventions Used in this Manual Important information is preceded with the ror symbol 1 1 4 Related Documents You may need to refer to any or all of the User Manuals while working on the Mantas Integration interface module e CASA e Core Entities e Clearing e Funds Transfer e Settlements e Payments and Collecti
19. nrrnnnnnnnnnenssee 2 9 227 VINN 2 10 2 3 CAPTURING COUNTRY INFORMATION scvsssseosnesaoagssnasnanstenasasstnansnacuecaonasd nas snastedacasetnan Maacwenacneatasneanteaabaeetnas 2 10 2 3 1 Maintaining Customer ACCOUNMt oeeesssssseeeesssssseeeesessssssseeresssssseerrssssssserressssseteesesssseeereessssseereeess 2 11 202 Maintaining Ultimate Beneficiary Details rrrrrrnnnnnnnnnnnnnnnvnvnvnvnvvvnnnnnnnnnnnnnnnrerrnrrrrrnnnrrrnrnnnnnnnnnsree 2 11 2 3 3 Instrument Transaction Details srrrrrrrnrrnnnnnnnnrrnnrrnnnnnnnrrrnnvrnnnnnnnrrnnnnnnnnnnnnrrnnnnnnnnenesernnnnnnnnssssesennnnn 2 11 2 3 4 Funds Transfer Transaction Details rrrrrrnnnrrrrrrnrrnnnnnnnnnrrvrnrnnnnnnnrrrvnrrnnnnnnnrrrnnnnnnnnennrrnnnvnnnnnesnsnnnene 2 11 23 3 Clearing Transaction Details rrrrrrrrnnrnnnnnnrnrrnnnrnnnnnnnrrvrnrnnnnnnnnrrrnnnnnnnnennrrnnrnnnnnnsenernrnnvnnnnnesssernnsnnnn 2 11 2 3 6 TD Redemption Renewal rrrrrnnnnnnnnrnnnrnnnnnnnnrrvnnnnnnnnnnnrvnnrnnnnnnnnrnnnrnnnnnnnnenssennnnnnnnneesennnnnnnnnsessennnnsnnen 2 11 LAS YA PC Transaction Input rrrrrnnnnrrnnnnnnnrrnvnnnnnrvvvnnnnnnrnvnnnnnrrnnnnnenrrnnnnnnesennnnnensnnnnnnnssennnnnnesennnnnessennnnnennsne 2 11 2 3 8 Settlement Instructions rrnnnnnnnrrnnrrnnnnnnnrrvnnrrnnnnnnnrrrnnrnnnnnennnnerrnnrnnnnneessennrnnnnneeessennnnnnnnessssenennnnnnnnseee 2 12 2 4 PERFORMING THE DATA HAND OFF oooorovevvesrsrsssnnnnnnnnnnnnnennvsnevsnssnnnnnnnnnnnnnnensnnvsvensssnnnnnnnnnnnnnenssensvsesssssnne
20. ons e Standing Instructions e Term Deposits e Utility Payment e Salary Processing e ATM POS Transactions e Liquidity Management 1 3 ORACLE 2 Oracle FLEXCUBE Mantas Integration 2 1 Introduction Money Laundering is the process of moving illicit funds through the banking system so as to disguise the origin of the funds Anti money laundering applications based on the data from the banking system tracks and identifies patterns in the banking transactions to trace any possible fraud or money laundering involved AML systems also attempt to detect money laundering activities by analyzing the changes in specific customer account information and the transactions performed on an account Mantas is an AML system which monitors the money flowing into and out of the banking system to detect possible money laundering An interface between Oracle FLEXCUBE and Mantas enables data hand off from Oracle FLEXCUBE to Mantas To perform AML monitoring Mantas requires reference data relating to the customer accounts etc as well as transaction details related to customer accounts 2 2 Maintaining Details for Data Hand Off to Mantas You need to maintain the following details to enable the data hand off to Mantas e Mantas Installation parameters e Mantas Data file parameters e Frequency and Hand off type parameters e Branch parameters e UDF s related to customer account and user In addition to the above maintenances you need to captu
21. pertaining to the customer and its accounts to Oracle Mantas The customer risks indentified can be integrated with third party source systems like Watch Lists Negative News Providers and Identity Verification Vendors The Oracle Mantas KYC solution comprehends the risk of the customer at the following stages of the lifecycle e Real time account on boarding risk assessing the customer risk at the time of account opening e Default Account review assessing the risk of new customers e Periodic review reviewing the risk of the customer at regular intervals e Accelerated review assessing the risk based on i alerts received from AML ii the change in controlling role in accounts File Formats The following conventions are used while generating the data files e ach file will be a text file with each field delimited by e Fields with blank values will be recognized by successive delimiters e There will be a delimiter at the end of a record e Each record will be on a new line Refer Savings Account Creation and Current Account Creation Process Document User Manuals for more information on KYC process flow Maintaining Mantas Response You can read the response of the customer risk from Mantas in the Mantas Response Maintenance screen You can invoke this screen by typing IFDMTSRWM in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button ex ORACLE 3 1
22. re the country information in the following screens e Customer Account Maintenance e Ultimate Beneficiaries e Instrument Transaction Details e Funds Transfer Contract Details e Clearing Transaction Input e TD Redemption Renewal e PC Transaction Input e Settlement Instructions Each of these maintenances is discussed in detail in the following sections of this Manual 2 2 1 Maintaining Mantas Installation Parameters You can capture the details specific to the Mantas installation in the Mantas Code Parameters screen 2 1 ORACLE To invoke the installation parameters screen from the Application Browser select Install Parameters under Mantas in the Interface module Mantas Code Parameters Mantas Code Description Base Currency File Write Batch Name File Write Destination Rate Code Rate Code Type Maker Date Time Checker Date Time Mod No Record Status Authorization Status You can capture the following details in this screen Mantas Code Specify the Mantas Code which identifies the Mantas instance to which the Oracle FLEXCUBE physical instance is mapped Description Specify the description for the Mantas installation File Write Destination Specify the pre defined destination where Oracle FLEXCUBE will place the hand off file Mantas will pick up the hand off file from this destination File Write Batch Name Specify a pre defined name for the file batch which w
23. te Time Checker Date Time Mod No Record Status Authorization Status You can capture the following details here File Name This provides a list of all the reference data files Option You can specify whether you want to include or exclude a particular data file for the data hand off 2 5 ORACLE 2 2 3 2 specifying Transaction data file parameters Transaction data file parameterization provides the bank an option to choose the type of transactions to be included in the transaction hand off files Mantas File Parameters Bank Code Source ID Reference Data Transaction Data Change Log Transaction Data 1071 m transaction Type Opto C Maker Date Time Checker Date Time Mod No Record Status Authorization Status You can specify the following details here Transaction Type The different transaction types with the corresponding modules which qualify for hand off are listed out Option You can specify whether you want to include or exclude a particular transaction type for the hand off 2 6 ORACLE 2 2 3 3 Specifying Change Log File Parameters 2 2 4 Change Log file consists of modified data of specific fields relating only to Account Account Address Customer and Account to Customer entities Change Log parameterization provides the bank an option to include or exclude an entity in the Change Log hand off file Mantas File Parameters Bank Code Source ID Reference Dat
24. tent products and services Oracle Corporation and its affiliates will not be responsible for any loss costs or damages incurred due to your access to or use of third party content products or services

Download Pdf Manuals

image

Related Search

Related Contents

【取扱説明書 正誤表】 - 産業用鉛蓄電池|株式会社 GSユアサ  User Manual ExoQuick  ficha técnica carpaccio de pulpo especificaciones del producto  取扱説明書デザインにおける HCD プロセスの適用  los proyectos hacen los objetos eternos, las modas los  SERI ES    Control system for communication apparatus  Cnet CBH-m21  Home Decorators Collection 26660 FAQ  

Copyright © All rights reserved.
Failed to retrieve file