Swift 8

SWIFT for CorporatesSCORE 2.0

21 September 2007

SWIFTStandards MX - MessageReference Guide

Table Of Contents Legal Notices ............................................................................................................................................................. 1

Copyright ............................................................................................................................................................... 1Confidentiality ........................................................................................................................................................ 1Disclaimer ............................................................................................................................................................... 1SWIFTStandards Intellectual Property Rights (IPR) Policy - End-User License Agreement ............................... 1Translations ............................................................................................................................................................ 1Trademarks ............................................................................................................................................................. 1

SWIFTStandards IPR Policy .................................................................................................................................. 2SWIFTStandards IPR Policy End-User License Agreement September 2005 ...................................................... 2

Overview .................................................................................................................................................................... 4What does this handbook contain? ......................................................................................................................... 4Payments Initiation messages ................................................................................................................................. 4Bank-to-Customer Account Reporting messages ................................................................................................... 4

MX camt.052.001.01 BankToCustomerAccountReportV01 ................................................................................ 5Message Scope and Usage ...................................................................................................................................... 5Message Structure ................................................................................................................................................... 5Message Items Description ................................................................................................................................... 17Business Example ............................................................................................................................................... 118

MX camt.053.001.01 BankToCustomerStatementV01 ..................................................................................... 123Message Scope and Usage .................................................................................................................................. 123Message Structure ............................................................................................................................................... 123Message Items Description ................................................................................................................................. 135Business Example ............................................................................................................................................... 235

MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01 .............................................................. 242Message Scope and Usage .................................................................................................................................. 242Message Structure ............................................................................................................................................... 242Message Items Description ................................................................................................................................. 253Business Example ............................................................................................................................................... 345

MX pain.001.001.02 CustomerCreditTransferInitiationV02 ........................................................................... 349Message Scope and Usage .................................................................................................................................. 349Message Structure ............................................................................................................................................... 353Message Items Description ................................................................................................................................. 357Business Example ............................................................................................................................................... 394

MX pain.002.001.02 PaymentStatusReportV02 ................................................................................................ 402Message Scope and Usage .................................................................................................................................. 402Message Structure ............................................................................................................................................... 403Message Items Description ................................................................................................................................. 407Business Example - Status of a CustomerCreditTransferInitiation .................................................................... 452Business Example - Status of a PaymentCancellationRequest .......................................................................... 454Business Example - Status of a CustomerDirectDebitInitiation ........................................................................ 456

Message Item Types .............................................................................................................................................. 460Data Types .......................................................................................................................................................... 460End Points ........................................................................................................................................................... 476

Indexes ................................................................................................................................................................... 541Index of Message Items ...................................................................................................................................... 541Index of XML tags ............................................................................................................................................. 570Index of Message Item Types ............................................................................................................................. 600Index of Error Codes .......................................................................................................................................... 621

Legal NoticesCopyright Copyright © S.W.I.F.T. SCRL ("SWIFT"), avenue Adèle 1, B-1310 La Hulpe, Belgium, or its licensors, 2006. All rights reserved.You may copy this publication within your organisation. Any such copy must include these legal notices.

ConfidentialityThis publication may contain SWIFT or third-party confidential information. Do not disclose this publication outside your organisation without the prior written consent of SWIFT.

DisclaimerThe information in this publication may change from time to time. You must always refer to the latest available version.

SWIFTStandards Intellectual Property Rights (IPR) Policy - End-User License AgreementSWIFTStandards are licensed subject to the terms and conditions of the SWIFTStandards IPR Policy - End-User License Agreement, available on www.swift.com > Standards > More information.

TranslationsThe English version of SWIFT documentation is the only official version.

TrademarksSWIFT, S.W.I.F.T., the SWIFT logo, Sibos, SWIFTNet, SWIFTAlliance, SWIFTStandards, SWIFTReady, and Accord are trademarks of S.W.I.F.T. SCRL. Other SWIFT-derived service and product names, including SWIFTSolutions, SWIFTWatch, and SWIFTSupport are tradenames of S.W.I.F.T. SCRL.SWIFT is the trading name of S.W.I.F.T. SCRL.Other product or company names in this publication are tradenames, trademarks, or registered trademarks of their respective owners.

SCORE 2.0 Legal Notices

21 September 2007 Page 1

SWIFTStandards IPR PolicySWIFTStandards IPR Policy End-User License Agreement September 2005

1. Definitions"SWIFT"means Society for Worldwide Interbank Financial Telecommunication SCRL."SWIFTStandards" means any message-based standard or component thereof, developed by or for SWIFT, including the related business model, messages, message flows and documentation, whether in draft or final form."IP Rights"means all copyright, proprietary know-how, patent rights (including patent applications) or other intellectual or industrial property rights.

2. LicenseSWIFT hereby grants you a world-wide, royalty-free, non-exclusive license to use or promote SWIFTStandards (i) for information transmission purposes in or outside the context of SWIFT messaging services and/or (ii) to develop software, products or services which support transmission of information in accordance with SWIFTStandards

3. LimitationsYou may not directly or indirectly sell SWIFTStandards. You may not modify SWIFTStandards while maintaining "SWIFTStandards"as a reference for the modified standard. This License Agreement does not grant you a license to use any of SWIFT's trademarks, except the trademark "SWIFTStandards" for the use as defined in Section 2.

4. Sub-licensingYou may grant sub-licenses on a royalty free basis only and provided that any such sub-license remains within the scope of your rights under this License Agreement.

5. Ownership of SWIFTStandardsAll IP Rights, worldwide ownership of and rights, title and interest in and to SWIFTStandards, and all copies and portions thereof, are and shall remain exclusively in SWIFT and its licensors.

6. TerminationThis license will terminate immediately without notice if you fail to comply with any material provision of this License Agreement.

7. Disclosure of IP RightsDuring the thirty (30) days period immediately following the date that SWIFTStandards are provided to you, you may disclose that the publication of, use of or compliance with SWIFTStandards as presented, in whole or in part, would infringe any of your IP Rights. Upon timely disclosure and considering the non-commercial nature of SWIFTStandards, you agree to license any such IP Right to SWIFT (including the right to grant sub-licenses) on royalty-free or otherwise reasonable and non-discriminatory terms and solely for the purpose of developing, implementing, promoting and using SWIFTStandards.

8. Non-Enforcement of IP RightsAny non-disclosure of your IP Rights pursuant to Section 7 of this License Agreement, shall be considered as a final and irrevocable waiver to assert or enforce any such IP Right that you may own or control, against SWIFT or any other third

SWIFTStandards MX

Page 2 Message Reference Guide

party that may use SWIFTStandards, if the allegedly infringing activity is caused solely by the use of SWIFTStandards in accordance with this License Agreement.

9. DisclaimerSWIFTStandards are provided "as is". SWIFT makes no express or implied representations, including but not limited to, warranties of merchantability or fitness for any particular purpose nor any warranty that the use of SWIFTStandards will not infringe any third party IP Rights.

10. Limitation of liabilitySince SWIFTStandards result from industry consultation and are adopted by consensus amongst relevant industry participants, SWIFT will not be liable for any direct, indirect, special or consequential damages arising out of any use of SWIFTStandards even if SWIFT is expressly advised of the possibility of such damages.

11. Choice of Law - ArbitrationThis License Agreement shall be governed by Belgian law.Any dispute concerning this License Agreement, that cannot be amicably resolved, shall be finally settled under the Rules of Conciliation and Arbitration of the International Chamber of Commerce (ICC) by three arbitrators appointed in accordance with these rules. The arbitration proceedings shall take place in Brussels, Belgium and shall be conducted in the English language.

SCORE 2.0 SWIFTStandards IPR Policy


OverviewWhat does this handbook contain?This handbook describes a set of ISO 20022 (UNIFI) Payments Initiation messages and Bank-to-Customer Account Reporting messages that can be used for Cash Management in the framework of SCORE.The following messages are included :

Payments Initiation messages- The CustomerCreditTransferInitiation message;- The PaymentStatusReport message.

Bank-to-Customer Account Reporting messages- The BankToCustomerAccountReport; - The BankToCustomerStatement; - The BankToCustomerDebitCreditNotification.

SWIFTStandards MX


MX camt.052.001.01 BankToCustomerAccountReportV01Message Scope and UsageScopeThe Bank-to-Customer Account Report message is sent by the account servicer to an account owner or to a party authorised by the account owner to receive the message. It can be used to inform the account owner, or authorised party, of the entries reported to the account, and/or to provide the owner with balance information on the account at a given point in time.

UsageThe Bank-to-Customer Account Report message can contain reports for more than 1 account. It provides information for cash management and/or reconciliation. It can be used to :- report pending and booked items;- provide balance informationIt can include underlying details of transactions that have been included in the entry.It is possible that the receiver of the message is not the account owner, but a party entitled by the account owner to receive the account information (also known as recipient).For a statement that is required due to local legal stipulations, the Bank-to-Customer Account Statement message should be used.

OutlineThe Bank-to-Customer Account Report message is composed of 2 building blocks:A. Group HeaderThis building block is mandatory and present once. It contains elements such as Message Identification and CreationDateTime.B. ReportThis building block is mandatory and repetitive. It should be repeated for each account on which a report is provided. The report contains components such as Balance and Entry information.

Message StructureIndex Or Message Item <XML Tag> Mult. Represent./

TypeRule/ Guid.

No.Message root <BkToCstmrAcctRpt

V01>[1..1]

Index Or Message Item <XML Tag> Mult. Represent./Type

Rule/ Guid.

No.1.0 GroupHeader <GrpHdr> [1..1]

1.1 MessageIdentification <MsgId> [1..1] Text

1.2 CreationDateTime <CreDtTm> [1..1] DateTime

1.3 MessageRecipient <MsgRcpt> [0..1] +

1.4 MessagePagination <MsgPgntn> [0..1] +

SCORE 2.0 MX camt.052.001.01 BankToCustomerAccountReportV01



Rule/ Guid.

No.1.5 AdditionalInformation <AddtlInf> [0..1] Text


Rule/ Guid.

No.2.0 Report <Rpt> [1..n]

2.1 Identification <Id> [1..1] Text

2.2 ElectronicSequenceNumber <ElctrncSeqNb> [0..1] Quantity

2.3 LegalSequenceNumber <LglSeqNb> [0..1] Quantity


2.5 FromToDate <FrToDt> [0..1] +

2.6 CopyDuplicateIndicator <CpyDplctInd> [0..1] Code

2.7 Account <Acct> [1..1]

2.8 Identification <Id> [1..1] +

2.9 Type <Tp> [0..1]

2.10 {Or Code <Cd> [1..1] Code

2.11 Or} Proprietary <Prtry> [1..1] Text

2.12 Currency <Ccy> [0..1] Code

2.13 Name <Nm> [0..1] Text

2.14 Owner <Ownr> [0..1] +

2.15 Servicer <Svcr> [0..1] +

2.16 RelatedAccount <RltdAcct> [0..1] +

2.17 Interest <Intrst> [0..n]

2.18 Type <Tp> [0..1]



2.21 Rate <Rate> [0..n]

2.22 Rate <Rate> [1..1]

2.23 {Or PercentageRate <PctgRate> [1..1] Rate

2.24 Or} TextualRate <TxtlRate> [1..1] Text

2.25 ValidityRange <VldtyRg> [0..1] +


2.27 Reason <Rsn> [0..1] Text

2.28 Balance <Bal> [0..n]

2.29 Type <Tp> [1..1]

SWIFTStandards MX



Rule/ Guid.

No.2.30 {Or Code <Cd> [1..1] Code


2.32 CreditLine <CdtLine> [0..1]

2.33 Included <Incl> [1..1] Indicator

2.34 Amount <Amt> [0..1] Amount


2.36 CreditDebitIndicator <CdtDbtInd> [1..1] Code

2.37 Date <Dt> [1..1] +

2.38 Availability <Avlbty> [0..n]

2.39 Date <Dt> [1..1]

2.40 {Or NumberOfDays <NbOfDays> [1..1] Text

2.41 Or} ActualDate <ActlDt> [1..1] DateTime



2.44 TransactionsSummary <TxsSummry> [0..1]

2.45 TotalEntries <TtlNtries> [0..1]

2.46 NumberOfEntries <NbOfNtries> [0..1] Text

2.47 Sum <Sum> [0..1] Quantity

2.48 TotalNetEntryAmount <TtlNetNtryAmt> [0..1] Quantity


2.50 TotalCreditEntries <TtlCdtNtries> [0..1]



2.53 TotalDebitEntries <TtlDbtNtries> [0..1]



2.56 TotalEntriesPerBankTransactionCode <TtlNtriesPerBkTxCd>

[0..n]





2.61 BankTransactionCode <BkTxCd> [1..1]

2.62 Domain <Domn> [0..1]

2.63 Code <Cd> [1..1] Code




Rule/ Guid.

No.2.64 Family <Fmly> [1..1]

2.65 Code <Cd> [1..1] Code

2.66 SubFamilyCode <SubFmlyCd> [1..1] Code

2.67 Proprietary <Prtry> [0..1]

2.68 Code <Cd> [1..1] Text

2.69 Issuer <Issr> [0..1] Text


2.71 Date <Dt> [1..1]





2.76 Entry <Ntry> [0..n]



2.79 ReversalIndicator <RvslInd> [0..1] Indicator

2.80 Status <Sts> [1..1] Code

2.81 BookingDate <BookgDt> [0..1] +

2.82 ValueDate <ValDt> [0..1] +

2.83 AccountServicerReference <AcctSvcrRef> [0..1] Text


2.85 Date <Dt> [1..1]







2.92 Code <Cd> [1..1] Code

2.93 Family <Fmly> [1..1]

2.94 Code <Cd> [1..1] Code



2.97 Code <Cd> [1..1] Text


SWIFTStandards MX



Rule/ Guid.

No.2.99 CommissionWaiverIndicator <ComssnWvrInd> [0..1] Indicator

2.100 AdditionalInformationIndicator <AddtlInfInd> [0..1]

2.101 MessageNameIdentification <MsgNmId> [0..1] Text


2.103 Batch <Btch> [0..n]


2.105 PaymentInformationIdentification <PmtInfId> [0..1] Text

2.106 NumberOfTransactions <NbOfTxs> [0..1] Text

2.107 AmountDetails <AmtDtls> [0..1]

2.108 InstructedAmount <InstdAmt> [0..1]


2.110 CurrencyExchange <CcyXchg> [0..1]

2.111 SourceCurrency <SrcCcy> [1..1] Code

2.112 TargetCurrency <TrgtCcy> [0..1] Code

2.113 UnitCurrency <UnitCcy> [0..1] Code

2.114 ExchangeRate <XchgRate> [1..1] Rate

2.115 ContractIdentification <CtrctId> [0..1] Text

2.116 QuotationDate <QtnDt> [0..1] DateTime

2.117 TransactionAmount <TxAmt> [0..1]









2.126 CounterValueAmount <CntrValAmt> [0..1]











Rule/ Guid.

No.2.134 QuotationDate <QtnDt> [0..1] DateTime

2.135 AnnouncedPostingAmount <AnncdPstngAmt> [0..1]









2.144 ProprietaryAmount <PrtryAmt> [0..n]

2.145 Type <Tp> [1..1] Text









2.154 Charges <Chrgs> [0..n]

2.155 TotalChargesAndTaxAmount <TtlChrgsAndTaxAmt>

[0..1] Amount


2.157 Type <Tp> [0..1]

2.158 {Or Code <Cd> [1..1] Code

2.159 Or} ProprietaryCode <PrtryCd> [1..1] Text

2.160 Rate <Rate> [0..1] Rate

2.161 Bearer <Br> [0..1] Code

2.162 Party <Pty> [0..1] +

2.163 Tax <Tax> [0..1]





SWIFTStandards MX



Rule/ Guid.

No.2.168 Amount <Amt> [1..1] Amount


2.170 Type <Tp> [0..1]

2.171 {Or Code <Cd> [1..1] Code


2.173 Rate <Rate> [0..n]

2.174 Rate <Rate> [1..1]






2.180 TransactionDetails <TxDtls> [0..n]

2.181 References <Refs> [0..1]



2.184 InstructionIdentification <InstrId> [0..1] Text

2.185 EndToEndIdentification <EndToEndId> [0..1] Text

2.186 TransactionIdentification <TxId> [0..1] Text

2.187 MandateIdentification <MndtId> [0..1] Text

2.188 ChequeNumber <ChqNb> [0..1] Text

2.189 ClearingSystemReference <ClrSysRef> [0..1] Text


2.191 Type <Tp> [1..1] Text

2.192 Reference <Ref> [1..1] Text














Rule/ Guid.

No.2.203 TransactionAmount <TxAmt> [0..1]




























2.231 Type <Tp> [1..1] Text







SWIFTStandards MX



Rule/ Guid.

No.2.238 ContractIdentification <CtrctId> [0..1] Text



2.241 Date <Dt> [1..1]






2.247 Domain <Domn> [0..1]

2.248 Code <Cd> [1..1] Code

2.249 Family <Fmly> [1..1]

2.250 Code <Cd> [1..1] Code



2.253 Code <Cd> [1..1] Text




[0..1] Amount


2.258 Type <Tp> [0..1]

2.259 {Or Code <Cd> [1..1] Code




2.263 Party <Pty> [0..1] +

2.264 Tax <Tax> [0..1]







2.271 Type <Tp> [0..1]




Rule/ Guid.



2.274 Rate <Rate> [0..n]

2.275 Rate <Rate> [1..1]






2.281 RelatedParties <RltdPties> [0..1]

2.282 InitiatingParty <InitgPty> [0..1] +

2.283 Debtor <Dbtr> [0..1] +

2.284 DebtorAccount <DbtrAcct> [0..1] +

2.285 UltimateDebtor <UltmtDbtr> [0..1] +

2.286 Creditor <Cdtr> [0..1] +

2.287 CreditorAccount <CdtrAcct> [0..1] +

2.288 UltimateCreditor <UltmtCdtr> [0..1] +

2.289 TradingParty <TradgPty> [0..1] +

2.290 Proprietary <Prtry> [0..n]

2.291 Type <Tp> [1..1] Text

2.292 Party <Pty> [1..1] +

2.293 RelatedAgents <RltdAgts> [0..1]

2.294 DebtorAgent <DbtrAgt> [0..1] +

2.295 CreditorAgent <CdtrAgt> [0..1] +

2.296 IntermediaryAgent1 <IntrmyAgt1> [0..1] +



2.299 ReceivingAgent <RcvgAgt> [0..1] +

2.300 DeliveringAgent <DlvrgAgt> [0..1] +

2.301 IssuingAgent <IssgAgt> [0..1] +

2.302 SettlementPlace <SttlmPlc> [0..1] +


2.304 Type <Tp> [1..1] Text

2.305 Agent <Agt> [1..1] +

2.306 Purpose <Purp> [0..1]

SWIFTStandards MX



Rule/ Guid.



2.309 RelatedRemittanceInformation <RltdRmtInf> [0..10]

2.310 RemittanceIdentification <RmtId> [0..1] Text

2.311 RemittanceLocationMethod <RmtLctnMtd> [0..1] Code

2.312 RemittanceLocationElectronicAddress

<RmtLctnElctrncAdr> [0..1] Text

2.313 RemittanceLocationPostalAddress <RmtLctnPstlAdr> [0..1]

2.314 Name <Nm> [1..1] Text

2.315 Address <Adr> [1..1] +

2.316 RemittanceInformation <RmtInf> [0..1]

2.317 Unstructured <Ustrd> [0..n] Text

2.318 Structured <Strd> [0..n]

2.319 ReferredDocumentInformation <RfrdDocInf> [0..1]

2.320 ReferredDocumentType <RfrdDocTp> [0..1]

2.321 {Or Code <Cd> [1..1] Code



2.324 ReferredDocumentNumber <RfrdDocNb> [0..1] Text

2.325 ReferredDocumentRelatedDate <RfrdDocRltdDt> [0..1] DateTime

2.326 ReferredDocumentAmount <RfrdDocAmt> [0..n]

2.327 {Or DuePayableAmount <DuePyblAmt> [1..1] Amount

2.328 Or DiscountAppliedAmount <DscntApldAmt> [1..1] Amount

2.329 Or RemittedAmount <RmtdAmt> [1..1] Amount

2.330 Or CreditNoteAmount <CdtNoteAmt> [1..1] Amount

2.331 Or} TaxAmount <TaxAmt> [1..1] Amount

2.332 CreditorReferenceInformation <CdtrRefInf> [0..1]

2.333 CreditorReferenceType <CdtrRefTp> [0..1]

2.334 {Or Code <Cd> [1..1] Code



2.337 CreditorReference <CdtrRef> [0..1] Text

2.338 Invoicer <Invcr> [0..1] +

2.339 Invoicee <Invcee> [0..1] +




Rule/ Guid.

No.2.340 AdditionalRemittanceInformati

on<AddtlRmtInf> [0..1] Text

2.341 RelatedDates <RltdDts> [0..1]

2.342 AcceptanceDateTime <AccptncDtTm> [0..1] DateTime

2.343 TradeDate <TradDt> [0..1] DateTime

2.344 InterbankSettlementDate <IntrBkSttlmDt> [0..1] DateTime

2.345 StartDate <StartDt> [0..1] DateTime

2.346 EndDate <EndDt> [0..1] DateTime

2.347 TransactionDateTime <TxDtTm> [0..1] DateTime


2.349 Type <Tp> [1..1] Text

2.350 {Or Date <Dt> [1..1] DateTime

2.351 Or} DateTime <DtTm> [1..1] DateTime

2.352 RelatedPrice <RltdPric> [0..1]

2.353 {Or DealPrice <DealPric> [1..1] Amount

2.354 Or} Proprietary <Prtry> [1..n]

2.355 Type <Tp> [1..1] Text

2.356 Price <Pric> [1..1] Amount

2.357 RelatedQuantities <RltdQties> [0..n]

2.358 {Or Quantity <Qty> [1..1] +

2.359 Or} Proprietary <Prtry> [1..1]

2.360 Type <Tp> [1..1] Text

2.361 Quantity <Qty> [1..1] Text

2.362 FinancialInstrumentIdentification <FinInstrmId> [0..1]

2.363 {Or ISIN <ISIN> [1..1] Identifier


2.365 Type <Tp> [1..1] Text


2.367 Tax <Tax> [0..1] +

2.368 ReturnInformation <RtrInf> [0..1]

2.369 OriginalBankTransactionCode <OrgnlBkTxCd> [0..1]

2.370 Domain <Domn> [0..1]

2.371 Code <Cd> [1..1] Code

2.372 Family <Fmly> [1..1]

2.373 Code <Cd> [1..1] Code

SWIFTStandards MX



Rule/ Guid.

No.2.374 SubFamilyCode <SubFmlyCd> [1..1] Code


2.376 Code <Cd> [1..1] Text


2.378 ReturnOriginator <RtrOrgtr> [0..1] +

2.379 ReturnReason <RtrRsn> [0..1]

2.380 {Or Code <Cd> [1..1] Code


2.382 AdditionalReturnReasonInformation

<AddtlRtrRsnInf> [0..n] Text

2.383 CorporateAction <CorpActn> [0..1]

2.384 Code <Cd> [0..1] Text

2.385 Number <Nb> [0..1] Text

2.386 Proprietary <Prtry> [0..1] Text

2.387 SafekeepingAccount <SfkpgAcct> [0..1] +

2.388 AdditionalTransactionInformation <AddtlTxInf> [0..1] Text

2.389 AdditionalEntryInformation <AddtlNtryInf> [0..1] Text

2.390 AdditionalReportInformation <AddtlRptInf> [0..1] Text

Message Items DescriptionThe following section identifies the elements of the BankToCustomerAccountReportV01 message.

1.0 GroupHeader <GrpHdr>Presence: [1..1]Definition: Common information for the message.Type: The GroupHeader block is composed of the following GroupHeader23 element(s):






1.5 AdditionalInformation <AddtlInf> [0..1] Text

1.1 MessageIdentification <MsgId>Presence: [1..1]



Definition: Point to point reference assigned by the account servicing institution and sent to the account owner to unambiguously identify the message.

Usage: The account servicing institution has to make sure that 'MessageIdentification' is unique per instructed party for a pre-agreed period.

Data Type: Max35TextFormat: maxLength: 35

minLength: 1

1.2 CreationDateTime <CreDtTm>Presence: [1..1]Definition: Date and time at which the message was created by the account servicer.Data Type: ISODateTime

1.3 MessageRecipient <MsgRcpt>Presence: [0..1]Definition: Party that is entitled by the account owner to receive information about movements in the account.

Guideline : MessageRecipient should only be identified when different from the account owner.Type: This message item is composed of the following PartyIdentification8 element(s):

Or Message Item <XML Tag> Mult. Represent./Type

Name <Nm> [0..1] Text

PostalAddress <PstlAdr> [0..1]

Identification <Id> [0..1]

CountryOfResidence <CtryOfRes> [0..1] Code

For additional Type information, please refer to PartyIdentification8 p.523 in 'Message Item Types' section.

1.4 MessagePagination <MsgPgntn>Presence: [0..1]Definition: Pagination of the message.

Usage: the pagination of the message is only allowed when agreed between the parties.Type: This message item is composed of the following Pagination element(s):


PageNumber <PgNb> [1..1] Text

LastPageIndicator <LastPgInd> [1..1] Indicator

For additional Type information, please refer to Pagination p.522 in 'Message Item Types' section.

1.5 AdditionalInformation <AddtlInf>Presence: [0..1]

SWIFTStandards MX


Definition: Further details on the message.Data Type: Max500TextFormat: maxLength: 500

minLength: 1

2.0 Report <Rpt>Presence: [1..n]Definition: Reports on a cash account.Type: The Report block is composed of the following AccountReport9 element(s):














2.390 AdditionalReportInformation <AddtlRptInf> [0..1] Text

2.1 Identification <Id>Presence: [1..1]Definition: Unique and unambiguous identification of the account report, assigned by the account servicer.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.2 ElectronicSequenceNumber <ElctrncSeqNb>Presence: [0..1]Definition: Sequential number of the report, assigned by the account servicer. It is increased incrementally for each

report sent electronically.Data Type: NumberFormat: fractionDigits: 0

totalDigits: 18

2.3 LegalSequenceNumber <LglSeqNb>Presence: [0..1]



Definition: Legal sequential number of the report, assigned by the account servicer. It is increased incrementally for each report sent.

Usage : in those scenarios where eg a paper statement is a legal requirement, the paper statement may have a different numbering than the electronic sequential number. Paper statements can for instance only be sent if movement on the account has taken place, whereas electronic statements can be sent eg each day, regardless of whether movements have taken place or not.

Data Type: NumberFormat: fractionDigits: 0

totalDigits: 18

2.4 CreationDateTime <CreDtTm>Presence: [1..1]Definition: Date and time at which the report was created.Data Type: ISODateTime

2.5 FromToDate <FrToDt>Presence: [0..1]Definition: Range of time between the start date and the end date for which the account report is issued.Type: This message item is composed of the following DateTimePeriodDetails element(s):


FromDateTime <FrDtTm> [1..1] DateTime

ToDateTime <ToDtTm> [1..1] DateTime

For additional Type information, please refer to DateTimePeriodDetails p.509 in 'Message Item Types' section.

2.6 CopyDuplicateIndicator <CpyDplctInd>Presence: [0..1]Definition: Specifies if this document is a copy, a duplicate, or a duplicate of a copy.Data Type: CodeWhen this message item is present, one of the following CopyDuplicate1Code values must be used:

Code Name DefinitionCODU CopyDuplicate Message is being sent as a copy to a party other than the

account owner, for information purposes and the message is a duplicate of a message previously sent.

COPY Copy Message is being sent as a copy to a party other than the account owner, for information purposes.

DUPL Duplicate Message is for information/confirmation purposes. It is a duplicate of a message previously sent.

2.7 Account <Acct>Presence: [1..1]

SWIFTStandards MX


Definition: Business relationship between two entities; one entity is the account owner, the other entity is the account servicer.

Type: This message item is composed of the following CashAccount13 element(s):



2.9 Type <Tp> [0..1]


2.13 Name <Nm> [0..1] Text

2.14 Owner <Ownr> [0..1] +


2.8 Identification <Id>Presence: [1..1]Definition: Unique and unambiguous identification of the account between the account owner and the account servicer.Type: This message item is composed of one of the following AccountIdentification3Choice element(s):


{Or IBAN <IBAN> [1..1] Identifier

Or BBAN <BBAN> [1..1] Identifier

Or UPIC <UPIC> [1..1] Identifier

Or} ProprietaryAccount <PrtryAcct> [1..1]

For additional Type information, please refer to AccountIdentification3Choice p.477 in 'Message Item Types' section.

2.9 Type <Tp>Presence: [0..1]Definition: Nature, or use, of the account.Type: This message item is composed of one of the following CashAccountType2 element(s):




2.10 Code <Cd>Presence: [1..1]This message item is part of choice 2.9 Type.Definition: Nature or use of the account in a coded form.Data Type: CodeOne of the following CashAccountType4Code values must be used:



Code Name DefinitionCACC Current Account used to post debits and credits when no specific

account has been nominated.

CASH CashPayment Account used for the payment of cash.

CHAR Charges Account used for charges if different from the account for payment.

CISH CashIncome Account used for payment of income if different from the current cash account.

COMM Commission Account used for commission if different from the account for payment.

LOAN Loan Account used for loans.

MGLD MarginalLending Account used for a marginal lending facility.

MOMA MoneyMarket Account used for money markets if different from the cash account.

NREX NonResidentExternal Account used for non-resident external.

ODFT Overdraft Account is used for overdrafts.

ONDP OverNightDeposit Account used for overnight deposits.

SACC Settlement Account used to post debit and credit entries, as a result of transactions cleared and settled through a specific clearing and settlement system.

SLRY Salary Accounts used for salary payments.

SVGS Savings Account used for savings.

TAXE Tax Account used for taxes if different from the account for payment.

TRAS CashTrading Account used for trading if different from the current cash account.

2.11 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.9 Type.Definition: Proprietary nature or use of the account.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.12 Currency <Ccy>Presence: [0..1]Definition: Identification of the currency in which the account is held.Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable

SWIFTStandards MX


2.13 Name <Nm>Presence: [0..1]Definition: Name of the account, assigned by the account servicing institution in agreement with the account owner in

order to provide an additional means of identification of the account.

Usage : the account name is different from the account owner name. The account name is used in certain user communities to provide a means of identifying the account, in addition to the account owner's identity and the account number.


minLength: 1

2.14 Owner <Ownr>Presence: [0..1]Definition: Party that legally owns the account.Type: This message item is composed of the following PartyIdentification8 element(s):







2.15 Servicer <Svcr>Presence: [0..1]Definition: Party that manages the account on behalf of the account owner, ie, manages the registration and booking of

entries on the account, calculates balances on the account and provides information about the account.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):


FinancialInstitutionIdentification <FinInstnId> [1..1]

BranchIdentification <BrnchId> [0..1]

For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.510 in 'Message Item Types' section.

2.16 RelatedAccount <RltdAcct>Presence: [0..1]Definition: Identifies the parent account of the reported account.Type: This message item is composed of the following CashAccount7 element(s):





Type <Tp> [0..1]

Currency <Ccy> [0..1] Code


For additional Type information, please refer to CashAccount7 p.478 in 'Message Item Types' section.

2.17 Interest <Intrst>Presence: [0..n]Definition: Provides general interest information that applies to the account at a particular moment in time.Type: This message item is composed of the following AccountInterest1 element(s):


2.18 Type <Tp> [0..1]

2.21 Rate <Rate> [0..n]



2.18 Type <Tp>Presence: [0..1]Definition: Specifies the type of interest.Type: This message item is composed of one of the following InterestType1Choice element(s):




2.19 Code <Cd>Presence: [1..1]This message item is part of choice 2.18 Type.Definition: Specifies the type of interest.Data Type: CodeOne of the following InterestType1Code values must be used:

Code Name DefinitionINDY IntraDay During or within a business day.

OVRN OverNight Period of time between the end of a business day and the start of the next business day (usually the day after).

SWIFTStandards MX


2.20 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.18 Type.Definition: Specifies the type of interest in uncoded form.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.21 Rate <Rate>Presence: [0..n]Definition: Set of elements qualifying the interest rate.Type: This message item is composed of the following Rate1 element(s):


2.22 Rate <Rate> [1..1]


2.22 Rate <Rate>Presence: [1..1]Definition: Percentage charged for the use of an amount of money, usually expressed at an annual rate. The interest rate

is the ratio of the amount of interest paid during a certain period of time compared to the principal amount of the interest bearing financial instrument. Example percentage rate : Rate expressed as a percentage, ie, in hundredths, eg, 0.7 is 7/10 of a percent, and 7.0 is 7%.Example Textual rate : Rate is expressed as a text.

Type: This message item is composed of one of the following RateTypeChoice element(s):




2.23 PercentageRate <PctgRate>Presence: [1..1]This message item is part of choice 2.22 Rate.Definition: Percentage charged for the use of an amount of money, usually expressed at an annual rate. The interest rate

is the ratio of the amount of interest paid during a certain period of time compared to the principal amount of the interest bearing financial instrument.

Data Type: PercentageRateFormat: fractionDigits: 10

totalDigits: 11



2.24 TextualRate <TxtlRate>Presence: [1..1]This message item is part of choice 2.22 Rate.Definition: Rate is expressed as a text.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.25 ValidityRange <VldtyRg>Presence: [0..1]Definition: An amount range where the interest rate is applicableType: This message item is composed of the following CurrencyAndAmountRange element(s):


Amount <Amt> [1..1]

CreditDebitIndicator <CdtDbtInd> [0..1] Code


For additional Type information, please refer to CurrencyAndAmountRange p.482 in 'Message Item Types' section.

2.26 FromToDate <FrToDt>Presence: [0..1]Definition: Range of time between a start date and an end date for the calculation of the interest.Type: This message item is composed of the following DateTimePeriodDetails element(s):





2.27 Reason <Rsn>Presence: [0..1]Definition: Underlying reason for the interest, eg, yearly credit interest on a savings account.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.28 Balance <Bal>Presence: [0..n]Definition: Set of elements defining the balance(s).Type: This message item is composed of the following CashBalance1 element(s):

SWIFTStandards MX



2.29 Type <Tp> [1..1]




2.37 Date <Dt> [1..1] +


Rule(s): AvailabilityAndTypeRule If Type is equal to ForwardAvailable, Availability is not allowed.

2.29 Type <Tp>Presence: [1..1]Definition: Specifies the nature of a balance, eg, opening booked balance.Type: This message item is composed of one of the following BalanceType1Choice element(s):




2.30 Code <Cd>Presence: [1..1]This message item is part of choice 2.29 Type.Definition: Specifies the code for the type of a balance, eg, opening booked balance.Data Type: CodeOne of the following BalanceType8Code values must be used:

Code Name DefinitionCCLA CollectionClosingAvailable Collection closing balance of amount of money that is at the

disposal of the account owner on the date specified.

CCLB CollectionClosingBooked Collection balance of the account at the end of the pre-agreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period.

CFWA CollectionForwardAvailable Collection forward available balance of money that is at the disposal of the account owner on the date specified.

CITA CollectionInterimAvailable Collection available balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.



Code Name DefinitionCITB CollectionInterimBooked Collection balance calculated in the course of the account

servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

CLAV ClosingAvailable Closing balance of amount of money that is at the disposal of the account owner on the date specified.

CLBD ClosingBooked Balance of the account at the end of the pre-agreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period.

COPA CollectionOpeningAvailable Collection opening balance of amount of money that is at the disposal of the account owner on the date specified.

COPB CollectionOpeningBooked Collection book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report.

CXPC CollectionExpected Collection balance, composed of booked entries and pending items known at the time of calculation , which projects the end of day balance if everything is booked on the account and no other entry is posted.

DCLA DisbursementClosingAvailable

Disbursement closing balance of amount of money that is at the disposal of the account owner on the date specified.

DCLB DisbursementClosingBooked

Disbursement balance of the account at the end of the pre-agreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period.

DFWA DisbursementForwardAvailable

Disbursement forward available balance of money that is at the disposal of the account owner on the date specified.

DITA DisbursementInterimAvailable

Disbursement available balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

DITB DisbursementInterimBooked

Disbursement balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

DOPA DisbursementOpeningAvailable

Disbursement opening balance of amount of money that is at the disposal of the account owner on the date specified.

DOPB DisbursementOpeningBooked

Disbursement book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report.

SWIFTStandards MX


Code Name DefinitionDXPC DisbursementExpected Disbursement balance, composed of booked entries and

pending items known at the time of calculation , which projects the end of day balance if everything is booked on the account and no other entry is posted.

FWAV ForwardAvailable Forward available balance of money that is at the disposal of the account owner on the date specified.

ICLA InvestmentClosingAvailable Investment closing balance of an amount of money that is at the disposal of the account owner on the date specified.

ICLB InvestmentClosingBooked Investment (mutual funds) balance of the account at the end of the pre-agreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period.

IFWA InvestmentForwardAvailable

Investment forward available balance of money that is at the disposal of the account owner on the date specified.

IITA InvestmentInterimAvailable Investment available balance for calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

IITB InvestmentInterimBooked Investment balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

IOPA InvestmentOpeningAvailable

Investment opening balance of amount of money that is at the disposal of the account owner on the date specified.

IOPB InvestmentOpeningBooked Investment book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report.

ITAV InterimAvailable Available balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

ITBD InterimBooked Balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

IXPC InvestmentExpected Investment balance, composed of booked entries and pending items known at the time of calculation , which projects the end of day balance if everything is booked on the account and no other entry is posted.



Code Name DefinitionOPAV OpeningAvailable Opening balance of amount of money that is at the disposal

of the account owner on the date specified.

OPBD OpeningBooked Book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report.

PRCD PreviouslyClosedBooked Balance of the account at the previously closed account reporting period. The opening booked balance for the new period has to be equal to this balance.

Usage: the previously booked closing balance should equal (inclusive date) the booked closing balance of the date it references and equal the actual booked opening balance of the current date.

XPCD Expected Balance, composed of booked entries and pending items known at the time of calculation , which projects the end of day balance if everything is booked on the account and no other entry is posted.

2.31 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.29 Type.Definition: Specifies a proprietary code for the balance type.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.32 CreditLine <CdtLine>Presence: [0..1]Definition: Provides further details on the credit line information.Type: This message item is composed of the following CreditLine1 element(s):




2.33 Included <Incl>Presence: [1..1]Definition: Indicates whether the credit line is included or not.

Usage : if not present, credit line is not included in the balance amount.Data Type: One of the following TrueFalseIndicator values must be used:

MeaningWhenTrue: True

SWIFTStandards MX


MeaningWhenFalse: False

2.34 Amount <Amt>Presence: [0..1]Definition: Amount of money of the credit line.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount

fractionDigits: 5minInclusive: 0totalDigits: 18CurrencyCode[A-Z]{3,3}

Rule(s): CurrencyCodeValidationByTable

2.35 Amount <Amt>Presence: [1..1]Definition: Currency and amount of money of the cash balance.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.36 CreditDebitIndicator <CdtDbtInd>Presence: [1..1]Definition: Indicates whether the balance is a credit or a debit balance. A zero balance is considered to be a credit balanceData Type: CodeOne of the following CreditDebitCode values must be used:

Code Name DefinitionCRDT Credit Operation is an increase.

DBIT Debit Operation is a decrease.

2.37 Date <Dt>Presence: [1..1]Definition: Specifies the date (and time) of the balance.Type: This message item is composed of one of the following DateAndDateTimeChoice element(s):




{Or Date <Dt> [1..1] DateTime

Or} DateTime <DtTm> [1..1] DateTime

For additional Type information, please refer to DateAndDateTimeChoice p.508 in 'Message Item Types' section.

2.38 Availability <Avlbty>Presence: [0..n]Definition: Set of elements used to indicate when the booked amount of money will become available, ie can be accessed

and start generating interest.

Usage : this type of info is eg used in US, and is linked to particular instruments, such as cheques.Example : When a cheque is deposited, it will be booked on the deposit day, but the funds will only be accessible as of the indicated availability day (according to national banking regulations).

Type: This message item is composed of the following CashBalanceAvailability1 element(s):


2.39 Date <Dt> [1..1]



2.39 Date <Dt>Presence: [1..1]Definition: Indicates when the amount of money will become available.Type: This message item is composed of one of the following CashBalanceAvailabilityDate1 element(s):




2.40 NumberOfDays <NbOfDays>Presence: [1..1]This message item is part of choice 2.39 Date.Definition: Indicates the number of float days attached to the balance.Data Type: Max15PlusSignedNumericTextFormat: [+]{0,1}[0-9]{1,15}

2.41 ActualDate <ActlDt>Presence: [1..1]This message item is part of choice 2.39 Date.Definition: Identifies the actual availability date.

SWIFTStandards MX


Data Type: ISODate

2.42 Amount <Amt>Presence: [1..1]Definition: Identifies the available amount.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.43 CreditDebitIndicator <CdtDbtInd>Presence: [1..1]Definition: Indicates whether the availability balance is a credit or a debit balance. A zero balance is considered to be a

credit balanceData Type: CodeOne of the following CreditDebitCode values must be used:



2.44 TransactionsSummary <TxsSummry>Presence: [0..1]Definition: Set of element providing summary information on entries.Type: This message item is composed of the following TotalTransactions1 element(s):





2.56 TotalEntriesPerBankTransactionCode <TtlNtriesPerBkTxCd> [0..n]

2.45 TotalEntries <TtlNtries>Presence: [0..1]Definition: Indicates the total number and sum of debit and credit entries.Type: This message item is composed of the following NumberAndSumOfTransactions2 element(s):








Guideline(s): DebitCreditIndicatorGuideline DebitCreditIndicator should be present when TotalNetEntryAmount is present.

2.46 NumberOfEntries <NbOfNtries>Presence: [0..1]Definition: Number of individual entries included in the report.Data Type: Max15NumericTextFormat: [0-9]{1,15}

2.47 Sum <Sum>Presence: [0..1]Definition: Total of all individual entries included in the report.Data Type: DecimalNumberFormat: fractionDigits: 17

totalDigits: 18

2.48 TotalNetEntryAmount <TtlNetNtryAmt>Presence: [0..1]Definition: Resulting amount of the netted amounts for all debit and credit entries. Data Type: DecimalNumberFormat: fractionDigits: 17

totalDigits: 18

2.49 CreditDebitIndicator <CdtDbtInd>Presence: [0..1]Definition: Indicates whether the total net entry amount is a credit or a debit amount.Data Type: CodeWhen this message item is present, one of the following CreditDebitCode values must be used:



2.50 TotalCreditEntries <TtlCdtNtries>Presence: [0..1]Definition: Indicates the total number and sum of credit entries.Type: This message item is composed of the following NumberAndSumOfTransactions1 element(s):

SWIFTStandards MX







totalDigits: 18

2.53 TotalDebitEntries <TtlDbtNtries>Presence: [0..1]Definition: Indicates the total number and sum of debit entries.Type: This message item is composed of the following NumberAndSumOfTransactions1 element(s):






totalDigits: 18

2.56 TotalEntriesPerBankTransactionCode <TtlNtriesPerBkTxCd>Presence: [0..n]



Definition: Indicates the total number and sum of entries per bank transaction code.Type: This message item is composed of the following NumberAndSumOfTransactionsPerBankTransactionCode1

element(s):









2.57 NumberOfEntries <NbOfNtries>Presence: [0..1]Definition: Number of individual entries contained in the report.Data Type: Max15NumericTextFormat: [0-9]{1,15}


totalDigits: 18

2.59 TotalNetEntryAmount <TtlNetNtryAmt>Presence: [0..1]Definition: Resulting amount of the netted amounts for all debit and credit entries per bank transaction code. Data Type: DecimalNumberFormat: fractionDigits: 17

totalDigits: 18




SWIFTStandards MX


2.61 BankTransactionCode <BkTxCd>Presence: [1..1]Definition: Set of elements to fully identify the type of underlying transaction resulting in an entry.Type: This message item is composed of the following BankTransactionCodeStructure1 element(s):




Rule(s): DomainAndProprietary1Rule If Domain is absent, then Proprietary must be present.

DomainAndProprietary2Rule If Proprietary is absent, then Domain must be present.

FamilyAndSubFamilyRule A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.

2.62 Domain <Domn>Presence: [0..1]Definition: Specifies the domain, the family and the sub-family of the bank transaction code, in a structured and

hierarchical format.

Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the domain or the generic subfamily code defined for the family should be provided.

Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):


2.63 Code <Cd> [1..1] Code


2.63 Code <Cd>Presence: [1..1]Definition: Specifies the business area of the underlying transaction.Data Type: ExternalBankTransactionDomainCodeFormat: maxLength: 4

minLength: 1

2.64 Family <Fmly>Presence: [1..1]Definition: Specifies the family and the sub-family of the bank transaction code, within a specific domain, in a structured

and hierarchical format.Type: This message item is composed of the following BankTransactionCodeStructure3 element(s):




2.65 Code <Cd> [1..1] Code


2.65 Code <Cd>Presence: [1..1]Definition: Specifies the family within a domain.Data Type: ExternalBankTransactionFamilyCodeFormat: maxLength: 4

minLength: 1

2.66 SubFamilyCode <SubFmlyCd>Presence: [1..1]Definition: Specifies the sub-product family within a specific family.Data Type: ExternalBankTransactionSubFamilyCodeFormat: maxLength: 4

minLength: 1

2.67 Proprietary <Prtry>Presence: [0..1]Definition: Proprietary identification of the bank transaction code, as defined by the issuer.Type: This message item is composed of the following ProprietaryBankTransactionCodeStructure1 element(s):


2.68 Code <Cd> [1..1] Text


2.68 Code <Cd>Presence: [1..1]Definition: Proprietary bank transaction code to identify the underlying transaction.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.69 Issuer <Issr>Presence: [0..1]Definition: Identification of the issuer of the proprietary bank transaction code.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

SWIFTStandards MX



and start generating interest. Type: This message item is composed of the following CashBalanceAvailability1 element(s):


2.71 Date <Dt> [1..1]








2.73 ActualDate <ActlDt>Presence: [1..1]This message item is part of choice 2.71 Date.Definition: Identifies the actual availability date.Data Type: ISODate


fractionDigits: 5minInclusive: 0totalDigits: 18



CurrencyCode[A-Z]{3,3}






2.76 Entry <Ntry>Presence: [0..n]Definition: Specifies the elements of an entry in the report.

Usage: At least one reference must be provided to identify the entry and its underlying transaction(s).Type: This message item is composed of the following ReportEntry1 element(s):











2.99 CommissionWaiverIndicator <ComssnWvrInd> [0..1] Indicator








SWIFTStandards MX


Rule(s): StatusAndBookingDateRule If Status is pending, BookingDate is not allowed.

Guideline(s): ReferenceGuideline At least one reference should present to identify the underlying transaction(s).

2.77 Amount <Amt>Presence: [1..1]Definition: Amount of money in the cash entry.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.78 CreditDebitIndicator <CdtDbtInd>Presence: [1..1]Definition: Specifies if an entry is a credit or a debit.Data Type: CodeOne of the following CreditDebitCode values must be used:



2.79 ReversalIndicator <RvslInd>Presence: [0..1]Definition: Indicates whether the entry is the result of a reversal operation.

Usage : this element should only be present if the entry is the result of a reversal operation.If the CreditDebitIndicator is CRDT and ReversalIndicator is Yes, the original operation was a debit entry.If the CreditDebitIndicator is DBIT and ReversalIndicator is Yes, the original operation was a credit entry.

Data Type: One of the following TrueFalseIndicator values must be used:MeaningWhenTrue: TrueMeaningWhenFalse: False

2.80 Status <Sts>Presence: [1..1]Definition: Status of an entry on the books of the account servicer.Data Type: CodeOne of the following EntryStatus2Code values must be used:



Code Name DefinitionBOOK Booked Booked means that the transfer of money has been

completed between account servicer and account owner

Usage : Status Booked does not necessarily imply finality of money as this depends on other factors such as the payment system used, the completion of the end-to-end transaction and the terms agreed between account servicer and owner.Status Booked is the only status that can be reversed.

INFO Information Entry is only provided for information, and no booking on the account owner's account in the account servicer's ledger has been performed.

PDNG Pending Booking on the account owner's account in the account servicer's ledger has not been completed.

Usage : this can be used for expected items, or for items for which some conditions still need to be fulfilled before they can be booked. If booking takes place, the entry will be included with status Booked in subsequent account report or statement. Status Pending cannot be reversed.

2.81 BookingDate <BookgDt>Presence: [0..1]Definition: Date and time when an entry is posted to an account on the account servicer's books.

Usage : Booking date is only present if Status is booked.Type: This message item is composed of one of the following DateAndDateTimeChoice element(s):





2.82 ValueDate <ValDt>Presence: [0..1]Definition: Date and time assets become available to the account owner (in a credit entry), or cease to be available to

the account owner (in a debit entry). Usage : When entry status is pending , and value date is present, value date refers to an expected/requested value date.For entries which are subject to availability/float (and for which availability information is present), value date must not be used, as the availability component identifies the number of availability days.

Type: This message item is composed of one of the following DateAndDateTimeChoice element(s):

SWIFTStandards MX






2.83 AccountServicerReference <AcctSvcrRef>Presence: [0..1]Definition: Account servicing institution's reference for the entry.Data Type: Max35TextFormat: maxLength: 35

minLength: 1






2.85 Date <Dt> [1..1]







2.86 NumberOfDays <NbOfDays>Presence: [1..1]This message item is part of choice 2.85 Date.Definition: Indicates the number of float days attached to the balance.



Data Type: Max15PlusSignedNumericTextFormat: [+]{0,1}[0-9]{1,15}









2.90 BankTransactionCode <BkTxCd>Presence: [1..1]Definition: Set of elements to fully identify the type of underlying transaction resulting in the entry.Type: This message item is composed of the following BankTransactionCodeStructure1 element(s):





SWIFTStandards MX









2.92 Code <Cd> [1..1] Code



minLength: 1




2.94 Code <Cd> [1..1] Code



minLength: 1




minLength: 1



2.97 Code <Cd> [1..1] Text



minLength: 1


minLength: 1

2.99 CommissionWaiverIndicator <ComssnWvrInd>Presence: [0..1]Definition: Indicates whether the transaction is exempt from commission.Data Type: One of the following YesNoIndicator values must be used:

MeaningWhenTrue: YesMeaningWhenFalse: No

2.100 AdditionalInformationIndicator <AddtlInfInd>Presence: [0..1]Definition: Indicates whether the underlying transaction details are provided through a separate message, eg in case of

aggregate bookings.Type: This message item is composed of the following MessageIdentification2 element(s):

SWIFTStandards MX





2.101 MessageNameIdentification <MsgNmId>Presence: [0..1]Definition: Specifies the message name identifier of the message that will be used to provide additional details.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.102 MessageIdentification <MsgId>Presence: [0..1]Definition: Specifies the identification of the message that will be used to provide additional details.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.103 Batch <Btch>Presence: [0..n]Definition: Set of elements providing details on batched transactions.

Usage : this element can be repeated in case more than one batch is included in the entry, eg, in lockbox scenarios, to specify the ID and number of transactions included in each of the batches.

Type: This message item is composed of the following BatchInformation1 element(s):





2.104 MessageIdentification <MsgId>Presence: [0..1]Definition: Point to point reference assigned by the sending party to unambiguously identify the batch of transactions.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.105 PaymentInformationIdentification <PmtInfId>Presence: [0..1]Definition: Reference assigned by a sending party to unambiguously identify a payment information block within a

payment message.




minLength: 1

2.106 NumberOfTransactions <NbOfTxs>Presence: [0..1]Definition: Number of individual transactions included in the batch.Data Type: Max15NumericTextFormat: [0-9]{1,15}

2.107 AmountDetails <AmtDtls>Presence: [0..1]Definition: Set of elements providing information on the original amount.

Usage : This component (on entry level) should be used when a total original batch or aggregate amount has to be provided. (If required, the individual original amounts can be included in the same component on transaction details level).

Type: This message item is composed of the following AmountAndCurrencyExchange2 element(s):







2.108 InstructedAmount <InstdAmt>Presence: [0..1]Definition: Identifies the amount of money to be moved between the debtor and creditor, before deduction of charges,

expressed in the currency as ordered by the initiating party and provides currency exchange info in case the instructed amount and/or currency is/are different from the entry amount and/or currency.

Type: This message item is composed of the following AmountAndCurrencyExchangeDetails1 element(s):




2.109 Amount <Amt>Presence: [1..1]Definition: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in

the currency as ordered by the initiating party.Data Type: CurrencyAndAmount

SWIFTStandards MX


This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.110 CurrencyExchange <CcyXchg>Presence: [0..1]Definition: Reports on currency exchange information.Type: This message item is composed of the following CurrencyExchange3 element(s):








2.111 SourceCurrency <SrcCcy>Presence: [1..1]Definition: Currency of the amount to be converted in a currency conversion. Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable

2.112 TargetCurrency <TrgtCcy>Presence: [0..1]Definition: Currency into which an amount is to be converted in a currency conversion. Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable

2.113 UnitCurrency <UnitCcy>Presence: [0..1]Definition: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR,

the unit currency is GBP. Data Type: CurrencyCodeFormat: [A-Z]{3,3}



Rule(s): ValidationByTable

2.114 ExchangeRate <XchgRate>Synonym(s): :92A::EXCH (ISO 15022)Presence: [1..1]Definition: Factor used for the conversion of an amount from one currency into another. This reflects the price at which

one currency was bought with another currency.

Usage: ExchangeRate expresses the ratio between UnitCurrency and QuotedCurrency (ExchangeRate = UnitCurrency/QuotedCurrency).

Data Type: BaseOneRateFormat: fractionDigits: 10

totalDigits: 11

2.115 ContractIdentification <CtrctId>Presence: [0..1]Definition: Unique and unambiguous identifier of the foreign exchange contract. Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.116 QuotationDate <QtnDt>Presence: [0..1]Definition: Date and time at which an exchange rate is quoted.Data Type: ISODateTime

2.117 TransactionAmount <TxAmt>Presence: [0..1]Definition: Amount of the underlying transaction.Type: This message item is composed of the following AmountAndCurrencyExchangeDetails1 element(s):





the currency as ordered by the initiating party.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount


SWIFTStandards MX















the unit currency is GBP. Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable

2.123 ExchangeRate <XchgRate>Synonym(s): :92A::EXCH (ISO 15022)Presence: [1..1]



Definition: Factor used for the conversion of an amount from one currency into another. This reflects the price at which one currency was bought with another currency.



totalDigits: 11


minLength: 1


2.126 CounterValueAmount <CntrValAmt>Presence: [0..1]Definition: Identifies the countervalue amount and provides currency exchange information. Either the counter amount

quoted in an FX deal, or the result of the currency information applied to an instructed amount, before deduction of charges.








Rule(s): CurrencyCode

SWIFTStandards MX


ValidationByTable



















totalDigits: 11


minLength: 1


2.135 AnnouncedPostingAmount <AnncdPstngAmt>Presence: [0..1]Definition: Information on the amount of money, based on terms of corporate action event and balance of underlying

securities, entitled to/from the account owner.

Amount of money, based on terms of corporate action event and balance of underlying securities, entitled to/from the account owner.In those situations, this amount may alternatively be called entitled amount.









SWIFTStandards MX


ValidationByTable



















totalDigits: 11


minLength: 1


2.144 ProprietaryAmount <PrtryAmt>Presence: [0..n]Definition: Provides proprietary amount information.Type: This message item is composed of the following AmountAndCurrencyExchangeDetails2 element(s):


2.145 Type <Tp> [1..1] Text



2.145 Type <Tp>Presence: [1..1]Definition: Identifies the type of amount.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.146 Amount <Amt>Presence: [1..1]Definition: Identifies the proprietary amount.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount


SWIFTStandards MX





totalDigits: 11


minLength: 1


2.154 Charges <Chrgs>Presence: [0..n]Definition: Provides information on the charges included in the entry amount.

Usage : this component is used on entry level in case of batch or aggregate bookings.Type: This message item is composed of the following ChargesInformation3 element(s):


2.155 TotalChargesAndTaxAmount <TtlChrgsAndTaxAmt> [0..1] Amount


2.157 Type <Tp> [0..1]



2.162 Party <Pty> [0..1] +

2.163 Tax <Tax> [0..1]

2.155 TotalChargesAndTaxAmount <TtlChrgsAndTaxAmt>Presence: [0..1]Definition: Total of all charges and taxes applied to the entry.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount

fractionDigits: 5

SWIFTStandards MX


minInclusive: 0totalDigits: 18CurrencyCode[A-Z]{3,3}


2.156 Amount <Amt>Presence: [1..1]Definition: Transaction charges to be paid by the charge bearer.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.157 Type <Tp>Presence: [0..1]Definition: Identifies the type of charge.Type: This message item is composed of one of the following ChargeTypeChoice element(s):


2.158 {Or Code <Cd> [1..1] Code


2.158 Code <Cd>Presence: [1..1]This message item is part of choice 2.157 Type.Definition: Service for which a charge is asked or paid, eg, brokerage fees.Data Type: CodeOne of the following ChargeType1Code values must be used:

Code Name DefinitionBRKF BrokerageFee Fee paid to a broker for services provided.

COMM Commission Fee paid for services provided.

2.159 ProprietaryCode <PrtryCd>Presence: [1..1]This message item is part of choice 2.157 Type.



Definition: Type of charge is a bilaterally agreed code.

Data Type: Max4AlphaNumericTextFormat: [a-zA-Z0-9]{1,4}

2.160 Rate <Rate>Presence: [0..1]Definition: Rate used to calculate the amount of the charge or fee.Data Type: PercentageRateFormat: fractionDigits: 10

totalDigits: 11

2.161 Bearer <Br>Presence: [0..1]Definition: Specifies which party/parties will bear the charges associated with the processing of the payment transaction.Data Type: CodeWhen this message item is present, one of the following ChargeBearerType1Code values must be used:

Code Name DefinitionCRED BorneByCreditor All transaction charges are to be borne by the creditor.

DEBT BorneByDebtor All transaction charges are to be borne by the debtor.

SHAR Shared In a credit transfer context, means that transaction charges on the sender side are to be borne by the debtor, transaction charges on the receiver side are to be borne by the creditor. In a direct debit context, means that transaction charges on the sender side are to be borne by the creditor, transaction charges on the receiver side are to be borne by the debtor.

SLEV FollowingServiceLevel Charges are to be applied following the rules agreed in the service level and/or scheme.

2.162 Party <Pty>Presence: [0..1]Definition: Party that takes the transaction charges or to which the transaction charges are due.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





2.163 Tax <Tax>Presence: [0..1]

SWIFTStandards MX


Definition: Specifies tax details applied to charges.Type: This message item is composed of the following TaxCharges1 element(s):





2.164 Identification <Id>Presence: [0..1]Definition: Reference identifying the nature of tax levied, eg, Value Added Tax (VAT).Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.165 Rate <Rate>Presence: [0..1]Definition: Rate used for calculation of the tax.Data Type: PercentageRateFormat: fractionDigits: 10

totalDigits: 11

2.166 Amount <Amt>Presence: [0..1]Definition: Amount of money resulting from the calculation of the tax.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.167 Interest <Intrst>Presence: [0..n]Definition: Set of elements providing details on the interest amount included in the entry amount.

Usage : This component is used on entry level in case of batch or aggregate bookings.Type: This message item is composed of the following TransactionInterest1 element(s):






2.170 Type <Tp> [0..1]

2.173 Rate <Rate> [0..n]



2.168 Amount <Amt>Presence: [1..1]Definition: Identifies the amount of interest included in the entry amount. Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.169 CreditDebitIndicator <CdtDbtInd>Presence: [1..1]Definition: Identifies whether the interest amount included in the entry amount is positive (CRDT) or negative (DBIT).Data Type: CodeOne of the following CreditDebitCode values must be used:





2.171 {Or Code <Cd> [1..1] Code


SWIFTStandards MX






minLength: 1



2.174 Rate <Rate> [1..1]













totalDigits: 11


minLength: 1



Amount <Amt> [1..1]




2.178 FromToDate <FrToDt>Presence: [0..1]Definition: Range of time between a start date and an end date.Type: This message item is composed of the following DateTimePeriodDetails element(s):





2.179 Reason <Rsn>Presence: [0..1]

SWIFTStandards MX


Definition: Underlying reason for the interest, eg, yearly credit interest on a savings account.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.180 TransactionDetails <TxDtls>Presence: [0..n]Definition: Set of elements providing information on the underlying transaction (s).Type: This message item is composed of the following EntryTransaction1 element(s):

















2.367 Tax <Tax> [0..1] +





2.181 References <Refs>Presence: [0..1]Definition: Set of elements providing the identification of the underlying transaction.Type: This message item is composed of the following TransactionReferences1 element(s):














2.182 MessageIdentification <MsgId>Presence: [0..1]Definition: Point to point reference assigned by the instructing party of the underlying message.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.183 AccountServicerReference <AcctSvcrRef>Presence: [0..1]Definition: The account servicing institution's reference for the transaction. Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.184 InstructionIdentification <InstrId>Presence: [0..1]Definition: Unique identification as assigned by an instructing party for an instructed party to unambiguously identify

the instruction.

Usage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.


minLength: 1

2.185 EndToEndIdentification <EndToEndId>Presence: [0..1]Definition: Unique identification assigned by the initiating party to unumbiguously identify the transaction. This

identification is passed on, unchanged, throughout the entire end-to-end chain.

Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction.

SWIFTStandards MX


Usage: In case there are technical limitations to carry on multiple references, the end-to-end identification must be carried on throughout the entire end-to-end chain.


minLength: 1

2.186 TransactionIdentification <TxId>Presence: [0..1]Definition: Unique identification assigned by the first instructing agent to unambiguously identify the transaction and

passed on, unchanged, throughout the entire interbank chain.

Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to the transaction on the interbank level. Usage: The instructing agent has to make sure the transaction identification is unique for a pre-agreed period.


minLength: 1

2.187 MandateIdentification <MndtId>Presence: [0..1]Definition: Reference of the direct debit mandate that has been signed between by the debtor and the creditor.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.188 ChequeNumber <ChqNb>Presence: [0..1]Definition: Identifies the cheque number.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.189 ClearingSystemReference <ClrSysRef>Presence: [0..1]Definition: Unique and unambiguous identifier for a payment instruction, assigned by the clearing system.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.190 Proprietary <Prtry>Presence: [0..1]Definition: Proprietary reference of an underlying transaction.Type: This message item is composed of the following ProprietaryReference1 element(s):




2.191 Type <Tp> [1..1] Text


2.191 Type <Tp>Presence: [1..1]Definition: Identifies the type of reference reported.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.192 Reference <Ref>Presence: [1..1]Definition: Proprietary reference specification related to the underlying transaction.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.193 AmountDetails <AmtDtls>Presence: [0..1]Definition: Set of elements providing details information on the original amount.

Usage: This component (on transaction level) should be used in case booking is for a single transaction and the original amount is different from the entry amount. It can also be used in case individual original amounts are provided in case of a batch or aggregate booking.











SWIFTStandards MX


















2.198 TargetCurrency <TrgtCcy>Presence: [0..1]



Definition: Currency into which an amount is to be converted in a currency conversion. Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable







totalDigits: 11


minLength: 1






SWIFTStandards MX








totalDigits: 11


minLength: 1








SWIFTStandards MX








totalDigits: 11


minLength: 1









SWIFTStandards MX








totalDigits: 11


minLength: 1




2.231 Type <Tp> [1..1] Text



SWIFTStandards MX



minLength: 1























totalDigits: 11


minLength: 1


2.240 Availability <Avlbty>Presence: [0..n]Definition: Set of elements used to indicate when the booked funds will become available, ie can be accessed and start

generating interest.



SWIFTStandards MX



2.241 Date <Dt> [1..1]




















2.247 Domain <Domn> [0..1]










2.248 Code <Cd> [1..1] Code

2.249 Family <Fmly> [1..1]

SWIFTStandards MX



minLength: 1




2.250 Code <Cd> [1..1] Code



minLength: 1


minLength: 1



2.253 Code <Cd> [1..1] Text


2.253 Code <Cd>Presence: [1..1]



Definition: Proprietary bank transaction code to identify the underlying transaction.Data Type: Max35TextFormat: maxLength: 35

minLength: 1


minLength: 1


Usage : This component (on transaction level) can be used in case the booking is for a single transaction, and charges are included in the entry amount. It can also be used in case individual charge amounts are applied to individual transactions in case of a batch or aggregate amount booking.

Type: This message item is composed of the following ChargesInformation3 element(s):




2.258 Type <Tp> [0..1]



2.263 Party <Pty> [0..1] +

2.264 Tax <Tax> [0..1]




SWIFTStandards MX







2.259 {Or Code <Cd> [1..1] Code





2.260 ProprietaryCode <PrtryCd>Presence: [1..1]This message item is part of choice 2.258 Type.Definition: Type of charge is a bilaterally agreed code.





totalDigits: 11











2.264 Tax <Tax>Presence: [0..1]Definition: Specifies tax details applied to charges.Type: This message item is composed of the following TaxCharges1 element(s):

SWIFTStandards MX







minLength: 1


totalDigits: 11





Usage : This component (on transaction level) can be used in case the booking is for a single transaction, and interest amount is included in the entry amount. It can also be used in case individual interest amounts are applied to individual transactions in case of a batch or aggregate amount booking.

Type: This message item is composed of the following TransactionInterest1 element(s):






2.271 Type <Tp> [0..1]

2.274 Rate <Rate> [0..n]











2.272 {Or Code <Cd> [1..1] Code


SWIFTStandards MX






minLength: 1



2.275 Rate <Rate> [1..1]













totalDigits: 11


minLength: 1



Amount <Amt> [1..1]










SWIFTStandards MX



minLength: 1

2.281 RelatedParties <RltdPties>Presence: [0..1]Definition: Set of elements identifying the parties related to the underlying transaction.Type: This message item is composed of the following TransactionParty1 element(s):



2.283 Debtor <Dbtr> [0..1] +








2.282 InitiatingParty <InitgPty>Presence: [0..1]Definition: Party initiating the payment to an agent. In the payment context, this can either be the debtor (in a credit

transfer), the creditor (in a direct debit), or a party that initiates the payment on behalf of the debtor or creditor. In the context of treasury, the party that instructs the trading party to execute a treasury deal on its behalf.

Type: This message item is composed of the following PartyIdentification8 element(s):







2.283 Debtor <Dbtr>Presence: [0..1]Definition: Party that owes an amount of money to the (ultimate) creditor.Type: This message item is composed of the following PartyIdentification8 element(s):









2.284 DebtorAccount <DbtrAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the debtor.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]




2.285 UltimateDebtor <UltmtDbtr>Presence: [0..1]Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.Type: This message item is composed of the following PartyIdentification8 element(s):







2.286 Creditor <Cdtr>Presence: [0..1]Definition: Party to which an amount of money is due.Type: This message item is composed of the following PartyIdentification8 element(s):

SWIFTStandards MX








2.287 CreditorAccount <CdtrAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the creditor of the payment transaction.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]




2.288 UltimateCreditor <UltmtCdtr>Presence: [0..1]Definition: Ultimate party to which an amount of money is due.Type: This message item is composed of the following PartyIdentification8 element(s):







2.289 TradingParty <TradgPty>Presence: [0..1]Definition: Party that plays an active role in planning and executing the transactions that create or liquidate investments

of the investors assets, or that move the investor's assets from one investment to another. A trading party is a trade instructor, an investment decision-maker, a post trade administrator, or a trader. In the context of treasury, it is the party negotiates and executes the treasury transaction.










2.290 Proprietary <Prtry>Presence: [0..n]Definition: Provides proprietary party information.Type: This message item is composed of the following ProprietaryParty1 element(s):


2.291 Type <Tp> [1..1] Text

2.292 Party <Pty> [1..1] +

2.291 Type <Tp>Presence: [1..1]Definition: Identifies the type of proprietary party reported.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.292 Party <Pty>Presence: [1..1]Definition: Proprietary party.Type: This message item is composed of the following PartyIdentification8 element(s):







2.293 RelatedAgents <RltdAgts>Presence: [0..1]Definition: Set of elements identifying the agents related to the underlying transaction.

SWIFTStandards MX


Type: This message item is composed of the following TransactionAgents1 element(s):












2.294 DebtorAgent <DbtrAgt>Presence: [0..1]Definition: Financial institution servicing an account for the debtor.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





2.295 CreditorAgent <CdtrAgt>Presence: [0..1]Definition: Financial institution servicing an account for the creditor.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





2.296 IntermediaryAgent1 <IntrmyAgt1>Presence: [0..1]Definition: Agent between the debtor agent and creditor agent.



Usage: If more than one intermediary agent is present, then IntermediaryAgent1 identifies the agent between the debtor agent and the intermediary agent 2.

Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):






Usage: If more than two intermediary agents are present, then IntermediaryAgent2 identifies the agent between the intermediary agent 1 and the intermediary agent 3.







Usage: If IntermediaryAgent3 is present, then it identifies the agent between the intermediary agent 2 and the creditor agent.






2.299 ReceivingAgent <RcvgAgt>Presence: [0..1]

SWIFTStandards MX


Definition: Party that receives securities from the delivering agent at the place of settlement, eg, central securities depository.Can also be used in the context of treasury operations.






2.300 DeliveringAgent <DlvrgAgt>Presence: [0..1]Definition: Party that delivers securities to the receiving agent at the place of settlement, eg, central securities depository.

Can also be used in the context of treasury operations.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





2.301 IssuingAgent <IssgAgt>Presence: [0..1]Definition: Legal entity that has the right to issue securities.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





2.302 SettlementPlace <SttlmPlc>Presence: [0..1]Definition: Place where settlement of the securities takes place.

Note : this is typed by a financial institution identification - as this is the standard way of identifying eg securities settlement agent/central system.








2.303 Proprietary <Prtry>Presence: [0..n]Definition: Proprietary agent related to the underlying transaction.Type: This message item is composed of the following ProprietaryAgent1 element(s):


2.304 Type <Tp> [1..1] Text

2.305 Agent <Agt> [1..1] +

2.304 Type <Tp>Presence: [1..1]Definition: Identifies the type of proprietary agent reported.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.305 Agent <Agt>Presence: [1..1]Definition: Proprietary agent.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





2.306 Purpose <Purp>Presence: [0..1]Definition: Underlying reason for the payment transaction, eg, a charity payment, or a commercial agreement between

the creditor and the debtor.

SWIFTStandards MX


Usage: purpose is used by the end-customers, ie originating party, initiating party, debtor, creditor, final party, to provide information concerning the nature of the payment transaction. Purpose is a content element, which is not used for processing by any of the agents involved in the payment chain.

Type: This message item is composed of one of the following Purpose1Choice element(s):


2.307 {Or Code <Cd> [1..1] Code


2.307 Code <Cd>Presence: [1..1]This message item is part of choice 2.306 Purpose.Definition: Specifies the underlying reason for the payment transaction, as published in an external purpose code list.Data Type: ExternalPurposeCodeFormat: maxLength: 35

minLength: 1

2.308 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.306 Purpose.Definition: User community specific purpose.

Usage: When available, codes provided by local communities should be used.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.309 RelatedRemittanceInformation <RltdRmtInf>Presence: [0..10]Definition: Information related to the handling of the remittance information by any of the agents in the transaction

processing chain.Type: This message item is composed of the following RemittanceLocation1 element(s):




2.312 RemittanceLocationElectronicAddress <RmtLctnElctrncAdr> [0..1] Text


2.310 RemittanceIdentification <RmtId>Presence: [0..1]Definition: Unique and unambiguous identification of the remittance information, e.g. a remittance advice, which is sent

separately from the payment instruction.




minLength: 1

2.311 RemittanceLocationMethod <RmtLctnMtd>Presence: [0..1]Definition: Specifies the method used to deliver the remittance advice information.Data Type: CodeWhen this message item is present, one of the following RemittanceLocationMethod1Code values must be used:

Code Name DefinitionEDIC ElectronicDataInterchange Remittance advice information must be sent through

Electronic Data Interchange (EDI).

EMAL EMail Remittance advice information must be sent through e-mail.

FAXI Fax Remittance advice information must be faxed.

POST Post Remittance advice information must be sent through postal services.

URID UniformResourceIdentifier Remittance advice information needs to be sent to a Uniform Resource Identifier (URI). URI is a compact string of characters that uniquely identify an abstract or physical resource. URI's are the super-set of identifiers, such as URLs, email addresses, ftp sites, etc, and as such, provide the syntax for all of the identification schemes.

2.312 RemittanceLocationElectronicAddress <RmtLctnElctrncAdr>Presence: [0..1]Definition: Electronic address to which an agent is to send the remittance information.Data Type: Max256TextFormat: maxLength: 256

minLength: 1

2.313 RemittanceLocationPostalAddress <RmtLctnPstlAdr>Presence: [0..1]Definition: Postal address to which an agent is to send the remittance information.Type: This message item is composed of the following NameAndAddress3 element(s):


2.314 Name <Nm> [1..1] Text

2.315 Address <Adr> [1..1] +

2.314 Name <Nm>Presence: [1..1]Definition: Name by which a party is known and is usually used to identify that identity.

SWIFTStandards MX



minLength: 1

2.315 Address <Adr>Presence: [1..1]Definition: Postal address of a party.Type: This message item is composed of the following PostalAddress1 element(s):


AddressType <AdrTp> [0..1] Code

AddressLine <AdrLine> [0..5] Text

StreetName <StrtNm> [0..1] Text

BuildingNumber <BldgNb> [0..1] Text

PostCode <PstCd> [0..1] Text

TownName <TwnNm> [0..1] Text

CountrySubDivision <CtrySubDvsn> [0..1] Text

Country <Ctry> [1..1] Code

For additional Type information, please refer to PostalAddress1 p.533 in 'Message Item Types' section.

2.316 RemittanceInformation <RmtInf>Presence: [0..1]Definition: Information that enables the matching, ie, reconciliation, of a payment with the items that the payment is

intended to settle, eg, commercial invoices in an account receivable system.Type: This message item is composed of the following RemittanceInformation1 element(s):




2.317 Unstructured <Ustrd>Presence: [0..n]Definition: Information supplied to enable the matching of an entry with the items that the transfer is intended to settle,

eg, commercial invoices in an accounts' receivable system in an unstructured form.Data Type: Max140TextFormat: maxLength: 140

minLength: 1

2.318 Structured <Strd>Presence: [0..n]



Definition: Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, eg, commercial invoices in an accounts' receivable system in a structured form.

Type: This message item is composed of the following StructuredRemittanceInformation6 element(s):








2.340 AdditionalRemittanceInformation <AddtlRmtInf> [0..1] Text

2.319 ReferredDocumentInformation <RfrdDocInf>Presence: [0..1]Definition: Reference information to allow the identification of the underlying reference documents.Type: This message item is composed of the following ReferredDocumentInformation1 element(s):




2.320 ReferredDocumentType <RfrdDocTp>Presence: [0..1]Definition: Provides the type of the referred document.Type: This message item is composed of the following ReferredDocumentType1 element(s):


2.321 {Or Code <Cd> [1..1] Code



2.321 Code <Cd>Presence: [1..1]This message item is part of choice 2.320 ReferredDocumentType.Definition: Document type in a coded form.Data Type: CodeOne of the following DocumentType2Code values must be used:

SWIFTStandards MX


Code Name DefinitionCINV CommercialInvoice Document is an invoice.

CMCN CommercialContract Document is an agreement between the parties, stipulating the terms and conditions of the delivery of goods or services.

CNFA CreditNoteRelatedToFinancialAdjustment

Document is a credit note for the final amount settled for a commercial transaction.

CREN CreditNote Document is a credit note.

DEBN DebitNote Document is a debit note.

DISP DispatchAdvice Document is a dispatch advice.

DNFA DebitNoteRelatedToFinancialAdjustment

Document is a debit note for the final amount settled for a commercial transaction.

HIRI HireInvoice Document is an invoice for the hiring of human resources or renting goods or equipment.

MSIN MeteredServiceInvoice Document is an invoice claiming payment for the supply of metered services, eg, gas or electricity, supplied to a fixed meter.

SBIN SelfBilledInvoice Document is an invoice issued by the debtor.

SOAC StatementOfAccount Document is a statement of the transactions posted to the debtor's account at the supplier.

2.322 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.320 ReferredDocumentType.Definition: Proprietary identification of the type of the remittance document.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.323 Issuer <Issr>Presence: [0..1]Definition: Identification of the issuer of the reference document type.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.324 ReferredDocumentNumber <RfrdDocNb>Presence: [0..1]Definition: Unique and unambiguous identification number of the referred document.Data Type: Max35TextFormat: maxLength: 35

minLength: 1



2.325 ReferredDocumentRelatedDate <RfrdDocRltdDt>Presence: [0..1]Definition: Date associated with the referred document, eg, date of issue. Data Type: ISODate

2.326 ReferredDocumentAmount <RfrdDocAmt>Presence: [0..n]Definition: Amount of money and currency of a document referred to in the remittance section. The amount is typically

either the original amount due and payable, or the amount actually remitted for the referred document.Type: This message item is composed of one of the following ReferredDocumentAmount1Choice element(s):







2.327 DuePayableAmount <DuePyblAmt>Presence: [1..1]This message item is part of choice 2.326 ReferredDocumentAmount.Definition: Amount specified is the exact amount due and payable to the creditor.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.328 DiscountAppliedAmount <DscntApldAmt>Presence: [1..1]This message item is part of choice 2.326 ReferredDocumentAmount.Definition: Amount of money resulting from the application of an agreed discount to the amount due and payable to the

creditor.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount


SWIFTStandards MX




2.329 RemittedAmount <RmtdAmt>Presence: [1..1]This message item is part of choice 2.326 ReferredDocumentAmount.Definition: Amount of money remitted for the referred document.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.330 CreditNoteAmount <CdtNoteAmt>Presence: [1..1]This message item is part of choice 2.326 ReferredDocumentAmount.Definition: Amount specified for the referred document is the amount of a credit note.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.331 TaxAmount <TaxAmt>Presence: [1..1]This message item is part of choice 2.326 ReferredDocumentAmount.Definition: Quantity of cash resulting from the calculation of the tax.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount





2.332 CreditorReferenceInformation <CdtrRefInf>Presence: [0..1]Definition: Reference information provided by the creditor to allow the identification of the underlying documents.Type: This message item is composed of the following CreditorReferenceInformation1 element(s):




2.333 CreditorReferenceType <CdtrRefTp>Presence: [0..1]Definition: Provides the type of the creditor reference.Type: This message item is composed of the following CreditorReferenceType1 element(s):


2.334 {Or Code <Cd> [1..1] Code



2.334 Code <Cd>Presence: [1..1]This message item is part of choice 2.333 CreditorReferenceType.Definition: Coded creditor reference type.Data Type: CodeOne of the following DocumentType3Code values must be used:

Code Name DefinitionDISP DispatchAdvice Document is a dispatch advice.

FXDR ForeignExchangeDealReference

Document is a pre-agreed or pre-arranged foreign exchange transaction to which the payment transaction refers.

PUOR PurchaseOrder Document is a purchase order.

RADM RemittanceAdviceMessage Document is a remittance advice sent separately from the current transaction.

RPIN RelatedPaymentInstruction Document is a linked payment instruction to which the current payment instruction is related, eg, in a cover scenario.

SCOR StructuredCommunicationReference

Document is a structured communication reference provided by the creditor to identify the referred transaction.

SWIFTStandards MX


2.335 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.333 CreditorReferenceType.Definition: Creditor reference type not avilable in a coded format.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.336 Issuer <Issr>Presence: [0..1]Definition: Identification of the issuer of the credit reference type.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.337 CreditorReference <CdtrRef>Presence: [0..1]Definition: Unique and unambiguous reference assigned by the creditor to refer to the payment transaction.

Usage: if available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the cash.

If the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.


minLength: 1

2.338 Invoicer <Invcr>Presence: [0..1]Definition: Identification of the organization issuing the invoice when different than the creditor or final party.Type: This message item is composed of the following PartyIdentification8 element(s):







2.339 Invoicee <Invcee>Presence: [0..1]



Definition: Identification of the party to whom an invoice is issued, when different than the originator or debtor.Type: This message item is composed of the following PartyIdentification8 element(s):







2.340 AdditionalRemittanceInformation <AddtlRmtInf>Presence: [0..1]Definition: Additional information, in free text form, to complement the structured remittance information.Data Type: Max140TextFormat: maxLength: 140

minLength: 1

2.341 RelatedDates <RltdDts>Presence: [0..1]Definition: Set of elements identifying the dates related to the underlying transactions.Type: This message item is composed of the following TransactionDates1 element(s):









2.342 AcceptanceDateTime <AccptncDtTm>Presence: [0..1]Definition: Point in time when the payment order from the initiating party meets the processing conditions of the account

servicing agent (debtor's agent in case of a credit transfer, creditor's agent in case of a direct debit). This means - amongst others - that the account servicing agent has received the payment order and has applied checks as eg, authorisation, availability of funds.

Data Type: ISODateTime

2.343 TradeDate <TradDt>Presence: [0..1]

SWIFTStandards MX


Definition: Date on which the trade was executed.Data Type: ISODate

2.344 InterbankSettlementDate <IntrBkSttlmDt>Presence: [0..1]Definition: Date on which the amount of money ceases to be available to the agent that owes it and when the amount of

money becomes available to the agent to which it is due.Data Type: ISODate

2.345 StartDate <StartDt>Presence: [0..1]Definition: Start date of the underlying transaction, such as a treasury transaction, an investment plan.Data Type: ISODate

2.346 EndDate <EndDt>Presence: [0..1]Definition: End date of the underlying transaction, such as a treasury transaction, an investment plan.Data Type: ISODate

2.347 TransactionDateTime <TxDtTm>Presence: [0..1]Definition: Date and time of the underlying transaction.Data Type: ISODateTime

2.348 Proprietary <Prtry>Presence: [0..n]Definition: Proprietary date related to the underlying transaction.Type: This message item is composed of the following ProprietaryDate1 element(s):


2.349 Type <Tp> [1..1] Text



2.349 Type <Tp>Presence: [1..1]Definition: Identifies the type of date reported.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.350 Date <Dt>Presence: [1..1]



This message item is part of choice 2.348 Proprietary.Definition: Date in ISO format.Data Type: ISODate

2.351 DateTime <DtTm>Presence: [1..1]This message item is part of choice 2.348 Proprietary.Definition: Date and time in ISO format.Data Type: ISODateTime

2.352 RelatedPrice <RltdPric>Presence: [0..1]Definition: Set of elements identifying the price information related to the underlying transaction.Type: This message item is composed of one of the following TransactionPrice1Choice element(s):




2.353 DealPrice <DealPric>Presence: [1..1]This message item is part of choice 2.352 RelatedPrice.Definition: Specifies the price of the traded financial instrument.

This is the deal price of the individual trade transaction. If there is only one trade transaction for the execution of the trade, then the deal price could equal the executed trade price (unless, for example, the price includes commissions or rounding, or some other factor has been applied to the deal price or the executed trade price, or both).

Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.354 Proprietary <Prtry>Presence: [1..n]This message item is part of choice 2.352 RelatedPrice.Definition: Proprietary price specification of the underlying transaction.Type: This message item is composed of the following ProprietaryPrice1 element(s):

SWIFTStandards MX



2.355 Type <Tp> [1..1] Text


2.355 Type <Tp>Presence: [1..1]Definition: Identifies the type of price reported.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.356 Price <Pric>Presence: [1..1]Definition: Proprietary price specification related to the underlying transaction.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.357 RelatedQuantities <RltdQties>Presence: [0..n]Definition: Identifies related quantities (eg of securities) in the underlying transaction.Type: This message item is composed of one of the following TransactionQuantities1Choice element(s):


2.358 {Or Quantity <Qty> [1..1] +


2.358 Quantity <Qty>Presence: [1..1]This message item is part of choice 2.357 RelatedQuantities.Definition: Specifies the quantity (eg of securities) in the underlying transaction.Type: This message item is composed of one of the following FinancialInstrumentQuantityChoice element(s):


{Or Unit <Unit> [1..1] Quantity




Or FaceAmount <FaceAmt> [1..1] Amount

Or} AmortisedValue <AmtsdVal> [1..1] Amount

For additional Type information, please refer to FinancialInstrumentQuantityChoice p.535 in 'Message Item Types' section.

2.359 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.357 RelatedQuantities.Definition: Proprietary quantities specification defined in the underlying transaction.Type: This message item is composed of the following ProprietaryQuantity1 element(s):


2.360 Type <Tp> [1..1] Text


2.360 Type <Tp>Presence: [1..1]Definition: Identifies the type of proprietary quantity reported.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.361 Quantity <Qty>Presence: [1..1]Definition: Provides the proprietary quantity in free format.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.362 FinancialInstrumentIdentification <FinInstrmId>Presence: [0..1]Definition: Identification of a security, as assigned under a formal or proprietary identification scheme.Type: This message item is composed of one of the following SecurityIdentification4Choice element(s):




SWIFTStandards MX


2.363 ISIN <ISIN>Presence: [1..1]This message item is part of choice 2.362 FinancialInstrumentIdentification.Definition: International Securities Identification Number (ISIN). A numbering system designed by the United Nation's

International Organisation for Standardisation (ISO). The ISIN is composed of a 2-character prefix representing the country of issue, followed by the national security number (if one exists), and a check digit. Each country has a national numbering agency that assigns ISIN numbers for securities in that country.

Data Type: ISINIdentifierFormat: [A-Z0-9]{12,12}

2.364 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.362 FinancialInstrumentIdentification.Definition: Proprietary identification of an underlying financial instrument.Type: This message item is composed of the following AlternateSecurityIdentification2 element(s):


2.365 Type <Tp> [1..1] Text


2.365 Type <Tp>Presence: [1..1]Definition: Identifies the type of financial instrument identifier type.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.366 Identification <Id>Presence: [1..1]Definition: Unique and unambiguous identifier of a security.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.367 Tax <Tax>Presence: [0..1]Definition: Amount of money due to the government or tax authority, according to various pre-defined parameters such

as thresholds or income.Type: This message item is composed of the following TaxInformation2 element(s):


CreditorTaxIdentification <CdtrTaxId> [0..1] Text

CreditorTaxType <CdtrTaxTp> [0..1] Text




DebtorTaxIdentification <DbtrTaxId> [0..1] Text

TaxReferenceNumber <TaxRefNb> [0..1] Text

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount

TotalTaxAmount <TtlTaxAmt> [0..1] Amount

TaxDate <TaxDt> [0..1] DateTime

TaxTypeInformation <TaxTpInf> [0..n]

For additional Type information, please refer to TaxInformation2 p.536 in 'Message Item Types' section.

2.368 ReturnInformation <RtrInf>Presence: [0..1]Definition: Set of elements specifying the return information.Type: This message item is composed of the following ReturnReasonInformation5 element(s):





2.382 AdditionalReturnReasonInformation <AddtlRtrRsnInf> [0..n] Text

Rule(s): ReturnReasonRule If ReturnReason/Code is equal to 'NARR', then at least one occurrence of AdditionalReturnReasonInformation must be present.

2.369 OriginalBankTransactionCode <OrgnlBkTxCd>Presence: [0..1]Definition: Bank transaction code included in the original entry for the transaction.Type: This message item is composed of the following BankTransactionCodeStructure1 element(s):


2.370 Domain <Domn> [0..1]





SWIFTStandards MX







2.371 Code <Cd> [1..1] Code

2.372 Family <Fmly> [1..1]


minLength: 1




2.373 Code <Cd> [1..1] Code



minLength: 1




minLength: 1



2.376 Code <Cd> [1..1] Text



minLength: 1


minLength: 1

2.378 ReturnOriginator <RtrOrgtr>Presence: [0..1]Definition: Party issuing the return.Type: This message item is composed of the following PartyIdentification8 element(s):







2.379 ReturnReason <RtrRsn>Presence: [0..1]Definition: Specifies the reason for the return.Type: This message item is composed of one of the following ReturnReason1Choice element(s):

SWIFTStandards MX



2.380 {Or Code <Cd> [1..1] Code


2.380 Code <Cd>Presence: [1..1]This message item is part of choice 2.379 ReturnReason.Definition: Reason for the return in a coded form.Data Type: CodeOne of the following TransactionRejectReason2Code values must be used:

Code Name DefinitionAC01 IncorrectAccountNumber Format of the account number specified is not correct.

AC04 ClosedAccountNumber Account number specified has been closed on the Receiver's books.

AC06 BlockedAccount Account specified is blocked, prohibiting posting of transactions against it.

AG01 TransactionForbidden Transaction forbidden on this type of account (formerly NoAgreement).

AG02 InvalidBankOperationCode Bank Operation code specified in the message is not valid for receiver.

AM01 ZeroAmount Specified message amount is equal to zero.

AM02 NotAllowedAmount Specified transaction/message amount is greater than allowed maximum.

AM03 NotAllowedCurrency Specified message amount is in an non processable currency outside of existing agreement.

AM04 InsufficientFunds Amount of funds available to cover specified message amount is insufficient.

AM05 Duplication This message appears to have been duplicated.

AM06 TooLowAmount Specified transaction amount is less than agreed minimum.

AM07 BlockedAmount Amount specified in message has been blocked by regulatory authorities.

AM09 WrongAmount Amount received is not the amount agreed or expected.

AM10 InvalidControlSum Sum of instructed amounts does not equal the control sum.

BE01 InconsistentWithEndCustomer

Identification of end customer is not consistent with associated account number. (formerly CreditorConsistency)

BE04 MissingCreditorAddress Specification of creditor's address, which is required for payment, is missing/not correct (formerly IncorrectCreditorAddress).

BE05 UnrecognisedInitiatingParty Party who initiated the message is not recognised by the end customer.



Code Name DefinitionBE06 UnknownEndCustomer End customer specified is not known at associated Sort/

National Bank Code or does no longer exist in the books.

BE07 MissingDebtorAddress Specification of debtor's address, which is required for payment, is missing/not correct.

DT01 InvalidDate Invalid date (eg, wrong settlement date).

ED01 CorrespondentBankNotPossible

Correspondent bank not possible.

ED03 BalanceInfoRequested Balance of payments complementary info is requested.

ED05 SettlementFailed Settlement of the transaction has failed.

MD01 NoMandate Mandate is cancelled or invalid.

MD02 MissingMandatoryInformationInMandate

Mandate related information data required by the scheme is missing.

MD03 InvalidFileFormatForOtherReasonThanGroupingIndicator

File format incomplete or invalid.

MD04 InvalidFileFormatForGroupingIndicator

File format incorrect in terms of grouping indicator.

MD06 RefundRequestByEndCustomer

Return of funds requested by end customer.

MD07 EndCustomerDeceased End customer is deceased.

MS02 NotSpecifiedReasonCustomerGenerated

Reason has not been specified by end customer.

MS03 NotSpecifiedReasonAgentGenerated

Reason has not been specified by agent.

NARR Narrative Reason is provided as narrative information in the additional reason information.

RC01 BankIdentifierIncorrect Bank identifier code specified in the message has an incorrect format (formerly IncorrectFormatForRoutingCode).

RF01 NotUniqueTransactionReference

Transaction reference is not unique within the message.

TM01 CutOffTime Associated message was received after agreed processing cut-off time.

2.381 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.379 ReturnReason.Definition: Reason for the return not catered for by the available codes.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

SWIFTStandards MX


2.382 AdditionalReturnReasonInformation <AddtlRtrRsnInf>Presence: [0..n]Definition: Further details on the return reason.Data Type: Max105TextFormat: maxLength: 105

minLength: 1

2.383 CorporateAction <CorpActn>Presence: [0..1]Definition: Set of elements identifying the underlying corporate action.Type: This message item is composed of the following CorporateAction1 element(s):


2.384 Code <Cd> [0..1] Text



2.384 Code <Cd>Presence: [0..1]Definition: Specifies the code of corporate action event, in free-text format.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.385 Number <Nb>Presence: [0..1]Definition: Reference assigned by the account servicer to unambiguously identify a corporate action event.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.386 Proprietary <Prtry>Presence: [0..1]Definition: Proprietary corporate action event information.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.387 SafekeepingAccount <SfkpgAcct>Presence: [0..1]Definition: Safekeeping or investment account. A safekeeping account is an account on which a securities entry is made.

An investment account is an account between an investor(s) and a fund manager or a fund. The account can



contain holdings in any investment fund or investment fund class managed (or distributed) by the fund manager, within the same fund family.




Type <Tp> [0..1]




2.388 AdditionalTransactionInformation <AddtlTxInf>Presence: [0..1]Definition: Further details on the transaction details.Data Type: Max500TextFormat: maxLength: 500

minLength: 1

2.389 AdditionalEntryInformation <AddtlNtryInf>Presence: [0..1]Definition: Further details on the entry details.Data Type: Max500TextFormat: maxLength: 500

minLength: 1

2.390 AdditionalReportInformation <AddtlRptInf>Presence: [0..1]Definition: Further details on the account report.Data Type: Max500TextFormat: maxLength: 500

minLength: 1

Business ExampleNarrativeAAAA Banken has agreed to provide an intraday account report to its customer Finpetrol. Each business day, at 12.30 PM, AAAA Banken will provide Finpetrol with an overview of all booked and expected entries since the start of the business day. On 18 October, at 12.30 PM, AAAASESS sends such an intraday BankToCustomerAccountReport to Company Finpetrol. It contains two entries : one booked, and one expected item. It has been pre-agreed between account servicer and account owner that AAAA Banken will not include (expected) balance info in this intraday report.

Business Description

Element <XMLTag> Content

SWIFTStandards MX


Group Header <GrpHdr>

MessageIdentification <MsgId> AAAASESS-FP-ACCR001

CreationDateTime <CreDtTm> 2007-10-18T12:30:00+01:00

MessagePagination <MsgPgntn>

PageNumber <PgNb> 1

LastPageIndicator <LastPgInd> true

Report <Rpt>

Identification <Id> AAAASESS-FP-ACCR001


FromToDate <FrToDt>

FromDateTime <FrmDtTm> 2007-10-18T08:00:00+01:00

ToDateTime <ToDtTm> 2007-10-18T12:30:00+01:00

Account <Acct>

Identification <Id>

ProprietaryAccount <PrtryAcct>

ID <Id> 50000000054910000003

Owner <Ownr>

Name <Nm> FINPETROL

Servicer <Svcr>

FinancialInstitutionIdentification <FinInstnId>

NameAndPostalAddress <NmAndAdr>

Name <Nm> AAAA BANKEN

Country <Ctry> SE

Entry <Ntry>

Amount <Amt Ccy=SEK> 200000

CreditDebitIndicator <CdtDbtInd> DBIT

Status <Sts> BOOK

BookingDate <BookgDt>

DateTime <DtTm> 2007-10-18T10:15:00+01:00

ValueDate <ValDt>

Date <Dt> 2007-10-18

AccountServicerReference <AcctSvcrRef> AAAASESS-FP-ACCR-01

BankTransactionCode <BkTxCd>

Domain <Domn>

Code <Cd> PAYM

Family <Fmly>

Code <Cd> 0001



SubFamilyCode <SbFmlyCd> 0003

Batch <Btch

MessageIdentification <MsgId> FINP-0055

PaymentInformationIdentification <PmtInfID> FINP-0055–001

NumberOfTransactions <NbOfTxs> 20

Entry <Ntry>


CreditDebitIndicator <CdtDbtInd> CRED

Status <Sts> PDNG

ValueDate <ValDt>

Date <Dt> 2007-10-18

AccountServicerReference <AcctSvcrRef> AAAASESS-FP-CONF-FX


Domain <Domn>

Code <Cd> TREA

Family <Fmly>

Code <Cd> 0002


TransactionDetails <TxDtls>

References <Refs>

InstructionID <InstrId> FP-004567-FX

EndToEndId <End2EndID> AAAASS1085FINPSS

AmountDetails <AmtDtls>

CountervalueAmount <CntrValAmt>

Amount <Amt Ccy=EUR> 3255.5694

CurrencyExchange <CcyXchg>

SourceCurrency <SrcCcy> EUR

ExchangeRate <XchRate> 0.1085

XML Instance<?xml version = "1.0" encoding = "UTF-8"?><Document xmlns = "urn:iso:std:iso:20022:tech:xsd:camt.052.001.01" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance">

<BkToCstmrAcctRptV01><GrpHdr>

<MsgId>AAAASESS-FP-ACCR001</MsgId><CreDtTm>2007-10-18T12:30:00+01:00</CreDtTm><MsgPgntn>

<PgNb>1</PgNb><LastPgInd>true</LastPgInd>

SWIFTStandards MX


</MsgPgntn></GrpHdr><Rpt>

<Id>AAAASESS-FP-ACCR001</Id><CreDtTm>2007-10-18T12:30:00+01:00</CreDtTm><FrToDt>

<FrDtTm>2007-10-18T08:00:00+01:00</FrDtTm><ToDtTm>2007-10-18T12:30:00+01:00</ToDtTm>

</FrToDt><Acct>

<Id><PrtryAcct>

<Id>50000000054910000003</Id></PrtryAcct>

</Id><Ownr>

<Nm>FINPETROL</Nm></Ownr><Svcr>

<FinInstnId><NmAndAdr>

<Nm>AAAA BANKEN</Nm><PstlAdr>

<Ctry>SE</Ctry></PstlAdr>

</NmAndAdr></FinInstnId>

</Svcr></Acct><Ntry>

<Amt Ccy = "SEK">200000</Amt><CdtDbtInd>DBIT</CdtDbtInd><Sts>BOOK</Sts><BookgDt>

<DtTm>2007-10-18T10:15:00+01:00</DtTm></BookgDt><ValDt>

<Dt>2007-10-18</Dt></ValDt><AcctSvcrRef>AAAASESS-FP-ACCR-01</AcctSvcrRef><BkTxCd>

<Domn><Cd>PAYM</Cd><Fmly>

<Cd>0001</Cd><SubFmlyCd>0003</SubFmlyCd>

</Fmly></Domn>

</BkTxCd><Btch>

<MsgId>FINP-0055</MsgId><PmtInfId>FINP-0055-001</PmtInfId>



<NbOfTxs>20</NbOfTxs></Btch>

</Ntry><Ntry>

<Amt Ccy = "SEK">30000</Amt><CdtDbtInd>CRDT</CdtDbtInd><Sts>PDNG</Sts><ValDt>

<Dt>2007-10-18</Dt></ValDt><AcctSvcrRef>AAAASESS-FP-CONF-FX</AcctSvcrRef><BkTxCd>

<Domn><Cd>TREA</Cd><Fmly>


</Fmly></Domn>

</BkTxCd><TxDtls>

<Refs><InstrId>FP-004567-FX</InstrId><EndToEndId>AAAASS1085FINPSS</EndToEndId>

</Refs><AmtDtls>

<CntrValAmt><Amt Ccy = "EUR">3255.5694</Amt><CcyXchg>

<SrcCcy>EUR</SrcCcy><XchgRate>0.1085</XchgRate>

</CcyXchg></CntrValAmt>

</AmtDtls></TxDtls>

</Ntry></Rpt>

</BkToCstmrAcctRptV01></Document>

SWIFTStandards MX


MX camt.053.001.01 BankToCustomerStatementV01Message Scope and UsageScopeThe Bank-to-Customer Statement message is sent by the account servicer to an account owner or to a party authorised by the account owner to receive the message. It is used to inform the account owner, or authorised party, of the entries booked to the account, and to provide the owner with balance information on the account at a given point in time.

UsageThe Bank-to-Customer Statement message can contain reports for more than 1 account. It provides information for cash management and/or reconciliation. It contains information on booked entries only. It can include underlying details of transactions that have been included in the entry.The message is exchanged as defined between the account servicer and the account owner. It provides information on items that have been booked to the account (and therefore are ‘binding’) and also balance information. Depending on services agreed between banks and their customers, ‘binding’ statements can be generated and exchanged intraday. Depending on legal requirements in local jurisdictions, ‘end-of-day’ statements may need to be mandatorily generated and exchanged.It is possible that the receiver of the message is not the account owner, but a party entitled through arrangement with the account owner to receive the account information (also known as recipient).

OutlineThe Bank-to-Customer Statement message is composed of 2 building blocks:A. Group HeaderThis building block is mandatory and present once. It contains elements such as Message Identification and CreationDateTime.B. StatementThis building block is mandatory and repetitive. It should be repeated for each account on which a statement is provided. The report contains components such as Balance and Entry information.


TypeRule/ Guid.

No.Message root <BkToCstmrStmtV01

>[1..1]


Rule/ Guid.




SCORE 2.0 MX camt.053.001.01 BankToCustomerStatementV01



Rule/ Guid.

No.1.3 MessageRecipient <MsgRcpt> [0..1] +




Rule/ Guid.

No.2.0 Statement <Stmt> [1..n]









2.9 Type <Tp> [0..1]




2.13 Name <Nm> [0..1] Text

2.14 Owner <Ownr> [0..1] +




2.18 Type <Tp> [0..1]



2.21 Rate <Rate> [0..n]

2.22 Rate <Rate> [1..1]






SWIFTStandards MX



Rule/ Guid.

No.2.28 Balance <Bal> [1..n]

2.29 Type <Tp> [1..1]








2.37 Date <Dt> [1..1] +


2.39 Date <Dt> [1..1]


















[0..n]









Rule/ Guid.

No.2.62 Domain <Domn> [0..1]

2.63 Code <Cd> [1..1] Code


2.65 Code <Cd> [1..1] Code



2.68 Code <Cd> [1..1] Text



2.71 Date <Dt> [1..1]














2.85 Date <Dt> [1..1]







2.92 Code <Cd> [1..1] Code


2.94 Code <Cd> [1..1] Code



SWIFTStandards MX



Rule/ Guid.

No.2.97 Code <Cd> [1..1] Text






































Rule/ Guid.

No.2.132 ExchangeRate <XchgRate> [1..1] Rate













2.145 Type <Tp> [1..1] Text











[0..1] Amount


2.157 Type <Tp> [0..1]

2.158 {Or Code <Cd> [1..1] Code




2.162 Party <Pty> [0..1] +

2.163 Tax <Tax> [0..1]



SWIFTStandards MX



Rule/ Guid.





2.170 Type <Tp> [0..1]

2.171 {Or Code <Cd> [1..1] Code


2.173 Rate <Rate> [0..n]

2.174 Rate <Rate> [1..1]

















2.191 Type <Tp> [1..1] Text













Rule/ Guid.

No.2.201 ContractIdentification <CtrctId> [0..1] Text






























2.231 Type <Tp> [1..1] Text





SWIFTStandards MX



Rule/ Guid.

No.2.236 UnitCurrency <UnitCcy> [0..1] Code





2.241 Date <Dt> [1..1]






2.247 Domain <Domn> [0..1]

2.248 Code <Cd> [1..1] Code

2.249 Family <Fmly> [1..1]

2.250 Code <Cd> [1..1] Code



2.253 Code <Cd> [1..1] Text




[0..1] Amount


2.258 Type <Tp> [0..1]

2.259 {Or Code <Cd> [1..1] Code




2.263 Party <Pty> [0..1] +

2.264 Tax <Tax> [0..1]









Rule/ Guid.

No.2.270 CreditDebitIndicator <CdtDbtInd> [1..1] Code

2.271 Type <Tp> [0..1]

2.272 {Or Code <Cd> [1..1] Code


2.274 Rate <Rate> [0..n]

2.275 Rate <Rate> [1..1]








2.283 Debtor <Dbtr> [0..1] +








2.291 Type <Tp> [1..1] Text

2.292 Party <Pty> [1..1] +












2.304 Type <Tp> [1..1] Text

SWIFTStandards MX



Rule/ Guid.

No.2.305 Agent <Agt> [1..1] +


2.307 {Or Code <Cd> [1..1] Code








2.314 Name <Nm> [1..1] Text

2.315 Address <Adr> [1..1] +






2.321 {Or Code <Cd> [1..1] Code













2.334 {Or Code <Cd> [1..1] Code








Rule/ Guid.

No.2.339 Invoicee <Invcee> [0..1] +

2.340 AdditionalRemittanceInformation

<AddtlRmtInf> [0..1] Text









2.349 Type <Tp> [1..1] Text






2.355 Type <Tp> [1..1] Text



2.358 {Or Quantity <Qty> [1..1] +


2.360 Type <Tp> [1..1] Text





2.365 Type <Tp> [1..1] Text


2.367 Tax <Tax> [0..1] +



2.370 Domain <Domn> [0..1]

2.371 Code <Cd> [1..1] Code

2.372 Family <Fmly> [1..1]

SWIFTStandards MX



Rule/ Guid.

No.2.373 Code <Cd> [1..1] Code



2.376 Code <Cd> [1..1] Text




2.380 {Or Code <Cd> [1..1] Code





2.384 Code <Cd> [0..1] Text






2.390 AdditionalStatementInformation <AddtlStmtInf> [0..1] Text

Message Items DescriptionThe following section identifies the elements of the BankToCustomerStatementV01 message.










1.1 MessageIdentification <MsgId>Presence: [1..1]Definition: Point to point reference assigned by the account servicing institution and sent to the account owner to

unambiguously identify the message.



minLength: 1
















SWIFTStandards MX


1.5 AdditionalInformation <AddtlInf>Presence: [0..1]Definition: Further details on the message.Data Type: Max500TextFormat: maxLength: 500

minLength: 1

2.0 Statement <Stmt>Presence: [1..n]Definition: Reports on booked entries and balances for a cash account.Type: The Statement block is composed of the following AccountStatement1 element(s):














2.390 AdditionalStatementInformation <AddtlStmtInf> [0..1] Text


minLength: 1



totalDigits: 18



2.3 LegalSequenceNumber <LglSeqNb>Presence: [0..1]Definition: Legal sequential number of the report, assigned by the account servicer. It is increased incrementally for

each report sent.



totalDigits: 18


2.5 FromToDate <FrToDt>Presence: [0..1]Definition: Range of time between the start date and the end date for which the account statement is issued.Type: This message item is composed of the following DateTimePeriodDetails element(s):










SWIFTStandards MX


2.7 Account <Acct>Presence: [1..1]Definition: Business relationship between two entities; one entity is the account owner, the other entity is the account

servicer.Type: This message item is composed of the following CashAccount13 element(s):



2.9 Type <Tp> [0..1]


2.13 Name <Nm> [0..1] Text

2.14 Owner <Ownr> [0..1] +













2.10 Code <Cd>Presence: [1..1]This message item is part of choice 2.9 Type.



Definition: Nature or use of the account in a coded form.Data Type: CodeOne of the following CashAccountType4Code values must be used:


















2.11 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.9 Type.Definition: Proprietary nature or use of the account.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.12 Currency <Ccy>Presence: [0..1]Definition: Identification of the currency in which the account is held.Data Type: CurrencyCode

SWIFTStandards MX


Format: [A-Z]{3,3}Rule(s): ValidationByTable





minLength: 1














2.16 RelatedAccount <RltdAcct>Presence: [0..1]Definition: Identifies the parent account of the reported account.






Type <Tp> [0..1]




2.17 Interest <Intrst>Presence: [0..n]Definition: Provides general interest information that applies to the account at a particular moment in time.Type: This message item is composed of the following AccountInterest1 element(s):


2.18 Type <Tp> [0..1]

2.21 Rate <Rate> [0..n]










SWIFTStandards MX



minLength: 1



2.22 Rate <Rate> [1..1]











totalDigits: 11




minLength: 1



Amount <Amt> [1..1]




2.26 FromToDate <FrToDt>Presence: [0..1]Definition: Range of time between a start date and an end date for the calculation of the interest.Type: This message item is composed of the following DateTimePeriodDetails element(s):






minLength: 1

2.28 Balance <Bal>Presence: [1..n]Definition: Set of elements defining the balance(s).Type: This message item is composed of the following CashBalance2 element(s):

SWIFTStandards MX



2.29 Type <Tp> [1..1]




2.37 Date <Dt> [1..1] +


Rule(s): AvailabilityAndTypeRule If Type is equal to ForwardAvailable, Availability is not allowed.

2.29 Type <Tp>Presence: [1..1]Definition: Specifies the nature of a balance, eg, opening booked balance.Type: This message item is composed of one of the following BalanceType2Choice element(s):




2.30 Code <Cd>Presence: [1..1]This message item is part of choice 2.29 Type.Definition: Specifies the code for the type of a balance, eg, opening booked balance.Data Type: CodeOne of the following BalanceType9Code values must be used:

Code Name DefinitionCCLA CollectionClosingAvailable Collection closing balance of amount of money that is at the

disposal of the account owner on the date specified.

CCLB CollectionClosingBooked Collection balance of the account at the end of the pre-agreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period.

CFWA CollectionForwardAvailable Collection forward available balance of money that is at the disposal of the account owner on the date specified.

CITA CollectionInterimAvailable Collection available balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.



Code Name DefinitionCITB CollectionInterimBooked Collection balance calculated in the course of the account

servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

CLAV ClosingAvailable Closing balance of amount of money that is at the disposal of the account owner on the date specified.

CLBD ClosingBooked Balance of the account at the end of the pre-agreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period.

COPA CollectionOpeningAvailable Collection opening balance of amount of money that is at the disposal of the account owner on the date specified.

COPB CollectionOpeningBooked Collection book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report.

DCLA DisbursementClosingAvailable

Disbursement closing balance of amount of money that is at the disposal of the account owner on the date specified.

DCLB DisbursementClosingBooked

Disbursement balance of the account at the end of the pre-agreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period.

DFWA DisbursementForwardAvailable

Disbursement forward available balance of money that is at the disposal of the account owner on the date specified.

DITA DisbursementInterimAvailable

Disbursement available balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

DITB DisbursementInterimBooked

Disbursement balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

DOPA DisbursementOpeningAvailable

Disbursement opening balance of amount of money that is at the disposal of the account owner on the date specified.

DOPB DisbursementOpeningBooked

Disbursement book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report.

FWAV ForwardAvailable Forward available balance of money that is at the disposal of the account owner on the date specified.

SWIFTStandards MX


Code Name DefinitionICLA InvestmentClosingAvailable Investment closing balance of an amount of money that is

at the disposal of the account owner on the date specified.

ICLB InvestmentClosingBooked Investment (mutual funds) balance of the account at the end of the pre-agreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period.

IFWA InvestmentForwardAvailable

Investment forward available balance of money that is at the disposal of the account owner on the date specified.

IITA InvestmentInterimAvailable Investment available balance for calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

IITB InvestmentInterimBooked Investment balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

IOPA InvestmentOpeningAvailable

Investment opening balance of amount of money that is at the disposal of the account owner on the date specified.

IOPB InvestmentOpeningBooked Investment book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report.

ITAV InterimAvailable Available balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

ITBD InterimBooked Balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified.

OPAV OpeningAvailable Opening balance of amount of money that is at the disposal of the account owner on the date specified.

OPBD OpeningBooked Book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report.

PRCD PreviouslyClosedBooked Balance of the account at the previously closed account reporting period. The opening booked balance for the new period has to be equal to this balance.



Code Name DefinitionUsage: the previously booked closing balance should equal (inclusive date) the booked closing balance of the date it references and equal the actual booked opening balance of the current date.

2.31 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.29 Type.Definition: Specifies a proprietary code for the balance type.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.32 CreditLine <CdtLine>Presence: [0..1]Definition: Provides further details on the credit line information.Type: This message item is composed of the following CreditLine1 element(s):




2.33 Included <Incl>Presence: [1..1]Definition: Indicates whether the credit line is included or not.

Usage : if not present, credit line is not included in the balance amount.Data Type: One of the following TrueFalseIndicator values must be used:

MeaningWhenTrue: TrueMeaningWhenFalse: False

2.34 Amount <Amt>Presence: [0..1]Definition: Amount of money of the credit line.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



SWIFTStandards MX


ValidationByTable

2.35 Amount <Amt>Presence: [1..1]Definition: Currency and amount of money of the cash balance.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.36 CreditDebitIndicator <CdtDbtInd>Presence: [1..1]Definition: Indicates whether the balance is a credit or a debit balance. A zero balance is considered to be a credit balanceData Type: CodeOne of the following CreditDebitCode values must be used:



2.37 Date <Dt>Presence: [1..1]Definition: Specifies the date (and time) of the balance.Type: This message item is composed of one of the following DateAndDateTimeChoice element(s):












2.39 Date <Dt> [1..1]












SWIFTStandards MX



totalDigits: 18


totalDigits: 18









2.52 Sum <Sum>Presence: [0..1]Definition: Total of all individual entries included in the report.

SWIFTStandards MX


Data Type: DecimalNumberFormat: fractionDigits: 17

totalDigits: 18







totalDigits: 18

2.56 TotalEntriesPerBankTransactionCode <TtlNtriesPerBkTxCd>Presence: [0..n]Definition: Indicates the total number and sum of entries per bank transaction code.Type: This message item is composed of the following NumberAndSumOfTransactionsPerBankTransactionCode1

element(s):













totalDigits: 18


totalDigits: 18










SWIFTStandards MX








2.63 Code <Cd> [1..1] Code



minLength: 1




2.65 Code <Cd> [1..1] Code



minLength: 1

2.66 SubFamilyCode <SubFmlyCd>Presence: [1..1]



Definition: Specifies the sub-product family within a specific family.Data Type: ExternalBankTransactionSubFamilyCodeFormat: maxLength: 4

minLength: 1



2.68 Code <Cd> [1..1] Text



minLength: 1


minLength: 1




2.71 Date <Dt> [1..1]



2.71 Date <Dt>Presence: [1..1]Definition: Indicates when the amount of money will become available.

SWIFTStandards MX


Type: This message item is composed of one of the following CashBalanceAvailabilityDate1 element(s):















2.76 Entry <Ntry>Presence: [0..n]Definition: Specifies the elements of an entry in the statement.

Usage: At least one reference must be provided to identify the entry and its underlying transaction(s).Type: This message item is composed of the following StatementEntry1 element(s):



















Rule(s): StatusAndBookingDateRule If Status is pending, BookingDate must is not allowed.




SWIFTStandards MX













2.81 BookingDate <BookgDt>Presence: [0..1]Definition: Date and time when an entry is posted to an account on the account servicer's books.Type: This message item is composed of one of the following DateAndDateTimeChoice element(s):








the account owner (in a debit entry).

Usage : For entries which are subject to availability/float (and for which availability information is present), value date must not be used, as the availability component identifies the number of availability days.






2.83 AccountServicerReference <AcctSvcrRef>Presence: [0..1]Definition: Account servicing institution's reference for the underlying transaction.Data Type: Max35TextFormat: maxLength: 35

minLength: 1






2.85 Date <Dt> [1..1]



SWIFTStandards MX
















2.92 Code <Cd> [1..1] Code



minLength: 1

SWIFTStandards MX





2.94 Code <Cd> [1..1] Code



minLength: 1


minLength: 1



2.97 Code <Cd> [1..1] Text



minLength: 1

2.98 Issuer <Issr>Presence: [0..1]



Definition: Identification of the issuer of the proprietary bank transaction code.Data Type: Max35TextFormat: maxLength: 35

minLength: 1









minLength: 1


minLength: 1




SWIFTStandards MX







minLength: 1


payment message.Data Type: Max35TextFormat: maxLength: 35

minLength: 1



Usage : This component (on entry level) should be used when a total original batch or aggregate amount has to be provided. (If required, the original amounts for each individual transaction can be included in the same component on transaction details level.)




























2.111 SourceCurrency <SrcCcy>Presence: [1..1]

SWIFTStandards MX


Definition: Currency of the amount to be converted in a currency conversion. Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable








totalDigits: 11


minLength: 1




















2.120 SourceCurrency <SrcCcy>Presence: [1..1]Definition: Currency of the amount to be converted in a currency conversion. Data Type: CurrencyCode

SWIFTStandards MX


Format: [A-Z]{3,3}Rule(s): ValidationByTable








totalDigits: 11


minLength: 1


2.126 CounterValueAmount <CntrValAmt>Presence: [0..1]



Definition: Identifies the countervalue amount and provides currency exchange information. Either the counter amount quoted in an FX deal, or the result of the currency information applied to an instructed amount, before deduction of charges.

















2.129 SourceCurrency <SrcCcy>Presence: [1..1]Definition: Currency of the amount to be converted in a currency conversion. Data Type: CurrencyCodeFormat: [A-Z]{3,3}

SWIFTStandards MX










totalDigits: 11


minLength: 1























2.138 SourceCurrency <SrcCcy>Presence: [1..1]Definition: Currency of the amount to be converted in a currency conversion. Data Type: CurrencyCodeFormat: [A-Z]{3,3}

SWIFTStandards MX










totalDigits: 11


minLength: 1






2.145 Type <Tp> [1..1] Text




minLength: 1












2.148 SourceCurrency <SrcCcy>Presence: [1..1]

SWIFTStandards MX


Definition: Currency of the amount to be converted in a currency conversion. Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable








totalDigits: 11


minLength: 1





Usage : this component is used in case of batch or aggregate bookings.Type: This message item is composed of the following ChargesInformation3 element(s):




2.157 Type <Tp> [0..1]



2.162 Party <Pty> [0..1] +

2.163 Tax <Tax> [0..1]







SWIFTStandards MX




2.158 {Or Code <Cd> [1..1] Code








totalDigits: 11





Code Name DefinitionDEBT BorneByDebtor All transaction charges are to be borne by the debtor.














minLength: 1

2.165 Rate <Rate>Presence: [0..1]

SWIFTStandards MX


Definition: Rate used for calculation of the tax.Data Type: PercentageRateFormat: fractionDigits: 10

totalDigits: 11





Usage : it is used in case of batch or aggregate bookings.Type: This message item is composed of the following TransactionInterest1 element(s):




2.170 Type <Tp> [0..1]

2.173 Rate <Rate> [0..n]




fractionDigits: 5minInclusive: 0totalDigits: 18CurrencyCode



[A-Z]{3,3}Rule(s): CurrencyCode

ValidationByTable






2.171 {Or Code <Cd> [1..1] Code






minLength: 1

SWIFTStandards MX




2.174 Rate <Rate> [1..1]











totalDigits: 11


minLength: 1





Amount <Amt> [1..1]










minLength: 1








SWIFTStandards MX













2.367 Tax <Tax> [0..1] +
















2.182 MessageIdentification <MsgId>Presence: [0..1]Definition: Point to point reference assigned by the instructing party of the underlying message.Data Type: Max35Text



Format: maxLength: 35minLength: 1


minLength: 1


the instruction.



minLength: 1






minLength: 1





minLength: 1

SWIFTStandards MX



minLength: 1


minLength: 1


minLength: 1



2.191 Type <Tp> [1..1] Text



minLength: 1


minLength: 1






















SWIFTStandards MX




totalDigits: 11


minLength: 1










2.205 CurrencyExchange <CcyXchg>Presence: [0..1]Definition: Reports on currency exchange information.

SWIFTStandards MX


Type: This message item is composed of the following CurrencyExchange3 element(s):
















totalDigits: 11




minLength: 1













SWIFTStandards MX

















totalDigits: 11




minLength: 1













2.223 CurrencyExchange <CcyXchg>Presence: [0..1]Definition: Reports on currency exchange information.

SWIFTStandards MX


Type: This message item is composed of the following CurrencyExchange3 element(s):
















totalDigits: 11




minLength: 1




2.231 Type <Tp> [1..1] Text




minLength: 1




SWIFTStandards MX




totalDigits: 11


minLength: 1







2.241 Date <Dt> [1..1]







SWIFTStandards MX



2.247 Domain <Domn> [0..1]










2.248 Code <Cd> [1..1] Code

2.249 Family <Fmly> [1..1]


minLength: 1




2.250 Code <Cd> [1..1] Code


SWIFTStandards MX



minLength: 1


minLength: 1



2.253 Code <Cd> [1..1] Text



minLength: 1


minLength: 1









2.258 Type <Tp> [0..1]



2.263 Party <Pty> [0..1] +

2.264 Tax <Tax> [0..1]








SWIFTStandards MX



2.259 {Or Code <Cd> [1..1] Code








totalDigits: 11




SHAR Shared In a credit transfer context, means that transaction charges on the sender side are to be borne by the debtor, transaction charges on the receiver side are to be borne by the creditor. In a direct debit context, means that transaction charges on



Code Name Definitionthe sender side are to be borne by the creditor, transaction charges on the receiver side are to be borne by the debtor.













minLength: 1


totalDigits: 11

SWIFTStandards MX











2.271 Type <Tp> [0..1]

2.274 Rate <Rate> [0..n]













2.272 {Or Code <Cd> [1..1] Code






minLength: 1

2.274 Rate <Rate>Presence: [0..n]Definition: Set of elements qualifying the interest rate.

SWIFTStandards MX


Type: This message item is composed of the following Rate1 element(s):


2.275 Rate <Rate> [1..1]











totalDigits: 11


minLength: 1





Amount <Amt> [1..1]










minLength: 1




2.283 Debtor <Dbtr> [0..1] +








SWIFTStandards MX





















Type <Tp> [0..1]























Type <Tp> [0..1]




2.288 UltimateCreditor <UltmtCdtr>Presence: [0..1]

SWIFTStandards MX


Definition: Ultimate party to which an amount of money is due.Type: This message item is composed of the following PartyIdentification8 element(s):


















2.291 Type <Tp> [1..1] Text

2.292 Party <Pty> [1..1] +


minLength: 1










2.293 RelatedAgents <RltdAgts>Presence: [0..1]Definition: Set of elements identifying the agents related to the underlying transaction.Type: This message item is composed of the following TransactionAgents1 element(s):
















SWIFTStandards MX









2.299 ReceivingAgent <RcvgAgt>Presence: [0..1]Definition: Party that receives securities from the delivering agent at the place of settlement, eg, central securities

depository.Can also be used in the context of treasury operations.












SWIFTStandards MX
















2.304 Type <Tp> [1..1] Text

2.305 Agent <Agt> [1..1] +


minLength: 1













2.307 {Or Code <Cd> [1..1] Code



minLength: 1



minLength: 1

SWIFTStandards MX










separately from the payment instruction.Data Type: Max35TextFormat: maxLength: 35

minLength: 1








2.312 RemittanceLocationElectronicAddress <RmtLctnElctrncAdr>Presence: [0..1]



Definition: Electronic address to which an agent is to send the remittance information.Data Type: Max256TextFormat: maxLength: 256

minLength: 1



2.314 Name <Nm> [1..1] Text

2.315 Address <Adr> [1..1] +

2.314 Name <Nm>Presence: [1..1]Definition: Name by which a party is known and is usually used to identify that identity.Data Type: Max70TextFormat: maxLength: 70

minLength: 1













intended to settle, eg, commercial invoices in an account receivable system.

SWIFTStandards MX


Type: This message item is composed of the following RemittanceInformation1 element(s):






minLength: 1

2.318 Structured <Strd>Presence: [0..n]Definition: Information supplied to enable the matching of an entry with the items that the transfer is intended to settle,

eg, commercial invoices in an accounts' receivable system in a structured form.Type: This message item is composed of the following StructuredRemittanceInformation6 element(s):













2.320 ReferredDocumentType <RfrdDocTp>Presence: [0..1]



Definition: Provides the type of the referred document.Type: This message item is composed of the following ReferredDocumentType1 element(s):


2.321 {Or Code <Cd> [1..1] Code


















minLength: 1

SWIFTStandards MX



minLength: 1


minLength: 1















ValidationByTable










SWIFTStandards MX












2.334 {Or Code <Cd> [1..1] Code















minLength: 1


minLength: 1





minLength: 1

2.338 Invoicer <Invcr>Presence: [0..1]Definition: Identification of the organization issuing the invoice when different than the creditor or final party.

SWIFTStandards MX









2.339 Invoicee <Invcee>Presence: [0..1]Definition: Identification of the party to whom an invoice is issued, when different than the originator or debtor.Type: This message item is composed of the following PartyIdentification8 element(s):








minLength: 1
















2.343 TradeDate <TradDt>Presence: [0..1]Definition: Date on which the trade was executed.Data Type: ISODate







SWIFTStandards MX



2.349 Type <Tp> [1..1] Text




minLength: 1

2.350 Date <Dt>Presence: [1..1]This message item is part of choice 2.348 Proprietary.Definition: Date in ISO format.Data Type: ISODate








Data Type: CurrencyAndAmount








2.355 Type <Tp> [1..1] Text



minLength: 1





SWIFTStandards MX



2.358 {Or Quantity <Qty> [1..1] +










2.360 Type <Tp> [1..1] Text



minLength: 1


minLength: 1












2.365 Type <Tp> [1..1] Text



minLength: 1


minLength: 1

SWIFTStandards MX























2.370 Domain <Domn> [0..1]












2.371 Code <Cd> [1..1] Code

2.372 Family <Fmly> [1..1]


minLength: 1




2.373 Code <Cd> [1..1] Code



SWIFTStandards MX


minLength: 1


minLength: 1



2.376 Code <Cd> [1..1] Text



minLength: 1


minLength: 1












2.380 {Or Code <Cd> [1..1] Code

















SWIFTStandards MX


Code Name DefinitionBE01 InconsistentWithEndCustom

erIdentification of end customer is not consistent with associated account number. (formerly CreditorConsistency)



BE06 UnknownEndCustomer End customer specified is not known at associated Sort/National Bank Code or does no longer exist in the books.





























minLength: 1


minLength: 1



2.384 Code <Cd> [0..1] Text




minLength: 1


minLength: 1

2.386 Proprietary <Prtry>Presence: [0..1]Definition: Proprietary corporate action event information.Data Type: Max35Text

SWIFTStandards MX




An investment account is an account between an investor(s) and a fund manager or a fund. The account can contain holdings in any investment fund or investment fund class managed (or distributed) by the fund manager, within the same fund family.




Type <Tp> [0..1]





minLength: 1


minLength: 1

2.390 AdditionalStatementInformation <AddtlStmtInf>Presence: [0..1]Definition: Further details on the account statement.Data Type: Max500TextFormat: maxLength: 500

minLength: 1

Business ExampleNarrativeOn 18 October, at 5.00 PM, AAAASESS sends an end-of-day BankToCustomerStatement to Company Finpetrol. It contains all booked items during the business day.




Element <XMLTag> ContentGroup Header <GrpHdr>

MessageIdentification <MsgId> AAAASESS-FP-STAT001


MessagePagination <MsgPgntn>

PageNumber <PgNb> 1

LastPageIndicator <LastPgInd> True

Statement <Stmt>

Identification <Id> AAAASESS-FP-STAT001


FromToDate <FrToDt>

FromDateTime <FrmDtTm> 2007-10-18T08:00:00+01:00

ToDateTime <ToDtTm> 2007-10-18T17:00:00+01:00

Account <Acct>

Identification <Id>


ID <Id> 50000000054910000003

Owner <Ownr>

Name <Nm> FINPETROL

Servicer <Svcr>




Country <Ctry> SE

Balance <Bal>

Type <Tp> OPBD


CreditDebitIndicator <CdtDbtInd> CRDT

Date <Dt> 2007-10-17

Balance <Bal>

Type <Tp> CLBD

Amount <Amt Ccy=SEK> 435678,50


Date <Dt> 2007-10-18

Entry <Ntry>

SWIFTStandards MX


Amount <Amt Ccy=SEK> 105678.50


Status <Sts> BOOK


DateTime <DtTm> 2007-10-18T13:15:00+01:00

ValueDate <ValDt>

Date <Dt> 2007-10-18

AccountServicerReference <AcctSvcrRef> AAAASESS-FP-CN-98765/01


Domain <Domn>

Code <Cd> PAYM

Family <Fmly>

Code <Cd> 0001



References <Refs>

EndToEndIdentification <EndToEndId>FIN MUELL/FINP/RA12345

RelatedParties <RltdPties>

Debtor <Dbtr>

Name <Nm> MUELLER

Entry <Ntry>


CreditDebitIndicator <CdtDbtInd> DBIT

Status <Sts> BOOK


DateTime <DtTm> 2007-10-18T10:15:00+01:00

ValueDate <ValDt>

Date <Dt> 2007-10-18

AccountServicerReference <AcctSvcrRef> AAAASESS-FP-ACCR-01


Domain <Domn>

Code <Cd> PAYM

Family <Fmly>

Code <Cd> 0001


Batch <Btch

MessageIdentification <MsgId> FINP-0055



PaymentInformationIdentification <PmtInfID> FINP-0055–001


Entry <Ntry>


CreditDebitIndicator <CdtDbtInd> CRED

Status <Sts> BOOK


DateTime <DtTm> 2007-10-18T15:15:00+01:00

ValueDate <ValDt>

Date <Dt> 2007-10-18

AccountServicerReference <AcctSvcrRef> AAAASESS-FP-CONF-FX


Domain <Domn>

Code <Cd> TREA

Family <Fmly>

Code <Cd> 0002



References <Refs>

InstructionID <InstrId> FP-004567-FX

EndToEndId <End2EndID> AAAASS1085FINPSS

AmountDetails <AmtDtls>

CountervalueAmount <CntrValAmt>

Amount <Amt Ccy=EUR> 3255.5694

CurrencyExchange <CcyXchg>

SourceCurrency <SrcCcy> EUR

ExchangeRate <XchRate> 0.1085

XML Instance<?xml version = "1.0" encoding = "UTF-8"?><Document xmlns = "urn:iso:std:iso:20022:tech:xsd:camt.053.001.01" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance">

<BkToCstmrStmtV01><GrpHdr>

<MsgId>AAAASESS-FP-STAT001</MsgId><CreDtTm>2007-10-18T17:00:00+01:00</CreDtTm><MsgPgntn>

<PgNb>1</PgNb><LastPgInd>true</LastPgInd>

</MsgPgntn>

SWIFTStandards MX


</GrpHdr><Stmt>

<Id>AAAASESS-FP-STAT001</Id><CreDtTm>2007-10-18T17:00:00+01:00</CreDtTm><FrToDt>

<FrDtTm>2007-10-18T08:00:00+01:00</FrDtTm><ToDtTm>2007-10-18T17:00:00+01:00</ToDtTm>

</FrToDt><Acct>

<Id><PrtryAcct>

<Id>50000000054910000003</Id></PrtryAcct>

</Id><Ownr>






</Svcr></Acct><Bal>

<Tp><Cd>OPBD</Cd>

</Tp><Amt Ccy = "SEK">500000</Amt><CdtDbtInd>CRDT</CdtDbtInd><Dt>

<Dt>2007-10-17</Dt></Dt>

</Bal><Bal>

<Tp><Cd>CLBD</Cd>

</Tp><Amt Ccy = "SEK">435678.50</Amt><CdtDbtInd>CRDT</CdtDbtInd><Dt>

<Dt>2007-10-18</Dt> </Dt>

</Bal><Ntry>

<Amt Ccy = "SEK">105678.50</Amt><CdtDbtInd>CRDT</CdtDbtInd><Sts>BOOK</Sts>



<BookgDt><DtTm>2007-10-18T13:15:00+01:00</DtTm>

</BookgDt><ValDt>

<Dt>2007-10-18</Dt></ValDt><AcctSvcrRef>AAAASESS-FP-CN-98765/01</AcctSvcrRef><BkTxCd>



</Fmly></Domn>

</BkTxCd><TxDtls>

<Refs><EndToEndId>MUELL/FINP/RA12345</EndToEndId>

</Refs><RltdPties>

<Dbtr><Nm>MUELLER</Nm>

</Dbtr></RltdPties>

</TxDtls></Ntry><Ntry>

<Amt Ccy = "SEK">2000000</Amt><CdtDbtInd>DBIT</CdtDbtInd><Sts>BOOK</Sts><BookgDt>


<Dt> 2007-10-18</Dt></ValDt><AcctSvcrRef> AAAASESS-FP-ACCR-01</AcctSvcrRef><BkTxCd>



</Fmly></Domn>

</BkTxCd><Btch>

<MsgId>FINP-0055</MsgId><PmtInfId>FINP-0055-001</PmtInfId><NbOfTxs>20</NbOfTxs>

</Btch>

SWIFTStandards MX


</Ntry><Ntry>

<Amt Ccy = "SEK">30000</Amt><CdtDbtInd>CRDT</CdtDbtInd><Sts>BOOK</Sts><BookgDt>


<Dt>2007-10-18</Dt></ValDt><AcctSvcrRef>AAAASESS-FP-CONF-FX</AcctSvcrRef><BkTxCd>

<Domn><Cd>TREA</Cd><Fmly>


</Fmly></Domn>

</BkTxCd><TxDtls>

<Refs><InstrId>FP-004567-FX</InstrId><EndToEndId>AAAASS1085FINPSS</EndToEndId>

</Refs><AmtDtls>

<CntrValAmt><Amt Ccy = "EUR">3255.5694</Amt><CcyXchg>

<SrcCcy>EUR</SrcCcy><XchgRate>0.1085</XchgRate>

</CcyXchg></CntrValAmt>

</AmtDtls></TxDtls>

</Ntry></Stmt>

</BkToCstmrStmtV01></Document>



MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01Message Scope and UsageScopeThe Bank-to-Customer Debit/Credit Notification message is sent by the account servicer to an account owner or to a party authorised by the account owner to receive the message. It can be used to inform the account owner, or authorised party, of single or multiple debit and/or credit entries reported to the account.

UsageThe Bank-to-Customer Debit/Credit Notification message can contain reports for more than 1 account. It provides information for cash management and/or reconciliation. It can be used to :- report pending and booked items;- notify one or more debit entries;- notify one or more credit entries;- notify a combination of debit and credit entriesIt can include underlying details of transactions that have been included in the entry.It is possible that the receiver of the message is not the account owner, but a party entitled by the account owner to receive the account information (also known as recipient).It does not contain balance information.

OutlineThe Bank-to-Customer DebitCreditNotification message is composed of 2 building blocks:A. Group HeaderThis building block is mandatory and present once. It contains elements such as Message Identification and CreationDateTime.B. NotificationThis building block is mandatory and repetitive. It should be repeated for each account on which a notification is provided. The notification contains information on the booked and pending debit and/or credit entries.


TypeRule/ Guid.

No.Message root <BkToCstmrDbtCdtN

tfctnV01>[1..1]


Rule/ Guid.



SWIFTStandards MX



Rule/ Guid.

No.1.2 CreationDateTime <CreDtTm> [1..1] DateTime





Rule/ Guid.

No.2.0 Notification <Ntfctn> [1..n]









2.9 Type <Tp> [0..1]




2.13 Name <Nm> [0..1] Text

2.14 Owner <Ownr> [0..1] +













SCORE 2.0 MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01



Rule/ Guid.

No.2.27 NumberOfEntries <NbOfNtries> [0..1] Text



[0..n]







2.36 Code <Cd> [1..1] Code


2.38 Code <Cd> [1..1] Code



2.41 Code <Cd> [1..1] Text



2.44 Date <Dt> [1..1]














2.58 Date <Dt> [1..1]



SWIFTStandards MX



Rule/ Guid.





2.65 Code <Cd> [1..1] Code


2.67 Code <Cd> [1..1] Code



2.70 Code <Cd> [1..1] Text





























Rule/ Guid.























2.118 Type <Tp> [1..1] Text











[0..1] Amount


SWIFTStandards MX



Rule/ Guid.

No.2.130 Type <Tp> [0..1]

2.131 {Or Code <Cd> [1..1] Code




2.135 Party <Pty> [0..1] +

2.136 Tax <Tax> [0..1]







2.143 Type <Tp> [0..1]

2.144 {Or Code <Cd> [1..1] Code


2.146 Rate <Rate> [0..n]

2.147 Rate <Rate> [1..1]

















2.164 Type <Tp> [1..1] Text




Rule/ Guid.

No.2.165 Reference <Ref> [1..1] Text



































SWIFTStandards MX



Rule/ Guid.





2.204 Type <Tp> [1..1] Text










2.214 Date <Dt> [1..1]






2.220 Domain <Domn> [0..1]

2.221 Code <Cd> [1..1] Code

2.222 Family <Fmly> [1..1]

2.223 Code <Cd> [1..1] Code



2.226 Code <Cd> [1..1] Text




[0..1] Amount


2.231 Type <Tp> [0..1]

2.232 {Or Code <Cd> [1..1] Code





Rule/ Guid.

No.2.234 Rate <Rate> [0..1] Rate


2.236 Party <Pty> [0..1] +

2.237 Tax <Tax> [0..1]







2.244 Type <Tp> [0..1]

2.245 {Or Code <Cd> [1..1] Code


2.247 Rate <Rate> [0..n]

2.248 Rate <Rate> [1..1]








2.256 Debtor <Dbtr> [0..1] +








2.264 Type <Tp> [1..1] Text

2.265 Party <Pty> [1..1] +




SWIFTStandards MX



Rule/ Guid.

No.2.269 IntermediaryAgent1 <IntrmyAgt1> [0..1] +








2.277 Type <Tp> [1..1] Text

2.278 Agent <Agt> [1..1] +


2.280 {Or Code <Cd> [1..1] Code








2.287 Name <Nm> [1..1] Text

2.288 Address <Adr> [1..1] +






2.294 {Or Code <Cd> [1..1] Code












Rule/ Guid.

No.2.303 Or CreditNoteAmount <CdtNoteAmt> [1..1] Amount




2.307 {Or Code <Cd> [1..1] Code






2.313 AdditionalRemittanceInformation

<AddtlRmtInf> [0..1] Text









2.322 Type <Tp> [1..1] Text






2.328 Type <Tp> [1..1] Text



2.331 {Or Quantity <Qty> [1..1] +


2.333 Type <Tp> [1..1] Text




SWIFTStandards MX



Rule/ Guid.

No.2.337 Or} Proprietary <Prtry> [1..1]

2.338 Type <Tp> [1..1] Text


2.340 Tax <Tax> [0..1] +



2.343 Domain <Domn> [0..1]

2.344 Code <Cd> [1..1] Code

2.345 Family <Fmly> [1..1]

2.346 Code <Cd> [1..1] Code



2.349 Code <Cd> [1..1] Text




2.353 {Or Code <Cd> [1..1] Code





2.357 Code <Cd> [0..1] Text






2.363 AdditionalNotificationInformation <AddtlNtfctnInf> [0..1] Text

Message Items DescriptionThe following section identifies the elements of the BankToCustomerDebitCreditNotificationV01 message.










1.1 MessageIdentification <MsgId>Presence: [1..1]Definition: Point to point reference assigned by the account servicing institution and sent to the account owner to




minLength: 1











SWIFTStandards MX







1.5 AdditionalInformation <AddtlInf>Presence: [0..1]Definition: Further details on the message.Data Type: Max500TextFormat: maxLength: 500

minLength: 1

2.0 Notification <Ntfctn>Presence: [1..n]Definition: Notifies debit and credit entries for the account.Type: The Notification block is composed of the following AccountNotification1 element(s):












2.363 AdditionalNotificationInformation <AddtlNtfctnInf> [0..1] Text


minLength: 1





totalDigits: 18

2.3 LegalSequenceNumber <LglSeqNb>Presence: [0..1]Definition: Legal sequential number of the report, assigned by the account servicer. It is increased incrementally for

each report sent.



totalDigits: 18


2.5 FromToDate <FrToDt>Presence: [0..1]Definition: Range of time between the start date and the end date for which the account notification is issued.Type: This message item is composed of the following DateTimePeriodDetails element(s):






SWIFTStandards MX






2.7 Account <Acct>Presence: [1..1]Definition: Business relationship between two entities; one entity is the account owner, the other entity is the account

servicer.Type: This message item is composed of the following CashAccount13 element(s):



2.9 Type <Tp> [0..1]


2.13 Name <Nm> [0..1] Text

2.14 Owner <Ownr> [0..1] +















2.10 Code <Cd>Presence: [1..1]This message item is part of choice 2.9 Type.Definition: Nature or use of the account in a coded form.Data Type: CodeOne of the following CashAccountType4Code values must be used:


















2.11 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.9 Type.

SWIFTStandards MX


Definition: Proprietary nature or use of the account.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.12 Currency <Ccy>Presence: [0..1]Definition: Identification of the currency in which the account is held.Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable





minLength: 1
















2.16 RelatedAccount <RltdAcct>Presence: [0..1]Definition: Identifies the parent account of the reported account.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]















SWIFTStandards MX







totalDigits: 18


totalDigits: 18













totalDigits: 18







totalDigits: 18

2.29 TotalEntriesPerBankTransactionCode <TtlNtriesPerBkTxCd>Presence: [0..n]Definition: Indicates the total number and sum of entries per bank transaction code.

SWIFTStandards MX


Type: This message item is composed of the following NumberAndSumOfTransactionsPerBankTransactionCode1 element(s):











totalDigits: 18


totalDigits: 18


















2.36 Code <Cd> [1..1] Code



minLength: 1



SWIFTStandards MX



2.38 Code <Cd> [1..1] Code



minLength: 1


minLength: 1



2.41 Code <Cd> [1..1] Text



minLength: 1


minLength: 1






2.44 Date <Dt> [1..1]











SWIFTStandards MX








2.49 Entry <Ntry>Presence: [0..n]Definition: Specifies the elements of an entry in the report.

Usage: At least one reference must be provided to identify the entry and its underlying transaction(s).Type: This message item is composed of the following NotificationEntry1 element(s):





















Rule(s): StatusAndBookingDateRule If Status is pending, BookingDate is not allowed.












SWIFTStandards MX





PDNG Pending Booking on the account owner's account in the account servicer's ledger has not been completed.

Usage : this can be used for expected items, or for items for which some conditions still need to be fulfilled before they can be booked. If booking takes place, the entry will be included with status Booked in subsequent account report or statement. Status Pending cannot be reversed.

2.54 BookingDate <BookgDt>Presence: [0..1]Definition: Date and time when an entry is posted to an account on the account servicer's books.

Usage : Booking date is only present if Status is booked.Type: This message item is composed of one of the following DateAndDateTimeChoice element(s):






the account owner (in a debit entry).

Usage : When entry status is pending , and value date is present, value date refers to an expected/requested value date.For entries which are subject to availability/float (and for which availability information is present), value date must not be used, as the availability component identifies the number of availability days.









2.56 AccountServicerReference <AcctSvcrRef>Presence: [0..1]Definition: Account servicing institution's reference for the entry.Data Type: Max35TextFormat: maxLength: 35

minLength: 1






2.58 Date <Dt> [1..1]







2.59 NumberOfDays <NbOfDays>Presence: [1..1]This message item is part of choice 2.58 Date.Definition: Indicates the number of float days attached to the balance.Data Type: Max15PlusSignedNumericText

SWIFTStandards MX


Format: [+]{0,1}[0-9]{1,15}









2.63 BankTransactionCode <BkTxCd>Presence: [1..1]Definition: Set of elements to fully identify the type of underlying transaction resulting in the entry.Type: This message item is composed of the following BankTransactionCodeStructure1 element(s):














2.65 Code <Cd> [1..1] Code



minLength: 1




2.67 Code <Cd> [1..1] Code



minLength: 1

SWIFTStandards MX



minLength: 1



2.70 Code <Cd> [1..1] Text



minLength: 1


minLength: 1











minLength: 1


minLength: 1









minLength: 1


payment message.

SWIFTStandards MX



minLength: 1



Usage : This component (on entry level) should be used when a total original batch or aggregate amount has to be provided. (If required, the individual original amounts can be included in the same component on transaction details level).















the currency as ordered by the initiating party.Data Type: CurrencyAndAmount

















the unit currency is GBP. Data Type: CurrencyCodeFormat: [A-Z]{3,3}

SWIFTStandards MX







totalDigits: 11


minLength: 1


























SWIFTStandards MX





totalDigits: 11


minLength: 1














ValidationByTable















SWIFTStandards MX




totalDigits: 11


minLength: 1















ValidationByTable















SWIFTStandards MX




totalDigits: 11


minLength: 1




2.118 Type <Tp> [1..1] Text




minLength: 1




















SWIFTStandards MX





totalDigits: 11


minLength: 1



Usage : this component is used on entry level in case of batch or aggregate bookings.Type: This message item is composed of the following ChargesInformation3 element(s):




2.130 Type <Tp> [0..1]



2.135 Party <Pty> [0..1] +

2.136 Tax <Tax> [0..1]


fractionDigits: 5



minInclusive: 0totalDigits: 18CurrencyCode[A-Z]{3,3}







2.131 {Or Code <Cd> [1..1] Code





2.132 ProprietaryCode <PrtryCd>Presence: [1..1]This message item is part of choice 2.130 Type.

SWIFTStandards MX


Definition: Type of charge is a bilaterally agreed code.



totalDigits: 11











2.136 Tax <Tax>Presence: [0..1]



Definition: Specifies tax details applied to charges.Type: This message item is composed of the following TaxCharges1 element(s):






minLength: 1


totalDigits: 11





Usage : This component is used on entry level in case of batch or aggregate bookings.Type: This message item is composed of the following TransactionInterest1 element(s):

SWIFTStandards MX





2.143 Type <Tp> [0..1]

2.146 Rate <Rate> [0..n]











2.144 {Or Code <Cd> [1..1] Code








minLength: 1



2.147 Rate <Rate> [1..1]








SWIFTStandards MX





totalDigits: 11


minLength: 1



Amount <Amt> [1..1]













minLength: 1


















2.340 Tax <Tax> [0..1] +








SWIFTStandards MX











2.155 MessageIdentification <MsgId>Presence: [0..1]Definition: Point to point reference assigned by the instructing party of the underlying message.Data Type: Max35TextFormat: maxLength: 35

minLength: 1


minLength: 1


the instruction.



minLength: 1








minLength: 1





minLength: 1


minLength: 1


minLength: 1


minLength: 1


SWIFTStandards MX



2.164 Type <Tp> [1..1] Text



minLength: 1


minLength: 1
































SWIFTStandards MX









totalDigits: 11


minLength: 1






















SWIFTStandards MX








totalDigits: 11


minLength: 1
























SWIFTStandards MX








totalDigits: 11


minLength: 1

























SWIFTStandards MX








totalDigits: 11


minLength: 1




2.204 Type <Tp> [1..1] Text






minLength: 1














SWIFTStandards MX









totalDigits: 11


minLength: 1









2.214 Date <Dt> [1..1]












SWIFTStandards MX








2.220 Domain <Domn> [0..1]










2.221 Code <Cd> [1..1] Code

2.222 Family <Fmly> [1..1]




minLength: 1




2.223 Code <Cd> [1..1] Code



minLength: 1


minLength: 1



2.226 Code <Cd> [1..1] Text


2.226 Code <Cd>Presence: [1..1]

SWIFTStandards MX


Definition: Proprietary bank transaction code to identify the underlying transaction.Data Type: Max35TextFormat: maxLength: 35

minLength: 1


minLength: 1







2.231 Type <Tp> [0..1]



2.236 Party <Pty> [0..1] +

2.237 Tax <Tax> [0..1]











2.232 {Or Code <Cd> [1..1] Code







SWIFTStandards MX



totalDigits: 11



















minLength: 1


totalDigits: 11







SWIFTStandards MX





2.244 Type <Tp> [0..1]

2.247 Rate <Rate> [0..n]











2.245 {Or Code <Cd> [1..1] Code








minLength: 1



2.248 Rate <Rate> [1..1]








SWIFTStandards MX





totalDigits: 11


minLength: 1



Amount <Amt> [1..1]













minLength: 1




2.256 Debtor <Dbtr> [0..1] +


















SWIFTStandards MX











Type <Tp> [0..1]























Type <Tp> [0..1]














SWIFTStandards MX










2.264 Type <Tp> [1..1] Text

2.265 Party <Pty> [1..1] +


minLength: 1








2.266 RelatedAgents <RltdAgts>Presence: [0..1]Definition: Set of elements identifying the agents related to the underlying transaction.



Type: This message item is composed of the following TransactionAgents1 element(s):























SWIFTStandards MX






















2.272 ReceivingAgent <RcvgAgt>Presence: [0..1]



Definition: Party that receives securities from the delivering agent at the place of settlement, eg, central securities depository.Can also be used in the context of treasury operations.




















SWIFTStandards MX








2.277 Type <Tp> [1..1] Text

2.278 Agent <Agt> [1..1] +


minLength: 1













2.280 {Or Code <Cd> [1..1] Code



minLength: 1



minLength: 1









separately from the payment instruction.

SWIFTStandards MX



minLength: 1









minLength: 1



2.287 Name <Nm> [1..1] Text

2.288 Address <Adr> [1..1] +

2.287 Name <Nm>Presence: [1..1]Definition: Name by which a party is known and is usually used to identify that identity.




minLength: 1



















minLength: 1

2.291 Structured <Strd>Presence: [0..n]

SWIFTStandards MX


Definition: Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, eg, commercial invoices in an accounts' receivable system in a structured form.

Type: This message item is composed of the following StructuredRemittanceInformation6 element(s):















2.294 {Or Code <Cd> [1..1] Code




















minLength: 1


minLength: 1


minLength: 1

SWIFTStandards MX












SWIFTStandards MX









2.307 {Or Code <Cd> [1..1] Code















minLength: 1


minLength: 1





minLength: 1








2.312 Invoicee <Invcee>Presence: [0..1]

SWIFTStandards MX


Definition: Identification of the party to whom an invoice is issued, when different than the originator or debtor.Type: This message item is composed of the following PartyIdentification8 element(s):








minLength: 1













2.316 TradeDate <TradDt>Presence: [0..1]



Definition: Date on which the trade was executed.Data Type: ISODate








2.322 Type <Tp> [1..1] Text




minLength: 1

2.323 Date <Dt>Presence: [1..1]

SWIFTStandards MX


This message item is part of choice 2.321 Proprietary.Definition: Date in ISO format.Data Type: ISODate















2.328 Type <Tp> [1..1] Text



minLength: 1






2.331 {Or Quantity <Qty> [1..1] +





SWIFTStandards MX








2.333 Type <Tp> [1..1] Text



minLength: 1


minLength: 1












2.338 Type <Tp> [1..1] Text



minLength: 1


minLength: 1






SWIFTStandards MX



















2.343 Domain <Domn> [0..1]












2.344 Code <Cd> [1..1] Code

2.345 Family <Fmly> [1..1]


minLength: 1




2.346 Code <Cd> [1..1] Code



minLength: 1


SWIFTStandards MX


minLength: 1



2.349 Code <Cd> [1..1] Text



minLength: 1


minLength: 1












2.353 {Or Code <Cd> [1..1] Code





















SWIFTStandards MX


Code Name DefinitionBE06 UnknownEndCustomer End customer specified is not known at associated Sort/

National Bank Code or does no longer exist in the books.



























minLength: 1




minLength: 1



2.357 Code <Cd> [0..1] Text




minLength: 1


minLength: 1

2.359 Proprietary <Prtry>Presence: [0..1]Definition: Proprietary corporate action event information.Data Type: Max35TextFormat: maxLength: 35

minLength: 1


An investment account is an account between an investor(s) and a fund manager or a fund. The account can

SWIFTStandards MX


contain holdings in any investment fund or investment fund class managed (or distributed) by the fund manager, within the same fund family.




Type <Tp> [0..1]





minLength: 1


minLength: 1

2.363 AdditionalNotificationInformation <AddtlNtfctnInf>Presence: [0..1]Definition: Further details on the account notification.Data Type: Max500TextFormat: maxLength: 500

minLength: 1

Business ExampleNarrative

Besides providing an intraday AccountReport at 12.30 PM (see example with AccountReport), AAAA Banken and Finpetrol have agreed on a credit notification service, for all incoming credits above a certain threshold. On 18 October, at 1.20 PM, AAAASESS sends a DebitCreditNotification to Company Finpetrol, to advise Finpetrol of an incoming credit on its account.


Element <XMLTag> Content



Group Header <GrpHdr>

MessageIdentification <MsgId> AAAASESS-FP-00001


Notification <Ntfctn>

Identification <Id> AAAASESS-FP-CN-98765


Account <Acct>

Identification <Id>


ID <Id> 50000000054910000003

Owner <Ownr>

Name <Nm> FINPETROL

Servicer <Svcr>




Country <Ctry> SE

Entry <Ntry>

Amount <Amt Ccy=SEK> 105678.50


Status <Sts> BOOK


DateTime <DtTm> 2007-10-18T13:15:00+01:00

ValueDate <ValDt>

Date <Dt> 2007-10-18

AccountServicerReference <AcctSvcrRef> AAAASESS-FP-CN-98765/01


Domain <Domn>

Code <Cd> PAYM

Family <Fmly>

Code <Cd> 0001



References <Refs>

EndToEndIdentification <EndToEndId>FIN MUELL/FINP/RA12345

RelatedParties <RltdPties>

Debtor <Dbtr>

SWIFTStandards MX


Name <Nm> MUELLER

XML Instance

<?xml version = "1.0" encoding = "UTF-8"?><Document xmlns = "urn:iso:std:iso:20022:tech:xsd:camt.054.001.01" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance">

<BkToCstmrDbtCdtNtfctnV01><GrpHdr>

<MsgId>AAAASESS-FP-00001</MsgId><CreDtTm>2007-10-18T13:20:00+01:00</CreDtTm>

</GrpHdr><Ntfctn>

<Id>AAAASESS-FP-CN-98765</Id><CreDtTm>2007-10-18T13:20:00+01:00</CreDtTm><Acct>

<Id><PrtryAcct>

<Id>50000000054910000003</Id></PrtryAcct>

</Id><Ownr>






</Svcr></Acct><Ntry>

<Amt Ccy = "SEK">105678.50</Amt><CdtDbtInd>CRDT</CdtDbtInd><Sts>BOOK</Sts><BookgDt>

<DtTm> 2007-10-18T13:15:00+01:00</DtTm></BookgDt><ValDt>

<Dt>2007-10-18</Dt></ValDt><AcctSvcrRef>AAAASESS-FP-CN-98765/01</AcctSvcrRef><BkTxCd>


<Cd>0001</Cd>



<SubFmlyCd>0005</SubFmlyCd></Fmly>

</Domn></BkTxCd><TxDtls>

<Refs><EndToEndId>MUELL/FINP/RA12345</EndToEndId>

</Refs><RltdPties>

<Dbtr><Nm>MUELLER</Nm><PstlAdr>

<Ctry>DE</Ctry></PstlAdr>

</Dbtr></RltdPties>

</TxDtls></Ntry>

</Ntfctn></BkToCstmrDbtCdtNtfctnV01>

</Document>

SWIFTStandards MX


MX pain.001.001.02 CustomerCreditTransferInitiationV02Message Scope and UsageScopeThe CustomerCreditTransferInitiation message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of funds from the debtor account to a creditor.

UsageThe CustomerCreditTransferInitiation message can contain one or more customer credit transfer instructions.

The CustomerCreditTransferInitiation message is used to exchange: - One or more instances of a credit transfer initiation;- Payment transactions that result in book transfers at the debtor agent or payments to another financial institution;- Payment transactions that result in an electronic cash transfer to the creditor account or in the emission of a cheque. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the debtor agent. The debtor agent is the account servicer of the

debtor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial

institution. It will forward the CustomerCreditTransferInitiation message to the debtor agent.

The message can also be used by an initiating party that has authority to send the message on behalf of the debtor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate.

The CustomerCreditTransferInitiation message can be used in domestic and cross-border scenarios.

The CustomerCreditTransferInitiation message must not be used by the debtor agent to execute the credit transfer instruction(s). The FIToFICustomerCreditTransfer message must be used instead.

If it is agreed to include the payment information related to the debit side only once (i.e. Grouped mode), the PaymentInformation block will be present only once. If it is agreed to repeat the payment information related to the debit side (i.e. Single mode), the PaymentInformation block must be present once per occurrence of the CreditTransferTransactionInformation block. The CustomerCreditTransferInitiation message also allows for a Mixed mode where the PaymentInformation block can be repeated and each PaymentInformation block can contain one or several CreditTransferTransactionInformation block(s).

SCORE 2.0 MX pain.001.001.02 CustomerCreditTransferInitiationV02


SingleWhen grouping is set to Single, information for each individual instruction is included separately. This means the PaymentInformation block is repeated and present for each occurrence of the Credit Transfer TransactionInformation block.

GroupedWhen grouping is set to Grouped, the PaymentInformation block will be present once and the Credit Transfer TransactionInformation block will be repeated.

SWIFTStandards MX


MixedWhen grouping is set to Mixed, the PaymentInformation block may be present once or may be repeated. Each sequence of the PaymentInformation block may contain one or several Credit Transfer TransactionInformation block(s).



OutlineThe CustomerCreditTransferInitiation message is composed of 3 building blocks:

A. Group HeaderThis building block is mandatory and present once. It contains elements such as MessageIdentification, CreationDateAndTime, Grouping indicator.

B. Payment InformationThis building block is mandatory and repetitive. It contains, amongst others, elements related to the debit side of the transaction, such as Debtor or PaymentTypeInformation.

SWIFTStandards MX


C. CreditTransfer Transaction InformationThis building block is mandatory and repetitive. It contains, amongst others, elements related to the credit side of the transaction, such as Creditor or RemittanceInformation.

RulesGrouping1RuleIf GroupHeader/Grouping is present and equals GRPD, then one and only one occurrence of PaymentInformation must be present.

Grouping2RuleIf GroupHeader/Grouping is present and equals SNGL, then each occurrence of PaymentInformation must contain one and only one occurrence of PaymentInformation/CreditTransferTransactionInformation.

Note : Rules applying to specific message components or message elements are included in the description of the relevant message component or message element.


TypeRule/ Guid.

No.Message root <pain.001.001.02> [1..1]


Rule/ Guid.




1.3 Authorisation <Authstn> [0..2] Text

1.4 BatchBooking <BtchBookg> [0..1] Indicator


1.6 ControlSum <CtrlSum> [0..1] Quantity

1.7 Grouping <Grpg> [1..1] Code


1.9 ForwardingAgent <FwdgAgt> [0..1] +


Rule/ Guid.

No.2.0 PaymentInformation <PmtInf> [1..n]





Rule/ Guid.

No.2.2 PaymentMethod <PmtMtd> [1..1] Code

2.3 PaymentTypeInformation <PmtTpInf> [0..1]

2.4 InstructionPriority <InstrPrty> [0..1] Code

2.5 {Or ServiceLevel <SvcLvl> [0..1]

2.6 {{Or Code <Cd> [1..1] Code

2.7 Or}} Proprietary <Prtry> [1..1] Text

2.8 Or} ClearingChannel <ClrChanl> [0..1] Code

2.9 LocalInstrument <LclInstrm> [0..1]



2.12 CategoryPurpose <CtgyPurp> [0..1] Code

2.13 RequestedExecutionDate <ReqdExctnDt> [1..1] DateTime

2.14 PoolingAdjustmentDate <PoolgAdjstmntDt> [0..1] DateTime

2.15 Debtor <Dbtr> [1..1] +



2.18 DebtorAgentAccount <DbtrAgtAcct> [0..1] +


2.20 ChargeBearer <ChrgBr> [0..1] Code

2.21 ChargesAccount <ChrgsAcct> [0..1] +

2.22 ChargesAccountAgent <ChrgsAcctAgt> [0..1] +

2.23 CreditTransferTransactionInformation <CdtTrfTxInf> [1..n]

2.24 PaymentIdentification <PmtId> [1..1]






2.30 {{Or Code <Cd> [1..1] Code







SWIFTStandards MX



Rule/ Guid.

No.2.37 Amount <Amt> [1..1]

2.38 {Or InstructedAmount <InstdAmt> [1..1] Amount

2.39 Or} EquivalentAmount <EqvtAmt> [1..1]


2.41 CurrencyOfTransfer <CcyOfTrf> [1..1] Code

2.42 ExchangeRateInformation <XchgRateInf> [0..1]


2.44 RateType <RateTp> [0..1] Code



2.47 ChequeInstruction <ChqInstr> [0..1] +



2.50 IntermediaryAgent1Account <IntrmyAgt1Acct> [0..1] +






2.56 CreditorAgentAccount <CdtrAgtAcct> [0..1] +




2.60 InstructionForCreditorAgent <InstrForCdtrAgt> [0..n]

2.61 Code <Cd> [0..1] Code

2.62 InstructionInformation <InstrInf> [0..1] Text

2.63 InstructionForDebtorAgent <InstrForDbtrAgt> [0..1] Text




2.67 RegulatoryReporting <RgltryRptg> [0..10]

2.68 DebitCreditReportingIndicator <DbtCdtRptgInd> [0..1] Code

2.69 Authority <Authrty> [0..1]

2.70 AuthorityName <AuthrtyNm> [0..1] Text

2.71 AuthorityCountry <AuthrtyCtry> [0..1] Code




Rule/ Guid.

No.2.72 RegulatoryDetails <RgltryDtls> [0..1]

2.73 Code <Cd> [0..1] Text


2.75 Information <Inf> [0..1] Text

2.76 Tax <Tax> [0..1] +







2.82 Name <Nm> [1..1] Text

2.83 Address <Adr> [1..1] +



















2.102 {Or Code <Cd> [1..1] Code




SWIFTStandards MX



Rule/ Guid.

No.2.106 Invoicer <Invcr> [0..1] +



Message Items DescriptionThe following section identifies the elements of the CustomerCreditTransferInitiationV02 message.

1.0 GroupHeader <GrpHdr>Presence: [1..1]Definition: Set of characteristics shared by all individual transactions included in the message.Type: The GroupHeader block is composed of the following GroupHeader1 element(s):




1.3 Authorisation <Authstn> [0..2] Text

1.4 BatchBooking <BtchBookg> [0..1] Indicator


1.6 ControlSum <CtrlSum> [0..1] Quantity

1.7 Grouping <Grpg> [1..1] Code



1.1 MessageIdentification <MsgId>Presence: [1..1]Definition: Point to point reference assigned by the instructing party and sent to the next party in the chain to


Usage: The instructing party has to make sure that 'MessageIdentification' is unique per instructed party for a pre-agreed period.


minLength: 1

1.2 CreationDateTime <CreDtTm>Presence: [1..1]Definition: Date and time at which a (group of) payment instruction(s) was created by the instructing party.Data Type: ISODateTime



1.3 Authorisation <Authstn>Presence: [0..2]Definition: User identification or any user key that allows to check if the initiating party is allowed to initiate transactions

from the account specified in the initiation.

Usage: the content is not of a technical nature, but reflects the organisational structure at the initiating side. The authorisation element can typically be used in relay scenarios, payment initiations, payment returns or payment reversals that are initiated on behalf of a different party than the initiating party.


minLength: 1

1.4 BatchBooking <BtchBookg>Presence: [0..1]Definition: Identifies whether a single entry per individual transaction or a batch entry for the sum of the amounts of all

transactions in the message is requested.Data Type: One of the following BatchBookingIndicator values must be used:

MeaningWhenTrue: Identifies that a batch entry for the sum of the amounts of all transactions in the message is requested.MeaningWhenFalse: Identifies that a single entry for each of the transactions in the message is requested.

1.5 NumberOfTransactions <NbOfTxs>Presence: [1..1]Definition: Number of individual transactions contained in the message.Data Type: Max15NumericTextFormat: [0-9]{1,15}

1.6 ControlSum <CtrlSum>Presence: [0..1]Definition: Total of all individual amounts included in the message, irrespective of currencies.Data Type: DecimalNumberFormat: fractionDigits: 17

totalDigits: 18

1.7 Grouping <Grpg>Presence: [1..1]Definition: Indicates whether common accounting information in the transaction is included once for all transactions or

repeated for each single transaction.Data Type: CodeOne of the following Grouping1Code values must be used:

Code Name DefinitionGRPD Grouped Indicates that there is only one occurrence of the payment

information block and several occurrences of the payment transaction block.

SWIFTStandards MX


Code Name DefinitionMIXD Mixed Indicates that there are one or several occurrences of the

payment information block where each of the occurences might contain one or several occurrences of the payment transaction block.

SNGL Single Indicates that for each occurrences of the payment information block, exactly one occurrence of the payment transaction block is present.

1.8 InitiatingParty <InitgPty>Presence: [1..1]Definition: Party initiating the payment. In the payment context, this can either be the debtor (in a credit transfer), the

creditor (in a direct debit), or the party that initiates the payment on behalf of the debtor or creditor.Type: This message item is composed of the following PartyIdentification8 element(s):







1.9 ForwardingAgent <FwdgAgt>Presence: [0..1]Definition: Financial institution that receives the instruction from the initiating party and forwards it to the next agent

in the payment chain for execution.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





2.0 PaymentInformation <PmtInf>Presence: [1..n]Definition: Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer

initiation.Type: The PaymentInformation block is composed of the following PaymentInstructionInformation1 element(s):





2.2 PaymentMethod <PmtMtd> [1..1] Code


2.13 RequestedExecutionDate <ReqdExctnDt> [1..1] DateTime

2.14 PoolingAdjustmentDate <PoolgAdjstmntDt> [0..1] DateTime

2.15 Debtor <Dbtr> [1..1] +






2.21 ChargesAccount <ChrgsAcct> [0..1] +

2.22 ChargesAccountAgent <ChrgsAcctAgt> [0..1] +

2.23 CreditTransferTransactionInformation <CdtTrfTxInf> [1..n]

Rule(s): ChargeBearerRule If ChargeBearer is present, then CreditTransferTransactionInformation/ChargeBearer is not allowed.If CreditTransferTransactionInformation/ChargeBearer is present, then ChargeBearer is not allowed.CreditTransferTransactionInformation/ChargeBearer and ChargeBearer may both be absent.

ChargesAccountAgentRule If ChargesAccountAgent is present, it must contain a branch of the DebtorAgent. It must not contain a completely different financial institution.

ChargesAccountRule If ChargesAccountAgent is present, then ChargesAccount must be present.

ChequeInstructionRule If PaymentMethod is CHK, then CreditTransferTransactionInformation/ChequeInstruction is optional.If PaymentMethod is different from CHK, then CreditTransferTransactionInformation/ChequeInstruction is not allowed.

Rule rationale: ChequeInstructionDetails may be present if the payment method is Cheque. It must not be present if the payment method is 'Transfer'.

CreditorAgentRule If PaymentMethod is CHK and if CreditTransferTransactionInformation/ ChequeInstruction/DeliveryMethod is present and is equal to MLFA, CRFA, RGFA or PUFA, then CreditTransferTransactionInformation/CreditorAgent is mandatory.

If PaymentMethod is CHK and if CreditTransferTransactionInformation/ ChequeInstruction/DeliveryMethod is not present or is not equal to MLFA, CRFA, RGFA or PUFA, then CreditTransferTransactionInformation/CreditorAgent is not allowed.

SWIFTStandards MX


CreditorAndOrCreditorAccountRule If PaymentMethod is CHK, then CreditTransferTransactionInformation/CreditorAccount is not allowed.

If PaymentMethod is different from CHK and if CreditTransferTransactionInformation/Creditor is not present, then CreditTransferTransactionInformation/CreditorAccount is mandatory.

If PaymentMethod is different from CHK and if CreditTransferTransactionInformation/Creditor is present, then CreditTransferTransactionInformation/CreditorAccount is optional.

PaymentTypeInformationRule If PaymentTypeInformation is present, then CreditTransferTransactionInformation/PaymentTypeInformation is not allowed.

Guideline(s): ChequeFromGuideline() CreditTransferTransactionInformation/ChequeInstruction/ChequeFrom may only be present if different from CreditTransferTransactionInformation/UltimateDebtor or Debtor.

ChequeInstructionDeliverToCreditorAgentGuideline() If CreditTransferTransactionInformation/ChequeInstruction/DeliveryMethod is present and is CRFA or MLFA or PUFA or RGFA, then CreditTransferTransactionInformation/ChequeInstruction/DeliverTo may only be present if different than CreditTransferTransactionInformation/Creditor.

ChequeInstructionDeliverToCreditorGuideline() If PaymentInformation/CreditTransferTransactionInformation/ChequeInstruction/DeliveryMethod is present and is CRCD or MLCD or PUCD or RGCD, then CreditTransferTransactionInformation/ChequeInstruction/DeliverTo may only be present if different from CreditTransferTransactionInformation/Creditor.

ChequeInstructionDeliverToDebtorGuideline() If CreditTransferTransactionInformation/ChequeInstruction/DeliveryMethod is present and if CreditTransferTransactionInformation/ChequeInstruction/DeliveryMethod/Code is CRDB or MLDB or PUDB or RGDB, then CreditTransferTransactionInformation/ChequeInstruction/DeliverTo may only be present if different than Debtor.

UltimateDebtorGuideline UltimateDebtor may only be present if different from Debtor.

2.1 PaymentInformationIdentification <PmtInfId>Presence: [0..1]Definition: Reference assigned by a sending party to unambiguously identify the payment information block within the

message.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.2 PaymentMethod <PmtMtd>Presence: [1..1]Definition: Specifies the means of payment that will be used to move the amount of money.Data Type: CodeOne of the following PaymentMethod3Code values must be used:



Code Name DefinitionCHK Cheque Written order to a bank to pay a certain amount of money

from one person to another person.

TRA TransferAdvice Transfer of an amount of money in the books of the account servicer. An advice should be sent back to the account owner.

TRF CreditTransfer Transfer of an amount of money in the books of the account servicer.

2.3 PaymentTypeInformation <PmtTpInf>Presence: [0..1]Definition: Set of elements that further specifies the type of transaction.Type: This message item is composed of the following PaymentTypeInformation1 element(s):







2.4 InstructionPriority <InstrPrty>Presence: [0..1]Definition: Indicator of the urgency or order of importance that the instructing party would like the instructed party to

apply to the processing of the instruction.Data Type: CodeWhen this message item is present, one of the following Priority2Code values must be used:

Code Name DefinitionHIGH High Priority level is high.

NORM Normal Priority level is normal.

2.5 ServiceLevel <SvcLvl>Presence: [0..1]This message item is part of choice 2.3 PaymentTypeInformation.Definition: Agreement under which or rules under which the transaction should be processed.Type: This message item is composed of one of the following ServiceLevel2Choice element(s):




SWIFTStandards MX


2.6 Code <Cd>Presence: [1..1]This message item is part of choice 2.5 ServiceLevel.Definition: Identification of a pre-agreed level of service between the parties in a coded form.Data Type: CodeOne of the following ServiceLevel1Code values must be used:

Code Name DefinitionPRPT EBAPriorityService Transaction must be processed according to the EBA

Priority Service.

SDVA SameDayValue Payment must be executed with same day value to the creditor.

SEPA SingleEuroPaymentsArea Payment must be executed following the Single Euro Payments Area scheme.

2.7 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.5 ServiceLevel.Definition: Proprietary identification of a pre-agreed level of service between the parties. Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.8 ClearingChannel <ClrChanl>Presence: [0..1]This message item is part of choice 2.3 PaymentTypeInformation.Definition: Specifies the clearing channel to be used for the instruction.Data Type: CodeWhen this message item is present, one of the following ClearingChannel2Code values must be used:

Code Name DefinitionBOOK BookTransfer Payment through internal book transfer.

MPNS MassPaymentNetSystem Clearing channel is a mass payment net settlement system.

RTGS RealTimeGrossSettlementSystem

Clearing channel is a real-time gross settlement system.

RTNS RealTimeNetSettlementSystem

Clearing channel is a real-time net settlement system.

2.9 LocalInstrument <LclInstrm>Presence: [0..1]Definition: User community specific instrument.

Usage : When available, codes provided by local authorities should be used.



Type: This message item is composed of one of the following LocalInstrument1Choice element(s):




2.10 Code <Cd>Presence: [1..1]This message item is part of choice 2.9 LocalInstrument.Definition: Specifies the local instrument published in an external local instrument code list.Data Type: ExternalLocalInstrumentCodeFormat: maxLength: 35

minLength: 1

2.11 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.9 LocalInstrument.Definition: Specifies the local instrument as a proprietary code.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.12 CategoryPurpose <CtgyPurp>Presence: [0..1]Definition: Specifies the high level purpose of the instruction based on a set of pre-defined categories.Data Type: CodeWhen this message item is present, one of the following PaymentCategoryPurpose1Code values must be used:

Code Name DefinitionCASH CashManagementTransfer Transaction is a general cash management instruction.

CORT TradeSettlementPayment Transaction is related to settlement of a trade, eg a foreign exchange deal or a securities transaction.

DIVI Dividend Transaction is the payment of dividends.

GOVT GovernmentPayment Transaction is a payment to or from a government department.

HEDG Hedging Transaction is related to the payment of a hedging operation.

INTC IntraCompanyPayment Transaction is an intra-company payment, ie, a payment between two companies belonging to the same group.

INTE Interest Transaction is the payment of interest.

LOAN Loan Transaction is related to the transfer of a loan to a borrower.

PENS PensionPayment Transaction is the payment of pension.

SALA SalaryPayment Transaction is the payment of salaries.

SWIFTStandards MX


Code Name DefinitionSECU Securities Transaction is the payment of securities.

SSBE SocialSecurityBenefit Transaction is a social security benefit, ie payment made by a government to support individuals.

SUPP SupplierPayment Transaction is related to a payment to a supplier.

TAXS TaxPayment Transaction is the payment of taxes.

TRAD Trade Transaction is related to the payment of a trade transaction.

TREA TreasuryPayment Transaction is related to treasury operations.

VATX ValueAddedTaxPayment Transaction is the payment of value added tax.

WHLD WithHolding Transaction is the payment of withholding tax.

2.13 RequestedExecutionDate <ReqdExctnDt>Presence: [1..1]Definition: Date at which the initiating party requests the clearing agent to process the payment. If payment by cheque,

the date when the cheque must be generated by the bank.

Usage: This is the date on which the debtor's account(s) is (are) to be debited.Data Type: ISODate

2.14 PoolingAdjustmentDate <PoolgAdjstmntDt>Presence: [0..1]Definition: Date used for the correction of the value date of a cash pool movement that has been posted with a different

value date.Data Type: ISODate








2.16 DebtorAccount <DbtrAcct>Presence: [1..1]Definition: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of

the transaction.






Type <Tp> [0..1]









2.18 DebtorAgentAccount <DbtrAgtAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the debtor agent at its servicing agent in the payment chain.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]





SWIFTStandards MX








2.20 ChargeBearer <ChrgBr>Presence: [0..1]Definition: Specifies which party/parties will bear the charges associated with the processing of the payment transaction.Data Type: CodeWhen this message item is present, one of the following ChargeBearerType1Code values must be used:





2.21 ChargesAccount <ChrgsAcct>Presence: [0..1]Definition: Account used to process charges associated with a transaction.

Usage : charges account should be used when charges have to be booked to an account different from the account identified in debtor's account.




Type <Tp> [0..1]






2.22 ChargesAccountAgent <ChrgsAcctAgt>Presence: [0..1]Definition: Agent that services a charges account.

Usage : charges account agent should only be used when the charges account agent is different from the debtor agent.






2.23 CreditTransferTransactionInformation <CdtTrfTxInf>Presence: [1..n]Definition: Set of elements providing information specific to the individual transaction(s) included in the message.Type: This message item is composed of the following CreditTransferTransactionInformation1 element(s):


2.24 PaymentIdentification <PmtId> [1..1]


2.37 Amount <Amt> [1..1]

2.42 ExchangeRateInformation <XchgRateInf> [0..1]


2.47 ChequeInstruction <ChqInstr> [0..1] +













2.60 InstructionForCreditorAgent <InstrForCdtrAgt> [0..n]

SWIFTStandards MX



2.63 InstructionForDebtorAgent <InstrForDbtrAgt> [0..1] Text


2.67 RegulatoryReporting <RgltryRptg> [0..10]

2.76 Tax <Tax> [0..1] +



Rule(s): InstructionForCreditorAgentRule If InstructionForCreditorAgent/Code contains CHQB, then CreditorAccount is not allowed.

IntermediaryAgent1AccountRule If IntermediaryAgent1 is not present, then IntermediaryAgent1Account is not allowed.


IntermediaryAgent2Rule If IntermediaryAgent2 is present, then IntermediaryAgent1 must be present.


IntermediaryAgent3Rule If IntermediaryAgent3 is present, then IntermediaryAgent2 must be present.

Guideline(s): UltimateCreditorGuideline UltimateCreditor may only be present if different from Creditor.

UltimateDebtorGuideline UltimateDebtor may only be present if different from Debtor.

2.24 PaymentIdentification <PmtId>Presence: [1..1]Definition: Set of elements to reference a payment instruction.Type: This message item is composed of the following PaymentIdentification1 element(s):





the instruction.





minLength: 1





minLength: 1












2.29 ServiceLevel <SvcLvl>Presence: [0..1]

SWIFTStandards MX


This message item is part of choice 2.27 PaymentTypeInformation.Definition: Agreement under which or rules under which the transaction should be processed.Type: This message item is composed of one of the following ServiceLevel2Choice element(s):






Priority Service.




minLength: 1

2.32 ClearingChannel <ClrChanl>Presence: [0..1]This message item is part of choice 2.27 PaymentTypeInformation.Definition: Specifies the clearing channel to be used for the instruction.Data Type: CodeWhen this message item is present, one of the following ClearingChannel2Code values must be used:







Code Name DefinitionRTNS RealTimeNetSettlementSyst

emClearing channel is a real-time net settlement system.


Usage : When available, codes provided by local authorities should be used.Type: This message item is composed of one of the following LocalInstrument1Choice element(s):





minLength: 1


minLength: 1





SWIFTStandards MX


Code Name DefinitionGOVT GovernmentPayment Transaction is a payment to or from a government

department.







SECU Securities Transaction is the payment of securities.









the currency as ordered by the initiating party.Type: This message item is composed of one of the following AmountType2Choice element(s):




2.38 InstructedAmount <InstdAmt>Presence: [1..1]This message item is part of choice 2.37 Amount.Definition: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in







2.39 EquivalentAmount <EqvtAmt>Presence: [1..1]This message item is part of choice 2.37 Amount.Definition: Amount of money to be transferred between the debtor and creditor, before deduction of charges, expressed

in the currency of the debtor's account, and to be transferred into a different currency.

Usage : Currency of the amount is expressed in the currency of the debtor's account, but the amount to be transferred is in another currency. The debtor agent will convert the amount and currency to the to be transferred amount and currency, eg, 'pay equivalent of 100000 EUR in JPY'(and account is in EUR).

Type: This message item is composed of the following EquivalentAmount element(s):




2.40 Amount <Amt>Presence: [1..1]Definition: Amount of money to be transferred between debtor and creditor, before deduction of charges, expressed in

the currency of the debtor's account, and to be transferred in a different currency.

Usage : Currency of the amount is expressed in the currency of the debtor's account, but the amount to be transferred is in another currency. The first agent will convert the amount and currency to the to be transferred amount and currency, eg, 'pay equivalent of 100000 EUR in JPY'(and account is in EUR).




2.41 CurrencyOfTransfer <CcyOfTrf>Presence: [1..1]Definition: Specifies the currency of the to be transferred amount, which is different from the currency of the debtor's

account.Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable

SWIFTStandards MX


2.42 ExchangeRateInformation <XchgRateInf>Presence: [0..1]Definition: Further detailed information on the exchange rate specified in the payment transaction.Type: This message item is composed of the following ExchangeRateInformation1 element(s):



2.44 RateType <RateTp> [0..1] Code


2.43 ExchangeRate <XchgRate>Presence: [0..1]Definition: The factor used for conversion of an amount from one currency to another. This reflects the price at which

one currency was bought with another currency.Data Type: BaseOneRateFormat: fractionDigits: 10

totalDigits: 11

2.44 RateType <RateTp>Presence: [0..1]Definition: Specifies the type used to complete the currency exchange.Data Type: CodeWhen this message item is present, one of the following ExchangeRateType1Code values must be used:

Code Name DefinitionAGRD Agreed Exchange rate applied is the rate agreed between the parties.

SALE Sale Exchange rate applied is the market rate at the time of the sale.

SPOT Spot Exchange rate applied is the spot rate.

2.45 ContractIdentification <CtrctId>Presence: [0..1]Definition: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party/

creditor and the debtor agent.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.46 ChargeBearer <ChrgBr>Presence: [0..1]Definition: Specifies which party/parties will bear the charges associated with the processing of the payment transaction.Data Type: Code



When this message item is present, one of the following ChargeBearerType1Code values must be used:





2.47 ChequeInstruction <ChqInstr>Presence: [0..1]Definition: Information related to the issuance of a cheque.Type: This message item is composed of the following Cheque5 element(s):


ChequeType <ChqTp> [0..1] Code

ChequeNumber <ChqNb> [0..1] Text

ChequeFrom <ChqFr> [0..1]

DeliveryMethod <DlvryMtd> [0..1]

DeliverTo <DlvrTo> [0..1]

InstructionPriority <InstrPrty> [0..1] Code

ChequeMaturityDate <ChqMtrtyDt> [0..1] DateTime

FormsCode <FrmsCd> [0..1] Text

MemoField <MemoFld> [0..1] Text

RegionalClearingZone <RgnlClrZone> [0..1] Text

PrintLocation <PrtLctn> [0..1] Text

For additional Type information, please refer to Cheque5 p.500 in 'Message Item Types' section.Rule(s): ChequeMaturityDateRule

If ChequeType is present and is DRFT or ELDR, then ChequeMaturityDate is optional. If ChequeType is not present or is different from DRFT or ELDR, then ChequeMaturityDate is not allowed.

Rule rationale: ChequeMaturityDate may be present only when ChequeType is DRFT or ELDR.


SWIFTStandards MX















2.50 IntermediaryAgent1Account <IntrmyAgt1Acct>Presence: [0..1]Definition: Unambiguous identification of the account of the intermediary agent 1 at its servicing agent in the payment

chain.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]













2.52 IntermediaryAgent2Account <IntrmyAgt2Acct>Presence: [0..1]Definition: Unambiguous identification of the account of the intermediary agent 2 at its servicing agent in the payment

chain.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]











2.54 IntermediaryAgent3Account <IntrmyAgt3Acct>Presence: [0..1]

SWIFTStandards MX


Definition: Unambiguous identification of the account of the intermediary agent 3 at its servicing agent in the payment chain.




Type <Tp> [0..1]









2.56 CreditorAgentAccount <CdtrAgtAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the creditor agent at its servicing agent in the payment chain.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]













2.58 CreditorAccount <CdtrAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result

of the payment transaction.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]











2.60 InstructionForCreditorAgent <InstrForCdtrAgt>Presence: [0..n]Definition: Further information related to the processing of the payment instruction, provided by the initiating party,

and intended for the creditor agent. Type: This message item is composed of the following InstructionForCreditorAgent1 element(s):

SWIFTStandards MX



2.61 Code <Cd> [0..1] Code

2.62 InstructionInformation <InstrInf> [0..1] Text

2.61 Code <Cd>Presence: [0..1]Definition: Coded information related to the processing of the payment instruction, provided by the initiating party, and

intended for the creditor's agent.Data Type: CodeWhen this message item is present, one of the following Instruction3Code values must be used:

Code Name DefinitionCHQB PayCreditorByCheque (Ultimate) creditor must be paid by cheque.

HOLD HoldCashForCreditor Amount of money must be held for the (ultimate) creditor, who will call. Pay on identification.

PHOB PhoneBeneficiary Please advise/contact (ultimate) creditor/claimant by phone

TELB Telecom Please advise/contact (ultimate) creditor/claimant by the most efficient means of telecommunication.

2.62 InstructionInformation <InstrInf>Presence: [0..1]Definition: Further information complementing the coded instruction or instruction to the creditor's agent that is

bilaterally agreed or specific to a user community.Data Type: Max140TextFormat: maxLength: 140

minLength: 1

2.63 InstructionForDebtorAgent <InstrForDbtrAgt>Presence: [0..1]Definition: Further information related to the processing of the payment instruction that may need to be acted upon by

the debtor agent, depending on agreement between debtor and the debtor agent.

Usage: The instruction can relate to a level of service, can be an instruction to be executed by the debtor's agent, or can be information required by the debtor's agent to process the instruction.


minLength: 1











minLength: 1



minLength: 1

2.67 RegulatoryReporting <RgltryRptg>Presence: [0..10]Definition: Information needed due to regulatory and statutory requirements.Type: This message item is composed of the following RegulatoryReporting2 element(s):


2.68 DebitCreditReportingIndicator <DbtCdtRptgInd> [0..1] Code

2.69 Authority <Authrty> [0..1]

2.72 RegulatoryDetails <RgltryDtls> [0..1]

2.68 DebitCreditReportingIndicator <DbtCdtRptgInd>Presence: [0..1]Definition: Identifies whether the regulatory reporting information applies to the debit side, to the credit side or to both

debit and credit sides of the transaction. Data Type: CodeWhen this message item is present, one of the following RegulatoryReportingType1Code values must be used:

SWIFTStandards MX


Code Name DefinitionBOTH Both Regulatory information applies to both credit and debit

sides.

CRED Credit Regulatory information applies to the credit side.

DEBT Debit Regulatory information applies to the debit side.

2.69 Authority <Authrty>Presence: [0..1]Definition: Entity requiring the regulatory reporting information.Type: This message item is composed of the following RegulatoryAuthority element(s):


2.70 AuthorityName <AuthrtyNm> [0..1] Text

2.71 AuthorityCountry <AuthrtyCtry> [0..1] Code

2.70 AuthorityName <AuthrtyNm>Presence: [0..1]Definition: Name of the entity requiring the regulatory reporting information.Data Type: Max70TextFormat: maxLength: 70

minLength: 1

2.71 AuthorityCountry <AuthrtyCtry>Presence: [0..1]Definition: Country of the entity requiring the regulatory reporting information.Data Type: CountryCodeFormat: [A-Z]{2,2}Rule(s): Country

The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).(Fatal) Error Code: Sw.Stds.D00004

2.72 RegulatoryDetails <RgltryDtls>Presence: [0..1]Definition: Details related to the regulatory reporting information.Type: This message item is composed of the following StructuredRegulatoryReporting2 element(s):


2.73 Code <Cd> [0..1] Text


2.75 Information <Inf> [0..1] Text



2.73 Code <Cd>Presence: [0..1]Definition: Specifies the nature, purpose, and reason for the transaction to be reported for regulatory and statutory

requirements in a coded form.Data Type: Max3TextFormat: maxLength: 3

minLength: 1

2.74 Amount <Amt>Presence: [0..1]Definition: Amount of money to be reported for regulatory and statutory requirements.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



2.75 Information <Inf>Presence: [0..1]Definition: Additional details that cater for specific domestic regulatory requirements.

Usage: Information is used to provide details that are not catered for in the Code or/and Amount elements.Data Type: Max35TextFormat: maxLength: 35

minLength: 1










SWIFTStandards MX














separately from the payment instruction.Data Type: Max35TextFormat: maxLength: 35

minLength: 1







URID UniformResourceIdentifier Remittance advice information needs to be sent to a Uniform Resource Identifier (URI). URI is a compact string of characters that uniquely identify an abstract or physical



Code Name Definitionresource. URI's are the super-set of identifiers, such as URLs, email addresses, ftp sites, etc, and as such, provide the syntax for all of the identification schemes.


minLength: 1



2.82 Name <Nm> [1..1] Text

2.83 Address <Adr> [1..1] +

2.82 Name <Nm>Presence: [1..1]Definition: Name by which a party is known and is usually used to identify that identity.Data Type: Max70TextFormat: maxLength: 70

minLength: 1










SWIFTStandards MX












minLength: 1











2.87 ReferredDocumentInformation <RfrdDocInf>Presence: [0..1]



Definition: Reference information to allow the identification of the underlying reference documents.Type: This message item is composed of the following ReferredDocumentInformation1 element(s):






















SWIFTStandards MX


Code Name DefinitionSOAC StatementOfAccount Document is a statement of the transactions posted to the

debtor's account at the supplier.


minLength: 1


minLength: 1


minLength: 1






















SWIFTStandards MX



2.102 {Or Code <Cd> [1..1] Code













minLength: 1


minLength: 1

2.105 CreditorReference <CdtrRef>Presence: [0..1]

SWIFTStandards MX


Definition: Unique and unambiguous reference assigned by the creditor to refer to the payment transaction.




minLength: 1
















minLength: 1



Business ExampleNarrative

ABC Corporation, New York has received three invoices: 1. An invoice with number 4562, dated 08 September 2006 from DEF Electronics, London: 10 million JPY needs to be paid to DEF Electronics account 23683707994215 with AAAA Bank, London (AAAAGB2L). ABC Corporation assigns reference ABC/4562/2006-09-08 to the payment. Payment transaction charges are shared between ABC Corporation and DEF Electronics. 2. An invoice with number ABC-13679, dated 15 September 2006 from GHI Semiconductors, Brussels: 500,000 EUR needs to be paid to GHI Semiconductors account BE30001216371411 with DDDD Bank, Belgium (DDDDBEBB). ABC Corporation assigns reference ABC/ABC-13679/2006-09-15 to the payment. The accounts receivable department of GHI Semiconductors needs to be advised when the funds have been credited on the account on telephone number +32/2/2222222. GHI Semiconductors will bear all payment transaction charges. 3. An invoice with number 987-AC, dated 27 September 2006, from their branch ABC Corporation, California: 1 million USD needs to be paid to the branch account 4895623 with BBBB Bank, San Francisco (BBBBUS66). ABC assigns a reference ABC/987-AC/2006-09-27 to the payment. Payment transaction charges are shared.

ABC Corporation holds an account 00125574999 with BBBB Bank, New York (BBBBUS33) and instructs its bank to execute payment of the invoices with a CustomerCreditTransferInitiation message.

Business DescriptionCustomerCreditTransferInitiation from ABC Corporation, New York to BBBBB Bank, New York:


MessageIdentification <MsgId> ABC/060928/CCT001

CreationDateTime <CreDtTm> 2006-09-28T14:07:00

BatchBooking <BtchBookg> false


Controlsum <CtrlSum> 11500000

Grouping <Grpg> GRPD

InitiatingParty <InitgPty>

Name <Nm> ABC Corporation

PostalAddress <PstlAdr>

StreetName <StrtNm> Times Square

BuildingNumber <BldgNb> 7

PostCode <PstCd> NY 10036

TownName <TwnNm> New York

Country <Ctry> US

PaymentInformation <PmtInf>

PaymentMethod <PmtMtd> TRF

RequestedExecutionDate <ReqdExctnDt> 2006-09-29

Debtor <Dbtr>

SWIFTStandards MX








Country <Ctry> US

DebtorAccount <DbtrAcct>

Identification <Id>


Identification <Id> 00125574999

DebtorAgent <DbtrAgt>


BIC <BIC> BBBBUS33

CreditTransferTransactionInformation<CdtTrfTxInf>

PaymentIdentification

InstructionIdentification <InstrId> ABC/060928/CCT001/1

EndToEndIdentification <EndToEnd> ABC/4562/2006-09-08

Amount <Amt>

InstructedAmount <InstAmt>Ccy=JPY 10000000.

ChargeBearer <ChrgBr> SHAR

CreditorAgent <CdtrAgt>


BIC <BIC> AAAAGB2L

Creditor <Cdtr>

Name <Nm> DEF Electronics


AddressLine <AdrLine> Corn Exchange 5th Floor

StreetName <StrtNm> Mark Lane


PostCode <PstCd> EC3R7NE

TownName <TwnNm> London

Country <Ctry> GB

CreditorAccount <CdtrAcct>

Identification <Id>





Purpose <Purp>

Code <Cd> GDDS

RemittanceInformation <RmtInf>

Structured <Strd>

ReferredDocumentInformation <RfrdDocInf>

ReferredDocumentType <RfrdDocType>

Code <Cd> CINV

ReferredDocumentNumber <RfrdDocNb> 4562

ReferredDocumentRelatedDate <RfrdDocRltdDt> 2006-09-08


PaymentIdentification <PmtId>


EndToEndIdentification <EndToEndId> ABC/ABC-13679/2006-09-15

Amount <Amt>

InstructedAmount <InstdAmt>Ccy=EUR 500000.00

ChargeBearer <ChrgBr> CRED



BIC <BIC> DDDDBEBB

Creditor <Cdtr>

Name <Nm> GHI Semiconductors


StreetName <StrtNm> Avenue Brugmann


PostCode <PstCd> 1180

TownName <TwnNm> Brussels

Country <Ctry> BE


Identification <Id>

IBAN <IBAN> BE30001216371411

InstructionForCreditorAgent <InstrForCdtrAgt>

Code <Cd> PHOB

InstructionInformation <InstrInf> +32/2/2222222

Purpose <Purp>

Code <Cd> GDDS


SWIFTStandards MX


Structured <Strd>



Code <Cd> CINV

ReferredDocumentNumber <RfrdDocNb> ABC-13679



PaymentIdentification <PmtId>


EndToEndIdentification <EndToEndId> ABC/987-AC/2006-09-27

Amount <Amt>

InstructedAmount <InstdAmt>Ccy=EUR 1000000.00

ChargeBearer <ChrgBr> SHAR



BIC <BIC> BBBBUS66

Creditor <Cdtr>



StreetName <StrtNm> Bush Street


PostCode <PstCd> CA 94108

TownName <TwnNm> San Francisco

Country <Ctry> US


Identification <Id>



Purpose <Purp>

Code <Cd> INTC


Structured <Strd>



Code <Cd> CINV

ReferredDocumentNumber <RfrdDocNb> 987-AC




XML Instance <pain.001.001.02>

<GrpHdr><MsgId>ABC/060928/CCT001</MsgId><CreDtTm>2006-09-28T14:07:00</CreDtTm><BtchBookg>false</BtchBookg><NbOfTxs>3</NbOfTxs><CtrlSum>11500000</CtrlSum><Grpg>GRPD</Grpg><InitgPty>

<Nm>ABC Corporation</Nm><PstlAdr>

<StrtNm>Times Square</StrtNm><BldgNb>7</BldgNb><PstCd>NY 10036</PstCd><TwnNm>New York</TwnNm><Ctry>US</Ctry>

</PstlAdr></InitgPty>

</GrpHdr><PmtInf>

<PmtMtd>TRF</PmtMtd><ReqdExctnDt>2006-09-29</ReqdExctnDt><Dbtr>



</PstlAdr></Dbtr><DbtrAcct>

<Id><PrtryAcct>

<Id>00125574999</Id></PrtryAcct>

</Id></DbtrAcct><DbtrAgt>

<FinInstnId><BIC>BBBBUS33</BIC>

</FinInstnId></DbtrAgt><CdtTrfTxInf>

<PmtId><InstrId>ABC/060928/CCT001/1</InstrId><EndToEndId>ABC/4562/2006-09-08</EndToEndId>

</PmtId>

SWIFTStandards MX


<Amt><InstdAmt Ccy = "JPY">10000000</InstdAmt>

</Amt><ChrgBr>SHAR</ChrgBr><CdtrAgt>

<FinInstnId><BIC>AAAAGB2L</BIC>

</FinInstnId></CdtrAgt><Cdtr>

<Nm>DEF Electronics</Nm><PstlAdr>

<AdrLine>Corn Exchange 5th Floor</AdrLine><StrtNm>Mark Lane</StrtNm><BldgNb>55</BldgNb><PstCd>EC3R7NE</PstCd><TwnNm>London</TwnNm><Ctry>GB</Ctry>

</PstlAdr></Cdtr><CdtrAcct>

<Id><PrtryAcct>

<Id>23683707994215</Id></PrtryAcct>

</Id></CdtrAcct><Purp>

<Cd>GDDS</Cd></Purp><RmtInf>

<Strd><RfrdDocInf>

<RfrdDocTp><Cd>CINV</Cd>

</RfrdDocTp><RfrdDocNb>4562</RfrdDocNb>

</RfrdDocInf><RfrdDocRltdDt>2006-09-08</RfrdDocRltdDt>

</Strd></RmtInf>

</CdtTrfTxInf><CdtTrfTxInf>

<PmtId><InstrId>ABC/060928/CCT001/2</InstrId><EndToEndId>ABC/ABC-13679/2006-09-15</EndToEndId>

</PmtId><Amt>

<InstdAmt Ccy = "EUR">500000</InstdAmt></Amt><ChrgBr>CRED</ChrgBr><CdtrAgt>



<FinInstnId><BIC>DDDDBEBB</BIC>

</FinInstnId></CdtrAgt><Cdtr>

<Nm>GHI Semiconductors</Nm><PstlAdr>

<StrtNm>Avenue Brugmann</StrtNm><BldgNb>415</BldgNb><PstCd>1180</PstCd><TwnNm>Brussels</TwnNm><Ctry>BE</Ctry>


<Id><IBAN>BE30001216371411</IBAN>

</Id></CdtrAcct><InstrForCdtrAgt>

<Cd>PHOB</Cd><InstrInf>+32/2/2222222</InstrInf>

</InstrForCdtrAgt><Purp>

<Cd>GDDS</Cd></Purp><RmtInf>

<Strd><RfrdDocInf>


</RfrdDocTp><RfrdDocNb>ABC-13679</RfrdDocNb>


</Strd></RmtInf>

</CdtTrfTxInf><CdtTrfTxInf>

<PmtId><InstrId>ABC/060928/CCT001/3</InstrId><EndToEndId>ABC/987-AC/2006-09-27</EndToEndId>

</PmtId><Amt>

<InstdAmt Ccy = "USD">1000000</InstdAmt></Amt><ChrgBr>SHAR</ChrgBr><CdtrAgt>


</FinInstnId></CdtrAgt>

SWIFTStandards MX


<Cdtr><Nm>ABC Corporation</Nm><PstlAdr>

<StrtNm>Bush Street</StrtNm><BldgNb>13</BldgNb><PstCd>CA 94108</PstCd><TwnNm>San Francisco</TwnNm><Ctry>US</Ctry>


<Id><PrtryAcct>

<Id>4895623</Id></PrtryAcct>

</Id></CdtrAcct><Purp>

<Cd>INTC</Cd></Purp><RmtInf>

<Strd><RfrdDocInf>


</RfrdDocTp><RfrdDocNb>987-AC</RfrdDocNb>


</Strd></RmtInf>

</CdtTrfTxInf></PmtInf>

</pain.001.001.02>



MX pain.002.001.02 PaymentStatusReportV02Message Scope and UsageScopeThe PaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction.

UsageThe PaymentStatusReport message is exchanged between an agent and a non-financial institution customer to provide status information on instructions previously sent. Its usage will always be governed by a bilateral agreement between the agent and the non-financial institution customer.

The PaymentStatusReport message can be used to provide information about the status (e.g. rejection, acceptance) of the initiation of a credit transfer, a direct debit, as well as on the initiation of other customer instructions (e.g. PaymentCancellationRequest).

The PaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction.

The PaymentStatusReport message can be used in domestic and cross-border scenarios.

The PaymentStatusReport message exchanged between agents and non-financial institution customers is identified in the schema as follows: urn:swift:xsd:$pain.002.001.02

OutlineThe PaymentStatusReport message is composed of 3 building blocks:

A. Group HeaderThis building block is mandatory and present once. It contains elements such as MessageIdentification, CreationDateAndTime.

B. Original Group Information and StatusThis building block is mandatory and present once. It contains elements such as OriginalMessageIdentification, OriginalMessageNameIdentification, GroupStatus.

C. Transaction Information and StatusThis building block is optional and repetitive. It contains elements referencing the original instruction (e.g. OriginalEndToEndIdentification), elements relating to the PaymentStatusReport (e.g. StatusReasonInformation). The TransactionInformationAndStatus block may also transport a set of elements from the original instruction.

RulesGroupAndTransactionStatus1RuleIf OriginalGroupInformationAndStatus/GroupStatus is present and is equal to ACTC, ACCP, ACSP, ACSC, ACCR or ACWC, then TransactionInformationAndStatus/TransactionStatus must be different from RJCT.

GroupAndTransactionStatus2Rule

SWIFTStandards MX


If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to PDNG, then TransactionInformationAndStatus/TransactionStatus must be different from RJCT.

GroupAndTransactionStatus3RuleIf OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RJCT, then TransactionInformationAndStatus/TransactionStatus must be different from ACTC, ACCP, ACSP, ACSC, ACCR, ACWC or PDNG.

GroupAndTransactionStatus4RuleIf OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RCVD, then TransactionInformationAndStatus/TransactionStatus is not allowed.

InstructedAgentRuleGroupHeader/InstructedAgent is not allowed.

InstructingAgentRuleGroupHeader/InstructingAgent is not allowed.

Note : Rules applying to specific message components or message elements are included in the description of the relevant message component or message element.


TypeRule/ Guid.

No.Message root <pain.002.001.02> [1..1]


Rule/ Guid.








1.7 InstructingAgent <InstgAgt> [0..1] +

1.8 InstructedAgent <InstdAgt> [0..1] +

SCORE 2.0 MX pain.002.001.02 PaymentStatusReportV02



Rule/ Guid.

No.2.0 OriginalGroupInformationAndStatus <OrgnlGrpInfAndSts> [1..1]

2.1 {Or OriginalMessageIdentification <OrgnlMsgId> [1..1] Text

2.2 Or} NetworkFileName <NtwkFileNm> [1..1] Text

2.3 OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text

2.4 OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime

2.5 FileOriginator <FileOrgtr> [0..1] Text

2.6 OriginalNumberOfTransactions <OrgnlNbOfTxs> [0..1] Text

2.7 OriginalControlSum <OrgnlCtrlSum> [0..1] Quantity

2.8 GroupStatus <GrpSts> [0..1] Code

2.9 StatusReasonInformation <StsRsnInf> [0..n]

2.10 StatusOriginator <StsOrgtr> [0..1] +

2.11 StatusReason <StsRsn> [0..1]



2.14 AdditionalStatusReasonInformation <AddtlStsRsnInf> [0..n] Text

2.15 NumberOfTransactionsPerStatus <NbOfTxsPerSts> [0..n]

2.16 DetailedNumberOfTransactions <DtldNbOfTxs> [1..1] Text

2.17 DetailedStatus <DtldSts> [1..1] Code

2.18 DetailedControlSum <DtldCtrlSum> [0..1] Quantity


Rule/ Guid.

No.3.0 TransactionInformationAndStatus <TxInfAndSts> [0..n]

3.1 StatusIdentification <StsId> [0..1] Text

3.2 OriginalPaymentInformationIdentification <OrgnlPmtInfId> [0..1] Text

3.3 OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text

3.4 OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text

3.5 OriginalTransactionIdentification <OrgnlTxId> [0..1] Text

3.6 TransactionStatus <TxSts> [0..1] Code






SWIFTStandards MX



Rule/ Guid.

No.3.12 AdditionalStatusReasonInformation <AddtlStsRsnInf> [0..n] Text

3.13 ChargesInformation <ChrgsInf> [0..n] +




3.17 OriginalTransactionReference <OrgnlTxRef> [0..1]

3.18 InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount

3.19 Amount <Amt> [0..1]






3.25 {Or RequestedExecutionDate <ReqdExctnDt> [0..1] DateTime

3.26 Or} RequestedCollectionDate <ReqdColltnDt> [0..1] DateTime

3.27 CreditorSchemeIdentification <CdtrSchmeId> [0..1] +

3.28 SettlementInformation <SttlmInf> [0..1]

3.29 SettlementMethod <SttlmMtd> [1..1] Code

3.30 SettlementAccount <SttlmAcct> [0..1] +

3.31 ClearingSystem <ClrSys> [0..1]

3.32 {Or ClearingSystemIdentification <ClrSysId> [1..1] Code


3.34 InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] +

3.35 InstructingReimbursementAgentAccount

<InstgRmbrsmntAgtAcct>

[0..1] +

3.36 InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] +

3.37 InstructedReimbursementAgentAccount

<InstdRmbrsmntAgtAcct>

[0..1] +

3.38 ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] +

3.39 ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct>

[0..1] +




3.43 {{Or Code <Cd> [1..1] Code





Rule/ Guid.

No.3.45 Or} ClearingChannel <ClrChanl> [0..1] Code




3.49 SequenceType <SeqTp> [0..1] Code



3.52 MandateRelatedInformation <MndtRltdInf> [0..1]


3.54 DateOfSignature <DtOfSgntr> [0..1] DateTime

3.55 AmendmentIndicator <AmdmntInd> [0..1] Indicator

3.56 AmendmentInformationDetails <AmdmntInfDtls> [0..1]

3.57 OriginalMandateIdentification <OrgnlMndtId> [0..1] Text

3.58 OriginalCreditorSchemeIdentification

<OrgnlCdtrSchmeId> [0..1] +

3.59 OriginalCreditorAgent <OrgnlCdtrAgt> [0..1] +

3.60 OriginalCreditorAgentAccount <OrgnlCdtrAgtAcct> [0..1] +

3.61 OriginalDebtor <OrgnlDbtr> [0..1] +

3.62 OriginalDebtorAccount <OrgnlDbtrAcct> [0..1] +

3.63 OriginalDebtorAgent <OrgnlDbtrAgt> [0..1] +

3.64 OriginalDebtorAgentAccount <OrgnlDbtrAgtAcct> [0..1] +

3.65 OriginalFinalCollectionDate <OrgnlFnlColltnDt> [0..1] DateTime

3.66 OriginalFrequency <OrgnlFrqcy> [0..1] Code

3.67 ElectronicSignature <ElctrncSgntr> [0..1] Text

3.68 FirstCollectionDate <FrstColltnDt> [0..1] DateTime

3.69 FinalCollectionDate <FnlColltnDt> [0..1] DateTime

3.70 Frequency <Frqcy> [0..1] Code









SWIFTStandards MX



Rule/ Guid.

No.3.79 ReferredDocumentNumber <RfrdDocNb> [0..1] Text


















3.97 Debtor <Dbtr> [0..1] +









Message Items DescriptionThe following section identifies the elements of the PaymentStatusReportV02 message.

1.0 GroupHeader <GrpHdr>Presence: [1..1]Definition: Set of characteristics shared by all individual transactions included in the status report message.Type: The GroupHeader block is composed of the following GroupHeader5 element(s):












1.1 MessageIdentification <MsgId>Presence: [1..1]Definition: Point to point reference assigned by the instructing party and sent to the next party in the chain to


Usage: The instructing party has to make sure that 'MessageIdentification' is unique per instructed party for a pre-agreed period.


minLength: 1

1.2 CreationDateTime <CreDtTm>Presence: [1..1]Definition: Date and time at which the status report was created by the instructing party.Data Type: ISODateTime

1.3 InitiatingParty <InitgPty>Presence: [0..1]Definition: Party initiating the payment. In the payment context, this can either be the debtor (in a credit transfer), the

creditor (in a direct debit), or the party that initiates the payment on behalf of the debtor or creditor.Type: This message item is composed of the following PartyIdentification8 element(s):







SWIFTStandards MX


1.4 ForwardingAgent <FwdgAgt>Presence: [0..1]Definition: Financial institution that receives the instruction from the initiating party and forwards it to the next agent

in the payment chain.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):















1.7 InstructingAgent <InstgAgt>Presence: [0..1]Definition: Agent that instructs the next party in the chain to carry out the (set of) instruction(s).Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):







1.8 InstructedAgent <InstdAgt>Presence: [0..1]Definition: Agent that is instructed by the previous party in the chain to carry out the (set of) instruction(s).Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





2.0 OriginalGroupInformationAndStatus <OrgnlGrpInfAndSts>Presence: [1..1]Definition: Original group information concerning the group of transactions, to which the status report message refers

to.Type: The OriginalGroupInformationAndStatus block is composed of the following OriginalGroupInformation1

element(s):


2.1 {Or OriginalMessageIdentification <OrgnlMsgId> [1..1] Text

2.2 Or} NetworkFileName <NtwkFileNm> [1..1] Text

2.3 OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text

2.4 OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime

2.5 FileOriginator <FileOrgtr> [0..1] Text

2.6 OriginalNumberOfTransactions <OrgnlNbOfTxs> [0..1] Text

2.7 OriginalControlSum <OrgnlCtrlSum> [0..1] Quantity

2.8 GroupStatus <GrpSts> [0..1] Code


2.15 NumberOfTransactionsPerStatus <NbOfTxsPerSts> [0..n]

Rule(s): StatusReasonInformationRule StatusReasonInformation/AdditionalStatusReasonInformation may only be present when GroupStatus is present and is equal to RJCTor PDNG.

SWIFTStandards MX


Guideline(s): NumberOfTransactionPerStatusGuideline OriginalGroupInformationAndStatus/NumberOfTransactionsPerStatus should only be present if GroupStatus equals 'PART'.

2.1 OriginalMessageIdentification <OrgnlMsgId>Presence: [1..1]This message item is part of choice 2.0 OriginalGroupInformationAndStatus.Definition: Point to point reference assigned by the original instructing party to unambiguously identify the original

group of individual transactions.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.2 NetworkFileName <NtwkFileNm>Presence: [1..1]This message item is part of choice 2.0 OriginalGroupInformationAndStatus.Definition: Name assigned by the sending party to unambiguously identify the file transmitted on the network.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.3 OriginalMessageNameIdentification <OrgnlMsgNmId>Presence: [1..1]Definition: Specifies the original message name identifier to which the message refers, eg, pacs.003.001.01 or MT103.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.4 OriginalCreationDateTime <OrgnlCreDtTm>Presence: [0..1]Definition: Date and time at which the original message was created.Data Type: ISODateTime

2.5 FileOriginator <FileOrgtr>Presence: [0..1]Definition: Party that sent the file for which the status has been generated.

Usage: this field will only be used when the content of the message could not be decoded at the receiving side.


minLength: 1

2.6 OriginalNumberOfTransactions <OrgnlNbOfTxs>Presence: [0..1]Definition: Number of individual transactions contained in the original message.



Data Type: Max15NumericTextFormat: [0-9]{1,15}

2.7 OriginalControlSum <OrgnlCtrlSum>Presence: [0..1]Definition: Total of all individual amounts included in the original message, irrespective of currencies.Data Type: DecimalNumberFormat: fractionDigits: 17

totalDigits: 18

2.8 GroupStatus <GrpSts>Presence: [0..1]Definition: Specifies the status of a group of transactions.Data Type: CodeWhen this message item is present, one of the following TransactionGroupStatus1Code values must be used:

Code Name DefinitionACCP AcceptedCustomerProfile Preceding check of technical validation was successful.

Customer profile check was also successful. This includes the assessment of the static risks.

ACCR AcceptedCancellationRequest

Cancellation is accepted.

ACSC AcceptedSettlementCompleted

Settlement on the debtor's account has been completed.

Usage : this can be used by the first agent to report to the debtor that the transaction has been completed. Warning : this status is provided for transaction status reasons, not for financial information. It can only be used after bilateral agreement

ACSP AcceptedSettlementInProcess

All preceding checks such as technical validation and customer profile were successful. Dynamic risk assessment is now also successful and therefore the payment initiation has been accepted for execution.

ACTC AcceptedTechnicalValidation

Authentication and syntactical and semantical validation are successful.

ACWC AcceptedWithChange Instruction is accepted but a change will be made, i.e., date, remittance not sent.

PART PartiallyAccepted A number of transactions have been accepted, whereas another number of transactions have not yet achieved 'accepted' status.

PDNG Pending Payment initiation or individual transaction included in the payment initiation is pending. Further checks and status update will be performed.

RCVD Received Payment initiation has been received by the receiving agent.

SWIFTStandards MX


Code Name DefinitionRJCT Rejected Payment initiation or individual transaction included in the

payment initiation has been rejected.

2.9 StatusReasonInformation <StsRsnInf>Presence: [0..n]Definition: Detailed information on the status reason.Type: This message item is composed of the following StatusReasonInformation1 element(s):





Rule(s): StatusReasonRule If StatusReason/Code is equal to 'NARR', then at least one occurrence of AddititionalStatusReasonInformation must be present.

2.10 StatusOriginator <StsOrgtr>Presence: [0..1]Definition: Party issuing the status.Type: This message item is composed of the following PartyIdentification8 element(s):







2.11 StatusReason <StsRsn>Presence: [0..1]Definition: Specifies the reason for the status report.Type: This message item is composed of one of the following StatusReason1Choice element(s):






2.12 Code <Cd>Presence: [1..1]This message item is part of choice 2.11 StatusReason.Definition: Reason for the status in a coded form.Data Type: CodeOne of the following TransactionRejectReason2Code values must be used:






















SWIFTStandards MX


Code Name DefinitionED01 CorrespondentBankNotPoss

ibleCorrespondent bank not possible.






















2.13 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 2.11 StatusReason.Definition: Reason for the status not catered for by the available codes.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

2.14 AdditionalStatusReasonInformation <AddtlStsRsnInf>Presence: [0..n]Definition: Further details on the status reason.



Usage: Additional information can be used for several purposes, e.g. to report repaired information, or to further detail the status reason.


minLength: 1

2.15 NumberOfTransactionsPerStatus <NbOfTxsPerSts>Presence: [0..n]Definition: Detailed information on the number of transactions for each identical individual transaction status.Type: This message item is composed of the following NumberOfTransactionsPerStatus1 element(s):


2.16 DetailedNumberOfTransactions <DtldNbOfTxs> [1..1] Text

2.17 DetailedStatus <DtldSts> [1..1] Code

2.18 DetailedControlSum <DtldCtrlSum> [0..1] Quantity

2.16 DetailedNumberOfTransactions <DtldNbOfTxs>Presence: [1..1]Definition: Number of individual transactions contained in the message, detailed per status.Data Type: Max15NumericTextFormat: [0-9]{1,15}

2.17 DetailedStatus <DtldSts>Presence: [1..1]Definition: Common transaction status for all individual transactions reported with the same status.Data Type: CodeOne of the following TransactionIndividualStatus1Code values must be used:










SWIFTStandards MX


Code Name DefinitionACTC AcceptedTechnicalValidatio

nAuthentication and syntactical and semantical validation are successful.



RJCT Rejected Payment initiation or individual transaction included in the payment initiation has been rejected.

2.18 DetailedControlSum <DtldCtrlSum>Presence: [0..1]Definition: Total of all individual amounts included in the message, irrespective of currencies, detailed per status.Data Type: DecimalNumberFormat: fractionDigits: 17

totalDigits: 18

3.0 TransactionInformationAndStatus <TxInfAndSts>Presence: [0..n]Definition: Information concerning the original transactions, to which the status report message refers.Type: The TransactionInformationAndStatus block is composed of the following PaymentTransactionInformation1

element(s):


3.1 StatusIdentification <StsId> [0..1] Text

3.2 OriginalPaymentInformationIdentification <OrgnlPmtInfId> [0..1] Text

3.3 OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text

3.4 OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text

3.5 OriginalTransactionIdentification <OrgnlTxId> [0..1] Text

3.6 TransactionStatus <TxSts> [0..1] Code


3.13 ChargesInformation <ChrgsInf> [0..n] +




3.17 OriginalTransactionReference <OrgnlTxRef> [0..1]

3.1 StatusIdentification <StsId>Presence: [0..1]



Definition: Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the reported status.


minLength: 1

3.2 OriginalPaymentInformationIdentification <OrgnlPmtInfId>Presence: [0..1]Definition: Unique and unambiguous identifier of the original payment information block as assigned by the original

sending party.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

3.3 OriginalInstructionIdentification <OrgnlInstrId>Presence: [0..1]Definition: Original unique instruction identification as assigned by an instructing party for an instructed party to

unambiguously identify the original instruction.

Usage: the original instruction identification is the original point to point reference used between the instructing party and the instructed party to refer to the original instruction.


minLength: 1

3.4 OriginalEndToEndIdentification <OrgnlEndToEndId>Presence: [0..1]Definition: Original unique identification assigned by the initiating party to unambiguously identify the original

transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

3.5 OriginalTransactionIdentification <OrgnlTxId>Presence: [0..1]Definition: Original identification of a transaction, as assigned by the first instructing agent and passed on, unchanged,

throughout the entire interbank chain. Data Type: Max35TextFormat: maxLength: 35

minLength: 1

3.6 TransactionStatus <TxSts>Presence: [0..1]Definition: Specifies the status of a transaction, in a coded form.Data Type: CodeWhen this message item is present, one of the following TransactionIndividualStatus1Code values must be used:

SWIFTStandards MX











ACTC AcceptedTechnicalValidation

Authentication and syntactical and semantical validation are successful.



RJCT Rejected Payment initiation or individual transaction included in the payment initiation has been rejected.

3.7 StatusReasonInformation <StsRsnInf>Presence: [0..n]Definition: Detailed information on the status reason.Type: This message item is composed of the following StatusReasonInformation1 element(s):





Rule(s): StatusReasonRule If StatusReason/Code is equal to 'NARR', then at least one occurrence of AddititionalStatusReasonInformation must be present.

3.8 StatusOriginator <StsOrgtr>Presence: [0..1]



Definition: Party issuing the status.Type: This message item is composed of the following PartyIdentification8 element(s):







3.9 StatusReason <StsRsn>Presence: [0..1]Definition: Specifies the reason for the status report.Type: This message item is composed of one of the following StatusReason1Choice element(s):




3.10 Code <Cd>Presence: [1..1]This message item is part of choice 3.9 StatusReason.Definition: Reason for the status in a coded form.Data Type: CodeOne of the following TransactionRejectReason2Code values must be used:









SWIFTStandards MX


Code Name DefinitionAM04 InsufficientFunds Amount of funds available to cover specified message

amount is insufficient.


































Code Name DefinitionRC01 BankIdentifierIncorrect Bank identifier code specified in the message has an

incorrect format (formerly IncorrectFormatForRoutingCode).




3.11 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 3.9 StatusReason.Definition: Reason for the status not catered for by the available codes.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

3.12 AdditionalStatusReasonInformation <AddtlStsRsnInf>Presence: [0..n]Definition: Further details on the status reason.

Usage: Additional information can be used for several purposes, e.g. to report repaired information, or to further detail the status reason.


minLength: 1

3.13 ChargesInformation <ChrgsInf>Presence: [0..n]Definition: Information on charges related to the processing of the rejection of the instruction.

Usage: ChargesInformation is past on for information purposes only. Settlement of the charges will be done separately.



ChargesAmount <ChrgsAmt> [1..1] Amount

ChargesParty <ChrgsPty> [1..1]

For additional Type information, please refer to ChargesInformation1 p.487 in 'Message Item Types' section.

3.14 AcceptanceDateTime <AccptncDtTm>Presence: [0..1]

SWIFTStandards MX


Definition: Point in time when the payment order from the initiating party meets the processing conditions of the account servicing agent (debtor's agent in case of a credit transfer, creditor's agent in case of a direct debit). This means - amongst others - that the account servicing agent has received the payment order and has applied checks as eg, authorisation, availability of funds.


3.15 InstructingAgent <InstgAgt>Presence: [0..1]Definition: Agent that instructs the next party in the chain to carry out the (set of) instruction(s).Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





3.16 InstructedAgent <InstdAgt>Presence: [0..1]Definition: Agent that is instructed by the previous party in the chain to carry out the (set of) instruction(s).Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





3.17 OriginalTransactionReference <OrgnlTxRef>Presence: [0..1]Definition: Set of key elements of the original transaction being referred to.Type: This message item is composed of the following OriginalTransactionReference1 element(s):


3.18 InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount

3.19 Amount <Amt> [0..1]


3.25 {Or RequestedExecutionDate <ReqdExctnDt> [0..1] DateTime

3.26 Or} RequestedCollectionDate <ReqdColltnDt> [0..1] DateTime

3.27 CreditorSchemeIdentification <CdtrSchmeId> [0..1] +




3.28 SettlementInformation <SttlmInf> [0..1]



3.52 MandateRelatedInformation <MndtRltdInf> [0..1]



3.97 Debtor <Dbtr> [0..1] +









3.18 InterbankSettlementAmount <IntrBkSttlmAmt>Presence: [0..1]Definition: Amount of money moved between the instructing agent and the instructed agent.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount




the currency as ordered by the initiating party.Type: This message item is composed of one of the following AmountType2Choice element(s):




SWIFTStandards MX


3.20 InstructedAmount <InstdAmt>Presence: [1..1]This message item is part of choice 3.19 Amount.Definition: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in




3.21 EquivalentAmount <EqvtAmt>Presence: [1..1]This message item is part of choice 3.19 Amount.Definition: Amount of money to be transferred between the debtor and creditor, before deduction of charges, expressed

in the currency of the debtor's account, and to be transferred into a different currency.

Usage : Currency of the amount is expressed in the currency of the debtor's account, but the amount to be transferred is in another currency. The debtor agent will convert the amount and currency to the to be transferred amount and currency, eg, 'pay equivalent of 100000 EUR in JPY'(and account is in EUR).

Type: This message item is composed of the following EquivalentAmount element(s):




3.22 Amount <Amt>Presence: [1..1]Definition: Amount of money to be transferred between debtor and creditor, before deduction of charges, expressed in

the currency of the debtor's account, and to be transferred in a different currency.

Usage : Currency of the amount is expressed in the currency of the debtor's account, but the amount to be transferred is in another currency. The first agent will convert the amount and currency to the to be transferred amount and currency, eg, 'pay equivalent of 100000 EUR in JPY'(and account is in EUR).






ValidationByTable

3.23 CurrencyOfTransfer <CcyOfTrf>Presence: [1..1]Definition: Specifies the currency of the to be transferred amount, which is different from the currency of the debtor's

account.Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable



3.25 RequestedExecutionDate <ReqdExctnDt>Presence: [0..1]This message item is part of choice 3.17 OriginalTransactionReference.Definition: Date at which the initiating party requests that the clearing agent to process the payment. If payment by

cheque, the date when the cheque must be generated by the bank.

Usage: This is the date on which the debtor's account(s) is (are) to be debited.Data Type: ISODate

3.26 RequestedCollectionDate <ReqdColltnDt>Presence: [0..1]This message item is part of choice 3.17 OriginalTransactionReference.Definition: Date at which the creditor requests the amount of money to be collected from the debtor.Data Type: ISODate

3.27 CreditorSchemeIdentification <CdtrSchmeId>Presence: [0..1]Definition: Credit party that signs the direct debit mandate.Type: This message item is composed of the following PartyIdentification8 element(s):






SWIFTStandards MX



3.28 SettlementInformation <SttlmInf>Presence: [0..1]Definition: Specifies the details on how the settlement of the original transaction(s) between the instructing agent and

the instructed agent was completed.Type: This message item is composed of the following SettlementInformation3 element(s):


3.29 SettlementMethod <SttlmMtd> [1..1] Code

3.30 SettlementAccount <SttlmAcct> [0..1] +

3.31 ClearingSystem <ClrSys> [0..1]

3.34 InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] +

3.35 InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> [0..1] +

3.36 InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] +

3.37 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> [0..1] +

3.38 ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] +

3.39 ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> [0..1] +

3.29 SettlementMethod <SttlmMtd>Presence: [1..1]Definition: Method used to settle the (batch of) payment instructions.Data Type: CodeOne of the following SettlementMethod1Code values must be used:

Code Name DefinitionCLRG ClearingSystem Settlement is done through a payment clearing system.

COVE CoverMethod Settlement is done through a cover payment.

INDA InstructedAgent Settlement is done by the agent instructed to execute a payment instruction.

INGA InstructingAgent Settlement is done by the agent instructing and forwarding the payment to the next party in the payment chain.

3.30 SettlementAccount <SttlmAcct>Presence: [0..1]Definition: A specific purpose account used to post debit and credit entries as a result of the transaction.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]







3.31 ClearingSystem <ClrSys>Presence: [0..1]Definition: Specification of a pre-agreed offering between clearing agents or the channel through which the payment

instruction is processed.Type: This message item is composed of one of the following ClearingSystemIdentification1Choice element(s):


3.32 {Or ClearingSystemIdentification <ClrSysId> [1..1] Code


3.32 ClearingSystemIdentification <ClrSysId>Presence: [1..1]This message item is part of choice 3.31 ClearingSystem.Definition: Infrastructure through which the payment instruction is processed.Data Type: CodeOne of the following CashClearingSystem3Code values must be used:

Code Name DefinitionABE EBAEuro1Step1 Scheme code for EBA Euro1/Step1.

AIP Albania Scheme code for AL (Albania) - Albania Interbank Payment System.

ART Austrian Scheme code for AT (Austria) - Austrian RTGS (ARTIS).

AVP NewZealand Scheme code for NZ (New Zealand) - New Zealand Assured Value Payments.

AZM Azerbaijan Scheme code for AZ (Azerbaijan) - Azerbaijan Interbank Payment System (AZIPS).

BAP BosniaHerzegovina Scheme code for BA (Bosnia and Herzegovina).

BCC SwedenBGC Scheme code for SE (Sweden) - Sweden BGC Clearing CUG.

BDS Barbados Scheme code for BB (Barbados) - Barbados RTGS (CBRTGS).

BEL Belgium Scheme code for BE (Belgium) - Belgium RTGS (ELLIPS).

BGN Bulgaria Scheme code for BG (Bulgaria) - Bulgaria RTGS.

BHS Bahamas Scheme code for BS (Bahamas) - Bahamas RTGS.

SWIFTStandards MX


Code Name DefinitionBIS Botswana Scheme code for BW (Botswana) - Botswana Interbank

Settlement System.

BOF Finland Scheme code for FI (Finland) - RTGS (BOF).

BOJ BankOfJapanNet Scheme code for the Bank of Japan clearing system.

BRL Italy Scheme code for IT (Italy) - Italy RTGS (BIREL).

BSP Philippines Scheme code for PH (Philippines) - Philippines Payment System.

CAD Canada Scheme code for CA (Canada) - Canadian Large Value Transfer System (LVTS)

CAM SpainCAM Scheme code for ES (Spain).

CBJ Ireland Scheme code for IE (Ireland) - Irish RTGS (IRIS).

CHI USChips CHIPS is the Clearing House Interbank Payment System in the US.

CHP UnitedKingdom Scheme code for GB (UK) - British Euro RTGS (CHAPS).

COP Columbia Scheme code for Columbia (CO) - Colombian ACH CENIT Central Bank Payment System.

DDK DenmarkDDK Scheme code for DK (Denmark) - Danish Krone RTGS (KRONOS)

DKC Denmark Scheme code for DK (Denmark) - Danish Euro RTGS (KRONOS)

EBA EBAEuro1 Scheme code for EBA Euro1.

ELS GermanyELS Scheme code for DE (Germany).

EPM ECB Scheme code for ECB (European Central Bank) - ECB Payment Mechanism.

EPN USChipsACH Scheme code for the US CHIPS-ACH.

ERP EBAStep1 Scheme code for EBA step 1 (members).

FDA USFedACH Scheme code for the US FED-ACH.

FDW Fedwire Scheme code for the US national real time gross settlement system.

FEY ForeignExchangeYenClearing

Scheme code for the Foreign Exchange Yen Clearing system (FEYCS). It is the Japanese electronic interbank system for sending guaranteed and unconditional yen payments of FX deals for same day settlement from one settlement bank, on behalf of itself or its customers, to another settlement bank.

GIS Ghana Scheme code for GH (Ghana) - Ghana Interbank Settlement System (GISS).

HRK Croatia Scheme code for HR (Croatia) - HSVP.

HRM Greece Scheme code for GR (Greece) - Greek RTGS (HERMES).

HUF Hungary Scheme code for HU (Hungary) - VIBER.



Code Name DefinitionINC NetherlandsIP Scheme code for NL (Netherlands) - Netherlands Interpay

CUG.

JOD Jordan Scheme code for JO (Jordan) - Jordan RTGS.

KPS Kenya Scheme code for KE (Kenya) - Kenyan Electronic Payment Settlement System.

LGS Luxemburg Scheme code for LU (Luxemburg) - Luxembourg RTGS (LIPS).

LKB SriLanka Scheme code for LK (Sri Lanka) - Sri Lanka (Lankasettle).

LVL Latvia Scheme code for LV (Latvia).

MEP Singapore Scheme code for SG (Singapore) - Singapore RTGS (MEPS+).

MOS SouthAfrica Scheme code for ZA (South Africa) - South-African Multiple Option Settlement.

MRS Malta Scheme code for MT (Malta) - Malta Realtime Interbank Settlement System.

MUP Mauritius Scheme code for MU (Mauritius).

NAM Namibia Scheme code for NA (Namibian) - Namibian Interbank Settlement System.

NOC Norway Scheme code for NO (Norway).

PCH Switzerland Scheme code for CH (Switzerland).

PDS Australia Scheme code for AU (Australia).

PEG Egypt Scheme code for EG (Egypt).

PNS FrancePNS Scheme code for FR (France).

PTR Angola Scheme code for AO (Angola) - Angola RTGS.

PVE Venezuela Scheme code for Ve (Venezuela).

ROL RomaniaEPO Scheme code for RO (Romania) - Romanian Electronic Payment Operations RT.

ROS RomaniaGSRS Scheme code for RO (Romania) - Romanian GSRS.

RTP GermanyRTGSPlus Scheme code for DE (Germany).

SCP Chili Scheme code for CL (Chile) - Chilean Interbank Payment System.

SEC SwedenSEC Scheme code for SE (Sweden) - Swedish Euro RTGS (SEC).

SIT Slovania Scheme code for SI (Slovenia).

SLB SpainES Scheme code for ES (Spain) - Spanish RTGS (SLBE).

SPG Portugal Scheme code for PT (Portugal) - Portuguese RTGS (SPGT).

SSK SwedenSSK Scheme code for SE (Sweden) - SEK RTGS (RIX).

STG UnitedKingdomGBP Scheme code for UK (United Kingdom) - CHAPS Sterling RTGS.

TBF FranceFR Scheme code for FR (France) - French RTGS (TBF).

SWIFTStandards MX


Code Name DefinitionTGT Target Scheme code for Target.

THB Thailand Scheme code for TH (Thailand) - Thailand Payment System (Bahtnet/2).

TIS Tanzania Scheme code for TZ (Tanzania) - Tanzania Interbank Settlement System (TISS).

TOP Netherlands Scheme code for NL (Netherlands) - Dutch RTGS (TOP)

TTD TrinidadAndTobago Scheme code for TT (Trinidad and Tobago ) - Trinidad and Tobago SAFE-TT.

UIS Uganda Scheme code for UG (Uganda) - Uganda National Interbank Settlement System.

XCT EBAStep2 Scheme code for EBA step 2.

ZEN Zengin Scheme code for the Zengin system. The electronic payment system for domestic third party transfers managed by the Tokyo Bankers Association.

ZET Zimbabwe Scheme code for ZW (Zimbabwe) - Zimbabwe Electronic Transfer & Settlement System.

ZIS Zambia Scheme code for ZM (Zambia) - Zambian Interbank Payment &Settlement System.

3.33 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 3.31 ClearingSystem.Definition: Proprietary clearing system service selected for a transaction.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

3.34 InstructingReimbursementAgent <InstgRmbrsmntAgt>Presence: [0..1]Definition: Specifies the agent through which the instructing agent will reimburse the instructed agent.

Usage: If the instructing and instructed agents have the same reimbursement agent, then only InstructingReimbursementAgent must be used.








3.35 InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the instructing reimbursement agent account at its servicing

agent in the payment chain.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]




3.36 InstructedReimbursementAgent <InstdRmbrsmntAgt>Presence: [0..1]Definition: Agent at which the instructed agent will be reimbursed.

Usage: If InstructedReimbursementAgent contains a branch of the InstructedAgent, then the instructed agent will claim reimbursement from that branch/will be paid by that branch.

Usage: If InstructingAgent and InstructedAgent have the same reimbursement agent, then only InstructingReimbursementAgent must be used.






3.37 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the instructed reimbursement agent account at its servicing

agent in the payment chain.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]


SWIFTStandards MX





3.38 ThirdReimbursementAgent <ThrdRmbrsmntAgt>Presence: [0..1]Definition: Specifies the branch of the instructed agent where the amount of money will be made available when different

from the instructed reimbursement agent.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





3.39 ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the third reimbursement agent account at its servicing agent

in the payment chain.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]













3.49 SequenceType <SeqTp> [0..1] Code






3.42 ServiceLevel <SvcLvl>Presence: [0..1]This message item is part of choice 3.40 PaymentTypeInformation.Definition: Agreement under which or rules under which the transaction should be processed.Type: This message item is composed of one of the following ServiceLevel2Choice element(s):






Priority Service.



SWIFTStandards MX



minLength: 1

3.45 ClearingChannel <ClrChanl>Presence: [0..1]This message item is part of choice 3.40 PaymentTypeInformation.Definition: Specifies the clearing channel to be used for the settlement of the instruction.Data Type: CodeWhen this message item is present, one of the following ClearingChannel2Code values must be used:





RTNS RealTimeNetSettlementSystem

Clearing channel is a real-time net settlement system.


Usage : When available, codes provided by local authorities should be used.Type: This message item is composed of one of the following LocalInstrument1Choice element(s):





minLength: 1




minLength: 1

3.49 SequenceType <SeqTp>Presence: [0..1]Definition: Identifies the direct debit sequence, eg, first, recurrent, final or one-off.Data Type: CodeWhen this message item is present, one of the following SequenceType1Code values must be used:

Code Name DefinitionFNAL Final Final collection of a series of direct debit instructions.

FRST First First collection of a series of direct debit instructions.

OOFF OneOff Direct debit instruction where the debtor's authorisation is used to initiate one single direct debit transaction.

RCUR Recurring Direct debit instruction where the debtor's authorisation is used for regular direct debit transactions initiated by the creditor.





GOVT GovernmentPayment Transaction is a payment to or from a government department.







SWIFTStandards MX


Code Name DefinitionSECU Securities Transaction is the payment of securities.








3.51 PaymentMethod <PmtMtd>Presence: [0..1]Definition: Specifies the transfer method that will be used by the instructing agent to transfer the funds to the creditor.Data Type: CodeWhen this message item is present, one of the following PaymentMethod4Code values must be used:

Code Name DefinitionCHK Cheque Written order to a bank to pay a certain amount of money

from one person to another person.

DD DirectDebit Collection of an amount of money from the debtor's bank account by the creditor. The amount of money and dates of collections may vary.

TRA TransferAdvice Transfer of an amount of money in the books of the account servicer. An advice should be sent back to the account owner.

TRF CreditTransfer Transfer of an amount of money in the books of the account servicer.

3.52 MandateRelatedInformation <MndtRltdInf>Presence: [0..1]Definition: Set of elements used to provide further details related to a direct debit mandate signed between the creditor

and the debtor.

Usage: Mandate related information is to be used only when the direct debit relates to a mandate signed between the debtor and the creditor.

Type: This message item is composed of the following MandateRelatedInformation1 element(s):



3.54 DateOfSignature <DtOfSgntr> [0..1] DateTime

3.55 AmendmentIndicator <AmdmntInd> [0..1] Indicator




3.56 AmendmentInformationDetails <AmdmntInfDtls> [0..1]

3.67 ElectronicSignature <ElctrncSgntr> [0..1] Text

3.68 FirstCollectionDate <FrstColltnDt> [0..1] DateTime

3.69 FinalCollectionDate <FnlColltnDt> [0..1] DateTime

3.70 Frequency <Frqcy> [0..1] Code

Rule(s): AmendmentIndicatorRule If AmendmentIndicator is true, then AmendementInformationDetails must be present, with amended mandate information.

If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.


minLength: 1

3.54 DateOfSignature <DtOfSgntr>Presence: [0..1]Definition: Date on which the direct debit mandate has been signed by the debtor.Data Type: ISODate

3.55 AmendmentIndicator <AmdmntInd>Presence: [0..1]Definition: Indicator notifying whether the underlying mandate is amended or not.Data Type: One of the following TrueFalseIndicator values must be used:

MeaningWhenTrue: TrueMeaningWhenFalse: False

3.56 AmendmentInformationDetails <AmdmntInfDtls>Presence: [0..1]Definition: List of direct debit mandate elements that have been modified.Type: This message item is composed of the following AmendmentInformationDetails1 element(s):


3.57 OriginalMandateIdentification <OrgnlMndtId> [0..1] Text

3.58 OriginalCreditorSchemeIdentification <OrgnlCdtrSchmeId> [0..1] +

3.59 OriginalCreditorAgent <OrgnlCdtrAgt> [0..1] +

3.60 OriginalCreditorAgentAccount <OrgnlCdtrAgtAcct> [0..1] +

SWIFTStandards MX



3.61 OriginalDebtor <OrgnlDbtr> [0..1] +

3.62 OriginalDebtorAccount <OrgnlDbtrAcct> [0..1] +

3.63 OriginalDebtorAgent <OrgnlDbtrAgt> [0..1] +

3.64 OriginalDebtorAgentAccount <OrgnlDbtrAgtAcct> [0..1] +

3.65 OriginalFinalCollectionDate <OrgnlFnlColltnDt> [0..1] DateTime

3.66 OriginalFrequency <OrgnlFrqcy> [0..1] Code

3.57 OriginalMandateIdentification <OrgnlMndtId>Presence: [0..1]Definition: Original mandate identification that has been modified.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

3.58 OriginalCreditorSchemeIdentification <OrgnlCdtrSchmeId>Presence: [0..1]Definition: Original creditor scheme identification that has been modified.Type: This message item is composed of the following PartyIdentification8 element(s):







3.59 OriginalCreditorAgent <OrgnlCdtrAgt>Presence: [0..1]Definition: Original creditor agent that has been modified.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):







3.60 OriginalCreditorAgentAccount <OrgnlCdtrAgtAcct>Presence: [0..1]Definition: Original creditor agent acount that has been modified.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]




3.61 OriginalDebtor <OrgnlDbtr>Presence: [0..1]Definition: Original debtor that has been modified.Type: This message item is composed of the following PartyIdentification8 element(s):







3.62 OriginalDebtorAccount <OrgnlDbtrAcct>Presence: [0..1]Definition: Original debtor account that has been modified.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]




3.63 OriginalDebtorAgent <OrgnlDbtrAgt>Presence: [0..1]

SWIFTStandards MX


Definition: Original debtor's agent that has been modified.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):





3.64 OriginalDebtorAgentAccount <OrgnlDbtrAgtAcct>Presence: [0..1]Definition: Original debtor agent account that has been modified.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]




3.65 OriginalFinalCollectionDate <OrgnlFnlColltnDt>Presence: [0..1]Definition: Original final collection date that has been modified.Data Type: ISODate

3.66 OriginalFrequency <OrgnlFrqcy>Presence: [0..1]Definition: Original frequency that has been modified.Data Type: CodeWhen this message item is present, one of the following Frequency1Code values must be used:

Code Name DefinitionADHO Adhoc Event takes place on request or as necessary.

DAIL Daily Event takes place every day.

INDA IntraDay Event takes place several times a day.

MIAN SemiAnnual Event takes place every six months or two times a year.

MNTH Monthly Event takes place every month or once a month.

QURT Quarterly Event takes place every three months or four times a year.

WEEK Weekly Event takes place once a week.



Code Name DefinitionYEAR Annual Event takes place every year or once a year.

3.67 ElectronicSignature <ElctrncSgntr>Presence: [0..1]Definition: Additional security provisions, eg, digital signature as provided by the debtor.Data Type: Max1025TextFormat: maxLength: 1025

minLength: 1

3.68 FirstCollectionDate <FrstColltnDt>Presence: [0..1]Definition: Date of the first collection of a direct debit as per the mandate.Data Type: ISODate

3.69 FinalCollectionDate <FnlColltnDt>Presence: [0..1]Definition: Date of the final collection of a direct debit as per the mandate.Data Type: ISODate

3.70 Frequency <Frqcy>Presence: [0..1]Definition: Regularity with which direct debit instructions are to be created and processed, eg, daily, weekly, monthly.Data Type: CodeWhen this message item is present, one of the following Frequency1Code values must be used:

Code Name DefinitionADHO Adhoc Event takes place on request or as necessary.

DAIL Daily Event takes place every day.

INDA IntraDay Event takes place several times a day.

MIAN SemiAnnual Event takes place every six months or two times a year.

MNTH Monthly Event takes place every month or once a month.

QURT Quarterly Event takes place every three months or four times a year.

WEEK Weekly Event takes place once a week.

YEAR Annual Event takes place every year or once a year.

3.71 RemittanceInformation <RmtInf>Presence: [0..1]Definition: Information supplied to enable the matching of an entry with the items that the transfer is intended to settle,

eg, commercial invoices in an accounts' receivable system.Type: This message item is composed of the following RemittanceInformation1 element(s):

SWIFTStandards MX







minLength: 1















3.75 ReferredDocumentType <RfrdDocTp>Presence: [0..1]Definition: Provides the type of the referred document.



Type: This message item is composed of the following ReferredDocumentType1 element(s):




















minLength: 1

SWIFTStandards MX



minLength: 1


minLength: 1















ValidationByTable










SWIFTStandards MX











minLength: 1


minLength: 1





minLength: 1

3.93 Invoicer <Invcr>Presence: [0..1]Definition: Identification of the organization issuing the invoice when different than the creditor or final party.

SWIFTStandards MX

















minLength: 1

















3.98 DebtorAccount <DbtrAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of

the transaction.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]









SWIFTStandards MX


3.100 DebtorAgentAccount <DbtrAgtAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the debtor agent at its servicing agent in the payment chain.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]









3.102 CreditorAgentAccount <CdtrAgtAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the creditor agent at its servicing agent in the payment chain.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]




3.103 Creditor <Cdtr>Presence: [0..1]Definition: Party to which an amount of money is due.










3.104 CreditorAccount <CdtrAcct>Presence: [0..1]Definition: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result

of the payment transaction.Type: This message item is composed of the following CashAccount7 element(s):



Type <Tp> [0..1]











Business Example - Status of a CustomerCreditTransferInitiationNarrative

SWIFTStandards MX


As follow-up to the payment initiation by ABC Corporation, BBBB Bank sends a PaymentStatusReport to acknowledge that the message passed technical validation and was accepted based on the customer profile. Note : the original CustomerCreditTransferInitiation sent by ABC Corporation to BBBB Bank is documented in the business example section of the CustomerCreditTransferInitiation message.

Business DescriptionPaymentStatusReport from BBBB Bank to ABC Corporation


MessageIdentification <MsgId> BBBB/060928-PSR/001









Country <Ctry> US



BIC <BIC> BBBBUS33

OriginalGroupInformationAndStatus <OrgnlGrpInfAndSts>

OriginalMessageIdentification <OrgnlMsgId> ABC/060928/CCT001

OriginalMessageNameIdentification <OrgnlMsgNmId> pain.001.001.02

OriginalCreationDateTime <OrgnlCreDtTm> 2006-09-28T14:07:00

OriginalNumberOfTransactions <OrgnlNbOfTxs> 3

OriginalControlSum <OrgnlCtrlSm> 11500000.

GroupStatus <GrpsSts> ACCP

XML Instance

<pain.002.001.02><GrpHdr>

<MsgId>BBBB/060928-PSR/001</MsgId><CreDtTm>2006-09-28T14:09:00</CreDtTm><InitgPty>


<StrtNm>Times Square</StrtNm><BldgNb>7</BldgNb><PstCd>NY 10036</PstCd>



<TwnNm>New York</TwnNm><Ctry>US</Ctry>

</PstlAdr></InitgPty><DbtrAgt>


</FinInstnId></DbtrAgt>

</GrpHdr><OrgnlGrpInfAndSts>

<OrgnlMsgId>ABC/060928/CCT001</OrgnlMsgId><OrgnlMsgNmId>pain.001.001.02</OrgnlMsgNmId><OrgnlCreDtTm>2006-09-28T14:07:00</OrgnlCreDtTm><OrgnlNbOfTxs>3</OrgnlNbOfTxs><OrgnlCtrlSum>11500000</OrgnlCtrlSum><GrpSts>ACCP</GrpSts>

</OrgnlGrpInfAndSts></pain.002.001.02>

Business Example - Status of a PaymentCancellationRequestNarrativeBBBB Banks confirms to ABC Corporation that it accepts the PaymentCancellationRequest by sending a PaymentStatusReport. Note : the PaymentCancellationRequest sent by ABC Corporation to BBBBUS33 is documented in the business example section of the PaymentCancellationRequest message.

Business DescriptionPaymentStatusReport from BBBBUS33 to ABC Corporation


MessageIdentification <MsgId> BBBB/060928-PSR/002









Country <Ctry> US


SWIFTStandards MX



BIC <BIC> BBBBUS33

OriginalGroupInformationAndStatus <OrgnlGrpInfAndSts>

OriginalMessageIdentification <OrgnlMsgId> ABC/060928/PCR001

OriginalMessageNameIdentification <OrgnlMsgNmId> pain.006.001.01

OriginalCreationDateTime <OrgnlCreDtTm> 2006-09-28T15:07:00

OriginalNumberOfTransactions <OrgnlNbOfTxs> 1

TransactionInformationAndStatus <TxInfAndSts>

StatusIdentification <StsId> BBBB/060928-PSR/002/1

OriginalInstructionIdentification <OrgnlInstrId> ABC/060928/PCR001/1

TransactionStatus <TxSts> ACCR

XML Instance


<MsgId>BBBB/060928-PSR/002</MsgId><CreDtTm>2006-09-28T15:49:00</CreDtTm><InitgPty>



</PstlAdr></InitgPty><DbtrAgt>


</FinInstnId></DbtrAgt>


<OrgnlMsgId>ABC/060928/PCR001</OrgnlMsgId><OrgnlMsgNmId>pain.006.001.01</OrgnlMsgNmId><OrgnlCreDtTm>2006-09-28T15:07:00</OrgnlCreDtTm><OrgnlNbOfTxs>1</OrgnlNbOfTxs>

</OrgnlGrpInfAndSts><TxInfAndSts>

<StsId>BBBB/060928-PSR/002/1</StsId><OrgnlInstrId>ABC/060928/PCR001/1 </OrgnlInstrId><TxSts>ACCR</TxSts>

</TxInfAndSts></pain.002.001.02>



Business Example - Status of a CustomerDirectDebitInitiationNarrative

AAAAUS29 received a PaymentStatusReport from its correspondent, ABABUS23, containing reject information about a previously sent FIToFICustomerDirectDebit. As AAAAUS29 has not yet credited the account of the original initiating party (Virgay) of the direct debit, AAAAUS29 in its turn informs Virgay about the rejection of the CustomerDirectDebitInitiation sent on 27 June 2006.Note : the PaymentStatusReport from ABABUS23 to AAAAUS29 is included in the business example section of the PaymentStatusReport message in the Payments Clearing and Settlement Message Reference Guide.

Business DescriptionPaymentStatusReport from AAAAUS29 to Virgay :


MessageIdentification <MsgId> AAAAUS29_5678c

CreationDateTime <CreDtTm> 2006-06-29T=11:35:00


Name <Nm> Virgay


StreetName <StrtNm> Virginia Lane


PostCode <PstCd> NJ 07311

TownName <TwnNm> Jersey City

Country <Ctry> US



BIC <BIC> AAAAUS29

OriginalGroupInformationAndStatus

<OrgnGrpInfAndSts>

OriginalMessageIdentification <OrgnlMsgId> CAVAY1234

OriginalMessageName Identification <OrgnlMsgNmId> Pacs.008.001.01

OriginalCreationDateAndTime <OrgnlCreDtTm> 2006-06-27T14:25:00

TransactionInformationAndStatus <TxInfAndSts>

StatusID <StsId> RJT2006_657B

OriginalEndToEndIdentification <OrgnlEndToEndId> VA060327/0123

TransactionStatus <TxSts> RJCT

StatusReasonInformation <StsRsnInf>

SWIFTStandards MX


StatusOriginator <StsOrgtr>

OrganisationIdentification <OrgId>

BIC <BIC> ABABUS23

Status Reason <StsRsn>

Code <Cd> AM05

OriginalTransactionReference <OrgnlTxRef>

Amount <Amt>

InstructedAmount <InstAmtCcy=USD> 1025.00

RequestedCollectionDate <ReqdColltnDt> 2006-07-03

MandateRelatedInformation <MndtRltdInf>

MandateIdentification <MndtId> VIRGAY123

Debtor <Dbtr>

Name <Name> Jones


StreetName <StrtNm> Hudston Street




Country <Ctry> US

Creditor <Cdtr>

Name <Name> Virgay


StreetName <StrtNm> Virginia Lane




Country <Ctry> US

XML Instance


<MsgId>AAAAUS29_5678c</MsgId><CreDtTm>2006-06-29T11:35:00</CreDtTm><InitgPty>

<Nm>Virgay</Nm><PstlAdr>

<StrtNm>Virginia Lane</StrtNm><BldgNb>36</BldgNb><PstCd>NJ 07311</PstCd>



<TwnNm>Jersey City</TwnNm><Ctry>US</Ctry>

</PstlAdr></InitgPty><CdtrAgt>

<FinInstnId><BIC>AAAAUS29</BIC>

</FinInstnId></CdtrAgt>


<OrgnlMsgId>CAVAY1234</OrgnlMsgId><OrgnlMsgNmId>Pain.008.001.01</OrgnlMsgNmId><OrgnlCreDtTm>2006-06-27T14:25:00</OrgnlCreDtTm>

</OrgnlGrpInfAndSts><TxInfAndSts>

<StsId>RJT2006-657B</StsId><OrgnlEndToEndId>VA060327/0123</OrgnlEndToEndId><TxSts>RJCT</TxSts><StsRsnInf>

<StsOrgtr><Id>

<OrgId><BIC>ABABUS23</BIC>

</OrgId></Id>

</StsOrgtr><StsRsn>

<Cd>AM05</Cd></StsRsn>

</StsRsnInf><OrgnlTxRef>

<Amt><InstdAmt Ccy = "USD">1025.00</InstdAmt>

</Amt><ReqdColltnDt>2006-07-03</ReqdColltnDt><MndtRltdInf>

<MndtId>VIRGAY123</MndtId></MndtRltdInf><Dbtr>

<Nm>Jones</Nm><PstlAdr>

<StrtNm>Hudston Street</StrtNm><BldgNb>19</BldgNb><PstCd>NJ 07302</PstCd><TwnNm>Jersey City</TwnNm><Ctry>US</Ctry>

</PstlAdr></Dbtr><Cdtr>

<Nm>Virgay</Nm><PstlAdr>

SWIFTStandards MX


<StrtNm>Virginia Lane</StrtNm><BldgNb>36</BldgNb><PstCd>NJ 07311</PstCd><TwnNm>Jersey City</TwnNm><Ctry/>

</PstlAdr></Cdtr>

</OrgnlTxRef></TxInfAndSts>

</pain.002.001.02>



Message Item TypesData TypesData Types Index

1 Amount1.1 CurrencyAndAmount1.2 ImpliedCurrencyAndAmount

2 Date Time2.1 ISODate2.2 ISODateTime2.3 ISOTime2.4 ISOYear

3 Identifier3.1 AustrianBankleitzahlIdentifier3.2 BBANIdentifier3.3 BEIIdentifier3.4 BICIdentifier3.5 BelgianIdentifier3.6 BloombergIdentifier3.7 CFIIdentifier3.8 CHIPSParticipantIdentifier3.9 CHIPSUniversalIdentifier3.10 CUSIPIdentifier3.11 CanadianPaymentsARNIdentifier3.12 ConsolidatedTapeAssociationIdentifier3.13 CountryCode3.14 CurrencyCode3.15 DunsIdentifier3.16 DutchIdentifier3.17 EANGLNIdentifier3.18 EuroclearClearstreamIdentifier3.19 ExtensiveBranchNetworkIdentifier3.20 ExternalBankTransactionDomainCode3.21 ExternalBankTransactionFamilyCode3.22 ExternalBankTransactionSubFamilyCode3.23 ExternalClearingSystemMemberCode3.24 ExternalCode3.25 ExternalLocalInstrumentCode3.26 ExternalPurposeCode3.27 FedwireRoutingNumberIdentifier3.28 GermanBankleitzahlIdentifier3.29 HellenicBankIdentificationCodeIdentifier3.30 HongKongBankIdentifier3.31 IBANIdentifier3.32 IBEIIdentifier3.33 ISINIdentifier

SWIFTStandards MX


3.34 IndianFinancialSystemCodeIdentifier3.35 IrishNSCIdentifier3.36 ItalianDomesticIdentifier3.37 LanguageCode3.38 MICIdentifier3.39 NationalityCode3.40 NewZealandNCCIdentifier3.41 PolishNationalClearingCodeIdentifier3.42 PortugueseNCCIdentifier3.43 QUICKIdentifier3.44 RICIdentifier3.45 RussianCentralBankIdentificationCodeIdentifier3.46 SEDOLIdentifier3.47 SicovamIdentifier3.48 SmallNetworkIdentifier3.49 SouthAfricanNCCIdentifier3.50 SpanishDomesticInterbankingIdentifier3.51 SwissBCIdentifier3.52 SwissSICIdentifier3.53 TickerIdentifier3.54 UKDomesticSortCodeIdentifier3.55 UPICIdentifier3.56 ValorenIdentifier3.57 WertpapierIdentifier

4 Quantity: Number and Decimal Number4.1 DecimalNumber4.2 Number

5 Rate5.1 BaseOneRate5.2 PercentageRate

6 Text6.1 Max1025Text6.2 Max105Text6.3 Max128Text6.4 Max140Text6.5 Max15NumericText6.6 Max15PlusSignedNumericText6.7 Max16Text6.8 Max256Text6.9 Max34Text6.10 Max350Text6.11 Max35Text6.12 Max3NumericText6.13 Max3Text6.14 Max4AlphaNumericText6.15 Max500Text6.16 Max5NumericText6.17 Max70Text

SCORE 2.0 Message Item Types


Data Types Description

1 Amount

1.1 CurrencyAndAmount

Definition: Number of monetary units specified in a currency, where the unit of currency is explicit and compliant with ISO 4217. The decimal separator is a dot.Note: A zero amount is considered a positive amount.

XML Attribute: Currency (Ccy). This XML Attribute is typed by CurrencyCode.Format: CurrencyAndAmount



Example: 100000 (Ccy='EUR')

1.2 ImpliedCurrencyAndAmount

Definition: Number of monetary units specified in a currency where the unit of currency is implied by the context and compliant with ISO 4217. The decimal separator is a dot.Note: a zero amount is considered a positive amount.

Format: fractionDigits: 5minInclusive: 0totalDigits: 18

Example: 500000

2 Date Time

2.1 ISODate

Definition: A particular point in the progression of time in a calendar year expressed in the YYYY-MM-DD format. This representation is defined in "XML Schema Part 2: Datatypes Second Edition - W3C Recommendation 28 October 2004" which is aligned with ISO 8601.

Example: 2002-02-25

2.2 ISODateTime

Definition: A particular point in the progression of time defined by a mandatory date and a mandatory time component, expressed in either UTC time format (YYYY-MM-DDThh:mm:ss.sssZ), local time with UTC offset format (YYYY-MM-DDThh:mm:ss.sss+/-hh:mm), or local time format (YYYY-MM-DDThh:mm:ss.sss). These representations are defined in "XML Schema Part 2: Datatypes Second Edition - W3C Recommendation 28 October 2004" which is aligned with ISO 8601.Note on the time format:1) beginning / end of calendar day00:00:00 = the beginning of a calendar day

SWIFTStandards MX


24:00:00 = the end of a calendar day2) fractions of second in time formatDecimal fractions of seconds may be included. In this case, the involved parties shall agree on the maximum number of digits that are allowed.

Example: 2002-07-21T08:35:30

2.3 ISOTime

Definition: A particular point in the progression of time in a calendar day expressed in either UTC time format (hh:mm:ss.sssZ), local time with UTC offset format (hh:mm:ss.sss+/-hh:mm), or local time format (hh:mm:ss.sss). These representations are defined in "XML Schema Part 2: Datatypes Second Edition - W3C Recommendation 28 October 2004" which is aligned with ISO 8601.Note on the time format:1) beginning / end of calendar day00:00:00 = the beginning of a calendar day24:00:00 = the end of a calendar day2) fractions of second in time formatDecimal fractions of seconds may be included. In this case, the involved parties shall agree on the maximum number of digits that are allowed.

Example: 16:34:44

2.4 ISOYear

Definition: Year represented by YYYY (ISO 8601)

Example: 2000

3 Identifier

3.1 AustrianBankleitzahlIdentifier

Definition: Austrian Bankleitzahl. Identifies Austrian financial institutions on the Austrian national clearing system.

Format: AT[0-9]{5,5}

Example: AT12345

3.2 BBANIdentifier

Definition: Basic Bank Account Number (BBAN). Identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the account of a customer.

Format: [a-zA-Z0-9]{1,30}

Example: BARC12345612345678

3.3 BEIIdentifier

Definition: Business Entity Identifier. Code allocated to non-financial institutions by the ISO 9362 Registration Authority. The Business Entity Identifier (BEI) has the same format as the BIC code (8 up to 11 characters) as stipulated in the standard ISO 9362 Banking (Banking Telecommunication Messages, Bank Identifier Codes, BIC).



Format: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}

Rule(s): BEI Only Business Entity Identifiers registered with the ISO 9362 Registration Authority and consisting of 8 or 11 contiguous characters comprising the first three or all four of the following components: BANK CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE, are valid BEIs.

(Fatal) Error Code: Sw.Stds.D00002

Example: USINFRPP

3.4 BICIdentifier

Definition: Bank Identifier Code. code allocated to a financial institution by a Registration Authority under an international identification scheme, as described in the latest edition of the international standard ISO 9362 "Banking - Banking telecommunication messages - Bank identifier codes".

Format: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}

Rule(s): BIC Valid BICs are registered with the ISO 9362 Registration Authority, and consist of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: BANK CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The bank code, country code and location code are mandatory, while the branch code is optional.(Fatal) Error Code: Sw.Stds.D00001

Example: CHASUS33

3.5 BelgianIdentifier

Definition: Identifier for Belgian securities.

Example: 359203

3.6 BloombergIdentifier

Definition: An identifier of a security assigned by the Bloomberg organisation.


Example: GGF.FP

3.7 CFIIdentifier

Definition: Classification type of the financial instrument, as per the ISO 10962 Classification of Financial Instrument (CFI) codification, eg, common share with voting rights, fully paid, or registered.

Format: [A-Z]{1,6}

Example: ESVUFR

SWIFTStandards MX


3.8 CHIPSParticipantIdentifier

Definition: (United States) Clearing House Interbank Payment System (CHIPS) Participant Identifier (ID). Identifies financial institutions participating on CHIPS. The CHIPS Participant ID is assigned by the New York Clearing House.

Format: CP[0-9]{4,4}

Example: CP1234

3.9 CHIPSUniversalIdentifier

Definition: (United States) Clearing House Interbank Payments System (CHIPS) Universal Identification (UID). Identifies entities that own accounts at CHIPS participating financial institutions, through which CHIPS payments are effected. The CHIPS UID is assigned by the New York Clearing House.

Format: CH[0-9]{6,6}

Example: CH123456

3.10 CUSIPIdentifier

Definition: Committee on Uniform Securities and Identification Procedures (CUSIP). The standards body that created and maintains the securities classification system in the US. Non-US securities have a similar number called the CINS number.

Example: 3134A33L8

3.11 CanadianPaymentsARNIdentifier

Definition: Canadian Payments Association Routing Number. Identifies Canadian financial institutions on the Canadian national clearing system.

Format: CA[0-9]{9,9}

Example: CA123456789

3.12 ConsolidatedTapeAssociationIdentifier

Definition: Identifier of a security assigned by the Consolidated Tape Association.


Example: 483894

3.13 CountryCode

Definition: Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).

Format: [A-Z]{2,2}

Rule(s): Country The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).(Fatal) Error Code: Sw.Stds.D00004

Example: BE



3.14 CurrencyCode

Definition: Code allocated to a currency, by a maintenance agency, under an international identification scheme as described in the latest edition of the international standard ISO 4217 "Codes for the representation of currencies and funds". Valid currency codes are registered with the ISO 4217 Maintenance Agency, and consist of three contiguous letters.

Format: [A-Z]{3,3}


Example: AWG

3.15 DunsIdentifier

Definition: Data Universal Numbering System. A unique identification number provided by Dun & Bradstreet to identify an organization.

Format: [0-9]{9,9}

Example: 578942538

3.16 DutchIdentifier

Definition: Identifier for Dutch securities.

Example: 234123

3.17 EANGLNIdentifier

Definition: Global Location Number. A non-significant reference number used to identify legal entities, functional entities or physical entities according to the European Association for Numbering (EAN) numbering scheme rules. The number is used to retrieve the detailed information linked to it.

Format: [0-9]{13,13}

Example: 7265658971233

3.18 EuroclearClearstreamIdentifier

Definition: Identifier of securities issued in Luxembourg. The common code is a 9-digit code that replaces the CEDEL (Clearstream) and Euroclear codes.


Example: 12197

3.19 ExtensiveBranchNetworkIdentifier

Definition: The extensive branch network list of the Australian Bank State Branch (BSB) Code. The codes are used for identifying Australian financial institutions, as assigned by the Australian Payments Clearing Association (APCA).

Format: AU[0-9]{6,6}

Example: AU123456

SWIFTStandards MX


3.20 ExternalBankTransactionDomainCode

Definition: Specifies the external domain code of the bank transaction code in the format of character string with a maximum length of 4 characters.The list of valid codes is an external code list published separately.


Example: D001

3.21 ExternalBankTransactionFamilyCode

Definition: Specifies the external family code of the bank transaction code in the format of character string with a maximum length of 4 characters.The list of valid codes is an external code list published separately, and is a sub-list of the bank transaction domain list.


Example: F001

3.22 ExternalBankTransactionSubFamilyCode

Definition: Specifies the external sub-family code of the bank transaction code in the format of character string with a maximum length of 4 characters.The list of valid codes is an external code list published separately, and is a sub-list of the bank transaction family code list.


Example: S001

3.23 ExternalClearingSystemMemberCode

Definition: Specifies the external clearing system member code in the format of character string with a maximum length of 35 characters.The list of valid codes is an external code list published separately.


Example: External Member Code 1

3.24 ExternalCode

Definition: Specifies an external code in the format of character string with a maximum length of 35 characters.The list of valid codes is an external code list published separately.


Example: External Code 1



3.25 ExternalLocalInstrumentCode

Definition: Specifies the external local instrument code in the format of character string with a maximum length of 35 characters.The list of valid codes is an external code list published separately.


Example: External Code 1

3.26 ExternalPurposeCode

Definition: Specifies the external purpose code in the format of character string with a maximum length of 35 characters.The list of valid codes is an external code list published separately.


Example: External Purpose Code 1

3.27 FedwireRoutingNumberIdentifier

Definition: Fedwire Routing Number. Identifies financial institutions, in the US, on the FedWire system. The routing number is assigned by the American Bankers Association (ABA).

Format: FW[0-9]{9,9}

Example: FW123456789

3.28 GermanBankleitzahlIdentifier

Definition: German Bankleitzahl. Identifies German financial institutions on the German national clearing systems.

Format: BL[0-9]{8,8}

Example: BL12345678

3.29 HellenicBankIdentificationCodeIdentifier

Definition: Hellenic Bank Identification Code Identifier. Identifies Greek financial institutions on the greek national clearing system.

Format: GR[0-9]{7,7}

Example: GR1234567

3.30 HongKongBankIdentifier

Definition: Hong Kong Bank Code. Identifies Hong Kong financial institutions on the Hong Kong local clearing system.

Format: HK[0-9]{3,3}

Example: HK123

SWIFTStandards MX


3.31 IBANIdentifier

Definition: An identifier used internationally by financial institutions to uniquely identify the account of a customer at a financial institution, as described in the latest edition of the international standard ISO 13616. "Banking and related financial services - International Bank Account Number (IBAN)".

Format: [a-zA-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}

Rule(s): IBAN A valid IBAN consists of all three of the following components: Country Code, check digits and BBAN.(Fatal) Error Code: Sw.Stds.D00003

Example: AT611904300234573201

3.32 IBEIIdentifier

Definition: International Business Entity Identifier to uniquely identify business entities playing a role in the lifecycle of and events related to a financial instrument. (tentative - to be confirmed).

Format: [A-Z]{2,2}[B-DF-HJ-NP-TV-XZ0-9]{7,7}[0-9]{1,1}

Example: DEXBC823N0

3.33 ISINIdentifier

Definition: International Securities Identification Number (ISIN). A numbering system designed by the United Nation's International Organisation for Standardisation (ISO). The ISIN is composed of a 2-character prefix representing the country of issue, followed by the national security number (if one exists), and a check digit. Each country has a national numbering agency that assigns ISIN numbers for securities in that country.

Format: [A-Z0-9]{12,12}

Example: US3134A33L82

3.34 IndianFinancialSystemCodeIdentifier

Definition: Indian Financial System Code Identifier. Identifies Indian financial institutions on the Indian national clearing system.

Format: IN[a-zA-Z0-9]{11,11}

Example: IN12azBX12345

3.35 IrishNSCIdentifier

Definition: Irish National Sorting Code. Identifies Irish financial institutions on the Irish national clearing system.

Format: IE[0-9]{6,6}

Example: IE123456

3.36 ItalianDomesticIdentifier

Definition: Italian Domestic Identification Code. Identifies Italian financial institutions on the Italian national clearing system. The code is assigned by the Associazione Bancaria Italiana (ABI).

Format: IT[0-9]{10,10}



Example: IT1234567890

3.37 LanguageCode

Definition: Specifies a language.


Example: ENG

3.38 MICIdentifier

Definition: Market Identifier Code. The identification of a financial market, as stipulated in the norm ISO 10383 'Codes for exchanges and market identifications'.

Format: [A-Z0-9]{4,4}

Example: XTKS

3.39 NationalityCode

Definition: Specifies the country where a person was born or is naturalised.


Example: US

3.40 NewZealandNCCIdentifier

Definition: New Zealand Bank/Branch Code. Identifies New Zealand institutions on the New Zealand national clearing system. The code is assigned by the New Zealand Bankers' Association (NZBA).

Format: NZ[0-9]{6,6}

Example: NZ123456

3.41 PolishNationalClearingCodeIdentifier

Definition: Polish National Clearing Code Identifier. Identifies Polish financial institutions on the Polish national clearing system.

Format: PL[0-9]{8,8}

Example: PL12345678

3.42 PortugueseNCCIdentifier

Definition: Portuguese National Clearing Code. Identifies Portuguese financial institutions on the Portuguese national clearing system.

Format: PT[0-9]{8,8}

Example: PT12345678

3.43 QUICKIdentifier

Definition: Identifier of a security assigned by the Japanese QUICK identification scheme for financial instruments.

Example: 97334

SWIFTStandards MX


3.44 RICIdentifier

Definition: Reuters Identification Code (RIC). A numbering system used within the Reuters system to identify instruments worldwide. The RIC contains an X-character market specific code (can be the CUSIP or EPIC codes) followed by a full stop, then the two-digit ISO country code, eg, IBM in UK is IBM.UK.


Example: TDVd.CR

3.45 RussianCentralBankIdentificationCodeIdentifier

Definition: Russian Central Bank Identification Code. Identifies Russian financial institutions on the Russian national clearing system.

Format: RU[0-9]{9,9}

Example: RU123456789

3.46 SEDOLIdentifier

Definition: Stock Exchange Daily Official List (SEDOL) number. A code used by the London Stock Exchange to identify foreign stocks, especially those that aren't actively traded in the US and don't have a CUSIP number.

Example: 5719210

3.47 SicovamIdentifier

Definition: Identifier for French securities assigned by the Societe Interprofessionnelle Pour La Compensation des Valeurs Mobilieres in France. The Sicovam is composed of 5-digits.

Example: 12777

3.48 SmallNetworkIdentifier

Definition: The small network list of the Australian Bank State Branch (BSB) Code. The codes are used for identifying Australian financial institutions, as assigned by the Australian Payments Clearing Association (APCA).

Format: AU[0-9]{6,6}

Example: AU123456

3.49 SouthAfricanNCCIdentifier

Definition: South African National Clearing Code (NCC). Identifies South African financial institutions on the South African national clearing system. The code is assigned by the South African Bankers Services Company Ltd. (BankServ).

Format: ZA[0-9]{6,6}

Example: ZA123456



3.50 SpanishDomesticInterbankingIdentifier

Definition: Spanish Domestic Interbanking Code. Identifies Spanish financial institutions on the Spanish national clearing system. The code is assigned by the Centro de Cooperacion Interbancaria (CCI).

Format: ES[0-9]{8,9}

Example: ES12345678

3.51 SwissBCIdentifier

Definition: Swiss Bank Code. Identifies Swiss institutions on the Swiss national clearing system.

Format: SW[0-9]{3,5}

Example: SW123

3.52 SwissSICIdentifier

Definition: Swiss Interbank Clearing (SIC) Code. Identifies Swiss financial institutions domestically, on the Swiss national clearing system.

Format: SW[0-9]{6,6}

Example: SW123456

3.53 TickerIdentifier

Definition: Letters that identify a stock traded on a stock exchange. The Ticker Symbol is a short and convenient way of identifying a stock, eg, RTR.L for Reuters quoted in London.


Example: SOL

3.54 UKDomesticSortCodeIdentifier

Definition: United Kingdom (UK) Sort Code. Identifies British financial institutions on the British national clearing systems. The sort code is assigned by the Association for Payments and Clearing Services (APACS).

Format: SC[0-9]{6,6}

Example: SC123456

3.55 UPICIdentifier

Definition: Universal Payment Identification Code (UPIC). Identifier used by the New York Clearing House to mask confidential data, such as bank accounts and bank routing numbers. UPIC numbers remain with business customers, regardless of banking relationship changes.

Format: [0-9]{8,17}

Example: 12345678

3.56 ValorenIdentifier

Definition: Identifier for Swiss securities assigned by Telekurs Financial, the Swiss numbering agency.

Example: 832614

SWIFTStandards MX


3.57 WertpapierIdentifier

Definition: Wertpapier Kenn-nummer. A number issued in Germany by the Wertpapier Mitteilungen.The Wertpapier Kenn-nummer, sometimes called WPK, contains 6-digits, but no check digit. There are different ranges of numbers representing different classes of securities.

Example: 911958

4 Quantity: Number and Decimal Number

4.1 DecimalNumber

Definition: Number of objects represented as a decimal number, eg, 0.75 or 45.6.

Format: fractionDigits: 17totalDigits: 18

Example: 123456789.123456789

4.2 Number

Definition: Number of objects represented as an integer.


Example: 123456789012345678

5 Rate

5.1 BaseOneRate

Definition: Rate expressed as a decimal, eg, 0.7 is 7/10 and 70%.


Example: 0.60

5.2 PercentageRate

Definition: Rate expressed as a percentage, ie, in hundredths, eg, 0.7 is 7/10 of a percent, and 7.0 is 7%.


Example: 35

6 Text

6.1 Max1025Text

Definition: Specifies a character string with a maximum length of 1025 characters.


Example: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789



6.2 Max105Text



Example: azefgvgldfpgtvcvlmgovl;v ; :B;lgkdfwxcvljfqsifj

6.3 Max128Text



Example: A string value of maximum 128 characters.

6.4 Max140Text



Example: ABCDEFGHIJKLMNOPQRST123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890

6.5 Max15NumericText

Definition: Specifies a numeric string with a maximum length of 15 digits.

Format: [0-9]{1,15}

Example: 458793625148975

6.6 Max15PlusSignedNumericText

Definition: Specifies a numeric string with a maximum length of 15 digits and may be prefixed with a plus sign.

Format: [+]{0,1}[0-9]{1,15}

Example: +2450

6.7 Max16Text



Example: ABCdEFghIJKLMNO?

6.8 Max256Text



SWIFTStandards MX



6.9 Max34Text




6.10 Max350Text



Example: 12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890

6.11 Max35Text






Format: [0-9]{1,3}

Example: 003

6.13 Max3Text



Example: Nad

6.14 Max4AlphaNumericText

Definition: Specifies an alphanumeric string with a maximum length of 4 characters.

Format: [a-zA-Z0-9]{1,4}

Example: aBc9



6.15 Max500Text



Example: 12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890



Format: [0-9]{1,5}

Example: 1

6.17 Max70Text

Definition: Specifies a character string with a maximum length of 70characters.


Example: A string value of maximum 70 characters.

End PointsEnd Points Index

1 Account identification1.1 AccountIdentification3Choice1.2 CashAccount7

2 Amount range2.1 CurrencyAndAmountRange

3 Charge3.1 ChargesInformation1

4 Cheque4.1 Cheque5

5 Date time5.1 DateAndDateTimeChoice

6 Date time period6.1 DateTimePeriodDetails

SWIFTStandards MX


7 Financial institution identification7.1 BranchAndFinancialInstitutionIdentification3

8 Miscellaneous8.1 Pagination

9 Party identification9.1 PartyIdentification8

10 Postal address10.1 PostalAddress1

11 Securities quantity11.1 FinancialInstrumentQuantityChoice

12 Tax12.1 TaxInformation2

End Points Description

1 Account identification

1.1 AccountIdentification3ChoiceAccountIdentification3Choice is used in message BankToCustomerAccountReportV01 p.6, message BankToCustomerDebitCreditNotificationV01 p.243, message BankToCustomerStatementV01 p.124.

Definition: Unique identifier of an account as assigned by the account servicer.Type: One of the following AccountIdentification3Choice element(s) must be used:

Ref Or Message Item <XML Tag> Mult. Represent./Type

1.1.0 {Or IBAN <IBAN> [1..1] Identifier

1.1.1 Or BBAN <BBAN> [1..1] Identifier

1.1.2 Or UPIC <UPIC> [1..1] Identifier

1.1.3 Or} ProprietaryAccount <PrtryAcct> [1..1]

1.1.4 Identification <Id> [1..1] Text

1.1.0 IBAN <IBAN>Presence: [1..1]This message item is part of choice 1.1 AccountIdentification3Choice.Definition: International Bank Account Number (IBAN) - identifier used internationally by financial institutions to

uniquely identify the account of a customer. Further specifications of the format and content of the IBAN can be found in the standard ISO 13616 "Banking and related financial services - International Bank Account Number (IBAN)" version 1997-10-01, or later revisions.

Data Type: IBANIdentifier



Format: [a-zA-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}Rule(s): IBAN

A valid IBAN consists of all three of the following components: Country Code, check digits and BBAN.(Fatal) Error Code: Sw.Stds.D00003

1.1.1 BBAN <BBAN>Presence: [1..1]This message item is part of choice 1.1 AccountIdentification3Choice.Definition: Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual

countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer.

Data Type: BBANIdentifierFormat: [a-zA-Z0-9]{1,30}

1.1.2 UPIC <UPIC>Presence: [1..1]This message item is part of choice 1.1 AccountIdentification3Choice.Definition: Universal Payment Identification Code (UPIC) - identifier used by the New York Clearing House to mask

confidential data, such as bank accounts and bank routing numbers. UPIC numbers remain with business customers, regardless of banking relationship changes.

Data Type: UPICIdentifierFormat: [0-9]{8,17}

1.1.3 ProprietaryAccount <PrtryAcct>Presence: [1..1]This message item is part of choice 1.1 AccountIdentification3Choice.Definition: Account number used by financial institutions in individual countries to identify an account of a customer,

but not necessarily the bank and branch of the financial institution in which the account is held.Type: This message item is composed of the following SimpleIdentificationInformation2 element(s):



1.1.4 Identification <Id>Presence: [1..1]Definition: Name or number assigned by an entity to enable recognition of that entity, eg, account identifier.Data Type: Max34TextFormat: maxLength: 34

minLength: 1

1.2 CashAccount7CashAccount7 is used in message BankToCustomerAccountReportV01 p.6, p.14, p.14, p.17, message BankToCustomerDebitCreditNotificationV01 p.243, p.250, p.250, p.253, message BankToCustomerStatementV01 p.124, p.132, p.132, p.135, message CustomerCreditTransferInitiationV02 p.354, p.354, p.354, p.355, p.355, p.355,

SWIFTStandards MX


p.355, p.355, message PaymentStatusReportV02 p.405, p.405, p.405, p.405, p.406, p.406, p.406, p.407, p.407, p.407, p.407.

Definition: Information used for identifying an account.Type: The following CashAccount7 element(s) must be used:


1.2.0 Identification <Id> [1..1]






1.2.6 Type <Tp> [0..1]

1.2.7 {Or Code <Cd> [1..1] Code

1.2.8 Or} Proprietary <Prtry> [1..1] Text

1.2.9 Currency <Ccy> [0..1] Code

1.2.10 Name <Nm> [0..1] Text

1.2.0 Identification <Id>Presence: [1..1]Definition: Unique and unambiguous identification of the account between the account owner and the account servicer.Type: This message item is composed of one of the following AccountIdentification3Choice element(s):






1.2.1 IBAN <IBAN>Presence: [1..1]This message item is part of choice 1.2.0 Identification.Definition: International Bank Account Number (IBAN) - identifier used internationally by financial institutions to

uniquely identify the account of a customer. Further specifications of the format and content of the IBAN can be found in the standard ISO 13616 "Banking and related financial services - International Bank Account Number (IBAN)" version 1997-10-01, or later revisions.

Data Type: IBANIdentifierFormat: [a-zA-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}Rule(s): IBAN

A valid IBAN consists of all three of the following components: Country Code, check digits and BBAN.




1.2.2 BBAN <BBAN>Presence: [1..1]This message item is part of choice 1.2.0 Identification.Definition: Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual

countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer.

Data Type: BBANIdentifierFormat: [a-zA-Z0-9]{1,30}

1.2.3 UPIC <UPIC>Presence: [1..1]This message item is part of choice 1.2.0 Identification.Definition: Universal Payment Identification Code (UPIC) - identifier used by the New York Clearing House to mask

confidential data, such as bank accounts and bank routing numbers. UPIC numbers remain with business customers, regardless of banking relationship changes.

Data Type: UPICIdentifierFormat: [0-9]{8,17}

1.2.4 ProprietaryAccount <PrtryAcct>Presence: [1..1]This message item is part of choice 1.2.0 Identification.Definition: Account number used by financial institutions in individual countries to identify an account of a customer,

but not necessarily the bank and branch of the financial institution in which the account is held.Type: This message item is composed of the following SimpleIdentificationInformation2 element(s):




minLength: 1

1.2.6 Type <Tp>Presence: [0..1]Definition: Nature, or use, of the account.Type: This message item is composed of one of the following CashAccountType2 element(s):


1.2.7 {Or Code <Cd> [1..1] Code

SWIFTStandards MX




1.2.7 Code <Cd>Presence: [1..1]This message item is part of choice 1.2.6 Type.Definition: Nature or use of the account in a coded form.Data Type: CodeOne of the following CashAccountType4Code values must be used:


















1.2.8 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 1.2.6 Type.Definition: Proprietary nature or use of the account.




minLength: 1

1.2.9 Currency <Ccy>Presence: [0..1]Definition: Identification of the currency in which the account is held.

Usage: Currency should only be used in case one and the same account number covers several currencies and the initiating party needs to identify which currency needs to be used for settlement on the account.

Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable

1.2.10 Name <Nm>Presence: [0..1]Definition: Name of the account, assigned by the account servicing institution in agreement with the account owner in




minLength: 1

2 Amount range

2.1 CurrencyAndAmountRangeCurrencyAndAmountRange is used in message BankToCustomerAccountReportV01 p.6, p.11, p.14, message BankToCustomerDebitCreditNotificationV01 p.247, p.250, message BankToCustomerStatementV01 p.124, p.129, p.132.

Definition: Range of amount values.Type: The following CurrencyAndAmountRange element(s) must be used:


2.1.0 Amount <Amt> [1..1]

2.1.1 {Or FromAmount <FrAmt> [1..1]

2.1.2 BoundaryAmount <BdryAmt> [1..1] Amount

2.1.3 Included <Incl> [1..1] Indicator

2.1.4 Or ToAmount <ToAmt> [1..1]



2.1.7 Or FromToAmount <FrToAmt> [1..1]

SWIFTStandards MX



2.1.8 FromAmount <FrAmt> [1..1]



2.1.11 ToAmount <ToAmt> [1..1]



2.1.14 Or EqualAmount <EQAmt> [1..1] Amount

2.1.15 Or} NotEqualAmount <NEQAmt> [1..1] Amount

2.1.16 CreditDebitIndicator <CdtDbtInd> [0..1] Code

2.1.17 Currency <Ccy> [1..1] Code

2.1.0 Amount <Amt>Presence: [1..1]Definition: Specified amount or amount range.Type: This message item is composed of one of the following ImpliedCurrencyAmountRangeChoice element(s):


2.1.1 {Or FromAmount <FrAmt> [1..1]

2.1.4 Or ToAmount <ToAmt> [1..1]

2.1.7 Or FromToAmount <FrToAmt> [1..1]

2.1.14 Or EqualAmount <EQAmt> [1..1] Amount

2.1.15 Or} NotEqualAmount <NEQAmt> [1..1] Amount

2.1.1 FromAmount <FrAmt>Presence: [1..1]This message item is part of choice 2.1.0 Amount.Definition: Lower boundary of a range of amount values.Type: This message item is composed of the following AmountRangeBoundary1 element(s):




2.1.2 BoundaryAmount <BdryAmt>Presence: [1..1]Definition: Amount value of the range limit.Data Type: ImpliedCurrencyAndAmount




2.1.3 Included <Incl>Presence: [1..1]Definition: Indicates whether the boundary amount is included in the range of amount values. Data Type: One of the following YesNoIndicator values must be used:


2.1.4 ToAmount <ToAmt>Presence: [1..1]This message item is part of choice 2.1.0 Amount.Definition: Upper boundary of a range of amount values.Type: This message item is composed of the following AmountRangeBoundary1 element(s):




2.1.5 BoundaryAmount <BdryAmt>Presence: [1..1]Definition: Amount value of the range limit.Data Type: ImpliedCurrencyAndAmountFormat: fractionDigits: 5

minInclusive: 0totalDigits: 18



2.1.7 FromToAmount <FrToAmt>Presence: [1..1]This message item is part of choice 2.1.0 Amount.Definition: Range of valid amount values.Type: This message item is composed of the following FromToAmountRange element(s):


2.1.8 FromAmount <FrAmt> [1..1]

SWIFTStandards MX



2.1.11 ToAmount <ToAmt> [1..1]

2.1.8 FromAmount <FrAmt>Presence: [1..1]Definition: Lower boundary of a range of amount values.Type: This message item is composed of the following AmountRangeBoundary1 element(s):




2.1.9 BoundaryAmount <BdryAmt>Presence: [1..1]Definition: Amount value of the range limit.Data Type: ImpliedCurrencyAndAmountFormat: fractionDigits: 5




2.1.11 ToAmount <ToAmt>Presence: [1..1]Definition: Upper boundary of a range of amount values.Type: This message item is composed of the following AmountRangeBoundary1 element(s):




2.1.12 BoundaryAmount <BdryAmt>Presence: [1..1]Definition: Amount value of the range limit.Data Type: ImpliedCurrencyAndAmount






2.1.14 EqualAmount <EQAmt>Presence: [1..1]This message item is part of choice 2.1.0 Amount.Definition: Exact value an amount must match to be considered valid.Data Type: ImpliedCurrencyAndAmountFormat: fractionDigits: 5


2.1.15 NotEqualAmount <NEQAmt>Presence: [1..1]This message item is part of choice 2.1.0 Amount.Definition: Value that an amount must not match to be considered valid.Data Type: ImpliedCurrencyAndAmountFormat: fractionDigits: 5


2.1.16 CreditDebitIndicator <CdtDbtInd>Presence: [0..1]Definition: Indicates whether the amount is a credited or debited amount.Data Type: CodeWhen this message item is present, one of the following CreditDebitCode values must be used:



2.1.17 Currency <Ccy>Presence: [1..1]Definition: Medium of exchange of value, used to qualify an amount.Data Type: CurrencyCodeFormat: [A-Z]{3,3}Rule(s): ValidationByTable

SWIFTStandards MX


3 Charge

3.1 ChargesInformation1ChargesInformation1 is used in message PaymentStatusReportV02 p.405.

Definition: Information on the charges related to the payment transaction.Type: The following ChargesInformation1 element(s) must be used:


3.1.0 ChargesAmount <ChrgsAmt> [1..1] Amount

3.1.1 ChargesParty <ChrgsPty> [1..1]

3.1.2 FinancialInstitutionIdentification <FinInstnId> [1..1]

3.1.3 {Or BIC <BIC> [1..1] Identifier

3.1.4 Or ClearingSystemMemberIdentification <ClrSysMmbId> [1..1]

3.1.5 {{Or Identification <Id> [1..1] Code

3.1.6 Or}} Proprietary <Prtry> [1..1] Text

3.1.7 Or NameAndAddress <NmAndAdr> [1..1]

3.1.8 Name <Nm> [1..1] Text

3.1.9 PostalAddress <PstlAdr> [1..1]

3.1.10 AddressType <AdrTp> [0..1] Code

3.1.11 AddressLine <AdrLine> [0..5] Text

3.1.12 StreetName <StrtNm> [0..1] Text

3.1.13 BuildingNumber <BldgNb> [0..1] Text

3.1.14 PostCode <PstCd> [0..1] Text

3.1.15 TownName <TwnNm> [0..1] Text

3.1.16 CountrySubDivision <CtrySubDvsn> [0..1] Text

3.1.17 Country <Ctry> [1..1] Code

3.1.18 Or ProprietaryIdentification <PrtryId> [1..1]


3.1.20 Issuer <Issr> [0..1] Text

3.1.21 Or} CombinedIdentification <CmbndId> [1..1]

3.1.22 BIC <BIC> [0..1] Identifier

3.1.23 ClearingSystemMemberIdentification <ClrSysMmbId> [0..1]



3.1.26 Name <Nm> [0..1] Text













3.1.36 ProprietaryIdentification <PrtryId> [0..1]



3.1.39 BranchIdentification <BrnchId> [0..1]


3.1.41 Name <Nm> [0..1] Text










3.1.0 ChargesAmount <ChrgsAmt>Presence: [1..1]Definition: Transaction charges to be paid by the charge bearer.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



3.1.1 ChargesParty <ChrgsPty>Presence: [1..1]

SWIFTStandards MX


Definition: Party that takes the transaction charges or to which the transaction charges are due.Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):




3.1.2 FinancialInstitutionIdentification <FinInstnId>Presence: [1..1]Definition: Unique and unambiguous identifier of a financial institution, as assigned under an internationally recognised

or proprietary identification scheme.Type: This message item is composed of one of the following FinancialInstitutionIdentification5Choice element(s):







3.1.3 BIC <BIC>Presence: [1..1]This message item is part of choice 3.1.2 FinancialInstitutionIdentification.Definition: Bank Identifier Code. Code allocated to financial institutions by the Registration Authority, under an

international identification scheme, as described in the latest version of the standard ISO 9362 Banking (Banking telecommunication messages, Bank Identifier Codes).

Data Type: BICIdentifierFormat: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}Rule(s): BIC

Valid BICs are registered with the ISO 9362 Registration Authority, and consist of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: BANK CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The bank code, country code and location code are mandatory, while the branch code is optional.(Fatal) Error Code: Sw.Stds.D00001

3.1.4 ClearingSystemMemberIdentification <ClrSysMmbId>Presence: [1..1]This message item is part of choice 3.1.2 FinancialInstitutionIdentification.Definition: Unique and unambiguous identifier of a clearing system member, as assigned by the system or system

administrator.Type: This message item is composed of one of the following ClearingSystemMemberIdentification3Choice element(s):




3.1.5 {Or Identification <Id> [1..1] Code


3.1.5 Identification <Id>Presence: [1..1]This message item is part of choice 3.1.4 ClearingSystemMemberIdentification.Definition: Identification for a clearing system member, identified in the list of clearing system member identifications

published externally. Data Type: ExternalClearingSystemMemberCodeFormat: maxLength: 35

minLength: 1

3.1.6 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 3.1.4 ClearingSystemMemberIdentification.Definition: Identification Code for a clearing system, that has not yet been identified in the list of clearing systems. Data Type: Max35TextFormat: maxLength: 35

minLength: 1

3.1.7 NameAndAddress <NmAndAdr>Presence: [1..1]This message item is part of choice 3.1.2 FinancialInstitutionIdentification.Definition: Identifies the name and address of a financial institution. Type: This message item is composed of the following NameAndAddress7 element(s):


3.1.8 Name <Nm> [1..1] Text


3.1.8 Name <Nm>Presence: [1..1]Definition: Name by which a party is known and which is usually used to identify that party.Data Type: Max70TextFormat: maxLength: 70

minLength: 1

3.1.9 PostalAddress <PstlAdr>Presence: [1..1]Definition: Information that locates and identifies a specific address, as defined by postal services.Type: This message item is composed of the following PostalAddress1 element(s):

SWIFTStandards MX











3.1.10 AddressType <AdrTp>Presence: [0..1]Definition: Identifies the nature of the postal address.Data Type: CodeWhen this message item is present, one of the following AddressType2Code values must be used:

Code Name DefinitionADDR Postal Address is the complete postal address.

BIZZ Business Address is the business address.

DLVY DeliveryTo Address is the address to which delivery is to take place.

HOME Residential Address is the home address.

MLTO MailTo Address is the address to which mail is sent.

PBOX POBox Address is a postal office (PO) box.

3.1.11 AddressLine <AdrLine>Presence: [0..5]Definition: Information that locates and identifies a specific address, as defined by postal services, that is presented in

free format text.Data Type: Max70TextFormat: maxLength: 70

minLength: 1

3.1.12 StreetName <StrtNm>Presence: [0..1]Definition: Name of a street or thoroughfare.Data Type: Max70TextFormat: maxLength: 70

minLength: 1



3.1.13 BuildingNumber <BldgNb>Presence: [0..1]Definition: Number that identifies the position of a building on a street.Data Type: Max16TextFormat: maxLength: 16

minLength: 1

3.1.14 PostCode <PstCd>Presence: [0..1]Definition: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting

of mail.Data Type: Max16TextFormat: maxLength: 16

minLength: 1

3.1.15 TownName <TwnNm>Presence: [0..1]Definition: Name of a built-up area, with defined boundaries, and a local government.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

3.1.16 CountrySubDivision <CtrySubDvsn>Presence: [0..1]Definition: Identifies a subdivision of a country eg, state, region, county.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

3.1.17 Country <Ctry>Presence: [1..1]Definition: Nation with its own government.Data Type: CountryCodeFormat: [A-Z]{2,2}Rule(s): Country


3.1.18 ProprietaryIdentification <PrtryId>Presence: [1..1]This message item is part of choice 3.1.2 FinancialInstitutionIdentification.Definition: Unique and unambiguous identifier, as assigned to a financial institution using a proprietary identification

scheme.Type: This message item is composed of the following GenericIdentification3 element(s):

SWIFTStandards MX






minLength: 1

3.1.20 Issuer <Issr>Presence: [0..1]Definition: Entity that assigns the identification.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

3.1.21 CombinedIdentification <CmbndId>Presence: [1..1]This message item is part of choice 3.1.2 FinancialInstitutionIdentification.Definition: Unique and unambiguous identification of a financial institution, through a combimation of globally

recognised or proprietary identification scheme.Type: This message item is composed of the following FinancialInstitutionIdentification3 element(s):




3.1.26 Name <Nm> [0..1] Text



3.1.22 BIC <BIC>Presence: [0..1]Definition: Bank Identifier Code. Code allocated to financial institutions by the Registration Authority, under an



Valid BICs are registered with the ISO 9362 Registration Authority, and consist of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: BANK CODE,



COUNTRY CODE, LOCATION CODE, BRANCH CODE. The bank code, country code and location code are mandatory, while the branch code is optional.(Fatal) Error Code: Sw.Stds.D00001

3.1.23 ClearingSystemMemberIdentification <ClrSysMmbId>Presence: [0..1]Definition: Unique and unambiguous identifier of a clearing system member, as assigned by the system or system







minLength: 1


minLength: 1


minLength: 1


SWIFTStandards MX




















minLength: 1


minLength: 1




minLength: 1



minLength: 1


minLength: 1


minLength: 1



3.1.36 ProprietaryIdentification <PrtryId>Presence: [0..1]Definition: Unique and unambiguous identifier, as assigned to a financial institution using a proprietary identification


SWIFTStandards MX






minLength: 1


minLength: 1

3.1.39 BranchIdentification <BrnchId>Presence: [0..1]Definition: Information identifying a specific branch of a financial institution.

Usage : this component should be used in case the identification information in the financial institution component does not provide identification up to branch level.

Type: This message item is composed of the following BranchData element(s):



3.1.41 Name <Nm> [0..1] Text


3.1.40 Identification <Id>Presence: [0..1]Definition: Unique and unambiguous identification of a branch of a financial institution.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

3.1.41 Name <Nm>Presence: [0..1]Definition: Name by which a party is known and which is usually used to identify that party.Data Type: Max35Text























minLength: 1

SWIFTStandards MX



minLength: 1


minLength: 1



minLength: 1


minLength: 1


minLength: 1





4 Cheque

4.1 Cheque5Cheque5 is used in message CustomerCreditTransferInitiationV02 p.355.

Definition: Set of characteristics related to a cheque instruction, eg cheque type or cheque number.Type: The following Cheque5 element(s) must be used:


4.1.0 ChequeType <ChqTp> [0..1] Code

4.1.1 ChequeNumber <ChqNb> [0..1] Text

4.1.2 ChequeFrom <ChqFr> [0..1]

4.1.3 Name <Nm> [1..1] Text

4.1.4 Address <Adr> [1..1]









4.1.13 DeliveryMethod <DlvryMtd> [0..1]

4.1.14 {Or Code <Cd> [1..1] Code


4.1.16 DeliverTo <DlvrTo> [0..1]

4.1.17 Name <Nm> [1..1] Text

4.1.18 Address <Adr> [1..1]









4.1.27 InstructionPriority <InstrPrty> [0..1] Code

4.1.28 ChequeMaturityDate <ChqMtrtyDt> [0..1] DateTime

SWIFTStandards MX



4.1.29 FormsCode <FrmsCd> [0..1] Text

4.1.30 MemoField <MemoFld> [0..1] Text

4.1.31 RegionalClearingZone <RgnlClrZone> [0..1] Text

4.1.32 PrintLocation <PrtLctn> [0..1] Text

Rule(s): ChequeMaturityDateRule If ChequeType is present and is DRFT or ELDR, then ChequeMaturityDate is optional. If ChequeType is not present or is different from DRFT or ELDR, then ChequeMaturityDate is not allowed.

Rule rationale: ChequeMaturityDate may be present only when ChequeType is DRFT or ELDR.

4.1.0 ChequeType <ChqTp>Presence: [0..1]Definition: Specifies the type of cheque to be issued by the first agent.Data Type: CodeWhen this message item is present, one of the following ChequeType2Code values must be used:

Code Name DefinitionBCHQ BankCheque Cheque drawn on the account of the debtor's financial

institution, which is debited on the debtor's account when the cheque is issued.These cheques are printed by the debtor's financial institution and payment is guaranteed by the financial institution. Synonym is 'cashier's cheque'.

CCCH CertifiedCustomerCheque Cheque drawn on the account of the debtor, and debited on the debtor's account when the cheque is cashed. The financial institution prints and certifies the cheque, guaranteeing the payment.

CCHQ CustomerCheque Cheque drawn on the account of the debtor, and debited on the debtor's account when the cheque is cashed. Synonym is 'corporate cheque'.

DRFT Draft A guaranteed bank cheque with a future value date (do not pay before], which in commercial terms is a 'negotiatable instrument': the beneficiary can receive early payment from any bank under subtraction of a discount. The ordering customer's account is debited on value date.

ELDR ElectronicDraft An instrument with a future value date (do not pay before], which in commercial terms is a 'negotiatable instrument': the beneficiary can receive early payment from any bank under subtraction of a discount. The ordering customer's account is debited on value date.

4.1.1 ChequeNumber <ChqNb>Presence: [0..1]



Definition: Identifies the cheque number.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

4.1.2 ChequeFrom <ChqFr>Presence: [0..1]Definition: Identifies the party that ordered the issuance of the cheque.Type: This message item is composed of the following NameAndAddress3 element(s):


4.1.3 Name <Nm> [1..1] Text

4.1.4 Address <Adr> [1..1]

4.1.3 Name <Nm>Presence: [1..1]Definition: Name by which a party is known and is usually used to identify that identity.Data Type: Max70TextFormat: maxLength: 70

minLength: 1

4.1.4 Address <Adr>Presence: [1..1]Definition: Postal address of a party.Type: This message item is composed of the following PostalAddress1 element(s):











SWIFTStandards MX










minLength: 1


minLength: 1


minLength: 1



minLength: 1


minLength: 1




minLength: 1



4.1.13 DeliveryMethod <DlvryMtd>Presence: [0..1]Definition: Specifies the delivery method of the cheque by the debtor's agent.Type: This message item is composed of one of the following ChequeDeliveryMethod1Choice element(s):


4.1.14 {Or Code <Cd> [1..1] Code


4.1.14 Code <Cd>Presence: [1..1]This message item is part of choice 4.1.13 DeliveryMethod.Definition: Specifies the delivery method of the cheque by the debtor's agent.Data Type: CodeOne of the following ChequeDelivery1Code values must be used:

Code Name DefinitionCRCD CourierToCreditor Cheque is to be sent through courier services to creditor.

CRDB CourierToDebtor Cheque is to be sent through courier services to debtor.

CRFA CourierToFinalAgent Cheque is to be sent through courier services to creditor agent.

MLCD MailToCreditor Cheque is to be sent through mail services to creditor.

MLDB MailToDebtor Cheque is to be sent through mail services to debtor.

MLFA MailToFinalAgent Cheque is to be sent through mail services to creditor agent.

PUCD PickUpByCreditor Cheque will be picked up by the creditor

SWIFTStandards MX


Code Name DefinitionPUDB PickUpByDebtor Cheque will be picked up by the debtor.

PUFA PickUpByFinalAgent Cheque will be picked up by the creditor agent.

RGCD RegisteredMailToCreditor Cheque is to be sent through registered mail services to creditor.

RGDB RegisteredMailToDebtor Cheque is to be sent through registered mail services to debtor

RGFA RegisteredMailToFinalAgent

Cheque is to be sent through registered mail services to creditor agent.

4.1.15 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 4.1.13 DeliveryMethod.Definition: Specifies a proprietary delivery method of the cheque by the debtor's agent.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

4.1.16 DeliverTo <DlvrTo>Presence: [0..1]Definition: Identifies the party to whom the debtor's agent should send the cheque.Type: This message item is composed of the following NameAndAddress3 element(s):


4.1.17 Name <Nm> [1..1] Text

4.1.18 Address <Adr> [1..1]

4.1.17 Name <Nm>Presence: [1..1]Definition: Name by which a party is known and is usually used to identify that identity.Data Type: Max70TextFormat: maxLength: 70

minLength: 1

4.1.18 Address <Adr>Presence: [1..1]Definition: Postal address of a party.Type: This message item is composed of the following PostalAddress1 element(s):






















minLength: 1


minLength: 1

4.1.22 BuildingNumber <BldgNb>Presence: [0..1]Definition: Number that identifies the position of a building on a street.

SWIFTStandards MX



minLength: 1



minLength: 1


minLength: 1


minLength: 1



4.1.27 InstructionPriority <InstrPrty>Presence: [0..1]Definition: Urgency or order of importance that the originator would like the recipient of the payment instruction to

apply to the processing of the payment instruction.Data Type: CodeWhen this message item is present, one of the following Priority2Code values must be used:





4.1.28 ChequeMaturityDate <ChqMtrtyDt>Presence: [0..1]Definition: Date when the draft becomes payable and the debtor's account is debited. Data Type: ISODate

4.1.29 FormsCode <FrmsCd>Presence: [0..1]Definition: Code agreed between the initiating party and the debtor's agent, that specifies the cheque layout, company

logo and digitised signature to be used to print the cheque. Data Type: Max35TextFormat: maxLength: 35

minLength: 1

4.1.30 MemoField <MemoFld>Presence: [0..1]Definition: Information that needs to be printed on a cheque, used by the payer to add miscellaneous information. Data Type: Max35TextFormat: maxLength: 35

minLength: 1

4.1.31 RegionalClearingZone <RgnlClrZone>Presence: [0..1]Definition: Regional area in which the cheque can be cleared, when a country has no nation-wide cheque clearing

organisation.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

4.1.32 PrintLocation <PrtLctn>Presence: [0..1]Definition: Specifies the print location of the cheque.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

5 Date time

5.1 DateAndDateTimeChoiceDateAndDateTimeChoice is used in message BankToCustomerAccountReportV01 p.7, p.8, p.8, message BankToCustomerDebitCreditNotificationV01 p.244, p.244, message BankToCustomerStatementV01 p.125, p.126, p.126.

Definition: Choice between a date or a date and time format.Type: One of the following DateAndDateTimeChoice element(s) must be used:

SWIFTStandards MX



5.1.0 {Or Date <Dt> [1..1] DateTime

5.1.1 Or} DateTime <DtTm> [1..1] DateTime

5.1.0 Date <Dt>Presence: [1..1]This message item is part of choice 5.1 DateAndDateTimeChoice.Definition: Specified date.Data Type: ISODate

5.1.1 DateTime <DtTm>Presence: [1..1]This message item is part of choice 5.1 DateAndDateTimeChoice.Definition: Specified date and time.Data Type: ISODateTime

6 Date time period

6.1 DateTimePeriodDetailsDateTimePeriodDetails is used in message BankToCustomerAccountReportV01 p.6, p.6, p.11, p.14, message BankToCustomerDebitCreditNotificationV01 p.243, p.247, p.250, message BankToCustomerStatementV01 p.124, p.124, p.129, p.132.

Definition: Time span defined by a start date and time, and an end date and time.Type: The following DateTimePeriodDetails element(s) must be used:


6.1.0 FromDateTime <FrDtTm> [1..1] DateTime

6.1.1 ToDateTime <ToDtTm> [1..1] DateTime

6.1.0 FromDateTime <FrDtTm>Presence: [1..1]Definition: Date and time at which the range starts.Data Type: ISODateTime

6.1.1 ToDateTime <ToDtTm>Presence: [1..1]Definition: Date and time at which the range ends.Data Type: ISODateTime



7 Financial institution identification

7.1 BranchAndFinancialInstitutionIdentification3BranchAndFinancialInstitutionIdentification3 is used in message BankToCustomerAccountReportV01 p.6, p.10, p.13, p.14, p.14, p.14, p.14, p.14, p.14, p.14, p.14, p.14, p.14, message BankToCustomerDebitCreditNotificationV01 p.243, p.247, p.250, p.250, p.250, p.251, p.251, p.251, p.251, p.251, p.251, p.251, p.251, message BankToCustomerStatementV01 p.124, p.128, p.131, p.132, p.132, p.132, p.132, p.132, p.132, p.132, p.132, p.132, p.133, message CustomerCreditTransferInitiationV02 p.353, p.354, p.354, p.355, p.355, p.355, p.355, message PaymentStatusReportV02 p.403, p.403, p.403, p.403, p.403, p.405, p.405, p.405, p.405, p.405, p.406, p.406, p.407, p.407.

Definition: Unique and unambiguous identifier of a financial institution or a branch of a financial institution, as assigned under an internationally recognised or proprietary identification scheme.

Type: The following BranchAndFinancialInstitutionIdentification3 element(s) must be used:








7.1.6 Name <Nm> [1..1] Text


















SWIFTStandards MX



7.1.24 Name <Nm> [0..1] Text















7.1.39 Name <Nm> [0..1] Text










7.1.0 FinancialInstitutionIdentification <FinInstnId>Presence: [1..1]Definition: Unique and unambiguous identifier of a financial institution, as assigned under an internationally recognised

or proprietary identification scheme.Type: This message item is composed of one of the following FinancialInstitutionIdentification5Choice element(s):










7.1.1 BIC <BIC>Presence: [1..1]This message item is part of choice 7.1.0 FinancialInstitutionIdentification.Definition: Bank Identifier Code. Code allocated to financial institutions by the Registration Authority, under an




7.1.2 ClearingSystemMemberIdentification <ClrSysMmbId>Presence: [1..1]This message item is part of choice 7.1.0 FinancialInstitutionIdentification.Definition: Unique and unambiguous identifier of a clearing system member, as assigned by the system or system







minLength: 1

7.1.4 Proprietary <Prtry>Presence: [1..1]This message item is part of choice 7.1.2 ClearingSystemMemberIdentification.Definition: Identification Code for a clearing system, that has not yet been identified in the list of clearing systems.

SWIFTStandards MX



minLength: 1

7.1.5 NameAndAddress <NmAndAdr>Presence: [1..1]This message item is part of choice 7.1.0 FinancialInstitutionIdentification.Definition: Identifies the name and address of a financial institution. Type: This message item is composed of the following NameAndAddress7 element(s):


7.1.6 Name <Nm> [1..1] Text



minLength: 1






















minLength: 1


minLength: 1


minLength: 1



minLength: 1


minLength: 1

SWIFTStandards MX



minLength: 1



7.1.16 ProprietaryIdentification <PrtryId>Presence: [1..1]This message item is part of choice 7.1.0 FinancialInstitutionIdentification.Definition: Unique and unambiguous identifier, as assigned to a financial institution using a proprietary identification






minLength: 1


minLength: 1



7.1.19 CombinedIdentification <CmbndId>Presence: [1..1]This message item is part of choice 7.1.0 FinancialInstitutionIdentification.Definition: Unique and unambiguous identification of a financial institution, through a combimation of globally

recognised or proprietary identification scheme.Type: This message item is composed of the following FinancialInstitutionIdentification3 element(s):




7.1.24 Name <Nm> [0..1] Text







7.1.21 ClearingSystemMemberIdentification <ClrSysMmbId>Presence: [0..1]Definition: Unique and unambiguous identifier of a clearing system member, as assigned by the system or system





7.1.22 Identification <Id>Presence: [1..1]This message item is part of choice 7.1.21 ClearingSystemMemberIdentification.

SWIFTStandards MX


Definition: Identification for a clearing system member, identified in the list of clearing system member identifications published externally.

Data Type: ExternalClearingSystemMemberCodeFormat: maxLength: 35

minLength: 1


minLength: 1


minLength: 1






















minLength: 1


minLength: 1


minLength: 1



minLength: 1


minLength: 1

SWIFTStandards MX



minLength: 1



7.1.34 ProprietaryIdentification <PrtryId>Presence: [0..1]Definition: Unique and unambiguous identifier, as assigned to a financial institution using a proprietary identification






minLength: 1


minLength: 1

7.1.37 BranchIdentification <BrnchId>Presence: [0..1]



Definition: Information identifying a specific branch of a financial institution.

Usage : this component should be used in case the identification information in the financial institution component does not provide identification up to branch level.

Type: This message item is composed of the following BranchData element(s):



7.1.39 Name <Nm> [0..1] Text


7.1.38 Identification <Id>Presence: [0..1]Definition: Unique and unambiguous identification of a branch of a financial institution.Data Type: Max35TextFormat: maxLength: 35

minLength: 1


minLength: 1











SWIFTStandards MX











minLength: 1


minLength: 1


minLength: 1



minLength: 1




minLength: 1


minLength: 1



8 Miscellaneous

8.1 PaginationPagination is used in message BankToCustomerAccountReportV01 p.5, message BankToCustomerDebitCreditNotificationV01 p.243, message BankToCustomerStatementV01 p.124.

Definition: Number used to sequence pages when it is not possible for data to be conveyed in a single message and the data has to be split across several pages (messages).

Type: The following Pagination element(s) must be used:


8.1.0 PageNumber <PgNb> [1..1] Text

8.1.1 LastPageIndicator <LastPgInd> [1..1] Indicator

8.1.0 PageNumber <PgNb>Presence: [1..1]Definition: Page number.Data Type: Max5NumericTextFormat: [0-9]{1,5}

SWIFTStandards MX


8.1.1 LastPageIndicator <LastPgInd>Presence: [1..1]Definition: Indicates the last page.Data Type: One of the following YesNoIndicator values must be used:


9 Party identification

9.1 PartyIdentification8PartyIdentification8 is used in message BankToCustomerAccountReportV01 p.5, p.6, p.14, p.14, p.14, p.14, p.14, p.14, p.14, p.15, p.15, p.17, message BankToCustomerDebitCreditNotificationV01 p.243, p.243, p.250, p.250, p.250, p.250, p.250, p.250, p.250, p.252, p.252, p.253, message BankToCustomerStatementV01 p.124, p.124, p.132, p.132, p.132, p.132, p.132, p.132, p.132, p.133, p.134, p.135, message CustomerCreditTransferInitiationV02 p.353, p.354, p.354, p.355, p.355, p.355, p.357, p.357, message PaymentStatusReportV02 p.403, p.404, p.404, p.405, p.406, p.406, p.407, p.407, p.407, p.407, p.407, p.407.

Definition: Identification of a person, a financial institution or a non-financial institution.Type: The following PartyIdentification8 element(s) must be used:


9.1.0 Name <Nm> [0..1] Text










9.1.10 Identification <Id> [0..1]

9.1.11 {Or OrganisationIdentification <OrgId> [1..1]


9.1.13 IBEI <IBEI> [0..1] Identifier

9.1.14 BEI <BEI> [0..1] Identifier

9.1.15 EANGLN <EANGLN> [0..1] Identifier

9.1.16 CHIPSUniversalIdentification <USCHU> [0..1] Identifier

9.1.17 DUNS <DUNS> [0..1] Identifier

9.1.18 BankPartyIdentification <BkPtyId> [0..1] Text

9.1.19 TaxIdentificationNumber <TaxIdNb> [0..1] Text







9.1.23 Or} PrivateIdentification <PrvtId> [1..4]

9.1.24 {{Or DriversLicenseNumber <DrvrsLicNb> [1..1] Text

9.1.25 Or CustomerNumber <CstmrNb> [1..1] Text

9.1.26 Or SocialSecurityNumber <SclSctyNb> [1..1] Text

9.1.27 Or AlienRegistrationNumber <AlnRegnNb> [1..1] Text

9.1.28 Or PassportNumber <PsptNb> [1..1] Text

9.1.29 Or TaxIdentificationNumber <TaxIdNb> [1..1] Text

9.1.30 Or IdentityCardNumber <IdntyCardNb> [1..1] Text

9.1.31 Or EmployerIdentificationNumber <MplyrIdNb> [1..1] Text

9.1.32 Or DateAndPlaceOfBirth <DtAndPlcOfBirth> [1..1]

9.1.33 BirthDate <BirthDt> [1..1] DateTime

9.1.34 ProvinceOfBirth <PrvcOfBirth> [0..1] Text

9.1.35 CityOfBirth <CityOfBirth> [1..1] Text

9.1.36 CountryOfBirth <CtryOfBirth> [1..1] Code

9.1.37 Or}} OtherIdentification <OthrId> [1..1]


9.1.39 IdentificationType <IdTp> [1..1] Text


9.1.41 CountryOfResidence <CtryOfRes> [0..1] Code


minLength: 1




SWIFTStandards MX



















minLength: 1


minLength: 1

9.1.5 BuildingNumber <BldgNb>Presence: [0..1]Definition: Number that identifies the position of a building on a street.




minLength: 1



minLength: 1


minLength: 1


minLength: 1



9.1.10 Identification <Id>Presence: [0..1]Definition: Unique and unambiguous way of identifying an organisation or an individual person.Type: This message item is composed of one of the following Party2Choice element(s):


9.1.11 {Or OrganisationIdentification <OrgId> [1..1]

9.1.23 Or} PrivateIdentification <PrvtId> [1..4]

SWIFTStandards MX


9.1.11 OrganisationIdentification <OrgId>Presence: [1..1]This message item is part of choice 9.1.10 Identification.Definition: Unique and unambiguous way of identifying an organisation.Type: This message item is composed of the following OrganisationIdentification2 element(s):



9.1.13 IBEI <IBEI> [0..1] Identifier

9.1.14 BEI <BEI> [0..1] Identifier

9.1.15 EANGLN <EANGLN> [0..1] Identifier

9.1.16 CHIPSUniversalIdentification <USCHU> [0..1] Identifier

9.1.17 DUNS <DUNS> [0..1] Identifier

9.1.18 BankPartyIdentification <BkPtyId> [0..1] Text

9.1.19 TaxIdentificationNumber <TaxIdNb> [0..1] Text






9.1.13 IBEI <IBEI>Presence: [0..1]Definition: International Business Entity Identifier to uniquely identify business entities playing a role in the lifecycle

of and events related to a financial instrument. (tentative - to be confirmed)Data Type: IBEIIdentifierFormat: [A-Z]{2,2}[B-DF-HJ-NP-TV-XZ0-9]{7,7}[0-9]{1,1}

9.1.14 BEI <BEI>Presence: [0..1]Definition: Business Entity Identifier. Code allocated to non-financial institutions by the ISO 9362 Registration

Authority. The Business Entity Identifier (BEI) has the same format as the BIC code (8 up to 11 characters)



as stipulated in the standard ISO 9362 Banking (Banking Telecommunication Messages, Bank Identifier Codes, BIC).

Data Type: BEIIdentifierFormat: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}Rule(s): BEI

Only Business Entity Identifiers registered with the ISO 9362 Registration Authority and consisting of 8 or 11 contiguous characters comprising the first three or all four of the following components: BANK CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE, are valid BEIs.


9.1.15 EANGLN <EANGLN>Presence: [0..1]Definition: Global Location Number. A non-significant reference number used to identify legal entities, functional

entities, or physical entities according to the European Association for Numbering (EAN) numbering scheme rules.The number is used to retrieve detailed information that is linked to it.

Data Type: EANGLNIdentifierFormat: [0-9]{13,13}

9.1.16 CHIPSUniversalIdentification <USCHU>Presence: [0..1]Definition: (United States) Clearing House Interbank Payments System (CHIPS) Universal Identification (UID) -

identifies entities that own accounts at CHIPS participating financial institutions, through which CHIPS payments are effected. The CHIPS UID is assigned by the New York Clearing House.

Data Type: CHIPSUniversalIdentifierFormat: CH[0-9]{6,6}

9.1.17 DUNS <DUNS>Presence: [0..1]Definition: Data Universal Numbering System. A unique identification number provided by Dun & Bradstreet to identify

an organization.Data Type: DunsIdentifierFormat: [0-9]{9,9}

9.1.18 BankPartyIdentification <BkPtyId>Presence: [0..1]Definition: Unique and unambiguous assignment made by a specific bank to identify a relationship as defined between

the bank and its client.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.19 TaxIdentificationNumber <TaxIdNb>Presence: [0..1]Definition: Number assigned by a tax authority to an entity.Data Type: Max35Text

SWIFTStandards MX



9.1.20 ProprietaryIdentification <PrtryId>Presence: [0..1]Definition: Unique and unambiguous identifier for an organisation that is allocated by an institution.Type: This message item is composed of the following GenericIdentification3 element(s):





minLength: 1


minLength: 1

9.1.23 PrivateIdentification <PrvtId>Presence: [1..4]This message item is part of choice 9.1.10 Identification.Definition: Unique and unambiguous identification of a person, eg, passport.Type: This message item is composed of the following PersonIdentification3 element(s):


9.1.24 {Or DriversLicenseNumber <DrvrsLicNb> [1..1] Text

9.1.25 Or CustomerNumber <CstmrNb> [1..1] Text

9.1.26 Or SocialSecurityNumber <SclSctyNb> [1..1] Text

9.1.27 Or AlienRegistrationNumber <AlnRegnNb> [1..1] Text

9.1.28 Or PassportNumber <PsptNb> [1..1] Text

9.1.29 Or TaxIdentificationNumber <TaxIdNb> [1..1] Text

9.1.30 Or IdentityCardNumber <IdntyCardNb> [1..1] Text

9.1.31 Or EmployerIdentificationNumber <MplyrIdNb> [1..1] Text

9.1.32 Or DateAndPlaceOfBirth <DtAndPlcOfBirth> [1..1]




9.1.37 Or} OtherIdentification <OthrId> [1..1]


9.1.24 DriversLicenseNumber <DrvrsLicNb>Synonym(s): :95S::ALTE//DRLC (ISO 15022)Presence: [1..1]This message item is part of choice 9.1.23 PrivateIdentification.Definition: Number assigned by a license authority to a driver's license.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.25 CustomerNumber <CstmrNb>Presence: [1..1]This message item is part of choice 9.1.23 PrivateIdentification.Definition: Number assigned by an agent to identify its customer.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.26 SocialSecurityNumber <SclSctyNb>Synonym(s): :95S::ALTE//SSNX (ISO 15022)Presence: [1..1]This message item is part of choice 9.1.23 PrivateIdentification.Definition: Number assigned by a social security agency.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.27 AlienRegistrationNumber <AlnRegnNb>Synonym(s): :95S::ALTE//ARNU (ISO 15022)Presence: [1..1]This message item is part of choice 9.1.23 PrivateIdentification.Definition: Number assigned by a government agency to identify foreign nationals.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.28 PassportNumber <PsptNb>Synonym(s): :95S::ALTE//CCPT (ISO 15022)Presence: [1..1]This message item is part of choice 9.1.23 PrivateIdentification.

SWIFTStandards MX


Definition: Number assigned by a passport authority to a passport.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.29 TaxIdentificationNumber <TaxIdNb>Synonym(s): :95S::ALTE//TXID (ISO 15022)Presence: [1..1]This message item is part of choice 9.1.23 PrivateIdentification.Definition: Number assigned by a tax authority to an entity.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.30 IdentityCardNumber <IdntyCardNb>Presence: [1..1]This message item is part of choice 9.1.23 PrivateIdentification.Definition: Number assigned by a national authority to an identity card.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.31 EmployerIdentificationNumber <MplyrIdNb>Synonym(s): :95S::ALTE//EINX (ISO 15022)Presence: [1..1]This message item is part of choice 9.1.23 PrivateIdentification.Definition: Number assigned to an employer by a registration authority.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.32 DateAndPlaceOfBirth <DtAndPlcOfBirth>Presence: [1..1]This message item is part of choice 9.1.23 PrivateIdentification.Definition: Date and place of birth of a person.Type: This message item is composed of the following DateAndPlaceOfBirth element(s):


9.1.33 BirthDate <BirthDt> [1..1] DateTime

9.1.34 ProvinceOfBirth <PrvcOfBirth> [0..1] Text

9.1.35 CityOfBirth <CityOfBirth> [1..1] Text

9.1.36 CountryOfBirth <CtryOfBirth> [1..1] Code



9.1.33 BirthDate <BirthDt>Presence: [1..1]Definition: Date on which a person is born.Data Type: ISODate

9.1.34 ProvinceOfBirth <PrvcOfBirth>Presence: [0..1]Definition: Province where a person was born.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.35 CityOfBirth <CityOfBirth>Presence: [1..1]Definition: City where a person was born.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.36 CountryOfBirth <CtryOfBirth>Presence: [1..1]Definition: Country where a person was born.Data Type: CountryCodeFormat: [A-Z]{2,2}Rule(s): Country


9.1.37 OtherIdentification <OthrId>Presence: [1..1]This message item is part of choice 9.1.23 PrivateIdentification.Definition: Identifier issued to a person for which no specific identifier has been defined.Type: This message item is composed of the following GenericIdentification4 element(s):



9.1.39 IdentificationType <IdTp> [1..1] Text

9.1.38 Identification <Id>Presence: [1..1]Definition: Identifier issued to a person for which no specific identifier has been defined.Data Type: Max35Text

SWIFTStandards MX



9.1.39 IdentificationType <IdTp>Presence: [1..1]Definition: Specifies the nature of the identifier.

Usage: IdentificationType is used to specify what kind of identifier is used. It should be used in case the identifier is different from the identifiers listed in the pre-defined identifier list.


minLength: 1

9.1.40 Issuer <Issr>Presence: [0..1]Definition: Entity that assigns the identifier.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

9.1.41 CountryOfResidence <CtryOfRes>Presence: [0..1]Definition: Country in which a person resides (the place of a person's home). In the case of a company, it is the country

from which the affairs of that company are directed.Data Type: CountryCodeFormat: [A-Z]{2,2}Rule(s): Country


10 Postal address

10.1 PostalAddress1PostalAddress1 is used in message BankToCustomerAccountReportV01 p.15, message BankToCustomerDebitCreditNotificationV01 p.251, message BankToCustomerStatementV01 p.133, message CustomerCreditTransferInitiationV02 p.356.

Definition: Information that locates and identifies a specific address, as defined by postal services.Type: The following PostalAddress1 element(s) must be used:






















minLength: 1


minLength: 1


minLength: 1

SWIFTStandards MX




minLength: 1


minLength: 1


minLength: 1



11 Securities quantity

11.1 FinancialInstrumentQuantityChoiceFinancialInstrumentQuantityChoice is used in message BankToCustomerAccountReportV01 p.16, message BankToCustomerDebitCreditNotificationV01 p.252, message BankToCustomerStatementV01 p.134.

Definition: Choice between formats for the quantity of security.Type: One of the following FinancialInstrumentQuantityChoice element(s) must be used:


11.1.0 {Or Unit <Unit> [1..1] Quantity

11.1.1 Or FaceAmount <FaceAmt> [1..1] Amount

11.1.2 Or} AmortisedValue <AmtsdVal> [1..1] Amount



11.1.0 Unit <Unit>Synonym(s): UNIT (ISO 15022)Presence: [1..1]This message item is part of choice 11.1 FinancialInstrumentQuantityChoice.Definition: Quantity expressed as a number, eg, a number of shares.Data Type: DecimalNumberFormat: fractionDigits: 17

totalDigits: 18

11.1.1 FaceAmount <FaceAmt>Presence: [1..1]This message item is part of choice 11.1 FinancialInstrumentQuantityChoice.Definition: Quantity expressed as an amount representing the face amount, ie, the principal, of a debt instrument.Data Type: ImpliedCurrencyAndAmountFormat: fractionDigits: 5


11.1.2 AmortisedValue <AmtsdVal>Presence: [1..1]This message item is part of choice 11.1 FinancialInstrumentQuantityChoice.Definition: Quantity expressed as an amount representing the current amortised face amount of a bond, eg, a periodic

reduction of a bond's principal amount.Data Type: ImpliedCurrencyAndAmountFormat: fractionDigits: 5


12 Tax

12.1 TaxInformation2TaxInformation2 is used in message BankToCustomerAccountReportV01 p.16, message BankToCustomerDebitCreditNotificationV01 p.253, message BankToCustomerStatementV01 p.134, message CustomerCreditTransferInitiationV02 p.356.

Definition: Details about tax paid, or to be paid, to the government in accordance with the law, including pre-defined parameters such as thresholds and type of account.

Type: The following TaxInformation2 element(s) must be used:


12.1.0 CreditorTaxIdentification <CdtrTaxId> [0..1] Text

12.1.1 CreditorTaxType <CdtrTaxTp> [0..1] Text

12.1.2 DebtorTaxIdentification <DbtrTaxId> [0..1] Text

12.1.3 TaxReferenceNumber <TaxRefNb> [0..1] Text

SWIFTStandards MX



12.1.4 TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount

12.1.5 TotalTaxAmount <TtlTaxAmt> [0..1] Amount

12.1.6 TaxDate <TaxDt> [0..1] DateTime

12.1.7 TaxTypeInformation <TaxTpInf> [0..n]

12.1.8 CertificateIdentification <CertId> [0..1] Text

12.1.9 TaxType <TaxTp> [0..1]

12.1.10 CategoryDescription <CtgyDesc> [0..1] Text

12.1.11 Rate <Rate> [0..1] Rate

12.1.12 TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount

12.1.13 Amount <Amt> [0..1] Amount

12.1.0 CreditorTaxIdentification <CdtrTaxId>Presence: [0..1]Definition: Tax Identification Number of the creditor.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

12.1.1 CreditorTaxType <CdtrTaxTp>Presence: [0..1]Definition: Type of tax payer (creditor).Data Type: Max35TextFormat: maxLength: 35

minLength: 1

12.1.2 DebtorTaxIdentification <DbtrTaxId>Presence: [0..1]Definition: Tax Identification Number of the debtor.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

12.1.3 TaxReferenceNumber <TaxRefNb>Presence: [0..1]Definition: Tax reference information that is specific to a taxing agency.Data Type: Max140TextFormat: maxLength: 140

minLength: 1



12.1.4 TotalTaxableBaseAmount <TtlTaxblBaseAmt>Presence: [0..1]Definition: Total amount of money on which the tax is based.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



12.1.5 TotalTaxAmount <TtlTaxAmt>Presence: [0..1]Definition: Amount of money resulting from the calculation of the tax.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



12.1.6 TaxDate <TaxDt>Presence: [0..1]Definition: Date by which tax is due.Data Type: ISODate

12.1.7 TaxTypeInformation <TaxTpInf>Presence: [0..n]Definition: Set of characteristics defining the type of tax.Type: This message item is composed of the following TaxDetails element(s):


12.1.8 CertificateIdentification <CertId> [0..1] Text

12.1.9 TaxType <TaxTp> [0..1]

Rule(s): CertificateIdentificationAndOrTaxTypeRule If CertificateIdentification is not present, then TaxType is mandatory.If CertificateIdentification is present, then TaxType is optional.

SWIFTStandards MX


12.1.8 CertificateIdentification <CertId>Presence: [0..1]Definition: Document issued by first agent on behalf of debtor to report withholding tax to taxing authority.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

12.1.9 TaxType <TaxTp>Presence: [0..1]Definition: Information on the type of tax.Type: This message item is composed of the following TaxType element(s):


12.1.10 CategoryDescription <CtgyDesc> [0..1] Text

12.1.11 Rate <Rate> [0..1] Rate

12.1.12 TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount

12.1.13 Amount <Amt> [0..1] Amount

12.1.10 CategoryDescription <CtgyDesc>Presence: [0..1]Definition: Description of the tax that is being paid, including specific representation required by taxing authority.Data Type: Max35TextFormat: maxLength: 35

minLength: 1

12.1.11 Rate <Rate>Presence: [0..1]Definition: Rate used for calculation of the tax.Data Type: PercentageRateFormat: fractionDigits: 10

totalDigits: 11

12.1.12 TaxableBaseAmount <TaxblBaseAmt>Presence: [0..1]Definition: Amount of money on which the tax is based.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount





12.1.13 Amount <Amt>Presence: [0..1]Definition: Amount of money resulting from the calculation of the tax.Data Type: CurrencyAndAmountThis data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.Format: CurrencyAndAmount



SWIFTStandards MX


IndexesIndex of Message ItemsAAcceptanceDateTime: <AccptncDtTm>

Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252Message PaymentStatusReportV02 405

Account: <Acct>Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

AccountServicerReference: <AcctSvcrRef>Message BankToCustomerAccountReportV01 8, 11Message BankToCustomerStatementV01 126, 129Message BankToCustomerDebitCreditNotificationV01 244, 247

ActualDate: <ActlDt>Message BankToCustomerAccountReportV01 7, 8, 8, 13Message BankToCustomerStatementV01 125, 126, 126, 131Message BankToCustomerDebitCreditNotificationV01 244, 244, 249

AdditionalEntryInformation: <AddtlNtryInf>Message BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

AdditionalInformation: <AddtlInf>Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

AdditionalInformationIndicator: <AddtlInfInd>Message BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245

AdditionalNotificationInformation: <AddtlNtfctnInf>Message BankToCustomerDebitCreditNotificationV01 253

AdditionalRemittanceInformation: <AddtlRmtInf>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 357Message PaymentStatusReportV02 407

SCORE 2.0 Indexes


AdditionalReportInformation: <AddtlRptInf>Message BankToCustomerAccountReportV01 17

AdditionalReturnReasonInformation: <AddtlRtrRsnInf>Message BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

AdditionalStatementInformation: <AddtlStmtInf>Message BankToCustomerStatementV01 135

AdditionalStatusReasonInformation: <AddtlStsRsnInf>Message PaymentStatusReportV02 404, 405

AdditionalTransactionInformation: <AddtlTxInf>Message BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

Address: <Adr>500, 500Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

AddressLine: <AdrLine>487, 488, 488, 500, 500, 510, 511, 511, 523, 533

AddressType: <AdrTp>487, 487, 488, 500, 500, 510, 511, 511, 523, 533

Agent: <Agt>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251

AlienRegistrationNumber: <AlnRegnNb>524

AmendmentIndicator: <AmdmntInd>Message PaymentStatusReportV02 406

AmendmentInformationDetails: <AmdmntInfDtls>Message PaymentStatusReportV02 406

AmortisedValue: <AmtsdVal>535

Amount: <Amt>482, 537

SWIFTStandards MX


Message BankToCustomerAccountReportV01 7, 7, 7, 8, 8, 8, 9, 9, 9, 10, 10, 10, 10, 11, 11, 12, 12, 12, 12, 13, 13, 13, 13Message BankToCustomerStatementV01 125, 125, 125, 126, 126, 126, 127, 127, 127, 128, 128, 128, 129, 129, 129, 130, 130, 130, 130, 131, 131, 131, 131Message BankToCustomerDebitCreditNotificationV01 244, 244, 245, 245, 245, 246, 246, 246, 246, 247, 247, 248, 248, 248, 248, 249, 249, 249, 250, 250Message CustomerCreditTransferInitiationV02 355, 355, 356Message PaymentStatusReportV02 405, 405

AmountDetails: <AmtDtls>Message BankToCustomerAccountReportV01 9, 11Message BankToCustomerStatementV01 127, 129Message BankToCustomerDebitCreditNotificationV01 245, 248

AnnouncedPostingAmount: <AnncdPstngAmt>Message BankToCustomerAccountReportV01 10, 12Message BankToCustomerStatementV01 128, 130Message BankToCustomerDebitCreditNotificationV01 246, 248

Authorisation: <Authstn>Message CustomerCreditTransferInitiationV02 353

Authority: <Authrty>Message CustomerCreditTransferInitiationV02 355

AuthorityCountry: <AuthrtyCtry>Message CustomerCreditTransferInitiationV02 355

AuthorityName: <AuthrtyNm>Message CustomerCreditTransferInitiationV02 355

Availability: <Avlbty>Message BankToCustomerAccountReportV01 7, 8, 8, 13Message BankToCustomerStatementV01 125, 126, 126, 131Message BankToCustomerDebitCreditNotificationV01 244, 244, 249

BBalance: <Bal>

Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 125

BankPartyIdentification: <BkPtyId>523

BankTransactionCode: <BkTxCd>Message BankToCustomerAccountReportV01 7, 8, 13Message BankToCustomerStatementV01 125, 126, 131Message BankToCustomerDebitCreditNotificationV01 244, 245, 249

Batch: <Btch>Message BankToCustomerAccountReportV01 9

SCORE 2.0 Indexes


Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245

BatchBooking: <BtchBookg>Message CustomerCreditTransferInitiationV02 353

BBAN: <BBAN>477, 479

Bearer: <Br>Message BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 247, 250

BEI: <BEI>523

BIC: <BIC>487, 487, 510, 510, 523

BirthDate: <BirthDt>524

BookingDate: <BookgDt>Message BankToCustomerAccountReportV01 8Message BankToCustomerStatementV01 126Message BankToCustomerDebitCreditNotificationV01 244

BoundaryAmount: <BdryAmt>482, 482, 483, 483

BranchIdentification: <BrnchId>488, 511

BuildingNumber: <BldgNb>487, 488, 488, 500, 500, 510, 511, 511, 523, 533

CCategoryDescription: <CtgyDesc>

537

CategoryPurpose: <CtgyPurp>Message CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 406

CertificateIdentification: <CertId>537

ChargeBearer: <ChrgBr>Message CustomerCreditTransferInitiationV02 354, 355

SWIFTStandards MX


Charges: <Chrgs>Message BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 246, 249

ChargesAccount: <ChrgsAcct>Message CustomerCreditTransferInitiationV02 354

ChargesAccountAgent: <ChrgsAcctAgt>Message CustomerCreditTransferInitiationV02 354

ChargesAmount: <ChrgsAmt>487

ChargesInformation: <ChrgsInf>Message PaymentStatusReportV02 405

ChargesParty: <ChrgsPty>487

ChequeFrom: <ChqFr>500

ChequeInstruction: <ChqInstr>Message CustomerCreditTransferInitiationV02 355

ChequeMaturityDate: <ChqMtrtyDt>500

ChequeNumber: <ChqNb>500Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

ChequeType: <ChqTp>500

CHIPSUniversalIdentification: <USCHU>523

CityOfBirth: <CityOfBirth>524

ClearingChannel: <ClrChanl>Message CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 406

ClearingSystem: <ClrSys>Message PaymentStatusReportV02 405

ClearingSystemIdentification: <ClrSysId>

SCORE 2.0 Indexes


Message PaymentStatusReportV02 405

ClearingSystemMemberIdentification: <ClrSysMmbId>487, 487, 510, 510

ClearingSystemReference: <ClrSysRef>Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

Code: <Cd>479, 500Message BankToCustomerAccountReportV01 6, 6, 7, 7, 8, 8, 8, 8, 8, 10, 11, 13, 13, 13, 13, 14, 15, 15, 15, 16, 16, 17, 17, 17Message BankToCustomerStatementV01 124, 124, 125, 126, 126, 126, 126, 126, 127, 128, 129, 131, 131, 131, 131, 132, 133, 133, 133, 134, 135, 135, 135, 135Message BankToCustomerDebitCreditNotificationV01 243, 244, 244, 244, 245, 245, 245, 247, 247, 249, 249, 249, 249, 250, 251, 251, 252, 253, 253, 253, 253, 253Message CustomerCreditTransferInitiationV02 354, 354, 354, 354, 355, 355, 356, 356, 356Message PaymentStatusReportV02 404, 404, 405, 406, 406, 407

CombinedIdentification: <CmbndId>487, 510

CommissionWaiverIndicator: <ComssnWvrInd>Message BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245

ContractIdentification: <CtrctId>Message BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 13Message BankToCustomerStatementV01 127, 127, 128, 128, 128, 130, 130, 130, 130, 131Message BankToCustomerDebitCreditNotificationV01 245, 246, 246, 246, 246, 248, 248, 248, 249, 249Message CustomerCreditTransferInitiationV02 355

ControlSum: <CtrlSum>Message CustomerCreditTransferInitiationV02 353

CopyDuplicateIndicator: <CpyDplctInd>Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

CorporateAction: <CorpActn>Message BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

CounterValueAmount: <CntrValAmt>Message BankToCustomerAccountReportV01 9, 12Message BankToCustomerStatementV01 127, 130Message BankToCustomerDebitCreditNotificationV01 246, 248

SWIFTStandards MX


Country: <Ctry>487, 488, 488, 500, 500, 510, 511, 511, 523, 534

CountryOfBirth: <CtryOfBirth>524

CountryOfResidence: <CtryOfRes>524

CountrySubDivision: <CtrySubDvsn>487, 488, 488, 500, 500, 510, 511, 511, 523, 534

CreationDateTime: <CreDtTm>Message BankToCustomerAccountReportV01 5, 6Message BankToCustomerStatementV01 123, 124Message BankToCustomerDebitCreditNotificationV01 243, 243Message CustomerCreditTransferInitiationV02 353Message PaymentStatusReportV02 403

CreditDebitIndicator: <CdtDbtInd>483Message BankToCustomerAccountReportV01 7, 7, 7, 7, 8, 8, 8, 11, 13, 13Message BankToCustomerStatementV01 125, 125, 125, 125, 126, 126, 126, 129, 131, 132Message BankToCustomerDebitCreditNotificationV01 243, 244, 244, 244, 245, 247, 249, 250

CreditLine: <CdtLine>Message BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125

CreditNoteAmount: <CdtNoteAmt>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

Creditor: <Cdtr>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 407

CreditorAccount: <CdtrAcct>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 407

CreditorAgent: <CdtrAgt>

SCORE 2.0 Indexes


Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 403, 407

CreditorAgentAccount: <CdtrAgtAcct>Message CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 407

CreditorReference: <CdtrRef>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

CreditorReferenceInformation: <CdtrRefInf>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

CreditorReferenceType: <CdtrRefTp>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

CreditorSchemeIdentification: <CdtrSchmeId>Message PaymentStatusReportV02 405

CreditorTaxIdentification: <CdtrTaxId>536

CreditorTaxType: <CdtrTaxTp>536

CreditTransferTransactionInformation: <CdtTrfTxInf>Message CustomerCreditTransferInitiationV02 354

Currency: <Ccy>479, 483Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

CurrencyExchange: <CcyXchg>Message BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 127, 128, 128, 129, 130, 130, 130, 130

SWIFTStandards MX


Message BankToCustomerDebitCreditNotificationV01 245, 245, 246, 246, 246, 248, 248, 248, 248, 249

CurrencyOfTransfer: <CcyOfTrf>Message CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 405

CustomerNumber: <CstmrNb>524

DDate: <Dt>

509Message BankToCustomerAccountReportV01 7, 7, 8, 8, 13, 16Message BankToCustomerStatementV01 125, 125, 126, 126, 131, 134Message BankToCustomerDebitCreditNotificationV01 244, 244, 249, 252

DateAndPlaceOfBirth: <DtAndPlcOfBirth>524

DateOfSignature: <DtOfSgntr>Message PaymentStatusReportV02 406

DateTime: <DtTm>509Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

DealPrice: <DealPric>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

DebitCreditReportingIndicator: <DbtCdtRptgInd>Message CustomerCreditTransferInitiationV02 355

Debtor: <Dbtr>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 354Message PaymentStatusReportV02 407

DebtorAccount: <DbtrAcct>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 354Message PaymentStatusReportV02 407

DebtorAgent: <DbtrAgt>

SCORE 2.0 Indexes


Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 354Message PaymentStatusReportV02 403, 407

DebtorAgentAccount: <DbtrAgtAcct>Message CustomerCreditTransferInitiationV02 354Message PaymentStatusReportV02 407

DebtorTaxIdentification: <DbtrTaxId>536

DeliveringAgent: <DlvrgAgt>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 251

DeliverTo: <DlvrTo>500

DeliveryMethod: <DlvryMtd>500

DetailedControlSum: <DtldCtrlSum>Message PaymentStatusReportV02 404

DetailedNumberOfTransactions: <DtldNbOfTxs>Message PaymentStatusReportV02 404

DetailedStatus: <DtldSts>Message PaymentStatusReportV02 404

DiscountAppliedAmount: <DscntApldAmt>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

Domain: <Domn>Message BankToCustomerAccountReportV01 7, 8, 13, 16Message BankToCustomerStatementV01 126, 126, 131, 134Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 253

DriversLicenseNumber: <DrvrsLicNb>524

DuePayableAmount: <DuePyblAmt>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251

SWIFTStandards MX


Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

DUNS: <DUNS>523

EEANGLN: <EANGLN>

523

ElectronicSequenceNumber: <ElctrncSeqNb>Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

ElectronicSignature: <ElctrncSgntr>Message PaymentStatusReportV02 406

EmployerIdentificationNumber: <MplyrIdNb>524

EndDate: <EndDt>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

EndToEndIdentification: <EndToEndId>Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247Message CustomerCreditTransferInitiationV02 354

Entry: <Ntry>Message BankToCustomerAccountReportV01 8Message BankToCustomerStatementV01 126Message BankToCustomerDebitCreditNotificationV01 244

EqualAmount: <EQAmt>483

EquivalentAmount: <EqvtAmt>Message CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 405

ExchangeRate: <XchgRate>Message BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 128, 128, 128, 129, 130, 130, 130, 131Message BankToCustomerDebitCreditNotificationV01 245, 246, 246, 246, 246, 248, 248, 248, 249, 249Message CustomerCreditTransferInitiationV02 355

ExchangeRateInformation: <XchgRateInf>

SCORE 2.0 Indexes


Message CustomerCreditTransferInitiationV02 355

FFaceAmount: <FaceAmt>

535

Family: <Fmly>Message BankToCustomerAccountReportV01 8, 8, 13, 16Message BankToCustomerStatementV01 126, 126, 131, 134Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 253

FileOriginator: <FileOrgtr>Message PaymentStatusReportV02 404

FinalCollectionDate: <FnlColltnDt>Message PaymentStatusReportV02 406

FinancialInstitutionIdentification: <FinInstnId>487, 510

FinancialInstrumentIdentification: <FinInstrmId>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

FirstCollectionDate: <FrstColltnDt>Message PaymentStatusReportV02 406

FormsCode: <FrmsCd>501

ForwardingAgent: <FwdgAgt>Message CustomerCreditTransferInitiationV02 353Message PaymentStatusReportV02 403

Frequency: <Frqcy>Message PaymentStatusReportV02 406

FromAmount: <FrAmt>482, 483

FromDateTime: <FrDtTm>509

FromToAmount: <FrToAmt>482

FromToDate: <FrToDt>Message BankToCustomerAccountReportV01 6, 6, 11, 14Message BankToCustomerStatementV01 124, 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 243, 247, 250

SWIFTStandards MX


GGroupHeader: <GrpHdr>

Message BankToCustomerAccountReportV01 5Message BankToCustomerStatementV01 123Message BankToCustomerDebitCreditNotificationV01 242Message CustomerCreditTransferInitiationV02 353Message PaymentStatusReportV02 403

Grouping: <Grpg>Message CustomerCreditTransferInitiationV02 353

GroupStatus: <GrpSts>Message PaymentStatusReportV02 404

IIBAN: <IBAN>

477, 479

IBEI: <IBEI>523

Identification: <Id>477, 479, 479, 487, 487, 487, 488, 488, 510, 510, 510, 511, 511, 523, 524, 524Message BankToCustomerAccountReportV01 6, 6, 10, 13, 16Message BankToCustomerStatementV01 124, 124, 128, 131, 134Message BankToCustomerDebitCreditNotificationV01 243, 243, 247, 250, 253

IdentificationType: <IdTp>524

IdentityCardNumber: <IdntyCardNb>524

Included: <Incl>482, 482, 483, 483Message BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125

Information: <Inf>Message CustomerCreditTransferInitiationV02 356

InitiatingParty: <InitgPty>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 353Message PaymentStatusReportV02 403

SCORE 2.0 Indexes


InstructedAgent: <InstdAgt>Message PaymentStatusReportV02 403, 405

InstructedAmount: <InstdAmt>Message BankToCustomerAccountReportV01 9, 11Message BankToCustomerStatementV01 127, 129Message BankToCustomerDebitCreditNotificationV01 245, 248Message CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 405

InstructedReimbursementAgent: <InstdRmbrsmntAgt>Message PaymentStatusReportV02 405

InstructedReimbursementAgentAccount: <InstdRmbrsmntAgtAcct>Message PaymentStatusReportV02 405

InstructingAgent: <InstgAgt>Message PaymentStatusReportV02 403, 405

InstructingReimbursementAgent: <InstgRmbrsmntAgt>Message PaymentStatusReportV02 405

InstructingReimbursementAgentAccount: <InstgRmbrsmntAgtAcct>Message PaymentStatusReportV02 405

InstructionForCreditorAgent: <InstrForCdtrAgt>Message CustomerCreditTransferInitiationV02 355

InstructionForDebtorAgent: <InstrForDbtrAgt>Message CustomerCreditTransferInitiationV02 355

InstructionIdentification: <InstrId>Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247Message CustomerCreditTransferInitiationV02 354

InstructionInformation: <InstrInf>Message CustomerCreditTransferInitiationV02 355

InstructionPriority: <InstrPrty>500Message CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 405

InterbankSettlementAmount: <IntrBkSttlmAmt>Message PaymentStatusReportV02 405

InterbankSettlementDate: <IntrBkSttlmDt>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

SWIFTStandards MX



Interest: <Intrst>Message BankToCustomerAccountReportV01 6, 10, 13Message BankToCustomerStatementV01 124, 129, 131Message BankToCustomerDebitCreditNotificationV01 247, 250

IntermediaryAgent1: <IntrmyAgt1>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 355

IntermediaryAgent1Account: <IntrmyAgt1Acct>Message CustomerCreditTransferInitiationV02 355





Invoicee: <Invcee>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 357Message PaymentStatusReportV02 407

Invoicer: <Invcr>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 357Message PaymentStatusReportV02 407

ISIN: <ISIN>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

SCORE 2.0 Indexes


Issuer: <Issr>487, 488, 510, 511, 524, 524Message BankToCustomerAccountReportV01 8, 8, 13, 15, 15, 17Message BankToCustomerStatementV01 126, 127, 131, 133, 133, 135Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 251, 252, 253Message CustomerCreditTransferInitiationV02 356, 356Message PaymentStatusReportV02 406, 407

IssuingAgent: <IssgAgt>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 251

LLastPageIndicator: <LastPgInd>

522

LegalSequenceNumber: <LglSeqNb>Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

LocalInstrument: <LclInstrm>Message CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 406

MMandateIdentification: <MndtId>


MandateRelatedInformation: <MndtRltdInf>Message PaymentStatusReportV02 406

MemoField: <MemoFld>501

MessageIdentification: <MsgId>Message BankToCustomerAccountReportV01 5, 9, 9, 11Message BankToCustomerStatementV01 123, 127, 127, 129Message BankToCustomerDebitCreditNotificationV01 242, 245, 245, 247Message CustomerCreditTransferInitiationV02 353Message PaymentStatusReportV02 403

MessageNameIdentification: <MsgNmId>Message BankToCustomerAccountReportV01 9

SWIFTStandards MX



MessagePagination: <MsgPgntn>Message BankToCustomerAccountReportV01 5Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

MessageRecipient: <MsgRcpt>Message BankToCustomerAccountReportV01 5Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

NName: <Nm>

479, 487, 487, 488, 500, 500, 510, 511, 511, 523Message BankToCustomerAccountReportV01 6, 15Message BankToCustomerStatementV01 124, 133Message BankToCustomerDebitCreditNotificationV01 243, 251Message CustomerCreditTransferInitiationV02 356

NameAndAddress: <NmAndAdr>487, 510

NetworkFileName: <NtwkFileNm>Message PaymentStatusReportV02 404

NotEqualAmount: <NEQAmt>483

Notification: <Ntfctn>Message BankToCustomerDebitCreditNotificationV01 243

Number: <Nb>Message BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

NumberOfDays: <NbOfDays>Message BankToCustomerAccountReportV01 7, 8, 8, 13Message BankToCustomerStatementV01 125, 126, 126, 131Message BankToCustomerDebitCreditNotificationV01 244, 244, 249

NumberOfEntries: <NbOfNtries>Message BankToCustomerAccountReportV01 7, 7, 7, 7Message BankToCustomerStatementV01 125, 125, 125, 125Message BankToCustomerDebitCreditNotificationV01 243, 243, 244, 244

NumberOfTransactions: <NbOfTxs>Message BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127

SCORE 2.0 Indexes


Message BankToCustomerDebitCreditNotificationV01 245Message CustomerCreditTransferInitiationV02 353

NumberOfTransactionsPerStatus: <NbOfTxsPerSts>Message PaymentStatusReportV02 404

OOrganisationIdentification: <OrgId>

523

OriginalBankTransactionCode: <OrgnlBkTxCd>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 253

OriginalControlSum: <OrgnlCtrlSum>Message PaymentStatusReportV02 404

OriginalCreationDateTime: <OrgnlCreDtTm>Message PaymentStatusReportV02 404

OriginalCreditorAgent: <OrgnlCdtrAgt>Message PaymentStatusReportV02 406

OriginalCreditorAgentAccount: <OrgnlCdtrAgtAcct>Message PaymentStatusReportV02 406

OriginalCreditorSchemeIdentification: <OrgnlCdtrSchmeId>Message PaymentStatusReportV02 406

OriginalDebtor: <OrgnlDbtr>Message PaymentStatusReportV02 406

OriginalDebtorAccount: <OrgnlDbtrAcct>Message PaymentStatusReportV02 406

OriginalDebtorAgent: <OrgnlDbtrAgt>Message PaymentStatusReportV02 406

OriginalDebtorAgentAccount: <OrgnlDbtrAgtAcct>Message PaymentStatusReportV02 406

OriginalEndToEndIdentification: <OrgnlEndToEndId>Message PaymentStatusReportV02 404

OriginalFinalCollectionDate: <OrgnlFnlColltnDt>Message PaymentStatusReportV02 406

OriginalFrequency: <OrgnlFrqcy>Message PaymentStatusReportV02 406

SWIFTStandards MX


OriginalGroupInformationAndStatus: <OrgnlGrpInfAndSts>Message PaymentStatusReportV02 404

OriginalInstructionIdentification: <OrgnlInstrId>Message PaymentStatusReportV02 404

OriginalMandateIdentification: <OrgnlMndtId>Message PaymentStatusReportV02 406

OriginalMessageIdentification: <OrgnlMsgId>Message PaymentStatusReportV02 404

OriginalMessageNameIdentification: <OrgnlMsgNmId>Message PaymentStatusReportV02 404

OriginalNumberOfTransactions: <OrgnlNbOfTxs>Message PaymentStatusReportV02 404

OriginalPaymentInformationIdentification: <OrgnlPmtInfId>Message PaymentStatusReportV02 404

OriginalTransactionIdentification: <OrgnlTxId>Message PaymentStatusReportV02 404

OriginalTransactionReference: <OrgnlTxRef>Message PaymentStatusReportV02 405

OtherIdentification: <OthrId>524

Owner: <Ownr>Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

PPageNumber: <PgNb>

522

Party: <Pty>Message BankToCustomerAccountReportV01 10, 13, 14Message BankToCustomerStatementV01 128, 131, 132Message BankToCustomerDebitCreditNotificationV01 247, 250, 250

PassportNumber: <PsptNb>524

PaymentIdentification: <PmtId>Message CustomerCreditTransferInitiationV02 354

PaymentInformation: <PmtInf>

SCORE 2.0 Indexes



PaymentInformationIdentification: <PmtInfId>Message BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245Message CustomerCreditTransferInitiationV02 353

PaymentMethod: <PmtMtd>Message CustomerCreditTransferInitiationV02 354Message PaymentStatusReportV02 406

PaymentTypeInformation: <PmtTpInf>Message CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 405

PercentageRate: <PctgRate>Message BankToCustomerAccountReportV01 6, 11, 14Message BankToCustomerStatementV01 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 247, 250

PoolingAdjustmentDate: <PoolgAdjstmntDt>Message CustomerCreditTransferInitiationV02 354

PostalAddress: <PstlAdr>487, 487, 488, 510, 511, 511, 523

PostCode: <PstCd>487, 488, 488, 500, 500, 510, 511, 511, 523, 534

Price: <Pric>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

PrintLocation: <PrtLctn>501

PrivateIdentification: <PrvtId>524

Proprietary: <Prtry>479, 487, 487, 500, 510, 510Message BankToCustomerAccountReportV01 6, 6, 7, 8, 8, 11, 11, 13, 14, 14, 14, 15, 15, 15, 16, 16, 16, 16, 17, 17, 17Message BankToCustomerStatementV01 124, 124, 125, 126, 126, 129, 129, 131, 132, 132, 132, 133, 133, 133, 134, 134, 134, 134, 135, 135, 135Message BankToCustomerDebitCreditNotificationV01 243, 244, 245, 247, 247, 249, 250, 250, 251, 251, 251, 252, 252, 252, 252, 253, 253, 253, 253Message CustomerCreditTransferInitiationV02 354, 354, 354, 354, 355, 356, 356Message PaymentStatusReportV02 404, 404, 405, 405, 406, 406, 407

SWIFTStandards MX


ProprietaryAccount: <PrtryAcct>477, 479

ProprietaryAmount: <PrtryAmt>Message BankToCustomerAccountReportV01 10, 12Message BankToCustomerStatementV01 128, 130Message BankToCustomerDebitCreditNotificationV01 246, 249

ProprietaryCode: <PrtryCd>Message BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 247, 249

ProprietaryIdentification: <PrtryId>487, 488, 510, 511, 524

ProvinceOfBirth: <PrvcOfBirth>524

Purpose: <Purp>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 355

QQuantity: <Qty>

Message BankToCustomerAccountReportV01 16, 16Message BankToCustomerStatementV01 134, 134Message BankToCustomerDebitCreditNotificationV01 252, 252

QuotationDate: <QtnDt>Message BankToCustomerAccountReportV01 9, 9, 10, 10, 10, 11, 12, 12, 12, 13Message BankToCustomerStatementV01 127, 127, 128, 128, 128, 130, 130, 130, 130, 131Message BankToCustomerDebitCreditNotificationV01 245, 246, 246, 246, 246, 248, 248, 248, 249, 249

RRate: <Rate>

537Message BankToCustomerAccountReportV01 6, 6, 10, 10, 11, 11, 13, 13, 14, 14Message BankToCustomerStatementV01 124, 124, 128, 128, 129, 129, 131, 131, 132, 132Message BankToCustomerDebitCreditNotificationV01 247, 247, 247, 247, 250, 250, 250, 250

RateType: <RateTp>Message CustomerCreditTransferInitiationV02 355

Reason: <Rsn>Message BankToCustomerAccountReportV01 6, 11, 14Message BankToCustomerStatementV01 124, 129, 132

SCORE 2.0 Indexes


Message BankToCustomerDebitCreditNotificationV01 247, 250

ReceivingAgent: <RcvgAgt>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 251

Reference: <Ref>Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 248

References: <Refs>Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

ReferredDocumentAmount: <RfrdDocAmt>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

ReferredDocumentInformation: <RfrdDocInf>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

ReferredDocumentNumber: <RfrdDocNb>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

ReferredDocumentRelatedDate: <RfrdDocRltdDt>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

ReferredDocumentType: <RfrdDocTp>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

SWIFTStandards MX


RegionalClearingZone: <RgnlClrZone>501

RegulatoryDetails: <RgltryDtls>Message CustomerCreditTransferInitiationV02 356

RegulatoryReporting: <RgltryRptg>Message CustomerCreditTransferInitiationV02 355

RelatedAccount: <RltdAcct>Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

RelatedAgents: <RltdAgts>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250

RelatedDates: <RltdDts>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

RelatedParties: <RltdPties>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250

RelatedPrice: <RltdPric>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

RelatedQuantities: <RltdQties>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

RelatedRemittanceInformation: <RltdRmtInf>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

RemittanceIdentification: <RmtId>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

RemittanceInformation: <RmtInf>

SCORE 2.0 Indexes



RemittanceLocationElectronicAddress: <RmtLctnElctrncAdr>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

RemittanceLocationMethod: <RmtLctnMtd>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

RemittanceLocationPostalAddress: <RmtLctnPstlAdr>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

RemittedAmount: <RmtdAmt>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

Report: <Rpt>Message BankToCustomerAccountReportV01 6

RequestedCollectionDate: <ReqdColltnDt>Message PaymentStatusReportV02 405

RequestedExecutionDate: <ReqdExctnDt>Message CustomerCreditTransferInitiationV02 354Message PaymentStatusReportV02 405

ReturnInformation: <RtrInf>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 253

ReturnOriginator: <RtrOrgtr>Message BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

ReturnReason: <RtrRsn>

SWIFTStandards MX


Message BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

ReversalIndicator: <RvslInd>Message BankToCustomerAccountReportV01 8Message BankToCustomerStatementV01 126Message BankToCustomerDebitCreditNotificationV01 244

SSafekeepingAccount: <SfkpgAcct>


SequenceType: <SeqTp>Message PaymentStatusReportV02 406

ServiceLevel: <SvcLvl>Message CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 405

Servicer: <Svcr>Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

SettlementAccount: <SttlmAcct>Message PaymentStatusReportV02 405

SettlementInformation: <SttlmInf>Message PaymentStatusReportV02 405

SettlementMethod: <SttlmMtd>Message PaymentStatusReportV02 405

SettlementPlace: <SttlmPlc>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 251

SocialSecurityNumber: <SclSctyNb>524

SourceCurrency: <SrcCcy>Message BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 127, 128, 128, 129, 130, 130, 130, 130Message BankToCustomerDebitCreditNotificationV01 245, 245, 246, 246, 246, 248, 248, 248, 248, 249

StartDate: <StartDt>Message BankToCustomerAccountReportV01 16

SCORE 2.0 Indexes



Statement: <Stmt>Message BankToCustomerStatementV01 124

Status: <Sts>Message BankToCustomerAccountReportV01 8Message BankToCustomerStatementV01 126Message BankToCustomerDebitCreditNotificationV01 244

StatusIdentification: <StsId>Message PaymentStatusReportV02 404

StatusOriginator: <StsOrgtr>Message PaymentStatusReportV02 404, 404

StatusReason: <StsRsn>Message PaymentStatusReportV02 404, 404

StatusReasonInformation: <StsRsnInf>Message PaymentStatusReportV02 404, 404

StreetName: <StrtNm>487, 488, 488, 500, 500, 510, 511, 511, 523, 533

Structured: <Strd>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

SubFamilyCode: <SubFmlyCd>Message BankToCustomerAccountReportV01 8, 8, 13, 17Message BankToCustomerStatementV01 126, 126, 131, 135Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 253

Sum: <Sum>Message BankToCustomerAccountReportV01 7, 7, 7, 7Message BankToCustomerStatementV01 125, 125, 125, 125Message BankToCustomerDebitCreditNotificationV01 243, 243, 244, 244

TTargetCurrency: <TrgtCcy>

Message BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 127, 128, 128, 129, 130, 130, 130, 130Message BankToCustomerDebitCreditNotificationV01 245, 245, 246, 246, 246, 248, 248, 248, 248, 249

Tax: <Tax>Message BankToCustomerAccountReportV01 10, 13, 16

SWIFTStandards MX


Message BankToCustomerStatementV01 128, 131, 134Message BankToCustomerDebitCreditNotificationV01 247, 250, 253Message CustomerCreditTransferInitiationV02 356

TaxableBaseAmount: <TaxblBaseAmt>537

TaxAmount: <TaxAmt>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

TaxDate: <TaxDt>537

TaxIdentificationNumber: <TaxIdNb>523, 524

TaxReferenceNumber: <TaxRefNb>536

TaxType: <TaxTp>537

TaxTypeInformation: <TaxTpInf>537

TextualRate: <TxtlRate>Message BankToCustomerAccountReportV01 6, 11, 14Message BankToCustomerStatementV01 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 247, 250

ThirdReimbursementAgent: <ThrdRmbrsmntAgt>Message PaymentStatusReportV02 405

ThirdReimbursementAgentAccount: <ThrdRmbrsmntAgtAcct>Message PaymentStatusReportV02 405

ToAmount: <ToAmt>482, 483

ToDateTime: <ToDtTm>509

TotalChargesAndTaxAmount: <TtlChrgsAndTaxAmt>Message BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 246, 249

TotalCreditEntries: <TtlCdtNtries>

SCORE 2.0 Indexes



TotalDebitEntries: <TtlDbtNtries>Message BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125Message BankToCustomerDebitCreditNotificationV01 243

TotalEntries: <TtlNtries>Message BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125Message BankToCustomerDebitCreditNotificationV01 243

TotalEntriesPerBankTransactionCode: <TtlNtriesPerBkTxCd>Message BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125Message BankToCustomerDebitCreditNotificationV01 244

TotalNetEntryAmount: <TtlNetNtryAmt>Message BankToCustomerAccountReportV01 7, 7Message BankToCustomerStatementV01 125, 125Message BankToCustomerDebitCreditNotificationV01 243, 244

TotalTaxableBaseAmount: <TtlTaxblBaseAmt>537

TotalTaxAmount: <TtlTaxAmt>537

TownName: <TwnNm>487, 488, 488, 500, 500, 510, 511, 511, 523, 534

TradeDate: <TradDt>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

TradingParty: <TradgPty>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250

TransactionAmount: <TxAmt>Message BankToCustomerAccountReportV01 9, 12Message BankToCustomerStatementV01 127, 130Message BankToCustomerDebitCreditNotificationV01 245, 248

TransactionDateTime: <TxDtTm>Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

SWIFTStandards MX


TransactionDetails: <TxDtls>Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

TransactionIdentification: <TxId>Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

TransactionInformationAndStatus: <TxInfAndSts>Message PaymentStatusReportV02 404

TransactionsSummary: <TxsSummry>Message BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125Message BankToCustomerDebitCreditNotificationV01 243

TransactionStatus: <TxSts>Message PaymentStatusReportV02 404

Type: <Tp>479Message BankToCustomerAccountReportV01 6, 6, 6, 10, 10, 11, 11, 12, 13, 13, 14, 14, 16, 16, 16, 16Message BankToCustomerStatementV01 124, 124, 125, 128, 128, 129, 129, 130, 131, 132, 132, 132, 134, 134, 134, 134Message BankToCustomerDebitCreditNotificationV01 243, 246, 247, 247, 247, 249, 249, 250, 250, 251, 252, 252, 252, 253

UUltimateCreditor: <UltmtCdtr>


UltimateDebtor: <UltmtDbtr>Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 354, 355Message PaymentStatusReportV02 407

Unit: <Unit>535

UnitCurrency: <UnitCcy>Message BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 127, 128, 128, 129, 130, 130, 130, 131

SCORE 2.0 Indexes


Message BankToCustomerDebitCreditNotificationV01 245, 245, 246, 246, 246, 248, 248, 248, 248, 249

Unstructured: <Ustrd>Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

UPIC: <UPIC>477, 479

VValidityRange: <VldtyRg>

Message BankToCustomerAccountReportV01 6, 11, 14Message BankToCustomerStatementV01 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 247, 250

ValueDate: <ValDt>Message BankToCustomerAccountReportV01 8Message BankToCustomerStatementV01 126Message BankToCustomerDebitCreditNotificationV01 244

Index of XML tagsA<AccptncDtTm>: AcceptanceDateTime


<Acct>: AccountMessage BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

<AcctSvcrRef>: AccountServicerReferenceMessage BankToCustomerAccountReportV01 8, 11Message BankToCustomerStatementV01 126, 129Message BankToCustomerDebitCreditNotificationV01 244, 247

<ActlDt>: ActualDateMessage BankToCustomerAccountReportV01 7, 8, 8, 13Message BankToCustomerStatementV01 125, 126, 126, 131Message BankToCustomerDebitCreditNotificationV01 244, 244, 249

<AddtlInf>: AdditionalInformationMessage BankToCustomerAccountReportV01 6

SWIFTStandards MX



<AddtlInfInd>: AdditionalInformationIndicatorMessage BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245

<AddtlNtfctnInf>: AdditionalNotificationInformationMessage BankToCustomerDebitCreditNotificationV01 253

<AddtlNtryInf>: AdditionalEntryInformationMessage BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

<AddtlRmtInf>: AdditionalRemittanceInformationMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 357Message PaymentStatusReportV02 407

<AddtlRptInf>: AdditionalReportInformationMessage BankToCustomerAccountReportV01 17

<AddtlRtrRsnInf>: AdditionalReturnReasonInformationMessage BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

<AddtlStmtInf>: AdditionalStatementInformationMessage BankToCustomerStatementV01 135

<AddtlStsRsnInf>: AdditionalStatusReasonInformationMessage PaymentStatusReportV02 404, 405

<AddtlTxInf>: AdditionalTransactionInformationMessage BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

<Adr>: Address500, 500Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

<AdrLine>: AddressLine487, 488, 488, 500, 500, 510, 511, 511, 523, 533

SCORE 2.0 Indexes


<AdrTp>: AddressType487, 487, 488, 500, 500, 510, 511, 511, 523, 533

<Agt>: AgentMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251

<AlnRegnNb>: AlienRegistrationNumber524

<AmdmntInd>: AmendmentIndicatorMessage PaymentStatusReportV02 406

<AmdmntInfDtls>: AmendmentInformationDetailsMessage PaymentStatusReportV02 406

<Amt>: Amount482, 537Message BankToCustomerAccountReportV01 7, 7, 7, 8, 8, 8, 9, 9, 9, 10, 10, 10, 10, 11, 11, 12, 12, 12, 12, 13, 13, 13, 13Message BankToCustomerStatementV01 125, 125, 125, 126, 126, 126, 127, 127, 127, 128, 128, 128, 129, 129, 129, 130, 130, 130, 130, 131, 131, 131, 131Message BankToCustomerDebitCreditNotificationV01 244, 244, 245, 245, 245, 246, 246, 246, 246, 247, 247, 248, 248, 248, 248, 249, 249, 249, 250, 250Message CustomerCreditTransferInitiationV02 355, 355, 356Message PaymentStatusReportV02 405, 405

<AmtDtls>: AmountDetailsMessage BankToCustomerAccountReportV01 9, 11Message BankToCustomerStatementV01 127, 129Message BankToCustomerDebitCreditNotificationV01 245, 248

<AmtsdVal>: AmortisedValue535

<AnncdPstngAmt>: AnnouncedPostingAmountMessage BankToCustomerAccountReportV01 10, 12Message BankToCustomerStatementV01 128, 130Message BankToCustomerDebitCreditNotificationV01 246, 248

<Authrty>: AuthorityMessage CustomerCreditTransferInitiationV02 355

<AuthrtyCtry>: AuthorityCountryMessage CustomerCreditTransferInitiationV02 355

<AuthrtyNm>: AuthorityNameMessage CustomerCreditTransferInitiationV02 355

<Authstn>: AuthorisationMessage CustomerCreditTransferInitiationV02 353

SWIFTStandards MX


<Avlbty>: AvailabilityMessage BankToCustomerAccountReportV01 7, 8, 8, 13Message BankToCustomerStatementV01 125, 126, 126, 131Message BankToCustomerDebitCreditNotificationV01 244, 244, 249

B<Bal>: Balance


<BBAN>: BBAN477, 479

<BdryAmt>: BoundaryAmount482, 482, 483, 483

<BEI>: BEI523

<BIC>: BIC487, 487, 510, 510, 523

<BirthDt>: BirthDate524

<BkPtyId>: BankPartyIdentification523

<BkTxCd>: BankTransactionCodeMessage BankToCustomerAccountReportV01 7, 8, 13Message BankToCustomerStatementV01 125, 126, 131Message BankToCustomerDebitCreditNotificationV01 244, 245, 249

<BldgNb>: BuildingNumber487, 488, 488, 500, 500, 510, 511, 511, 523, 533

<BookgDt>: BookingDateMessage BankToCustomerAccountReportV01 8Message BankToCustomerStatementV01 126Message BankToCustomerDebitCreditNotificationV01 244

<Br>: BearerMessage BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 247, 250

<BrnchId>: BranchIdentification488, 511

<Btch>: Batch

SCORE 2.0 Indexes



<BtchBookg>: BatchBookingMessage CustomerCreditTransferInitiationV02 353

C<Ccy>: Currency

479, 483Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

<CcyOfTrf>: CurrencyOfTransferMessage CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 405

<CcyXchg>: CurrencyExchangeMessage BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 127, 128, 128, 129, 130, 130, 130, 130Message BankToCustomerDebitCreditNotificationV01 245, 245, 246, 246, 246, 248, 248, 248, 248, 249

<Cd>: Code479, 500Message BankToCustomerAccountReportV01 6, 6, 7, 7, 8, 8, 8, 8, 8, 10, 11, 13, 13, 13, 13, 14, 15, 15, 15, 16, 16, 17, 17, 17Message BankToCustomerStatementV01 124, 124, 125, 126, 126, 126, 126, 126, 127, 128, 129, 131, 131, 131, 131, 132, 133, 133, 133, 134, 135, 135, 135, 135Message BankToCustomerDebitCreditNotificationV01 243, 244, 244, 244, 245, 245, 245, 247, 247, 249, 249, 249, 249, 250, 251, 251, 252, 253, 253, 253, 253, 253Message CustomerCreditTransferInitiationV02 354, 354, 354, 354, 355, 355, 356, 356, 356Message PaymentStatusReportV02 404, 404, 405, 406, 406, 407

<CdtDbtInd>: CreditDebitIndicator483Message BankToCustomerAccountReportV01 7, 7, 7, 7, 8, 8, 8, 11, 13, 13Message BankToCustomerStatementV01 125, 125, 125, 125, 126, 126, 126, 129, 131, 132Message BankToCustomerDebitCreditNotificationV01 243, 244, 244, 244, 245, 247, 249, 250

<CdtLine>: CreditLineMessage BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125

<CdtNoteAmt>: CreditNoteAmountMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

SWIFTStandards MX


<Cdtr>: CreditorMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 407

<CdtrAcct>: CreditorAccountMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 407

<CdtrAgt>: CreditorAgentMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 403, 407

<CdtrAgtAcct>: CreditorAgentAccountMessage CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 407

<CdtrRef>: CreditorReferenceMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

<CdtrRefInf>: CreditorReferenceInformationMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

<CdtrRefTp>: CreditorReferenceTypeMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

<CdtrSchmeId>: CreditorSchemeIdentificationMessage PaymentStatusReportV02 405

<CdtrTaxId>: CreditorTaxIdentification536

SCORE 2.0 Indexes


<CdtrTaxTp>: CreditorTaxType536

<CdtTrfTxInf>: CreditTransferTransactionInformationMessage CustomerCreditTransferInitiationV02 354

<CertId>: CertificateIdentification537

<ChqFr>: ChequeFrom500

<ChqInstr>: ChequeInstructionMessage CustomerCreditTransferInitiationV02 355

<ChqMtrtyDt>: ChequeMaturityDate500

<ChqNb>: ChequeNumber500Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

<ChqTp>: ChequeType500

<ChrgBr>: ChargeBearerMessage CustomerCreditTransferInitiationV02 354, 355

<Chrgs>: ChargesMessage BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 246, 249

<ChrgsAcct>: ChargesAccountMessage CustomerCreditTransferInitiationV02 354

<ChrgsAcctAgt>: ChargesAccountAgentMessage CustomerCreditTransferInitiationV02 354

<ChrgsAmt>: ChargesAmount487

<ChrgsInf>: ChargesInformationMessage PaymentStatusReportV02 405

<ChrgsPty>: ChargesParty487

<CityOfBirth>: CityOfBirth524

SWIFTStandards MX


<ClrChanl>: ClearingChannelMessage CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 406

<ClrSys>: ClearingSystemMessage PaymentStatusReportV02 405

<ClrSysId>: ClearingSystemIdentificationMessage PaymentStatusReportV02 405

<ClrSysMmbId>: ClearingSystemMemberIdentification487, 487, 510, 510

<ClrSysRef>: ClearingSystemReferenceMessage BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

<CmbndId>: CombinedIdentification487, 510

<CntrValAmt>: CounterValueAmountMessage BankToCustomerAccountReportV01 9, 12Message BankToCustomerStatementV01 127, 130Message BankToCustomerDebitCreditNotificationV01 246, 248

<ComssnWvrInd>: CommissionWaiverIndicatorMessage BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245

<CorpActn>: CorporateActionMessage BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

<CpyDplctInd>: CopyDuplicateIndicatorMessage BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

<CreDtTm>: CreationDateTimeMessage BankToCustomerAccountReportV01 5, 6Message BankToCustomerStatementV01 123, 124Message BankToCustomerDebitCreditNotificationV01 243, 243Message CustomerCreditTransferInitiationV02 353Message PaymentStatusReportV02 403

<CstmrNb>: CustomerNumber524

SCORE 2.0 Indexes


<CtgyDesc>: CategoryDescription537

<CtgyPurp>: CategoryPurposeMessage CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 406

<CtrctId>: ContractIdentificationMessage BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 13Message BankToCustomerStatementV01 127, 127, 128, 128, 128, 130, 130, 130, 130, 131Message BankToCustomerDebitCreditNotificationV01 245, 246, 246, 246, 246, 248, 248, 248, 249, 249Message CustomerCreditTransferInitiationV02 355

<CtrlSum>: ControlSumMessage CustomerCreditTransferInitiationV02 353

<Ctry>: Country487, 488, 488, 500, 500, 510, 511, 511, 523, 534

<CtryOfBirth>: CountryOfBirth524

<CtryOfRes>: CountryOfResidence524

<CtrySubDvsn>: CountrySubDivision487, 488, 488, 500, 500, 510, 511, 511, 523, 534

D<DbtCdtRptgInd>: DebitCreditReportingIndicator


<Dbtr>: DebtorMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 354Message PaymentStatusReportV02 407

<DbtrAcct>: DebtorAccountMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 354Message PaymentStatusReportV02 407

<DbtrAgt>: DebtorAgentMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 354

SWIFTStandards MX


Message PaymentStatusReportV02 403, 407

<DbtrAgtAcct>: DebtorAgentAccountMessage CustomerCreditTransferInitiationV02 354Message PaymentStatusReportV02 407

<DbtrTaxId>: DebtorTaxIdentification536

<DealPric>: DealPriceMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

<DlvrgAgt>: DeliveringAgentMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 251

<DlvrTo>: DeliverTo500

<DlvryMtd>: DeliveryMethod500

<Domn>: DomainMessage BankToCustomerAccountReportV01 7, 8, 13, 16Message BankToCustomerStatementV01 126, 126, 131, 134Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 253

<DrvrsLicNb>: DriversLicenseNumber524

<DscntApldAmt>: DiscountAppliedAmountMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

<Dt>: Date509Message BankToCustomerAccountReportV01 7, 7, 8, 8, 13, 16Message BankToCustomerStatementV01 125, 125, 126, 126, 131, 134Message BankToCustomerDebitCreditNotificationV01 244, 244, 249, 252

<DtAndPlcOfBirth>: DateAndPlaceOfBirth524

<DtldCtrlSum>: DetailedControlSumMessage PaymentStatusReportV02 404

SCORE 2.0 Indexes


<DtldNbOfTxs>: DetailedNumberOfTransactionsMessage PaymentStatusReportV02 404

<DtldSts>: DetailedStatusMessage PaymentStatusReportV02 404

<DtOfSgntr>: DateOfSignatureMessage PaymentStatusReportV02 406

<DtTm>: DateTime509Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

<DuePyblAmt>: DuePayableAmountMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

<DUNS>: DUNS523

E<EANGLN>: EANGLN

523

<ElctrncSeqNb>: ElectronicSequenceNumberMessage BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

<ElctrncSgntr>: ElectronicSignatureMessage PaymentStatusReportV02 406

<EndDt>: EndDateMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

<EndToEndId>: EndToEndIdentificationMessage BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247Message CustomerCreditTransferInitiationV02 354

<EQAmt>: EqualAmount483

SWIFTStandards MX


<EqvtAmt>: EquivalentAmountMessage CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 405

F<FaceAmt>: FaceAmount

535

<FileOrgtr>: FileOriginatorMessage PaymentStatusReportV02 404

<FinInstnId>: FinancialInstitutionIdentification487, 510

<FinInstrmId>: FinancialInstrumentIdentificationMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

<Fmly>: FamilyMessage BankToCustomerAccountReportV01 8, 8, 13, 16Message BankToCustomerStatementV01 126, 126, 131, 134Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 253

<FnlColltnDt>: FinalCollectionDateMessage PaymentStatusReportV02 406

<FrAmt>: FromAmount482, 483

<FrDtTm>: FromDateTime509

<FrmsCd>: FormsCode501

<Frqcy>: FrequencyMessage PaymentStatusReportV02 406

<FrstColltnDt>: FirstCollectionDateMessage PaymentStatusReportV02 406

<FrToAmt>: FromToAmount482

<FrToDt>: FromToDateMessage BankToCustomerAccountReportV01 6, 6, 11, 14Message BankToCustomerStatementV01 124, 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 243, 247, 250

<FwdgAgt>: ForwardingAgent

SCORE 2.0 Indexes



G<Grpg>: Grouping


<GrpHdr>: GroupHeaderMessage BankToCustomerAccountReportV01 5Message BankToCustomerStatementV01 123Message BankToCustomerDebitCreditNotificationV01 242Message CustomerCreditTransferInitiationV02 353Message PaymentStatusReportV02 403

<GrpSts>: GroupStatusMessage PaymentStatusReportV02 404

I<IBAN>: IBAN

477, 479

<IBEI>: IBEI523

<Id>: Identification477, 479, 479, 487, 487, 487, 488, 488, 510, 510, 510, 511, 511, 523, 524, 524Message BankToCustomerAccountReportV01 6, 6, 10, 13, 16Message BankToCustomerStatementV01 124, 124, 128, 131, 134Message BankToCustomerDebitCreditNotificationV01 243, 243, 247, 250, 253

<IdntyCardNb>: IdentityCardNumber524

<IdTp>: IdentificationType524

<Incl>: Included482, 482, 483, 483Message BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125

<Inf>: InformationMessage CustomerCreditTransferInitiationV02 356

<InitgPty>: InitiatingPartyMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 353

SWIFTStandards MX



<InstdAgt>: InstructedAgentMessage PaymentStatusReportV02 403, 405

<InstdAmt>: InstructedAmountMessage BankToCustomerAccountReportV01 9, 11Message BankToCustomerStatementV01 127, 129Message BankToCustomerDebitCreditNotificationV01 245, 248Message CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 405

<InstdRmbrsmntAgt>: InstructedReimbursementAgentMessage PaymentStatusReportV02 405

<InstdRmbrsmntAgtAcct>: InstructedReimbursementAgentAccountMessage PaymentStatusReportV02 405

<InstgAgt>: InstructingAgentMessage PaymentStatusReportV02 403, 405

<InstgRmbrsmntAgt>: InstructingReimbursementAgentMessage PaymentStatusReportV02 405

<InstgRmbrsmntAgtAcct>: InstructingReimbursementAgentAccountMessage PaymentStatusReportV02 405

<InstrForCdtrAgt>: InstructionForCreditorAgentMessage CustomerCreditTransferInitiationV02 355

<InstrForDbtrAgt>: InstructionForDebtorAgentMessage CustomerCreditTransferInitiationV02 355

<InstrId>: InstructionIdentificationMessage BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247Message CustomerCreditTransferInitiationV02 354

<InstrInf>: InstructionInformationMessage CustomerCreditTransferInitiationV02 355

<InstrPrty>: InstructionPriority500Message CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 405

<IntrBkSttlmAmt>: InterbankSettlementAmountMessage PaymentStatusReportV02 405

<IntrBkSttlmDt>: InterbankSettlementDateMessage BankToCustomerAccountReportV01 16

SCORE 2.0 Indexes


Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252Message PaymentStatusReportV02 405

<IntrmyAgt1>: IntermediaryAgent1Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 355

<IntrmyAgt1Acct>: IntermediaryAgent1AccountMessage CustomerCreditTransferInitiationV02 355





<Intrst>: InterestMessage BankToCustomerAccountReportV01 6, 10, 13Message BankToCustomerStatementV01 124, 129, 131Message BankToCustomerDebitCreditNotificationV01 247, 250

<Invcee>: InvoiceeMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 357Message PaymentStatusReportV02 407

<Invcr>: InvoicerMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 357Message PaymentStatusReportV02 407

<ISIN>: ISINMessage BankToCustomerAccountReportV01 16

SWIFTStandards MX



<IssgAgt>: IssuingAgentMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 251

<Issr>: Issuer487, 488, 510, 511, 524, 524Message BankToCustomerAccountReportV01 8, 8, 13, 15, 15, 17Message BankToCustomerStatementV01 126, 127, 131, 133, 133, 135Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 251, 252, 253Message CustomerCreditTransferInitiationV02 356, 356Message PaymentStatusReportV02 406, 407

L<LastPgInd>: LastPageIndicator

522

<LclInstrm>: LocalInstrumentMessage CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 406

<LglSeqNb>: LegalSequenceNumberMessage BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

M<MemoFld>: MemoField

501

<MndtId>: MandateIdentificationMessage BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247Message PaymentStatusReportV02 406

<MndtRltdInf>: MandateRelatedInformationMessage PaymentStatusReportV02 406

<MplyrIdNb>: EmployerIdentificationNumber524

<MsgId>: MessageIdentificationMessage BankToCustomerAccountReportV01 5, 9, 9, 11Message BankToCustomerStatementV01 123, 127, 127, 129Message BankToCustomerDebitCreditNotificationV01 242, 245, 245, 247

SCORE 2.0 Indexes



<MsgNmId>: MessageNameIdentificationMessage BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245

<MsgPgntn>: MessagePaginationMessage BankToCustomerAccountReportV01 5Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

<MsgRcpt>: MessageRecipientMessage BankToCustomerAccountReportV01 5Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

N<Nb>: Number


<NbOfDays>: NumberOfDaysMessage BankToCustomerAccountReportV01 7, 8, 8, 13Message BankToCustomerStatementV01 125, 126, 126, 131Message BankToCustomerDebitCreditNotificationV01 244, 244, 249

<NbOfNtries>: NumberOfEntriesMessage BankToCustomerAccountReportV01 7, 7, 7, 7Message BankToCustomerStatementV01 125, 125, 125, 125Message BankToCustomerDebitCreditNotificationV01 243, 243, 244, 244

<NbOfTxs>: NumberOfTransactionsMessage BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245Message CustomerCreditTransferInitiationV02 353

<NbOfTxsPerSts>: NumberOfTransactionsPerStatusMessage PaymentStatusReportV02 404

<NEQAmt>: NotEqualAmount483

<Nm>: Name479, 487, 487, 488, 500, 500, 510, 511, 511, 523Message BankToCustomerAccountReportV01 6, 15Message BankToCustomerStatementV01 124, 133Message BankToCustomerDebitCreditNotificationV01 243, 251

SWIFTStandards MX



<NmAndAdr>: NameAndAddress487, 510

<Ntfctn>: NotificationMessage BankToCustomerDebitCreditNotificationV01 243

<Ntry>: EntryMessage BankToCustomerAccountReportV01 8Message BankToCustomerStatementV01 126Message BankToCustomerDebitCreditNotificationV01 244

<NtwkFileNm>: NetworkFileNameMessage PaymentStatusReportV02 404

O<OrgId>: OrganisationIdentification

523

<OrgnlBkTxCd>: OriginalBankTransactionCodeMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 253

<OrgnlCdtrAgt>: OriginalCreditorAgentMessage PaymentStatusReportV02 406

<OrgnlCdtrAgtAcct>: OriginalCreditorAgentAccountMessage PaymentStatusReportV02 406

<OrgnlCdtrSchmeId>: OriginalCreditorSchemeIdentificationMessage PaymentStatusReportV02 406

<OrgnlCreDtTm>: OriginalCreationDateTimeMessage PaymentStatusReportV02 404

<OrgnlCtrlSum>: OriginalControlSumMessage PaymentStatusReportV02 404

<OrgnlDbtr>: OriginalDebtorMessage PaymentStatusReportV02 406

<OrgnlDbtrAcct>: OriginalDebtorAccountMessage PaymentStatusReportV02 406

<OrgnlDbtrAgt>: OriginalDebtorAgentMessage PaymentStatusReportV02 406

<OrgnlDbtrAgtAcct>: OriginalDebtorAgentAccountMessage PaymentStatusReportV02 406

SCORE 2.0 Indexes


<OrgnlEndToEndId>: OriginalEndToEndIdentificationMessage PaymentStatusReportV02 404

<OrgnlFnlColltnDt>: OriginalFinalCollectionDateMessage PaymentStatusReportV02 406

<OrgnlFrqcy>: OriginalFrequencyMessage PaymentStatusReportV02 406

<OrgnlGrpInfAndSts>: OriginalGroupInformationAndStatusMessage PaymentStatusReportV02 404

<OrgnlInstrId>: OriginalInstructionIdentificationMessage PaymentStatusReportV02 404

<OrgnlMndtId>: OriginalMandateIdentificationMessage PaymentStatusReportV02 406

<OrgnlMsgId>: OriginalMessageIdentificationMessage PaymentStatusReportV02 404

<OrgnlMsgNmId>: OriginalMessageNameIdentificationMessage PaymentStatusReportV02 404

<OrgnlNbOfTxs>: OriginalNumberOfTransactionsMessage PaymentStatusReportV02 404

<OrgnlPmtInfId>: OriginalPaymentInformationIdentificationMessage PaymentStatusReportV02 404

<OrgnlTxId>: OriginalTransactionIdentificationMessage PaymentStatusReportV02 404

<OrgnlTxRef>: OriginalTransactionReferenceMessage PaymentStatusReportV02 405

<OthrId>: OtherIdentification524

<Ownr>: OwnerMessage BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

P<PctgRate>: PercentageRate


SWIFTStandards MX


<PgNb>: PageNumber522

<PmtId>: PaymentIdentificationMessage CustomerCreditTransferInitiationV02 354

<PmtInf>: PaymentInformationMessage CustomerCreditTransferInitiationV02 353

<PmtInfId>: PaymentInformationIdentificationMessage BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245Message CustomerCreditTransferInitiationV02 353

<PmtMtd>: PaymentMethodMessage CustomerCreditTransferInitiationV02 354Message PaymentStatusReportV02 406

<PmtTpInf>: PaymentTypeInformationMessage CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 405

<PoolgAdjstmntDt>: PoolingAdjustmentDateMessage CustomerCreditTransferInitiationV02 354

<Pric>: PriceMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

<PrtLctn>: PrintLocation501

<Prtry>: Proprietary479, 487, 487, 500, 510, 510Message BankToCustomerAccountReportV01 6, 6, 7, 8, 8, 11, 11, 13, 14, 14, 14, 15, 15, 15, 16, 16, 16, 16, 17, 17, 17Message BankToCustomerStatementV01 124, 124, 125, 126, 126, 129, 129, 131, 132, 132, 132, 133, 133, 133, 134, 134, 134, 134, 135, 135, 135Message BankToCustomerDebitCreditNotificationV01 243, 244, 245, 247, 247, 249, 250, 250, 251, 251, 251, 252, 252, 252, 252, 253, 253, 253, 253Message CustomerCreditTransferInitiationV02 354, 354, 354, 354, 355, 356, 356Message PaymentStatusReportV02 404, 404, 405, 405, 406, 406, 407

<PrtryAcct>: ProprietaryAccount477, 479

<PrtryAmt>: ProprietaryAmountMessage BankToCustomerAccountReportV01 10, 12Message BankToCustomerStatementV01 128, 130Message BankToCustomerDebitCreditNotificationV01 246, 249

SCORE 2.0 Indexes


<PrtryCd>: ProprietaryCodeMessage BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 247, 249

<PrtryId>: ProprietaryIdentification487, 488, 510, 511, 524

<PrvcOfBirth>: ProvinceOfBirth524

<PrvtId>: PrivateIdentification524

<PsptNb>: PassportNumber524

<PstCd>: PostCode487, 488, 488, 500, 500, 510, 511, 511, 523, 534

<PstlAdr>: PostalAddress487, 487, 488, 510, 511, 511, 523

<Pty>: PartyMessage BankToCustomerAccountReportV01 10, 13, 14Message BankToCustomerStatementV01 128, 131, 132Message BankToCustomerDebitCreditNotificationV01 247, 250, 250

<Purp>: PurposeMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 355

Q<QtnDt>: QuotationDate

Message BankToCustomerAccountReportV01 9, 9, 10, 10, 10, 11, 12, 12, 12, 13Message BankToCustomerStatementV01 127, 127, 128, 128, 128, 130, 130, 130, 130, 131Message BankToCustomerDebitCreditNotificationV01 245, 246, 246, 246, 246, 248, 248, 248, 249, 249

<Qty>: QuantityMessage BankToCustomerAccountReportV01 16, 16Message BankToCustomerStatementV01 134, 134Message BankToCustomerDebitCreditNotificationV01 252, 252

R<Rate>: Rate

537

SWIFTStandards MX


Message BankToCustomerAccountReportV01 6, 6, 10, 10, 11, 11, 13, 13, 14, 14Message BankToCustomerStatementV01 124, 124, 128, 128, 129, 129, 131, 131, 132, 132Message BankToCustomerDebitCreditNotificationV01 247, 247, 247, 247, 250, 250, 250, 250

<RateTp>: RateTypeMessage CustomerCreditTransferInitiationV02 355

<RcvgAgt>: ReceivingAgentMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 251

<Ref>: ReferenceMessage BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 248

<Refs>: ReferencesMessage BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

<ReqdColltnDt>: RequestedCollectionDateMessage PaymentStatusReportV02 405

<ReqdExctnDt>: RequestedExecutionDateMessage CustomerCreditTransferInitiationV02 354Message PaymentStatusReportV02 405

<RfrdDocAmt>: ReferredDocumentAmountMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

<RfrdDocInf>: ReferredDocumentInformationMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

<RfrdDocNb>: ReferredDocumentNumberMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

<RfrdDocRltdDt>: ReferredDocumentRelatedDateMessage BankToCustomerAccountReportV01 15

SCORE 2.0 Indexes


Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

<RfrdDocTp>: ReferredDocumentTypeMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

<RgltryDtls>: RegulatoryDetailsMessage CustomerCreditTransferInitiationV02 356

<RgltryRptg>: RegulatoryReportingMessage CustomerCreditTransferInitiationV02 355

<RgnlClrZone>: RegionalClearingZone501

<RltdAcct>: RelatedAccountMessage BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

<RltdAgts>: RelatedAgentsMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250

<RltdDts>: RelatedDatesMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

<RltdPric>: RelatedPriceMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

<RltdPties>: RelatedPartiesMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250

<RltdQties>: RelatedQuantitiesMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

<RltdRmtInf>: RelatedRemittanceInformation

SWIFTStandards MX


Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

<RmtdAmt>: RemittedAmountMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

<RmtId>: RemittanceIdentificationMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

<RmtInf>: RemittanceInformationMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

<RmtLctnElctrncAdr>: RemittanceLocationElectronicAddressMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

<RmtLctnMtd>: RemittanceLocationMethodMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

<RmtLctnPstlAdr>: RemittanceLocationPostalAddressMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

<Rpt>: ReportMessage BankToCustomerAccountReportV01 6

<Rsn>: ReasonMessage BankToCustomerAccountReportV01 6, 11, 14Message BankToCustomerStatementV01 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 247, 250

<RtrInf>: ReturnInformation

SCORE 2.0 Indexes



<RtrOrgtr>: ReturnOriginatorMessage BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

<RtrRsn>: ReturnReasonMessage BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

<RvslInd>: ReversalIndicatorMessage BankToCustomerAccountReportV01 8Message BankToCustomerStatementV01 126Message BankToCustomerDebitCreditNotificationV01 244

S<SclSctyNb>: SocialSecurityNumber

524

<SeqTp>: SequenceTypeMessage PaymentStatusReportV02 406

<SfkpgAcct>: SafekeepingAccountMessage BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

<SrcCcy>: SourceCurrencyMessage BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 127, 128, 128, 129, 130, 130, 130, 130Message BankToCustomerDebitCreditNotificationV01 245, 245, 246, 246, 246, 248, 248, 248, 248, 249

<StartDt>: StartDateMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

<Stmt>: StatementMessage BankToCustomerStatementV01 124

<Strd>: StructuredMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

SWIFTStandards MX


<StrtNm>: StreetName487, 488, 488, 500, 500, 510, 511, 511, 523, 533

<Sts>: StatusMessage BankToCustomerAccountReportV01 8Message BankToCustomerStatementV01 126Message BankToCustomerDebitCreditNotificationV01 244

<StsId>: StatusIdentificationMessage PaymentStatusReportV02 404

<StsOrgtr>: StatusOriginatorMessage PaymentStatusReportV02 404, 404

<StsRsn>: StatusReasonMessage PaymentStatusReportV02 404, 404

<StsRsnInf>: StatusReasonInformationMessage PaymentStatusReportV02 404, 404

<SttlmAcct>: SettlementAccountMessage PaymentStatusReportV02 405

<SttlmInf>: SettlementInformationMessage PaymentStatusReportV02 405

<SttlmMtd>: SettlementMethodMessage PaymentStatusReportV02 405

<SttlmPlc>: SettlementPlaceMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 251

<SubFmlyCd>: SubFamilyCodeMessage BankToCustomerAccountReportV01 8, 8, 13, 17Message BankToCustomerStatementV01 126, 126, 131, 135Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 253

<Sum>: SumMessage BankToCustomerAccountReportV01 7, 7, 7, 7Message BankToCustomerStatementV01 125, 125, 125, 125Message BankToCustomerDebitCreditNotificationV01 243, 243, 244, 244

<SvcLvl>: ServiceLevelMessage CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 405

<Svcr>: ServicerMessage BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

SCORE 2.0 Indexes


T<Tax>: Tax

Message BankToCustomerAccountReportV01 10, 13, 16Message BankToCustomerStatementV01 128, 131, 134Message BankToCustomerDebitCreditNotificationV01 247, 250, 253Message CustomerCreditTransferInitiationV02 356

<TaxAmt>: TaxAmountMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

<TaxblBaseAmt>: TaxableBaseAmount537

<TaxDt>: TaxDate537

<TaxIdNb>: TaxIdentificationNumber523, 524

<TaxRefNb>: TaxReferenceNumber536

<TaxTp>: TaxType537

<TaxTpInf>: TaxTypeInformation537

<ThrdRmbrsmntAgt>: ThirdReimbursementAgentMessage PaymentStatusReportV02 405

<ThrdRmbrsmntAgtAcct>: ThirdReimbursementAgentAccountMessage PaymentStatusReportV02 405

<ToAmt>: ToAmount482, 483

<ToDtTm>: ToDateTime509

<Tp>: Type479Message BankToCustomerAccountReportV01 6, 6, 6, 10, 10, 11, 11, 12, 13, 13, 14, 14, 16, 16, 16, 16Message BankToCustomerStatementV01 124, 124, 125, 128, 128, 129, 129, 130, 131, 132, 132, 132, 134, 134, 134, 134

SWIFTStandards MX


Message BankToCustomerDebitCreditNotificationV01 243, 246, 247, 247, 247, 249, 249, 250, 250, 251, 252, 252, 252, 253

<TradDt>: TradeDateMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

<TradgPty>: TradingPartyMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250

<TrgtCcy>: TargetCurrencyMessage BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 127, 128, 128, 129, 130, 130, 130, 130Message BankToCustomerDebitCreditNotificationV01 245, 245, 246, 246, 246, 248, 248, 248, 248, 249

<TtlCdtNtries>: TotalCreditEntriesMessage BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125Message BankToCustomerDebitCreditNotificationV01 243

<TtlChrgsAndTaxAmt>: TotalChargesAndTaxAmountMessage BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 246, 249

<TtlDbtNtries>: TotalDebitEntriesMessage BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125Message BankToCustomerDebitCreditNotificationV01 243

<TtlNetNtryAmt>: TotalNetEntryAmountMessage BankToCustomerAccountReportV01 7, 7Message BankToCustomerStatementV01 125, 125Message BankToCustomerDebitCreditNotificationV01 243, 244

<TtlNtries>: TotalEntriesMessage BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125Message BankToCustomerDebitCreditNotificationV01 243

<TtlNtriesPerBkTxCd>: TotalEntriesPerBankTransactionCodeMessage BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125Message BankToCustomerDebitCreditNotificationV01 244

<TtlTaxAmt>: TotalTaxAmount537

<TtlTaxblBaseAmt>: TotalTaxableBaseAmount

SCORE 2.0 Indexes


537

<TwnNm>: TownName487, 488, 488, 500, 500, 510, 511, 511, 523, 534

<TxAmt>: TransactionAmountMessage BankToCustomerAccountReportV01 9, 12Message BankToCustomerStatementV01 127, 130Message BankToCustomerDebitCreditNotificationV01 245, 248

<TxDtls>: TransactionDetailsMessage BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

<TxDtTm>: TransactionDateTimeMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

<TxId>: TransactionIdentificationMessage BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

<TxInfAndSts>: TransactionInformationAndStatusMessage PaymentStatusReportV02 404

<TxsSummry>: TransactionsSummaryMessage BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125Message BankToCustomerDebitCreditNotificationV01 243

<TxSts>: TransactionStatusMessage PaymentStatusReportV02 404

<TxtlRate>: TextualRateMessage BankToCustomerAccountReportV01 6, 11, 14Message BankToCustomerStatementV01 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 247, 250

U<UltmtCdtr>: UltimateCreditor


<UltmtDbtr>: UltimateDebtorMessage BankToCustomerAccountReportV01 14

SWIFTStandards MX


Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250Message CustomerCreditTransferInitiationV02 354, 355Message PaymentStatusReportV02 407

<Unit>: Unit535

<UnitCcy>: UnitCurrencyMessage BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 127, 128, 128, 129, 130, 130, 130, 131Message BankToCustomerDebitCreditNotificationV01 245, 245, 246, 246, 246, 248, 248, 248, 248, 249

<UPIC>: UPIC477, 479

<USCHU>: CHIPSUniversalIdentification523

<Ustrd>: UnstructuredMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

V<ValDt>: ValueDate


<VldtyRg>: ValidityRangeMessage BankToCustomerAccountReportV01 6, 11, 14Message BankToCustomerStatementV01 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 247, 250

X<XchgRate>: ExchangeRate

Message BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 128, 128, 128, 129, 130, 130, 130, 131Message BankToCustomerDebitCreditNotificationV01 245, 246, 246, 246, 246, 248, 248, 248, 249, 249Message CustomerCreditTransferInitiationV02 355

<XchgRateInf>: ExchangeRateInformationMessage CustomerCreditTransferInitiationV02 355

SCORE 2.0 Indexes


Index of Message Item TypesAAccountIdentification3Choice

477, 479Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

AccountInterest1Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124

AccountNotification1Message BankToCustomerDebitCreditNotificationV01 243

AccountReport9Message BankToCustomerAccountReportV01 6

AccountStatement1Message BankToCustomerStatementV01 124

AddressType2Code487, 487, 488, 500, 500, 510, 511, 511, 523, 533

AlternateSecurityIdentification2Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 253

AmendmentInformationDetails1Message PaymentStatusReportV02 406

AmountAndCurrencyExchange2Message BankToCustomerAccountReportV01 9, 11Message BankToCustomerStatementV01 127, 129Message BankToCustomerDebitCreditNotificationV01 245, 248

AmountAndCurrencyExchangeDetails1Message BankToCustomerAccountReportV01 9, 9, 9, 10, 11, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 127, 128, 129, 130, 130, 130Message BankToCustomerDebitCreditNotificationV01 245, 245, 246, 246, 248, 248, 248, 248

AmountAndCurrencyExchangeDetails2Message BankToCustomerAccountReportV01 10, 12Message BankToCustomerStatementV01 128, 130Message BankToCustomerDebitCreditNotificationV01 246, 249

AmountRangeBoundary1482, 482, 483, 483

SWIFTStandards MX


AmountType2ChoiceMessage CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 405

AustrianBankleitzahlIdentifier463

BBalanceType1Choice

Message BankToCustomerAccountReportV01 6

BalanceType2ChoiceMessage BankToCustomerStatementV01 125

BalanceType8CodeMessage BankToCustomerAccountReportV01 7

BalanceType9CodeMessage BankToCustomerStatementV01 125

BankTransactionCodeStructure1Message BankToCustomerAccountReportV01 7, 8, 13, 16Message BankToCustomerStatementV01 125, 126, 131, 134Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 253



BaseOneRate473Message BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 128, 128, 128, 129, 130, 130, 130, 131Message BankToCustomerDebitCreditNotificationV01 245, 246, 246, 246, 246, 248, 248, 248, 249, 249Message CustomerCreditTransferInitiationV02 355

BatchBookingIndicatorMessage CustomerCreditTransferInitiationV02 353

BatchInformation1Message BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245

BBANIdentifier

SCORE 2.0 Indexes


463, 477, 479

BEIIdentifier463, 523

BelgianIdentifier464

BICIdentifier464, 487, 487, 510, 510, 523

BloombergIdentifier464

BranchAndFinancialInstitutionIdentification3487, 510Message BankToCustomerAccountReportV01 6, 10, 13, 14, 14, 14, 14, 14, 14, 14, 14, 14, 14Message BankToCustomerStatementV01 124, 128, 131, 132, 132, 132, 132, 132, 132, 132, 132, 132, 133Message BankToCustomerDebitCreditNotificationV01 243, 247, 250, 250, 250, 251, 251, 251, 251, 251, 251, 251, 251Message CustomerCreditTransferInitiationV02 353, 354, 354, 355, 355, 355, 355Message PaymentStatusReportV02 403, 403, 403, 403, 403, 405, 405, 405, 405, 405, 406, 406, 407, 407

BranchData488, 511

CCanadianPaymentsARNIdentifier

465

CashAccount13Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

CashAccount7478Message BankToCustomerAccountReportV01 6, 14, 14, 17Message BankToCustomerStatementV01 124, 132, 132, 135Message BankToCustomerDebitCreditNotificationV01 243, 250, 250, 253Message CustomerCreditTransferInitiationV02 354, 354, 354, 355, 355, 355, 355, 355Message PaymentStatusReportV02 405, 405, 405, 405, 406, 406, 406, 407, 407, 407, 407

CashAccountType2479Message BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

CashAccountType4Code479

SWIFTStandards MX



CashBalance1Message BankToCustomerAccountReportV01 6

CashBalance2Message BankToCustomerStatementV01 125

CashBalanceAvailability1Message BankToCustomerAccountReportV01 7, 8, 8, 13Message BankToCustomerStatementV01 125, 126, 126, 131Message BankToCustomerDebitCreditNotificationV01 244, 244, 249

CashBalanceAvailabilityDate1Message BankToCustomerAccountReportV01 7, 8, 8, 13Message BankToCustomerStatementV01 125, 126, 126, 131Message BankToCustomerDebitCreditNotificationV01 244, 244, 249

CashClearingSystem3CodeMessage PaymentStatusReportV02 405

CFIIdentifier464

ChargeBearerType1CodeMessage BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 247, 250Message CustomerCreditTransferInitiationV02 354, 355

ChargesInformation1487Message PaymentStatusReportV02 405

ChargesInformation3Message BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 246, 249

ChargeType1CodeMessage BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 247, 249

ChargeTypeChoiceMessage BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 247, 249

Cheque5

SCORE 2.0 Indexes


500Message CustomerCreditTransferInitiationV02 355

ChequeDelivery1Code500

ChequeDeliveryMethod1Choice500

ChequeType2Code500

CHIPSParticipantIdentifier465

CHIPSUniversalIdentifier465, 523

ClearingChannel2CodeMessage CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 406

ClearingSystemIdentification1ChoiceMessage PaymentStatusReportV02 405

ClearingSystemMemberIdentification3Choice487, 487, 510, 510

ConsolidatedTapeAssociationIdentifier465

CopyDuplicate1CodeMessage BankToCustomerAccountReportV01 6Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

CorporateAction1Message BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

CountryCode465, 487, 488, 488, 500, 500, 510, 511, 511, 523, 524, 524, 534Message CustomerCreditTransferInitiationV02 355

CreditDebitCode483Message BankToCustomerAccountReportV01 7, 7, 7, 7, 8, 8, 8, 11, 13, 13Message BankToCustomerStatementV01 125, 125, 125, 125, 126, 126, 126, 129, 131, 132Message BankToCustomerDebitCreditNotificationV01 243, 244, 244, 244, 245, 247, 249, 250

CreditLine1

SWIFTStandards MX



CreditorReferenceInformation1Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

CreditorReferenceType1Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

CreditTransferTransactionInformation1Message CustomerCreditTransferInitiationV02 354

CurrencyAndAmount462, 487, 537, 537, 537, 537Message BankToCustomerAccountReportV01 7, 7, 7, 8, 8, 8, 9, 9, 9, 10, 10, 10, 10, 10, 11, 11, 12, 12, 12, 12, 13, 13, 13, 13, 13, 15, 15, 15, 15, 15, 16, 16Message BankToCustomerStatementV01 125, 125, 125, 126, 126, 126, 127, 127, 127, 128, 128, 128, 128, 129, 129, 129, 130, 130, 130, 130, 131, 131, 131, 131, 131, 133, 133, 133, 133, 133, 134, 134Message BankToCustomerDebitCreditNotificationV01 244, 244, 245, 245, 245, 246, 246, 246, 246, 246, 247, 247, 248, 248, 248, 248, 249, 249, 249, 249, 250, 250, 251, 251, 251, 252, 252, 252, 252Message CustomerCreditTransferInitiationV02 355, 355, 356, 356, 356, 356, 356, 356Message PaymentStatusReportV02 405, 405, 405, 407, 407, 407, 407, 407

CurrencyAndAmountRange482Message BankToCustomerAccountReportV01 6, 11, 14Message BankToCustomerStatementV01 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 247, 250

CurrencyCode466, 479, 483, 487, 537, 537, 537, 537Message BankToCustomerAccountReportV01 6, 7, 7, 7, 8, 8, 8, 9, 9, 9, 9, 9, 9, 9, 9, 9, 9, 9, 9, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 11, 11, 11, 11, 11, 12, 12, 12, 12, 12, 12, 12, 12, 12, 12, 12, 12, 12, 12, 12, 12, 13, 13, 13, 13, 13, 15, 15, 15, 15, 15, 16, 16Message BankToCustomerStatementV01 124, 125, 125, 125, 126, 126, 126, 127, 127, 127, 127, 127, 127, 127, 127, 127, 127, 127, 127, 128, 128, 128, 128, 128, 128, 128, 128, 128, 128, 129, 129, 129, 129, 129, 129, 130, 130, 130, 130, 130, 130, 130, 130, 130, 130, 130, 130, 130, 130, 130, 131, 131, 131, 131, 131, 131, 133, 133, 133, 133, 133, 134, 134Message BankToCustomerDebitCreditNotificationV01 243, 244, 244, 245, 245, 245, 245, 245, 245, 245, 245, 245, 246, 246, 246, 246, 246, 246, 246, 246, 246, 246, 246, 246, 246, 246, 247, 247, 248, 248, 248, 248, 248, 248, 248, 248, 248, 248, 248, 248, 248, 248, 248, 248, 249, 249, 249, 249, 249, 249, 249, 250, 250, 251, 251, 251, 252, 252, 252, 252Message CustomerCreditTransferInitiationV02 355, 355, 355, 356, 356, 356, 356, 356, 356Message PaymentStatusReportV02 405, 405, 405, 405, 407, 407, 407, 407, 407

SCORE 2.0 Indexes


CurrencyExchange3Message BankToCustomerAccountReportV01 9, 9, 9, 10, 10, 11, 12, 12, 12, 12Message BankToCustomerStatementV01 127, 127, 127, 128, 128, 129, 130, 130, 130, 130Message BankToCustomerDebitCreditNotificationV01 245, 245, 246, 246, 246, 248, 248, 248, 248, 249

CUSIPIdentifier465

DDateAndDateTimeChoice

508Message BankToCustomerAccountReportV01 7, 8, 8Message BankToCustomerStatementV01 125, 126, 126Message BankToCustomerDebitCreditNotificationV01 244, 244

DateAndPlaceOfBirth524

DateTimePeriodDetails509Message BankToCustomerAccountReportV01 6, 6, 11, 14Message BankToCustomerStatementV01 124, 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 243, 247, 250

DecimalNumber473, 535Message BankToCustomerAccountReportV01 7, 7, 7, 7, 7, 7Message BankToCustomerStatementV01 125, 125, 125, 125, 125, 125Message BankToCustomerDebitCreditNotificationV01 243, 243, 243, 244, 244, 244Message CustomerCreditTransferInitiationV02 353Message PaymentStatusReportV02 404, 404

DocumentType2CodeMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

DocumentType3CodeMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 252Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

DunsIdentifier466, 523

DutchIdentifier

SWIFTStandards MX


466

EEANGLNIdentifier

466, 523

EntryStatus2CodeMessage BankToCustomerAccountReportV01 8

EntryStatus3CodeMessage BankToCustomerStatementV01 126

EntryStatus4CodeMessage BankToCustomerDebitCreditNotificationV01 244

EntryTransaction1Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

EquivalentAmountMessage CustomerCreditTransferInitiationV02 355Message PaymentStatusReportV02 405

EuroclearClearstreamIdentifier466

ExchangeRateInformation1Message CustomerCreditTransferInitiationV02 355

ExchangeRateType1CodeMessage CustomerCreditTransferInitiationV02 355

ExtensiveBranchNetworkIdentifier466

ExternalBankTransactionDomainCode467Message BankToCustomerAccountReportV01 7, 8, 13, 16Message BankToCustomerStatementV01 126, 126, 131, 134Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 253

ExternalBankTransactionFamilyCode467Message BankToCustomerAccountReportV01 8, 8, 13, 16Message BankToCustomerStatementV01 126, 126, 131, 135Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 253

ExternalBankTransactionSubFamilyCode467Message BankToCustomerAccountReportV01 8, 8, 13, 17

SCORE 2.0 Indexes


Message BankToCustomerStatementV01 126, 126, 131, 135Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 253

ExternalClearingSystemMemberCode467, 487, 487, 510, 510

ExternalCode467

ExternalLocalInstrumentCode468Message CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 406

ExternalPurposeCode468Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 355

FFedwireRoutingNumberIdentifier

468

FinancialInstitutionIdentification3487, 510

FinancialInstitutionIdentification5Choice487, 510

FinancialInstrumentQuantityChoice535Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

Frequency1CodeMessage PaymentStatusReportV02 406, 406

FromToAmountRange482

GGenericIdentification3

487, 488, 510, 511, 524

GenericIdentification4524

SWIFTStandards MX


GermanBankleitzahlIdentifier468

GroupHeader1Message CustomerCreditTransferInitiationV02 353

GroupHeader23Message BankToCustomerAccountReportV01 5Message BankToCustomerStatementV01 123Message BankToCustomerDebitCreditNotificationV01 242

GroupHeader5Message PaymentStatusReportV02 403

Grouping1CodeMessage CustomerCreditTransferInitiationV02 353

HHellenicBankIdentificationCodeIdentifier

468

HongKongBankIdentifier468

IIBANIdentifier

469, 477, 479

IBEIIdentifier469, 523

ImpliedCurrencyAmountRangeChoice482

ImpliedCurrencyAndAmount462, 482, 482, 483, 483, 483, 483, 535, 535

IndianFinancialSystemCodeIdentifier469

Instruction3CodeMessage CustomerCreditTransferInitiationV02 355

InstructionForCreditorAgent1Message CustomerCreditTransferInitiationV02 355

InterestType1ChoiceMessage BankToCustomerAccountReportV01 6, 11, 13

SCORE 2.0 Indexes


Message BankToCustomerStatementV01 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 247, 250

InterestType1CodeMessage BankToCustomerAccountReportV01 6, 11, 14Message BankToCustomerStatementV01 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 247, 250

IrishNSCIdentifier469

ISINIdentifier469Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

ISODate462, 500, 509, 524, 537Message BankToCustomerAccountReportV01 7, 8, 8, 13, 15, 16, 16, 16, 16, 16Message BankToCustomerStatementV01 125, 126, 126, 131, 133, 134, 134, 134, 134, 134Message BankToCustomerDebitCreditNotificationV01 244, 244, 249, 251, 252, 252, 252, 252, 252Message CustomerCreditTransferInitiationV02 354, 354, 356Message PaymentStatusReportV02 405, 405, 405, 406, 406, 406, 406, 407

ISODateTime462, 509, 509, 509Message BankToCustomerAccountReportV01 5, 6, 9, 9, 10, 10, 10, 11, 12, 12, 12, 13, 16, 16, 16Message BankToCustomerStatementV01 123, 124, 127, 127, 128, 128, 128, 130, 130, 130, 130, 131, 134, 134, 134Message BankToCustomerDebitCreditNotificationV01 243, 243, 245, 246, 246, 246, 246, 248, 248, 248, 249, 249, 252, 252, 252Message CustomerCreditTransferInitiationV02 353Message PaymentStatusReportV02 403, 404, 405

ISOTime463

ISOYear463

ItalianDomesticIdentifier469

LLanguageCode

470

LocalInstrument1ChoiceMessage CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 406

SWIFTStandards MX


MMandateRelatedInformation1


Max1025Text473Message PaymentStatusReportV02 406

Max105Text474Message BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253Message PaymentStatusReportV02 404, 405

Max128Text474Message CustomerCreditTransferInitiationV02 353

Max140Text474, 536Message BankToCustomerAccountReportV01 15, 16Message BankToCustomerStatementV01 133, 134Message BankToCustomerDebitCreditNotificationV01 251, 252Message CustomerCreditTransferInitiationV02 355, 355, 356, 357Message PaymentStatusReportV02 406, 407

Max15NumericText474Message BankToCustomerAccountReportV01 7, 7, 7, 7, 9Message BankToCustomerStatementV01 125, 125, 125, 125, 127Message BankToCustomerDebitCreditNotificationV01 243, 243, 244, 244, 245Message CustomerCreditTransferInitiationV02 353Message PaymentStatusReportV02 404, 404

Max15PlusSignedNumericText474Message BankToCustomerAccountReportV01 7, 8, 8, 13Message BankToCustomerStatementV01 125, 126, 126, 131Message BankToCustomerDebitCreditNotificationV01 244, 244, 249

Max16Text474, 487, 487, 488, 488, 488, 488, 500, 500, 500, 500, 510, 510, 511, 511, 511, 511, 523, 523, 533, 534

Max256Text474Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

SCORE 2.0 Indexes


Max34Text475, 477, 479

Max350Text475

Max35Text475, 479, 487, 487, 487, 487, 487, 487, 488, 488, 488, 488, 488, 488, 488, 488, 500, 500, 500, 500, 500, 500, 501, 501, 501, 501, 510, 510, 510, 510, 510, 510, 511, 511, 511, 511, 511, 511, 511, 511, 523, 523, 523, 523, 524, 524, 524, 524, 524, 524, 524, 524, 524, 524, 524, 524, 524, 524, 524, 534, 534, 536, 536, 536, 537, 537Message BankToCustomerAccountReportV01 5, 6, 6, 6, 6, 6, 7, 8, 8, 8, 8, 8, 9, 9, 9, 9, 9, 9, 9, 10, 10, 10, 10, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 12, 12, 12, 12, 13, 13, 13, 13, 14, 14, 14, 14, 14, 15, 15, 15, 15, 15, 15, 15, 15, 16, 16, 16, 16, 16, 16, 17, 17, 17, 17, 17, 17Message BankToCustomerStatementV01 123, 124, 124, 124, 124, 124, 125, 126, 126, 126, 127, 127, 127, 127, 127, 127, 127, 127, 128, 128, 128, 128, 128, 129, 129, 129, 129, 129, 129, 129, 129, 129, 129, 129, 129, 129, 130, 130, 130, 130, 130, 131, 131, 131, 131, 132, 132, 132, 132, 132, 133, 133, 133, 133, 133, 133, 133, 133, 134, 134, 134, 134, 134, 134, 135, 135, 135, 135, 135, 135Message BankToCustomerDebitCreditNotificationV01 242, 243, 243, 244, 244, 244, 245, 245, 245, 245, 245, 245, 245, 246, 246, 246, 246, 246, 247, 247, 247, 247, 247, 247, 247, 247, 247, 247, 247, 247, 247, 248, 248, 248, 248, 249, 249, 249, 249, 249, 250, 250, 250, 250, 250, 251, 251, 251, 251, 251, 251, 252, 252, 252, 252, 252, 252, 252, 253, 253, 253, 253, 253, 253, 253, 253Message CustomerCreditTransferInitiationV02 353, 353, 354, 354, 354, 354, 354, 354, 355, 355, 356, 356, 356, 356, 356, 356, 356, 356Message PaymentStatusReportV02 403, 404, 404, 404, 404, 404, 404, 404, 404, 404, 404, 404, 405, 405, 406, 406, 406, 406, 406, 407, 407, 407, 407

Max3NumericText475

Max3Text475Message CustomerCreditTransferInitiationV02 356

Max4AlphaNumericText475Message BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 247, 249

Max500Text476Message BankToCustomerAccountReportV01 6, 17, 17, 17Message BankToCustomerStatementV01 124, 135, 135, 135Message BankToCustomerDebitCreditNotificationV01 243, 253, 253, 253

Max5NumericText476, 522

Max70Text476, 479, 487, 487, 487, 487, 488, 488, 488, 488, 500, 500, 500, 500, 500, 500, 510, 510, 510, 511, 511, 511, 511, 511, 523, 523, 523, 533, 533Message BankToCustomerAccountReportV01 6, 15

SWIFTStandards MX


Message BankToCustomerStatementV01 124, 133Message BankToCustomerDebitCreditNotificationV01 243, 251Message CustomerCreditTransferInitiationV02 355, 356

MessageIdentification2Message BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245

MICIdentifier470

NNameAndAddress3

500, 500Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

NameAndAddress7487, 510

NationalityCode470

NewZealandNCCIdentifier470

NotificationEntry1Message BankToCustomerDebitCreditNotificationV01 244

Number473Message BankToCustomerAccountReportV01 6, 6Message BankToCustomerStatementV01 124, 124Message BankToCustomerDebitCreditNotificationV01 243, 243

NumberAndSumOfTransactions1Message BankToCustomerAccountReportV01 7, 7Message BankToCustomerStatementV01 125, 125Message BankToCustomerDebitCreditNotificationV01 243, 243

NumberAndSumOfTransactions2Message BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125Message BankToCustomerDebitCreditNotificationV01 243

NumberAndSumOfTransactionsPerBankTransactionCode1Message BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125

SCORE 2.0 Indexes


Message BankToCustomerDebitCreditNotificationV01 244

NumberOfTransactionsPerStatus1Message PaymentStatusReportV02 404

OOrganisationIdentification2

523

OriginalGroupInformation1Message PaymentStatusReportV02 404

OriginalTransactionReference1Message PaymentStatusReportV02 405

PPagination

522Message BankToCustomerAccountReportV01 5Message BankToCustomerStatementV01 124Message BankToCustomerDebitCreditNotificationV01 243

Party2Choice523

PartyIdentification8523Message BankToCustomerAccountReportV01 5, 6, 14, 14, 14, 14, 14, 14, 14, 15, 15, 17Message BankToCustomerStatementV01 124, 124, 132, 132, 132, 132, 132, 132, 132, 133, 134, 135Message BankToCustomerDebitCreditNotificationV01 243, 243, 250, 250, 250, 250, 250, 250, 250, 252, 252, 253Message CustomerCreditTransferInitiationV02 353, 354, 354, 355, 355, 355, 357, 357Message PaymentStatusReportV02 403, 404, 404, 405, 406, 406, 407, 407, 407, 407, 407, 407

PaymentCategoryPurpose1CodeMessage CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 406

PaymentIdentification1Message CustomerCreditTransferInitiationV02 354

PaymentInstructionInformation1Message CustomerCreditTransferInitiationV02 353

PaymentMethod3CodeMessage CustomerCreditTransferInitiationV02 354

PaymentMethod4CodeMessage PaymentStatusReportV02 406

SWIFTStandards MX


PaymentTransactionInformation1Message PaymentStatusReportV02 404

PaymentTypeInformation1Message CustomerCreditTransferInitiationV02 354, 354

PaymentTypeInformation6Message PaymentStatusReportV02 405

PercentageRate473, 537Message BankToCustomerAccountReportV01 6, 10, 10, 11, 13, 13, 14Message BankToCustomerStatementV01 124, 128, 128, 129, 131, 131, 132Message BankToCustomerDebitCreditNotificationV01 247, 247, 247, 250, 250, 250

PersonIdentification3524

PolishNationalClearingCodeIdentifier470

PortugueseNCCIdentifier470

PostalAddress1487, 487, 488, 500, 500, 510, 511, 511, 523, 533Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

Priority2Code500Message CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 405

ProprietaryAgent1Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 251

ProprietaryBankTransactionCodeStructure1Message BankToCustomerAccountReportV01 8, 8, 13, 17Message BankToCustomerStatementV01 126, 126, 131, 135Message BankToCustomerDebitCreditNotificationV01 244, 245, 249, 253

ProprietaryDate1Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

ProprietaryParty1

SCORE 2.0 Indexes



ProprietaryPrice1Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

ProprietaryQuantity1Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

ProprietaryReference1Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

Purpose1ChoiceMessage BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 355

QQUICKIdentifier

470

RRate1


RateTypeChoiceMessage BankToCustomerAccountReportV01 6, 11, 14Message BankToCustomerStatementV01 124, 129, 132Message BankToCustomerDebitCreditNotificationV01 247, 250

ReferredDocumentAmount1ChoiceMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 407

ReferredDocumentInformation1Message BankToCustomerAccountReportV01 15

SWIFTStandards MX


Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

ReferredDocumentType1Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

RegulatoryAuthorityMessage CustomerCreditTransferInitiationV02 355

RegulatoryReporting2Message CustomerCreditTransferInitiationV02 355

RegulatoryReportingType1CodeMessage CustomerCreditTransferInitiationV02 355

RemittanceInformation1Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

RemittanceLocation1Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

RemittanceLocationMethod1CodeMessage BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356

ReportEntry1Message BankToCustomerAccountReportV01 8

ReturnReason1ChoiceMessage BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253

ReturnReasonInformation5Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 253

SCORE 2.0 Indexes


RICIdentifier471

RussianCentralBankIdentificationCodeIdentifier471

SSecurityIdentification4Choice


SEDOLIdentifier471

SequenceType1CodeMessage PaymentStatusReportV02 406

ServiceLevel1CodeMessage CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 405

ServiceLevel2ChoiceMessage CustomerCreditTransferInitiationV02 354, 354Message PaymentStatusReportV02 405

SettlementInformation3Message PaymentStatusReportV02 405

SettlementMethod1CodeMessage PaymentStatusReportV02 405

SicovamIdentifier471

SimpleIdentificationInformation2477, 479

SmallNetworkIdentifier471

SouthAfricanNCCIdentifier471

SpanishDomesticInterbankingIdentifier472

StatementEntry1Message BankToCustomerStatementV01 126

SWIFTStandards MX


StatusReason1ChoiceMessage PaymentStatusReportV02 404, 404

StatusReasonInformation1Message PaymentStatusReportV02 404, 404

StructuredRegulatoryReporting2Message CustomerCreditTransferInitiationV02 356

StructuredRemittanceInformation6Message BankToCustomerAccountReportV01 15Message BankToCustomerStatementV01 133Message BankToCustomerDebitCreditNotificationV01 251Message CustomerCreditTransferInitiationV02 356Message PaymentStatusReportV02 406

SwissBCIdentifier472

SwissSICIdentifier472

TTaxCharges1

Message BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 128, 131Message BankToCustomerDebitCreditNotificationV01 247, 250

TaxDetails537

TaxInformation2536Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 253Message CustomerCreditTransferInitiationV02 356

TaxType537

TickerIdentifier472

TotalTransactions1Message BankToCustomerAccountReportV01 7Message BankToCustomerStatementV01 125Message BankToCustomerDebitCreditNotificationV01 243

TransactionAgents1Message BankToCustomerAccountReportV01 14

SCORE 2.0 Indexes



TransactionDates1Message BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

TransactionGroupStatus1CodeMessage PaymentStatusReportV02 404

TransactionIndividualStatus1CodeMessage PaymentStatusReportV02 404, 404

TransactionInterest1Message BankToCustomerAccountReportV01 10, 13Message BankToCustomerStatementV01 129, 131Message BankToCustomerDebitCreditNotificationV01 247, 250

TransactionParty1Message BankToCustomerAccountReportV01 14Message BankToCustomerStatementV01 132Message BankToCustomerDebitCreditNotificationV01 250

TransactionPrice1ChoiceMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

TransactionQuantities1ChoiceMessage BankToCustomerAccountReportV01 16Message BankToCustomerStatementV01 134Message BankToCustomerDebitCreditNotificationV01 252

TransactionReferences1Message BankToCustomerAccountReportV01 11Message BankToCustomerStatementV01 129Message BankToCustomerDebitCreditNotificationV01 247

TransactionRejectReason2CodeMessage BankToCustomerAccountReportV01 17Message BankToCustomerStatementV01 135Message BankToCustomerDebitCreditNotificationV01 253Message PaymentStatusReportV02 404, 404

TrueFalseIndicatorMessage BankToCustomerAccountReportV01 7, 8Message BankToCustomerStatementV01 125, 126Message BankToCustomerDebitCreditNotificationV01 244Message PaymentStatusReportV02 406

SWIFTStandards MX


UUKDomesticSortCodeIdentifier

472

UPICIdentifier472, 477, 479

VValorenIdentifier

472

WWertpapierIdentifier

473

YYesNoIndicator

482, 482, 483, 483, 522Message BankToCustomerAccountReportV01 9Message BankToCustomerStatementV01 127Message BankToCustomerDebitCreditNotificationV01 245

Index of Error CodesFatal

Sw.Stds.D00001BIC

464, 489, 493, 512, 516, 527

Sw.Stds.D00002BEI

464, 528

Sw.Stds.D00003IBAN

469, 478, 479

Sw.Stds.D00004Country

465, 492, 496, 499, 504, 507, 515, 519, 522, 526, 532, 533, 535Message CustomerCreditTransferInitiationV02 383

SCORE 2.0 Indexes


Swift 8

Documents

Transcript of Swift 8