Home

[January] [2010] Oracle Part Number E51573-01

1. 4 Annexure A File Formats 4 1 Introduction This section lists out the upload file formats 4 2 BIC record upload As mentioned earlier Oracle FLEXCUBE allows you to upload the entire BIC directory or individual records like Fl and AM The record Financial Instructions Fl includes the modified data of all the fields in the BIC directory except the BIC The Amendments AM record contains the modified BIC details 4 3 Record file formats The file formats for the Fl and AM records is as under Fl record V VARCHAR2 Y A addition M modification D deletion U unchanged VARCHAR2 Y Bank code 4 char Country code 2 char Location code 2 char ARCHAR2 Y Branch code with XXX if no branch code exists VARCHAR2 Y Name first part VARCHAR2 N Name second part Institution Name 3 VARCHAR2 N Name third part Branch 3 VARCHAR2 N Branch specification first Information part 155 Branch 35 VARCHAR2 N Branch specification Information second part 4 4 ORACLE code Institution Name Institution Name L 2 1 BIC Branch 3 3 3 Modification Flag 4 5 8 3 120 5 BIC Bank Country amp Location Code 190 City Heading 35 225 229 289 324 359 394 429 464 199 534 569 604 639 674 709 144 779 814 Subtype indication Value Added Services Extra Information Physical addres
2. eon i ee oaeen fee recast 50 Ordering The information captured in the Ordering Customer details field Customer will be defaulted here only if the details are different from the Ordering Institution For outgoing MT210 the first line should have number 1 present in option F 52a Ordering This is the BIC of the Sending Bank The information maintained Institution in the Ordering Institution field of the Settlement Message Details screen is defaulted here If the BIC of the ordering institution and sending bank are the same this field generation in the message is mandatory 56a The information captured in the Intermediary field of the Intermediary Settlement Message details screen is defaulted to this field You have the option of deleting the information captured in this field 2 7 9 MT 320 Fixed Deposit Confirmation Message Field Tag Description Type MT 320 Transaction reference Number If the SWIFT SILVER parameter has been set to YES for your bank a unique reference number will be generated instead of the transaction reference number Se emee es e pemean O e eww E a Value Date of Deposit Currency Value Date of Deposit Currency Code Contract Amount Contract Amount Value Date for Change Currency Code Principal Amount to be Transferred 5 ORACLE Message Field Tag Description Type e en es oaar conta Next interest Due Date Currency Code interest Amount 37a Interest Fie
3. Location Chips ID Country Name Branch Qualifier Special Code BAN Courtry Code Other National D1 IBAN National ID Other National D2 Unique IBAN National ID ZIP Code Subtype indicator Pob Number Service Codes POS ZIP Code National ID Expiry Date POS Location Pob Country Name Address Physical Address1 Physical Address Physical Address3 Unique Key for Record Specify the unique key of the record in the file This consists of ISO country code and sequential number of six digits Invoke the Iban Information Summary screen by typing ISSISBAN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 2 6 ORACLE T iban information sumiar y es Web Fare Make Biha Sas DAN Country Dra AR E jy P Records per Ma FA l RISSPLREB i i i i i i m COSSSCOOSGOOD GOS SSR Oo Fy Pa m a n n n e e A D a E E EE A M ih bh kh Gh Rh pi ga gi a di di ki ee i BF FEF BS FF FF Fo FI RI RI MI bt bF kF RF EF A A E E 4 4 4 a m fi fi a a A A aj Aug Pen iran Sade Bo bre U Unwired Invoke the Iban Information Maintenance screen by typing ISDISBAN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button F Iban information maintenance Web Page Dialog Iban Details Other Details BAN Couniry Cone DH Bank identifier Position BAH Country Posit
4. Receiver Intermediary This field corresponds to field 56a of S W I F T Specify details of the financial institution between the Receiver and the Account With Institution through which the amount must pass The Intermediary may be a branch or affiliate of the Receiver or of the Account With Institution or an entirely different financial institution In this field you can choose to enter the e ISO Bank Identifier Code of the bank e Name and address of the Bank Country Specify the country of the receiver s intermediary This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Beneficiary Institution This field corresponds to field 58a of S W I F T Enter details of the institution in favor of which the payment is made It is in reality the bank which services the account of the ultimate beneficiary You will be allowed to make entries into this field only for Bank transfers MT 200 or MT 202 In this field you can enter either the The ISO Bank Identifier Code of the Beneficiary Institution The Name and Address of the Beneficiary Institution Country Specify the country of the beneficiary institution This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Note the following If you have already maintained this information in the Settlement Instructions Maintenance screen then it will
5. This message type is sent by or on behalf of the financial institution of the ordering customer directly or through a correspondent s to the financial institution of the beneficiary customer Given below is a list of fields present in an MT 103 message type Message Field Tag Description Type MT103 20 Transaction Reference Number If the SWIFT SILVER parameter has been set to YES for your bank a unique reference number will be generated instead of the transaction reference number pf 82R Value Date Currency Code and Amount 50 Ordering This information you have maintained for the Ordering Customer Customer field in the Other Messages tab of the Settlements screen is defaulted here For outgoing M1108 the first line should have number 1 present in option F If the ordering customer specified is a valid BIC then the system will update field 50a with this BIC If the BIC is nota valid code the system will display the name and address of the customer instead as per option K different bank this field should contain the name of the Originating Bank If you do not need this field clear the data from this field 53a Sender s The information that is captured for the Receiver of Cover Correspondent field in the Settlement Instructions screen is defaulted if a cover is sent Else the BIC of the Nostro account is defaulted This field gets populated only if there are multiple account relationships between the sender
6. chain to the Beneficiary This field corresponds to field 70 of S W I F T Refer to the S W I F T manual for details on the code words and the format of the message you can input Transfer Type You can specify whether the Transfer Type should be e Bank Transfer e Customer Transfer e Bank Transfer for own A c 2 33 ORACLE e Direct Debit Advice e MCK e Customer Transfer with Cover e None Banking Priority Select the priority of the payment messages from the drop down list The options available are e Highly Urgent e Urgent e Normal The default value is Normal RTGS Payments If the settlement chosen is one of the RTGS Nostro that is RTGS outgoing Nostro account in case of Outgoing customer and Bank transfer and RTGS incoming Nostro in case of outgoing Direct Debit transfer then the system will check this check box as per the validations done in RTGS Network The user cannot change this value RTGS Network If in a RTGS Network the accounts are maintained as Pay account or Receiver Account during the save of settlement instruction then a set of validations will be performed as mentioned below For Pay message it will validate the intermediary if intermediary is not present the Account with Institution AWI will be validated and if the AWI is also not present then receiver will be validated is a RTGS participant For Pay Cover message it will validate that a receiver correspondent is a RTGS networ
7. B or C 26T Transaction This field would be filled up only if the Transaction Type codes for all the Type Code underlying FT Contracts are the same 77B Regulatory This field would be filled up only if the Regulatory Reporting for all the Reporting underlying FT Contracts are the same 71A Details of This field would be based on Charge Whom and will be filled up only if Charges Charge Whom is same for all the underlying FT Contracts 36 Exchange Rate This field would be filled up only if the Cr Currency Settlement Currency and Exchange Rate for all the underlying FT Contracts are the same and Cr Currency lt gt Settlement Currency Mandatory Repetitive Sequence B Transaction Details Transaction FT Contract Ref No Reference Transaction OUR or SHA Credit Currency and Credit Amount BEN Credit Currency and Credit Amount Sender s Charges 21 32B 0 Ordering This field would be filled up only if the Ordering Customer for the Customer A or underlying FT Contracts differs K Ol NO Q Ordering This field would be filled up only if the Ordering Institution for the Institution A or underlying FT Contracts differs 7 Acct With Account With Institution details of FT Contract Ol N pe O1 sab Institution A or C O1 O Q Beneficiary Beneficiary Customer details of FT Contract Customer A or No letter Remittance Payment Details of FT Contract Information Transaction This fiel
8. Code 6 Description Envelope Contents Envelope Contents 1 Envelope Contents 2 Envelope Contents 3 Envelope Contents 4 Envelope Contents 5 2 6 4 1 Clearing Details You have the option of changing any or all of the default values for fields in MT 103 messages while processing a contract Bank Operation Code You can indicate the bank operation code that will be inserted in Field 23B of the MT 103 message The options available are SPRI SSTD SPAY and CRED Transaction Code This is the code for the transaction type This field corresponds to field 26T of the MT103 message Instruction Code You can indicate the Instruction code that will be inserted in Field 23E of the MT103 message You can specify a maximum of six instructions codes here However you cannot repeat any code that has already been specified The options available are 2 41 ORACLE e CHBQ e TELE e PHON e PHO e REPA e INTC e TELI e SDVA e PHOB e TELB e HOLD e CORT Instruction Code Description You can specify the additional information if any which would be inserted to qualify multiple Instruction Codes in Field 23E of the MT103 message The instruction code description can only be maintained for the following instruction codes e PHON e PHOB e PHO e TELE e TELB e TELI e HOLD e REPA For instance if the Instruction Code is REPA and the description is Repayment then the text REPA Repayment is inserted in Field 23E Regu
9. FLEXCUBE BIC directory an error will be logged and the upload will continue If there is any record existing then it will be marked as CLOSED 2 10 ORACLE e AM For an existing record in the BIC file or AM file BIC code would be renamed in the upload file BIC addresses that have changed will be appropriately updated Addresses bearing the tag D will be automatically deleted New BIC records will be created for records that bear the tag N The network codes that are marked for exclusion in the BIC Upload Maintenance screen will not be uploaded The upload sequence is based on the modification tags in the BIC records The sequence will occur in the following order e Deletion e Modification e Addition e Unchanged The file upload is processed in an asynchornous manner The system prompts the user to check the logs Note The logs can be viewed by visiting Batch Operations gt Intra Day Batch gt Monitor Fast Path BASIDMTR The function field can be given as ISDBICPU for searching the upload logs Click Exit or Cancel button to exit the screen without initiating the upload process 2 3 Maintaining multi mode settlement details Multimode settlement is applicable only for Consumer lending module of Oracle FLEXCUBE All settlements are typically made using accounts However in Oracle FLEXCUBE settlements can be done through different modes in addition to the account level settlement The differen
10. Net Amount s Payable by Party A Field Tag Field Name Format Mandatory Optional 15E 18A Number of Repetitions 32M 53a C a C AWD fo 2 16 1 Processing Incoming MT362 During STP the system picks up an incoming MT362 message and extracts the following details from Sequence D for auto confirmation e The currency and interest amount to be paid Field 32H e The currency and principal to be exchanged Field 33E e The payment due date Field 30F After the above details are extracted the corresponding interest and principal schedule on that date is compared with the details extracted as mentioned above The following details are considered for matching e The schedule due date e The amount of the schedule e The currency of the schedule e The pay and receive flag of the schedule If the details match the schedule will be marked as Confirmed The same approach is followed for party B whose details are extracted from sequence B of the message After the message is processed the message is marked as Processed You can view the message status in the incoming browser After the corresponding schedules are marked as confirmed they can be viewed in the contract confirmation screen After confirmation Media will be updated as SWIFT and Authorization Status as Auto in this screen RCON is triggered post confirmation and can be viewed under Contract Online screen 2 67 ORACLE 2 8 G
11. Settlements Message Details screen In the Message Details tab you can indicate the payment mode and the cover details If you indicate payment through the local clearing network or cover through the local clearing network you must indicate the external counterparty details in the Local Clearing tab in the Settlement Message Details screen ze Settlement Details Web Page Dialog Reference Number Component Account Details Message Details Parties Parties Cover Parties Other Details Clearing Details Local Clearing External Counterparty Details Counterparty Bank Description Counterparty Account Counterparty Name Agreement Identification Clearing Network I Post Accounting 2 6 3 4 Other Details Select the Counterparty Bank from the option list provided All the Counterparty Accounts pertaining to this Bank will appear for selection On selecting the Counterparty Account the system will default the Counterparty Name as maintained for that account If at the time of selecting Counterparty Account Counterparty Bank is Null then the Counterparty Bank will also appear by default For processing direct debits you will also need to capture the Agreement ID of the counterparty in order to facilitate a cross referencing between the Payment and the Direct Debit instruction when a reversal of payment is carried out due to rejection of the outbound DD The Post Accounting option is defaulted from the Settlements to Payment Product and
12. a Branch Account and Currency combination The following options are available e Instrument settlement is done through a Check MCK etc e Message payment is made by means of a SWIFT Message e Clearing the transaction is a local payment transaction and the settlement is routed through the Clearing House of the bank You can indicate the payment method as Clearing only e f the payment currency is the local currency of the branch e If it is one of the clearing currencies defined for the branch e If you have selected ALL in the currency field No payment message will be generated for settlements routed through a Clearing House Depending on the method in which you want to settle the contract you should specify either Instrument or Message details Instrument details If you opt to settle a contract with an instrument you should specify the type of instrument that you would use For example you could settle a contract using a Manager s Check a Check or a Demand Draft You should also specify the number that identifies the instrument This number will be printed on the instrument If the settlement is through an instrument you cannot specify party details 2 32 ORACLE Settlement through instruments is a feature applicable only for the Funds Transfer module of Oracle FLEXCUBE Details of Charges In this section you can maintain details of the party who will bear the charges incurred in processing the transac
13. a funds transfer instruction domestically Message Field Description Type Tag MT 205 20 Transaction Reference Number If the SWIFT SILVER parameter has been set to YES for your bank a unique reference number will be generated instead of the transaction reference number pda Related Reference a2 Value Date Currency Code Amount Js oeme Ja esen le imme fore fossa Yass eenen fe lesen nomi 2 52 ORACLE 2 7 7 MT 202COV 205COV For customer credit transfers you can send the outgoing payment messages in MT 202 COV or MT 205 COV formats if the receiver currency supports these formats sus Ton reamme anon gt O 136 Time Indication 8c 4 n1 x4 n Sender to Receiver Information 2 53 ORACLE 5 5 5 5 3a 4a 6a 7a 08a 72 5 5 5 50a 2a 6a 7a 09a 70 72 Status Tag Field Name Content Options o Currency Instructed Amount 3 a15d End of Sequence B underlying customer credit transfer details M Mandatory O Optional 2 7 7 1 Processing Outgoing MT202 COV MT205 COV Messages For non STP contracts booked from any module outgoing messages are generated in the new COV format depending on the transfer type the value specified for the Cover Required option the country codes of the sender and receiver provided that the receiver currency supports the new formats The following message types are used to handle the cover messages in the new format e CUST
14. and Transaction Summary screen also Incoming Swift Upload process support MT019 would contain either e Reference number PC Contract e DCN of the outgoing message that was generated Reference number present in the field of MT019 is searched first in PC Contract and upon receiving MT019 the NAK_STATUS of the record is marked to NAK In case of the record not getting updated in the Contract Master the message table is queried for DCN in the field to obtain the reference no of the corresponding PC Contract and the NAK_STATUS is marked as NAK Given below are some examples of the SWIFT messages discussed above Example Customer Transfer Ms Tanya Agnihotri a customer of your bank Bank Austria Vienna instructs you to transfer Dutch Guilders 100 000 to the account of Ms Tina Shenoy with Citibank Mumbai for her birthday Message Details Format Explanation Sender BKAUATWWA The BIC Code assigned to Bank Austria Vienna Receiver CITIBKINMUO The BIC Code assigned to Citibank Mumbai Sender Reference 20 494931 DEV S Ol Bank Operation Code 20b 0RED oO Value date Currency Interbank Field 32 A of SWIFT settled amount 32A 020426NLG100000 2 62 ORACLE Message Details Format Explanation Ordering Customer 50K Tanya Agnihotri Field 50 K of SWIFT Sender s Correspondent 53B CITIBKUSNY1 Field 53 B of SWIFT The correspondent bank is Citibank New York Example Il Payment Order MT 202 esoo emt epenn
15. and settlement has RTGS cover required enabled and if the network level flag allows new COV format then the system uses following message format gt CUST_RTGS_COV new COVER_RTGS format similar to 205COV format If transfer type is CustomerTransferCover and settlement has RTGS cover required enabled and if the network level flag does not allow new COV format then the system uses following message format gt COVER_RTGS old RTGS cover format 2 7 8 MT 210 Notice to Receive All information pertaining to this message should be captured against the amount tag TRF_AMT Message Field Tag Description Type Transaction Reference Number This message type should not start or end with a or This displays the Contract Reference number for most contracts For an LC BC and LD message the user reference number is displayed For an FT message the source reference number is displayed If the SWIFT SILVER parameter has been set to YES for your bank a unique reference number will be generated instead of the transaction reference number Related Reference Number This is the contract reference number in most cases However for a Money Market confirmation message the common reference number of the Message Field Tag Description Type contract is displayed in this field For an LC message the user reference number is displayed For an FT message the source reference number is displayed
16. and the receiver 2 44 ORACLE 52a Ordering This field gets populated depending on your entry in the Institution Ordering institution field If the transfer has originated from a Message Field Tag Description Type ree 54a Receiver s This field gets populated based on your entry in the Receiver Correspondent Correspondent field in the Settlement Instructions screen The information available in this field can be deleted if you do not need it 55 Third This field Specifies the Receiver s branch when the funds Reimbursement are made available to this branch through a financial bank institution other than that indicated in field 53a 56a Intermediary This information maintained for the Intermediary field is defaulted here You can change it 57a Account With The information maintained for the Account With Institution Institution field is displayed here You have the option of changing tt If the value for field 72 does not contain the string RCB and field 55 is not null then the value in field 55 will be displayed here If field 55 is null then the value in field 54 will be displayed here 59 Beneficiary The information maintained in the Ultimate Beneficiary field Customer is defaulted here You have the option of deleting this information Here you need to link this tag content to the customer account and sender to the counter party BIC If the ultimate beneficiary of the transaction is a valid
17. codes maintained in the system You can choose the appropriate one The country information is captured to enable Mantas to analyse the transactions for possible money laundering activities For more details on Mantas refer Mantas interface document Receiver You can specify the final Receiver as apart from the Account With Institution if the Ultimate Beneficiary desires that the payment message should be sent there If this is not maintained the Account With Institution becomes the default Receiver You can also capture the Sender to Receiver Information in this screen 2 20 ORACLE 2 4 3 For more details relating to specific parties please refer to the SWIFT manuals ERI Currency For every Counterparty and In Currency combination for which you maintain settlement instructions you can define an Euro Related Information ERI Currency The ERI Currency can be e In currency e Euro This is used during the transition period settlements of components in In currencies can be made either in the same currency or in the Euro EUR depending on the settlement account s maintained Similarly components in Euro can either be settled in EUR or in an In currency In the settlement messages that are generated MT 100 MT202 the settlement amount would be reported in the Settlement Account Currency However you can opt to additionally furnish the value of the component in an ERI currency The ERI Currency that you
18. e PHOWN Deal by Phone e PHONBEW Contact beneficiary by phone ORACLE 2 19 e PHONIBK Contact intermediary by phone e RCB Receiver s correspondent e REC Receiver e REJT REJT e RETN RETN e TELE TELE e TELEBEWN TELEBEN e TELEIBK TELEIBK e TSU Trade Services Utility transaction e BROKER Broker negotiating the contract e ELEC Deal has been arranged via an electronic means e TELEX Deal by TELEX e TIME Time of transaction execution e VENU Venue of transaction execution If you choose TSU the code placed between slashes must be followed by the invoice number a slash and the amount paid Account With Institution An Account with Institution refers to the financial institution at which the ordering party requests the Beneficiary to be paid The Account With Institution may be a branch or affiliate of the Receiver or of the Intermediary or of the Beneficiary Institution or an entirely different financial institution This field corresponds to Field 57A of a SWIFT message You can enter one of the following e ISO Bank Identifier Code of the bank e Branch of the Receiver s Correspondent e Name and address of the Receiver s Correspondent e Other identification codes for example account number Country Specify the country of the account with institution This adjoining option list displays all valid country
19. for an entity means defining the settlement accounts and a detailed settlement route comprising the correspondent accounts and the intermediaries through which payment is to be routed The party information you can capture adheres to SWIFT standards You can maintain the following basic settlement preferences for an entity Customer BIC module currency product Sequence Number and branch combination e The Pay out Account Branch and Currency The Receive Account for incoming payments Branch and Currency If a Cover is required to be sent for SWIFT messages e If the charge for the message is to be borne by the bank or the beneficiary or shared between them e The charge account which will be used as the default account for all charges during contract input e lf a receive notice MT 210 has to be generated for money settlements made in a specific currency Counterparty Type The Counterparty Type can either be CIF or BIC depending on whether your bank has an accounting relationship with the party for whom the instruction is being maintained or whether it only has a SWIFT messaging relationship If the counterparty is a CIF in Oracle FLEXCUBE you will have to select CIF as the party type and choose the relevant CIF ID in the adjacent field 2 14 ORACLE However if the entity is not an actual customer of your bank but you would be sending receiving payment messages to from that party you will have to choose BIC as the count
20. sent by the Account Servicing institution to notify an account owner of an entry that has been debited to its account Bank Austria Vienna asks Citibank NY to pay Citibank Mumbai by debiting Bank Austria s account with Citibank New York An MT 900 is sent by Citibank NY after it pays Citibank Mumbai and debits Bank Austria s account with it 2 16 MT 362 Interest Rate Reset Advice of Payment This message is exchanged by or on behalf of the financial institutions Party A and Party B who have agreed to a single or cross currency interest rate derivative transaction including caps collars and floors This message may be used to e advise details of determination of the floating interest rate s e advise details of payment of interest at the end of an interest period Maximum Length 2000 Tieton a 4 Identification of the Swap 10a 5a Contract Number Party A 16 6x 6x Ic Ic X Contract Number Party B 16 Effective Date 8 Termination Date 8 Fund or Beneficiary Customer Contact Information Sender to Receiver Information and Amount sees is Currency Principal Exchange 3la15d Amount 2 65 ORACLE Optional Sequence D Interest Rate Principal Payable by Party A Field Tag Field Name Mandatory Optional and Amount Currency Interest Amount N 3 a15d Currency Principal Exchange 3la15d Amount Details of Interest Rate 6 35x 2 66 ORACLE Optional Sequence E
21. soe rman a m s pe q Refer the Procedures User Manual for further details about the icons Ee 9 e lan i L 1 wj i 1 2 ORACLE 1 6 Related Documents For further information on procedures discussed in the manual refer to the Oracle FLEXCUBE manuals on e Common Procedures 1 3 ORACLE 2 The Settlements Service 2 1 Introduction The Settlements sub system is part of the core of Oracle FLEXCUBE This system is a central money settlement service that interfaces with the other modules of Oracle FLEXCUBE In Oracle FLEXCUBE the Settlements and Messaging systems are closely associated The Settlements system provides for a common set up of money settlement accounts and routes The Messaging system on the other hand handles the generation of settlement messages To handle money settlements in Oracle FLEXCUBE you have to e Maintain Bank Identifier Codes BIC e Maintain Settlement Preferences for a Customer Module Currency Branch or for a combination of any of the entities 2 2 Maintaining BIC Directory details As part of setting up some basic information for the functioning of Oracle FLEXCUBE you should maintain Bank Identifier Codes BIC You can define bank codes through the BIC Code Details screen You can invoke this screen by typing ISDBICDI in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button If you are maintaining de
22. specify for a Counterparty and In currency combination will default in the ERI CCY field in the Settlements Message Details screen Settlement through an instrument or message When the actual settlement event for a contract involving the entity takes place the payment and receive message details are updated in a message hand off table The Messaging system picks up the details from this table and based on the formats set up generates the messages Capturing Details of Parties Involved in Receipts Depending on the route funds take when you receive incoming payments you can maintain Intermediary and Beneficiary Institutions in the Receive Parties section of the Settlements Instructions Maintenance screen E Settlement Instructions Maintenance Web Page Dialog Branch BGT Module AL Counterparty BGTOOOBGT Product Code ALL Counterparty Type c IF 7 Sequence Number Currency GBP Relations Receive Branch BGT Branch BGT T Cover Required Account bgt003 Account bgt004 Cover By 7 Currency GBP Currency GBP Charges Details Payment By Message Payment By Message Ourselves Benificiary Shared Pay Parties Pay Parties Receiver Parties Cover Parties Clear Details Cover Detials Other Details Receiver Intermediary Beneficiary Instituion Fields Input By KAN2 Date Time 7 3 2000 19 58 05 Modification Number 1 open Authorized By KAN2 Date Time 7 3 2000 19 58 36 IY Authorized 2 24 ORACLE
23. these details in the Other Details tab in the Settlement Instructions Maintenance screen ze Settlement Instructions Maintenance Web Page Dialog Branch BGT Module AL Counterparty BGTOOOBGT Product Code ALL Counterparty Type CIF Sequence Number Currency GBP Relations Receive Branch BGT Branch BGT P Cover Required Account bgt003 Account bgt004 Cover By A Currency GBP Currency GBP Charges Details Payment By Message Payment By Message Ourselves Benificiary Shared Pay Parties Pay Parties Receiver Parties Cover Parties Clear Details Cover Detials Other Details Regulatory Reporting Details Transaction Type Bank Operation Code r Instruction Code Input By KAN2 Date Time 7 3 2000 19 58 05 Modification Number 1 fv Open Authorized By KAN2 Date Time 7 3 2000 19 58 36 E Authorized You can maintain the default MT 103 values for the following fields Bank Operation Code You can indicate the bank operation code that will be inserted in Field 23B of the MT 103 message The options available are SPRI SSTD SPAY and CRED Note that if the Bank Operation Code contains SPAY SSTD or SPRI the following validations will be done e C11 If account with institution is used with D option then party identifier is mandatory Either Clearing code or account has to be specified in the account line e C12 Account is mandatory in field 59 Instruction Code You can indicate the Inst
24. to identify the kind of relationship that exists between your bank and the BIC entity Select any one of the following options to indicate the same e No to indicate that the BIC Entity is not a customer of your bank e Mail select this option if the BIC entity is not a recognized SWIFT entity but an address internal to you bank In such cases all correspondence directed to the particular BIC entity will be sent as mail messages e Keys If a SWIFT Telex connectivity exists between your bank and the bank for which you are maintaining details you can select this option Subsequently you will have to specify the SWIFT Telex Key in the adjacent field SK arrangement Indicate whether a SK arrangement exists between your bank and the BIC entity If an arrangement does exist you can select the Yes option from the option list Sub Type Code Select the appropriate sub type code to be mapped to the BIC The adjoining option list offers the following factory shipped codes e BANK SWIFT Member Sub member e BEID Business Entity Identifier e BROK Brokers Dealers e COOP Co operative Agreement with SWIFT e CSDS Clearing Houses Central Depositories e CUST Subsidiary Providers of Custodian and Nominee Services e ETCP Electronic Trade Confirmation Providers e EXCH Recognized Exchanges e FUAD Fund Administrators e IMIS Investment Management Institutions e MCFI Financial Institution in a MA CUG 2 2 ORACLE e M
25. 1 Relations l Search Advanced Search Reset Authorization Status Record Status Bank Identification Code TRBRGB21LON BARBINBBSOO CHASNOKKXRX DEUTPLPK XXX BANKGBEBBRE SBININBBSOO CITIGB2LXXX HSBCGB11BR1 YESBGB11BR1 HAMAGB21 XXX PASCGB2LAXX BNBGBGSFRXX ABCDGBAD AFDSGBAD CUBDUSS3X XX m Authorization Status 4 Authorized U Unauthorized oooooooooooo0o0o 0o A A A A A A A A A A A A A A A 4 Record Status C Closed O Open Records per page 45 v Tike 1 Bank Name TRADE BRANCH FOR LC AND BC BARBINBESOO JPMORGAN EUROPE LIMITED OLSO BRANC DEUTSCHE BANK PBC 5 4 CM2 BANK BRANCH BANK THREE CITIBANK EUROPE PLC HSBC BANK SN RELIANCE IND SN BANK OF YOKOHAMA LTD BANCA BULGARIAN NATIONAL BANK CLEARSTREAM EUROCLEAR BANK 2 v aa P pil ootwpae Customer Number MN2000446 MN2000460 BIBO00383 CM2000261 CM2000277 ECW000455 MN2000395 MN2000450 SE68000457 SE8000456 TBROOO419 Bank Addr TRBRGB21LON BARBINBBSO0 ESSENDROPSGATE 7 UL J SAREGO 2 4 CM2 BANK 4D1 SBININBBSOO EUROPE HSBCGB11BR1 YESBGB11BR1 40 BASINGHALL STR PASCGB2LAXX ALEXANDER BATTEN CLEARSTREAM EUROCLEA CUBDUS33xXXX gt The query option is available on the following fields in this screen e BIC Code e National ID Only BIC Database plus e CHIPS UID Only BIC Database plus e Institution name e Tag To identify either Fl or AM record ty
26. 50 506 7000 Fax 1 650 506 7200 www oracle com financial_ services Copyright 2010 Oracle Financial Services Software Limited All rights reserved No part of this work may be reproduced stored in a retrieval system adopted or transmitted in any form or by any means electronic mechanical photographic graphic optic recording or otherwise translated in any language or computer language without the prior written permission of Oracle Financial Services Software Limited Due care has been taken to make this document and accompanying software package as accurate as possible However Oracle Financial Services Software Limited makes no representation or warranties with respect to the contents hereof and shall not be responsible for any loss or damage caused to the user by the direct or indirect use of this document and the accompanying Software System Furthermore Oracle Financial Services Software Limited reserves the right to alter modify or otherwise change in any manner the content hereof without obligation of Oracle Financial Services Software Limited to notify any person of such revision or changes All company and product names are trademarks of the respective companies with which they are associated
27. BIC then this field will display the BIC In case the beneficiary BIC is invalid then the field value will be null 70 Details of The Details of Payment captured in the Settlements screen Payment will be defaulted here 71A Information is defaulted from the Charge Bearer field in the FT Contract screen Sender s Charges Receiver s Charges 72 Sender to If you have captured the ERI Currency and Amount in the o Settlements screen the OCMT is populated along with the Information data in the Sender to Receiver information field in the Settlements screen Some of the fields like field 20 and 32A are generic in nature The details pertaining to the other fields are defaulted from your maintenance in the Settlement Instructions screen 2 45 ORACLE 2 1 2 Field 32A will display the credit amount and currency while field 33B will display the debit amount and currency in case of cross currency payments In case of intra European payments where EUR is the only currency involved field 33B will display the transaction amount In such cases input to field 33B will be mandatory The sender s charge currency of previous banks in the payment chain will be appended in field 71F of an outgoing MT103 During the STP of an incoming MT108 the fields 32A and 33B will not be compared to fields 71F and 71G While processing an incoming payment message where the value for field 71A is OUR and 71G is also present the system wi
28. CCO Non Financial Institution Participant in a MA CUG e MONE Money Brokers e NSFI Non Shareholding Financial Institutions e NSWB Non SWIFT BIC s e PRXY Securities Proxy Voting Agency e PSPA Payment System Participants e REGI Registrars and Transfer Agents e SSPA Securities System Participants e TESP Treasury ETC Service Provider e TRAD Trading Institutions e TRAV Travellers Cheques Issuers e TRCO Treasury Counterparty e TRUS Trustees Fiduciary Service Companies e ZZZZ Undefined Institutions Choose the appropriate one In case of upload the system automatically updates this field with the sub type code corresponding to the BIC BEI Indicator The system identifies whether the BEI status for the chosen sub type code is Yes or No from the back end maintenance in the ISTM_ SUBTYPE_CODE table It checks this option whenever the status in the table for the sub type code is Yes You cannot modify this field Payment Message You can indicate whether your counterparty whose BIC Code details you are capturing is capacitated to receive payment messages in the MT 103 format If so enable the Generate MT 103 as Payment Message option by checking the box However the Counterparty bank will still receive the payment messages in the MT103 format if you do not enable the box Generate MT 103 as Payment Message If you have chosen the MT 103 option you can enable the MT 103 format
29. Detials Other Details Cover details Bank Code Account Name Clearing Network Bank Name Input By KAN2 Date Time 7 3 2000 19 58 05 Modification Number 1 IY Open Authorized By KAN2 Date Time 7 3 2000 19 58 36 E Authorized For the cover party account details you can specify the bank code account and account name The following scenarios are possible Cover Cover By Payment Local Clearing Counterparty Cover Required By Details Details Local Message No Clearing Yes No Clearing Clearing Network for Local Clearing in Settlement Instructions You can specify a clearing network during settlement instruction maintenance for the Pay Leg and the Cover details This will be defaulted as part of Settlement pick up during Contract input and used subsequently while generating a PC Contract The Counter party name shows the list of Bank Codes for Cover Transfer and Bank Transfer The system will validate that the Bank Code Type for both the Counter party name and Counter party Bank Code is the same For Customer transfers this would be a user enterable field 2 25 ORACLE 2 4 6 Specifying the default MT 103 details You can define the default values for fields in MT 103 messages that are generated in respect of contracts involving the customer When a contract is entered for the customer in any module the values that you maintain here will be defaulted for MT 103 generation in respect of the contract You can maintain
30. LL in the currency field No payment message will be generated for settlements routed through a Clearing House Charge Details Specify whether charges for the message are to be borne by the bank ourselves or the beneficiary or will be shared This information is inserted in Field 71A of an MT103 message involving the combination for which settlement instructions are being maintained Cover Required This indicates whether the payment has to be sent with a cover message Check this box to enable this option Cover By If you have indicated that a cover is required for payments involving the customer then in this field you can indicate whether the cover is through messaging or through local clearing Accordingly you can choose the required option in this field If you indicate that cover is through messaging and the payment is through local clearing you need to maintain the local clearing counterparty details in the Local Clearing tab If you indicate that cover is through local clearing you need to maintain the cover details in the Cover Details tab 2 4 1 1 Maintaining settlement instructions for CLS deals When maintaining settlement instructions for CLS deals you should specify the module as FS FX Settlements This will indicate that they are meant exclusively for CLS deals The pay and receive accounts specified for the settlement instructions will be used as the Control Accounts for CLS deals Refer th
31. MT102 consolidation queue 2 49 ORACLE 2 3 2 Processing Incoming MT102 The following will be the sequence of processing incoming swift message MT 102 e MT102 upload process would decompose the message to create multiple MT103 s with Consolidation status Yes e Decomposition process validates whether any transaction is creating an outgoing message i e whether the bank is acting as an agent or not and if such a case exists then entire message M1102 would be sent to repair queue Therefore only incoming MT102 meant for the current branch would be supported Conditions to be met for Incoming message Tag 57A is Same as Receiver of the message Tag 57A is not present If above condition is not satisfied then message would be rejected e The decomposition process would create following entries Dr Senders NOSTRO Consolidated Amount Cr MT102 Incoming Suspense GL maintained at Branch level Consolidated Amount e The above entry s accounting reference number would be stored in Consolidated Acc Ref Number Field of each contract e STP rule would be enhanced to provide information of consolidation flag This function would help to route incoming MT103 generated due to MT102 to the Multi Credit Transfer Product e All the MT103 generated would be routed to the same Multi Credit Transfer product using Consolidation flag at message level e The incoming process of MT103 would populate Multi Credit R
32. Settlements Version 11 0 INT1316 ORACLE FCUBSV UM 11 0 0 0 0 0 0 January 2010 Oracle Part Number E51573 01 ORACLE FINANCIAL SERVICES ORACLE Document Control Author Documentation Team Group UBPG ae Created on October 01 2008 Revision No Final OO Updated by Documentation Team Reviewed by Development Approved by Software Quality Testing teams Assurance Team Updated on January 04 2010 Reviewed on January 04 Approved on January 04 2010 2010 ORACLE Settlements Table of Contents PT WS TIN oars ccc ace acs atcece sve ec occu cec cate ean cranes atece ee ean ececwect eden dene tases cueen se neeecececsuedesveueecoewer 1 1 1 1 MIND EC TON ereere iea rv vo a gate np sete EEEE EEE na scanned EE EEEE E l 1 e 2 E E E I T E N A E E eT E ey E eee E T eee l 1 1 3 ORANA TON ce smote a E E E E E ONG l 1 1 4 CONVENTIONS USED IN THIS MANUAL cccccccccccecccsseesstssssceescccccceeeeeseeseessstnsceessaseceeeeseseseeeeesttssseeeseaaaees l 1 1 5 GLOSSARY OF TC ONS cae scutes onies ERIE AE TEE I EEAS EEE ISEE EEE 1 2 t6 RELATED DOCUMENTS renee nee ae nr ener E A EEEREN EE EEE 1 3 TOE SEFILEMENTIS SERVICE eee ee ee re 2 1 2 1 TINERODU C O a E E EE E E E E taeerenneaceenia aeenaaca 2 1 2 2 MANTANING BIC DIRECTORY DETALLS seseeeeeeeeeeeeeeeeereeeeeeeseeseerereeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeeeeeeeees 2 1 Zed Specifying BIC Code etal ccccccsccccccccccccscsessssseccceccnaesssseeceeesaaensseeceeeesa
33. T Payment Message A fax copy of an MT 103 can be sent to the counterparty of a transfer only if the Payment Message PAYMENT MESSAGE was triggered at the transfer initiation event INIT Generated with a Payment Message While indicating the messages that should be generated at the event INIT you should also associate the pre shipped advice tyoe FAX_PMT_MSG to the event When the FT is authorized the MT 103 is generated from the Outgoing Message Browser and the Fax copy is triggered for generation 9 43 ORACLE Generation of a unique reference number for Field 20 If the SWIFT SILVER parameter has been set to YES for your bank during the funds transfer a unique reference number will be generated in field 20 The unique reference number is a combination of the first 7 characters of the contract reference number a single digit unique number and the last 8 characters of the contract reference number The single digit unique number is obtained as follows For all credit type transfers MT910 MT200 MT103 MT103P MT202 and cover message it would be 2 If the cover message is also sent along with the payment messages then it would be 3 For debit type transfers MT210 and MT900 it would be 1 Due to this setup during the Nostro reconciliation process the internal reference number of transaction related to funds transfer module would be modified before comparison with the external reference number
34. T message is captured in the Settlement Message Details Parties screen the system will display the parties involved in the transaction based on the values that come in the fields 52 54 55 56 57 58 etc However you can change the parties by choosing the appropriate value from the respective option lists In case of the messages MT 103 MT202 and MT210 the option lists will display only those BICs for which the option BEI Indicator is unchecked in the BIC Code Maintenance screen However you can manually enter a BIC for which the option BEI Indicator is checked During message generation the system will replace the BIC with the corresponding name and address of the party The number of banks intermediaries involved in the transfer would in practice depend on the e Relationships and arrangements between the sending and receiving banks e Customer instructions 2 38 ORACLE e Location of parties e The banking regulations of a country During the life cycle of a contract you will be allowed to amend the details of a Settlement Instruction only for those components which are yet to be settled Settlement Details Web Page Dialog Reference Number Component Account Details Message Details Parties Parties Cover Parties Other Details Clearing Details Local Clearing Beneficiary Institution For Cover For Cover 1 For Cover 2 For Cover 3 For Cover 4 For Cover 5 2 6 3 3 Cover Parties For local cur
35. UDF Mapping screen If enabled this indicates that accounting entries maintained for the PC product should be posted for the PC contract initiated for Clearing 2 40 ORACLE 2 6 4 Clearing Network During Contract Input Clearing Network in settlement screen will be defaulted with Clearing Network maintained in local clearing section in settlement instruction Default MT 103 details In the Settlement Instructions screen you would have maintained the default values for fields in MT 103 messages that are generated in respect of contracts involving an entity module currency and branch combination When a contract is entered for the customer in any module the values that you maintain here will be defaulted for MT 103 generation in respect of the contract and you can view them in the Settlement sub screen of the contract main screen Settlement Details Web Page Dialog Reference Number Component Account Details Message Details Parties Parties Cover Parties Other Details Clearing Details Local Clearing Regulatory Reporting Details Time Indicators Regulatory Report 1 Y Time Indicator 1 7 Bank Operation Code 7 Regulatory Report 2 Time Indicator 2 v Transaction Code Regulatory Report 3 r Time Indicator 3 v Instruction Code Instruction Code 1 Description Instruction Code 2 Description Instruction Code 3 Description Instruction Code 4 Description Instruction Code 5 Description Instruction
36. _COVER e CUST_COVERL e CUST_RTGS_COV The cover message format to be used during message generation is derived as follows e If transfer type is CustomerTransfer Cover required is true and country codes of sender and receiver are same and the receiver currency allows new COV format then the system uses following message format gt CUST_COVERL MT205COV lf transfer type is CustomerTransfer Cover required is true and country codes of sender and receiver are same and if the receiver currency does not allow new COV format then the system uses following message format gt COVERL MT205 old cover format If transfer type is CustomerTransfer Cover required is true and currency of sender and receiver are not same and if receiver currency allows new COV format then the system uses following message format gt CUST COVER MT202COV If transfer type is CustomerTransfer Cover required is true and currency of sender and receiver are not same and if receiver currency does not allow new COV format then the system uses following message format gt COVER MT202 old cover format If transfer type is CustomerTransfer and settlement has RTGS cover required enabled ad if the network level flag allows new COV format then the system uses following message format gt CUST_RTGS_COV new RTGS COV format similar to 205COV format If transfer type is CustomerTransfer and
37. aassseeeeeeeaaaaasseseeseeeeuauaaseeeeees 2 2 222 Reguest Tor T ransfeF nasczstaanceaasa Soin issan eno aaa eE A A Aa saai anoda i ane ia aa ainaani aiaiai 2 4 P Maintaining BIC directories nneeennnnnnnnnnnnssssseennnssssseerossssssrereosssssrereosssssserrensssssserereessssereesssssee 2 4 224 I 59 OF eg HT RY 0572 VARY 2 126 eee 2 5 2 22 Uploading BIC files cccccccccccccccccccccsceesseeceeeeeaeesseeeeeeeeeaeeeeeeeeeeeeaaeeeeeeeeeesaaaeseeeeeeeeaaaaeseeeeeeesaaaanseseeeenaas 2 9 2 2 6 Operations on a BIC record wicccccccccccccccccece cece eens eee eeeeeeeee cece eee e ae AAA AAA EEASEEEEEEEEEEEEE EEE E EE EEEEA GAGA GAGA EERE EEEEEES 2 10 25 MAINTAINING MULTI MODE SETTLEMENT DETAILS seseeeseessesessseesessseeessessesssssssseesseeeeeaaaaaeeeasaaaeeaes 2 11 2 4 CAPTURING SETTLEMENT PREFERENCES FOR A CUSTOMER ssssseeeeseneeeeececeeceeeeeeeeseeeenaaaeeeeeeeeeeeeees 2 14 2 4 2 Capturing Details of Parties Involved in PAYMENUES ccccccccccssseccccecccceeeeeeseecceeeaaaeneseeeeeeeaaaeeeeseeseseaaaes 2 17 2 4 3 Capturing Details of Parties Involved in R CCIpPtS cccccccccsseccsecccccceneneesseeeceeeaaaseseeeeeeeeaaaaseeeeeeeeeaaaes 2 21 2 4 4 Capiurine Cover CLAUS scicaistacesnudtaueneioteiictisaaiistvaseedeeetiawiensotivan S EAE EEA E N ANE 2 23 2 4 5 Maintaining Local Clearing Details and Cover Details for Customer Settlement Instructions 2 23 2 4 6 Specifying the default MT 103 details cccccccccccc
38. aining settlement instructions then you can choose any Product available under the module from the option list provided You can also choose All to maintain settlement instructions for all products under the selected module Product Code Indicate a specific product code or choose All from the option list However if you have chosen All in the Module field this field will be defaulted to ALL You will not be allowed to change this Currency You can maintain settlement instructions for a particular currency or for all the currencies From the option list select the particular currency code or choose the ALL option Branch You can maintain settlement instructions for all the branches or for a particular branch From the option list select the particular branch code or choose the ALL option Payment By Indicate the method of payment for both Outgoing as well as Incoming Payments for a Branch Account and Currency combination The following options are available e Instrument settlement is done through a Check MCK etc e Message payment is made by means of a SWIFT Message 2 15 ORACLE e Clearing the transaction is a local payment transaction and the settlement is routed through the Clearing House of the bank vou can indicate the payment method as Clearing only e Ifthe payment currency is the local currency of the branch e If it is one of the clearing currencies defined for the branch e f you have selected A
39. an ooy moo oner 2 97 ORACLE tv comer ccv oaae Ban 2 6 Processing Settlements The Settlement details for a contract or deal get defaulted based on the maintenance of settlement instructions for the Customer BIC code involved in the transaction To invoke the Settlement Details screen click Settlement button in the Contract Main screen of a module Settlement Details Web Page Dialog Reference Number Component Account Details Message Details Parties Parties Cover Parties Other Details Clearing Details Local Clearing IBAN Account Number Settlement Details C Component Currency Branch Account Account Currency D C Exchange Rate Rate Code Spread Definition Customer Spread ERI Currency ERI Amount Hj ee Settlement Direction D Debit C Credit Component Description By default the settlement details of all components of a contract which affect a customer type of account the Role Types can be Customer Remitter Beneficiary for all the events associated to the product for which the Role to Head mapping has not been provided to the product associated with the contract are displayed in this screen 2 28 ORACLE 2 6 1 Example As per the maintenance that you have done for a Product the following accounting entries will be posted during the initiation of a contract Accounting Role Amount Tag Dr Cr Indicator ASSETGL PRINCIPAL cusTowen PRINCIPAL To achieve this in the Ro
40. be picked up and reflected here The country information is captured to enable Mantas to analyse the transactions for possible money laundering activities For more details on Mantas refer Mantas interface document 2 22 ORACLE 2 4 4 Capturing Cover details The Cover details are defaulted from the Contract Online screen only for Outgoing Customer Transfers with Cover t T Settlement Instructions Maintenance Web Page Dialog Branch BGT Module AL Counterparty BGTOOOBGT Product Code ALL Counterparty Type CIF Sequence Number Currency GBP Relations Receive Branch BGT Branch BGT I Cover Required Account bgt003 Account bgt004 Cover By Currency GBP Currency GBP Charges Details Payment By Message Payment By Message Ourselves Benificiary Shared Pay Parties Pay Parties Receiver Parties Cover Parties Clear Details Cover Detials Other Details Beneficiary Institution For Cover Input By KAN Date Time 7 3 2000 19 58 05 Modification Number 1 Iv Open Authorized By KAN2 Date Time 7 3 2000 19 58 36 E Authorized You can specify the following details Country Specify the country of the beneficiary institution for cover This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one 2 4 5 Maintaining Local Clearing Details and Cover Details for Customer Settlement Instructions When you specify settlement instructions for a customer
41. ber This is the contract reference number in most cases However for a Money Market confirmation message the common reference number of the contract is displayed in this field For an LC message the user reference number is displayed For an FT message the source reference number is displayed Value Date Currency Code Amount Your entry for Our Correspondent in the Settlement Instructions screen is defaulted here Your entry for the Intermediary field in the Settlement Instructions screen is defaulted here Your entry against the Account With Institution field in the Settlement Instructions screen id defaulted here MT 202 General Financial Institution Transfer All information pertaining to this message should be captured against the amount tag TRF_AMT Message Field Tag Description Type g T OO oo Transaction Reference Number This message type should not start or end with a or This displays the Contract Reference number for most contracts For an LC BC and LD message the user reference number is displayed For an FT message the source reference number is displayed If the SWIFT SILVER parameter has been set to YES for your bank a unique reference number will be generated instead of the transaction reference number Related Reference Number This is the contract reference number in most cases However for a Money Market confirmation message the common reference number of the contra
42. cccccccccssescccccceeeeeesesecceeeeaasesseseeeeeeesaaseeeeeceeesaaaaeeeeeeeeas 2 26 2 5 THE SEQUENCE IN WHICH SETTLEMENT INSTRUCTIONS ARE RESOLVED ccccscccescsccesceuscescescenscusceusss 2 27 20 PROCESSING SE PIU EMIEINGS wcopsscasusssccsemssiedsicennidereepavaasennsanesieeesnsswensseasensainaasecnesecseesayaasensuinesoopneneseeedeunesnnt 2 28 2 6 1 CODA IO ACCOM ICIS sa E eval cud iincwesiursuachoat dak E E 2 29 2 6 2 Capturing Message Details fOr a CONE ACE cccccccccsccccccccccse ne eseeececeeeeaeeeseceeeeeaaaaeseeeeeeesaaaasseeeeeeseaaanees 2 31 2 6 3 CODA III E siscias havens savab seat ionntons usa vse ne ateach veneers amas eeae anna een 2 35 2 6 4 DeU MEIO GCL S saci sa sts hess E code alualute cose outa Navan teh lune seagienis nese abn E 2 4 2T SWIFT MESSAGES HANDLED BY ORACLE FLEXCUBE ssssssessseeeseeeeeeeeeeereeereerereereeeeeeereeeeeeererereeeeeeeeeees 2 43 2 7 1 Formeni Message MT LUO 103 leemes E E doa 2 43 LU WET LOO CCU SOM CI L OS T ees S A E R 2 46 Ra MT 102 Consolidated Customer Transfer with Cover cccccccccccssssssesccccceecasesseeececeeeecaaseseseceeeeaaaaess 2 47 NE MT 200 Financial Institution Transfer for its Own ACCOUNL ccsssecccccccecceeeeeecccceeeceaaaeesesceeeeeaaaes 2 50 E MT 202 General Financial Institution Transfer ccccccccccsecccccccccccnsesssecceeeeaaeessecceeeeeeaaaaaseeeeeeeeaas 2 51 2 7 6 MT 205 Financial Institution Transfer EXCCULION cccccccccscecccccccece ne eeeeeeee
43. ceiver Correspondent field in the Settlement Instructions screen The information available in this field can be deleted if you do not need it 56a Intermediary This information maintained for the Intermediary field is defaulted here You can change it 2 46 ORACLE 53a Sender s The information that is captured for the Receiver of Cover Correspondent field in the Settlement Instructions screen is defaulted if a Message Field Tag Description Type 57a Account With The information maintained for the Account With Institution Institution field is displayed here You have the option of changing it 59 Beneficiary The information maintained in the Ultimate Beneficiary field Customer is defaulted here You have the option of deleting this information Here you need to link this tag content to the customer account and sender to the counter party BIC 70 Details of The Details of Payment captured in the Settlements screen Payment will be defaulted here Information is defaulted from the Charge Bearer field in the FT Contract screen 72 Sender to If you have captured the ERI Currency and Amount in the Receiver Settlements screen the OCMT is populated along with the Information data in the Sender to Receiver information field in the Settlements screen Some of the fields like field 20 and 32A are generic in nature The details pertaining to the other fields are defaulted from your maintenance in the Settlement Inst
44. cessio Of LINCOM J20 sinsahcbonsaascinnnoatursneveinsaewa EEEN ETE ENTE 2 69 ORACLE 3 NETTING PAY MENTS ACROSS MODULES wisscasssdsesceavasetsseuanassesnssencesseasonssesecnnnacsssousbecdsesenseansesssnusasesave 3 1 3 1 DODO TIO eee E A A E E S E E ere err ee 3 1 3 1 1 Maintenance required for Netting Payments in Oracle FLEXCUBE oooooeeeeeeennnnsnnssssssseseeeeeeenes 3 1 3 1 2 Capturing the Agreement related details cccccccccssccccccccccccneesseccceeeeaeeeeseceeeeeaaaeeeeeeeeeesaaaaseeeseeeeaaaages 3 3 1 3 Maintaining netting related information at the contract level nnneennnnnnnnnnnnnnsseeennnnsssseereesssse 3 4 3 1 4 Maintenance pertaining to the Route for settling payments oooeseonsssnnnnnnnsssseeennnssssseernessssseeereesse 3 5 a2 TENE RATING DME IE TT FW E E E 3 6 3 24 Viewing details of Netted Contracts cscccccccccccssseececcceeeeneeesseeeeeeeeeeaaeneeeeeeeeeaaseeseeeeeeeeaaaasseeeeeesaaaaaees 3 6 d Oh 05 6 a Dee Dd dh 9 ee ee aaa 4 1 4 1 MINE ON ercsi I EE EE E E RG sate a pea sete EEE EEEE EEEE 4 1 A2 BIC RECORDUPLOAD arrearage reton E EEE EEEE E EE EEE 4 1 Bo 5 600 9 118 TOMATE maa E E E E E E E E 4 1 ORACLE 1 About this Manual 1 1 Introduction This manual is designed to help you get acquainted with the manner in which contracts in a product are settled in Oracle FLEXCUBE It takes you through the various steps involved in processing a Settlement Besides this User Manual y
45. chosen becomes the pay account Similarly if a component is to be received the debit account chosen becomes the receive account in the settlement maintenance Capturing Message Details for a contract A contract can either be settled through an instrument or a Messaging service such as SWIFT The details of the instrument or message have to be specified in the Message Details screen The message details that you specify will apply only for messages generated through SWIFT The type of SWIFT message that is generated depends on the parties involved in the contract 2 31 ORACLE ze Settlement Details Web Page Dialog Reference Number Component Account Details Message Details Parties Parties Cover Parties Other Details Clearing Details Local Clearing Instrument Details Type Component Payment By Number Message Instrument Clearing Details of Charges Remitter all Charges Beneficiary all Charges Remitter our Charges Clearing Network Message Details Sender to Receiver Information Network Code F Cover Required Information 1 Information 2 Cover By Information 3 Clearing Information 4 Message Information 5 Information 6 Details of Payment Details of Payment 1 F RTGS Payment RTGS Network Details of Payment 2 Details of Payment 3 Details of Payment 4 Transfer Type 2 6 2 1 Account Details Payment By Indicate the method of payment for both Outgoing as well as Incoming Payments for
46. cific counterparty for the currency pair are unavailable the System looks for the customer spread maintained for the wildcard ALL entry If even that is not available then the Customer Spread defaults to zero The method of spread definition whether percentage or points is also displayed If you have specified an account that uses an account class that is restricted for the product an override is sought when you attempt to save the contract Customer Spread This defaults from your specification of tenor wise spread for the relevant Currency Pair in the Customer Spread Maintenance screen You can change this for a specific contract ERI Currency and ERI Amount SWIFT messages MT103 MT202 generated towards settlement can furnish the value of the settlement amount in both the settlement account currency and a Euro Related Information ERI currency of your choice If you opt to furnish the ERI value of the amount you have to enter the following in this screen e The ERI currency e The ERI Amount The system defaults to the ERI currency specified for the customer and currency combination You can change the default ERI currency The ERI amount that you specify will be validated against the Tolerance Limit specified for the ERI currency in the Currency Maintenance screen 2 30 ORACLE 2 6 2 Gen Message Enable this option if a payment messages has to be generated for the settlement instruction Netting In addition to main
47. ct is displayed in this field For an LC message the user reference number is displayed For an FT message the source reference number is displayed Value Date Currency Code Amount Message Field lola Description Type 52a nindi Your entry for Ordering Institution in the Settlement Message Institution Details screen is defaulted here If the transfer is originating from a different bank you will need to capture the relevant data in this field You will also need to capture information if the ordering institution is different from the Sending institution 57a Account This is field 54 of the corresponding MT103 it During STP if this field is null in the incoming message the system will not send an outgoing MT202 It will only book an incoming payment 58a The details of the receiver in the corresponding MT100 are Beneficiary defaulted here ASEE You can capture the BIC code or the CIF Number assigned to the bank in this field STOP In MT103 MT103P and MT202 if the value in field 52 Ordering Institution is the same as the sender s correspondent then field 52 will be suppressed during message generation 2 6 MT 205 Financial Institution Transfer Execution This message is sent by the Receiver of a category 2 transfer message i e MT 200 201 202 203 or 205 directly or through correspondent s to another financial institution located in the same country as the Sender It is used to further transmit
48. d would be filled up only if the Transaction Type codes for Type Code the underlying FT Contracts differ Regulatory This field would be filled up only if the Regulatory Reporting for the Reporting underlying FT Contracts differs 7 0 26 T B 11 Mandatory Sequence A General Information Currency Instru This field will be populated only if the Credit Amount lt gt 32B cted Amount 71A Details of This field would be based on Charge Whom and will be filled up Charges only if Charge Whom for the underlying FT Contracts differs 71F Sender s Sender s Charges Charges 71G Receiver s Receivers Charges Charges 36 Exchange Rate This field would be filled up in case the Currency Codes in Field 32B and 33B are different Mandatory Sequence C Settlement Details 32A M_ Value Date Sum of all Amounts in 32B Sum of Receiver s Charges if Currency Charge Whom OUR else this is equal to the Amount in 33B Code Amount 32B 19 Sum of Sum of all amounts in 32B Amounts 71G Sum of Sum of Receiver s Charges Receiver s Charges 53a Sender s Sender s Correspondent Corresponden t 54a Receiver s Receivers Correspondent Corresponden t 72 O Sender to Payment Details of FT Contract Receiver Information 2 7 3 1 End of Transaction Input for MT102 The End of Transaction Input EOTI process will display an error message if there are some pending consolidated transactions in
49. e Continuous Linked Settlements chapter of the Foreign Exchange User Manual for details on the following e Maintaining settlement instructions for CLS deals e Other maintenances required to be CLS compliant e The processing involved in the settlement of CLS deals in Oracle FLEXCUBE 2 16 ORACLE 2 4 2 Capturing Details of Parties Involved in Payments Before funds actually reach the Ultimate Beneficiary of a payment it may have to pass through several other banks or parties You can capture details of the parties involved in a payment in the Pay Parties sections of the Settlement Instructions Maintenance screen eS Settlement Instructions Maintenance Web Page Dialog Branch BGT Module AL Counterparty BGTOOOBGT Product Code ALL Counterparty Type c IF zj Sequence Number Currency GBP Relations Receive Branch BGT Branch BGT T Cover Required Account bgt003 Account bgt004 Cover By 7 Currency GBP Currency GBP Charges Details Payment By Message Payment By Message Ourselves Benificiary Shared Pay Parties Pay Parties Receiver Parties Cover Parties Clear Details Cover Detials Other Details Intermediary Reimbursement Institution Intermediary I RTGS Payment RTGS Network Input By KAN2 Date Time 7 3 2000 19 58 05 Modification Number 1 Iv Open Authorized By KAN2 Date Time 7 3 2000 19 58 36 IY Authorized These screens contain fields that mark possible routes of a payment Intermediar
50. e applicable on transactions involving specific products thereby establishing certain controls you can maintain a Product Restriction list for each counterparty To maintain a list of allowed disallowed products click on the Product Restriction tab in this screen 3 3 ORACLE 3 1 3 E Netting Agreement Maintenance Web Page Dialog Customer Number 4 4410001 Agreement Reference Number REFO1 Met Agreements Product Restriction Product Restriction Products Allowed f Allowed Disallowed Netting Products E Product Code Product Description Fields Input By SAM Date Time 142007 23 11 11 Modification Number 1 gi Open Authorized By SANT Date Time 14 200 23 12 45 E Authorized Choosing the list type You can specify product restrictions in the form of allowed lists or disallowed lists If you create an allowed list of products entries involving transactions for the particular counterparty and product combination will be netted On the other hand if you maintain a disallowed list the entries involving the respective product and counterparty combination will not be netted You can indicate whether you are maintaining an allowed or a disallowed list type by choosing the appropriate option Maintaining netting related information at the contract level In addition to maintaining a netting agreement for each counterparty you have to specify whether or not the contract is under the netting agreemen
51. eeecaaeeeeeeeeeeeaaaasseeeeseseuaaaees 2 52 2d IVE OV a CO Vasa atest seasons E das oe dactepaite ae E O tucaaede 2 53 2 7 8 VEE ZT CIN GCC TO TROCCIV GS aaea E ET E ENEO NOANA 2 55 2 7 9 MT 320 Fixed Deposit Confirmation cccccccsssescseeccecececeececeenneeeeeeeaesssessssseeeeeeeeeeeeeeeaaaaaaaassseeeeeeees 2 56 2 7 10 MT 300 Foreign Exchange Confirmation ccccccccccsssscccccccecsseseesecceeeecaussssecceeeeeesaaseseeecesesaaaaseeeeees 2 58 2 7 11 MT 400 Advice Of Payment cccccccccccccccccsssssscecccccuccussseeecccsuaausseeececcaaaaseeeeeecsaaausaaseeseeessuauaneeseeeees 2 59 2 7 12 Payment Message Generation for MT300 3 20 cccccccccccccccccceececeaaeeseeeeseeeeeeeeeeeeeeaaaasaaaaaaaaassseeseeees 2 60 2 7 13 MT 756 Advice of Reimbursement or Payment cccccccccccssseeesecceeeecnaeeseccceseeeaaaseeseceeeesaaaeeeeeeeeees 2 61 2 7 14 MT 012 ACK Status ACKnOWleAGCMENL cccccccccccssseesseccceeeeneeeseeeeeeeeaaaeeseeeeeeeeasaeeeeeeeessaaaeeseeeeeees 2 61 2 715 MT 019 NAK Status ACKNOWleAZCMENL cccccccccccssseecceccceeceneeesseeeeeeenaeeeseeeeeeeeaaaseseeeeeessaaaaeeeeeeeees 2 62 2 7 16 MT 362 Interest Rate Reset Advice Of Payment cccccccccccssesesesccecececaeeesseeceeeeaaaeseseeeeeesaaaaeeeeeeeeas 2 64 Zee GENERATION OF IVI 20 MESSAGES eaters esses soaaatsetesierttic ete somsandte NERONE NEO UE EEA 2 68 2 8 1 Generalin MII20 IGS 5G servirsene issiron rar EE N EE OEE EE O EEEE EAEE 2 68 2 8 2 Pro
52. eference Number at contract level with Consolidation reference tag 20 of MT102 number present at message level e Incoming upload Process of MT103 which are linked to the Multi Credit Transfer would pass following entries at each transaction level gt Dr MT102 Clearing Suspense GL gt Cr DAO Beneficiary A field called Multi Credit Ref No will be available in the Incoming Browser This would be populated for all the MT103 generated due to an incoming MT102 and would be populated with the value of tag 20 in Sequence A of the MT102 2 4 MT 200 Financial Institution Transfer for its Own Account In Oracle FLEXCUBE you need to capture specific information against each field number for the Amount Tag TRF_AMT Message Field Tag Description Type MT200 20 Transaction Reference Number This message type should not start or end with a or This displays the Contract Reference number for most contracts For an LC BC and LD message the user reference number is displayed For an FT message the source reference number is displayed If the SWIFT_SILVER parameter has been set to YES for your bank a unique reference number will be generated instead of 2 50 ORACLE 2 7 9 Message Field Tag Type 56a Intermediary 57a Account With Institution 72 Sender to Receiver Information 53B Sender s SE otclrshc the transaction reference number Related Reference Num
53. eneration of MT920 Messages 2 8 1 Oracle FLEXCUBE allows you to generate SWIFT Messages for transactions MT920 is a transaction message requesting latest information available for the particular account The request will be to transmit account customer statement message M1940 or Balance report M1941 or Interim statement M1942 or a customer Summary statement MT950 Generating MT920 Message You need to generate the MT920 message You can do this in the Generate MT920 screen The screen is as shown below F Genarate M1920 Web Pape Dialog Receiver Transaction Ref Mo Details CusiomerNo AccountNo Message Currency D FLOOR LIMITI F C FLOOR LIMT2 34F Message Input Bry Dat Time Modification Humber Bogen Authorized Bry Date Time BB authorized Fa Receiver In the Generate MT920 screen you can select the receiver of the message The system shows only those receivers whose details you have maintained in the customer maintenance with MT920 as Y Reference No After providing the receiver details click P button Based on this the system generates the new reference number Details Under Details in the Generate MT920 screen provide the following details about the chosen receiver Customer No Under Details select the required Customer No from the options listed In the list you can find only those customer numbers maintained for the receiver in customer BIC maintenance with MT920 f
54. er either e The ISO Bank Identifier Code of the Beneficiary Institution e The Name and Address of the Beneficiary Institution Country Specify the country of the beneficiary institution This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Ultimate Beneficiary The Ultimate Beneficiary refers to the Customer to whom the amount of the component is to be paid This field refers to field 59 is this now 59A of SWIFT You can make entries into this field only for a customer transfer MT 103 or MT 100 This would not be applicable for Bank Transfers only for Customer Transfers You can also select an ultimate beneficiary account from the option list provided Upon selection of the account the Account with Institution of the selected ultimate beneficiary will appear by default in the AWI field in the Parties 1 tab If no selection is made for AWI in the Parties tab 1 screen then all accounts of ultimate beneficiaries existing in the system will be appear for selection Country Specify the country of the ultimate beneficiary This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Note the following e The country information is captured to enable Mantas to analyse the transactions for possible money laundering activities For more details on Mantas refer Mantas interface document e When the SWIF
55. erparty type and specify the counterparty s address as well As a result you will need to identify the preferred Nostro Vostro accounts for that currency and BIC code combination Note the following e f you opt to generate receive notices for settlements made in all currencies involving all counterparties and transactions in all modules of Oracle FLEXCUBE an MT 210 will automatically be generated for any money settlement made by your branch e f you are defining settlement instructions for a customer related to the FT module you have to indicate the charge account which will be used as the default account for deducting all charges involved in processing the FT While processing an FT for the customer the appropriate charge account is picked up depending on the customer currency and branch processing the FT In addition you can maintain the details of the various intermediaries involved in payments and receipts The preferences maintained for an entity determine the manner in which money settlements are made on behalf of the entity Counter Party You can maintain settlement instructions for all the customers or for specific customers only From the option list select the specific customer number or choose the ALL option Module You can maintain different settlement instructions for different products If you choose Module as ALL then the Product must also be chosen as ALL If you choose a specific module for maint
56. g Branch Info BIC Code Branch Code Unique GB100068 APAC BANK LONDON APACGBE1 XXX APACE NL100072 BLACKROCK NETHERLANDS B V EINDHOVEN BLNENL21 XXX BLNEN NL100073 CITIBANK INTERNATIONAL AMSTERDAM CITINL2 KAR CITINL NL100074 ING INVESTMENT MANAGEMENT NETHERLANDS N V 5 GRAYENHAGE INGONL21 XXX INGON GB100075 DEUTSCHE BANK TRUST COMPANY LONDON BKTIGB2L XXX BKTIGE GB100076 BANK OF YOKOHAMA LTD LONDON HAMAGB21 XXX HAMA GB100077 DB UK BANK LIMITED LONDON MGCOGB2L XXX MGCOr GB100076 BANCA MONTE DEI PASCHI DI SIENA LONDON PASCGB2L XXX PASCE GB110080 Chase Bank LONDON CHASGB2L XXX CHASE JP100100 BANK Futura JAPAN APACJP61 ZCD APAC BH100101 BANK Futuraa BAHRAIN APACBH61 TCD APACE E5067569 BULGARIAN NATIONAL BANK SOFIA BNBGBGSF XXX BNBGE ESO67570 ABN AMRO BANK NY ZURICH ABNACHZS XXX ABNAC ESO6757 1 ALPHA BANK CYPRUS LIMITED NICOSIA LEFKOSIA ABKLCY2N XXX ABKLC ESO6 572 UNICREDIT BANK CZECH REPUBLIC 4 5 PRAGUE BACKCZPP XXX BACHE E E You can invoke the BICpluslban Maintenance screen by typing ISDIBANP in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Bicplusiban Maintenance Web Page Dialog Unique Details IBAN Details Unique key for Record IBAN BIC Code institution Name IBAN Branch Code Routing BIC Code Routing Branch Code Country Details Unique BIC Code Cty Heading Unique Branch Code Branch into Courtry Code Parert Bank Code National ID Unique National ID
57. have to capture data in the Account With Institution field and leave the Receiver Correspondent field blank Consequently the accompanying MT202 shall contain fields 54 and 57 depending on the availability of data in Receiver Correspondent and Account With Institution fields respectively The information pertaining to fields 20 Sending Bank s TRN 21 Related Reference 32a Amount Collected 33A Proceeds Remitted is picked up from the contract details screen 2 12 Payment Message Generation for MT300 320 In Oracle FLEXCUBE a new parameter CSTB_ PARAM is introduced The account number indicated in the party identification fields 56a and 57a of the MT 300 320 330 are serviced and not owned by the party indicated in the same field If the value of this parameter is Y and if the account lines of fields 56 amp 57 do not have sort codes then e The account number in field 58 is populated in the account line of field 57 e The account number in field 57 is populated in the account line of field 56 2 12 1 Processing for Incoming MT300 320 Based on the value of the parameter CSTB_ PARAM the incoming message processing will fetch the account number for pay and receive If the parameter value is Y the account number is fetched from field 56 instead of field 57 Otherwise the account number of pay and receive will be fetched from field 57 2 60 ORACLE 2 13 MT 756 Advice of Reimbursement or Payment The recei
58. he Ordering Institution e The branch or city of the Ordering Institution e The Name and address of the Bank Country Specify the country of the ordering institution This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Ordering Customer The Ordering Customer refers to the customer ordering the transfer Here you can enter the name and address or the account number of the Customer ordering the transaction This field corresponds to field 50 of SWIFT You will be allowed to enter details in this field only if you have initiated a customer transfer MT 103 and MT 102 In case of an MT 910 a credit confirmation message the first line should contain number 1 in option F of field 50 Country Specify the country of the ordering customer This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one 2 37 ORACLE Beneficiary Institution Here you can enter details of the institution in favor of which the payment is made It Is in reality the bank which services the account of the Ultimate Beneficiary This is applicable only in the case of bank transfers and not for customer transfers This field corresponds to field 58a of SWIFT You will be allowed to make entries into this field only for Bank Transfers when the remitter and beneficiary of the transfer are financial institutions MT 202 Here you can ent
59. ion Bank Wentifer Length IBAN Country Code Lenght Branch Wenitier Postig BAN Check Digte Poston Branch idenbiter Lergh BAN Check Digis Length 2 Acoount Humber Position BAN National id Length Account Number Length BAH Tatal Lenght input By SS TEM Date Time Tao Mogdiicalian rumber 1 EJ pen Authorized Ey SYSTEM Date Time RRO H suthorized Here you can specify the details of the following IBAN Country Code Specify the ISO country code prefix in the IBAN IBAN Country Position Specify the position of the country code in IBAN IBAN Country Code Length Specify the number of characters of the country code in the IBAN 2 7 ORACLE IBAN Check Digits Position Specify the start position of check digits in the IBAN IBAN Check Digits Length Enter the Number of check digits in the IBAN Bank Identifier Position Enter the Start position of bank identifier in the IBAN Bank Identifier Length Specify the Number of characters of bank identifier in the IBAN Branch Identifier Position Specify the Start position of the branch identifier in the IBAN value is empty if the branch identifier is not applied in the country s IBAN format Branch Identifier Length Specify the Number of characters of the branch identifier in the IBAN value is 0 if the branch identifier is not applied in the country s BAN format IBAN National ID Length Specify the Number of significant characters of the National ID value that are used by SWIFT to pop
60. k participant If the above conditions are satisfied the RTGS Network will be updated and the system will check RTGS Payments check box 2 34 ORACLE 2 6 3 Capturing Party Details When you settle a contract funds may have to pass through a series of banks before it actually reaches the Ultimate Beneficiary In the Parties screen you can capture details of all parties involved in a contract Settlement Details Web Page Dialog E Reference Number Component Account Details Message Details Parties Parties Cover Parties Other Details Clearing Details Local Clearing Intermediary 3 5 an Intermediary 1 Intermediary Reimbursement Institution i Reimburse Institution 1 Intermediary 2 Reimburse Institution 2 Intermediary 3 Reimburse Institution 3 Intermediary 4 Reimburse Institution 4 Intermediary 5 Reimburse Institution 5 Receiver Correspondent Account With Institution Correspondent 1 Account with Institution 1 Correspondent 2 Account with Institution 2 Correspondent 3 Account with Institution 3 Correspondent 4 Account with Institution 4 Correspondent 5 Account with Institution 5 Receiver of Cover Receiver 2 6 3 1 Parties These screens contain fields that can capture details of all the possible parties through whom the funds involved in a contract can pass Depending on the type of contract you are processing and the number of banks involved you should enter details in these screens Intermediary Reimbursement Insti
61. lag as Y Account No Select the relevant account number of the customer from the available options In the list you will find only those Account numbers maintained for the receiver BIC and the Account in customer BIC maintenance 2 68 ORACLE Message Select the message requested by the customer here Currency Indicate the preferred currency of the customer Floor Limit Indicate the debit D and credit C floor limits of the customer here On save and authorization of the Maintenance system generates the outgoing SWIFT message namely MT920 If you click Message button the system will display the outgoing MT920 message separately 2 8 2 Processing of Incoming 920 When the incoming message is MT920 and the requested message is 940 customer account statement message the system sends back the SWIFT Message MT940 with response When the incoming message is MT920 and the requested message is M1941 the system sends back the SWIFT Message M1941 with response When the incoming message is MT920 and the requested message is MT942 the system sends back the SWIFT Message MT942 with response When the incoming message is MT920 and the requested message is MT942 the system sends back the SWIFT Message MT950 with response Thus the system which uploads an MT920 message is also able to generate an outgoing MT940 MT941 or MT942 Swift Messages 2 69 ORACLE 3 Netting Payments across modules 3 1 In
62. latory Reporting Details You can select the Regulatory Reporting Details from the option list displaying the following values e BENEFRES e ORDERRES The chosen value will be inserted in Field 77B of the MT103 message Time Indicators Time Indication specifies one or several time indication s related to the processing of the payment instruction Select the time indication code from the following values available in the option list e CLSTIME Time by which funding payment must be credited with confirmation to the CLS Bank s account at the central bank expressed in CET 2 42 ORACLE e RNCTIME Time at which a TARGET payment has been credited at the receiving central bank expressed in CET e SNDTIME Time at which a TARGET payment has been debited at the sending central bank expressed in CET 2 7SWIFT messages handled by Oracle FLEXCUBE 2 7 1 The following table gives the SWIFT message types that will be generated for the various transfers that can be initiated through Oracle FLEXCUBE Payment Message MT 100 103 Sending a Fax copy of an MT 103 For outgoing transfers you have the option to generate a fax copy of a Payment Message MT 103 that is sent when the transfer is initiated INIT A fax copy of an MT 103 can be triggered for generation e Automatically when the MT 103 is generated e When a customer requests one The format and content of the fax will be similar to the corresponding SWIF
63. ld Field NEWT AMND depending on whether the contract is being booked or amended Common Reference Number according to the SWIFT validation rules Booking date of the contract Value Date of the contract Maturity Date of the contract Contract Currency and Contract Amount Next interest date in case of schedules else Maturity Date Currency and Interest amount Interest Rate Interest calculation basis in ICCF screen for interest C LENDING The information associated with the amount tag PRINCIPAL is defaulted from the Settlement Instructions screen 53A 53D Account holder of the settlement account 56A 56D Details entered in the intermediary field in the settlement instruction screen 57A 57D Details entered in the Account With Institution field in the Settlement Instruction screen 58A 58D Details entered in the Beneficiary Institution field in the Settlement Instruction screen BORROWING The information associated with the amount tag PRINCIPAL _LIQD is defaulted from the Settlement Instructions A O1 screen 53A 53D Account holder of the settlement account 56A 56D Details entered in the intermediary field in the settlement instruction screen 57A 57D Details entered in the Account With Institution field in the 2 57 ORACLE Message Field Tag Description ee Settlement Instruction screen 58A 58D Details entered in the Beneficiary Institution field in the Settlement Instruction screen 15D LENDING The informa
64. le to Head mapping sub screen of the Product Definition screen you would have mapped the Accounting Role ASSETGL to an actual internal leaf GL of your Chart of Accounts However you would not have maintained such a mapping for CUSTOMER since this is a role whose value gets defined at the contract level based on the counterparty involved in the contract While processing a contract you can modify the following information pertaining to Settlements e Account details details about the accounts involved in the contract or deal that have to be either debited or credited in your branch e Message details payment details whether settled by an instrument or a messaging service such as SWIFT e Party details details about the various parties banks involved in the transfer of funds to the Ultimate Beneficiary e Other Details the default values for fields in MT 103 messages for the contract Capturing Account Details In the Settlement Instructions screen you would have maintained the settlement accounts for an entity module currency and branch combination While processing a contract these details will be defaulted to the Settlement sub screen of the contract main screen You have the option of changing any or all of the settlement accounts while processing a contract ze Settlement Details Web Page Dialog Reference Number Component Account Details Message Details Parties Parties Cover Parties Other Details Clearing Detai
65. ll compute the transfer amount by subtracting the receiver s charges from the credit amount Receiver s charges will not be displayed in an outgoing MT 103 MT 100 Customer Transfer The MT100 which is a customer transfer message consists of 12 fields each having its own identity and field number This message type is sent by or on behalf of the financial institution of the ordering customer directly or through a correspondent s to the financial institution of the beneficiary customer Given below is a list of fields present in an MT 100 message type Message Field Tag Description Type M1100 20 Transaction Reference Number If the SWIFT SILVER parameter has been set to YES for your bank a unique reference number will be generated instead of the transaction reference number o ae Value Date Currency Code and Amount 50 Ordering This information you have maintained for the Ordering Customer Customer field in the Other Messages tab of the Settlements screen is defaulted here 52a Ordering This field gets populated depending on your entry in the Institution Ordering institution field If the transfer has originated from a different bank this field should contain the name of the Originating Bank If you do not need this field clear the data from this field cover is sent Else the BIC of the Nostro account is defaulted 54a Receivers This field gets populated based on your entry in the Correspondent Re
66. ls Local Clearing IBAN Account Number Settlement Details a Component Currency Branch Account Account Currency D C Exchange Rate RateCode Spread Definition Customer Spread ERI Currency ERI Amount E Ep Settlement Direction D Debit C Credit Component Description 2 29 ORACLE 2 6 1 1 Account Details The account details that get defaulted include the following e Component and its Currency e Payment Account and its Currency e Branch of your bank to which the account belongs Account Currency The currency of the account that you specified in the previous field will be defaulted here You will not have an option to change it Exchange Rate If the component currency is different from the account currency the system requires an exchange rate for the conversion The components of the final exchange rate used for conversion are e The Base Rate this is defaulted from the exchange rate that you have maintained for the currency pair involved It is computed as Mid Rate Spread depending on whether it is the Buy Spread or the Sell Spread e The Customer Spread the spread that you have maintained for the specified Counterparty Currency Pair and Tenor combination in the Customer Spread Maintenance screen is picked up and applied for the customer involved in the deal The final exchange rate Base Rate Customer Spread depending on whether it is a Buy or a Sell deal y If Customer Spread details for a spe
67. ls to the customer e The netting Suspense account into which the entries are to be posted during contract processing Example Assume you have entered into three separate FX MM and DV deals with Cavillieri and Barrett Finance Corporation the counterparty You bank has also signed a netting agreement with the counterparty whereby you have indicated that entries involving contracts for the counterparty should be netted 3 2 ORACLE As a result while posting the entries during contract processing the accounting function will replace the customer account with the netting suspense account and the entries will be posted as follows FX a CSA1 Cust Suspense Acct AssetGL b CSA1 Cust Suspense Acct The system will not generate payment messages for the three individual contracts However during the EOD BOD processing a single FT will be generated The payment message will be sent through this FT As a result of the FT Contract the following set of entries will be passed a c b the actual customer account The netted payment message will be generated Settlement Message Days maintained in the Currency Definition screen before the due date The Settlement Messages SGEN event will be triggered as usual but the individual payment messages will not be generated for counterparties with whom you have a netting agreement 3 1 2 1 Specifying Product restrictions for the Counterpart If you choose not to make the netting featur
68. ment By Message Ourselves Benificiary Shared Pay Parties Pay Parties Receiver Parties Cover Parties Clear Details Cover Detials Other Details Receivers Correspondent Sender To Receiver Information Account With Institution Receiver ERI Currency input By KANZ Authorized By KAN2 Date Time 7 3 2000 19 58 05 Modification Number 1 Date Time 7 3 2000 19 58 36 fv Open fv Authorized Receivers Correspondent This field corresponds to field 54a of S W I F T Enter the branch of the Receiver or another financial institution at which the funds will be made available to the Receiver You can enter any one of the following e ISO Bank Identifier Code of the bank e The branch of the Receiver s Correspondent e Name and address of the Receiver s Correspondent Country Specify the country of the branch of the receiver institution This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Sender to Receiver Information The sender to receiver information maintained in the settlement instructions can be defaulted in the field 72 in the confirmation messages The adjoining option lists displays the following values e e ACC Account with Institution e BNF Beneficiary e BUP Backup Payment e CHEQUE Pay only by cheque e CLSTIME CLS Time e INS Instructing Institution e INT Intermediary e MANPAY Mandated Payment
69. mount Tag SETBOTAMT 2 11 MT 400 Advice of Payment The receiver of the MT400 is the Remitting bank The details are captured in the Parties section of the Settlements screen If the Remitting bank is not a customer of your bank you can use the CIF ID assigned to the walk in customer You will also have to capture the SWIFT address of the remitting bank If the Remitting bank is not a customer of your bank and you have used the CIF ID assigned to the walk in customer you will have to change the media to SWIFT in the Advices FFT tab for generating the Collection Payment advice COLL_PAY_ADV 9 59 ORACLE If you choose not to send an MT 400 the message can be suppressed in the Advices FFT screen A MT100 and MT202 Cover can be send instead by choosing the Cover Required option in the Settlements Instruction screen Message Field Tag Description Type 53A D Sender s The receiver of MT202 The information captured in the set S Receiver field of the Settlement Instruction screen for the Correspondent Amount Tag BILL_LIQ_AMT is defaulted here This field is not populated if the receiver of MT400 is same as Our Correspondent 54A D and 57A D If you would like both field 54 and 57 to appear in the generated message you will have to capture the relevant data in the Receiver Correspondent and Account With Institution fields against the Amount Tag BILL_LIQ_ AMT If only field 54 is required in the SWIFT message you will
70. o analyse the transactions for possible money laundering activities For more details on Mantas refer Mantas interface document Receiver of Cover Specify the details of the Receiver of the cover message which can be any one of the following e ISO Bank Identifier Code of the bank e Branch of the Receiver e Name and address of the Receiver 2 36 ORACLE e Other identification codes for example account number Settlement Details Web Page Dialog Reference Number Component Account Details Message Details Parties Parties Cover Parties Other Details Clearing Details Local Clearing Ordering Institution Beneficiary Institution Ordering Institution 1 Beneficiary Institution 1 Ordering Institution 2 Beneficiary Institution 2 Ordering Institution 3 Beneficiary Institution 3 Ordering Institution 4 Beneficiary Institution 4 Ordering Institution 5 Beneficiary Institution 5 Ordering Customer Ultimate Beneficiary Ordering Customer 1 Ultimate Beneficiary 1 Ordering Customer 2 Ultimate Beneficiary 2 Ordering Customer 3 Ultimate Beneficiary 3 Ordering Customer 4 Ultimate Beneficiary 4 Ordering Customer 5 Ultimate Beneficiary 5 2 6 3 2 Parties Ordering Institution The Ordering Institution is the financial Institution which is acting on behalf of itself or a customer to initiate the transaction This field corresponds to 52a of SWIFT In this field you can enter one of the following e The ISO Bank Identifier Code of t
71. of the Receiver s Correspondent Country Specify the country of the receiver s correspondent This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Account with Institution An Account with Institution refers to the financial institution at which the ordering party requests the Beneficiary to be paid The Account with Institution may be a branch or affiliate of the Receiver or of the Intermediary or of the Beneficiary Institution or an entirely different financial institution This field corresponds to field 57a of SWIFT You can enter one of the following e ISO Bank Identifier Code of the bank e The branch of the Receiver s Correspondent e Name and address of the Receiver s Correspondent e Other identification codes for example account number If no selection is made for Account with Institution all beneficiaries will appear for selection in the option list for Ultimate Beneficiaries in the Parties tab 2 screens If a particular Ultimate Beneficiary is selected in Parties tab 2 then the Account with Institution for the selected ultimate beneficiary will appear by default in the AWI field in the Parties tab 1 screen Country Specify the country of the account with institution This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one The country information is captured to enable Mantas t
72. option if you would like to generate outgoing MT 103 messages in the MT 103 Format Enable the MT 103 option by checking the MT 103 Preferred box You will be allowed to choose the MT 103 option only if you have enabled the generation of MT 103 messages as Payment Messages Moreover you should also ensure that you have also enabled this option e For your bank branch in the Branch Parameters Maintenance e By choosing the Generate 103 option for currency in the Currency Definition e For the product used by the contract in the Product Preferences The other preferences that you need to specify for each BIC entity are as follows e CUG Member enable this option by checking the box positioned next to this field to indicate that the BIC entity is a Closed User Group member e Update During Upload 2 3 ORACLE 2 2 2 2 2 3 e Black Listed this indicates that the BIC entity is also black listed e Remit Member This indicates that the customer is registered with MT 103 Extended Remittance Information Multi User Group Multi Customer Credit Transfer This option is to indicate whether or not a Multi Credit Transfer Feature M1102 support exists between your bank and the BIC entity Maximum Size Indicate the maximum size in bytes agreed upon between the two parties for transmitting a MT102 message A null value in this field signifies that there is no limit set on the size of the message Whenever the queue e
73. ou can find answers to specific features and procedures in the Online Help which can be invoked by choosing Help Contents from the Help Menu of the software You can further obtain information specific to a particular field by placing the cursor on the relevant field and striking lt F1 gt on the keyboard 1 2 Audience This manual is intended for the following User User Roles Back office clerk Input functions for contracts Back office managers officers Authorization functions Product Managers Product definition and authorization End of day operators Processing during end of day beginning of day Financial Controller Product Managers Generation of reports 1 3 Organization This manual contains the following chapters Chapter 1 About this Manual gives information on the intended audience It also lists the various chapters covered in this User Manual Chapter 2 The Settlements Service details the procedure to set up Settlement details and the processing of Settlements It also lists the SWIFT messages handled by Oracle FLEXCUBE Chapter 3 Netting Payments Across Modules explains the process of netting transactions that have some common features Chapter 4 Annexure A File Formats lists out the upload file formats 1 4Conventions Used in this Manual Important information is preceded with the symbol 1 1 ORACLE 1 5 Glossary of Icons This User Manual may refer to all or some of the following icons
74. ou can invoke this screen by typing ISDNETNG in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 3 Netting Across Modules Detailed Web Page Dialog Netting Reference Number Customer Account Branch Amount Currency DebitCredit Value Date Contracts Under Netting T Contract Reference Number Event Sequence Number Amount Tag Settlement Amount Debit Crecit In this screen you will be able to view details of all Contracts Under Netting for the following parameters The Netting Reference Number The Customer involved in the transactions The Value Date of the transactions The netted amount The code of the branch in which the transactions were processed The currency of the transactions 3 6 ORACLE e The debit credit indicator indicating whether the amount was debited or credited to the Net Account Querying for details of the Netted contracts You will also be able to perform queries on the Netted Amount and the Netting Reference Number through the Netting Across Modules Summary screen s Netting Across Modules Summary Web Page Dialog Netting Reference Number Customer Branch a Account Currency EH Search Advanced Search Reset Records per page 15 z TT Of 1 TT Netting Reference Number Customer Branch Account Currency In this screen Double Click on the record to view details of the FT contract 37 ORACLE
75. party BGTOOOBGT Product Code ALL Counterparty Type for E Sequence Number Currency USD Relations Receive Branch Branch Account Account Currency Currency Payment By Message Payment By Pay Parties Pay Parties Receiver Parties Cover Parties Clear Details Cover Detials Other Details Intermediary Reimbursement Institution Intermediary I RTGS Payment RTGS Network Input By KAN2 Date Time 7 3 2 9 Modification Number 2 iv Open Authorized By KAN2 Date Time 7 3 21 6 iv Authorized 3 5 I Cover Required Cover By v Charges Details Ourselves Benificiary Shared ORACLE You will have to maintain a set of instructions for the Netting NT module While sending the payment message for the netted FT the default settlement route that you have maintained for the parties involved in this module will be used Refer section Capturing Settlement Preferences for a Customer for explanation on Settlement Instruction Screen 3 2 Generating the netted FT You can generate the netted FT at any time of the day by executing a batch program The Netting Across Modules program is available under the Batch Program option in the Application Browser Upon executing this program successfully you will be intimated with the following message Netting across Modules Successful 3 2 1 Viewing details of Netted Contracts You can view details of netted contracts through the Netting Across Modules Detailed screen Y
76. pe e City e Location e Country Name e New BIC e New Branch Code e Modification The BIC Code Summary screen operates as an upload table The data is entered into Oracle FLEXCUBE using these tables BICPlusIBAN support Oracle FLEXCUBE supports the Upload of BICPlusIBAN directory BICPlusIBAN is a SWIFT directory that lists institution identifiers recognized by the financial industry for example Bank Identifier Codes CHIPS UIDs national clearing codes and IBAN related information It also provides name and addresses of the corresponding entities BICPlusIBAN is used to identify correspondents and counterparties accurately and to allocate the correct code when sending messages thus improving Straight Through Processing STP Initiators of cross border payments within Europe are required to submit the BIC and IBAN codes to the receiver in order to benefit from reduced payment transaction charges ORACLE 2 5 You can invoke the BIC Iban Maintenance Summary screen by typing ISSIBANP in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button E Bicplusiban Maintenance Summary Web Page Dialog Unique key for Record Institution Name BIC Code Branch Code IBAN BIC Code IBAN Branch Code Routing BIC Code Lid Routing Branch Code Search Advanced Search Reset Records perpage 15 v Like of 7 KALI Go to Page Unique key for Record Institution Name City Headin
77. pulates the SWIFT BIC directory and the clearing codes automatically 2 2 5 1 IS File Upload This file forms the part of the BICPlusIBAN package This contains information about the IBAN structure applicable in the countries IS File forms are stored in a new data store and are used for IBAN structure validations Invoke the BIC Upload screen by typing ISDBICPU in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button BIC Upload Web Page Dialog Source Code x v File Name BIC File Path CCH File Intraday Sequence Number BICPLUSIBAN BICIPLUSIBANIS Submit Params Cancel Here you can specify the following details 2 9 ORACLE 2 2 6 Source Code Specify the source from which you want to upload details You can select the appropriate source code from the drop down list displaying the following values e BIC Select this to upload the BIC file e CCH Select this to upload the country wise holiday file e BICPLUSIBAN e BICPLUSIBANIS File Path State the path in the database server where the uploaded file should be stored File Name Specify a name for the uploaded file The file name should bear the extension DAT Click Submit Params button and Submit Batch button to start the upload process The file formats of these records are explained in the chapter titled Annexure A File Formats Refer this chapter fo
78. r further details Operations on a BIC record On an existing BIC code record you can perform any of the following operations if a function under the Actions Menu is disabled it means that the function is not allowed for the record Apart from defining a new BIC code record you can perform any of the following operations on an existing record if any function under the Actions Menu is disabled it means that the function is not allowed e Amend the details of a record e Authorize a record e Copy the details of the record e Close the record e Reopen the record e Delete the details of a record Refer to the User Manual on Common Procedures for details of these operations lt is assumed that the upload source contains details of all relevant BIC codes The BIC records that are uploaded to Oracle FLEXCUBE should contain the following tags e U If records do not exist in the Oracle FLEXCUBE BIC directory the same would be inserted For a record that already exists it will be updated with that of the BIC upload e M If there is no existing record in the Oracle FLEXCUBE BIC directory the same would be inserted Otherwise the record will be updated with the one in the BIC upload e A Foran existing record in the Oracle FLEXCUBE BIC directory an error will be logged and the upload will continue If no records exist then a new record will be updated with the one in the BIC upload e D If there is no existing record in the Oracle
79. ransfer and RTGS incoming Nostro in case of outgoing Direct Debit transfer then the system will check this check box as per the validations done in RTGS Network You cannot change this value RTGS Network If in a RTGS Network the accounts are maintained as Pay account or Receiver Account while saving the settlement instruction then a set of validations will be performed as mentioned below For Pay message system will validate whether the intermediary if intermediary is not present the Account with Institution AWI will be validated and if the AWI is also not present then receiver will be validated is a RTGS participant For Pay Cover message system will validate if the receiver correspondent is a RTGS network participant If the above conditions are satisfied the RTGS Network will be updated and the system will check RTGS Payments check box Receiver s Correspondent The Receiver s Correspondent is the branch of the Receiver or another financial institution at which the funds will be made available to the Receiver 2 18 ORACLE 3 Settlement Instructions Maintenance Branch BGT Counterparty BGTOOOBGT Counterparty Type cir 7 Web Page Dialog Module AL Product Code ALL Sequence Number Currency GBP Relations Receive Branch BGT Account bat004 Branch BGT Account bgt003 Currency GBP I Cover Required Cover By z Currency GBP Charges Details Payment By Wessaqe Pay
80. rency transactions for which the payment instructions are to be generated through the Payments module you can specify the following settlement details e Whether the payment is to be effected through messaging or via the local clearing network e Whether a cover is required for the payment e Whether the cover must be available through messaging or through the local clearing network Beneficiary Institution for Cover This field corresponds to field 58a of S W I F T Enter details of the institution in favor of which the payment is made It is in reality the bank which services the account of the ultimate beneficiary You will be allowed to make entries into this field only for Bank transfers MT 200 or MT 202 In this field you can enter either the e The ISO Bank Identifier Code of the Beneficiary Institution e The Name and Address of the Beneficiary Institution Country Specify the country of the beneficiary institution for cover This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one 2 39 ORACLE The country information is captured to enable Mantas to analyse the transactions for possible money laundering activities For more details on Mantas refer Mantas interface document 3 If you have already maintained this information in the Settlement Instructions Maintenance screen then it will be picked up and reflected here You can specify these details in the
81. ruction code that will be inserted in Field 23E of the MT103 message The options available are CHQB TELE PHON PHOI REPA INTC TELI SDVA PHOB TELB HOLD CORT and BONL 2 26 ORACLE Instruction Code Description You can specify the additional information if any which would be inserted to qualify the Instruction Code in Field 23E of the MT103 message The instruction code description can only be maintained for the instruction codes PHON PHOB PHOI TELE TELB TELI HOLD or REPA For instance if the Instruction Code is REPA and the description is Repayment then the text REPA Repayment is inserted in Field 23E Transaction Type You can indicate the Transaction Type that will be inserted in Field 26T of the MT103 message Regulatory Reporting Details You can indicate the Regulatory Reporting Details that will be inserted in Field 77B of the MT103 message Charges Details You can indicate whether charges for the message are to be borne by the bank ourselves or the beneficiary or will be shared You can specify this in the Charges Details section in the main Settlement Instructions screen This information is inserted in Field 71A of the MT103 message 2 5 The Sequence in which Settlement Instructions are resolved While processing contracts in Oracle FLEXCUBE the settlement instructions maintained are resolved in the following sequence tv comer ccv moaie Ban ecomomy x voo a ecomomy x ak aL p
82. ructions screen 2 8 MT 102 Consolidated Customer Transfer with Cover During Close operation of a consolidation if the PAYMENT MESSAGE is linked as an advice to the INIT event for the PC product then the following two message types are created e CONS _CUST_TRANS This would represent consolidated customer transfer i e MT102 e CONS COVER This would represent consolidated cover message generated for MT 102 The MT102 would consists of three sequences e Sequence A This contains General Information and is a single occurrence sequence and contains information which applies to all individual transactions described in sequence B e Sequence B This contains Transaction Details in a repetitive sequence Each occurrence is used to provide details of one individual transaction e Sequence C This contains the Settlement Details and is a single occurrence sequence and contains information about the settlement Mandatory Sequence A General Information File Reference Accounting Entry Ref 23 M Bank Operation Bank Operation Code Code 50a O Ordering This field would be filled up only if the Ordering Customer for all the Customer A underlying FT Contracts is same For outgoing MT102 the first line 2 47 ORACLE Mandatory Sequence A General Information Ls eee eee 52a Ordering This field would be filled up only if the Ordering Institution for all the Institution A underlying FT Contracts is same or
83. s Physical address Physical address Physical address Location Location Location Country name Country name POB Number POB Location POB Location POB Location POB Country name POB Country Length D 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 Type VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 T N Mandatory Y Y N N N N N N N N N N N N N N N N N A subtype can be bank broker etc 20 x 3 char Fields indicating the Value added Service Code Specific information Physical address first part Physical address second part Physical address third part Physical address fourth part Country name second part Post Office Box number POB Location first part POB Location second part POB Location third part POB Country name first part POB Country name ORACLE ee e AM record The AM record would consist of only the tag identifier old BIC and the new BIC The file format is as follows 4 3 ORACLE ORACLE Settlements January 2010 Version 11 0 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores CA 94065 U S A Worldwide Inquiries Phone 1 6
84. s Cover Parties Clear Details Cover Detials Other Details External Counterparty Pay Details External Counterparty Receive details Bank Code Bank Code Account Account Name Name Clearing Network Bank Name Bank Name Input By KAN2 Date Time 7 3 2000 19 58 05 Modification Number 1 Iv Open Authorized By KAN2 Date Time 7 3 2000 19 58 36 Ed Authorized For the counterparty details you can specify the bank code account and account name External Counterparty Pay Details The description of the selected bank where the external counterparty account resides is displayed here External Counterparty Receive Details The description of the selected bank where the external counterparty account resides is displayed here If you indicate cover for payment via the local clearing network you must specify the account details of the cover party in the Cover Details tab in the Settlement Instructions Maintenance screen 2 24 ORACLE ze Settlement Instructions Maintenance Web Page Dialog Branch BGT Module AL Counterparty BGTOOOBGT Product Code ALL Counterparty Type CIF Sequence Number Currency GBP Relations Receive Branch BGT Branch BGT F Cover Required Account bgt003 Account bgt004 Cover By X Currency GBP Currency GBP Charges Details Payment By Message Payment By Message Ourselves Benificiary Shared Pay Parties Pay Parties Receiver Parties Cover Parties Clear Details Cover
85. sen wr Messe ef C e A von aoe ae Related Reference 721 494931 DEV Field 20 of MT 103 Value date Currency code 32A 020426NLG100000 Amount Beneficiary Institution 58 CITIBKINMUO Field 57a of SWIFT The bank is Citibank Mumbai End of message text trailer Example Ill MT 200 You Bank Austria Vienna order Citibank NY to transfer NLG 1 Million from your Nostro account with them to your Nostro account with HDFC bank Mumbai An Intermediary can be involved in this transfer if Citibank NY requests Citibank Mumbai to transfer the funds to HDFC Mumbai In this case Citibank Mumbai will be the Intermediary Example IV MT 202 In the example for MT 200 if you involve an Intermediary field 56a of SWIFT then a cover MT 202 will be sent to Citibank Mumbai Example V Notice to Receive MT 210 As a result of a Foreign Exchange deal with HDFC Mumbai you at Bank Austria Vienna are expecting to receive 1 Million USD to be credited to your account with Citibank NY Notice To Receive MT210 2 63 ORACLE Field In Oracle Corresponding Field in Entry FLEXCUBE SWIFT Ordering Institution Field 52a of SWIFT HDFC Mumbai Intermediary Field 56a of SWIFT Citibank Mumbai Details of Payment Field 70 of SWIFT A message that you want to send The Notice to Receive MT 210 will be sent from Bank Austria Vienna to Citibank New York Example VI Debit Advice MT 900 An MT 900 is a debit advice It is
86. settlement has RTGS cover required enabled ad if the network level flag does not allow new COV format then the system uses following message format 2 54 ORACLE gt COVER_RTGS old RTGS cover format 2 7 7 2 Processing Incoming MT202 COV MT205 COV Messages FT products with the transfer type as CustomerTransferCover will be used to handle the incoming SWIFT messages The cover message format to be used during message generation is derived as follows e If transfer type is CustomerTransferCover and country codes of sender and receiver are same and if the receiver currency allows new COV format then the system uses following message format gt CUST _COVERL MT205COV e If transfer type is CustomerTransferCover and country codes of sender and receiver are same and if the receiver currency does not allow new COV format then the system uses following message format gt COVERL MT205 old cover format If transfer type is CustomerTransferCover and currency of sender and receiver are not same and if the receiver currency allows new COV format then the system uses following message format gt CUST_COVER MT202COV If transfer type is CustomerTransferCover and currency of sender and receiver are not same and if the receiver currency does not allow new COV format then the system uses following message format gt COVER MT202 old cover format If transfer type is CustomerTransferCover
87. stem here The source codes of all external systems are available in the option list provided from where you can make the appropriate selection You may use the Source Code Oracle FLEXCUBE to maintain settlement modes for transactions originating in Oracle FLEXCUBE Module You have to specify the module of the transactions that have to be settled using different modes The value of this field is defaulted to CL Consumer Lending You cannot modify this value Product Here you have to indicate the product of the transactions that have to be settled using different modes The option list will display the different products available under the selected module You may also use the wild character as the product code The system will use this information if settlement mode maintenance is not available for a product under the selected module Currency You have to specify the currency of the transactions that have to be settled using different modes You may also use the wild character for a currency This will be used if maintenance for a specific currency is not available 9 12 ORACLE For the above combination of Source Module Product and Currency you can maintain multiple settlement modes and the associated details given below Setl Mode For the selected combination you have to specify the settlement mode The list of available modes is predefined in the system and you can select a mode from the drop down lis
88. t Event 2 58 ORACLE Message Field Tag Description Type oa date for all other events 30V Value Date Bought Value Date 32B Bought The information pertaining to these fields is picked up from Currency Amount the settlement detailed maintained for the Amount Tag SETBOTAMT 53a Delivery The details entered in the Receiver s Correspondent field in Agent the settlement Instructions screen are defaulted here 56a intermediary The details entered in the Intermediary field in the Settlement Instructions screen 57a Receiving Details entered in the Account With Institution field in the Agent Settlement Instructions screen If the data is not available then the field will be populated with UNKNOWN according to the SWIFT requirements 33B Sold The information pertaining to these fields is picked up from Currency and Sold the settlement detailed maintained for the Amount Tag Amount SETSOLDAMT 53 Delivery Agent The delivery agent is the account holder of the settlement account for SETSOLDAMT 56 The details entered in the intermediary field in the settlement instructions screen 57a Receiving The details entered in the Account With Institution field in Agent the Settlement Instructions screen If the data is not available then the field will be populated with UNKNOWN according to the SWIFT requirements 58 The details entered in the Beneficiary Institution field in Settlement Instructions for the A
89. t Since CL is the module used for the multimode settlement the different modes available are e CASA e Cash Teller e Instrument e External Account e Electronic Pay Order e Internal Cheque e Clearing e Debit Card e Credit Card Pay Setl Ac For the selected settlement mode you have to specify the Suspense Control GL into which the transactions that satisfy the selected combination need to pass the accounting entry This GL will be used only when the bank is making a payment The settlement account gets credited in this case Pay Setl Prod For the selected settlement mode if the originating transaction results in a linked transaction you need to specify the product that should be used to create the linked transaction This product will be used when the settlement account gets credited For example if the settlement mode is DD you have to specify the product code i e the DD instrument type for creating the corresponding instrument transaction in Oracle FLEXCUBE Recv Setl Ac Just as you specify the pay settlement account for the mode selected you also have to indicate the Suspense Control GL into which transactions that satisfy the selected combination need to pass the accounting entry when the bank receives a payment The selected account gets debited in this case Recv Setl Prod If the originating transaction payment received results in a linked transaction you have to specify the product to be used
90. t for each contract involving the counterparty You can do so by enabling the Netting option in the Settlements sub screen of the Contract Online screen while processing contracts involving the customer 3 4 ORACLE 3 1 4 E Settlement Details Web Page Dialog Reference Number Component Account Details Message Details Parties Parties Cover Parties Other Details Clearing Details Local Clearing IBAN Account Number Settlement Details O Component Currency Branch Account Account Currency D C Exchange Rate Rate Code Spread Definition Customer Spread ERI Currency ERI Amount E Mf Settlement Direction D Debit C Credit Component Description Signature Yerification The various components Amount Tags of the transaction like commission interest tax charges etc will be displayed in this screen Ensure that you enable this option for each component of the transaction Refer section Account Details of Capturing Account Details for explanation on Settlement Details Screen Maintenance pertaining to the Route for settling payments You can maintain the settlement preferences of a customer or a bank in the Settlement Instructions Maintenance screen You can invoke this screen by typing ISDINSTR in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 2 Settlement Instructions Maintenance Web Page Dialog Branch BGT Module AL Counter
91. t modes can be e Cash e Instruments e External Accounts e Pay Orders e Internal Cheque e Clearing e Debit Card e Credit Card You can also make settlements using a combination of any of the modes mentioned above i e part by cash part by cheque and the rest by credit card or any other combination of your choice You can capture the different modes of settlement through the Multimode Settlement Maintenance screen You can invoke this screen by typing ISDSRCMD in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button The modes are captured for a Source Module Product and Currency combination 2 11 ORACLE E Multimode Settlement Maintenance Web Page Dialog Source ACUMEM Module Code Lb Product Currency Coc Source Mode Detail F E Settlement Mode Select Pay Settlement Account Select Pay Settlement Product Select Recieve Settlement Account Select Recieve l Fields Input By SARINA Date Time a2000 15 55 56 Modification Number 1 g Open Authorized By Date Time I Authorized The following details have to be captured in this screen Source Oracle FLEXCUBE interfaces with other external systems of your bank Transactions originating in external systems may require to be uploaded into Oracle FLEXCUBE for further processing For maintaining the settlement modes for such transactions you have to indicate the source code of the external sy
92. tails of a new bank code select New from the Actions Menu in the Application toolbar or click new icon Z BIC Code Details Web Page Dialog Bank Identification Code Bank Name Customer Number Bank Address Bank Address2 Bank Address3 SVVIFT Key Telex Key SVVIFT Key Arrangement Relations Sub Type Code BEI Indicator Payment Message MT103 Preferred Remit Member Black listed Update during upload Cug Member Multi Customer Credit Transfer Multi Customer Credit Generate 102 Fields Transfer Input By Date Time Modification Number WB authorized Authorized By Date Time WB open BIC codes can be maintained manually or uploaded from an external source onto Oracle FLEXCUBE 2 1 ORACLE 2 2 1 Specifying BIC Code details BIC Code You need to indicate the code by which the bank is identified by SWIFT On indicating the Bank Identifier Code you should indicate the detailed name of the bank If the bank is a customer of your bank you can select the CIF ID assigned to the bank from the option list Once you select the CIF ID the name of the bank will be displayed in the Bank Name field If the bank is not a customer of your bank you will have to manually enter the name and address of the bank The country information is captured to enable Mantas to analyse the transactions for possible money laundering activities For more details on Mantas refer Mantas interface document Relationship You have
93. taining a netting agreement for each counterparty you have to specify whether or not the contract is under the netting agreement for each contract involving the counterparty Check this box to indicate that you would like to enable the Netting option for the various components Amount Tags involved in the transaction These components could be commission interest tax charges etc Cross currency Settlements of FX deals Oracle FLEXCUBE allows cross currency settlements of foreign exchange deals that involve an In currency You can settle the In currency leg in another In currency or in Euro Example Assume you enter into the following foreign exchange deal You sell 100 000 FRF against USD The scenario e You specify the exchange rate 1 USD 5 2 FRF e The bought amount is therefore 19230 769 USD e The settlement account is in EUR e The exchange rate between EUR FRF 1 EUR 6 475 FRF Since FRF is an In currency you can settle the sell leg of the deal through EUR in this example The settlement amount would be EUR 15444 015 Suppressing Settlement Messages Settlement messages defined for components that fall due will be generated automatically when the settlement actually happens for the respective component You can suppress the generation of the settlement message defined for a component by clearing the check box in the Gen Message field If a component is to paid the credit account
94. the institution from which sender received the funds This is applicable only if the institution is different from the ordering institution The information pertaining to fields 20 Sending Bank s TRN 21 Presenting Bank s Reference 32B Total Amount Claimed 33A Amount Reimbursed or Paid is picked up from the contract details screen 2 7 14 MT 012 ACK Status Acknowledgement In PC contract online is provided with ACK Status having values e P Pending e A ACK e N NAK 2 61 ORACLE After message dispatch the ACK status is updated to Pending Subsequently during processing of MT012 status changed to ACK ad ACK Status is updated in Transaction online and Transaction Summary screen also Incoming Swift Upload process support MT012 would contain either e Reference number PC Contract e DCN of the outgoing message that was generated Reference number present in field 108 of MT012 is searched first in PC Contract and upon receiving MT012 the ACK_STATUS of the record is marked to ACK In case of the record not getting updated in the Contract Master the message table is queried for DCN in field 108 to obtain the reference no of the corresponding PC Contract and the ACK_STATUS is marked as ACK 2 7 15 MT 019 NAK Status Acknowledgement After message dispatch the ACK status is NAK during processing of MT019 changing the status to NAK Subsequently NAK Status is updated in Transaction online
95. tion It could be either e Remitter All Charges e Beneficiary All Charges e Remitter Our Charges Clearing Network Cover details for local clearing will capture Clearing Network This clearing network will be defaulted during Contract Input and be used subsequently for PC Product resolution while generating a PC contract 2 6 2 2 Message details For a SWIFT message you should specify e Whether a Cover has to be sent to the Reimbursement Bank along with the payment message to the receiver e Bank to bank payment details these can be in the form of instructions or additional information to any of the parties involved in the contract e Any Sender to Receiver information Sender to Receiver Information This could be instructions or additional information for the Receiver Intermediary Account With Institution or Beneficiary Institution This field corresponds to field 72 of the S W I F T message The format of the message depends on the type of S W I F T message that is generated Refer to the S W I F T manual for details on the format of the message and the code words to be used Details of Payment Here you can specify information from the Ordering Party to the Beneficiary Customer about the reason for the payment This field can contain reference numbers invoice numbers or any other details which will enable the Beneficiary to identify the transaction This information is to be passed through the payment
96. tion associated with the amount tag PRINCIPAL _LIQD is defaulted from the Settlement Instructions screen 53A 53D The details entered in the Receiver s Correspondent field are defaulted in this field 56A 56D Details entered in the Intermediary field in the Settlement Instructions screen are defaulted in this field 57A 57D Details entered in the Account With Institution field in the Settlement Instruction screen are defaulted here Type BORROWING The information associated with the amount tag PRINCIPAL is defaulted from the Settlement Instructions screen 53A 53D Details entered in the Receiver s Correspondent field in the Settlement Instructions screen are defaulted here 56A 56D Details entered in the Intermediary field of the Settlement Instructions screen are defaulted here 57A 57D Details entered in the Account With Institution field in the Settlement Instruction screen are defaulted here 58A 58D Details entered in the Beneficiary Institution field in the Settlement Instruction screen 2 7 10 MT 300 Foreign Exchange Confirmation Message Field Tag Description Type 22A Scope of NEWT AMND depending on Contract booking or Operation Amendment 58A 58D Details entered in the Beneficiary Institution field in the Settlement Instruction screen are defaulted here 22C Common Common Reference Number according to the SWIFT Reference validation rules a 30T Trade Date Booking date for the Contract Booking NEWT even
97. to create the linked transaction This product will be used when the settlement account gets debited For instance if the settlement mode is External Cheque you have to specify the clearing product to be used for creating the clearing transaction For details on multi mode settlement processing refer the heading titled Processing settlements in this chapter 2 4 Capturing Settlement Preferences for a Customer You can maintain the settlement preferences of a customer or a bank in the Settlement Instructions Maintenance screen You can invoke this screen by typing ISDINSTR in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button ze Settlement Instructions Maintenance Web Page Dialog Branch BGT Module AL Counterparty BGTOOOBGT Product Code ALL Counterparty Type c IF z Sequence Number Currency GBP Relations Receive Branch BGT Branch BGT Cover Required Account bgt003 Account bgt004 Cover By A Currency GBP Currency GBP Charges Details Payment By Message Payment By Message Ourselves Benificiary Shared Pay Parties Pay Parties Receiver Parties Cover Parties Clear Details Cover Detials Other Details Intermediary Reimbursement Institution Intermediary I RTGS Payment RTGS Network Input By KAN2 Date Time 7 3 2000 19 58 05 Modification Number 1 Iv Open Authorized By KAN2 Date Time 7 3 2000 19 58 36 E Authorized Indicating preferences
98. top right corner of the Application tool bar and clicking the adjoining arrow button 3 1 ORACLE E Netting Agreement Maintenance Web Page Dialog Customer Number 4 4410001 Agreement Reference Number REFO1 Met Agreements Product Restriction Agreement Details Agreement Start Date 14 2007 Product Outgoing Bank FOBT Agreement End Date 14 2008 Netting Agreement 423501054 Agreement Details Pay Details Fields Input By SANT Date Time 14 2007 23 11 11 Modification Number 1 gi Open Authorized By SANT Date Time 14 200 23 12 45 E Authorized These details will be used to net all deals that you enter into with the counterparty Customer Number You must identify the CIF ID assigned to the Counterparty for whom you are maintaining the netting agreement details When you choose to net contracts at the beginning of the day all contracts specified for netting will be netted for every customer for whom you have maintained netting details Agreement Reference Number Each netting agreement record that you maintain should be identified with a unique reference number in Oracle FLEXCUBE You can specify a unique number to identify each agreement Indicating the details of the Agreement As part of specifying the details of the agreement you will have to capture the following information e The period for which the netting agreement is valid e The Outgoing FT product which is to be used to send the payment detai
99. troduction 3 1 1 Oracle FLEXCUBE allows you to net contracts pertaining to different modules provided they Satisfy certain conditions The Netting facility is useful at the time of contract settlement You can opt to net two or more contracts at the time of settlement if the contracts are e Linked to the same counterparty customer e Have the same Value Date e If your bank has signed a netting agreement with the counterparty Thus if four contracts for a given counterparty settle on the same day and if your bank has signed a netting agreement with the counterparty then instead of four separate payment messages a single payment message will be sent to the counterparty Maintenance required for Netting Payments in Oracle FLEXCUBE To net entries pertaining to deals involving a specific counterparty in Oracle FLEXCUBE requires certain basic information to be maintained The information that needs to be captured includes the following e Capturing the netting agreement related details e Maintaining netting related information at the contract level e Maintenance pertaining to the Route for settling payments e Maintenance required for FT upload Capturing the Agreement related details To net deals in Oracle FLEXCUBE you must enter into a netting agreement with the concerned counterparty You can do this through the Netting Agreement Maintenance screen You can invoke this screen by typing STDNTMNT in the field at the
100. tution An Intermediary Reimbursement Institution is the financial institution between the Sender s Correspondent and the Receiver s Correspondent through which the reimbursement of the funds will take place Country Specify the country of the intermediary reimbursement institution This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Intermediary The Intermediary in a contract refers to the financial institution between the Receiver and the Account with Institution through which the funds must pass The Intermediary may be a branch or affiliate of the Receiver or the Account With Institution or an entirely different financial institution This field corresponds to field 56a of SWIFT Here you can enter either the e ISO Bank Identifier Code of the bank 2 35 ORACLE e Name and address of the Bank Country Specify the country of the intermediary institution This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Receiver s Correspondent The Receiver s Correspondent is the branch of the Receiver or another financial institution at which the funds will be made available to the Receiver This field corresponds to field 54a of SWIFT You can enter one of the following e ISO Bank Identifier Code of the bank e The branch of the Receiver s Correspondent e Name and address
101. ulate the IBAN NATIONAL ID and that are sufficient to derive the IBAN BIC correctly This number can be different from that is smaller than the length of the national bank branch identifier defined in the IBAN Registry Note that as SWIFT refines its IBAN to BIC translation algorithms this number may change from release to release Account Number Position Specify the Start position of the account number in IBAN Account Number Length Specify the Number of characters of account number in IBAN IBAN Total Length Specify the total number of characters of the IBAN 2 8 ORACLE 2 2 9 Uploading BIC files SWIFT allows you to upload the entire BIC file or individual records like Amendments AM and File Instructions Fl record files within the BIC upload file on to the BIC directory You can perform this through the BIC Upload screen The BICPlusIBAN directory consists of the following files e BI file BICPlusIBAN Information e IS file IBAN Structure information e The BICPlusIBAN directory should be used to e Translate beneficiary bank s BIC into national clearing sort code e Show banks participation in RTGS system e Show banks details name address amp so on e BICPlusIBAN Directory can also be used as an enquiry tool e SEPA Related e Derive BIC from the IBAN if missing e Validate IBANs and BICs e Validate IBAN BIC combination in payments On successful upload of BIC Plus IBAN system po
102. ver of the MT756 is the Remitting Negotiating bank The details are captured in the Parties screen lf the Remitting bank is not a customer of your bank you can use the CIF ID assigned to the walk in customer You will also have to capture the SWIFT address of the remitting bank If the Remitting bank is not a customer of your bank and you have used the CIF ID assigned to the walk in customer you will have to change the media to SWIFT in the Advices FFT tab for generating the Reimbursement Payment advice REIM_PAY_ ADV If you choose not to send an MT 756 the message can be suppressed in the Advices FFT screen An MT100 and MT202 Cover can be sent instead by choosing the Cover Required option in the Settlements Instruction screen Message Field Tag Description Type 53A D Sender s The receiver of MT202 This is the data input in the receiver Sa field in the Settlement Instruction screen for the Amount Tag BILL_LIQ_AMT This field is not populated if the receiver of the MT756 is the same as Our Correspondent 54A D Receivers Your entry for this field should be provided in the Account Correspondent With Institution field in the Settlement Instructions screen for the Amount Tag BILL_LIQ AMT The data in this field will appear as 57A in the accompanying MT202 a Sender to Receiver Information MT 910 This is mandatory and needs to be validated pst This is mandatory and needs to be validated 56a This field is populated with
103. xceeds the maximum size specified in the BIC maintenance the system automatically splits the queue into multiple queues to contain the message within the specified limits Generate MT102 Select this check box to process MT102 messages Selecting this check box also required the Multi Customer Credit Transfer checkbox to be selected Request for Transfer Generate MT101 This field indicates whether an MT101 can be sent received from this BIC Select this option to generate MT101 message Note This is a primary selection criterion A separate maintenance for agreements has to be maintained in the function ISDCCYRS to generate the MT101 No of Transaction per Message Here you can indicate the no of transactions to be included in an MT101 message If you donot specify a value it will be defaulted to 10 Maintaining BIC directories Oracle FLEXCUBE allows you to store SWIFT BIC in the database You can directly transfer data from the SWIFT BIC directories to the Oracle FLEXCUBE tables You can view the uploaded data in the BIC Summary screen You can invoke the BIC Code Summary screen by typing ISSBICDI in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 2 4 ORACLE 2 2 4 BIC Code Summary Web Page Dialog Authorization Status Bank Identification Code Customer Number SWIFT Key Arrangement YES Record Status Bank Name Bank Address
104. y Reimbursement Institution An Intermediary Reimbursement Institution is the financial institution between the Sender s Correspondent and the Receiver s Correspondent through which the reimbursement of the transfer takes place Country Specify the country of the intermediary reimbursement institution This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Intermediary The Intermediary in a payment refers to the financial institution between the Receiver and the Account With Institution through which the transfer must pass The Intermediary may be a branch or affiliate of the Receiver or the account with Institution or an entirely different financial institution This field corresponds to field 56a of a SWIFT message You can either enter the e ISO Bank Identifier Code of the bank e The Name and address of the Bank 2 17 ORACLE Country Specify the country of the intermediary institution This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one The country information is captured to enable Mantas to analyse the transactions for possible money laundering activities For more details on Mantas refer Mantas interface document RTGS Payments If the settlement chosen is one of the RTGS Nostro that is RTGS outgoing Nostro account in case of Outgoing customer and Bank t
105. you can indicate whether payment for local currency transactions is to be effected via messaging or over the local clearing network You can also indicate whether a cover is required for payment and whether the cover is through messaging or over the local clearing network You can specify these details in the Settlement Instructions screen In the Payment By field indicate the mode of payment either Message or Clear Details and in the Cover By field indicate the mode through which cover must be available If you indicate payment over a clearing network you must specify the account details of the external counterparties both pay and receive accounts in the Clear Details tab in the Settlement Instructions Maintenance screen In case you choose the option Clearing then a PC contract will be automatically created This PC contract will be created based on the appropriate transaction currency based on the Clearing Network that is maintained as part of the Settlement Instructions 2 23 ORACLE E Settlement Instructions Maintenance Web Page Dialog Branch BGT Module AL Counterparty BGTOOOBGT Product Code ALL Counterparty Type or E Sequence Number Currency GBP Relations Receive Branch BGT Branch BG I Cover Required Account bgt003 Account Cover By x Currency GBP Currency Charges Details Payment By Message Payment By Message Ourselves Benificiary Shared Pay Parties Pay Parties Receiver Partie

[January] [2010] Oracle Part Number E51573-01

Contents

Download Pdf Manuals

Related Search

Related Contents