Standard Solution March 2023 - Release notes

Documentation in FA User guide about fee formulas is improved to better explain the available options and the different configurations. Learn more: Configure a fee formula in FA User Guide.

Documentation in FA User Guide about handling options have been improved to better explain which transaction types to be used. Learn more: Options in FA User Guide.

In January release we switched to using a new implementation of settlements, which allows greater configurability and usability. This version introduces a new configuration profile to set up SEB settlement-specific connection parameters. Learn more: Settlement configurations for SEB in FA User Guide.Settlement configurations for SEB

Earlier we introduced a new security field Votes per share in FA Back to track how many votes one has in a company. Now we updated our mapping used to create securities with the Bloomberg reference data integration so that it also fetches Votes per share automatically when an equity security is created.

Bloomberg and Stamdata mappings used when updating security reference data now also fetch Moody’s, Fitch & Standard & Poor´s issuer credit ratings along with information about whether a bond is covered or not. Ratings are saved as Security key figures, and covered/not covered is saved to security Solvency II profile.

Transactions and holdings files to Futur Pension now also include data about accrued interest if there are bond positions/transactions in a reportable portfolio.

Before, we used the same email/sms message template for the initial document signing request message and the reminder messages. With this version, you can use different templates for the initial request and reminder messages. Having separate templates is more convenient for the recipient – they could tell at a glance if the message is for a new request or related to a previous one. Learn more: Document signing in FA User Guide

Norwegian tax Finansprodukter report now supports a tag to use for filtering out transactions. Typically used in situations when transactions in the portfolio should not be included in the reporting. Learn more: Create authority reports in FA User Guide.

The limits history dashboard now uses updated queries – now it also shows the current limit value, minimum limit value, maximum limit value, and the actual run time. 

Limit report(s) now uses data from GraphQL API to get sufficient information about the analysis details. The report now also structures the result in a tree making it easier to read. Learn more: Generate limit report in FA User Guide.

New Tax formula for income distribution calculates tax on income distributions for the funds that do not pay out dividends to the shareholders. The new formula is used with the ITX - Accrued tax debt for income transaction type.

If you want to combine similar trade orders from client portfolios into one big order before sending them to the market, you can bulk orders together. This version introduces a new profile for configuring specific bulking parameters. Learn more: Handle bulking in FA User Guide.

The sample set of accounts for bookkeeping which is available as an optional package now has a proper account number for "Clearing account" instead of having a text as the account number.

There were two pre-configured views for trading order waiting bulking with identical search criteria. Duplicate view is now removed.

The Private Equity security type now uses the Always use average price valuation method to not cause issues with purchase lots if the deferral process is used.

The contacts view "Contacts on sanctions list" used tag SanctionsList-Yes. Changed the tag on the view to use Sanctions list-Yesinstead.

Some transaction type effects of transaction type Add (internal) are changed to properly reflect the use case of the transaction type.

Background-generated documents with no creator user, such as reports scheduled to document library could not be migrated to the new document library since FA Back 3.16.9. This is now again possible.

The exact content that FA receives back when creating or updating a security from Stamdata can vary from client to client due to different setups on Stamdata side. To avoid situations where we might input empty values for coupons, we have added a null-check to prevent that from happening.

Fixed an issue where mutual funds could not be created when using EOD Historical Data market data connector.

Fixed an issue in formulas used for Analytics+ columns Theta, Vega, Rho and Gamma used for options.

Incoming payments process is improved so that the generated CSV files which are attached to the tasks, no longer become malformed if any of the columns contain semicolons.

Incoming payments no longer update the trade order status to Executable status for payments where the amount mismatches. Status instead remains untouched.

Outgoing payments now work again with fetching the payment account and contract details from security profile.

SEPA payments can contain either an “unstructered message” or a creditor reference, but not both. Fixed an issue in Outgoing payments pain.001 generation so that we don't include both if such information exists for the transaction. If a creditor reference is provided, only creditor reference is included.

Fixed an issue in Norwegian tax Finansprodukter report so that it no longer fails to report dividends if a sell has happened after the dividend.

The SIRA/PEF report did group capital flows together unless the "Aggregate holdings on this share class" selection was selected in the SIRA/PEF profile of the share class security. This was incorrect, since the capital flows should always be grouped together per share class, regardless of what's selected on the share class profile. This is now fixed. Note that this applies only for Private Equtiy.

Position reconciliation now works properly even if the processed file has empty rows. Now ignores rows that have no account number and no ISIN code.

Position reconciliation can now handle MT535 files with "messages block 5 (trailers)" which some banks (i.e. Nordea) implemented. Before our MT535 processor broke when trying to read it.

When mass running the PEP and Sanctions check from Trapets, the process now tags/flag the contact correctly if there is a match. Before, the sanction list flag was not set properly.

Buy/Sell/Switch process no longer saves orders twice. Before every order was saved twice and used unnecessary resources.

Previously there was an issue generating API-based reports using the reporting API when having an extra back-API instance in use. That issue is now resolved.

The query monitoring process no longer generates a very long logging in AUDIT_SYSTEM table as the message is supposed to be readable at a quick glance and any details should be in the attachment.