Extensions Q2 / 2020 - Release notes

Deferral of other securities now allows you to create reverse transactions with a different transaction type. In order to be able to use different bookkeeping accounts for +/- transactions and use the option to reverse the deferral transactions the following day so that the effect of the transaction is reversed also from bookkeeping point of view, a new configuration now allows you to define a separate transaction type code for the reverse transactions. This allows you to define different posting rules for "reversals".

Deferral of other securities now runs the created deferral transactions through any rules installed in the system, and has been optimized to avoid triggering an unnecessary report recalculation.

Deferral of other securities for accounts now also takes into account the effect of unsettled transactions in the deferral amount.

Bookkeeping rules now correctly calculate "currency profit" also in a scenario when you are using multiple currencies and you have selected to "Use book values for FX profit calculation".

Bookkeeping rules can now correctly handle transactions without an account and security, often created into the portfolio for certain kinds of costs or for TWR calculation.

Strategy Analyzer now allows you to choose between TWR Net or Gross when doing attribution analysis. Which one to use depends on the user's preference of what type of TWR they report to their stakeholders.

Strategy Analyzer can now correctly analyze a portfolio which has an asset class or asset type entirely sold away during the analysis period - this scenario is now handled without unnecessary errors.

Performance of Transactions and trade orders API has been optimized, and new endpoints (v2.0) for trade orders and transactions and their filter methods have been released.

General importer API has been restructured for better performance to handle running rules more efficiently and to avoid saving the imported data twice.

Standard APIs have updated to take into account the possibility obfuscate certain client data in the database, and the APIs now correctly return the obfuscated data as "de-obfuscated".

M2 integration now allows you to map transaction types with data mapping.

M2Reader within the M2 integration now picks available account on interest transactions even when security information (master data) is unavailable.

Asset / value monitoring now allows you to conveniently monitor new contacts, as soon as they start to have assets into their portfolio(s), without you having to manually enter a "previous reporting date" for such contacts. If configured to do so, this process not doesn't skip contacts who do not have a previous reporting date. Instead, the contacts' previous asset value default to 100%, and monitoring is done as long as the contact has assets on the end date of the monitoring (i.e. current date).

Drift tracker now works even in scenarios when the system has currencies with mismatching code and name, and if the portfolio has multiple accounts in the same currency.

Ex-post costs report now shows percentage figures in cost breakdown correctly also when there are third-party payments involved.

Corporate actions now include a new query that allows you to generate corporate action import files for partial redemptions on bonds. This query searches from your bonds' security information for redemptions marked for the current date. If it finds such redemptions, it creates an import file which, once imported through the transaction importer, creates redemption transactions into all active portfolios which contain a position in that bond security.

Import corporate actions process now has an improved logic to update existing corporate actions: in addition to having the same corporate action type, security and date, a corporate action now also needs to have the same transaction type in order for the process to update it (instead of creating a new corporate action). This now supports a corporate action workflow wherein a single corporate action is run in two stages (for example running an “estimated dividend” first, then a “realized dividend” later), so that we get two separate corporate actions instead of updating the single one.

Coupons and Expirations process no longer produces a zero coupon in a specific scenario when running the process on a fixing date on floating rate notes (when fixings are defined one-by-one within the bond information) - the process now results in a correct coupon even when run on a floating rate note's fixing date.

Import - Transaction approval process now works even when you don't have a market data connector connected to "Close 2" field - you can now configure which close field your market data connector is connected to, or use the process without a connection to market data.

Fixed an issue in the Import - Transaction approval process to correctly handle scenarios when the process is run without user's input, and the imported transactions contain securities missing from the system.

As a new feature, you can no generate AIFMD report to DNB custody, allowing fund companies to report their AIF funds to DNB when using DNB as a custody. The reporting process generates daily "TRUSTEE AIF XML" report to DNB "depotmottakker".

MiFIR reporting now allows you to use an additional tag to control which transactions are used with which configuration sets. This allows you to use the standard MiFIR-related tags to control whether transactions should be reported at all, and an additional tag to control for example which country the MiFIR report should be sent to.

SIRA reporting for Bank of Finland has been updated according to the changes in record structures, required from May 2020 onward. In addition, the report can now also handle derivatives correctly.

Certain values in certain sections of the SIRA reporting for Bank of Finland have been corrected: SBS section in Subscriptions (B) and Redemptions (S) now shows market value (dirty) correctly even if the fund's currency is different than EUR, and ITEM section now shows counterparty identifiers correctly if counterparty's type is O (=Other).

TIN element in the FATCA report is now left out (instead of being empty) from AccountHolder / Organization structure for organizations if TIN has not been defined.

You can now select to show the "from" account to your users for your customer's withdrawals through an optional filed in FA Front's Deposit / Withdrawal process. This allows you to show which account your customer's deposit is withdrawn from.

You can now select to show a date selector for your customer's deposits and withdrawals through an optional filed in FA Front's Deposit / Withdrawal process. This allows you advisors to select a date when entering a deposit or a withdrawal on their customer's behalf, when the transaction is created on the selected date instead of current date.

Buy, Sell or Switch process now allows you to generate a switch by using the same trade amount for both sell and buy sides of the switch. This allows you to do trade-amount-based same day fund exchanges, when the buy and the sell should always get the same trade amount (instead of setting the buy's trade amount initially 0, which is later updated based on the sell once the sell is executed).

Standard capitalization process now allows you to do capitalizations per account. This allows you to capitalize multiple accounts separately in a more convenient way - for example, if your portfolio has two accrued interest accounts and two corresponding cash accounts (accrued interest and cash in EUR and accrued interest and cash in USD), you can now capitalize accrued interest interest in EUR into EUR cash account and the same for your USD accounts. Capitalize-per-account also supports looking for account tags when looking for the previous capitalization date.

Performance of the account interest formula has been optimized in scenarios when a single portfolio contains multiple accounts that accrued interest should be calculated for.

Standard fee calculation process now again correctly considers the account tags, allowing you to configure which account to use the book the fees into.

Fund management now uses the actual cashflow with receivables and liabilities (instead of determining receivables and liabilities through transaction type effects. This allows for example negative dividends to be correctly treated as liabilities.

Fund management now support recording accrued income into the "Accrual" field for fund security's market data and unit holder transactions. This new field is available from FA 3.7 onward, allowing you to record this data into the appropriate field also through Fund Management.

Fund info profile on your fund portfolio now allows you to enter details about the NAV calculation schedule. You can define First NAV date, frequency, holiday calendar, business day convention, roll contention and offset - based on this information, calculating NAV on your fund will keep previous and next NAV and calculation dates up-to-date. Allows you to follow up when you should next calculate NAV on your fund, available within the new FA Fund Management application.

Danske custodian reports now allow you to exclude closed accounts from cash balances report.

Fund management now excludes portfolio-level income distribution / management fees from the gross asset value. When you have a fund with only one share class that has a portfolio-level accrued management fee (included in income distribution) and income distributions set up, the management fee was incorrectly included in the gross asset value on the share class resulting in it been deducted twice.

Fund management's NAV calculation no longer crashes with "Something went wrong" if there are sub-share classes without previous price.

UCITS report is now saved to the correct folder after fixing an issue in the path used to save the report.

Stamdata market data connector now allows you to fetch instrument data also form other datasets than "Issue", allowing you to get more instrument information through the connector than just the basic instrument data.

Bloomberg market data connector now allows you to connect to your Bloomberg Terminal account, allowing you to get more data through the connector in case you have credentials to Bloomberg Terminal.

Bloomberg market data connector's flags "fetchCreditRisk" and "fetchFundamentals" can now be disabled through configuration, allowing you not to include this data within your data. Note! If you were using these feeds before, you need to update your feed configurations!

Fetching instrument data through market data connectors now appropriately handles situation when fetching is started against an empty list of securities - instrument data is no longer unnecessarily fetched for an empty list of securities.

Payments now supports adding a regulatory reporting code to the pain.001 file if it has been defined in the payment transaction's internal info with identifier "RegulatoryReportingCode".

Incoming payments for NETS rejection handling now allows you to find transaction and portfolios also with their database IDs, and supports configuring all tags used within the process.

Fixed an issue in outgoing payments for NETS files that prevented the file from being generated properly.

As a new feature, Monthly investment and de-investment schedules now allow you to define how much of specific securities your investors want to buy or sell each month. Based on the investment or de-investment schedule, the process creates buy or sells for your portfolios based on what has been defined in the schedule.

Mark-to-market now correctly shows the configured default trade time in the process, and also transfers the defined trade time into the created mark-to-market transactions.

Position reconciliation and Cash reconciliation processes now correctly allow you to configure the process so that only users with certain role(s) are allowed to complete the reconciliation task.

Cash reconciliation now takes into account transactions without a settlement date, and also allows you to correctly configure the process to use cash balances based on settlement dates in the reconciliation.

Positions report (3.0 version) now shows purchase value, purchase unit price and change correctly also for short positions after changing the report pick up the data from the correct field.

Fixed an issue in the latest version of the Settle transactions with a file (SWIFT) process that prevented the process from saving the generated files to disc.

Signicat Sign API now gives a response as soon as we have verified that the request itself is valid (or invalid), ensuring we respond to requests fast enough. In addition, this process now logs events appropriately, making it easier to investigate potential issues.

Signicat Sign process no longer creates duplicate "Completed" tasks (records about what was signed and when) even if you have configured the process to store such as task behind a contact.

You can now use a separate process to "Calculate ASK balance for portfolios" as part of Norwegian tax reporting. Norwegian tax reporting does the ASK balance calculations when the tax report is run, but this new process now allows you to run the calculation separately for example to easily get a daily or monthly status on your portfolios' ASK balance.

VSAPUUSE report in Finnish tax reporting now contains a unique transaction ID in all scenarios due to a fix in lot number logic in field 049 for reporting in roles 2, 3 and 4. The logic used to enter 000 in all scenarios, which caused duplicate IDs in some cases.

Latest taxpayer's form for "9A Tax form" for Finnish tax reporting now correctly calculates capital gain from acquisition cost assumption if it is greater than the acquisition cost + selling cost.

"9A Tax form" for Finnish tax reporting now correctly shows two decimals also "selling price", instead of showing this figure without decimals.

Summary section in the client printout for Norwegian tax report for equities now properly fits large numbers with all decimals - this was achieved by making the font on the report smaller, allowing it to have enough space to fit large numbers with all decimals.

You can now define per transaction type whether or not supporting orders are used when bulking trade orders. Supporting orders may cause practical problems with certain kinds of trading setups with trade-amount-based orders, and this new configuration allows you to disable the use of supporting orders for certain transaction types.

Validation logic within trade order bulking has been improved: performance of bulk trade orders' validation logic has been improved to prevent duplicate bulks and to handle concurrent modification errors, and the validation logic has been made more bulletproof.

Performance of Bulk trade orders has been improved in terms of saving transactions simultaneously instead of one-by-one, avoiding saving data unnecessarily multiple times, and not loading unnecessary data when it is not needed.

Validate orders process now allows you to adjust trades downward for partial approval. This allows you to handle partial approvals, i.e. adjusting a buy or withdrawal down to match available cash, or adjusting a sell down to match remaining units.

New trading connector to send fund orders to a trading platform with ISO 20022 standard. This trading connector is using the new "Trading microservice" and a process to send trade orders to be processed by the microservice.

New trading connector to use FA as the trading platform that receives fund orders and sends out execution information with ISO 20022 standard. This trading connector is using the new "Trading microservice" and a process to send trade orders to be processed by the microservice.

Infront trading connector has been externalized from FA Back, and is now available to be installed as an extension through FA AppStore as most of other trading connectors.

Trading connector to Nasdaq NFM is changed now to work against Allfunds, where the service has been moved.

Fundsettle trading connector now formats even large numbers correctly in the generated files, instead of incorrectly converting large figures to scientific notation such as 1.89E7.

MFEX trading connector now works properly also after the technical changes done on MFEX' side on June 1st, 2020.

Fixed an issue in Infront trading connector that resulted in the connector failing to start every night. In addition, Infront trading connector no longer produces unnecessary error messages on the logs.

You can now use new and improved standard queries for diagnosing the system: a new query allows you to find duplicate ext IDs from transactions within the same portfolio, and "Negative accounts today" and "Negative positions today" queries now include information about portfolio ID, security code, and account number and name.

Scheduling manager no longer crashes when you try to open details of a process which is currently in progress.

Design-based importer now allows you to override values before they go to the UI. For example, you can when creating new objects via design-based importer, the system automatically generates a new identifier (UUID) for it,and you can now have a UI where this default value is overridden by user's input.