camt.052 Bank to Customer Report camt.053 Bank to Customer Statement camt.054 Bank to Customer Notification Format Description
|
|
- Cecily Boone
- 6 years ago
- Views:
Transcription
1 camt.052 Bank to Customer Report camt.053 Bank to Customer Statement camt.054 Bank to Customer Notification Format Description
2 camt.053 Format Description Introduction... 3 Character set... 3 Date and time format... 4 Number format... 4 Message structure... 6 List of elements... 7 GroupHeader (GrpHdr) Statement (Stmt) Entry (Ntry) EntryDetails (NtryDtls) Example Annex SWIFT character set Resources... 53
3 camt.053 Format Description Introduction Cash Management (camt) messages provide Bank-To-Customer information in XML format. They are part of the ISO message definitions. Three types of camt messages are available: XML-Message Type SWIFT/EDIFACT-Message camt.052 Interim statement SWIFT MT942 camt.053 End of day statement SWIFT MT940 camt.054 Return data carrier EDIFACT Cremul/Debmul This document describes the format of each of those messages. It includes the restrictions based on implementation recommendations of EPC and the extensions for use in Austria. The camt.052 (Bank to Customer Report) is used to inform the account owner of entries booked and pending on the account as well as balance information during the day (interim statement). camt.052 ISO XML schema: camt.052 ISO Namespace: camt.052 Austrian XML schema: camt.052 Austrian Namespace: camt xsd urn:iso:std:iso:20022:tech:xsd:camt ISO.camt austrian.003.xsd ISO:camt :APC:STUZZA:payments:003 The camt.053 (Bank to Customer Statement) is used to inform the account owner of entries booked on the account as well as balance information at the end of the day (end of day statement). camt.053 ISO XML schema: camt.053 ISO Namespace: camt.053 Austrian XML schema: camt.053 Austrian Namespace: camt xsd urn:iso:std:iso:20022:tech:xsd:camt ISO.camt.053.0wenn er austrian.003.xsd ISO:camt :APC:STUZZA:payments:003 The camt.054 (Bank to Customer Notification) is used to provide further details for every single transaction for account movements booked as a batch. camt.053 ISO XML schema: camt.054 ISO Namespace: camt.053 Austrian XML schema: camt.054 Austrian Namespace: camt xsd urn:iso:std:iso:20022:tech:xsd:camt ISO.camt austrian.003.xsd ISO:camt :APC:STUZZA:payments:003 Links to download the schema files can be found in chapter Resources on page 53. Character set ISO XML messages are UTF-8 encoded. For references, ID s and codes only the SWIFT character set will be used. A list of those characters can be found in chapter SWIFT character set on page 53. Names, addresses and remittance information may contain country specific characters. In Austria the following characters are common: Ä, ä, Ö, ö, Ü, ü, ß. Several XML specific characters will be escaped in the file when used in names, addresses or similar fields:
4 camt.053 Format Description Name Character Entity Ampersand & & Double quotation mark " Apostrophe ' Less-than sign < < Greater-than sign > > Examples of how text with special characters will appear in the XML file: Text Number 123 Ben & Jerry s XML-File Number "123" Ben & Jerry's Date and time format The date and time format is aligned to ISO Dates will be formatted the following way: YYYY-MM-DD 4 digits year, 2 digits month, 2 digits day Example: <Dt> </Dt> 1 st of August 2014 <Dt> </Dt> 31 st of October 2016 Timestamps (Date and Time) will be written in the following format: YYYY-MM-DDThh:mm:ss.sss+hh:mm Example: <CreDtTm> T15:31: :00</CreDtTm> This format includes the date, hours, minutes, seconds, milliseconds and the timezone (offset from UTC). Number format Amounts will be specified without leading or trailing zeros. No thousands separator is used. Decimal separator will be. in case decimal places are used. Example: <Amt Ccy="EUR">31</Amt> <Amt Ccy="EUR">4.99</Amt> <Amt Ccy="EUR">0.15</Amt> <Amt Ccy="EUR">2468.5</Amt> <Amt Ccy="EUR"> </Amt> The amount itself is always unsigned. A negative amount will be indicated by a specific XML- Tag (<CdtDbtInd>) following the amount (<Amt>).
5 camt.053 Format Description The currency of an amount is specified in the attribute Ccy of the Amount-Tag (<Amt>). The 3-character alphabetic code according to ISO 4217 is used. Example: <Amt Ccy="EUR">27</Amt> <CdtDbtInd>CRDT</CdtDbtInd> Positive amount (credit) equals to 27 EUR. <Amt Ccy="USD">11</Amt> <CdtDbtInd>DBIT</CdtDbtInd> Negative amount (debit) equals to -11 USD. Exchange rates may be specified with a precision of (technically) up to 10 decimal places. Usually 5 decimal places won t be exceeded. Example: <XchgRate>1.3185</XchgRate>
6 camt.053 Format Description Message structure In the following chapter the XML structure for a camt.053 (Statement) is described. The structure for the camt.052 (Intraday Report) and camt.054 (Notification) only differs for the following parent tags: camt.052 camt.053 camt.054 <BkToCstmrAcctRpt> <BkToCstmrStmt> <BkToCstmrDbtCdtNtfctn> <Rpt> <Stmt> <Ntfctn> A file containing a camt.053 message has the following structure: Figure 1: Document root The envelope or document root (Document/BkToCstmrStmt) contains the following blocks: GroupHeader (GrpHdr): This block is mandatory and present once. It contains information valid for the whole file such as Message Identification and Creation Time. Statement (Stmt): This block is mandatory and will be repeated for each account on which a statement will be provided. It contains balances and information about the movements. Example: <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt " xmlns:xsi=" <BkToCstmrStmt> <GrpHdr> contents of GrpHdr </GrpHdr> <Stmt> contents of Stmt this block may appear more than once </Stmt> </BkToCstmrStmt> </Document> In the following table and chapters, only elements that are used by RLB will be listed and described.
7 List of elements Level Message Item XML-Tag Presence Type Description Example BankToCustomerStatement <BkToCstmrStmt> [1..1] 0 GroupHeader <GrpHdr> [1..1] Basic information of transmitted file. 1 MessageIdentification <MsgId> [1..1] Text Technical reference of transmitted file CreationDateTime <CreDtTm> [1..1] DateTime Creation date and time of the file. The format is YYYY-MM- DDThh:mm:ss.sss+hh:mm 1 MessageRecipient <MsgRcpt> [1..1] Specifies the channel through which the message is sent T21:44: :00 2 Identification <Id> [0..1] 3 OrganisationIdentification <OrgId> [1..1] 4 Other <Othr> [0..n] 5 Identification <Id> [1..1] Text Name of the channel. ATMULTICASH 0 Statement <Stmt> [1..n] This structure contains exactly one account statement. The structure is repeatable. Therefore multiple accounts and statements are possible in a file. 1 Identification <Id> [1..1] Text Unique technical reference of this account statement. 1 LegalSequenceNumber <LglSeqNb> [1..1] Number Statement Number CreationDateTime <CreDtTm> [1..1] DateTime Creation date and time of the statement. The format is YYYY-MM-DDThh:mm:ss. Timezone is CET/CEST. 1 Account <Acct> [1..1] 2 Identification <Id> [1..1] T21:44: :00 3 IBAN <IBAN> [1..1] Identifier IBAN AT Currency <Ccy> [0..1] Code Account currency. EUR 2 Servicer <Svcr> [0..1] 3 FinancialInstitutionIdentification <FinInstnId> [1..1] 4 BIC <BIC> [1..1] Identifier BIC RLNWATWW 1 Balance <Bal> [1..n] Balance information. 2 Type <Tp> [1..1] 3 CodeOrProprietary <CdOrPrtry> [1..1]
8 Level Message Item XML-Tag Presence Type Description Example 4 Code <Cd> [1..1] Code Type of balance. The following balances will be delivered: PRCD: Preceding balance (Opening balance) CLBD: Closing balance CLAV: Available balance FWAV: Future available balance CLBD 2 Amount <Amt Ccy="AAA"> [1..1] Amount Amount of the balance CreditDebitIndicator <CdtDbtInd> [1..1] Code Indicates a credit or a debit: CRDT: Credit DBIT: Debit CRDT 2 Date <Dt> [1..1] 3 Date <Dt> [1..1] DateTime Specifies the date of the balance (e.g. opening date or closing date) DateTime <DtTm> [1..1] DateTime 1 Entry <Ntry> [0..n] Start of a booking line. 2 EntryReference <NtryRef> [0..1] Text Customer Reference Ref123 2 Amount <Amt Ccy="AAA"> [1..1] Amount Amount of the booking CreditDebitIndicator <CdtDbtInd> [1..1] Code Indicates a credit or a debit: CRDT: Credit DBIT: Debit DBIT 2 ReversalIndicator <RvslInd> [0..1] Indicator Returned, rejected or reversed bookings will be indicated by "true". true 2 Status <Sts> [1..1] Code Booking status. BOOK 2 BookingDate <BookgDt> [1..1] 3 Date <Dt> [1..1] DateTime Booking date ValueDate <ValDt> [0..1] 3 Date <Dt> [1..1] DateTime Value date AccountServicerReference <AcctSvcrRef> [1..1] Text Bank reference. D BankTransactionCode <BkTxCd> [1..1] Set of elements used to fully identify the type transaction. 3 Domain <Domn> [1..1] 4 Code <Cd> [1..1] Code Specifies the business area of the transaction. PMNT
9 Level Message Item XML-Tag Presence Type Description Example 4 Family <Fmly> [1..1] 5 Code <Cd> [1..1] Code Specifies the family/category. ICDT 5 SubFamilyCode <SubFmlyCd> [1..1] Code Specifies the subfamily/subcategory. ESCT 3 Proprietary <Prtry> [1..1] 4 Code <Cd> [1..1] Text Austrian Transaction Type (GVC) Issuer <Issr> [1..1] Text Always "APC" (Austrian Payments Council). APC 2 EntryDetails <NtryDtls> [0..1] Detailed information about a batch or single booking. 3 Batch <Btch> [0..1] Information about a batch booking. 4 PaymentInformationIdentification <PmtInfId> [0..1] Text Batch reference. SCT-AT RB 4 NumberOfTransactions <NbOfTxs> [1..1] Number Number of transactions of this batch TransactionDetails <TxDtls> [0..n] Information about a single booking. This structure is repeatable in case of a batch booking where details of each transaction are available. 4 References <Refs> [0..1] 5 AccountServicerReference <AcctSvcrRef> [0..1] Text Bank reference. D EndToEndIdentification <EndToEndId> [0..1] Text Ordering party reference (End to End ID) / TransactionIdentification <TxId> [0..1] Text Transaction reference D MandateIdentification <MndtId> [0..1] Text Mandate reference for SEPA direct debits. MREFCOR-RB ChequeNumber <ChqNb> [0..1] Text Cheque number AmountDetails <AmtDtls> [1..1] 5 InstructedAmount <InstdAmt> [0..1] 6 Amount <Amt [1..1] Amount Original amount and currency of the transaction. Ccy="AAA"> 5 TransactionAmount <TxAmt> [0..1] 6 Amount <Amt [1..1] Amount Booked amount and currency of the transaction. Ccy="AAA"> 6 CurrencyExchange <CcyXchg> [0..1] 7 SourceCurrency <SrcCcy> [1..1] Code Original currency of the transaction GBP ExchangeRate <XchgRate> [1..1] Amount Exchange rate used for the transaction CounterValueAmount <CntrValAmt> [0..1] 6 Amount <Amt Ccy="BBB"> 4 Charges <Chrgs> [0..1] [1..1] Amount Counter value (different currency) amount and currency of the transaction
10 Level Message Item XML-Tag Presence Type Description Example 5 Amount <Amt Ccy="AAA"> [1..1] Amount Amount of charges that were applied CreditDebitIndicator <CdtDbtInd> [1..1] Code Indicates a credit or a debit: CRDT: Credit DBIT: Debit DBIT 5 Type <Tp> [1..1] 6 Proprietary <Prtry> [1..1] 7 Identification <Id> [1..1] Code Specifies the type of the fee. AA2 4 RelatedParties <RltdPties> [0..1] 5 Debtor <Dbtr> [0..1] 6 Name <Nm> [0..1] Text Debtor name. Erwin Schrödinger 5 DebtorAccount <DbtrAcct> [0..1] 6 Identification <Id> [1..1] 7 IBAN <IBAN> [1..1] Identifier Debtor IBAN. AT Other <Othr> [1..1] 8 Identification <Id> [1..1] Text Debtor account number if no IBAN available UltimateDebtor <UltmtDbtr> [0..1] 6 Name <Nm> [0..1] Text Ultimate debtor name Ernst Mach 5 Creditor <Cdtr> [0..1] 6 Name <Nm> [0..1] Text Creditor name. Konrad Lorenz 6 Identification <Id> [0..1] 7 PrivateIdentification <PrvtId> [1..1] 8 Other <Othr> [0..n] 9 Identification <Id> [1..1] Text Creditor ID (Direct Debits) AT15CCM CreditorAccount <CdtrAcct> [0..1] 6 Identification <Id> [1..1] 7 IBAN <IBAN> [1..1] Identifier Creditor IBAN. AT Other <Othr> [1..1] 8 Identification <Id> [1..1] Text Creditor account number if no IBAN available UltimateCreditor <UltmtCdtr> [0..1] 6 Name <Nm> [0..1] Text Ultimate creditor name. Josef Ressel 4 RelatedAgents <RltdAgts> [0..1]
11 Level Message Item XML-Tag Presence Type Description Example 5 DebtorAgent <DbtrAgt> [0..1] 6 FinancialInstitutionIdentification <FinInstnId> [1..1] 7 BIC <BIC> [0..1] Identifier Debtor BIC. RLNWATWW 7 Other <Othr> [0..1] 8 Identification <Id> [1..1] Text Debtor bank code if no BIC available CreditorAgent <CdtrAgt> [0..1] 6 FinancialInstitutionIdentification <FinInstnId> [1..1] 7 BIC <BIC> [0..1] Identifier Creditor BIC RLNWATWW 7 Other <Othr> [0..1] 8 Identification <Id> [1..1] Text Creditor bank code if no BIC available RemittanceInformation <RmtInf> [0..1] 5 Unstructured <Ustrd> [0..1] Text Unstructured remittance information. Payment for goods 5 Structured <Strd> [0..1] 6 CreditorReferenceInformation <CdtrRefInf> [0..1] 7 Type <Tp> [0..1] 8 CodeOrProprietary <CdOrPrtry> [1..1] 9 Code <Cd> [1..1] Code Always "SCOR" (Structured communication reference) SCOR
12 7 Reference <Ref> [0..1] Text Structured remittance information (Payment reference). 4 ReturnInformation <RtrInf> [0..1] 5 Reason <Rsn> [0..1] 6 Code <Cd> [1..1] Code Return reason MD AdditionalTransactionInformation <AddtlTxInf> [0..1] Text Additional Information for the transaction. Die Gutschrift erfolgt Eingang vorbehalten. 1 AdditionalStatementInformation <AddtlStmtInf> [0..1] Text BIC and IBAN of the account IBAN: AT BIC/SWIFTADRESSE: RLNWATWW Legend ISO Index Presence Type Pattern ISO assigned each XML-tag a unique Index. This index is shown for information purposes only. [0..1]: Optional tag. May appear zero times or once. [0..n]: Optional tag. May appear zero or more times. [1..1]: Mandatory tag. Has to appear exactly once. [1..n]: Mandatory tag. Has to appear one or more times. Code: Valid codes are listed in the appropriate section where the tag is described in detail. Tags without any Type are only parents to other tags and do not have content on its own. The pattern either shows the allowed characters in the respective field or the format which will be used for dates or timestamps.
13 GroupHeader (GrpHdr) Figure 2: GroupHeader (GrpHdr) XML-Path: Document/BkToCstmrStmt/GrpHdr Description: The GroupHeader contains general information about the file such as a Message-ID and the creation time of the file. MessageIdentification (MsgId) XML-Path: Document/BkToCstmrStmt/GrpHdr/MsgId Description: Technical reference of transmitted file. AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <MsgId> </MsgId> CreationDateTime (CreDtTm) XML-Path: Document/BkToCstmrStmt/GrpHdr/CreDtTm Description: Creation date and time of the file. ISODateTime Pattern: YYYY-MM-DDThh:mm:ss.sss+hh:mm Example: <CreDtTm> T21:44: :00</CreDtTm>
14 MessageRecipient (MsgRcpt) XML-Path: Document/BkToCstmrStmt/GrpHdr/MsgRcpt Description: Specifies the channel through which the message is sent. Example: <MsgRcpt> <Id> <OrgId> <Othr> <Id>ATMULTICASH</Id> </Othr> </OrgId> </Id> </MsgRcpt> Identification (Id) XML-Path: Document/BkToCstmrStmt/GrpHdr/MsgRcpt/Id OrganisationIdentification (OrgId) XML-Path: Document/BkToCstmrStmt/GrpHdr/MsgRcpt/Id/OrgId Other (Othr) XML-Path: Presence: Document/BkToCstmrStmt/GrpHdr/MsgRcpt/Id/OrgId/Othr [0..n] Identification (Id) XML-Path: Document/BkToCstmrStmt/GrpHdr/ MsgRcpt/Id/OrgId/Othr/Id Description: Name of the channel through which the message is sent. AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <Id> </Id>
15 Statement (Stmt) Figure 3: Statement (Stmt) XML-Path: Description: Presence: Document/BkToCstmrStmt/Stmt This structure contains exactly one account statement. The structure is repeatable. Therefore multiple accounts and statements are possible in a file. [1..n] Identification (Id) XML-Path: Document/BkToCstmrStmt/Stmt/Id Description: Unique technical reference of this account statement. AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <Id> </Id> LegalSequenceNumber (LglSeqNb) XML-Path: Document/BkToCstmrStmt/Stmt/LglSeqNb
16 Description: Statement Number. Number Maximum digits: 18 Example: <LglSeqNb>100</LglSeqNb> CreationDateTime (CreDtTm) XML-Path: Document/BkToCstmrStmt/Stmt/CreDtTm Description: Creation date and time of the statement. ISODateTime Pattern: YYYY-MM-DDThh:mm:ss.sss+hh:mm Example: <CreDtTm> T21:44: :00</CreDtTm> Account (Acct) Figure 4: Account (Acct) XML-Path: Document/BkToCstmrStmt/Stmt/Acct Description: This structure contains the identification (IBAN) of the account for which the statement is generated. Example <Acct> <Id> <IBAN>AT </IBAN> </Id> <Ccy>EUR</Ccy> <Svcr> <FinInstnId>
17 <BIC>RLNWATWW</BIC> </FinInstnId> </Svcr> </Acct> Identification (Id) XML-Path: Document/BkToCstmrStmt/Stmt/Acct/Id IBAN (IBAN) XML-Path: Document/BkToCstmrStmt/Stmt/Acct/Id/IBAN Description: IBAN of the account for which the statement is generated. IBAN2007Identifier Length: (IBAN length) Pattern: [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} Example: <IBAN>AT </IBAN> Currency (Ccy) XML-Path: Document/BkToCstmrStmt/Stmt/Acct/Ccy Description: Currency of the account for which the statement is generated. Text (ISO 4217 currency code) Length: 3 Pattern: [A-Z]{3,3} Example: <Ccy>EUR</Ccy> Servicer (Svcr) XML-Path: Document/BkToCstmrStmt/Stmt/Acct/Svcr FinancialInstitutionIdentification (FinInstnId) XML-Path: Document/BkToCstmrStmt/Stmt/Acct/Svcr/FinInstnId BIC (BIC) XML-Path: Document/BkToCstmrStmt/Stmt/Acct/Svcr/FinInstnId/BIC Description: BIC of the account for which the statement is generated. BICIdentifier Length: 8 or 11 (BIC length)
18 Pattern: Example: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} <BIC>RLNWATWW</BIC> Balance (Bal) Figure 5: Balance (Bal) XML-Path: Description: Presence: Document/BkToCstmrStmt/Stmt/Bal This structure contains the balance information. It includes the amount and the date of the balance. It will be repeated four times with the following balance types: PRCD: Preceding balance (Opening balance) CLBD: Closing balance CLAV: Available balance FWAV: Future available balance [1..n] Example <Bal> <Tp> <CdOrPrtry> <Cd>CLBD</Cd> </CdOrPrtry> </Tp>
19 <Amt Ccy="EUR"> </Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Dt> <Dt> </Dt> </Dt> </Bal> Type (Tp) XML-Path: Document/BkToCstmrStmt/Stmt/Bal/Tp CodeOrProprietary (CdOrPrtry) XML-Path: Document/BkToCstmrStmt/Stmt/Bal/Tp/CdOrPrtry Code (Cd) XML-Path: Document/BkToCstmrStmt/Stmt/Bal/Tp/CdOrPrtry/Cd Description: Type of balance. The following balances will be delivered: PRCD: Preceding balance (Opening balance) CLBD: Closing balance CLAV: Available balance FWAV: Future available balance Code Length: 4 Example: <BIC>CLBD</BIC> Amount (Amt) XML-Path: Document/BkToCstmrStmt/Stmt/Bal/Amt Description: Amount of the balance. The currency will be specified through the attribute Ccy of the <Amt> tag and contains the ISO 4217 currency code. Amount Maximum digits: 18 (Maximum decimal places: 5) Example: <Amt Ccy="EUR"> </Amt> XML-Path: Description: Code CreditDebitIndicator (CdtDbtInd) Document/BkToCstmrStmt/Stmt/Bal/CdtDbtInd Indicates a credit or a debit: CRDT: Credit DBIT: Debit
20 Length: 4 Example: <CdtDbtInd>CRDT</CdtDbtInd> Date (Dt) XML-Path: Document/BkToCstmrStmt/Stmt/Bal/Dt Date (Dt) XML-Path: Document/BkToCstmrStmt/Stmt/Bal/Dt/Dt Description: Specifies the date of the balance. The <Dt> tag will be used for opening-, closing- and available balance (PRCD, CLBD, CLAV). For the future available balance (FWAV) the <DtTm> tag will be used. ISODate Pattern: YYYY-MM-DD Example: <Dt> </Dt> DateTime (DtTm) XML-Path: Document/BkToCstmrStmt/Stmt/Bal/Dt/DtTm Description: Specifies the date of the balance. The <DtTm> tag will only be used for the future available balance (FWAV). For the other balance the <Dt> tag will be used. ISODateTime Pattern: YYYY-MM-DDThh:mm:ss.sss+hh:mm Example: <DtTm> T00:00:00</DtTm>
21 Entry (Ntry) Figure 6: Entry (Ntry) XML-Path: Description: Presence: Document/BkToCstmrStmt/Stmt/Ntry Start of a booking line. [0..n] EntryReference (NtryRef) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryRef Description: Customer reference. AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <NtryRef>Ref123</NtryRef> Amount (Amt) XML-Path: Document/BkToCstmrStmt/Stmt/Bal/Amt Description: Amount of the booking. The currency will be specified through the attribute Ccy of the <Amt> tag and contains the ISO 4217 currency code.
22 Maximum digits: Example: Amount 18 (Maximum decimal places: 5) <Amt Ccy="EUR"> </Amt> CreditDebitIndicator (CdtDbtInd) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/CdtDbtInd Description: Indicates a credit or a debit: CRDT: Credit DBIT: Debit Code Length: 4 Example: <CdtDbtInd>DBIT</CdtDbtInd> ReversalIndicator (RvslInd) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/RvslInd Description: Returned, rejected or reversed bookings will be indicated by true ; otherwise the tag will be absent or false. Indicator Example: <RvslInd>true</RvslInd> Status (Sts) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/Sts Description: Booking status. In the camt.053 message this will always be BOOK. Code Length: 4 Example: <Sts>BOOK</Sts> BookingDate (BookgDt) Figure 7: BookingDate (BookgDt) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/BookgDt Description: Parent tag for the booking date. Only the <Dt> child-tag will be used.
23 Date (Dt) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/BookgDt/Dt Description: Booking date. ISODate Pattern: YYYY-MM-DD Example: <Dt> </Dt> ValueDate (ValDt) Figure 8: ValueDate (ValDt) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/ValDt Description: Parent tag for the value date. Only the <Dt> child-tag will be used. Date (Dt) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/ValDt/Dt Description: Value date. ISODate Pattern: YYYY-MM-DD Example: <Dt> </Dt> AccountServicerReference (AcctSvcrRef) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/AcctSvcrRef Description: Bank reference. AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <AcctSvcrRef> </AcctSvcrRef>
24 BankTransactionCode (BkTxCd) Figure 9: BankTransactionCode (BkTxCd) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/BkTxCd Description: Set of elements used to fully identify the type transaction. Example <BkTxCd> <Domn> <Cd>PMNT</Cd> <Fmly> <Cd>ICDT</Cd> <SubFmlyCd>ESCT</SubFmlyCd> </Fmly> </Domn> <Prtry> <Cd>NTRF</Cd> <Issr>APC</Issr> </Prtry> </BkTxCd> Domain (Domn) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/BkTxCd/Domn Description: Set of elements used to provide the domain, the family and the sub-family of the bank transaction code, in a structured and hierarchical format.
25 Code (Cd) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/BkTxCd/Domn/Cd Description: Specifies the business area of the transaction. Code Length: 4 Example: <Cd>PMNT</Cd> A complete list of domain (business area) codes can be found on the ISO website. From this list, the following domain codes are most common in the camt.053: Code ACMT CAMT PMNT SECU Name Account Management Cash Management Payments Securities To further categorize the transaction, the following family and subfamily codes are used. Family (Fmly) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/BkTxCd/Domn/Fmly Description: Specifies the family and the sub-family of the bank transaction code, within a specific domain, in a structured and hierarchical format. Code (Cd) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/BkTxCd/Domn/Fmly/Cd Description: Specifies the family/category. Code Length: 4 Example: <Cd>ICDT</Cd> A complete list of family (category) codes can be found on the ISO website. From this list, the following family codes are most common in the camt.053: Code ACCB CCRD CNTR CORP DRFT ICCN ICDT ICHQ IDDT MDOP Name Account Balancing Customer Card Transactions Counter Transactions Corporate Action Drafts / Bill Of Orders Issued Cash Concentration Issued Credit Transfers Issued Cheques Issued Direct Debits Miscellaneous Debit Operations
26 OPCL OTHR RCDT RCHQ RDDT SETT Opening & Closing Other Received Credit Transfers Received Cheques Received Direct Debits Trade, Clearing and Settlement To further categorize the transaction, the following subfamily code is used. SubFamilyCode (SubFmlyCd) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/BkTxCd/Domn/Fmly/SubFmlyCd Description: Specifies the subfamily/subcategory. Code Length: 4 Example: <SubFmlyCd>ESCT</SubFmlyCd> A complete list of subfamily (subcategory) codes can be found on the ISO website. From this list, the following subfamily codes are most common in the camt.053: Code ACCC BBDD CCHQ CDPT CHRG COAT COMM CWDL DDFT DMCT DVOP ESCT ESDD FEES INTR ORCQ OTHR PMDD PRDD RRTN SALA STDO STLR TRAD UPDD URDD XBCT ZABA Name Account Closing SEPA B2B Direct Debit Cheque Cash Deposit Charges Corporate Own Account Transfer Commission Cash Withdrawal Discounted Draft Domestic Credit Transfer Dividend Option SEPA Credit Transfer SEPA Core Direct Debit Fees Interest Order Cheque Other Direct Debit Reversal due to Payment Reversal Reversal due to Payment Return Payroll/Salary Payment Standing Order Settlement under reserve Trade Reversal due to Return/Unpaid Direct Debit Direct Debit under reserve Cross-Border Credit Transfer Zero Balancing
27 Proprietary (Prtry) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/BkTxCd/Domn Description: Set of elements to specify the transaction type according to SWIFT MT940. Code (Cd) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/BkTxCd/Prtry/Cd Description: Austrian Transaction Type ( Geschäftsvorfallcode ) Code Length: 3 Example: <Cd>116</Cd> Issuer (Issr) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/BkTxCd/Prtry/Issr Description: Always "APC" (Austrian Payments Council). Code Length: 3 Example: <Issr>APC</Issr> EntryDetails (NtryDtls) Figure 10: EntryDetails (NtryDtls) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls Description: Detailed information about a batch or single booking.
28 Batch (Btch) Figure 11: Batch (Btch) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/Btch Description: Information about a batch booking. Example <Btch> <PmtInfId>SCT-AT RB</PmtInfId> <NbOfTxs> </NbOfTxs> </Btch> PaymentInformationIdentification (PmtInfId) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/Btch/PmtInfId Description: Batch reference. AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <PmtInfId>SCT-AT RB</PmtInfId> NumberOfTransactions (NbOfTxs) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/Btch/NbOfTxs Description: Number of transactions of this batch. Leading zeros will be used. Number Maximum digits: 15 Example: <NbOfTxs> </NbOfTxs>
29 TransactionDetails (TxDtls) Figure 12: TransactionDetails (TxDtls) XML-Path: Description: Presence: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls Information about a single booking. [0..n]
30 References (Refs) Figure 13: References (Refs) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/Refs Description: Set of elements with information about several references. Example <Refs> <EndToEndId> </EndToEndId> <TxId> D </TxId> <MndtId>MAREF-COR1-1UMS-001</MndtId> </Refs> AccountServicerReference (AcctSvcrRef) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/Refs/AcctSvcrRef Description: Bank reference. AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <AcctSvcrRef> </AcctSvcrRef> EndToEndIdentification (EndToEndId) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/Refs/EndToEndId Description: Ordering party reference (End to End ID). AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <EndToEndId> </EndToEndId>
31 TransactionIdentification (TxId) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/Refs/TxId Description: Transaction reference. AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <TxId> D </TxId> MandateIdentification (MndtId) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/Refs/MndtId Description: Mandate reference for SEPA direct debits. AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <MndtId>MAREF-COR1-1UMS-001</MndtId> ChequeNumber (ChqNb) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/Refs/ChqNb Description: Mandate reference for SEPA direct debits. AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <ChqNb>123456</ChqNb> AmountDetails (AmtDtls) Figure 14: AmountDetails (AmtDtls) XML-Path: Description: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/AmtDtls Set of elements to specify different amount related information.
32 Example <AmtDtls> <InstdAmt> <Amt Ccy="EUR">11</Amt> </InstdAmt> </AmtDtls> InstructedAmount (InstdAmt) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt Description: Parent tag to specify the instructed amount and, optionally, an exchange rate. Amount (Amt) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/AmtDtls/InstdAmt/Amt Description: Instructed amount of the booking. The currency will be specified through the attribute Ccy of the <Amt> tag and contains the ISO 4217 currency code. Amount Maximum digits: 18 (Maximum decimal places: 5) Example: <Amt Ccy="EUR"> </Amt> RelatedParties (RltdPties) Figure 15: RelatedParties (RltdPties) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties Description: Set of elements used to identify the parties related to the transaction.
33 Debtor (Dbtr) Figure 16: Debtor (Dbtr) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/Dbtr Description: Party that owes an amount of money to the (ultimate) creditor. Example <Dbtr> <Nm>Erwin Schrödinger</Nm> </Dbtr> Name (Nm) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/Dbtr/Nm Description: Debtor name. AT_Max140Text_Nm Length: 1-70 Pattern: A-Za-z0-9+-/?:().,'äöüßÄÖÜ&>< $ %!=#~;*{}[]@_ ^[Space] Example: <Nm>Erwin Schrödinger</Nm>
34 DebtorAccount (DbtrAcct) Figure 17: DebtorAccount (DbtrAcct) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/DbtrAcct Description: Unambiguous identification of the account of the debtor. Either IBAN (if available) or account number will be shown. Example <DbtrAcct> <Id> <IBAN>AT </IBAN> </Id> </DbtrAcct> Identification (Id) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/DbtrAcct/Id Description: Parent tag for the IBAN or account number of the debtor. IBAN (IBAN) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/DbtrAcct/Id/ IBAN Description: IBAN of the debtors account. IBAN2007Identifier Length: (IBAN length) Pattern: [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}
35 Example: <IBAN>AT </IBAN> Other (Othr) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/DbtrAcct/Id/ Othr Description: Parent tag for the account number of the debtor. Identification (Id) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/DbtrAcct/Id/ Othr/Id Description: Account number of the debtors account. AT_Max34Text Length: 1-34 Pattern: A-Za-z0-9+-/?:().,'äöüßÄÖÜ&>< $ %!=#~;*{}[]@_ ^[Space] Example: <Id> </Id> UltimateDebtor (UltmtDbtr) Figure 18: UltimateDebtor (UltmtDbtr) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/UltmtDbtr Description: Ultimate party that owes an amount of money to the (ultimate) creditor. Example <UltmtDbtr> <Nm>Ernst Mach</Nm> </UltmtDbtr> Name (Nm) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/UltmtDbtr/Nm Description: Ultimate debtor name.
36 AT_Max140Text_Nm Length: 1-70 Pattern: A-Za-z0-9+-/?:().,'äöüßÄÖÜ&>< $ %!=#~;*{}[]@_ ^[Space] Example: <Nm>Ernst Mach</Nm> Creditor (Cdtr) Figure 19: Creditor (Cdtr) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/Cdtr Description: Party to which an amount of money is due. Example <Dbtr> <Nm>Konrad Lorenz</Nm> </Dbtr> Name (Nm) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/Cdtr/Nm Description: Creditor name. AT_Max140Text_Nm Length: 1-70 Pattern: A-Za-z0-9+-/?:().,'äöüßÄÖÜ&>< $ %!=#~;*{}[]@_ ^[Space] Example: <Nm>Konrad Lorenz</Nm>
37 Identification (Id) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/Cdtr/Id Description: Parent tag for the Creditor ID in case of direct debit bookings. PrivateIdentification (PrvtId) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/Cdtr/Id/PrvtId Description: Parent tag for the Creditor ID in case of direct debit bookings. Other (Othr) XML-Path: Description: Presence: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/Cdtr/Id/PrvtId/ Othr Parent tag for the Creditor ID in case of direct debit bookings [0..n] Identification (Id) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/Cdtr/Id/PrvtId/ Othr/Id Description: Creditor ID in case of direct debit bookings. AT_Max35Text Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'äöüßÄÖÜ&>< $ %!=#~;*{}[]@_ ^[Space] Example: <Id> AT15CCM </Id>
38 CreditorAccount (CdtrAcct) Figure 20: CreditorAccount (CdtrAcct) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/CdtrAcct Description: Unambiguous identification of the account of the creditor. Either IBAN (if available) or account number will be shown. Example <CdtrAcct> <Id> <IBAN>AT </IBAN> </Id> </CdtrAcct> Identification (Id) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/CdtrAcct/Id Description: Parent tag for the IBAN or account number of the creditor. IBAN (IBAN) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/CdtrAcct/Id/ IBAN Description: IBAN of the creditors account. IBAN2007Identifier Length: (IBAN length) Pattern: [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}
39 Example: <IBAN>AT </IBAN> Other (Othr) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/CdtrAcct/Id/ Othr Description: Parent tag for the account number of the creditor. Identification (Id) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/CdtrAcct/Id/ Othr/Id Description: Account number of the creditors account. AT_Max34Text Length: 1-34 Pattern: A-Za-z0-9+-/?:().,'äöüßÄÖÜ&>< $ %!=#~;*{}[]@_ ^[Space] Example: <Id> </Id> UltimateCreditor (UltmtCdtr) Figure 21: UltimateCreditor (UltmtCdtr) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/UltmtCdtr Description: Ultimate party to which an amount of money is due. Example <UltmtCdtr> <Nm>Josef Ressel</Nm> </UltmtCdtr> Name (Nm) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdPties/UltmtCdtr/Nm Description: Ultimate creditor name.
40 AT_Max140Text_Nm Length: 1-70 Pattern: A-Za-z0-9+-/?:().,'äöüßÄÖÜ&>< $ %!=#~;*{}[]@_ ^[Space] Example: <Nm>Josef Ressel</Nm> RelatedAgents (RltdAgts) Figure 22: RelatedAgents (RltdAgts) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdAgts Description: Set of elements used to identify the banks related to the transaction. DebtorAgent (DbtrAgt) Figure 23: DebtorAgent (DbtrAgt) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdAgts/DbtrAgt Description: Financial institution servicing an account for the debtor. Either BIC (if available) or local bank code will be shown. Example <DbtrAgt> <FinInstnId> <BIC>RLNWATWW</BIC> </FinInstnId>
41 </DbtrAgt> FinancialInstitutionIdentification (FinInstnId) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdAgts/DbtrAgt/ FinInstnId Description: Parent tag for the BIC or bank code of the debtors bank. BIC (BIC) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdAgts/DbtrAgt/ FinInstnId/BIC Description: BIC of the debtors bank. BICIdentifier Length: 8 or 11 (BIC length) Pattern: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} Example: <BIC>RLNWATWW</BIC> Other (Othr) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdAgts/DbtrAgt/ FinInstnId/Othr Description: Parent tag for the bank code of the debtors bank. Identification (Id) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdAgts/DbtrAgt/ FinInstnId/Othr/Id Description: Bank code of the debtors bank. AT_Max35Text Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'äöüßÄÖÜ&>< $ %!=#~;*{}[]@_ ^[Space] Example: <Id>32000</Id>
42 CreditorAgent (CdtrAgt) Figure 24: CreditorAgent (CdtrAgt) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdAgts/CdtrAgt Description: Financial institution servicing an account for the creditor. Either BIC (if available) or local bank code will be shown. Example <CdtrAgt> <FinInstnId> <Othr> <Id>32000</Id> </Othr> </FinInstnId> </CdtrAgt> FinancialInstitutionIdentification (FinInstnId) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdAgts/CdtrAgt/ FinInstnId Description: Parent tag for the BIC or bank code of the creditors bank. BIC (BIC) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdAgts/CdtrAgt/ FinInstnId/BIC Description: BIC of the creditors bank. BICIdentifier Length: 8 or 11 (BIC length) Pattern: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} Example: <BIC>RLNWATWW</BIC>
43 Other (Othr) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdAgts/CdtrAgt/ FinInstnId/Othr Description: Parent tag for the bank code of the creditors bank. Identification (Id) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RltdAgts/CdtrAgt/ FinInstnId/Othr/Id Description: Bank code of the creditors bank. AT_Max35Text Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'äöüßÄÖÜ&>< $ %!=#~;*{}[]@_ ^[Space] Example: <Id>32000</Id> RemittanceInformation (RmtInf) Figure 25: RemittanceInformation (RmtInf) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RmtInf Description: Set of elements to show remittance information. Only one of the following tags will be used: either unstructured remittance information (<Ustrd>) or structured information (<Strd>) which usually contains a payment reference. Unstructured (Ustrd) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RmtInf/Ustrd Description: Unstructured remittance information. It may contain up to 140 characters of free format text. AT_Max140Text Length: Pattern: A-Za-z0-9+-/?:().,'äöüßÄÖÜ&>< $ %!=#~;*{}[]@_ ^[Space] Example: <Ustrd>Payment for goods</ustrd>
44 Structured (Strd) Figure 26: Structured (Strd) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RmtInf Description: Parent tag which contains all elements for the structured remittance information. The type (which is always SCOR ) and the reference. Example <Strd> <CdtrRefInf> <Tp> <CdOrPrtry> <Cd>SCOR</Cd> </CdOrPrtry> </Tp> <Ref> </Ref> </CdtrRefInf> </Strd> CreditorReferenceInformation (CdtrRefInf) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RmtInf/Strd/CdtrRefInf Description: Parent tag for the creditor reference information (payment reference).
45 Type (Tp) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RmtInf/Strd/CdtrRefInf/ Tp Description: Parent tag for the type of the creditor reference information (payment reference). CodeOrProprietary (CdOrPrtry) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RmtInf/Strd/CdtrRefInf/ Tp/CdOrPrtry Description: Parent tag for the code of the creditor reference information (payment reference). Code (Cd) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RmtInf/Strd/CdtrRefInf/ Tp/CdOrPrtry/Cd Description: Code of the creditor reference information (payment reference). This code will always be SCOR (Structured communication reference). Code Length: 4 Example: <Cd>SCOR</Cd> Reference (Ref) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RmtInf/Strd/CdtrRefInf/ Ref Description: Payment reference. AT_Max35Text_REF Length: 1-35 Pattern: A-Za-z0-9+-/?:().,'[Space] Example: <Ref> </Ref>
46 ReturnInformation (RtrInf) Figure 27: ReturnInformation (RtrInf) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RtrInf Description: Set of elements to specify the reason for a returned transaction. Example <RtrInf> <Rsn> <Cd>MD01</Cd> </Rsn> </RtrInf> Reason (Rsn) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RtrInf/Rsn Description: Parent tag for the return reason code. Code (Cd) XML-Path: Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/RtrInf/Rsn/Cd Description: Return reason code. Code Length: 4 Example: <Cd>MD01</Cd> The most used codes are listed in the following table. The table also lists if the code can be used for a returned SEPA Credit Transfer (SCT), SEPA Direct Debit Core (SDD CORE) or SEPA Direct Debit B2B (SDD B2B).
47 Code SCT SDD CORE SDD B2B Description AC01 X X X Incorrect account number AC04 X X X Closed account number AC06 X X X Blocked account AC13 X Invalid debtor account type AG01 X X X Transaction forbidden AG02 X X X Invalid bank operation code AM04 X X Insufficient funds AM05 X X X Duplication BE04 X X Missing creditor address BE05 X X Unrecognised initiating party FF05 X Invalid local instrument code FOCR X Following cancellation request MD01 X X No mandate MD06 X Refund request by end customer MD07 X X End customer deceased MS02 X X X Customer generated MS03 X X X Reason not specified RC01 X X X Bank identifier incorrect RR01 X X X Missing debtor account RR02 X X X Missing debtors name or address RR03 X X X Missing creditors name or address RR04 X X X Regulatory reason SL01 X X Specific service offered by debtor bank AdditionalStatementInformation (AddtlStmtInf) XML-Path: Document/BkToCstmrStmt/Stmt/AddtlStmtInf Description: Used to carry further information about a statement. Used to deliver BIC and IBAN of the account for which the statement is generated. AT_Max500Text Length: Pattern: A-Za-z0-9+-/?:().,'äöüßÄÖÜ&>< $ %!=#~;*{}[]@_ ^[Space] Example: <AddtlStmtInf>IBAN: AT BIC/SWIFTADRESSE: RLNWATWW</AddtlStmtInf>
48 Example <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt " xmlns:xsi=" <BkToCstmrStmt> <GrpHdr> <MsgId> </MsgId> <CreDtTm> T21:44: :00</CreDtTm> <MsgRcpt> <Id> <OrgId> <Othr> <Id>ATMULTICASH</Id> </Othr> </OrgId> </Id> </MsgRcpt> </GrpHdr> <Stmt> <Id> </Id> <LglSeqNb>105</LglSeqNb> <CreDtTm> T21:44: :00</CreDtTm> <Acct> <Id> <IBAN>AT </IBAN> </Id> <Ccy>EUR</Ccy> <Svcr> <FinInstnId> <BIC>RLNWATWW</BIC> </FinInstnId> </Svcr> </Acct> <Bal> <Tp> <CdOrPrtry> <Cd>PRCD</Cd> </CdOrPrtry> </Tp> <Amt Ccy="EUR"> </Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Dt> <Dt> </Dt> </Dt> </Bal> <Bal> <Tp> <CdOrPrtry> <Cd>CLBD</Cd> </CdOrPrtry> </Tp> <Amt Ccy="EUR"> </Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Dt> <Dt> </Dt>
49 </Dt> </Bal> <Bal> <Tp> <CdOrPrtry> <Cd>FWAV</Cd> </CdOrPrtry> </Tp> <Amt Ccy="EUR"> </Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Dt> <DtTm> T00:00:00</DtTm> </Dt> </Bal> <Bal> <Tp> <CdOrPrtry> <Cd>CLAV</Cd> </CdOrPrtry> </Tp> <Amt Ccy="EUR"> </Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Dt> <Dt> </Dt> </Dt> </Bal> <Ntry> <NtryRef>SCT-AT RB</NtryRef> <Amt Ccy="EUR">4513.5</Amt> <CdtDbtInd>DBIT</CdtDbtInd> <RvslInd>false</RvslInd> <Sts>BOOK</Sts> <BookgDt> <Dt> </Dt> </BookgDt> <ValDt> <Dt> </Dt> </ValDt> <AcctSvcrRef> </AcctSvcrRef> <BkTxCd> <Domn> <Cd>PMNT</Cd> <Fmly> <Cd>ICDT</Cd> <SubFmlyCd>ESCT</SubFmlyCd> </Fmly> </Domn> <Prtry> <Cd>NTRF</Cd> <Issr>APC</Issr> </Prtry> </BkTxCd> <NtryDtls> <Btch> <PmtInfId>SCT-AT RB</PmtInfId> <NbOfTxs> </NbOfTxs> </Btch> <TxDtls> <Refs>
50 <TxId> </TxId> </Refs> <AmtDtls> <InstdAmt> <Amt Ccy="EUR">4513.5</Amt> </InstdAmt> </AmtDtls> <RmtInf> <Ustrd>DTEIN SCT-AT RB Anzahl Umsätze </Ustrd> </RmtInf> </TxDtls> </NtryDtls> </Ntry> <Ntry> <Amt Ccy="EUR">11</Amt> <CdtDbtInd>DBIT</CdtDbtInd> <RvslInd>false</RvslInd> <Sts>BOOK</Sts> <BookgDt> <Dt> </Dt> </BookgDt> <ValDt> <Dt> </Dt> </ValDt> <AcctSvcrRef>D </AcctSvcrRef> <BkTxCd> <Domn> <Cd>PMNT</Cd> <Fmly> <Cd>OTHR</Cd> <SubFmlyCd>OTHR</SubFmlyCd> </Fmly> </Domn> <Prtry> <Cd>NDDT</Cd> <Issr>APC</Issr> </Prtry> </BkTxCd> <NtryDtls> <TxDtls> <Refs> <TxId> D </TxId> <MndtId>mandref</MndtId> </Refs> <AmtDtls> <InstdAmt> <Amt Ccy="EUR">11</Amt> </InstdAmt> </AmtDtls> <RltdPties> <Cdtr> <Nm> Schuberth</Nm> <Id> <PrvtId> <Othr> <Id>AT </Id> </Othr> </PrvtId>
51 </Id> </Cdtr> <CdtrAcct> <Id> <IBAN>AT </IBAN> </Id> </CdtrAcct> </RltdPties> <RltdAgts> <CdtrAgt> <FinInstnId> <BIC>RLNWATWW</BIC> </FinInstnId> </CdtrAgt> </RltdAgts> </TxDtls> </NtryDtls> </Ntry> <Ntry> <Amt Ccy="EUR">7.6</Amt> <CdtDbtInd>DBIT</CdtDbtInd> <RvslInd>false</RvslInd> <Sts>BOOK</Sts> <BookgDt> <Dt> </Dt> </BookgDt> <ValDt> <Dt> </Dt> </ValDt> <AcctSvcrRef>D </AcctSvcrRef> <BkTxCd> <Domn> <Cd>ACMT</Cd> <Fmly> <Cd>MDOP</Cd> <SubFmlyCd>CHRG</SubFmlyCd> </Fmly> </Domn> <Prtry> <Cd>NCHG</Cd> <Issr>APC</Issr> </Prtry> </BkTxCd> <NtryDtls> <TxDtls> <Refs> <TxId> D </TxId> </Refs> <AmtDtls> <InstdAmt> <Amt Ccy="EUR">7.6</Amt> </InstdAmt> </AmtDtls> <RmtInf> <Ustrd>Rückleitungsentgelt zu SEPA-Rückleitung am EUR 7,60 Entgelt zu Transaktion</Ustrd> </RmtInf> </TxDtls> </NtryDtls>
52 </Ntry> <AddtlStmtInf>IBAN: AT RLNWATWW</AddtlStmtInf> </Stmt> </BkToCstmrStmt> </Document> BIC/SWIFTADRESSE: This XML camt.053 message contains one statement with three movements. For a better understanding of the transmitted information, the same statement is now presented with all the detailed information which is available in the XML message in the following more userfriendly way:
53 Annex SWIFT character set a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z / -? : ( )., ' + { } CR LF Space Resources ISO Schema - camt xsd ISO Schema - camt xsd p ISO Schema - camt xsd ISO Message Definition Report - camt.05x: ISO Bank transaction code set: Austrian Schema - ISO.camt austrian.003.xsd Austrian Schema - ISO.camt austrian.003.xsd Austrian Schema - ISO.camt austrian.003.xsd
Message Definition Report Part 1
Standards Bank To Customer Cash Management November 2018 Standards MX Message Definition Report Part 1 This document provides information about the use of the messages for Bank-to-Customer Cash Management
More informationING Group CAMT Format Description
ING Group CAMT.053.001.02 Format Mijn ING Zakelijk The Netherlands June 2017 Document version 1.2 Document version history Version Date Change description 1.0 11-03-2016 Initial version 1.1 28-03-2017
More informationISO Message Implementation Guide for Cash Management Reports
ISO 20022 Message Implementation Guide for Cash Management Reports CAMT052 CAMT053 CAMT054 CAMT060 Version: 1.5 Issue date: 9 July 2015 Author: Swedbank Table of Contents 1. Introduction 2. Bank To Customer
More informationMessage Definition Report Part 1
Standards Bank-to-Customer Cash Management November 2015 Standards MX Message Definition Report Part 1 This document provides information about the use of the messages for Bank-to-Customer Cash Management
More informationISO Credit Notification
ISO 20022 Credit Notification camt.054 version 2 Version 1.0.0 Publishing date 30 November 2012 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL RULES... 4 2.1
More informationThe Nets camt.054 service is based on the contents of the Egiro service for credit notifications and on Dirrem accounting data for the Debit part.
Index Element XML Tag Occurrence Type UseInIG Definition BSK Rules Nets Usage Document Document Document Document BkToCstmrDbtCdtN1..1 BankToCustomerDebitCreditNotificationV02 The Bank-to-Customer Debit
More informationImplementation guide. ISO Credit Notification camt.054 version 2
Implementation guide ISO 20022 Credit Notification camt.054 version 2 Version 1.1.1 Publishing date 13 April 2018 Implementation guide Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2
More informationThe Nets camt.054 service is based on the contents of the Egiro service for credit notifications and on Dirrem accounting data for the Debit part.
Index Element XML Tag Occurrence Type UseInIG Definition BSK Rules Nets Usage Document Document Document Document BkToCstmrDbtCdtN1..1 BankToCustomerDebitCreditNotificationV02 The Bank-to-Customer Debit
More informationXML Format of Account Statements Supported by KBSK, Effective as from 25 February 2016
XML Format of Account Statements Supported by KBSK, Effective as from 25 February 2016 1/20 Contents: 1 Introduction... 4 1.1 Purpose of the Document... 4 1.2 Information on the Document... 4 1.3 Rules
More informationPKO Webconnect Context CZ - Export Formats.
PKO Webconnect Context CZ - Export Formats. March 2017 TABLE OF CONTENTS EXPORT FORMATS IN PKO WEBCONNECT CONTEXT CZ... 3 EXPORT TO CSV FORMAT... 3 List of Possible Export Sets to CSV Format From WebConnect
More informationImplementation guide. ISO Extended Account Statement camt.053 version 2
Implementation guide ISO 20022 Extended Account Statement camt.053 version 2 Version 1.2.2 Published 13 April 2018 Implementation guide Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3
More informationXML Message for SEPA Direct Debit Initiation
XML Message for SEPA Direct Debit Initiation Core and Business-to-Business Implementation Guidelines Version 1.4 Table of Contents 1 Introduction... 4 1.1 SEPA Direct Debit definition... 5 1.2 Message
More informationpain EPC; 1.0
Message Implementation Guideline pain.008.001.02 - EPC; 1.0 Model: pain.008.001.02 - EPC Version: 1.0 Issue date: June 2015 Author: Credit Suisse Message Overview... 2 Message Details... 6 Components...
More informationDanish Inpayment Form 01, 04, 15, 71, 73, 75
Danish Inpayment Form 01, 04, 15, 71, 73, 75 Change log Version no. Date Change 0.1 15.07.2014 New design 0.2 29.10.2014 Remarks in English CGI rules added in Remarks Danish Clearing rules for addresses.
More informationSDD Bulk Payments XML File Format
www.aib.ie/sepa SDD Bulk Payments XML File Format This document is the property of AIB Group. No official or other user of this document, may, without the prior written permission of the Bank, disseminate
More informationXML message for Credit Transfer Initiation
XML message for Credit Transfer Initiation Implementation Guidelines Version 2.5 This document is greatly inspired by the Febelfin one. Table of Contents XML message for Credit Transfer Initiation... 1
More informationXML message for Credit Transfer Initiation
XML message for Credit Transfer Initiation Implementation Guidelines Version 2.4 This document is greatly inspired by the Febelfin one. Table of Contents XML message for Credit Transfer Initiation... 1
More informationOrders in ISO format for issuance of transfers and cheques in euros
Orders in ISO 20022 format for issuance of transfers and cheques in euros Series of banking standards and procedures Implementation Guide Adapted to version 1.0 RB 2017 SEPA Credit Transfer November 2017
More informationXML Message for European Direct Debit Initiation
XML Message for European Direct Debit Initiation Core and Business-to-Business Implementation Guidelines Version 4.1a Belgian Financial Sector Federation rue d Arlon/Aarlenstraat, 82 B-1040 Brussels http://www.febelfin.be
More informationOrders in ISO format for transfers, checks, promissory notes and direct debit payments, in euros and other currencies
Confidence, social commitment and quality Orders in ISO 20022 format for transfers, checks, promissory notes and direct debit payments, in euros and other currencies February 2016 INDEX Page INTRODUCTION...
More informationAppendix 1 Bank Transaction Codes Account statement Standard & Extended
1 of 6 Appendix 1 Bank Transaction Codes Account statement Standard & Extended 1.1 Account Statement Standard & Extended Entry level Batch booking entries 1 In case batch (lump-sum) booking applies by
More informationC2B - Customer to Bank Services
SEPA Data Format (XML) Version: 02.02 Status: Final Go live date: 2016-02-01 Related Documents Reference Title Source EPC132-08 Implementation Guidelines SEPA CT C2B European Payments Council EPC130-08
More informationOrders in ISO format for issuance of transfer in euros and other currencies, cheques, promissory notes and direct debit payments in euros
Confianza, compromiso social y calidad Orders in ISO 20022 format for issuance of transfer in euros and other currencies, cheques, promissory notes and direct debit payments in euros February 2018 CHANGE
More informationISO Customer-to-Bank messages usage guidelines
ISO 20022 Customer-to-Bank messages usage guidelines 1 Contents 1. Foreword... 3 2. Message description... 3 3. Message structure... 4 3.1. Message structure... 4 3.2. Character set... 5 3.3. Message pain.001.001.03...
More informationISO Cash Management
ISO 20022 Cash Management Swiss Implementation Guidelines for Customer-Bank Messages (Reports) Bank-to-Customer Account Report (camt.052) Bank-to-Customer (camt.053) Bank-to-Customer Debit/Credit Notification
More informationSwiss Payment Standards 2018
2018 Swiss Implementation Guidelines for Customer-Bank Messages (Reports) Bank-to-Customer Account Report (camt.052) Bank-to-Customer (camt.053) Bank-to-Customer Debit/Credit Notification (camt.054) Version
More informationISO Customer Direct Debit Initiation
ISO 20022 Customer Direct Debit Initiation pain.008.001.02 Version 1.0.1 Publishing date 10 January 2017 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL INFORMATION...
More informationXML Message for European Direct Debit Initiation
XML Message for European Direct Debit Initiation Core and Business-to-Business Implementation Guidelines Version 3.0.a Belgian Financial Sector Federation rue d Arlon/Aarlenstraat, 82 B-1040 Brussels http://www.febelfin.be
More informationXML message for Payment Initiation Implementation Guideline
XML message for Payment Initiation Implementation Guideline Version 1.3 Version 1.3 Changes Updated 20160901 Customer Credit Transfer: Message element name is changed to Customer Credit Transfer Initiation
More informationXML message for Credit Transfer Initiation
XML message for Credit Transfer Initiation Implementation Guidelines Version 3.2.a (see updates in annex 3) Table of Contents 1 Introduction... 4 1.1 Coverage... 5 1.2 Use of these Guidelines... 6 1.3
More informationImplementation guide. ISO CustomerPaymentStatusReport pain.002 version 3
ISO 20022 CustomerPaymentStatusReport pain.002 version 3 Version 1.0.0 Publishing date 30 August 2016 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL RULES...
More informationBank Connect. Customer Credit Transfer Pain Table of Contents
Bank Connect Customer Credit Transfer Pain 001.001.03 Table of Contents Introduction... 2 Scope... 2 Character set... 2 Change log... 3 Explanation on format usage... 5 1 Introduction This Danish Message
More informationXML Message for Payment Status Report
XML Message for Payment Status Report Implementation Guidelines Version 1.1 Table of Contents Table of Contents... 2 1 Introduction... 5 1.1 Coverage... 6 1.2 Use of these Guidelines... 7 1.3 Character
More informationSEPA Credit Transfer Instructions
SEPA Credit Transfer Instructions STANDARD ISO 20022 pain.001.001.03 Guideline for SEPA Credit Transfer Instructions transmitted to Société Générale France Version: August 2015 ORDRE DE VIREMENT SEPA STANDARD
More informationRules for the use of ISO standard data format in LUMINOR-TO-CUSTOMER statement
Rules for the use of ISO 20022 standard data format in LUMINOR-TO-CUSTOMER statement Version 1.4 September 2017 References No Description Reference 1 Guidelines on the conversion of the LITAS ESIS data
More informationMutual Fund Trailer Fee Payments Market Practice
Mutual Fund Trailer Fee Payments Market Practice ISITC Payments Working Group DISCLAIMER This market practice document has been developed by the International Securities Association for Institutional Trade
More informationSwiss Payment Standards 2018
Swiss Payment Standards 2018 Swiss Implementation Guidelines for Customer-Bank Messages SEPA Direct Debit (SEPA Direct Debit Scheme) Customer Direct Debit Initiation (pain.008) Version 2.6, with effect
More informationISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages SEPA Direct Debit (SEPA Direct Debit Scheme)
ISO 20022 Payments for Customer-Bank Messages SEPA Direct Debit (SEPA Direct Debit Scheme) Version 2.5.2 21.08.2017 General note Any suggestions or questions relating to this document should be addressed
More informationISO XML messages for Customer Credit Transfer and Account Statement. Contents. Implementation Guideline
ISO 20022 XML messages for Customer Credit Transfer and Account Statement Implementation Guideline Contents Introduction... 2 1. Message content of the Customer Credit Transfer... 3 2. Additional description
More informationXML message for Payment Initiation Implementation Guideline
XML message for Payment Initiation Implementation Guideline Version 1.2 Version 1.2 Changes Updated 20130916 New column XML Tag added to the Customer Credit Transfer and Payment Status Report tables Version
More informationRules for the use of ISO standard data format in DNB BANK-TO-CUSTOMER statement
Rules for the use of ISO 20022 standard data format in DNB BANK-TO-CUSTOMER statement Version 1.3 April 2016 References No Description Reference 1 Guidelines on the conversion of the LITAS ESIS data exchange
More informationFormat Specification
Format Specification ISO20022-pain.001.001.03 mbank S.A. 2017.11.27 Version 1.6 1. General Info... 3 2. Short review of pain.001.001.03 file, format requirements and processing mechanism... 3 3. Type of
More informationCash-Securities Split Settlement Market Practice
Cash-Securities Split Settlement Market Practice Disclaimer The Securities Market Practice Group is a group of experts who devote their time on a voluntary basis to define global and local market practices
More informationFormat description CT-XML import
Format description CT-XML import Rabo Cash Management Rabobank Format description CT-XML import 2 October 2017 Version 1.02 1 Contents 1 CT-XML import format... 3 1.1 CT-XML import format description...
More informationXML message for Credit Transfer Initiation
XML message for Credit Transfer Initiation Implementation Guidelines Version 2.0 XML message for Credit Transfer Initiation 2 Table of Contents 1 Introduction... 4 1.1 Coverage... 5 1.2 Use of these Guidelines...
More informationImplementation guide. ISO CustomerPaymentStatusReport pain.002 version 2
ISO 20022 CustomerPaymentStatusReport pain.002 version 2 Version 1.0.0 Publishing date 30 August 2016 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL RULES...
More informationISO XML message for Payment Initiation Implementation Guideline. Version 1.0 Estonia
ISO 20022 XML message for Payment Initiation Implementation Guideline Version 1.0 Estonia Approved by payment standards working group of Estonian Banking Association 31.01.2013 Table of contents Table
More informationUBS Implementation Guidelines
US Implementation Guidelines Swiss Payment Standards for ash Management Reports camt.053.001.04 - SPS Version 1.6 US Version 1.0 August 2018 US Implementation Guidelines Swiss Payment Standards for ash
More informationDifferences BTL91and Generic Payment File. RCM, RIB Pro, RDC and SWIFT FileAct
Differences BTL91and Generic Payment File RCM, RIB Pro, RDC and SWIFT FileAct Contents 1 GENERAL INFORMATION 3 2 INTRODUCTION 3 3 GENERAL DIFFERENCES 4 4 DESCRIPTION OF THE DIFFERENCES 6 APPENDIX: CHANGE
More informationpain ch-six cs-st; 1
Message Implementation Guideline Model: pain.002.001.03-ch-six-1.5. Version: 1 Issue date: November 2016 Author: Credit Suisse (Switzerland) Ltd. Message Overview... 2 Message Details... 5 Components...
More informationSEPA B2B DIRECT DEBIT SCHEME ADVANCE MANDATE INFORMATION SERVICE IMPLEMENTATION GUIDELINES
Doc: EPC315-10 26 January 2015 (Version 7.0 Approved) EPC SEPA B2B DIRECT DEBIT SCHEME ADVANCE MANDATE INFORMATION SERVICE IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets
More informationFormat Specification
Format Specification ISO20022-pain.001.001.03 mbank S.A. 2016.11.28 Version 1.5 1. General Info... 3 2. Short review of pain.001.001.03 file, format requirements and processing mechanism... 3 3. Type of
More informationFormat Specification
Format Specification ISO20022-pain.001.001.03 mbank S.A. Version 1.7 / 2018-04-13 1. General Info... 3 2. Short review of pain.001.001.03 file, format requirements and processing mechanism... 3 3. Type
More informationpain MandateCancellationRequestV03
Corporate egateway Message Implementation Guideline MandateCancellationRequestV03 MIG version: 1.2 : 01-10-2018 2 of 12 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references... 3
More informationpain MandateInitiationRequestV03
Corporate egateway Message Implementation Guideline MandateInitiationRequestV03 MIG version: 1.2 : 11-02-2017 2 of 14 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references... 4 4.
More informationISO Message Implementation Guide for Payment Initiation
ISO 20022 Message Implementation Guide for Payment Initiation Pain001 Pain002 Version: 1.7 Issue date: 12 January 2017 Author: Swedbank Table of Contents 1. Introduction 2. Customer Credit Transfer Initiation
More informationAddendum on the XML message for SEPA Credit Transfer Initiation (PAIN)
Addendum on the XML message for SEPA Credit Transfer Initiation (PAIN) Version 6.4 July 2013 Table of content 1 Introduction 5 1.1 Character Set 6 1.2 Change history 6 2 Message item description 7 1.0
More informationCorporate Payments Service Payments from Latvia, Lithuania and Estonia example appendix
Corporate Payments Service Payments from Latvia, Lithuania and Estonia example appendix pain.001 version 3 pain.002 version 3 pain.006 version 1 May 2013 Content 1. Background... 4 2. About Corporate Payments
More informationpain CustomerDirectDebitInitiationV02
Corporate egateway Message Implementation Guideline CustomerDirectDebitInitiationV02 MIG version: 1.2 : 01-10-2018 2 of 13 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Nordea usage of 20022
More informationXML message for Payment Initiation Implementation Guideline. Pain001. Version 1.0
XML message for Payment Initiation Implementation Guideline Pain001 Version 1.0 1 Version history Version Changes Date 1.0 First version 21.09.2015 1.1 ControlSum field is mandatory in GroupHeader and
More informationSwedbank Sweden's MIG Credit Transfer and Payment Status (pain.001, pain.002) Swedbank AB (publ) (28)
Swedbank Sweden's MIG Credit Transfer and Payment Status (pain.001, pain.002) Swedbank AB (publ) 2015-11-17 1 (28) ver15.02.01 Introduction This document describes the usage on a set of ISO20022 messages.
More informationpain CustomerCreditTransferInitiationV03
Corporate Access Payables Changes in Message Implementation Guideline pain.001.001.03 CustomerCreditTransferInitiationV03 Changes in version 1.3 since version 1.2 MIG version: 1.3 : 20-06-2016 Please refer
More informationSEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES
Doc: EPC131-08 17 November 2011 (Version 4.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets
More informationCZECH REPUBLIC INSIDEBUSINESS PAYMENTS CZECH REPUBLIC ANNEX. File formats and validations. Contents
INSIDEBUSINESS PAYENTS CZECH REPUBLIC ANNEX File formats and validations Contents Validation of fields 2 CFD File Format 3 CFA File Format 5 Single credit transfer format T103 8 Single European Credit
More informationSEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES
Doc: EPC131-08 1 November 2010 (Version 3.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference This document sets out the
More informationCodification Annex. ING Format Descriptions Structured MT940 & MT942 Camt.052 & Camt.053
Codification Annex ING Format Descriptions Structured MT940 & MT942 Camt.052 & Camt.053 Strategic InsideBusiness Connect InsideBusiness Payments InsideBusiness Payments CEE SwiftNet FIN SwiftNet FileAct
More informationCorporate Payments Service. Example appendix - pain.001 version 3
Corporate Payments Service Example appendix - pain.001 version 3 January 2018 Content 1 Background... 3 2 About Corporate Payments Service... 3 3 Message structure... 3 4 Example of the payment initiation
More informationSwiss Payment Standards 2018
Swiss Payment Standards 2018 Swiss Business Rules for Payments and Cash Management for Customer-Bank Messages Version 2.7, with effect from November 2018 Version 2.7 18.12.2017 General note Any suggestions
More informationSEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES
Doc: EPC130-08 1 November 2010 (Version 5.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference This document sets out the rules for implementing
More informationSEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES
Doc: EPC130-08 30 October 2009 (Version 3.4 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for
More informationSEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES
Doc: EPC114-06 30 November 2012 (Version 7.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing
More informationUBS Implementation Guidelines
US Implementation Guidelines Swiss Recommendations for credit transfers pain.001.001.03.ch.02 - SR Version 1.5.1 US Version 1.0 July 2016 US Implementation Guidelines Swiss Recommendations for credit transfers
More informationSEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES
Doc: EPC301-07 30 November 2012 (Version 5.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the
More informationSEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES
Doc: EPC131-08 26 January 2015 (Version 7.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out
More informationFunds Order Processing
UK Funds Market Practice Group Funds Order Processing Status: Final version Preparation date: August 2009 Author: UK NMPG Steve Wallace, Idea Group Ltd Version 01.00.00 FINAL UK NMPG Orders 2009 Version
More informationDanske Bank Baltic ISO XML messages for Payment Initiation and Cash Management Implementation Guideline. Pain001 Pain002 Camt052 Camt053 Camt054
Danske Bank Baltic ISO 20022 XML messages for Payment Initiation and Cash Management Implementation Guideline Pain001 Pain002 Camt052 Camt053 Camt054 Version 1.0 1 Version history Version Changes Date
More informationCorporate Payments Service. Appendix on Request for Transfer
Corporate Payments Service Appendix on Request for Transfer March 2018 Content 1 Background... 2 2 Payments with Request for Transfer orders... 2 3 Messages used... 3 3.1 Payment order from a customer
More informationAddendum on the XML message for SEPA Direct Debit Initiation (PAIN)
Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) Version 6.0 - May 2012 Table of content 1 Introduction 5 1.1 Character Set 6 1.2 Change history 6 2 Message item description 7 1.0 Group
More informationpain CustomerCreditTransferInitiationV03
20022 Message Implementation Guidelines for payment initiation pain.001.001.03 CustomerCreditTransferInitiationV03 Version: 0.2 : Author: Luminor Bank AB 31/08/2015 2 of 17 Table of contents 1. Introduction...
More informationCorporate Payments. Example appendix, pain.001 version 2. March 2018
Corporate Payments Example appendix, pain.001 version 2 March 2018 Content 1 Background... 3 2 About Corporate Payments Service... 3 3 The message structure... 3 4 Example of the payment initiation message...
More informationVersion OUTGOING PAYMENTS SERVICE DESCRIPTION. Pain Pain
Version 2.6 15.1.2018 OUTGOING PAYMENTS SERVICE DESCRIPTION Pain001.001.03 Pain002.001.03 2 (54) CONTENTS VERSION INFORMATION... 4 1 OUTGOING PAYMENTS, APPLICATION GUIDELINE... 5 1.1 ISO 20022 MESSAGE
More informationABN AMRO addendum on the XML Message for European Direct Debit Initiation
ABN AMRO addendum on the XML Message for European Direct Debit Initiation Table of contents 1 Introduction...4 2 Message description...5 1.0 Group Header... 5 1.1 Message Identification... 5 1.2 Creation
More informationVersion 8.0 final for Core rulebook 9.1 and B2B rulebook 7.1
Nets Denmark A/S Lautrupbjerg 10 P.O. 500 DK-2750 Ballerup T + 45 44 68 44 68 F 45 44 86 09 30 www.nets.eu CVR-nr. 20016175 17 August 2016 SEPA Direct Debit Interface Description RBF/LP edition Version
More informationService description Corporate Access Payables Appendix Denmark
Service description Corporate Access Payables Appendix Denmark Page 2 of 21 Table of contents 1 APPENDIX - DENMARK... 3 2 GENERAL OVERVIEW OF THE DANISH PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT
More informationSEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES
Doc: EPC131-08 30 November 2012 (Version 5.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets
More informationService description. Corporate Access Payables Appendix Norway
Service description Corporate Access Payables Appendix Norway Page 2 of 16 Table of contents 1 APPENDIX NORWAY... 3 2 GENERAL OVERVIEW OF THE NORWEGIAN PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT
More informationSEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES
Doc: EPC130-08 30 November 2012 (Version 7.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for
More informationMessage Item XML Tag Occurrence Data Type / Code Message Item Definition T2S Mapping Use in T2S Business Rules SCOPE
SecuritiesTransactionCancellat ionrequeststatusadvicev02 Document Document Last updated: 30/09/2013 SctiesTxCxlReqS tsadvc 1..1 SecuritiesTransactionCancella tionrequeststatusadvicev03 SCOPE An account
More informationMulti-Currency Bulk Payments XML File Format
www.aib.ie/sepa Multi-Currency Bulk Payments XML File Format This document is the property of AIB Group. No official or other user of this document, may, without the prior written permission of the Bank,
More informationMulti-Currency Bulk Payments XML File Format
www.aib.ie/sepa Multi-Currency Bulk Payments XML File Format This document is the property of AIB Group. No official or other user of this document, may, without the prior written permission of the Bank,
More informationService description. Corporate Access Payables Appendix Denmark
Service description Corporate Access Payables Appendix Denmark Page 2 of 19 Table of contents 1 APPENDIX - DENMARK... 3 2 GENERAL OVERVIEW OF THE DANISH PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT
More informationService description. Corporate Access Payables Appendix Norway
Service description Corporate Access Payables Appendix Norway Table of contents Page 2 of 13 1 APPENDIX NORWAY... 3 2 GENERAL OVERVIEW OF THE NORWEGIAN PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT
More information[SLOVAK REPUBLIC] ANNEX. File formats and validations. Validation of fields 2. SKI File Format - Domestic payment 3. SKI File Format - Direct debit 5
ANNEX File formats and validations Validation of fields 2 SKI File Format - Domestic payment 3 SKI File Format - Direct debit 5 [SLVAK REPUBLIC] MT100 File Format 7 Single credit transfer format MT103
More informationJames Wills Standards - Banking Initiatives SWIFT Pan Americas. David Repking Information Rpting Product Mgmt J. P. Morgan Chase
James Wills Standards - Banking Initiatives SWIFT Pan Americas David Repking Information Rpting Product Mgmt J. P. Morgan Chase The new standard that replaces the old BAI2 Cash Management reporting Specification
More informationSEPA DIRECT DEBIT CORE RULEBOOK CHANGE REQUEST - PUBLIC CONSULTATION DOCUMENT COVER PAGE
EPC012-16 Version 1.0 05 April 2016 SEPA DIRECT DEBIT CORE RULEBOOK CHANGE REQUEST - PUBLIC CONSULTATION DOCUMENT COVER PAGE The Single Euro Payments Area (SEPA) payment schemes, as set out in the SEPA
More informationCode list. Change log.
Page 1 of 23 Change log. Version Date Edit 1 10.11.2003 Document created 2 06.04.2009 Updated with new codes Updated with code 005, 006, 157, 306, 366, 711, 742, 743, 770, 862, 863, 864, 865, 866, 867,
More informationSEPA DIRECT DEBIT B2B RULEBOOK CHANGE REQUEST - PUBLIC CONSULTATION DOCUMENT COVER PAGE
EPC013-16 Version 1.0 05 April 2016 SEPA DIRECT DEBIT B2B RULEBOOK CHANGE REQUEST - PUBLIC CONSULTATION DOCUMENT COVER PAGE The Single Euro Payments Area (SEPA) payment schemes, as set out in the SEPA
More informationING Reference Guide. Structured MT940 & MT942
ING Reference Guide Structured MT940 & MT942 (Version 4) Strategic InsideBusiness Connect InsideBusiness Payments InsideBusiness Payments CEE SwiftNet FIN SwiftNet FileAct Telelink@Isabel EBICS Document
More informationSWIFT for Corporates
SWIFTStandards MT Implementation Guide This document describes the rules users must follow when sending or receiving SWIFTStandards MT in SCORE (Standardised Corporate Environment). Cash Management Standards
More informationService description. Corporate Access Payables Appendix Finland
Service description Corporate Access Payables Appendix Finland Page 2 of 5 Table of contents APPENDIX FINLAND... 3 2 GENERAL OVERVIEW OF THE FINNISH PAYMENT INFRASTRUCTURE... 3 2. AVAILABLE PAYMENT TYPES...
More information