Configuring Account Code Mapping
The Universal Trading Platform (UTP) requires the presence of specific values for the AccountCode and ClearingInstruction (formally ePostingCode) fields. The value of these two fields vary based on the exchange which hosts a particular product and the account type the user wishes to use for the order.
TT Gateways allow the user to determine an Order Session's account code by referencing the following sections in the hostinfo.cfg file:
- [ExchangeCodeMappings]: This section defines which exchange codes map to each exchange. Users may also create groups that merge multiple exchanges.
This section sets the values for account code mapping. By default, TT Gateways
install with the correct, default values for all exchange products.
In order to create custom mappings for different Order Sessions, users may create additional account code sections. When adding account code sections, you must name the section header [AccountCodeMapping_X] where X is any unique alpha-numeric value.
Configuring the Order Session
Each Order Session uses an AccountCodeMapping parameter to determine the account code mapping section to use. You must set the AccountCodeMapping parameter equal to the unique value in the [AccountCodeMapping_X] section.
- AccountCodeMapping=DefaultMapping causes the Order Session to submit orders with the default values listed in the [AccountCodeMapping_DefaultMapping] section.
- AccountCodeMapping=London causes the Order Session to submit orders with the custom values configured in a [AccountCodeMapping_London] section.
Using the Default Account Codes
By default, TT Gateways contain default account code configurations. However, TT recommends you verify the Order Session's default account code mapping using the procedure below:
To verify the default account code mapping:
- Open the hostinfo.cfg file using a text editor such as Notepad.
- Ensure that any [OrderServerSession_X] sections that should use default account mappings contains the following setting: AccountCodeMapping=DefaultMapping.
- Save the updated hostinfo.cfg file.
You can restrict the available account codes by adding a hash symbol (#) in front of the account code's line. The TT Gateway rejects orders submitted with a restricted account code.
Creating Custom Account Codes
You can add an [AccountCodeMapping_X] section by using the following format to map the account codes:
AccountType=Region:AccountCode ClearingInstruction, Region:AccountCode ClearingInstruction
- AccountType equals
the two-character Account Type listed in X_TRADER.
Below is the list of possible values for AccountType and their description:
Accounts in X_TRADER
First Agent Account (e.g., broker)
First Market Maker
Second Agent Account
Second Market Maker
Third Agent Account
Market Maker/Give-up or System Allocation
First Principal Account (Proprietary Trader)
Second Principal Account
House/Give-up or System Allocation
- Region equals the regions defined in the [ExchangeCodeMappings] section. By default, TT Gateways install with two defined regions, London and Continent.
- AccountCode equals
the single-character exchange account code.
Give-up to single firm
You must verify that Account Types mapped to either A (Allocation) or G (Giveup) appear in the GiveupAccounts parameter.
- ClearingInstruction equals
the single-character instruction forwarded to the clearing firm.
Possible values ClearingInstruction include
Account Clearing Instruction
Manual Posting and Account Authorisation* (4009)
Automatic Posting and Account Authorisation* (4008)
Give-up to single firm (4010)
*Apply to Amsterdam products only.
For information on mapping account codes for Give-up orders, refer to Configuring Give Up Orders.
For Order Sessions that use custom mappings, the TT Gateway rejects orders submitted with any account type other than the account types defined in the [AccountCodeMapping_X] section.
Example: Custom Account Code Mapping
Example Custom Account Code Mapping
A trading firm would like to create custom mappings for the A2 account type.
For products available on the London exchanges, the firm would like A2 to map to a Segregated account (i.e., S) and contain no clearing instruction (i.e., _).
For the Continental exchanges, A2 should map to a Customer account (i.e., C) and contain the Manual (i.e., M) clearing instruction.
Under the [AccountCodeMapping_X] section, the firm adds the following:
In this example, A2 is the only configured account type. For Order Sessions that use these custom mappings, the TT Gateway rejects orders submitted with any account type other than A2.