Page last modified 09:16, 16 Mar 2016 by kari_admin

EndToEndId

    Table of contents
    No headers

    ISO20022 describes EndToEndId as follows:

    Presence:  [1..1]
    Definition:  Unique identification assigned by the initiating party to unumbiguously identify the transaction. This 
    identification is passed on, unchanged, throughout the entire end-to-end chain.
    Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. 
    It can be included in several messages related to the transaction.
    Data Type:  Max35Text, Format:  maxLength: 35, minLength: 1
     
    In CT the element is not mandatory. In DD it is.
     
    It's worth noting that the uniqueness combined with element being mandatory can bring certain problems. Common workaround is to allow element to be filled with value NOTPROVIDED. For RBS, value NOTPROVIDED is allowed.
     

    Example:

    <PmtInf>
<CdtTrfTxInf> 
   <EndToEndId>1</EndToEndId>
</CdtTrfTxInf>
</PmtInf>
<PmtInf>
<CdtTrfTxInf> 
   <EndToEndId>2</EndToEndId>
</CdtTrfTxInf>
<CdtTrfTxInf> 
   <EndToEndId>NOTPROVIDED</EndToEndId>
</CdtTrfTxInf>
<CdtTrfTxInf> 
   <EndToEndId>NOTPROVIDED</EndToEndId>
</CdtTrfTxInf>
<PmtInf>

    (Various elements have been removed for the sake of the example)

    The example is in valid format.

    Menu