Using Bank-Defined Import File Formats - Welcome to ... Bank-Defined Import File Formats CashPro®...

CashPro® Online

CashPro® Online Quick Reference Guide Global Payments Using Bank-Defined Import File Formats

CashPro® Online Quick Reference Guide 2

CashPro® Online

About this Guide ..................................................................................................................................3

Global Payments Comma-Separated Value Format ...................................................................5

Wandalink Format ............................................................................................................................ 11

Foreign Exchange, Wires, and Drafts Comma-Separated Value Format .......................... 15

Table of Contents


CashPro® Online

About this Guide

Note: You can print each topic individually for your convenience, if desired.

This Global Payments quick reference guide provides the information needed to create import files using several formats defined and supported by Bank of America Merrill Lynch. The bank-defined formats available are:

▪ Comma-separated value (CSV)

– Global Payments (GPCSV)

– Foreign Exchange, Wires, and Drafts (FXWDCSV)

▪ Wandalink CSV

This guide describes the layout of each file format in detail, lists the payment types each format supports, and provides examples of import files that follow each format.

Please keep the following in mind when choosing a file format:

▪ Bank of America Merrill Lynch does not recommend using formats other than those listed above and provides limited support for them. Any format not listed is intended for use only by clients who migrated from a legacy application and already have a file format.

▪ All other clients should map to the GPCSV format, or create a custom file format. Refer to Importing a File for information on creating a custom file format.

▪ Use these guidelines when entering values in file format fields:

– Use only the following characters, unless specifically allowed by the local clearinghouse used for payment:

A-Z

a-z

0-9

/ (forward slash)

- (hyphen)

? (question mark)

: (colon)

( (left parenthesis)

) (right parenthesis)

. (period)

, (comma)


Return to Table of Contents

‘ (apostrophe or single quotation mark. Do not use the tick mark (`) above the Tab key.)

+ (plus sign)

(space)

– Start or end a field only with A-Z, a-z, or 0-9. Do not start or end a field with a non-alphanumeric character. Using a hyphen (-) or colon (:) as the first, last, or only character in any field will cause a transaction to fail.

– If copying and pasting data from another source, first paste the data into Microsoft® Notepad (or another text editor that strips formatting). Then, copy the data from the text editor into your import file. This should remove any illegal or unprintable characters from your data. Extraneous formatting characters in any field will cause a transaction to fail during import.

– If sending Beneficiary or Remittance information, always enter data in these fields in order, starting with line 1. Do not leave lines blank.

In addition, Bank of America Merrill Lynch supports the following country-specific file formats:

▪ CNABE (Brazil)

▪ ZENGIN (Japan)



CashPro® Online

Introduction

This card provides the information needed to use the Global Payments Comma-Separated Value (GPCSV) format to import a file to Global Payments within CashPro® Online.

The GPCSV format supports the following payment types:

▪ Automated Clearing House (ACH)

▪ Drafts

▪ Internal Transfers

▪ MT210

▪ Multibank

▪ US Drawdowns

▪ Wires

Note: US Drawdown payments must be sent by themselves in a file.

You must use the following guidelines when creating a file using the GPCSV format:

▪ Insert a comma after each field value (Value,), except for the last value in the record.

▪ Insert an additional comma after a field value (Value,,) to skip the next field.

The following table provides the layout for the GPCSV format and information needed for each field:

Note: The M/O/C column indicates whether the field is Mandatory (M), Optional (O), or Conditional (C).

Field Num

Field Name

Description Expected Values

M/O/C Payment Types Supported

Wire ACH Multibank Draft MT210 US Drawdown

1 Destination Country

2-character country code (GB, US, for example).

For MT210s, country code of the ordering party or ordering institution.

M X X X X X X

Global Payments: Global Payments Comma-Separated Value Format



Field Num

Field Name




2 Payment Type

AT - Internal Transfers

DD - US Drawdown

LOW - Low priority. Use for ACH. LOW - Low priority where Beneficiary Account and Beneficiary Bank ID are blank. Use for Drafts.

MT210 - MT210 transaction

URG - Urgent. Use for Wires and Multibank.

M X X X X X X

3 Sender’s Reference

1 - 16 alphanumeric characters O X X N/A X N/A N/A

4 Related Reference

1 - 16 alphanumeric characters O N/A N/A X N/A X N/A

5 Value Date Formats:

MMDDYYYY

DDMMYYYY

Format used depends on import profile preference.

Global Payments will use the earliest available date if left blank.

O X X X X X N/A

6 Debit Account Number

Client Debit Account (Bank of America Merrill Lynch or Multibank)

For MT210s, the Bank of America Merrill Lynch account being credited.

M X X X X X N/A

7 Debit Amount

Amount being debited.

Decimal precision depends on import profile preference.

Required if no credit amount entered.

C X X X X N/A N/A

8 Credit Amount

Amount being credited.

Required if no debit amount entered.

C X X X X X N/A

9 Currency Currency of Debit or Credit Amount M X X X X X N/A

10 Drawee Country

If draft currency is EUR, country of Draft Drawee Branch.

O N/A N/A N/A X N/A N/A

11 Originator Name

Name of originator to append to payment in field 50 in SWIFT format

O X X X X N/A N/A

12 Originator Account

Account number for a transaction on behalf of another party

X X X X X N/A N/A

13 Originator Address

Originator Address to append to payment in field 50 in SWIFT format

O X X X X N/A N/A

14 Originator City

City of Originator to append to payment in field 50 in SWIFT format

O X X X X N/A N/A

15 Originator Country

2-character Country Code (GB, US, DE, for example) of Originator to append to payment in field 50 in SWIFT format

O X X X X N/A N/A

16 Beneficiary Account

Account being credited.

Depends on country/payment type requirement.

C X X X - optional N/A N/A N/A



Field Num

Field Name




17 Beneficiary Name

Name of Credit Party M X X X X N/A N/A

18 Beneficiary Address

Address of Credit Party M X X X X N/A N/A

19 Beneficiary City

City of Credit Party M X X X X N/A N/A

20 Beneficiary Postal Code

Postal Code of Credit Party O X X X X N/A N/A

21 Beneficiary Country

2-character Country Code (GB, US, DE, for example) of Credit Party

M X X X X N/A N/A

22 Beneficiary Bank ID

Bank of account being credited. (Bank country should = Destination Country in Field 1. Use SWIFT Bank Identifier Code (BIC) or country-specific Routing ID.)

Depends on country/payment type requirement details.

C X X X - Optional N/A N/A N/A

23 Beneficiary Information Line 1

Free-form Originating Bank Information (OBI) data

O X X X X N/A N/A


Free-form OBI data O X X X X N/A N/A





27 Intermediary Bank ID

Intermediary Bank BIC or country-specific Routing ID

O X X X N/A X N/A

28 Receiving Bank ID

Not currently supported N/A N/A N/A N/A N/A N/A N/A

29 Receiver Information Line 1

Bank to Bank Information (BBI) data.

Must start this field with a forward slash (/).

Include key word data here: /PAYACH/, for example.

To initiate the correct payment type for some in-country payments, specific key words are required to differentiate Domestic Wire from other in-country payments.

C X X N/A X N/A N/A


Must start this field value with two forward slashes (//).

Include additional instructions:

//FFC to Account 12334, for example.

O X X N/A X N/A N/A


Must start this field value with two forward slashes (//).



O X X N/A X N/A N/A


Must start this field with two forward slashes (//).



O X X N/A X N/A N/A



Field Num

Field Name




33 Beneficiary Email

Send beneficiary advising alerts to this email address.

O X X X X X N/A

34 Notes Notes to store with the payment. O X X X X X N/A

35 Send Note to Beneficiary

Set value to “1” to send stored notes in the advising alert to the beneficiary.

O X X X X X N/A

36 Charges Who pays for the transactions fees.

Valid values:

SHA: Shared

OUR: Originator

BEN: Beneficiary

The client must be entitled to OUR. If no value is entered, payment defaults to SHA.

O X X X X N/A N/A

37 User Defined Field 1

User-defined field.

Data types depend on user-defined field configuration in Global Payments Preferences.

O X X X X X N/A


User-defined field.


O X X X X X N/A


User-defined field.


O X X X X X N/A


User-defined field.


O X X X X X N/A


User-defined field.


O X X X X X N/A

42 Template Code

If importing a file with a template code and name, use the template code stored in Global Payments.

C X X X X N/A N/A

43 Template Name

Template name associated with the template code.

O X X X X X N/A

44 Reserved

45 Purpose of Payment

To help ensure timely delivery of funds to the beneficiary, this field is required for some cross-currency payments.

C X X X X X N/A

46 Beneficiary Advising

Mobile Number of Beneficiary for Beneficiary Advising Alerts.

O X X X X X N/A

47 System Field 1

48 System Field 2

49 System Field 3

50 System Field 4

51 System Field 5



Field Num

Field Name




52 System Field 6

53 System Field 7

For FX Wires, this field is reserved for the FX regulatory Purpose of Payment value. Required only for certain credit currencies when Debit Currency is not = Credit Currency.

For MT210 (Advice to Receive), this field is reserved for Ordering Party Name. Include only if Ordering Party is not a bank.

For Multibank, include SWIFT key words for 23E additional processing instructions (URGP = Urgent Payment, RTGS = Real-Time Gross Settlement)

C X N/A X N/A X X

54 System Field 8

First line of Ordering Party Address.

Include only if Ordering Party is not a bank.

For Multibank, include free-form text instructions for 23E key word.

C N/A N/A X N/A X X

55 System Field 9

Ordering Party City.


For Multibank, include Swift key words for 23E additional processing instructions (URGP, RTGS).

C N/A N/A X N/A X X

56 System Field 10

Ordering Party Postal Code.


For Multibank, Include free-form text instructions for 23E key word.

C N/A N/A X N/A X X

57 System Field 11

Ordering Party Country. Use 2-character country code (GB, DE, for example).


For Multibank, Include Swift key words for 23E additional processing instructions (URGP, RTGS).

C N/A N/A X N/A X X

58 System Field 12

Ordering Institution. If Ordering Institution ID is a local sort ID, use this position only.

Include only if Ordering Party is a bank and identified with a local sort ID.


C N/A N/A X N/A X X

59 System Field 13

Beneficiary Identification Code (BIC) of the Ordering Institution. If the Ordering Institution ID is a SWIFT BIC, use this position only.

Include only if Ordering Party is a bank and identified with a BIC.

For Multibank, Include Swift key words for 23E additional processing instructions (URGP, RTGS).

C N/A N/A X N/A X N/A

60 System Field 14


C N/A N/A X N/A N/A N/A

61 System Field 15



Field Num

Field Name




62 System Field 16

63 System Field 17

64 System Field 18

65 System Field 19

66 System Field 20

The following is a sample of a file formatted according to GPCSV specifications:



CashPro® Online

Global Payments

Introduction

This card provides the information needed to use the Wandalink format for importing a file to Global Payments within CashPro® Online. This format supports the following payment types:

▪ Automated Clearing House

▪ Drafts

▪ MT202

▪ Multibank

▪ Payroll transactions

▪ Wires

You must use the following guidelines when creating a file using the Wandalink format:

▪ The first record of the file contains the field names for the data being imported. Enclose all field names in double quotation marks, and insert a comma after each (“Name”,), except for the last name in the record.

▪ The second record in the file contains the first payment transaction. Enclose all field values in double quotation marks, and insert a comma after each field value (“Value”,) except for the last value in the record.

Note: The Date and Count fields do not require double quotation marks.

▪ Enclose opening and closing double quotation marks in commas (,””,) to skip a field value.

▪ Each record in the file should contain only one payment transaction.

▪ Fields such as Name and Address may contain “CR-LF” as a separator. Each “CR-LF” must be enclosed in double quotation marks.

Wandalink Format



The following table provides the layout for the Wandalink format and information needed for each field:

Note: The M/O/C/V column indicates whether a field is Mandatory (M), Optional (O), Conditional (C), or Variable (V). TMP means a field that is part of template when a client is using repetitive matching and not inputting a free form payment.

Field Num

Field Name Description Field Length/Type

TMP M/O/C/V

Wires Payroll ACH

Drafts Multibank MT202

1 ImportSequence Number

N/A 6 numeric characters

M N/A N/A N/A N/A

2 RepetitiveName (template code)

Template code when using repetitive matching (sending a file with a template code and name).

35 alphanumeric characters

O X X X X

3 MessageType Transaction type. If using repetitive matching, may be left blank.

Value is “GBX” for MT202.

Value is “IFT” for ACH, Drafts, Multibank, Payroll, and Wires.

Value is “WT” for Wires and Drafts.

If value is “WT” or “IFT”, the key word in the ReceiverInfo field indicates the Payment Type and Payment Method.


V X X X X

4 Amount Credit amount of transaction. If amount is included in the template when using repetitive matching, amount may be left blank.

17 numeric characters

V X X X X

5 Beneficiary AccountType

Mandatory when BeneficiaryAccount Identifier is populated.


V X X X X

6 Beneficiary AccountIdentifier

Mandatory when BeneficiaryAccount Type is populated.


V X X X X

7 BeneficiaryName Address

Line 1 (beneficiary name) is mandatory. Lines 3 and 4 are optional.

4 lines of 35 alphanumeric characters each

C X X X X

8 BeneficiaryBank AccountType

Mandatory when BeneficiaryBank AccountIdentifier is populated.


C X X X X

9 BeneficiaryBank AccountIdentifier

Mandatory when BeneficiaryBank AccountType is populated.


C X X X X



Field Num


TMP M/O/C/V

Wires Payroll ACH


10 BeneficiaryBank NameAddress

Line 1 (name of beneficiary) is mandatory when Line 2 (address 1) is populated, and BeneficiaryAccount Type and BeneficiaryAccount Identifier are blank.

Line 2 is mandatory when Line 1 is populated, and BeneficiaryAccount Type and BeneficiaryAccount Identifier are blank.

Lines 3 and 4 are optional.


C X X X X

11 BeneficiaryInfo Information to communicate to the beneficiary, such as invoice information.


O X X N/A N/A

12 ChargesTo Code that indicates who pays for charges.

SHA: Shared

OUR: Originator

BEN: Beneficiary

The Client must be entitled to OUR. If no value is entered, payment defaults to SHA.

3 characters alphanumeric

C X X X X

13 Currency Currency of funds delivered to beneficiary. May be blank if RepetitiveName (Field 2) is provided.


V X X X X

14 DebitAccount Identifier

May be blank if RepetitiveName is provided.


V X X X X

15 DebitCurrency May be blank if RepetitiveName is provided.


V X X X X

16 IntermediaryBank AccountType

Mandatory when IntermediateBank AccountIdentifier is populated.


V Wires N/A X X

17 IntermediaryBank AccountIdentifier

Mandatory when IntermediateBank AccountType is populated.


V Wires N/A X X



Field Num


TMP M/O/C/V

Wires Payroll ACH


18 IntermediaryBank NameAddress

First line (name of beneficiary) is mandatory when:

Second line (address 1) is populated, and IntermediaryAccount Type and IntermediaryAccount Identifier are blank.

Second line is mandatory when:

First line is populated, and IntermediaryAccount Type and IntermediaryAccount Identifier are blank.

Lines 3 and 4 are optional.


V Wires N/A X X

19 OriginatorName Address

Name and address of payment originator.


O X X N/A N/A

20 ReceiverInfo Includes Payment Method information and Instructions to beneficiary.


O X X X X

21 SendersRef Allows client to include reference information, such as the Transaction Number of a previously created payment.


O X X X X

22 ValueDate Value Date of instruction

M X X X X

23 Comment Additional comments or instructions for other users who may view or approve the transaction.


O X X X X

The following is a sample of a file formatted according to Wandalink specifications:



CashPro® Online

Introduction

This card provides the information needed to use the Foreign Exchange, Wires, and Drafts Comma-Separated Value (FXWDCSV) format for importing a file to Global Payments within CashPro® Online. FXWDCSV is a standard, bank-defined format.

The FXWDCSV format supports the following payment types:

▪ Automated Clearing House (ACH)

▪ Drafts

▪ MT202

▪ Multibank

▪ Wires

The FXWDCSV format supports Roman and Asian local language characters (Korean, Japanese, and Chinese, for example), so the File Encoding option UTF 16 must be enabled in the import profile within Global Payments. Refer to Importing a File for more information.

The import file must follow these standards:

▪ The header record is the first record in the file.

▪ Field values are enclosed in double quotation marks (“Value”).

▪ A comma follows every field except the last field in a record (“Value”,).

▪ An additional comma follows a field value to indicate the omission of an optional field (“Value”,,).

▪ The trailer record is the last record in the file.

Important: More than one header record or trailer record causes the file import to abort.

Foreign Exchange, Wires, and Drafts Comma-Separated Value Format

Global Payments



Header Record

The layout for the header record is:Field Number Field Name Field Description/Value

1 File Type “PAYMENT”

2 Record Type “HEADER”

3 Creation Date MMDDYYYY format

4 Location ID 8-character Company identifier plus a 4-character identifier for the location where the file was created.

Example: Your Company ID is “ABCDComp”, and the file was created in the London office. The Location ID could be “ABCDCompLndn”.

5 Sequence Number An integer from 0001 to 9999 that identifies the import file.

This is an example of a complete header record:

“PAYMENT”,”HEADER”,”09212013”,”ABCDCompLndn”,”0001”

Payment Record

Each payment record must begin with the word “PAYMENT”.

The following table provides the layout for the FXWDCSV format and information needed for each field:

Note: The M/O/C column indicates whether a field is Mandatory (M), Optional (O), or Conditional (C).

Payment Types Supported

Field Num


M/O/C/ ACH Payroll Wires


1 Record Type Indicates the record type. Always contains the value “PAYMENT”.


M X X X N/A

2 Payment Type Indicates the payment type:

“FXW” for ACH, Drafts, Payroll, and Wire payments.

“MBW” for Multibank.


M X X X N/A

3 Senders Reference Number

May include reference information such as the Transaction Number of a previously created payment.

1 – 16 alphanumeric characters

O X X X N/A

3b Related Reference Number

Additional reference information

1 – 16 alphanumeric characters

O X X X X

4 Value Date Value Date of Instruction. Format determined by FXWDCSV profile in Global Payments.


O X X X N/A




Field Num




5 Amount Type Valid values are “DEBIT” or “CREDIT”. Defines the Amount in field 6.

Global Payments rejects the transaction record if the Amount Type is an invalid value.

Value should always be “CREDIT” for Multibank and MT202 transactions.

5 – 6 characters M X X X X

6 Amount If Amount Type is “CREDIT”, amount paid to the beneficiary.

If Amount Type is “DEBIT”, amount debited from the Debit Account.

Amount must be in the format 9,999,99.


M X X X X

7 Credit Currency International Organization for Standardization (ISO) code of the currency paid to the beneficiary

3 alphanumeric characters, all uppercase (USD, for example)

M X X X X

8 Originator Name Name of the customer ordering the wire payment


O X X N/A N/A

9 Originator Address Line 1

First line of the ordering customer’s address


O X X N/A N/A


Second line of the ordering customer’s address


O X X N/A N/A


Third line of the ordering customer’s address


O X X N/A N/A

12 Debit Account Identifier of the account debited for the transaction.


M X X X N/A

13 Beneficiary ID Type

Code of the Identifier Type for the fund recipient.

If left blank, Beneficiary ID should be blank.

Examples: DD - Other IB - IBAN


C X N/A X N/A




Field Num




14 Beneficiary ID Identifier of the fund recipient.

If left blank, Beneficiary ID Type should be blank.


C X N/A X N/A

15 Beneficiary Name Name of the fund recipient.

If Beneficiary ID Type and Beneficiary ID are blank, populate this field and Beneficiary Address Line 1.


M X X X N/A

16 Beneficiary Address Line 1

If Beneficiary ID Type and Beneficiary ID are blank, populate this field to accompany Beneficiary Name.


C X X X N/A


Second address line 35 alphanumeric characters

O X X X N/A


Third address line 35 alphanumeric characters

O X X X N/A

19 Beneficiary Bank ID Type

Identifier Type Code of the Pay Through Bank. If this field is blank, Beneficiary Bank ID should be blank.


C X N/A X N/A

20 Beneficiary Bank ID

Identifier of the Pay Through Bank. If this field is blank, Beneficiary Bank ID Type should be blank.


C X N/A X N/A

21 Beneficiary Bank Name

If Beneficiary Bank ID Type and Beneficiary Bank ID are blank, populate this field and Beneficiary Address Line 1.


M X N/A X N/A

22 Beneficiary Bank Address Line 1

If Beneficiary Bank ID Type and Bank ID are blank, populate this field and Beneficiary Bank Name.

If Beneficiary Bank ID Type and Beneficiary Bank ID are populated, all address fields are optional.

If Beneficiary Bank ID is blank, Beneficiary Bank Name and Beneficiary Bank Address Line 1 are required.


C X N/A X N/A


Line 2 of Beneficiary Bank Address


O X N/A X N/A




Field Num





Line 3 of Beneficiary Bank Address


O X N/A X N/A

25 Intermediary Bank ID Type

Identifier Type Code for the Intermediary Bank.

If this field is blank, Intermediary Bank ID type should be blank.


C X N/A X N/A

26 Intermediary Bank ID

Identifier for the Intermediary Bank.

If this field is blank, Intermediary Bank ID Type should be blank.


C X N/A X N/A

27 Intermediary Bank Name

Name of the Intermediary Bank.

This field is mandatory if Intermediary Bank ID Type and Intermediary Bank ID are blank.


C X N/A X N/A

28 Intermediary Bank Address Line 1

Address line 1 of the Intermediary Bank.

If Intermediary Bank Name is populated, but Intermediary Bank ID Type and Intermediary Bank ID are blank, Intermediary Bank Address Line 1 is required.


C X (Wires only)

N/A X N/A


Address line 2 of the Intermediary Bank


O X N/A X N/A


Address line 3 of the Intermediary Bank


O X N/A X N/A


Line 1 of additional transaction information


O X N/A X N/A




O X X X N/A




O X X X N/A




O X X X N/A




Field Num




35 Charges Code that indicates who pays for charges.

SHA: Shared

OUR: Originator

BEN: Beneficiary

The client must be entitled to OUR.

If no value is entered, payment defaults to SHA.


O X N/A X N/A


Instructions for Bank of America Merrill Lynch and other banks processing the transaction.

May contain routing key words such as PAYEFT or PAYACH that determine payment type and payment method.

May also contain non-routing key words with specific payment instructions.

Format:

/codeword/

OR

/codeword/text


O X N/A X N/A


Same as row 36, except format can also be /text/


O X N/A X N/A




O X N/A X N/A




O X N/A X N/A




O X N/A X N/A




O X N/A X N/A



“Bank of America Merrill Lynch” is the marketing name for the global banking and global markets businesses of Bank of America Corporation. Lending, derivatives, and other commercial banking activities are performed globally by banking affiliates of Bank of America Corporation, including Bank of America, N.A., member FDIC. Securities, strategic advisory, and other investment banking activities are performed globally by investment banking affiliates of Bank of America Corporation (“Investment Banking Affiliates”), including, in the United States, Merrill Lynch, Pierce, Fenner & Smith Incorporated and Merrill Lynch Professional Clearing Corp., both of which are registered broker-dealers and members of SIPC, and, in other jurisdictions, by locally registered entities. Merrill Lynch, Pierce, Fenner & Smith Incorporated and Merrill Lynch Professional Clearing Corp. are registered as futures commission merchants with the CFTC and are members of the NFA. Investment products offered by Investment Banking Affiliates: Are Not FDIC Insured • May Lose Value • Are Not Bank Guaranteed. ©2015 Bank of America Corporation

Ouvidoria Bank of America Merrill Lynch1 | DDG: 0800 886 2000 | e-mail: [email protected] 1 Bank of America Merrill Lynch Banco Múltiplo S.A. e Merrill Lynch S.A. Corretora de Títulos e Valores Mobiliários

Trailer Record

The layout for the trailer record is:Field Number Field Name Field Description/Value

1 File Type “PAYMENT”

2 Record Type “TRAILER”

3 Hash Total Mandatory if the Hash Totals option in the FXWDCSV import profile is set to Yes.

Optional if the Hash Totals option in the FXWDCSV import profile is set to No.

Right-justified.

4 Record Count Mandatory if the Record Count option in the FXWDCSV import profile is set to Yes.

Optional if the Record Count option in the FXWDCSV import profile is set to No.

1 – 5 numeric characters

This is an example of a complete trailer record:

“PAYMENT”,”TRAILER”,”0000015000000”,”100”

The following is a sample of a file formatted according to FXWDCSV specifications:

Date post:	04-Jul-2018
Category:	Documents
Upload:	ngothien
View:	628 times
Download:	15 times

Using Bank-Defined Import File Formats - Welcome to ... Bank-Defined Import File Formats CashPro®...

Documents