Professional Documents
Culture Documents
XML Payment Order File Spec
XML Payment Order File Spec
Integrated Payables
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
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 2 of 79
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.
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.
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 3 of 79
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
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.
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 4 of 79
Supported Characters
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
& &
< <
> >
“ "
‘ '
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 5 of 79
Account Transfer Credit Transactions (PAIN.001)
This section outlines the PAIN.001 file format that will be accepted by Capital One Bank.
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
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Account Transfer
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)
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 7 of 79
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.”
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 8 of 79
Payment Information Block, Payment Transaction Section
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Account Transfer
Tag Mapping
Credit Transfer ++ Empty Tag Mandatory
Transaction
Information
<CdtTrfTxInf>
Decimal, one digit after the decimal, i.e. 1.2, interpreted as 1.20
“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:
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 9 of 79
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
Identification <FinInstnId>
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:
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 10 of 79
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>
<NbOfTxs>1</NbOfTxs>
<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>
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 11 of 79
<CdtTrfTxInf>
<PmtId>
<EndToEndId>1-0001239</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="USD">3000</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<ClrSysMmbId>
<MmbId>065000090</MmbId>
</ClrSysMmbId>
</FinInstnId>
</CdtrAgt>
<CdtrAcct>
<Id>
<Othr>
<Id>0812121359</Id>
</Othr>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>Memo</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
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 12 of 79
ACH Credit Transactions (PAIN.001)
This section outlines the PAIN.001 file format that will be accepted by Capital One Bank.
Group Header Block – this can only occur once per file
Field Index – Tag Content Mandatory / Description / Processing Rules / Error Messages
Field Name – Depth Optional NACHA
Tag Mapping
Group Header + Empty Tag Mandatory
<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)
Number of ++ Yes Mandatory Number of individual An amount mismatch will cause the file load to fail:
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].”
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 13 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
Field Index – Tag Content Mandatory / Description / Processing Rules / Error Messages
Field Name – Depth Optional NACHA
Tag Mapping
Payment Information + Empty Tag Mandatory
<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
Information ID] will be skipped.”
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
Information ID] will be skipped.”
Local Instrument +++ Empty Tag Mandatory
<LclInstrm>
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 14 of 79
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.”
“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].”
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 15 of 79
Originating ++++ Empty Tag Required
Identification <OrgId>
Other <Othr> +++++ Empty Tag Required
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””
“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].”
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 16 of 79
If no offset is defined for the ACH Company, the ID record is
skipped.
Debtor Agent ++ Empty Tag Mandatory
<DbtrAgt>
Financial Institution +++ Empty Tag Mandatory
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.
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 17 of 79
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
Instructed Amount ++++ Yes Mandatory Amount No decimal - amount treated as whole number
<InstdAmt CCy=
“USD”> Entry Detail, Decimal, two digits after the decimal - interpreted literally, with
positions 30 - 39 decimal
If the transaction exceeds the user’s limits, the file load will fail:
“Amount field does not validate for line 1: Field length exceeds
maximum: [invalid length] > 10”
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 18 of 79
Payment Information Block, Payment Transaction, Receiver Section
Field Index – Tag Content Mandatory / Description / Comments and validation
Field Name – Depth Optional NACHA
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.
CIE - positions 55 –
76
Creditor +++ Empty Tag Required
Account<CdtrAcct>
Identification <Id> ++++ Empty Tag Required
Other <Othr> +++++ Empty Tag Required
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:
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 19 of 79
DDA, SAV, GL, If the group tag containing the receiver account type (Tp.Prtry)
LOAN is missing, the transaction will be skipped:
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 20 of 79
Sample
<?xml version="1.0" encoding="UTF-8" ?>
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 21 of 79
<Id>3052516569</Id>
</Othr>
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<ClrSysMmbId>
<MmbId>111111118</MmbId>
</ClrSysMmbId>
</FinInstnId>
</DbtrAgt>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>0200000</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="USD">2416.00</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<ClrSysMmbId>
<MmbId>061000104</MmbId>
</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>
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 22 of 79
ACH Debit Transactions (PAIN.008)
This section outlines the debit PAIN.008 file format that will be accepted by Capital One Bank.
Group Header Block – this can only occur once per file
Field Index – Tag Content Mandatory / Description / Processing Rules / Error Messages
Field Name – Depth Optional NACHA
Tag Mapping
Group Header + Empty Tag Mandatory
<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)
Number of ++ Yes Mandatory Number of individual An amount mismatch will cause the file load to fail:
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].”
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 23 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
Field Index – Tag Content Mandatory / Description / Error Validation Message
Field Name – Depth Optional NACHA
Tag Mapping
Payment Information + Empty Tag Mandatory
<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
Information ID] will be skipped.”
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
ACH) and Service Code must be one of NURG. The batch [Payment
Information ID] will be skipped.”
Local Instrument +++ Empty Tag Required
<LclInstrm>
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 24 of 79
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)
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 25 of 79
the allowed number of days in the future, the payment date
must be before [calculated maximum processing date].”
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 26 of 79
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].”
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 27 of 79
Payment Information Block, Payment Transaction Section
Field Index – Tag Content Mandatory / Description / Processing Rules / Error Messages
Field Name – Depth Optional NACHA
Tag Mapping
Direct Debit ++ Empty Tag Mandatory
Transaction
Information
<DrctDbtTxInf>
If the transaction exceeds the user’s limits, the file load will fail:
“Amount field does not validate for line 1: Field length exceeds
maximum: [invalid length] > 10”
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 28 of 79
“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
Member Identification
<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
with End to End ID [End to End ID] will be skipped.”
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
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.
CIE - positions 55 -
76
Debtor +++ Empty Tag Mandatory
Account<DbtrAcct>
Identification <Id> ++++ Empty Tag Mandatory
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 29 of 79
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:
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 30 of 79
Sample
<?xml version="1.0" encoding="UTF-8" ?>
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 31 of 79
<Ccy>USD</Ccy>
</CdtrAcct>
<CdtrAgt>
<FinInstnId>
<ClrSysMmbId>
<MmbId>111111118</MmbId>
</ClrSysMmbId>
<PstlAdr>
<Ctry>US</Ctry>
</PstlAdr>
</FinInstnId>
</CdtrAgt>
<DrctDbtTxInf>
<PmtId>
<EndToEndId>112235</EndToEndId>
</PmtId>
<InstdAmt Ccy="USD">1000</InstdAmt>
<DbtrAgt>
<FinInstnId>
<ClrSysMmbId>
<MmbId>021000021</MmbId>
</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>
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 32 of 79
Check Print Transactions (PAIN.001)
This section outlines the PAIN.001 file format that will be accepted by Capital One Bank.
Group Header Block – this can only occur once per file
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Harland Mapping
Tag
Group Header + Empty Tag Mandatory
<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 and time
<CreDtTm> YYYY-MM-DDTHH:MM:SS
(e.i., 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 33 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
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Harland Mapping
Tag
Payment Information + Empty Tag Mandatory
<PmtInf>
Payment Information ++ Yes Mandatory Not Used
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.”
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
<CtrlSum> transactions for this amount], found [calculated amount] for PmtInfId [Payment
payment block Information ID].
Requested Execution ++ Yes Mandatory Payment Date If date is a date in the past, the transaction will fail:
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.”
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 34 of 79
Payment Information Block, Payer Section
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Harland Mapping
Tag
Debtor <Dbtr> ++ Empty tag Mandatory
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]”
“Payer field does not validate for line 1: Field length exceeds
maximum: [invalid length] > 50”
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
“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
“No value found for required field: Payer Address Line 3 for
record [invalid record]”
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
“No value found for required field: Payer Address Line 3 for
record [invalid record]”
Contact Details +++ Empty Tag Optional
<CtctDtls>
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 35 of 79
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
length exceeds maximum: [invalid length] > 30”
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
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 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.”
Debtor Agent ++ Empty Tag Mandatory
<DbtrAgt>
Financial Institution +++ Empty Tag Mandatory
Identification
<FinInstnId>
Clearing System ++++ Empty Tag Mandatory
Member Identification
<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.”
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 36 of 79
Payment Information Block, Payment Transaction Section
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Harland Mapping
Tag
Credit Transfer ++ Empty Tag Mandatory
Transaction
Information
<CdtTrfTxInf>
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 37 of 79
Payment Information Block, Payment Transaction, Check Details Section
Field Index – Field Tag Content Mandatory / Description / Processing Rules / Error Messages
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:
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
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 38 of 79
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, Payee- “No value found for required field: Payee for record [invalid
Name record]”
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
length exceeds maximum: [invalid length] > 50”
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
record [invalid record]”
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 39 of 79
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
Order Record, Payee- will fail:
Address
“No value found for required field: Payee Address Line 3 for
record [invalid record]”
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
Order Record, Payee- will fail:
Address
“No value found for required field: Payee Address Line 3 for
record [invalid record]”
Contact Details ++++ Empty Tag Optional
<CtctDtls>
Name <Nm> +++++ Yes Optional Additional Payee Name If the value of the field exceeds 29 characters, the
transaction will fail:
Order Record, Payee-
Name “Additional Payee Name field does not validate for line 1:
Field length exceeds maximum: [invalid length] > 29”
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 40 of 79
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>Acme Check</MsgId>
<CreDtTm>2014-12-01T14:08:05</CreDtTm>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>4000</CtrlSum>
<InitgPty>
<Id>
<OrgId>
<Othr>
<Id>ABC</Id>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>B2</PmtInfId>
<PmtMtd>CHK</PmtMtd>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>4000.00</CtrlSum>
<ReqdExctnDt>2014-11-24</ReqdExctnDt>
<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>
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 41 of 79
<FinInstnId>
<ClrSysMmbId>
<MmbId>111111118</MmbId>
</ClrSysMmbId>
<PstlAdr>
<Ctry>US</Ctry>
</PstlAdr>
</FinInstnId>
</DbtrAgt>
<CdtTrfTxInf>
<PmtId>
<InstrId>Void</InstrId>
<EndToEndId>20</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="USD">4000</InstdAmt>
</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>
<PstCd>68154-8500</PstCd>
<TwnNm>Atlanta</TwnNm>
<CtrySubDvsn>GA</CtrySubDvsn>
</PstlAdr>
<CtctDtls>
<Nm>Additional Payee Name</Nm>
</CtctDtls>
</Cdtr>
<RmtInf>
<Ustrd>TX1|20130906|Invoice 112233TX1|21030907|Invoice 445566</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
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 42 of 79
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 (\)
9/ N/ When FED ABA, Bank ID must be 9 digits; When SWIFT BIC, Bank ID can be an 8 or
Correspondent Bank ID 9/8
11 AN 11 AN field
Intermediary 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
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
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 43 of 79
This section outlines the PAIN.001 file format that will be accepted by Capital One Bank.
Group Header Block – this can only occur once per file
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Fedwire Mapping
Tag
Group Header + Empty Tag Mandatory
<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 and time
<CreDtTm> YYYY-MM-DDTHH:MM:SS
(e.i., 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
Originating ++++ Empty Tag Conditional
Identification (required when
<OrgId> Identification
tag is present)
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 44 of 79
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
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Fedwire Mapping
Tag
Payment Information + Empty Tag Mandatory
<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.”
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
<CtrlSum> transactions for this amount], found [calculated amount] for PmtInfId [Payment
payment block Information ID].”
Payment Type ++ Empty Tag Mandatory
Information
<PmtTpInf>
Service Level +++ Empty Tag Mandatory
<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
[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>
{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)
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 45 of 79
If the date exceeds the maximum allowed number of days in
the future:
{5000} Originator “No value found for required field: Originator Name for [invalid
record]”
Originator Name field does not validate for line 1: Field length
exceeds maximum: [invalid length] > 35
Postal Address +++ Empty Tag Required
<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]”
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 46 of 79
“No value found for required field: Originator Address 2 for
record [invalid record]”
Country Subdivision ++++ Yes Required Originator Address 2 At least one tag must be present (PstCd, TwnNm, or
<CtrySubDvsn> CtrySubDvsn). If all three tags are missing, the transaction will
{5000} Originator be skipped:
Payment Information Block, By Order of Third Party Block only Required for Travel Rule purposes
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Fedwire Mapping
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.
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 47 of 79
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.
The following error messages will be displayed on the Load
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.
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 48 of 79
If a provided value is not an approved state code, the
transaction will be skipped.
The following error messages will be displayed on the Load
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.
The following error messages will be displayed on the Load
Validation Report.
“By Order Of Country code is missing.”
“By Order Of Country code is not permitted:
<Submitted Country Code>.”
Identification <Id> +++ Empty Tag Optional
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 Must be present for By-Order-Of wire transaction, otherwise
(required when optional
Other tag is
present)
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 49 of 79
Payment Information Block, Payment Transaction Section
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Fedwire Mapping
Tag
Credit Transfer ++ Empty Tag Mandatory
Transaction
Information
<CdtTrfTxInf>
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:
“Amount field does not validate for line 1: Field length exceeds
maximum: [invalid length] > 10”
If InstdAmt CCY does not equal USD, the transaction will fail:
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 50 of 79
“Monetary Currency is not a valid. The wire with End to End ID
[End to End ID] will be skipped.”
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
“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.”
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 51 of 79
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
transaction will fail:
“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:
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 52 of 79
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:
{4200} Beneficiary “No value found for required field: Beneficiary Name for record
[invalid record]”
“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
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 53 of 79
Country Subdivision +++++ Yes Optional Beneficiary Address 2
<CtrySubDvsn>
{4200} Beneficiary
Creditor +++ Empty Tag Required
Account<CdtrAcct>
Identification <Id> ++++ Empty Tag Required
Other <Othr> +++++ Empty Tag Required
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
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 54 of 79
Sample
<?xml version="1.0" encoding="UTF-8" ?>
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 55 of 79
<DbtrAgt>
<FinInstnId>
<ClrSysMmbId>
<MmbId>111111118</MmbId>
</ClrSysMmbId>
</FinInstnId>
</DbtrAgt>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>ABC123</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="USD">350.00</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<ClrSysMmbId>
<MmbId>111111118</MmbId>
</ClrSysMmbId>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>Henry Construction</Nm>
<PstlAdr>
<StrtNm>PO BOX 542500</StrtNm>
<PstCd>68154-8500</PstCd>
<TwnNm>OMAHA</TwnNm>
<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>
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 56 of 79
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
3. US Territories
AS GU MP PR
NOTE: United States Minor Outlying Islands (UM) and Virgin Islands (VI) currently are not supported.
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 57 of 79
Wire Drawdown - Debit Transactions (PAIN.008)
This section outlines the PAIN.008 file format that will be accepted by Messenger Financial Center.
Group Header Block – this can only occur once per file
Field Index – Field Tag Depth Content Mandatory / Description / Fedwire Processing Rules / Error Messages
Name – Tag Optional 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
(e.i., 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
<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]”
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 58 of 79
If the value of the field exceeds 35 characters, the transaction
will fail:
“Originator Name field does not validate for [invalid line]: Field
length exceeds maximum: [invalid length] > 35”
Postal Address +++ Empty Tag Required
<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]”
{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.”
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 59 of 79
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.
The payment with End to End ID [End to End ID] to [Beneficiary
Name (last four of beneficiary’s account)] will be skipped.”
Payment Information Block – this can occur multiple times within a file
Field Index – Field Tag Depth Content Mandatory / Description / Fedwire Processing Rules / Error Messages
Name – Tag Optional Mapping
Payment Information + Empty Tag Mandatory
<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
[Payment Information 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
<CtrlSum> transactions for this amount], found [calculated amount] for PmtInfId [Payment
payment block Information ID].”
Payment Type ++ Empty Tag Mandatory
Information
<PmtTpInf>
Service Level +++ Empty Tag Mandatory
<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
[Payment Information ID] will be skipped.”
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
four of beneficiary’s account number)] from [last four of
originator’s account number] was sent for a payment date in
the past.”
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 60 of 79
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:
{4200} Beneficiary “No value found for required field: Beneficiary Name for record
[invalid record]”
“Beneficiary Name field does not validate for [invalid line]: Field
length exceeds maximum: [invalid length] > 35”
Postal Address +++ Empty Tag Optional
<PstlAdr>
Street Name ++++ Yes Optional Beneficiary Address 1
<StrtNm>
{4200} Beneficiary
{4200} Beneficiary
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 61 of 79
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>
Financial Institution +++ Empty Tag Mandatory
Identification
<FinInstnId>
Clearing System ++++ Empty Tag Mandatory
Member Identification
<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.”
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 62 of 79
Payment Information Block, Payment Transaction, Payment Information Section
Field Index – Field Name Tag Depth Content Mandatory / Description / Fedwire Processing Rules / Error Messages
– Tag Optional Mapping
Payment Identification +++ Empty Tag Mandatory
<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.
“Amount field does not validate for line [invalid record count]:
Field length exceeds maximum: [invalid length] > 12”
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 63 of 79
If InstdAmt CCY does not equal USD, the transaction will
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.
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 64 of 79
[Beneficiary (last four of beneficiary’s account number)]
will be skipped.”
{6000} Originator to
Beneficiary Information
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 65 of 79
Sample
<?xml version="1.0" encoding="UTF-8" ?>
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 66 of 79
<Othr>
<Id>0812121359</Id>
</Othr>
</Id>
</CdtrAcct>
<CdtrAgt>
<FinInstnId>
<ClrSysMmbId>
<MmbId>065000090</MmbId>
</ClrSysMmbId>
</FinInstnId>
</CdtrAgt>
<DrctDbtTxInf>
<PmtId>
<EndToEndId>ABC123</EndToEndId>
</PmtId>
<InstdAmt Ccy="USD">111</InstdAmt>
<DbtrAgt>
<FinInstnId>
<ClrSysMmbId>
<MmbId>061000104</MmbId>
</ClrSysMmbId>
</FinInstnId>
</DbtrAgt>
<Dbtr>
<Nm>DEBIT PARTY</Nm>
<PstlAdr>
<StrtNm>PO BOX 542500</StrtNm>
<PstCd>68154-8500</PstCd>
<TwnNm>OMAHA</TwnNm>
<CtrySubDvsn>NEBRASKA</CtrySubDvsn>
</PstlAdr>
</Dbtr>
<DbtrAcct>
<Id>
<Othr>
<Id>586521453</Id>
</Othr>
</Id>
</DbtrAcct>
<RmtInf>
<Ustrd>REMITTANCE INFORMATION</Ustrd>
</RmtInf>
</DrctDbtTxInf>
</PmtInf>
</CstmrDrctDbtInitn>
</Document>
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 67 of 79
Virtual Card Payment Transactions (PAIN.001)
This section outlines the PAIN.001 file format that will be accepted by Capital One Bank.
Group Header Block – this can only occur once per file
Field Index – Tag Content Mandatory Description / Processing Rules / Error Messages
Field Name – Depth / Optional Harland Mapping
Tag
Group Header + Empty Tag Mandatory
<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 and time
<CreDtTm> YYYY-MM-DDTHH:MM:SS
(e.i., 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 68 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
Field Index – Tag Content Mandatory / Description / Processing Rules / Error Messages
Field Name – Depth Optional Harland Mapping
Tag
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 TRF. The batch
<PmtMtd> [Payment Information 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
<CtrlSum> transactions for this amount], found [calculated amount] for PmtInfId [Payment
payment block Information ID].
Payment Type ++ Empty Tag Mandatory
Information
<PmtTpInf>
Service Level +++ Empty Tag Mandatory
<SvcLvl>
Code <Cd> ++++ Yes Mandatory Must be NUGP Fail the TRANSACTION using the following message if the
payment method is invalid:
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 69 of 79
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.”
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.
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 70 of 79
Client ID field does not validate for line [line number]: Field
length exceeds maximum: 17 > 16
Debtor Account ++ Empty tag Mandatory
<DbtrAcct>
Identification <Id> +++ Empty Tag Mandatory
Other <Othr> ++++ Empty Tag Mandatory
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
Financial Institution +++ Empty Tag Mandatory
Identification <FinInstnId>
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.
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 71 of 79
Decimal, one digit after the decimal, i.e. 1.2, interpreted as
1.20
“Amount field does not validate for line [line number]: Field
length exceeds maximum: [invalid length] > 11”
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.”
Field Index – Field Tag Content Mandatory / Description / Processing Rules / Error Messages
Name – Tag Depth Optional Harland Mapping
Creditor <Cdtr> +++ Empty Tag Required
Identification <Id> ++++ Empty Tag Required
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.
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 72 of 79
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:
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 73 of 79
“User Defined Field 6 field length exceeds maximum:
[invalid length] > 130. The payment with End to End
ID [End to End ID] will be skipped.”
Unstructured ++++ Yes Optional UDF7 If the value of the field exceeds 130 characters, fail
<Ustrd> the TRANSACTION:
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 74 of 79
“User Defined Field 14 field length exceeds
maximum: [invalid length] > 130. The payment with
End to End ID [End to End ID] will be skipped.”
Unstructured ++++ Yes Optional UDF15 If the value of the field exceeds 130 characters, fail
<Ustrd> the TRANSACTION:
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 75 of 79
Decimal, two digits after the decimal - interpreted
literally, with decimal
• 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.
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 76 of 79
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>Acme Card</MsgId>
<CreDtTm>2016-07-29T14:08:05</CreDtTm>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>71000</CtrlSum>
<InitgPty>
<Id>
<OrgId>
<Othr>
<Id>INITG PTY ID - NOT USED</Id>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>PMT INF ID - NOT USED</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>71000</CtrlSum>
<PmtTpInf>
<SvcLvl>
<Cd>NUGP</Cd>
</SvcLvl>
</PmtTpInf>
<ReqdExctnDt>2016-08-09</ReqdExctnDt>
<Dbtr>
<Id>
<OrgId>
<Othr>
<Id>1234234534564567</Id>
</Othr>
</OrgId>
</Id>
</Dbtr>
<DbtrAcct>
<Id>
<Othr>
<Id>DUMMY DEBTOR DATA - NOT USED</Id>
</Othr>
</Id>
</DbtrAcct>
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 77 of 79
<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>
<InstdAmt Ccy="USD">71000</InstdAmt>
</Amt>
<Cdtr>
<Id>
<OrgId>
<Othr>
<Id>Vendor1ISO</Id>
</Othr>
</OrgId>
</Id>
</Cdtr>
<RmtInf>
<Ustrd>User Defined Fields 1</Ustrd>
<Ustrd>User Defined Fields 2</Ustrd>
<Ustrd>User Defined Fields 3</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>
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 78 of 79