Skip to main content

Extensions Q1 / 2021 - Release notes

These features, improvements and bug fixes have been developed as extensions during Q1 / 2021 - they have been released in FA AppStore throughout the quarter, allowing you to update the extensions you are using to the latest version from the FA AppStore.

Accounting

Features and improvements

  • SIE Export process now exports the SIE file with a more solid file name and file extension. File extension is changed from .sie to .se according to the recommended file extension for export files from financial reporting systems, and the file name is now dependant on number of portfolios included in the file (either SIE_mindate-maxdate.se for multi-portfolio files or portfoliShortName_mindate-maxdate.se for single portfolio).

Bug fixes

  • Bookkeeping rules no longer runs unnecessarily on all transactions/trade orders with a parent portfolio - the condition to trigger bookkeeping rules is now more limited, and bookkeeping rules are only run on transactions (not trade orders) and only when the portfolio has posting rules linked to it. This ensures the rules are not run unnecessarily when the rule wouldn't anyway result in postings.

  • Bookkeeping rules now work correctly also in versions older than FA 3.7, allowing you to use the latest version of the rules even in environments that don't yet support tracking fund's accrual.

Analytics

Bug fixes

  • First column in Strategy Analyzer widget's results is now frozen, making it easy for you to track the numbers at the end of the table.

APIs

Features and improvements

  • Standard API: Transactions and trade orders now allows you to also fetch transaction's price, coefficient and reference.

  • Standard API: Queries now allows you to choose to direct the API call to main or replica database with a parameter. Note that you need to have a replica database set up to use this parameter!

Bank and custody connections

Features and improvements

  • M2Wealth: Import transactions and reconcile positions process now supports reconciling positions on trade date (in addition to settled quantities), when there is no settlement information of trade positions from the bank.

  • M2Wealth: Import transactions and reconcile positions process is now configurable in an easier way, and no longer requires a custom route to process the files.

Communications

Bug fixes

  • Show status of sent SMS-messages now works again after version FA 3.7 and newer.

  • Messaging package and Send message(s) process no longer require you to enter old unnecessary configurations for the processes to work.

Compliance

Bug fixes

  • Portfolio/Asset Value Monitoring is now more fail-safe when sending e-mails: if the connection cannot be established at first attempt, the process will try 2 more times with 10 seconds wait in between to send the email.

  • Limits report now divides the limits it lists under headings "Pre-trade limits", "Post trade limits" and "Investment plan limits". This structures the content, allowing you to see which type of a limit is listed in the report.

  • PEP and Sanctions lists integration now works correctly with template configurations used in the Standard Setup.

Corporate actions

Bug fixes

  • Coupons and Expirations process no longer sets the settlement date on a non-business day on bonds with "No adjustment" business day convention. If you have a bond with "No adjustment" business day convention, and the coupon payment falls on a weekend, the settlement date is now set as the following business day.

Data aggregation

Bug fixes

  • General importer process now runs contacts, securities, portfolios or orders through rules, ensuring that any custom rules are applied also when importing data programmatically.

External reporting

FATCA and CRS/DAC2 reporting

Bug fixes

  • FATCA process now formats the docRefId and messageRefId correctly both in Finland and Sweden based on transmitting country. If the report is generated in Finland (FI), a dash "-" is used as a separator, otherwise a dot "." is used as a separator.

  • CRS/DAC2 process includes various bugfixes: accounts are now reported only once for required types, excluding reported accounts from controlling person now works correctly, reporting no longer fails if the controlling person also has items to report, and fake value is now correctly used for identification number (IN) when IN is not given.

  • In addition, taxfi xml schema has been updated to version 2.0 in CRS/DAC2 process.

MiFIR transaction reporting

Features and improvements

  • MiFIR Transaction reporting process now also supports automatic sending of MiFIR transaction reports to authorities and choosing between test and production systems in standard MiFIR routes.

Bug fixes

  • MiFIR Transaction reporting process now longer crashes if configured LEI code is invalid. If an invalid LEI code is configured, the user is now provided with a proper error message instead of an error on the logs.

SIRA reporting

Features and improvements

  • SIRA report process now supports also creating Private Equity fund (PEF) records. The option to produce either PEF report or regular investment fund report is based on a process configuration.

Bug fixes

  • SIRA report process now again produces a report that can be uploaded to Bank of Finland's service after fixing the incorrect character formatting .

Other external reporting

Features and improvements

  • New Futur IDD report process allows you to report ex-post costs and charges to Futur. This process creates XML report files containing ex-post cost information that can be sent out to Futur.

Bug fixes

  • AIFMD reporting for DNB custody process now gets accrual for fund securities and reports it same way as accrued interest for bonds in account balances. Before, interest fields were left empty for fund instruments in account balances section.

FA Front

Bug fixes

  • Attachments now again work correctly in FA Front's Send Message process.

Fee management

Features and improvements

  • Standard capitalization process now supports settlement date lags. You can now choose to set the settlement date of the transactions based on manual (fixed date), offset (number of days from transaction date adjusted by holiday calendar in use) or automatically calculated (calculate the date like it is calculated in transaction form).

  • In addition, Standard capitalization process has been improved in terms of memory usage and performance when there is a large number of capitalization configurations.

  • Standard Fee Calculation process now saves a record of all fee calculations run by it into the Fee calculation view. This allows you to see at once all the fee calculations run in the system (including scheduled fee calculations), and to manage also the calculations performed with this process.

Bug fixes

  • Standard capitalization process now works correctly also when the currency of the security is different from the currency of the account - the currency of created transactions is set based on the security and not the account if security is defined.

  • Standard capitalization process now supports capitalizing multiple accounts with the same target account, transaction type and security. Checking of previous capitalization date has been improved to make it possible to use the same target settings for multiple configurations.

  • Standard Fee Calculation process now correctly uses the calculation date given in the user interface, if the user manually enters a date for the fee calculation.

  • Periodic relative fee formulas now record correct information and values when describing the calculation formula into the created fee transactions.

  • Accrued kickback and Accrued management fee formulas no longer produce unnecessary rows on the logs on a daily basis.

Fund management

Features and improvements

  • Fund Management process now supports also the new trade order execution method field to interpret client orders as unit-based or trade-amount-based.

  • Fund settings profile now allows you to select how account is set to the executed client orders, and define accounting settings for running deferrals within the new FA Fund Management application.

  • UCITS xml report process now supports generating the report automatically with offset days and fund's business day convention. In addition, the process now reports FX Contracts correctly, grouping the two future cashflow positions together to represent an FX Contract to report.

  • UCITS xml report process now supports identifying OTC instruments based on their market place. Normally securities are divided into different blocks in the report based on their security type. However, this is not detailed enough for some OTC instruments, and instruments should instead be identified based on their marketplace. A new configuration allows you now to list marketplaces that would result in the instrument to be listed in the OTC block.

  • In addition, UCITS xml report and Custodian reports to Danske processes are now compatible with NAV calculations done in the new FA Fund Management application.

Bug fixes

  • Fund Management process now analyzes limits on the NAV calculation date (instead of current date) and stores the result of the limit analysis into portfolio's limits.

  • Fund settings profile now again contains the checkbox "Mark postings are 'Reported'".

  • Fee formula for income distributions now uses the correct signs in the results, and correctly interprets the new structure of defining income distributions in the Fund settings profile.

  • UCITS xml report process can now handle scenarios when a security included in a prior NAV calculation can no longer be found with the same code when the report is generated - process no longer produces an erroneous file if it cannot find an old security.

Market data connector

Features and improvements

  • EOD Historical Data security data and prices connector now supports fetching update codes for securities through the Security window or Update menu. As with other market data connectors, ISIN and currency are used to fetch the result.

  • Bloomberg security data and prices connector has been improved in terms of configurability: update code fetching is now supported also when no mapping is defined.

  • Create/update security information from external source process now supports configuring mapping key even if the integration already has a mapping defined. This allows you to run the process with using multiple mappings with Bloomberg.

Bug fixes

  • Bloomberg security data and prices connector now works interprets securities correctly based on their ticker also when there is a dot "." in the ticker.

Model portfolio management

Features and improvements

  • Invest deposits according to investment plan rule now supports an option to temporarily pause automatic investments of monthly savings for specific portfolios. This does not pause the monthly savings (deposits) themselves, but simply prevents the automatic investments rule from firing (until the portfolio is un-paused). You can pause automatic investments through tagging the portfolio with "Automatically invest deposits-Paused".

  • Execute cash transfers process now supports tagging portfolios that receive cash. This allows you for example to automatically rebalance a portfolio after it receives cash from a transfer.

Bug fixes

  • Rebalance templates process now allows you also to use "Other tags". Saving a rebalance template with other tags no longer produces an error and is correctly saved.

  • Rebalance templates process now works correctly also when scheduled: scheduled runs no longer fail doe to invalid dependency.

Payments

Features and improvements

  • Monthly withdrawals process now supports sub-portfolios and withdrawal priorities. These allow you to withdraw a percentage of an investor's funds on a monthly basis. These funds may be split across multiple portfolios; if so, the withdrawals should not be done evenly across these portfolios, but instead withdrawn from portfolios in a prioritized order (i.e. withdraw from portfolio A until it is empty, then from portfolio B until it is empty, etc.).

  • General incoming payments process for incoming CAMT053 payment processing picks up payer information and passes it on to the "Internal info" of the created payment transaction.

  • General outgoing payments process now supports automatically converting Norwegian IBAN account numbers to standard account number format.

Portfolio management

Features and improvements

  • New Security pricing formulas process now allow you to define a pricing formula on your securities with a groovy script, and to price your securities through running the script and storing the calculated market data entry to your security.

  • New Total position in selected security over time query allows you to export a time series of aggregated positions (units).

  • Transfer assets between portfolios process now uses the standard customer/portfolio selector for better usability and consistency.

  • Document checker process has been improved in terms of feedback it provides and the error log messages it produces. In addition, the process now runs rules on the objects it tags.

Bug fixes

  • Populate fixings for floating rate notes process now rounds the calculated fixing values. Before, fixings were saved without rounding which caused problems in some scenarios and resulted in coupon payment corporate actions to fail.

  • Export trade orders and Trade splitting processes are now able to correctly handle also transactions with exchanges and/or marketplaces.

  • Trade splitting process is now again able to generate any transactions after to fixing an unresolved compatibility issue.

  • Update security price from portfolio process now works better with fixed percentage and day count convention. Fixed price percentage on new securities or securities without market data now work correctly, and better error handling has been added for situations when selected day convention cannot be used (some conventions need more data than end and start dates).

Reconciliation

Features and improvements

  • New Positions export query lists all positions in the selected portfolios on the selected date. The query uses the standard format used by reconciliation and position import - the query returns columns for portfolio short name, date, amount as well as security ISIN or code (primarily ISIN, code if ISIN not available) or account.

Reporting

Bug fixes

  • Positions by customer report no longer uses an extremely slow query to fetch the positions. In addition, the latest version of the report with these performance improvements is now compatible also with version FA 3.7 and older.

  • Transaction confirmation report now works also with versions older than FA 3.8.

  • Schedulable report generation process now again supports PDF encryption.

Settlements

Features and improvements

  • SWIFT process no longer contains an additional slash in SHB csv settlement message in the 95RValue field.

Tax reporting

Finnish tax reporting

Features and improvements

  • VSAPUUSE report (Annual notification - Purchases and sales) in Finnish tax reporting process now allows you to generate the report in the background. If there are a lot portfolios and transactions to report, running the process will take some time - through running it in the background, you can continue with other work and fetch the results later through the Tasks view.

  • VSAPUUSE report (Annual notification - Purchases and sales) in Finnish tax reporting process now also handles futures' purchase and sell values correctly in the report.

  • VSTVERIE report (Annual notification - Profits and shares) in Finnish tax reporting process now supports fetching tax from "Tax 1" field of the transaction if "Tax 2" field is empty for payment type 2E.

  • VSTVERIE report (Annual notification - Profits and shares) in Finnish tax reporting process now allows you to bypass position reporting completely, when you are not required to report e.g. fund position to the tax authority. Bypassing position reporting will also make the report lighter for clients that do not report position at all.

  • VSULKOSE report (Annual notification - Foreign dividends) in Finnish tax reporting process now also produces a csv output for checking purposes, making it easier for you to check and verify the data that is reported to the tax authorities.

  • VSULKOSE report (Annual notification - Foreign dividends) in Finnish tax reporting process now allows you to report both dividends and dividend as shares at the same time: you can now configure multiple transaction type codes as the "Transaction type code for dividends".

Bug fixes

  • 9A tax form report generated in Swedish now contains proper titles for all sections in the report.

  • All tax reports (VSAPUUSE, VSTVERIE, VSRAERIE, VSOMHOIE, VSULKOSE, VSKTVYSL) within the Finnish tax reporting process now use correct rounding method (HALF_UP) for all values that need to be rounded.

  • Open tasks created by the Finnish tax reporting process are now named clearly with the report name and timestamp ("<ReportName> report was generated on <timestamp>"), allowing you to find open tasks related to a tax report generation.

  • VSAPUUSE report (Annual notification - Purchases and sales) in Finnish tax reporting process now ensures that the field 049 Transaction code always contains a unique identifier. The identifier is formed as PurchaseTransactionId + TransactionId + lot, accompanied with a running number in a rare case of duplicates.

  • VSAPUUSE report (Annual notification - Purchases and sales) in Finnish tax reporting process now contains all sell transactions regardless of whether the transaction resulted in any profit/loss.

  • VSAPUUSE report (Annual notification - Purchases and sales) in Finnish tax reporting process now correctly includes transfer tax in field 152 also when reporting is done with role 3 and 4.

  • VSAPUUSE report (Annual notification - Purchases and sales) in Finnish tax reporting process now correctly skips reporting certain types of securities (for example Bonds) with reporting role 3.

  • VSAPUUSE report (Annual notification - Purchases and sales) in Finnish tax reporting process now contains the correct fake ID and name also for private persons. If customer has no business ID or person ID, field 083 now gets a fake id (010101-UUUU for persons and 0000000-0 for organizations) and customers name is filled in correctly. Before, organization information was used also for private persons.

  • VSRAERIE report (Annual notification - Limited tax liability payments) in Finnish tax reporting process now contains proper fake id and TIN handling. If the contact doesn't have a person ID or business ID, then fake id is used in field 083 (010101-UUUU for persons and 0000000-0 for organizations), and field 313 includes TIN for organizations.

  • VSTVERIE report (Annual notification - Profits and shares) in Finnish tax reporting process now pick up the correct common business id in field 010 for payment types other than 2B, 2G, 3J and 3L.

  • VSTVERIE report (Annual notification - Profits and shares) in Finnish tax reporting process now calculates the tax correctly in field 535 also when there are multiple transactions with the same customer, security and tag and the transactions are aggregated together to one row in the file.

  • VSTVERIE report (Annual notification - Profits and shares) in Finnish tax reporting process now correctly uses the payment date of the transaction (instead of the transaction date) if payment date has been defined to determine when the transaction should be reported.

  • VSULKOSE report (Annual notification - Foreign dividends) in Finnish tax reporting process now correctly aggregates data up to one row if customer, payment date and ISIN code of the dividend are the same.

  • VSULKOSE report (Annual notification - Foreign dividends) in Finnish tax reporting process now picks dividends to the report based on payment date (instead of transaction date) if payment date has been defined.

Norwegian tax reporting

Features and improvements

  • Verdipapirfond report in Norwegian tax report process now supports handling tax-free transfers between two shareholders for correct FIFO chain. If an individual in Norway is making a transfer of shares between two financial institutes, for that tax year both the transferring out and transferring in institute becomes legally obligated to report a full tax year for that person. Norwegian tax report now takes this into consideration when handling the transfer transactions.

  • Verdipapirfond client report in Norwegian tax report process now supports excluding fees in the client report. Leaving out the fees is relevant when you don't book fee transactions into each shareholder's portfolio separately, but the shareholders pay fees within the fund they have invested in.

Bug fixes

  • ASK report in Norwegian tax report process is now properly validated in terms of the XML Schema.

  • Finansprodukter client report in Norwegian tax report process now shows a correct percentage threshold of 35%. In addition, the percentage threshold is removed from corresponding organization reports.

  • Verdipapirfond client report in Norwegian tax report process no longer fails when run for a large set of portfolios at once.

  • Norwegian tax report process now handles bought interest correctly also for subscriptions and redemptions that occur on December 31st for funds that include income distribution in the fund's value on the same date. Before, bought interest was doubled in such a scenario.

Swedish tax reporting

Features and improvements

  • KU31 (Income statement for dividends etc for shares and other securities) report in KURED process for Swedish tax reporting now supports monthly reporting of dividends. According to tax authorities, dividends should be reported within 4 months from the day the dividend was received - instead of fetching dividends for the entire tax year, KU31 report now supports fetching dividends based on a time period, allowing you to report them with shorter intervals.

  • KURED process for Swedish tax reporting has been improved in terms of handling cancellations. You can now cancel reported data with greater precision than before - you can flexibly cancel specific data only for specific contacts and only regarding data reported on a given date. Before, cancelling the reported data was an all-or-nothing matter.

Bug fixes

  • KU30 (Income statement for investment savings account) report in KURED process for Swedish tax reporting not correctly considers portfolio's account setting "Exclude balance from portfolio total" when calculating portfolio's total market value.

  • KU40 (Income statement for transfer of shares in investment funds) client printout in KURED process for Swedish tax reporting now works also in situation when client has made a profit and a loss on the same security during the tax year.

  • KU50 (Income statement for pension savings) report in KURED process for Swedish tax reporting no longer shows a validation error due to security information that shouldn't be included in the report at all.

Trade order management

Features and improvements

  • Bulk trade orders process now allows you to optionally bulk your orders based on order's parent portfolio or order's portfolio's primary contact. This allows you to bulk your orders "per client" in case your clients have multiple portfolios or you are are maintaining your client portfolios in a parent-sub structure - bulking your orders based parent portfolio or primary contact allows you to send out only one order to the market.

Bug fixes

  • Validate Orders process now also works for orders without an account linked to the order. For improved cash flow control, account is not required anymore if the order does not have negative cash flow.

Trading connector

Features and improvements

  • Trading connector toolbox versions 1.3 and 1.4 provide the tools for Trading microservice 1.3 and 1.4. This package contains Infront, Allfunds and DNB routing options using the Connector microservice, along with all other trading connectors.

System (including Administration and Utilities)

Features and improvements

  • Query based monitoring process now allows you to choose to direct the queries to main or replica database with a parameter. Note that you need to have a replica database set up to use this parameter!

Bug fixes

  • Monitor User Count process now contains performance improvements and more descriptive text under "Last login date". If the last login information cannot be fetched, the user listing now shows "Not available" instead of "Never".

  • Integration Startup Tool process now reloads all beans whenever classloader is refreshed, ensuring the objects created with the tool won't eventually stop working when classloader is refreshed.

  • In addition, scheduled processes against Portfolios view now work again.