Processing Concepts
      Back to home
      1. Knowledge Base
      2. Reporting Services
      3. Processing Concepts

      What identifiers are available for tracking and searching?

      The KOR UI defaults to showing common fields and search attributes. Apply a jurisdiction filter to view columns and searchable fields specific to that jurisdiction.


      • KOR Defined Identifiers submitted by Client: 
        • KOR Lifecycle Identifier:  The identifier used to track submission uniqueness and the resulting regulatory message life cycle events. All stateful related regulatory message validations (NEWT -> MODI, etc) must reference the same KOR lifecycle identifier.  Note that the same KOR Lifecycle Identifier can reference multiple KOR Reg Lifecycle Identifiers.   
        • KOR Reg Lifecycle Identifier: The identifier used to track regulatory message uniqueness and life cycle events.  All stateful related regulatory message validations (NEWT -> MODI, etc) must be submitted referencing the same KOR reg lifecycle identifier within the same KOR Lifecycle Identifier
        • Client Trade Identifier: Client generated and submitted identifier per Trade that is not the UTI/USI.
        • Client Order Identifier: Client generated and submitted identifier per Order that is not the Unique Order Identifier.
      • Regulatory Defined Identifiers submitted by Client: 
        • Unique Transaction Identifier: A unique identifier assigned to all swap transactions that identifies the transaction uniquely throughout its lifecycle and is used for all recordkeeping and all transaction data reporting. A UTI comprises the generating entity's LEI and a unique alphanumeric code. 
        • Unique Swap Identifier OR Non-UTI Identifier: The USI is a unique identifier assigned to all swap transactions which identifies the transaction (the swap and its counterparties) uniquely throughout its duration. It consists of a namespace and a transaction identifier. This identifier is only used on transactions created prior to the implementation of the UTI.
          • USI is used for CFTC reporting
          • Non-UTI Identifier is used for ASIC and MAS reporting.
        • Unique Order Identifier: The order shall be identified by using a unique code identifier provided by the market place or counterparties. (REMIT reporting)
        • Initial Margin Collateral Portfolio Code:  If collateral is reported on a portfolio basis, a unique code assigned by the reporting counterparty to the portfolio that tracks the aggregate initial margin of a set of open swap transactions. This data element is not applicable if the collateralisation was performed on a transaction level basis, or if there is no collateral agreement, or if no collateral is posted or received.  
        • Variation Margin Collateral Portfolio Code: If collateral is reported on a portfolio basis, a unique code assigned by the reporting counterparty to the portfolio that tracks the aggregate variation margin related to a set of open swap transactions. This data element is not applicable if the collateralisation was performed on a transaction level basis, or if there is no "collateral agreement, or if no collateral is posted or received. 
        • Secondary Trade Identifier: Client generated and submitted identifier per Trade that is not the UTI/USI. (ASIC Reporting)
      • KOR generated IDs
        • Ingestion Identifier: Each ingestion is assigned a unique identifier.  The same ingestion identifier is passed on to all related Submissions created from the Ingestion. 
        • Submission Identifier: The resulting Submissions from the ingestion are assigned a unique identifier.  
        • Eligibility Identifier: Each eligibility check is assigned a unique identifier that corresponds directly to a specific Submission.
        • Regulatory Message Identifier: Each reporting obligation generated from a submission is assigned a unique Regulatory Message Identifier. A single submission may correspond to multiple Regulatory Message Identifiers.
        • Output Identifier: A unique identifier that is generated and assigned to each output resulting from a regulatory message. Each output identifier corresponds directly to a specific regulatory message identifier.
        • User Identifier: A unique identifier assigned to each user within the KOR system. This user identifier is accessible through KOR Central. While user names are visible within the application, all data queries must utilize the User Identifier linked to the respective user profile in KOR Central.
        • Package Definition Identifier: Identifier generated and assigned during package configuration set up. Used to identify the processing behavior of the package components assigned to that Package Definition Identifier.