Discussion:IG Rubis ActivationReport

From documentation SEPAmail
Jump to navigation Jump to search
SEPAmail – Norme 1206

Cette page fait partie de la version 1206 de la norme.

Sauf indication contraire, elle a été validée par les instances concernées et s'impose à tous les adhérents SEPAmail.
ATTENTION ! La version 1606 de la norme est disponible, vérifiez si cette page est toujours valable.

document de la série: directive d'implémentation
Rubis ActivationReport : Implementation Guidelines
  • These implementation rules shall be applied in accordance with ISO20022 and SEPA own implementation rules. Thus, unless explicitly specified, data contained within a field or XML structure of a SEPAmail message must comply with the constraints related to the equivalent field or XML structure in ISO20022 or SEPA messages.
  • for an explanation of the color coding used in the tables below, see this page
  • for general rules applying to all fields, see this page
  • for business rules directing these IG, see this page

Reference document

The underlying message, pain.014.001.01, is described by an ISO 20022 document, entitled "Creditor Payment Activation Request: Message Definition Report", in its October 2010 version, with which the reader should be familiar.

It is available directly from ISO 20022 here.

Introduction

This document describes the contents of the SEPAmail RUBIS message used to accept or reject payment as requested by a debtor. The full name of this message is sepamail_message_payment.activation_PaymentActivationReport. This message can be used in two cases:

  • Normally, it is generated and sent by the debtor upon reception of a “Payment Activation Request” Rubis ActivationRequest message, to indicate his approval or rejection.
  • It can also be generated and sent by the debtor's bank

This message contains one or several ISO pain.014 structures. For adaptability reasons, this message also includes non-ISO parts. All message parts are described in this document

Header

Ref. Mult. Ch. Depth Message element Requirements
A [1..1]   + Header
SEPAMAIL
rule		 Global header for message
A1 [1..1]   ++ CreationDateTime
SEPAMAIL
rule		 Creation date and time, ISO format. This date will be used as instruction date for the associated payments, if any.
MAP FROM
rule		 [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /Header /CreDtTm] (A1) within the [RUBIS Payment Activation Request] message must not be copied into this structure that refers to the creation timestamp of the paymentActivationReport itself.
MAP TO
rule		 This structure must not be copied into [ /Document /FIToFICstmrCdtTrf /GrpHdr /CreDtTm] (1.2) within the [SEPA Inter-Bank Credit Transfer] message
A2 [1..1]   ++ NbOfReports
SEPAMAIL
rule		 Mandatory. Number of RepCompl elements contained in the message
A3 [0..*]   ++ Documents
SEPAMAIL
rule		 Any document justifying the payment decision.
MAP FROM
rule		 The enclosed documents within [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /Header /Documents] (A3) within the [RUBIS Payment Activation Request] message must not be copied into this structure.
A3.1 [1..1]   +++ Type
SEPAMAIL
rule		 Type of document attached. Possible values are mandate, invoice and information. In this message, only the last two values should be used.
A3.2 [0..1]   +++ Date
SEPAMAIL
rule		 reference date of the document
A3.3 [1..1]   +++ Title
SEPAMAIL
rule		 title of the document
A3.4 [1..1]   +++ Reference
SEPAMAIL
rule		 internal reference
A3.5 [1..1]   +++ Lang
SEPAMAIL
rule		 language used on the document, 2-letter code
A3.6 [0..1]   +++ Contents
SEPAMAIL
rule		 Structured properties of the document
A3.6.1 [1..1]   ++++ mime-type
SEPAMAIL
rule		 Type of data in the document. Usage rule: only the following values can be used
  • image/gif
  • image/jpeg
  • image/png
  • image/vnd.microsoft.icon
  • application/pdf
A3.6.3 [0..1]   ++++ name
SEPAMAIL
rule		 original document name
A3.6.3 [1..1]   ++++ data
SEPAMAIL
rule		 actual document contents

ISO and Non-ISO parts

Each "ReportAndComplements" element describes exactly one payment method, which can be either accepted or rejected.

    • Usage rule 1 : No more than one payment in a given PaymentActivationReport message can be accepted.
    • Usage rule 2 : If the debtor accepts one payment among several proposed by the creditor, the PaymentActivationReport MAY include only the accepted payment. It MAY also include all other payments, each one with a rejected status (RJCT).
    • Usage rule 3 : If the debtor rejects all proposed payments, the PaymentActivationReport message MUST include all payments, each one with a rejected status (RJCT).
    Each RepCompl element has the following contents :
    Ref. Mult. Ch. Depth Message element Requirements
    B [1..*]   + RepCompl
    SEPAMAIL
    rule    		 ISO + non-ISO parts. This element must be present as many times as described by the NbOfReports element, in the header.
    SEPAMAIL
    rule    		 There can only be zero or one Report with an "Accepted" status (i.e. /PaymentActivationReport/sepamail_message_payment_activation_report_001/RepCompl/Report/OrgnlPmtInfAndSts/TxInfAndSts/TxSts set to « ACSP », « ACSC » or « ACWC »), as the payment modality which has been chosen by the debtor.
    It is possible to add as well the payment modalities which have not been accepted.
    Their status is then "Rejected" (i.e. /PaymentActivationReport/sepamail_message_payment_activation_report_001/RepCompl/Report/OrgnlPmtInfAndSts/TxInfAndSts/TxSts set to « RJCT »)
    B1 [1..1]   ++ Report
    SEPAMAIL
    rule    		 CreditorPaymentActivationReport, as per ISO 20022 pain.014.001.01
    SEPAMAIL
    rule    		 The sole report, as payment modality, that has been accepted by the debtor can be used later to generate one or several CT transaction that be embedded within FIToFICstmrCdtTrf messages (pacs.008)
    B2 [1..1]   ++ Complements
    SEPAMAIL
    rule    		 Non-ISO part, described further in this document

    ISO Part : CreditorPaymentActivationRequestStatusReportV01

    Please note : this whole part is directly copied from ISO20022 documents, and is only provided here for ease of reference. The indices in first column match the ones in this document.

    Ref. Mult. Ch. Depth Message element Requirements
    1.0 [1..1]   + GroupHeader
    ISO20022
    rule    		 Set of characteristics shared by all individual transactions included in the message.
    1.1 [1..1]   ++ MessageIdentification
    ISO20022
    rule    		 Point to point reference assigned by the instructing party and sent to the next party in the chain to unambiguously identify the message.
    ISO20022
    rule    		 Usage: The instructing party has to make sure that 'MessageIdentification' is unique per instructed party for a pre-agreed period.
    SEPAMAIL
    rule    		 To be set by the sender of the Activation report
    MAP FROM
    rule    		 [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /GrpHdr /MsgId] (1.1) within the [RUBIS Payment Activation Request] message must not be copied into this structure that shall be set by the party who sends the PaymentActivationReport.
    MAP TO
    rule    		 This structure must not be copied into [ /Document /FIToFICstmrCdtTrf /GrpHdr /MsgId] (1.1) within the [SEPA Inter-Bank Credit Transfer] message
    1.2 [1..1]   ++ CreationDateTime
    ISO20022
    rule    		 Date and time at which the status report was created by the instructing party.
    SEPAMAIL
    rule    		 This is a technical date, which may be different from the same field in main message
    MAP FROM
    rule    		 [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /GrpHdr /CreDtTm] (1.2) within the [RUBIS Payment Activation Request] message must not be copied into this structure that refers to the creation timestamp of the paymentActivationReport itself.
    MAP TO
    rule    		 This structure must not be copied into [ /Document /FIToFICstmrCdtTrf /GrpHdr /CreDtTm] (1.2) within the [SEPA Inter-Bank Credit Transfer] message
    1.3 [1..1]   ++ InitiatingParty
    ISO20022
    rule    		 Party initiating the creditor payment activation request. This can either be the creditor himself or the party that initiates the request on behalf of the creditor.
    SEPAMAIL
    rule    		 Party sending the message. Must indicate the debtor when this message is generated by his action (acceptance or rejection), and the debtor's bank in other cases.
    Notice that this rule is different from the original one provided by ISO20022 and overwrite this ISO20022 rule.
    MAP FROM
    rule    		 [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /GrpHdr /InitgPty] (1.5) within the [RUBIS Payment Activation Request] message must not be copied into this structure that refers to the party who creates the PaymentActivationReport.
    See details below
    1.4 [0..1]   ++ DebtorAgent
    ISO20022
    rule    		 Financial institution servicing an account for the debtor.
    SEPAMAIL
    rule    		 Usage Rule: Only BIC is allowed
    MAP FROM
    rule    		 This structure must be either omitted or copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /DbtrAgt] (2.17) within the [RUBIS Payment Activation Request] message.
    SELF-MAP
    rule    		 This structure and [ /PaymentActivationReport /sepamail_message_payment_activation_report_001 /RepCompl /Report /OrgnlPmtInfAndSts /TxInfAndSts /OrgnlTxRef /DbtrAgt] (3.121) refer to same actor, respectively at group and transaction level.
    1.4/3.1.0 [1..1]   +++ FinancialInstitutionIdentification
    ISO20022
    rule    		 Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme.
    1.4/3.1.1 [0..1]   ++++ BICFI
    ISO20022
    rule    		 Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
    SEPAMAIL
    rule    		 BICFI
    Valid BICs for financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consist of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: INSTITUTION CODE, COUNTRY CODE, LOCATION CODE and BRANCH CODE. The institution code, country code and location code are mandatory, while the branch code is optional.

    Warning: ISO 9362 has been modified in 2013 in order to specify:
    - the first four characters as the PARTY PREFIX (previously INSTITUTION CODE)
    - the two following characters as the COUNTRY CODE
    - the two following characters as the PARTY SUFFIX (previously COUNTRY CODE)
    - the three last characters as the BRANCH IDENTIFIER (previously BRANCH CODE)
    1.4/3.1.2 [0..1]   ++++ ClearingSystemMemberIdentification
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    1.4/3.1.7 [0..1]   ++++ Name
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    1.4/3.1.8 [0..1]   ++++ PostalAddress
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    1.4/3.1.19 [0..1]   ++++ Other
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    1.4/3.1.25 [0..1]   +++ BranchIdentification
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    1.5 [0..1]   ++ CreditorAgent
    ISO20022
    rule    		 Financial institution servicing an account for the creditor.
    SEPAMAIL
    rule    		 Mandatory. BIC.
    MAP FROM
    rule    		 This structure must be either omitted or copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /CdtTrfTx /CdtrAgt] (2.63) within the [RUBIS Payment Activation Request] message, though the copy of the following substructures is optional:
    - ClearingSystemMemberIdentification
    - Name
    - PostalAddress
    - Other
    - BranchIdentification
    SELF-MAP
    rule    		 This structure and [ /PaymentActivationReport /sepamail_message_payment_activation_report_001 /RepCompl /Report /OrgnlPmtInfAndSts /TxInfAndSts /OrgnlTxRef /CdtrAgt] (3.122) refer to same actor, respectively at group and transaction level.
    1.5/3.1.0 [1..1]   +++ FinancialInstitutionIdentification
    ISO20022
    rule    		 Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme.
    1.5/3.1.1 [0..1]   ++++ BICFI
    ISO20022
    rule    		 Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
    SEPAMAIL
    rule    		 BICFI
    Valid BICs for financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consist of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: INSTITUTION CODE, COUNTRY CODE, LOCATION CODE and BRANCH CODE. The institution code, country code and location code are mandatory, while the branch code is optional.

    Warning: ISO 9362 has been modified in 2013 in order to specify:
    - the first four characters as the PARTY PREFIX (previously INSTITUTION CODE)
    - the two following characters as the COUNTRY CODE
    - the two following characters as the PARTY SUFFIX (previously COUNTRY CODE)
    - the three last characters as the BRANCH IDENTIFIER (previously BRANCH CODE)
    1.5/3.1.2 [0..1]   ++++ ClearingSystemMemberIdentification
    ISO20022
    rule    		 Information used to identify a member within a clearing system.
    1.5/3.1.3 [0..1]   +++++ ClearingSystemIdentification
    ISO20022
    rule    		 Specification of a pre-agreed offering between clearing agents or the channel through which the payment instruction is processed.
    1.5/3.1.4 [1..1] | ++++++ Code
    ISO20022
    rule    		 Identification of a clearing system, in a coded form as published in an external list.
    1.5/3.1.5 [1..1] | ++++++ Proprietary
    ISO20022
    rule    		 Identification code for a clearing system that has not yet been identified in the list of clearing systems.
    1.5/3.1.6 [1..1]   +++++ MemberIdentification
    ISO20022
    rule    		 Identification of a member of a clearing system.
    1.5/3.1.7 [0..1]   ++++ Name
    ISO20022
    rule    		 Name by which an agent is known and which is usually used to identify that agent.
    1.5/3.1.8 [0..1]   ++++ PostalAddress
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services.
    ISO20022
    rule    		 Postal address of a party.
    1.5/3.1.9 [0..1]   +++++ AddressType
    ISO20022
    rule    		 Identifies the nature of the postal address.
    Code Name Definition
    ADDR Postal Address is the complete postal address.
    BIZZ Business Address is the business address.
    DLVY DeliveryTo Address is the address to which delivery is to take place.
    HOME Residential Address is the home address.
    MLTO MailTo Address is the address to which mail is sent.
    PBOX POBox Address is a postal office (PO) box.
    1.5/3.1.10 [0..1]   +++++ Department
    ISO20022
    rule    		 Identification of a division of a large organisation or building.
    1.5/3.1.11 [0..1]   +++++ SubDepartment
    ISO20022
    rule    		 Identification of a sub-division of a large organisation or building.
    1.5/3.1.12 [0..1]   +++++ StreetName
    ISO20022
    rule    		 Name of a street or thoroughfare.
    1.5/3.1.13 [0..1]   +++++ BuildingNumber
    ISO20022
    rule    		 Number that identifies the position of a building on a street.
    1.5/3.1.14 [0..1]   +++++ PostCode
    ISO20022
    rule    		 Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
    1.5/3.1.15 [0..1]   +++++ TownName
    ISO20022
    rule    		 Name of a built-up area, with defined boundaries, and a local government.
    1.5/3.1.16 [0..1]   +++++ CountrySubDivision
    ISO20022
    rule    		 Identifies a subdivision of a country such as state, region, country.
    1.5/3.1.17 [0..1]   +++++ Country
    ISO20022
    rule    		 Nation with its own government.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    1.5/3.1.18 [0..7]   +++++ AddressLine
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services, presented in free format text.
    1.5/3.1.19 [0..1]   ++++ Other
    ISO20022
    rule    		 Unique identification of an agent, as assigned by an institution, using an identification scheme.
    1.5/3.1.20 [1..1]   +++++ Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a person.
    1.5/3.1.21 [0..1]   +++++ SchemeName
    ISO20022
    rule    		 Name of the identification scheme.
    1.5/3.1.22 [1..1] | ++++++ Code
    ISO20022
    rule    		 Name of the identification scheme, in a coded form as published in an external list.
    1.5/3.1.23 [1..1] | ++++++ Proprietary
    ISO20022
    rule    		 Name of the identification scheme, in a free text form.
    1.5/3.1.24 [0..1]   +++++ Issuer
    ISO20022
    rule    		 Entity that assigns the identification.
    1.5/3.1.25 [0..1]   +++ BranchIdentification
    ISO20022
    rule    		 Identifies a specific branch of a financial institution
    1.5/3.1.26 [0..1]   ++++ Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a branch of a financial institution.
    1.5/3.1.27 [0..1]   ++++ Name
    ISO20022
    rule    		 Name by which an agent is known and which is usually used to identify that agent.
    1.5/3.1.28 [0..1]   ++++ PostalAddress
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services.
    ISO20022
    rule    		 Postal address of a party.
    1.5/3.1.29 [0..1]   +++++ AddressType
    ISO20022
    rule    		 Identifies the nature of the postal address.
    Code Name Definition
    ADDR Postal Address is the complete postal address.
    BIZZ Business Address is the business address.
    DLVY DeliveryTo Address is the address to which delivery is to take place.
    HOME Residential Address is the home address.
    MLTO MailTo Address is the address to which mail is sent.
    PBOX POBox Address is a postal office (PO) box.
    1.5/3.1.30 [0..1]   +++++ Department
    ISO20022
    rule    		 Identification of a division of a large organisation or building.
    1.5/3.1.31 [0..1]   +++++ SubDepartment
    ISO20022
    rule    		 Identification of a sub-division of a large organisation or building.
    1.5/3.1.32 [0..1]   +++++ StreetName
    ISO20022
    rule    		 Name of a street or thoroughfare.
    1.5/3.1.33 [0..1]   +++++ BuildingNumber
    ISO20022
    rule    		 Number that identifies the position of a building on a street.
    1.5/3.1.34 [0..1]   +++++ PostCode
    ISO20022
    rule    		 Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
    1.5/3.1.35 [0..1]   +++++ TownName
    ISO20022
    rule    		 Name of a built-up area, with defined boundaries, and a local government.
    1.5/3.1.36 [0..1]   +++++ CountrySubDivision
    ISO20022
    rule    		 Identifies a subdivision of a country such as state, region, country.
    1.5/3.1.37 [0..1]   +++++ Country
    ISO20022
    rule    		 Nation with its own government.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    1.5/3.1.38 [0..7]   +++++ AddressLine
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services, presented in free format text.
    2.0 [1..1]   + OriginalGroupInformationAndStatus
    ISO20022
    rule    		 Original group information concerning the group of transactions, to which the status report message refers to.
    2.1 [1..1]   ++ OriginalMessageIdentification
    ISO20022
    rule    		 Point to point reference, as assigned by the original instructing party, to unambiguously identify the original message.
    MAP FROM
    rule    		 Each occurrence of [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /GrpHdr /MsgId] (1.1) within the [RUBIS Payment Activation Request] message must be copied into the relevant occurrence of this structure in order to allow the reconciliation of the PaymentActivationRequest and the PaymentActivationReport.
    2.2 [1..1]   ++ OriginalMessageNameIdentification
    ISO20022
    rule    		 Specifies the original message name identifier to which the message refers.
    SEPAMAIL
    rule    		 Must be valued with "pain.013.001.01"
    2.3 [0..1]   ++ OriginalCreationDateTime
    ISO20022
    rule    		 Date and time at which the original message was created.
    MAP FROM
    rule    		 This structure must be either omitted or copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /GrpHdr /CreDtTm] (1.2) within the [RUBIS Payment Activation Request] message.
    2.4 [0..1]   ++ OriginalNumberOfTransactions
    ISO20022
    rule    		 Number of individual transactions contained in the original message.
    MAP FROM
    rule    		 This structure must be either omitted or copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /GrpHdr /NbOfTxs] (1.3) within the [RUBIS Payment Activation Request] message.
    2.5 [0..1]   ++ OriginalControlSum
    ISO20022
    rule    		 Total of all individual amounts included in the original message, irrespective of currencies.
    MAP FROM
    rule    		 This structure must be either omitted or copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /GrpHdr /CtrlSum] (1.4) within the [RUBIS Payment Activation Request] message.
    2.6 [0..1]   ++ GroupStatus
    ISO20022
    rule    		 Specifies the status of a group of transactions.
    Code Name Definition
    ACCP AcceptedCustomerProfile Preceding check of technical validation was successful. Customer profile check was also successful.
    ACSC AcceptedSettlementCompleted Settlement on the debtor's account has been completed.
    Usage : this can be used by the first agent to report to the debtor that the transaction has been completed. Warning : this status is provided for transaction status reasons, not for financial information. It can only be used after bilateral agreement
    ACSP AcceptedSettlementInProcess All preceding checks such as technical validation and customer profile were successful and therefore the payment initiation has been accepted for execution.
    ACTC AcceptedTechnicalValidation Authentication and syntactical and semantical validation are successful.
    ACWC AcceptedWithChange Instruction is accepted but a change will be made, such as date or remittance not sent.
    PART PartiallyAccepted A number of transactions have been accepted, whereas another number of transactions have not yet achieved 'accepted' status.
    PDNG Pending Payment initiation or individual transaction included in the payment initiation is pending. Further checks and status update will be performed.
    RCVD Received Payment initiation has been received by the receiving agent.
    RJCT Rejected Payment initiation or individual transaction included in the payment initiation has been rejected.

    ISO20022
    rule    		 R1 GroupAndTransactionStatus1Rule
    If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to ACTC, ACCP, ACSP or ACSC, ACCR or ACWC, then transactionInformationAndStatus/TransactionStatus must be different from RJCT.
    ISO20022
    rule    		 R3 GroupAndTransactionStatus3Rule
    If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RJCT, then TransactionInformationAndStatus/TransactionStatus must be different from ACTC, ACCP, ACSP, ACSC, ACCR, ACWC or PDNG.
    ISO20022
    rule    		 R8 StatusReasonInformationRule
    If GroupStatus is present and is different from RJCT or PDNG then StatusReasonInformation/AdditionalInformation must be absent.
    On Condition
    /StatusReasonInformation[1] is present
    And
    /StatusReasonInformation[*]/AdditionalInformation[*] is present
    And
    /GroupStatus is present
    Following Must be True
    /GroupStatus Must be equal to value 'Pending'
    Or
    /GroupStatus Must be equal to value 'Rejected'
    ISO20022
    rule    		 G1 NumberOfTransactionPerStatusGuideline
    OriginalGroupInformationAndStatus/NumberOfTransactionsPerStatus should only be present if GroupStatus
    equals 'PART'.
    ISO20022
    rule    		 StatusReasonInformationRule
    If GroupStatus is present and is different from RJCT or PDNG then StatusReasonInformation/AdditionalInformation must be absent.
    SEPAMAIL
    rule    		 The status, reason code and additional information can be set
    - at group level, providing all the transactions are in the same state
    - at transaction level, in any case
    Setting these data at both level is also allowed
    2.7 [0..*]   ++ StatusReasonInformation
    ISO20022
    rule    		 Set of elements used to provide detailed information on the status reason.
    2.8 [0..1]   +++ Originator
    ISO20022
    rule    		 Party that issues the status.
    SEPAMAIL
    rule    		 Optional for SEPAmail.
    See details below
    2.9 [0..1]   +++ Reason
    ISO20022
    rule    		 Specifies the reason for the status report.
    2.10 [1..1] | ++++ Code
    ISO20022
    rule    		 Reason for the status, as published in an external reason code list.
    ISO20022
    rule    		 R9 StatusReasonRule
    If Reason/Code is equal to NARR, then AddititionalInformation must be present.
    On Condition
    /Reason/Code is equal to value 'Narrative'
    And
    /Reason is present
    And
    /Reason/Code is present
    Following Must be True
    /AdditionalInformation[1] Must be present
    SEPAMAIL
    rule    		 Please refer to the RUBIS PaymentActivationRequest Implementation Guideline to get the reason codes to be used for the different checks.
    SEPAMAIL
    rule    		 Can be used here, if all transactions have the same status.
    2.11 [1..1] | ++++ Proprietary
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    2.12 [0..*]   +++ AdditionalInformation
    ISO20022
    rule    		 Further details on the status reason.
    Usage: Additional information can be used for several purposes such as the reporting of repaired information.
    ISO20022
    rule    		 R8 StatusReasonInformationRule
    If GroupStatus is present and is different from RJCT or PDNG then StatusReasonInformation/AdditionalInformation must be absent.
    On Condition
    /StatusReasonInformation[1] is present
    And
    /StatusReasonInformation[*]/AdditionalInformation[*] is present
    And
    /GroupStatus is present
    Following Must be True
    /GroupStatus Must be equal to value 'Pending'
    Or
    /GroupStatus Must be equal to value 'Rejected'
    ISO20022
    rule    		 R9 StatusReasonRule
    If Reason/Code is equal to NARR, then AddititionalInformation must be present.
    On Condition
    /Reason/Code is equal to value 'Narrative'
    And
    /Reason is present
    And
    /Reason/Code is present
    Following Must be True
    /AdditionalInformation[1] Must be present
    ISO20022
    rule    		 StatusReasonInformationRule
    If GroupStatus is present and is different from RJCT or PDNG then StatusReasonInformation/AdditionalInformation must be absent.
    2.13 [0..*]   ++ NumberOfTransactionsPerStatus
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.0 [0..*]   + OriginalPaymentInformationAndStatus
    ISO20022
    rule    		 Information concerning the original payment information, to which the status report message refers.
    3.1 [1..1]   ++ OriginalPaymentInformationIdentification
    ISO20022
    rule    		 Unique identification, as assigned by the original sending party, to unambiguously identify the original payment information group.
    MAP FROM
    rule    		 Each occurrence of [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /PmtInfId] (2.1) within the [RUBIS Payment Activation Request] message must be copied into the relevant occurrence of this structure.
    3.2 [0..1]   ++ OriginalNumberOfTransactions
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.3 [0..1]   ++ OriginalControlSum
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.4 [0..1]   ++ PaymentInformationStatus
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.5 [0..*]   ++ StatusReasonInformation
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.11 [0..*]   ++ NumberOfTransactionsPerStatus
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.15 [0..*]   ++ TransactionInformationAndStatus
    ISO20022
    rule    		 Set of elements used to provide information on the original transactions to which the status report message
    3.16 [0..1]   +++ StatusIdentification
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.17 [0..1]   +++ OriginalInstructionIdentification
    ISO20022
    rule    		 Unique identification, as assigned by the original instructing party for the original instructed party, to
    unambiguously identify the original instruction.
    MAP FROM
    rule    		 Each occurrence of [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /CdtTrfTx /PmtId /InstrId] (2.22) within the [RUBIS Payment Activation Request] message must be copied into the relevant occurrence of this structure.
    3.18 [0..1]   +++ OriginalEndToEndIdentification
    SEPAMAIL
    rule    		 Mandatory for SEPAmail
    ISO20022
    rule    		 Unique identification, as assigned by the original initiating party, to unambiguously identify the original transaction.
    MAP FROM
    rule    		 Each occurrence of [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /CdtTrfTx /PmtId /EndToEndId] (2.23) within the [RUBIS Payment Activation Request] message must be copied into the relevant occurrence of this structure.
    MAP TO
    rule    		 This structure must not be forwarded into [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /PmtId /EndToEndId] (2.3) within the [SEPA Inter-Bank Credit Transfer] message which shall instead contain the debtor end-to-end reference.
    It is reminded that the creditor end-to-end reference will be enclosed within the first block of 35 characters of the unstructured remittance information tag. This first block shall be right padded with space characters.
    3.19 [0..1]   +++ TransactionStatus
    ISO20022
    rule    		 Specifies the status of a transaction, in a coded form.
    ISO20022
    rule    		 Specifies the status of a transaction, in a coded form.
    Code Name Definition
    ACCP AcceptedCustomerProfile Preceding check of technical validation was successful. Customer profile check was also successful.
    ACSC AcceptedSettlementCompleted Settlement on the debtor's account has been completed.
    Usage : this can be used by the first agent to report to the debtor that the transaction has been completed. Warning : this status is provided for transaction status reasons, not for financial information. It can only be used after bilateral agreement
    ACSP AcceptedSettlementInProcess All preceding checks such as technical validation and customer profile were successful and therefore the payment initiation has been accepted for execution.
    ACTC AcceptedTechnicalValidation Authentication and syntactical and semantical validation are successful.
    ACWC AcceptedWithChange Instruction is accepted but a change will be made, such as date or remittance not sent.
    PDNG Pending Payment initiation or individual transaction included in the payment initiation is pending. Further checks and status update will be performed.
    RJCT Rejected Payment initiation or individual transaction included in the payment initiation has been rejected.
    ISO20022
    rule    		 R1 GroupAndTransactionStatus1Rule
    If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to ACTC, ACCP, ACSP or ACSC, ACCR or ACWC, then transactionInformationAndStatus/TransactionStatus must be different from RJCT.
    ISO20022
    rule    		 R3 GroupAndTransactionStatus3Rule
    If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RJCT, then TransactionInformationAndStatus/TransactionStatus must be different from ACTC, ACCP, ACSP, ACSC, ACCR, ACWC or PDNG.
    ISO20022
    rule    		 R10 PaymentInformationStatusAcceptedRule
    If OriginalPaymentInformationAndStatus/PaymentInformationStatus is present and is equal to ACTC, ACCP, ACSP, ACSC or ACWC, then TransactionInformationAndStatus/TransactionStatus must be different from RJCT.
    On Condition
    /PaymentInformationStatus is present
    And
    /PaymentInformationStatus is within DataType [Code] ValidationGroupStatus1Code
    And
    /TransactionInformationAndStatus[1]/TransactionStatus is present
    Following Must be True
    /TransactionInformationAndStatus[*]/TransactionStatus Must be different from value 'Rejected'
    ISO20022
    rule    		 R12 PaymentInformationStatusRejectedRule
    If OriginalPaymentInformationAndStatus/PaymentInformationStatus is present and is equal to RJCT, then
    TransactionInformationAndStatus/TransactionStatus, if present, must be equal to RJCT.
    On Condition
    /PaymentInformationStatus is present
    And
    /PaymentInformationStatus is equal to value 'Rejected'
    And
    /TransactionInformationAndStatus[1]/TransactionStatus is present
    Following Must be True
    /TransactionInformationAndStatus[*]/TransactionStatus Must not be within DataType [Code]
    ValidationGroupStatus2Code
    SEPAMAIL
    rule    		 The status, reason code and additional information can be set
    - at group level, providing all the transactions are in the same state
    - at transaction level, in any case
    Setting these data at both level is also allowed
    SEPAMAIL
    rule    		 Mandatory.
    Usage rules : following values are accepted:
    * ACSC (Accepted with settlement complete),
    * ACSP (Accepted by debtor),
    * ACWC (Accepted with Change -- the change can be either payment date, amount or anything else),
    * RJCT (Rejected).
    In the future, the "ACCP" code will also be usable.
    To indicate guarantee of payment, the PmtGuarantee element, in the non-ISO part, must be used.
    3.20 [0..*]   +++ StatusReasonInformation
    ISO20022
    rule    		 Set of elements used to provide detailed information on the status reason.
    ISO20022
    rule    		 StatusReasonRule
    If Reason/Code is equal to NARR, then AddititionalInformation must be present.
    3.21 [0..1]   ++++ Originator
    ISO20022
    rule    		 Party that issues the status.
    SEPAMAIL
    rule    		 Optional for SEPAmail.
    See details below
    3.22 [0..1]   ++++ Reason
    ISO20022
    rule    		 Specifies the reason for the status report.
    SEPAMAIL
    rule    		 Please refer to the RUBIS PaymentActivationRequest Implementation Guideline to get the reason codes to be used for the different checks.
    3.23 [1..1] | +++++ Code
    ISO20022
    rule    		 Reason for the status, as published in an external reason code list.
    ISO20022
    rule    		 R9 StatusReasonRule
    If Reason/Code is equal to NARR, then AddititionalInformation must be present.
    On Condition
    /Reason/Code is equal to value 'Narrative'
    And
    /Reason is present
    And
    /Reason/Code is present
    Following Must be True
    /AdditionalInformation[1] Must be present
    3.24 [1..1] | +++++ Proprietary
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.25 [0..*]   ++++ AdditionalInformation
    ISO20022
    rule    		 Further details on the status reason.
    Usage: Additional information can be used for several purposes such as the reporting of repaired information.
    ISO20022
    rule    		 R9 StatusReasonRule
    If Reason/Code is equal to NARR, then AddititionalInformation must be present.
    On Condition
    /Reason/Code is equal to value 'Narrative'
    And
    /Reason is present
    And
    /Reason/Code is present
    Following Must be True
    /AdditionalInformation[1] Must be present
    3.26 [0..*]   +++ ChargesInformation
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.29 [0..1]   +++ AcceptanceDateTime
    ISO20022
    rule    		 Point in time when the payment order from the initiating party meets the processing conditions of the account servicing agent. This means that the account servicing agent has received the payment order and has applied checks such as authorisation, availability of funds.
    3.30 [0..1]   +++ AccountServicerReference
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.31 [0..1]   +++ ClearingSystemReference
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.32 [0..1]   +++ OriginalTransactionReference
    ISO20022
    rule    		 Set of key elements used to identify the original transaction that is being referred to.
    3.33 [0..1]   ++++ InterbankSettlementAmount
    ISO20022
    rule    		 Amount of money moved between the instructing agent and the instructed agent.
    ISO20022
    rule    		 CurrencyAmount
    The number of fractional digits (or minor unit of currency) must comply with ISO 4217.
    Note: The decimal separator is a dot.
      [1..1]   +++++ Currency
    ISO20022
    rule    		 ActiveOrHistoricCurrency
    The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged.
    3.34 [0..1]   ++++ Amount
    ISO20022
    rule    		 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.
    3.35 [1..1] | +++++ InstructedAmount
    ISO20022
    rule    		 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.
    ISO20022
    rule    		 CurrencyAmount
    The number of fractional digits (or minor unit of currency) must comply with ISO 4217.
    Note: The decimal separator is a dot.
    SEPAMAIL
    rule    		 This must match exactly the original amount in ActivationRequest message (2.36)
    MAP FROM
    rule    		 Each occurrence of [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /CdtTrfTx /Amt /InstdAmt] (2.36) within the [RUBIS Payment Activation Request] message must be copied into the relevant occurrence of this structure.
    MAP TO
    rule    		 This structure must not be forwarded into [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /InstdAmt] (2.31) within the [SEPA Inter-Bank Credit Transfer] message which is a white field within EPC Implementation Guidelines.
    If the amount has not been modified by the debtor (tag B2.5.2 not present), the value must be used to set the relevant [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /IntrBkSttlmAmt] (2.18) within the [SEPA Inter-Bank Credit Transfer] message.
      [1..1] | ++++++ Currency
    ISO20022
    rule    		 ActiveOrHistoricCurrency
    The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged.
    3.36 [1..1] | +++++ EquivalentAmount
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.39 [0..1]   ++++ InterbankSettlementDate
    ISO20022
    rule    		 Date on which the amount of money ceases to be available to the agent that owes it and when the amount of money becomes available to the agent to which it is due.
    MAP TO
    rule    		 This structure must not be forwarded into [ /Document /FIToFICstmrCdtTrf /GrpHdr /IntrBkSttlmDt] (1.7) within the [SEPA Inter-Bank Credit Transfer] message.
    3.40 [0..1]   ++++ RequestedCollectionDate
    ISO20022
    rule    		 Date and time at which the creditor requests that the amount of money is to be collected from the debtor.
    SEPAMAIL
    rule    		 If present, this field MUST contain the RequestedExecutionDate (2.14) from ActivationRequest message
    MAP FROM
    rule    		 This structure must be either omitted or copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /ReqdExctnDt] (2.14) within the [RUBIS Payment Activation Request] message
    3.41 [0..1]   ++++ RequestedExecutionDate
    ISO20022
    rule    		 Date at which the initiating party requests the clearing agent to process the payment.
    Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date when the cheque must be generated by the bank.
    SEPAMAIL
    rule    		 If present, contains the date at which debtor requires execution.
    SEPAMAIL
    rule    		 Must be either omitted or valued by the debtor to indicate to his bank his requested execution date.
    MAP TO
    rule    		 This structure must not be forwarded into [ /Document /FIToFICstmrCdtTrf /GrpHdr /IntrBkSttlmDt] (1.7) within the [SEPA Inter-Bank Credit Transfer] message.
    3.42 [0..1]   ++++ CreditorSchemeIdentification
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.43 [0..1]   ++++ SettlementInformation
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.55 [0..1]   ++++ PaymentTypeInformation
    ISO20022
    rule    		 Set of elements used to further specify the type of transaction.
    3.56 [0..1]   +++++ InstructionPriority
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.57 [0..1]   +++++ ClearingChannel
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.58 [0..1]   +++++ ServiceLevel
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.61 [0..1]   +++++ LocalInstrument
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.64 [0..1]   +++++ SequenceType
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.65 [0..1]   +++++ CategoryPurpose
    ISO20022
    rule    		 Specifies the high level purpose of the instruction based on a set of pre-defined categories.
    Usage: This is used by the initiating party to provide information concerning the processing of the payment. It is likely to trigger special processing by any of the agents involved in the payment chain.
    MAP FROM
    rule    		 Each occurrence of [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /PmtTpInf /CtgyPurp] (2.11) within the [RUBIS Payment Activation Request] message must be copied into the relevant occurrence of this structure.
    MAP TO
    rule    		 This structure may be forwarded into [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /PmtTpInf /CtgyPurp] (2.15) within the [SEPA Inter-Bank Credit Transfer] message.
    3.66 [1..1] | ++++++ Code
    ISO20022
    rule    		 Category purpose, as published in an external category purpose code list.
    3.67 [1..1] | ++++++ Proprietary
    ISO20022
    rule    		 Category purpose, in a proprietary form.
    3.68 [0..1]   ++++ PaymentMethod
    ISO20022
    rule    		 Specifies the means of payment that will be used to move the amount of money.
    Code Name Definition
    CHK Cheque Written order to a bank to pay a certain amount of money from one person to another person.
    DD DirectDebit Collection of an amount of money from the debtor's bank account by the creditor. The amount of money and dates of collections may vary.
    TRA TransferAdvice Transfer of an amount of money in the books of the account servicer. An advice should be sent back to the account owner.
    TRF CreditTransfer Transfer of an amount of money in the books of the account servicer.</tbody>

    MAP FROM
    rule    		 Each occurrence of this structure must be either omitted or copied with the relevant occurrence of [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /PmtMtd] (2.2) within the [RUBIS Payment Activation Request] message.
    3.69 [0..1]   ++++ MandateRelatedInformation
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.86 [0..1]   ++++ RemittanceInformation
    SEPAMAIL
    rule    		 Only unstructured remittance information is allowed
    3.87 [0..*]   +++++ Unstructured
    ISO20022
    rule    		 Information supplied to enable the matching/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts' receivable system, in an unstructured form.
    SEPAMAIL
    rule    		 One occurrence must be present and must hold the concatenation of:
    • a first block, that contains the End-To-End Reference originated by the debtor and is right-padded with space characters up to 35 characters.
    • a second block, that contains, either the remittance information of the creditor, or an updated version provided by the debtor. This block is up to 105 characters long.
    MAP FROM
    rule    		 Each occurrence of this structure must be valued with the concatenation of the two following values
    * the end-to-end reference provided by the Debtor and padded up to 35 characters with space characters
    * and, within a limit of 105 characters that may need truncation:
    ** either a value given by the debtor
    ** or the copy of [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /CdtTrfTx /RmtInf /Ustrd] (2.83) within the [RUBIS Payment Activation Request] message.
    MAP TO
    rule    		 This structure must be forwarded into the [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /RmtInf /Ustrd] (2.76) within the [SEPA Inter-Bank Credit Transfer] message with replacement of the first 35 characters long block with the creditor end-to-end reference. This reference shall be padded with space characters.
    3.88 [0..*]   +++++ Structured
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.118 [0..1]   ++++ UltimateDebtor
    ISO20022
    rule    		 Ultimate party that owes an amount of money to the (ultimate) creditor.
    MAP FROM
    rule    		 This structure must be copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /UltmtDbtr] (2.18) within the [RUBIS Payment Activation Request] message. However, the copy of the substructures is only mandatory for data that will be eventually forwarded within the SEPA Credit Transfer Core Mandatory Subset (*). The other data may optionally be copied.
    MAP TO
    rule    		 This structure must be forwarded into [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /UltmtDbtr] (2.47) within the [SEPA Inter-Bank Credit Transfer] message with respect of the limits of the SEPA Credit Transfer Core Mandatory Subset (*).
    See details below
    3.119 [0..1]   ++++ Debtor
    SEPAMAIL
    rule    		 Mandatory for SEPAmail
    ISO20022
    rule    		 Party that owes an amount of money to the (ultimate) creditor.
    MAP FROM
    rule    		 This structure must be copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /Dbtr] (2.15) within the [RUBIS Payment Activation Request] message.
    MAP TO
    rule    		 This structure must not be forwarded into [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /Dbtr] (2.49) within the [SEPA Inter-Bank Credit Transfer] message that must be filled with the debtor's bank own customer data, with respect of the limits of the SEPA Credit Transfer Core Mandatory Subset.

    See details below
    3.120 [0..1]   ++++ DebtorAccount
    SEPAMAIL
    rule    		 Mandatory for SEPAmail
    ISO20022
    rule    		 Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.
    MAP FROM
    rule    		 This structure must be copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /DbtrAcct] (2.16) within the [RUBIS Payment Activation Request] message, though the copy of the following substructures is optional:
    - Type
    - Currency
    - Name
    MAP TO
    rule    		 This structure must be forwarded into [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /DbtrAcct] (2.50) within the [SEPA Inter-Bank Credit Transfer] message with respect of the limits of the SEPA Credit Transfer Core Mandatory Subset (*).
    3.120/1.1.0 [1..1]   +++++ Identification
    ISO20022
    rule    		 Unique and unambiguous identification for the account between the account owner and the account servicer.
    3.120/1.1.1 [1..1] | ++++++ IBAN
    ISO20022
    rule    		 International Bank Account Number (IBAN) - identifier used internationally by financial institutions to uniquely identify the account of a customer. Further specifications of the format and content of the IBAN can be found in the standard ISO 13616 "Banking and related financial services - International Bank Account Number (IBAN)" version 1997-10-01, or later revisions.
    ISO20022
    rule    		 A valid IBAN consists of all three of the following components: Country Code, check digits and BBAN.
    SEPAMAIL
    rule    		 Mandatory. IBAN or QXBAN
    3.120/1.1.2 [1..1] | ++++++ Other
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.120/1.1.8 [0..1]   +++++ Type
    ISO20022
    rule    		 Specifies the nature, or use of the account.
    3.120/1.1.9 [1..1] | ++++++ Code  
    3.120/1.1.10 [1..1] | ++++++ Proprietary  
    3.120/1.1.11 [0..1]   +++++ Currency
    ISO20022
    rule    		 Identification of the currency in which the account is held.
    Usage: Currency should only be used in case one and the same account number covers several currencies and the initiating party needs to identify which currency needs to be used for settlement on the account.
    ISO20022
    rule    		 ActiveOrHistoricCurrency
    The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged.
    3.120/1.1.12 [0..1]   +++++ Name
    ISO20022
    rule    		 Name of the account, as assigned by the account servicing institution, in agreement with the account owner in order to provide an additional means of identification of the account.
    Usage: The account name is different from the account owner name. The account name is used in certain user communities to provide a means of identifying the account, in addition to the account owner's identity and the account number.
    3.121 [0..1]   ++++ DebtorAgent
    SEPAMAIL
    rule    		 Mandatory for SEPAmail
    ISO20022
    rule    		 Financial institution servicing an account for the debtor.
    MAP FROM
    rule    		 This structure must be copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /DbtrAgt] (2.17) within the [RUBIS Payment Activation Request] message.
    SELF-MAP
    rule    		 [ /PaymentActivationReport /sepamail_message_payment_activation_report_001 /RepCompl /Report /GrpHdr /DbtrAgt] (1.4) and this structure refer to same actor, respectively at group and transaction level.
    MAP TO
    rule    		 This structure must be forwarded into [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /DbtrAgt] (2.51) within the [SEPA Inter-Bank Credit Transfer] message with respect of the limits of the SEPA Credit Transfer Core Mandatory Subset (*).
    3.121/3.1.0 [1..1]   +++++ FinancialInstitutionIdentification
    ISO20022
    rule    		 Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme.
    3.121/3.1.1 [0..1]   ++++++ BICFI
    ISO20022
    rule    		 Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
    SEPAMAIL
    rule    		 BICFI
    Valid BICs for financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consist of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: INSTITUTION CODE, COUNTRY CODE, LOCATION CODE and BRANCH CODE. The institution code, country code and location code are mandatory, while the branch code is optional.

    Warning: ISO 9362 has been modified in 2013 in order to specify:
    - the first four characters as the PARTY PREFIX (previously INSTITUTION CODE)
    - the two following characters as the COUNTRY CODE
    - the two following characters as the PARTY SUFFIX (previously COUNTRY CODE)
    - the three last characters as the BRANCH IDENTIFIER (previously BRANCH CODE)
    SEPAMAIL
    rule    		 Mandatory
    3.121/3.1.2 [0..1]   ++++++ ClearingSystemMemberIdentification
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.121/3.1.7 [0..1]   ++++++ Name
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.121/3.1.8 [0..1]   ++++++ PostalAddress
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.121/3.1.19 [0..1]   ++++++ Other
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.121/3.1.25 [0..1]   +++++ BranchIdentification
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.122 [1..1]   ++++ CreditorAgent
    ISO20022
    rule    		 Financial institution servicing an account for the creditor.
    MAP FROM
    rule    		 This structure must be copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /CdtTrfTx /CdtrAgt] (2.63) within the [RUBIS Payment Activation Request] message, though the copy of the following substructures is optional:
    - ClearingSystemMemberIdentification
    - Name
    - PostalAddress
    - Other
    - BranchIdentification
    SELF-MAP
    rule    		 [ /PaymentActivationReport /sepamail_message_payment_activation_report_001 /RepCompl /Report /GrpHdr /CdtrAgt] (1.5) and this structure refer to same actor, respectively at group and transaction level.
    MAP TO
    rule    		 This structure must be forwarded into [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /CdtrAgt] (2.53) within the [SEPA Inter-Bank Credit Transfer] message with respect of the limits of the SEPA Credit Transfer Core Mandatory Subset (*).
    3.122/3.1.0 [1..1]   +++++ FinancialInstitutionIdentification
    ISO20022
    rule    		 Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme.
    3.122/3.1.1 [0..1]   ++++++ BICFI
    ISO20022
    rule    		 Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
    SEPAMAIL
    rule    		 BICFI
    Valid BICs for financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consist of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: INSTITUTION CODE, COUNTRY CODE, LOCATION CODE and BRANCH CODE. The institution code, country code and location code are mandatory, while the branch code is optional.

    Warning: ISO 9362 has been modified in 2013 in order to specify:
    - the first four characters as the PARTY PREFIX (previously INSTITUTION CODE)
    - the two following characters as the COUNTRY CODE
    - the two following characters as the PARTY SUFFIX (previously COUNTRY CODE)
    - the three last characters as the BRANCH IDENTIFIER (previously BRANCH CODE)
    SEPAMAIL
    rule    		 Mandatory
    3.122/3.1.2 [0..1]   ++++++ ClearingSystemMemberIdentification
    ISO20022
    rule    		 Information used to identify a member within a clearing system.
    3.122/3.1.3 [0..1]   +++++++ ClearingSystemIdentification
    ISO20022
    rule    		 Specification of a pre-agreed offering between clearing agents or the channel through which the payment instruction is processed.
    3.122/3.1.4 [1..1] | ++++++++ Code
    ISO20022
    rule    		 Identification of a clearing system, in a coded form as published in an external list.
    3.122/3.1.5 [1..1] | ++++++++ Proprietary
    ISO20022
    rule    		 Identification code for a clearing system that has not yet been identified in the list of clearing systems.
    3.122/3.1.6 [1..1]   +++++++ MemberIdentification
    ISO20022
    rule    		 Identification of a member of a clearing system.
    3.122/3.1.7 [0..1]   ++++++ Name
    ISO20022
    rule    		 Name by which an agent is known and which is usually used to identify that agent.
    3.122/3.1.8 [0..1]   ++++++ PostalAddress
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services.
    ISO20022
    rule    		 Postal address of a party.
    3.122/3.1.9 [0..1]   +++++++ AddressType
    ISO20022
    rule    		 Identifies the nature of the postal address.
    Code Name Definition
    ADDR Postal Address is the complete postal address.
    BIZZ Business Address is the business address.
    DLVY DeliveryTo Address is the address to which delivery is to take place.
    HOME Residential Address is the home address.
    MLTO MailTo Address is the address to which mail is sent.
    PBOX POBox Address is a postal office (PO) box.
    3.122/3.1.10 [0..1]   +++++++ Department
    ISO20022
    rule    		 Identification of a division of a large organisation or building.
    3.122/3.1.11 [0..1]   +++++++ SubDepartment
    ISO20022
    rule    		 Identification of a sub-division of a large organisation or building.
    3.122/3.1.12 [0..1]   +++++++ StreetName
    ISO20022
    rule    		 Name of a street or thoroughfare.
    3.122/3.1.13 [0..1]   +++++++ BuildingNumber
    ISO20022
    rule    		 Number that identifies the position of a building on a street.
    3.122/3.1.14 [0..1]   +++++++ PostCode
    ISO20022
    rule    		 Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
    3.122/3.1.15 [0..1]   +++++++ TownName
    ISO20022
    rule    		 Name of a built-up area, with defined boundaries, and a local government.
    3.122/3.1.16 [0..1]   +++++++ CountrySubDivision
    ISO20022
    rule    		 Identifies a subdivision of a country such as state, region, country.
    3.122/3.1.17 [0..1]   +++++++ Country
    ISO20022
    rule    		 Nation with its own government.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.122/3.1.18 [0..7]   +++++++ AddressLine
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services, presented in free format text.
    3.122/3.1.19 [0..1]   ++++++ Other
    ISO20022
    rule    		 Unique identification of an agent, as assigned by an institution, using an identification scheme.
    3.122/3.1.20 [1..1]   +++++++ Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a person.
    3.122/3.1.21 [0..1]   +++++++ SchemeName
    ISO20022
    rule    		 Name of the identification scheme.
    3.122/3.1.22 [1..1] | ++++++++ Code
    ISO20022
    rule    		 Name of the identification scheme, in a coded form as published in an external list.
    3.122/3.1.23 [1..1] | ++++++++ Proprietary
    ISO20022
    rule    		 Name of the identification scheme, in a free text form.
    3.122/3.1.24 [0..1]   +++++++ Issuer
    ISO20022
    rule    		 Entity that assigns the identification.
    3.122/3.1.25 [0..1]   +++++ BranchIdentification
    ISO20022
    rule    		 Identifies a specific branch of a financial institution
    3.122/3.1.26 [0..1]   ++++++ Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a branch of a financial institution.
    3.122/3.1.27 [0..1]   ++++++ Name
    ISO20022
    rule    		 Name by which an agent is known and which is usually used to identify that agent.
    3.122/3.1.28 [0..1]   ++++++ PostalAddress
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services.
    ISO20022
    rule    		 Postal address of a party.
    3.122/3.1.29 [0..1]   +++++++ AddressType
    ISO20022
    rule    		 Identifies the nature of the postal address.
    Code Name Definition
    ADDR Postal Address is the complete postal address.
    BIZZ Business Address is the business address.
    DLVY DeliveryTo Address is the address to which delivery is to take place.
    HOME Residential Address is the home address.
    MLTO MailTo Address is the address to which mail is sent.
    PBOX POBox Address is a postal office (PO) box.
    3.122/3.1.30 [0..1]   +++++++ Department
    ISO20022
    rule    		 Identification of a division of a large organisation or building.
    3.122/3.1.31 [0..1]   +++++++ SubDepartment
    ISO20022
    rule    		 Identification of a sub-division of a large organisation or building.
    3.122/3.1.32 [0..1]   +++++++ StreetName
    ISO20022
    rule    		 Name of a street or thoroughfare.
    3.122/3.1.33 [0..1]   +++++++ BuildingNumber
    ISO20022
    rule    		 Number that identifies the position of a building on a street.
    3.122/3.1.34 [0..1]   +++++++ PostCode
    ISO20022
    rule    		 Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
    3.122/3.1.35 [0..1]   +++++++ TownName
    ISO20022
    rule    		 Name of a built-up area, with defined boundaries, and a local government.
    3.122/3.1.36 [0..1]   +++++++ CountrySubDivision
    ISO20022
    rule    		 Identifies a subdivision of a country such as state, region, country.
    3.122/3.1.37 [0..1]   +++++++ Country
    ISO20022
    rule    		 Nation with its own government.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.122/3.1.38 [0..7]   +++++++ AddressLine
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services, presented in free format text.
    3.123 [1..1]   ++++ Creditor
    ISO20022
    rule    		 Party to which an amount of money is due.
    SEPAMAIL
    rule    		 Mandatory
    MAP FROM
    rule    		 This structure must be copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /CdtTrfTx /Cdtr] (2.64) within the [RUBIS Payment Activation Request] message.
    MAP TO
    rule    		 This structure must be forwarded into [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /Cdtr] (2.55) within the [SEPA Inter-Bank Credit Transfer] message with respect of the limits of the SEPA Credit Transfer Core Mandatory Subset (*).
    See details below
    3.124 [0..1]   ++++ CreditorAccount
    SEPAMAIL
    rule    		 Mandatory for SEPAmail
    ISO20022
    rule    		 Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.
    MAP FROM
    rule    		 This structure must be copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /CdtTrfTx /CdtrAcct] (2.65) within the [RUBIS Payment Activation Request] message, though the copy of the following substructures is optional:
    - Type
    - Currency
    - Name
    MAP TO
    rule    		 This structure must be forwarded into [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /CdtrAcct] (2.56) within the [SEPA Inter-Bank Credit Transfer] message with respect of the limits of the SEPA Credit Transfer Core Mandatory Subset (*).
    3.124/1.1.0 [1..1]   +++++ Identification
    ISO20022
    rule    		 Unique and unambiguous identification for the account between the account owner and the account servicer.
    3.124/1.1.1 [1..1] | ++++++ IBAN
    ISO20022
    rule    		 International Bank Account Number (IBAN) - identifier used internationally by financial institutions to uniquely identify the account of a customer. Further specifications of the format and content of the IBAN can be found in the standard ISO 13616 "Banking and related financial services - International Bank Account Number (IBAN)" version 1997-10-01, or later revisions.
    ISO20022
    rule    		 A valid IBAN consists of all three of the following components: Country Code, check digits and BBAN.
    SEPAMAIL
    rule    		 Mandatory
    3.124/1.1.2 [1..1] | ++++++ Other
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.124/1.1.8 [0..1]   +++++ Type
    ISO20022
    rule    		 Specifies the nature, or use of the account.
    3.124/1.1.9 [1..1] | ++++++ Code  
    3.124/1.1.10 [1..1] | ++++++ Proprietary  
    3.124/1.1.11 [0..1]   +++++ Currency
    ISO20022
    rule    		 Identification of the currency in which the account is held.
    Usage: Currency should only be used in case one and the same account number covers several currencies and the initiating party needs to identify which currency needs to be used for settlement on the account.
    ISO20022
    rule    		 ActiveOrHistoricCurrency
    The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged.
    3.124/1.1.12 [0..1]   +++++ Name
    ISO20022
    rule    		 Name of the account, as assigned by the account servicing institution, in agreement with the account owner in order to provide an additional means of identification of the account.
    Usage: The account name is different from the account owner name. The account name is used in certain user communities to provide a means of identifying the account, in addition to the account owner's identity and the account number.
    3.125 [0..1]   ++++ UltimateCreditor
    ISO20022
    rule    		 Ultimate party to which an amount of money is due.
    MAP FROM
    rule    		 This structure must be copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /CdtTrfTx /UltmtCdtr] (2.66) within the [RUBIS Payment Activation Request] message. However, the copy of the substructures is only mandatory for data that will be eventually forwarded within the SEPA Credit Transfer Core Mandatory Subset (*). The other data may optionally be copied.
    MAP TO
    rule    		 This structure must be forwarded into [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /UltmtCdtr] (2.57) within the [SEPA Inter-Bank Credit Transfer] message with respect of the limits of the SEPA Credit Transfer Core Mandatory Subset (*).
    See details below

    Details of fields under /PaymentActivationReport/sepamail_message_payment_activation_report_001/RepCompl/Report/GrpHdr/InitgPty element (previously indexed as 1.3)

    Ref. Mult. Ch. Depth Message element Requirements
    1.3/4.1.0 [0..1]   + Name
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    SEPAMAIL
    rule    		 Name is mandatory if it is not a bank
    1.3/4.1.1 [0..1]   + PostalAddress
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services.
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services.
    ISO20022
    rule    		 Postal address of a party.
    1.3/4.1.2 [0..1]   ++ AddressType
    ISO20022
    rule    		 Identifies the nature of the postal address.
    ISO20022
    rule    		 Identifies the nature of the postal address.
    Code Name Definition
    ADDR Postal Address is the complete postal address.
    BIZZ Business Address is the business address.
    DLVY DeliveryTo Address is the address to which delivery is to take place.
    HOME Residential Address is the home address.
    MLTO MailTo Address is the address to which mail is sent.
    PBOX POBox Address is a postal office (PO) box.
    1.3/4.1.3 [0..1]   ++ Department
    ISO20022
    rule    		 Identification of a division of a large organisation or building.
    1.3/4.1.4 [0..1]   ++ SubDepartment
    ISO20022
    rule    		 Identification of a sub-division of a large organisation or building.
    1.3/4.1.5 [0..1]   ++ StreetName
    ISO20022
    rule    		 Name of a street or thoroughfare.
    1.3/4.1.6 [0..1]   ++ BuildingNumber
    ISO20022
    rule    		 Number that identifies the position of a building on a street.
    1.3/4.1.7 [0..1]   ++ PostCode
    ISO20022
    rule    		 Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
    1.3/4.1.8 [0..1]   ++ TownName
    ISO20022
    rule    		 Name of a built-up area, with defined boundaries, and a local government.
    1.3/4.1.9 [0..1]   ++ CountrySubDivision
    ISO20022
    rule    		 Identifies a subdivision of a country such as state, region, country.
    1.3/4.1.10 [0..1]   ++ Country
    ISO20022
    rule    		 Nation with its own government.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    1.3/4.1.11 [0..7]   ++ AddressLine
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services, presented in free format text.
    1.3/4.1.12 [0..1]   + Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a party.
    1.3/4.1.13 [1..1] | ++ OrganisationIdentification
    ISO20022
    rule    		 Unique and unambiguous way to identify an organisation.
    1.3/4.1.14 [0..1] | +++ AnyBICIdentifier
    ISO20022
    rule    		 Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
    ISO20022
    rule    		 AnyBIC
    Only a valid Business identifier code is allowed. Business identifier codes for financial or non-financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consists of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: INSTITUTION CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The institution code, country code and location code are mandatory, while the branch code is optional.

    Warning: ISO 9362 has been modified in 2013 in order to specify:
    - the first four characters as the PARTY PREFIX (previously INSTITUTION CODE)
    - the two following characters as the COUNTRY CODE
    - the two following characters as the PARTY SUFFIX (previously COUNTRY CODE)
    - the three last characters as the BRANCH IDENTIFIER (previously BRANCH CODE)
    SEPAMAIL
    rule    		 BIC (in Id) is mandatory if it is a bank
    1.3/4.1.15 [0..*] | +++ Other
    ISO20022
    rule    		 Unique identification of an organisation, as assigned by an institution, using an identification scheme.
    1.3/4.1.16 [1..1] | ++++ Identification
    ISO20022
    rule    		 Identification assigned by an institution.
    1.3/4.1.17 [0..1] | ++++ SchemeName
    ISO20022
    rule    		 Name of the identification scheme.
    1.3/4.1.18 [1..1] | | +++++ Code
    ISO20022
    rule    		 Name of the identification scheme, in a coded form as published in an external list.
    1.3/4.1.19 [1..1] | | +++++ Proprietary
    ISO20022
    rule    		 Name of the identification scheme, in a free text form.
    1.3/4.1.20 [0..1] | ++++ Issuer
    ISO20022
    rule    		 Entity that assigns the identification.
    1.3/4.1.21 [1..1] | ++ PrivateIdentification
    ISO20022
    rule    		 Unique and unambiguous identification of a person, eg, passport.
    1.3/4.1.22 [0..1] | +++ DateAndPlaceOfBirth
    ISO20022
    rule    		 Date and place of birth of a person.
    1.3/4.1.23 [1..1] | ++++ BirthDate
    ISO20022
    rule    		 Date on which a person is born.
    1.3/4.1.24 [0..1] | ++++ ProvinceOfBirth
    ISO20022
    rule    		 Province where a person was born.
    1.3/4.1.25 [1..1] | ++++ CityOfBirth
    ISO20022
    rule    		 City where a person was born.
    1.3/4.1.26 [1..1] | ++++ CountryOfBirth
    ISO20022
    rule    		 Country where a person was born.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    1.3/4.1.27 [0..*] | +++ Other
    ISO20022
    rule    		 Unique identification of a person, as assigned by an institution, using an identification scheme.
    1.3/4.1.28 [1..1] | ++++ Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a person.
    1.3/4.1.29 [0..1] | ++++ SchemeName
    ISO20022
    rule    		 Name of the identification scheme.
    1.3/4.1.30 [1..1] | | +++++ Code
    ISO20022
    rule    		 Name of the identification scheme, in a coded form as published in an external list.
    1.3/4.1.31 [1..1] | | +++++ Proprietary
    ISO20022
    rule    		 Name of the identification scheme, in a free text form.
    1.3/4.1.32 [0..1] | ++++ Issuer
    ISO20022
    rule    		 Entity that assigns the identification.
    1.3/4.1.33 [0..1]   + CountryOfResidence
    ISO20022
    rule    		 Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    1.3/4.1.34 [0..1]   + ContactDetails
    ISO20022
    rule    		 Set of elements used to indicate how to contact the party.
    1.3/4.1.35 [0..1]   ++ NamePrefix
    ISO20022
    rule    		 Specifies the terms used to formally address a person.
    Code Name Definition
    DOCT Doctor Title of the person is Doctor or Dr.
    MADM Madam Title of the person is Madam.
    MISS Miss Title of the person is Miss.
    MIST Mister Title of the person is Mister or Mr.
    1.3/4.1.36 [0..1]   ++ Name
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    1.3/4.1.37 [0..1]   ++ PhoneNumber
    ISO20022
    rule    		 Collection of information that identifies a phone number, as defined by telecom services.
    1.3/4.1.38 [0..1]   ++ MobileNumber
    ISO20022
    rule    		 Collection of information that identifies a mobile phone number, as defined by telecom services.
    1.3/4.1.39 [0..1]   ++ FaxNumber
    ISO20022
    rule    		 Collection of information that identifies a FAX number, as defined by telecom services.
    1.3/4.1.40 [0..1]   ++ EmailAddress
    ISO20022
    rule    		 Address for electronic mail (e-mail).
    1.3/4.1.41 [0..1]   ++ Other
    ISO20022
    rule    		 Contact details in another form.

    Details of fields under /PaymentActivationReport/sepamail_message_payment_activation_report_001/RepCompl/Report/OrgnlGrpInfAndSts/StsRsnInf/Orgtr element (previously indexed as 2.8)

    Ref. Mult. Ch. Depth Message element Requirements
    2.8/4.1.0 [0..1]   + Name
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    SEPAMAIL
    rule    		 Name is mandatory if the originator is not a bank
    2.8/4.1.1 [0..1]   + PostalAddress
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    2.8/4.1.12 [0..1]   + Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a party.
    2.8/4.1.13 [1..1] | ++ OrganisationIdentification
    ISO20022
    rule    		 Unique and unambiguous way to identify an organisation.
    2.8/4.1.14 [0..1] | +++ AnyBICIdentifier
    ISO20022
    rule    		 Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
    ISO20022
    rule    		 AnyBIC
    Only a valid Business identifier code is allowed. Business identifier codes for financial or non-financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consists of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: INSTITUTION CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The institution code, country code and location code are mandatory, while the branch code is optional.

    Warning: ISO 9362 has been modified in 2013 in order to specify:
    - the first four characters as the PARTY PREFIX (previously INSTITUTION CODE)
    - the two following characters as the COUNTRY CODE
    - the two following characters as the PARTY SUFFIX (previously COUNTRY CODE)
    - the three last characters as the BRANCH IDENTIFIER (previously BRANCH CODE)
    SEPAMAIL
    rule    		 BIC is mandatory if the originator is a bank
    2.8/4.1.15 [0..*] | +++ Other
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    2.8/4.1.21 [1..1] | ++ PrivateIdentification
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    2.8/4.1.33 [0..1]   + CountryOfResidence
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    2.8/4.1.34 [0..1]   + ContactDetails
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail

    Details of fields under /PaymentActivationReport/sepamail_message_payment_activation_report_001/RepCompl/Report/OrgnlPmtInfAndSts/TxInfAndSts/StsRsnInf/Orgtr element (previously indexed as 3.21)

    Ref. Mult. Ch. Depth Message element Requirements
    3.21/4.1.0 [0..1]   + Name
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    SEPAMAIL
    rule    		 Name is mandatory if the originator is not a bank
    3.21/4.1.1 [0..1]   + PostalAddress
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.21/4.1.12 [0..1]   + Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a party.
    3.21/4.1.13 [1..1] | ++ OrganisationIdentification
    ISO20022
    rule    		 Unique and unambiguous way to identify an organisation.
    3.21/4.1.14 [0..1] | +++ AnyBICIdentifier
    ISO20022
    rule    		 Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
    ISO20022
    rule    		 AnyBIC
    Only a valid Business identifier code is allowed. Business identifier codes for financial or non-financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consists of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: INSTITUTION CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The institution code, country code and location code are mandatory, while the branch code is optional.

    Warning: ISO 9362 has been modified in 2013 in order to specify:
    - the first four characters as the PARTY PREFIX (previously INSTITUTION CODE)
    - the two following characters as the COUNTRY CODE
    - the two following characters as the PARTY SUFFIX (previously COUNTRY CODE)
    - the three last characters as the BRANCH IDENTIFIER (previously BRANCH CODE)
    SEPAMAIL
    rule    		 BIC is mandatory if the originator is a bank
    3.21/4.1.15 [0..*] | +++ Other
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.21/4.1.21 [1..1] | ++ PrivateIdentification
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.21/4.1.33 [0..1]   + CountryOfResidence
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.21/4.1.34 [0..1]   + ContactDetails
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail

    Details of fields under /PaymentActivationReport/sepamail_message_payment_activation_report_001/RepCompl/Report/OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/UltmtDbtr element (previously indexed as 3.118)

    Ref. Mult. Ch. Depth Message element Requirements
    3.118/4.1.0 [0..1]   + Name
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    3.118/4.1.1 [0..1]   + PostalAddress
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services.
    ISO20022
    rule    		 Postal address of a party.
    3.118/4.1.2 [0..1]   ++ AddressType
    ISO20022
    rule    		 Identifies the nature of the postal address.
    Code Name Definition
    ADDR Postal Address is the complete postal address.
    BIZZ Business Address is the business address.
    DLVY DeliveryTo Address is the address to which delivery is to take place.
    HOME Residential Address is the home address.
    MLTO MailTo Address is the address to which mail is sent.
    PBOX POBox Address is a postal office (PO) box.
    3.118/4.1.3 [0..1]   ++ Department
    ISO20022
    rule    		 Identification of a division of a large organisation or building.
    3.118/4.1.4 [0..1]   ++ SubDepartment
    ISO20022
    rule    		 Identification of a sub-division of a large organisation or building.
    3.118/4.1.5 [0..1]   ++ StreetName
    ISO20022
    rule    		 Name of a street or thoroughfare.
    3.118/4.1.6 [0..1]   ++ BuildingNumber
    ISO20022
    rule    		 Number that identifies the position of a building on a street.
    3.118/4.1.7 [0..1]   ++ PostCode
    ISO20022
    rule    		 Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
    3.118/4.1.8 [0..1]   ++ TownName
    ISO20022
    rule    		 Name of a built-up area, with defined boundaries, and a local government.
    3.118/4.1.9 [0..1]   ++ CountrySubDivision
    ISO20022
    rule    		 Identifies a subdivision of a country such as state, region, country.
    3.118/4.1.10 [0..1]   ++ Country
    ISO20022
    rule    		 Nation with its own government.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.118/4.1.11 [0..7]   ++ AddressLine
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services, presented in free format text.
    3.118/4.1.12 [0..1]   + Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a party.
    3.118/4.1.13 [1..1] | ++ OrganisationIdentification
    ISO20022
    rule    		 Unique and unambiguous way to identify an organisation.
    3.118/4.1.14 [0..1] | +++ AnyBICIdentifier
    ISO20022
    rule    		 Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
    ISO20022
    rule    		 AnyBIC
    Only a valid Business identifier code is allowed. Business identifier codes for financial or non-financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consists of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: INSTITUTION CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The institution code, country code and location code are mandatory, while the branch code is optional.

    Warning: ISO 9362 has been modified in 2013 in order to specify:
    - the first four characters as the PARTY PREFIX (previously INSTITUTION CODE)
    - the two following characters as the COUNTRY CODE
    - the two following characters as the PARTY SUFFIX (previously COUNTRY CODE)
    - the three last characters as the BRANCH IDENTIFIER (previously BRANCH CODE)
    3.118/4.1.15 [0..*] | +++ Other
    ISO20022
    rule    		 Unique identification of an organisation, as assigned by an institution, using an identification scheme.
    3.118/4.1.16 [1..1] | ++++ Identification
    ISO20022
    rule    		 Identification assigned by an institution.
    3.118/4.1.17 [0..1] | ++++ SchemeName
    ISO20022
    rule    		 Name of the identification scheme.
    3.118/4.1.18 [1..1] | | +++++ Code
    ISO20022
    rule    		 Name of the identification scheme, in a coded form as published in an external list.
    3.118/4.1.19 [1..1] | | +++++ Proprietary
    ISO20022
    rule    		 Name of the identification scheme, in a free text form.
    3.118/4.1.20 [0..1] | ++++ Issuer
    ISO20022
    rule    		 Entity that assigns the identification.
    3.118/4.1.21 [1..1] | ++ PrivateIdentification
    ISO20022
    rule    		 Unique and unambiguous identification of a person, eg, passport.
    3.118/4.1.22 [0..1] | +++ DateAndPlaceOfBirth
    ISO20022
    rule    		 Date and place of birth of a person.
    3.118/4.1.23 [1..1] | ++++ BirthDate
    ISO20022
    rule    		 Date on which a person is born.
    3.118/4.1.24 [0..1] | ++++ ProvinceOfBirth
    ISO20022
    rule    		 Province where a person was born.
    3.118/4.1.25 [1..1] | ++++ CityOfBirth
    ISO20022
    rule    		 City where a person was born.
    3.118/4.1.26 [1..1] | ++++ CountryOfBirth
    ISO20022
    rule    		 Country where a person was born.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.118/4.1.27 [0..*] | +++ Other
    ISO20022
    rule    		 Unique identification of a person, as assigned by an institution, using an identification scheme.
    3.118/4.1.28 [1..1] | ++++ Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a person.
    3.118/4.1.29 [0..1] | ++++ SchemeName
    ISO20022
    rule    		 Name of the identification scheme.
    3.118/4.1.30 [1..1] | | +++++ Code
    ISO20022
    rule    		 Name of the identification scheme, in a coded form as published in an external list.
    3.118/4.1.31 [1..1] | | +++++ Proprietary
    ISO20022
    rule    		 Name of the identification scheme, in a free text form.
    3.118/4.1.32 [0..1] | ++++ Issuer
    ISO20022
    rule    		 Entity that assigns the identification.
    3.118/4.1.33 [0..1]   + CountryOfResidence
    ISO20022
    rule    		 Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.118/4.1.34 [0..1]   + ContactDetails
    ISO20022
    rule    		 Set of elements used to indicate how to contact the party.
    3.118/4.1.35 [0..1]   ++ NamePrefix
    ISO20022
    rule    		 Specifies the terms used to formally address a person.
    Code Name Definition
    DOCT Doctor Title of the person is Doctor or Dr.
    MADM Madam Title of the person is Madam.
    MISS Miss Title of the person is Miss.
    MIST Mister Title of the person is Mister or Mr.
    3.118/4.1.36 [0..1]   ++ Name
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    3.118/4.1.37 [0..1]   ++ PhoneNumber
    ISO20022
    rule    		 Collection of information that identifies a phone number, as defined by telecom services.
    3.118/4.1.38 [0..1]   ++ MobileNumber
    ISO20022
    rule    		 Collection of information that identifies a mobile phone number, as defined by telecom services.
    3.118/4.1.39 [0..1]   ++ FaxNumber
    ISO20022
    rule    		 Collection of information that identifies a FAX number, as defined by telecom services.
    3.118/4.1.40 [0..1]   ++ EmailAddress
    ISO20022
    rule    		 Address for electronic mail (e-mail).
    3.118/4.1.41 [0..1]   ++ Other
    ISO20022
    rule    		 Contact details in another form.

    Details of fields under /PaymentActivationReport/sepamail_message_payment_activation_report_001/RepCompl/Report/OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/Dbtr element (previously indexed as 3.119)

    Ref. Mult. Ch. Depth Message element Requirements
    3.119/4.1.0 [0..1]   + Name
    SEPAMAIL
    rule    		 Mandatory for SEPAmail
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    3.119/4.1.1 [0..1]   + PostalAddress
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services.
    ISO20022
    rule    		 Postal address of a party.
    3.119/4.1.2 [0..1]   ++ AddressType
    ISO20022
    rule    		 Identifies the nature of the postal address.
    Code Name Definition
    ADDR Postal Address is the complete postal address.
    BIZZ Business Address is the business address.
    DLVY DeliveryTo Address is the address to which delivery is to take place.
    HOME Residential Address is the home address.
    MLTO MailTo Address is the address to which mail is sent.
    PBOX POBox Address is a postal office (PO) box.
    3.119/4.1.3 [0..1]   ++ Department
    ISO20022
    rule    		 Identification of a division of a large organisation or building.
    3.119/4.1.4 [0..1]   ++ SubDepartment
    ISO20022
    rule    		 Identification of a sub-division of a large organisation or building.
    3.119/4.1.5 [0..1]   ++ StreetName
    ISO20022
    rule    		 Name of a street or thoroughfare.
    3.119/4.1.6 [0..1]   ++ BuildingNumber
    ISO20022
    rule    		 Number that identifies the position of a building on a street.
    3.119/4.1.7 [0..1]   ++ PostCode
    ISO20022
    rule    		 Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
    3.119/4.1.8 [0..1]   ++ TownName
    ISO20022
    rule    		 Name of a built-up area, with defined boundaries, and a local government.
    3.119/4.1.9 [0..1]   ++ CountrySubDivision
    ISO20022
    rule    		 Identifies a subdivision of a country such as state, region, country.
    3.119/4.1.10 [0..1]   ++ Country
    ISO20022
    rule    		 Nation with its own government.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.119/4.1.11 [0..7]   ++ AddressLine
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services, presented in free format text.
    3.119/4.1.12 [0..1]   + Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a party.
    3.119/4.1.13 [1..1] | ++ OrganisationIdentification
    ISO20022
    rule    		 Unique and unambiguous way to identify an organisation.
    3.119/4.1.14 [0..1] | +++ AnyBICIdentifier
    ISO20022
    rule    		 Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
    ISO20022
    rule    		 AnyBIC
    Only a valid Business identifier code is allowed. Business identifier codes for financial or non-financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consists of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: INSTITUTION CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The institution code, country code and location code are mandatory, while the branch code is optional.

    Warning: ISO 9362 has been modified in 2013 in order to specify:
    - the first four characters as the PARTY PREFIX (previously INSTITUTION CODE)
    - the two following characters as the COUNTRY CODE
    - the two following characters as the PARTY SUFFIX (previously COUNTRY CODE)
    - the three last characters as the BRANCH IDENTIFIER (previously BRANCH CODE)
    3.119/4.1.15 [0..*] | +++ Other
    ISO20022
    rule    		 Unique identification of an organisation, as assigned by an institution, using an identification scheme.
    3.119/4.1.16 [1..1] | ++++ Identification
    ISO20022
    rule    		 Identification assigned by an institution.
    3.119/4.1.17 [0..1] | ++++ SchemeName
    ISO20022
    rule    		 Name of the identification scheme.
    3.119/4.1.18 [1..1] | | +++++ Code
    ISO20022
    rule    		 Name of the identification scheme, in a coded form as published in an external list.
    3.119/4.1.19 [1..1] | | +++++ Proprietary
    ISO20022
    rule    		 Name of the identification scheme, in a free text form.
    3.119/4.1.20 [0..1] | ++++ Issuer
    ISO20022
    rule    		 Entity that assigns the identification.
    3.119/4.1.21 [1..1] | ++ PrivateIdentification
    ISO20022
    rule    		 Unique and unambiguous identification of a person, eg, passport.
    3.119/4.1.22 [0..1] | +++ DateAndPlaceOfBirth
    ISO20022
    rule    		 Date and place of birth of a person.
    3.119/4.1.23 [1..1] | ++++ BirthDate
    ISO20022
    rule    		 Date on which a person is born.
    3.119/4.1.24 [0..1] | ++++ ProvinceOfBirth
    ISO20022
    rule    		 Province where a person was born.
    3.119/4.1.25 [1..1] | ++++ CityOfBirth
    ISO20022
    rule    		 City where a person was born.
    3.119/4.1.26 [1..1] | ++++ CountryOfBirth
    ISO20022
    rule    		 Country where a person was born.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.119/4.1.27 [0..*] | +++ Other
    ISO20022
    rule    		 Unique identification of a person, as assigned by an institution, using an identification scheme.
    3.119/4.1.28 [1..1] | ++++ Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a person.
    3.119/4.1.29 [0..1] | ++++ SchemeName
    ISO20022
    rule    		 Name of the identification scheme.
    3.119/4.1.30 [1..1] | | +++++ Code
    ISO20022
    rule    		 Name of the identification scheme, in a coded form as published in an external list.
    3.119/4.1.31 [1..1] | | +++++ Proprietary
    ISO20022
    rule    		 Name of the identification scheme, in a free text form.
    3.119/4.1.32 [0..1] | ++++ Issuer
    ISO20022
    rule    		 Entity that assigns the identification.
    3.119/4.1.33 [0..1]   + CountryOfResidence
    ISO20022
    rule    		 Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.119/4.1.34 [0..1]   + ContactDetails
    ISO20022
    rule    		 Set of elements used to indicate how to contact the party.
    3.119/4.1.35 [0..1]   ++ NamePrefix
    ISO20022
    rule    		 Specifies the terms used to formally address a person.
    Code Name Definition
    DOCT Doctor Title of the person is Doctor or Dr.
    MADM Madam Title of the person is Madam.
    MISS Miss Title of the person is Miss.
    MIST Mister Title of the person is Mister or Mr.
    3.119/4.1.36 [0..1]   ++ Name
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    3.119/4.1.37 [0..1]   ++ PhoneNumber
    ISO20022
    rule    		 Collection of information that identifies a phone number, as defined by telecom services.
    3.119/4.1.38 [0..1]   ++ MobileNumber
    ISO20022
    rule    		 Collection of information that identifies a mobile phone number, as defined by telecom services.
    3.119/4.1.39 [0..1]   ++ FaxNumber
    ISO20022
    rule    		 Collection of information that identifies a FAX number, as defined by telecom services.
    3.119/4.1.40 [0..1]   ++ EmailAddress
    ISO20022
    rule    		 Address for electronic mail (e-mail).
    3.119/4.1.41 [0..1]   ++ Other
    ISO20022
    rule    		 Contact details in another form.

    Details of fields under /PaymentActivationReport/sepamail_message_payment_activation_report_001/RepCompl/Report/OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/Cdtr element (previously indexed as 3.123)

    Ref. Mult. Ch. Depth Message element Requirements
    3.123/4.1.0 [0..1]   + Name
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    3.123/4.1.1 [0..1]   + PostalAddress
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services.
    ISO20022
    rule    		 Postal address of a party.
    3.123/4.1.2 [0..1]   ++ AddressType
    ISO20022
    rule    		 Identifies the nature of the postal address.
    Code Name Definition
    ADDR Postal Address is the complete postal address.
    BIZZ Business Address is the business address.
    DLVY DeliveryTo Address is the address to which delivery is to take place.
    HOME Residential Address is the home address.
    MLTO MailTo Address is the address to which mail is sent.
    PBOX POBox Address is a postal office (PO) box.
    3.123/4.1.3 [0..1]   ++ Department
    ISO20022
    rule    		 Identification of a division of a large organisation or building.
    3.123/4.1.4 [0..1]   ++ SubDepartment
    ISO20022
    rule    		 Identification of a sub-division of a large organisation or building.
    3.123/4.1.5 [0..1]   ++ StreetName
    ISO20022
    rule    		 Name of a street or thoroughfare.
    3.123/4.1.6 [0..1]   ++ BuildingNumber
    ISO20022
    rule    		 Number that identifies the position of a building on a street.
    3.123/4.1.7 [0..1]   ++ PostCode
    ISO20022
    rule    		 Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
    3.123/4.1.8 [0..1]   ++ TownName
    ISO20022
    rule    		 Name of a built-up area, with defined boundaries, and a local government.
    3.123/4.1.9 [0..1]   ++ CountrySubDivision
    ISO20022
    rule    		 Identifies a subdivision of a country such as state, region, country.
    3.123/4.1.10 [0..1]   ++ Country
    ISO20022
    rule    		 Nation with its own government.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.123/4.1.11 [0..7]   ++ AddressLine
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services, presented in free format text.
    3.123/4.1.12 [0..1]   + Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a party.
    3.123/4.1.13 [1..1] | ++ OrganisationIdentification
    ISO20022
    rule    		 Unique and unambiguous way to identify an organisation.
    SEPAMAIL
    rule    		 Mandatory for ICQX@SCHEME registered users.
    3.123/4.1.14 [0..1] | +++ AnyBICIdentifier
    ISO20022
    rule    		 Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
    ISO20022
    rule    		 AnyBIC
    Only a valid Business identifier code is allowed. Business identifier codes for financial or non-financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consists of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: INSTITUTION CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The institution code, country code and location code are mandatory, while the branch code is optional.

    Warning: ISO 9362 has been modified in 2013 in order to specify:
    - the first four characters as the PARTY PREFIX (previously INSTITUTION CODE)
    - the two following characters as the COUNTRY CODE
    - the two following characters as the PARTY SUFFIX (previously COUNTRY CODE)
    - the three last characters as the BRANCH IDENTIFIER (previously BRANCH CODE)
    3.123/4.1.15 [0..*] | +++ Other
    ISO20022
    rule    		 Unique identification of an organisation, as assigned by an institution, using an identification scheme.
    3.123/4.1.16 [1..1] | ++++ Identification
    ISO20022
    rule    		 Identification assigned by an institution.
    MAP FROM
    rule    		 [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /CdtTrfTx /Cdtr /Id /OrgId /Othr /Id] (2.64/4.1.16) within the [RUBIS Payment Activation Request] message, when containing an ICQX, must be forwarded into this structure
    3.123/4.1.17 [0..1] | ++++ SchemeName
    ISO20022
    rule    		 Name of the identification scheme.
    3.123/4.1.18 [1..1] | | +++++ Code
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.123/4.1.19 [1..1] | | +++++ Proprietary
    ISO20022
    rule    		 Name of the identification scheme, in a free text form.
    SEPAMAIL
    rule    		 Must contain the value "SEPAMAIL.EU" when present
    MAP FROM
    rule    		 [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /CdtTrfTx /Cdtr /Id /OrgId /Othr /SchmeNm /Prtry] (2.64/4.1.19) within the [RUBIS Payment Activation Request] message, if valued with "SEPAMAIL.EU", must be forwarded into this structure.
    3.123/4.1.20 [0..1] | ++++ Issuer
    ISO20022
    rule    		 Entity that assigns the identification.
    3.123/4.1.21 [1..1] | ++ PrivateIdentification
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.123/4.1.33 [0..1]   + CountryOfResidence
    SEPAMAIL
    rule    		 Not Allowed for SEPAmail
    3.123/4.1.34 [0..1]   + ContactDetails
    ISO20022
    rule    		 Set of elements used to indicate how to contact the party.
    3.123/4.1.35 [0..1]   ++ NamePrefix
    ISO20022
    rule    		 Specifies the terms used to formally address a person.
    Code Name Definition
    DOCT Doctor Title of the person is Doctor or Dr.
    MADM Madam Title of the person is Madam.
    MISS Miss Title of the person is Miss.
    MIST Mister Title of the person is Mister or Mr.
    3.123/4.1.36 [0..1]   ++ Name
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    3.123/4.1.37 [0..1]   ++ PhoneNumber
    ISO20022
    rule    		 Collection of information that identifies a phone number, as defined by telecom services.
    3.123/4.1.38 [0..1]   ++ MobileNumber
    ISO20022
    rule    		 Collection of information that identifies a mobile phone number, as defined by telecom services.
    3.123/4.1.39 [0..1]   ++ FaxNumber
    ISO20022
    rule    		 Collection of information that identifies a FAX number, as defined by telecom services.
    3.123/4.1.40 [0..1]   ++ EmailAddress
    ISO20022
    rule    		 Address for electronic mail (e-mail).
    3.123/4.1.41 [0..1]   ++ Other
    ISO20022
    rule    		 Contact details in another form.

    Details of fields under /PaymentActivationReport/sepamail_message_payment_activation_report_001/RepCompl/Report/OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/UltmtCdtr element (previously indexed as 3.125)

    Ref. Mult. Ch. Depth Message element Requirements
    3.125/4.1.0 [0..1]   + Name
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    3.125/4.1.1 [0..1]   + PostalAddress
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services.
    ISO20022
    rule    		 Postal address of a party.
    3.125/4.1.2 [0..1]   ++ AddressType
    ISO20022
    rule    		 Identifies the nature of the postal address.
    Code Name Definition
    ADDR Postal Address is the complete postal address.
    BIZZ Business Address is the business address.
    DLVY DeliveryTo Address is the address to which delivery is to take place.
    HOME Residential Address is the home address.
    MLTO MailTo Address is the address to which mail is sent.
    PBOX POBox Address is a postal office (PO) box.
    3.125/4.1.3 [0..1]   ++ Department
    ISO20022
    rule    		 Identification of a division of a large organisation or building.
    3.125/4.1.4 [0..1]   ++ SubDepartment
    ISO20022
    rule    		 Identification of a sub-division of a large organisation or building.
    3.125/4.1.5 [0..1]   ++ StreetName
    ISO20022
    rule    		 Name of a street or thoroughfare.
    3.125/4.1.6 [0..1]   ++ BuildingNumber
    ISO20022
    rule    		 Number that identifies the position of a building on a street.
    3.125/4.1.7 [0..1]   ++ PostCode
    ISO20022
    rule    		 Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
    3.125/4.1.8 [0..1]   ++ TownName
    ISO20022
    rule    		 Name of a built-up area, with defined boundaries, and a local government.
    3.125/4.1.9 [0..1]   ++ CountrySubDivision
    ISO20022
    rule    		 Identifies a subdivision of a country such as state, region, country.
    3.125/4.1.10 [0..1]   ++ Country
    ISO20022
    rule    		 Nation with its own government.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.125/4.1.11 [0..7]   ++ AddressLine
    ISO20022
    rule    		 Information that locates and identifies a specific address, as defined by postal services, presented in free format text.
    3.125/4.1.12 [0..1]   + Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a party.
    3.125/4.1.13 [1..1] | ++ OrganisationIdentification
    ISO20022
    rule    		 Unique and unambiguous way to identify an organisation.
    3.125/4.1.14 [0..1] | +++ AnyBICIdentifier
    ISO20022
    rule    		 Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
    ISO20022
    rule    		 AnyBIC
    Only a valid Business identifier code is allowed. Business identifier codes for financial or non-financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consists of eight (8) or eleven (11) contiguous characters comprising the first three or all four of the following components: INSTITUTION CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE. The institution code, country code and location code are mandatory, while the branch code is optional.

    Warning: ISO 9362 has been modified in 2013 in order to specify:
    - the first four characters as the PARTY PREFIX (previously INSTITUTION CODE)
    - the two following characters as the COUNTRY CODE
    - the two following characters as the PARTY SUFFIX (previously COUNTRY CODE)
    - the three last characters as the BRANCH IDENTIFIER (previously BRANCH CODE)
    3.125/4.1.15 [0..*] | +++ Other
    ISO20022
    rule    		 Unique identification of an organisation, as assigned by an institution, using an identification scheme.
    3.125/4.1.16 [1..1] | ++++ Identification
    ISO20022
    rule    		 Identification assigned by an institution.
    3.125/4.1.17 [0..1] | ++++ SchemeName
    ISO20022
    rule    		 Name of the identification scheme.
    3.125/4.1.18 [1..1] | | +++++ Code
    ISO20022
    rule    		 Name of the identification scheme, in a coded form as published in an external list.
    3.125/4.1.19 [1..1] | | +++++ Proprietary
    ISO20022
    rule    		 Name of the identification scheme, in a free text form.
    3.125/4.1.20 [0..1] | ++++ Issuer
    ISO20022
    rule    		 Entity that assigns the identification.
    3.125/4.1.21 [1..1] | ++ PrivateIdentification
    ISO20022
    rule    		 Unique and unambiguous identification of a person, eg, passport.
    3.125/4.1.22 [0..1] | +++ DateAndPlaceOfBirth
    ISO20022
    rule    		 Date and place of birth of a person.
    3.125/4.1.23 [1..1] | ++++ BirthDate
    ISO20022
    rule    		 Date on which a person is born.
    3.125/4.1.24 [0..1] | ++++ ProvinceOfBirth
    ISO20022
    rule    		 Province where a person was born.
    3.125/4.1.25 [1..1] | ++++ CityOfBirth
    ISO20022
    rule    		 City where a person was born.
    3.125/4.1.26 [1..1] | ++++ CountryOfBirth
    ISO20022
    rule    		 Country where a person was born.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.125/4.1.27 [0..*] | +++ Other
    ISO20022
    rule    		 Unique identification of a person, as assigned by an institution, using an identification scheme.
    3.125/4.1.28 [1..1] | ++++ Identification
    ISO20022
    rule    		 Unique and unambiguous identification of a person.
    3.125/4.1.29 [0..1] | ++++ SchemeName
    ISO20022
    rule    		 Name of the identification scheme.
    3.125/4.1.30 [1..1] | | +++++ Code
    ISO20022
    rule    		 Name of the identification scheme, in a coded form as published in an external list.
    3.125/4.1.31 [1..1] | | +++++ Proprietary
    ISO20022
    rule    		 Name of the identification scheme, in a free text form.
    3.125/4.1.32 [0..1] | ++++ Issuer
    ISO20022
    rule    		 Entity that assigns the identification.
    3.125/4.1.33 [0..1]   + CountryOfResidence
    ISO20022
    rule    		 Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
    ISO20022
    rule    		 Country
    The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
    3.125/4.1.34 [0..1]   + ContactDetails
    ISO20022
    rule    		 Set of elements used to indicate how to contact the party.
    3.125/4.1.35 [0..1]   ++ NamePrefix
    ISO20022
    rule    		 Specifies the terms used to formally address a person.
    Code Name Definition
    DOCT Doctor Title of the person is Doctor or Dr.
    MADM Madam Title of the person is Madam.
    MISS Miss Title of the person is Miss.
    MIST Mister Title of the person is Mister or Mr.
    3.125/4.1.36 [0..1]   ++ Name
    ISO20022
    rule    		 Name by which a party is known and which is usually used to identify that party.
    3.125/4.1.37 [0..1]   ++ PhoneNumber
    ISO20022
    rule    		 Collection of information that identifies a phone number, as defined by telecom services.
    3.125/4.1.38 [0..1]   ++ MobileNumber
    ISO20022
    rule    		 Collection of information that identifies a mobile phone number, as defined by telecom services.
    3.125/4.1.39 [0..1]   ++ FaxNumber
    ISO20022
    rule    		 Collection of information that identifies a FAX number, as defined by telecom services.
    3.125/4.1.40 [0..1]   ++ EmailAddress
    ISO20022
    rule    		 Address for electronic mail (e-mail).
    3.125/4.1.41 [0..1]   ++ Other
    ISO20022
    rule    		 Contact details in another form.

    Non-ISO part

    This part is only used by the SEPAmail/RUBIS system, to provide additional services both to creditor and debtor.

    Ref. Mult. Ch. Depth Message element Requirements
    B2.1 [0..1]   + OtherPmtMtd
    SEPAMAIL
    rule    		 This field must be used if the debtor prefers another payment method than the one requested by the creditor.
    B2.1.1 [1..1]   ++ PaymentMethod
    SEPAMAIL
    rule    		 Payment method chosen by debtor. Possible values are CHK (check), TRF (Transfer), DD (Direct Debit), and CARD (payment card). If this field is present, the PaymentMethod field, in the ISO part, will be ignored.
    B2.1.2 [0..1]   ++ PmtMtdId
    SEPAMAIL
    rule    		 Payment method-specific identifier: mandatory for CARD (the card number), it is optional in all other cases. For TRF payment, this field can be used to indicate another IBAN to be used for the transfer. For CHK or DD, it may hold an internal reference number.
    B2.2 [0..1]   + PmtGuarantee
    SEPAMAIL
    rule    		 Should be set to true if the bank guarantees the related payment
    B2.3 [1..1]   + ImmPmt
    SEPAMAIL
    rule    		 Mandatory. Reflects the decision of the Debtor about accepting immediate payment, if proposed by the creditor.
    MAP FROM
    rule    		 This structure is set to «False» if [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Complements /PmtCond /ImmPmtAccepted] (B2.2.2) within the [RUBIS Payment Activation Request] message was set to «False».
    Otherwise, ImmPmt is set to true (accepts) or false (does not accept) according to the choice of the debtor.
    B2.4 [0..1]   + ImmPmtRebate
    MAP FROM
    rule    		 This structure must be either omitted or copied from [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Complements /PmtCond /ImmPmtRebate] (B2.2.4) within the [RUBIS Payment Activation Request] message.
    B2.5 [0..*]   + PmtModif
    SEPAMAIL
    rule    		 Debtor modified the amount to be paid, whether more or less than the instructed amount. This is possible only if the creditor accepts it (B2.2.1 true in the Request message). Each modified sum must be indicated by a PmtModif element and the associated PmtId.
    MAP FROM
    rule    		 This structure is only set if the relevant [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Complements /PmtCond /PmtModifAccepted] (B2.2.1) within the [RUBIS Payment Activation Request] message was set to «True».
    B2.5.1 [1..1]   ++ PaymentIdentification
    SEPAMAIL
    rule    		 The related PaymentIdentification, as it appears in the Request message.
    MAP FROM
    rule    		 Each occurrence of this structure must be copied from the relevant occurrence of [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Request /PmtInf /PmtInfId] (2.1) within the [RUBIS Payment Activation Request] message in case of modification of the amount by the debtor.
    B2.5.2 [1..1]   ++ Amount
    ISO20022
    rule    		 CurrencyAmount
    The number of fractional digits (or minor unit of currency) must comply with ISO 4217.
    Note: The decimal separator is a dot.
    SEPAMAIL
    rule    		 This structure must be set by the debtor in case of modification in order to specify the accepted amount, possibly with a currency code attribute.
    MAP TO
    rule    		 This structure, if present, must be forwarded within each relevant [ /Document /FIToFICstmrCdtTrf /CdtTrfTxInf /IntrBkSttlmAmt] (2.18) within the [SEPA Inter-Bank Credit Transfer] message.
      [1..1]   +++ Currency
    ISO20022
    rule    		 ActiveOrHistoricCurrency
    The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged.
    B2.6 [0..1]   + TrfNature
    SEPAMAIL
    rule    		 The nature of the requested transfer. Possible values are IMMED and TERM. This field must match exactly the TrfNature field of the associated ActivationRequest message.
    MAP FROM
    rule    		 This structure must exactly match [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Complements /TrfNature] (B2.6) within the [RUBIS Payment Activation Request] message.
    B2.7 [0..3]   + CustRef
    SEPAMAIL
    rule    		 Customer reference, delivered by the creditor, unambiguously identifying the debtor in the creditor reference system. If several ReportComplements are present, this field must have the same value in all structures.
    MAP FROM
    rule    		 This structure must exactly match [ /PaymentActivationRequest /sepamail_message_payment_activation_request_001 /ReqCompl /Complements /CustRef] (B2.7) within the [RUBIS Payment Activation Request] message.
    B2.8 [0..1]   + DecisionDate
    SEPAMAIL
    rule    		 This structure is valued by the debtor bank with the date of the debtor's decision. This value is mandatory when the report notifies a decision of the debtor.
    (*) The SEPA Credit Transfer Core Mandatory Subset to which several [MAP TO] rules refer in this document is the subset specified through the yellow shaded elements within the SEPA Credit Transfer Scheme Inter-Bank Implementation Guidelines produced by the European Payment Council.</body>
Retrieved from "https://documentation.sepamail.org/index.php?title=Discussion:IG_Rubis_ActivationReport&oldid=7695"