We’re excited to share a preview of the upcoming release, which will be officially published later this week. Below are the key enhancements and features to look forward to:

Compliance - The Compliance Evaluation History report (CO-EVAL-HIST) has been updated with the following enhancements.

The ‘Date Range' parameter has been renamed to 'Compliance Execution Dates'. This refers to the date when the action is carried out. For example, if you run the compliance evaluation for different evaluation dates but run it as at today, the report with an execution date of today will include results from all previous evaluation dates. The execution date essentially refers to the ‘run date’ for the report.

A new parameter has been added for the ‘Evaluation Date’ range. This returns results specific to that evaluation date, regardless of when these compliance rules were executed.

We’ve added a flag for 'Latest Results Only'. When selected, the report returns the latest results for each portfolio and rule or rule set combination, ordered by Evaluation Date and then by Execution Date.

A new compliance datasource, fn_Compliance_ClientPortfolioRuleSetDefaults, has been created. This returns the portfolio defaults for pre or post trade compliance rule sets and has the ability to filter for portfolios not associated with any rule set default.

We’ve also enhanced the ability to explode holdings via internal look through using FPM’s actual ‘Cash’ Instruments. Previously, compliance rules would consolidate all ‘Cash’ holdings from different issuers under one issuer, regardless of the underlying issuer. Now, ‘Cash’ holdings from different issuers are not consolidated, allowing the compliance evaluation to run correctly using FPM’s actual cash instruments. To achieve this, FPM will link portfolios to bank accounts, and the issuer will be based on the Institution field of the bank account, not the compliance tab of the external instrument.

If compliance is run using exploded internal look through holdings, and an underlying portfolio is linked to a different issuer than the parent portfolio’s cash instrument, then the exploded holdings will not consolidate the Cash Instruments.

The same logic will apply when rolling up a child portfolio into a parent portfolio where cash holdings with different issuers will not be consolidated into a single cash holding.

This logic will also be applicable to the holdings enquiry.

Lastly, Compliance Evaluations are now collapsible, providing a larger view of the screen.

Front Office - Additional validation was incorporated into the short position validator to ignore buy orders and verify whether the sum of all sell orders will cause the position to go short. This is managed by the parameter FrontOffice/Orders/PerformSellsOnlyShortPositionValidation, which defaults to applying this validation. If the parameter is set to false, the check is not performed.

Grid Layouts - We’ve added a new 'Layouts' group to the navigation bar of all standard forms, making it easier to manage layouts directly without using the popup menu.

You are now able to select a layout from the drop-down list to apply it to the grid. If the layout is applied or saved via the popup menu, the drop-down list is automatically updated.

Look Through – We’ve enhanced the holdings enquiry to correctly retrieve both directly held instruments and internal and external look through portfolio holdings when you specify the instrument and leave the portfolio parameter blank. Previously, the instrument filter on the holdings enquiry only returned directly held instruments.

Modelling - The ability to save modelling views with a code and name already exists, aiding managers in identifying their specific sessions. We’ve expanded this functionality to include the recording of ‘Created by’ and ‘Created on’ fields for saved modelling sessions in the view list. When saving a new view, the code and name are defaulted to the current user and modelling type, but users can edit these before saving.

Additionally, we’ve added new filters to the Modelling view list, including Portfolios, Instruments, Benchmark and Created By.

Furthermore, cash has been incorporated into the Target % and Proposed Weight % in the modelling operations, ensuring that changes in instrument targets have corresponding effects on the cash balance. This effect is applied per currency, meaning changes to an instrument’s target result in opposite changes in the target of the corresponding currency line item.

Multi-Manager Pricing - We’ve enhanced the multi-manager unit movement import block with additional validation. Now, transactions without a requested price and value will result in failure. This helps prevent issues where orders are not allocated in the Pricing Process.

Override Prices Module - As part of the Multi-Tenant Front Office feature, Fundamental serves as a Trade Order Management System for Portfolio Managers. These managers frequently access live price feeds for portfolio analysis. To support their analysis, Portfolio Managers need to periodically update prices. To facilitate this, we've introduced an option to flag prices as 'Override Price Sets'. With this feature, no price history is retained, and only one price per instrument is used regardless of date. This price set operates on a flush and replace basis, meaning new prices replace existing ones without maintaining a price history.

When an override price set is utilised, it impacts valuations in several ways. Firstly, if an override price for an instrument exists it will be used irrespective of the capture date. In cases where no override price is available, the system defaults to the default prices set. Exchange rates are sourced exclusively from the system default price set.

Changes to override prices are reflected in the audit tables if instrument price audits are enabled. Override Price sets can be chosen for enquiries and reports but not for processing operations. Additionally, a new import for Override Prices has been added.

PO-MATPROF Report - We’ve updated the report to include a column displaying the weighted time to maturity. Additionally, users can now split maturity profiles of less than 1 year into monthly bands. You can also specify maturity bands to display as yearly, two-year periods, or three-year periods.

Portfolio Static - You are now able to specify the Unexcor Code on the Scrip and Exchange Codes tab of the portfolio setup. Additionally, users can import this field.

For a comprehensive list of changes included in this release (2024.2.2), please refer to the release notes website.