Trade Creation & Management
      Back to home
      1. Knowledge Base
      2. Trading & Trade Management
      3. Trade Creation & Management

      Understanding Trading Tickets

      When a trade is executed. Kooltra creates a ticket to record the details of the trade.

      What is a ticket

      When a trade is executed. Kooltra creates a ticket to record the details of the trade. Tickets are created for;

      • Trade execution via ‘trade on behalf’

      • Trade execution from the portal

      • API and Post Trade integrations (drop copies)

      • Manual Trade entry

      Details captured on the ticket is viewable from the Kooltra UI or via trade reports.

      Ticket Naming Conventions

      Each ticket is given an ID in the following format;

      ParentID.SubID e.g. 32432.0

       

      Some trades may have multiple legs. ex a client deal that is hedged with an LP. In this case the ParentID will be common across the trade and each ticket will have its own SubID. ex

      32432.0 - Client ticket

      32432.1- Hedge ticket

       

      For Spot and Forward trades, the SubID will only contain numbers. i.e. 32432.0, 32432.1, 32432.2, 32432.3

       

      Swap Trades can be identified by having SubIDs that start with N or F. These letters identify the ticket as the Near or Far leg of the swap. for example;

      32433.N1 - Near leg swap ticket

      32433.F1 - Corresponding far leg ticket

       

      When gross processing, settlement instructions are added to the trade. In Kooltra, pending cashflows are created during this process. The cashflows will also use the ParentID of the related trade with a SubID that starts with C. For Example;

      32432.0 - Client ticket

      32432.C0 - pending cashflow (for example: pending deposit)

      32432.C1 - pending cashflow (for example: pending payment)

       

      This convention allows users to easily Identify related trades and cashflows. The Ticket page is used to show trade details and can be accessed by clicking on the ticket ID.

      Trade Overview

      Ticket pages display the trade Id and associated trade details. Depending on user profile and trade status it may be possible to amend details and update the trade.

      The Ticket page may contain additional tabs.

      • Settlements - The settlements tab will show if the ticket is against a gross settlement client (See settlement types). This page can be used to add settlement instructions to the trade.

      • Details - The details tab holds additional information about the ticket. This tab is especially useful for trades originating from external sources as it will show details of the source system and the underlying API message for the trade (for example the original FIX message that created the ticket)

      • Confirmations - If trade confirmations are active, trade and settlement confirmations will be accessible from this tab

      • Notes - This tab allows users to store notes and comments about the ticket. Notes stored here are internal to your organisation.

      • History - The History tab shows an audit history of amendments to the ticket.

      • Advanced -The advanced tab contains links pages related to the ticket. for example, if the ticket is a window forward, this tab will contain a link to the Drawdown/Roll over page.