XML Payment Order File Spec

Payables
Integrated Payables
ISO 20022 Payment Order–

File Format Technical Guide
VERSION 3.2  OCT, 2020

This document contains information that is confidential and is the property of Capital One
Bank N.A.
It may not be copied, published, or used in whole or in part for any purpose other than as
expressly authorized by Capital One Bank N.A.
All trademarks, trade names, and service marks appearing herein are the property of their
respective owners.
© Capital One Bank N.A., 2015. All Rights Reserved.
Revision History
Date Version Comments
03/23/2015 1.0 Initial release
Removed Number of Transactions <NbofTxs>
and Control Sum <CtrlSum> from
Acknowledgment
Updated ClrSysRef & Cdtr.Nm in confirmation
05/27/2015 1.1
file
Corrected some error messages wherein
there was a mismatch with some of the
verbiage
08/16/2015 1.2 Minor updates to layout
01/12/2016 1.3 Minor updates to xml tags
Updated the Check print Payer/Payee name
02/11/2016 1.4
field extension lengths
Updated the Check Print Additional Payee
05/25/2016 1.5
name to 29 Characters
08/22/2016 2.0 Virtual Card payment support added
Updated Wire payment with By Order of Third
05/09/2018 3.0
party rule
10/04/2018 3.1 Comments added for Check Print Remittance
Updated Check Remittance to include only
10/15/2020 3.2
TX1
CAPITAL ONE BANK— ISO20022 Payment Order–File Format Technical GuideD D E N D U M T O B A I 2 C A S H M A N A G EM EN T B A L A N C E R E P O R T I N G S P EC I F I C A T I O Page 1 of 79
Table of Contents
Document Overview ............................................................................................................... 3

ISO 20022 File Syntax and Structure ...................................................................................... 4
Field Types ........................................................................................................................ 4
Tag Depth Structure ........................................................................................................... 4
Supported Characters......................................................................................................... 5
Account Transfer Credit Transactions (PAIN.001) ................................................................... 6
Sample ............................................................................................................................ 11
ACH Credit Transactions (PAIN.001) .................................................................................... 13
Sample ............................................................................................................................ 21
ACH Debit Transactions (PAIN.008) ..................................................................................... 23
Sample ............................................................................................................................ 31
Check Print Transactions (PAIN.001).................................................................................... 33
Sample ............................................................................................................................ 41
Wire Transfer - Credit Transactions (PAIN.001)..................................................................... 43
Sample ............................................................................................................................ 55
List of Approved Country Codes ........................................................................................ 57
List of Approved State Codes ............................................................................................ 57
Wire Drawdown - Debit Transactions (PAIN.008) .................................................................. 58
Sample ............................................................................................................................ 66
Virtual Card Payment Transactions (PAIN.001) ..................................................................... 68
Virtual Card Payments – Important Notes .......................................................................... 76
Sample ............................................................................................................................ 77
Document Overview
Capital One Bank’s Integrated Payables service supports the initiation of ACH, Account Transfer,
Check Print with/without Positive Pay, Wire Drawdown, and Wire Transfer (Domestic and
International in USD), in a variety of formats including EDI 820, ISO 20022 XML and Delimited
Flat File Format.
This document details the XML ISO 20022 PAIN.001 (Credit) and PAIN.008 (Debit) file formats.
Note about document structure:
This document aims to provide clear information regarding the file format needed to correctly
import/transmit a payment. For each block, this document provides a table that details the record
structure as well as validation messages that may be encountered, followed by a sample file as
needed to successfully import/transmit a payment. Fields not listed here are not validated at this
time and if encountered in the imported file, will be skipped. The fields supported and therefore
included in this document are those that are mandatory for the document type and required for
successful payment processing. If support of additional fields is needed, this document will be
updated to include them.
ISO 20022 File Syntax and Structure
Field Types
The section details the type of fields that are contained in the specification document.
• Mandatory - Fields that must be present for proper file format in the PAIN.001
• Required - Fields that must be present to validate the end user’s payment settings or to
construct an Account Transfer
• Optional - Fields that are not required to construct an Account Transfer, but if provided,
will be validated
• Conditional - Fields that must be present if corresponding fields are present
Tag Depth Structure
In the ‘Tag Depth’ column within the file format table below, each of the ‘Field Name’ tags are
represented by a ‘+’. The ‘+’ represents the depth of the field name tag within the document.
Supported Characters
PAIN.001 and PAIN.008 can support the following characters:

Element Type Valid Characters
A Alpha (A-Z, a-z and spaces)
N Numeric (0-9)
NS Numeric (0-9) and Special Characters (see table below)
AN Alpha-numeric (A-Z, a-z, 0-9, and spaces)
ANS Alpha-numeric (A-Z, a-z, 0-9, and spaces) and Special Characters (see table below)
Special Character Name
. Period
? Question Mark
! Exclamation Point
, Comma
; Semi-colon
: Colon
_ Underscore
@ At Sign
& Ampersand
/ Forward Slash
\ Back Slash
' Apostrophe
" Quote
` Grave Accent
~ Tilde
( Left Parenthesis
) Right Parenthesis
< Less Than
> Greater Than
$ Dollar Sign
# Pound / Number
% Percent
+ Plus
- Minus / Hyphen
= Equal
Note: Forward slash (/), back slash (\), greater than (>), and less than (<) aren’t allowed characters
for any field in ISO20022 format
Special XML Character XML Representation
& &
< <
> >
“ "
‘ '
Account Transfer Credit Transactions (PAIN.001)
This section outlines the PAIN.001 file format that will be accepted by Capital One Bank.
Document Header - this can only occur once per file

Field Index – Field Name – Tag Content Mandatory / Optional Description / Account Transfer Mapping
<?xml version="1.0" encoding="UTF-8" ?> Empty Tag Mandatory This tag must always be placed before the group header
tag.
<Document
xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.0 The contents of Credit messages are validated using the
3" xmlns:xsi="http://www.w3.org/2001/XMLSchema- Version 3 xsd.
instance">
<CstmrCdtTrfInitn> Empty Tag Mandatory This tag must always be placed before the group header tag
Group Header Block – this can only occur once per file
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Account Transfer
Tag Mapping
Group Header + Empty Tag Mandatory
<GrpHdr>
Message ++ Yes Mandatory Stored and used in pain.002 – acknowledgements as the
Identification Original Message ID - OrgnlMsgId
<MsgId>
Creation Date Time ++ Yes Mandatory File creation date and time
<CreDtTm> YYYY-MM-DDTHH:MM:SS
(i.e., 2014-10-
14T14:18:30)
Number of ++ Yes Mandatory Number of individual An amount mismatch will cause the file load to fail:
Transactions transactions contained in
<NbOfTxs> the file “The number of transactions expected is [number indicated in
this field], found [number listed in MsgId] found for MsgId
[Message ID].”
Control Sum ++ Yes Mandatory Total of all individual A count mismatch will cause the file load to fail:
<CtrlSum> payment amounts in the
file “The total amount of transactions expected in the file is [amount
in CtrlSum], found [sum of MsgId found in the file] for MsgId
[MsgId].”
Initiating Party ++ Empty Tag Mandatory The InitgPty tag is not used in processing and its contents are
<InitgPty> not stored or passed with the transaction. Its presence is an
ISO XML requirement.
Identification <Id> +++ Empty Tag Optional
CAPITAL ONE BANK— ISO20022 Payment Order–File Format Technical Guide D D E N D U M T O B A I 2 C A S H M A N A G EM EN T B A L A N C E R E P O R T I N G S P EC I F I C A T I O Page 6 of 79
Originating ++++ Empty Tag Conditional
Identification (required when
<OrgId> Identification
tag is present)
Other <Othr> +++++ Empty Tag Conditional
(required when
Originating
Identification
tag is present)
Identification <Id> ++++++ Yes Conditional Not used
(required when
Other tag is
present)
Payment Information Block – this can occur multiple times within a file
Tag Mapping
Payment Information + Empty Tag Mandatory
<PmtInf>
Payment Information ++ Yes Mandatory Not Used
Identification
<PmtInfId>
Payment Method ++ Yes Mandatory Must be TRF Payment Method is required and must be one of [TRF]. The
<PmtMtd> batch [batch ID] will be skipped.
Number of ++ Yes Mandatory Number of transactions for “The number of transactions expected is [reported number],
Transactions this payment block found [calculated number] found for PmtInfId [Payment
<NbOfTxs> Information ID].”
Control Sum ++ Yes Mandatory Total dollar amount of all The total amount of transactions expected is [reported amount],
<CtrlSum> transactions for this found [calculated amount] for PmtInfId [Payment Information
payment block ID].
Payment Type ++ Yes Mandatory
Information
<PmtTpInf>
Service Level +++ Yes Mandatory
<SvcLvl>
Code <Cd> ++++ Yes Mandatory Must be SDVA “Payment Method is required and must be one of TRF, DD and
Service Code must be one of NURG. The batch [Payment
Information ID] will be skipped.”
Requested Execution ++ Yes Mandatory Payment Date If date is a date in the past, the transaction will fail:
Date <ReqdExctnDt>
{ Format: YYYY-MM- ““An account transfer with End to End ID [End to End ID] was
DDTHH:MM:SS e.g. 2014- uploaded for an invalid payment date.”
10-14T14:18:30)
If the date exceeds the maximum allowed number of days in
the future:
“An account transfer with End to End ID [End to End ID] was
uploaded for an invalid payment date.”
Payment Information Block, Debit ABA & Account Section

Field Index – Field Tag Content Mandatory / Description / Processing Rules / Error Messages
Name – Tag Depth Optional Account Transfer
Mapping
Debtor <Dbtr> ++ Empty tag Mandatory
Name <Nm> +++ Yes Optional
Debtor Account ++ Empty tag Mandatory
<DbtrAcct>
Identification <Id> +++ Empty Tag Mandatory
Other <Othr> ++++ Empty Tag Mandatory
Identification <Id> +++++ Yes Mandatory Debit Account If missing or does not match a value in the customer
profile setup during implementation, the transaction will
fail:
“The account [invalid account] is not permitted. The

payment with End to End ID [End to End ID] will be
skipped.”
Debtor Agent <DbtrAgt> ++ Empty Tag Mandatory
Financial Institution +++ Empty Tag Mandatory
Identification <FinInstnId>
Clearing System Member ++++ Empty Tag Mandatory
Identification
<ClrSysMmbId>
Member Identification +++++ Yes Mandatory Debit ABA If missing or does not match a value in the customer
<MmbId> profile setup during implementation, the transaction will
fail:
“The account [invalid account] is not permitted. The

payment with End to End ID [End to End ID] will be
skipped.”
Must be a valid ABA number, e.g. pass MOD-10 check.
If invalid, the transaction will fail:
“Debit ABA [invalid ABA] is not a valid ABA number. The

transfer with End to End ID [End to End ID] will be
skipped.”
Payment Information Block, Payment Transaction Section
Tag Mapping
Credit Transfer ++ Empty Tag Mandatory
Transaction
Information
<CdtTrfTxInf>
Payment Information Block, Payment Transaction, Payment Information Section

Field Index – Field Tag Content Mandatory Description / Processing Rules / Error Messages
Name – Tag Depth / Optional Account Transfer
Mapping
Payment Identification +++ Empty Tag Mandatory
<PmtId>
End to End Identification ++++ Yes Mandatory Missing tag or value will cause an ISO XML-level (XSD)
<EndToEndId> validation error and cause the file load to fail
Instructed Amount ++++ Yes Mandatory Amount No decimal - amount treated as whole number
<InstdAmt CCy= “USD”>
Decimal, two digits after the decimal - interpreted literally, with
decimal
Decimal, one digit after the decimal, i.e. 1.2, interpreted as 1.20
If the transaction exceeds the user’s limits, the transaction will

fail:
“One or more records exceed the user’s [limit type exceeded]

of [limit allowed].”
If the amount exceeds 8 digit (9 characters with decimal) limit,

the transaction will fail:
“Amount field does not validate for line 1: Field length exceeds
maximum: [invalid length] > 8”
If InstdAmt CCY does not equal USD, the transaction will fail:
“Monetary Currency is not valid. The check with End to End ID

[End to End ID] will be skipped.”
Payment Information Block, Payment Transaction, Credit ABA & Account Section
Field Index – Field Tag Conten Mandatory / Description / Comments and validation
Name – Tag Depth t Optional Account Transfer
Mapping
Creditor Agent <CdtrAgt> +++ Empty Tag Required
Financial Institution ++++ Empty Tag Required
Clearing System Member +++++ Empty Tag Required
Identification
<ClrSysMmbId>
Member Identification ++++++ Yes Required Credit ABA If missing or does not match a value in the customer profile
<MmbId> setup during implementation, the transaction will fail:
“The account [invalid account] is not permitted. The payment

with End to End ID [End to End ID] will be skipped.”
“Credit ABA [invalid ABA] is not a valid ABA number. The

transfer with End to End ID [End to End ID] will be skipped.”
Creditor +++ Empty Tag Required
Account<CdtrAcct>
Identification <Id> ++++ Empty Tag Required
Other <Othr> +++++ Empty Tag Required
Identification <Id> ++++++ Yes Required Credit Account If missing or does not match a value in the customer profile
setup during implementation, the transaction will fail:
“The account [invalid account] is not permitted. The payment

Payment Information Block, Payment Transaction, Memo Section

Field Index – Field Tag Content Mandatory Description / Comments and validation
Name – Tag Depth / Optional Account Transfer
Mapping
Remittance Information +++ Empty Tag Optional Remittance Information <RmtInf>
<RmtInf>
Unstructured Unstructured
<Ustrd>
Sample
<?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">
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>2014-11-12-001-003</MsgId>
<CreDtTm>2014-11-12T11:07:03</CreDtTm>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>3000.00</CtrlSum>
<InitgPty>
<Id>
<OrgId>
<Othr>
<Id>123456789</Id>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>ACMEPPD4</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<CtrlSum>3000</CtrlSum>
<PmtTpInf>
<SvcLvl>
<Cd>SDVA</Cd>
</SvcLvl>
</PmtTpInf>
<ReqdExctnDt>2015-03-23</ReqdExctnDt>
<Dbtr>
<Nm>Debtor</Nm>
</Dbtr>
<DbtrAcct>
<Id>
<Othr>
<Id>674582086</Id>
</Othr>
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<ClrSysMmbId>
<MmbId>065000090</MmbId>
</ClrSysMmbId>
</FinInstnId>
</DbtrAgt>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>1-0001239</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="USD">3000</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<ClrSysMmbId>
</ClrSysMmbId>
</FinInstnId>
</CdtrAgt>
<CdtrAcct>
<Id>
<Othr>
<Id>0812121359</Id>
</Othr>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>Memo</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
ACH Credit Transactions (PAIN.001)

Field Index – Field Name – Tag Content Mandatory / Optional Description / NACHA Mapping
tag.
<Document
instance">
Field Index – Tag Content Mandatory / Description / Processing Rules / Error Messages
Field Name – Depth Optional NACHA
Tag Mapping
<GrpHdr>
Message ++ Yes Mandatory Stored and used in pain.002 – acknowledgements as the Original
Identification Message ID - OrgnlMsgId
<MsgId>
Creation Date Time ++ Yes Mandatory File creation date
<CreDtTm> and time
YYYY-MM-
DDTHH:MM:SS (e.i.,
2014-10-
14T14:18:30)
Transactions transactions “The number of transactions expected is [number indicated in
<NbOfTxs> contained in the file this field], found [number listed in MsgId] found for MsgId
[Message ID].”
<CtrlSum> payment amounts in
the file “The total amount of transactions expected in the file is [amount
[MsgId].”
<OrgId> Identification tag
is present)
(required when
Originating
Identification tag
is present)
(required when
Other tag is
present)
Tag Mapping
<PmtInf>
Payment Information ++ Yes Mandatory Company Entry
Identification Description Batch
<PmtInfId> Header, positions 54
- 63
Payment Method ++ Yes Mandatory Must be TRF “Payment Method is required and must be one of TRF and
<PmtMtd> Service Code must be one of NURG. The batch [Payment
Number of ++ Yes Mandatory Number of “The number of transactions expected is [reported number],
Transactions transactions for this found [calculated number] found for PmtInfId [Payment
<NbOfTxs> payment block Information ID].”
Control Sum ++ Yes Mandatory Total dollar amount “The total amount of transactions expected is [reported
<CtrlSum> of all transactions amount], found [calculated amount] for PmtInfId [Payment
for this payment Information ID].”
block
Payment Type ++ Empty Tag Mandatory
Information
<PmtTpInf>
Service Level +++ Empty Tag Mandatory
<SvcLvl>
Code <Cd> ++++ Yes Mandatory Must be NURG (for “Payment Method is required and must be one of TRF, DD and
ACH) Service Code must be one of NURG. The batch [Payment
Local Instrument +++ Empty Tag Mandatory
<LclInstrm>
Code <Cd> ++++ Yes Mandatory Standard Entry If ACH company is not permitted to Standard Entry Class:
Class
“The ACH Company [ACH Company ID] is not permitted to
Batch Header, create CREDIT [SEC Code] batches. The payment with End to
positions 51 - 53 End ID [End to End ID] to [receiver name and ID] will be
skipped.”
Supported values:
CCD, PPD, CTX, If ACH Company is not permitted to initiate credits for the SEC:
CIE
“Credit [SEC Code] Payments are not supported by ACH
Company [ACH Company]. The payment with End to End ID
[End to End ID] to [receiver name and ID] will be skipped. ”
Requested Execution ++ Yes Mandatory Payment Date / If date is a date in the past, but in the current year:
Date <ReqdExctnDt> Effective Entry Date
“An ACH payment was sent for a date before the next
Batch Header, available payment date. The [SEC Code] batch for ACH
positions 70 – 75 company [ACH Company] on [reported date] will be skipped.”
Format: YYYY-MM- If date is a date in the past, but in a different year:

DDTHH:MM:SS e.g.
2014-10- “The payment with End to End ID [End to End ID] to [Payee
14T14:18:30) Name (last four digits of payee’s account)] has an invalid
payment year. Year [year] is before the next available payment
year and this record will be skipped.”

the future:
“An ACH [SEC Code] batch for ACH company [ACH Company]
was scheduled on [date in the file] which exceeds the allowed
number of days in the future, the payment date must be before
[calculated maximum processing date].”
Payment Information Block, Originator Section

Tag Mapping
Name <Nm> +++ Yes Optional ACH Company At this time, this field is not validated or used. Output NACHA
Name file will use value found in ACH Company Name stored on
Capital One system..
Batch Header,
positions 05 - 20
Identification <Id> +++ Empty Tag Required
Originating ++++ Empty Tag Required
Identification <OrgId>
Identification <Id> ++++++ Yes Required ACH Company ID Must match the ID of an ACH Company listed on the
implementation setup form. The ID must be entitled to initiate
Batch Header, ACH credits /debits.
positions 41 - 50
If the value in the file is invalid, the transaction will be skipped
and the following three error messages will be displayed for
each transaction in the “batch””
“The ACH Company [invalid ACH Company ID] for the

payment with End to End ID [End to End ID] to [receiver name
and ID] was unknown.”
“The ACH Company [invalid ACH Company ID] is not

permitted to create CREDIT [SEC] batches. The payment with
End to End ID [End to End ID] to [receiver name and ID] will be
skipped.”
“Credit [SEC] payments are not supported by [invalid ACH

Company ID]. The payment with End to End ID [End to End ID]
to [receiver name and ID] will be skipped.”
<DbtrAcct>
Identification <Id> +++++ Yes Required Offset Account If offset present in ACH Company record,
PmtInf.DbtrAcct.Id.Othr must be populated and must match a
Entry Detail, defined offset for the ACH Company.
positions 13 - 29
If more than one offset defined for ACH Company, the value in
file must match one. If the offset in the input file matches a
disabled offset account, the transaction will be skipped:
“ACH Company [ACH Company ID] for the payment with End
to End ID [End to End ID] to [receiver name and ID] is not
permitted to use the offset account [offset ABA and account
number].”
If missing or does not match a value in the database, the

transaction will be skipped:
“ACH Company [ACH Company] for the payment with End to

End ID [End to End ID] to Payee [receiver name and ID]
requires that a valid offset account be provided.”
If no offset is defined for the ACH Company, the ID record is
skipped.
Debtor Agent ++ Empty Tag Mandatory
<DbtrAgt>
Identification
<FinInstnId>
Clearing System ++++ Empty Tag Mandatory
Member Identification
<ClrSysMmbId>
Member Identification +++++ Yes Mandatory Offset ABA If offset present in ACH Company record,
<MmbId> PmtInf.DbtrAgt.FinInstnId.ClrSysMbmId must be populated
Entry Detail, and must match a defined offset for the ACH Company.
positions 4 - 12
If more than one offset defined for ACH Company, value in file
must match one.


If no offset defined for the ACH Company, the ID record is

skipped.

Tag Mapping
Transaction
Information
<CdtTrfTxInf>

Tag Mapping
<PmtId>
End to End ++++ Yes Mandatory Trace Number Transaction Trace #, first 8 digits should be ‘06500009’, last 7
Identification digits is client’s unique trace #.
<EndToEndId>
Entry Detail, Note: To be used to identify the electronic payment reference
positions 80 - 94 number – equivalent to a check serial number
Amount <Amt> +++ Empty Tag Mandatory
<InstdAmt CCy=
“USD”> Entry Detail, Decimal, two digits after the decimal - interpreted literally, with
positions 30 - 39 decimal
Decimal, one digit after the decimal, i.e. 1.2, interpreted as

1.20
If the transaction exceeds the user’s limits, the file load will fail:

If the amount exceeds 10 digit (11 characters with decimal)

limit, the file load will fail:
Zero Dollar Rule:
If zero dollar, PmtInf.LclInstrm.Cd (SEC Code) must be CTX or

CCD and CdtTrfTxInf.RmtInf.Ustrd must be populated, else the
file load will fail:
“Monetary Amount may only be zero for CTX or CCD SEC

codes. The payment with End to End ID [End to End ID] will be
skipped.”
Creditor Agent +++ Empty Tag Required
<CdtrAgt>
Identification
<FinInstnId>
Clearing System +++++ Empty Tag Required
<ClrSysMmbId>
Member Identification ++++++ Yes Required Receiver ABA Must be a valid ABA number, e.g. pass MOD-10 check.
<MmbId>
Entry Detail, If invalid, the transaction will be skipped:
positions 4 - 12
“Receiver ABA [ABA] is not a valid ABA number. The payment
Payment Information Block, Payment Transaction, Receiver Section
Field Index – Tag Content Mandatory / Description / Comments and validation
Tag Mapping
Creditor <Cdtr> +++ Empty Tag Required
Name <Nm> ++++ Yes Required Receiver Name / NACHA accepts up to 22 characters for SEC’s other than CTX
Receiving Company and 16 characters for CTX. Name values longer than the 22
Name character limit will be truncated – right-most characters will be
dropped.
Entry Detail,
For CTX, name values of longer than 16 characters will be
CCD and PPD truncated, with the right-most characters being dropped.
positions 55 - 76
If the tag is missing, the transaction will be skipped:
CIE - 40 - 54
“Receiver Name is required. The payment with End to End ID
CTX - positions 59 – [End to End ID] will be skipped.”
74
Contact Details ++++ Empty Tag Optional
<CtctDtls>
Other <Othr> +++++ Yes Optional Receiver ID NACHA accepts up to 15 characters. Name values longer
than the 15 character limit will be truncated – right-most
Entry Detail, characters will be dropped.
CCD, CTX, PPD, -

positions 40 - 54
CIE - positions 55 –
76
Account<CdtrAcct>
Identification <Id> ++++++ Yes Required Receiver Account If the value of the field exceeds 17 characters, the transaction
Number will be skipped:
Entry Detail, “Receiving Account Number field does not validate for line 1:
positions 13 - 29 Field length exceeds maximum: [invalid length] > 17”
Type <Tp> ++++ Empty Tag Required
Proprietary <Prtry> +++++ Yes Required Receiver Account Allowed Values:
Type DDA (checking), SAV (savings), GL and LOAN
Entry Detail, If the tag containing the receiver account type (Prtry) is
positions 02 - 03 missing, an XSD error will be displayed and the file load will
fail.
Allowed Values:
DDA, SAV, GL, If the group tag containing the receiver account type (Tp.Prtry)
LOAN is missing, the transaction will be skipped:
“Account Type is required. The payment with End to End ID

If the receiver account type is invalid, the transaction will be

skipped:
“Invalid payee account type: [account type]. The payment with

End to End ID [End to End ID] will be skipped.”
Remittance +++ Empty Tag Optional
Information
<RmtInf>
Unstructured ++++ Yes Optional Addenda
<Ustrd>
Addenda,
positions 04 - 83
Sample

<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>2014-11-06-001-001</MsgId>
<InitgPty>
<Id>
<OrgId>
<Othr>
<Id>123456789</Id>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>ACMEPPD6</PmtInfId>
<PmtTpInf>
<SvcLvl>
<Cd>NURG</Cd>
</SvcLvl>
<LclInstrm>
<Cd>PPD</Cd>
</LclInstrm>
</PmtTpInf>
<Dbtr>
<Nm>Acme</Nm>
<Id>
<OrgId>
<Othr>
<Id>123409987</Id>
</Othr>
</OrgId>
</Id>
</Dbtr>
<DbtrAcct>
<Id>
<Othr>
<Id>3052516569</Id>
</Othr>
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<ClrSysMmbId>
</ClrSysMmbId>
</FinInstnId>
</DbtrAgt>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>0200000</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="USD">2416.00</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<ClrSysMmbId>
</ClrSysMmbId>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>Linda Johnson</Nm>
</Cdtr>
<CdtrAcct>
<Id>
<Othr>
<Id>3004334</Id>
</Othr>
</Id>
<Tp>
<Prtry>DDA</Prtry>
</Tp>
</CdtrAcct>
<RmtInf>
<Ustrd>Addenda - Expenses</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
ACH Debit Transactions (PAIN.008)
This section outlines the debit PAIN.008 file format that will be accepted by Capital One Bank.

Field Index – Field Name – Tag Content Mandatory / Optional Description / NACHA Mapping
tag.
<Document The contents of Debit messages are validated using the

xmlns="urn:iso:std:iso:20022:tech:xsd:pain.008.001.0 Version 3 xsd.
3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance">
<CstmrDrctDbtInitn> Empty Tag Mandatory This tag must always be placed before the group header tag
Tag Mapping
<GrpHdr>
<MsgId>
Creation Date Time ++ Yes Mandatory File creation date
<CreDtTm> and time
YYYY-MM-
DDTHH:MM:SS (e.i.,
2014-10-
14T14:18:30)
Transactions transactions “The number of transactions expected is [number indicated in
<NbOfTxs> contained in the file this field], found [number listed in MsgId] found for MsgId
[Message ID].”
<CtrlSum> payment amounts in
the file “The total amount of transactions expected in the file is [amount
[MsgId].”
<OrgId> Identification tag
is present)
(required when
Originating
Identification tag
is present)
(required when
Other tag is
present)
Field Index – Tag Content Mandatory / Description / Error Validation Message
Tag Mapping
<PmtInf>
Payment Information ++ Yes Mandatory Company Entry
Identification Description Batch
<PmtInfId> Header, positions 54
- 63
Payment Method ++ Yes Mandatory Must be DD “Payment Method is required and must be one of DD and
<PmtMtd> Service Code must be one of NURG. The batch [Payment
Number of ++ Yes Mandatory Number of “The number of transactions expected is [reported number],
Transactions transactions for this found [calculated number] found for PmtInfId [Payment
<NbOfTxs> payment block Information ID].”
Control Sum ++ Yes Mandatory Total dollar amount The total amount of transactions expected is [reported
<CtrlSum> of all transactions amount], found [calculated amount] for PmtInfId [Payment
for this payment Information ID].
block
Information
<PmtTpInf>
<SvcLvl>
Code <Cd> ++++ Yes Mandatory Must be NURG (for “Payment Method is required and must be one of TRF, DD
ACH) and Service Code must be one of NURG. The batch [Payment
Local Instrument +++ Empty Tag Required
<LclInstrm>
Code <Cd> ++++ Yes Required Standard Entry If ACH company is not permitted to Standard Entry Class:
Class
“The ACH Company [ACH Company ID] is not permitted to
Batch Header, create DEBIT [SEC Code] batches. The payment with End to
positions 51 - 53 End ID [End to End ID] to [receiver name and ID] will be
skipped.”
Supported values:
CCD, PPD, CTX, If ACH Company is not permitted to initiate debits for the SEC:
CIE, WEB, TEL
“Debit [SEC Code] Payments are not supported by ACH
Company [ACH Company]. The payment with End to End ID
[End to End ID] to [receiver name and ID] will be skipped. ”
Sequence Type +++ Yes Conditional Payment Type Code For WEB and TEL transactions
<SeqTp> (Required for
WEB Entry Detail Record For Single occurrence transactions, the system accepts the
transactions, (6 record), positions following supported ISO values:
Optional for TEL 77 - 78
transactions) FRST (First payment), FNAL (Final payment, OOFF (OneOff
payment), RPRE (Re-presented payment)
For Recurring occurrence transactions, the system accepts the

following ISO value:
RCUR (Recurring payment)
If the payment includes a value other than those listed above,

an ISO XML-level (XSD) validation error will be displayed and
the file load will fail.
Requested Collection ++ Yes Mandatory Payment Date / If date is a date in the past, but in the current year:
Date <ReqdColltnDt> Effective Entry Date
“An ACH payment was sent for a date before the next
Batch Header, available payment date. The [SEC Code] batch for ACH
positions 70 – 75 company [ACH Company] on [business date] will be skipped.”
Format: YYYY-MM- If date is a date in the past, but in a different year:

DDTHH:MM:SS e.g.
2014-10- “The payment with End to End ID [End to End ID] to [Payee
14T14:18:30) Name (last four digits of payee’s account)] has an invalid
payment year. Year [year] is before the next available payment
year and this record will be skipped.”

the future:
“An ACH [SEC Code] batch for ACH company [ACH

Company] was scheduled on [date in the file] which exceeds
the allowed number of days in the future, the payment date
must be before [calculated maximum processing date].”

Tag Mapping
Creditor <Cdtr> ++ Empty tag Mandatory
Name <Nm> +++ Yes Optional ACH Company At this time, this field is not validated or used. Output NACHA
Name file will use value found in ACH Company Name stored on
Capital One system.
Batch Header,
positions 05 - 20
Identification <OrgId>
Identification <Id> ++++++ Yes Required ACH Company ID Must match the ID of an ACH Company listed on the
implementation setup form. The ID must be entitled to initiate
Batch Header, ACH credits / debits for that Company.
positions 41 - 50
If the value in the file is invalid, the transaction will be skipped
and the following three error messages will be displayed for
each transaction in the “batch””
“The ACH Company [invalid ACH Company ID] for the

payment with End to End ID [End to End ID] to [receiver name
and ID] was unknown.”
“The ACH Company [invalid ACH Company ID] is not

permitted to create DEBIT [SEC] batches. The payment with
End to End ID [End to End ID] to [receiver name and ID] will
be skipped.”
“Debit [SEC] payments are not supported by [invalid ACH

Company ID]. The payment with End to End ID [End to End
ID] to [receiver name and ID] will be skipped.”
Creditor Account ++ Empty tag Mandatory
<CdtrAcct>
Identification <Id> +++++ Yes Required Offset Account If offset present in ACH Company record,
PmtInf.CdtrAcct.Id.Othr must be populated and must match a
defined offset for the ACH Company.
Entry Detail,
positions 13 - 29 If more than one offset defined for ACH Company, the value in
file must match one. If the offset in the input file matches a
disabled offset account, the transaction will be skipped:
“ACH Company [ACH Company ID] for the payment with End
to End ID [End to End ID] to [receiver name and ID] is not
permitted to use the offset account [offset ABA and account
number].”


If no offset is defined for the ACH Company, the ID record is

skipped.
Creditor Agent ++ Empty Tag Mandatory
<CdtrAgt>
Identification
<FinInstnId>
<ClrSysMmbId>
Member Identification +++++ Yes Mandatory Offset ABA If offset present in ACH Company record,
<MmbId> PmtInf.CrdtrAgt.FinInstnId.ClrSysMbmId must be populated
Entry Detail, and must match a defined offset for the ACH Company.
positions 4 - 12
If more than one offset defined for ACH Company, value in file
must match one.


If no offset defined for the ACH Company, the ID record is

skipped.
Tag Mapping
Direct Debit ++ Empty Tag Mandatory
Transaction
Information
<DrctDbtTxInf>

Tag Mapping
<PmtId>
End to End ++++ Yes Mandatory Trace Number Transaction Trace #, first 8 digits should be ‘06500009’, last 7
Identification digits is client’s unique trace #.
<EndToEndId> Entry Detail,
positions 80 - 94 Note: To be used to identify the electronic payment reference
number – equivalent to a check serial number
<InstdAmt CCy=
“USD”> Entry Detail, Decimal, two digits after the decimal - interpreted literally, with
positions 30 - 39 decimal

1.20


limit, the file load will fail:
Zero Dollar Rule:
If zero dollar, PmtInf.LclInstrm.Cd must be CTX or CCD and

CdtTrfTxInf.RmtInf.Ustrd must be populated, else the file load
will fail:
“Monetary Amount may only be zero for CTX or CCD SEC
codes. The payment with End to End ID [End to End ID] will be
skipped.”
Debtor Agent +++ Empty Tag Mandatory
<DbtrAgt>
Financial Institution ++++ Empty Tag Mandatory
Identification
<FinInstnId>
Clearing System +++++ Empty Tag Mandatory
<ClrSysMmbId>
Member Identification ++++++ Yes Mandatory Receiver ABA Must be a valid ABA number, e.g. pass MOD-10 check.
<MmbId>
Entry Detail, If invalid, the transaction will be skipped:
positions 4 - 12
“Receiver ABA [ABA] is not a valid ABA number. The payment
Debtor <Dbtr> +++ Empty Tag Mandatory
Name <Nm> ++++ Yes Mandatory Receiver Name / NACHA accepts up to 22 characters for SEC’s other than CTX
Receiving Company and 16 characters for CTX. Name values longer than the 22
Name character limit will be truncated – right-most characters will be
dropped.
Entry Detail,
For CTX, name values of longer than 16 characters will be
CCD and PPD truncated, with the right-most characters being dropped.
positions 55 - 76
If the tag is missing, the transaction will be skipped:
CIE - 40 - 54
“Receiver Name is required. The payment with End to End ID
CTX - positions 59 – [End to End ID] will be skipped.”
74
<CtctDtls>
Other <Othr> +++++ Yes Optional Receiver ID NACHA accepts up to 15 characters. Name values longer
than the 15 character limit will be truncated – right-most
Entry Detail, characters will be dropped.
CCD, CTX, PPD,

TEL, WEB -
positions 40 - 54
CIE - positions 55 -
76
Debtor +++ Empty Tag Mandatory
Account<DbtrAcct>
Identification <Id> ++++ Empty Tag Mandatory
Other <Othr> +++++ Empty Tag Mandatory
Identification <Id> ++++++ Yes Mandatory Receiver Account If the value of the field exceeds 17 characters, the transaction
Number will be skipped:
Entry Detail, “Receiving Account Number field does not validate for line 1:
positions 13 - 29 Field length exceeds maximum: [invalid length] > 17”
Type <Tp> ++++ Empty Tag Required
Proprietary <Prtry> +++++ Yes Required Receiver Account Allowed Values:
Type DDA (checking), SAV (savings), GL and LOAN
Entry Detail, If the tag containing the receiver account type (Prtry) is
positions 02 - 03 missing, an XSD error will be displayed and the file load will
fail.
Allowed Values:
DDA, SAV, GL, If the group tag containing the receiver account type (Tp.Prtry)
LOAN is missing, the transaction will be skipped:
“Account Type is required. The payment with End to End ID

If the receiver account type is invalid, the transaction will be

skipped:
“Invalid payee account type: [account type]. The payment with

Purpose <Purp> +++ Empty Tag Optional
Proprietary <Prtry> +++++ Yes Conditional Prenote indicator in Must be populated as “PRENOTE” or will it will be ignored.
Transaction Type
Additionally, the amount must be zero. If this tag is present
Entry Detail, and the amount is not zero, the transaction will be skipped:
Positions 02 - 03
“The total amount of transactions expected is 0.00, found
[amount] for [PmtInfId Entry Description].”
Remittance +++ Empty Tag Conditional
Information <RmtInf>
Unstructured ++++ Yes Conditional Addenda
<Ustrd>
Addenda, positions
04 - 83
Sample

<CstmrDrctDbtInitn>
<GrpHdr>
<MsgId>Acme Direct Debit</MsgId>
<InitgPty>
<Id>
<OrgId>
<Othr>
<Id>123456789</Id>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>COLL</PmtInfId>
<PmtMtd>DD</PmtMtd>
<PmtTpInf>
<SvcLvl>
<Cd>NURG</Cd>
</SvcLvl>
<LclInstrm>
<Cd>PPD</Cd>
</LclInstrm>
</PmtTpInf>
<ReqdColltnDt>2014-11-12</ReqdColltnDt>
<Cdtr>
<Nm>ACH Company</Nm>
<Id>
<OrgId>
<Othr>
<Id>6012220383</Id>
</Othr>
</OrgId>
</Id>
</Cdtr>
<CdtrAcct>
<Id>
<Othr>
<Id>674582086</Id>
</Othr>
</Id>
<Ccy>USD</Ccy>
</CdtrAcct>
<CdtrAgt>
<FinInstnId>
<ClrSysMmbId>
</ClrSysMmbId>
<PstlAdr>
<Ctry>US</Ctry>
</PstlAdr>
</FinInstnId>
</CdtrAgt>
<DrctDbtTxInf>
<PmtId>
</PmtId>
<DbtrAgt>
<FinInstnId>
<ClrSysMmbId>
</ClrSysMmbId>
</FinInstnId>
</DbtrAgt>
<Dbtr>
<Nm>Wilson Construction</Nm>
<CtctDtls>
<Othr>40029900</Othr>
</CtctDtls>
</Dbtr>
<DbtrAcct>
<Id>
<Othr>
<Id>10002345</Id>
</Othr>
</Id>
<Tp>
<Prtry>DDA</Prtry>
</Tp>
</DbtrAcct>
<RmtInf>
<Ustrd>Addenda</Ustrd>
</RmtInf>
</DrctDbtTxInf>
</PmtInf>
</CstmrDrctDbtInitn>
</Document>
Check Print Transactions (PAIN.001)

Field Index – Field Name – Tag Content Mandatory / Optional Description / Harland Mapping
tag.
<Document
instance">
Field Name – Depth / Optional Harland Mapping
Tag
<GrpHdr>
<MsgId>
(e.i., 2014-10-
14T14:18:30)
[Message ID].”
[MsgId].”
tag is present)
(required when
Originating
Identification
tag is present)
(required when
Other tag is
present)
Tag
<PmtInf>
Identification
<PmtInfId>
Payment Method ++ Yes Mandatory Must be CHK “Payment Method is required and must be one of CHK. The
<PmtMtd> batch [Payment Information ID] will be skipped.”
Control Sum ++ Yes Mandatory Total dollar amount of all The total amount of transactions expected is [reported
<CtrlSum> transactions for this amount], found [calculated amount] for PmtInfId [Payment
payment block Information ID].
Date <ReqdExctnDt>
Must not be more than 15 “The payment date must be current day or a future date. The
calendar days from current payment with End to End ID [End to End ID] to [Payee Name]
date. for [check amount] will be skipped.”
Format: YYYY-MM- If the date exceeds the maximum allowed number of days in
DDTHH:MM:SS e.g. 2014- the future will fail:
10-14T14:18:30)
“A check with End to End ID [End to End ID] to [Payee Name]
for [check amount] was sent for a payment date that is invalid.”
Payment Information Block, Payer Section
Tag
Name <Nm> +++ Yes Required Payer Name If the tag is missing, the transaction will fail:
Order Record, Payer-Name “No value found for required field: Payer for [invalid record]”
If the value of the field exceeds 50 characters, the transaction

will fail:
“Payer field does not validate for line 1: Field length exceeds
Postal Address +++ Empty Tag Required
<PstlAdr>
Street Name ++++ Yes Required Payer Address 1 If the tag is missing, the transaction will fail:
<StrtNm>
Order Record, Payer- “No value found for required field: for [invalid record]” Payer
Address Address Line 1

will fail:
“Payer Address Line 1 field does not validate for line 1: Field
length exceeds maximum: [invalid length] > 50”
Postal Code <PstCd> ++++ Yes Required Payer Address 3 At least one tag must be present (PstCd, TwnNm, or
CtrySubDvsn). If all three tags are missing, the transaction will
Order Record, Payer- fail:
Address
“No value found for required field: Payer Address Line 3 for
record [invalid record]”
Town Name ++++ Yes Required Payer Address 3 At least one tag must be present (PstCd, TwnNm, or
<TwnNm> CtrySubDvsn). If all three tags are missing, the transaction will
Order Record, Payer- be skipped:
Address
Country Subdivision ++++ Yes Required Payer Address 3 At least one tag must be present (PstCd, TwnNm, or
<CtrySubDvsn> CtrySubDvsn). If all three tags are missing, the transaction will
Order Record, Payer- be skipped:
Address
Contact Details +++ Empty Tag Optional
<CtctDtls>
Name <Nm> ++++ Yes Optional Additional Payer Name If the value of the field exceeds 30 characters, the transaction
will fail:
Order Record, Payer-Name
“Additional Payer Name field does not validate for line 1: Field
Phone Number ++++ Yes Optional Payer Phone Number
<PhneNb>
Order Record, Payer-
Phone
Format: +NNN-NNN-NNNN
e.g. +800-555-5555
Or
+N-NNN-NNN-NNNN e.g.
+1-800-555-5555
<DbtrAcct>
Identification <Id> +++++ Yes Mandatory Debit Account If missing or does not match a value indicated on the
implementation form, the transaction will fail:
Order Record, Clearing-
Acct# “The account [ABA/last four of account] is not permitted. The
payment with End to End ID [End to End ID] to [Payee Name]
for [check amount] will be skipped.”
<DbtrAgt>
Identification
<FinInstnId>
<ClrSysMmbId>
Member Identification +++++ Yes Mandatory Debit ABA If missing or does not match a value indicated on the
<MmbId> implementation form, the transaction will fail:
Order Record, Clearing-
Transit-Routing# “The account [ABA/last four of account] is not permitted. The
payment with End to End ID [End to End ID] to [Payee Name]
for [check amount] will be skipped.”
Tag
Transaction
Information
<CdtTrfTxInf>

Name – Tag Depth / Optional Harland Mapping
<PmtId>
Instruction Identification ++++ Yes Optional Void Indicator Field value must be “Void”. Any other value will cause the
<InstrId> transaction to be classified as a standard check and not a
Order Record, Void-Flag void.
Order Record, Check- Decimal, two digits after the decimal - interpreted literally,
Amount with decimal

1.20
If the transaction exceeds the user’s limits, the transaction

will fail:
“One or more records exceed the user’s [limit type

exceeded] of [limit allowed].”

limit, the transaction will fail:
“Amount field does not validate for line 1: Field length

exceeds maximum: [invalid length] > 8”
If InstdAmt CCY does not equal USD, the transaction will

fail:
“Monetary Currency is not valid. The check with End to End

ID [End to End ID] will be skipped.”
Payment Information Block, Payment Transaction, Check Details Section
Name – Tag Depth Optional Harland Mapping
Cheque Instruction +++ Empty Tag Required
<ChqInstr>
Cheque Number ++++ Yes Optional Check Number If the check number exceeds 10 characters, the transaction
<ChqNb> will fail:
Order Record, Check#
“Check Number cannot exceed 10 characters. The payment
with End to End ID [End to End ID] to [Payee Name] for
[check amount] will be skipped.”
Delivery Method ++++ Empty Tag Optional
<DlvryMtd>
Proprietary <Prtry> +++++ Yes Optional Shipping Method “Invalid shipping method. Valid shipping methods are USPS,
FEDX, UPS, BNDL. The check with End to End ID [End to
Order Record, Ship- End ID] will be skipped.”
Method
Accepted Values:
USPS, FEDX, UPS, BNDL

Cheque Maturity Date ++++ Yes Required Check Date If the date exceeds the maximum allowed number of days in
<ChqMtrtyDt> the future or the maximum stale date (+/- 15 calendar days),
Order Record, Issue-Date the transaction will fail:
Format: YYYY-MM- “Check Date must be between [maximum allowed stale

DDTHH:MM:SS e.g. 2014- date] and [maximum post-date allowed]. The payment with
10-14T14:18:30) End to End ID [End to End ID] to [Payee Name] for [amount]
will be skipped.”
Voids can exceed the maximum stale date but cannot be

postdated. If so, the transaction will fail:
“Void payments cannot have a check date in the future. The

payment with End to End ID [End to End ID] to [Payee
Name] for [amount] will be skipped.”
Forms Code <FrmsCd> ++++ Yes Required Check Layout If the tag is missing, the transaction will fail:
Order Record, Product-ID “No value found for required field: Check Layout for record
Allowed Values: 1”
ADVONLY - Debit/Credit
Advice No Remittance If the field value is not a valid check layout, the transaction
Detail will fail:
CKCOLMN - Payment
Accompanies Remittance “Valid Check Layouts are ADVCOLMN, CKCOLMN,
Advice ADVONLY, CKONLY and CKSTUB. The payment with End
CKONLY - Make Payment to End ID [End to End ID] to [Payee Name] for [amount] will
Only be skipped.”
ADVCOLMN - Debit/Credit
Advice with Remittance
Detail
CKSTUB -
Memo/Additional
Remittance Detail
Memo Field <MemoFld> ++++ Yes Optional Memo Information to be printed on the memo line of the check
Order Record, Memo-Line
Payment Information Block, Payment Transaction, Payee Section

Name <Nm> ++++ Yes Required Payee Name If the tag is missing, the transaction will fail:
Order Record, Payee- “No value found for required field: Payee for record [invalid
Name record]”
If the value of the field exceeds 50 characters, the

transaction will fail:
“Payee field does not validate for line 1: Field length

exceeds maximum: [invalid record] > 50”
Postal Address ++++ Empty Tag Required
<PstlAdr>
Street Name <StrtNm> +++++ Yes Required Payee Address 1 If the tag is missing, the transaction will fail:
Order Record, Payee- “No value found for required field: Payee Address Line 1 for
Address record [invalid record]”

“Payee Address Line 1 field does not validate for line 1: Field
Postal Code <PstCd> +++++ Yes Required Payee Address 3 At least one tag must be present (PstCd, TwnNm, or
CtrySubDvsn). If all three tags are missing, the transaction
Order Record, Payee- will fail:
Address
“No value found for required field: Payee Address Line 3 for
Town Name <TwnNm> +++++ Yes Required Payee Address 3 At least one tag must be present (PstCd, TwnNm, or
CtrySubDvsn). If all three tags are missing, the transaction
Address
Country Subdivision +++++ Yes Required Payee Address 3 At least one tag must be present (PstCd, TwnNm, or
<CtrySubDvsn> CtrySubDvsn). If all three tags are missing, the transaction
Address
<CtctDtls>
Name <Nm> +++++ Yes Optional Additional Payee Name If the value of the field exceeds 29 characters, the
Order Record, Payee-
Name “Additional Payee Name field does not validate for line 1:
Field length exceeds maximum: [invalid length] > 29”
Remittance Information +++ Empty Tag Optional

<RmtInf>
Unstructured ++++ Yes Optional Remittance Note : Each column data must be separated by a pipe
<Ustrd> delimiter “l”
Transaction Record Data must start with TX1 followed by Remit data.
Remittance is required for check layouts ADVCOLMN and

CKCOLMN. If missing, the transaction will fail:
“Remittance information required for Check Layouts

ADVCOLMN and CKCOLMN. The payment with End to End
ID [End to End ID] to [Payee Name] for [amount] will be
skipped.”
If remittance cannot be present if the check layout is

ADVONLY, CKONLY, or CKSTUB. If so, the transaction will
fail:
“Remittance information cannot be entered for Check

Layouts ADVONLY, CKONLY and CKSTUB. The payment
with End to End ID [End to End ID] to [Payee Name] for
[amount] will be skipped.”
Sample
<?xml version="1.0" encoding="UTF-8"?>
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>Acme Check</MsgId>
<InitgPty>
<Id>
<OrgId>
<Othr>
<Id>ABC</Id>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>B2</PmtInfId>
<PmtMtd>CHK</PmtMtd>
<Dbtr>
<Nm>ABC Manufacturing</Nm>
<PstlAdr>
<StrtNm>123 Peachtree Street</StrtNm>
<PstCd>12346-9999</PstCd>
<TwnNm>Atlanta</TwnNm>
<CtrySubDvsn>GA</CtrySubDvsn>
</PstlAdr>
<CtctDtls>
<Nm>Additional Payer Name</Nm>
<PhneNb>+404-555-1234</PhneNb>
</CtctDtls>
</Dbtr>
<DbtrAcct>
<Id>
<Othr>
<Id>674582086</Id>
</Othr>
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<ClrSysMmbId>
</ClrSysMmbId>
<PstlAdr>
<Ctry>US</Ctry>
</PstlAdr>
</FinInstnId>
</DbtrAgt>
<CdtTrfTxInf>
<PmtId>
<InstrId>Void</InstrId>
</PmtId>
<Amt>
</Amt>
<ChqInstr>
<ChqNb>1001</ChqNb>
<DlvryMtd>
<Prtry>USPS</Prtry>
</DlvryMtd>
<ChqMtrtyDt>2014-11-07</ChqMtrtyDt>
<FrmsCd>ADVCOLMN</FrmsCd>
<MemoFld>Memo</MemoFld>
</ChqInstr>
<Cdtr>
<Nm>Henry Imports</Nm>
<PstlAdr>
<StrtNm>123 Spring Ave</StrtNm>
<TwnNm>Atlanta</TwnNm>
</PstlAdr>
<CtctDtls>
<Nm>Additional Payee Name</Nm>
</CtctDtls>
</Cdtr>
<RmtInf>
<Ustrd>TX1|20130906|Invoice 112233TX1|21030907|Invoice 445566</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
Wire Transfer - Credit Transactions (PAIN.001)
The following section breaks down the allowed characters and the min / max for each field within manual entry (including templates
and edit) and transaction import:
Field Min
Max Type Notes / Comments
Originator Name 1 35 ANS Excluding forward slash (/) and back slash (\)
Originator Address 1 35 ANS Excluding forward slash (/) and back slash (\)
Amount 1 12 N Min and Max does not include thousand separators (comma) and decimal (.);
Beneficiary Name 1 35 ANS Excluding forward slash (/) and back slash (\)
Beneficiary Address 1 35 ANS Excluding forward slash (/) and back slash (\)
Beneficiary Bank Name 1 35 ANS Excluding forward slash (/) and back slash (\)
9/ N/ When FED ABA, Bank ID must be 9 digits; When SWIFT BIC, Bank ID can be an 8 or
Beneficiary Bank ID 9/8
11 AN 11 AN field
Correspondent Bank Name 1 35 ANS Excluding forward slash (/) and back slash (\)
Correspondent Bank ID 9/8
11 AN 11 AN field
Intermediary Bank Name 1 35 ANS Excluding forward slash (/) and back slash (\)
Intermediary Bank ID 9/8
11 AN 11 AN field
Reference Information for
1 16 ANS
Beneficiary
Additional Information for
1 35 ANS Outbound file allows 4 lines of 35 characters
Beneficiary
Note: Forward slash (/), back slash (\), greater than (>), and less than (<) aren’t allowed characters for any field in ISO20022 format

Field Index – Field Name – Tag Content Mandatory / Optional Description / Fedwire Mapping
tag.
<Document
instance">
Field Name – Depth / Optional Fedwire Mapping
Tag
<GrpHdr>
<MsgId>
(e.i., 2014-10-
14T14:18:30)
[Message ID].”
[MsgId].”
tag is present)
(required when
Originating
Identification
tag is present)
(required when
Other tag is
present)
Tag
<PmtInf>
Payment Information ++ Yes Mandatory Referenced in error
Identification messages that occur within
<PmtInfId> this Payment Information
Block.
Payment Method ++ Yes Mandatory Must be TRF “Payment Method is required and must be one of TRF and
<PmtMtd> Service Code must be one of URGP, URNS, BKTR. The batch
[Payment Information ID] will be skipped.”
Control Sum ++ Yes Mandatory Total dollar amount of all “The total amount of transactions expected is [reported
payment block Information ID].”
Information
<PmtTpInf>
<SvcLvl>
Code <Cd> ++++ Yes Mandatory Must be URGP, URNS, or “Payment Method is required and must be one of TRF, DD and
BKTR Service Code must be one of URGP, URNS, BKTR. The batch
Date <ReqdExctnDt>
{2000} IMAD “A wire with End to End ID [End to End ID] to [Beneficiary (last
four of beneficiary’s account number)] from [last four of
Format: YYYY-MM- originator’s account number] was sent for a payment date in the
DDTHH:MM:SS e.g. 2014- past.”
10-14T14:18:30)
the future:
“A wire with End to End ID [End to End ID] to [Beneficiary (last

originator’s account number] was sent for a payment date in the
future.”

Tag
Name <Nm> +++ Yes Required Originator Name If the tag is missing, the transaction will fail:
{5000} Originator “No value found for required field: Originator Name for [invalid
record]”

will be skipped:
Originator Name field does not validate for line 1: Field length
exceeds maximum: [invalid length] > 35
<PstlAdr>
Street Name ++++ Yes Required Originator Address 1 If the tag is missing, the transaction will fail:
<StrtNm>
{5000} Originator “No value found for required field: Originator Address 1 for
[invalid record]”

will be skipped:
“Originator Address 1 field does not validate for line 1: Field

Postal Code <PstCd> ++++ Yes Required Originator Address 2 At least one tag must be present (PstCd, TwnNm, or
CtrySubDvsn). If all three tags are missing, the transaction will
{5000} Originator be skipped:
“No value found for required field: Originator Address 2 for

Town Name ++++ Yes Required Originator Address 2 At least one tag must be present (PstCd, TwnNm, or
Country Subdivision ++++ Yes Required Originator Address 2 At least one tag must be present (PstCd, TwnNm, or

<DbtrAcct>
Identification <Id> +++++ Yes Mandatory Debit Account If missing or does not match a value in the database, the
{5000} Originator
“The account [ABA/last four of invalid account] is not permitted.
The payment with End to End ID [End to End ID] to [Beneficiary
Name (last four of beneficiary’s account)] will be skipped.”
<DbtrAgt>
Identification
<FinInstnId>
<ClrSysMmbId>
Member Identification +++++ Yes Mandatory Debit ABA If missing or does not match a value in the database, the
<MmbId> transaction will be skipped:
{3100} Sender DI
“The account [ABA/last four of invalid account] is not permitted.
Payment Information Block, By Order of Third Party Block only Required for Travel Rule purposes
Tag
Ultimate Debtor ++ Empty Tag Mandatory Must be present for By-Order-Of wire transaction, otherwise
<UltmtDbtr> optional.
The ultimate party that owes an amount of money to the
(ultimate) creditor
Name <Nm> +++ Yes Required By Order of Party Name Must be present for By-Order-Of wire transaction, otherwise
optional.
Postal Address +++ Empty Tag Mandatory Must be present for By-Order-Of wire transaction, otherwise
<PstlAdr> optional.
Information that locates and identifies a specific address, as
defined by postal services.
Street Name ++++ Yes Required Must be present for By-Order-Of wire transaction, otherwise
<StrtNm> optional.
The following error messages will be displayed on the Load
Validation Report.
“By Order Of Address 3 is missing or blank.”
Postal Code ++++ Yes Conditional Must be present for By-Order-Of wire transaction when Country
<PstCd> Code is “US”, otherwise optional.
First five positions must be NUMERIC.
If the first five positions are not numeric, the transaction will be
skipped.
The following error message will be displayed on the Load
Validation Report:
“By Order Of Postal code is invalid: <Submitted Postal Code>.
First five positions must be numeric.”
Town Name ++++ Yes Mandatory Must be present for By-Order-Of wire transaction, otherwise
<TwnNm> optional.
Free form text field limited to 18 positions. If a provided value
exceeds 18 positions, the transaction will be accepted, but City
Name will be truncated at 18.
Validation Report.
“By Order Of City name is too long and will be truncated:
<Submitted City Name>.”
Country Sub ++++ Yes Mandatory Must be present for By-Order-Of wire transaction, otherwise
Division optional.
<CtrySubDvsn>
Must be present when Country Code is “US”, otherwise
optional.
Must contain an approved two-letter state code, and is case
insensitive.
If a provided value is not an approved state code, the
transaction will be skipped.
Validation Report:
“By Order Of State code is missing.”
“By Order Of State code is not approved:
<Submitted State Code>.”
Country ++++ Yes Mandatory Must be present for By-Order-Of wire transaction, otherwise
<Ctry> optional.
Must contain an approved two-letter country code. Only upper
case characters are allowed.
If a provided value is missing or is not an approved country
code, the transaction will be skipped.
Validation Report.
“By Order Of Country code is missing.”
“By Order Of Country code is not permitted:
<Submitted Country Code>.”
tag is present)
(required when
Originating
Identification
tag is present)
Identification <Id> ++++++ Yes Conditional Must be present for By-Order-Of wire transaction, otherwise
(required when optional
Other tag is
present)
Tag
Transaction
Information
<CdtTrfTxInf>
Payment Transaction, Payment Information Section

Tag
Payment +++ Empty Tag Mandatory
Identification
<PmtId>
End to End ++++ Yes Mandatory Reference Information for Missing tag or value will cause an ISO XML-level (XSD) validation
Identification Beneficiary error and cause the file load to fail.
<EndToEndId>
{4320} Reference for
Beneficiary
<InstdAmt CCy=
“USD”> {2000} Amount Decimal, two digits after the decimal - interpreted literally, with
decimal
Decimal, one digit after the decimal, i.e. 1.2, interpreted as 1.20
“One or more records exceed the user’s [limit type exceeded] of

[limit allowed].”
If the amount exceeds 10 digit (11 characters with decimal) limit,

the file load will fail:
If InstdAmt CCY does not equal USD, the transaction will fail:
“Monetary Currency is not a valid. The wire with End to End ID
Payment Information Block, Payment Transaction, Additional Bank Information Section

Field Index – Tag Content Mandatory Description / Comments and validation
Tag
Intermediary Agent 1 +++ Empty Tag Optional
<IntrmyAgt1>
Financial Institution ++++ Empty Tag Optional
Identification
<FinInstnId>
Clearing System +++++ Empty Tag Optional
Member
Identification
<ClrSysMmbId>
Member ++++++ Yes Optional Correspondent Bank ID A valid USD International Wire Transfer is defined as routing a US
Identification dollar payment through a domestic correspondent bank with final
<MmbId> {3400} Receiver DI credit to a foreign beneficiary bank.
IMPORTANT NOTE:
For All USD Intl Wires, a correspondent bank is required. If you do
not have a specified Correspondent Bank, please default <MmbId>
to: 026005092
This will indicate Wells Fargo, Capital One Bank’s default USD
Correspondent
If the beneficiary bank routes through SWIFT, this tag must be

present. If the tag is missing, the transaction will fail:
“A wire with End to End ID [End to End ID] to [beneficiary name (last
four of beneficiary’s account number)] from [last four of originator’s
debit account] was attempted by a user who does not have the
permission to the requested action.”
“Correspondent Bank ID is not a valid ABA number: [invalid ABA].

The payment with End to End ID [End to End ID] to [beneficiary
name (last four of beneficiary’s account)] from [last four of
originator’s account] will be skipped.”
Intermediary Agent 2 +++ Empty Tag Optional
<IntrmyAgt2>
Financial Institution ++++ Empty Tag Optional
Identification
<FinInstnId>
{Or BICFI +++++ Yes Optional Intermediary Bank ID Invalid value will cause an ISO XML-level (XSD) validation error and
<BICFI> cause the file load to fail.
{4000} Intermediary FI
If payment is being routed to a domestic beneficiary with an ABA,
the intermediary bank ID must also be an ABA. If not, the
“A wire with End to End ID [End to End ID] to [beneficiary name (last
four of beneficiary’s account)] from [last four of originator’s debit
account] contained invalid routing information: Cannot use foreign
Intermediary when Beneficiary is ABA.”
Or} Clearing +++++ Empty Tag Optional
System
Member
Identification
<ClrSysMmbI
d>
Member ++++++ Yes Optional Intermediary Bank ID Must be a valid ABA number, e.g. pass MOD-10 check.
Identification
<MmbId> {4000} Intermediary FI If invalid, the transaction will fail:
“Intermediary Bank ID is not a valid ABA number: [invalid ABA]. The

payment with End to End ID [End to End ID] to [beneficiary name
(last four of beneficiary’s account)] from [last four of originator’s
account] will be skipped.”
Payment Information Block, Payment Transaction, Beneficiary Section

Field Index – Tag Content Mandatory Description / Comments and validation
Tag
Creditor Agent +++ Empty Tag Required
<CdtrAgt>
Identification
<FinInstnId>
{Or BICFI +++++ Empty Tag Required Beneficiary Bank ID Invalid SWIFT BIC will cause an ISO XML-level (XSD) validation
<BICFI> error and cause the file load to fail.
If the tag is missing, the transaction will fail:
“A wire with End to End ID [End to End ID] to [beneficiary name

account] was invalid: Invalid wire routing information, the following
fields are required for valid wire routing: Beneficiary Bank ID
and/or Beneficiary Bank ID Type”
Or} Clearing +++++ Empty Tag Required
System
Member
Identification
<ClrSysMmbI
d>
Member ++++++ Yes Required Beneficiary Bank ID Must be a valid ABA number, e.g. pass MOD-10 check.
Identification
<MmbId> {3400} Receiver ID If invalid, the transaction will fail:
Or “Beneficiary Bank ID is not a valid ABA number: [invalid ABA]. The

payment with End to End ID [End to End ID] to [beneficiary name
{4100} Beneficiary’s FI (last four of beneficiary’s account)] from [last four of originator’s
account] will be skipped.”
“A wire with End to End ID [End to End ID] to [beneficiary name

account] was invalid: Invalid wire routing information, the following
fields are required for valid wire routing: Beneficiary Bank ID
and/or Beneficiary Bank ID Type”
Name <Nm> ++++ Yes Required Beneficiary Name If the tag is missing, the transaction will fail:
{4200} Beneficiary “No value found for required field: Beneficiary Name for record
[invalid record]”
If the value of the field exceeds 35 characters, the transaction will

fail:
“Beneficiary Name field does not validate for line 1: Field length
exceeds maximum: [invalid record] > 35”
Postal Address ++++ Empty Tag Optional
<PstlAdr>
Street Name +++++ Yes Optional Beneficiary Address 1
<StrtNm>
{4200} Beneficiary
Postal Code +++++ Yes Optional Beneficiary Address 2
<PstCd>
{4200} Beneficiary
Town Name +++++ Yes Optional Beneficiary Address 2
<TwnNm>
{4200} Beneficiary
Country Subdivision +++++ Yes Optional Beneficiary Address 2
<CtrySubDvsn>
{4200} Beneficiary
Account<CdtrAcct>
Identification <Id> ++++++ Yes Required Beneficiary ID If the tag is missing, the transaction will fail:
{4200} Beneficiary “No value found for required field: Beneficiary ID for record [invalid
record]”
Remittance +++ Empty Tag Optional
Information
<RmtInf>
Unstructured ++++ Yes Optional Additional Information for
<Ustr Beneficiary
{6000} Originator to
Beneficiary Information
Sample

<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>new id</MsgId>
<InitgPty>
<Id>
<OrgId>
<Othr>
<Id>ABC</Id>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>12323</PmtInfId>
<PmtTpInf>
<SvcLvl>
<Cd>URGP</Cd>
</SvcLvl>
</PmtTpInf>
<Dbtr>
<Nm>Acme Manufacturing </Nm>
<PstlAdr>
<StrtNm>1125 NW COUCH STREET, SUITE 700</StrtNm>
<TwnNm>OMAHA</TwnNm>
<CtrySubDvsn>Nebraska</CtrySubDvsn>
</PstlAdr>
</Dbtr>
<DbtrAcct>
<Id>
<Othr>
<Id>0812121359</Id>
</Othr>
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<ClrSysMmbId>
</ClrSysMmbId>
</FinInstnId>
</DbtrAgt>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>ABC123</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="USD">350.00</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<ClrSysMmbId>
</ClrSysMmbId>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>Henry Construction</Nm>
<PstlAdr>
<StrtNm>PO BOX 542500</StrtNm>
<CtrySubDvsn>Nebraska</CtrySubDvsn>
</PstlAdr>
</Cdtr>
<CdtrAcct>
<Id>
<Othr>
<Id>123456789</Id>
</Othr>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>This is remittance information</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
List of Approved Country Codes
AD AE AF AG AI AL AM AO AQ AR AS AT AU AW AX AZ BA
BB BD BE BF BG BH BI BJ BL BM BN BO BQ BR BS BT BV
BW BY BZ CA CC CD CF CG CH CI CK CL CM CN CO CR CU
CV CW CX CY CZ DE DJ DK DM DO DZ EC EE EG EH ER ES
ET FI FJ FK FM FO FR GA GB GD GE GF GG GH GI GL GM
GN GP GQ GR GS GT GU GW GY HK HM HN HR HT HU ID IE
IL IM IN IO IQ IR IS IT JE JM JO JP KE KG KH KI KM
KN KP KR KW KY KZ LA LB LC LI LK LR LS LT LU LV LY
MA MC MD ME MF MG MH MK ML MM MN MO MP MQ MR MS MT
MU MV MW MX MY MZ NA NC NE NF NG NI NL NO NP NR NU
NZ OM PA PE PF PG PH PK PL PM PN PR PS PT PW PY QA
RE RO RS RU RW SA SB SC SD SE SG SH SI SJ SK SL SM
SN SO SR SS ST SV SX SY SZ TC TD TF TG TH TJ TK TL
TM TN TO TR TT TV TW TZ UA UG UM US UY UZ VA VC VE
VG VI VN VU WF WS YE YT ZA ZM ZW
List of Approved State Codes

1. 50 States plus District of Columbia
AL AK AZ AR CA CO CT DE DC FL GA HI ID IL IN IA KS
KY LA ME MD MA MI MN MS MO MT NE NV NH NJ NM NY NC
ND OH OK OR PA RI SC SD TN TX UT VT VA WA WV WI WY
2. Military State Codes / Armed Forces

AA AE AP
3. US Territories
AS GU MP PR
NOTE: United States Minor Outlying Islands (UM) and Virgin Islands (VI) currently are not supported.
4. Freely Associated states

MH PW
NOTE: Federated States of Micronesia (FM) currently is not supported.
Wire Drawdown - Debit Transactions (PAIN.008)
This section outlines the PAIN.008 file format that will be accepted by Messenger Financial Center.

Field Index – Field Name – Tag Content Mandatory / Optional Description / Fedwire Mapping
tag.
<Document The contents of Debit messages are validated using the

xmlns="urn:iso:std:iso:20022:tech:xsd:pain.008.001.0 Version 3 xsd.
3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance">
<CstmrDrctDbtInitn> Empty Tag Mandatory This tag must always be placed before the group header tag
Field Index – Field Tag Depth Content Mandatory / Description / Fedwire Processing Rules / Error Messages
Name – Tag Optional Mapping
<GrpHdr>
Message ++ Yes Mandatory Stored and used in pain.002 – acknowledgements as the
Identification Original Message ID - OrgnlMsgId
<MsgId>
(e.i., 2014-10-
14T14:18:30)
[Message ID].”
[MsgId].”
Initiating Party ++ Empty Tag Mandatory
<InitgPty>
Name <Nm> +++ Yes Required Originator Name If the tag is missing, the transaction will fail:
{5000} Originator “No value found for required field: Originator Name for [invalid
record]”
will fail:
“Originator Name field does not validate for [invalid line]: Field
<PstlAdr>
Street Name ++++ Yes Required Originator Address 1 If the tag is missing, the transaction will fail:
<StrtNm>
{5000} Originator “No value found for required field: Originator Address 1 for
[invalid record]”

will fail:
“Originator Address [invalid record count] field does not validate

for invalid line]: Field length exceeds maximum: [invalid length]
> 35”
Postal Code ++++ Yes Required Originator Address 2 At least one tag must be present (PstCd, TwnNm, or
<PstCd> CtrySubDvsn). If all three tags are missing, the transaction will
{5000} Originator fail:
“No value found for required field: Originator Address [invalid

record count] for record [invalid record]”
Town Name ++++ Yes Required Originator Address 2 At least one tag must be present (PstCd, TwnNm, or

Country Subdivision ++++ Yes Required Originator Address 2 At least one tag must be present (PstCd, TwnNm, or

Identification
<OrgId>
Identification <Id> ++++++ Yes Required Debit Account If missing or does not match a value in the database, the
(Originator’s Account) transaction will fail:
{5000} Originator “The account [ABA/last four of invalid account] is not permitted.
Issuer <Issr> ++++++ Yes Required Debit Account If value does not match a value in the database, the transaction
(Originator’s ABA) will fail:
{3100} Sender DI “The account [ABA/last four of invalid account] is not permitted.
“Wire Drawdown Account ABA missing or blank. The wire with

<PmtInf>
Payment Information ++ Yes Mandatory Referenced in error
Identification messages that occur within
<PmtInfId> this Payment Information
Block.
Payment Method ++ Yes Mandatory Must be DD “Payment Method is required and must be one of DD and
<PmtMtd> Service Code must be one of URGP, URNS, BKTR. The batch
Control Sum ++ Yes Mandatory Total dollar amount of all “The total amount of transactions expected is [reported
payment block Information ID].”
Information
<PmtTpInf>
<SvcLvl>
Code <Cd> ++++ Yes Mandatory Must be URGP, URNS, or “Payment Method is required and must be one of TRF, DD and
BKTR Service Code must be one of URGP, URNS, BKTR. The batch
Requested Collection ++ Yes Mandatory Payment Date If date is a date in the past, the transaction will fail:
Date <ReqdColltnDt>
{1520} IMAD “A wire with End to End ID [End to End ID] to [Beneficiary (last
originator’s account number] was sent for a payment date in
the past.”
Format: YYYY-MM-
DDTHH:MM:SS e.g. 2014- If the date exceeds the maximum allowed number of days in
10-14T14:18:30) the future, the transaction will fail:
“A wire with End to End ID [End to End ID] to [Beneficiary (last

originator’s account number] was sent for a payment date in
the future.”
Payment Information Block, Beneficiary Section

Creditor <Cdtr> ++ Empty tag Mandatory
Name <Nm> +++ Yes Required Beneficiary Name If the tag is missing, the transaction will fail:
{4200} Beneficiary “No value found for required field: Beneficiary Name for record
[invalid record]”

will fail:
“Beneficiary Name field does not validate for [invalid line]: Field
Postal Address +++ Empty Tag Optional
<PstlAdr>
Street Name ++++ Yes Optional Beneficiary Address 1
<StrtNm>
{4200} Beneficiary
Postal Code <PstCd> ++++ Yes Optional Beneficiary Address 2
{4200} Beneficiary
Town Name ++++ Yes Optional Beneficiary Address 2

<TwnNm>
{4200} Beneficiary
Country Subdivision ++++ Yes Optional Beneficiary Address 2

<CtrySubDvsn>
{4200} Beneficiary
Creditor Account ++ Empty tag Mandatory

<CdtrAcct>
Identification <Id> +++++ Yes Mandatory Beneficiary Account If the tag is missing, the transaction will fail:
{4200} Beneficiary “No value found for required field: Beneficiary ID for record
[invalid record]”
Creditor Agent ++ Empty Tag Mandatory
<CdtrAgt>
Identification
<FinInstnId>
<ClrSysMmbId>
Member Identification +++++ Yes Mandatory Beneficiary ABA Must be a valid ABA number, e.g. pass MOD-10 check.
<MmbId>
{5400} Account Credited in If invalid, the transaction will fail:
Drawdown
“Beneficiary Bank ID is not a valid ABA number: [invalid ABA].
The payment with End to End ID [End to End ID] to
[beneficiary name (last four of beneficiary’s account)] from [last
four of originator’s account] will be skipped.”
“A wire with End to End ID [End to End ID] to [beneficiary

name (last four of beneficiary’s account)] from [last four of
originator’s account] was invalid: Invalid wire routing
information, the following fields are required for valid wire
routing: Beneficiary Bank ID and/or Beneficiary Bank ID Type”

Direct Debit ++ Empty Tag Mandatory
Transaction
Information
<DrctDbtTxInf>
Field Index – Field Name Tag Depth Content Mandatory / Description / Fedwire Processing Rules / Error Messages
– Tag Optional Mapping
<PmtId>
End to End Identification ++++ Yes Mandatory Reference Information for Missing tag or value will cause an ISO XML-level (XSD)
<EndToEndId> Beneficiary validation error and cause the file load to fail.
{4320} Reference for

Beneficiary
{2000} Amount Decimal, two digits after the decimal - interpreted literally,
with decimal

1.20
If dollar amount is improperly formatted, the transaction will

fail:
“A wire with End to End ID [End to End ID] to [beneficiary

(last four of beneficiary’s account)] from [last four of
originator’s account] was sent with an invalid amount.”

limit, the transaction will fail:
“Amount field does not validate for line [invalid record count]:
If the transaction exceeds the user’s Daily Transaction

Count per Account, the file load will fail:
“A payment with End to End ID [End to End ID] to

[beneficiary (last four of beneficiary’s account)] from [last
four of originator’s account] failed for the following limit
violations: User's Per Account Total Daily Wire Transaction
Count Limit [limit] exceeded.”
If InstdAmt CCY does not equal USD, the transaction will
fail:
“Monetary Currency is not valid. The wire with End to End ID

Payment Information Block, Payment Transaction, Ultimate Debit Party Section

Field Index – Field Tag Depth Content Mandatory / Description / Fedwire Comments and validation
Debtor Agent <DbtrAgt> +++ Empty Tag Required
Identification
<FinInstnId>
Clearing System +++++ Empty Tag Required
<ClrSysMmbId>
Member Identification ++++++ Yes Required Ultimate Debit Party ABA Must be a valid ABA number, e.g. pass MOD-10 check. If
<MmbId> not, the transaction will fail:
{3400} Receiver ID
(receiver of the drawdown “A wire with End to End ID [End to End ID] to [beneficiary
request) (last four of beneficiary’s account)] from [originator’s
account] contained an invalid ABA number.”
Debtor <Dbtr> +++ Empty Tag Required

Name <Nm> ++++ Yes Required Ultimate Debit Party If the tag is missing, the transaction fill fail:
{4400} Account Debited in Wire Drawdown Ultimate Debit Party missing or blank.
Drawdown The wire with End to End ID [End to End ID] will be
skipped.

“Ultimate Debit Party field does not validate for line

[invalid line count]: Field length exceeds maximum:
[invalid length] > 35”
Debtor +++ Empty Tag Required
Account<DbtrAcct>
Identification <Id> ++++++ Yes Required Ultimate Debit Account If the tag is missing, the transaction will fail:
{4400} Account Debited in “Wire Drawdown Ultimate Debit Account missing or

Drawdown blank. The wire with End to End ID [End to End ID] to
[Beneficiary (last four of beneficiary’s account number)]
will be skipped.”
Remittance Information +++ Empty Tag Optional

<RmtInf>
Unstructured ++++ Yes Optional Additional Information for
<Ustrd> Beneficiary
{6000} Originator to
Beneficiary Information
Sample

<CstmrDrctDbtInitn>
<GrpHdr>
<MsgId>NEW ID</MsgId>
<InitgPty>
<Nm>ORIGINATOR</Nm>
<PstlAdr>
<StrtNm>1776 PEACHTREE ST NW</StrtNm>
<PstCd>30309</PstCd>
<TwnNm>ATLANTA</TwnNm>
</PstlAdr>
<Id>
<OrgId>
<Othr>
<Id>0812121359</Id>
<Issr>065000090</Issr>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>12323</PmtInfId>
<PmtMtd>DD</PmtMtd>
<PmtTpInf>
<SvcLvl>
<Cd>URGP</Cd>
</SvcLvl>
</PmtTpInf>
<ReqdColltnDt>2015-02-23</ReqdColltnDt>
<Cdtr>
<Nm>BENEFICIARY</Nm>
<PstlAdr>
<StrtNm>1125-88 NW COUCH STREET, SUITE 700</StrtNm>
<TwnNm>PORTLAND</TwnNm>
<CtrySubDvsn>OR</CtrySubDvsn>
</PstlAdr>
</Cdtr>
<CdtrAcct>
<Id>
<Othr>
<Id>0812121359</Id>
</Othr>
</Id>
</CdtrAcct>
<CdtrAgt>
<FinInstnId>
<ClrSysMmbId>
</ClrSysMmbId>
</FinInstnId>
</CdtrAgt>
<DrctDbtTxInf>
<PmtId>
<EndToEndId>ABC123</EndToEndId>
</PmtId>
<DbtrAgt>
<FinInstnId>
<ClrSysMmbId>
</ClrSysMmbId>
</FinInstnId>
</DbtrAgt>
<Dbtr>
<Nm>DEBIT PARTY</Nm>
<PstlAdr>
<StrtNm>PO BOX 542500</StrtNm>
<CtrySubDvsn>NEBRASKA</CtrySubDvsn>
</PstlAdr>
</Dbtr>
<DbtrAcct>
<Id>
<Othr>
<Id>586521453</Id>
</Othr>
</Id>
</DbtrAcct>
<RmtInf>
<Ustrd>REMITTANCE INFORMATION</Ustrd>
</RmtInf>
</DrctDbtTxInf>
</PmtInf>
</CstmrDrctDbtInitn>
</Document>
Virtual Card Payment Transactions (PAIN.001)

Field Index – Field Name – Tag Content Mandatory / Optional Description / Harland Mapping
tag.
<Document
instance">
Tag
<GrpHdr>
<MsgId>
(e.i., 2014-10-
14T14:18:30)
[Message ID].”
[MsgId].”
tag is present)
(required when
Originating
Identification
tag is present)
(required when
Other tag is
present)
Field Name – Depth Optional Harland Mapping
Tag
<PmtInf>
Identification
<PmtInfId>
Payment Method ++ Yes Mandatory Must be TRF “Payment Method is required and must be TRF. The batch
<PmtMtd> [Payment Information ID] will be skipped.”
Control Sum ++ Yes Mandatory Total dollar amount of all The total amount of transactions expected is [reported
payment block Information ID].
Information
<PmtTpInf>
<SvcLvl>
Code <Cd> ++++ Yes Mandatory Must be NUGP Fail the TRANSACTION using the following message if the
payment method is invalid:
“Payment Method is required and must be one of TRF and

Service Code must be one of NUGP. The Card Payment
Requested Execution ++ Yes Mandatory Processing Date Each error will result in a TRANSACTION failure / skip.
Date <ReqdExctnDt>
NOT PASSED IN Format = YYYY-MM-DD
VERIENT FILE; USED
FOR FILE PROCESSING A date in the past is not allowed.
Format= YYYY-MM-DD “Verient card payment was sent for a date before the next
available payment date. The payment will be skipped.”
Date may be a working or non-working date.
Future dated payments are allowed but must be within the

banks defined maximum allowed number of days in the future.
“Processing Date [date in mm/dd/yyyy format] for Verient card

payment exceeds the number of allowed days in the future of
[limit]. The payment will be skipped.”
Payment Information Block, Vendor ID Section


Originating Identification ++++ Empty Tag Required
<OrgId>
Identification <Id> ++++++ Yes Required Client ID Must match the Client ID within the database. Import user
must be entitled to initiate Credit Card Payments for that
Client ID. Valid characters include a – z, A – Z, 0 – 9,
hyphens, single-quote, ampersand, period, and under-
score.
If there is a single card payment in the file and the Client ID

is invalid, the TRANSACTION will be skipped.
If there is more than one card payment in the file and the
Client ID for one or more transactions is invalid, the FILE
will fail.
“The Client ID [Client ID] for a Verient card payment is

invalid. The payment for record number [record number]
will be skipped.”
“Client ID [Client ID] is not valid for Verient Card

Transactions as it must be between 1 and 16 characters in
length. The payment for record number [record number]
will be skipped.”
Client ID field does not validate for line [line number]: Field
length exceeds maximum: 17 > 16
<DbtrAcct>
Identification <Id> +++++ Yes Required Missing tag or value will cause an ISO XML-level (XSD)
validation error and cause the file load to fail.
Debtor Agent <DbtrAgt> ++ Empty Tag Mandatory
Clearing System Member ++++ Empty Tag Mandatory
Identification
<ClrSysMmbId>
Member Identification +++++ Yes Mandatory Missing tag or value will cause an ISO XML-level (XSD)
<MmbId> validation error and cause the file load to fail.

Tag
Transaction
Information
<CdtTrfTxInf>

<PmtId>
Instructed Amount ++++ Yes Mandatory Amount Format validated, but not used.
Order Record, Check- No decimal - amount treated as whole number
Amount
Decimal, two digits after the decimal - interpreted literally,
with decimal
1.20
Amounts loaded with no decimal will be interpreted as whole

amounts, i.e .100 = 100.00
If the amount exceeds 10 digits (11 characters with decimal)

limit, fail the FILE with the following error message:
“Amount field does not validate for line [line number]: Field
Payment Information Block, Payment Transaction, Vendor ID Section
If more than one Vendor is included within a single payment, the file load will fail with the following error: “Error validating ISO file.
Found issue on line [line] column [column]. cvc-complex-type.2.4.d: Invalid content was found starting with element 'Cdtr'. No child
element is expected at this point.”
OrganizationIdentification +++++ Empty Tag Required
<OrgId>
Other <Othr> ++++++ Empty Tag Required
Identification <Id> +++++++ Yes Required Vendor ID Valid characters for this field include: a- z, A- Z, 0 -
1, hyphens, single-quote, ampersand, period, and under-
score.
If the tag is missing, fail the TRANSACTION:
“Vendor ID missing. The payment with End to End ID [End

to End ID] will be skipped.”
Payment Information Block, Payment Transaction, Remittance/Invoice Section
If more than one RMR is found with a single payment, the file load will fail with the following error: “Error validating ISO file. Found
issue on line [line] column [column]. cvc-complex-type.2.4.d: Invalid content was found starting with element 'RmtInf'. No child element
is expected at this point.”
Field Index – Field Name – Tag Content Mandatory Description / Processing Rules / Error Messages
Tag Depth / Optional Harland Mapping
Remittance Information <RmtInf> +++ Empty Tag Optional
Unstructured ++++ Yes Optional UDF1 If the value of the field exceeds 130 characters, fail
<Ustrd> the TRANSACTION:
“User Defined Field 1 field length exceeds maximum:

[invalid length] > 130. The payment with End to End







“User Defined Field 10 field length exceeds

maximum: [invalid length] > 130. The payment with





Structured <Strd> +++ Empty Tag Required
ReferredDocumentationInformation ++++ Empty Tag Required
<RfrdDocInf>
Type <Tp> +++++ Empty Tag Required
CodeOrProprietary <CdOrPrtry> ++++++ Empty Required
Tag
Code <Cd> ++++++ Yes Required “CINV” Not validated, but indicates the type of document
referenced in this transaction. Valid code value is
“CINV” = Commercial Invoice
Number <Nb> +++++ Yes Required Invoice Number If the tag is missing, fail the TRANSACTION:
“Invoice Number is missing. The payment with End to

End ID [End to End ID] will be skipped.”
RelatedDate <RltdDt> +++++ Yes Required Invoice Date Each error will result in a FILE failure.
Must be in a valid ISO date format = YYYY-MM-DD
If the format is incorrect, the load will fail with:

“The Invoice Payment Date, is invalid. The payment
F the Invoice Date is missing, the load will fail with:

“Error validating ISO file. Found issue on line 153
column 32. cvc-datatype-valid.1.2.1: '201608-17' is
not a valid value for 'date'.”
Invoice Date is not validated, other than format

ReferredDocumentAmount ++++ Empty Tag Required Includes the attribute: “Ccy”=”USD”
<RfrdDocAmt>
DuePayableAmount +++++ Yes Required Invoice Amount No decimal - amount treated as whole number
<DuePyblAmt>
Decimal, two digits after the decimal - interpreted
literally, with decimal
Decimal, one digit after the decimal, i.e. 1.2,

interpreted as 1.20
Amounts loaded with no decimal will be interpreted

as whole amounts, i.e .100 = 100.00
If the transaction exceeds the user’s limits, fail the

FILE with the following error message:
“One or more records exceed the user’s [limit type

exceeded] of [limit allowed].”
If the amount exceeds 10 digits (11 characters with

decimal) limit, fail the FILE with the following error
message:
“Amount field does not validate for line [line number]:

If the Invoice Amount is missing, the TRANSACTION

will be skipped and the following error displayed:
“Invoice amount could not be found. The payment
The payment with End to End [end to end ID] will be
skipped.”
Virtual Card Payments – Important Notes
• Virtual Card payments should be created on a 1 to 1 basis based on invoice #. For XML, please use <DuePyblAmt> tag amount
per invoice.
• Multiple Virtual Card Master Account #’s are supported for Integrated Payables, but separate files per Master Account #’s are
required. Multiple Master Account #’s cannot be combined into one (1) file.
Sample
<?xml version="1.0" encoding="UTF-8"?>
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>Acme Card</MsgId>
<InitgPty>
<Id>
<OrgId>
<Othr>
<Id>INITG PTY ID - NOT USED</Id>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>PMT INF ID - NOT USED</PmtInfId>
<PmtTpInf>
<SvcLvl>
<Cd>NUGP</Cd>
</SvcLvl>
</PmtTpInf>
<Dbtr>
<Id>
<OrgId>
<Othr>
<Id>1234234534564567</Id>
</Othr>
</OrgId>
</Id>
</Dbtr>
<DbtrAcct>
<Id>
<Othr>
<Id>DUMMY DEBTOR DATA - NOT USED</Id>
</Othr>
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<ClrSysMmbId>
<MmbId>DUMMY DEBTOR FI DATA - NOT USED</MmbId>
</ClrSysMmbId>
</FinInstnId>
</DbtrAgt>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>END TO END ID - NOT USED</EndToEndId>
</PmtId>
<Amt>
</Amt>
<Cdtr>
<Id>
<OrgId>
<Othr>
<Id>Vendor1ISO</Id>
</Othr>
</OrgId>
</Id>
</Cdtr>
<RmtInf>
<Ustrd>User Defined Fields 1</Ustrd>
<Strd>
<RfrdDocInf>
<Tp>
<CdOrPrtry>
<Cd>CINV</Cd>
</CdOrPrtry>
</Tp>
<Nb>2016-1002</Nb>
<RltdDt>2016-08-09</RltdDt>
</RfrdDocInf >
<RfrdDocAmt>
<DuePyblAmt Ccy=”USD”>71000</DuePyblAmt>
</RfrdDocAmt>
</Strd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>

XML Payment Order File Spec

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

XML Payment Order File Spec

Hochgeladen von

Copyright:

Verfügbare Formate

Payables

ISO 20022 Payment Order–

VERSION 3.2  OCT, 2020

Document Overview ............................................................................................................... 3

Note about document structure:

Tag Depth Structure

PAIN.001 and PAIN.008 can support the following characters:

Document Header - this can only occur once per file

Payment Information Block, Debit ABA & Account Section

“The account [invalid account] is not permitted. The

“The account [invalid account] is not permitted. The

Must be a valid ABA number, e.g. pass MOD-10 check.

If invalid, the transaction will fail:

“Debit ABA [invalid ABA] is not a valid ABA number. The

Payment Information Block, Payment Transaction, Payment Information Section

If the transaction exceeds the user’s limits, the transaction will

“One or more records exceed the user’s [limit type exceeded]

If the amount exceeds 8 digit (9 characters with decimal) limit,

“Monetary Currency is not valid. The check with End to End ID

“The account [invalid account] is not permitted. The payment

Must be a valid ABA number, e.g. pass MOD-10 check.

If invalid, the transaction will fail:

“Credit ABA [invalid ABA] is not a valid ABA number. The

“The account [invalid account] is not permitted. The payment

Payment Information Block, Payment Transaction, Memo Section

Document Header - this can only occur once per file

Format: YYYY-MM- If date is a date in the past, but in a different year:

If the date exceeds the maximum allowed number of days in

Payment Information Block, Originator Section

Identification <Id> +++ Empty Tag Required

“The ACH Company [invalid ACH Company ID] for the

“The ACH Company [invalid ACH Company ID] is not

“Credit [SEC] payments are not supported by [invalid ACH

If missing or does not match a value in the database, the

“ACH Company [ACH Company] for the payment with End to

If missing or does not match a value in the database, the

“ACH Company [ACH Company] for the payment with End to

If no offset defined for the ACH Company, the ID record is

Payment Information Block, Payment Transaction Section

Payment Information Block, Payment Transaction, Payment Information Section

Decimal, one digit after the decimal, i.e. 1.2, interpreted as

“One or more records exceed the user’s [limit type exceeded]

If the amount exceeds 10 digit (11 characters with decimal)

Zero Dollar Rule:

If zero dollar, PmtInf.LclInstrm.Cd (SEC Code) must be CTX or

“Monetary Amount may only be zero for CTX or CCD SEC

CCD, CTX, PPD, -

“Account Type is required. The payment with End to End ID

If the receiver account type is invalid, the transaction will be

“Invalid payee account type: [account type]. The payment with

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

Document Header - this can only occur once per file

<Document The contents of Debit messages are validated using the

For Recurring occurrence transactions, the system accepts the

RCUR (Recurring payment)

If the payment includes a value other than those listed above,

Format: YYYY-MM- If date is a date in the past, but in a different year:

If the date exceeds the maximum allowed number of days in

“An ACH [SEC Code] batch for ACH company [ACH

Payment Information Block, Originator Section

“The ACH Company [invalid ACH Company ID] for the

“The ACH Company [invalid ACH Company ID] is not

“Debit [SEC] payments are not supported by [invalid ACH

If missing or does not match a value in the database, the