Add trading platform information
When using the trading connectors, it is common that certain securities or certain types of securities are always traded through the same platform. To automate this process, follow the steps:
Set the Trading channel tag in the Trade order window, or define a decision table that adds a certain tag depending on the security type or subtype.
Define the platform-specific information that has to be added to the trade order.
Set the Trading channel tags
To have Trading channel tags for trade orders set automatically depending on the security type or subtype, use the fa_tradeOrder_tradingPlatform.xlsx decision table.
Download the sample decision table:
Open the file and make the following changes:
Column A: Provide a descriptive rule name, for example, "Trade Collective investment vehicles via FundSettle".
Column B: Add “x” in the rule row to make the rule active.
Column C: Order status for which the rule works. The order status in FA as the initiator must match the status at the executor (broker/counterparty). The trading microservice setup supports several, but not all, of the available statuses in FA and integrates a 1-to-1 mapping against the counterparty when this is possible. The available statuses used for updating are:
2 – Executed
3 – Cancelled
5 – Accepted (recommended)
6 – In execution
7 – Executed in the market
8 – Rejected
9 – Expired
10 – Sent to execution (this is set by default in the sending process)
11 – Settled in the market
12 – Partially executed in the market (supported by Bloomberg and Infront). The trading platforms provide updates with an aggregated order amount and average price directly to the order. If an order in the market place is cancelled or expired, the original order will be marked as fully executed in FA.
For example, you sent an order at 900 Apple, and it is partially executed in the marketplace with 300, and then with 300. The order amount in FA will be updated to 300 and then 600, as well as the average price on each order. If the order expires end of day, it is marked as executed in FA.
Column D: Order type for which the rule works. Transaction type code. Available standard types are listed in Transaction types for Security Transactions .
Column E: Security type code. Available standard types are listed in Security types .
Column F: Security sub type code. Available standard types are listed in Security types .
Column G: Marketplace code. Available standard sub types are listed in Security types .
Column H: Issuer contact ID. Available standard market places are listed in Marketplaces .
Coluimn I: Any security tag that you wish to use.
Column J: Trading channel tag. Possible values:
Allfunds
Bloomberg
Calastone
DNB
FIX44
FundSettle
Infront
MFEX
Column K: Order type tag (only for Bloomberg). Possible values: Market, Limit.
Column L: Order expiration tag (only for Blomberg).
Upload the updated decision table in Tools → Administer → Decision tables and click Done.
The uploaded rules apply only for new trade orders. To update existing trade orders, go to the Trade orders view, search for the orders that you want to update, and click Modify trade orders → Run rules.
Example decision table
In the example below, Accepted buy trade orders in Collective investment vehicles (C) are traded via FundSettle (condition security type C in column B) and Equities (E) of subtype Common/Ordinary shares (ES) are traded via Bloomberg as Limit orders with a day as expiration time.
Define platform-specific information
In order for the Trading Microservice to determine which format the orders should be sent in (ISO20022V3, ISO2020022V4, FIX, Infront, and so on), and to produce them in an accurate manner, the service requires several fields to be set to the text objects sent to it.
To add trading platform-specific information to trade orders, use a decision table that adds this data in the Internal info field in the Trade order window depending on the Trading channel tag. For example, the decision table can define that trade orders marked with Trading channel=Calastone tag must be sent in the ISO2020022V4 format.
To create and upload the decision table:
Download the sample decision table
fa-trading-channel-format-configurations.xlsx:Open the file and make the following changes:
Column B: Add “x” in the rule row to make the rule active.
Column D: Add client-specific data (for example, SenderSubID) to channel configuration.
Upload the updated decision table in Tools → Administer → Decision tables and click Done.
The uploaded rules apply only for new trade orders. To update existing trade orders, go to the Trade orders view, search for the orders that you want to update, and click Modify trade orders → Run rules.
Configure accounts for Infront and DNB
You can set up one or several trading accounts in Infront and DNB to send trade orders.
Single account
To send an order to a trading account in Infront or DNB, the order in FA needs to have AccountIdentification=<trading account> as part of its internal info.
For DNB only: if the DNB channel is expected to receive updates on orders created in other channels, then orders created in these channels require this internal info as well. For example, if an order is sent through Infront but updates are also received in the DNB channel, this order must have AccountIdentification=&lt;account in DNB&gt; set for the Infront orders as well.
Multiple accounts
To send trade orders to multiple accounts on DNB and Infront side, and receive updates on them, follow the steps:
Set the external ID for the portfolios in Portfolio window, IDs tab. The default external ID is "DNB" or "Infront".
Download the sample decision table below. Place the DNB or Infront sheet as the first sheet in the file.
Rename the decision table file to mark that it is modified, for example, with “-DNB” or "-Infront".
Upload the updated decision table in Tools → Administer → Decision tables and click Done.