DOCSLIB.ORG

Pain.002.001.03-CH-SIX-1.1.1-CS-ST Customer Payment Status Report

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pain.002.001.03-CH-SIX-1.1.1-CS-ST Customer Payment Status Report Credit Suisse Version 1.0 Issue date: January 2020 pain.002.001.03-CH-SIX-1.1.1-CS-ST Customer Payment Status Report Message implementation guidelines Table of contents 1. Message overview 3 2. Message details 6 3. Components 23 4. Legend – description of cardinality 71 5. Disclaimer 72 pain.002.001.03-CH-SIX-1.1.1-CS-ST 2 1. Message overview Index XML Name ISO Name Cardinality Document 1 CstmrPmtStsRpt Customer Payment Status Report V03 1..1 1.1 GrpHdr Group Header 1..1 1.1.1 MsgId Message Identification 1..1 1.1.2 CreDtTm Creation Date Time 1..1 1.1.3 InitgPty Initiating Party 0..1 1.1.3.1 Nm Name 0..1 1.1.3.3 Id Identification 0..1 xs:choice 1..1 1.1.3.3.1 OrgId Organisation Identification 1..1 1.1.3.3.1.1 BICOrBEI BICOr BEI 0..1 1.1.3.3.1.2 Othr Other 0..n 1.1.3.3.1.2.1 Id Identification 1..1 1.1.3.3.1.2.2 SchmeNm Scheme Name 0..1 xs:choice 1..1 1.1.3.3.1.2.2.1 Cd Code 1..1 1.1.3.3.1.2.2.2 Prtry Proprietary 1..1 1.1.3.3.1.2.3 Issr Issuer 0..1 1.2 OrgnlGrpInfAndSts Original Group Information And Status 1..1 1.2.1 OrgnlMsgId Original Message Identification 1..1 1.2.6 GrpSts Group Status 0..1 1.2.7 StsRsnInf Status Reason Information 0..n 1.2.7.1 Orgtr Originator 0..1 1.2.7.1.1 Nm Name 0..1 1.2.7.1.3 Id Identification 0..1 xs:choice 1..1 1.2.7.1.3.1 OrgId Organisation Identification 1..1 1.2.7.1.3.1.1 BICOrBEI BICOr BEI 1..1 1.2.7.2 Rsn Reason 1..1 xs:choice 1..1 1.2.7.2.1 Cd Code 1..1 1.2.7.2.2 Prtry Proprietary 1..1 1.2.7.3 AddtlInf Additional Information 0..n 1.3 OrgnlPmtInfAndSts Original Payment Information And Status 0..n 1.3.1 OrgnlPmtInfId Original Payment Information Identification 1..1 1.3.4 PmtInfSts Payment Information Status 0..1 1.3.5 StsRsnInf Status Reason Information 0..n 1.3.5.1 Orgtr Originator 0..1 1.3.5.1.1 Nm Name 0..1 1.3.5.1.3 Id Identification 0..1 xs:choice 1..1 1.3.5.1.3.1 OrgId Organisation Identification 1..1 1.3.5.1.3.1.1 BICOrBEI BICOr BEI 1..1 1.3.5.2 Rsn Reason 1..1 xs:choice 1..1 1.3.5.2.1 Cd Code 1..1 1.3.5.2.2 Prtry Proprietary 1..1 1.3.7 TxInfAndSts Transaction Information And Status 0..n 1.3.7.1 StsId Status Identification 0..1 1.3.7.4 TxSts Transaction Status 0..1 1.3.7.5 StsRsnInf Status Reason Information 0..n 1.3.7.5.1 Orgtr Originator 0..1 1.3.7.5.1.1 Nm Name 0..1 1.3.7.5.1.3 Id Identification 0..1 xs:choice 1..1 1.3.7.5.1.3.1 OrgId Organisation Identification 1..1 1.3.7.5.1.3.1.1 BICOrBEI BICOr BEI 1..1 1.3.7.5.2 Rsn Reason 1..1 xs:choice 1..1 1.3.7.5.2.1 Cd Code 1..1 pain.002.001.03-CH-SIX-1.1.1-CS-ST 3 Index XML Name ISO Name Cardinality 1.3.7.5.2.2 Prtry Proprietary 1..1 1.3.7.5.3 AddtlInf Additional Information 0..n 1.3.7.10 OrgnlTxRef Original Transaction Reference 0..1 1.3.7.10.2 Amt Amount 0..1 xs:choice 1..1 1.3.7.10.2.1 InstdAmt Instructed Amount 1..1 Ccy Currency Required 1.3.7.10.8 PmtTpInf Payment Type Information 0..1 1.3.7.10.8.1 InstrPrty Instruction Priority 0..1 1.3.7.10.8.3 SvcLvl Service Level 0..1 xs:choice 1..1 1.3.7.10.8.3.1 Cd Code 1..1 1.3.7.10.8.3.2 Prtry Proprietary 1..1 1.3.7.10.8.4 LclInstrm Local Instrument 0..1 xs:choice 1..1 1.3.7.10.8.4.1 Cd Code 1..1 1.3.7.10.8.4.2 Prtry Proprietary 1..1 1.3.7.10.8.6 CtgyPurp Category Purpose 0..1 xs:choice 1..1 1.3.7.10.8.6.1 Cd Code 1..1 1.3.7.10.8.6.2 Prtry Proprietary 1..1 1.3.7.10.11 RmtInf Remittance Information 0..1 1.3.7.10.11.1 Ustrd Unstructured 0..n 1.3.7.10.11.2 Strd Structured 0..n 1.3.7.10.11.2.3 CdtrRefInf Creditor Reference Information 0..1 1.3.7.10.11.2.3.1 Tp Type 0..1 1.3.7.10.11.2.3.1.1 CdOrPrtry Code Or Proprietary 1..1 xs:choice 1..1 1.3.7.10.11.2.3.1.1.1 Cd Code 1..1 1.3.7.10.11.2.3.1.1.2 Prtry Proprietary 1..1 1.3.7.10.11.2.3.1.2 Issr Issuer 0..1 1.3.7.10.11.2.3.2 Ref Reference 0..1 1.3.7.10.11.2.6 AddtlRmtInf Additional Remittance Information 0..3 1.3.7.10.17 CdtrAgt Creditor Agent 0..1 1.3.7.10.17.1 FinInstnId Financial Institution Identification 1..1 1.3.7.10.17.1.1 BIC BIC 0..1 1.3.7.10.17.1.2 ClrSysMmbId Clearing System Member Identification 0..1 1.3.7.10.17.1.2.1 ClrSysId Clearing System Identification 0..1 xs:choice 1..1 1.3.7.10.17.1.2.1.1 Cd Code 1..1 1.3.7.10.17.1.2.1.2 Prtry Proprietary 1..1 1.3.7.10.17.1.2.2 MmbId Member Identification 1..1 1.3.7.10.17.1.3 Nm Name 0..1 1.3.7.10.17.1.4 PstlAdr Postal Address 0..1 1.3.7.10.17.1.4.4 StrtNm Street Name 0..1 1.3.7.10.17.1.4.5 BldgNb Building Number 0..1 1.3.7.10.17.1.4.6 PstCd Post Code 0..1 1.3.7.10.17.1.4.7 TwnNm Town Name 0..1 1.3.7.10.17.1.4.9 Ctry Country 0..1 1.3.7.10.17.1.4.10 AdrLine Address Line 0..7 1.3.7.10.17.1.5 Othr Other 0..1 1.3.7.10.17.1.5.1 Id Identification 1..1 1.3.7.10.19 Cdtr Creditor 0..1 1.3.7.10.19.1 Nm Name 0..1 1.3.7.10.19.2 PstlAdr Postal Address 0..1 1.3.7.10.19.2.4 StrtNm Street Name 0..1 1.3.7.10.19.2.5 BldgNb Building Number 0..1 1.3.7.10.19.2.6 PstCd Post Code 0..1 1.3.7.10.19.2.7 TwnNm Town Name 0..1 1.3.7.10.19.2.9 Ctry Country 0..1 1.3.7.10.19.2.10 AdrLine Address Line 0..7 1.3.7.10.19.3 Id Identification 0..1 xs:choice 1..1 1.3.7.10.19.3.1 OrgId Organisation Identification 1..1 1.3.7.10.19.3.1.1 BICOrBEI BICOr BEI 0..1 1.3.7.10.19.3.1.2 Othr Other 0..n 1.3.7.10.19.3.1.2.1 Id Identification 1..1 1.3.7.10.19.3.1.2.2 SchmeNm Scheme Name 0..1 xs:choice 1..1 1.3.7.10.19.3.1.2.2.1 Cd Code 1..1 1.3.7.10.19.3.1.2.2.2 Prtry Proprietary 1..1 1.3.7.10.19.3.1.2.3 Issr Issuer 0..1 pain.002.001.03-CH-SIX-1.1.1-CS-ST 4 Index XML Name ISO Name Cardinality 1.3.7.10.19.4 CtryOfRes Country Of Residence 0..1 1.3.7.10.20 CdtrAcct Creditor Account 0..1 1.3.7.10.20.1 Id Identification 1..1 xs:choice 1..1 1.3.7.10.20.1.1 IBAN IBAN 1..1 1.3.7.10.20.1.2 Othr Other 1..1 1.3.7.10.20.1.2.1 Id Identification 1..1 1.3.7.10.20.1.2.2 SchmeNm Scheme Name 0..1 xs:choice 1..1 1.3.7.10.20.1.2.2.1 Cd Code 1..1 1.3.7.10.20.1.2.2.2 Prtry Proprietary 1..1 1.3.7.10.20.1.2.3 Issr Issuer 0..1 1.3.7.10.20.2 Tp Type 0..1 xs:choice 1..1 1.3.7.10.20.2.1 Cd Code 1..1 1.3.7.10.20.2.2 Prtry Proprietary 1..1 1.3.7.10.20.3 Ccy Currency 0..1 1.3.7.10.21 UltmtCdtr Ultimate Creditor 0..1 1.3.7.10.21.1 Nm Name 0..1 1.3.7.10.21.2 PstlAdr Postal Address 0..1 1.3.7.10.21.2.4 StrtNm Street Name 0..1 1.3.7.10.21.2.5 BldgNb Building Number 0..1 1.3.7.10.21.2.6 PstCd Post Code 0..1 1.3.7.10.21.2.7 TwnNm Town Name 0..1 1.3.7.10.21.2.9 Ctry Country 0..1 1.3.7.10.21.2.10 AdrLine Address Line 0..7 1.3.7.10.21.3 Id Identification 0..1 xs:choice 1..1 1.3.7.10.21.3.1 OrgId Organisation Identification 1..1 1.3.7.10.21.3.1.1 BICOrBEI BICOr BEI 0..1 1.3.7.10.21.3.1.2 Othr Other 0..n 1.3.7.10.21.3.1.2.1 Id Identification 1..1 1.3.7.10.21.3.1.2.2 SchmeNm Scheme Name 0..1 xs:choice 1..1 1.3.7.10.21.3.1.2.2.1 Cd Code 1..1 1.3.7.10.21.3.1.2.2.2 Prtry Proprietary 1..1 1.3.7.10.21.3.1.2.3 Issr Issuer 0..1 1.3.7.10.21.4 CtryOfRes Country Of Residence 0..1 pain.002.001.03-CH-SIX-1.1.1-CS-ST 5 2.
Load more

Recommended publications
  • Oracle Financial Services Regulatory Reporting 2.1 Web Service Guide
    Oracle Financial Services Compliance Regulatory Reporting Web Service Guide Release 2.5.6 May 2016 Oracle Financial Services Compliance Regulatory Reporting Web Service Guide Release 2.5.6 December 2016 Part Number: E70640-01 Oracle Financial Services Software, Inc. 1900 Oracle Way Reston, VA 20190 Part Number: E70640-01 First Edition (May 2016) Copyright © 2016 Oracle and/or its affiliates. All rights reserved. Printed in U.S.A. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise without the prior written permission. Trademarks Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Oracle Financial Services Software, Inc. 1900 Oracle Way Reston, VA 20190 Phone: 703-478-9000 Fax: 703-318-6340 Internet: www.oracle.com/financialservices Contents Contents About This Guide ............................................................................................................ III Who Should Use this Guide .............................................................................................................................................III Scope of this Guide............................................................................................................................................................III How this Guide is Organized...........................................................................................................................................III
    [Show full text]
  • PAYMENT FORMATS STP Rules
    PAYMENT FORMATS STP Rules © VTB Bank (Europe) SE – Payment Formats – STP Rules Page 1 / 10 List of Contents General Information ............................................................................................................... 3 Requirements of the regulations of the Anti Money Laundering Act ....................................... 3 Transaction quality and price ................................................................................................. 3 Account number format ......................................................................................................... 4 BIC (SWIFT address) ............................................................................................................ 4 Customer payment order MT 103 .......................................................................................... 4 Customer payment order MT 103+ ........................................................................................ 8 Bank-to-Bank payments MT 200/202/202Cov ....................................................................... 8 Appendix I ........................................................................................................................... 10 © VTB Bank (Europe) SE – Payment Formats – STP Rules Page 2 / 10 General Information The costs of international payment transactions can be considerably reduced by the observation of prevailing standard rules. The term „Straight Through Processing“ (STP) refers to the highly automated and standardised processing of payment
    [Show full text]
  • Payment Formatting Guidelines
    PAYMENT FORMATTING GUIDELINES May 2019 Version 2019.1 PAYMENT FORMATTING GUIDELINES Welcome the the First Quarter 2019 Edition of the Payment Formatting Guidelines (PFG). • Address: Beneficiary address requests should be a physical • NOK: ADDITIONAL CONSIDERATIONS: Draft capability is address, PO Boxes are not recommended no longer available. • AED/ANY CURRENCY: Purpose Of Payment Code is • NZD: ADDITIONAL CONSIDERATIONS: NZD Payments to required regardless of currency. Thailand require a Purpose Of Payment. • AUD: High Value Account Number: 6 - 9 digits • PAB: Panamanian balboa (PAB) to Banco General S.A. • CLP: Registro Unico Tributario (RUT) Number: 9-digit Tax Suspended. Customers may send U.S. dollars in place of ID # in ‘SWIFT Branch Details’ field, (Without the word local currency. RUT). A valid RUT less than 9 digits, must be added with • PHP: ADDITIONAL CONSIDERATIONS: Payments to Bank preceding zeros. of the Philippine Island (BOPIPHMM) should now use the • CRC: IBAN should have 22: CRkk BBBC CCCC CCCCCCCC following SWIFT Code: BOPIPHMMTRY CC: Additional Tax ID instructions • RUB/ANY CURRENCY: Purpose Of Payment is highly • DKK: ADDITIONAL CONSIDERATIONS: Draft capability is recommended for all payments to Russia regardless of no longer available. currency. • JMD: Branch Routing Code - 8 • SCR: RECOMMENDED: Beneficiary IBAN: 31 Alpha Numerical Digits digits (3 digit bank code, 5 digit transit code) • SGD: ADDITIONAL CONSIDERATIONS: SGD-ACH • JPY: ADDITIONAL CONSIDERATIONS: JPY cannot be sent to Japan Post Bank (JPPSJPJ1) but USD and EUR are payments are only available for beneficiaries located in Singapore. accepted. • SGD: ADDITIONAL CONSIDERATIONS: Payments to • KES: RECOMMENDED: When making tax payment the remitter needs to include a 17 digit Payment Registration HSBC Singapore should use the following SWIFT Codes: Number (PRN) in filed 70 “RETAIL/PERSONAL” accounts use SWIFT HSBCSGS2.
    [Show full text]
  • Pain.001.001.03 - SIC; 1.0
    Message Implementation Guideline pain.001.001.03 - SIC; 1.0 Model: pain.001.001.03 - SIC Version: 1.0 Issue date: June 2015 Author: Credit Suisse Message Overview ............................................................................................................................................ 2 Message Details ................................................................................................................................................. 6 Components .................................................................................................................................................... 37 Legend ........................................................................................................................................................... 100 Disclaimer ...................................................................................................................................................... 101 Generated by GEFEG.FX pain.001.001.03 - SIC; 1.0 Message Overview Index XML Name ISO Name Cardinality Document 1 CstmrCdtTrfInitn Customer Credit Transfer Initiation V03 1..1 1.1 GrpHdr Group Header 1..1 1.1.1 MsgId Message Identification 1..1 1.1.2 CreDtTm Creation Date Time 1..1 1.1.4 NbOfTxs Number Of Transactions 1..1 1.1.5 CtrlSum Control Sum 0..1 1.1.6 InitgPty Initiating Party 1..1 1.1.6.1 Nm Name 0..1 1.1.6.3 Id Identification 0..1 xs:choice 1..1 1.1.6.3.1 OrgId Organisation Identification 1..1 1.1.6.3.1.1 BICOrBEI BICOr BEI 0..1 1.1.6.3.1.2 Othr Other 0..1 1.1.6.3.1.2.1 Id Identification
    [Show full text]
  • XML-ACH Rules Sections 1-7
    OPT-IN RULES FOR INCORPORATING XML MESSAGING IN ACH ADDENDA RECORDS (XML-ACH) June 12, 2015 Copyright © 2013-2015 by NACHA All Rights Reserved. DC1 3766883v.8 07/09/2015 11:34 AM TABLE OF CONTENTS Page 1. Introduction and Overview .................................................................................. 1 2. Participation of DFIs, XML Service Providers and Other Service Providers in XML-ACH. ................................................................................................................ 1 3. Initiation of ISO 20022 XML Entries ........................................................................ 2 4. XML Participant Directory ..................................................................................... 3 5. Representations and Warranties ......................................................................... 3 6. Indemnification: Limitation of Liability: Covenant Not to Sue ...................... 4 7. Miscellaneous ......................................................................................................... 5 8. Glossary for XML-ACH Rules Sections 1-7 ........................................................... 7 9. Appendix A: Technical Specifications ................................................................ 8 10. Appendix B: Best Practices and Guidelines for Stakeholders ...................... 68 11. Appendix C: XML Schema Overview and XML Output of NACHA XSD .... 77 12. Appendix D: Technical Glossary for Sections 8-11 ....................................... 103 13. Appendix E:
    [Show full text]
  • Payments Standards - Exceptions and Investigations
    UNIFI (ISO 20022) Message Definition Report Payments Standards - Exceptions and Investigations Approved by UNIFI Payments SEG on 25 July 2006 Edition August 2006 Table Of Contents Overview .................................................................................................................................................................... 1 What does this document contain? ......................................................................................................................... 1 Exceptions and Investigations messages ................................................................................................................ 1 Business rationale for the Exceptions and Investigations messages ...................................................................... 1 How to read ............................................................................................................................................................ 2 How to use the exceptions and investigations messages ........................................................................................ 3 Introduction ............................................................................................................................................................ 3 Concepts ................................................................................................................................................................. 3 Rules ......................................................................................................................................................................
    [Show full text]
  • Mt 200 Mip Vtb Europe Format Specifications
    VTB Bank (Europe) SE Rüsterstraße 7–9 60325 Frankfurt Germany MT 200 MIP VTB EUROPE SE FORMAT SPECIFICATIONS © VTB Bank (Europe) SE – MIP formats – MT200 Page 1 / 7 VTB Bank (Europe) SE Rüsterstraße 7–9 60325 Frankfurt Germany MT 200 Financial Institution Transfer for its Own Account Status Tag Field Name Content/Options M 20 Transaction Reference Number 16x M 32A Value Date, Currency Code, 6!n3!a15d Amount O 53B Sender's Correspondent /D/10 digits your account number O 56a Intermediary A or D M 57a Account With Institution A, B or D O 72 Sender to Receiver Information 6*35x M = Mandatory O = Optional MT 200 Usage Rules The beneficiary of this transfer is always the Sender. MT 200 Field Specifications Field 20: Transaction Reference Number FORMAT 16x DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message. MIP VTB EUROPE VALIDATED RULES This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' © VTB Bank (Europe) SE – MIP formats – MT200 Page 2 / 7 VTB Bank (Europe) SE Rüsterstraße 7–9 60325 Frankfurt Germany Field 32A: Value Date, Currency Code, Amount FORMAT Option A 6!n3!a15d (Date)(Currency)(Amount) DEFINITION This field specifies the value date, currency and amount to be transferred. MIP VTB EUROPE VALIDATED RULES Date must be a valid date expressed as YYMMDD Field 53B: Sender's Correspondent Account DEFINITION This field specifies the ordering institution when other than the Sender of the message. Option B [/1!a][/34x] (Party Identifier) [35x] (Location) Example: 53B:/D/1234567890 Field 56a: Intermediary Option A [/1!a][/34x] (Party Identifier) 4!a2!a2!c[3!c] (Identifier Code) Option C /34x (Party Identifier) Option D [/1!a][/34x] (Party Identifier) 4*35x (Name & Address) DEFINITION This field specifies the financial institution through which the transaction must pass to reach the account with institution.
    [Show full text]
  • Documento Ayuda
    TRANSFERENCIAS AL EXTERIOR Beneficios Realiza transferencias al exterior desde nuestras más de 450 Agencias BCP a nivel nacional o desde la comodidad de tu casa a través de nuestra Banca por Internet. @ Recibe la confirmación de tus transferencias y el SWIFT automáticamente vía correo electrónico. Para ello deberás indicar tu correo electrónico en la solicitud. Seguridad: Las transferencias se trasmiten con claves encriptadas (vía sistema SWIFT). Características El importe mínimo a transferir es de USD 100.00 o su equivalente en otras monedas. Las transferencias al exterior están afectas al cobro del ITF. Tiempo de llegada de una transferencia al banco corresponsal de destino según horario de recepción de solicitud: TIEMPO DE LLEGADA AL BANCO CORRESPONSAL DE DESTINO PARA TRANSFERENCIAS AL EXTERIOR EN DÓLARES AMERICANOS MISMO DÍA SIGUIENTE DÍA ÚTIL (T+1) DOS DÍAS ÚTILES (T+2) RECIBIDA HASTA LAS RECIBIDA ENTRE LAS U.S.A. Y AMÉRICA LATINA 12:00 PM (MEDIO DÍA) 12:01 PM Y 04:00 PM RECIBIDA HASTA LAS RECIBIDA ENTRE LAS EUROPA 12:00 PM (MEDIO DÍA) 12:00 PM Y 04:00 PM RECIBIDA ENTRE LAS ASIA 8:00 AM Y 04:00 PM TIEMPO DE LLEGADA AL BANCO CORRESPONSAL DE DESTINO PARA TRANSFERENCIAS AL EXTERIOR EN OTRAS MONEDAS DISTINTAS AL DÓLAR MISMO DÍA SIGUIENTE DÍA ÚTIL (T+1) DOS DÍAS ÚTILES (T+2) RECIBIDA HASTA LAS U.S.A. Y AMÉRICA LATINA 12:00 PM (MEDIO DÍA) RECIBIDA HASTA LAS EUROPA 12:00 PM (MEDIO DÍA) RECIBIDA HASTA LAS ASIA 12:00 PM (MEDIO DÍA) 1 ANEXO 1: ¿CÓMO IDENTIFICAR LA CUENTA DE ABONO DEL BENEFICIARIO EN UNA TRANSFERENCIA AL EXTERIOR? Las cuentas de abono de los beneficiarios dentro de otros bancos en el exterior se identifican según tipos de códigos y dependiendo de la región donde se ubiquen pueden ser: 1.
    [Show full text]
  • Cash Management with SAP S/4HANA: Functionality and Implementation 477 Pages, 2017, $89.95 ISBN 978-1-4932-1579-9
    First-hand knowledge. Reading Sample This sample presents an overview of the bank account management process in a company and discuss the typical complexities and challen- ges the Treasury Department faces regarding their bank relationship data. It also covers in detail how to maintain banks and house banks in Cash Management in SAP S/4HANA. “Bank Account Management” Contents Index The Authors Dirk Neumann, Lawrence Liang Cash Management with SAP S/4HANA: Functionality and Implementation 477 Pages, 2017, $89.95 ISBN 978-1-4932-1579-9 www.sap-press.com/4479 Chapter 2 Bank Account Management 2 Online banking fraud is on the rise everywhere in the world. Compa- nies with hundreds, sometimes thousands, of bank accounts across the world are especially exposed to this risk. Bank Account Manage- ment gives you the control over your accounts and helps you centrally manage account signatories for the whole group. Managing large numbers of bank relations and signatory data is time-consuming and can be a real challenge for Treasury Departments of large organizations. Add the complexity of managing and maintaining bank relations, the inherent fraud and compliance risk, and you can understand the motivation behind SAP’s new develop- ment, Bank Account Management (BAM). This chapter will first present an overview of the bank account management process in a company, discuss the typical complexities and challenges for the Treasury Department to get control over and to gain insights into their bank relationship data. We’ll then cover in detail the functionalities provided by the Bank Account Manage- ment module, which is part of SAP S/4HANA Finance for Cash Management.
    [Show full text]
  • Payment Formatting Guidelines
    PAYMENT FORMATTING GUIDELINES 03.2014 Version 2.7 business.westernunion.com Page 1 of 77 business.westernunion.com TABLE OF CONTENTS CURRENCY GUIDELINES ................................................................................. 3 MAXIMIZING THE USE OF THE GUIDELINES .................................................. 3 BBAN / BASIC ACCOUNT NUMBER .................................................................. 3 IBAN / ACCOUNT NUMBER ............................................................................... 3 SWIFT / BIC CODE ............................................................................................. 4 BANK CODE ....................................................................................................... 4 NON-SWIFT BIC ................................................................................................. 5 ADDITIONAL REQUIREMENTS ........................................................................ 5 IBAN & SWIFT CODE COUNTRIES ................................................................... 6 COUNTRY CURRENCIES (BY CURRENCY CODE) CURRENCIES A - E ............................................................................................ 7 EURO IBAN REQUIREMENTS ......................................................................... 21 CURRENCIES F - J .......................................................................................... 29 CURRENCIES K - O ......................................................................................... 35 CURRENCIES P - T .........................................................................................
    [Show full text]
  • Information About Transfer Orders with Missing Or Incorrect Data
    INFORMATION about transfer orders incurring “Extra transfer fees for transfer orders with missing or incorrect data” Incorrect SWIFT / BIC Cause of error: - The SWIFT/BIC code is missing, and the name and address of the bank is indicated only in words - The SWIFT/BIC code is indicated but not in the appropriate field but in the rows left for the bank’s name and address, or the rows of the sender’s message to the beneficiary, which are free-format rows and hence cannot be interpreted by the systems automatically. - The SWIFT/BIC code is indicated but incorrectly. How can you avoid this error? - This information has to be indicated on the invoices incoming from partners more and more often, since it is vital information in international money transfers. Thus, it is in the interest of your partners as well to indicate this on the invoices or other documents in which they ask for transfers from their clients. - Should there be no such information on the invoice, please ask from your partners for their bank’s SWIFT/BIC code. Every bank has to specify their SWIFT/BIC code on their bank account statements or announce it to their clients upon request, so your partners have to be able to provide you with this information. - SWIFT/BIC codes may only consist of 8 or 11 characters, and any length other than these are incorrect. - SWIFT/BIC codes may be searched by the name of the bank on the http://www.swift.com/bsl webpage. - Please enter the correct SWIFT code you have been provided with only in the field where the SWIFT/BIC code has to be indicated.
    [Show full text]
  • PAYMENT GUIDELINES Frequently Asked Questions & Definitions
    ROTARY INTERNATIONAL PAYMENT GUIDELINES Frequently Asked Questions & Definitions Where can I find the banking information requested on the payee form/What information is required to make an electronic transfer into my account? There are different requirements in different countries depending on your country’s banking regulations (see the Payment Guidelines for Rotarians: http://www.rotary.org/RIdocuments/en_pdf/rits_payment_guidelines_en.pdf ). It is helpful to visit your bank and ask them to help provide you with the appropriate information listed on the payee form as they may be more familiar with the type of information required. General requirements for electronic funds transfers are listed below. Please also see the definitions below for an explanation of the various bank codes required to make payments. Why does Rotary need my bank information to make a payment? As banking becomes more and more electronic worldwide, checks and paper-based payment methods are becoming less common because they are considerably less efficient, less secure and much more costly to process. Already, virtually all of Rotary’s cross border banking transactions are being made via electronic transfers and a significant number of domestic payments are made electronically as well. While all bank transfers can be subject to fees, most recipients of domestic transfers pay minimal to no fees. The best way for Rotary to keep these fees minimal, from the perspective of both the recipient of funds and the sender, is to provide complete and correct account information to the bank through which the funds are being sent, including all required bank codes. By providing complete and correct account information initially, including instructions to make payments via the preferred payment method, Rotarians help us to keep payment processing costs low and to send funds more quickly and efficiently.
    [Show full text]