Home

Clearing Interface Oracle FLEXCUBE Universal Banking Release

1. Group Detail Maintenance Network DTA Description Number Padding Process Direction Incoming External Node DTAOGPAY1 Number Padding Outgoing Direction Flexcube Node PAYMENTCHARGES FormatType Batch Body Alpha Padding i i Alpha Padding Direction a opona Length Check Required Date Format DDMMRR Time Format Format Seq No 1 External Rec Type C 1 External Rectype Desc BODY External Node Counter 1 value Translation Mapping Details 10f4 gt pl Go F W External Tags Flexcube Tags Flexcube Tag Position Mandatory Default Value Data Typ DATA_REC_LEN NO TRANSLATION number RECORD_TYPE C null return default else no translation char _ FIRST_PART_BANK 70110600 null return default else no translation number _ BENE_BANK CPTY_BANKCODE 49 NO TRANSLATION number _ BENE_ACC CPTY_AC_NO 51 Derivation number _ REFERENCE_NO CUSTOM_REF_NO 27 NO TRANSLATION number lt il Maker M35718 Date Time 2011 12 31 14 46 18 Mod No 1 Checker A35718 Date Time 2011 12 31 14 59 04 Record Status Open Authorization Status Authorized Through this screen you can establish a mapping between the Local Payments module of Oracle FLEXCUBE to fields that are required by the network A predefined set of Clearing Message Types will be shipped along with the software You can change the default attributes of these message types to suit the requirements of your bank Network ID The Oracle FLEXCUBE Clearing Gateway is a common channel for dat
2. 51200 merchant bank clearing bank of the merchant bank information centre in favour of the dealer merchant bank Cash card credit entry for dealer charges by the merchant 51210 bank in favour of the clearing bank of the merchant bank information centre Cash card credit entry for dealer charges by the clearing 51211 bank of the merchant bank information centre in favour of the clearing bank of the card issuer s information centre Cash card credit entry for dealer charges by the clearing 51212 bank of the card issuer s information centre in favour of the card issuing institution 2 25 ORACLE 220 221 230 240 241 nng 000 000 XXJ 777 000 Cash card credit entry for charges by the apex agency of the terminal operator in favour of the charging terminal operating institution Cash card credit entry for charges by the apex agency of the card issuer in favour of the charging apex agency of the terminal operator Cash card credit entry for a wrongly debited debit amount by the card issuing institution in favour of the terminal operating institution Cancellation of 05230 Cash card credit entry for a wrongly debited debit amount by the card issuing institution in favour of the client account Cancellation of 05240 Cash card credit entry of an amount released by the stock exchange by the card issuing institution in favour of the client account Re
3. derivation logic to obtain a value for such tags if required Indicating whether data pertaining to a specific tag should be made Mandatory You have the option of specifying whether the data pertaining to a specific information tag should necessarily be made available in the incoming outgoing message Check the box available under the column head titled Mandatory Specifying the Default Value You can associate a default value with each information tag While uploading or handing off messages suppose an information tag within the incoming outgoing message does not have a value associated with it the system automatically appends the default value with the particular information tag only if the translation type is set up for it Translation details for the specific Oracle FLEXCUBE and external tag combinations If you have indicated that Value Translation is required for all Oracle FLEXCUBE and external tag combinations this specification will be defaulted to all the tag mappings within the Oracle FLEXCUBE and external node combination However you have the option of changing this for individual tag mappings by choosing the appropriate translation option from the available list The seven options available are 1 No Translation Translation null return error Null returns default else no translation Null returns default else no translation Null returns Null else translation Derivation System Elements ee eS Pe Se NF Tem
4. Authorisation Key Start Position Key Length Include Reject l Clearing Msg Type Allowed Code Transaction Basis R Batch Key Length Mod No 1 Record Status Open Authorization Status Authorized Date Time 2011 12 31 14 43 32 Date Time 2011 12 31 14 44 15 Maker M35718 Checker A35718 Outgoing attributes If you are maintaining the details of an outgoing message group you have to specify the attributes of the batch hand off file that is sent These include e Include Reject indicates whether the details of the rejected contracts need to be part of the outgoing file e Block Enabled indicates whether the outgoing file needs to be block enabled e Line Length indicate the length of a line within a block e Block Filler specifies the identifier which should be used to identify the block e Block Factor specifies the factor by which the line length should be multiplied This in turn will provide the total number of characters in the block Incoming attributes Automatic Auth if enabled indicates that the incoming file should be automatically authorized upon receipt Transaction Basis specifies the basis on which transactions are grouped in an incoming file The options available are gt Record Based gt Batch Based If the records are batch based you have to capture the Batch Key Start position and the Batch Key Length to uniquely identify the batch Length Attributes e Length Check Req
5. File Format The DTA format is as shown below e A Header e C All the payment records e E End File Name DTAUS in HDR1 Field 3 The file name must invariably appear at the start of Field 3 of the HDR1 The entry of additional information maximum 11 positions after the file name DTAUS is permissible Such additional information should be separated from the file name DTAUS with a point X 4B Structure and Specifications of DTA Messages The structure and specifications of the DTA messages are explained in the subsequent sections 2 1 3 1 A Header Data record A data carrier set The data record A contains the mention of the tape transmitter and receiver Length Data Content Description Comments i format Data record The mention of the length Hard code to 150 of the data record shall be according to the conventions for variable data record lengths data record length field 4 bytes of which 2 bytes shall be left justified the remaining bytes X 40 or X 00 Type of Constant A To be hard coded to data record A 2 ORACLE character GK or 1K GB or B Bank designation client name Reference to credit entries G or debits and or cheque collections L bank tape B client tape K For inward delivery For outward delivery For inward delivery For outward delivery For inwar
6. Outgoing Process 10f1 Product Dect eee ODTA Loo Maker 435718 Date Time 2011 12 30 11 56 14 Mod No Checker M35718 Date Time 2011 12 30 11 56 38 Record Status Open Authorization Status Authorized 2 30 ORACLE In this screen you can capture the following attributes about the clearing message Type Category Network ID a valid network code from a pre defined set of Network Codes For instance you can define a network code called DTA Clearing Message Type a valid name to identify the clearing message type which is to be associated with the Network ID You can also capture a brief description to identify the clearing message type Process Direction specify whether the payment order which you are defining belongs to the Incoming transfer order or whether it belongs to the Outgoing transfer category Product Category Product Restriction If the process direction of the transaction type which you are defining is Incoming you will associate existing PC Product Categories with each transaction type Conversely if the process direction is Outgoing you will need to associate existing PC Products with each transaction type You can specify product category product restrictions in the form of allowed lists or disallowed lists 2 1 6 Viewing Clearing Message Type You can view clearing message type details using Clearing Msg Type Summary screen You can invoke this screen by typing IFSTXNTY i
7. 00 DTA DTAIGPAY DTA cust 0123456100 DTA DTAIGPAY DTA cust 0123456100 DTA DTAIGPAY DTA cust 0123456100 DTA DTAIGPAY DTA cust 0123456100 DTA DTAIGPAY DTA cust 0123456100 DTA DTAIGPAY DTA cust 0123456100 DTA DTAIGPAY 1 DTA cust 0123456100 DTA DTAIGPAY1 DTA cust 0123456100 DTA DTAIGPAY 1 DTA cust 0123456100 DTA DTAIGPAY DTA cust 0123456100 DTA DTAIGPAY DTA cust 0123456100 DTA DTAIGPAY DTAUS31121301330063 t DTAUS31121301330063 t DTAUS31121301330063 t DTAUS31121301330063 tet DTAUS31121126350101 tt DTAUS31121126350101 tt DTAUS31121126350101 tt DTAUS31121126350101 tet DTAUS311215035501 04 tt DTAUS02031 4295501 21 tt DTAUSO2031 4493801 23 tt DTAUSO2031 9070001 24 tt DTAUSO2031 537170141 tt DTAUS05031 231320161 tet DTAUSO8031 747030201 tt Ll Reset acetate Transaction group FileName partied You can either choose to view the details of files with a particular status or view the details of all files that were handed off The details of each file within a network will be displayed in a different color depending on its status For instance a file with errors will be displayed in red The system displays the following details Contract Reference Number Product Code customer No Account Number Account Branch Foreign Ccy Amount Transaction Amount Exchange Rate Account Number Name Customer Account LCF Network Transaction Group File Name Total Amount 2 54 ORACLE e Account Total 2 3 2 Ignoring Clearing Log Detail
8. 28 Ladd Maintaining Clearing Message Types oooeessssssssssssneenesessssssssssssseerereesesssssssssssseerrreeessssssssssseeeeeeereo 2 30 2 1 6 Viewing Clearing Message Type cccccccccccccccccccccensssseeeeeseeeeeeeeee eee ee eae se sseeeeeeeeeeeeeeeeeeeaaaaaaeaanseeeeeeeeeess 2 31 Zed Maintaining Clearing Interface derived UDF S ccccccccccsseeeccccceeee ee eeeseeeeeeeeeaaeseeeeeeeeaaaaeeseeeeeaaaaaees 2 32 2 1 8 Viewing Clearing Interface Derived UDF viccccccccccssscccccccccenneesececceeeenaeeseeeeeeeeaaesseeeeeessaaaaseeeeeeesaaaaens 2 33 2 1 9 Maintaining Group Detals cccccccccccccssecccccccceccneeeeseeceeeeeneeeeeeeeeeeeeaeeeeseeeeeeeaaaeeeeeeeeeesaaaaeseeeeeeeeaaaeees 2 34 2 1 10 Mapping sub nodes with the corresponding nodes in the External System cccccccseeccccccceeeeeeeeeeeees 2 39 2 1 11 Maintaining Transaction Group ccccccccccccccccccccccccccnseeceee cesses eeeegeeeeee eee eeeeee eee seee cece aa eee essa aaa eeeesaaaaeeeeeas 2 43 2 1 12 Viewing Transaction Group Details cccccccccccsscccccccccccccsecsscceeeeeeasssseeeeeeeeaseeeseeeeeeeeaaaeeeeeceeeesaaaseseees 2 49 22 OUTOON TARNO UPLOA Dipo eei octane eee ict tc one EE S 2 50 Lr OOM CE ARNG PEAY a O E eee tee eereeecetoeee 2 53 23 1 Viewing the details of Files that were HANdCd Off ccccccccccssccccccccccceeeeseeeceeceenaeesseeceeeeeaaeeeeeeeeeeaaaness 2 53 ye POPU CCAS Lo CI cre a aca cect caer cue cass tected E sso adc ied ea cee ea ea nade 2 55 24 PROCESSING FOR THE UN TE
9. 5 7000400000546 OO148810 O0022 000 14042 O02 QO OOOO OOO OO O00 Here 210 211 212 and 213 are the keys or external nodes Each key is used to identify the line of data that follows The external tag values will be picked up from the data as per the specifications in the Clearing Message Type Group Details Maintenance screen 2 44 ORACLE Identify the Record Separator The details of each contract are displayed as separate records within an ASCII file To differentiate the details of one contract record from another within the file you will need to identify the key external node that would be used to indicate the beginning of a new record within the ASCII file For instance let us assume that you have specified the following details e Key Start Position 1 e Key Length 3 e Record Separator 210 Consequently while processing data the system will differentiate between one record and the next only after verifying whether the first three characters of the record is three characters in length and is 210 Given below is a sample of how record separators are used to distinguish between details of one contract and another 210 O0O12207 293690001904 064 55 211 OGOOOOO0S 0400208 415 70004 00000546 l2 O0148e10 00022000 14042 O02 21s QOOQOOOOOO0000 2 2QOOOQ00000 1404204 O9380 401TG P 44EUREUR GOOO0O0068699S QOOO00004 0400 225 AKBANK INTERNATIONAL NY 246 C MAMAK 233 PATER BLEIJSSTRA
10. AT 17 230 4348 AM O85 210 00l2207729309000117721003 211 dOoOOooOF 00000208 705 7000400000546 l2 00216610 O0022000 l2362 O02 21s SLOLOLSLSLCLOLOLSISL OL OLOL8 2 2000000000 12436204 034240501TG 44EUREUR OOOO0O01101855 ooOo003 00000 221 AKBANK INTERNATIONAL NY 226 DEMIR HOLLAND BY 235 VENRAYSEWEG 120 B 236 49244 RH VENLO 240 BEYOGLU LTD MERSIN T REEI flO GOL420 7 F295 59000828 F 29561 Going by our example in the sample shown above the details from line 1 to line 10 are construed to be details of a single record or contract The details available from line 11 to 21 will be treated as a second record contract and so on Specifying the Masks and other attributes of the File The File Mask is the nomenclature in which the external system names the ASCII file You will need to capture the corresponding Process File Mask which is the format in which you have named the file in Oracle FLEXCUBE Example File Mask BETOPD04 Process File Mask BETOPD d t d is the date t denotes the time and indicates a running serial number If you check the Use Process File Mask box the external system will name the ASCII file based on the file mask specified for Oracle FLEXCUBE File Extension In addition to specifying the file masks you have to indicate the manner in which each file is to be stored Typically you can store these files with a btc extension However you have the choice of specifying any extension you wi
11. Clearing Interface Oracle FLEXCUBE Universal Banking Release 11 3 1 0 0EU April 2012 Oracle Part Number E51534 01 ORACLE FINANCIAL SERVICES ORACLE Clearing Interface Table of Contents L ABOUT THIS MANUA MD ip siscssssscitscstivactcsscistacssasasctuas ssi eaaa E tess eecsosdansaesissseusiisstaebeectbieertaassuceanseess 1 1 1 1 INTRODUC HON errr ten ene ee era centre Mer rete ene ee ert eee emer rer eee ener aren aree emer ee rere ee eT ere ener eT rer l 1 Lo AUDENC arnie E O EE E E ENE N E E E E E re l 1 1 3 ACRONYMS AND ABBREVIATIONS curosos aeo a oben a a 1 1 LA ORGANIZATION en ee E ee en er rr ee ee es re l 1 1 5 CONVENTIONS USED IN THIS MANUA E scvcicsnasttinseonensiinnnensinttonensintnnie a a nie sid ianewhint iene bled Mohansideenemmetanenbin 1 2 LO RTOS SAR OFICON crea E E E E E E nes 1 2 Li RECATDDOCUMENT S cereti rein E eee ee 1 3 2 CLEARING INTERFACE DTA MESSAGES eeeeccccccssssssseceececccccocossossessceccecosososssssssesscceeeecsssssssssssssseeee 2 1 2l CEOD TON se a E E E O E E O E 2 1 2 1 1 al 20 a eee nee RET CREE Meter ET CPR E TCT eT CRET eePEe ETT E DEN ERR Rr ter er er errr Cert E rr rerterrerrr ttre 2 1 nA P N E ER E EE AA 2 1 2 153 Structure and Specifications Of DTA Messages wiccccccccsessccccccccnenesseeceeeeeeaaeseeeeeeeeaaaeeeseeeeeesaaaaeeeeeeeeeaas 2 1 2 1 4 Definition Of a Return Direct Debit ccccccccccccccccccssesececeeceenneeeseeeeeeeeaaeeeseeeeeeeeaaaseeeeeeeeeaaaaeseeeeeeeeaaaaees 2
12. Field C 7a 09 for extension identifier 02 purpose of payment for voucher less unpaid cheque bookings or equal to 00 for unpaid cheque bookings via return cover l 7 Record return with extension part Same as 01 02 or numerical 03 in ascending order Maximum 1 times 01 Maximum 13 times 02 Maximum 1 times 03 ORACLE 2 20 The check totals from the addition of Numerically Tape return the unit counts of the data records C packed the fields Reserve C9 and amount C 12 account number of the beneficiary party liable to pay person writing cheque C 5 and bank code number of the bank of the beneficiary the paying agency the relevant bank C 4 should correspond to the details given in the data record E if the Field C9 is filled with a value that is greater than 0 the bank of the beneficiary is advised to notify the original amount from Field C9 in DM in addition to the amount in Euros from the Field C12 for information purposes alpha alopha numerical data left aligned blank positions X 40 From the field C9 only in exceptional cases where DM payments are still made Control measures plausibility and field content tests for DTA messages continued Data Record E Content Data Consequences Comments Format of errors Length Equal to Binary Notification to of data 150 the presenter record Field E 1 Type of Same as Tape retu
13. ISATION or NO DIRECT DEBIT AUTHORISATION 4 for RECALL 5 for DUE TO INCONSISTENCY this is only possible in the case of debit reversal entries from the direct debiting procedure 6 for RETURN CHARGEBACK FOR EXAMPLE MAESTRO T for the absence of GSE cheques no special provision as per Footnote 4 For amounts up to 12 500 Euros the numerical ISO country code of the country of the remitter can be used instead of the text code supplement 000 for example 9 27 ORACLE ow fom a a a In addition the stipulations contained in Footnote 2 shall apply EZU remittances in which the calculation of the check digit for the account number of the beneficiary leads to a negative result should be marked with the text code supplement 444 check digit calculation negative Remittances in which the account number of the beneficiary is not present should be identified with the text code supplement 445 account number missing The alphabets XX should preferably be replaced by 00 or by the relevant percentage of the savings bonus the alphabet J should be replace by the last digit of the year for which the payment is valid For example in the case of a payment for 2001 with 10 savings bonus the correct entry for the data field 7 shall be 54001 or 54101 The alphabets YY should be replaced by the original text code of the DTA remittance The alp
14. RE ACB cs cet ext setigncitieteanosnetincwaiatenniytetiecu eb Ee 2 56 2 4 1 licomne VIC SSC TOC S ILS nasais site sus sinus EAEE teste heck es pe Coa ach NR 2 56 2 4 2 Omon MESSE T TOCCSS TID ee ON TE E EA EE RE E E ONE 2 56 z SCREEN GLOSSARY cessans E E 3 1 3 1 PORC TORITO LI oes cay erage naisaesavaverwwnsdesnacadenconsnie E 3 1 ORACLE 1 About this Manual 1 1 Introduction This manual is designed to help acquaint you with the interface between Oracle FLEXCUBE and the relevant clearing networks This manual provides you extensive explanations about the various maintenances required for the smooth exchange of data between Oracle FLEXCUBE and the networks applicable It also gives you an insight into the processes involved in the actual exchange of data Besides this User Manual while maintaining the interface related details you can invoke the context sensitive help available for each field This help encapsulates the purpose of each field within a screen Placing the cursor on the relevant field and striking the lt F1 gt key on the keyboard can obtain information specific to a particular field 1 2 Audience This manual is intended for the following User User Roles Back office data entry Clerks Input functions for maintenance related to the interface Back office Managers Officers Authorization functions 1 3 Acronyms and Abbreviations Unless and otherwise specified it shall always refer to Oracle FLEXCUBE system U
15. UBE Nodes Just like in Oracle FLEXCUBE the clearing network too may have a set of its own Tag definitions Consequently it becomes necessary to maintain a mapping between the information tags within Oracle FLEXCUBE with those required by the clearing network The Oracle FLEXCUBE node represents a set of tags grouped together It is known as the parent node record from which the sub records sub nodes tags are derived for mapping to the external tags Format Type As stated earlier the messages that are handed off and uploaded into Oracle FLEXCUBE are in the ASCII file format An ASCII file consists of the following sections in the order specified 1 File Header 2 Batch Header 3 Batch Body 4 Batch Footer 2 36 ORACLE 5 File Footer You can maintain a format for each section of the ASCII file The file header marks the beginning of a file Every batch begins with a batch header and ends with the batch footer The batch body is the actual content of the message that is being handed off or uploaded The file footer marks the end of the file A file can consist of several file headers file footers batch footers and so on You can maintain a format for each occurrence of a format type within the ASCII file Format Seq No The format of an ASCII file is as shown below File Header Batch Header l Batch Body Batch Footer File Footer To recall a file can consist of multiple file headers batch h
16. a exchange between Oracle FLEXCUBE and the local clearing networks applicable The details of the applicable local clearing networks are maintained in Oracle FLEXCUBE You can define the process direction for each of these clearing networks through the Clearing Message Type Maintenance screen You can select the ID assigned to the Network whose tag names need to correspond with those maintained in Oracle FLEXCUBE On selection of the network from the available option list the description gets defaulted alongside Process Direction The format for hand off from Oracle FLEXCUBE is different from the format for upload into Oracle FLEXCUBE Therefore you need to indicate the process direction for which the format is being defined The options are e Incoming for upload into Oracle FLEXCUBE e Outgoing for hand off from Oracle FLEXCUBE 2 35 ORACLE Clearing Message Group Type Incoming message uploads formats are defined for a Clearing Message Group When you select the Incoming option the set of Clearing Message Groups supported in Oracle FLEXCUBE are made available to you in the option list provided Select the appropriate Group from the list The format will be applicable to all product categories belonging to the transaction types linked to the selected Message Group Likewise outgoing message hand offs formats are defined for a Clearing Message Type On selection of the Outgoing option all the Clearin
17. adjoining arrow button incoming Clearing Upload Metwork Metwork Description Transaction Group Group Description File Fath File Hame Upload IEW Log In this screen you need to identify the network and the message group for which the message needs to be uploaded If you do not want to use the file path specified for the Message Group you can enter a different path here This path will take precedence over the one maintained for the Message Group The three folders mentioned earlier will be created in the file path specified in this screen After you trigger the upload process the system will pick up the ASCII file from the in folder and move it to the wip area It retains a copy of the file in the fcc area as backup 2 3 1 Viewing the details of Files that were Handed off 2 53 ORACLE You can view the details of all files that were handed off through the Dispatch Incoming Clearing Log Summary screen You can invoke this screen click View Log button in Incoming Clearing screen Dispatch Incoming Clearing Log Summary 00000033 00000033 00000033 00000033 00000033 00000033 00000033 00000033 00000033 00000033 00000033 00000033 00000033 00000033 00000033 lt Network File Name Transaction group Records perpage 158 4 41 Of 3 p p Go DTA cust 0123456100 DTAIGPAY DTA cust 0123456100 DTA DTAIGPAY DTA cust 0123456100 DTA DTAIGPAY DTA cust 01234561
18. 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
19. aring Message Group combination can be resent only the specified number of times For instance you have indicated 3 as the resend count A specific message has failed to parse through all three times Since the resend count has been busted you will not be able to send the message one more time The message will be logged as an error message Click Handoff tab to invoke the following screen Transaction Group Maintenance Network Id DTA Key Start Position Clearing Message Group DTAOGPAY1 Key Length Group Description Include Reject Process Direction Incoming Outgoing Batch Count 0 Message Count Handoff Grouping T Line Length Block Filter Block Factor Block Enabled Maker M35718 Date Time 2011 12 31 14 43 32 Mod No 1 Checker A35718 Date Time 2011 12 31 14 44 15 Record Status Open Authorization Status Authorized Specifying the Handoff Parameters Since a single hand off file can have multiple batches you can indicate the number of batches that should be sent in a single file Similarly you have to indicate the number of transactions messages types which should be sent within a batch Additionally you can also specify manner in which message transaction types are to be sorted The options available are 1 By Clearing Message Type 2 By Account Number If you select the second option the transactions messages will be sorted by the Account Number involved in the transaction Else the sorting will be based on the tra
20. at is eventually handed off by Oracle FLEXCUBE 2 50 ORACLE You can trigger the message hand off event through the Outgoing Clearing Upload screen invoked from the Application Browser You can invoke the Outgoing Clearing Upload screen by typing IFDHFDET in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button gt Outgoing Clearing Upload Metwork Transaction Group Single Branch Branch Single Customer Customer No single Account Account Number Single Contract Contract Dispatch Group File Mame File Path view Log Wpload For message hand off you need to select the network and the clearing message group as mandatory information Additionally you can also specify one or all of the following options for hand off e Single Branch if you want to hand off messages from a specific branch for the selected network and message group combination You can select the branch from the option list available e Single Customer if you want to hand off transactions for a specific customer for the selected network and message group combination choose the name of the customer from the option list provided Transactions involving all the accounts of the selected customer will be handed off e Single Account select this option if you want to hand off transactions involving a specific customer account for the selected network and message group combination Yo
21. ave the option to indicate whether you want to calculate the length of each line in the file If you specify that line check is required you can maintain line attributes such as start position and length for the clearing message group in the Clearing Msg Group Maintenance screen explained later in this manual Date and Time Format For date related fields you need to identify the format in which the date value will be sent from and received into Oracle FLEXCUBE By default Oracle FLEXCUBE sends all date fields in RRRRMMDD format 2 38 ORACLE 2 1 10 Similarly for time related fields you have to identify the format in which the time value is to be sent from and received into Oracle FLEXCUBE For instance you can maintain a format like HHMMSS This format will continue to apply for the entire line of the message format Value Translation For each Oracle FLEXCUBE Node and External Tag combination you have to indicate whether translations should be performed for all tag values associated with the tag names A value translation is required only if the values sent by Oracle FLEXCUBE do not match with the external system specifications and vice versa Example Assume that Oracle FLEXCUBE recognizes only USD for US Dollars The external system requires the value of US dollars as Dollar When you upload into Oracle FLEXCUBE if the value of the tag CCY is Dollar it gets translated to USD Likewise during handoff USD gets
22. cending order starting from 0001 and the entry must not be without spaces Remitter presenter or If Bank is making a account receiving client max 10 payment then this number positions field is left blank But if the bank is making a payment on behalf of a customer then the customer account needs to be filled in this field FC en C e alpha alpha numerical data left aligned blank positions X 40 numerical numerical data unpacked numerically packed numerical data packed plus sign 2 1 3 2 Data Record C Payment Exchange Record The data record C contains particulars concerning the assignments to be carried out credit entries debits or direct cheque collections It is sub divided into a constant and a variable ee 1 Constant part Length in bytes Data Content Description Comments format 2 3 ORACLE Length specification of the data record as per the conventions for variable record length record length field 4 bytes of which 2 bytes are with binary left justified entry remaining bytes X 40 or X 00 alpha Type of Constant C data record Numerically Numerically packed Numerically packed Bank code Bank code number Account Number First participating bank released insofar as For EZU EZL identical with remitting bank first collection agency For BSE Cheque safekeeping agency Cheque converting agency First parti
23. cipating bank released For GSE Otherwise Bank of the beneficiary paying agency for BSE GSE concerned bank Field 2 of the coding line Beneficiary party liable to pay For BSE GSE cheque drawer Field 4 of the coding line Right justified maximum 10 positions Specify the length of the data record Consider the variable record length also Max possible value is 585 150 for constant part and 15 29 variable part K be hard coded to Optional field This field is the first collecting agent in the chain of transfer Ultimate beneficiary bank code paying agency Beneficiary account number Numerically DTA EZU packed EZL BZU hil BSE GSE p ONB SWIF T EDIFACT identifier and 1 half byte For DTA payments 0 Ref no For EZU EZL payments q For EZU payments 2 For BSE cheque collections o For GSE cheque collections 4 For ONB payments 6 For converted SWIFT payments 7 For converted EDIFACT payments 8 2 12 half byte reference number of the payment or zero 7 numerical Zero Reserve data alpha aloha numerical data left aligned blank positions X 40 numerical numerical data unpacked numerically packed numerical data packed plus sign Online Banking 2 5 First half byte is the type of the payment and then the reference number The type of the payment is always 0 o
24. d delivery For outward delivery Bank code number of the account controlling authority in the bank Zero packed Zero packed Zero packed Bank code number of the account controlling authority in the bank Remitter presenter or receiving client max 10 positions The counter value shall be calculated over this account NATIONAL CENTRAL BANK G credit Entry L debit entry kK Customer disk file B Bank disk tile Bank code of the bank receiving the file Sending bank code if the bank is sending the diskette If the customer is sending the file this should be Zero packed Name of the sender If bank then bank name else customer name For outward delivery the German equivalent of NATIONAL CENTRAL BANK has to be printed which is Landeszentalbank This is an optional field This can contain a valid 7 4 numerically Date date of creation of tape packed DDMMYY right justified ey Number for unique identification of the file right justified numerically Serial number of the file 2 2 number between For inward delivery it 0001 and 9999 should be kept in mind that the number circle is between 0001 and 9999 and that no number dependent on Field A 7 date is used multiple times The numbers must neither be entered without spaces nor in ascending order For outward delivery the number shall be entered in as
25. d C Content Data Consequences of Commets Format errors Text code same as 01 02 03 Numerically Record return Cheque 11 12 only permissible in packed collectione connection with identifier without 3 or 4 in the first half byte prefix of Field C 6a in the case of fixed code 01 02 11 or 12 the amount limit for BSE cheque collections shall be checked Same as 04 05 14 15 only permissible in connection with identifier 2 16 ORACLE 0 1 or 6 in the first half byte of Field C 6a Same as 09 or 10 only permissible in connection with identifier 0 1 3 4 or 6 in the first half byte of Field C 6a Debits Same as 51 54 or 56 59 65 and 67 69 only permissible in connection with identifier 0 1 2 6 7 or 8 in the first half byte of Field C 6a Credit entries Field C 7a Text code Same as or greater than Numerically Record return supplement zero packed Field C 7b Reserve If the content is not equal Numerically Record return Field C 9 to zero it should be packed possible to calculate the Tape return corresponding Euro amount Field C 12 from the DM amount that has been mentioned for information Bank Code 1 position X 0 Numerically Record return number of packed the remitting bank of the first 2 position not equal to 0 or 9 collection agency of the presenter a ORACLE O a alpha alpha numerical data left aligned b
26. displayed informing you of the same Suppose you had failed to associate a corresponding Oracle FLEXCUBE value USD for the External Value Dollar in the Translation screen the system would have displayed an error message informing you of the same You would have been allowed to maintain the record only after having maintained the corresponding translation value Case Ill If you select the option Null returns default else no translation Condition If the tag value is null the system will not translate it However the default value associated with the tag will be used Result As stated earlier the Tag Value associated with the external system is Dollar and the corresponding tag value in Oracle FLEXCUBE is USD Let us assume that the Tag Value associated with the Tag Name CCY is Null In such a case the system will use the default value GBP Case IV If you select the option Null returns default else translate 2 41 ORACLE Condition If the tag value is null the default value associated with the tag will be used else the value will be translated based on your maintenance in the Translation screen Result If the tag value in the external tag is Dollar during upload the system will translate this value to USD Similarly or hand off USD will get translated to Dollar If the Tag Value is Null the default value GBP will be used Case V If you select the option Null returns Null else tra
27. eaders file footers and so on The sequence number determines the manner in which multiple formats of the same format type appear in the ASCII file Oracle FLEXCUBE automatically sequences these formats for you If you are maintaining more than one file header format for a combination of Clearing Network and Oracle FLEXCUBE Node the sequence number will start with one and get incremented by one for each subsequent file header format External Node Just as the Oracle FLEXCUBE node represents a set of tags grouped together the external node is a unique name for identifying the set of tags belonging to the external system clearing network in this case You will need to map each tag identified by the external node to the corresponding tag belonging to the selected Oracle FLEXCUBE node You can enter a brief description of the external node in the adjacent field External Node Counter Multiple occurrences of the same External Node for a network and format type combination are tracked by means of an external tag counter This is required if a single external tag has to hold multiple columns of data when mapped to the corresponding Oracle FLEXCUBE tag 2 37 ORACLE The following example will illustrate this concept In the Oracle FLEXCUBE node Cust_Add the following child tags represent the address details e Addi e Add2 e Add3 e Add4 The value for each tag is required to upload or handoff the complete customer address d
28. eason for rejection ranged from values 1 to 6 Only 1 to 6 other than 5 can be used if bank rejects the same If bank rejects the direct debit then the first format will be used in the first four extensions part of the C record First line contains original date second line original amount third line the foreign charge and local charge and fourth line the reason for rejection The reason for rejection ranged from values 1 to 6 Only 5 can be used if customer rejects the same If customer rejects the direct debit then the second format will be used in the first four extensions of the C record First line contains the original date second line the return date and original amount third line the foreign charge and local charge and forth line the reason for rejection The text along with the data as above mentioned should be the same Maintaining Clearing Message Types A Clearing Transaction Message Type is a Payment Order belonging to a Transfer Category These Clearing Message Types Categories will be specific to the Network example BankGiro etc You can maintain the clearing message Type Category details through the Clearing Msg Type maintenance screen You can invoke this screen by typing IFDTXNTY in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Clearing Msg Type Network Code DTA Description Clearing Msg Type DTAOGPAY Description OUTGOING Process Direction
29. elds that are required by the clearing network In other words Oracle FLEXCUBE tags are mapped to the corresponding external system tags Sometimes you may not find a direct relationship between an external system tag and the Oracle FLEXCUBE tags For such tags with no corresponding tags in Oracle FLEXCUBE you can define an UDF User Defined Field and obtain a value by writing derivation logic Likewise you can also write rejection logic If a particular contract in the hand off message satisfies the rejection criteria the system will reject the entire contract The rejection logic will filter the contracts within the message that is being handed off During mapping you can map the external tag with the corresponding UDF name Example The external system may have a tag called Account Type A corresponding tag does not exist in Oracle FLEXCUBE Instead Oracle FLEXCUBE has a tag called Account_No Therefore to obtain a value for Account Type you can derive a logic such that if the first character of the Account No is C the Account Type would be Normal else it will be considered as a Special account Therefore when you actually hand off a message the Account Type would be associated with the value Normal or Special as the case may be You can maintain the UDFs in the Clearing Interface Derived UDF screen You can invoke this screen by typing IFDCLDUD in the field at the top rig
30. ength of data record Length specification of the data record as per the conventions for variable record length record length field 4 bytes of which 2 bytes are with binary left justified entry remaining bytes X 40 or X 00 ec C 4 4 Numerically Number of C data Reconciliation packed records document 5 7 Null Reserve right justified Numerically Total of the Account Reconciliation packed numbers for document beneficiaries parties liable to pay Cheque Drawer 2 12 ORACLE Numerically Total of Bank Code Reconciliation packed numbers of the banks document of the beneficiaries paying agencies concerned lending institutions Numerically Total of Euro amounts Reconciliation packed from the C data document records Field 12 alpha alpha numerical data left aligned blank positions X 40 numerical numerical data unpacked numerically packed numerical data packed plus sign The DM amounts from the data records C Field 9 may be entered in this field if in exceptional cases DM payments are still made Section 2 b Control measures plausibility and field content tests for DTA messages Data Record A Content Data Consequences Comments Format of errors Tape Same as the tape Alpha Tape return number in number in the order label record Variable maximum Binary Tape return 32 000 bytes incl block length field Record Equal to 150 Binary Notification to
31. etails The External Node 211 consists of maintenance required for customer address details It consists of a single tag Address In order for the external system tag Address to hold multiple columns of data from the corresponding Oracle FLEXCUBE tags Add1 Add2 Add3 and Add4 you need to map Address with each of the Oracle FLEXCUBE tags To achieve this you need to create a new record in the Clearing Msg Type Group Details Maintenance for each mapping for the same combination of e Clearing Network e External Node e Oracle FLEXCUBE Node and e Format Type The external node counter will track each occurrence of the above combination The count starts from one and gets incremented by one for every new record The Format Sequence Number will also get incremented by one for the same combination of Clearing Network Format Type and Oracle FLEXCUBE Node IS Optional On occasion you may need to send additional payment information with an ACH payment by using extended record formats called addenda Addenda may include payment related information such as Customer Addresses or Reject Codes While maintaining Clearing Message Group Type maintenance record for addenda you can indicate whether the record is optional or mandatory Check the option box to indicate that the format you are maintained is an optional one Leave the box unchecked to indicate that it is a mandatory record Length check required You h
32. g Message Types supported in Oracle FLEXCUBE become available in the option list provided The outgoing message forma Oracle FLEXCUBE t being defined will be applicable to all products that fall within the selected Clearing Message Type Number Padding Direction The messages that are uploaded to or handed off from Oracle FLEXCUBE consists of fields of a specific length Most often the maximum field length is not utilized when you capture the actual field values Therefore you need to specify a padding character to fill the gaps You also need to indicate the direction of the padding characters whether you would like to pad to the left of the actual field value or to its right Normally for numeric fields you would choose to pad to the left of the numeric value Example Assume that the length of a numeric field say Amount is 10 and the actual field value is 100 consisting of only 3 digits Further you select 0 zero as the padding character and choose to pad to the left of the field value If the message consists of this numeric field zero will be used to fill the gaps and the value will be displayed as 0000000100 Alpha Padding Direction similarly you have to select the padding character for the alphanumeric fields in Oracle FLEXCUBE You also need to indicate the padding direction for the same Normally for alphanumeric fields you would choose to pad to the right of the actual value Oracle FLEXC
33. g the charges and 05242 compensation payable to the terminal operating institution to the debit of the EC card issuing institution nn Reverse entry in view of accidental double DTA 05nn9 payment return credit cover s Charges for delivery of cheque copy or original 10000 cheque z 2 24 ORACLE O1 O1 O1 O1 O1 O1 l s _ hk _ hk l s ss s gt NO D O s D ee OOO Maestro 2 presentation of a debit due to online 14003 POS withdrawal abroad 14 005 Charges due to withdrawals from EMV ATM s 14005 abroad 14 Debit due to online POS withdrawal abroad 14006 Maestro EMV 14 007 Maestro EMV 2 presentation of a debit due to 44007 online POS withdrawal abroad 14 082 Debit due to offline POS withdrawal abroad 14082 Maestro 14 083 Maestro 2 d presentation of a debit due to online 14083 POS withdrawal abroad 14 084 Debit due to offline POS withdrawal abroad 14084 Maestro EMV 14 085 Maestro EMV 2 presentation of a debit due to 14085 offline POS withdrawal abroad 15 000 Charges due to international standard remittance 45000 within the reporting limits Remittance credit entry for example commercial 51000 utility Text key Explanation Content of supplement the data Field 7 b field 7 Cash card credit entry for cash card transactions by the
34. h C16 contains the old C16 C6 contains the old C6 Field C7a contains 09 Field C7b contains the old C7a field 04 or 05 with an extension of the code number indicating the reason for return 0 No details given keine Angabe 1 Account no longer exists Konto erloschen 2 Details not clear account is wrong account differs from name KTO Nr Falsch KTO Nr Name nicht identisch 3 No instruction to pay debit notes Kein Abbuchungsauftrag C7a old 04 Keine Einzugsermachtigung c7a old 05 4 Recall Ruckruf 5 Due to objection by debtor Wegen Widerspruch 6 Return chargeback EDC Ruckgabe 1 If the bank rejects the direct debit the first 4 extensions reason for payment should contain 12345678901 2345678901 234567 first VORGELEGT AM dd mm yy NICHT second BEZAHLT EU 123456789 12ENT original amount third GELT FREMD12 12EIGEN12 12EU foreign charge own charge forth XXXXXXXXXXXXXXXXXXXXXXXXXXX reason for return 2 if the customer rejects the direct debit then the first 4 extensions reason for payment should contain case of due to objection by debtor 123456789012345678901234567 first BELASTET AM dd mm yy ZUR CK date of debit 2 29 ORACLE 2 1 5 second dd mm yyEU 123456789 12ENT date of return original amount third GELT FREMD12 12EIGEN12 12EU foreign charge own charge forth XXXXXXXXXXXXXXXXXXXXXXXXXXX reason for return The r
35. habet Z should be replace by the respective digit of the encoded Ground for Return 1 for ACCOUNT CANCELLED 2 for ACCOUNT BANK CODE NUMBER WRONG 3 for CONTRACT EXECUTED or CONTRACT INTERRUPTED CREDIT NOT PERMISSIBLE 4 for RECALL 5 for ACCOUNT NUMBER NAME NOT IDENTICAL Remittances in which the account number of the beneficiary is not specified should be identified with the text code supplement 445 account number missing 2 1 4 Definition of a Return Direct Debit If a direct debit is returned by the bank or by the customer a DTA message will be generated to intimate the originating bank The reject DTA message will change from the original DTA message mainly in terms of the following explained fields The reason for rejection is written in the first 4 lines of the C extension record with identifier of the extension part as 02 If there is already some data in the extension part of the original DTA message it will be over written by this So the DTA standards suggest the customers to put the purpose of payment in the original record field C16 with the least text possible The original C record of a non payed direct debit has some changes C4 BLZ Bank Code changes with C10 C5 Account changes with C11 C14 Name changes with C15 2 28 ORACLE C12 contains the sum of the original amount foreign charge own charge the highest charge 3 5 eac
36. hecker A435718 Date Time 2011 12 31 14 44 15 Record Status Open Authorization Status Authorized Indicating the Network ID In the Clearing Networks screen you can maintain the networks such as INTERPAY and HLAYOUT through which you communicate with other banks and financial institutions for local currency funds transfers You can identify the Network ID for which you are grouping transaction types When you select the relevant Network ID from the available option list the associated description will be defaulted to the adjacent field Identifying the Clearing Message Group You will have to uniquely identify each clearing message group that you define with an appropriate name Additionally you can also specify a brief description to identify the group Specifying the Key Start Position and Key Length The ASCII file consists of multiple lines of messages A unique key identifies each line of data within a message You have to indicate the start position of the key and the length of the key This will help you in identifying the key in the message and subsequently in deciphering the data that follows The key actually denotes an External Node The values that appear after the key are assigned to the external tags as per the format maintained for that external node in the Clearing Message Type Group Details Maintenance screen Consider the sample shown below PIO 0 l22077293090001904 064535 PIT OO00000S 040020871
37. ht corner of the Application tool bar and clicking the adjoining arrow button 2 32 ORACLE 2 1 8 Clearing Interface Derived UDF IOF Name DUDFR WOOF Description UDF Type Derivation Rejection Metwork Code OTA Incoming Outgoing Incoming Outgoing Rule I_No Number Errors Charge_Amount Number 0 Begin select TREQ_DTA currval into _no from dual p_ result Ipadf l no 4 04 p Result 0022 Return True Default Return End x LEd Maker M35718 Date Time 2011 12 30 17 24 26 Mod Mo a Checker A435718 Date Time 2011 12 30 17 24 38 Record Status Open Authorization Status Authorized In this screen you have to specify the following details UDF Name and UDF Description You can specify a unique name to identify the UDF A brief description can also be provided in the adjacent field UDF Type Additionally you should also specify the type of the UDF being defined whether you are writing a logic to derive a tag value or for filtering the transactions in a message file based on a rejection criteria Network Specify the network for which you are writing the derivation rejection logic To execute the logic click on the X button If you encounter any error during execution you can view the same by clicking on the E button Make the necessary corrections before you re execute the logic The UDFs defined through this screen will be available in the drop down menu of the Derive Type f
38. ield in the Clearing Message Type Group Details Maintenance screen This is discussed in the section that follows You can maintain only 25 derived logics UDFs for all the networks that are applicable for data exchange with Oracle FLEXCUBE Likewise you can maintain only one rejection logic per network Viewing Clearing Interface Derived UDF You can view clearing interface derived UDF using Clearing Interface Derived UDF Summary screen You can invoke this screen by typing SIFSCLDUD in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 2 33 ORACLE Clearing Interface Derived UDF Summary Authorization Status Record Status UDF Name UDF Type Network Code Incoming Outgoing Refresh Reset Records per page 15 YM 4 1 of 1 bl dE c Authorization Status Record Status UDF Name UDF Description UDF Type a Pa om Authorized Authorized Authorized Authorized Authorized Authorized Authorized Authorized Authorized Authorized Authorized Authorized Authorized Authorized Authorized Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open DUDF12 DUDFE6 DUDF15 DUDF101 DUDF4 DUDF13 DUDF2 DUDF19 DUDF 21 DUDF14 DUDF1 DUDF100 DUDFS DUDF200 DUDF25 Derivation Derivation Derivation Derivation Derivation Derivation Derivation Derivation Derivation Derivation Derivation Derivation Der
39. incoming messages contracts are uploaded using the following process stages You will initiate the process of uploading files The system checks if any recovery operation is required If required it is handled first The file name is logged into the log table before the contents of the file are processed The file name can be used for recovery and reporting After this the entire file is read into memory in chunks The key identifier for the message is derived from the position and the number of characters maintained at the file level For the Identifier thus derived the subsequent details are picked from the message maintenance Next the system processes each line and populates it into a row type Whenever the beginning of a new contract is found the system inserts the row type into the corresponding table with a particular flag This process goes on till the end of file is reached The following totals will be kept for each file driven by a flag Total for Debits Total for Credits Total for Accounts Total of Amounts No of Records in the Message Vv Vv Y V WV After processing all the records the file is moved into the fcc area All the status for the contracts uploaded will be changed for booking and these data are processed using a batch function 2 4 2 Outgoing Message Processing While processing outgoing messages the following stages are involved in the creation of Clearing files You will have to specif
40. ivation Derivation Derivation DTA DTA DTA DTA DTA DTA DTA DTA DTA DTA DTA DTA DTA DTA _Cpty_Bnk_Code Numbe _No Number _Charge_ Procedure Dbg l_Msg Val _result VARCHAR2 3200 _ Result Varchar2 32000 _result VARCHAR2 3200 _cpty_bnk_code NUMBE Chg_Amount Numbertz Begin procedure body g Begin procedure body p Begin procedure body _cpty_bnk_code NUMBE _Number_Ext Number _cpty_bnk_code NUMBE _result VARCHAR 2 3200 lt iii gt Exit In the above screen you can base your queries on any or all of the following parameters and fetch records e Authorization Status e Record Status e UDF Name e UDF Type e Network Code e Incoming Outgoing Select any or all of the above parameters for a query and click Search button The records meeting the selected criteria are displayed e Authorization Status e Record Status e UDF Name e UDF Description e UDF Type e Network Code e Rule 2 1 9 Maintaining Group Details 2 34 ORACLE Each network and clearing message type category has a fixed format that needs to be handed off from or uploaded into Oracle FLEXCUBE Therefore you will need to specify the format in which data is to uploaded and handed off You can do this through the Group Details Maintenance screen You can invoke this screen by typing IFDTXNDT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button
41. lank positions X 40 The DM amount may be entered in this field for purpose of information ad ORACLE Control measures plausibility and field content tests for DTA messages continued Data Record C Content Data Consequences Comments Format of errors Account number 1 position X 0 Numerically Record return of the remitter R packed ayee est not equal to p zero 1 position X 0 For BSE GSE cheque Rest not equal to a zero collections Internal number Field C 11 Amount in Euros Amount not equal Numerically record return Field C 12 peste packed tape return Name of the not equal to X 40 alpha Record return beneficiary party liable to pay or text constant for BSE GSE Field C 14 Name of the of not equal to X 40 alpha Record return the remitter payee or text constant for BSE GSE Field C 15 alpha alpha numerical data left aligned blank positions X 40 Control measures plausibility and field content tests for DTA messages continued Data Record C Content Data Format Consequences Commets of errors Extension identifiers For BSE GSE cheque collections For BZU payments For return debits Field C 18 Identification of the extension part Field C 1 variable part same as 00 15 Numerically packed same as 00 same as OO if Field C 7a 67 same as 01 if Field C 7a 59 equal to 03 or 04 if
42. length presenter Field A 1 Type of Same as constant alpha Tape return record A Field A 2 2 13 ORACLE Identifier 1 position L or alpha Tape return Field A 3 gt Bank Code same as the Bank Numerically Tape return numberof Code number of the packed the account controlling account authority in the controlling bank authority in the bank Field A 4 Bank Code equal to 0 Numerically Tape return number of packed the person sending the magnetic tape Field A 5 Date same as permitted Numerically Tape return date current date packed FERR or date of one of right the past 10 justified business days Serial same as valid file Numerically Tape return numberof number the file packed the file number may be right l given only once in justified ee connection with field A 9 as well as A 7 Account same as client Numerically Tape return number of entitled to remit packed the remitter presenter Client Field A 9 alpha alpha numerical data left aligned blank positions X 40 Control measures plausibility and field content tests for DTA messages continued Data Record C Text code same as 01 02 03 Numerically Record return Cheque 11 1 2 only permissible packed eolo on in connection with without prefix identifier 3 or 4 in the first half byte of Field C 6a in the case of fixed code 01 02 11 or 12 Debits the amount limit for BSE cheque Credit entries co
43. llections shall be Field C 7a checked Same as 04 05 14 15 only permissible in connection with identifier 0 1 or 6 in the first half byte of Field C 6a same as 09 or 10 only permissible in connection with identifier 0 1 3 4 or 6 in the first half byte of Field C 6a Same as 51 54 or 56 59 65 and 67 69 only permissible in connection with identifier 0 1 2 6 7 or 8 in the first half byte of Field C 6a Text code Same as or greater Numerically Record return supplement than zero packed Field C 7b Reserve If the content is not Numerically Record return equal to zero it should packed be possible to calculate the corresponding Euro amount Field C 12 from the DM amount that has been mentioned for information Bank Code 1 position X 0 Numerically Record return nome 2 position not equal to Peed the remitting 0 we q bank of the first collection agency of the presenter Field C 10 alpha alpha numerical data left aligned blank positions X 40 Field C 9 Tape return If this test cannot be carried out by the presenter for technical reasons it should be carried out by the German Federal Bank This is only permissible for data records from Bank Institutes Only in the case of data records of the German Federal Bank ONB Online Banking Control measures plausibility and field content tests for DTA messages continued Data Recor
44. n the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Clearing Msg Type Summary Authorization Status Record Status Network Code Clearing Msg Type Process Direction Refresh Reset 1 1 Of 1 __ Records per page 5 el Authorization Status Record Status NetworkCode Clearing Msg Type T Authorized Authorized Authorized Authorized Authorized Authorized Authorized Authorized Open Open Open Open Open Open Open Open EF DTA EFT DTA EFT DTA DTA DTA DTAOP DTAOGPAY DTAIP DTAIGPAY1 OUTDTA DTAOGPAYS DTAIGPAY DTAQGPAY1 DTA_OutgoingPayment Outgoing OUTGOING Outgoing DTA_Incoming_Payment Incoming Incoming Clearing Incoming OUTCLGDTA Outgoing OUTGOING Outgoing Incoming Clearing Incoming OUTGOING Outgoing In the above screen you can base your queries on any or all of the following parameters and fetch records Authorization Status Network Code Process Direction Record Status 2 31 ORACLE e Clearing Msg Type Select any or all of the above parameters for a query and click Search button The records meeting the selected criteria are displayed e Authorization Status e Record Status e Network Code e Clearing Msg Type e Description e Process Direction 2 1 7 Maintaining Clearing Interface derived UDFs As part of maintenance you have to establish a mapping between the Local Payments module of Oracle FLEXCUBE to fi
45. nal tag say Date to the system element SYSDATE The hand off file will contain the actual date of the transactions Maintaining Transaction Group Transaction types having common attributes should be grouped together into Clearing Message Groups for ease of processing For each clearing message group that you maintain you will need to define a set of uniquely identifying specifications These specifications will determine the parameters for the manner in which contracts also referred to as records are arranged within ASCII files Invoke the Transaction Group Maintenance screen from the Application Browser to group transaction types into clearing message groups You can invoke the Transaction Group Maintenance screen by typing IFDTXNGR in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Transaction Group Maintenance Network Id DTA Key Start Position Clearing Message Group DTAOGPAY 1 Key Length Group Description Include Reject Process Direction Incoming Outgoing File Attributes Handoff Parameter Incoming Attributes Clearing Msg Type Allowed File Mask DTAUS d m h i Process File Mask DTAUS d m h i s File path ftmp File Extension tt Record Separator Field Separator Session Timeout Clearing Msg Typ Use Process File Mask Separator Length Check Required Resend Count Starting Position Length Maker M35718 Date Time 2011 12 31 14 43 32 Mod No 1 C
46. nce let us assume that you have specified the following details e Tagi gt Start Position 1 gt Data Length 10 e Tag2 gt Start Position 11 gt Data Length 10 As a result while processing data the system will identify the first 10 characters as Tag 1 and the next 10 characters 11 to 20 for Tag 2 Derive Type For an external tag if you choose the translation option as Derivation Logic you have to map it to the corresponding UDF name You would have already maintained the UDF in the Derived UDF Maintenance screen The external tag will get the value based on the logic that you have maintained for the selected UDF All the UDFs that you maintain in Oracle FLEXCUBE will be available in the drop down list You can select the appropriate one from the list System Elements If you need to hand off the system Oracle FLEXCUBE derived values you have to select the translation option System Element Further you are also required to map the external tag with a system element The set of system elements are available in the drop down menu You can select the appropriate element to map to the external tag For instance the clearing network may want you to hand off transactions that were entered in Oracle FLEXCUBE on a specific calendar date System Date the current date as shown in your machine The Oracle FLEXCUBE date may be different from the current system date Therefore you will need to map the exter
47. nsactions themselves For instance assume there are 12 transactions within a file Out of these 12 transactions four involve the same account number and the other eight involve a different account number For the given Clearing Group you have indicated that messages should be sorted as per the Account Number As a result the details of eight messages involving the same account will be listed first and the details of the other four messages will be listed subsequently Restricting specific Clearing Transaction Type from a group A list of all the transaction types you have maintained in the system are displayed in the Available column For each Clearing Group that you define you can choose to restrict or allow specific transaction types in the form of allowed or disallowed lists Indicating the Process Direction and the related attributes A Message Group can be defined to group transaction types maintained for the upload of messages into Oracle FLEXCUBE Incoming or for the hand off of messages from Oracle FLEXCUBE Outgoing You have to indicate the process direction of the message group You will need to specify the process attributes depending upon the process direction that you specify Click Incoming Attributes tab to invoke the following screen 2 47 ORACLE Transaction Group Maintenance Network Id DTA Clearing Message Group DTAOGPAY 1 Group Description Process Direction Incoming Outgoing Batch Key Start Position Auto
48. nslate Condition If the tag value is Null the Tag Value will be retained as Null If the value is present it will be translated Result Since the Tag Value is Dollar it will be translated to USD for upload For hand off the tag value will be translated to Dollar Suppose the Tag Value is Null it will be retained as null Case VI If you select the option Derivation Logic To recall you use a derivation logic if for an external tag there is no corresponding tag in Oracle FLEXCUBE The logic is identified by a unique UDF User Defined Field You will need to map the name of the corresponding UDF to the external tag During handoff the system will associate the value obtained from the derivation logic maintained for the associated UDF Case VII If you select the option System Element The external tag will inherit the value of the system element to which it is mapped Data Type In addition to mapping the Oracle FLEXCUBE tags with the external tags you should also specify the type of data for each tag The Data Type indicates the nature of the data whether it is numeric or a character format The following options are available e CHAR e NUMBER e DATE and e TIME Start Position and Data Length To differentiate the data of one tag from another you will need to indicate the position from where a particular tag begins The length of the data within the tag should also be captured 2 42 ORACLE 2 1 11 For insta
49. o including decimal places Remitting bank 1 Remitting bank code collection agency Or For BSE GSE Remitting bank 1 collection agency from field 5 of the coding line of the consolidated voucher positions 6 13 or from Field 1 of the individual data record of the tape accompanying the voucher positions 1 8 For BZU Remitting bank or remitting bank Remitter payee Remitter s account right justified number Maximum 10 positions For example presenter number from Field 5 of the coding line of the consolidated voucher positions 1 5 or bundle daybook number or from Field 1 of the individual data record of the accompanying voucher tape positions 9 13 right justified maximum 10 positions Right justified If not used X Bank internal field In DTA this field is 40 optional While generating the DIA message FLEXCUBE UBS can generate all the transactions in to a single file containing one ACE record irrespective of the value date At PAS the HVB system will use this field to group the transactions with same value date to generate the proper DTA message that can be send out Interface requirement section 5 outgoing for more details Beneficiary party Beneficiary name liable to pay left justified For BSE GSE text constant CHEQUE Beers Left justified alpha alpha numerical data left aligned blank positions X 40 numerical n
50. ping based on the customer accounts involved in the transactions All contracts involving a specific customer account will be grouped under a single batch file After you trigger the hand off process the system will pick up the relevant tag values for all the transactions from the database table and display the contents of the hand off file in the Outgoing Message Browser Dispatch Outgoing Clearing Log Summary screen Dispatch Outgoing Clearing Log Summary Network File Mame Refresh Reset 15 1 of 2b pil Gol Network Records perpage File Hame DTAUS311213501 330063 tt DTAUS31121301330063 tst DTALS31121126350101 tst DTAUSO2031 4295501 21 tt DTAUSO2031 4295501 21 tt DTAUSO20315371 70141 tat DTAUSO5031 231320161 tt DTAUSO5031 231320161 tt DTAUS 3112145702008 txt DTAUS311214581 10084 tt DTAUS 311215035501 04 tt DTAUS3112150355501 04 tet DTAUS0S03202355501 81 txt DTAUS050320235501 81 tt DTAUS 3112114150006 tt Total Amount Account Total 33 123456100 123456100 33 123456100 123456100 33 123456100 0 33 33 123456100 33 0 33 The following details will also be available e Network the name of the network to which the file is hand off is triggered e Transaction Group the clearing message group for which the hand off is taking place Product Code 2 52 Customer Mo 003000857 E E 003000857 E w ODOS00057 E 003000857 002000s57 003000857 w 003000857 E 003000857 Acco
51. porary Data In case of choosing derivation the derivation has to be selected from the drop down In case of choosing system elements the element from drop down system element has to be selected Let us assume that you are maintaining the translation details for an information tag called CCY currency The value of this tag in Oracle FLEXCUBE is USD But the external system uses Dollar for the same In the Translation Values screen the information that you capture will look as follows Oracle FLEXCUBE Value External Value USD Dollar The example given below illustrates the manner in which the system will behave when you choose any one of the Translation options Example We have specified the following parameters for the External Tag named CCY currency e The Translation Value for gt Oracle FLEXCUBE USD gt External System Dollar e The Default Value is GBP which is the local currency Case If you select the option No Translation the system will not perform any translation As a result if the message involves the tag CCY with value USD both the incoming and the outgoing messages will retain the value USD Case Il If you select the option Translate null returns error Condition The tag value will be translated based on your maintenance in the Translation screen If you fail to send the corresponding value to the system i e if the value of the tag is null an error message will be
52. r 7 2 to 12 half bytes can contain the reference number of the transaction would require O for all payment and collection items that are getting uploaded would require 1 for all payment and collection items that are getting entered directly into FC would require 6 for all payment and collection items that are getting into FC from the fc Only permissible in the case of data records of banks Only permissible in the case of data records of the German Federal Bank Structure and clarifications concerning DTA messages 1 Constant part continued Constant part 1 Constant part continued Length Data format Description Numerically Text code Identification of the Identification of type of packed type of payment for the transaction Type without prefix BSE GSE Field 1 of of transaction is the coding line uniquely identified with Anei code the combination of supplements as per fields 7a and 7b There Section 2 is a list available which is given in the Section Identification of type of the transaction Type of transaction is uniquely identified with the combination of fields 7a and 7b There is a list available which is given in the Section Comments Numerically Text code packed supplement 2 6 ORACLE 11 12 Numerically packed Numerically packed Numerically packed Bank Code number Account number Or For BSE and GSE Internal number Amount in Eur
53. redit cards 05009 Debits due to POS withdrawals with foreign card Maestro EMV_ 05010 Debits due to POS withdrawals POZ 05015 Cash card debits for debiting cash card transactions by the 05200 dealer the merchant bank to the merchant bank the clearing bank of the merchant bank information centre Cash card debit for debiting the cash card transactions by the 05201 clearing bank of the merchant bank information centre to the clearing bank of the card issuer information centre Cash card debit for debiting cash card transactions by the 05202 clearing bank of the card issuer s information centre to the stock exchange clearance account of the card issuer Text key Field 7a Text key Explanation Content of the data field 7 supplement Field 7 b 210 Cash card debit for debiting dealer payments 05210 through the clearing bank of the merchant bank information centre the merchant bank to the dealer 222 Cash card debit for debiting the charges by the 05222 card issuer s apex agency to the card issuing institution 230 Cash card debit for debiting the charges of the 05230 card issuing institution to the terminal operating institution while charging against other currencies 240 Cash card debit for debiting the charges and 05240 compensation payable to the card issuing institution to the client account 242 Cash card debit for debitin
54. rn record constant Field E F 2 alpha alpha numerical data left aligned blank positions X 40 Section 3 1 Details concerning the remitter payee party liable to pay The details should not exceed the 27 positions provided in the data field C 15 or C 14 see Section 1a or 1b Explanations concerning Field 7 a and 7 b of the data record C 2 21 ORACLE For identifying the type of payment in Field 7 a use the text codes specified in the Guidelines for standardised payment forms The payment types mentioned below should also be identified with a special text code supplement in Field 7 b 9 29 ORACLE Text key Explanation Content of supplement the data Field 7 b field 7 Debit 04000 pre authorised payment process Debit 05000 direct debit process Debits due to supra institutional withdrawals from EC ATM s 05001 abroad Debits due to EC ATM withdrawals by foreign persons 05002 Debits due to supra institutional EC EMV ATM withdrawals 05003 within the country Debits due to EC ATM withdrawals via credit cards or CIRRUS 05004 and PLUS debit cards Debits due to POS withdrawals 05005 Electronic cash Debits due to POS withdrawals 05006 with foreign card Maestro Debits due to EMV ATM withdrawals by foreign persons using 05007 debit cards Debits due to credit card transactions 05008 Debits due to EMV ATM withdrawals using c
55. s After you trigger the hand off process the system will pick up the relevant tag values for all the transactions from the database table and display the contents of the hand off file in the Outgoing Message Browser To invoke the Ignore Clearing Log screen type IFSIGCLG in the field at the top right corner of the Application tool bar and click the adjoining arrow button Ignore Clearing Log Product Category a Product Code a oO Search Advanced Search Records eee 4 4 1 of 1 PIF Go Contract Reference CustamerMo Customer Account LEF AccountMo Transaction Amount Exchange Rat The system displays the following details e Network the name of the network to which the file is hand off is triggered e Transaction Group the clearing message group for which the hand off is taking place e File Name the name of the hand off file in ASCII format e Amount Total the sum total of the amount involved in all the transactions that are handed off e Account Total the sum total of all the accounts in the transactions The account number is anumeric value The system will add the account numbers involved in each transaction to display this value 2 55 ORACLE 2 4 Processing for the Interface The interface can either be Online or in a Batch format For the online mode each contract in Oracle FLEXCUBE will be handed off as a separate file 2 4 1 Incoming Message Processing While processing
56. s processed e If the record is locked successfully then the details of the record are passed on to the Business Rule layer to update the record to the dispatch status e Based on the flag passed from the Business layer the message is formatted on the basis of the maintenance done e A preset number of contracts is processed and committed and written to the file based on the maintenance done e After all the contracts are processed the file is moved to the area specified in the maintenance The above processes are also responsible for converting the data formats and tag formats from the Oracle FLEXCUBE standard format to the formats as required by the external systems The above set of processes also translates the fields that require a translation as per the maintenance for the particular interface 2 57 ORACLE 3 Screen Glossary 3 1 Function ID List The following table lists the function id and the function description of the screens covered as part of this User Manual ston ronson 3 1 ORACLE ORACLE Clearing Interface April 2012 V ersion 11 3 1 0 0EU Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores CA 94065 U S A Worldwide Inquiries Phone 1 650 506 7000 Fax 1 650 506 7200 www oracle com financial_ services Copyright 2012 Oracle Financial Services Software Limited All rights reserved No part of this work may be reproduced stored in a retrieval system
57. ser Defined Fields Automated Clearing House 1 4 Organization This document talks about the maintenance required for data exchange between Oracle FLEXCUBE and the relevant clearing networks This includes the following e Maintaining Clearing Message Types e Maintaining File Formats e Maintaining Clearing Message Groups e Derived and Rejection UDF Maintenance e Message Status Browser The manual also talks about the following processes e Message hand off to the clearing network e Message upload into Oracle FLEXCUBE e Online message processing X ORACLE 1 5 Conventions Used in this Manual Important information is preceded with the symbol 1 6 Glossary of Icons This User Manual may refer to all or some of the following icons eme Jenan a e 1 2 ORACLE 1 7 Refer the Procedures User Manual for further details about the icons Related Documents You can refer to the XML Interface document which outlines the details of the interface mechanism between Oracle FLEXCUBE and an External System ORACLE 2 1 2 1 1 2 1 3 2 Clearing Interface DTA Messages Introduction All the customer payments normal and direct debit notes within Germany will be handled in DTA format Oracle FLEXCUBE handles the DTA messages through the clearing interface There is usually a single file one for credit notes and one for debit notes transfer containing mass data It is called EMZ Electronic Mass Transfer
58. sh to generate these files in File Path The file path is the directory or area in your system where the ASCII files are to be stored Field Separator You have the option of using delimiters to separate data within a file The options available are e S indicating that a space needs to be used as a delimiter e ST indicating that a tab needs to be used as a delimiter Alternatively you can also choose to have a comma a semi colon a hyphen etc Clearing Message Type Separator To recall in this screen you are grouping clearing transaction message types which share similar attributes You have the option of differentiating messages within a group with delimiters Session Timeout The session timeout is the maximum time limit that Oracle FLEXCUBE will wait for a response to a request sent to the external system You can indicate in terms of minutes the time within which an outgoing file should be processed by the External System and sent back to Oracle FLEXCUBE Each time the external system fails to send a response to a request sent by Oracle FLEXCUBE within the maximum time limit maintained Oracle FLEXCUBE will recreate the message and send it to the external system again You can maintain a count for the number of times a message can be resent Resend Count An outgoing message can be resent any number of times You have to indicate the resend count in this field As a result all messages for the given Network ID and Cle
59. t description of the payment In case of rejection of direct debit the reason for rejection can be entered this Numerically Extension 00 no extension fno extension is used identifier BSE part follows then put 00 and the C GSE and BZU 01 15 number of cord ends here 00 _ Otherwise put the extension parts up number of extensions For return to 29 bytes used in this field remittances alpha alpha numerical data left aligned blank positions X 40 numerical numerical data unpacked numerically packed numerical data packed plus sign Structure and clarifications concerning DTA messages 2 Variable part The variable part forms one unit together with the constant part It is only present if the data fields in the constant part are insufficient for recording information A maximum of 15 extension parts can be appended to the constant part of the data record C taking into account the ascending sequence of the extension sign The following may occur one extension part for beneficiaries or party liable to pay 01 up to 13 extension parts for purpose of payment in each case 02 and 1 extension part for remitter or payee 03 In the case of return remittances the content of extension parts cannot be given by the banks All the purpose of payment details required for the processing of such return remittances and reverse debits should therefore be included by the pa
60. translated to Dollar However it takes place only if translation is set for the external system and Oracle FLEXCUBE tag combination Mapping sub nodes with the corresponding nodes in the External System As part of the format maintenance you need to ensure that each child tag defined in the External Node corresponds to a pre defined tag in Oracle FLEXCUBE Step After capturing the name of the External Tag of the clearing network identify the corresponding Oracle FLEXCUBE Node Step Il After you select the Oracle FLEXCUBE node the sub nodes child nodes also called child tags linked to the selected node will be displayed in the drop down list available for the Oracle FLEXCUBE Tags You can key in the appropriate external sub node belonging to the External Node specified earlier and map it to the corresponding Oracle FLEXCUBE sub node tag Example Assume that the External Node is 10 and consists of the following tags e RECORD CODE e CONTRACT NUM e BRANCH e CUSTOMER The corresponding Oracle FLEXCUBE node is PAYMENTS COLLECTIONS and the following are the Oracle FLEXCUBE tags that belong to it e CONTRACT _REF_NO e BRANCH_OF_INPUT e CUSTNO e CPTY_NO e CUST_AC_NO Therefore you need to maintain the following mappings CONTRACT_NUM CONTRACT_REF_NO BRANCH BRANCH_OF_INPUT CUSTOMER CUSTNO 2 39 ORACLE If for an external tag there is no corresponding Oracle FLEXCUBE tag you can use the
61. typing IFDTXNGR in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 2 49 ORACLE Transaction Group Summary Authorization Status Record Status Metwork Id Clearing Message Group File Mask File Extension _Refresn _Reset Records per page 15 EIE Ala 0 Authorization Status Record Status Network Id Clearing Message Group File Mask File Extension Authorized DTAOQPMG DT AS 95 0 Sr Sh S61 Ss Authorized DTAIPCG ATA SH Authorized DTAOPCG DT AWS 95 0 So rr Soh S61 Ss Authorized DTAIGPAY ATAUS Authorized DTAIGPAY ATA SH Authorized DTAOQGPAY DT AUS 95 0 Sr Soh S616 s tet tet tet tet tet tet tet Authorized DTADGPAYI DTAUJUS Sd m h i ws In the above screen you can base your queries on any or all of the following parameters and fetch records e Authorization Status e Record Status e Network Id e Clearing Message Group e File Mask e File Extension Select any or all of the above parameters for a query and click Search button The records meeting the selected criteria are displayed e Authorization Status e Record Status e Network Id e Clearing Message Group e File Mask e File Extension 2 2 Outgoing Clearing Upload For the actual message hand off you have to manually trigger the event from Oracle FLEXCUBE You also need to specify the network and the clearing message group for which the hand off file has to be created This file in ASCII form
62. u can select the account from the option list provided e Single Contract will hand off details of a specific contract If you select only the network and message group the system will hand off all the contracts irrespective of the branches customers and accounts involved for the selected combination For hand off you should also specify the following File Path You can also specify the path for storing the hand off file When you trigger the process the hand off file will be picked up from the path you specify here If you do not specify a path the file will be picked up from the path specified for the selected message group At the time of implementation of Oracle FLEXCUBE the implementer will create the following five folders in the file path that you specify in the Handoff of Clearing Details screen if not specified the folders will be created in the path maintained for selected message group 2 51 ORACLE e in folder e out folder e wip folder work in progress e fccarea folder for Internal logging e debug folder Handoff Grouping You also have the option of grouping the transactions within the hand off file The following options are available for grouping e By Clearing Message Type if you select this option the transactions will be grouped as batches of different clearing message types that are allowed for the selected clearing message group e By Account Type this option will do the grou
63. uired If you have opted for this facility in Clearing Message Type screen and also check this box here the system will calculate the length of the particular line and subsequently writes the calculated value from the length starting position maintained for the particular message group e Starting Position This field indicates the position from which the calculated value has to be written into e Length ORACLE 2 48 This indicates the length for the line Example Let us assume that the length of the transaction line is about 300 The line attributes indicated are e Start position 6 e Length of position 5 The calculated value will be 300 and positions 6 to 10 will denote the length of the line Oracle FLEXCUBE automatically writes the calculated value from position 6 to 10 as 00300 Click Clearing Msg Type Allowed tab invoke the following screen Transaction Group Maintenance Network Id DTA Key Start Position Clearing Message Group DTAOGPAY1 Key Length Group Description Include Reject Process Direction Incoming Outgoing 10f1 DTAOGPAY 1 Maker M35718 Date Time 2011 12 31 14 43 32 Mod No 1 Checker 435718 Date Time 2011 12 31 14 44 15 Record Status Open Authorization Status Authorized 2 1 12 Viewing Transaction Group Details You can view the transaction group details using Transaction Group Summary screen You can invoke the Transaction Group Maintenance screen by
64. umerical data unpacked numerically packed numerical data packed plus sign The DM amount is entered in this field for purpose of information Structure and clarifications concerning DTA messages 1 constant part continued 2 8 ORACLE Remitter payee Remitter name left justified the shortest possible designations should be used In the case of BSE GSE text constant CHEQUE NUMBER empty space 13 digit cheque number from Field 5 of the coding line Left justified 2 9 ORACLE 16 2 alpha The shortest possible entries should be made The details at the Start of this field should be left justified and should be such that the beneficiary would intend to access mechanically in the case of remittances for example building society account number insurance number invoice number or which the payee requires for debits if the payment is sent back to him as unpaid or non executable Purpose of payment Or In case of BSE X 40 In case of GSE text constant EINR BEI LZB inward remittance to national central bank 13 digit presenter number of the presenter to the LZB from Field 5 of the coding line of the consolidated voucher or from Field 8 of the individual data record of the tape accompanying the voucher In the case of BZU exactly 13 positions Left justified 2 10 Free format text This field can contain a shor
65. unt Number oooo000033 in To Ooooo00033 a To DOOOOOOOSS To o000000033 DOOOOOOOSS ooooooo0sS To o000000033 in oo00000033 ORACLE 2 3 e File Name The name of the hand off file in ASCII format e Amount Total the sum total of the amount involved in all the transactions that are handed off e Account Total the sum total of all the accounts in the transactions The account number is anumeric value The system will add the account numbers involved in each transaction to display this value On confirmation click the Ok button of the details displayed in the Dispatch screen the upload file gets created in the path specified The system will then move the file from the wip area to the out folder Prior to moving the file it will retain a copy of the hand off file in the fcc area as backup This marks the successful completion of the hand off process At this stage if you want to cancel the hand off process click on Exit or Cancel button Incoming clearing upload Just like the hand off process the upload process too needs to be manually triggered from Oracle FLEXCUBE You can trigger the message upload event through the Incoming Incoming Clearing Upload screen invoked from the Application Browser You can invoke the Incoming Clearing Upload screen by typing IFDINDET in the field at the top right corner of the Application tool bar and clicking the
66. verse entry in view of accidental double DTA payment Standing order credit entry Credit entry for salary wages interest Asset creating action VL Asset creating action under EZU collection Remittances by public cash offices Return remittances Remittance credit from abroad Remittance credit with check digit protected classification data Credit entry for neutral remittance payment slip Credit entry for a donation payment There is no obligation on the part of the Bank to enter the text code supplement 888 51220 1221 51230 51240 51241 If the remitter payee is a non resident within the meaning of the Foreign Trade and Payments Ordinance the text code supplement 000 should be supplemented by 888 if the payment amount exceeds 12 500 Euros The text code supplement 888 should be changed by the bank of the beneficiary the paying agency while printing out the account statements or the debit credit vouchers in the indication text Follow AWV Disclosure Requirements Information under 0800 1234111 As for all remittances it also applies to remittance of a non resident to a resident there is an identification obligation if there is a negative check digit calculation or a missing target account number in the case of a negative check digit calculation the payment exchange record must be identified with the text code supplement 444 for payments up to 12 500 Euros for payments e
67. xceeding 12 500 Euros the text code 2 26 ORACLE supplement 844 should be used Remittances in which the beneficiary account number is not mentioned should be marked with the text code supplement 445 account number missing for payments up to 12 500 Euros For payments exceeding 12 500 Euros such remittances from a non resident to a resident should be identified with the text code supplement 845 The alphabets nn should be replaced by the original text code of DTA payments that have been executed twice by mistake Thereafter the reverse entry for the accidental double DTA entry should be identified with 05519 The alphabets nn should be replaced by the original text code from Field 7 a of the BSE GSE data record The alphabet X should be replaced by the relevant number of the encoded Ground for Return 0 for RETURNED CHEQUE 1 for ACCOUNT CANCELLED Z for ACCOUNT NO BANK CODE NUMBER WRONG 5 for STOPPED CHEQUE 6 for DATA ERROR TRAVELLER S CHEQUE T for GSE DOCUMENT NOT PRESENTED The alphabet X should be replace by the relevant number of the encoded Ground for Return 0 no entry 1 for ACCOUNT CANCELLED 2 for ACCOUNT NUMBER FALSCH or SAVINGS ACCOUNT ACCOUNT NO NAME NOT IDENTICAL the relevant text constant is to be allocated 3 for NO PAYMENT PRE AUTHOR
68. y the File Clearing Message Type that needs to be created On initiation the system first checks if there is any recovery operation is required If required it is handled first For the given clearing message type all products for which the file needs to be created will be picked up from the Product Mapping Clearing Message Type maintenance Since it is possible for the file to have a batch grouped on an account too the system will pick up the corresponding flag for the file The system will select the relevant records from the Message Maintenance for a given message type The file level attributes that are maintained will be picked up from File Clearing Message Type These are gt File Name gt File Extension 2 56 ORACLE File Path Session Timeout Number of Resends Number of Transactions in a file gt Number of Transaction in a Batch Vv Vv V WV e Contracts pertaining to each product selected from the Product Mapping Clearing Message Type maintenance will be picked up for processing for the Clearing File e The sequence that is followed during the processing is gt File Header Records FH gt Message Header Records MH gt Message Records MR gt Message Footer Records MF gt File Trailer Records FF e The following batch totals are assumed for the trailer records gt Total for Accounts gt Total of Amounts gt No of Records in the Message e Each record Is locked before the data in the record i
69. yee or the client in the constant part of the data recorded C see explanations concerning Field C 16 This means that when the payment direct debit is initiated by the customer in DTA format the customer should not use any of the extension part for describing the purpose of payment This is because if the bank rejects the same for any reason bank will use the extension records to give the reason for rejection date of rejection etc So there is a risk of purpose of payment getting over written by the rejection message if customer uses the extension part The purpose of payment should be intact as much as possible even in the rejection message Also there is a specific format in which the rejection details need to be written which is given in Section 4 Length in Data Content Description Comments bytes format 1 2 numerical Identifier of the 01 name of extension part beneficiary or party liable to pay 02 purpose of payment 03 name of remitter or payee 2 11 ORACLE Beneficiary or party Left justified liable to pay purpose of payment remitter or alpha alpha numerical data left aligned blank positions X 40 numerical numerical data unpacked numerically packed numerical data packed plus sign Structure and clarifications concerning DTA messages Data record E end of file label of data carrier The data record E is for reconciliation it is present only once for every logical file 7 O binary L

Clearing Interface Oracle FLEXCUBE Universal Banking Release

Contents

Download Pdf Manuals

Related Search

Related Contents