UBS Implementation Guidelines

Transcription

1 US Implementation Guidelines Swiss Payment Standards for ash Management Reports camt SPS Version 1.6 US Version 1.0 August 2018

2 US Implementation Guidelines Swiss Payment Standards for ash Management Reports Table of ontents 1. ash Management Reports Scope of application of this document Flow of messages in accordance with Swiss Payment Standards 3 2. Technical specifications US Implementation Structure of camt.053 message Explanation of statuses used in this chapter 4 3. Amendment control 5 4. Appendix Usage of ank Transaction odes Payments irect ebits omplete List of ank Transaction odes US 62 2

3 US Implementation Guidelines Swiss Payment Standards for ash Management Reports 1. ash Management Reports 1.1 Scope of application of this document US provides implementation guidelines for the following ank-to-ustomer ash Management Reports: Name camt.052 camt.053 camt.054 camt.054 efinition Account report Statement ollective booking details ebit/redit notification 1.2 Flow of messages in accordance with Swiss Payment Standards The message standard recommended by Swiss financial institutions is based on the ISO Payments Standard, the Swiss Payment Standards. The chart below provides an overview of the flow of messages currently supported by US and shows the use of all camt reports in the context of the end-to-end message flow: This specific brochure is designed to inform you about technical aspects for the camt.053 message at US. The document is valid within the following scope of application: haracteristics Use of message Product Service Message type available to Recommendation Schema Implementation Guide Version Equivalent SWIFT messages Available through US electronic interfaces Scope of application Account statement camt.053 ank-to-ustomer Statement ash management report ebtor and creditor Swiss Payment Standards camt MT940: ustomer statement message MT950: Statement message (for banks) For clients of US Switzerland AG US KeyPort EIS SWIFT for orporates (FileAct) 3

4 US Implementation Guidelines Swiss Payment Standards for ash Management Reports 2. Technical specifications 2.1 US Implementation The US Implementation Guidelines for ash Management Reports this document - contain technical specifications and instructions for the technical and business implementation of camt.052, camt.053 and camt.054 messages in accordance with the Swiss Payment Standards (see section 1.1) and consequently also the ISO Payments Standard. All ash Management Reports transmitted from US comply with ISO Payments Standard, Swiss Payment Standards and the US Implementation as outlined in this document. The diagram beside shows the interaction of the ISO Payments Standard, Swiss Payment Standards and US Implementation with a link to the respective rules and guidelines that must be adhered to. ISO Payments Standard Swiss Payment Standards US Implementation Structure of camt.053 message The camt.053 ank-to-ustomer Statement message is essentially structured as follows: A-Level: message level, "Group Header". This block contains all the elements that apply to all the transactions in the report. It occurs exactly once in the message. -Level: account level, "Account Statement". The entries in this block correspond in camt.053 to the booked transactions and balances. -Level: amount level, "Statement Entry". This block contains the sub-elements which describe a single entry on the account in question. One entry can combine several transactions. 2.3 Explanation of statuses used in this chapter The following statuses (information about usage) are permitted for individual XML elements according to the Swiss Payment Standards (Implementation Guidelines V1.6 and usiness Rules V2.7) based on the ISO Payments Standard. M = Mandatory O = Optional -Level: amount details, "Entry etails". This block contains booking details about the entry. 4

5 3. Amendment control SPS Version US Version ate Amendment description to previous version SPS V1.5/ US V Various field description have been specified: Level Tag Field hanges A AddtlInf AddtlInf In the US Paymentstandards Test Platform the value "TEST" is affixed in front of the title. In production this field will only reference to the current Swiss Payment Standards version (e.g. SPS/1.6) ElctrncSeqNb ElctrncSeqNb The Electronic Sequence number is always reset to 1 at the beginning of a new year. In the camt.054 delivered through US KeyPort the Electronic Sequence Number will not be reported. Svcr I US always delivers the US I USWHZH80A. Svcr Nm US always provides the name of the legal entity US Switzerland AG. Svcr Id New Svcr Issr New NtryRef NtryRef US delivers the ESR participant number of US (e.g ). The ESR-I will not be displayed. tch NbOfTxs US has a max. volume of transactions per camt-message of 99'999 transactions per payment. Refs MsgId US provides information only when the payment is initiated through pain.001. Refs TxId US delivers transaction identification only for pacs.008. (outbound only) Refs MndtId US delivers Mandate I only for S transactions. 5

6 Level XML Element efinition A A A A A ++GrpHdr ISO Index: GrpHdr +++MsgId ISO Index: GrpHdr +++rettm ISO Index: 1.2 US Implementation Guidelines Swiss Payment Standards for ash Management Reports ISO Name: ank To ustomer Statement V04 XML Name: ktostmrstmt ISO efinition: Scope The anktoustomerstatement 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. Usage The anktoustomerstatement message can contain reports for more than one 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 also balance information. epending on services and schedule agreed between banks and their customers, statements may be generated and exchanged accordingly, for example for intraday or prior day periods. 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). H efinition: The XML message "ank-to-ustomer Statement" (camt.053) is used by financial institutions to send electronic account information to their customers. It is used on the basis of the ISO XML schema "camt ". ISO Name: Group Header XML Name: GrpHdr ISO efinition: ommon information for the message. H efinition: The "Group Header" (A-Level of the message) contains information about the message. It occurs once. ISO Name: Message Identification XML Name: MsgId ISO efinition: Point to point reference, as assigned by the account servicing institution, and sent to the account owner or the party authorised to receive the message, to unambiguously identify the message. Usage: The account servicing institution has to make sure that MessageIdentification is unique per account owner for a pre-agreed period. H efinition: Unique message reference which is assigned by the sender of the message. US Notes: US Message Identification is a random unique string of 16 characters. US Example: <MsgId>99AZEGWNSSVLNA</MsgId> ISO Name: reation ate Time XML Name: rettm ISO efinition: ate and time at which the message was created. H efinition: ate and time when message was created US Notes: Milliseconds will not be reported in the timestamp. US Example: <rettm> t14:13:59+02:00</rettm> ISO Name: XML Name: Message Recipient MsgRcpt 6

7 Level XML Element efinition A ++GrpHdr +++MsgRcpt ISO Index: GrpHdr +++MsgRcpt ++++Id US Implementation Guidelines Swiss Payment Standards for ash Management Reports ISO efinition: Party authorised by the account owner to receive information about movements on the account. Usage: MessageRecipient should only be identified when different from the account owner. H efinition: Element can be used if the recipient is not the account holder (see "Statement/Account/Owner"). ISO Name: Identification XML Name: Id ISO efinition: Unique and unambiguous identification of a party. A ISO Index: GrpHdr +++MsgRcpt ++++Id +++++OrgId ISO Name: Organisation Identification XML Name: OrgId ISO efinition: Unique and unambiguous way to identify an organisation. ISO Index: 1.3 A ISO Name: Any I XML Name: AnyI ++GrpHdr ISO efinition: ode allocated to a financial institution or non +++MsgRcpt financial institution by the ISO 9362 Registration ++++Id Authority as described in ISO 9362 "anking OrgId anking telecommunication messages - usiness AnyI identifier code (I)". H efinition: If used, "Other" must not be present. US Notes: US delivers the Receiver I (e.g. US KeyPort). Status: US Example: <AnyI>USWHZHS</AnyI> A ISO Name: Message Pagination XML Name: MsgPgntn ++GrpHdr ISO efinition: Provides details on the page number of the message. +++MsgPgntn Usage: The pagination of the message is only allowed ISO Index: 1.4 when agreed between the parties. A ISO Name: Page Number XML Name: PgNb ++GrpHdr ISO efinition: Page number. +++MsgPgntn H efinition: The Page Number, beginning with "1", is used to count ++++PgNb the number of messages in a statement. US Example: <PgNb>1</PgNb> ISO Index: 1.4 A ISO Name: Last Page Indicator XML Name: LastPgInd ++GrpHdr ISO efinition: Indicates the last page. +++MsgPgntn H efinition: This element indicates whether the message is the last in ++++LastPgInd the statement. If, on account of size restrictions, a statement has to be divided into more than one ISO Index: 1.4 message, this element is marked "FALSE" in the first messages and "TRUE" in the last one. The individual messages belonging to a single "Electronic Sequence Number" are counted using the "Page Number" element (see above). US Example: <LastPgInd>true</LastPgInd> A ISO Name: Additional Information 7

8 Level XML Element efinition ++GrpHdr +++AddtlInf ISO Index: 1.5 Length: ISO Index: 2.0 ardinality: 1..unbounded +++Id ISO Index: ElctrncSeqNb ISO Index: rettm US Implementation Guidelines Swiss Payment Standards for ash Management Reports XML Name: AddtlInf ISO efinition: Further details of the message. H efinition: ode "SPS" to indicate that values can be sent in accordance with the Implementation Guidelines Swiss Payment Standards. "/" is used as a separator between the values that are sent. Value 1 contains the reference to the underlying Guideline Major Release number in the form "n.n" Value 2 is either "PRO" or "TEST"; if not delivered, then "PRO" applies. Example: "SPS/1.6/TEST". US Notes: In the US Paymentstandards Test Platform the value "TEST" is affixed in front of the title. In production this field will only reference to the current Swiss Payment Standards version (e.g. SPS/1.6) US Example: <AddtlInf>SPS/1.6</AddtlInf> ISO Name: Statement XML Name: Stmt ISO efinition: Reports on booked entries and balances for a cash account. H efinition: Only one instance will be provided, one account per "camt" message. etails about the statement for which the following information is being delivered. This level is described as followed in the various "camt" messages: camt.053: Element name is "Statement", <Stmt> camt.052: Element name is "Report", <Rpt> camt.054: Element name is "Notification", <Ntfcn> This element contains, for camt.053: Report on balances and transactions on an account camt.052: Report on movement within a particular period camt.054: Notification of credits and debits and batch booking breakdown Sub-elements also apply to "camt.052" (Report) and "camt.054" (Notification), unless mentioned explicitly. ISO Name: Identification XML Name: Id ISO efinition: Unique identification, as assigned by the account servicer, to unambiguously identify the account statement. H efinition: Unique Statement Identification. This I is unique for a period of at least one calendar year. US Notes: US Statement Identification is a random unique string of 16 characters. US Example: <Id>E9AZEGWNU682ZA</Id> ISO Name: Electronic Sequence Number XML Name: ElctrncSeqNb ISO efinition: Sequential number of the statement, as assigned by the account servicer. Usage: The sequential number is increased incrementally for each statement sent electronically. H efinition: This field must be completed and shows the current statement number for the year. It begins each year with 1 and always continues in ascending order. US Notes: The Electronic Sequence number is always reset to 1 at the beginning of a new year. In the camt.054 delivered through US KeyPort the Electronic Sequence Number will not be reported. US Example: <ElctrncSeqNb>1</ElctrncSeqNb> ISO Name: reation ate Time XML Name: rettm ISO efinition: ate and time at which the statement was created. H efinition: ate and time of creation of the statement US Notes: Same as on A-Level. Milliseconds will not be reported in the timestamp. 8

9 Level XML Element efinition ISO Index: FrTot ISO Index: 2.5 US Example: US Implementation Guidelines Swiss Payment Standards for ash Management Reports <rettm> t10:35:37+02:00</rettm> ISO Name: From To ate XML Name: FrTot ISO efinition: Range of time between a start date and an end date for which the account statement is issued. US Notes: Milliseconds will not be reported in the timestamp. camt.053: From reported day 00:00:00 till 24:00:00; camt.052 (delta since last report): from last report TotTm till actual report cut off time; camt.052 (all movements since last cut off): From reported day 00:00:00 till actual report cut off time. +++FrTot ++++FrtTm ISO Index: FrTot ++++TotTm ISO Index: pyplctind ISO Index: RptgSrc +++RptgSrc ISO time logic: 00:00:00 = the beginning of a calendar day / 24:00:00 = the end of a calendar day ISO Name: From ate Time XML Name: FrtTm ISO efinition: ate and time at which the range starts. US Example: <FrtTm> T00:00:00+02:00</FrtTm> ISO Name: To ate Time XML Name: TotTm ISO efinition: ate and time at which the range ends. US Example: <TotTm> T24:00:00+02:00</TotTm> ISO Name: opy uplicate Indicator XML Name: pyplctind ISO efinition: Indicates whether the document is a copy, a duplicate, or a duplicate of a copy. H efinition: etails of the current message type (copy, duplicate, copy of a duplicate). All 3 values (OU/OPY/UPL) are permitted. This element is not delivered in the original message. Messages to other recipients of the original message contain the value "OPY". If a message is created again, it contains the value "UPL" for the original recipient and "OU" for other recipients. US Notes: At US, the messages can be re-created only through re-order of existing order. Hence the code UPL will be sent for any re-order. OU and OPY will not be reported. US Example: <pyplctind>upl</pyplctind> ISO Name: Reporting Source XML Name: RptgSrc ISO efinition: Specifies the application used to generate the reporting. ISO Name: Proprietary XML Name: Prtry ISO efinition: Reporting source, in a proprietary form. H efinition: The following values can be used: 9

10 Level XML Element efinition ++++Prtry +++Acct ISO Index: Acct ++++Id ISO Index: Acct ++++Id +++++IAN ISO Index: 2.10 Status: +++Acct ++++cy +++Acct ++++Ownr US Implementation Guidelines Swiss Payment Standards for ash Management Reports 53F ollective ooking Statement FI collects 53 ollective ooking Statement ustomer collects 52F ollective ooking Account Report FI collects 52 ollective ooking Account Report ustomer collects TN ebit Notification TN redit Notification OTHR ollective ooking Statement (other source than camt) US Notes: Only used in camt.054. The code "OTHR" will only be used for separate collective booking details (ESR / LSV) without a relation to camt.052 or camt F, TN and TN reports will be delivered at a later stage. US Example: <Prtry>53</Prtry> ISO Name: Account XML Name: Acct ISO efinition: Unambiguous identification of the account to which credit and debit entries are made. H efinition: Information about the account, its owner and the financial institution. ISO Name: Identification XML Name: Id ISO efinition: Unique and unambiguous identification for the account between the account owner and the account servicer. H efinition: This element is used as follows: IAN or Proprietary Account (Some financial institutions offer IAN exclusively.) ISO Name: IAN XML Name: IAN ISO efinition: International ank Account Number (IAN) - identifier used internationally by financial institutions to uniquely identify the account of a customer. Further specifications of the format and content of the IAN can be found in the standard ISO "anking and related financial services - International ank Account Number (IAN)" version , or later revisions. H efinition: If used, then "Proprietary Account" must not be present. US Notes: US always delivers an IAN, no proprietary account possible. US Example: <IAN>H R</IAN> ISO Name: urrency XML Name: cy ISO efinition: Identification of the currency in which the account is held. H efinition: Account currency US Notes: US always delivers the currency in which the account is held. US Example: <cy>hf</cy> ISO Name: Owner XML Name: Ownr ISO efinition: Party that legally owns the account. H efinition: Information about the account holder ISO Index: 2.10 ISO Name: XML Name: Name Nm 10

11 Level XML Element efinition +++Acct ++++Ownr +++++Nm ISO Index: 2.10 Length: Acct ++++Svcr +++Acct ++++Svcr +++++FinInstnId ISO efinition: US Notes: US Example: US Implementation Guidelines Swiss Payment Standards for ash Management Reports Name by which a party is known and which is usually used to identify that party. US delivers the name from the static data of the account owner. <Nm>Owner TEST AG</Nm> ISO Name: Servicer XML Name: Svcr ISO efinition: Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account. US Notes: US provides its own information. ISO Name: Financial Institution Identification XML Name: FinInstnId ISO efinition: Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. +++Acct ++++Svcr +++++FinInstnId IFI +++Acct ++++Svcr +++++FinInstnId Nm Length: Acct ++++Svcr +++++FinInstnId Othr +++Acct ++++Svcr +++++FinInstnId Othr Id ISO Name: IFI XML Name: IFI ISO efinition: ode allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "anking - anking telecommunication messages - usiness identifier code (I)". US Notes: US always delivers the US I USWHZH80A. US Example: <I>USWHZH80A</I> ISO Name: Name XML Name: Nm ISO efinition: Name by which an agent is known and which is usually used to identify that agent. US Notes: US always provides the name of the legal entity US Switzerland AG. US Example: <Nm>US SWITZERLAN AG</Nm> ISO Name: Other XML Name: Othr ISO efinition: Unique identification of an agent, as assigned by an institution, using an identification scheme. ISO Name: Identification XML Name: Id ISO efinition: Unique and unambiguous identification of a person. H efinition: VAT number US Example: <Id>HE MWST</Id> 11

12 US Implementation Guidelines Swiss Payment Standards for ash Management Reports Level XML Element efinition +++Acct ++++Svcr +++++FinInstnId Othr Issr +++al ISO Index: 2.23 ardinality: 1..unbounded +++al ++++Tp ISO Index: al ++++Tp +++++dorprtry ISO Index: al ++++Tp +++++dorprtry d ISO Index: 2.26 ISO Name: Issuer XML Name: Issr ISO efinition: Entity that assigns the identification. H efinition: Value "VAT-I" US Example: <Issr>VAT-I</Issr> ISO Name: alance XML Name: al ISO efinition: Set of elements used to define the balance as a numerical representation of the net increases and decreases in an account at a specific point in time. H efinition: The content of the "camt.053", "camt.052" and "camt.054" messages differs only in the use of this element. The following rules apply: camt.053: Is always sent. camt.052: an be sent. camt.054: Is not sent. US Notes: US rules apply: camt.053: is always sent. camt.052: is always sent. camt.054: is not sent. ISO Name: Type XML Name: Tp ISO efinition: Specifies the nature of a balance. H efinition: Type of balance ISO Name: ode Or Proprietary XML Name: dorprtry ISO efinition: oded or proprietary format balance type. ISO Name: ode XML Name: d ISO efinition: alance type, in a coded form. H efinition: In Switzerland, the following values are used, depending on the use case: 1. camt.053: mandatory OP in combination with L optional LAV optional FWAV optional INFO 2. camt.052 full (transactions always since the last regular statement) optional OP in combination with IT optional ITAV 3. camt.052 incremental (transactions since the last 12

13 US Implementation Guidelines Swiss Payment Standards for ash Management Reports Level XML Element efinition US Notes: Intraday statement) optional IT (can be sent up to twice as interim balance, opening and closing, or closing only, in combination with the "alance/ate/ate Time" element) optional ITAV Type of booking. US provides the following values: 1. For camt.053: OP (Opening ooked) L (losing ooked) LAV (losing Available) FWAV (Forward Available) 2. For camt.052 (All movements since last cut off) OP (Opening ooked) IT (Interim ooked) 3. For camt.052 (delta since last report) IT (Interim ooked) +++al ++++Amt ISO Index: al ++++dtbtind ISO Index: al ++++t ISO Index: al ++++t +++++t ISO Index: 2.36 Status: +++al ++++t +++++ttm ISO Index: 2.36 US delivers IT only for closing balance. US Example: <d>op</d> ISO Name: Amount XML Name: Amt ISO efinition: Amount of money of the cash balance. US Notes: The balance will always be delivered in account currency. US Example: <Amt cy="hf"> </amt> ISO Name: redit ebit Indicator XML Name: dtbtind ISO efinition: Indicates whether the balance is a credit or a debit balance. Usage: A zero balance is considered to be a credit balance. US Notes: A zero balance is considered to be a credit balance. US Example: <dtbtind>rt</dtbtind> ISO Name: ate XML Name: t ISO efinition: Indicates the date (and time) of the balance. H efinition: ate of balance depending on "alance Type" ISO Name: ate XML Name: t ISO efinition: Specified date. H efinition: If used, then "ate Time" must not be present. US Notes: Used in camt.053 and camt.052 (all movements since last cut off). US Example: <t> </t> ISO Name: ate Time XML Name: ttm ISO efinition: Specified date and time. H efinition: If used, then "ate" must not be present. US Notes: Only used in camt.052 (delta since last report). Milliseconds will not be reported in the timestamp. US Example: <ttm> t10:35:37+02:00</ttm> 13

14 Level XML Element efinition Status: +++TxsSummry ISO Index: TxsSummry ++++TtlNtries US Implementation Guidelines Swiss Payment Standards for ash Management Reports ISO Name: Transactions Summary XML Name: TxsSummry ISO efinition: Provides summary information on entries. H efinition: Totals per statement. ontains the total for the entries and the breakdown into credits and debits. US Notes: Only used in camt.052 messages. ISO Name: Total Entries XML Name: TtlNtries ISO efinition: Specifies the total number and sum of debit and credit entries. H efinition: Summary of all account movements per statement. ISO Index: TxsSummry ++++TtlNtries +++++NbOfNtries ISO Index: TxsSummry ++++TtlNtries +++++Sum ISO Index: TxsSummry ++++TtlNtries +++++TtlNetNtry +++TxsSummry ++++TtlNtries +++++TtlNetNtry Amt +++TxsSummry ++++TtlNtries +++++TtlNetNtry dtbtind ISO Name: Number Of Entries XML Name: NbOfNtries ISO efinition: Number of individual entries included in the report. H efinition: Total number of account movements of this statement US Example: <NbOfNtries>00019</NbOfNtries> ISO Name: Sum XML Name: Sum ISO efinition: Total of all individual entries included in the report. H efinition: Total amount for all account movements of this statement US Example: <Sum>255.94</Sum> ISO Name: Total Net Entry XML Name: TtlNetNtry ISO efinition: Resulting debit or credit amount of the netted amounts for all debit and credit entries. ISO Name: Amount XML Name: Amt ISO efinition: Resulting amount of the netted amounts for all debit and credit entries. H efinition: hanges to the account balance as a result of all the account movements shown in the statement US Example: <Amt>98.18</Amt> ISO Name: redit ebit Indicator XML Name: dtbtind ISO efinition: Indicates whether the amount is a credit or a debit amount. H efinition: Shows whether the change (element "Total Net Entry Amount") is positive or negative US Example: <dtbtind>it</dtbtind> 14

15 US Implementation Guidelines Swiss Payment Standards for ash Management Reports Level XML Element efinition +++TxsSummry ++++TtldtNtries ISO Index: TxsSummry ++++TtldtNtries +++++NbOfNtries ISO Index: TxsSummry ++++TtldtNtries +++++Sum ISO Index: TxsSummry ++++TtlbtNtries ISO Index: TxsSummry ++++TtlbtNtries +++++NbOfNtries ISO Index: TxsSummry ++++TtlbtNtries +++++Sum ISO Index: 2.54 ISO Name: Total redit Entries XML Name: TtldtNtries ISO efinition: Specifies the total number and sum of credit entries. ISO Name: Number Of Entries XML Name: NbOfNtries ISO efinition: Number of individual entries included in the report. H efinition: Number of all credits US Example: <NbOfNtries>00019</NbOfNtries> ISO Name: Sum XML Name: Sum ISO efinition: Total of all individual entries included in the report. H efinition: Total amount of all credits US Example: <Sum>255.94</Sum> ISO Name: Total ebit Entries XML Name: TtlbtNtries ISO efinition: Specifies the total number and sum of debit entries. ISO Name: Number Of Entries XML Name: NbOfNtries ISO efinition: Number of individual entries included in the report. H efinition: Number of all debits US Example: <NbOfNtries>00019</NbOfNtries> ISO Name: Sum XML Name: Sum ISO efinition: Total of all individual entries included in the report. H efinition: Total amount of all debits US Example: <Sum>255.94</Sum> ISO Name: Entry XML Name: Ntry ISO efinition: Set of elements used to specify an entry in the statement. 15

16 Level XML Element efinition ISO Index: 2.76 ardinality: 0..unbounded +Ref ISO Index: Amt ISO Index: dtbtind US Implementation Guidelines Swiss Payment Standards for ash Management Reports Usage: At least one reference must be provided to identify the entry and its underlying transaction(s). H efinition: etailed information about a single entry Is always sent, provided at least 1 account movement has taken place. If there has been no account movement and only account balances are being reported, this element is not sent. camt.052/053: This element is optional. camt.054: This element is always sent. ISO Name: Entry Reference XML Name: NtryRef ISO efinition: Unique reference for the entry. H efinition: For ISR/LSV, H- and QR-IAN entries, a value is always sent and differs in the kind of batch booking logic that is applied (for a description of the versions, see usiness Rules): Version 1: ISR participant number in the format Version 2: ISR participant number and ISR-I (example: /123456) Version 3: RS-PI in the format Version 4: QR-IAN in the format H Version 5: QR-IAN and the first 6 characters of the QR reference (example: H /123456) US Notes: UUS delivers the ESR participant number of US (e.g ). The ESR-I will not be displayed. With QR-bill: US will display QR-IAN. US Example: <NtryRef> </NtryRef> ISO Name: Amount XML Name: Amt ISO efinition: Amount of money in the cash entry. H efinition: Amount and currency of the entry The currency shown in the "Amount" field at "Entry" level is the same as the account currency. Note: the currency is always sent as an attribute of the "Amount" element. US Example: <Amt cy="hf"> </amt> ISO Name: redit ebit Indicator XML Name: dtbtind ISO efinition: Indicates whether the entry is a credit or a debit entry. H efinition: Indicator of credit or debit entry US Example: <dtbtind>it</dtbtind> ISO Index: RvslInd ISO Index: 2.80 ISO Name: Reversal Indicator XML Name: RvslInd ISO efinition: Indicates whether or not the entry is the result of a reversal. Usage: This element should only be present if the entry is the result of a reversal. If the reditebitindicator is RT and ReversalIndicator is Yes, the original operation was a debit entry. If the reditebitindicator is IT and ReversalIndicator is Yes, the original operation was a credit entry. H efinition: Indicator shows whether the entry is a return. It should only be present for a transaction (Entry) in the following cases: 1. Reversal after S (Return/Refund) 2. Reversal after H- or H-TA 3. Reversal after transfers (refund because a payment 16

17 US Implementation Guidelines Swiss Payment Standards for ash Management Reports Level XML Element efinition could not be credited to the creditor s financial institution). 4. ank internal cancellation ++++Sts ISO Index: ookgt ISO Index: ookgt +++++t ISO Index: 2.82 Status: ++++Valt ISO Index: 2.83 If the "redit ebit Indicator" is "RT" and the "Reversal Indicator" is "TRUE", then the original entry was a debit entry. If the "redit ebit Indicator" is "IT" and the "Reversal Indicator" is "TRUE", then the original entry was a credit entry. US Notes: In case of storno transactions, US does not provide related parties. R-transactions are booked as separate transactions, without a Reversal Indicator (TRUE). US Example: <RvslInd>true</RvslInd> ISO Name: Status XML Name: Sts ISO efinition: Status of an entry on the books of the account servicer. H efinition: Status of an entry Swiss financial institutions offer the following codes: OOK (ooked) PNG (Pending) camt.053: Only "OOK" is sent. camt.052/054: "OOK" and "PNG" may be sent. US Example: <Sts>OOK</Sts> / <Sts>PNG</Sts> ISO Name: ooking ate XML Name: ookgt ISO efinition: ate and time when an entry is posted to an account on the account servicer's books. Usage: ooking date is the expected booking date, unless the status is booked, in which case it is the actual booking date. H efinition: orresponds to the booking date. camt.053: Element is always sent. camt.052: Element may be sent. camt.054: Element may be sent. US Notes: US delivers as follows: camt.053: Element is always sent camt.052: Element is always sent camt.054: Element is always sent ISO Name: ate XML Name: t ISO efinition: Specified date. H efinition: If used, then "ate Time" must not be present. US Example: <t> </t> ISO Name: Value ate XML Name: Valt ISO efinition: ate and time at which assets become available to the account owner in case of a credit entry, or cease to be available to the account owner in case of a debit entry. Usage: If entry status is pending and value date is present, then the value date refers to an expected/ requested value date. For entries subject to availability/float and for which availability information is provided, the value date must not be used. In this case the availability component identifies the number of availability days. H efinition: orresponds to the value date. US Notes: US delivers as follows: 17

18 Level XML Element efinition ++++Valt +++++t US Implementation Guidelines Swiss Payment Standards for ash Management Reports camt.053: Element is always sent camt.052: Element is always sent camt.054: Element is always sent ISO Name: ate XML Name: t ISO efinition: Specified date. H efinition: If used, then "ate Time" must not be present. US Example: <t> </t> ISO Index: 2.83 Status: ++++AcctSvcrRef ISO Index: ktxd ISO Index: ktxd +++++omn ISO Index: ktxd +++++omn d ISO Index: 2.93 Length: ktxd +++++omn Fmly ISO Index: 2.94 ISO Name: Account Servicer Reference XML Name: AcctSvcrRef ISO efinition: Unique reference as assigned by the account servicing institution to unambiguously identify the entry. H efinition: Unique reference for the entry, assigned by the financial institution. US Notes: US shows the Account Servicer Reference on the - Level for all transactions. US Example: <AcctSvcrRef>ASR </AcctSvcrRef> ISO Name: ank Transaction ode XML Name: ktxd ISO efinition: Set of elements used to fully identify the type of underlying transaction resulting in an entry. H efinition: ank Transaction ode This element provides details of the type of entry. US Notes: US usage of ank Transaction odes is described in a separate chapter. ISO Name: omain XML Name: omn ISO efinition: 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. Usage: If a specific family or sub-family code cannot be provided, the generic family code defined for the domain or the generic sub-family code defined for the family should be provided. H efinition: omain for the "ank Transaction ode" Always sent in Switzerland. ISO Name: ode XML Name: d ISO efinition: Specifies the business area of the underlying transaction. H efinition: omain code for the "ank Transaction ode" Always sent in Switzerland. US Notes: US usage of ank Transaction odes is described in a separate chapter. US Example: <d>pmnt</d> ISO Name: Family XML Name: Fmly ISO efinition: Specifies the family and the sub-family of the bank transaction code, within a specific domain, in a structured and hierarchical format. H efinition: Family of the "ank Transaction ode" Always sent in Switzerland. 18

19 Level XML Element efinition ++++ktxd +++++omn Fmly d US Implementation Guidelines Swiss Payment Standards for ash Management Reports ISO Name: ode XML Name: d ISO efinition: Specifies the family within a domain. H efinition: Family code for the "ank Transaction ode" Always sent in Switzerland. US Notes: US usage of ank Transaction odes is described in a separate chapter. US Example: <d>it</d> ISO Index: 2.95 Length: ktxd +++++omn Fmly SubFmlyd ISO Index: 2.96 Length: ktxd +++++Prtry ++++ktxd +++++Prtry d ++++AddtlInfInd ISO Index: AddtlInfInd ISO Name: Sub Family ode XML Name: SubFmlyd ISO efinition: Specifies the sub-product family within a specific family. H efinition: Sub-family code for the "ank Transaction ode" Always sent in Switzerland. US Notes: US usage of ank Transaction odes is described in a separate chapter. US Example: <SubFmlyd>AUTT</SubFmlyd> ISO Name: Proprietary XML Name: Prtry ISO efinition: ank transaction code in a proprietary form, as defined by the issuer. ISO Name: ode XML Name: d ISO efinition: Proprietary bank transaction code to identify the underlying transaction. H efinition: May contain the existing proprietary bank transaction code. US Notes: US delivers the original US ank Transaction ode. The ank Transaction ode escription will be displayed in the Additional Entry Information. US Example: <d>z24</d> ISO Name: Additional Information Indicator XML Name: AddtlInfInd ISO efinition: Indicates whether the underlying transaction details are provided through a separate message, as in the case of aggregate bookings. H efinition: This element can contain a reference to the separate information in a "camt.054" message. camt.053: Element may be sent. camt.052: Element may be sent. camt.054: Element is not used. US Notes: US uses in camt.053 and camt.052 this element to reference the related camt.054. ISO Name: Message Name Identification XML Name: MsgNmId ISO efinition: Specifies the message name identifier of the message that will be used to provide additional details. H efinition: Name (type) of message containing the details of this 19

20 Level XML Element efinition +++++MsgNmId ISO Index: AddtlInfInd +++++MsgId ISO Index: Amttls ++++Amttls +++++InstdAmt ++++Amttls +++++InstdAmt Amt ++++Amttls +++++TxAmt ++++Amttls US Example: US Implementation Guidelines Swiss Payment Standards for ash Management Reports transaction <MsgNmId>camt </MsgNmId> ISO Name: Message Identification XML Name: MsgId ISO efinition: Specifies the identification of the message that will be used to provide additional details. H efinition: I of the message containing the details of this transaction US Example: <MsgId>25AZEGWNSSVLNA</MsgId> ISO Name: Amount etails XML Name: Amttls ISO efinition: Provides 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. H efinition: For rules on entries see section 2.5 US Notes: US uses amount details to deliver all booking relevant details. ue to the booking logic, US delivers exchange information on -Level only. In case of incoming ESR payments US does not deliver amount details. ISO Name: Instructed Amount XML Name: InstdAmt ISO efinition: 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 information in case the instructed amount and/or currency is/are different from the entry amount and/or currency. H efinition: Amount in the currency of the instruction ISO Name: Amount XML Name: Amt ISO efinition: 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. US Notes: US delivers Instructed Amount for payment bookings if available. For non payment transactions it is not available. US Example: <Amt cy="eur">100.02</amt> ISO Name: Transaction Amount XML Name: TxAmt ISO efinition: Amount of the underlying transaction. H efinition: Amount exchanged between the financial institutions involved. For sub-elements see element "Instructed Amount" <InstdAmt>. ISO Name: Amount XML Name: Amt ISO efinition: 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. 20

21 Level XML Element efinition +++++TxAmt Amt ++++Amttls +++++ntrvalamt ++++Amttls +++++ntrvalamt Amt ++++Amttls +++++ntrvalamt cyxchg US Notes: US Example: US Implementation Guidelines Swiss Payment Standards for ash Management Reports In case of credit bookings US does not deliver transaction amount. <Amt cy="eur">100.02</amt> ISO Name: ounter Value Amount XML Name: ntrvalamt ISO efinition: Set of elements used to provide the countervalue amount and currency exchange information. Usage: This can be 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. H efinition: Amount in the account currency, before charges For sub-elements see element "Instructed Amount" <InstdAmt>. US Notes: Only used if transaction currency is not account currency. ISO Name: Amount XML Name: Amt ISO efinition: 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. US Notes: Only used if transaction currency is not account currency. US Example: <Amt cy="hf">115.02</amt> ISO Name: urrency Exchange XML Name: cyxchg ISO efinition: Set of elements used to provide details on the currency exchange. ++++Amttls +++++ntrvalamt cyxchg Srccy ++++Amttls +++++ntrvalamt cyxchg Trgtcy ++++Amttls ISO Name: Source urrency XML Name: Srccy ISO efinition: urrency from which an amount is to be converted in a currency conversion. US Example: <Srccy>EUR</Srccy> ISO Name: Target urrency XML Name: Trgtcy ISO efinition: urrency into which an amount is to be converted in a currency conversion. US Example: <Trgtcy>HF</Trgtcy> ISO Name: Exchange Rate XML Name: XchgRate ISO efinition: Factor used to convert an amount from one currency into another. This reflects the price at which one currency was bought with another currency. 21

22 Level XML Element efinition +++++ntrvalamt cyxchg XchgRate ++++hrgs ISO Index: hrgs +++++TtlhrgsAndTaxAmt ISO Index: hrgs +++++Rcrd US Example: US Implementation Guidelines Swiss Payment Standards for ash Management Reports Usage: ExchangeRate expresses the ratio between Uniturrency and Quotedurrency (ExchangeRate = Uniturrency/Quotedurrency). <XchgRate> </XchgRate> ISO Name: harges XML Name: hrgs ISO efinition: Provides information on the charges, pre-advised or included in the entry amount. Usage: This component is used on entry level in case of batch or aggregate bookings. H efinition: oth charges deducted directly from the booking and those applied later can be sent in this field. US Notes: US will deliver charges related information on - Level at a later stage. ISO Name: Total harges And Tax Amount XML Name: TtlhrgsAndTaxAmt ISO efinition: Total of all charges and taxes applied to the entry. H efinition: oth charges deducted directly from the booking and those applied later can be sent in this field. US Example: <TtlhrgsAndTaxAmt cy="hf">0.12</ TtlhrgsAndTaxAmt> ISO Name: Record XML Name: Rcrd ISO efinition: Provides details of the individual charges record. H efinition: etails about individual charges ardinality: 0..unbounded ++++hrgs +++++Rcrd Amt ++++hrgs +++++Rcrd dtbtind ++++hrgs +++++Rcrd hrginclind ISO Name: Amount XML Name: Amt ISO efinition: Transaction charges to be paid by the charge bearer. US Example: <Amt cy="hf">0.01</amt> ISO Name: redit ebit Indicator XML Name: dtbtind ISO efinition: Indicates whether the charges amount is a credit or a debit amount. Usage: A zero amount is considered to be a credit. US Example: <dtbtind>it</dtbtind> ISO Name: harge Included Indicator XML Name: hrginclind ISO efinition: Indicates whether the charge should be included in the amount or is added as pre-advice. US Notes: US handles charges in a separate booking and always delivers "FALSE". US Example: <hrginclind>false</hrginclind> 22

23 Level XML Element efinition ++++hrgs +++++Rcrd Tp ISO Name: Type XML Name: Tp ISO efinition: Specifies the type of charge. US Implementation Guidelines Swiss Payment Standards for ash Management Reports ++++hrgs +++++Rcrd Tp Prtry ++++hrgs +++++Rcrd Tp Prtry Id ++++hrgs +++++Rcrd r +tls ISO Index: ardinality: 0..unbounded ISO Name: Proprietary XML Name: Prtry ISO efinition: Type of charge in a proprietary form, as defined by the issuer. ISO Name: Identification XML Name: Id ISO efinition: Name or number assigned by an entity to enable recognition of that entity, eg, account identifier. H efinition: Values 1-5 for ISR/QR charges Values for internal institutional charges (assigned by each specific institution) Values for external charges (assigned by each specific institution) US Notes: ategories of charges: 1 = Reject for ESR, ES 2 = Payment post office (Einzahlungen am Postschalter) for ESR, ES. Reprocessing charges will not be separated and displayed under ode 2 4 = Reprocessing for ESR will not be used. US delivers in a first step only charge type payment post office and the reject costs. All other charges will be delivered at a later stage. US Example: <Id>1</Id> ISO Name: earer XML Name: r ISO efinition: Specifies which party/parties will bear the charges associated with the processing of the payment transaction. US Notes: US uses the following codes: ET RE SHAR SLEV (SEPA) For payment post office charges and reject costs only RE is used. US Example: <r>re</r> ISO Name: Entry etails XML Name: Ntrytls ISO efinition: Provides details on the entry. H efinition: ontains details about the entry. 23

24 Level XML Element efinition +tls +++++tch US Implementation Guidelines Swiss Payment Standards for ash Management Reports ISO Name: atch XML Name: tch ISO efinition: Provides details on batched transactions. US Notes: US provides the summary of the collective and salary booking information. ISO Index: tls +++++tch MsgId +tls +++++tch PmtInfId +tls +++++tch NbOfTxs +tls +++++tch TtlAmt +tls +++++tch dtbtind ISO Name: Message Identification XML Name: MsgId ISO efinition: Point to point reference, as assigned by the sending party, to unambiguously identify the batch of transactions. H efinition: Reference to the message I of the original message. US Notes: US provides this information only for ISO-payments. US Example: <MsgId>MSGI-T101V </ MsgId> ISO Name: Payment Information Identification XML Name: PmtInfId ISO efinition: Unique identification, as assigned by a sending party, to unambiguously identify the payment information group within the message. H efinition: The batch booking reference assigned by the customer can be entered here. US Notes: US provides information only when the payment is initiated through pain.001. US Example: <PmtInfId>PMTINFI-T101V </ PmtInfId> ISO Name: Number Of Transactions XML Name: NbOfTxs ISO efinition: Number of individual transactions included in the batch. H efinition: Number of payments in the batch booking. US Notes: US has a max. volume of transactions per camtmessage of 99'999 transactions per payment. US Example: <NbOfTxs>2</NbOfTxs> ISO Name: Total Amount XML Name: TtlAmt ISO efinition: Total amount of money reported in the batch entry. H efinition: Total value of payments in the batch booking. US Example: <TtlAmt cy="eur">0.05</ttlamt> ISO Name: redit ebit Indicator XML Name: dtbtind ISO efinition: Indicates whether the batch entry is a credit or a debit entry. H efinition: Indicates whether the batch booking is a credit or a debit booking. US Example: <dtbtind>rt</dtbtind> ISO Name: Transaction etails XML Name: Txtls ISO efinition: Provides information on the underlying transaction(s). 24

25 Level XML Element efinition +tls +++++Txtls ISO Index: ardinality: 0..unbounded +tls +++++Txtls Refs H efinition: US Implementation Guidelines Swiss Payment Standards for ash Management Reports ontains booking details for the entry, e.g. the end-toend identification and remittance information. escription see section "Transaction etails (Txtls, - Level)". ISO Name: References XML Name: Refs ISO efinition: Provides the identification of the underlying transaction. H efinition: References to the original transaction in relation to which these details are being sent. ISO Index: tls +++++Txtls Refs MsgId ISO Index: tls +++++Txtls Refs AcctSvcrRef ISO Index: tls +++++Txtls Refs PmtInfId ISO Index: tls ISO Name: Message Identification XML Name: MsgId ISO efinition: Point to point reference, as assigned by the instructing party of the underlying message. H efinition: "Message Identification" (A-Level) from the original instruction message (e.g. from "pain.001" or MT103, Field :20:) US Notes: US provides information only when the payment is initiated through pain.001. US Example: <MsgId>REP HIP TSV </MsgId> ISO Name: Account Servicer Reference XML Name: AcctSvcrRef ISO efinition: Unique reference, as assigned by the account servicing institution, to unambiguously identify the instruction. H efinition: If references other than to -Level are available in the same element, these could be given here (e.g. -Level = collective reference and/or -Level = breakdown for each transaction in the batch). In the case of separate transactions (one - and one -Level), the reference is the same. US Notes: US shows the reference on the -Level same as on -Level for all transactions except for ESR/LSVcollective-payments (credit End of ay) where US displays the specific Account Servicer Reference of the individual transaction. US Example: <AcctSvcrRef>Z81115E </AcctSvcrRef> ISO Name: Payment Information Identification XML Name: PmtInfId ISO efinition: Unique identification, as assigned by a sending party, to unambiguously identify the payment information group within the message. H efinition: Identification from the original instruction message (- Level from "pain.001" or "pain.008") US Notes: US provides information only when the payment is initiated through pain.001 and pain.008 (S). US Example: <PmtInfId>PMTINFI-T101V </ PmtInfId> ISO Name: Instruction Identification XML Name: InstrId ISO efinition: Unique identification, as assigned by an instructing party for an instructed party, to unambiguously identify the instruction. 25

26 Level XML Element efinition +++++Txtls Refs InstrId ISO Index: tls +++++Txtls Refs EndToEndId ISO Index: tls +++++Txtls Refs TxId +tls +++++Txtls Refs MndtId ISO Index: US Implementation Guidelines Swiss Payment Standards for ash Management Reports 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. H efinition: I of the -Level from the original instruction ("pain. 001" or "pain.008") is sent back to the relevant initiating party. US Notes: US provides information only when the payments are initiated through pain.001. US Example: <InstrId>INSTI-T101V </ InstrId> ISO Name: End To End Identification XML Name: EndToEndId ISO efinition: Unique identification, as assigned by the initiating party, to unambiguously 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. Usage: In case there are technical limitations to pass on multiple references, the end-to-end identification must be passed on throughout the entire end-to-end chain. H efinition: ustomer reference for the debtor from the original instruction is sent throughout (-Level from "pain.001"). In the case of "pain.008" this may be the reference for the payment recipient. US Notes: At US the End to End Identification will be available for ISO payments. US Example: <EndToEndId>E2EI-T101V </EndToEndId> ISO Name: Transaction Identification XML Name: TxId ISO efinition: Unique identification, as assigned by the first instructing agent, to unambiguously identify the transaction that is 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 that the transaction identification is unique for a preagreed period. H efinition: "Transaction I" for the corresponding Interbank message (pacs.008 or pacs.003). US Notes: US delivers transaction identification only for pacs (outbound only). US Example: <TxId>TX </TxId> ISO Name: Mandate Identification XML Name: MndtId ISO efinition: Unique identification, as assigned by the creditor, to unambiguously identify the mandate. H efinition: Mandate identification from the original irect ebit instruction (-Level, from "pain.008") US Notes: US Example: US delivers Mandate I only for S transactions. <MndtId>MandateId- A E</MndtId> 26