1 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 by the International Securities Association for Institutional Trade Communication (ISITC) as a statement of professional practices recommended by ISITC. Institutions providing the information recommended in this document will benefit from the efficiencies inherent in a more automated transaction process. Although all institutions are encouraged to act consistently with this document, none are required to do so, and a failure to do so is not, in and of itself, evidence of negligent or inappropriate conduct.
2 Document History Change Date Description of Change Author Dec 2008 Initial Release of Payments Market Practice Document Co-chairs Sept 2009 Updated with Generic payment details Co-chairs June 2010 Updated with MT 202 and 210 message details, and appendices Co-chairs for Cash Collateral and Securities Lending. December Removal of business data elements (Payment Method) as this is a messaging requirement not a business element requirement -Update to Actors/Roles Diagram to highlight different terminology by related security product (Generic/Lending/Bank Loan) -Update to Generic Appendix Section 4.1 to include CASH cash purpose code usage -Update to Generic Appendix 1 Section 4.4 (MT210 field recommendations) fields 52a usage usage and field 56a usage. -Update to Message Sequence diagrams for generic appendix -Update Message Sequence diagrams in Lending Appendix with pacs.009 in place of pain.001. Need to review all messages noted in message diagrams within Lending appendix. Need to update field recommendations and samples with pacs.009 instead of PAIN001 and need to add camt.057 field recommendations and samples. -Addition of Derivatives Appendix with pacs.009 and camt.057 field recommendation and samples to be added. -Addition of Bank Loans Appendix with MP Rules, pacs.009 and camt.057 field recommendation and samples to be added. January Update to Generic Appendix to include field recommendations of camt.057 (embedded document V3) based on updated camt.057 MDR document distributed by SWIFT in Oct Also need to include sample message. Note sent to Frank V. 12/20 to provide feedback and a sample. -Update to Generic Appendix Section 4.2 and 4.3 to state pacs instead of pain Field recommendation and sample to be updated. -Open question noted on Creditor Agent field within MT202 field recommendations February Updated camt.057 field recommendations incorporated after feedback and review with SWIFT standards -Updated pacs.009 field recommendations incorporated after feedback and review with SWIFT standards -Bank loan appendix updated Update MT202 Matrix when using Fed ID within a Payment Instruction February 2011 March 2011 Disclaimer added to document Co-chairs June 2011 Further updates on camt.057 and pacs.009 messages based on continued discussions with SWIFT standards Co-chairs
3 March, 2012 Addition of new cash purpose codewords under Derivatives Appendix to differentiate initial vs variation margin. May, Update of examples XML on page 30 and 39 -Addition of pacs.009 extension example October, -Clarification of Ordering Institution field recommendations on 2012 MT210 message J. Brasile J. Brasile J. Brasile
4 Table of Contents Document History Introduction BACKGROUND BUSINESS DEFINITION APPENDIX Background TYPES OF PAYMENT FLOWS ACTORS AND ROLES Business Definition BUSINESS DATA REQUIREMENTS MESSAGE USAGE RULES CASH PURPOSE CODES PROCESS FLOW FOR MARKET SETTLEMENTS OF PAYMENTS/RECEIPTS ADDITIONAL PROCESS FLOW INCLUDING ACCOUNTING MESSAGING OF PAYMENTS/RECEIPTS Appendix #1 Generic Payment ISITC CASH PURPOSE CODEWORDS FOR GENERIC PAYMENTS MESSAGE SEQUENCE DIAGRAMS FIN MT 202 MESSAGE FIN MT 210 MESSAGE ISO MX PACS MESSAGE ISO MX CAMT MESSAGE Appendix #2 Cash Collateral Payment ISITC CASH PURPOSE CODEWORDS SPECIFIC TO CASH COLLATERAL PAYMENTS ACTORS AND ROLES MESSAGE STRUCTURE AND REQUIREMENTS SAMPLE MX PACS MESSAGE TO BE UPDATED. BELOW IS A PAIN Appendix #3 Securities Lending Payments ISITC CASH PURPOSE CODEWORDS SPECIFIC TO SECURITIES LENDING PAYMENTS ACTORS AND ROLES MESSAGE SEQUENCE DIAGRAMS MESSAGE STRUCTURE AND REQUIREMENTS SAMPLE MX PACS MESSAGE Appendix #4 Derivatives Payments Scope Definitions Actors and Roles Message Sequence Diagram Message Usage Rules Message Structure and Field Requirements/Recommendations... 54
5 7.6 Notification to Receive Field recommendations: Notification to Receive Field samples Payment Instruction Field recommendations: Payment Instruction Field sample Appendix #5 Bank Loan Payments Scope Definitions Actors and Roles Message Sequence Diagram Message Usage Rules: Message Structure and Field Requirements/Recommendations Notification to Receive Field recommendations: Notification to Receive Field samples Payment Instruction Field recommendations: Payment Instruction Field sample Disclaimer: MX Messaging Market Practice Recommendations The existing Payment MX messaging formats do not fully support the payment needs of the Securities Industry. ISITC has submitted a business justification and is working with Payment Seg and Security Seg to identify proper messaging attributes need in support of Securities Industry payment flows. Our business justification is currently being reviewed by the Security Seg and Payment Seg and a solution has not yet been determined. The MX messaging flows are a work in process and items highlighted within this document have not been fully vetted.
6 1.0 Introduction This purpose of this document is to provide guidelines and market practice recommendations for the use of messaging in support of payments related processing. These guidelines are for payment messages as used within the Securities segment of the financial services industry within the United States. It should be noted that while there may be some overlap around usage, these market practice recommendations are separate from the Payments segment of the banking service industry. This document focuses on the data flow between two parties, and provides recommendations on how different industry standard messaging can be used in support of several business models. This Market Practice document is a working document and will continue to be enhanced to provide additional guidelines and market practices as needed by our constituency within ISITC. New guidelines will be added throughout time as requested by the ISITC membership. This market practice document itself is structured with three separate sections: 1.1 Background This section provides high level information with respect to payments processing and the introduction of messaging in support of that processing. It will introduce the concept of payment instructions, payment instruction cancellations, payments status, payment confirmation, and lastly reversal of payment instructions. Further it will introduce the basic parties that are the intended audience of this document; Investment Managers and Global Custodians. 1.2 Business Definition This section introduces some basic concepts and definitions that are used throughout the use of payments messaging. A basic, or generic, payments message is introduced to identify and define the common data elements that are typically found (and therefore are recommended) in most payments messages. Also within this section, Cash Purpose code words as identified by the industry are introduced, defined, and recommendation for use of code words is explained. 1.3 Appendix There are multiple business processes within the industry and within individual organizations for which payments related data flow is required. These business processes in many cases can be unique, but will also have similarities to other processes that are outlined. This document will contain multiple appendices, each to be used to provide details and recommendations of market practice use for payment messaging. The recommendations can be specific to a particular business process, or separately may be specific to the use of certain message format /syntax (csv files, industry messages etc.) 6
7 Each appendix will provide market practice recommendations for the use of messaging in support of the business process identified within it. Included in the appendix will be an explanation of the business process, identification of parties involved and their role in the process, and an outline of the data flow among those parties. The final section of the appendix will be the detailed technical recommendation on how to construct and use the messages in support of the business process. Following is a list of Appendices included in this document: Appendix Name Description Link # #1 Generic Payment Baseline business and data requirements for Appendix #1 securities related payment messages. Provide detail mapping for MT and MX messages. #2 Cash Collateral Payment Specific field recommendations for Cash Collateral Appendix#2 payments associated with derivatives, margin, repo and lending transactions. #3 Securities Lending Specific field recommendations for Securities Appendix #3 Payment Lending related payments between the lending agent and borrowing broker. #4 Derivatives Specific recommendations for OTC Swap Appendix #4 payments #5 Bank Loans Specific recommendations for Bank Loan initial and final contract related payments Appendix #5 7
8 2.0 Background This section provides high level information with respect to payments processing and the introduction of messaging in support of that processing. It will introduce the concept of payment instructions, payment instruction cancellations, payments status, payment confirmation, and lastly, reversal of payment instructions. The appendices in this document are included to provide details of individual work flows that leverage payment messaging. Details of each appendix will include the scope, identification of the actors involved, a process flow, message usage rules, message structure recommendations, and a sample message. 2.1 Types of Payment Flows Flow General Description Instruction Message from a client that requests an account servicer to initiate/receive a payment to/from another party. Status Message from an account servicer to a client indicating the current (at the time the message is sent) status of that payment. Confirmation of instruction Message from an account servicer to a client confirming that a payment has been made. Instruction cancellation Message from a client that requests an account servicer to cancel a previously sent instruction. Cancellation Message from an account servicer to a client indicating the Status/Confirmation current status of a previously sent instruction cancellation. Reversal Message from a client requesting an account servicer to recall a previously made payment Or Message from an account servicer to a client confirming that a previously made payment had been reversed. 8
9 2.2 Actors and Roles A brief note regarding Actors and Roles, and terms used within the document. The term Actor is used to identify a type of organization that is involved in a certain flow or process being described. The term Role is used to identify the task or purpose of that Actor involved in a certain flow or process. The organization will be indicated by its Actor name and described by the Role it plays. The following Actors have been identified and are referenced throughout this document: Roles Account Owner Account Cash Local Clearing Counterparty Servicer Clearing Agent Depository Underlying Client Global Custodian Executing Broker Investment Manager Accounting Agent Actors 3 rd Party Middle Office Provider Lending Agent Client s Custodian Broker s Custodian Prime Broker Lending Agent s Custodian Cash Clearing Depository Sub-Custodian Clearing Bank Borrowing Broker Lending Brokers Custodian Lender (Account/Fund investing in loan) Lender s Custodian Loan Agent Executing Broker Investment Manager Bank Loan Agent 9
10 3.0 Business Definition This section introduces the generic payment message and baseline business data requirements for all securities related payment messages. Although the different business flows are defined within their own appendices, in practice most of the payments messages will include the same business elements as the generic payment message, and will be differentiated only by the use of certain other data points. 3.1 Business Data Requirements This section identifies the common business elements that are the foundation of payment instructions. Business Element Comments Message Identification Reference number to unambiguously identify the message. Debtor (Account Owner) Party that owes an amount of money to the ultimate creditor** Requested Execution Date/Settlement Date Date on which the debtor s account is debited. End-to-end Identification Currency of Payment Instructed Amount of Payment Cash Purpose Code Intermediary Agent Creditor agent Creditor Unique identification assigned by initiating party to unambiguously identify the payment. This id is passed on, unchanged, throughout the entire end-to-end chain, which all parties in the chain can use to identify this particular payment Currency Amount of money to be moved between the debtor and creditor, expressed in currency as ordered by initiating party. Underlying reason for the payment transaction. (see ISITC Cash Purpose Codeword List for list of approved ISITC purpose codes). The agent between the debtor agent and creditor agent. Optional to be used (or not used) as required for payment chain. Financial institution servicing an account for the creditor Party to which an amount of money is due. **The amount of detail required may vary in accordance with OFAC and/or other regulatory requirements. As this needs to be determined on a case by case basis by individual institution(s), it is therefore not included in the market practice. 3.2 Message Usage Rules This initial version of the market practice supports the use of a single message for a single payment, i.e. funds will de debited from a single account at the debtor agent and will be credited to a single account at the creditor agent. 10
11 3.3 Cash Purpose Codes This section introduces the concept of Cash Purpose Code words. Within the release of the MX Payment messages, the use of a Cash Purpose Code word is recommended as a manner in which the purpose of the payment can be specified. Although the Payments Industry already has a list of published code words, the ISITC membership concluded that the list was not sufficient to support payment message needs for the Securities Industry. ISITC has created a list of standard code words, and recommends that any payment message utilizes one of the ISITC code words to ensure the efficient and automated processing of that message. The content of the ISITC Cash Purpose Codeword List is controlled by the ISITC Payments Market Practice working group, and the list itself is maintained by the ISITC Reference Data Working Group. Requests to add, remove, or modify code words in this list must be submitted to the Payments Working group via business case and will be reviewed and approved accordingly. A complete list is available on the ISITC web-site Process Flow for Market Settlements of Payments/Receipts This is the generic payment process workflow on which this market practice is based. It identifies the primary roles of the participants in the workflow. 11
12 Additional Process Flow including Accounting Messaging of Payments/Receipts Fund accountant Postings Accounting Security Trade FPML/MT54X with RPTO Cash Instruction MT 202 MT 210 MT 202/MT 210 or fax Account Owner (e.g. IM) MT 202 or MT 210 Accounting Security Trade FPML/MT54X with RPTO (contract) Account Servicer (e.g. Custodian) Fund accountant Postings Account Servicer Cash Correspondant Account Servicer a/c «Custody» MT910/900 Confirmation of debit/credit and MT950/MT940 Statement «Accounting MT950/MT940 Statement» 1 Source documents were obtained SWIFT documentation 12
13 4.0 Appendix #1 Generic Payment This section provides the specific field recommendations for generic payments associated with nonspecific security trades. 4.1 ISITC Cash Purpose Codewords for Generic Payments This is a subset of the ISITC Classification Code list located on the Reference Data Working Group web-page. Business Element Generic Cash Purpose codeword Codeword CASH Definition Any cash payment not otherwise already identified with a specific cash purpose related type. Transaction is a general cash management instruction. 13
14 4.2 Message Sequence Diagrams Ordering Account 1 Account 1 Account 2 Account 2 Beneficiary Customer Ordering Sender Receiver Account w/ Customer Institution Custodian Custodian Institution PACS CAMT PACS Customer Credit Transfer Initiation Message Msg. to deliver/pay funds to beneficiary customer. CAMT Notice to Receive Message Msg. to expect payment receipt PACS PACS Instruction to deliver/ pay funds to beneficiary PACS PACS Instruction to expect a payment receipt PACS Payment Status Report PACS Status Msg to sender PACS Payment Status Report PACS Status Msg. to receiver PACS Payment Status Report PACS Status Msg to deliverer of payment CAMT Payment Status Report CAMT Status Msg. to receiver of payment CAMT CAMT Confirmation Confirmation of payment of receipt CAMT CAMT CAMT CAMT Confirmation Confirmation of payment of receipt CAMT CAMT
15 Account 1 Account 1 Account 2 Account 2 Beneficiary Ordering Sender Receiver Account w/ Customer Institution Custodian Custodian Institution CAMT CAMT CAMT Customer Credit Transfer Cancellation Message Msg. to cancel deliver/pay funds PACS PACS Cancellation of deliver/ pay funds instruction CAMT Notice to Receive Cancellation Msg. to cancel expected payment receipt. PACS PACS Cancellation of expected payment receipt instruction CAMT Resolution of Investigation CAMT Status Msg on cancellation Request for delivery of payment CAMT Resolution of Investigation CAMT Status Msg on cancellation Request for delivery of No message sent to notify on status of cancellation of receipt of payment 15
16 4.3 FIN MT 202 message This section provides the detailed technical recommendation for usage of the FIN MT 202 message for a generic or basic payment with one debtor and one creditor. Since this market practice is specific to the securities industry, this appendix makes the additional assumption that there is a direct account relationship between the sender (e.g. investment manager on behalf of their client, or mutual fund client) of the MT 202 and the receiver of the MT 202 (e.g. global custodian, or prime broker). Business Element Field Name Definition Usage Rule/ Comment Tag Example Message Identification Transaction Reference Number This field specifies the reference assigned by the Sender to unambiguously identify the message. 20 :20: Cash Purpose Code Related Reference This field contains a reference to the related transaction. ISITC recommends populating this tag with an ISITC approved Cash Purpose Code, available on the ISITC Classification Code list on the Reference Data Working Group web-page. ISITC understands the MT 202 has been utilized by the security industry for a number of years, and that organizations have already hard coded this field with other formats. Therefore, the market practice includes the following commonly used alternative formats: - Cash Purpose Code/Reference Number - Reference Number transaction. - NONREF 21 :21: MARG Or :21: MARG/Ref Number Or :21: Ref Number Or :21: NONREF Payment Method This business element is not applicable to the MT 202 Message 1) Requested Execution Date / Settlement Date 2) Currency of Payment 3) Instructed Amount 1) Value Date 2) Currency Code 3) Amount This field specifies the value date, currency and amount to be transferred. 32A :32A:090203GBP150000, Debtor (Account Owner) Sender s Correspondent This field specifies the account or branch of the Sender or another financial institution through which the Sender will reimburse the Receiver. ISITC recommends the use of this field be mandatory; it specifies the debtor s account number that will be debited by the account servicer (normally the receiver of the MT 202 instruction) in order to make the payment. 53a :53B:/ Business Element Field Name Definition Usage Rule/ Comment Tag Example Intermediary Agent Intermediary This field specifies the financial institution through which the transaction must pass to reach the account with institution. ISITC recommends using option A with BIC address. The field should be populated with the local market clearing id; otherwise populate the BIC code. 56a :56A:FIBAUS33XXX Or :56D://FW021000ABA 16
17 Business Element Field Name Definition Usage Rule/ Comment Tag Example For three levels of clearing, tags 56, 57, and 58 should be populated. For two levels of clearing, tags 57 and 58 should be populated. First level: Creditor agent Account With Institution This field identifies the financial institution which will pay or credit the beneficiary institution. ISITC recommends the use of this field as mandatory and using option A. Where it is the first level of clearing, ISITC recommends populating the local market clearing id; otherwise populate the BIC code. Where it is the second level of clearing, ISITC recommends populating both the BIC code and the creditor agent s account number with the Intermediary Agent in tag 56a. If Counterparty BIC address is not available the preferred method is to identify the Bank using option D (including name and address in the party field 57a :57D://FW021000ABA Or :57A:FIBAUS33XXX Second Level: :57A:/ FIBADEFFXXX Third Level: 57D: //AC Paying Agent XYZ Creditor Beneficiary Institution This field specifies the financial institution which has been designated by the ordering institution as the ultimate recipient of the funds being transferred. ISITC recommends the use of this field as mandatory and using option A. It should be populated with both the creditor s BIC code and their account number with the creditor s agent in tag 57a. If Counterparty BIC address is not available the preferred method is to identify the Beneficiary using option D (including name and address in the party field 58a :58A:/ FIBADEFFXXX 58D:/ACCT123 Beneficiary Name 17
18 MT 202 Examples: USD Payment via Fed Wire with two levels of clearing 20 : : MARG 32A: USD150000, 53B: / D: //FW021000ABA 58A: / FIBADEFFXXX USD Payment via Fed Wire with three levels of clearing 20 : : MARG/ A: USD150000, 53B: / D: //FW021000ABA 57A: / FIBAUS33XXX 58A: / FIBADEFFXXX 18
19 4.4 FIN MT 210 Message This section provides the detailed technical recommendation for usage of the FIN MT 210 message instruction of advice to receive funds. This message is sent from an account owner to one of its account servicing institutions. Since this market practice is specific to the securities industry, this appendix makes the additional assumption that there is a direct account relationship between the sender (e.g. investment manager on behalf of their client, or mutual fund client) of the MT 210 and the receiver of the MT 210 (e.g. global custodian, or prime broker). Business Element Field Name Definition Usage Rule/Comment Tag Format Message Identification Credit Account Transaction Reference Number Account Identification This field specifies the reference assigned by the Sender to unambiguously identify the message. This field identifies the account to be credited with the incoming funds ISITC recommends the use of this field be mandatory; it specifies the creditor s account number that will be credited by the account servicer (normally the receiver of the MT 210 notification). 20 :20: : Value Date Value Date This field contains the value date of all incoming funds specified in this message 30 :30: ISITC recommends populating this field with an ISITC approved Cash Purpose Code.** Cash Purpose Code Related Reference This field contains a related transaction reference Number, or other common reference, ISITC recognizes that the MT 210 has been utilized by the security industry for a number of years, and that many organizations have already hard coded other formats. Therefore, the market practice also includes the following commonly used alternative formats: - Cash Purpose Code/Reference Number - Reference Number transaction. - NONREF **Please see the ISITC Classification Code list on the Reference Data Working Group webpage. 21 :21: MARG Or :21: MARG/Ref Number Or :21: Ref Number Or :21: NONREF Requested Receipt Currency and Amount Currency Code, Amount This field specifies the currency and amount to be received. 32B :32B:USD
20 Ordering Institution Ordering Institution BIC Address This field specifies the party which owns the funds and is ordering their account to be debited to make the payment After discussions with SWIFT Standards it was clarified that the ordering institution is the party who owns the money and is ordering the money to be debited from their account in order to make the payment. Example: If IM ABC is ordering account servicer DEF to debit their (ABC s) account and make a payment to counterparty 123, then IM ABC should be populated in field 52a of the MT a 52A: GOLDJPJX Intermediary Intermediary Institution BIC This field specifies the financial institution from which the Receiver is to receive the funds. Identifier Code must be a registered BIC. ISITC recommends the use of this field be mandatory. If an intermediary party is not applicable to the receipt of funds, the ordering institution clearing agent should be populated. 56a :56A: BKTRUS33 MT 210 Examples: USD ADVICE TO RECEIVE :20: CU :25: :30: :21: FEES :32B: USD1200 :52A: GOLDJPJX :56A: BKTRUS33 - USD ADVICE TO RECEIVE FED Funds 20 : : : : FEES/ B: USD200218,80 52A : SBSIUS33 56D : //FW
21 4.5 ISO MX PACS.009. message This section provides the detailed technical recommendation for usage of the ISO MX pacs.009 message for a generic or basic payment with one debtor and one creditor. This provides the baseline business and data requirements for all securities related payment messages. Scope: The FinancialInstitutionCreditTransfer message is sent by a debtor financial institution to a creditor financial institution, directly or through other agents and/or a payment clearing and settlement system. It is used to move funds from a debtor account to a creditor, where both debtor and creditor are financial institutions. Usage: The FinancialInstitutionCreditTransfer message is exchanged between agents and can contain one or more credit transfer instructions where debtor and creditor are both financial institutions. **Note on PACS 009 field usage table and sample message: ISITC continues to work with SWIFT to determine the proper field usage for the PACS 009 payment message in support of securities industry requirements. The Usage Rules/Comments column is being used to track the running discussion points in order to maintain the context that will lead to final decisions. Please ensure you review the discussion points and open questions as you evaluate the content of this table. 21
22 This section provides the detailed technical recommendation for usage of the ISO MX PACS message for a generic or basic payment with one debtor and one creditor. This provides the baseline business and data requirements for all securities related payment messages. Index Message Item Definition Mult. ISITC Mult. Type / Representation Usage Rule / Comments <XML Tag> XML Example Group Header Message Identification Creation Date Time Set of characteristics shared by all individual transactions included in the message. Point to point reference assigned by the account servicing institution and sent to the account owner to unambiguously identify the message. Date and time at which the message was created. [1..1] [1..1] <GrpHdr> [1..1] [1..1] [1..1] [1..1] Max35Text ISO Date Time US ISITC Market Practice Recommendation (here after referred to as ISITC) is to follow stated usage. The instructing party has to ensure that Message Identification is unique per instructed party for a pre-agreed period. ISITC recommends following stated usage. <MsgId> <CreDtTm> <MsgId> </MsgId> <CreDtTm> T11:03:00-00:00</CreDtTm> 1.4 Number Of Transactions Number of individual transactions contained in the message. [1..1] [1..1] Max15Numeric Text ISITC recommends following stated usage. <NbOfTxs> <NbOfTxs>1</NbOfTxs> Settlement Information Settlement Method Specifies the details on how the settlement of the transaction(s) between the instructing agent and the instructed agent is completed. Method used to settle the (batch of) payment instructions. [1..1] [1..1] <SttlmInf> [1..1] [1..1] Code INDA - InstructedAgent - Settlement is done by the agent instructed to execute a payment instruction. <SttlmMtd> <SttlmInf> <SttlmMtd>INDA</SttlmMtd> </SttlmInf> Index Message Item Definition Mult. ISITC Mult. Type / Representation Usage Rule / Comments <XML Tag> XML Example Credit Transfer Transaction Information Payment Identification Set of elements providing information specific to the individual credit transfer(s). Set of elements used to reference a payment instruction. [1..n] [1..n] <CdtTrfTxInf> [1..1] [1..1] Need example to see how multiple Ids are populated on PACS009. Is the entire sequence repeated or can the multiple Ids be populated within one occurrence of the PmtID sequence? SWIFT: not sure what is meant, but maybe below comments clarify <PmtId> 22
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.
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.
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
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
EPC016-06 Version 7.1 Approved Date issued: 27 January 2014 Date effective: 1 February 2014 SEPA CORE DIRECT DEBIT SCHEME RULEBOOK Conseil Européen des Paiements AISBL Cours Saint-Michel 30A B 1040 Brussels
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...
General Principles of Software Validation; Final Guidance for Industry and FDA Staff Document issued on: January 11, 2002 This document supersedes the draft document, "General Principles of Software Validation,
Independent Amounts Release 2.0 Independent Amounts Abstract Collateralization has become a key method of mitigating counterparty credit risk in the derivative markets, both bilateral, privately-negotiated
PROCESSING ACKNOWLEDGEMENT FORM (PAF) GUIDE United States Postal Service National Customer Support Center (NCSC) January 8, 2014 This page intentionally left blank. Table of Contents WHY IS THE PAF REQUIRED?...
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
EDiscovery Q@A Question 1: In our initial review of the RFP we have some questions around the data volumes. Can you confirm the data volumes are correct? We are questioning the validity of the total data
Standard: PCI Data Security Standard (PCI DSS) Version: 3.0 Date: August 2014 Author: Third-Party Security Assurance Special Interest Group PCI Security Standards Council Information Supplement: Third-Party
Authorised Persons Regulations Contents Part 1: General Provisions Article 1: Preliminary... Article 2: Definitions... Article 3: Compliance with the Regulations and Rules... Article 4: Waivers... Part
EBA/GL/2014/07 16 July 2014 Guidelines on the data collection exercise regarding high earners Contents 1. Executive summary 3 2. Background and rationale 4 3. EBA Guidelines on the data collection exercise
27 June 2014 EBA/GL/2014/03 Guidelines on disclosure of encumbered and unencumbered assets Contents 1. Executive Summary 3 2. Background and rationale 5 Current disclosure requirements and identified shortfalls
NAVIGATION GUIDE Mortgage Call Reports and Financial Statements Purpose This navigation guide is designed to provide a general understanding of completing Mortgage Call Reports (MCR) and Financial Statements
January 2015 Please read this important information carefully. Schwab One Account Agreement Information about your: Schwab One Account Schwab StockBuilder Plan Schwab One International Account Contents
Transaction Costs Disclosure: Improving Transparency in Workplace Pensions Call for Evidence March 2015 DP15/2 Contents Introduction... 3 About this call for evidence... 3 Freedom of information... 4 Feedback
FORM PF (Paper Version) Reporting Form for Investment Advisers to Private Funds and Certain Commodity Pool Operators and Commodity Trading Advisors OMB APPROVAL OMB Number: 3235-0679 Expires: March 31,
General Consumer Code of Practice for the Communications and Multimedia Industry Malaysia Communications and Multimedia Consumer Forum of Malaysia (CfM) October 2003 TABLE OF CONTENTS Page PART 1 INTRODUCTION
Program Fundamentals: Fidelity Portfolio Advisory Service Strategic Advisers, Inc. 245 Summer Street, V5D Boston, MA 02210 1-800-544-3455 March 30, 2015 On behalf of Fidelity, we thank you for the opportunity
TILA-RESPA INTEGRATED DISCLOSURE Guide to the Loan Estimate and Closing Disclosure forms Consumer Financial Protection Bureau Version log The Bureau updates this guide on a periodic basis to reflect finalized
Business Guidelines Guggenheim Life and Annuity Company 10689 N. Pennsylvania, Suite 200 Indianapolis, IN 46280-0248 800-767-7749 www.guggenheiminsurance.com To our valued agents... As a representative
PRINCIPLES FOR PERIODIC DISCLOSURE BY LISTED ENTITIES Final Report TECHNICAL COMMITTEE OF THE INTERNATIONAL ORGANIZATION OF SECURITIES COMMISSIONS FEBRUARY 2010 CONTENTS Chapter Page 1 Introduction 3 Uses
Issues Paper Managing General Agencies Life Insurance Distribution Model Agencies Regulation Committee February 2011 This document reflects the work of regulators who are members of CCIR. The views expressed
POLICIES ON DIRECT ELECTRONIC ACCESS Consultation Report TECHNICAL COMMITTEE OF THE INTERNATIONAL ORGANIZATION OF SECURITIES COMMISSIONS FEBRUARY 2009 This paper is for public consultation purposes only.
Guideline 6A: Record Keeping and Client Identification for Life Insurance Companies, Brokers and Agents Rev. 2014-02 Guideline 6A: Record Keeping and Client Identification for Life Insurance Companies,
Joint UNECE/Eurostat/OECD Work Session on Statistical Metadata (METIS) Generic Statistical Business Process Model Version 4.0 April 2009 Prepared by the UNECE Secretariat 1 I. Background 1. The Joint UNECE