Standard Solution March 2025 - Release notes
Released: April 1st, 2025
The Standard Solution March 2025 release introduces a number of fixes.
Other improvements
External reporting
Updated the SIRA reporting process to ensure the Create XML report option is enabled by default, aligning with the mandatory XML format requirement effective from December.
Fixes
Communications
Added support for retrieving portfolio external IDs such as OCR number in email templates used in Send messages process. The missing allows dynamic keys like %%portfolio.extPortfolioIdList.OCR%% to be correctly populated in emails.
Compliance
Fixed an issue in the trade order validation when the “Use cash and units from unsettled transactions to cover for buys and sells” setting was enabled and the initial position for a security was zero. Previously, validation didn't account for future-settling transactions if there were no prior transactions for the security.The issue was resolved by correctly initializing the position for unsettled transactions, ensuring that sell orders are approved when there are enough units settling from a future buy transaction.
Fixed an issue in the trade order validation when “Use cash and units from unsettled transactions to cover for buys and sells” was enabled. Unsettled buy transactions were incorrectly counted twice. As a result, the orders were approved when they should have been rejected due to insufficient units.
Fixed an issue in the trade order validation when “Use cash and units from unsettled transactions to cover for buys and sells” is enabled. In specific cases where the unsettled buy amount was larger than the unsettled sell amount, the validation incorrectly rejected orders due to insufficient units. The calculation now correctly includes unsettled buy transactions in the expected position.
External reporting
Fixed an issue where counterparty information for Option and Future security types was sometimes missing in reports. The solution replaces the restrictive SQL query with FA Back’s service methods to ensure all relevant opening transactions are considered.
Fixed an issue where profiles with identical names caused incorrect content display in the user interface. Share class-related SIRA/PEF settings have now been moved to the existing Share class settings tab, Reporting subtab. Learn more: Configure and create SIRA and PEF reports.
Added support for marking cash account balances as collateral in SIRA reporting. Accounts categorized as "Collateral account" now influence the collateralRequirementForDerivatives field based on their balance. Positive balances are reported with instrument classification code 72 and marked as collateral (C), while negative balances use code 76 and are not marked as collateral (N). If no collateral accounts exist, collateral fields are omitted. Learn more: Configure and create SIRA and PEF reports.
Added a new “Include unofficial NAVs” configuration for the SIRA report. When enabled, it allows the use of unofficial NAVs if no officially accepted NAV is available for the reporting date. Learn more: Configure and create SIRA and PEF reports.
SIRA and PEF reporting were incorrectly configured with ADD as the unit certificate transaction type, potentially causing regular ADD transactions (for example, from transfers) to be treated as pledges. Now, we updated the configuration to use the UC transaction type instead.
Fixed an issue where Option and Future security types were generating duplicate rows in SIRA reporting. The filtering logic was updated to align with the process configuration used for option rows, preventing redundant entries.
Fixed an issue in a database variable that caused SIRA reporting to fail when there were many subscriptions or redemptions in the report.
Fixed an issue in SIRA reporting where counterparty information for Options was missing due to an incorrect SQL query. The query has been corrected to properly fetch counterparty details, preventing errors in the report generation.
Updated the SEB subscription and redemption report to match the decimal precision of the fund's official unit price and amount, instead of a fixed two-decimal format, ensuring compliance with SEB's expectations.
Trading connector
Fixed an issue where empty tags were causing an exception during status update processing in trading application.
Utilities
The scheduled processes now runs correctly against a saved Contacts view with portfolio group as a filter.