STP rules for correspondent banks

Similar documents
International Securities Association For Institutional Trade Communication

Settlements Oracle FLEXCUBE Universal Banking Release [April] [2014] Oracle Part Number E

Settlements Oracle FLEXCUBE Universal Banking Release [May] [2011] Oracle Part Number E

Settlements Oracle FLEXCUBE Universal Banking Release [July] [2014]

STRAIGHT THROUGH PROCESSING FORMATTING GUIDELINES FOR AUSTRALIA

ASX - AU - Austraclear - Renminbi - V1-103_Single Customer Credit Transfer

Business Conditions for the bank accounts managed by the Magyar Nemzeti Bank and for settlements in forint and other currencies.

STRAIGHT THROUGH PROCESSING FORMATTING GUIDELINES FOR NEW ZEALAND

Guideline 8: Submitting Electronic Funds Transfer Reports to FINTRAC

SWIFT FIN MT103. Format Description

Bankline. Import file layout guide SWIFT MT101 format

Bankline. Import file layout guide SWIFT MT101 format

Bankline. Import file layout guide SWIFT MT103 format

Bankline export file layout guide Bankline (CSV) format

Request for transfer batches in MT101 format

K&H web Electra and web Electra+ user manual

Wire & Internal Transfers

SR 2018 Business Highlights

Bankline Internet Banking Export File Layout User Guide

Category 2 Financial Institution Transfers

No Description of Field. 1 BAR CODE 1.1 Please ignore as is currently not in use. DATE APPLICATION TYPE. 4 Section 1- APPLICANT'S DETAILS

INSTRUCTIONS FOR FILLING IN A FOREIGN TRANSFER

Funds Transfer User Guide Oracle FLEXCUBE Universal Banking. Release Part No. E

Usage Guidelines. Standards MT November 2017

Deutsche Postbank AG. Format Descriptions for Eurogiro Euro Settlement Service ESSP. ESSP Format Descriptions. Page 1.

User Manual. 1bank Internet Banking for Business Subscribers. Version 2.0

Sberbank Online User Guide

CashPro Online. CashPro Online Quick Reference Guide Global Payments Using Bank-Defined Import File Formats

TBC Internet Banking - Batch Transaction Files Description

Payments and Collections Oracle FLEXCUBE Universal Banking Release CN Cluster Oracle Part Number E [January] [2016]

Access Online. Payment Upload

Notes on completing the documents

Client.dotBANK users guide

Payments Quick start guide Payment Management

HCT INST SCHEME RULEBOOK V2.0

Message Reference Guide. Category 2 - Financial Institution Transfers. Standards. For Standards MT November 2017

UOB TRANSACTION BANKING. BIBPlus Cash Management User Guide

Record Descriptions - lang


Compiling Data on International Mobile Money Transfer Services

BANKING CIRCLE WEB BULK UPLOAD

Step 1: Data Input 1. Click Cash Management > Payments > Express Transfer (RTGS/CHATS)

Application of Key UCC 4A Concepts and Terms to the Real-Time Payment System

Oracle FLEXCUBE Direct Banking

Exchange of Hal E-Bank Documents with Accounting Systems in S.W.I.F.T. Format (Implementation on Slovene Market)

COLLATERAL MANGEMENT AND CUSTODY CLIENT DATA COLLECTION DOCUMENT FOR SMF & OTHER OFFICIAL OPERATIONS, FLS, TFS, DWF, CHAPS IDL AND UK PAYMENT SCHEMES

SEPA CREDIT TRANSFER SCHEME IMPLEMENTATION GUIDELINES

Cash Funding (Derivatives)

Change is easy. Personal New Account Kit. Your Success is Our Mission.

AdmiCash conversion to ISO / SEPA

CASH WITHDRAWAL. User manual

Oracle Banking Digital Experience

Payables: Priority Payments

Local, Danish payments Bulk debits - Business Online

NEW SUPPLIER REGISTRATION GUIDE

THIRD QUARTER ENDING 30 SEPTEMBER 2017 HIGHLIGHTS REPORT NATIONAL PAYMENT SYSTEMS

Internet Banking User Guide

1.5 Hints 1. You need a separate license for each computer or USB memory stick, on which you install the singleuser

XML CONVERTING LLOYDSLINK ONLINE EURO MONEYMOVER PAYMENT XML FILES. Importing Payments in Commercial Banking Online

Business Online International Wires User Guide

Isabel 6 Guide #3. How to encode SEPA and Non-SEPA transactions from an ING account from region 3 & all other banks?

Intermediary Oracle FLEXCUBE Universal Banking Release [May] [2011] Oracle Part Number E

MT104 Direct Debit and Request for Debit Transfer Message.

High Value (India RTGS) Payments User Guide Oracle Banking Payments. Release Part No. E

Updated High-Level Information

SCOTIABANK STUDENT GIC PROGRAM APPLICATION GUIDE

Reminder You MUST have the SMS One Time Password facility set up to make use of international payments.

AdmiCash update information

Business e-banking Wires User Guide

Table of Content Create Remittance and Transfer Transaction Create Template, Draft and Standing Instruction

Format Description MT942 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional)

Wire Templates. Enhanced Business Online Banking WIRE TEMPLATES PAGE 1

* Free calls from landlines and public phones. Some standard network charge applies.

Request for Transfer. Service description. May 2018

Associated Connect. Reference Guide: Wire Import

RCB Remote Banking Services. User Guide

Layout File MT101 Format

Controller s Office Supplier Training September 12, 2017

Changes to the use of Norwegian Telepay format v. 2.01

Supplier/Payee Portal - Individual Registration Guide

CONFERENCE REGISTRATION FORM Sheraton Hotel, Rhodes, Greece, September 2018

FREQUENTLY ASKED QUESTIONS

Processing Reimbursements in Kuali with a Disbursement Voucher Quick Expense (DVQE) document for travel and non-travel expenses

Oracle FLEXCUBE Direct Banking

Coupa Guidance for New Suppliers

Configuration form - Belfius via SWIFT Service

Business Online Banking

Process Document Viewing Customer Accounts

Category 9 - Cash Management and Customer Status

ICBC (London) Plc Internet Banking FAQ s

Online International Remittance (OIR) FAQs

BOARD OF THE BANK OF LITHUANIA. RESOLUTION No 46 ON THE REGULATIONS ON KEEPING THE PUBLIC REGISTER OF PAYMENT INSTITUTIONS. of 24 December 2009

Scotiabank Student GIC Program Application Guide - Please Read Before Applying. Important Dates to Remember:

ACH Rules Update for Originating Companies

BKT KOSOVA BUSINESS E-BANKING USER MANUAL

Format description MT940 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional)

ibanking Corporate Quick Reference Guide Global Transaction Banking

Class Oracle FLEXCUBE Universal Banking Release 12.0 [May] [2012] Oracle Part Number E

JLP isupplier Frequently Asked Questions 2017

Signature Verification Oracle FLEXCUBE Universal Banking Release 12.0 [May] [2012] Oracle Part Number E

Transcription:

STP rules for correspondent banks 1. Incoming MT103/103+ single customer credit transfers in favour of MKB customers Field 23B: Bank Operation Code (M) (4!c) The value of the field must be CRED. Field 23E: Instruction Code (O) (4!c[/30x]) The following codes are not STP compatible: SDVA Please do not use the instruction code HOLD in field 23E as according to our business policy we do not accept this type of payment from September 1, 2004. If the beneficiary is not our customer or customer of another Hungarian bank, the transaction can be effected as a postal payment. See field 59 in section 2. Incoming MT103/103+ single customer credit transfers in favour of non-mkb customers for details. Field 50a: Ordering Customer (M) Field 50A: Field 50K: BIC of the ordering party (4!a2!a2!c[3!c]) Account number of the ordering customer ([/34x]). Name and address of the ordering customer (4*35x). The international rules for prevention of money laundering are to be applied. If field 50K contains the account number of the ordering customer, then the name and address (which cannot be a p.o. box number) must also be indicated; the account number alone is not acceptable. Field 50K cannot indicate the expression One of our customers. An exact customer name must be specified. If the message does not meet the above requirements we will consider it as null and void and - after deducting our charges - we will return the cover. Field 53A: Sender's Correspondent (O) (4!a2!a2!c[3!c]) BIC of the sender s clearing bank. Fields 53B and 53D are not applicable. If the message does not contain field 54A, the bank in field 53A must have direct account relationship with MKB in the currency of the transfer. Field 54A: Receiver's Correspondent (O) (4!a2!a2!c[3!c]) BIC of MKB s clearing bank. Fields 54B and 54D are not applicable. Field 55A: Third Reimbursement Institution (O) (4!a2!a2!c[3!c]) BIC of the Third Reimbursement Institution. Fields 55B and 55D are not applicable. Field 57A: Account With Institution If the beneficiary of the transaction is an MKB customer this field is not applicable as only the head office of MKB does have a BIC (MKKBHUHB), the branches do not.

Field 59a: Beneficiary Customer (M) Indication of the account number and the name of the beneficiary customer are obligate (4*35x). Account numbers at MKB contain numeric characters only (apart from the HU prefix in case of IBAN). An account number is STP compatible in the following formats: a) The customer account number without the GIRO* ID of MKB (16 digits). e.g. /5011234531004012 b) The customer account number with the GIRO ID (10300002) of MKB (24 digits). e.g. /103000025011234531004012 c) International Bank Account Number (IBAN): HUnn + GIRO ID of MKB (10300002) + 16 digits customer accont number. e.g. /HU08103000025011234531004012 Field 71A: Details of Charges (M) (3!a) The valid codes are OUR, SHA, BEN. Field 71G: Receiver s Charges (O) (3!a15d) If the amount in this field does not equal with the difference of fields 32A and 33B /or in case of conversion ((the amount in field 33B x the exchange rate in field 36) - the amount in field 32A) not = the amount of the charges in field 71G/, the message will be manually processed. Field 72: Sender to Receiver Information (O) (6*35x) The following codes are not STP compatible: /ACC/ 2. Incoming MT103/103+ single customer credit transfers in favour of non-mkb customers Field 23B: Bank Operation Code (M) (4!c) The value of the field must be CRED. Field 23E: Instruction Code (O) (4!c[/30x]) Valid codes are SDVA, INTC, REPA, CORT, BONL, CHQB, PHOB, TELB, PHON, TELE, PHOI, TELI. Field 50a: Ordering Customer (M) Field 50A: Field 50K: BIC code of the ordering customer (4!a2!a2!c[3!c]). Account number of the ordering customer ([/34x]). Name and address of the ordering customer (4*35x).

The international rules for the prevention of money laundering have to be applied. If field 50K contains the account number of the ordering customer, then name and address (which cannot be a p.o. box number) must be indicated; the account number alone is not acceptable. Field 50K cannot indicate the expression One of our customers. An exact customer name must be specified. If the message does not meet the above requirements we will consider it as null and void and - after deducting our charges - we will return the cover. Field 53A: Sender's Correspondent (O) (4!a2!a2!c[3!c]) BIC of the sender s clearing bank. Fields 53B and 53D are not applicable. If the message does not contain field 54A, the bank in field 53A must have direct account relationship with MKB in the currency of the transfer. Field 54A: Receiver's Correspondent (O) (4!a2!a2!c[3!c]) BIC of the MKB s clearing bank. Fields 54B and 54D are not applicable. Field 55A: Third Reimbursement Institution (O) BIC of the Third Reimbursement Institution (4!a2!a2!c[3!c]). Fields 55B and 55D are not applicable. Field 56A: Intermediary Institution (O) the currency of the transfer. Fields 56C and 56D are not applicable. Field 57a: Account With Institution (O) field must be a valid BIC (57A: 4!a2!a2!c[3!c]). In this case fields 57B, 57C and 57D are not applicable. original amount will be remitted to the beneficiary s bank via the VIBER** system). In this case, using the option 57A the second line of this field must contain a valid BIC, or using the option 57D, the lines 2-5 must contain the name and address of the beneficiary s bank. Field 59a: Beneficiary Customer (M) (4*35x) Indication of the account number and the name of the beneficiary customer are obligate. If field 59 do not contain an account number (held at MKB or another Hungarian bank) the transaction can be effected as a postal payment (and will not be an STP transaction). In this case, MKB will send the amount to the beneficiary by post, after converting it to HUF with the actual currency rate (because postal payments can be effected only in HUF). To enable this type of transaction, field 59 must contain the full and correct name and address (city/town, street, street number, postal code) of the beneficiary and field 72 must indicate the code POST. Field 71A: Details of Charges (M) (3!a) The valid codes are OUR, SHA, BEN. Note: If the transfer is sent via two or more Hungarian banks, it is likely that all of them request their own commission fee from the ordering party, so the possibility of double or multiple charging is high.

Field 71G: Receiver's Charges (O) (3!a15d) The (pre-paid) charges that are to be booked by MKB. The amount indicated in the first 71G field is deducted by MKB as transaction fee before forwarding the cover to the beneficiary s bank. Field 72: Sender to Receiver Information (O) (6*35x) The following codes are not STP compatible: /INT/ In the first line of this field the code can be used with the following STP compatible options (in all of the below cases the amount of the transaction will be converted to HUF): VIBER The HUF equivalent of the original amount is remitted by MKB to the beneficiary s bank via the VIBER system. GIRO The HUF equivalent of the original amount is forwarded by MKB to the beneficiary s bank via the GIRO system. If this code is used, in the first line of field 59a the beneficiary s account number must be formatted GIRO compatible (the 8 digits GIRO id of the beneficiary s bank and the 8 or 16 digits long customer account number). If the field 72 does not contain the codes VIBER or GIRO then our default system is GIRO. If the non-resident ordering disposer transfers HUF amount in favour of a resident customer, the exact payment reason code must be indicated in field 70 (Remittance Information). 3. Incoming MT200 financial institution transfers for its own account Field 53B: Sender's Correspondent (O) This field is not applicable. Field 56A: Intermediary (O) the currency of the transfer. Field 56D is not applicable. Field 57a: Account With Institution (O) field must be a valid BIC (57A: 4!a2!a2!c[3!c]). In this case fields 57B and 57D are not applicable. original amount will be remitted to the beneficiary s bank via the VIBER system). In this case, using the option 57A the second line of this field must contain a valid BIC, or using the option 57D, the lines 2-5 must contain the name and address of the beneficiary s bank. Field 72: Sender to Receiver Information (O) This field is not applicable.

4. Incoming MT202 general financial institution transfers Field 52A: Ordering Institution (O) BIC of the ordering party (4!a2!a2!c[3!c]). Field 52D is not applicable. Field 56A: Intermediary (O) the currency of the transfer. Field 56D is not applicable. Field 57a: Account With Institution (O) field must be a valid BIC (57A: 4!a2!a2!c[3!c]). In this case fields 57B and 57D are not applicable. original amount will be remitted to the beneficiary s bank via the VIBER system). In this case, using the option 57A the second line of this field must contain a valid BIC, or using the option 57D, the lines 2-5 must contain the name and address of the beneficiary s bank. Field 58A: Beneficiary Institution (M) BIC of the beneficiary bank (4!a2!a2!c[3!c]). If field 56A and/or 57A is not present, this can be either a Hungarian bank or a foreign bank maintaining account with MKB in the currency of the transfer. Field 58D is not applicable. If field 72 contains the code GIRO the GIRO ID of the bank must be also present in the first line of field 58A before the account number (altogether 16 or 24 digits). Field 72: Sender to Receiver Information (O) (6*35x) The following code is not STP compatible: In the first line of this field the code can be used with the following STP compatible options (in all of the below cases the amount of the transaction will be converted to HUF): VIBER The HUF equivalent of the original amount is remitted by MKB to the beneficiary s bank via the VIBER system. GIRO The HUF equivalent of the original amount is forwarded by MKB to the beneficiary s bank via the GIRO system. If this code is used, in the first line of field 58A the bank id number must be formatted GIRO compatible (the 8 digits GIRO ID of the beneficiary s bank and the 8 or 16 digits long customer account number). 5. Incoming MT203 multiple general financial institution transfers Field 52A: Ordering Institution

BIC of the ordering party (4!a2!a2!c[3!c]). Field 52D is not applicable. Fields 56A: Intermediary the currency of the transfer. Field 56D is not applicable. Fields 57a: Account With Institution field must be a valid BIC (57A: 4!a2!a2!c[3!c]). In this case fields 57B and 57D are not applicable. original amount will be remitted to the beneficiary s bank via the VIBER system). In this case, using the option 57A the second line of this field must contain a valid BIC, or using the option 57D, the lines 2-5 must contain the name and address of the beneficiary s bank. Fields 58A: Beneficiary Institution (M) BIC of the beneficiary bank (4!a2!a2!c[3!c]). If field 56A and/or 57A is not present, this can be either a Hungarian bank or a foreign bank maintaining account with MKB in the currency of the transfer. Field 58D is not applicable. If Field 72 contains the code GIRO the GIRO ID of the bank must be also present in the first line of Field 58A before the account number (altogether 16 or 24 digits). Fields 72: Sender to Receiver Information (O) (6*35x) The following code is not STP compatible: In the first line of this field the code can be used with the following STP compatible options (in all of the below cases the amount of the transaction will be converted to HUF): VIBER The HUF equivalent of the original amount is remitted by MKB to the beneficiary s bank via the VIBER system. GIRO The HUF equivalent of the original amount is forwarded by MKB to the beneficiary s bank via the GIRO system. If this option is used, in the first line of field 58A the bank id number must be formatted GIRO compatible (the 8 digits GIRO ID of the beneficiary s bank and the 8 or 16 digits long customer account number). If you have further questions regarding the STP formatting rules of payment orders please contact: International Payments Department István Gáll Phone: (36) 1 268-8324 Fax: (36) 1 268-7707

E-mail: gall.istvan@mkb.hu * GIRO=Hungarian Net Settlement System ** VIBER=Hungarian RTGS