Standards Release 2017 (SR 2017): Frequently Asked Questions related to the SWIFT global payment innovation (gpi) service
|
|
- Anthony Kennedy
- 4 years ago
- Views:
Transcription
1 Standards Release 2017 (SR 2017): Frequently Asked Questions related to the SWIFT global payment innovation (gpi) service Frequently Asked Questions This document describes Frequently Asked Questions (FAQs) about SR 2017 changes linked to SWIFT gpi. This document is intended for anyone who needs more information about the impact of SWIFT gpi on Market Infrastructures and Financial Institutions (including gpi and non-gpi banks) in SR April 2017
2 Table of Contents Table of Contents... 2 Preface... 3 Purpose of the document... 3 Intended Audience... 3 Related documentation What is SWIFT gpi? What is SWIFT gpi? Where can I find more information about SWIFT gpi? Who can become a SWIFT gpi member? Background info about SWIFT gpi-related fields in FIN MT Which fields distinguish a gpi payment from a non-gpi payment? What is the Unique End-to-End Transaction Reference (UETR)? What is the Service Type Identifier? Who will use the UETR and Service Type identifier? How will I be informed of future standards-related changes related to gpi? SWIFT gpi-related changes in SR 2017 for banks What are the SWIFT gpi-related changes in SR 2017 for banks? As a non-gpi bank, can I forward gpi fields to the next party in the transaction chain? Will SWIFT validate the gpi-data in the Header of the MT 103? How can I test that I am able to receive the gpi-related data in the MT 103? What about MT 202 COV? What about the MT 199? What about the MT 101? What about the MX payments messages? What about the impact on FINInform? As a non-gpi Bank, how will the gpi Tracker use my data? SWIFT gpi-related changes insr 2017 Impact on Market Infrastructures What is the impact on Market infrastructures using FINCopy (Y or T-mode)? Are other FINCopy features or messages impacted? What can a Market Infrastructure do with gpi data? How can a Market Infrastructure on Y-Copy test the gpi fields? How will payment Market Infrastructure using SWIFT in V-shape mode support gpi transactions? What about Payment Market Infrastructures using FINInform? What about Payment Market Infrastructures not using SWIFT? What about Payment Market Infrastructures with plans to implement ISO 20022? Legal Notices April
3 Preface Purpose of the document This document describes Frequently Asked Questions (FAQs) about the SR 2017 impact of changes linked to SWIFT gpi on Market Infrastructures and financial institutions (gpi and nongpi banks). Intended Audience This document is for the following audience: Technical implementers of the Standards MT messages Operational users of the Standards MT messages All other interested SWIFT users Related documentation Standards MT Release 2017 timeline Standards MT Release Guide 2017: Standards Release Guide FIN System Messages Advance Information FIN Operations Guide Advance Information Extended Use of SWIFT gpi Fields 111 and 121 SWIFT gpi: Recording of webinars: April
4 1. What is SWIFT gpi? 1.1 What is SWIFT gpi? SWIFT s global payments innovation (gpi) is a platform designed to improve the customer experience in cross-border payments by increasing their speed, transparency, and traceability. It is the live service derived from the global payments innovation initiative that was launched in December The SWIFT gpi platform brings together the world s leading transaction banks from Europe, Asia Pacific, Africa and the Americas to significantly improve cross-border payments. SWIFT gpi is a robust response to evolving bank and corporate needs for enhanced customer service and operational efficiency. It delivers an enhanced value proposition for correspondent banking by addressing key challenges the industry faces. To achieve this, gpi banks agree to respect service-specific business rules and technical requirements captured in a rulebook. Live in a SWIFT gpi CUG (Closed User Group) since February 2017, SWIFT gpi focuses on business-tobusiness payments, in a first phase. Designed to help corporates grow their international business, improve supplier relationships, and achieve greater treasury efficiencies, the service enables corporates to experience an enhanced payments service directly from their banks. 1.2 Where can I find more information about SWIFT gpi? Visit or download the brochure to find out more about gpi, its member banks, vision, timeline etc. 1.3 Who can become a SWIFT gpi member? Any supervised financial institution (SUPE) that is a member of SWIFT and adheres to the business rules of the global payments innovation initiative can join the new service and become a gpi member. To receive more information on the benefits of joining gpi directly, please contact us on or visit April
5 2. Background info about SWIFT gpi-related fields in FIN MT 2.1 Which fields distinguish a gpi payment from a non-gpi payment? The SWIFT gpi service relies on the correct usage of the MT 103, MT 103 STP and MT 103 REMIT. Additionally, to flag a payment as a gpi payment, two new fields have been introduced in the User Header (Block 3): Field 121: contains the Unique End-to-End Transaction Reference (UETR) Field 111: contains the gpi Service Type Identifier These fields must be included in the User Header (Block 3) of the FIN MT exchanged in the framework of SWIFT gpi. More information on the FIN Header Block 3 and details of field 111 and 121 are available in the Operations Guide on swift.com. 2.2 What is the Unique End-to-End Transaction Reference (UETR)? An end-to-end payment transaction typically involves multiple MT messages, exchanged between different parties involved in the end-to-end payments chain. In order to uniquely identify and track the lifecycle of the transaction to which these different messages relate, the SWIFT gpi service has introduced the usage of a unique gpi end-to-end transaction reference (UETR), a SWIFT tracking number. The UETR used in SWIFT gpi messages is based on a well-known and mature mechanism for generating such an identifier: the Universally Unique Identifier (UUID), sometimes also known as Globally Unique Identifier (GUID), compliant with IETF standard RFC 4211 using version 4 of the generation algorithm. The format consists of 36!x composed of 32 hexadecimal characters, displayed in 5 groups separated by hyphens: xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx x = any hexadecimal character (lower case only); y is one of 8, 9, a or b. The UUID is designed to be globally unique, without risk of repetition over time. Example: {121:eb6305c9-1f7f-49de-aed c27b42d} The UETR is included in field 121 in the User Header (Block 3 of a SWIFT MT). The UETR is generated by the gpi instructing bank (the first gpi bank in the payment chain) when initiating a payment and communicated together with the gpi Service type Identifier (field 111) in the User Header 2.3 What is the Service Type Identifier? In order to flag a payment as a gpi payment, the gpi instructing bank will include the service type identifier in field 111 of the User Header. The value for the currently defined gpi service type is 001. SWIFT will validate that the service type identifier complies with the format 3!n. The number itself is not validated. Additional numbers may be used in the future for other gpi service types. The Service Type Identifier must always be accompanied by the UETR (field 121) in the User Header. 2.4 Who will use the UETR and Service Type identifier? The unique gpi end-to-end transaction reference (UETR) is generated by the gpi instructing bank (the first April
6 gpi bank in the payment chain) when initiating a payment and communicated together with the gpi service type identifier in the User Header of the payment MT. These fields are transported throughout the gpi end-to-end payment s lifecycle: Field 111 and field 121 must both be present or both absent (error code U12) Together these two fields will: highlight to the receiving gpi bank that the payment has to be processed according to the service level guaranteed in the gpi rulebook, allow SWIFT to update the gpi tracker with real-time status information about a specific transaction allow gpi banks to consult and update the status of a specific transaction in the gpi tracker As of SR 2017, gpi banks will be able to send these two new fields to non-gpi banks as well. Non-gpi banks will not be allowed to create or forward these 2 fields: Use of field tags 111 and 121 is restricted to the gpi Closed User Group (error code G27) 2.5 How will I be informed of future standards-related changes related to gpi? Future gpi standards-related changes will be communicated as per the normal SWIFT Standards Release process. April
7 3. SWIFT gpi-related changes in SR 2017 for banks 3.1 What are the SWIFT gpi-related changes in SR 2017 for banks? gpi-related data in MT 103/MT 103 STP/MT 103 REMIT Since SR 2016, gpi banks can already exchange gpi payments with field 111 and 121 in the User Header, in the gpi Closed User Group (CUG). The change request for SR 2017 was given the number CR and requested non-gpi MT 103 message receivers to be able to receive the field 111 and field 121 in the User Header. The submitter was the gpi community, sponsored by US NMG. The main aim was to enhance the end-to-end tracking of payments when non gpi banks are involved in the payment (also 1 leg outside the gpi CUG) and facilitate payments input by allowing gpi banks to put the extra fields in all MTs 103 they send, irrespective of the receiver being a gpi bank or a non-gpi bank. 3.2 As a non-gpi bank, can I forward gpi fields to the next party in the transaction chain? For SR 2017, non-gpi banks cannot forward the gpi-related fields in the header of the MT 103. It was agreed that non-gpi banks must be able to receive the gpi data in the User Header only, no processing or forwarding requirements. Should this become a requirement in the future, a change request will need to be raised, which will be handled as part of a (future) normal standards release process. In case a non-gpi bank sends the gpi data in the User Header, it will receive a NAK (error code G27). 3.3 Will SWIFT validate the gpi-fields in the Header of the MT 103? SWIFT will validate that: The sender is registered to the gpi CUG (error code G27) gpi fields (111 and 121) are both present or absent in the User Header (error code U12) the format of the UETR complies with xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx where x is any hexadecimal character (lower case only) and y is one of 8, 9, a, or b the format of the Service Type Identifier is correct (3!n) 3.4 How can I test that I am able to receive the gpi-related data in the MT 103? For banks wanting to test the new fields, SWIFT s Test and Training system will be available as of 23 July FIN has a repository of sample messages known as the tank file. A Test and Training user can request FIN to generate and output a sample of FIN current or future user-to-user Test and Training messages. SWIFT will add MT 103 sample messages which contain the new gpi data to the tank file. You can request these MT messages by sending an MT 073 Message Sample Request. More information is available in the FIN Service Description. April
8 3.5 What about the MT 202 COV? In SR 2017, non-gpi banks only have to be able to receive the UETR and service type identifier in the MT 103, MT 103 STP and MT 103 REMIT. SWIFT gpi banks are already sending and receiving MT 103s with gpi-fields in the User Header in the gpi CUG. As part of the evolving gpi service portfolio, gpi banks may start exchanging other payment messages in the gpi CUG, such as the MT 202 COV This will allow tracking of MT 202 cover flows (related to the MT 103) and notifying the cover parties in case of settlement issues, missing or non-compliant cover. As gpi banks will exchange MT 202 COV in the gpi CUG, the implementation can be done outside of the Standards Release process. The same also applies to the MT 205 COV. These evolving requirements may result in future change requests that could impact non-gpi banks. Change requests will be handled through the normal Standards Release process. 3.6 What about the MT 199? gpi banks currently exchange MT 199s to update the transaction status in the gpi tracker within the gpi CUG. As of April 2017, gpi banks can exchange these MT 199s with the gpi tracker, or use API calls to update/receive info from the gpi tracker. This means there is no impact on the MT 199 for non-gpi financial institutions. 3.7 What about the MT 101? In the first phase gpi business rules are only applicable to gpi banks for their correspondent banking flows. SWIFT is working together with the whole community (banks, corporates and partners) to explore business rules for corporates to be able to flag a gpi payment within the credit transfer request (MT 101 Request for Transfer and ISO payment initiation messages). For more information contact SWIFT at Today, in order to benefit from the gpi service, corporates need to agree with their banks to initiate gpi payments for specific flows and currencies; this will be covered by the T&C s agreed with each bank. 3.8 What about the MX payments messages? Because the gpi service is focussing on correspondent banking, the decision was in a first phase to look at the MT payments messages, as today there is no official migration plan towards ISO in the correspondent banking space (which does exist in the MI space, see question 4.7). The possible use of ISO in a later phase of gpi will be discussed by the gpi vision group. For more information contact SWIFT at 3.9 What about the impact on FINInform? As part of normal FINInform processes, the complete Header Block of user-to-user messages is included in the MT 096 copied to a copy destination for the MT messages indicated in the parameters of the FINInform service. If the MT 103 is part of this, there will be an impact (in SR 2017) on the MT 096 if the sender of the original MT 103 message is a gpi bank and included field 111 and field 121 in the User Header of the original message. The information of the MT 103 will be present in block 4 of the MT 096 (also when the parameters of FINInform only indicate a partial copy, because the partial is only linked to block 4 of the original MT 103). April
9 {1:F01BANKGB2LACMR } {2: O DYLPXXXXXXXX S} {3:{ABC}{108: MUR OF MT 096} {4: {1:F01SNDRGB22AXXX } {2:I103RCVRGB2LAXXX U} {3:{108:XY/T44961}{111:001}{121:eb6305c9-1f7f-49de-aed c27b42d}} {4: :20:TRANSFER :23B:CRED :32A:140902GBP150000,00 :33B:STG150000,00 :50K:/ BIODATA LTD 46 GREEN LANE CAMBORNE CORNWALL TR14 7EQ ENGLAND :59:/ H.F. TRELAWNEY 68 MARK LANE LONDON EC2 ENGLAND :71A:SHA -} {5: {CHK:81EC89D79E80}} {5:{CHK:CHECKSUM OF MT 096}{SYS:SYSTEM TRAILER OF MT 096}} The MT 096 will contain a copy of the original message for all MTs incorporated by the parameters of the specific FINInform service If the gpi service expands to other MT messages (for example MT 202 COV outside the standards release cycle), there will also be an impact on the MT 096 copying the MT 202 COV when both the sender and the receiver are gpi banks, as the MT 096 is payment message agnostic As a non-gpi Bank, how will the gpi Tracker use my data? By enabling non-gpi banks to receive gpi data in payments, the gpi tracker will be able to increase the reach of the transaction status made available through the tracker and confirm the reception of a gpi payment to the previous agents in the transaction chain. Information that will be available in the tracker: The sender s reference (field 20) of the message that was sent to the non-gpi bank The date and time when the non-gpi bank received the message (based on the UAK (User Acknowledgement) Non-gpi banks do not have access to the tracker. April
10 4. SWIFT gpi-related changes in SR 2017 Impact on Payments Market Infrastructures (PMI) 4.1 What is the impact on PMIs using FINCopy (Y or T-mode)? As part of normal FINCopy processes, the complete Header Block of user-to-user messages is included in the MT 096copied to a FINCopy destination. As gpi-related changes introduced in the User Header (new field 111 and 121) were introduced late in the SR 2016 process, it was agreed to temporarily shield Market Infrastructures from the impact of introducing these new fields for gpi banks. This means that, gpi banks can exchange gpi payments across all SWIFT MIs using Y-Copy. For information about the new fields, please see Section 2 of this document. As part of SR 2017, SWIFT will resume its copy-as-usual functionality, which means that MIs using FINCopy, will receive the gpi fields in the MT 096 as part of the User header block of the copied message. Market infrastructures just need to be able to receive the new fields. As gpi banks may start exchanging other payment messages (such as the MT 202COV) in the near future within the gpi Closed User Group (CUG), Market infrastructures should be aware that, if gpi banks exchange these payment messages containing the gpi fields in the User Header, these fields will also be copied to the MT 096. The MT 096 is payment message agnostic; it does not distinguish between a copy of eg MT 103 or MT 202COV. 4.2 Are other FINCopy features or messages impacted? There is no impact on other FINCopy features, nor on any of the other system messages used in FINCopy. 4.3 What can a PMI do with gpi data? As of SR 2017, Market Infrastructures (MIs) using FINCopy must be able to receive the new gpi fields in the MT 096. They do not have to include these fields in any subsequent FINCopy messages. SWIFT will use the data to automatically update the transaction status in the gpi tracker. MIs do not have to update the tracker, nor do they have access to the tracker. As of SR 2017, FINInform users will receive the gpi data as part of the FINCopy to Server Destination April
11 Message (MT 096) linked to the original credit transfer. FINInform also uses the MT 096 to copy the payment message. The same impact as described above applies. 4.4 How can a PMI on Y-Copy test the gpi fields? Market Infrastructures using FINCopy in Y-Copy mode can test the new gpi data elements copied in the MT 096 as of 23 July 2017: Using Local Test Mode to test with SWIFT: SWIFT will add MT 096 and MT 103 sample messages which contain the new gpi data to the tank file. MIs can request these MT 096 messages by sending an MT 073 Message Sample Request. This mode will be available as of 23 July Using Full Function Mode to allow MIs to test with themselves: to enable Market Infrastructures to test with themselves, SWIFT can add the MI test BIC to the test-gpi CUG. MI will need to request this through a dedicated form. This enables the MI to benefit from its full Test and Training environment to send test MT 103s with the new gpi data elements and the service identifier in the User Header between an MI s test-and training destinations. The new gpi data elements will then be included in the MT 096 copied to the FINCopy Test and Training destination, allowing an MI to simulate testing with its service participants. Using Full Function Mode to allow MIs to test with their members: if feasible, Market Infrastructures could set up tests with a number of their service participants, as of 23 July Please contact for additional information. 4.5 How will a PMI using SWIFT in V-shape mode support gpi transactions? For V-shaped payment Market Infrastructures using standard FIN messaging, the same changes as for non-gpi banks will apply. These changes are documented in section 3 of this document. As of SR 2017, gpi banks can send payments with gpi data to these Payment Market Infrastructures (PMI). These PMIs need to be able to receive the gpi fields included in the User Header of the MT 103, MT 103 STP and MT 103 Remit. Market Infrastructures operating in V-shape mode, cannot yet forward the gpi fields in the User Header of the onward MT 103. SWIFT is currently investigating how these Payment Market Infrastructures could potentially forward the gpi data to gpi and non-gpi banks. If you are a Market Infrastructure using SWIFT in a V-shaped mode and interested in supporting gpi payments, please contact us on For details regarding the new gpi fields, see section 2 in this document. 4.6 What about PMIs using FINInform? As of SR 2017, FINInform users will receive the gpi data as part of the FINCopy to Server Destination Message (MT 096) linked to the original credit transfer. FINInform also uses the MT 096 to copy the payment message. The same impact as described in question 4.1 applies. 4.7 What about PMIs not using SWIFT? SWIFT is in contact with some of the world s largest payment Market Infrastructures not using SWIFT to establish local market practices, developed in collaboration with select gpi member Banks and SWIFT, to enable the exchange of SWIFT gpi transactions between their members. Next to available market practices for the Fed, CHIPS and CIPS (RMB), this includes the development of local market practices for Japan and Switzerland. April
12 In addition, SWIFT is actively engaging with key Payment Market Infrastructures worldwide to further extend the gpi experience and ensure global interoperability between domestic and cross-border payments services. 4.8 What about PMIs with plans to implement ISO 20022? For communities that will implement ISO in the (near) future, SWIFT is developing a new global market practice that can be used by any community that will start to adopt ISO for High-Value Payments Systems..All major Payment Market Infrastructures and representatives of PMPG (Payments Market Practice Group) banks are part of this initiative. April
13 Legal Notices Copyright SWIFT All rights reserved. Confidentiality This publication contains SWIFT or third-party confidential information. Do not disclose this publication outside your organisation without SWIFT s prior written consent. Disclaimer SWIFT supplies this publication for information purposes only. The information in this publication may change from time to time. You must always refer to the latest available version. Trademarks SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT: the SWIFT logo, SWIFT, SWIFTNet, SWIFTReady, Accord, Sibos, 3SKey, Innotribe, the Standards Forum logo, MyStandards, and SWIFT Institute. Other product, service, or company names in this publication are trade names, trademarks, or registered trademarks of their respective owners. April
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.
Customer Testing Policy
SWIFT Customer Testing Policy This document provides specific conditions for performance or vulnerability testing of SWIFT services and products and non-swift services and products. This document covers
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
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
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
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
Cross-border CNY Transaction Guidelines for SWIFT MT messages
Cross-border CNY Transaction Guidelines for SWIFT MT messages Sep 2014 V1.0 Legal Notices Disclaimer The information in this publication may change from time to time. the latest available version information
SWIFT Certified Specialist - Consultancy for Trade and Supply Chain Finance Track Criteria
Service Partners SWIFT Certified Specialist - Consultancy for Trade and Supply Chain Finance Track Criteria This document introduces the framework of the SWIFT Certified Specialist (formerly, SWIFTReady
Alliance Access Integration Automated File Transfer
Alliance Access Integration Automated File Transfer Technical Qualification Test 2011 This document lists the tests for application providers that integrate their middleware or back-office application
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...
Alliance Access Integration SOAP Host Adaptor
Alliance Access Integration SOAP Host Adaptor Technical Qualification Test 2013 This document lists the tests for application providers that integrate their back-office application or middleware with Alliance
Interface Certification for a FIN Interface
Title Page Interface Certification for a FIN Interface BOX Messaging Hub (formerly known as BOX For SWIFTNet) Conformance Statement Table of Contents Title Page... 1 1 General Information... 3 1.1 Supplier...
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
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
Reference Data. IBAN Plus. Questions & Answers. This document contains the most frequently asked questions and answers.
Reference Data IBAN Plus Questions & Answers This document contains the most frequently asked questions and answers. Update date: 16 June 2013 Table of Contents Table of Contents... 2 Questions about the
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.
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
Personal Token Software Installation Guide
This document explains how to install and how to remove the token software for your personal token. 20 May 2016 Table of Contents Table of Contents Preface...3 1 Token Software Installation Prerequisites...4
Information paper. Best Practice for Successful Implementation of ISO 20022 for Financial Institutions
Information paper Best Practice for Successful Implementation of ISO 20022 for Financial Institutions Contents Executive summary...3 The ISO 20022 standard...3 Growth of ISO 20022 adoption...4 Adoption
Interface Certification for a Store-andforward InterAct Messaging Interface
Title Page Interface Certification for a Store-andforward InterAct Messaging Interface IBM Sterling B2B Integrator SWIFTNet MEFG Server Conformance Statement Table of Contents Title Page... 1 1 General
Message Usage Guidelines
Standards Category 3 - Treasury Markets - Foreign Exchange, Money Markets, and Derivatives For Standards MT November 2015 Message Usage Guidelines These usage guidelines provide information about Standards
SWIFTNet Online Operations Manager
Messaging SWIFTNet 7.0 SWIFTNet Online Operations Manager Quick Overview December 2010 Table of Contents Preface... 3 1 Introduction... 4 1.1 Background... 4 1.2 SWIFTNet Online Operations Manager... 4
Connectivity. Alliance Access 7.0. Database Recovery. Information Paper
Connectivity Alliance Access 7.0 Database Recovery Information Paper Table of Contents Preface... 3 1 Overview... 4 2 Resiliency Concepts... 6 2.1 Database Loss Business Impact... 6 2.2 Database Recovery
Capturing an Elusive Market
Capturing an Elusive Market The World of Global Remittances Payments 2010 April 28, 2010 Meet the speakers Ernest Gregg, Treasurer, Ria Financial Wendy Miller, Global Payments Manager, BNY Mellon Steve
Connectivity. Alliance Access 7.0. Database Recovery. Information Paper
Connectivity Alliance 7.0 Recovery Information Paper Table of Contents Preface... 3 1 Overview... 4 2 Resiliency Concepts... 6 2.1 Loss Business Impact... 6 2.2 Recovery Tools... 8 3 Manual Recovery Method...
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
SWIFT e-invoicing consultation
SWIFT e-invoicing consultation October 2008 Legal Notices Copyright SWIFT 2008. All rights reserved. You may copy this publication within your organisation. Any such copy must include these legal notices.
White Paper on Dodd Frank Section 1073 Cross-border Remittance Transfers (Version 3.0, September 2013)
White Paper on Dodd Frank Section 1073 Cross-border Remittance Transfers (Version 3.0, September 2013) A partnership initiative between The Clearing House Association, L.L.C. and the PMPG Note: Relevant
SEPA - Frequently Asked Questions
SEPA - Frequently Asked Questions Contents SEPA Overview Questions... 2 What is SEPA?... 2 What is the aim of SEPA?... 3 Where did SEPA come from?... 3 What countries are included in SEPA?... 3 What currencies
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
Global Iris Integration Guide ecommerce Remote Integration
Global Iris Integration Guide ecommerce Remote Integration February 2013 Table Of Contents 1 About This Guide... 3 1.1 Purpose... 3 1.2 Audience... 3 1.3 Prerequisites... 3 1.4 Related Documents... 3 2
SWIFT Response to ESMA s consultation paper on
SWIFT Response to ESMA s consultation paper on Draft technical standards on access to data and aggregation and comparison of data across TR under Article 81 of EMIR 01 February, 2016 SWIFT thanks ESMA
Connectivity. SWIFTNet Link 7.0. Functional Overview
Connectivity SWIFTNet Link 7.0 Functional Overview December 2010 SWIFTNet Link 7.0 Table of Contents 1 Introduction... 3 2 Enhancements and features... 4 2.1 Message and File Copy... 4 2.2 Message and
STANDARD 48 FORMAT OF THE IBAN ISSUED IN THE UK (International Bank Account Number) June 2007
STANDARD 48 FORMAT OF THE IBAN ISSUED IN THE UK (International Bank Account Number) June 2007 UK Payments Administration Mercury House, Triton Court Finsbury Square London EC2A 1LQ Limited 2009 COPYRIGHT
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
SWIFT Response To the IOSCO Consultation on Risk Mitigation Standards for Non- Centrally Cleared OTC Derivatives
SWIFT Response To the IOSCO Consultation on Risk Mitigation Standards for Non- Centrally Cleared OTC Derivatives 16 October 2014 Foreword SWIFT thanks IOSCO for the opportunity to respond to the Consultation
Realex Payments Integration Guide - Ecommerce Remote Integration. Version: v1.1
Realex Payments Integration Guide - Ecommerce Remote Integration Version: v1.1 Document Information Document Name: Realex Payments Integration Guide Ecommerce Remote Integration Document Version: 1.1 Release
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
SWIFT Certified Application - Alliance Monitoring Add-On
Service Partner Programme SWIFT Certified Application - Alliance Monitoring Add-On Label Criteria 2015 This document provides a structured and detailed view of the criteria that an add-on application must
Technical Specifications
SEPA Plus TXT Files Version 3 Technical Specifications This document describes the technical matters of the SEPA ROUTING TXT file, included in the SEPA Plus product. The file is used by financial institutions
Service Description. 3SKey. Connectivity
Connectivity 3SKey Service Description This document describes the features and functions of the components of the 3SKey solution and the roles and responsibilities of all parties involved in the 3SKey
Lebanon National Payment System
Lebanon National Payment System How a Bank Institution subscribed to NPS services RTGS CLEAR Browse Version 3 - Dec 2011 1 P a g e Contents 1 How to subscribe to NPS services as a Bank Institution?...
How much do you pay for your PKI solution?
Information Paper Understand the total cost of your PKI How much do you pay for your PKI? A closer look into the real costs associated with building and running your own Public Key Infrastructure and 3SKey.
Introduction to Macroscope. Version 5.0. April 2012
Version 5.0 April 2012 Macroscope is a registered trademark of Fujitsu Consulting (Canada) Inc. 2012, Fujitsu Consulting (Canada) Inc. OWNERSHIP NOTICE This document is proprietary to Fujitsu Consulting
National Geospatial Data Asset Management Plan
National Geospatial Data Asset Management Plan Portfolio Management Implementation Plan for the OMB Circular A 16 Supplemental Guidance as it relates to OMB Circular A 16, Coordination of Geographic Information
Certificate Policy. SWIFT Qualified Certificates SWIFT
SWIFT SWIFT Qualified Certificates Certificate Policy This Certificate Policy applies to Qualified Certificates issued by SWIFT. It indicates the requirements and procedures to be followed, and the responsibilities
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
INFORMATION WE MAY COLLECT FROM YOU
Privacy Policy ABOUT Prolific Academic Ltd. ("We") are committed to protecting and respecting your privacy. This policy (together with our terms of use and any other documents referred to on it) sets out
Cisco Collaboration with Microsoft Interoperability
Cisco Collaboration with Microsoft Interoperability Infrastructure Cheatsheet First Published: June 2016 Cisco Expressway X8.8 Cisco Unified Communications Manager 10.x or later Microsoft Lync Server 2010
STEP2 Pan-European Bulk Payment Processing System. Functional Overview
STEP2 Pan-European Bulk Payment Processing System Functional Overview Final 3v1 of 11 th September 2006 1 Contents 1 Introduction...4 1.1 References...4 1.2 Modification History...4 2 The Scope Of The
New Remittance Information Format for Wire Payments By: David Bonneau
New Remittance Information Format for Wire Payments By: David Bonneau Abstract On November 21, 2011, Fedwire and CHIPS are instituting a new structure in their wire formats so that your customers can provide
Electronic Bill of Lading for Carriers
www.bolero.net Electronic Bill of Lading for Carriers Frequently Asked Questions (FAQs) Introduction As with a traditional bill of lading (b/l) there are two principle types of electronic bill of lading
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
The new EU Clinical Trials Regulation How NHS research and patients will benefit
the voice of the NHS in Europe Briefing September 2014 Issue 19 The new EU Clinical Trials Regulation How NHS research and patients will benefit Who should read this briefing? This briefing will be of
Infrastructures Short version 7. Stephane Ernst, Market Manager for HVPMIs
SWIFT for Payment Market Infrastructures Short version 7 Stephane Ernst, Market Manager for HVPMIs Sep 2010 Basic concept of RTGS Real Time Gross Settlement the continuous (real-time) settlement t of funds
HSCIC Audit of Data Sharing Activities:
Directorate / Programme Data Dissemination Services Project Data Sharing Audits Status Approved Director Terry Hill Version 1.0 Owner Rob Shaw Version issue date 26/10/2015 HSCIC Audit of Data Sharing
EDI Compliance Report
The EDI Deenvelope business processes (that is, X12Deenvelope, EDIFACTDeenvelope, CIIDeenvelope) perform a compliance check to verify absolute adherence to the supported EDI standards, including ANSI X12,
PRIVACY POLICY. "Personal Information" comprising:
PRIVACY POLICY Uniqlo is committed to respecting the privacy rights of visitors to its website. This privacy policy ("Policy") explains how we collect, store and use personal data about you when you browse
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
Introducing Alliance Lite2. The easiest way to use SWIFT
Introducing Alliance Lite2 The easiest way to use SWIFT SWIFT Is a cooperative founded by and for the financial industry Provides platform, products and services that enable customers to exchange financial
Elavon Payment Gateway - Redirect Integration Guide
Elavon Payment Gateway - Redirect Integration Guide Version: v1.1 Table of Contents 1 About This Guide 3 1.1 Purpose 3 1.2 Audience 3 1.3 Prerequisites 3 1.4 Related Documents 3 2 Elavon Payment Gateway
SWIFTReady Messaging Data Services
SWIFTReady Messaging Data Services -- SWIFTReady Messaging Data Services Label criteria 2008 Version 3 May 2008 Messaging Data Services Label Criteria Copyright S.W.I.F.T. s.c.r.l. All rights reserved.
ISO 20022 Payments Standard Initiative Consultation Summary
ISO 20022 Payments Standard Initiative Consultation Summary The CPA ISO 20022 Project Team March 14, 2016 BACKGROUND From August 10 to September 30, 2015, the Canadian Payments Association (CPA) conducted
Deltek Touch Time & Expense for Vision 1.3. Release Notes
Deltek Touch Time & Expense for Vision 1.3 Release Notes June 25, 2014 While Deltek has attempted to verify that the information in this document is accurate and complete, some typographical or technical
Kiwi SyslogGen. A Freeware Syslog message generator for Windows. by SolarWinds, Inc.
Kiwi SyslogGen A Freeware Syslog message generator for Windows by SolarWinds, Inc. Kiwi SyslogGen is a free Windows Syslog message generator which sends Unix type Syslog messages to any PC or Unix Syslog
media kit 2014 Advertise Global Mobile Ad Network
media kit 2014 Advertise Global Mobile Ad Network WHY MOBILE ADVERTISING Proliferation of smartphone devices and tablets is shifting the way that customers use Internet, making advertising a key part of
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
An Oracle White Paper October 2011. Why Projects Fail: Avoiding the Classic Pitfalls
An Oracle White Paper October 2011 Why Projects Fail: Avoiding the Classic Pitfalls Executive Summary There is an age-old saying that goes something like this: we can do anything we want, but we cannot
The PIRUS Code of Practice for recording and reporting usage at the individual article level
PIRUS A COUNTER Standard The PIRUS Code of Practice for recording and reporting usage at the individual article level (Note: this draft is for public consultation only and is not yet ready for full implementation)
Post Trade. Business Process Requirements Document Broker Matching Solution
Business Process Requirements Document Broker Matching Solution Disclaimer This document is intended for discussion purposes only and does not create any legally binding obligations on the part of AFME.
1 Introduction. 2 The need for Engineering Workflow. 3 Example engineering workflow -3- NLR-TP-2000-313
-3- Engineering Workflow The Process in Product Data Technology D.J.A. Bijwaard, J.B.R.M. Spee, P.T. de Boer National Aerospace Laboratory NLR, P.O.Box 90502, 1006 BM AMSTERDAM, The Netherlands Fax:+31
PEOPLESOFT CASH MANAGEMENT
PEOPLESOFT CASH MANAGEMENT Oracle s PeopleSoft Cash Management is a cash management solution that optimizes enterprise-wide liquidity and cash control. KEY FEATURES Increase efficiency by performing cash
HSCIC Audit of Data Sharing Activities:
Directorate / Programme Data Dissemination Services Project Data Sharing Audits Status Approved Director Terry Hill Version 1.0 Owner Rob Shaw Version issue date 20/04/2016 HSCIC Audit of Data Sharing
Shift from Letters of Credit to Open Account using Electronic Supply Chain Management Tools
Shift from Letters of Credit to Open Account using Electronic Supply Chain Management Tools Christopher A. Conn Senior Business Manager Trade & Supply Chain Management Americas Banking Initiatives SWIFT
Environmental Scan - International Interoperability Standards -
Environmental Scan - International Interoperability Standards - Environmental Scan - International Interoperability Standards - February 2009 TABLE OF CONTENTS EXECUTIVE SUMMARY 1 I INTRODUCTION 2 1. PURPOSE
ENTERPRISE PAYMENTS SOLUTIONS
ENTERPRISE PAYMENTS SOLUTIONS OFFERINGS Enterprise payments transformation services Messaging infrastructure consolidation Functional and technology solution design Liquidity management optimization Development,
Gilead Transparency Reporting Methodological Note
Gilead Transparency Reporting Methodological Note Contents 1 Introduction... 2 2 Definition of Transfers of Value... 2 3 Definition and management of Cross-Border Spend... 3 4 Which Recipients of Transfers
Business-to-Business EIPP: Presentment Models, Part 1 By: The Council for Electronic Billing and Payment
Business-to-Business EIPP: Presentment Models, Part 1 By: The Council for Electronic Billing and Payment Abstract In the short time since the release of the first web browser in 1993, the Internet has
SOCIAL MEDIA STRATEGY 2013 2015
SOCIAL MEDIA STRATEGY 2013 2015 October 2013 1 Contents 1. Background 2. Channels 3. Use 4. Management and Administration 5. Analytics and Reporting 6. Communication and Employee Engagement 7. Timeline
CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS
CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS Procedural Reference Document PRD-002 PROCEDURES FOR U.S. DOLLAR AND FOREIGN CURRENCY TRANSFERS WITHIN CANADA November 2009 CANADIAN PAYMENTS
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
The Bank of New York Mellon is Open For Business.
TREASURY SERVICES The Bank of New York Mellon is Open For Business. Merger Spawns New Platform for Enhanced Treasury Services. Sponsored supplement to Treasury & Risk magazine The Bank of New York Mellon
COM Port Stress Test
COM Port Stress Test COM Port Stress Test All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording,
Optimizing Payment Cycles for Trade Payables and Receivables
Optimizing Payment Cycles for Trade Payables and Receivables Houston Treasury Management Association Space City Cash Conference September 2013 Madeline Sprague, HSBC Bank USA, N.A. Global Trade & Receivables
Global (Re)insurance Best Practices Accounting, Settlement and Claims
Global (Re)insurance Best Practices Accounting, Settlement and Claims A Consistent Community Approach to Implementing the ACORD Global Reinsurance and Large Commercial Message Standards V1 July 2012 Legal
Universal Printer Driver Guide
Universal Printer Driver Guide Brother Universal Printer Driver (BR-Script3) Brother Mono Universal Printer Driver (PCL) Brother Universal Printer Driver (Inkjet) Version B ENG 1 Overview 1 The Brother
Changes in Schengen visa application process
Changes in Schengen visa application process As part of the worldwide introduction of the Visa Information System (VIS) 1, the Schengen States will launch the VIS in India (and in the neighbouring countries
TERMS AND CONDITIONS APPLICABLE TO CREDIT INSTITUTIONS
ERSTE BANK HUNGARY ZRT TERMS AND CONDITIONS APPLICABLE TO CREDIT INSTITUTIONS Effective from: 01 September 2014 1. General Provisions 1.1. These Terms and Conditions (hereinafter TC ) apply to all correspondent
Euroclear Finland. Technical Connectivity Description. September 2014 V1.4
September 2014 Euroclear Finland Technical Connectivity Description V1.4 Summary of changes Version Date Version history V1.0 December 2013 First internal issue V1.1 February 2014 First issue V1.2 April
State Bank of Pakistan. Guidelines: IBAN Implementation in Pakistan
State Bank of Pakistan Guidelines: IBAN Implementation in Pakistan Page ii 1. Introduction 2. IBAN Implementation 3. IBAN Benefits 4. Scope 5. IBAN Implementation Phases 6. IBAN Format 7. Proposed IBAN
Finance. Human resources. Health and safety. Compliance Procurement. Corporate affairs. Sales and marketing. Public relations Commercial development
Heads of Internal Audit Service Benchmarking Report Document Control Introduction This report contains an analysis of results for the survey entitled: Document Control. The survey asks heads of internal
Background. IBAN Overview
International Bank Account Number ( IBAN ) IBAN Overview The International Bank Account Number ( IBAN ) is an international standard for identifying bank accounts across national borders in a way that
PINAL COUNTY POLICY AND PROCEDURE 2.50 ELECTRONIC MAIL AND SCHEDULING SYSTEM
PINAL COUNTY POLICY AND PROCEDURE 2.50 Subject: ELECTRONIC MAIL AND SCHEDULING SYSTEM Date: November 18, 2009 Pages: 1 of 5 Replaces Policy Dated: April 10, 2007 PURPOSE: The purpose of this policy is
Search. Innovative MyStandards technology from SWIFT fast tracks ISO 20022 onboarding
Innovative MyStandards technology from SWIFT fast tracks ISO 20022 onboarding Innovative MyStandards technology from SWIFT fast tracks ISO 20022 onboarding Barclays and Navigators Insurance realise the
Bankline internet banking import file layout user guide
Bankline internet banking import file layout user guide Bankline internet banking import file layout user guide 2 Contents 1. Introduction to Bankline import...3 1.1 What is Bankline import?...3 1.2 How
Cover Payments: Background Information and Implications of the new SWIFT Message Format (due to go live on November 21, 2009)
da D0946B-2009 May 2009 Cover Payments: Background Information and Implications of the new SWIFT Message Format (due to go live on November 21, 2009) It is important that participants in payment systems
TGA key performance indicators and reporting measures
TGA key indicators and reporting measures Regulator Performance Framework Version 1.0, May 2015 About the Therapeutic Goods Administration (TGA) The Therapeutic Goods Administration (TGA) is part of the
Your Partner for European Payment Processing
Your Partner for European Payment Processing A state-of-the-art platform built to support European diversity We believe that SEPA and domestic instruments will co-exist for some time, and both need to
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