Transaction window

The portfolio you want to create the transaction in.

The chosen basic type of the transaction or allows you to choose the basic type: the chosen of the basic type influences the fields available for defining the transaction. The available basic types are cash, stock, bond, fund, discount, deposit, currency, option and future.

the security related to the transaction. The + icon next to the security field allows you to create a new security directly in the transaction window in case the security to be linked to you transaction cannot yet be found from the system. When choosing to create a new security, the possible security types are filtered to match the security base type chosen to the transaction. When you save the security, it is automatically selected as the security of the transaction.

The transaction type from the alternatives, which are defined in Transaction type Preferences. You can only see the transaction types which are linked to the selected security's security type, or if no security is selected, linked to all security types with the selected security type's base type.

The account to record the money transactions caused by the transaction. You can see only accounts with the security, transaction or portfolio currency. Shared accounts (an account of the same customer's portfolio defined to be shared to the portfolios of the customer, the account of a main portfolio automatically shared to its sub-portfolios, or an account of a subportfolio shared to all parent portfolio's subportfolios) are indicated with a star * before account number and name. You can see the shared account's portfolio in brackets.

The appropriate report exchange rate, or exchange rate between you transaction's security's currency and you portfolio's currency, for the transaction. You can fetch the exchange rate to the field with a question mark (?), when the system sets the exchange rate to be the transaction day's market price of the currency. If no market price is can be found for the transaction date, the latest available market price is used.

The appropriate account exchange rate, or exchange rate between you transaction's security's currency and you portfolio's account's currency, for the transaction. You can fetch the exchange rate to the field with a question mark (?), when the system sets the exchange rate to be the transaction day's market price of the currency. If no market price is can be found for the transaction date, the latest available market price is used.

The transaction date. Transaction date determines when the the transaction actually occurred (i.e. when the transaction originally took effect). Positions, portfolio's content and most reports are most often based on the transaction date. For more information on how to select dates, see Selecting dates.

The time of the trade either in the format of hh:mm, for example 14:30, or in the format of hh:mm:ss, for example 14:30:15.

The settlement date of the transaction. For more information on how to select dates, see Selecting dates. You can also set the settlement date the following ways:

The status of the transaction: Accepted, Deleted, Not finished. Only accepted transactions are visible in the portfolio and have an effect on the portfolio total and portfolio reports. Transactions with any status are searchable in the transactions view.

Hide this transaction from the Overview’s transaction listing. Hidden transactions still affect your positions, but they are not shown on the Overview’s transaction listing. This allows you to filter the Overview to only show transactions you need in your day-to-day work to get an overview of your client’s investments, while you can access other transactions through the Transactions view. This is especially useful for bookkeeping transactions, such as deferrals or value adjustments, which don’t directly affect how much you own, but only alter the position’s values for bookkeeping purposes.

The amount / denomination of the transaction. Amount can have as many decimals as defined in the Security type Preferences or as the block size of the transaction's security - only the allowed number of decimals can be inputted in the transaction window.

The coefficient of the transaction. The field is available only for transaction of the basic type bond with a linked index (i.e. for index linked bonds). You can also set the coefficient the following ways:

The unit price of the chosen security. You can also set the unit price the following ways:

The system automatically calculates the price of the transaction based on the inserted values. If the transaction required an account exchange rate, price and all other values below it are also shown against the account's currency, converted with the defined account exchange rate.

The tax type from alternatives, which are defined in Tax type Preferences (see Preference - Taxation). The tax type defines the type of tax in question (for example Capital gains tax or Withholding tax).

The tax of the transaction. A plain numerical value is interpreted in terms of money, and there are different ways you can trigger the system to calculate the tax on your transaction:

Record the paid / received accrued interest of the transaction, up to the settlement date of the transaction. The field is available only for transaction of the base type BOND If coupon/fixing information is defined for the security (Extra info tab of the Security window), you can calculate the accrued interest to the transaction by typing a question mark (?) to the field. The system automatically calculates the accrued interest up to the settlement date.

Record the paid/received accrued income included in your transaction's unit price. The field is available only for transactions of the base type FUND. Unit price already includes the accrued income, and thus accrual doesn’t have an effect on your transaction's trade amount. If accrual component is recorded within security's market data (Market data info tab of the Security window), you can calculate the accrual to the transaction by typing a question mark (?) to the field. The system automatically calculates the accrual on the transaction date. This field is used for accrued income management with mutual funds: NAV of a fund includes accrued income, but when you subscribe into a fund, you pay for the income accrued before your subscription, and when you redeem your shares, you receive the accrued income not yet paid out. (Available from FA 3.7 onward). Your position's purchase value excludes the paid accrual recorded on your transaction, while your position's purchase unit price includes accrual (available from FA 3.8 onward).

The cost type from alternatives, which are defined in Transaction cost type Preferences. The cost type defines the type of cost in question (for example Advisory fee, Custodian fee or Broker commission). If you don't select a cost type, your costs are identified as generic Credit fee and Fee.

The credit fee of your transaction. A plain numerical value is interpreted in terms of money, and there are different ways you can trigger the system to calculate the tax on your transaction:

The fee of your transaction. A plain numerical value is interpreted in terms of money, and there are different ways you can trigger the system to calculate the tax on your transaction:

The system automatically calculates the total trade amount of the transaction based on the values in the Total column, taking into account the tax and fees. Modifying the total trade amount will adjust the value in the Unit price field in order for the values to add up correctly. If there are no values defined for the Amount and Unit price fields, setting the total trade amount will set the total trade amount to the Amount field and 1 to the Unit price field. If the transaction required an account exchange rate, trade amount and all other values above it are also shown against the account's currency, converted with the defined account exchange rate.

The reference of the transaction. You can automatically generate the reference number to a transaction with a question mark (?), when the system generates a reference number to the transaction with the formula portfolio ID * 100 000 + transaction external ID + control number. Portfolio ID is used as a basis of the reference number by default, but if the portfolio ID is not a number, then portfolio external ID is used. If the portfolio external ID is not a number, then portfolio database ID is used. The control number is calculated based on the formula defined for forming reference numbers.

A counter and a counter portfolio for your transaction. The first dropdown for the counter contact first lists contacts of the type Counter party and Custody in alphabetical order, and then the rest of the contacts within the system in alphabetical order. The second dropdown for the counter portfolio lists all portfolios within the system in alphabetical order.

The marketplace (MIC) of the transaction from the alternatives, which are defined in Marketplace Preferences. To find a marketplace, start typing the MIC code or marketplace name in the field.

The settlement place (BIC) of the transaction from the alternatives, which are defined in Settlement place Preferences.

External ID / number of your transaction. When creating a transaction, the system automatically generates an external ID for it by determining the next available number - the available number depends on whether you have selected transaction numbering to be handled on the portfolio or contact level within Transaction no. level field in the Contact window. For example, if the largest external ID in your portfolio at the moment is 123, the next transaction would get the external ID of 124. You can also modify the external ID manually or have the system re-generate it with the next available number by typing in a question mark (?). External ID can also include letters and other non-numeric characters - however, these can only be added manually and are not considered by the automatic external ID generation.

The intra-day priority of the transaction with a number (-1, 0, 1, 2, 3 etc.). The transaction with the lowest priority has the highest number defined in the priority field (0 is lower than 1 and -1 is lower than 0). The default priority is 0. The priority field is used to order the transaction within one day, in other words, to define which transactions take effect first. If priorities have not been used, but if trade times are defined, the transactions take effect in trade time order (empty trade time is interpreted as 00:00 and takes effect before transactions with a later trade time). If priorities or trade times are not used, the transactions within a day are ordered based on the transaction external ID.

The date when you created the original trade order or received it from the client.

The time when you created the original trade order or received it from the client. Enter the time either in the format of hh:mm, for example 14:30, or in the format of hh:mm:ss, for example 14:30:15.

The booked transaction date.

The exchange rate, if the original exchange rate is different from the new exchange rate of the transaction (if no exchange rate is needed, define 1 as the exchange rate). The booked exchange rate can also be fetched to the field with a question mark (?), when the system fetches the exchange rate to be the booked transaction day's market price of the currency. If no market price is can be found for the transaction date, the latest available market price is used.

The booked trade amount. The booked trade amount can also be fetched to the field with a question mark (?), when the system fetches the booked transaction day's market price of the transaction's security (if no market price is can be found for the booked transaction date, the latest available market price is used), and calculates the booked trade amount by multiplying the fetched price with the defined amount.

The second security for the transaction. For example, for issues, the second security often shows which security the issue is based on.

The ratio in the form of x:x, for example 1:2. For example, for splits, the ratio tells the split ratio.

The payment date of your transaction, when the payment date is different from your transaction's settlement date. Payment date field is available for security trades linked to an account, since there is no need to separately define a payment date to cash transactions. Payment date is optional, and only affects the date when your account balance changes.

The external ID of the transaction you want to link this transaction to in order to override FIFO. When calculating FIFO, transactions linked together through this field are considered first, and all remaining transactions are ordered based on FIFO logic. This allows you, for example, to link a "sell" transaction to a specific "buy" transaction in order to sell a specific purchase lot over FIFO.

You can also override FIFO with a fraction of lots. To increase the amount on an existing lot without creating a new lot, use the Equalization credit (EQCR) transaction type and specify the external ID of the existing lot you want to increase in the Override FIFO (ext ID) field. To decrease the amount on a specific lot without leaving out any purchase lots from the FIFO chain, use equalization debit (EQDE) transaction type and specify the external ID of the existing lot you want to increase in the Override FIFO (ext ID) field.

The linked transaction has to pass though the following validation:

An optional description of the transaction, which is visible for example on the bank statement report.

An optional description of the transaction, which is visible only internally in the Transaction window.

Tags from the alternatives defined in Tags Preferences (see Preference - Tags). Tags can be defined in three different ways: