Documento Ayuda
Total Page:16
File Type:pdf, Size:1020Kb
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 -
RSA Adaptive Authentication (Hosted) 11 Programmer's Guide
RSA Adaptive Authentication (Hosted) Programmer's Guide Contact Information Go to the RSA corporate web site for regional Customer Support telephone and fax numbers: www.rsa.com Trademarks RSA, the RSA Logo and EMC are either registered trademarks or trademarks of EMC Corporation in the United States and/or other countries. All other trademarks used herein are the property of their respective owners. For a list of RSA trademarks, go to www.rsa.com/legal/trademarks_list.pdf. License agreement This software and the associated documentation are proprietary and confidential to EMC, are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice below. This software and the documentation, and any copies thereof, may not be provided or otherwise made available to any other person. No title to or ownership of the software or documentation or any intellectual property rights thereto is hereby transferred. Any unauthorized use or reproduction of this software and the documentation may be subject to civil and/or criminal liability. This software is subject to change without notice and should not be construed as a commitment by EMC. Note on encryption technologies This product may contain encryption technology. Many countries prohibit or restrict the use, import, or export of encryption technologies, and current use, import, and export regulations should be followed when using, importing or exporting this product. Distribution Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC believes the information in this publication is accurate as of its publication date. -
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 -
2015 Global Payments Guide
TREASURY SERVICES 2015 Global Payments Guide Your Guide To Making Cross-Currency Payments in over 150 Countries with Ease. 2015 Global Payments Guide Last Updated: July 29, 2015 For the most up-to-date version, please visit jpmorgan.com/visit/guide | 2 The J.P. Morgan Global Payments Guide is your desktop resource to help you make timely and accurate payments to beneficiaries around the world. Work with J.P. Morgan to get the global payment support that Setting up your payment SWIFT BIC your business demands When setting up a payment, basic identifying information is SWIFT BIC, BIC, SWIFT ID or SWIFT refers to the ISO 9362 With employees, suppliers and operations located around the required. Additional information may be required by countries with restricted currencies. unique bank identifier code of a particular bank. They are globe, ensuring prompt payments in multiple currencies is a used to ensure automated and accurate identification of challenge. Your business requires a partner who takes the J.P. Morgan may use third party vendors for processing financial institutions within payment systems when messages time to understand your needs and helps ensure your payments in certain exotic currencies. These third party or money is transferred. payments are processed smoothly. vendors may require beneficiaries to provide supporting The BIC format contains a minimum of 8 and a maximum of As one of the top-ranked cash management and payments documents for regulatory purposes in some countries. 11 alphanumeric characters. processors in the world, J.P. Morgan is able to offer the tools Basic Information that help you manage your day-to-day global operations, Example: CHASUS33XXX o Full beneficiary name along with your more sophisticated foreign exchange needs. -
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. -
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 ...................................................................................................................................................................... -
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. -
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 -
Payment Formatting Guidelines
PAYMENT FORMATTING GUIDELINES 10.2018 Version 6.2 kpcu.com PAYMENT FORMATTING GUIDELINES Welcome to the October 2018 edition of the Payment Formatting Guidelines (PFG). In response to newly implemented payment requirements, we will be updating the following: • AUD (Australian Dollar), Beneficiary Account requirements • ARS (Argentine Peso), full beneficiary address required • ILS (Israeli Shekel), payments to Palestine require a 29 character IBAN • INR (Indian Rupee), P1401 POP code added back to list • MXN (Mexican Peso), beneficiary tax ID required: - Tax ID character length for INDIVIDUAL = 13 or 18 alphanumeric digits - Tax ID character length for BUSINESS = 12 alphanumeric digits • MXN (Mexican Peso), Recommendation: Beneficiary name should not include initials. Beneficiary names must consist of 3 or more letters. • NAD (Namibian Dollar), beneficiary bank branch address requirement removed • PHP (Philippines Peso), beneficiary bank branch address requirement removed • TWD (New Taiwan Dollar), Chunghwa Post Co., Ltd. will not accept TWD payments • SGD (Singapore Dollars), beneficiary bank account requirements amended to 5-14 digits, branch code required for payments to HSBC, OCBS or SBI. • NPR (Nepalese Rupee), (Removed) ADDITIONAL CONSIDERATIONS: Payments to Nepalese Nationals in Nepal can be done in NPR only. We are also happy to include requirements for the following new currencies: AWG (Arubian Florin); CDF (Congolese Franc); MDL (Maldavian Lieu); MNT (Mongolian Tugrik); MRU (Mauritanian Olguiya); STN (Dobra); and IQD (Iraqi Dinar). TABLE OF CONTENTS CURRENCY GUIDELINES �����������������������������������������������������������������������������������������������������������������������������������������������������3 MAXIMIZING THE USE OF THIS DOCUMENT . .3 BBAN/BASIC BANK ACCOUNT NUMBER . .3 IBAN/INTERNATIONAL BANK ACCOUNT NUMBER . .3 SWIFT/BIC CODE . .4 BANK CODE . .4 NON-SWIFT BIC . .5 BENEFICIARY ADDRESS . -
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 ......................................................................................... -
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. -
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.