Direct Exchange Notes on the Electronic Interface Technical Documentation

Size: px
Start display at page:

Download "Direct Exchange Notes on the Electronic Interface Technical Documentation"

Transcription

1 Page 1/Page 75

2 Table of Contents 1. Introduction 5 2. Overview of Available Banking Services 6 3. Formats: File-Naming Conventions 7 4. Data Exchange/Communication Delivery of Files to Eingang Directory Collection of Account Information in Ausgang Directory 9 5. Establishing a Connection Process Encryption E-Documents Introduction Overview of E-Document Services via Direct Exchange Download Steps for E-Documents File Names Metadata Separate XML File Structure of the XML File Included Metadata Available Documents Formats DTA Payment Orders LSV+ Collections Credit Transfers Referencing between pain.001 and pain Salary and Pension Payments Type of Booking, Type of Display, and Deadlines for Submission SEPA Direct Debit Payment Status Report Account Statement (MT940 and Provisional Bookings/Intraday (MT942) Credit Suisse Account Statement (MT940) Credit Suisse Provisional Bookings/Intraday (MT942) Structure of Field 61 (Credit Suisse) Structure of Field 86 (Credit Suisse) BESR (ESR Type3) Processing Logs 25 Page 2/Page 75

3 8.1 Purpose and Prerequisites Overview of Processing Filegate Framework DTA Processing LSV+-Processing Schema Structure Processing Log DTA Processing Log Log Structure File Summary Information on Payment Groups Rejected Payments Severe Errors/Reason for Rejection Scenarios Processed Rejected LSV + Processing Log Log Structure FileDetails Payment Group Details Validations Scenarios Error-Free File File without Serious Errors File with Severe Errors Rejected File Double Transmission of File Test File Error Messages DTA Error Messages LSV+ Error Messages E-Documents: Feeder Applications, Group Names and Document Types Feeder Application ID and Group Names Document Types: Payment Transactions Document Types: Securities Document Types: Statement of Investments/Investment Performance Document Types: Mortgages Document Types: Account Records Document Types: Marketing/Bonus Points 70 Page 3/Page 75

4 11. Appendix Appendix A: Filegate Headers Appendix B: Types Appendix C: Glossary 75 Page 4/Page 75

5 1. Introduction Direct Exchange is the electronic interface for connecting large systems to the Credit Suisse payment transaction infrastructure. Using Direct Exchange, our clients can automatically execute all payments (DTA format) from their ERP solutions as well as LSV+ collections. They automatically receive the necessary data for comparison in Accounting, can collect information on account administration (MT940/MT942), and retrieve their e-documents. The client does not log into Direct Exchange, but simply sends the relevant files to the bank. These files are encrypted and enciphered, and on request, electronic certificates and/or line encryption may be agreed upon for additional security. Credit Suisse checks the client authorization on the basis of the agreed rights and executes the instructions. Alternatively, the client can also send individual orders, needing separate approval by means of a form. The openness and flexibility needed for large systems is achieved by the use of standards such as FTP, MQ or SWIFT FileAct SSL, SSH, Secure+ and VPN for encryption of communication and data transfer also across public networks (public internet) as well as through proven file transfer products supported by numerous systems. Due to the implementation costs, Direct Exchange is only suitable for large corporate clients. Our Electronic Banking experts will be pleased to help you choose the most suitable delivery interface for your company. You can reach us on freephone number , Monday through Friday, from 07:30 to 17:30. Further information on electronic banking and additional bank services can also be found at and Page 5/Page 75

6 2. Overview of Available Banking Services Depending on the type of client connection involved, Direct Exchange allows access to a wide range of banking services. The following overview table details these. Table 1: Overview of Direct Exchange bank services No. Bank service Description Client sends Client receives Same-day execution possible until 1 DTA Multiple payment order, multiple booking and display 07:00 2 DTA without electronic signature Multiple payment order, to be approved separately, multiple booking and display 07:00 3 DTA express Multiple payment order, multiple booking and display 12:00 4 DTA dispo Individual payment order, individual booking and display 14:00 5 DTA single Multiple payment order, individual booking and display 07:00 6 DTA single express Multiple payment order, individual booking and display 12:00 7 DTA test Test payment 8 DTA processing log Banking confirmation at file and payment level 9 LSV + /BDD Collection order 10 LSV+ without electronic signature Collection order, to be approved separately 11 LSV + test Test collection 12 LSV + processing log Banking confirmation at file and collection level 13 BESR BESR credit advice 14 MT940 End-of-day account statement for Credit Suisse 15 MT942 Intraday account statement Provisional bookings (non-binding) for Credit Suisse 16 E-Documents Bank records and documents electronically as a PDF file 17 Credit transfer Credit transfer in accordance with the Swiss ISO payments standard, in pain.001 format 18 SEPA direct debit Collection order in accordance with SEPA direct debits, in pain.008 format 19 Payment status report Payment status report in accordance with the Swiss ISO payments standard, in pain.002 format See chapter Page 6/Page 75

7 3. Formats: File-Naming Conventions When data is sent to, or delivered from, Direct Exchange, the following naming conventions must be adhered to for automatic further processing: Table 2: Overview of file naming conventions No. Bank service Description Directory File name 1 DTA Multiple payment order, multiple booking and display 2 DTA without electronic signature Multiple payment order, to be approved separately, multiple booking and display 3 DTA express Multiple payment order, multiple booking and display 4 DTA dispo Individual payment order, individual booking and display 5 DTA single Multiple payment order, individual booking and display 6 DTA single express Multiple payment order, individual booking and display Extension for transmission Extension Incoming DTAS_<contract>_<date>_<time> TMP TXT Incoming DTAO_<contract>_<date>_<time> TMP TXT Incoming DTAE_<contract>_<date>_<time> TMP TXT Incoming DTAD_<contract>_<date>_<time> TMP TXT Incoming DTAN_<contract>_<date>_<time> TMP TXT Incoming DTAX_<contract>_<date>_<time> TMP TXT 7 DTA test Test payment Incoming DTAT_<contract>_<date>_<time> TMP TXT 8 DTA processing log Banking confirmation at file and payment level Outgoing Collective file: VPDTA_<contract> One-time original file: VPDTA_<contract>_<date>_<time> 9 LSV + /BDD Collection order Incoming LSVS_<contract>_<date>_<time> TMP TXT TMP XML 10 LSV+ without electronic signature Collection order, to be approved separately Incoming LSVO_<contract>_<date>_<time> TMP TXT 11 LSV + test Test collection Incoming LSVT_<contract>_<date>_<time> TMP TXT 12 LSV + processing log Banking confirmation at file and collection level Outgoing Collective file: VPLSV_<contract> One-time original file: VPLSV_<contract>_<date>_<time> 13 BESR BESR credit advice Outgoing Collective file: BESR_<contract> One-time original file: BESR_<contract>_<date>_<time> TMP TMP XML TXT Page 7/Page 75

8 No. Bank service Description Directory File name 14 MT940 End-of-day account statement for Credit Suisse Outgoing Collective file: MT940_<contract> One-time original file: MT940_<contract>_<date>_<time> Extension for transmission Extension TMP TXT 15 MT942 Intraday account statement Provisional bookings (non-binding) for Credit Suisse 16 E-Documents Bank records and documents electronically as PDF 17 Credit transfer Credit transfer in accordance with the Swiss ISO payments standard, in pain.001 format 18 SEPA direct debit Collection order in accordance with SEPA direct debits, in pain.008 format 19 Payment status report Payment status report in accordance with the Swiss ISO payments standard, in pain.002 format Outgoing Outgoing Collective file: MT942_<contract> One-time original file: MT942_<contract>_<date>_<time> E-Documents (PDFs) Collective file: EDOCS_<contract> One-time original file: EDOC_<contract>_<date>_<time> Metadata Collective file: edoc_metadata_<contract> One-time original file: edoc_ metadata_<contract>_<date>_<time> TMP TMP TXT Incoming PN1_<contract>_<date>_<time> TMP XML Incoming SDDE_<contract>_<date>_<time> TMP XML ZIP Metadata: XML Outgoing SDDSM_<contract>_<date>_<time> TMP XML Page 8/Page 75

9 4. Data Exchange/Communication The client has one directory each provided for delivering and collecting files. 4.1 Delivery of Files to Eingang Directory The file delivered by the client must have the extension.tmp. Once file transfer is complete, the client must rename the same file with the extension.txt. This ensures that processing is triggered correctly. Definition of placeholders: <contract> 6 7 digit Direct Exchange contract number <date> Date of delivery in format YYYYMMDD <time> Time of delivery in format hhmmss Definition of file types: *.TMP File extension during delivery (file transfer) *.TXT File extension for automatic processing Documents that do not correspond to the naming conventions will be rejected. The client is responsible for ensuring that no files with duplicate names are delivered (e.g. see time details in the file name). Direct Exchange cannot tell if a file has been overwritten. Since the processing transfers and removes the delivered files from the Eingang directory, the files are no longer visible to the client. Where DTA files are concerned, both the diskette format and the magnetic tape format are supported. Please note that the debit account number must be in Multicash or IBAN format. 4.2 Collection of Account Information in Ausgang Directory Information for the services BESR, MT940, MT942, processing logs DTA, LSV+, and e-documents is provided in two file types in each case: (a) A collective file with a fixed name. It contains the complete cumulated current information and remains in the directory until collected by the client. (b) In addition, the data from each new updated delivery is made available to the client as backup and also made available as separate files (one-time original file). These files are automatically deleted after 60 days. Page 9/Page 75

10 The files delivered by the client must have the extension.tmp. The client is responsible for deleting the collective files once the transfer is complete. Definition of placeholders: <contract> 6 7 digit Direct Exchange contract number <date> Date of delivery in format YYYYMMDD <time> Time of delivery in format hhmmss Definition of file types: *.TMP *.TXT, *.XML or *.ZIP File extension during collection (file transfer) File extension for the files provided Page 10/Page 75

11 5. Establishing a Connection 5.1 Process The Direct Exchange connection is established within the framework of an IT project paid for on a time and materials basis. This is commissioned by the responsible IT unit of the client. Technical implementation on the bank server side is carried out by Fides Treasury Services, a subsidiary of the Credit Suisse Group. A project kick-off meeting is held to determine the services to be provided by the various partners involved. Project start To permit the implementation to be effected efficiently, the client should appoint an IT project manager, responsible for technical coordination on the client side. A preliminary meeting together with the client IT project manager lays down the general technical requirements (e.g. IP address, type of connection and encryption desired). These are defined in a document that includes the following points: Direct Exchange contract number (predefined by Credit Suisse) Full company name (Department) Client contact person for initial technical clarification (internal or external; IT project manager, responsible for technical coordination and forwarding of information on the client side) Credit Suisse contact person Fides Treasury Services contact person Fixed IP addresses for the connection to be established Preferred connection type (FTP, etc.) Technical information on the type of connection chosen by the client (FTP Client, Nodes, MQ Queue set, certificate type, etc.) Information on the type of encryption desired (See table in Section 5.2) Project realization As soon as the general technical requirements are defined, the handover to Fides Treasury Services takes place. Fides organizes a kick-off meeting for project commencement and further planning. Establishment of the connection is then generally carried out as follows: Establishment of a VPN (Virtual Private Network) if desired Establishment of actual connection Testing of delivery and collection by client Determination of correct functioning Project conclusion meeting: A debriefing form must be completed at this meeting. Amongst other things, it contains the type of connection and encryption chosen. Operation After conclusion of the project, the client advisor is once again responsible for all client queries. Page 11/Page 75

12 5.2 Encryption The kind of encryption is determined by the client and may consist of a software or hardware solution. Credit Suisse recommends that individual data packets are encrypted before being transmitted via a communication protocol, to eliminate unauthorized access. The sender and the recipient always remain unencrypted. Figure 1: Overview of communication type and software encryption Communication type Software encryption FTP MQ Fileact SWIFT Other type of communication Encryption at network level Page 12/Page 75

13 6. E-Documents 6.1 Introduction E-documents are digitally signed bank records that are delivered electronically. They are identical to the paper versions. For example, payment-related debit advices, account statements, and fund settlements can be sent as e-documents. The key benefits of e-documents for you, the client: As the records are not sent by post, they are often available more quickly. Using less paper helps to protect the environment The digital signature confirms that the electronic documents were created by Credit Suisse and that they have not been altered. Large selection of documents available Further information can be found at Overview of E-Document Services via Direct Exchange A new directory is being set up in Direct Exchange, via which e-documents can be retrieved. In addition to the e-documents in PDF format, a separate XML file of metadata from the PDFs is also delivered. This metadata contains useful information on the e-documents which can be used for a search, or with which your software can assign the e-documents to individual users or accounts, for example. 6.3 Download Steps for E-Documents The following steps for downloading e-documents are possible, depending on the software used. Downloading of the e-documents and XML file via a new E-documents session Allocation and granting of user rights in the software Checking of digital signature and storing of the verification document Archiving of e-documents: Electronic archiving as required by law using automated processes spares you the previously time-consuming archiving of paper documents and saves HR and archiving costs. Overview of e-documents, search function. The following points should be noted regarding downloads: E-documents are downloaded as PDF files with accompanying XML file containing metadata Once the PDFs and XML file have been retrieved, they are deleted from the Direct Link server. I.e. they must be saved by the client to be retained. We recommend a regular download of e-documents. Availability: E-documents become ready for delivery every hour between 5 a.m. and 6 p.m. The greatest volume is to be expected in the morning. During end-of-quarter processing, there may be a delay in bank records becoming available, owing to the high volume of data. Page 13/Page 75

14 User Rights Credit Suisse activates e-documents for each Direct Exchange user contract. Thus, e-documents can be received via the Direct Exchange interface for as many accounts and safekeeping accounts as wished. The access rights must be set up through the client s own software. Checking of Digital Signatures All Credit Suisse e-documents bear digital signatures. The digital signature forms part of the PDF document. A digital signature confirms the following: 1. The documents were issued by Credit Suisse. 2. The documents have not been altered. The signature can be checked by the software. You can find more information on digital signatures at under Digital Signature. 6.4 File Names The name of the PDF will contain a three-digit serial number: <pdf_name>_<3-digit-runningnumber>.pdf; the file name for each individual e-document is thus unique. The first document to be downloaded will be given the serial number 000. The number will increase by 1 for each subsequent download. The metadata file will be called: edoc_metadata_<contract>_<date>_<time>.xml, in the collective file metadata file edoc_metadata_<contract>.xml. 6.5 Metadata Separate XML File E-documents are always made available as PDF files. Alongside the actual business data (PDF files), an XML file is sent for each transport (successful transmission of PDFs) containing the metadata from all the PDFs being delivered. The XML file contains references to the e-documents in question as well as metainformation. You can find the name of the XML file in section Structure of the XML File The XML file is structured as follows: Figure 2: Structure of the XML file Page 14/Page 75

15 6.5.3 Included Metadata The XML file contains the following metainformation for each e-document. Further metadata may be added in future, e.g. the IBAN number. Metadata on the E-Document No. Field Name Mandatory Status Brief Description 1 XC101_RECIP_CIFNR Y Recipient CIF associated with the document 2 XC101_DOC_TYP Y Document Type (Four char code which uniquely identifies the document type in EOS 1 ) Explanation Possible Values/ Field Formats Attributes Mailbox CHAR(12) DIT Number 3006 CHAR(4) 3 XC101_DOC_TRG_FRMT Y PDF In future, documents possible in other formats than PDF 4 XC101_APPL_ID Y Application ID Possibility for Software to group into payments, securities etc. PDF BE01, WS80, AIS etc., see chapter 10 CHAR(3) CHAR(8) 5 XC101_DATE_BEVENT Y Business Event Date Booking date dd.mm.yyyy DATE 6 XC101_TS_INREP Y Timestamp which shows when document was inserted into EOS repository TIMESTMP 7 XC101_IS_ORIGINAL Y Flag showing if original or copy. Only possible values are Y/N Y or N CHAR(1) 8 XC101_IS_SIGNED Y Flag indicating whether document has digital signature or not. Only possible values are Y/N Software can make a check of the signature Y or N CHAR(1) 9 XC101_DOC_LANG_COD Y Document Language code 1, 2, 3, 4 for D, F, I, E respectively. CHAR(1) 1 EOS is the name of the application that produces the e-documents. Page 15/Page 75

16 No. Field Name Mandatory Status Brief Description 10 XC101_OWNER_CIFNR Y Owner CIF number Explanation Possible Values/ Field Formats Attributes CHAR(12) 11 XC101_TYP_RELATION Y Type of account number, e.g account, depot or Money market Depot, Account or CIF 65,66,67 for CIF, Depot or Konto account CHAR(2) 12 XC101_TYP_BU_RENUM Y Account Number/ Deposit No/CIF No Value in this field depends upon XC101_TYP_RELAT ION CHAR(20) 13 XC101_CURRENCY N Currency ISO currency code CHAR(3) 14 XC101_AMOUNT N Amount DEC(31,8) 15 XC101_DATE_VALUE N Date associated with the amount and currency 16 XC101_HAS_DOC_SUP N Flag indicating if there is any enclosures associated with this document 17 XC101_DOC_FILENAME Y Download File Name, including three-digit sequence number 18 XC101_IS_IMPORTANT N Flag which highlights the document in docbox. Only possible values are Y/N 19 XC101_UUID_DOC_C Y Document unique identifier value date (only if amount and currency available) For Marketing documents dd.mm.yyyy Y or N PDF name _name_yyyy-mmdd.123.pdf, e.g. Unique ID of each Document _extract_of_account_ pdf Y or N 9E8D04B DC- 8004CF02-EC1A2094 DATE CHAR(1) VC(254) CHAR(1) CHAR(35) Page 16/Page 75

17 Metadata on the Enclosures If field 16 XC101_HAS_DOC_SUP contains a Y, an enclosure is being delivered along with the e- document. Although there are further metadata on the enclosure, only the following are relevant: No. Field Name Mandatory Status Brief Description Explanation Possible Values/ Field Formats Attributes 1 XC109_SUP_FILENAME N Enclosure file name in PDF format. Test_Enclosure1.pdf VARCHAR(254) 6.6 Available Documents The various e-documents can be classified as follows: Application ID (Metadata field 4 XC101_APPL_ID ): AIS/IPC: Statements of investments, performance reports Bonus Points Mortgages Marketing WS80: Securities XBS: Account Documents ZV: Payment Transactions Document type/dit number (metadata field 2 XC101_DOC_TYP ): The DIT number can be used to assign the e-document to the appropriate area such as Payment Transactions or Mortgages. Document groups: Every DIT number is assigned to a document group. Section 10 contains a detailed listing of the feeder applications, document group names and document types. These tables can also be obtained from Credit Suisse in electronic form. Page 17/Page 75

18 7. Formats 7.1 DTA Payment Orders The DTA format is described in the SIC documentation under DTA Standards and Formats ( 7.2 LSV+ Collections Details on LSV+ collections can be found in the LSV + technical documentation or the SIC documentation on LSV + ( 7.3 Credit Transfers The Credit Transfer pain.001 format in accordance with the Swiss ISO payments standard is described in the SIC documentation under "Implementation Guidelines for Credit Transfers" ( The features specific to Credit Suisse are outlined in the chapters that follow Referencing between pain.001 and pain.002 At Credit Suisse, referencing of payments from pain.001 to pain.002 is completed on the basis of field 2.29 <InstrId> Salary and Pension Payments In accordance with ISO 20022, a marker can be entered in field 2.15 <Cd> to indicate salary or pension payments using the values "SALA" and "PENS". As the booking and display type in other fields (see chapter 7.3.3) can be managed flexibly and in a differentiating manner, field 2.15 has no influence on processing at Credit Suisse. For this reason, the "true" value is used for salary payments in field 2.3 <BtchBookg> and the "CND" value is used in field 2.20 <Prtry>. These values effect a global debit with a global debit display. Page 18/Page 75

19 7.3.3 Type of Booking, Type of Display, and Deadlines for Submission The type of booking, type of display, and deadlines for submission can all be managed flexibly in pain.001 at B level to suit client requirements. Table1: Type of Booking, Type of Display, and Deadlines for Submission for Credit Suisse Type of booking Field 2.3 <BtchBookg> Priority Field 2.7 <InstrPrty> Display management Field 2.20 <Prtry> Booking Display Deadline for submission blank STANDARD or blank blank Multiple booking Multiple display 07:00 blank STANDARD or blank NOA Multiple booking No display 07:00 blank STANDARD or blank SIA Individual booking Individual display 07:00 blank STANDARD or blank CND Multiple booking Multiple display 07:00 blank STANDARD or blank CWD Multiple booking Document list 07:00 blank HIGH blank Multiple booking Multiple display 12:00 blank HIGH NOA Multiple booking No display 12:00 blank HIGH SIA Individual booking Individual display 14:00 blank HIGH CND Multiple booking Multiple display 12:00 blank HIGH CWD Multiple booking Document list 12:00 false STANDARD or blank blank Multiple booking No display 07:00 false STANDARD or blank NOA Individual booking No display 07:00 false STANDARD or blank SIA Individual booking Individual display 07:00 false STANDARD or blank CND Multiple booking Multiple display 07:00 false STANDARD or blank CWD Multiple booking Document list 07:00 false HIGH blank Multiple booking No display 12:00 false HIGH NOA Individual booking No display 14:00 false HIGH SIA Individual booking Individual display 14:00 false HIGH CND Multiple booking Multiple display 12:00 false HIGH CWD Multiple booking Document list 12:00 true STANDARD or blank blank Multiple booking Multiple display 07:00 true STANDARD or blank NOA Multiple booking No display 07:00 true STANDARD or blank SIA Individual booking Individual display 07:00 true STANDARD or blank CND Multiple booking Multiple display 07:00 true STANDARD or blank CWD Multiple booking Document list 07:00 true HIGH blank Multiple booking Multiple display 12:00 true HIGH NOA Multiple booking No display 12:00 true HIGH SIA Individual booking Individual display 14:00 true HIGH CND Multiple booking Multiple display 12:00 true HIGH CWD Multiple booking Document list 12:00 Page 19/Page 75

20 7.4 SEPA Direct Debit The pain.008 format for SEPA direct debits is described in the SIC documentation under "Implementation Guidelines for SEPA Direct Debits". ( 7.5 Payment Status Report The pain.002 format for the payment status report is described in the SIC documentation under "Implementation Guidelines for Credit Transfers" and under "Implementation Guidelines for SEPA Direct Debits". ( 7.6 Account Statement (MT940 and Provisional Bookings/Intraday (MT942) The formats for account statements and provisional bookings/intraday of Credit Suisse accounts are described in sections through Credit Suisse Account Statement (MT940) Table 3: Structure of Credit Suisse account statement (MT940) Contents Format Example SWIFT header {1:F01CRESCHZZ080A }{2:I940X N2}{4: Reference no. 16x :20:XBS/050614/0001 Account no. 35x :25:4835/ [or IBAN on request] Sequence no. 5n[/5n] :28C:9/1 Opening balance 1!a6!n3!a15d :60F:C050808GBP1375,57 Transaction details 2 6!n[4!n]2a[1!a]15d 1!a3!c16x[//16x][34x] :61: D50,50NTRFNONREF//3M Information to account holder 3 6 * 65x :86:1019?33 Mr. John Test 36, Sackville Garden GB - Brighton?60Booking: CS client Bank account (SWIFT case without expenses)?23barclays Bank PLC Head Office 54 Lombard Street GB-London EC3P 3AH Final balance (booked) 1!a6!n3!a15d :62F:C050808GBP479,24 Final balance (value balance) 1!a6!n3!a15d :64:C050808GBP3845,64 Balance with post-value 1!a6!n3!a15d :65:C050809GBP5570,99 :65:C050810GBP53570,99 SWIFT tail -} 2 Field 61: see section Field 86: see section Page 20/Page 75

21 7.6.2 Credit Suisse Provisional Bookings/Intraday (MT942) Table 4: Structure of Credit Suisse provisional bookings/intraday (MT942) Contents Format Example SWIFT header {1:F01CRESCHZZ080A }{2:I942X N2}{4: Reference no. 16x :20:XBS/050614/0001 Account no. 35x :25:4835/ [or IBAN on request] Sequence no. 5n[/5n] :28C:9/1 Indicator for amount limit 3!a[1!a]15d :34F:GBP0, Date/time indicator 6!n4!n1!x4!n :13D: Transaction details 4 Information to account holder 5 6!n[4!n]2a[1!a]15d 1!a3!c16x[//16x][34x] :61: D50,50NTRFNONREF//3M * 65x :86:1019?33 Mr. John Test 36, Sackville Garden GB - Brighton?60Booking: CS client Bank account (SWIFT case without expenses)?23barclays Bank PLC Head Office 54 Lombard Street GB-London EC3P 3AH Intraday Intraday Transaction details 4 6!n[4!n]2a[1!a]15d 1!a3!c16x[//16x][34x] :61:050808D50,50NTRFNONREF//3M Provisional bookings Information to account holder 5 6 * 65x :86:1019 Provisional bookings SWIFT tail -} The provisional bookings (non-binding) are placed after the Intraday and have no booking date in field Structure of Field 61 (Credit Suisse) Table 5: Structure of transaction details Sub-field Sub-field Contents 1 6!n Value date (YYMMDD) 2 [4!n] Booking date (MMDD) [with booking date for Intraday, without for provisional bookings] 3 2a Debit/Credit (D or C)/for cancellation, Reversal of Debit (RD) or Reversal of Credit (RC) 4 [1!a] Third character of currency code 5 15d Amount 6 1!a3!c N plus business case identification (S plus message type for SWIFT) 7 16x Client reference, if available (from Additional supplier text ) 8 [//16x] CS reference (edited order number) 9 [34x] Additional explanations and/or client references (if too little space in sub-field 7) 4 Field 61: see section Field 86: see section Page 21/Page 75

22 Table 6: Business case identification (sub-field 6) ID code Business case identification ID code Business case identification BOE Bill of exchange DIV Dividend warrants BRF Brokerage fee EQA Equivalent amount CHG Charges and other expenses ECK Eurocheques CHK Checks FEX Foreign exchange CLR Cash letters/checks remittance INT Interest CMI Cash management item - No detail LBX Lock box CMN Cash management item - Notional pooling LDP Loan deposit CMS Cash management item Sweeping MSC Miscellaneous CMT Cash management item Topping RTI Returned item CMZ Cash management item - Zero balancing SEC Securities (used when entering a principal amount) COL Collections (used when entering a principal amount) STO Standing order COM Commission TCK Travelers checks DCR Documentary credit (used when entering a principal amount) TRF Transfer DDT Direct debit item VDA Value date adjustment (used with an entry made to withdraw an incorrectly dated entry - it will be followed by the correct entry with the relevant code) Structure of Field 86 (Credit Suisse) A unique booking text code (Extended Product Code EPC) identifies each transaction type. The codes are assigned to the number ranges for a specific kind of business. A detailed list of the individual EPCs can be found at It is recommended that the current version of the EPC list is obtained from the internet on a regular basis so that new codes can be assigned. Table 7: Extended Product Codes EPC Business transaction Payment transactions Check Securities Treasury/Money market Treasury/Foreign exchange Treasury/Precious metals Credit business Mortgages Counter Various charges/commissions Other Page 22/Page 75

23 The business case details are each flagged with a leading trigger tag according to the table below. The individual details are separated using the? delimiter. Table 8: Trigger tags Trigger tag Description 20 Form text 21 Your reference 22 Client reference 23 Account at (bank check: bank concerned) 24 Conversion text 25 Our expenses 26 Third-party expenses 27 Total expenses 28 VAT 32 Order issued by 33 Beneficiary 60 Reason for payment 61 Free text 62 Special text Page 23/Page 75

24 7.7 BESR (ESR Type3) In Direct Exchange, the BESR records are attached to the existing BESR collective file every day. If the client does not collect the BESR record on a daily basis, the collective record will contain multiple total records. Further information can be found in our technical documentation on the BESR received payments. Page 24/Page 75

25 8. Processing Logs 8.1 Purpose and Prerequisites Section 8 describes the processing log generated by the Credit Suisse Filegate Business Engine while processing the DTA and LSV+ files. These specifications are oriented to developers of applications that use the XML processing log generated by the Credit Suisse Filegate Business Engine. Since the following descriptions are of a technical nature, it is assumed that the reader is familiar with XML and the associated schemas. Knowledge of these is indispensable in order to understand the following explanations. 8.2 Overview of Processing Filegate Framework In the Filegate framework, files are processed which fulfill the SIC (Swiss Interbank Clearing) prescribed DTA and LSV+ norms (see also Payments present in the original file are grouped according to specific criteria and then processed DTA Processing Payments belonging to a DTA file are grouped according to the following criteria: Client ID Debit account Currency Value date Salary flag The most important characteristics of DTA processing include: Payment orders are created immediately upon processing the file and sent to the payment system. Only fundamental validations are carried out on the value day. The payment processing system can contain further validations that may affect the closing date. Files with payment errors are, depending on the circumstances, partially processed if the partial processing function is activated. Specific types of error are classified as being correctable. If the correction function is activated, the payment is processed after correction. A file containing severe errors is rejected independently of the payment status. Severe errors include, for example, an invalid file format, an invalid total amount (TA890) etc. Page 25/Page 75

26 8.2.3 LSV+-Processing Payments and debit orders belonging to an LSV file are grouped according to the following criteria: BC number CR-FI Credit account number LSV identification CR Value date Currency (in general, an LSV file contains payments in a single currency, either CHF or EUR) The most important steps in processing an LSV file are: 1. Preliminary processing. The application starts preliminary processing immediately after receiving the LSV file. It comprises the following procedures: Official validation of the correctness of all entries Generation of payment groups on the basis of sort criteria Authorization of the payment groups Company validations 2. Main processing. Based on the value date, the application performs the main processing of the file. As part of the main processing, the application generates messages of the type D10 and the transaction is executed. 3. Final processing. After main processing, the application creates a one-off summary of results. To inform the originator about file processing, validation and the results of the authorizing, the application generates a processing log during preliminary processing, which is sent immediately. This gives the originator sufficient time to react if an error has occurred. At this point, the processing log is generated, based on the information available after preliminary processing. The file is then further processed on the value dates. Since the log has already been created and transmitted, further processing is not contained in it. 8.3 Schema Structure The Filegate schema is split into four separate namespaces and thus into four different source files: filegate.xsd, types.xsd, lsv.xsd, and dta.xsd. The namespaces are split up as follows: Framework (urn:vo.framework.filegate.cs.csg.com): Here, elements are described at framework level. Types (urn:types.vo.framework.filegate.cs.csg.com): Data structures used in the framework, DTA, and LSV schemas. DTA (urn:vo.dta.filegate.cs.csg.com): Specific structures for DTA processing. LSV (urn:vo.lsv.filegate.cs.csg.com): LSV-specific data structures. Page 26/Page 75

27 The schema files are given once again here for reference purposes: types.xsd filegate.xsd dta.xsd lsv.xsd 8.4 Processing Log The structure of the processing log is defined at framework level and is composed as follows: The filegateheader element describes the header information created for processing of the DTA or LSV file. It contains client-specific information and settings for the channel used to transmit the file. This structure is described in more detail in Appendix A. The protocol element is an abstract element that acts as a placeholder for the processing log generated by the Business Engines for LSV+ or DTA. More information on the LSV and DTA logs can be found in the sections referring to these logs. processingprotocollist element With the help of this element, multiple processing logs can be grouped. Note that the Filegate Business Engine transmits the processing log as soon as a file is processed. The individual logs are not grouped. This element can, however, be used by those client applications which receive the Filegate processing log. Page 27/Page 75

28 8.5 DTA Processing Log The processing log generated by the DTA Business Engine comprises the following information: Summary of the original file. Payment group data generated from the original file. These include Payment orders generated from the groups. Errors found at group level. Rejected payments Errors at file level or reason for rejection of the file Log Structure To be able to record all of the information given above, the DTA processing log is structured as shown below: Note that the display of specific information depends on the processing result. These are optional elements marked by dotted lines. dtaprotocol element File Summary This section contains a summary of the results of the data processing. The main elements are: state Gives the final status of the file (processed, rejected). errorpayments Number of payments rejected due to errors. Page 28/Page 75

29 paymentsforapproval Number of payments that must be approved manually. dateoftransmit Indicates when the file was received by Credit Suisse. The structure of the file summary is shown in the following. dtaprotocol/filedetails element Page 29/Page 75

30 Information on Payment Groups This, the most important part of the log, contains all the information on the payment groups generated from the original order file. The structure is described in the following sections. Payment group details Multiple payment groups can be generated from one DTA file, the information is structured as shown below. The paymentgroupdetails element can contain one or more paymentgroupdetail elements. dtaprotocol/paymentgroupdetails element Payment group detail (paymentgroupdetail) Details on a specific payment group are stored in the paymentgroupdetail element. The mfoid attribute gives the sequence number of this specific payment group in the file. The sub-elements are: mpodetail This element contains data on the master payment orders that have been generated from this group. Depending on whether any of the payments contain correctable errors, there may be one or two payment orders. If errors are present, the corresponding payment orders must be grouped separately from the error-free orders. This element is described in more detail in the next section. If the payment group is rejected, no payment order is created. In this case, the section only contains additional information on the group. totalamount Total amount of all payments for this group. totalerroramount Total amount of all rejected payments for this group. error Describes the errors found at group level. The most common structural details for this element can be found in the Appendix. If the group criteria contain a non-correctable error (degree of severity 20), the group is rejected. Page 30/Page 75

31 The paymentgroupdetail element is constructed as follows: paymentgroupdetails/paymentgroupdetail element Page 31/Page 75

32 Master payment order detail (mpodetail) This element describes the payment group more closely. It also contains information about the created master payment order sent to the payment processing system. The main elements are: orderreferencenumber Identification number of the generated payment order. It only exists if a payment order was created and the group was not rejected. intermediateaccount The credit account, which is generally an internal account, to which the group total amount is initially credited before it is forwarded to the actual beneficiaries. visumrequired States whether the generated payment orders must be approved. noofvisumsrequired Number of approvals required if applicable. Page 32/Page 75

33 paymentgroupdetail/mpodetail element Page 33/Page 75

34 Rejected Payments Payments that have been rejected because of non-correctable errors are recorded in the paymenterrors element. Payment errors (paymenterrors) A paymenterrors element consists of a series of paymenterror elements, each describing individual payments. These payments do not form part of the generated payment orders. DtaProtocol/paymentErrors element Payment error (paymenterror) The term payment error refers to a specific payment containing an error. paymentdetail Describes the payment for which the error was determined. The structure is described in more detail in the following section. error At least one error that was determined for this payment. The structure is described in the Appendices. paymenterrors/paymenterror element Page 34/Page 75

35 Payment detail (paymentdetail) The main elements are: orderreferencenumber Identification number of the generated payment order. It only exists if the error is correctable, since rejected payments are not assigned to any payment order. seqnumber Sequence number of a specific payment in the original DTA file. type Transaction type of payment. pmtreferencenumber Combination of the originator ID (ATG-ID) and the transaction number for the payment. bnkclrid Identifier for bank clearing (not present for all types of transaction). accountnumber Beneficiary bank account number (not present for all types of transaction). valuedate Value date of payment according to the original file. If specific date processing rules are used, this value can be changed in the payment processing system. amount Amount of a specific payment. paymenterror/paymentdetail element Page 35/Page 75

36 Severe Errors/Reason for Rejection Severe errors are errors that occur at file level with a degree of severity of 30 and that lead to the entire file being rejected. Severe errors include, for example, an invalid file format or files that have been transmitted twice. This part of the log gives the reason for rejection of the entire file. Although in theory more than one error can occur, the log usually contains only one. dtaprotocol/severeerrors element Scenarios The schema for the DTA processing protocol contains specific optional elements, which may exist depending on the processing result. The different scenarios are described below on the basis of these optional elements. <dta:filedetail> is the only required element; it is always present Processed Fully processed This is the optimal scenario: All payments are error-free and the file has been successfully processed. In this case, only <dta:paymentgroupdetail> elements that describe the various payment groups created are present. Examples: VPDTA_ xml Partially processed In this case, a DTA file has only been partially processed. In addition to the element <dta:paymenterrors>, <dta:paymentgroupdetail> elements containing details of the payment groups processed and the main availability orders that have been created are also present here: For rejected payments Examples: VPDTA_ xml For rejected groups Examples: VPDTA_ xml Page 36/Page 75

37 Rejected Severe errors In this case, only the <dta:severeerrors> element is present, containing the error at file level. In this scenario, the file is in any case rejected, so no further payment details are present. Examples: VPDTA_ xml Payment errors A DTA file is rejected if payments contain errors and the partialprocessing flag contains the value False. No payment orders are created, and the <dta:paymenterrors> element contains details on the payments containing errors and a description of the errors. In addition, the <dta:severeerrors> element is present, giving the reason for the rejection. For errors at payment level Examples: VPDTA_ xml For errors at group level Examples: VPDTA_ xml 8.6 LSV + Processing Log The LSV processing log is created during preliminary processing of the LSV file. It offers an overview of the file processing and contains the following information: Details at file level The number of debit orders, total amount, file name, client ID, status, etc. Payment group details A list of payment groups with LSV ID, creditor account number, number of debit orders for the payment group, total amount for the payment group, requested value date, etc. Wrong entries This section contains validation errors at file level or debit order level. If validation errors occur at the file level, the file is rejected and no debit orders are processed. If the errors are in individual debit orders, only those containing errors are rejected. All others are processed. Page 37/Page 75

38 8.6.1 Log Structure The following sections describe the LSV processing log. fg:processingprotocol element fg:protocol element LSVProtocol element Page 38/Page 75

39 FileDetails LSVProtocol/LSVFileDetails element Contains a summary of the LSV file. Page 39/Page 75

40 The main elements are described in the following sections. LSVFileDetails/userId element ID of the user who transmitted the LSV file. LSVFileDetails/state element Gives the status of the file after preliminary processing. The following possible statuses exist for LSV files: preprocessed The Business Engine successfully completed preliminary processing of the file. Processing of individual groups will recommence on the corresponding value days. duplicatefile The application carries out a special check for duplicates, to avoid the same file being processed twice. Files rejected for this reason show this status. rejected The errors found in the LSV file are split into two groups: severe and non-severe. For severe errors at the file level, the file shows the rejected status. testprocessed If the application receives a test file that is then processed, the application determines the status as testprocessed. testrejected If a severe error is found in a test file, the file is rejected by the application and the file status is set to testrejected. LSVFileDetails/noOfPaymentGroups element This element contains the total number of payment groups discovered in the LSV file. LSVFileDetails/noOfErrorPaymentGroups element This element contains the number of payment groups which have an error. LSVFileDetails/noOfTxn element This element contains the number of payments (debit orders) without errors. LSVFileDetails/noOfErrorTxn element This element contains the number of payments (debit orders) with errors. Page 40/Page 75

41 LSVFileDetails/totalAmount element Total amount of file Payment Group Details The main elements are described in the following sections: LSVProtocol/mfoDetails element LSVProtocol/mfoDetails/mfoDetail element Page 41/Page 75

42 paymentgroup element PaymentGroup/orderDetails element Page 42/Page 75

43 PaymentGroup/creditor element Creditor/address element Page 43/Page 75

44 PaymentGroup/paymentSummary element PaymentSummary/totalAmount element MfoDetail/status element Gives the status of the payment group after preliminary processing has been completed. The following status details are possible for payment groups: readytoprocess The payment group has been successfully authorized and validated and will be processed according to the value date rules without further approval. approval1pendin The payment group has been successfully authorized and validated, but must still be approved. After approval, it is processed according to the value date rules. approval2pendin The payment group has been successfully authorized and validated, but must still be approved twice. After approval, it is processed according to the value date rules. Page 44/Page 75

45 rejected The payment group has been rejected due to the following validation error: Unauthorized user Wrong value date Wrong credit account number testnotprocess The payment group belongs to a test file. The payment group has been successfully validated and authorized. No further processing takes place. testrejected The payment group belongs to a test file. The payment group has been rejected due to a validation error Validations Validation errors found during processing are described with the aid of a general validation structure. Validation is carried out at two levels on an LSV file: File level These errors are stored in the lsvprotocol/validations element. There are two kinds of error at file level: Severe errors In this case, the entire file is rejected and no debit orders are processed. For example: Wrong total amount Non-severe errors If a data record field contains errors, these are not classed as severe errors. These data records are rejected and are not added to a payment group. For example: Empty value date Payment group level These types of error are found within payment groups. These payment groups are rejected and debit orders for these payment groups are not processed. These errors are stored in the mfodetails/validations element. The validations element acts as a placeholder for the various validation elements that describe an individual validation error. Page 45/Page 75

46 The validation element has the following structure and contains data record information as well as the errors. types:validations/validation element Data record information This part of the log describes the payment in which the validation error occurred. The fieldinfo element describes a specific field in this payment, and a fixed group of fields represents the data record information (see illustration below). types:validation/recordinfo element types:validation/recordinfo/fieldinfo element The following fields are shown: inseqno Entry sequence number of the debit order debitoraccid Number of debtor account for debit order creditoraccid Number of creditor account for debit order Page 46/Page 75

Customer Statement - MT940 with Structured Information To Account Owner

Customer Statement - MT940 with Structured Information To Account Owner General Information The MT940 customer statement message is an electronic message containing financial statement information for customers concerning their accounts. Danske Bank can send a MT940 either

More information

Format Description SWIFT MT940 Structured

Format Description SWIFT MT940 Structured Format Description SWIFT MT940 Structured Rabo Cash Management Colophon Title Format Description SWIFT MT940 Structured Version, date 3.331, November 2014 On behalf of Zakelijke Klantkanalen Contact address

More information

499.35 en (pf.ch/dok.pf) 11.2015 PF. EPO manual Electronic payment order via file transfer

499.35 en (pf.ch/dok.pf) 11.2015 PF. EPO manual Electronic payment order via file transfer 499.35 en (pf.ch/dok.pf) 11.2015 PF EPO manual Electronic payment order via file transfer Customer support Customer support for EPO Consulting & Sales Phone +41 848 888 900 (CHF 0.08/min. from a landline)

More information

Format Description MT940. Rabo Cash Management

Format Description MT940. Rabo Cash Management Format Description MT940 Rabo Cash Management COLOFON Title Format Description MT940 Version, date 2.4, January 2013 On behalf of Contact address FL-Services Rabobank Nederland, Croeselaan 18, Postbus

More information

480.84 en (pf.ch/dok.pf) 10.2015 PF. Manual PostFinance ISO messages for banks [pacs messages]

480.84 en (pf.ch/dok.pf) 10.2015 PF. Manual PostFinance ISO messages for banks [pacs messages] 480.84 en (pf.ch/dok.pf) 10.2015 PF Manual PostFinance ISO messages for banks [pacs messages] Customer service Enquiries concerning service ISO 20022 for banks PostFinance Ltd Customer Service Banks Mingerstrasse

More information

Implementation of ISO 20022: starter kit for software partners

Implementation of ISO 20022: starter kit for software partners Insert images: Swiss Post menu > image > insert image. For more images go to www.brandingnet.ch Technical details Full screen image size W 25.4 cm x H 19.05 cm equals W 1500 pixels x H 1125 pixels Resolution

More information

Deutsche Bank www.deutschebank.nl. Deutsche Bank MT940/942 format specifications

Deutsche Bank www.deutschebank.nl. Deutsche Bank MT940/942 format specifications Deutsche Bank www.deutschebank.nl Deutsche Bank MT940/942 format specifications Content 1. Introduction 3 2. SWIFT MT940 Customer Statement Message 4 2.1 MT940 Format 4 2.2 MT940 Tag & (sub)field Specifications

More information

Corporates. Current Account Overview of Prices and Conditions for Companies

Corporates. Current Account Overview of Prices and Conditions for Companies Corporates Current Account Overview of Prices and Conditions for Companies October, 205 Business Easy Package Simple and geared towards your needs as a small business, our comprehensive banking package

More information

Format description XML SEPA Credit Transfer. Format Description

Format description XML SEPA Credit Transfer. Format Description Format description XML SEPA Credit Transfer Format Description CONTENTS 1 SEPA CT Import format 3 1.1 SEPA CT import format description 3 1.1.1 Description 3 1.1.2 General characteristics 3 1.1.3 Difference

More information

Cards and Accounts Overview of Conditions

Cards and Accounts Overview of Conditions Cards and Accounts Overview of Conditions Updated 8/1/2015 Table of Contents General Notes 3 Package Services: Bonviva 4 Package Services: Viva 5 Private Accounts 6 Savings Accounts 6 Payment Transactions

More information

Q&A Payment Transaction Standardization in Europe and Switzerland

Q&A Payment Transaction Standardization in Europe and Switzerland Payment Transaction Standardization in Europe and Switzerland Version: October 2015 Payment Transaction Standardization in Europe and Switzerland General Introduction Starting February 1, 2014, Europe

More information

Corporate Access File Transfer Service Description Version 1.0 01/05/2015

Corporate Access File Transfer Service Description Version 1.0 01/05/2015 Corporate Access File Transfer Service Description Version 1.0 01/05/2015 This document describes the characteristics and usage of the Corporate Access File Transfer service, which is for transferring

More information

ODEX Enterprise. Introduction to ODEX Enterprise 3 for users of ODEX Enterprise 2

ODEX Enterprise. Introduction to ODEX Enterprise 3 for users of ODEX Enterprise 2 ODEX Enterprise Introduction to ODEX Enterprise 3 for users of ODEX Enterprise 2 Copyright Data Interchange Plc Peterborough, England, 2013. All rights reserved. No part of this document may be disclosed

More information

Service description. Corporate Access Payables

Service description. Corporate Access Payables Service description Corporate Access Payables Table of contents Page 2 of 12 1 INTRODUCTION... 3 2 STRUCTURE OF DOCUMENTATION... 4 3 AGREEMENT SET-UP... 4 4 AVAILABLE MESSAGE TYPES... 5 5 OFFERED PAYMENT

More information

TERMS AND CONDITIONS OF REMOTE DATA TRANSMISSION

TERMS AND CONDITIONS OF REMOTE DATA TRANSMISSION TERMS AND CONDITIONS OF REMOTE DATA TRANSMISSION I. Scope of services 1. The bank offers to its customers (account holders) data transmission by electronic means hereinafter referred to as remote data

More information

SEPA Direct Debit Implementation Guide. Version 1.7

SEPA Direct Debit Implementation Guide. Version 1.7 SEPA Direct Debit Implementation Guide Version 1.7 DANSKE BANK Table of contents 1 Change log... 3 2 Purpose of this document... 4 2.1 Target groups... 4 2.2 Help... 4 3 Introduction to SEPA Direct Debit...

More information

Business On Line File Gateway Guide for Customers

Business On Line File Gateway Guide for Customers Business On Line File Gateway Guide for Customers This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced

More information

BT 24 User Manual 1. Useful information... 4 2. Application access... 6 2.1 First log into BT24... 6 2.2 Subsequent logins into BT 24... 6 2.

BT 24 User Manual 1. Useful information... 4 2. Application access... 6 2.1 First log into BT24... 6 2.2 Subsequent logins into BT 24... 6 2. BT 24 User Manual 1. Useful information... 4 2. Application access... 6 2.1 First log into BT24... 6 2.2 Subsequent logins into BT 24... 6 2.3 Password changing... 7 2.4 How I reset the password... 8 2.5

More information

Cash Management Balance Reporting Specifications Version 2. Technical Reference Manual

Cash Management Balance Reporting Specifications Version 2. Technical Reference Manual Cash Management Balance Reporting Specifications Version 2 Technical Reference Manual 10/2005 Printed in the United States of America Copyright 2005 by BAI, Chicago, Illinois All rights reserved. No part

More information

Terms and Conditions for Remote Data Transmission

Terms and Conditions for Remote Data Transmission Terms and Conditions for Remote Data Transmission (Status 31 October 2009) 1. Scope of services (1) The Bank is available to its Customers (account holders) for remote transmission of data by electronic

More information

SIX Trade Repository AG

SIX Trade Repository AG May 2016 Please note: The SIX Trade Repository (SIX TR) has not yet been registered with FINMA. It is therefore not yet an authorized Swiss trade repository. The content of this documentation is without

More information

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC130-08 30 November 2012 (Version 7.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for

More information

Intra-day payment Frequently asked questions

Intra-day payment Frequently asked questions Intra-day payment Frequently asked questions Contents 1. THE MEANING, advantages and scope of intra-day payment... 3 1.1. What does the launch of intra-day payment mean?... 3 1.2. What advantages does

More information

HSBC Your Guide to SEPA. Capitalising on the opportunities

HSBC Your Guide to SEPA. Capitalising on the opportunities HSBC Your Guide to SEPA Capitalising on the opportunities Executive Summary Developed by the European Payments Council, the Single Euro Payments Area or SEPA expands on the vision behind the Euro to establish

More information

OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE

OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE Version 2.5 13.4.2016 OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE 2 (54) CONTENTS VERSION INFORMATION... 4 1 OUTGOING PAYMENTS, ISO 20022 APPLICATION GUIDELINE... 5 1.1 ISO 20022 MESSAGE DESCRIPTION

More information

SWIFT MT940 MT942 formats for exporting data from OfficeNet Direct

SWIFT MT940 MT942 formats for exporting data from OfficeNet Direct SWIFT MT940 MT942 formats for exporting data from OfficeNet Direct January 2008 2008 All rights reserved. With the exception of the conditions specified in or based on the 1912 Copyright Act, no part of

More information

FILE FORMAT OF PAYMENT ORDERS ACCEPTED BY CITIBANK EUROPE PLC FOR CITIBUSINESS DIRECT INTERNET BANKING

FILE FORMAT OF PAYMENT ORDERS ACCEPTED BY CITIBANK EUROPE PLC FOR CITIBUSINESS DIRECT INTERNET BANKING FILE FORMAT OF PAYMENT ORDERS ACCEPTED BY CITIBANK EUROPE PLC FOR CITIBUSINESS DIRECT INTERNET BANKING FILE FORMAT OF PAYMENT ORDERS for Citibank Europe plc, organizační složka CitiBusiness Direct Internet

More information

1.1. Overview... 5 1.2. Direct credits... 6 1.3. Direct debits... 9 1.4. Nab direct credits... 12

1.1. Overview... 5 1.2. Direct credits... 6 1.3. Direct debits... 9 1.4. Nab direct credits... 12 1.1. Overview... 5 1.2. Direct credits... 6 1.3. Direct debits... 9 1.4. Nab direct credits... 12 2.1. Overview... 16 2.2. Credit card transaction... 17 2.3. Credit card response... 20 3.1. Overview...

More information

LECTURE No.9 INSTRUMENTS OF PAYMENT

LECTURE No.9 INSTRUMENTS OF PAYMENT LECTURE No.9 INSTRUMENTS OF PAYMENT Cash and cash instruments The cashier s work consists in receiving cash and cash instruments such as cheques and other instruments ( documents of title to cash ) in

More information

Foreign Account Tax Compliance Act (FATCA) Foreign Account Tax Compliance Act (FATCA) FATCA Reports

Foreign Account Tax Compliance Act (FATCA) Foreign Account Tax Compliance Act (FATCA) FATCA Reports Foreign Account Tax Compliance Act (FATCA) August 2015 Foreign Account Tax Compliance Act (FATCA) FATCA Reports International Compliance Management Model (ICMM) Notifications User Guide FATCA Reports Foreign

More information

Migration of the customerbank

Migration of the customerbank Migration of the customerbank interface Information event for software companies Migration Payment Traffic Switzerland Credit Suisse AG, Michael Wunderl Zurich, 11 September 2014 Migration of the customer-bank

More information

Wire Transfer. Business Link. Creating a Wire Transfer Template. Wire Transfer Types. Wire Transfer Templates and Transactions

Wire Transfer. Business Link. Creating a Wire Transfer Template. Wire Transfer Types. Wire Transfer Templates and Transactions Wire Transfer Funds Mgmt Check Mgmt Reporting Administration Wire Transfers The Wire Transfer module provides a convenient and secure way to transfer funds between your accounts, or between your accounts

More information

Treasury Management Guide to ACH Origination Processing and Customer Service March 2012

Treasury Management Guide to ACH Origination Processing and Customer Service March 2012 Treasury Management Guide to ACH Origination Processing and Customer Service March 2012 This guide provides important information regarding ACH origination processing at PNC and addresses many frequently

More information

Electronic foreign currency payments, LUM2

Electronic foreign currency payments, LUM2 Electronic foreign currency payments, LUM2 Contents 1 Electronic foreign currency payment service... 3 2 Service agreement and testing... 3 2.1 Agreement... 3 2.2 Testing... 4 2.2.1 File transfer and processing...

More information

Cathay Business Online Banking

Cathay Business Online Banking Cathay Business Online Banking A QUICK GUIDE TO CATHAY BUSINESS ONLINE BANKING R6119 CATHAY 8_5x11 Cover V2.indd 1 6/11/13 5:50 PM Welcome Welcome to Cathay Business Online Banking (formerly known as Cathay

More information

Electronic Income Withholding Orders Software Interface Specification for States and Employers

Electronic Income Withholding Orders Software Interface Specification for States and Employers Electronic Income Withholding Orders Software Interface Specification for States and Employers This document was prepared for the United States Department of Health and Human Services, Office of Child

More information

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information in this publication

More information

How To Create An Overseas Telegraphic Transfer

How To Create An Overseas Telegraphic Transfer VELOCITY@OCBC 2.0 BUSINESS INTERNET BANKING USER GUIDE 1 of 131 1 Contents 1. Log in to Velocity@ocbc 2.0 4 2. View Trade Finance portfolio 12 3. View and download a bank statement 15 4. Create a Letter

More information

Guideline 8A: Submitting Non-SWIFT Electronic Funds Transfer Reports to FINTRAC Electronically

Guideline 8A: Submitting Non-SWIFT Electronic Funds Transfer Reports to FINTRAC Electronically Guideline 8A: Submitting Non-SWIFT Electronic Funds Transfer Reports to FINTRAC Electronically Rev. 2015-09 Guideline 8A: Submitting Non-SWIFT Electronic Funds Transfer Reports to FINTRAC Electronically

More information

SEPA Direct Debit Creditor Guide

SEPA Direct Debit Creditor Guide SEPA SEPA Direct Debit Creditor Guide Glossary of Terms Version Control Version Date Name Update V1.0 30/10/2013 Bank of Ireland Creditors Guide published on BOI website This document is published by Bank

More information

WEBKINCSTAR ONLINE SECURITIES TRADING - TERMS AND CONDITIONS OF USE

WEBKINCSTAR ONLINE SECURITIES TRADING - TERMS AND CONDITIONS OF USE WEBKINCSTAR ONLINE SECURITIES TRADING - TERMS AND CONDITIONS OF USE The Hungarian State Treasury (hereinafter: Distributor) provides general information (on its website) and executes securities trading

More information

Shared Accounting Module Trading Partner Integration Guide

Shared Accounting Module Trading Partner Integration Guide Trading Partner Integration Guide Document Version 2.2 Table of Contents How to Use This Document... 2 Section 1: Services and Options... 2 Section 2: SAM Technical Overview... 7 Section 3: Getting Started...

More information

Funds Transfer Agreement

Funds Transfer Agreement Funds Transfer Agreement Your Lifetime Financial Partner This Funds Transfer Authorization Agreement & Notice ( Agreement ) applies to all domestic or international Wire Transfers and Automated Clearing

More information

TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK

TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK TABLE OF CONTENTS SECTION 1 General provisions... 1 I. General rules for payment execution in foreign exchange transactions...

More information

1. July 2016. Corporates: Current Account Overview of Prices and Conditions for Companies

1. July 2016. Corporates: Current Account Overview of Prices and Conditions for Companies 1. July 2016 Corporates: Current Account Overview of Prices and Conditions for Companies Business Easy Package Business Easy is the full-service offer for small and mediumsized businesses. It includes

More information

E-mail Management: A Guide For Harvard Administrators

E-mail Management: A Guide For Harvard Administrators E-mail Management: A Guide For Harvard Administrators E-mail is information transmitted or exchanged between a sender and a recipient by way of a system of connected computers. Although e-mail is considered

More information

Format Description. SWIFT MT103 Single Customer Credit Transfer

Format Description. SWIFT MT103 Single Customer Credit Transfer De Format Description SWIFT MT103 Single Customer Credit Transfer COLOPHON Title Format Description SWIFT MT103 Version, date 1.3, June 2015 On behalf of Contact address Corporate Client Channels Rabobank

More information

Guide to Handling Direct Deposit

Guide to Handling Direct Deposit PAYROLL CS DIRECT DEPOSIT Guide to Handling Direct Deposit version 2009.x.x TL20765 (7/10/09) Copyright Information Text copyright 1998 2009 by Thomson Reuters/Tax & Accounting. All rights reserved. Video

More information

Business On Line. The complete online package for your business

Business On Line. The complete online package for your business Business On Line The complete online package for your business Manage your cash flow wherever you are Controlling your cash flow is crucial to the success of your business. At Bank of Ireland we understand

More information

BALLSTON SPA NATIONAL BANK. Online Banking Service Agreement

BALLSTON SPA NATIONAL BANK. Online Banking Service Agreement BALLSTON SPA NATIONAL BANK Online Banking Service Agreement Agreement This Agreement which includes the Application Form 1, and Terms and Conditions of Your Deposit Account 2, is a contract which establishes

More information

Attachment E. BUSINESS DAY - A calendar day other than a Saturday, Sunday, or Federal holiday.

Attachment E. BUSINESS DAY - A calendar day other than a Saturday, Sunday, or Federal holiday. GLOSSARY OF TERMS: ACH - The Automated Clearing House network. ACH OPERATOR - The central clearing facility that receives entries from ODFIs, edits and processes based on requirements of the Rules, distributes

More information

M&T ACH Services ACH RETURNS MANUAL

M&T ACH Services ACH RETURNS MANUAL M&T ACH Services ACH RETURNS MANUAL M&T ACH SERVICES Welcome to M&T Bank Services and the latest update to our ACH Returns Manual. This ACH Returns Manual is your resource for frequently asked information

More information

CASHMERE VALLEY BANK ELECTRONIC BANKING AGREEMENT AND DISCLOSURE STATEMENT

CASHMERE VALLEY BANK ELECTRONIC BANKING AGREEMENT AND DISCLOSURE STATEMENT CASHMERE VALLEY BANK ELECTRONIC BANKING AGREEMENT AND DISCLOSURE STATEMENT In this Electronic Banking Agreement and Disclosure, Agreement, "you", "your", and "yours" refers to each person that will be

More information

Section I Transmission Modes

Section I Transmission Modes Transmission Modes Transmission Options Available...2 Value Added Networks (VAN)...2 File Transfer Protocol (FTP)...2 HTTPS File Upload (WEB)...3 Storing and Receiving Data with File Transfer Protocol...3

More information

SEPA Creditors Guide. SEPA Direct Debit Core Scheme. Version 1.3 Final Page 1 of 38

SEPA Creditors Guide. SEPA Direct Debit Core Scheme. Version 1.3 Final Page 1 of 38 SEPA Creditors Guide SEPA Direct Debit Core Scheme Version 1.3 Final Page 1 of 38 Log of Revisions to the SDD Creditors Guide Version number Version1.1 Brief description of revision Comprehensive guide

More information

PAIN.002. Format description Functional

PAIN.002. Format description Functional PAIN.002 Format description Functional Content 1. PAIN.002 STATUS EXPORT FORMAT 3 2. PAIN.002 SCENARIOS 5 APPENDIX 1: EXPORTING PAIN.002 FROM RABO CASH MANAGEMENT 12 APPENDIX 2: DOWNLOADING PAIN.002 FROM

More information

RATES FOR CASH AND SETTLEMENT SERVICES TO CORPORATE CUSTOMERS (LEGAL ENTITIES AND PRIVATE ENTERPRENEURS)

RATES FOR CASH AND SETTLEMENT SERVICES TO CORPORATE CUSTOMERS (LEGAL ENTITIES AND PRIVATE ENTERPRENEURS) Valid from 16.03.2015 RATES FOR CASH AND SETTLEMENT SERVICES TO CORPORATE CUSTOMERS (LEGAL ENTITIES AND PRIVATE ENTERPRENEURS) Item Service Applicable rates Payment procedure Notes 1.1. Opening an account

More information

PROCEDURES MANUAL FOR IMPLEMENTATION OF THE FLORIDA MOTOR VEHICLE NO-FAULT LAW AND FINANCIAL RESPONSIBILITY LAW INITIAL/RELOAD REQUIREMENTS

PROCEDURES MANUAL FOR IMPLEMENTATION OF THE FLORIDA MOTOR VEHICLE NO-FAULT LAW AND FINANCIAL RESPONSIBILITY LAW INITIAL/RELOAD REQUIREMENTS PROCEDURES MANUAL FOR IMPLEMENTATION OF THE FLORIDA MOTOR VEHICLE NO-FAULT LAW AND FINANCIAL RESPONSIBILITY LAW INITIAL/RELOAD REQUIREMENTS STATE OF FLORIDA DEPARTMENT OF HIGHWAY SAFETY AND MOTOR VEHICLES

More information

Standards MX Message Implementation Guide and Rule Book

Standards MX Message Implementation Guide and Rule Book Solutions SWIFT for Corporates Standards MX Message Implementation Guide and Rule Book Payment Initiation and Account Reporting This document describes and references a set of rules and guidelines you

More information

Manage. Your payments and securities trading over the Internet www.bcge.ch. je connais mon banquier je connais mon banquier

Manage. Your payments and securities trading over the Internet www.bcge.ch. je connais mon banquier je connais mon banquier Your payments and securities trading over the Internet www.bcge.ch Manage 2 Index 1. How to become a BCGE Netbanking user? 3 2. Advantages of BCGE Netbanking 4 3. BCGE Netbanking functions 6 3.1 Check

More information

ipko biznes Administrator s Guide

ipko biznes Administrator s Guide ipko biznes Administrator s Guide 1 1. GLOSSARY Client an entity that entered into e-banking agreement with the Bank. User a representative entitled to use e-banking services, that is a person appointed

More information

Basic Requirements...2. Software Requirements...2. Mailbox...2. Gatekeeper...3. Plan Your Setup...3. Meet Extreme Processing...3. Script Editor...

Basic Requirements...2. Software Requirements...2. Mailbox...2. Gatekeeper...3. Plan Your Setup...3. Meet Extreme Processing...3. Script Editor... Guide on EDI automation and use of VAN services Copyright 2008-2009 Etasoft Inc. Main website http://www.etasoft.com Extreme Processing website http://www.xtranslator.com Basic Requirements...2 Software

More information

XML message for Payment Initiation Implementation Guideline. Version 1.02

XML message for Payment Initiation Implementation Guideline. Version 1.02 XML message for Payment Initiation Implementation Guideline Version 1.02 Version 1.02 Changes Updated 20131211 1) SEB specific rule added under tag 2.44 Equivalent Amount 2) To the tag 2.89 Regulatory

More information

Implementation Guide for. Direct Filing of. Telecommunications Returns

Implementation Guide for. Direct Filing of. Telecommunications Returns Illinois Department of Revenue Implementation Guide for Direct Filing of Telecommunications Returns July 2014 Overview We encourage all taxpayers to file electronically. Illinois business taxpayers can

More information

About Data File Exchange

About Data File Exchange Methods for Service Providers to maintain accurate employer data September 2012 Tax and General Accounting Unemployment Insurance State of Wisconsin Contents Introduction Submitting a File through Secure

More information

SWIFT Certified Application - Exceptions and Investigations

SWIFT Certified Application - Exceptions and Investigations Service Partner Programme SWIFT Certified Application - Exceptions and Investigations Label Criteria 2016 This document explains the criteria required to obtain the SWIFT Certified Application - Exceptions

More information

MOBILKINCSTAR ONLINE SECURITIES TRADING TERMS AND CONDITIONS OF USE

MOBILKINCSTAR ONLINE SECURITIES TRADING TERMS AND CONDITIONS OF USE MOBILKINCSTAR ONLINE SECURITIES TRADING TERMS AND CONDITIONS OF USE The Hungarian State Treasury (hereinafter: Distributor) provides general information, executes securities trading and investment transactions

More information

ISO 20022 PAYMENT GUIDE. Messages: Pain.001.001.03 Pain.002.001.03

ISO 20022 PAYMENT GUIDE. Messages: Pain.001.001.03 Pain.002.001.03 ISO 20022 PAYMENT GUIDE Messages: Pain.001.001.03 Pain.002.001.03 20.11.2012 1 ISO 20022 Payment Guide Table of Contents 1 Background... 3 1.1 SEPA and ISO 20022... 3 1.2 Usage of ISO 20022 in Finland...

More information

Implementation Guide Corporate egateway

Implementation Guide Corporate egateway Implementation Guide Corporate egateway 2(16) Page Table of contents 1 Purpose of this guide... 3 1.1 Recommended information 4 1.2 How to get started? 4 2 Project preparation... 5 2.1 List of interested

More information

Online Banking Record Descriptions

Online Banking Record Descriptions Record s hotline@sydbank.dk Page 1 of 65 Contents Introduction... 3 Sydbank format... 3 Format descriptions... 5 of fixed-length records... 5 of variable-length records... 6 Payment start... 7 IB000000000000...

More information

SYSTEM LOGIN/PASSWORD SUPPORT

SYSTEM LOGIN/PASSWORD SUPPORT SYSTEM LOGIN/PASSWORD SUPPORT Why am I unable to log into the system? What if I forgot my password? Why do I need to create Security Questions/Answers? Why does it ask me if I want to remember this computer?

More information

PAYMENT FACTORY AND IN-HOUSE BANK

PAYMENT FACTORY AND IN-HOUSE BANK Wallstreet Suite Comprehensive, cross-asset investment and debt management solutions for financial institutions www.wallstreetsystems.com FACT SHEET: PAYMENT FACTORY AND IN-HOUSE BANK Wallstreet Suite

More information

Secure Envelope specification

Secure Envelope specification Secure Envelope specification for Corporate Access File Transfer 2/13/2015 Version 1.0.3 This document defines how a file (e.g. a payment file) which will be sent to the bank is digitally signed by the

More information

International Business Price List

International Business Price List International Business Price List Prices correct as at 28 June 2014 Introduction This International Business Price List sets out the prices we charge for international transactions and our most frequently

More information

Swedbank Business Internet Banking User Manual

Swedbank Business Internet Banking User Manual Swedbank Business Internet Banking User Manual Content Introduction 1. HOW TO START 1.1 USING INTERNET BANKING 1.2 TERMINATING INTERNET BANKING SESSION 2. INTERNET BANKING SECURITY 2.1 PASSWORD SYSTEM

More information

Business Banking Price List

Business Banking Price List Business Banking Price List The information in this leaflet is correct as at 17 February 2014 (unless our customer notice to you stated otherwise). Introduction This Business Banking Price List sets out

More information

System to System Interface Guide

System to System Interface Guide System to System Interface Guide Overview What does this guide cover? This guide describes the interface definition to firms intending to submit their TRS Product Sales Data (PSD) or Securities Trades

More information

Infor10 ERP Enterprise (LN) Financials. Reference Guide for Cash Management

Infor10 ERP Enterprise (LN) Financials. Reference Guide for Cash Management Infor10 ERP Enterprise (LN) Financials Reference Guide for Cash Management Copyright 2011 Infor All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks

More information

SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands

SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands CORE and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.

More information

PORTFOLIO ACCOUNTING SYSTEM

PORTFOLIO ACCOUNTING SYSTEM PORTFOLIO ACCOUNTING SYSTEM by Investment Systems Company 37840 Jackson Road Moreland Hills, OH 44022-1912 (440) 247-2865 www.investmentsystems.com Table of Contents Text Overview...1 Base System...2 Optional

More information

Matching, Amending and Foreign Invoices in Accounts Payable

Matching, Amending and Foreign Invoices in Accounts Payable Matching, Amending and Foreign Invoices in Accounts Payable Table of Contents 1. Overview of Matching an External Invoice... 3 2. Matching an Invoice to a Purchase Order... 4 3. Additional Charges for

More information

Entering payment order abroad and payment order in a foreign currency in the Czech Republic via electronic banking service ČSOB InternetBanking 24

Entering payment order abroad and payment order in a foreign currency in the Czech Republic via electronic banking service ČSOB InternetBanking 24 Entering payment order abroad and payment order in a foreign currency in the Czech Republic via electronic banking service ČSOB InternetBanking 24 Content 1. Payment order abroad... 2 1.1. Entering payment

More information

User Guide for Payroll Service (APS+)

User Guide for Payroll Service (APS+) User Guide for Payroll Service (APS+) Sept 2015 No part of this document may be reproduced, stored in a retrieval system of transmitted in any form or by any means, electronic, mechanical, chemical, photocopy,

More information

Funds Transfer Oracle FLEXCUBE Universal Banking Release 11.3.1.0.0EU [April] [2012] Oracle Part Number E51534-01

Funds Transfer Oracle FLEXCUBE Universal Banking Release 11.3.1.0.0EU [April] [2012] Oracle Part Number E51534-01 Funds Transfer Oracle FLEXCUBE Universal Banking Release 11.3.1.0.0EU [April] [2012] Oracle Part Number E51534-01 Table of Contents Funds Transfer 1. ABOUT THIS MANUAL... 1-1 1.1 INTRODUCTION... 1-1 1.1.1

More information

Batch Processing Version 2.0 Revision Date: April 29, 2014

Batch Processing Version 2.0 Revision Date: April 29, 2014 Batch Processing Version 2.0 Revision Date: April 29, 2014 1 Processing payments with batch files is very simple: 1. You put your payment records into tab-delimited text files. In this format, data items

More information

Schedule of fees and charges for business customers

Schedule of fees and charges for business customers Schedule of fees and charges for business customers Effective 23 February 2015 Bank of Ireland is regulated by the Central Bank of Ireland. 37-560RU.35(02/15) Schedule of fees and charges Contents Introduction

More information

Table of Commissions and Fees for Enterprises

Table of Commissions and Fees for Enterprises Table of Commissions and Fees for Enterprises Effective as of 16 December 2013 scan 1/7 9230 I. BANK ACCOUNTS any in PLN 1. Maintenance of each account (monthly) PLN 100.00 2. Maintenance of a progressive

More information

Wealth and Investment Management Intermediaries. Online Banking. Bulk Payments User guide

Wealth and Investment Management Intermediaries. Online Banking. Bulk Payments User guide Wealth and Investment Management Intermediaries Online Banking Bulk Payments User guide Contents Contents 1. Introduction 3 2. Log in steps 4 3. Make BACS payments 5 3.1 Select BACS from account 6 3.2

More information

Payment solutions for individual clients. Swiss ways and customs

Payment solutions for individual clients. Swiss ways and customs ab Payment solutions for individual clients. Swiss ways and customs Contents Introduction to payments in Switzerland 05 How can I make day-to-day payments without using cash? Maestro card 06 Credit cards

More information

The complete online package for your business

The complete online package for your business The complete online package for your business Bank of Ireland is regulated by the Central Bank of Ireland. 37-1322R (01/16) Manage your cash flow wherever you are Controlling your cash flow is crucial

More information

IMPLEMENTATION OF AN ELECTRONIC DOCUMENT MANAGEMENT SYSTEM

IMPLEMENTATION OF AN ELECTRONIC DOCUMENT MANAGEMENT SYSTEM IMPLEMENTATION OF AN ELECTRONIC DOCUMENT MANAGEMENT SYSTEM TECHNICAL SPECIFICATIONS FOR AGENCIES AND BROKERS ACTING ON THEIR ACCOUNT DATA PRESERVATION EXPLANATORY NOTES : The preservation of information

More information

ELECTRONIC FUNDS TRANSFER GUIDE

ELECTRONIC FUNDS TRANSFER GUIDE ELECTRONIC FUNDS TRANSFER GUIDE ACH CREDIT METHOD Included inside is an application form and instructions. INTRODUCTION Job Service North Dakota (JSND) has developed a program to accept Unemployment Insurance

More information

Connectivity and Communications

Connectivity and Communications Chapter 5 Connectivity and Communications This chapter provides information to establish an electronic communications session with Anthem and to submit and receive files. Important: Do not send duplicate

More information

Business On Line. The complete online package for your business

Business On Line. The complete online package for your business Business On Line The complete online package for your business Manage your cash flow wherever you are Controlling your cash flow is crucial to the success of your business. At Bank of Ireland we understand

More information

ISO 20022 ACCOUNT STATEMENT GUIDE. v 1.3

ISO 20022 ACCOUNT STATEMENT GUIDE. v 1.3 ISO 20022 ACCOUNT STATEMENT GUIDE v 1.3 4.10.2012 1 ISO 20022 Account Statement Guide Table of contents 1 Introduction... 3 2 General... 3 2.1 Effects on customer routines... 4 2.2 Activities... 4 3 Electronic

More information

SEPA. Frequently Asked Questions

SEPA. Frequently Asked Questions SEPA Frequently Asked Questions Page 1 of 13 Contents General SEPA Questions... 4 What is SEPA?... 4 What is the aim of SEPA?... 4 What are the benefits of SEPA?... 4 What countries are included in SEPA?...

More information

BANKOH BUSINESS CONNECTIONS WIRE TRANSFER GUIDE

BANKOH BUSINESS CONNECTIONS WIRE TRANSFER GUIDE BANKOH BUSINESS CONNECTIONS WIRE TRANSFER GUIDE Revision 2/2013 1 of 35 Contents GENERAL INFORMATION... 3 Wire Transfers... 3 Types of Wires... 3 Wire Templates... 3 Bankoh Business Connections Wire Cut-off

More information

Banana is a native application for Windows, Linux and Mac and includes functions that allow the user to manage different types of accounting files:

Banana is a native application for Windows, Linux and Mac and includes functions that allow the user to manage different types of accounting files: banana Accounting 7 TECHNICA NICAL DATA Applications and accounting types Banana is a native application for Windows, Linux and Mac and includes functions that allow the user to manage different types

More information

SWIFT Certified Application Payments

SWIFT Certified Application Payments SWIFT Certified Application Payments Technical validation Guide 2014 Version 1.1 April 2014 Legal notices Copyright SWIFT 2014. All rights reserved. You may copy this publication within your organisation.

More information