MT940 to CAMT.053 Mapping

Transcription

1 to Mapping Description of the SEPA reporting format ABN-Amro Clearing Bank January 2014 Document version: 0.04 Table of Contents General Layout... 2 General Identifiers... 2 Transaction Reference Number...2 Account Identification...3 Statement/Sequence Number...3 Balance Reporting... 4 Balance types and Codes...4 Balance types when a message must be split...4 Credit/Debit Indicator...5 Balance Date...5 Currency and Amount...5 Example...5 How to tell how many files span one report?... 5 Transactions... 6 Value date and Entry date...6 Credit/debit Indicator and Amount...6 Optional Reversal Indicator...7 Transaction type, Owner reference, Bank reference...7 Information to the Account Owner...8 1

2 General Layout The reporting layout accommodates balance reports for one or more accounts. Per account, one or more balances (beginning of day, end of day etc.) are stated, and cash movements. The format is an XML message with the following global layout: <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt " xmlns:xsi=" <GrpHdr> Message-related identification </GrpHdr> Statement for one account <Bal> Balance report for e.g. opening balance </Bal> <Bal> Next balance report for e.g. closing balance Entry holding a cash movement Subsequent entries </Stmt> Optional subsequent statements </GrpHdr> </Document> General Identifiers The report has the following general identifiers: the Transaction Reference Number (:20:), the Account Identification (:25:) and the Statement/Sequence number (:28:, :28C:). Transaction Reference Number The Transaction Reference Number is number that uniquely identifies the message and can be used to e.g. prevent re-processing the message. The report does not reflect the same number, but has its own unique identifier, which is the MsgID in the GrpHdr (or, in shorthand: /Document/BkToCstmrStmt/GrpHdr/MsgId: :20:S <Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt " xmlns:xsi=" <GrpHdr> <MsgId>S </MsgId> 2

3 Account Identification Tag :25: of an message identifies the account. ABN-Amro Clearingbank uses the account number and currency to identify an account, e.g., EUR. The corresponding mapping is as follows. The account number is seen as /Document/BkToCstmrStmt/Stmt/Acct/Id/IBAN. The account is in IBAN format; e.g., NL04ABNC This means that the first 10 characters of the account identifier (0..9) are seen as the last 10 characters of the IBAN value. The currency occurs as /Document/BkToCstmrStmt/Stmt/Acct/Ccy. :25: EUR <Acct> <Id> <IBAN>NL04ABNC </IBAN> </Id> <Ccy>EUR</Ccy> Statement/Sequence Number Tag :28C: (or :28:) has the statement number and the sequence number of an statement. These two are slash-separated, as in 1/1. The last part, the sequence number, may be absent, in which case 1 is implied (for example, 96 implies 96/1 ). Regarding the report, the numbers are mapped as follows: The statement number occurs as the electronic sequence number in a Stmt block, /Document/BkToCstmrStmt/Stmt/ElctrncSeqNb. In the report the number is normally 1, because only one (large) daily statement is generated. If a report spans more than one file (due to an extraordinary number of reported transactions), then the second electronic statement number is 2, and so on. The sequence number is seen as the page number at the level of the group header GrpHdr, in the value for message pagination, as /Document/ BkToCstmrStmt/GrpHdr/ MsgPgntn/PgNb. In the report the number is always 1. Please note that the pagination indicator LastPgInd (last page index) is always true, meaning that there are no more parts to the statement file indicated by the statement number. :28C:1/1 <GrpHdr> <MsgPgntn> <PgNb>1</PgNb> <LastPgInd>true</LastPgInd> </MsgPgntn> </GrpHdr> <ElctrncSeqNb>1</ElctrncSeqNb> 3

4 Balance Reporting uses a number of tags for balance reporting. In, the Stmt block contains one or more Bal blocks. The balance report in has a type and a code. The code indicates the type of balance; e.g., code CLBD reflects a closing balance. Subparts of the value, such as credit/debit indicator and balance date, have their specific slots in the report. Balance types and Codes The following table summarizes the tags and the corresponding codes. Note that ABN-Amro Clearing Bank: Generates one report per day, with one opening balance and one closing balance. Therefore interim balances (type ITBD) do not appear on reports; Therefore, unless an extraordinary number of transactions needs to be reported (see below), only types PRCD and CLBD will appear on a report. Balance type tag code Opening balance :60F: PRCD Closing balance :62A: CLBD Interim balance :62F: or :62M: ITBD Closing available balance :64: CLAV Forward available balance :65: FWAV Balance types when a message must be split The file size of a zipped message is more than enough to accommodate the daily report of balances and transactions 1. In extraordinary situations, ABN-Amro Clearing Bank may have to split a report into more than one file in order to avoid one too large file. In this case intermediate balances are reported as the type ITBD, as follows. In a two-page report: The first page reports: o The opening balance as PRCD o The closing interim balance as ITBD The second page reports: o The opening balance as ITBD o The closing balance as CLBD. In a three-or-more page report: The first page reports: o The opening balance as PRCD o The closing interim balance as ITBD The middle pages report: o Both the opening and the closing balances as ITBD The last page reports: o The opening balance as ITBD o The closing balance as CLBD. 1 Technically there is no maximum file size for a report. Practically however, a maximum size is dictated by the transport media; e.g., servers will typically accept attachments up to 5Mb. 4

5 Credit/Debit Indicator The credit/debit indicator in is the first character of a balance statement. E.g., :60F:C indicates a credit. This is reflected in as /Document/BkToCstmrStmt/Stmt/Bal/CdtDbtInd with value CRDT. Balance Date The balance date in follows the credit/debit indicator, is 6 characters long, and represents a YYMMDD value (year in two digits); for example :60F:C131203, which reports a balance for December 3 rd, The corresponding value in is in /Document/BkToCstmrStmt/Stmt/Bal/Dt/Dt. The value is however formatted as YYYY-MM-DD: a four-digit year, and hyphens to separate year from month and month from day: in this example this would be Currency and Amount The currency and amount occur in the report following the balance date, as in: :60F:C131203EUR31213,54. These fields are reflected in the report as: /Document/BkToCstmrStmt/Stmt/Bal/Amt, attribute Ccy /Document/BkToCstmrStmt/Stmt/Bal/Amt, the tag content is the amount. Note that the amount has a dot as decimal separator, not a comma like the report. Example Below is a sample mapping using the closing interim balance including amount and currency. :60F:C131203EUR31213,54 <Bal> <Tp> <CdOrPrtry> <Cd>PRCD</Cd> </CdOrPrtry> </Tp> <Amt Ccy="EUR"> </Amt> <CdtDbtInd>CRDT</CdtDbtInd> <Dt> <Dt> </Dt> </Dt> </Bal> How to tell how many files span one report? A report that consists of only one file has the following characteristics: the reported balance types are PRCD and CLBD and the electronic sequence number is 1. A report that consists of two files, starts with a file where balances PRCD and ITBD are reported in the file with the electronic sequence number 1. The file with sequence number 2 has the balance types ITBD and CLBD. A report that consists of three or more files, also starts with a file with sequence number 1 and with balance types PRCD and ITBD. However, subsequent middle files have increasing sequence numbers (2, 3, etc.) and balance types ITBD. If these balance 5

6 statements, the first block is always the starting intermediate balance, and the last block is always the ending intermediate balance. Finally, the last page (which again has an incremental sequence number) holds balance types ITBD and CLBD. Transactions Transactions are reported in s as two tags, :61: (statement line) and :86: (information to account owner). Value date and Entry date The value date and the entry date are the first parts of the information in tag :61:. The value date is given in the format YYMMDD, the entry date as MMDD (implying the year from the value date). The dates occur in the message as /Document/BkToCstmrStmt/Stmt/Ntry/ValDt/Dt and /Document/BkToCstmrStmt/Stmt/Ntry/BookgDt /Dt An example is shown below. :61: <BookgDt> <Dt> </Dt> </BookgDt> <ValDt> <Dt> </Dt> </ValDt> Credit/debit Indicator and Amount Following the dates, the information states the credit/debit indicator and the amount; e.g.: :61: D54125,89. This information is in the report at: /Document/BkToCstmrStmt/Stmt/Ntry/CdtDbtInd, with a value either CRDT or DBIT; /Document/BkToCstmrStmt/Stmt/Ntry/Amt with attribute Ccy for currency and with content stating the amount, but using a dot as decimal separator (as opposed to s comma). The currency which is stated in the CAMT report is not present in tag :61: of the report, but by definition it is the currency of the account in question (as stated in /Document/BkToCstmrStmt/Stmt/Acct/Ccy, see above). For example the following is a debit transaction of euro s: :61: D55851,99 6

7 <Amt Ccy="EUR"> </Amt> <CdtDbtInd>DBIT</CdtDbtInd> Optional Reversal Indicator Between the credit/debit indicator and the amount, an optional reversal indicator R may occur in the information; for example: :61: DR55851,99 (note the R). When this is the case, then /Document/BkToCstmrStmt/Stmt/Ntry/RvslInd is set to true: :61: DR55851,99 <RvslInd>true</RvslInd> Transaction type, Owner reference, Bank reference The remainder of an tag :61: are identifiers; as in: :61: D55851,99NMSCNPabcdefg// These are subsequently: Transaction type, 4 characters following the amount (in the above example MSCN). The transaction type is mapped into the field Bank Transaction Code: /Document/BkToCstmrStmt/Stmt/Ntry/BkTxCd/Prtry/Cd. Owner reference, up to //, in this example Pabcdefg. This is mapped in to the end to end ID: /Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/TxDtls/Refs/EndToEndId. Bank reference, which follows the //, in this case By convention ABN-Amro Clearingbank uses 22 to indicate an internal transfer, 229 for an incoming credit, etc. This is mapped in to the Account Service Reference: /Document/BkToCstmrStmt/Stmt/Ntry/AcctSvcrRef. Supplemental details, on the next line, in this case This is mapped to Additional Transaction Information /Document/BkToCstmrStmt/Stmt/Ntry/NtryDtls/AddtlTxInf. This is illustrated in the following example. :61: D55851,99NMSCNPabcdefg// <AcctSvcrRef> </AcctSvcrRef> <BkTxCd> <Prtry> <Cd>NMSC</Cd> </Prtry> </BkTxCd> <NtryDtls> 7

8 <TxDtls> <Refs> <EndToEndId>NPabcdefg</EndToEndId> </Refs> <AddtlTxInf> </AddtlTxInf> </TxDtls> </NtryDtls> Information to the Account Owner Extra information to the account owner is stored in in tag :86:. Most often this is semi-structured information that can be used for reconciliation. The entire contents of tag :86: appear in the report as the Additional Entry Information, /Document/BkToCstmrStmt/Stmt/Ntry/AddtlNtryInf. The appearance in is not totally identical: where separate lines occur in the representation, the information in is separated using the pipeline sign to indicate where one line ends and the next starts. For example (note that the text in the AddtlNtryInf tag is displayed line-wrapped in this document, in the original file it is all 1 line): :86: /REC/MARKETS Free format description Instr. Amount/EUR <AddtlNtryInf> /REC/MARKETS Free format description Instr. Amount/EUR </AddtlNtryInf> 8