U.S.

Bank
CustomerCreditTransferInitiationV03
pain.001.001.03
Date Last Modified: July 16, 2019
Version 1.0

XML Declaration:
Specify standard XML version declaration and the <Document> tag with an appropriate namespace before. Example:
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This declaration is made before the Message Root tag at the start of the ISO message.

Statuses used in this document:

R = Required
O = Optional
C = Conditional

COMMON IMPLEMENTATION GUIDELINES

~ Columns Y - AB specify the use status for a specific payment type.

~ Any data populated in a schema-defined optional field that is not required will be ignored and will not stop processing
of the payment. This rule includes elements that are designated "Not Used" by the bank.

~ If field is used by the bank processing, one of the above usage statuses will be specified (O, R
or C). Otherwise, when the field is not used, no status is noted.

~ Where individual clients do not maintain Required or Conditional data elements in their systems, they should consult
with U.S. Bank on the minimum of data elements required for that type of transaction. This could result in the need to
add those data elements into the client's systems.

~ Clients should consult with their Beneficiary Banks on the regulatory requirement rules defined by the Central Bank in
those countries and provide that information in the required format.

~ Any of the data tags included in this guide will be accepted by U.S. Bank. The bank will either use the tag for
processing or ignore it.

INTRODUCTION
This document details the usage of ISO 20022 pain.001.001.03 (Customer Credit Transfer Initiation) by U.S. Bank and
provides guidance on how information is to be structured for exchange between customers and U.S. Bank. This
implementation complies with standard content and use, as set under ISO 20022 message definitions. While only
applicable information is detailed, full documentation can be found per links below. Message elements not represented in
this document but meeting standard will be ignored.

~ ISO 20022 Message Definition Report (MDR), Message Usage Guideline (MUG) and XML schema
(pain.001.001.02.xsd)
https://www.iso20022.org/message_archive.page#PaymentsInitiation3
~ Payments External Code List which provides the standard code values for payment message elements

https://www.iso20022.org/external_code_list.page

MESSAGE STRUCTURE
The main blocks of the Customer Credit Transfer Initiation message as defined by the schema are as follows:

1. Group Header <GrpHdr> (1..1). This block is mandatory and should be present only once in the file. It contains a set
of general elements that are common to the entire message such as message identification date and time, number of
transactions in the message, etc.).

2. Payment Information <PmtInf> (1..n). This block is mandatory and can repeat. It contains a set of elements related
to the creditor side of the message. It consists of payment identification, payment method, debtor details (name,
account number, bank), etc.

3. Transaction Information <CdtTrfTxInf> (1..n). This block is a part of the Payment Information block and is mandatory
and repetitive. It contains a set of elements related to the creditor side of the transaction. It indicates payment and
transaction identification, amount, creditor information, etc.

PERMITTED CHARACTERS
ISO 20022 XML messages should be encoded using UTF-8 as indicated on first line of file.
<?xml version="1.0" encoding="UTF-8"?>
The supported characters for this implementation:
Alpha (A - Z, a - z, and spaces)
Numeric (0 - 9)
Special Characters: See Appendix A tab

Reserved XML characters must be represented by entity references (ex. < = &lt; or &#60; in XML file)

VALIDATION OF MESSAGES
The incoming pain.001 message will be validated against the schema pain.001.001.03.xsd.
~ If the message fails schema validation, the entire message/file will be rejected.
~ If the message fails duplicate checking, the entire message/file will be rejected.
~ If the file header field(s) fail validation rule, the entire message/file will be rejected.
~ If the PaymentInformation group field(s) fail validation rule, all transactions in the batch will be rejected.
~ At the transaction level, single payments will be validated against any additional rules set forth
and only the transaction in error will be rejected.
~ A 1st Level CustomerPaymentStatusReport (pain.002.001.03) will be sent file once the file
passes or fails technical validation.
~ A 2nd Level CustomerPaymentStatusReport (pain.002.001.03) will be sent once the file
reaches the backend system.
MLSchema-instance">

ill not stop processing

, they should consult

d result in the need to

by the Central Bank in

se the tag for

n) by U.S. Bank and

S. Bank. This
ns. While only
nts not represented in

ema
 ements

as follows:

e file. It contains a set

e and time, number of

t of elements related
or details (name,

ock and is mandatory

cates payment and

ML file)

ejected.
Level ISO Or Message Item 1 2 3 4 5 6 7 8 9 10 11 12 Full Path Type Min Max Min Max File Level Field Description Repetitive Semi-
Index Tag Len Leng Occur Occurs Rejection Wire (All Repetitive
No. Tree gth th s types) Wire (all
types)

XML_HEADER <?xml version="1.0" encoding="UTF-8"?>

1 Document Document 1 1 <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

2 Message Root CstmrCdtTrfInitn Document/CstmrCdtTrfI 1 1

3 1.0 GroupHeader GrpHdr Document/CstmrCdtTrfI 1 1
4 1.1 MessageIdentification MsgId Document/CstmrCdtTrfIText 1 35 1 1 Y Message Control Number. This number should be unique for each file due to R R
a Duplicate Checking requirement.15 characters maximum length

4 1.2 CreationDateTime CreDtTm Document/CstmrCdtTrfIDateTime 1 1 Use ISO format (yyyy-mm-ddThh:mm:ss or yyyy-mm-ddThh:mm:ssZ or yyyy- R R
mm-ddThh:mm:ss+HH:MM)
4 1.6 NumberOfTransactions NbOfTxs Document/CstmrCdtTrfIText 1 1 Y Specify the total number of transactions in the entire message. Element will be R R
validated by the bank. If validation fails, the entire message will be rejected
and the reason will be reflected in your pain.002 Payment Status Report. This
value is used for duplicate checking.

4 1.7 ControlSum CtrlSum Document/CstmrCdtTrfIQuantity 0 1 Y While this field is optional, best practice is to provide this element. If populated, O O
this field will be validated and the entire message will be rejected if the value
doesn’t match calculated total amount. This value is used for duplicate
checking if provided.

4 1.8 InitiatingParty InitgPty Document/CstmrCdtTrfIn

+ 1 1
5 9.1.0 Name Nm Document/CstmrCdtTrfIText 1 140 0 1 Y Name of the Initiating party R R
5 9.1.12 Identification Id Document/CstmrCdtTrfIn 0 1 Unique and unambiguous way of identifying an organization or an individual
person.
6 9.1.13 OrganisationIdentification OrgId Document/CstmrCdtTrfIn 1 1
7 9.1.14 BICOrBEI BICOrBEI Document/CstmrCdtTrfIn
Identifier 0 1 Y The Initiating Party's BIC. C C
Either this field or InitgPty/Id/OrgId/Othr/Id must be provided
7 9.1.15 Other Othr Document/CstmrCdtTrfIn 0 *
8 9.1.16 Identification Id Document/CstmrCdtTrfIn
Text 1 35 1 1 Y The Initiating Party's Customer Identification as assigned by U.S. Bank. This C C
field will be used to identify a customer sending the payment file.
Either this field or InitgPty/Id/OrgId/BICOrBEI must be provided

8 9.1.17 SchemeName SchmeNm Document/CstmrCdtTrfI 0 1

9 9.1.18 Code Cd Document/CstmrCdtTrfICode 1 4 1 1 Name of the identification scheme, in a coded form as published in an external O O
list. When using InitgPty/Id/OrgId/Othr/Id then it's recommended to use the
code word "CUST" here if you are a corporation.

3 2.0 PaymentInformation PmtInf Document/CstmrCdtTrfI 1 * PaymentInformation - Batch Level. Transactions must be grouped by
Company ID (CIF-ID), Payment Type, Debtor account and currency, execution
date.
4 2.1 PaymentInformationIdentification PmtInfId Document/CstmrCdtTrfIn
Text 1 35 1 1 Batch Reference Number. This number should be unique for each batch within R R
the file. The value is not validated except for the length.15 characters max
length is allowed.
4 2.2 PaymentMethod PmtMtd Document/CstmrCdtTrfICode 1 1 Payment Method. Always value "TRF" for ACH and WIRE. R R
For Check populate as "CHK" TRF TRF
4 2.4 NumberOfTransactions NbOfTxs Document/CstmrCdtTrfIText 0 1 Number of Total Transactions in this Message. This value is not validated if O O
provided.
4 2.5 ControlSum CtrlSum Document/CstmrCdtTrfIQuantity 0 1 Control Sum (Hash Total) of all Transactions in this Message. This value is not O O
validated if provided.
4 2.6 PaymentTypeInformation PmtTpInf Document/CstmrCdtTrfI 0 1
5 2.8 ServiceLevel SvcLvl Document/CstmrCdtTrfI 0 1
6 2.9 {Or Code Cd Document/CstmrCdtTrfICode 1 4 1 1 Service Code - Payment Information Level. It is required to specify Service R R
Level Code on the PmtInf level. All transactions in the same PmtTpInf batch URGP URGP
should be of the same payment type (ACH, WIRE or Check) in case multiple
payment types are sent in the same file.

4 2.17 RequestedExecutionDate ReqdExctnDt Document/CstmrCdtTrfIDateTime 1 1 Requested Execution Date of the Payment Instruction (e.g. Value Date) in R R
yyyy-mm-dd format. Must be populated on the Payment Information Level.
Domestic wires can be value dated out up to 30 calendar days. If a value date
lands on a no business day, the wire will be sent on the next business day.
International transactions must always be dated current day.

4 2.19 Debtor Dbtr Document/CstmrCdtTrfIn

+ 1 1
5 9.1.0 Name Nm Document/CstmrCdtTrfIText 1 140 0 1 Debtor Name. Name (First and Last) of the holder of the account to be debited.

5 9.1.1 PostalAddress PstlAdr Document/CstmrCdtTrfIn 0 1

6 9.1.10 Country Ctry Document/CstmrCdtTrfIn
Code 0 1 Country of the Debtor. Not used for Repetitive and semi-Repetitive Wires,
mandatory for non-repetitive Wires
6 9.1.11 AddressLine AdrLine Document/CstmrCdtTrfIn
Text 1 70 0 7 Only unstructured, Free-form address of the Debtor should be used. Up to 3
lines, 35 characters each can be populated. Although it is required to provide
Ctry structured field, it won't be mapped to the address and it is expected that
country is included in the AdrLine 1-3.
Not used for Repetitive and semi-Repetitive wires

5 9.1.12 Identification Id Document/CstmrCdtTrfIn 0 1

6 9.1.13 {Or OrganisationIdentification OrgId Document/CstmrCdtTrfIn 1 1
7 9.1.15 Other Othr Document/CstmrCdtTrfIn 0 *
8 9.1.16 Identification Id Document/CstmrCdtTrfIn
Text 1 35 1 1 Enter the CIF-ID assigned by the U.S. Bank implementation team here. R R
Maximum length of the CIF-ID is 20 characters. Note that CIF-ID should be a
factor in your logical batching criteria. There could be multiple CIF-ID assigned
to your company, one per Debtor Account Number. CIF-ID must be in the first
occurrence of PmtInf/Dbtr/Id/OrgId/Othr if SchmeNm/Prtry is not populated as
"USBCIFID"

8 9.1.17 SchemeName SchmeNm Document/CstmrCdtTrfI 0 1

9 9.1.19 Or}} Proprietary Prtry Document/CstmrCdtTrfIn
Text 1 35 1 1 It is recommended to enter "USBCIFID" in the same occurrence of OrgId/Othr O O
where U.S. Bank CIF-ID is populated for Wires

8 9.1.20 Issuer Issr Document/CstmrCdtTrfIn

Text 1 35 0 1 5-digit Security Code (PIN) as setup with U.S. Bank. This code will be used by R R
U.S. Bank for the wire validation. If code is not valid, all wires under this
PaymentInformation group will be rejected.

4 2.20 DebtorAccount DbtrAcct Document/CstmrCdtTrfI+ 1 1

5 1.1.0 Identification Id Document/CstmrCdtTrfIn 1 1
6 1.1.2 Or} Other Othr Document/CstmrCdtTrfIn 1 1
7 1.1.3 Identification Id Document/CstmrCdtTrfIn
Text 1 34 1 1 Debtor's Account (account Number to be debited). R R
Not used for repetitive wires, but mandatory per ISO schema.
4 2.21 DebtorAgent DbtrAgt Document/CstmrCdtTrfI+ 1 1
5 6.1.0 FinancialInstitutionIdentification FinInstnId Document/CstmrCdtTrfIn 1 1
6 6.1.1 BIC BIC Document/CstmrCdtTrfIn
Identifier 0 1 SWIFT BIC associated to the U.S. Bank Branch holding your Debtor Account, O O
as provided by your Implementation Team.
6 6.1.2 ClearingSystemMemberIdentification ClrSysMmbId Document/CstmrCdtTrfI 0 1
7 6.1.6 MemberIdentification MmbId Document/CstmrCdtTrfIText 1 35 1 1 The non-SWIFT Bank Identifier associated to the U.S. Bank Branch holding O O
your Debtor Account, as provided by your Implementation Team.

6 6.1.8 PostalAddress PstlAdr Document/CstmrCdtTrfIn 0 1

7 6.1.17 Country Ctry Document/CstmrCdtTrfIn
Code 0 1 ISO Country Code of the Debtor Agent. Mandatory for Wires R R
4 2.24 ChargeBearer ChrgBr Document/CstmrCdtTrfICode 0 1 DEBT - Debtor pays all charges. (Equivalent of SWIFT "OUR").
SHAR - Debtor pays U.S. Bank fees; Creditor all other fees. (Equivalent of
SWIFT "SHA").
CRED - Creditor pays all fees. (Equivalent of SWIFT "BEN").
It is recommended to use ChrgBr on the transaction level. If no transaction
level ChrgBr populated, this field will be used. If not populated, defaulted to
"SHAR".

4 2.27 CreditTransferTransactionInformation CdtTrfTxInf Document/CstmrCdtTrfIn 1 * Transaction Level. This group repeats for each transaction in the batch.

5 2.28 PaymentIdentification PmtId Document/CstmrCdtTrfIn 1 1

6 2.29 InstructionIdentification InstrId Document/CstmrCdtTrfIn
Text 1 35 0 1 This value will not be returned in the pain.002 response coming from the O O
payment channel.
6 2.30 EndToEndIdentification EndToEndId Document/CstmrCdtTrfIText 1 35 1 1 Unique identifier for this payment from the initiating system. Value is returned R R
in pain.002 acknowledgments.
The value is not validated except for the length.15 characters max length is
allowed.

5 2.31 PaymentTypeInformation PmtTpInf Document/CstmrCdtTrfIn 0 1

6 2.36 LocalInstrument LclInstrm Document/CstmrCdtTrfIn 0 1
7 2.37 {Or Code Cd Document/CstmrCdtTrfIn
Code 1 35 1 1 If this field is not populated, U.S. Bank will default the payment to CTR O O
(Customer Transfer).
Valid values:
CTR - Customer Transfer
BTR - Bank Transfer
IRS - Internal Revenue Service (only supported for a repetitive wire). This
value must be provided for IRS. Note: Either the Cd or Prtry must be populated
for IRS wire.

7 2.38 Or} Proprietary Prtry Document/CstmrCdtTrfIn

Text 1 35 1 1 C C
IRS - Internal Revenue Service (only supported for a repetitive wire). This
value must be provided for IRS. Note: Either the Cd or Prtry must be populated
for IRS wire.
5 2.42 Amount Amt Document/CstmrCdtTrfIn 1 1
6 2.43 {Or InstructedAmount InstdAmt Document/CstmrCdtTrfIn
Amount 1 1 Amount of money to be moved between debtor and creditor, before deduction R R
of charges, expressed in the currency as ordered by the Debtor.
15 characters maximum, including a decimal point.

7 Ccy Document/CstmrCdtTrfIAttribute 1 1 CCY in which the receiver of payment will receive the amount R R
5 2.47 ExchangeRateInformation XchgRateInf Document/CstmrCdtTrfIn 0 1
6 2.48 ExchangeRate XchgRate Document/CstmrCdtTrfIRate 0 1 Only send exchange rate if the deal number is populated. If no deal number is
available, and this field is populated, the transaction will be rejected. If deal
number is available and Exchange Rate is not populated, the transaction will
also be rejected.
Rate should be provided in American terms. Provided rates multiplied by
payment amount will equal US dollar amount that will be debited from your
account.
Up to 6 decimal places may be specified.

6 2.50 ContractIdentification CtrctId Document/CstmrCdtTrfIn

Text 1 35 0 1 Provide a deal number if available for currency exchange. If there is no deal
number available, do not populate this field and XchgRate field. Market rate
will be used for currency exchange by U.S. Bank if no deal number is
available.
5 2.51 ChargeBearer ChrgBr Document/CstmrCdtTrfIn
Code 0 1 DEBT - Debtor pays all charges. (Equivalent of SWIFT "OUR").
SHAR - Debtor pays U.S. Bank fees; Creditor all other fees. (Equivalent of
SWIFT "SHA").
CRED - Creditor pays all fees. (Equivalent of SWIFT "BEN").
It is recommended to use ChrgBr on the transaction level. If no transaction
level ChrgBr populated, PmtInf/ChrgBr will be used. If not populated, defaulted
to "SHAR" by U.S. Bank.

5 2.71 IntermediaryAgent1 IntrmyAgt1 Document/CstmrCdtTrfIn

+ 0 1 Only one Intermediary Bank information is populated if available. When not
populated, U.S. Bank will designate the appropriate Intermediary Bank. If
Intermediary bank is populated, either BIC, Local Routing Code or Name and
Address must be populated.

6 6.1.0 FinancialInstitutionIdentification FinInstnId Document/CstmrCdtTrfIn 1 1

7 6.1.1 BIC BIC Document/CstmrCdtTrfIn
Identifier 0 1 Intermediary Bank BIC code
7 6.1.2 ClearingSystemMemberIdentification ClrSysMmbId Document/CstmrCdtTrfIn 0 1
8 6.1.3 ClearingSystemIdentification ClrSysId Document/CstmrCdtTrfIn 0 1
9 6.1.5 Or} Proprietary Prtry Document/CstmrCdtTrfIn
Text 1 35 1 1 If local routing code is populated, this field must be populated with one of the
following codes:
AT 5!n Austrian Bankleitzahl
AU 6!n Australian Bank State Branch (BSB) Code
BL 8!n German Bankleitzahl
CC 9!n Canadian Payments Association Payment Routing Number
CH 6!n CHIPS Universal Identifier
CP 4!n CHIPS Participant Identifier
ES 8..9n Spanish Domestic Interbanking Code
FW 9!n Fedwire Routing Number
GR 7!n HEBIC (Hellenic Bank Identification Code)
HK 3!n Bank Code of Hong Kong
IE 6!n Irish National Clearing Code (NSC)
IN 11!c Indian Financial System Code (IFSC)
IT 10!n Italian Domestic Identification Code
NZ 6!n New Zealand National Clearing Code
PT 8!n Portuguese National Clearing Code
RT Pay by Real Time Gross Settlement
RU 9!n Russian Central Bank Identification Code
SC 6!n UK Domestic Sort Code
SW 3..5n Swiss Clearing Code (BC code)
SW 6!n Swiss Clearing Code (SIC code)
ZA 6!n South African National Clearing Code

8 6.1.6 MemberIdentification MmbId Document/CstmrCdtTrfIText 1 35 1 1 Intermediary Bank Local Routing Code

7 6.1.7 Name Nm Document/CstmrCdtTrfIn
Text 1 140 0 1 Intermediary Bank Name
7 6.1.8 PostalAddress PstlAdr Document/CstmrCdtTrfIn 0 1
8 6.1.18 AddressLine AdrLine Document/CstmrCdtTrfIn
Text 1 70 0 7 Intermediary Bank Address must only be used in exceptional circumstances:
when the party cannot be identified by a financial institution BIC, when there is
a need to be able to specify a name and address, for example, due to
regulatory considerations or when there is a bilateral agreement between the
Sender and the Receiver permitting its use. If used, populate complete
address (including a country) in unstructured address lines 1-3. U.S. Bank will
use the first 35 characters on each line.

5 2.73 IntermediaryAgent2 IntrmyAgt2 Document/CstmrCdtTrfIn

+ 0 1 Second Intermediary Bank information is populated here if available. If Second
Intermediary Bank is populated, either BIC, Local Routing Code or Name and
Address must be populated.
6 6.1.0 FinancialInstitutionIdentification FinInstnId Document/CstmrCdtTrfIn 1 1
7 6.1.1 BIC BIC Document/CstmrCdtTrfIn
Identifier 0 1 Intermediary Bank BIC code
7 6.1.2 ClearingSystemMemberIdentification ClrSysMmbId Document/CstmrCdtTrfIn 0 1
8 6.1.3 ClearingSystemIdentification ClrSysId Document/CstmrCdtTrfIn 0 1
9 6.1.5 Or} Proprietary Prtry Document/CstmrCdtTrfIn
Text 1 35 1 1 If local routing code is populated, this field must be populated with one of the
following codes:
AT 5!n Austrian Bankleitzahl
AU 6!n Australian Bank State Branch (BSB) Code
BL 8!n German Bankleitzahl
CC 9!n Canadian Payments Association Payment Routing Number
CH 6!n CHIPS Universal Identifier
CP 4!n CHIPS Participant Identifier
ES 8..9n Spanish Domestic Interbanking Code
FW 9!n Fedwire Routing Number
GR 7!n HEBIC (Hellenic Bank Identification Code)
HK 3!n Bank Code of Hong Kong
IE 6!n Irish National Clearing Code (NSC)
IN 11!c Indian Financial System Code (IFSC)
IT 10!n Italian Domestic Identification Code
NZ 6!n New Zealand National Clearing Code
PT 8!n Portuguese National Clearing Code
RT Pay by Real Time Gross Settlement
RU 9!n Russian Central Bank Identification Code
SC 6!n UK Domestic Sort Code
SW 3..5n Swiss Clearing Code (BC code)
SW 6!n Swiss Clearing Code (SIC code)
ZA 6!n South African National Clearing Code

8 6.1.6 MemberIdentification MmbId Document/CstmrCdtTrfIText 1 35 1 1 Intermediary Bank Local Routing Code

7 6.1.7 Name Nm Document/CstmrCdtTrfIn
Text 1 140 0 1 Intermediary Bank Name
7 6.1.8 PostalAddress PstlAdr Document/CstmrCdtTrfIn 0 1
8 6.1.18 AddressLine AdrLine Document/CstmrCdtTrfIn
Text 1 70 0 7 Intermediary Bank Address must only be used in exceptional circumstances:
when the party cannot be identified by a financial institution BIC, when there is
a need to be able to specify a name and address, for example, due to
regulatory considerations or when there is a bilateral agreement between the
Sender and the Receiver permitting its use. If used, populate complete
address (including a country) in unstructured address lines 1-3. U.S. Bank will
use the first 35 characters on each line.

5 2.77 CreditorAgent CdtrAgt Document/CstmrCdtTrfIn

+ 0 1
6 6.1.0 FinancialInstitutionIdentification FinInstnId Document/CstmrCdtTrfIn 1 1
7 6.1.1 BIC BIC Document/CstmrCdtTrfIn
Identifier 0 1 SWIFT Bank Identifier associated to the bank/branch holding the Creditor
Account. Either BIC or local routing number must be populated.

7 6.1.2 ClearingSystemMemberIdentification ClrSysMmbId Document/CstmrCdtTrfIn 0 1

8 6.1.3 ClearingSystemIdentification ClrSysId Document/CstmrCdtTrfIn 0 1
9 6.1.4 {Or Code Cd Document/CstmrCdtTrfIn
Code 1 5 1 1 If US ABA number is provided in MmbId, either populate "USABA" in the
CdtrAgt/FinInstnId/ClrSysMmbId/ClrSysId/Cd field or populate "FW" in the
CdtrAgt/FinInstnId/ClrSysMmbId/ClrSysId/Prtry field. It is strongly
recommended to use ABA for non-repetitive FED wires.

9 6.1.5 Or} Proprietary Prtry Document/CstmrCdtTrfIn

Text 1 35 1 1 If MmbId is populated , Party Identifier may be used to indicate a national
clearing system code - see the list below:
AT 5!n Austrian Bankleitzahl
AU 6!n Australian Bank State Branch (BSB) Code
BL 8!n German Bankleitzahl
CC 9!n Canadian Payments Association Payment Routing Number
CH 6!n CHIPS Universal Identifier
CP 4!n CHIPS Participant Identifier
ES 8..9n Spanish Domestic Interbanking Code
FW 9!n Fedwire Routing Number
GR 7!n HEBIC (Hellenic Bank Identification Code)
HK 3!n Bank Code of Hong Kong
IE 6!n Irish National Clearing Code (NSC)
IN 11!c Indian Financial System Code (IFSC)
IT 10!n Italian Domestic Identification Code
NZ 6!n New Zealand National Clearing Code
PT 8!n Portuguese National Clearing Code
RT Pay by Real Time Gross Settlement
RU 9!n Russian Central Bank Identification Code
SC 6!n UK Domestic Sort Code
SW 3..5n Swiss Clearing Code (BC code)
SW 6!n Swiss Clearing Code (SIC code)
ZA 6!n South African National Clearing Code

8 6.1.6 MemberIdentification MmbId Document/CstmrCdtTrfIText 1 35 1 1 The non-SWIFT Bank Identifier associated to the bank/branch holding the
Creditor Account.
If US ABA number is populated either populate "USABA" in the
CdtrAgt/FinInstnId/ClrSysMmbId/ClrSysId/Cd field or populate "FW" in the
CdtrAgt/FinInstnId/ClrSysMmbId/ClrSysId/Prtry field.

7 6.1.7 Name Nm Document/CstmrCdtTrfIn

Text 1 140 0 1 The name of the Creditor Agent.
7 6.1.8 PostalAddress PstlAdr Document/CstmrCdtTrfIn 0 1
8 6.1.17 Country Ctry Document/CstmrCdtTrfIn
Code 0 1 ISO Country Code of the Creditor Agent
8 6.1.18 AddressLine AdrLine Document/CstmrCdtTrfIn
Text 1 70 0 7 Address must only be used in exceptional circumstances: when the party
cannot be identified by a financial institution BIC, when there is a need to be
able to specify a name and address, for example, due to regulatory
considerations or when there is a bilateral agreement between the Sender and
the Receiver permitting its use. Otherwise, do not populate.

5 2.79 Creditor Cdtr Document/CstmrCdtTrfIn

+ 0 1
6 9.1.0 Name Nm Document/CstmrCdtTrfIn
Text 1 140 0 1 Creditor Name. Name (First and Last) of the holder of the account to be
debited. U.S. Bank will use the first 35 characters

6 9.1.1 PostalAddress PstlAdr Document/CstmrCdtTrfIn 0 1 Unstructured address lines will be used for Wire.
7 9.1.11 AddressLine AdrLine Document/CstmrCdtTrfIn
Text 1 70 0 7 Free-form Street address of the Creditor. Unstructured address lines 1-3 will
be used for Fed Wire. U.S. Bank will use the first 35 characters on each line.
Only Unstructured address should be populated for Wires.

5 2.80 CreditorAccount CdtrAcct Document/CstmrCdtTrfIn

+ 0 1
6 1.1.0 Identification Id Document/CstmrCdtTrfIn 1 1
7 1.1.1 {Or IBAN IBAN Document/CstmrCdtTrfIn
Identifier 1 1 Creditor's IBAN
Either IBAN or Account Number must be present
7 1.1.2 Or} Other Othr Document/CstmrCdtTrfIn 1 1
8 1.1.3 Identification Id Document/CstmrCdtTrfIn
Text 1 34 1 1 Creditor's Account Number to be credited.
Either IBAN or Account Number must be present
5 2.82 InstructionForCreditorAgent InstrForCdtrAgt Document/CstmrCdtTrfIn 0 * Bank-To-Bank Information
Up to 6 occurrences of InstrForCdtrAgt can be used
6 2.84 InstructionInformation InstrInf Document/CstmrCdtTrfIni
Text 1 140 0 1 Up to 6 occurrences of InstrForCdtrAgt can be used, with each InstrInf line
maximum length of 35 characters.
Unless bilaterally agreed otherwise between the Sender and the Receiver, one
of the following codes must be used, placed between slashes ('/'):
ACC - Instructions following are for the account with institution.
INS - The instructing institution which instructed the Sender to execute the
transaction.
INT - Instructions following are for the intermediary institution.
REC - Instructions following are for the Receiver of the message.
Each item, for which a code exists, must start with that code and may be
completed with additional information.
Each code used must be populated between slashes and appear at the
beginning of a line. It may be followed by additional narrative text.
Narrative text relating to a preceding code, which is continued on the next
line(s), must start with a double slash '//', and, if used, must begin on a new
line. Narrative text should preferably be the last information in this field.
Use of this field, particularly with uncoded instructions, may cause delay,
because, in automated systems, the presence of this field will normally require
manual intervention.
It is strongly recommended to use the standard codes proposed above. In any
case, where bilateral agreements covering the use of codes in this field are in
effect, the code must conform to the structured format of this field.
Examples:
1) <InstrForCdtrAgt><InstrInf>/INS/ABNANL2A</InstrInf></InstrForCdtrAgt>
2) <InstrForCdtrAgt><InstrInf>/REC/CONFIRM RCPT OF
PMT</InstrInf></InstrForCdtrAgt>
3) <InstrForCdtrAgt>
<InstrInf>/REC/CONFIRM RCPT OF PMT</InstrInf> - line 1
</InstrForCdtrAgt>
<InstrForCdtrAgt>
<InstrInf>//978-555-1234 EXT 41</InstrInf> - continuation on line 2
</InstrForCdtrAgt>

5 2.86 Purpose Purp Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxI 0 1

6 2.88 Or} Proprietary Prtry Document/CstmrCdtTrfIn
Text 1 35 1 1 Mandatory for Repetitive and Semi-Repetitive Wires. Populated to instruct U.S. R R
Bank to use pre-arranged standing instructions. Please populate with the
value "REPLINE" immediately followed by the Repetitive Code Number
assigned by U.S. Bank.
E.g. : REPLINE123456
Do not populate for non-repetitive wires.

5 2.90 Tax Tax Document/CstmrCdtTrfIn

+ 0 1
6 13.1.18 Record Rcrd Document/CstmrCdtTrfIn 0 * Up to 3 occurrences can be populated for each of the following Tax amounts C
for IRS:
T - Tax Amount
I - Interest Amount
P - Penalty Amount
If Tax Amount is not populated, one occurrence must be sent for IRS with
Rcrd/Prd/Yr and Rcrd/Prd/Tp (mandatory for IRS)

7 13.1.19 Type Tp Document/CstmrCdtTrfIn

Text 1 35 0 1 Populate tax amount type: C
"T" for Tax Amount
"I" for Interest Amount
"P" for Penalty Amount
If Rcrd/TaxAmt is populated, this field must be populated

7 13.1.25 Period Prd Document/CstmrCdtTrfIn 0 1

8 13.1.26 Year Yr Document/CstmrCdtTrfIn
DateTime 0 1 Tax Year for IRS must be populated in this field. The field format is YYYY-MM- C C
DD. If not populated, the transaction will be rejected. Always map in the first
occurrence of Tax/Rcrd. Tax Month for IRS payments will be either populated
here (MM) or in the Tax/Rcrd/Prd/Tp field. If Tax/Rcrd/Prd/Tp field is not sent,
this field will be used.

8 13.1.27 Type Tp Document/CstmrCdtTrfIn

Code 0 1 Populate "MM" + <tax calendar Month in MM format>, e.g. "MM10" for C C
October. Either this field or month in Tax/Rcrd/Prd/Yr field must be populated
for IRS. If not populated in either field, the IRS transaction will be rejected.

7 13.1.31 TaxAmount TaxAmt Document/CstmrCdtTrfI 0 1

8 13.1.34 TotalAmount TtlAmt Document/CstmrCdtTrfIn
Amount 0 1 Map Tax Amount, Interest Amount or Penalty Amount in a numeric format with O O
"." as a decimal separator and 2 decimal places. E.g. "250.00"

9 Ccy Document/CstmrCdtTrfIAttribute 1 1 Valid ISO currency for Tax Amount, Interest Amount or Penalty Amount. If C C
corresponding amount is populated, Ccy must be populated.

5 2.98 RemittanceInformation RmtInf Document/CstmrCdtTrfIn 0 1

6 2.99 Unstructured Ustrd Document/CstmrCdtTrfIn
Text 1 140 0 * Only Unstructured Remittance Information is used for Wires. O
Use is limited to max 4 lines, 35 characters each; maps to Fed field OBI.
Remittance information is limited to 140 characters in total, including
remittance, regulatory reporting information and Ultimate Debtor if applicable.
Note: For national clearing purposes, the Sender must check with the Receiver
regarding length restrictions of Remittance Information, as well as information
necessary for Receiver's local country Regulatory Requirements (Purpose
Code etc.). This Information must be provided in this field in the format
required by the local country rules.
The information specified in this field is intended only for the beneficiary
customer.
If Reference for Beneficiary is required for International Wires, use the SWIFT
format code /RFB/ in this field.
Multiple references can be used, if separated with a double slash, '//'. Code
must not be repeated between two references of the same kind.
One of the following codes may be used, placed between slashes ('/'):
INV - Invoice (followed by the date, reference and details of the invoice).
IPI - Unique reference identifying a related International Payment Instruction
(followed by up to 20 characters).
RFB - Reference for the beneficiary customer (followed by up to 16
characters). For International wires only. For FED wires EndToEnd will be
used as Reference for the Beneficiary.
ROC - Ordering customer's reference.
Examples:
1) <Ustrd>/RFB/BET072</Ustrd>
<Ustrd>/INV/abc/SDF-96//1234-234///ROC/98I</Ustrd>
<Ustrd>U87</Ustrd>
2) <Ustrd>18-0938</Ustrd>
<Ustrd>OBI FIELD 1</Ustrd>
<Ustrd>OBI FIELD 2</Ustrd>
Non- Non-
Repetitive Repetitive
US FED SWIFT
Wire (Internatio
nal) Wire

R R

R R

R R

O O

R R

C C

C C

O O

R R

R R
TRF TRF
O O

O O

R R
URGP URGP

R R

R R

R R

O O

R R

O O

R R

R R

O O

O O

R R
O O

O O

R R
O O

C C

R R

R R

O O

O O

C C

O O
O O

O O

O O

C C

O O
O O

O O

C C
C

C C

C C

O O

R R
O O

R R

O O

C C

C C

O O
O O
PERMITTED CHARACTERS
SWIFT
Any letter or number is acceptable.
Acceptable special characters on SWIFT:
Regular parentheses ( )
Period .
Dash/hyphen -
Plus sign +
Colon :
Apostrophes '
Comma ,
Back slash \
Question mark ?

Ampersand & is not allowed — substitute with the word AND.

At sign @ is not allowed — substitute with the word AT.

Fedwire
Any letter or number is acceptable.
Non-printable characters are not allowed.
Acceptable special characters:
Regular parentheses ( )
Dash/hyphen -
Plus sign +
Equals =
Colon :
Semi-colon ;
Quotation Mark "
Comma ,
Period .
Back slash \
Forward slash /
Question mark ?
Exclamation mark !
Dollar sign $
Pound/number #
Percent %
Underscore _
Grave Accent `
Less than <
Greater than >

Ampersand & is not allowed — substitute with the word AND.

At sign @ is not allowed — substitute with the word AT.

The following characters can be used but it would be best to leave out, unless
there is a specific instruction in the Implementation Guide to use them:
Quotation Mark "
Pound/number #
Colon :
Semi-colon ;
Question mark ?
Less than <
Greater than >
Equals =
Back slash \
Forward slash /
Circumflex ^
Underscore _
Grave Accent `
Opening Square Bracket [
Closing Square Bracket ]
Opening Brace {
Closing Brace }
Vertical Line |