Standards MX Message Implementation Guide and Rule Book

Size: px
Start display at page:

Download "Standards MX Message Implementation Guide and Rule Book"

Transcription

1 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 must follow when you implement, send or receive ISO payment initiation and account reporting messages using FileAct in SCORE (Standardised Corporate Environment) 01 December 2011

2 Preface Table of Contents 1 Message Rules and Guidelines Key Rules Rule and Guideline Conventions Payment Initiation Overview Customer Credit Transfer Initiation Payment Status Report Customer Direct Debit Initiation Account Reporting Overview Account Reporting Messages Common Message Components Mapping Guidelines MX - MT Mapping from pain.001 to MT Mapping from pain.001 to MT Comparison MT - MX Comparison MT 942 to camt Comparison MT 941 to camt Comparison MT 940 to camt Comparison MT 950 to camt Comparison MT 900 to camt Comparison MT 910 to camt Standards MX Message Implementation Guide (Dec 2011)

3 Preface Preface Purpose of this document SWIFT has designed this document to promote an industry implementation standard for : Payment Initiation - customer initiated credit transfers, direct debits, and reporting back on the status of these transfers, using the ISO Customer Credit Transfer Initiation, the ISO Customer Direct Debit Initiation and ISO Payment Status Report messages. Account Reporting - bank-to-customer reporting of account activity information, using the ISO Bank-to-Customer Account Report, the ISO Bank-to-Customer Statement, and the ISO Bank-to-Customer Debit/Credit Notification messages. By using these messages on SWIFTNet, each user agrees to abide by the minimum rules and guidelines applicable to them, as specified in the sections that follow and in the referenced CGI implementation templates. For the avoidance of any doubt, nothing in these documents shall be binding upon SWIFT nor construed as constituting an obligation, representation, or warranty on the part of SWIFT. The scope of these guidelines In summary, the aim of developing these guidelines is to facilitate automation by : ensuring common interpretation and understanding of data elements included in the messages, and ensuring common implementation of functionalities covered through the messages. Document Release Management This document represents a significant update to the previous version: Standards MX Message Implementation Guide and Rule Book, Payment Initiation and Account Reporting, 17 June 2009 Summary of differences: ISO Message Updates adoption of later ISO message versions: - camt BankToCustomerAccountReportV02 - camt BankToCustomerStatementV02 - camt BankToCustomerDebitCreditNotificationV02 - pain CustomerCreditTransferInitiationV03 - pain CustomerPaymentStatusReportV03 - pain CustomerDirectDebitInitiationV02 CGI Message Implementation Templates adoption of CGI message implementation templates as the base implementation reference source for payment intitiation and cash management messages in SCORE: - ISO Credit Transfer V3 Message Implementation Guide 13 June ISO Payment Status Report V3 Message Implementation Guide 13 June ISO Direct Debit V2 Message Implementation Guide 28 July ISO Cash Management V2 Message Implementation Guide 28 July Standards MX Message Implementation Guide (Dec 2011)

4 Preface In order to faciliate the migration from the previous version of the guidelines to the latest version, SCORE supports both the latest version of the implementation guide and the prior version, namely: Standards MX Message Implementation Guide, Payment Initiation and Account Reporting, 17 June 2009 Standards MX Message Implementation Guide and Rule Book, Payment Initiation and Account Reporting,18 November 2011 Acknowledgements SWIFT acknowledges the contribution of the participants in the Common Global Implementation (CGI) initiative. The aim of CGI is to provide a forum for financial institutions (banks and bank associations) and non-financial institutions (corporates, corporate associations, vendors and market infrastructures) to progress various bank-to-corporate implementation topics on the use of ISO message and to other related activities.this is achieved through consultation, collaboration and agreement on common implementation templates for relevant ISO financial messages, leading to their subsequent publication and promotion in order to attain widespread recognition and adoption. CGI is structured as an ad hoc, voluntary, non-legal forum that is open to financial and nonfinancial institutions having a common interest in collaboration, promotion and adoption of the ISO XML financial message set. SWIFT is both a contributor and the support organisation for the CGI initiative. Contributors to the CGI include: Financial Institutions : Bank of America Merrill Lynch, Barclays, BBVA, BSK, Citibank, Danish Bankers Association, Danske Bank, Deutsche Bank, DnB NOR, HSBC, ING Bank, J.P.Morgan, Nordea Bank, Royal Bank of Scotland, Santander, SEB, Standard Chartered Bank, Sydbank A/S, UK Payments Administration, UniCredit Bank. Non-financial institutions : Bottomline Technologies, CBI Consortium, General Electric, GXS, Nets, Sungard, UTSIT, XMLdation, SAP AG. Document structure This guide is structured as follows: Section 1 covers the Key Rules and specific Implementation Rules and Guidelines Section 2 covers the payment initiation messsages Section 3 covers the account reporting messages Section 4 covers the common message components Section 5 provides a set of mapping guidelines for the ISO payment initiation messages to the subsequent MT messages Section 6 provides a comparison of the account reporting MT messages with the corresponding ISO messages. 4 Standards MX Message Implementation Guide (Dec 2011)

5 Message Rules and Guidelines 1 Message Rules and Guidelines 1.1 Key Rules Support of ISO Messages For Payment Initiation and Account Reporting the following ISO Messages are applicable: camt BankToCustomerAccountReportV02 camt camt pain pain pain BankToCustomerStatementV02 BankToCustomerDebitCreditNotificationV02 CustomerCreditTransferInitiationV03 CustomerPaymentStatusReportV03 CustomerDirectDebitInitiationV02 SCORE requires for Payment Initiation that users support the Customer Credit Transfer Initiation (pain.001) message to initiate electronic transfers and the Payment Status Report (pain.002) message to provide positive and negative status information on the operational status of the transfer. For the other messages, support is dependant on the services that the bank offers. Provision needs to be made that allows for future updates to the associated Message Definition Report, to this Implementation Guide and Rule Book and to the referenced CGI implementation templates. Compliance Users using the messages on SWIFTNet commit to comply with the standards as described in the ISO Message Definition Report (which contains the same message specifications as the SWIFTStandards MX Message Reference Guide) and when published, the corresponding Message Usage Guide. This means that : all mandatory data in the schema should be provided, logic embedded in the schema should be respected, and rules and guidelines defined for the generic ISO messages should also be adhered to. values not supported by the schema should not be present (ie an XML instance containing an element not present in the schema, would cause an error when the instance is validated against the schema). Note : If an instance contains such a schema mistake, it is up to the recipient to decide how to react (ie either accept and process, or reject). In addition, users must also comply with the minimum implementation rules as outlined in the sections below. Technical implementation rules Instances (ie actual messages exchanged) should not contain empty tags ie should not contain elements which do not contain content. Operational rules Optional elements, which are included in the schema, but which are not considered to be key for transactions in scope and which are however present in the message instance (included in the instance by the Sender) may be ignored (i.e. not used for processing and not passed on) by the Receiver (i.e. would not be a cause for rejecting the message). 5 Standards MX Message Implementation Guide (Dec 2011)

6 SWIFT for Corporates Where the recipient may not actually require this surplus information, it will be viewed as data overpopulation and will be ignored. This applies for both corporate to bank and bank to corporate messages. Under CGI, this concept of data overpopulation provides the core foundation to establishing a single generic harmonised template. Character set All banks subscribing to the SCORE service will support the following characters : a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z / -? : ( )., ' + Space Banks can support additional characters/character sets as part of their service offering. The EndToEndIdentification should always be expressed in the character set referred to under the first bullet above. Depending on supported character sets in the interbank clearing and settlement channels, banks may have to convert the characters contained in text-based elements received in the payment initiation messages. For guidance on how to represent disallowed characters in XML content, please refer to the section SWIFTStandards Supported Character Sets, under SWIFTStandards XML for Standards MX Messages in the User Handbook. 1.2 Rule and Guideline Conventions The ISO Message Definition Report contains full standard specifications and rules that must be adhered to. When published, a corresponding Message Usage Guide would contain a series of topics illustrating these standard specifications and rules. As the messages enable various degrees of complexity and flexibility in implementation, some additional usage rules and guidelines have been defined and referenced in the context of this document. The rules and guidelines adopted by SCORE are defined in the respective CGI Message Implementation Templates and associated Appendices, as developed and approved by the CGI. These globally agreed templates are designed to provide clear guidance, in terms of which XML fields are required, optional, bilaterally determined or not used from both a core message and local country rules perspective. An overview of the templates can be found below. The specific template references are indicated in the individual message descriptions in the sections that follow. These message descriptions also depict the schema structures, components and elements. While a limited number of usage rules and guidelines are replicated in the message descriptions, the CGI Message Implementation Templates should serve as the definitive reference. Message components that are common to a number of messages are shown in section 4. CGI Implementation Templates The CGI message implementation templates provide the opportunity to establish generic harmonised multi-banking ISO XML messages. It should also be noted that this may not be the only implementation that banks will support. Some banks may be able to offer value added solutions that are over and above the core CGI message implementation template. For futher information see the SWIFT for Corporates Resource Centre and SwiftCommunitiy.Net CGI publishes their guidance in the form of: 6 Standards MX Message Implementation Guide (Dec 2011)

7 Message Rules and Guidelines Document Type Core Template Appendices Description This represents the core CGI implementation guidance for the use of the designated ISO message. For corporate-to-bank flows it defines all the elements that are mandated by the schema or CGI required, that will be accepted by all CGI supporting banks. For bank-to-corporate flows it defines all the elements that are mandated by the schema or CGI required, that will be provided by all CGI supporting banks. Each template may further qualify the content, for example by payment instrument type. Additional implementation information to support message use in a particular context (e,g. country/region specific requirements) or to provide reference information (e,g. local instrument codes). Appendix are created, when appropriate, based on the business requirements of a specific message and may be subject to a more frequent revision cycle. In the CGI Implementation Templates, specific usage of a data element is designated with one of the following codes. Additional detail is provided in the template Rules column, including recommendations and best practice that must be followed whenever possible. CGI Implementation Template Attributes Codes Term Definitions R Required Standard element for CGI; Required either by schema or CGI C Conditional Standard element for CGI; Dependent upon a certain condition. BD Bilaterally Determined Standard element for CGI. Contents are bilaterally determined between client and bank XOR exclusive Or Standard element for CGI. Contents are XOR either by the schema or CGI usage. NU Not Used Not Specified by CGI Schema Diagram Conventions: In the sections that follow a number of schema diagrams are provided to illustrate the relevant components and elements of the individual messages. The symbols denote the following: Box with a full line is a mandatory message element (also expressed in text as 1..1 ) Box with a dotted line is an optional message element (also expressed in text as 0..1 ) 7 Standards MX Message Implementation Guide (Dec 2011)

8 SWIFT for Corporates The component can contain a number of mandatory and optional elements. The elements must appear in the sequence mentioned The component contains a number of elements. Only one of the possible elements may be present (choice). 8 Standards MX Message Implementation Guide (Dec 2011)

9 Payment Initiation 2 Payment Initiation 2.1 Overview The implementation rules and guidelines included in this chapter relate to the following ISO Payment Initiation messages : Customer Credit Transfer Initiation Version 3 (pain ) Customer Direct Debit Initiation Version 2 (pain ) Payment Status Report Version 3 (pain ) Further Customer-to-Bank Payment Initiation messages may be added in a later phase. Chapter 3 deals with the Bank-to-Customer Account Reporting messages. Maintenance The current version of this document is based on version 2/3 of the above pain messages. Publication of new versions of these messages on may require the document to be revised at a future date, in concert with the approval and publication of the associated CGI Message Implementation Templates. Documentation The standards covered by this document are fully described in : ISO Message Definition Report Payment Initiation (www.iso20022.org). This report contains the full description of the standards (scope, format specifications, definitions for all elements, rules and guidelines defined for the generic standards). It contains 9 Standards MX Message Implementation Guide (Dec 2011)

10 SWIFT for Corporates descriptions for the full ISO Payment Initiation portfolio, ie, it also included other payment initation messages. ISO Message schema s and samples (pain , pain and pain ) (www.iso20022.org) ISO Customer to Bank Message Usage Guide Customer Credit Transfer Initiation, Customer Direct Debit Initiation and Payment Status Report (www.iso20022.org). When published, the ISO Message Usage Guide ( MUG ) will provide generic illustrations and explanations about the standard. It is designed to complement the ISO Message Definition Report. SWIFTStandards MX Message Reference Guide (www.swift.com/corporates/resource.htm) contains the same information as the ISO Message Definition Report, but includes the cash reporting messages and is also available in HTML format. CGI Message Implementation Template (www.swiftcommunity.net/cgi) contains the specific rules and implementation guidance. The documentation referred to above contains the full standard specifications and rules that must be adhered to. This document contains further explanatory notes and additional usage rules and guidelines to facilitate common implementation and usage of these standards using FileAct in SCORE (Standardised Corporate Environment). 2.2 Customer Credit Transfer Initiation Scope The Customer Credit Transfer Initiation message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of funds from the debtor account to a creditor. Standard Specifications The ISO Message Definition Report and when published/updated the ISO Customer-to-Bank Message Usage Guide serve as the main documents describing the standards. Please consult these documents for full information. CGI Message Implementation Templates The following CGI Message Implementation Templates provide the specific usage rules and guidelines. Please consult these documents for full information. Template Name Date ISO Credit Transfer V3 Message Implementation Guide 13 June 2011 Appendix A Payment System References Appendix B Country Specific Requirements Latest version Latest version Message Schema Components The Customer Credit Transfer Initiation message is composed of the structures that follow. 10 Standards MX Message Implementation Guide (Dec 2011)

11 Payment Initiation Customer Credit Transfer Initiation (pain ) Message Level 11 Standards MX Message Implementation Guide (Dec 2011)

12 SWIFT for Corporates Customer Credit Transfer Initiation (pain ) Transaction Level 12 Standards MX Message Implementation Guide (Dec 2011)

13 Payment Initiation Specific Rules and Guidelines In the framework of this document, where additional SCORE specific rules and guidelines have been defined these are notated below as SCORE Rule or SCORE Guideline. Where an earlier SCORE Rule has been superseded by a CGI Rule these are noted as CGI Rule or CGI Guideline and have been retained for consistency reasons in this version of the guide. File SCORE Rule Per FileACT file, include only 1 pain message Payment Type Information 2.6 / 2.31 (Payment Information/Payment Type Information and Credit Transfer Transaction Information/ Payment Type Information) (0..1) CGI Rule Required at either Payment or Transaction Level, but should not be present at both levels. Recommended usage is at Payment level. Charge Bearer 2.24 / 2.51 (Payment Information/Charge Bearer and Credit Transfer Transaction Information/Charge Bearer) (0..1) CGI Rule Conditional based on payment transaction. Should be used exclusively at the payment or transaction level. Ultimate Debtor 2.23 / 2.70 (Payment Information/Ultimate Debtor and Credit Transfer Transaction Information/ Ultimate Debtor) (0..1) CGI Rule Conditional based on business need and payment transaction. Batch Booking 2.3 (Payment Information/BatchBooking) (0..1) SCORE Guideline 1 Batch Booking can be populated as an optional element but is not required. SCORE Guideline 2 SCORE Guideline 3 If Batch Booking is not present, pre-agreed client-bank conditions will apply. The Batch Booking element is a request, not an order. If batch booking is requested, banks will respect this request on a best effort basis : ie, the logical organization of the message expresses how the corporate intends batch booking to be actioned. Banks will try to book as such. Banks will pre-agree with their customer criteria for batching (depending on payment type, etc). 13 Standards MX Message Implementation Guide (Dec 2011)

14 SWIFT for Corporates Instruction Priority 2.32 (Payment Information/PaymentTypeInformation/Instruction Priority) (0..1) CGI Rule SCORE Guideline Based on whether priority processing versus normal processing is offered by the bank. If not present, following applies : Instruction Priority is an in-bank processing queue priority where the bank offers the ability to change the priority for processing of a transaction type. It is only used in these cases and its absence is read as normal processing priority for the bank s normal service level for that transaction type and customer. There is no relationship between instruction priority and category purpose. Service Level 2.33 (Payment Information/PaymentTypeInformation/Service level (0..1) CGI Rule If an instrument or country is not listed on CGI Appendix A (Payment System References), agreement will be bilateral until included on the list. SCORE Guideline If the initiating party would like to request a payment to be processed as a SEPA payment, it is recommended to provide the code SEPA in Service Level/Code. Banks will make best efforts to process as such, i.e. are not bound to guarantee that the transaction will indeed be processed as SEPA as it will depend on certain criteria whether the bank can do so. 14 Standards MX Message Implementation Guide (Dec 2011)

15 Payment Initiation Local Instrument 2.36 (Payment Information/PaymentTypeInformation/Local instrument) (0..1) CGI Rule If an instrument or country is not listed on CGI Appendix A (Payment System References), agreement will be bilateral until included on the list. Remittance Identification 2.92 (Payment Information/CreditTransferTransactionInformation/RelatedRemittance Information/RemittanceIdentification) (0..1) SCORE Guideline If the Related Remittance Information component is used, and a Remittance Identification is provided, it is recommended that the RemittanceIdentification equal the EndToEndIdentification. References The message contains a number of mandatory and optional references. The definition of these references can be found in the ISO Message Definition Report. The most recent ISO Customer-to-Bank Message Usage Guide for the Customer Credit Transfer Initiation message contains a large number of explanatory illustrations and scenarios. Below find a short extract of the ISO Customer-to-Bank Message Usage Guide to provide context around the rules and guidelines. Point-to-point references : 1.1 Message ID (1..1) 2.1 Payment Info ID (1..1) 15 Standards MX Message Implementation Guide (Dec 2011)

16 SWIFT for Corporates Payment transaction reference : 2.29 Instruction ID (0..1) 2.30 End to End ID (1..1) Underlying transaction (remittance) references : Remittance Identification Creditor Reference Referred document number Mandatory references which are included in the standard are the Message ID, Payment Info ID and the End-to-End ID. The End to End ID should be carried through the end-to-end payment chain, and be reported to the Creditor. The End to End ID is a payment reference generated by the originator. It can form the basis for a beneficiary who wants to investigate the payment transaction. Note : The End-to-End ID is intended as a unique identifier exchanged between the debtor and creditor and is not intended for use by the agents of the interbank chain. They will use other references as the primary key in tracking and investigating transactions. Reference Truncation principle SCORE Rule If references need to be truncated by the Debtor s Agent (in view of existing length constraints in legacy applications/interbank clearing and settlement systems), they will always be truncated from the right. Duplicate checking Is an optional service to be agreed on between bank and customer. Duplicate checking SCORE Guideline Set of elements to be used : File level : Group Header/Message ID Transaction : Credit Transfer Transaction/EndToEnd ID Unique by sender/customer Id :Other elements identified by bank 16 Standards MX Message Implementation Guide (Dec 2011)

17 2.3 Payment Status Report Scope Payment Initiation The Payment Status Report message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It may also be used to report on a pending instruction. Standard Specifications The ISO Message Definition Report and the ISO Customer-to-Bank Message Usage Guide serve as the main documents describing the standards. Please consult these documents for full information. CGI Message Implementation Templates The following CGI Message Implementation Template provides the specific usage rules and guidelines. Please consult these documents for full information. Template Name Date ISO Payment Status Report V3 Message Implementation Guide 13 June 2011 Message Schema Components The Payment Status Report message is composed of the following structure. 17 Standards MX Message Implementation Guide (Dec 2011)

18 SWIFT for Corporates Payment Status Report (pain ) Message Level 18 Standards MX Message Implementation Guide (Dec 2011)

19 Payment Initiation Payment Status Report (pain ) Transaction Information and Status Level 19 Standards MX Message Implementation Guide (Dec 2011)

20 SWIFT for Corporates Payment and Status Flow The diagrams below from CGI illustrate the potential usage scenarios covered by the Payment Status Report. 20 Standards MX Message Implementation Guide (Dec 2011)

21 Payment Initiation 21 Standards MX Message Implementation Guide (Dec 2011)

22 SWIFT for Corporates Specific SCORE Rules and Guidelines In the framework of this document, a set of minimum usage rules has been defined. All banks subscribing to the SCORE service agree to comply with these minimum usage rules. Further status reporting service offering is to be agreed bilaterally between the customer and its bank. Subscribers to the SCORE service agree to always provide back a Payment Status Report back to the initiating party after receiving a Customer Credit Transfer Initiation message. The diagram and the table below illustrate the usage scenarios covered by the Payment Status Report in the framework of this document.it corresponds to the second scenario above (Support of Payment and Transaction Status Report message - one or more messages) The diagram includes the two main checkpoints at which a Payment Status Report will/can be sent Banks agree to always send a Payment Status Report at checkpoint 1. At checkpoint 2, a Payment Status Report must only be sent if transactions cannot be executed (as minimum rule in this document). As stated above, further status reporting service offering is to be agreed between a customer and its bank. Payment Status Report at checkpoint 1 (illustrated in diagram above) SCORE Rule 1 1. All transactions included in the Customer Credit Transfer Initiation are positive : Group Status must be present and contains : a. ACTC Accepted Technical Validation Authentication and syntactical and semantical validation are successful. 22 Standards MX Message Implementation Guide (Dec 2011)

23 Payment Initiation Or b. ACCP Accepted Customer Profile Preceding check of technical validation was successful. Customer profile check was also successful. In this scenario, no further information on Transaction level is provided. It needs to be pre-agreed between a customer and its bank which of these values will be provided. SCORE Rule 2 2. The complete message is rejected ie the lifecycle of all instructions included in the initiation message stops. Group Status must be present and contains RJCT Rejected. Status Reason information (in Original Group Information and Status) can be included to provide further reasons for the reject. SCORE Rule 3 3. Some transactions included in the initiation are accepted, others are rejected, pending or accepted with change. Group Status must be present and contains PART Partially Accepted. Banks will offer a choice (in Transaction Information and Status level/transaction Status) ) between providing: > only a status for those transactions which are rejected (RJCT) and/or pending (PDNG) Or > a status for each transaction (ACTC Accepted Validation/ACCP Accepted Customer Profile/ACWC Accepted with Change/PDNG Pending/RJCT Rejected) It needs to be pre-agreed between a customer and its bank which of these 2 modes needs to be provided. SCORE Rule 4 Minimum set of data when referring to an original individual transaction in the Payment Status Report : mandatory to include the End to End ID optional to include the Instruction ID (when present in the initiation) mandatory to include the Payment Info ID (when present in the initiation) Inclusion of additional original transaction details in the Payment Status Report to refer to a particular transaction needs to be preagreed between a customer and its bank. Payment Status Report at checkpoint 2 (illustrated in diagram above) Is mandatory only if transactions cannot be executed. SCORE Rule 1 If a first Payment Status Report has been sent with ACTC or ACCP as Group Status, and, during the further process, all, some or one of the transactions cannot be processed by the Debtor Agent, the Debtor Agent must send a Payment Status Report. Group Status information should not be present and Transaction Status must contain : Rejected. 23 Standards MX Message Implementation Guide (Dec 2011)

24 SWIFT for Corporates Reason Information for the Reject can be included in the Status Reason information. In this case, the Payment Status Report will only include those transactions that are rejected. The same minimum data set as quoted under Rule 4 should be included to refer to an individual transaction. 24 Standards MX Message Implementation Guide (Dec 2011)

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

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC115-06 25 November 2014 (Version 8.0 Approved) EPC SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing

More information

SWIFTReady for Corporates Cash Management

SWIFTReady for Corporates Cash Management Service Partners SWIFTReady for Corporates Cash Management Label Criteria 2012 This document explains the business criteria needed to obtain the SWIFTReady for Corporates Cash Management label, aimed at

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

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC115-06 30 November 2012 (Version 7.0 Approved) EPC SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing

More information

Danish Implementation Guideline for Common Global Implementation (CGI) Customer Payment Status Report

Danish Implementation Guideline for Common Global Implementation (CGI) Customer Payment Status Report Danish Implementation Guideline for Common Global Implementation (CGI) Customer Payment Status Report based on documentation from ISO 20022 Message Definition Report December 15th 2012 FINAL VERSION Page

More information

Payment Status Report

Payment Status Report Payment Status Report Implementation Guidelines Version 1.0 Beligian Finance Sector Federation rue d Arlon, 82 B-1040 Brussels http://www.febelfin.be T +32 2 507 68 11 F +32 2 888 68 11 2 Table of Contents

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

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

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

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

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 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

SEPA DATA MODEL. Reason for Issue Approved by the EPC Plenary on 13 December 2006

SEPA DATA MODEL. Reason for Issue Approved by the EPC Plenary on 13 December 2006 Doc: EPC029-06 (Version 2.2) 13 December2006 OITS SG SEPA DATA MODEL Abstract Document Reference Issue This document sets out the SEPA Data Model which is referred to in the SEPA Credit Transfer and Direct

More information

Electronic Bank Account Management - EBAM

Electronic Bank Account Management - EBAM Electronic Bank Account Management - EBAM This guide provides an overview of s EBAM offering. It includes a definition of the scope of the offering as well as a high level description of its building blocks.

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

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

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

Date: 8 January 2009 (Message Versions: pain.001.001.02, pain.008.001.01, pain.006.001.01, pain.007.001.01 and pain.002.001.02)

Date: 8 January 2009 (Message Versions: pain.001.001.02, pain.008.001.01, pain.006.001.01, pain.007.001.01 and pain.002.001.02) ISO 20022 Customer-to-Bank Message Usage Guide Customer Credit Transfer Initiation, Customer Direct Debit Initiation, and Payment Status Report Version 3.0 Date: 8 January 2009 (Message Versions: pain.001.001.02,

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

SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES

SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Doc: EPC114-06 19 June 2007 (Version 2.3 ) OITS SG SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the SEPA rules for implementing the direct

More information

ISDA International Swaps and Derivatives Association, Inc.

ISDA International Swaps and Derivatives Association, Inc. STANDARD SETTLEMENT INSTRUCTIONS REPOSITORY Best Practice Requirements August 2010 Table of Contents 1 REVISION HISTORY... 2 2 PROBLEM STATEMENT... 3 3 DOCUMENT PURPOSE... 3 4 SCOPE... 3 5 STANDARD SETTLEMENT

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

SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC114-06 25 November 2014 (Version 8.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing

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

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

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

One for All How Companies Can Benefit from the Standardised ISO 20022 CGI Format for Global Payments

One for All How Companies Can Benefit from the Standardised ISO 20022 CGI Format for Global Payments One for All How Companies Can Benefit from the Standardised ISO 20022 CGI Format for Global Payments November 2013 by Thomas Keim, Senior Consultant, Hanse Orga The standardised ISO 20022 CGI message format

More information

Standards MT Migration Guide

Standards MT Migration Guide Solutions SWIFT for Corporates Standards MT Migration Guide MT Migration 2009 Version 1.0 This document provides guidance for the November 2009 mandatory migration from the MT 103, Customer Credit Transfer,

More information

SWIFT for Corporates SPIN 2009. Barbara Sacchi. 15 th June 2009

SWIFT for Corporates SPIN 2009. Barbara Sacchi. 15 th June 2009 SWIFT for Corporates SPIN 2009 Barbara Sacchi 15 th June 2009 Business needs Cash visibility has become critical Where is my cash? Can I move my cash? Can I reach all my banks? MT 940 MT 101 Multi-bank

More information

RECOMMENDATION ON CUSTOMER REPORTING OF SEPA CREDIT TRANSFERS AND SEPA DIRECT DEBITS

RECOMMENDATION ON CUSTOMER REPORTING OF SEPA CREDIT TRANSFERS AND SEPA DIRECT DEBITS Doc: EPC188-09 27 October 2009 (Version 1.01 Approved) EPC RECOMMENDATION ON CUSTOMER REPORTING OF SEPA CREDIT TRANSFERS AND SEPA DIRECT DEBITS 0 Background With ISO 20022 standards mandatory in the Rulebooks

More information

SWIFT Certified Application for Corporates - Trade and Supply Chain Finance

SWIFT Certified Application for Corporates - Trade and Supply Chain Finance Service Partner Programme SWIFT Certified Application for Corporates - Trade and Supply Chain Finance Label Criteria 2016 This document explains the business criteria required to obtain the SWIFT Certified

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

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

Interface Certification for a RMA Interface

Interface Certification for a RMA Interface Title Page Interface Certification for a RMA Interface STAR/RMA Conformance Statement Table of Contents Title Page... 1 1 General Information... 3 1.1 Supplier... 3 1.2 Product Information... 3 1.3 Operational

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

Frequently Asked Questions

Frequently Asked Questions Reference Data SEPA Plus Frequently Asked Questions This document describes the most Frequently Asked Questions (FAQs) about the SEPA Plus product. This includes information about the SEPA Plus files and

More information

XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands

XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information

More information

SEPA CREDIT TRANSFER SCHEME RULEBOOK

SEPA CREDIT TRANSFER SCHEME RULEBOOK EPC125-05 Version 7.2 Approved Date issued: 4 March 2015 Date effective: 3 April 2015 SEPA CREDIT TRANSFER SCHEME RULEBOOK Conseil Européen des Paiements AISBL Cours Saint-Michel 30 B 1040 Brussels Tel:

More information

The successful introduction of a payment factory

The successful introduction of a payment factory Global Transaction Banking The successful introduction of a payment factory Implementing integration solutions based on best-practice components The purpose of this white paper The white papers published

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

Transactions User Guide (Internet)

Transactions User Guide (Internet) Version Oct 2011 Pg 1 of 256 Table of Contents Purpose...5 1. Transaction Flow Overview...5 2. Bulk Import...6 2.1. Import...6 2.2. Batch Instructions...8 3. Create Transaction From Template...10 4. Copy

More information

Payments Market Practice Document. ISITC Settlements Working Group

Payments Market Practice Document. ISITC Settlements Working Group Payments Market Practice Document ISITC Settlements Working Group Publication Date: October, 2012 Author(s): ISITC Settlements Working Group DISCLAIMER This market practice document has been developed

More information

ING Service for SWIFTNet. 1A single gateway for your financial information!

ING Service for SWIFTNet. 1A single gateway for your financial information! ING Service for SWIFTNet 1A single gateway for your financial information! ING Service for SWIFTNet ING Service for SWIFTNet offers you the possibility to send and receive financial information anywhere

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

Service Description. Standards Developer Kit. Standards

Service Description. Standards Developer Kit. Standards Standards Standards Developer Kit Service Description This service description describes the features and functions of the SWIFT Standards Developer Kit. The document also describes the roles and responsibilities

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

SEPA formats - an introduction to XML. version September 2013. www.ing.be/sepa

SEPA formats - an introduction to XML. version September 2013. www.ing.be/sepa Financial Supply Chain SEPA SEPA formats - an introduction to XML version September 2013 www.ing.be/sepa INTRODUCTION 1 INTRODUCTION TO XML 2 What is XML? 2 What is a root element? 2 What are the specifications

More information

Functional specification for Payments Corporate egateway

Functional specification for Payments Corporate egateway Functional specification for Payments Corporate egateway 2(53) Page Table of contents 1 Introduction... 5 1.1 Explanation of definitions for EDIFACT & XML ISO20022 6 1.2 Level descriptions for EDIFACT

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

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

BUSINESS JUSTIFICATION

BUSINESS JUSTIFICATION BUSINESS JUSTIFICATION FOR THE DEVELOPMENT OF NEW ISO 20022 FINANCIAL REPOSITORY ITEMS A. Name of the request: Real Time Payments B. Submitting organisation: Payments Council Limited UK C. Scope of the

More information

ISO 20022 Message Implementation Guide for Payment Initiation

ISO 20022 Message Implementation Guide for Payment Initiation ISO 20022 Message Implementation Guide for Payment Initiation Pain001 Pain002 Version: 1.5 Issue date: 16 November 2015 Author: Swedbank Table of Contents 1. Introduction 2. Customer Credit Transfer Initiation

More information

SWIFT supporting the corporate market

SWIFT supporting the corporate market SWIFT supporting the corporate market Elie Lasker SWIFT Journée SWIFTNet pour les entreprises - Reuters Utsit, Paris, 12th February Slide 1 Journée SWIFTNet pour les entreprises - Reuters Utsit, Paris,

More information

SEPA Reason Codes. Direct Debit Customer to Bank Implementation Guidelines

SEPA Reason Codes. Direct Debit Customer to Bank Implementation Guidelines SEPA Reason s The SEPA reason codes in this document are sourced from the following European Payments Council Implementation Guideline documentation which detail the customer-to-bank and inter-bank formats

More information

BUSINESS JUSTIFICATION

BUSINESS JUSTIFICATION BUSINESS JUSTIFICATION FOR THE DEVELOPMENT OF NEW UNIFI (ISO 20022) FINANCIAL REPOSITORY ITEMS A. Name of the request: Bank Account Management (BAM) B. Submitting organization(s): S.W.I.F.T. scrl Standards

More information

Functional specifications for Nordea XML Direct Debit (NDD) Corporate egateway

Functional specifications for Nordea XML Direct Debit (NDD) Corporate egateway Functional specifications for Nordea XML Direct Debit (NDD) Corporate egateway Table of contents 1 Introduction... 1 1.1 NDD documents 1 2 Basic description of the NDD service... 1 2.1 Basic architecture

More information

SEPA INSTANT CREDIT TRANSFER SCHEME RULEBOOK. Version 0.1 for public consultation. from 12 April to 10 July 2016

SEPA INSTANT CREDIT TRANSFER SCHEME RULEBOOK. Version 0.1 for public consultation. from 12 April to 10 July 2016 EPC 004-16 Version 0.1 for public consultation 12 April 2016 SEPA INSTANT CREDIT TRANSFER SCHEME RULEBOOK Version 0.1 for public consultation from 12 April to 10 July 2016 Conseil Européen des Paiements

More information

MT104 Direct Debit and Request for Debit Transfer Message.

MT104 Direct Debit and Request for Debit Transfer Message. MT104 Direct Debit and Request for Debit Transfer Message. Change log Version Date Edit 1 10.11.2003 Document created 2 22.10.2005 Updated with German Direct Debit 3 21.03.2006 Updated with English Irish

More information

SWIFT for high-value payment market infrastructures. End-to-end solutions for payment clearing and settlement

SWIFT for high-value payment market infrastructures. End-to-end solutions for payment clearing and settlement SWIFT for high-value payment market infrastructures End-to-end solutions for payment clearing and settlement 1 Table of contents Introduction 03 03 Executive Summary 04 04 Evolving demand 05 05 SWIFT s

More information

White Paper on Extended Remittance Information (ERI) and Payment Notification

White Paper on Extended Remittance Information (ERI) and Payment Notification White Paper on Extended Remittance Information (ERI) and Payment Notification (Version 1.0, February 2015) Note: Relevant regulations and any applicable legislation take precedence over the guidance notes

More information

SEPA as a driver for streamlining receivables

SEPA as a driver for streamlining receivables SEPA 2.0: Opportunities and challenges after the end-date by Luca Poletto, BNP Paribas Five years after the go-live date of the first Single Euro Payments Area (SEPA) instrument, we are in the last sprint

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

Interactive Financial exchange

Interactive Financial exchange Interactive Financial exchange Understanding the ISO 20022 Stand-Alone Remittance Messages June 2014 Interactive Financial exchange Forum, Inc. Publications http://www.ifxforum.org Copyright 2014, by the

More information

Offshore CNY Guidelines. for. SWIFT MT and ISO 15022 Messages

Offshore CNY Guidelines. for. SWIFT MT and ISO 15022 Messages Offshore CNY Guidelines for SWIFT MT and ISO 15022 Messages Offshore CNY guidelines v 3.0 August 2014 Page 1 August 2014 Version 3 Legal Notices Disclaimer The information in this publication may change

More information

IBM Financial Services Sector. IBM Payment Platform to face SEPA A flexible approach for a Smarter Bank

IBM Financial Services Sector. IBM Payment Platform to face SEPA A flexible approach for a Smarter Bank IBM Payment Platform to face SEPA A flexible approach for a Smarter Bank Market Forces Driving the Payments Industry to Transform Economic Pressures Increasing pressures on fees Margins being squeezed

More information

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands Core and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.

More information

BUSINESS JUSTIFICATION

BUSINESS JUSTIFICATION BUSINESS JUSTIFICATION FOR THE DEVELOPMENT OF NEW UNIFI (ISO 20022) FINANCIAL REPOSITORY ITEMS Name of the request: Payments Mandates Submitting organization: SWIFT SCRL Avenue Adèle, 1 1310 La Hulpe Belgium

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

Frequently Asked Questions

Frequently Asked Questions This document describes (FAQs) about IBAN Plus. This includes the IBAN Plus product, how to use the product, the quality of the data, and IBAN regulations and standards. This document is for anyone who

More information

The role of banks to support the SME s business models in the international landscape

The role of banks to support the SME s business models in the international landscape The role of banks to support the SME s business models in the international landscape Liliana Fratini Passi ABI - Secretary General CBI Consortium Member - UN/CEFACT TBG5 Member of Expert Group on E-Invoicing

More information

SEPA Country-Specific Information Italy

SEPA Country-Specific Information Italy SEPA Country-Specific Information Italy Cash Management & ebanking January 2014 Contents INTRODUCTION 3 END-DATE INFORMATION 3 IBAN CONVERSION SERVICE 3 SEPA PRODUCTS 4 SEPA CREDITOR IDENTIFIER (CI) 6

More information

Spanish legacy branch code 4 numbers. Spanish legacy bank code 4 numbers

Spanish legacy branch code 4 numbers. Spanish legacy bank code 4 numbers SEPA in Spain Useful links Spanish official SEPA website (in Spanish language) http://www.sepaesp.es/ National Central Bank of Spain www.bde.es/bde/en Official Migration Guide for the Spanish market Download

More information

SEPA Country Guide Italy. Introduction

SEPA Country Guide Italy. Introduction Introduction This document provides an overview of all the country specific information you need to successfully implement your migration to SEPA in Italy. Intending to provide a global picture of the

More information

RF Creditor Reference

RF Creditor Reference RF Creditor Reference Facilitating full end-to-end straight-through payment processing version 1.0, May 2010 RF Expert Group 2 (36) Page RF Creditor Reference... 1 Facilitating full end-to-end straight-through

More information

March 2014. Euro Payment. Manual

March 2014. Euro Payment. Manual March 2014 Euro Payment Manual Contents 1 Introduction 2 Euro Payment: characteristic features 2.1 Introduction 2.2 Differences compared to the Dutch credit transfer 2.3 IBAN and BIC 2.4 Timelines and

More information

USER INFORMATION GUIDE TO THE TARGET2 PRICING

USER INFORMATION GUIDE TO THE TARGET2 PRICING ATTACHMENT 2 USER INFORMATION GUIDE TO THE TARGET2 PRICING October 2007 Page 1 of 23 USER INFORMATION GUIDE TO THE TARGET2 PRICING Table of contents Introduction 4 1. General Overview of TARGET2 and the

More information

CHAPS Technical Requirements

CHAPS Technical Requirements CHAPS Technical Requirements 1. Technical Overview CHAPS provides a payment system between its Members settling in real time across sterling settlement accounts at the Bank of England. The key components

More information

Corporate egateway Supports a centralised payment and collection factory

Corporate egateway Supports a centralised payment and collection factory Corporate Supports a centralised payment and collection factory Corporate is Nordea s file based mass payment service for customers demanding one point of entry for bulk payments and collections in the

More information

SEPA Country-Specific Information Hungary

SEPA Country-Specific Information Hungary SEPA Country-Specific Information Hungary Cash Management & ebanking January 2014 Contents INTRODUCTION 3 END-DATE INFORMATION 3 IBAN CONVERSION SERVICE 3 SEPA PRODUCTS 4 SEPA CREDITOR IDENTIFIER (CI)

More information

SEPA Direct Debit Unpaid Report File Format

SEPA Direct Debit Unpaid Report File Format SEPA Direct Debit Unpaid Report File Format PAIN.002.001.03 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document

More information

Market Practice Guidelines for use of field 50a, Ordering Customer to comply with FATF SR VII (Version 1.8, June 2010)

Market Practice Guidelines for use of field 50a, Ordering Customer to comply with FATF SR VII (Version 1.8, June 2010) Market Practice Guidelines for use of field 50a, Ordering Customer to comply with FATF SR VII (Version 1.8, June 2010) Note: Relevant regulations and any applicable legislation take precedence over the

More information

Alliance Access Integration MQ Host Adaptor

Alliance Access Integration MQ Host Adaptor Alliance Access Integration MQ Host Adaptor Technical Qualification Test 2014 This document lists the tests for application providers that integrate their back-office application or middleware with Alliance

More information

SEPA CREDIT TRANSFER SCHEME RULEBOOK

SEPA CREDIT TRANSFER SCHEME RULEBOOK EPC125-05 Version 8.2 Date issued: 03 March 2016 Date effective: 01 April 2016 SEPA CREDIT TRANSFER SCHEME RULEBOOK Conseil Européen des Paiements AISBL Cours Saint-Michel 30 B 1040 Brussels Tel: +32 2

More information

Cross-Border Payment Systems and International Remittances

Cross-Border Payment Systems and International Remittances Cross-Border Payment Systems and International Remittances Seminar Improving Central Bank Reporting and Procedures on Remittances Mexico City, Mexico, July 11-14, 2006 José Antonio García The World Bank

More information

SEPA in Netherlands. Quick facts. International Bank Account Number (IBAN) IBAN structure. 66 SEPA Country Sheets - Netherlands

SEPA in Netherlands. Quick facts. International Bank Account Number (IBAN) IBAN structure. 66 SEPA Country Sheets - Netherlands SEPA in Netherlands Useful links Information campaign, by National Forum on SEPA migration www.overopiban.nl IBAN-Acceptgiro information www.acceptgiro.nl/ IBAN BIC conversion service www.ibanbicservice.nl

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

TARGET2-Securities. Settlement services quick guide

TARGET2-Securities. Settlement services quick guide TARGET2-Securities Settlement services quick guide Contents Introduction 05 T2S is getting closer. What you need to know 06 Settlement day schedule 06 Your securities account setup 06 Your connectivity

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

SEPA CREDIT TRANSFER SCHEME RULEBOOK

SEPA CREDIT TRANSFER SCHEME RULEBOOK EPC125-05 Version 4.1 approved Date issued: 1 November 2010 Date effective: 1 November 2010 SEPA CREDIT TRANSFER SCHEME RULEBOOK Conseil Européen des Paiements AISBL Av. de Tervueren 12 B 1040 Brussels

More information

The Business Application Header is a header that has been defined by the ISO 20022 community,

The Business Application Header is a header that has been defined by the ISO 20022 community, N3072 Business Application Header Frequently Asked Questions Business Application Header Frequently Asked Questions There has been a lot of discussion about the Business Application Header within the ISO

More information

Connectivity. Alliance 7.0. Alliance Interfaces. FileAct support in SWIFTNet Release 7.0

Connectivity. Alliance 7.0. Alliance Interfaces. FileAct support in SWIFTNet Release 7.0 Connectivity Alliance Alliance Interfaces Act support in SWIFTNet Release February 2012 Table of Contents Preface... 3 1 Introduction... 4 2 Portfolio Act Support... 6 2.1 Alliance Gateway... 6 2.1.1 Overview...

More information

Guide. 1 Dec 2010. Introduction of the global Structured Creditor Reference in Finnish companies. 1 December 2010

Guide. 1 Dec 2010. Introduction of the global Structured Creditor Reference in Finnish companies. 1 December 2010 1 Dec 2010 Guide Introduction of the global Structured Creditor Reference in Finnish companies 1 December 2010 Federation of Finnish Financial Services Contents Guide Introduction of the global Structured

More information

OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE

OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE Version 1.94 13.4.2016 OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE Pain.001.001.02 Pain.002.001.02 2 (51) Sisällysluettelo MANUAL VERSION INFORMATION... 4 1 SEPA CREDIT TRANSFER, ISO 20022 APPLICATION

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

SWIFT for Corporates: Making the Business Case

SWIFT for Corporates: Making the Business Case SWIFT for Corporates: Making the Business Case Vince Bahl, Vice President of Systems Engineering Bottomline Technologies David Levine, Director of Product Marketing Bottomline Technologies 2 Access to

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

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version.

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version. The Deutsche Bundesbank s technical specifications for the clearing and settlement of interbank SEPA credit transfers via the RPS ( SCT/BCT/SCL technical specifications ) Version 2.4 valid from 30 September

More information

ERP SEPA readiness checklist

ERP SEPA readiness checklist ERP SEPA readiness checklist version July 2013 www.ingsepa.com Financial Supply Chain SEPA This list contains 11 questions to determine the level of SEPA-readiness of an ERP 1. The first 3 questions deal

More information