How to handle acquisition values for internal transfers via API
February 26, 2021. Carl Haglind.
In order to simplify things and make this method (CreateInternalInstrumentTransferOrders) less error prone we have removed the two properties AcquisitionPrice and AcquisitionPriceAccountCurrency. Instead we calculate these from their corresponding value-properties: AcquisitionValue and AcquisitionValueAccountCurrency.
But don’t worry, we will not make any breaking changes for you but instead deprecate these properties in the API method in the near future. Be aware though that these properties will not correspond to any functionality.
AcquisitionPrice = AcquisitionValue / Units
AcquisitionPriceAccountCurrency = AcquisitionValueAccountCurrency / Units
We also let the user decide if they want the system to use a default behavior to set the Acquisition values or not. If the properties AcquisitionValue and AcquisitionValueAccountCurrency are submitted with any values apart from null we will use the formulas above to set their corresponding Acquisition prices on the order. However, if these values are submitted as null, the system will default these values on the order. The Acquisition values set on the order will be as follows:
The acquisition values on the transactions placed on the account where the asset is transferred from, will always be calculated from the acquisition price taken from its origin position.
The transactions on the account where the assets are transferred to will depend on whether the order will result in a technical trade or not.
If the order will result in a technical trade the acquisition values will be calculated from the current price of the asset that is transferred. An order that will not result in a technical trade will calculate its acquisition values from the current position and will therefore obtain the same values as for the transactions placed on the account where the asset was transferred from.
More Developer posts
Why I love using Bricknode for new financial applications - January 19, 2022
How to connect to the BFS API using Visual Studio and our NuGet package - October 12, 2021
New API release including AutoGiro Orders - February 1, 2021
We are speeding up the release rate of new API functionality - January 24, 2021
Use JSON to work with complex data in custom fields - June 27, 2020
The great new feature called KycDate - February 16, 2020
Our API progress in release 2.23 of BFS - January 3, 2020