ACCESS CSV Wire Transactions Import Reference Guide
ACCESS CSV Wire Transactions Import Reference Guide
This guide is confidential and proprietary to J.P. Morgan and is provided for your general information only.
It is subject to change without notice and is not intended to be legally binding. All services described in
this guide are subject to applicable laws and regulations and service terms. Not all products and services
are available in all locations. Eligibility for particular products and services will be determined by
JPMorgan Chase Bank, N.A. or its affiliates. J.P. Morgan makes no representation as to the legal,
regulatory or tax implications of the matters referred to in this guide.
J.P. Morgan is a marketing name for the Treasury Services businesses of JPMorgan Chase Bank, N.A.,
member FDIC, and its affiliates worldwide.
2
Table of Contents
Overview ...................................................................................................................................................... 4
Appendix A ................................................................................................................................................ 57
Transaction Method Codes ..................................................................................................................... 57
Clearing Codes ....................................................................................................................................... 57
Delivery Methods .................................................................................................................................... 57
Instruction Codes .................................................................................................................................... 58
Regulatory Reporting Codes ................................................................................................................... 59
Sender to Receiver Codes ...................................................................................................................... 59
Additional Details - Key Codes................................................................................................................ 61
Appendix E: Copy Active Templates from one J.P. Morgan Access® Client Profile to Another .... 100
Export Active Templates to a CSV Format ........................................................................................... 100
Import (Modified) CSV File Under Target Client Profile ........................................................................ 100
3
OVERVIEW
The J.P. Morgan Access® Transactions Import File feature allows the import and validation of files in
preparation for submitting transactions for approval and release. The Access Transactions file format is
used in this process and allows you to import:
Free-form transactions (Wires, Book Transfers, U.S. Account Transfers, Drafts/Checks,
Drawdowns and Advices to Receive)
Transactions from templates
Templates
Note: The Import File feature can be used to copy existing wire templates from one Access client
profile to another. Refer to Appendix E for more details.
When a file is imported into Access Transactions, various checks will be performed on the file and on
each transaction detail record contained in the file during the validation process. These checks include
duplicate file, file structure, entitlement, date range, field length and allowed characters.
During import, Access Transactions will determine if a file has been previously imported and will reject the
file if it is a duplicate. To be considered a duplicate file, all of the data in the file must be identical to a
previously imported file. If there are any differences between the files, the newly imported file will not be
rejected as a duplicate.
A client setting can be used to allow the submission of partial files, which are files found to contain both
valid and rejected transactions after import into Access. When submission of partial files is allowed,
successfully validated transactions will be submitted into the workflow and invalid transactions will be
rejected. You will need to correct and re-import rejected transactions in a new file. If partial submission is
not allowed and one or more transactions in a file fail to pass validation, no transactions are submitted
into the workflow. You will need to be correct and re-import the file.
The most important method for avoiding file import errors is to import the file first as a test file. The Import
File Test feature allows you to test a file by validating it in a test environment. When the test validation is
complete, the file displays in the import list as a test file with “(Test)” preceding its file name. You can then
view any transactions that were not validated successfully, as well as the reason(s) for their failure. Test
files cannot be submitted as transactions or rejected. The test file should be used to review and correct
any errors in your source file before re-importing. Test files can be deleted at any time.
Please refer to this guide to prepare your file to be transmitted (imported) for subsequent processing. You
may also refer to J.P. Morgan Access® OnlineSM Support Help for information on testing and importing
files for all methods except U.S. ACH. For U.S. ACH payments, please refer to the Payments U.S. ACH
Reference Guide.
4
GENERAL FILE REQUIREMENTS
An Access Transactions file can be composed of various transactions from different record input types
(i.e., free-form transactions, transactions from templates and templates) with different fields for each
record and transaction method. Each line of the file is considered an input type to be imported:
Access accepts data imported in a comma-delimited format (.CSV or .TXT file extensions).
The import file contains a header, a trailer and multiple detail record sections.
Enter each record or input type on one line of the file.
Do not include any data before the header section or after the trailer section. Doing so will cause
the file import to fail.
Separate each field within a record by a comma.
Do not enter a comma after the final field of a record.
The field lengths indicate the maximum length for the applicable field.
Leading and trailing spaces within a field will be ignored.
The characters allowed within alphanumeric fields (i.e. type = A) are defined by what the fields
represent. The characters entered are checked during validation.
If the field data includes a comma, then enclose the field in quotation marks (“”).
Enter digits in numeric fields (i.e., type = N). Use a period to indicate a decimal point. The field
validation determines the maximum number of digits allowed following a decimal point. Leading
or trailing zeroes are not required. The length of a numeric field includes the decimal point
character.
The date field (i.e., type = D) format is YYYYMMDD.
The box or Boolean field (i.e. type = B) format is populated with either Y (for Yes)/N (for No) or 1
(for Active)/2 (for Passive).
Enter values in all mandatory fields (i.e., the field must have a value other than spaces).
You may leave optional fields blank, but if you enter data in a field following a field you have
intentionally left blank, you must enter a comma in the blank field to mark its place in the record.
Fields denoted with an * are conditional, details of which may be found in the Conditional Logic
column. For fields noted as “mandatory for some locations,” please refer to the Online portal for
locations.
No data will be imported from fields labeled “unused” in the record layout, regardless of the value.
Fill in the name, street address and reference text fields from the first line. If there are several
lines of text, blank or empty lines should follow lines in which you have entered data.
The character set supported is:
abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
0123456789
/ - ? : ( ) . , ' + and SPACE
Note: Spaces should be embedded within text
For U.S. branch transactions, the following characters are also supported: # ! \ $ % & @ _ *
5
File format record layouts
An Access Transactions file must contain a header, trailer and at least one record or input type (i.e., free-
form transactions, transactions from template, and templates).
Header Format
The header is the first record within the file. All data entered before the header will be ignored.
Trailer Format
The trailer record should be at the end of the file. All data entered after the trailer record will be ignored.
Field Field Type Length Description Mandatory Example
No. Name
1 TRAILER A 7 Must be TRAILER Yes TRAILER
6
Detail Record Format for Free-form Transactions
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
1 Input Type A 2 To indicate import of a Y
free-form transaction,
Information
Record
transaction from a
template, or template.
Enter P to indicate a free-
form transaction.
Refer to Appendix A:
Transaction Method
Codes.
7
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
8
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
If a non-resident, value
is N (No).
11 Rate Type N 1 Field is used only for N* Unused for same-
creating U.S. FX currency transactions
transactions when the
client supports a choice of
rates.
Values:
1 = Active
2 = Passive
If left blank, field value is
derived from client
setting. When left blank
and a choice is available,
then Active is the default.
12 N/A N/A Unused field; please leave
blank.
value date.
Date format =
YYYYMMDD.
If not populated, defaults
to the first available
business day.
9
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
locations.
20 City, State, N/A Unused field for wires and N* Mandatory for some
Postal code book transfers; please beneficiary bank
leave blank. countries
10
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
11
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
12
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
number. 49 is ACCT
13
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
14
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
15
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
supports additional
text
16
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
Sender to Receiver
Codes.
17
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
Refer to Appendix A:
Additional Details – Key
Codes for the key names
and description of the
values.
18
Drafts/Checks – Generic Layout
The following grid outlines the detail record format for free-form drafts/checks to be imported through an
Access Transactions file.
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
transaction from a
template, or a template.
Enter P to indicate a free-
form transaction.
drawn.
Refer to Appendix C:
Branch Codes.
4 Account A 34 This is the account to be Y
Number debited for a transaction; It
is an optionally zero-
padded account number.
Example: 1BB456789
19
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
11 Rate Type N 2 Used only for creating U.S. N Unused for same-
FX transactions when the currency transactions.
client supports a choice of
rates.
Values:
1 = Active
2 = Passive
If left blank, field value is
derived from client setting.
When left blank and a
choice is available, then
Active is the default.
20
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
16 Name A 35/70* The payee name; free- Y Field length for Asia
format text. back offices is 70.
21
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
32 leave blank.
22
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
Address 2
48 leave blank.
23
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
on ordering account
reporting.
24
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
25
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
26
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
27
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
Refer to Appendix A:
Additional Details – Key
Codes for the key names
and description of the
values.
28
U.S. Drawdowns – Generic Layout
The following grid outlines the detail record format for free-form drawdowns to be imported through an
Access Transactions file. This layout applies to U.S. branches only.
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
29
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
12 leave blank.
value date.
Date format =
YYYYMMDD.
If not populated, defaults
to the first available
business day.
format text.
Example: ABC Company
30
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
drawdown
31
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
Debit Bank Section (cont.)
72 City A 32 For U.S. Wire drawdown, N* Mandatory for Wire
enter city, state, postal drawdown only
code (zip code) as free-
format text.
Field is unused for Book
drawdown
the receipt
blank
32
Advice to Receive – Generic Layout
The following grid outlines the detail record format for free-form advice to receive transactions to be
imported through an Access Transactions file.
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
transaction from a
template, or a template.
Enter P to indicate a free-
form transaction.
33
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
Amount required
Use a period to indicate a
decimal point.
(cont.)
value date.
Date format =
YYYYMMDD.
If not populated, defaults to
the first available business
day.
34
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
Intermediary Bank Section
35
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
blank
36
U.S. Account Transfers – Generic Layout
The following grid outlines the detail record format for free-form U.S. account transfers to be imported
through an Access Transactions file.
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
transaction from a
template, or a template.
Enter P to indicate a free-
form transaction.
37
Section Field Field Name Type Length Description Mandatory Conditional Logic
No.
Date format =
YYYYMMDD.
If not populated, defaults to
the first available business
day.
14 N/A Unused; please leave N/A
blank.
15 ID Value A 34 For US account transfers, Y
this is the To Account
Beneficiary Section
Number.
16 Name A 35 Beneficiary name; For US Y
Account Transfers ONLY,
the field is optional and can
be left blank. However, if
provided, it should be the
Bank ID of the To Account.
Free-format text
17 to N/A N/A Unused fields; please leave N/A
23 blank.
24 to N/A N/A Unused fields, but I be N/A
Section Unused
account transfer.
blank
38
Detail Record Format for Transactions From Templates
Generic Layout
The following grid outlines the detail record format for transactions created from templates to be
imported through an Access Transactions file.
To find country-specific information for formatting fields, please refer to the generic detail record formats
for rules specific to transactions for the template being used, or to the regional detail record formats,
where available. Fields denoted with an * are conditional; please refer to the Conditional Logic column of
the generic detail record format for the specific transaction. The last column of the grid below provides the
corresponding field number of the generic detail record format for free-form transactions.
Notes:
If the template being used has locked fields, any data supplied in the corresponding field in the
import record will be ignored.
If the template being used has unlocked fields and data is supplied in the corresponding field
within the import record, then this data will be used to create the transaction, overriding data
stored on the template.
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
Codes.
39
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
5 Enhanced N 10 N* An optionally zero-padded N/A
Template Line number.
Number
Mandatory for an enhanced
template; unused for a
standard template and must be
left blank.
40
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
41
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
17 Detail 5 A 35/70 N If a domestic U.S. enhanced 81
template is used, then semi-
repetitive text can be provided,
if allowed; otherwise, the field is
unused and left blank.
42
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
25 Code A 8 N Regulatory reporting code; 89
unused for U.S. branches.
Refer to Appendix A:
Regulatory Reporting Codes,
Regulatory Reporting Section
when applicable.
Refer to Appendix A:
Instruction Codes.
43
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
33 Instruction Text 2 A 30 N Free format text 97
44
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
44 Sender to A 8 N* Code as advised by 108
Receiver Code 5 J.P.Morgan or your beneficiary.
48 Priority B 1 N 112
49 Urgent B 1 N 113
45
Detail Record Format for Templates
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
1 Input Type A 2 Y Enter T to indicate template 1
Information
Record
46
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
4 Method A 7 Y Must be one of the following: 2
WIRES, BOOKTX, ACTTX,
ATR, DRWDWN, BNKDRFT
5 Debit/Credit Bank A 11 Y SWIFT BIC or ABA identifier: 3
ID identifies the branch of the
originating account ordering
the transaction.
Refer to Appendix C: Branch
Codes
47
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
10 Maximum Amount N 20,3 N Optional maximum transaction N/A
amount in transaction currency.
Use a period for a decimal
point; decimal places are not
mandatory.
In Access Transactions, the
amount will be displayed
according to the user’s
preference.
48
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
16 ID Type A 34 N* Refer to Appendix B: Bank and 14
Account ID Type Codes.
24 Supplementary ID A 34 N* 22
49
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
25 Supplementary ID A 34 N 23
Value
33 Supplementary ID A 34 N* 31
34 Supplementary ID A 34 N 32
Value
50
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
35 Address 1 A 35 N* 33
36 Address 2 A 35 N* 34
Mail To Address Section
37 Address 3 A 32 N* 35
38 City A 21 N* 36
39 State A 2 N* 37
40 Zip A 5 or 5-4 N* 38
41 Mail To Country A 2 N* 39
43 ID Value A 34 N* 41
44 Name A 35 N 42
Intermediary Bank Section
45 Address 1 A 35 N 43
46 Address 2 A 35 N 44
49 Supplementary A 34 N* 47
ID
50 Supplementary A 34 N 48
ID Value
51
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
52 ID Value A 34 N* 50
By Order Of Section
53 Name A 35 N* 51
54 Address 1 A 35 N 52
55 Address 2 A 35 N 53
56 Address 3 A 32 N 54
58 Name A 35 56
Ordering Party Section
59 Address 1 A 35 57
60 Address 2 A 35 58
61 City A 32 59
62 Country A 2 60
63 Account A 34 61
Debit Party Section
64 Name A 35 62
65 Address 1 A 35 63
66 Address 2 A 35 64
52
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
67 City A 32 65
Section (cont.)
Debit Party
68 Country A 2 66
71 Name A 35 69
72 Address 1 A 35 70
73 Address 2 A 35 71
74 City A 32 72
75 Country A 2 73
76 Reference Sent A 16 N 74
with Payment
77 Internal A 16 N 75
Reference
Transaction Details Section
78 On Behalf Of A 30 N* 76
80 Detail 1 A 35/70 N 77
81 Detail 2 A 35/70 N 78
82 Detail 3 A 35/70 N 79
83 Detail 4 A 35/70 N 80
53
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
84 Detail 5 A 70 N 81
85 Detail 6 A 70 N 82
Transaction Details Section (cont.)
86 Detail 7 A 70 N 83
87 Detail 8 A 70 N 84
88 Detail 9 A 70 N 85
89 Detail 10 A 70 N 86
90 Detail 11 A 70 N 87
91 Detail 12 A 70 N 88
Regulatory Reporting Section
92 Code A 8 N 89
93 Country A 2 N* 90
94 Instruction 1 A 21/33 N 91
95 Instruction 2 A 33 N 92
96 Instruction 3 A 33 N 93
Bank to
Section
97 Instruction A 4 N 94
Bank
Code 1
98 Instruction Text A 30 N 95
1
99 Instruction A 4 N 96
Code 2
101 Instruction A 4 N 98
Code 3
54
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
103 Sender to A 8 N* 100
Receiver Code
1
Receiver Code
3
55
Section Field Field Name Type Length Mandatory Description Record Format
No Field No. for
Free-form
Transactions
114 Sender to A 23-30 N 111
Receiver Line 6
from US Accounts)
• BEN = Beneficiary
• OUR = Remitter
118 Delivery Method A 3 N* Applicable for Asia branch 115
draft/check initiations only;
otherwise, field is unused.
Refer to Appendix A: Delivery
Methods.
119 Additional A N* Key value pairs provide 116
Details additional information fields
specific to the transaction.
Format is
KEY=VALUE|KEY=VALUE
(Use a pipe delimiter “|” to
separate each pair.)
Refer to Appendix A: Additional
Details – Key Codes for the key
names and description of the
values.
120 Enhanced N 5 N* Field is applicable to Enhanced
Template Templates created on US
branch accounts. When
populated, the template will be
created with this line number if
it is available (not in use). If the
field is left blank, a number will
automatically be generated and
assigned to the template.
121 Beneficiary A 60 N Beneficiary Email address; 118
Beneficiary
56
APPENDIX A
Clearing Codes
The following clearing codes are available when originating transactions are from specific Asia branches.
Delivery Methods
These codes apply to Asia checks. Note: Refer to the Online portal for available values by branch.
57
Instruction Codes
2. Additional instruction codes are available for some non-JPM branch messages.
Code Description
CMSW Cash management instruction, requesting to sweep the account of the
ordering customer.
CMTO Cash management instruction, requesting to top the account of the ordering
customer above a certain floor amount. The floor amount, if not pre-agreed by
the parties involved, may be specified after the code.
CMZB Cash management instruction, requesting to zero balance the account of the
ordering customer.
EQUI Transaction contains an instruction requesting to pay the beneficiary
customer an amount in one currency, equivalent to an instructed amount in a
different currency.
NETS Transaction should be settled via a net settlement system, if available.
OTHR Bilaterally agreed codes/information; the actual bilateral code/information
needs to be specified in additional information.
RTGS Transaction should be settled via a real-time gross settlement system, if
available.
URGP Time-sensitive transaction that should be executed in an expeditious manner.
58
Regulatory Reporting Codes
Below are regulatory reporting codes used for wires and book transfers
Code Description
BENEFRES Residence of beneficiary customer
NONRES Non-resident beneficiary
ORDERRES Residence of ordering customer
Note: This is a standard list of codes only. Other code words also can be used as advised by J.P. Morgan
or the beneficiary.
59
Code Description Wire Book Check/Draft
TELE PLEASE ADVISE THE ACCOUNT WITH x except US x except NY
INSTITUTION BY THE MOST EFFICIENT
MEANS OF TELECOMMUNICATION
TELEBEN PLEASE ADVISE THE x except US x except NY
BENEFICIARY/CLAIMANT BY THE MOST
EFFICIENT MEANS OF
TELECOMMUNICATION
TELEIBK PLEASE ADVISE THE INTERMEDIARY BY THE x except US x except NY
MOST EFFICIENT MEANS OF
TELECOMMUNICATION.
TSU TRADE SERVICES UTILITY TRANSACTION. x except US x except NY
60
Additional Details - Key Codes
Below are the key codes for the Additional Details fields for transactions. Not all additional detail fields
apply to all transaction methods. Please refer to the Description/Usage column for methods that apply
(usually when paying into specific countries).
61
Key Codes (not case sensitive) Description/Usage
62
Key Codes (not case sensitive) Description/Usage
63
Key Codes (not case sensitive) Description/Usage
64
Description/Usage
Key Codes (not case sensitive)
TypeofBeneficiary Provide for wire payments less than 500,000,000
IDR, when paying into Indonesia:
Expected values - 1 , 2 or 3
1 for Individual
2 for Corporate
3 for Goverment
BeneficiaryRelationship This is the Beneficiary Relationship with the Ordering
Party for non-IDR wire transactions when paying out
from or into Indonesia, including the below single
character code word (which is case sensitive) for
respective options:
G for Group
P for Shareholder
T for Subsidiary
N for Not Related
CategoryBeneficiary This is the Category of Beneficiary for the non-IDR
wire transactions paying out from Indonesia, including
the below two character code words (which are case
sensitive) for respective options:
A0 for Individual
B0 for Government
C1 for Banks – Reporting Bank
C2 for Banks – Branch/Head Office Abroad
C9 for Banks – Other
D0 for Non-Bank Financial Institutions
E0 for Company
Z9 for Others
65
Key Codes (not case sensitive) Description/Usage
66
APPENDIX B: BANK AND ACCOUNT ID TYPE CODES
Use the following ID type codes to specify the type of identifier (such as a local bank code) provided
within the Party ID Type (i.e., Beneficiary ID, Beneficiary Bank ID, Intermediary ID or Debit Bank ID) for
the various transaction methods (wires, book transfers, account transfers, drafts/checks, drawdowns and
receipts). When there is no identifier, you can leave the ID type field blank.
Note: If an ID type is not provided in the import record, then the import validation will attempt to set it to
the default. This may cause an error when multiple options are available. Providing an ID type is
recommended to ensure optimum performance.
ID Type Description
ACCT Account number
AUBSB Australian Bank State Branch (BSB) Code
CACPA Canadian Routing Number
CBU_CODE Argentina CBU (Clave Bancaria Uniforme)
CHIPSID CHIPS Universal IDentifier
CHK_ACCT J. P. Morgan Mexico Checking Account number
CHSIC Swiss Bank Code(SIA)
CLBE_CODE Mexico CLABE (Clave Bancaria Estandarizada)
CNAPS China Bank Code(CNAPS)
DEP_ACCT J. P. Morgan Mexico Deposit Account number
DR_CARD Mexico - Debit Card
GBDSC United Kingdom Sort Code
HKNCC Hong Kong Bank Code
IBAN IBAN
INFSC Indian Financial System Code
JPMACC J. P. Morgan account used for book transfers debiting U.S. accounts
JPMC_IBAN Indicates a J. P. Morgan IBAN account type
JPZGN Japan Bank Code
LOCAL_CODE Local Clearing Code
MSKD_BENE Masked Beneficiary Tax (South Africa)
MSKD_BENE_UTILITY Masked Beneficiary Utility (South Africa)
NZNCC New Zealand Clearing Code
RUCBC Russian Central Bank Identification Code
SPEI_CODE Mexican SPEI Code
SWIFT SWIFT BIC
SWIFT_PARTY_CODE Used when ID is RT. Applicable to Asia branches
TWNCC Taiwan Code
USABA United States FED ABA
USPID CHIPS Participant Number
VN_CODE Vietnam Bank Code
VOSTRO_CD Vostro
ZANCC South African Clearing Code
67
APPENDIX C: BRANCH CODES
The following grid provides SWIFT BIC codes for J.P. Morgan branches.
Branch Name SWIFT BIC
Banco J.P. Morgan S.A., Institucion de Banca Multiple, J.P. Morgan Grupo Financiero CHASMXMX
BANCO JPMORGAN S.A. BRASIL CHASBRSP
J.P. Morgan AG CHASDEFX
J.P. Morgan Chase Bank Berhad CHASMYKX
J.P. MORGAN BANK LUXEMBOURG S.A., DUBLIN BRANCH CHASIE4L
JPMORGAN BANK INTERNATIONAL MOSCOW CHASRUMX
JPMorgan Chase Bank (China) Company Limited - Beijing CHASCN22
JPMorgan Chase Bank (China) Company Limited - Chengdu CHASCNBC
JPMorgan Chase Bank (China) Company Limited - Guangzhou CHASCN2G
JPMorgan Chase Bank (China) Company Limited - Harbin CHASCNBH
JPMorgan Chase Bank (China) Company Limited - Shanghai CHASCNSH
JPMorgan Chase Bank (China) Company Limited - Shenzhen CHASCNBZ
JPMorgan Chase Bank (China) Company Limited - Suzhou CHASCNBS
JPMorgan Chase Bank (China) Company Limited - Tianjin CHASCNBX
JPMorgan Chase Bank N.A., Sucursal en Espana CHASESM3
JPMORGAN CHASE BANK NA SUCURSAL B A CHASARBATSS
JPMorgan Chase Bank, N.A. - Amsterdam CHASNL2X
JPMorgan Chase Bank, N.A. - Bangkok CHASTHBX
JPMorgan Chase Bank, N.A. - Brussels CHASBEBX
JPMorgan Chase Bank, N.A. - Ho Chi Minh City CHASVNVX
JPMorgan Chase Bank, N.A. - Hong Kong CHASHKHH
JPMorgan Chase Bank, N.A. - Jakarta CHASIDJX
JPMorgan Chase Bank, N.A. - Johannesburg MGTCZAJJ
JPMorgan Chase Bank, N.A. - Labuan CHASMY2A
JPMorgan Chase Bank, N.A. - London CHASGB2L
JPMorgan Chase Bank, N.A. - Manila CHASPHMM
JPMorgan Chase Bank, N.A. - Milan CHASITMX
JPMorgan Chase Bank, N.A. - Mumbai CHASINBX
JPMorgan Chase Bank, N.A. - New York 021000021
JPMorgan Chase Bank, N.A. - New Zealand CHASNZ2A
JPMorgan Chase Bank, N.A. - Paris CHASFRPP
JPMorgan Chase Bank, N.A. - Seoul CHASKRSX
JPMorgan Chase Bank, N.A. - Singapore CHASSGSG
JPMorgan Chase Bank, N.A. - Sydney CHASAU2X
JPMorgan Chase Bank, N.A. - Taipei CHASTWTX
JPMorgan Chase Bank, N.A. - Tokyo CHASJPJT
JPMorgan Chase Bank, N.A. - Toronto CHASCATT
68
Branch Name SWIFT BIC
JPMorgan Chase Bank, N.A. - Zurich CHASCHGX
JPMORGAN CHASE BANK, N.A. RIYADH CHASSARI
JPMORGAN CHASE BANK, NA NEW YORK CHASCNY2XXX
JPMORGAN EUROPE LIMITED CHASGB22
JPMorgan Europe Limited Oslo CHASNOKK
JPMORGAN SECURITIES (FAR EAST) LTD CHASKRSE
69
APPENDIX D: WIRES/BOOK TRANSFERS – REGIONAL-
SPECIFIC LAYOUTS
This section outlines regional specific layouts for free-form Wires and Book Transfers initiated from the
U.S. and LATAM–Brazil and Mexico.
This layout is for same-currency Wires initiated from a U.S. account in USD being paid to the beneficiary
in USD.
U.S. Book Transfers require a U.S. J.P. Morgan Account (ID Type: JPMACC) as the first credit party (the
Intermediary if an Intermediary is provided; the Beneficiary Bank if only a Beneficiary and Beneficiary
Bank are provided; or the Beneficiary, if no other parties are provided). It is not valid to provide a U.S.
J.P.Morgan Chase Bank ID (e.g., FED ABA: 021000021; CHIPS ABA: 0002 or SWIFT ID: CHASUS33) in
the Beneficiary Bank or Intermediary Bank sections for U.S. Book Transfers.
For Wires, if a U.S. J.P. Morgan Chase Bank ID (e.g., FED ABA: 021000021, CHIPS ABA: 0002 or
SWIFT ID: CHASUS33) is provided in the Beneficiary Bank or Intermediary Bank sections for U.S. Book
Transfers, the transaction is subject to a repair.
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
1 Input Type A 2 To Indicate import of a Y P
free-form transaction,
Information
Record
transaction from a
template, or a template.
Enter P to indicate a free-
form transaction.
2 Method A 5/6 Must be one of the Y WIRES
Transaction Information Section
following:
WIRES
BOOKTX
3 Debit A 9 ABA Identifier: Identifies Y 021000021
Account the branch of the account
Bank ID to be debited for a
transaction.
4 Account A 35 This is the account to be Y 9BB654321
Number debited for a transaction; it
is optionally zero-padded.
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
5 Bank to Bank B 1 Used to indicate the N N
Transfer transaction is between
financial institutions.
Default is N.
Transaction Information Section (cont.)
Possible Values :
N -Non Financial
Institution (Customer
Transfer)
Y - Create bank-to-bank
transaction (for Financial
Institutions only).
6 Currency A 3 Currency of transaction Y USD
amount. Must be USD.
7 Payment N 20,3 Use a period to indicate a Y 50000.00
Amount decimal point.
Decimal places are not
mandatory.
12 leave blank.
value date.
Date format =
YYYYMMDD.
If not populated, defaults
to the first available
business day.
71
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
14 ID Type A A code to identify the type N* Must be ACCT
of the value supplied in provided if
the Beneficiary ID Value field 15 is
field (15). populated.
Available values are:
ACCT – Account Number
IBAN – IBAN*
JPMACC -JPM U.S.
Account (Book transfers
only)
CHIPSID - CHIPS
Universal IDentifier
SWIFT – SWIFT ID
USABA - United States
FED ABA
Beneficiary Section
NONE – No ID (when
providing only a name and
address)
USPID - CHIPS
Participant Number (Bank
to Bank Transfers only)
Recommended value is
ACCT or IBAN for wires or
JPMACC for book
transfers
*IBAN is mandatory when
Beneficiary Bank country
(field 30) is LB (Lebanon)
or JO (Jordan).
15 ID Value A 34 This is the Beneficiary N* Mandatory 9BB6543210
identifier, typically the when
beneficiary’s account Beneficiary ID
number. Type (field 14)
is other than
NONE.
16 Name A 35 Full name of the Y ABC Company
beneficiary; free-format
text.
72
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
17 Address 1 A 35 Beneficiary street N* Beneficiary
address line 1; free- address is
format text. recommended.
Mandatory when
Beneficiary Bank
Country (field
30) is:
AU
(AUSTRALIA)
CA (CANADA)
CC
Beneficiary Section (cont.)
(COCOS
(KEELING)
ISLANDS )
CX
(CHRISTMAS
ISLAND )
HM
(HEARD
ISLAND AND
MCDONALD
ISLANDS)
KI
(KIRIBATI)
NF
(NORFOLK
ISLAND)
NR (NAURU)
TV (TUVALU)
73
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
18 Address 2 A 35 Beneficiary street address N* Mandatory
line 2; free-format text. when
Beneficiary
Bank Country
(field 30) is:
AU
(AUSTRALIA)
CA (CANADA)
CC
(COCOS
(KEELING)
ISLANDS )
CX
Beneficiary Section (cont.)
(CHRISTMAS
ISLAND )
HM
(HEARD
ISLAND AND
MCDONALD
ISLANDS)
KI
(KIRIBATI)
NF
(NORFOLK
ISLAND)
NR (NAURU)
TV (TUVALU)
19 Address 3 A 32 Provide city, state, postal N* New York
code (free-format text. NY 10004
20 N/A N/A Unused field; please leave N/A
blank.
21 Country A 2 Beneficiary country ISO Y US
3166 country code
22 to N/A N/A Unused fields; please N/A
Unused
23 leave blank.
74
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
24 ID Type A 34 A code to identify the type N* Must be FED ABA
of value supplied in the provided if
Beneficiary Bank identifier field 25 is
field. Available values are: populated.
ACCT – Account Number
JPMACC – JPM U.S.
Account (Book Transfers
only)
CHIPSID – CHIPS
Universal IDentifier
SWIFT – SWIFT ID
USABA – United States
FED ABA
NONE – No ID (when
Beneficiary Bank Section
75
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
30 Country A 2 Beneficiary Bank country Y US
Beneficiary Bank
Section (cont.)
76
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
41 ID Value A 34 This is an intermediary N* Must be 0001
bank identifier, which is provided if
usually a SWIFT BIC, or field 40 is
local clearing code, such populated
as FED ABA, CHIPS
Participant Number or
JPMACC -JPM U.S.
Account ( for Book
Intermediary Bank Section (cont.)
Transfers only)
42 Name A 35 Intermediary bank name; N* Mandatory ABC BANK
free-format text. when
Intermediary
information is
present.
43 Address 1 A 35 Intermediary bank street N 2 Broad
address; free-format text. Street
44 Address 2 A 35 Intermediary bank N
address; free-format text.
45 Address 3 A 32 Provide city, state, postal N Boston MA
code (zip code); free- 02144
format text.
46 Country A 2 Intermediary country ISO N* Mandatory US
3166 country code; when
usually US. Intermediary is
present
47 to N/ Unused; please leave N/A
Unused
48 blank.
77
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
50 ID Value A 34 By Order Of party N* Mandatory if
identifier (Account field 49 is
Number) populated.
51 Name A 35 By Order Of party full N* Mandatory if
name; free-format text. field 50 is
By Order Of Section (cont.)
populated.
52 Address 1 A 35 By Order of party street N* Mandatory if
address of the field 50 is
intermediary bank; free- populated.
format text.
53 Address 2 A 35 By Order Of party N
address; free-format text.
54 Address 3 A 32 City, state, postal code N* Mandatory if Hoboken NJ
(zip code) supplied as field 50 is 07891
free-format text. populated.
55 Country A 2 By Order Of party country Y US
ISO 3166 country code
56 to N/A N/A These fields are unused N/A
Unused
78
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
78 Detail 2 A 35 Free-format text. N JUNE
Transaction Details
SALARY
Section (cont.)
PAYMENT
79 Detail 3 A 35 Free-format text. N
80 Detail 4 A 35 Free-format text. N
Must be blank when field
76 is populated.
81 to N/A N/A These fields are unused N/A
88 for wires/book transfers,
but must be present with
Unused
no value.
79
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
104 Sender to A 8 Include code as advised N
Receiver by J.P. Morgan or your
Code 3 beneficiary.
Refer to Appendix A:
Sender to Receiver
Codes.
105 Sender to A 23-30 Free-form Instruction text N
Receiver as advised by J.P.Morgan
Line 3 or your beneficiary.
80
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
115 to N/A N/A Unused fields; please N/A
Unused
81
Wires/Book Transfers Initiated From LATAM – Brazil
from a template, or a
template.
Enter P to indicate a free-form
transaction.
82
Section Field Field Name Type Length Description Mandatory Conditional Example
Name No. Logic
Either field 7
(Transaction
Amount) or
field 8
(Equivalent
Amount) is
mandatory.
Whichever
field is
provided,
the other
field must be
blank.
83
Section Field Field Name Type Length Description Mandatory Conditional Example
Name No. Logic
23 leave blank.
84
Section Field Field Name Type Length Description Mandatory Conditional Example
Name No. Logic
85
Section Field Field Name Type Length Description Mandatory Conditional Example
Name No. Logic
with no value.
86
Section Field Field Name Type Length Description Mandatory Conditional Example
Name No. Logic
87
Section Field Field Name Type Length Description Mandatory Conditional Example
Name No. Logic
blank.
(cont.)
blank.
• SHA = Shared
section
• BEN = Beneficiary
• OUR = Remitter
88
Wires/Book Transfers Initiated From LATAM – Mexico
template, or a template.
Record
89
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
field is
populated,
the other
field must
be blank.
12 blank.
value date.
Date format =
YYYYMMDD.
If not populated, defaults
to the first available
business day.
90
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
CLABE is 8 digits
16 digits)
Vostro is up to 34 digits
16 Name A 35 Beneficiary name; free- Y BENEFICIARY
format text. NAME
91
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
name is
usually
required.
92
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
32 Supple- A 34 A supplementary N
mentary ID beneficiary bank identifier.
Value
May be supplied if an
additional code is
available, but it must not
be the same as the value
in field 25.
39 blank.
financial
institution
paying on
behalf of a
third party.
93
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
94
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
field 89.
95
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
96
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
97
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
98
Section Field Field Name Type Length Description Mandatory Conditional Example
No. Logic
99
APPENDIX E: COPY ACTIVE TEMPLATES FROM ONE
J.P. MORGAN ACCESS® CLIENT PROFILE TO
ANOTHER
The Import File feature can be used to copy existing wire templates from one Access client profile to
another.
Important:
The client profile to which templates are to be added must be configured so that Allow
Template Import is enabled.
Users need to be entitled to Templates & Enhanced Templates - Import and Modify.
Contact your Security Administrator for help.
Notes:
If all the accounts in the CSV file exist under another client profile and that profile does not
have any templates, the file can import as is under the target client profile.
If the profile to which the templates will be imported already has templates, change the
Account Numbers/Template Names manually in the CSV file before it is imported under the
target client profile.
Please refer to Access Support Help for Transactions for information on testing and importing files.
100