How to Prepare Standard Template Files for Import

Prerequisites

We assume you have all prerequisites you may need, including:

1. If needed: the VPN is configured to access the Finmars resources
2. If needed: access to the Virtual Machine to work with the sensitive information
3. Must have: registered in Finmars in the needed region environment (self-registered or registered by Finmars)
4. Must have: having permissions set to allow continue with the Action in the Guide
   
5. Must have: to create a new Workspace you must have a License Key (provided by Finmars)
6. Must have: installed Standard Configuration package from the marketplace

Prepare Standard Template Files for Import

Standard Configuration supports importing from Excel files:

Currencies, Accounts, Portfolios, Instruments, Instruments Factor Schedules, Instruments Accrual Schedules, Counterparties, Responsibles, Strategies1, Transactions, Positions, Prices & FX Rates.

To import this files follow instruction: How to Import Data into a Workspace via Dashboard (STD Manual Import)

Below you can find instructions on how to fill in templates.

General Requirements:

• Files MUST be structured in accordance with templates (same columns and formatting).

• Excel files must NOT have formulas (only values).

• Excel files must NOT have more than one sheet.

• Excel files must NOT have empty cells in fields for the data row.

Transactions

• To book a transaction in the system you can import it from a file.

• One transaction is one row of data in the file.

• You should enter a transaction in the file for import in accordance with the instructions below for supported standard transaction/position types.

• Supported Standard transaction types list (case-sensitive):

   

  • Transactions

    • Deposit

    • Withdraw

    • Expense (Non-instrument)

    • Income (Non-instrument)

    • Coupon

    • Dividend

    • Expense (Instrument)

    • Other Income (Instrument)

    • Buy

    • Sell

    • FX Trade

    • FX Forward (Open)

    • FX Forward (Expiration)

    • Transfer Cash

    • Transfer Instrument

Deposit/Withdraw

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Transactions.

  • For Deposit/Withdraw transactions values should be:

    • Deposit

    • Withdraw

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

  • For Deposit/Withdraw transactions:

    • Date (Value) should be equal to Date (Trade)

• Portfolio

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Currency (Settlement)

  • Text field. Case-sensitive.

  • A currency in which the payment or transfer of funds takes place to fulfil the terms of the transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Cash Consideration

  • Numeric field.

  • A monetary value or payment made in the form of cash for a particular transaction or asset.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Account (Position)

  • Text field. Case-sensitive.

  • For Deposit/Withdraw transactions values should be “-" (dash).

• Instrument

  • Text field. Case-sensitive.

  • For Deposit/Withdraw transactions values should be “-" (dash).

• Allocation (PL)

  • Text field. Case-sensitive.

  • For Deposit/Withdraw transactions values should be “-" (dash). 

• Position size

  • Numeric field.

  • For Deposit/Withdraw transactions values should be “0" (zero).

• Principal/Share price

  • Numeric field.

  • For Deposit/Withdraw transactions:

    • The share price of the open-end fund.

  • For Deposit/Withdraw transactions values should be “0" (zero) for default.

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Amount (Carry)

  • Numeric field.

  • For Deposit/Withdraw transactions values should be “0" (zero).

• Amount (Charges)

  • Numeric field.

  • For Deposit/Withdraw transactions values should be “0" (zero).

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • For Deposit/Withdraw transactions values should be “-" (dash).

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

• Portfolio To

  • Text field. Case-sensitive.

  • For Deposit/Withdraw transactions values should be “-" (dash).

• Account To (Cash)

  • Text field. Case-sensitive.

  • For Deposit/Withdraw transactions values should be “-" (dash).

• Account To (Position)

  • Text field. Case-sensitive.

  • For Deposit/Withdraw transactions values should be “-" (dash).

• Counterparty

  • Text field. Case-sensitive.

• Responsible

  • Text field. Case-sensitive.

• Strategy1

  • Text field. Case-sensitive.

Expense/Income (Non-instrument)

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Transactions.

  • For Income/Expense (Non-instrument) transactions values should be:

    • Income (Non-instrument)

    • Expense (Non-instrument)

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Portfolio

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Currency (Settlement)

  • Text field. Case-sensitive.

  • A currency in which the payment or transfer of funds takes place to fulfil the terms of the transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Cash Consideration

  • Numeric field.

  • A monetary value or payment made in the form of cash for a particular transaction or asset.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Account (Position)

  • Text field. Case-sensitive.

  • For Income/Expense (Non-instrument) transactions values should be “-" (dash).

• Instrument

  • Text field. Case-sensitive.

  • For Income/Expense (Non-instrument) transactions values should be “-" (dash).

• Allocation (PL)

  • Text field. Case-sensitive.

  • For Income/Expense (Non-instrument) transactions values should be “-" (dash). 

• Position size

  • Numeric field.

  • For Income/Expense (Non-instrument) transactions values should be “0" (zero).

• Principal/Share price

  • Numeric field.

  • For Income/Expense (Non-instrument) transactions values should be “0" (zero).

• Amount (Carry)

  • Numeric field.

  • An amount of an Income/Expense.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Amount (Charges)

  • Numeric field.

  • Costs or fees associated with a transaction.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • A type of Income/Expense associated with a transaction.

  • Used for grouping in reports for non-instrument transactions.

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

• Portfolio To

  • Text field. Case-sensitive.

  • For Expense/Income (Non-instrument) transactions values should be “-" (dash).

• Account To (Cash)

  • Text field. Case-sensitive.

  • For Expense/Income (Non-instrument) transactions values should be “-" (dash).

• Account To (Position)

  • Text field. Case-sensitive.

  • For Expense/Income (Non-instrument) transactions values should be “-" (dash).

• Counterparty

  • Text field. Case-sensitive.

• Responsible

  • Text field. Case-sensitive.

• Strategy1

  • Text field. Case-sensitive.

Coupon/Dividend

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Transactions.

  • For Coupon/Dividend transactions values should be:

    • Coupon

    • Dividend

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Portfolio

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Currency (Settlement)

  • Text field.

  • A currency in which the payment or transfer of funds takes place to fulfil the terms of the transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Cash Consideration

  • Numeric field.

  • A monetary value or payment made in the form of cash for a particular transaction or asset.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Account (Position)

  • Text field. Case-sensitive.

  • An account that tracks and records the positions or holdings of assets.

• Instrument

  • Text field. Case-sensitive.

  • A financial asset or security involved in a transaction.

  • Value must be:

    • ISIN (e.g. GB00BFZNLB60) to import Instrument from Finmars Database

    • user_code - for instruments without ISIN or already created instruments.

• Allocation (PL)

  • Text field. Case-sensitive.

  • An instrument to which the financial outcome of a transaction is attributed or allocated.

  • Value must be:

    • ISIN (e.g. GB00BFZNLB60) to import Instrument from Finmars Database

    • user_code - for instruments without ISIN or already created instruments.

• Position size

  • Numeric field.

  • For Coupon/Dividend transactions values should be “0" (zero).

• Principal/Share price

  • Numeric field.

  • For Coupon/Dividend transactions values should be “0" (zero).

• Amount (Carry)

  • Numeric field.

  • An amount of a Coupon/Dividend.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Amount (Charges)

  • Numeric field.

  • Costs or fees associated with a transaction.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • For Coupon/Dividend transactions values should be “-" (dash).

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

• Portfolio To

  • Text field. Case-sensitive.

  • For Coupon/Dividend transactions values should be “-" (dash).

• Account To (Cash)

  • Text field. Case-sensitive.

  • For Coupon/Dividend transactions values should be “-" (dash).

• Account To (Position)

  • Text field. Case-sensitive.

  • For Coupon/Dividend transactions values should be “-" (dash).

• Counterparty

  • Text field. Case-sensitive.

• Responsible

  • Text field. Case-sensitive.

• Strategy1

  • Text field. Case-sensitive.

Expense/Other Income (Instrument)

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Transactions.

  • For Other Income/Expense (Instrument) transactions values should be:

    • Other Income (Instrument)

    • Expense (Instrument)

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Portfolio

  • Text field.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Currency (Settlement)

  • Text field. Case-sensitive.

  • A currency in which the payment or transfer of funds takes place to fulfil the terms of the transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Cash Consideration

  • Numeric field.

  • A monetary value or payment made in the form of cash for a particular transaction or asset.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Account (Position)

  • Text field. Case-sensitive.

  • An account that tracks and records the positions or holdings of assets.

• Instrument

  • Text field. Case-sensitive.

  • A financial asset or security involved in a transaction.

  • Value must be:

    • ISIN (e.g. GB00BFZNLB60) to import Instrument from Finmars Database

    • user_code - for instruments without ISIN or already created instruments.

• Allocation (PL)

  • Text field. Case-sensitive.

  • An instrument to which the financial outcome of a transaction is attributed or allocated.

  • Value must be:

    • ISIN (e.g. GB00BFZNLB60) to import Instrument from Finmars Database

    • user_code - for instruments without ISIN or already created instruments.

• Position size

  • Numeric field.

  • For Other Income/Expense (Instrument) transactions values should be “0" (zero).

• Principal/Share price

  • Numeric field.

  • For Other Income/Expense (Instrument) transactions values should be “0" (zero).

• Amount (Carry)

  • Numeric field.

  • An amount of an Income/Expense.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Amount (Charges)

  • Numeric field.

  • Costs or fees associated with a transaction.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • A type of Income/Expense associated with a transaction.

  • Used for grouping in reports for non-instrument transactions.

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

• Portfolio To

  • Text field. Case-sensitive.

  • For Expense/Other Income (Instrument) transactions values should be “-" (dash).

• Account To (Cash)

  • Text field. Case-sensitive.

  • For Expense/Other Income (Instrument) transactions values should be “-" (dash).

• Account To (Position)

  • Text field. Case-sensitive.

  • For Expense/Other Income (Instrument) transactions values should be “-" (dash).

• Counterparty

  • Text field. Case-sensitive.

• Responsible

  • Text field. Case-sensitive.

• Strategy1

  • Text field. Case-sensitive.

Buy/Sell

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Transactions.

  • For Buy/Sell transactions values should be:

    • Buy

    • Sell

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Portfolio

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Currency (Settlement)

  • Text field. Case-sensitive.

  • A currency in which the payment or transfer of funds takes place to fulfil the terms of the transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Cash Consideration

  • Numeric field.
    

  • A monetary value or payment made in the form of cash for a particular transaction or asset.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Account (Position)

  • Text field. Case-sensitive.

  • An account that tracks and records the positions or holdings of assets.

• Instrument

  • Text field. Case-sensitive.

  • A financial asset or security involved in a transaction.

  • Value must be:

    • ISIN (e.g. GB00BFZNLB60) to import Instrument from Finmars Database

    • user_code - for instruments without ISIN or already created instruments.

• Allocation (PL)

  • Text field. Case-sensitive.

  • An instrument to which the financial outcome of a transaction is attributed or allocated.

  • Value must be:

    • ISIN (e.g. GB00BFZNLB60) to import Instrument from Finmars Database

    • user_code - for instruments without ISIN or already created instruments.

• Position size

  • Numeric field.

  • An adjusted position of the asset after all alterations or corrections (e.g. adjusted for a factor).

  • A sign of the number:

    • “+" (plus sign) is for position increase

    • “-" (minus sign) is for position decrease

• Principal/Share price

  • Numeric field.

  • For Buy/Sell transactions this field is a Principal price:

    • A unit price or value of a financial instrument, excluding any accrued interest or additional earnings.

  • Must be in Settlement Currency.

  • Multipliers will be applied automatically in accordance with an instrument of the transaction.

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Amount (Carry)

  • Numeric field.

  • An amount or expense that has been incurred but not yet paid or settled.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Amount (Charges)

  • Numeric field.

  • Costs or fees associated with a transaction.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-” (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • For Buy/Sell transactions values should be “-" (dash).

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

• Portfolio To

  • Text field. Case-sensitive.

  • For Buy/Sell transactions values should be “-" (dash).

• Account To (Cash)

  • Text field. Case-sensitive.

  • For Buy/Sell transactions values should be “-" (dash).

• Account To (Position)

  • Text field. Case-sensitive.

  • For Buy/Sell transactions values should be “-" (dash).

• Counterparty

  • Text field. Case-sensitive.

• Responsible

  • Text field. Case-sensitive.

• Strategy1

  • Text field. Case-sensitive.

FX Trade

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Transactions.

  • For FX Trade transactions values should be:

    • FX Trade

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

  • For FX Trade transactions:

    • Date (Value) should be equal to Date (Trade)

• Portfolio

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Instrument

  • Text field.

  • For FX Trade transactions:

    • A currency that is being purchased (buy currency - base) in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Allocation (PL)

  • Text field. Case-sensitive.

  • An instrument to which the financial outcome of a transaction is attributed or allocated.

  • Value must be:

    • ISIN (e.g. GB00BFZNLB60) to import Instrument from Finmars Database

    • user_code - for instruments without ISIN or already created instruments.

• Position size

  • Numeric field.

  • For FX Trade transactions:

    • An amount of a particular currency that is being purchased (buy currency - base) in a foreign exchange transaction.

  • A sign of the number:

    • “+" (plus sign) is for position increase

    • “-" (minus sign) is for position decrease

• Principal/Share price

  • Numeric field.

  • For FX Trade transactions:

    • An exchange rate used for a contract’s foreign exchange transaction, where Sell currency is the Quote currency and Buy currency is the Base currency (e.g. we sell 110 USD and buy 100 EUR, then the field’s value should be 1.1 EUR/USD).

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Amount (Carry)

  • Numeric field.

  • For FX Trade transactions values should be “0" (zero).

• Amount (Charges)

  • Numeric field.

  • For FX Trade transactions values should be “0" (zero).

• Cash Consideration

  • Numeric field.

  • For FX Trade transactions:

    • An amount of a particular currency that is being sold (sell currency - quote) in a foreign exchange transaction.

  • A sign of the number:

    • “+” (plus sign) is for position increase

    • “-” (minus sign) is for position decrease

• Currency (Settlement)

  • Text field. Case-sensitive.

  • For FX Trade transactions:

    • A currency that is being sold (sell currency - quote) in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • For FX Trade transactions values should be “-" (dash).

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

• Portfolio To

  • Text field. Case-sensitive.

  • For FX Trade transactions values should be “-" (dash).

• Account To (Cash)

  • Text field. Case-sensitive.

  • For FX Trade transactions values should be “-" (dash).

• Account To (Position)

  • Text field. Case-sensitive.

  • For FX Trade transactions values should be “-" (dash).

• Counterparty

  • Text field. Case-sensitive.

• Responsible

  • Text field. Case-sensitive.

• Strategy1

  • Text field. Case-sensitive.

Transfer Cash

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Transactions.

  • For Transfer Cash transactions values should be:

    • Transfer Cash

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

  • For Deposit/Withdraw transactions:

    • Date (Value) should be equal to Date (Trade)

• Portfolio

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Currency (Settlement)

  • Text field. Case-sensitive.

  • A currency in which the payment or transfer of funds takes place to fulfil the terms of the transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Cash Consideration

  • Numeric field.

  • A monetary value or payment made in the form of cash for a particular transaction or asset.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Account (Position)

  • Text field. Case-sensitive.

  • For Transfer Cash transactions values should be “-" (dash).

• Instrument

  • Text field. Case-sensitive.

  • For Transfer Cash transactions values should be “-" (dash).

• Allocation (PL)

  • Text field. Case-sensitive.

  • For Transfer Cash transactions values should be “-" (dash).
    

• Position size

  • Numeric field.

  • For Transfer Cash transactions values should be “0" (zero).

• Principal/Share price

  • Numeric field.

  • For Transfer Cash transactions values should be “0" (zero) for default.

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Amount (Carry)

  • Numeric field.

  • For Transfer Cash transactions values should be “0" (zero).

• Amount (Charges)

  • Numeric field.

  • For Transfer Cash transactions values should be “0" (zero).

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • For Transfer Cash transactions values should be “-" (dash).

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

• Portfolio To

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization where the transaction transfer to.

• Account To (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions where the transaction transfer to.

• Account To (Position)

  • Text field. Case-sensitive.

  • For Transfer Cash transactions values should be “-" (dash).

• Counterparty

  • Text field. Case-sensitive.

• Responsible

  • Text field. Case-sensitive.

• Strategy1

  • Text field. Case-sensitive.

Transfer Instrument

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Transactions.

  • For Transfer Instrument transactions values should be:

    • Transfer Instrument

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Portfolio

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Currency (Settlement)

  • Text field. Case-sensitive.

  • A currency in which the payment or transfer of funds takes place to fulfil the terms of the transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Cash Consideration

  • Numeric field.

  • A monetary value or payment made in the form of cash for a particular transaction or asset.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Account (Position)

  • Text field. Case-sensitive.

  • An account that tracks and records the positions or holdings of assets.

• Instrument

  • Text field. Case-sensitive.

  • A financial asset or security involved in a transaction.

  • Value must be:

    • ISIN (e.g. GB00BFZNLB60) to import Instrument from Finmars Database

    • user_code - for instruments without ISIN or already created instruments.

• Allocation (PL)

  • Text field. Case-sensitive.

  • For Transfer Instrument transactions values should be “-" (dash).

• Position size

  • Numeric field.

  • An adjusted position of the asset after all alterations or corrections (e.g. adjusted for a factor).
    

  • A sign of the number:

    • “+" (plus sign) is for position increase

    • “-" (minus sign) is for position decrease

• Principal/Share price

  • Numeric field.

  • For Transfer Instrument transactions this field is a Principal price:

    • A unit price or value of a financial instrument, excluding any accrued interest or additional earnings.

  • Must be in Settlement Currency.

  • Multipliers will be applied automatically in accordance with an instrument of the transaction.

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Amount (Carry)

  • Numeric field.

  • An amount or expense that has been incurred but not yet paid or settled.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Amount (Charges)

  • Numeric field.

  • Costs or fees associated with a transaction.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-” (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • For Transfer Instrument transactions values should be “-" (dash).

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

• Portfolio To

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization where the transaction transfer to.

• Account To (Cash)

  • Text field. Case-sensitive.

  • For Transfer Instrument transactions values should be “-" (dash).

• Account To (Position)

  • Text field. Case-sensitive.

  • An account that tracks and records the positions or holdings of assets where the transaction transfer to.

• Counterparty

  • Text field. Case-sensitive.

• Responsible

  • Text field. Case-sensitive.

• Strategy1

  • Text field. Case-sensitive.

FX Forward (Open)/FX Forward (Expiration)

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Transactions.

  • For FX Forward (Open)/FX Forward (Expiration) transactions values should be:

    • FX Forward (Open)

    • FX Forward (Expiration)

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Portfolio

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Instrument

  • Text field.

  • For FX Forward (Open)/FX Forward (Expiration) transactions:

    • A currency that is being purchased (buy currency - base) in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Allocation (PL)

  • Text field. Case-sensitive.

  • An instrument to which the financial outcome of a transaction is attributed or allocated.

  • Value must be:

    • ISIN (e.g. GB00BFZNLB60) to import Instrument from Finmars Database

    • user_code - for instruments without ISIN or already created instruments.

• Position size

  • Numeric field.

  • For FX Forward (Open)/FX Forward (Expiration) transactions:

    • An amount of a particular currency that is being purchased (buy currency - base) in a foreign exchange transaction.

  • A sign of the number:

    • “+" (plus sign) is for position increase

    • “-" (minus sign) is for position decrease

• Principal/Share price

  • Numeric field.

  • For FX Forward (Open)/FX Forward (Expiration) transactions:

    • An exchange rate used for a contract’s foreign exchange transaction, where Sell currency is the Quote currency and Buy currency is the Base currency (e.g. we sell 110 USD and buy 100 EUR, then the field’s value should be 1.1 EUR/USD).

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Amount (Carry)

  • Numeric field.

  • For FX Forward (Open)/FX Forward (Expiration) transactions values should be “0" (zero).

• Amount (Charges)

  • Numeric field.

  • For FX Forward (Open)/FX Forward (Expiration) transactions values should be “0" (zero).

• Cash Consideration

  • Numeric field.

  • For FX Forward (Open)/FX Forward (Expiration) transactions:

    • An amount of a particular currency that is being sold (sell currency - quote) in a foreign exchange transaction.

  • A sign of the number:

    • “+” (plus sign) is for position increase

    • “-” (minus sign) is for position decrease

• Currency (Settlement)

  • Text field. Case-sensitive.

  • For FX Forward (Open)/FX Forward (Expiration) transactions:

    • A currency that is being sold (sell currency - quote) in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • For FX Forward (Open)/FX Forward (Expiration) transactions values should be “-" (dash).

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

• Portfolio To

  • Text field. Case-sensitive.

  • For FX Forward (Open)/FX Forward (Expiration) transactions values should be “-" (dash).

• Account To (Cash)

  • Text field. Case-sensitive.

  • For FX Forward (Open)/FX Forward (Expiration) transactions values should be “-" (dash).

• Account To (Position)

  • Text field. Case-sensitive.

  • For FX Forward (Open)/FX Forward (Expiration) transactions values should be “-" (dash).

• Counterparty

  • Text field. Case-sensitive.

• Responsible

  • Text field. Case-sensitive.

• Strategy1

  • Text field. Case-sensitive.

Positions Initial/Daily

• To book a position in the system you can import it from a file, what differentiate Initial from Daily is Import Schemes, use corresponding.

• One position is one row of data in the file.

• You should enter a position in the file for import in accordance with the instructions below for supported standard transaction types.

• Supported Standard transaction types for Positions Initial/Daily list (case-sensitive):

  • Positions Initial/Daily (different schemes use the same selectors):

    • Position Cash

    • Position Instrument

    • Position FX Forward

Position Cash

Daily transaction type is valid only on the trade date then position will be nullified.

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Positions.

  • For Position Cash transactions values should be:

    • Position Cash

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

  • For Position Cash transactions:

    • Date (Value) should be equal to Date (Trade)

• Portfolio

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Currency (Settlement)

  • Text field. Case-sensitive.

  • A currency in which the payment or transfer of funds takes place to fulfil the terms of the transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Cash Consideration

  • Numeric field.

  • A monetary value or payment made in the form of cash for a particular transaction or asset.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Account (Position)

  • Text field. Case-sensitive.

  • For Position Cash transactions values should be “-" (dash).

• Instrument

  • Text field. Case-sensitive.

  • For Position Cash transactions values should be “-" (dash).

• Position size

  • Numeric field.

  • For Position Cash transactions values should be “0" (zero).

• Principal/Share price

  • Numeric field.

  • For Position Cash transactions:

    • The share price of the open-end fund.

  • For Position Cash transactions values should be “0" (zero) for default.

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Amount (Carry)

  • Numeric field.

  • For Position Cash transactions values should be “0" (zero).

• Amount (Charges)

  • Numeric field.

  • For Position Cash transactions values should be “0" (zero).

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • For Position Cash transactions values should be “-" (dash).

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

Position Instrument

Daily transaction type is valid only on the trade date then position will be nullified.

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Positions.

  • For Position Instrument transactions values should be:

    • Position Instrument

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

  • For Position Instrument transactions:

    • Date (Value) should be equal to Date (Trade)

• Portfolio

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Currency (Settlement)

  • Text field. Case-sensitive.

  • A currency in which the payment or transfer of funds takes place to fulfil the terms of the transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Cash Consideration

  • Numeric field.

  • A monetary value or payment made in the form of cash for a particular transaction or asset.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Account (Position)

  • Text field. Case-sensitive.

  • An account that tracks and records the positions or holdings of assets.

• Instrument

  • Text field. Case-sensitive.

  • A financial asset or security involved in a transaction.

  • Value must be:

    • ISIN (e.g. GB00BFZNLB60) to import Instrument from Finmars Database

    • user_code - for instruments without ISIN or already created instruments.

• Position size

  • Numeric field.

  • An adjusted position of the asset after all alterations or corrections (e.g. adjusted for a factor).
    

  • A sign of the number:

    • “+" (plus sign) is for position increase

    • “-" (minus sign) is for position decrease

• Principal/Share price

  • Numeric field.

  • For Position Instrument transactions this field is a Principal price:

    • A unit price or value of a financial instrument, excluding any accrued interest or additional earnings.

  • Must be in Settlement Currency.

  • Multipliers will be applied automatically in accordance with an instrument of the transaction.

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Amount (Carry)

  • Numeric field.

  • An amount or expense that has been incurred but not yet paid or settled.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Amount (Charges)

  • Numeric field.

  • Costs or fees associated with a transaction.

  • Must be in Settlement Currency.

  • A sign of the number:

    • “+" (plus sign) is for income

    • “-" (minus sign) is for expenses

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-” (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • For Position Instrument transactions values should be “-" (dash).

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

Position FX Forward

• Transaction ID

  • Text field. Case-sensitive.

  • A unique complex transaction identifier (only one in the workspace).

  • Transactions with repeated ID will NOT be booked (will be skipped).

• Transaction Type

  • Text field. Case-sensitive.

  • Type of a transaction.

  • Should be a value from Standard transaction types for Positions.

  • For Position FX Forward transactions values should be:

    • Position FX Forward

• Reverse

  • Text field.

  • Indicator for a reverse transaction.

  • Valid values:

    • True

    • False

  • This field has only indicative meaning and will NOT invert any signs in other fields.

• Date (Trade)

  • Date field.

  • A date on which a particular financial transaction is executed or agreed upon.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Date (Value)

  • Date field.

  • A date when cash or funds are expected to be received or paid as part of a financial transaction.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Portfolio

  • Text field. Case-sensitive.

  • A collection of financial assets or investments held by an individual or organization.

• Account (Cash)

  • Text field. Case-sensitive.

  • An account that is specifically designated for managing and tracking cash transactions.

• Instrument

  • Text field.

  • For Position FX Forward transactions:

    • A currency that is being purchased (buy currency - base) in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Position size

  • Numeric field.

  • For Position FX Forward transactions:

    • An amount of a particular currency that is being purchased (buy currency - base) in a foreign exchange transaction.

  • A sign of the number:

    • “+" (plus sign) is for position increase

    • “-" (minus sign) is for position decrease

• Principal/Share price

  • Numeric field.

  • For Position FX Forward transactions:

    • An exchange rate used for a contract’s foreign exchange transaction, where Sell currency is the Quote currency and Buy currency is the Base currency (e.g. we sell 110 USD and buy 100 EUR, then the field’s value should be 1.1 EUR/USD).

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Amount (Carry)

  • Numeric field.

  • For Position FX Forward transactions values should be “0" (zero).

• Amount (Charges)

  • Numeric field.

  • For Position FX Forward transactions values should be “0" (zero).

• Cash Consideration

  • Numeric field.

  • For Position FX Forward transactions:

    • An amount of a particular currency that is being sold (sell currency - quote) in a foreign exchange transaction.

  • A sign of the number:

    • “+” (plus sign) is for position increase

    • “-” (minus sign) is for position decrease

• Currency (Settlement)

  • Text field. Case-sensitive.

  • For Position FX Forward transactions:

    • A currency that is being sold (sell currency - quote) in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Payment Purpose (for Income/Expense)

  • Text field. Case-sensitive.

  • For Position FX Forward transactions values should be “-" (dash).

• Reference transaction code

  • Text field. Case-sensitive.

  • A reference to related transactions' unique identifiers.

  • For reverse transaction you can specify a transaction ID of the reversed transaction.

Instruments

Instruments

• Instrument ID

  • Text field. Case-sensitive.

  • A unique user_code for a financial asset or security involved in a transaction.

• ISIN

  • Text field. Case-sensitive.

  • An identification code assigned to a financial instrument (e.g. GB00BFZNLB60).
    

• Pricing Currency

  • Text field. Case-sensitive.

  • A currency in which the valuation or pricing of a financial instrument is expressed.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).
    

• Instrument Type

  • Text field. Case-sensitive.

  • A user-friendly name for a instrument type of financial asset or security involved in a transaction (may influence view forms).

  • Valid values:

    • Bond
    • CDS
    • CFD
    • Derivative
    • Forward
    • FX Forward Leg
    • Option
    • Other
    • Portfolio
    • Stock
    • T-Bill

• Asset Type

  • Text field. Case-sensitive.

  • A user-friendly name for an asset type financial asset or security involved in a transaction.

  • Valid values:

    • Alternative Investments

    • Cash & Equivalents

    • Commodities

    • Crypto

    • Debt

    • Derivatives

    • Equipment

    • Equity

    • Other

    • Real Estate

    • Transport

• Name

  • Text field. Case-sensitive.

  • A name of the entity.

• Short Name

  • Text field. Case-sensitive.

  • A short name of the entity.

• Public Name

  • Text field. Case-sensitive.

  • A public name of the entity. Will be shown instead of Name if user has no right to see this entity.

• Description

  • Text field. Case-sensitive.

  • Additional comments, instructions, or relevant information associated with a particular instrument.

  • If there are no notes enter “-" (dash).

• Country

  • Text field. Case-sensitive.

  • A currency in which the valuation or pricing of a financial instrument is expressed.

  • Must be iso 3 symbols country alphabetic code (e.g. LUX, GBR, USA).

• Security Price Multiplier

  • Numeric field.

  • A factor applied to adjust the nominal value of certain assets. For example, in the context of bonds, a price multiplier of 0.01 is used to convert the quoted price to its actual value.

• Maturity Date

  • Date field.

  • A date on which a financial instrument (e.g. bond or certificate of deposit) reaches the end of its term.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Maturity Price

  • Numeric field.

  • A unit price or value of a financial instrument, excluding any accrued interest or additional earnings effective after and including Maturity Date.

  • Must be in instrument Pricing Currency.

  • Multipliers will be applied automatically in accordance with an instrument of the transaction.

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Yellow Fields for Advanced settings can be left Empty

Instruments Accrual Schedules

• Instrument ID

  • Text field. Case-sensitive.

  • A unique user_code for a financial asset or security involved in a transaction.

• Accrual ID

  • Text field. Case-sensitive.

  • ID of accrual schedule entries (unique in one Instrument, may repeat for different instruments).

• Accrual Start Date

  • Date field.

  • A date on which a financial instrument starts accrual.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• First Payment Date

  • Date field.

  • A date on which a financial instrument has its first accrual payment.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Accrual Calculation Model

  • Text field. Case-sensitive.

  • A user code of the Day Count Convention a.k.a. Accrual Calculation Model (drop-down valid values in Excel).

  • Valid values (as per 2024-07-19 see reference in Finmars API like https://stage.finmars.com/REALM_CODE/SPACE_CODE/api/v1/instruments/accrual-calculation-model/):

    • DAY_COUNT_30_360_ISDA

    • DAY_COUNT_30_360_ISMA

    • DAY_COUNT_30_360_GERMAN

    • DAY_COUNT_30_360_US

    • DAY_COUNT_30_365

    • DAY_COUNT_30E_PLUS_360

    • DAY_COUNT_30E_360

    • DAY_COUNT_ACT_360

    • DAY_COUNT_ACT_364

    • DAY_COUNT_ACT_365

    • DAY_COUNT_ACT_365A

    • DAY_COUNT_ACT_365_FIXED

    • DAY_COUNT_ACT_365L

    • DAY_COUNT_ACT_366

    • DAY_COUNT_ACT_ACT_AFB

    • DAY_COUNT_ACT_ACT_ICMA

    • DAY_COUNT_ACT_ACT_ISDA

    • DAY_COUNT_BD_252

    • DAY_COUNT_NL_365

    • NONE

    • DAY_COUNT_SIMPLE

  • NONE is only applicable for Periodicity with defined N for example:

    • Accrual Calculation Model=N_DAY and Periodicity N=35

• Periodicity

  • Text field. Case-sensitive.

  • A user code of the Periodicity (drop-down valid values in Excel).

  • Valid values (as per 2024-07-19 see reference in Finmars API like https://stage.finmars.com/REALM_CODE/SPACE_CODE/api/v1/instruments/periodicity/):

    • -

    • ANNUALLY

    • BIMONTHLY

    • MONTHLY

    • N_DAY

    • N_MONTH_EOM

    • N_MONTH_SAME_DAY

    • N_WEEK_EOBW

    • N_YEAR_EOY

    • N_YEAR_SAME_DAY

    • QUARTERLY

    • SEMI_ANNUALLY

    • WEEKLY

• Periodicity N

  • Numeric field.

  • Only applicable for Periodicity with defined N, for example:

    • Accrual Calculation Model=N_DAY and Periodicity N=35.

• Accrual Size, %

  • Numeric field.

  • Accrual size is in %, so that you need to input 5 for 5% and NOT 0.05.

• End of Month

  • Text field.

  • Indicator for a payment in the End of Month.

  • Valid values:

    • True

    • False

Instruments Factor Schedules

• Instrument ID

  • Text field. Case-sensitive.

  • A unique user_code for a financial asset or security involved in a transaction.

• Factor ID

  • Text field. Case-sensitive.

  • ID of factor schedule entries (unique in one Instrument, may repeat for different instruments).

• Date

  • Date field.

  • A date on which a financial instrument set the factor.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Factor

  • Numeric field.

  • Factor size is of float type, so that you need to input 0.5 for 50% and NOT 50.

Prices

• Date

  • Date field.

  • A date of valuation.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Instrument ID

  • Text field. Case-sensitive.

  • A unique user_code for a financial asset or security involved in a transaction.

• Principal Price

  • Numeric field.

  • A unit price or value of a financial instrument, excluding any accrued interest or additional earnings.

  • Must be in instrument Pricing Currency.

  • Multipliers will be applied automatically in accordance with an instrument of the transaction.

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Accrued Price

  • Numeric field.

  • A unit price or value of accrued interest or other earnings of a financial instrument.

  • Must be in accrued currency.

  • Multipliers will be applied automatically in accordance with an instrument of the transaction.

  • A sign of the number:

    • “+" (plus sign) is for standard prices

    • “-" (minus sign) is for special prices (e.g. for exotic derivatives)

• Factor

  • Numeric field.

  • A multiplicative factor applied to the nominal or face value of a security, such as bonds or other financial instruments to adjust its value for various purposes.

  • Must NOT be negative.

• YTM

  • Numeric field.

  • Yield to maturity.

• Modified Duration

  • Numeric field.

• Yellow Fields for Advanced settings can be left Empty

FX Rates

• Date

  • Date field.

  • A date of valuation.

  • Format should be: “YYYY-MM-DD” (e.g. “2000-12-31")

• Currency ID

  • Text field. Case-sensitive.

  • A currency that is being purchased in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• FX Rate

  • Numeric field.

  • An exchange rate used for a foreign exchange transaction.

  • Must be in USD (USD must be quoted currency).

  • Must NOT be negative.

• Yellow Fields for Advanced settings can be left Empty

Other Entities

Currencies

• Currency ID

  • Text field. Case-sensitive.

  • A currency that is being purchased in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Name

  • Text field. Case-sensitive.

  • A name of the entity.

• Short Name

  • Text field. Case-sensitive.

  • A short name of the entity.

• Public Name

  • Text field. Case-sensitive.

  • A public name of the entity. Will be shown instead of Name if user has no right to see this entity.

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Yellow Fields for Advanced settings can be left Empty

Accounts

• Account ID

  • Text field. Case-sensitive.

  • A currency that is being purchased in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Name

  • Text field. Case-sensitive.

  • A name of the entity.

• Short Name

  • Text field. Case-sensitive.

  • A short name of the entity.

• Public Name

  • Text field. Case-sensitive.

  • A public name of the entity. Will be shown instead of Name if user has no right to see this entity.

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Yellow Fields for Advanced settings can be left Empty

Portfolios

• Portfolio ID

  • Text field. Case-sensitive.

  • A currency that is being purchased in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Name

  • Text field. Case-sensitive.

  • A name of the entity.

• Short Name

  • Text field. Case-sensitive.

  • A short name of the entity.

• Public Name

  • Text field. Case-sensitive.

  • A public name of the entity. Will be shown instead of Name if user has no right to see this entity.

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Yellow Fields for Advanced settings can be left Empty

Counterparties

• Counterparty ID

  • Text field. Case-sensitive.

  • A currency that is being purchased in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Name

  • Text field. Case-sensitive.

  • A name of the entity.

• Short Name

  • Text field. Case-sensitive.

  • A short name of the entity.

• Public Name

  • Text field. Case-sensitive.

  • A public name of the entity. Will be shown instead of Name if user has no right to see this entity.

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Yellow Fields for Advanced settings can be left Empty

Responsibles

• Responsible ID

  • Text field. Case-sensitive.

  • A currency that is being purchased in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Name

  • Text field. Case-sensitive.

  • A name of the entity.

• Short Name

  • Text field. Case-sensitive.

  • A short name of the entity.

• Public Name

  • Text field. Case-sensitive.

  • A public name of the entity. Will be shown instead of Name if user has no right to see this entity.

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Yellow Fields for Advanced settings can be left Empty

Strategies

• Strategy ID

  • Text field. Case-sensitive.

  • A currency that is being purchased in a foreign exchange transaction.

  • Must be an alphabetic code of a currency alphabetic code (e.g. USD, EUR, CHF).

• Name

  • Text field. Case-sensitive.

  • A name of the entity.

• Short Name

  • Text field. Case-sensitive.

  • A short name of the entity.

• Public Name

  • Text field. Case-sensitive.

  • A public name of the entity. Will be shown instead of Name if user has no right to see this entity.

• Notes

  • Text field.

  • Additional comments, instructions, or relevant information associated with a particular transaction.

  • If there are no notes enter “-" (dash).

• Yellow Fields for Advanced settings can be left Empty