Standard Solution June 2025 - Release notes

Added a new SIRA report generation parameter – Position date for liability reporting. You can now choose if liabilities are reported based on position data from the reporting date (default) or from the previous day. Using the previous day's position data helps align the liabilities side with the NAV calculation data, especially if you have automatic order execution and execute orders on the NAV calculation date. The new parameter can be found under Tools → Administer → SIRA and PEF reporting. Learn more: Configure and create SIRA and PEF reports.

Fixed an issue where scheduled Coupons and expirations process created duplicate expiration corporate actions and transactions. This was caused by a mismatch in how expiration dates were adjusted using holiday calendars, leading the system to not recognize existing actions.

Fixed an issue in the scheduled Create coupon and expirations process where coupon payments weren't run if the Days back value was set to 1. The problem was caused by time-based logic that excluded events occurring earlier on the same day. The process now correctly identifies and includes coupon payments regardless of the time of day.

Fixed an issue in the SEB Life reporting where the portfolio ID appeared in two separate columns of the holdings file.

Resolved a validation issue in the SIRA report where duplicate entries could occur for instruments 71 and 73 due to overlapping data. Each entry now includes a unique internal identification code to ensure compliance with reporting rules and prevent conflicts.

SIRA report for instrument code 71 (receivables that are security-based) now correctly reflects the nominal value currency, rather than defaulting to EUR. Now, the report features the underlying security’s currency and splits items by nominalValueCurrency when applicable (for example, one item per USD, NOK).

Corrected an issue where the counterparty’s country code was missing from the SIRA report for options. This was due to a small typo in the system, which has now been fixed to ensure the correct information is included.

Resolved an issue where scheduled process runs incorrectly selected configuration sets with similar keys, leading to unintended mappings (for example, selecting mapping.bloomberg.equity instead of update.bloomberg) used.