| Changelog

New options were added to the reporting component Profit & Loss (detailed) mainly to allow more control on the excluded fees visualization.

 

1. Invert flows values for summability: when selected, the neutral flows and/or excluded fees displayed in the component are inverted. In this way it is possible to sum the "Change in value + cash deposits/withdrawals + securities deposits/withdrawals + ev. other neutral flows + excluded fees" = "Portfolio P&L".
   It is now possible to select the option FeeFlowsOnly to invert the excluded fees only.
2. Excluded fees grouping: independently from the "Show Split Performance Value Type" option (differently from before), it is now possible to select how the excluded fees are displayed in the main panel.
   1. SingleGroup: shows the excluded fees grouped into a single row
   2. FeeGroups: shows the excluded fees grouped by pre-defined fee type groups (displays rows: ManagementFees, PerformanceFees, OperationFees, CustodianFees, Taxes and WithholdingTaxes)
   3. FeeTypes: shows the detailed excluded fees by fee types (displays rows: ManagementFee, PerformanceFee, BankFee, ServiceFee, InsuranceFee, FiduciaryFee, ProductFee, OperationFee, Taxes, WithholdingTax)
3. Show excluded fees percentage: when selected, shows the percentage of the excluded fees calculated as the weighted performance change from the Net performance value type to the selected Gross performance value type.
   For example, if the net performance is 10% and the gross performance is 15%, and there are 2 groups of fees with values 5'000 and 7'000, their respective percentages would be:
   (15% - 10%) * 5'000 / (5'000 + 7'000) = 2.08%
   and
   (15% - 10%) * 7'000 / (5'000 + 7'000) = 2.92%
   so that 10% + 2.08% + 2.92% = 15%
4. Show deposits/withdrawals percentage: when selected, shows the percentage of the deposits/withdrawals entries calculated against the average portfolio value in the period.

 

Examples:

Invert FeeFlowsOnly, SingleGroup for excluded fees, show percentages of excluded fees and deposits/withdrawals:

Invert FeeFlowsOnly, FeeTypes for excluded fees, show percentages of excluded fees:

It's now possible to import mandate or nominative documents in bulk by using the new Documents import excel file:

As default, document rows are validated before importing. In case of errors, a new Excel file is generated containing the failing rows, including error details.

The Issuer Country column in Positions previously displayed the instrument’s domicile rather than the actual country of the issuer. This has now been corrected — the Domicile and Issuer Country columns each display their proper values.

Exports which may take a while to generate the result now use the download widget.
This is to avoid browsers timing out on long running requests.

For example, exporting a finance report:

Will now export the file through the download widget:

 

This was applied to the following exports:

• Finance module - all exports to Excel and PDF
• Global dashboard - positions search
• Advanced queries
• Queries

 

Crypto currency ZCHF is now available

It's now possible to customize report options specifically for the investment proposal.

A new configuration window is available in the REPORT GENERATION tab:

In Portfolio - Configuration widget, the Tags field was showing an empty versioning history. This was fixed:

Added support for the new additionalDetails field when submitting a trade

Rebalancing speed was improved, with special focus on group rebalancing, i.e. when a large number of portfolios are rebalanced at the same time.

For example, rebalancing 200 medium-sized portfolios was taking roughly 15 minutes.
With the improvements, also depending on the machine and available cores, this was reduced to roughly 2 minutes (or less) - i.e. roughly 80% faster.

Loading of the rebalancing group, which is also part of the rebalancing flow, was also improved (roughly 75% faster).

 

Rebalancing speed was improved, with special focus on group rebalancing, i.e. when a large number of portfolios are rebalanced at the same time.

For example, rebalancing 200 medium-sized portfolios was taking roughly 15 minutes.
With the improvements, also depending on the machine and available cores, this was reduced to roughly 2 minutes (or less) - i.e. roughly 80% faster.

Loading of the rebalancing group, which is also part of the rebalancing flow, was also improved (roughly 75% faster).

 

The report component "Detailed Contribution Grid" has been enhanced to show (optionally) also the Category Performance (i.e. the absolute category return, as calculated in the Attribution calculation methodologies).

This viewing option can be enabled in the Reporting:

Since this component shows the values based on the selected Performance Value Type, also the Attribution UI has been enhanced to include also the "Performance Value Type" selection:

We reviewed all translations and enhanced them for the existing languages:

• English
• German
• Italian

Furthermore, we added translations for

• Dutch
• French

As the enhanced translations might differ quite a lot from the previous ones and thus impact the usability of the system and the client reporting, these are not enabled by default.

To enable the new translations, choose them from the personal user settings dialog:

IMPORTANT NOTES:

• Before switching permanently to the new translations, we need to copy all language overrides and reporting dictionaries. Please contact us.
• Next year we will deprecated and subsequently remove the old translations, so we kindly ask you to plan switching to the new version.

Counter Party classification has been updated to include cash related instruments. For most instruments, the institution linked is the Issuer institution configured from Financial Data.

For cash positions, there is usually no configured issuer, and the risk should be associated to the Custodian holding the cash. 

• A new field "Institution" has been added in Configurations->Custodians view.
• Once configured, Counter Party classification will assign cash positions to the configured Institution for the Custodian configured on the portfolio mandate instead of "Other" category.
• This also affects InstitutionThresholdRestriction as cash will be aggregated with the custodian institution.

The instrument domicile field, which already existed but was not visible, is now visible in the instrument form and can be edited. Usually, it is given by the data provider.
The domicile of the instrument is the jurisdiction where the instrument is registered or listed, often tied to where it trades or is regulated.
The domicile may be used to automatically classify the instrument by region.

Note that it can differ from the issuer's country. For example: a bond issued by a Swiss company (issuer country = Switzerland) could be domiciled in Luxembourg if it's listed and registered there.

The instrument domicile is also available as column in the "Positions" widget:

The performance attribution calculation process was greatly improved in terms of speed.
With the improvements, the calculation process is roughly 10 times faster than before. 
This can vary depending on the portfolio/consolidated portfolio being calculated.

Performance improvements

• Reduced load times for the Positions grid when opening a portfolio. The improvement is mostly noticeable for users which have limited authorizations (e.g. users that can see only their own portfolios)
• Improved loading times for Portfolios searches (in Portfolios dashboard - favorites section and advanced search)
• Performance gains of up to 30–40% were observed during profiling. Please note that actual performance improvements may vary depending on the specific data and configuration of your instance.

 

In the Exposure (Table) and Exposure (Bar) widgets it is now possible to select any portfolio as reference portfolio.

When leaving the selection empty, it will default to the reference portfolio configured on the portfolio:

Otherwise, any portfolio can be selected:

 

The same option is available also in the corresponding reporting components:

Expanding a universe into the matching instruments in the system has been improved in terms of speed, especially for the case where a lot (>10k) of filters specifying ISINs/valors are defined.

Additionally, importing an existing universe will now clear the list of rules related to the same date being imported, if any.

The Advanced Query Executor Job has been enhanced with the following feature:

Both the Override Output File Name and Override Email Subject fields now support our template language for dynamic content generation.

Example – Override Output File Name (template):

{queryName}_${from}-${to}

Results in:
All-Mandates-v3_2025-01-01-2025-03-31

The same syntax applies to the Override Email Subject (template).

In the Mandates - Correspondence Details widget, the following fields were missing in the "Copy to" section, and have been added:

• Heading (override)
• Full heading (override)

A new report template type can be created in the reporting module: PortfolioLossReporting.

A new DtD* column has been added to the Portfolio Dashboard.
If the date is today, DtD* shows yesterday’s DtD value (t-1), as today’s performance is usually 0% before the valuations are generated at night.
For all other dates, DtD* matches the regular DtD.
This provides a more meaningful day-over-day view during the trading day.

Added a new optional column named "[underscore]Main[underscore]" for explicitly defining the main category for each classification when importing the excel file with the static classifications for instruments

In the All Mandates queries (v1, v2 and v3) the following columns have been changed to show both the creation date and modification date of the respective questionnaire:

• "A.H. Last KYC"
• "A.H. Last I. Profile"
• "B.O. Last KYC"
• "B.O. Last I. Profile"

Will now show:

• A.H. Last KYC (creation) -> the creation date of the KYC (what was previously exported as 'Last KYC')

• A.H. Last KYC (modification) -> the modification date of the last KYC

• A.H. Last I. Profile (creation) -> the creation date of the IP

• A.H. Last I. Profile (modification) -> the modification date of the last IP

• B.O. Last KYC (creation)

• B.O. Last KYC (modification)

• B.O. Last I. Profile (creation)

• B.O. Last I. Profile (modification)

Before, not all factor shocks have been reflected in the scenario calculations. Furthermore, in rare cases, the used asset time series data was missing the first value.
These bugs have been fixed now.

The reconciliation logic in Assetmax has been extended to better handle reversal transactions received from custodians.

The system now supports the following scenarios when a reversal operation is received:

---

1. Automatic Reconciliation – Reversal Already Exists in Assetmax

If the reversal already exists in Assetmax (i.e., the original operation has already been reversed), the system treats it as a perfect match — even if there are minor differences — and automatically reconciles the two operations without overriding any data in Assetmax.

---

2. Create Reversal in Assetmax – Reversal Not Yet Booked

If the reversal is not yet booked in Assetmax, the system attempts to identify the original operation and then create and reconcile a new reversal. This includes the following sub-cases:

• A. Perfect Match Found

  • The original operation is identified as a perfect match.
  • A reversal is created in Assetmax (replicating the “Reverse” action) and is automatically reconciled with the custodian's reversal.

• B. No Perfect Match Found

  • The original operation must be manually identified.

  • A UI (similar to Lead vs Custody Operations) will be shown, allowing users to adjust filters and locate the original transaction.

  • Once identified, the user can:

    • Create a reversal in Assetmax and reconcile it
      

    • Or If a reversal operation already exists in Assetmax but wasn't matched automatically, reconcile it manually.
      

• C. Multiple Operations Selected

  • For operations that are perfect matches (as in A), reversals are automatically created and reconciled.
  • For unmatched items, a warning is shown, and users are prompted to resolve them manually.

---

Note:
Matching behavior is determined by the Custody Matching Rules Configuration. Depending on those settings, operations that aren't exact matches may still qualify as matches.

Rebalancing a portfolio by filtering on a category of a different classification with respect to the reference portfolio's classification was not working for model positions which were not already present in the mandate portfolio.

This case has been fixed and model positions which are not present in the mandate portfolio are filtered according to their categorization in the selected classification. If they are part of the selected category, they will be bought/sold according to the reference portfolio weights the same way as for instruments which are already present in the mandate portfolio.

• All Mandates v3: now including issued invoices, and a configurable reference currency
• All Operations for Statistics: returns operation information including profits, fees, value, custodian, ... to create statistics and analytics (e.g. Pivot Tables)
• AuMs delta over a period (v2): made reference currency configurable
• All Asset Allocations: added look through option, weight vs exposure fields
• All Nominatives: separate fields for First name, Last name

In all the dashboards, selecting a widget that is already present will no longer open a new widget of that type but will re-open the existing one.
By clicking on the plus "+" icon, a new widget will be opened instead.

Filtering on some columns which were rendering values which differed from the column's key was fixed.

For example, the Debit and Credit accounts under Finance - Management Fee could not be correctly filtered based on the displayed text.
This is now correct:

Other widgets and the corresponding columns where this was fixed:

• Compliance - Audit Events:
  • Changes column
• Compliance - High Risk Persons:
  • Nominative Status column
• Portfolios - Flows:
  • Status column
  • Operation type column
  • Flow type column
  • Main column
• ...

In some rare cases it could have happened that an error occurs when saving mandate information.
This has been fixed now.

When Portfolio Loss Report is created, a Simple Task on Mandate is also created to handle it.
It is now better visualised on all Portfolio Loss Reporting views, in Compliance, Portfolio and Main Dashboard.
New table columns are added showing the task’s status, modifying user and modification time:

The column "Entry ID" was added, which shows the ID of the flow of fund entry:

The column was added to the following widgets:

• Flow of Funds - Transactions{}
• Compliance - Cash Transactions (AMLA)
• Global Dashboard - Cash Transactions (AMLA)

This allows to filter audit events regarding a specific entry when loading the Flow of Funds audit events under Compliance - Audit Events widget:

In some cases the creation of index instruments resulted in an error because the data provider uses points instead of the currency.
This problem has been fixed now, and index instruments can be created also in such cases.

The Average Invested Capital (AIC) was not being calculated when importing historical data.
Now this has been fixed and the AIC is calculated accordingly.

When calculating the Money-Weighted Return (MWR) for a portfolio over a period (e.g., 01.01.2025–08.05.2025), special handling is required if the portfolio's initial data load starts on the first day of the period (in this case, 01.01.2025), meaning there is no valuation for the previous day (31.12.2024).

During the calculation there was an inconsistency: In normal cases (where a real valuation exists for the day before), we treat cash flows as end-of-day. But in this special case, we incorrectly treated the cash flow on 01.01.2025 as beginning-of-day, which resulted in an inaccurate performance for that day.

This issue has now been fixed. The initial period is handled consistently with other periods, ensuring correct MWR calculation.

Additionally, we fixed another issue affecting periods that do have a real valuation on the previous day (e.g., 31.12.2024). While we correctly excluded neutral flows from that initial valuation (since we only need the end-of-day value), we were including the fees values. These are now also excluded, so the calculation is correct. This issue impacts only the MWR gross performances when fees are present on the last day of the previous period

Please note that Time-Weighted performance calculation is **NOT **affected.

Tops/Flops widgets in Portfolios dashboard were enhanced:

1. Additional filters were added to all 4 "Tops/Flops" widgets:
Aggregate positions: whether to aggregate positions in case multiple positions for the same instrument exist. This applies to consolidated portfolios.

2. Export to Excel button was added for Tops/Flops - Contribution and Tops/Flops - Performance table widgets.

 

In the standard query Name Matching Hits, new options have been added to include changes history of name matching hits:

When the new options are unchecked, as before, each name matching hit with a decision will be listed:

By checking the Include all changes history option, each name matching hit row will be expanded into multiple rows, each showing the versioned changes of each update:

By checking the Include last history change only option, only the last change will be listed for each hit (so each hit will be shown once):

 

In some rare cases it could have happened that an error occurs when saving mandate information.
This has been fixed now.

Improved (World Check / SGR) search in case of entries containing characters with umlaut. It might find more hits compared to the previous version.

Clearer Display of Pending Orders

• In the Positions view, you’ll now see a "P" flag in the Flags column to indicate positions with pending orders. The pending amount is also shown.
  

• When adding a Trade, you can specify is this is a pending orders like a limit order.
  

• In the Transactions table, two new columns help clarify pending orders:

  • "Pending order (created as)" shows if the transaction was originally entered as a pending order.
  • "Pending order (currently)" shows if the transaction is still considered pending (pending orders don't affect your portfolio balance).
    

• You can now create pending orders via the Group transaction feature.

  

• In the Balance view, pending orders are shown in grey, with the same two new columns to help you track their status.
  

Currently there are two Restrictions types which behave like the Text Warning restriction (i.e. at every pre-trade check the popup is shown):

• Warning
  
• Basic Information Investment Product
  

To ensure that such restrictions breaches are also shown in Group Transactions every time new transactions are created, such restrictions will always generate a new breach when checked.

This means that if a breach exists already and it is currently in statuses Closed or Justified it will be re-opened.

Since these restrictions types are meant to be used for Pre-Trade checks please note that when creating new restrictions by default it will only select the Pre-Trade options:

In the following Advanced Queries the Mandate/Nominative tags have been added.

• "All Mandates" and "All Mandates (Beta)"
  • New columns:
    • "A.H. Tags"
    • "B.O. Tags"
      
• "Mandate Entity Link Export"
  • New columns:
    • "Mandate Tags"
    • "Nominative Tags"
      

A new KPI Widget was added on the Main Dashboard, showing the number of Portfolio Loss Reports generated by the Portfolio Loss Reporting Job that have an open Task related to them:

The template for Call Deposit instrument ident had been improved. Now it's possible also to select custodyInternalCode (if there are more codes, only the first one will be considered)

It can be used in call deposit template adding this text in the preferred position in property assetmax.instrument.template.calldeposit.name

${if custodyInternalCodeExists}${custodyInternalCode}${end}

Example:
assetmax.instrument.template.calldeposit.name = "Call 48h ${interestRate}% ${currency} ${dto.issueDate} ${if custodyInternalCodeExists}${custodyInternalCode}${end} ${if fiduciary}Fiduc. ${issuer}${end}"

These new columns had been added in

Positions widget:

• TX W (Loans Excluded)

Group Transactions widget:

• Cash - Before TX - Weight (ex Loans)
• Cash - After TX - Weight a/TX (ex Loans)
• Main Instrument - Before TX - Weight (ex Loans)
• Main Instrument - After TX - Weight a/TX (ex Loans)
• Main Instrument - Exposure a/TX - Exposure main leg % a/TX (ex Loans)
• Main Instrument - Exposure a/TX - Exposure cash leg % a/TX (ex Loans){}
• Switch Instrument - Before TX - Weight (ex Loans)
• Switch Instrument - After TX - Weight a/TX (ex Loans)

Previously, if a Portfolio Category was missing a translation, the corresponding field in the Portfolio Category column appeared blank.

This has now been fixed. If the translation is missing we show the 'ident' of the dynamic enum. 

Example:

A Mandate is assigned a Portfolio Category.

That Portfolio Category is a dynamic enum without a translation.

In Portfolio Search, the Portfolio Category column used to appear empty.

Now, it displays the enum’s ident instead of leaving the field blank.

Before, the Risk widget was sometimes empty for Risk Model. Now, there are numbers shown again.

The exposure history is, optionally, calculated during the day close operations job for the specific configured classifications. The data is then used by the Exposure History Chart widget to show the portfolio development in time.

An optimization has been implemented to reduce the disk space used by the calculated exposure history.
Depending on the data and calculated classifications, disk space usage is reduced by approximately 75%.

When loading a mandate, some dynamic information about management/performance fees was also loaded for the mandate, which could cause the loading of the mandate to be very slow.

Since these fields were, potentially, available only in the Mandate Info widget in the Portfolios dashboard, they are loaded only in that case.
In general, this may speed up loading of single mandates.

Before, the Risk widget was sometimes empty for Risk Model. Now, there are numbers shown again.

It is now possible to check how the realized P&L value is composed for the selected period with the new drilldown feature.

The new feature is available in the Portfolio and the Position Performance widgets, so it possible to check the value both at portfolio level and at position level.

Portfolio widget

1. the Portfolio widget was enhanced with the period type selector (including Custom period)
2. the Realized P&L (and the new, configurable, instrument type group realized P&L) value can be analyzed by checking the drilldown view, which shows the operations that caused realized P&L in the corresponding period:
   The drilldown view will show both:

• "since inception" realized P&L values, i.e. cost price since inception based, filtered for the selected period
• "period's" realized P&L values, i.e. based on the period's cost price (which corresponds to the P&L realized values of the selected period)

Position Performance widget
In the context menu which appears when right-clicking on a position will show the drilldown options:

The operations that caused realized P&L on the selected position will be listed, with the corresponding realized P&L values (Since Inception and period's):

It is also possible to check the drilldown on category level, which will include operations causing realized P&L for the positions in the selected category:

The Portfolio Loss Reporting table in Compliance and in portfolio view has been augmented with new columns:
Period type
Cumulation type
Last report date
Loss threshold
Value at start
Value at end
Perf. neutral flows
Perf. value type
Perf. methodology
Portfolio name
Portfolio ident
Mandate name

 

The Positions Search widget has been enhanced by adding a filter for Universes:

 

Please note:

• Since Universes can have historized versions, the reference date used to load that specific version is the selected "Valuation date".
• For example:
  • If we have the following history version of the Universe "Restricted ETFs":
  • 02.03.2025:
    
  • 10.03.2025:
    
  • By searching for positions of this Universe, by using as Valuation Date the 05.03.2025 will consider the instruments that were part of that universe on the 05.03 (in the example is just the "HSBC MSCI Rus USD" instruments
  • Instead, searching with Valuation Date = 10.03.2025 will consider the 2 instruments that were added later (in the example "In MSCI Wld USD-Ac" and "Invesco KBW Bank Fd")

 

 

A new view option for Profit & Loss is available: "Period-Adjusted Since Inception Realized/Unrealized P&L".

When analyzing portfolio profit & loss for a period like YTD, it is useful to assess both the total realized value of a position and its potential realization. By default, Assetmax displays realized and unrealized figures based on the selected period. For example, in a YTD analysis, it considers only gains or losses relative to the position’s price at the start of the period. However, when selling a position, the full amount is realized based on the original cost price since inception. This new option allows users to view total realized/unrealized gains since inception, rather than just the period-specific figures.

When this option is enabled, realized and unrealized P&L values will reflect gains and losses since inception but adjusted to align with the selected period. To account for the difference between period-specific and inception-based calculations, a new entry called "Period Adjustment" will be introduced.

For example, with this option enabled, the realized P&L for a YTD period will be calculated using the cost price since inception instead of the YTD cost price. Similarly, the unrealized P&L will show gains or losses relative to the cost price since inception rather than the beginning of the selected period.

Since the total P&L remains unchanged, the Period Adjustment entry will reflect the value needed to reconcile the differences between the standard period-based and the inception-based realized/unrealized P&L figures.

NOTES:

• This option is not available by default. Please contact consulting/support to enable it.
• Note: no portfolio recalculation is needed after enabling this option.

The option is currently available for the following widgets in the Portfolios dashboard:

• Position Performance:
  

• Portfolio:
  

 

As well as in the reporting component, Profit & Loss (Detailed):

It is possible to configure a set of instrument types for which 2 fields, corresponding to the total market plus FX P&L for realized and unrealized P&L, become available.

NOTE: a portfolio recalculation must be performed only for the dates for which this data needs to be available. There is no need for a full portfolio recalculation.

In the below examples, we configured the instrument types for options and futures.

These fields are available in the Portfolio dashboard:

• in the "Position Performance" widget:

• in the "Portfolio" widget:
  

And in the reporting in the "Profit & Loss (detailed)" report component. By enabling the corresponding option:

The 2 fields are shown:

The import of contact protocols has been enhanced with the possibility to import attachments in a subdirectory structure.

Enhanced Attachment Import: Added new import configuration AttachmentDirStructure.

• "Files" (default): existing behavior, attachments loaded by filenames.

AttachmentDir/
├── 2407217131911001-attachment1.pdf
├── 2407217131911001-attachment2.docx
└── 2407217131911002-attachment3.pdf 

• "Dirs" (new): attachments loaded from folders named by <reference> (matching “Old Id”).

AttachmentDir/
├── 2407217131911001/
│   ├── attachment1.pdf
│   └── attachment2.docx
└── 2407217131911002/
    └── attachment3.pdf

Minor Improvements (Usability & Error Messages): Improved import usability and readability of error messages.

Add parameters to Documents Expiration Check:

• Notify on task expiration
• Days before the deadline in which to send a notification

The process for sending task-created notifications has been modified.
Task created notification will be sent when:

1. New task is created manually
2. task is created in 'Documents Expiration Check' Job

Task created notification will NOT be sent when:

1. Tasks are imported
2. Running the 'Portfolio Loss Reporting Job'

Target Market Questionnaires are now available for instruments. There are two type of questionnaires:

1. EMT Target Market
2. MiFid Target Market

Questionnaire data is downloaded from Infront Core Data. If no data is available, the questionnaire will be empty; however, it can still be updated manually in either case using the 'Save' function.
The 'Update' function is used to retrieve or reset values to match those from Infront Core Data.

By default, this feature is disabled, please contact CRM/support to enable it.

Before, Security Delivery operations did not cause the unrealized P&L of the position to be realized. This has been corrected now and P&L will be realized by Security Delivery operations.

Already existing positions which are affected by this problem can be corrected by a day close.

New filtering options for Portfolio Loss Reporting Job, allowing for fine grained reporting.

Before the fix, the contract size of options and futures opened using Core Data API could be wrong. Now this issue is fixed.

Editing trade or value date of multiple lead operations should now trigger recalculation from the oldest possible date for portfolio.

The Profit & Loss (Detailed) report component has been improved, with enhanced support for consolidated portfolios and additional metrics.

• Consolidated portfolios with underlyings – Underlying portfolios are now visualized as additional columns when viewing a consolidated portfolio. (1)
• Portfolio volatility – A new option allows the visualization of portfolio volatility. (4)

 

New customization options:

• Show underlying portfolios – Enables the display of underlying portfolios alongside the consolidated one.
• Limit underlying portfolios – Groups smaller underlying portfolios together, showing only the largest ones. (2)
• Show portfolio name – If disabled, the portfolio name is displayed only for underlying portfolios. (3)
• Include risk metrics – Enables the inclusion of portfolio volatility in the report, available for both consolidated and standalone portfolios.
• Risk calculation type – Volatility is currently displayed using the Historical risk calculation method.

A new reporting component, Portfolio Risk Analysis, has been introduced. It extends the capabilities of the existing Ratio Analysis component, adding support for consolidated portfolios and additional enhancements.

• Consolidated Portfolios with Underlyings – When viewing a consolidated portfolio, users can now choose to visualize the consolidated portfolio alone, the consolidated portfolio together with its underlying portfolios, or the underlying portfolios alone. (1)
• Portfolio Performance – The report now includes portfolio performance visualization. (2)
• Average Invested Capital (AIC) – AIC is now available in the report, but only when using the Money Weighted performance methodology. (3)

A new reporting component, Portfolio Risk Analysis, has been introduced. It extends the capabilities of the existing Ratio Analysis component, adding support for consolidated portfolios and additional enhancements.

• Consolidated Portfolios with Underlyings – When viewing a consolidated portfolio, users can now choose to visualize the consolidated portfolio alone, the consolidated portfolio together with its underlying portfolios, or the underlying portfolios alone. (1)
• Portfolio Performance – The report now includes portfolio performance visualization. (2)
• Average Invested Capital (AIC) – AIC is now available in the report, but only when using the Money Weighted performance methodology. (3)

The Profit & Loss (detailed) component was enhanced with the option to group fees into a  single row for non-Net performance value types:

By checking the corresponding option (Show grouped fees), the excluded fees are shown as a single row instead of one row for each excluded fee group.
The grouped fees row will have a different label for each different performance value type.

When the option is unchecked, each fee group will be shown in its own row. Depending on the performance value type, a subset of fee rows will be shown.
For Gross performance value type, all fee rows will be shown:

The Profit & Loss (Detailed) report component has been improved, with enhanced support for consolidated portfolios and additional metrics.

• Consolidated portfolios with underlyings – Underlying portfolios are now visualized as additional columns when viewing a consolidated portfolio. (1)
• Portfolio volatility – A new option allows the visualization of portfolio volatility. (4)

New customization options:

• Show underlying portfolios – Enables the display of underlying portfolios alongside the consolidated one.
• Limit underlying portfolios – Groups smaller underlying portfolios together, showing only the largest ones. (2)
• Show portfolio name – If disabled, the portfolio name is displayed only for underlying portfolios. (3)
• Include risk metrics – Enables the inclusion of portfolio volatility in the report, available for both consolidated and standalone portfolios.
• Risk calculation type – Volatility is currently displayed using the Historical risk calculation method.

In the Mandates dashboard, the "Persons" widget has been enhanced with the addition of new columns which show details about each role (such as the Account Holder's Signature type, or Beneficial Owner %, etc). This helps in making it easier and faster to see such details without requiring to open the Mandate Role popup for every person.

As usual the columns can be configured so that only the needed ones can be shown.

Columns added:

• For all roles:
  • Valid from
  • Valid to
  • Notes
• Account Holder:
  • Signature type
  • Signature notes
• Power Of Attorney:
  • Signature type
  • Signature notes
• Beneficial Owner
  • BO %
• Control Holder
  • Type
• Signatory Power
  • Signature type

Improved the error message when attempting to delete a universe that is still in use. The message now includes detailed information about where the universe is being utilized.

New option "Cumulation type" has been added. It differs in how the date period for performance calculation is calculated.
Reset—if the performance threshold has been reached before, the performance calculation will be done from that previous report date.
Cumulative-the performance calculation is done from the start of the selected period, no matter if the threshold has been reached.
This means that if the threshold has been reached, new reports will be created every time the job runs, until the performance recovers.

From now the deposit of type Custom Deposit will be no longer automatically created.
When importing portfolio with positions which are not linked to deposit then there will be created a new Securities Deposit.
It will behave the same while creating new positions on portfolio which has no deposits in configuration.

Some of the task/contact protocols couldn't be deleted because of system error, this issue is fixed now.

In Document Management - Import from folder feature had issue with xml parser, this is now fixed.

The SwissRev job was not working correctly due to column name changes in SwissRev's data. This has now been fixed, with validation added to prevent future column name discrepancies.

In the Portfolios dashboard, the column "Account identifier for trading interface" was added in the portfolios search result grid:

Issue with the 'Risikoperson (nom_risk_individual)' column is fixed.

Before the fix, using the Alt+Click functionality to copy text fields could result in the text being incorrectly parsed as a number, potentially modifying the original content (e.g., removing leading zeros or approximating long numbers). This issue has now been resolved, ensuring that the text is copied accurately without unintended modifications.

In the Reconciliation dashboard, Transactions widget, it is possible to show and edit portfolio operation flows:

Updating flows this way will now prompt the user to either mark or perform the portfolio recalculation from the operation's trade date:

Marking the portfolio to be recalculated will cause the portfolio to be recalculated during the nightly jobs.
Please note: until the "day close job" has not been executed, the portfolio positions will not show the updated amounts.

Before this fix, updating flows this way was not marking portfolios to be recalculated at all, which could cause inconsistencies.

Support for agio/disagio flow has been added.
Agio/disagio is considered as a fee with the difference that it can be both negative (a cost) or positive (reduce of cost).
A specific agio/disagio fee group has been added, where agio/disagio flows are categorized in. By default, this fee group is disabled and agio/disagio flows will fall into the operations fee group. Please contact your CRM/support to enable the agio/disagio fee group.

Operations will show the agio/disagio values if the corresponding custodian bank delivers this flow.
If the agio/disagio fee group is disabled, the changes end there.

When the agio/disagio fee group is enabled:

• the fee group is shown in the UI and reporting cost widgets. E.g.:
  
• Positions and portfolio profit and loss will have the corresponding field filled:
  • Portfolio:
    
  • Positions:
    
• Profit and loss report components will show the corresponding field. For example, the Detailed P&L component:
  

In the standard query "AuMs delta over a period", the In/Out-flows and other performance neutral flows are now being converted to CHF with the correct FX rate of the previous day instead of the FX rate of the day.

This makes these values consistent throughout Assetmax.

The report component "Cumulated P&L/Performance" grid was enhanced with the following options:

• Max. number of items: if defined, shows only the first, most recent, N number of entries. This behaves similarly to the view period options, where only the entries within the specified view period are shown.
• Always include period first entry: if checked, independently from the selected view period, the first entry of the data period will be shown. When used in conjunction with the Max. number of items, the first entry will always take precedence (i.e. configuring Max. number of items = 1 will show the first entry only).

For example, it is possible to configure the component as follows:

1. All Entries: no view period, no max. number of entries, so start entry is also naturally visible.
2. Max. 8 entries, always including the period's first entry. Useful when the grid needs to fit in a specific height.
3. View period MTD which, based on the data periodicity, shows 3 entries in this case, with the first entry always included. Similarly to example 2., useful when the grid needs to fit in a specific height.

We have introduced a new feature that enables the creation of restrictions using customizable logic, similar to Advanced Queries. This allows for implementing tailored logic upon request and plugging it into the restriction.

Before the fix, email addresses were not displayed in the "E-mails for mailing" field within the "Details" window. Now, this issue is resolved: all relevant email addresses are correctly shown in the field.

Before the fix, it could happen that the value date was missing in the generated bank invoices if the user didn’t change the date from the default one provided. Now, this issue is resolved: the value date is consistently included in all generated bank invoices, regardless of whether the user modifies the default date or not.

New crypto currency that has been added:

OND

With the new FX Derivatives calculation enabled, there was an issue when forwards were part of content portfolios, expanded with the look through option.

The forwards were valued against the opposite currency, causing differences in the position values and the total portfolio value when the look through option was enabled.

This has been fixed.
No recalculation of portfolios is needed.

Before the fix, mandate types on the Main Dashboard were displayed in their default names rather than showing their appropriate translations. This issue has now been fixed, and the correct translations are now properly displayed.

A new component type has been added: Risk Contribution Grid.
Expected Shortfall (CVaR)

The component can be configured to include categories or not, or to show only categories.
Total row can be switched off.
Classification can be used for filtering.
Additional Derivatives or FX Hedge rows can be also inserted.

When creating an order and selecting "Money" as amount type, it is now possible to select the desired currency. By default, it is set to the portfolio currency.

Additionally, an issue was fixed which caused issues with improper amount while selecting the "Money" amount type without currency while editing simulated transaction.

• Added support for selecting the Tax Fx type alongside the Tax Fx date when updating ROA/Tax dates.
  
• Made the Tax Fx type a dynamic enum to allow for easier addition of new types in the future.
  

When using the Notification Service and Event Recorder for receiving notifications about fields changes (e.g. specific KYC fields changes for a nominative, or a specific mandate field) the notification itself will show the identification of the entity that was modified.

By default we were showing for Mandate the anonymized ident field (typically named 'Mandate Nr.'), and for Nominatives the internal id or the person name (if the vault was unlocked).

With this change a configuration has been added to be able to always use the internal id of the entities (and avoid having in the notification itself the person name). By default this setting is only enabled for nominatives (meaning we will only show the internal id for nominatives).

 

Please contact our Support or your CRM if you'd like this configuration changed.

Name was missing in the addresses table, now it has been fixed.

New crypto currencies that were added:

• APE
• ICP

In the Consolidation Summary report component, loading previous years values was already possible, but only the AuM value was available.

Now, all fields available for the valuation date are also available for the "previous years" columns.

For example, one could show the cumulated P&L of each underlying and the P&L of the previous 2 years:

Two new columns `Mandate nr.` and `Internal ID` have been added to widgets:

• Products
• Generic Revenue
• Federal Stamp
• Bank commission sharing
• Intermediaries
• Mgt / Transfer
• Operations Retro
• ROA

By default these columns will not be visible.

The calculation of Money Weighted performance now extracts also the Average invested capital value.
The average invested capital is available in the "Performance (Table)" widget:

And in the following report components (optionally):

• Profit & Loss (detailed)
  
• Consolidation summary
  

To view this value for past reference dates, please note that a portfolio recalculation is required for the specific reference date you wish to see.

In the reporting, added an option to the Dynamic Performance chart to show the cumulated performance in a dedicated column:

This applies, optionally, to the "data periodicity" performances of the main portfolio and/or to the additional portfolios configured on the chart.
Note: the date axis must be set to "categorized" for the dedicated column to show correctly.

Furthermore, options to define the series type (line, scatter, column) have been added.

1. Show the cumulated performance for the data periodicity (Yearly, in this case) performance of the main portfolio in the dedicated column.
2. Show the cumulated performance for the data periodicity performance of the additional portfolios in the dedicated column.
3. The series type definition for the different possible series. Possible values: column, line, scatter, any other string value which refers to a series type.

In the Group Transactions widget, when closing a position (by using the "substitute with" or with the standard target percentages) the behavior has been fixed to ensure that rounding will not be applied. Please note that this concerns only the closing-side (i.e. when using "substitute with" the rounding will still be applied to the Buy/Subscription side).
Also, some warning labels have been added to the UI to make this behavior clearer:

The Manage Order functionality has been enhanced with added support for the Order Type / Limit Price / Stop Price fields.

By adding this field to the system configuration, it will be possible to perform bulk changes to operations:

 

 

Note: once an order has been sent to the bank via Trading Interface (e.g. FIX or Open Weatlh), these fields cannot be modified anymore.

 

Also, those fields have been added as read-only columns in the Manage Order grid:

The Contact Protocol functionality has been enhanced to support multiple users to be selected in the "Employee" field.

• Multi-selection field added:

  

• Column added to the Contact Protocols widget containing the Employee/s selected:

  

• Printing the Contact Protocol form will also include the employees:

  

• The import functionality for contact protocols has been also enhanced to support this field:
  

Added support for multi-currency configuration. Amounts previously displayed exclusively in CHF can now be visualized in a system-defined currency.

Creating a new instrument manually in the root folder was not selecting it in the view and in the instrument list.
Now this has been fixed and the new instrument is correctly selected.

Before the fix, when downloading multiple documents as a compressed group, the file names could differ from those when downloading the documents individually. This issue has now been resolved, and the file names remain consistent whether downloaded individually or as part of a group.

Added an enhancement to the model portfolio configuration, allowing users to set up portfolios to automatically apply static weights at day close. Performance calculations for model portfolios use drifting weights by default, which works well for most cases:

However, this new configuration provides flexibility for those who require static weights rebalancing done automatically:

It is now possible to search for multiple RM/PM in Order Management search:

After the update, the last searched values for those fields will reset to the default empty state.

Debit account IBAN and credit account IBAN are added in Management Fee grid and will be available in XLS exported documents also.

On the 'Select debit account' the dropdown 'Client debit account' will now display not only Currency and Account Name, but also debit Account IBAN.

Date range selection for Mandate signature date / Compliance opening date is changed, before user could select only 'From' date,
which would filter results to today's date.
Now, in date range selection is also available to choose 'To' date.
New columns were added in the result list and also in the export file.
New columns are: Mandate Status, RM and RM Assistant

When showing the Performance Attribution from the very beginning of the portfolio, the weights sometimes did not sum up to 100%. This has been fixed now.

'Mandate tags' is now available in Portfolio - Mandate Info

A Line of Credit account is an account from which cash can be borrowed at any time up to a certain limit.
When the account is negative, it behaves as a loan.

Support for Lines of Credits has been added in Assetmax.
Note: lines of credits are disabled by default. Please contact your CRM to enable them.
Note 2: the new loans excluded calculations need to be enabled in the system for lines of credits to be calculated correctly.

Line of Credits in Assetmax

In Assetmax, once the Line of Credits feature has been enabled, it is possible to configure cash accounts as "line of credits" through the context-menu option (right-click), which allows setting validity dates, line of credit limit, and notes.

Note: as of now, the specified limit is not used in any way and it is simply informative.

It is not possible to have configurations with overlapping validity dates.

Cash accounts configured as Line of Credit will start behaving as loans when their value becomes negative.
This means that any value shown as "loans excluded" will be affected by line of credit cash accounts when their value is negative.
These values include: portfolio value, exposure, position weights, portfolio and position profit and loss, portfolio performance, position contribution, etc...

A cash account will behave as a loan only when there is an active line of credit configuration and the value of the cash account is negative.
When adding, modifying or deleting a line of credit configuration, depending on the validity dates, the portfolio will need to be recalculated from the resulting date.
The starting date for the recalculation is calculated as the minimum date from where the cash account changed whether it needs to be considered as a line of credit or not. For example, if the existing configuration specifies the validity range from 10.07.2024, and the from date is modified to 12.07.2024, the portfolio will need to be recalculated from 10.07.2024. That's because, from 10.07.2024 up to 11.07.2024, the cash account must not be considered as a line of credit anymore.
In these cases, the system will prompt the user to decide whether to recalculate the portfolio right away or to mark the portfolio as to be recalculated. If the portfolio is marked as to be recalculated, the nightly "Day Close Operations Job" will take care of recalculating the portfolio:

Line of Credits Limitations

There are a few limitations in the usage of line of credits:

• as of now, the specified limit is not actively used and it is simply informative. This may be enhanced in the future, for example, with a restriction which would check that the limit is not surpassed.
• it is not possible to specify an interest rate on line of credits cash accounts. Accrued interest is thus not calculated.
• there are no transaction types which can reference only the "loan" part of the line of credit (no "fixed term loan interest"-like operations). This means that any performance relevant operation on the line of credit cash account will affect the performance of both "loans excluded" and "loans included" versions, independently of the current state of the line of credit (negative or positive).
• only cash accounts can be marked as "line of credit". Cash mortgages, crypto accounts and cash precious metal accounts cannot be marked as such.

Before the fix, the "select all portfolios" was not working properly, and no portfolio was used. Now this issue is fixed, when using the "select all portfolios" option, the manual selection of portfolios will be disabled and all the available Open and Closing portfolios of type Mandate, Consolidated and Model will be used.

A filter has been added to the Valuations Generation Job for the Report Issuance name. This allows searching/loading mandates that have a specific name in their Report Issuances (note: the matching is done using a partial match - for example searching for "rep" will match mandates which have report issuances with name "report").

It is now possible to calculate the aggregated rating values of positions for textual ratings (both credit and ESG ratings).
This was already possible for ESG ratings, but only when the ratings were numeric.

The aggregated values are calculated only when the corresponding option is selected in the filters:

The calculation is a weighted average of the ratings based on the positions' weights.
For textual ratings, the ratings are converted into their corresponding, configurable mapped value, and that value is used in the weighted average.
The resulting average is rounded to the nearest integer, rounding half up (e.g. 2.6 is rounded to 3; 2.5 is rounded to 3; 2.4 is rounded to 2).
The rounded integer is then re-mapped to the corresponding rating.

For example, the aggregated "Rating Fitch" of the example above is calculated as the aggregation of 2 positions, rated AA+ (25.67%) and BB- (37.15%).
The ratings are configured as:

• ...
• AA+ => 2
• AA => 3
• AA- => 4
• A+ => 5
• A => 6
• A- => 7
• BBB+ => 8
• BBB => 9
• BBB- => 10
• BB+ => 11
• BB => 12
• BB- => 13
• ...

So, AA+ is converted into 2, BB- is converted into 13, and the aggregation is calculated as: ((2 * 25.67%) + (13 * 37.15%)) / (25.67% + 37.15%) = 8.5051
Rounded to the nearest integer, 9, corresponds to the rating BBB.

It is possible to view the rating agencies and corresponding ratings under Configuration > Categorization > Ratings:

1. The rating agencies and ratings are for read-only. To modify them, export the rating agencies and ratings, apply the changes and re-import the file.
2. The new field "Rating Aggregation Type" defines how the aggregation needs to be calculated.
   Possible values are: TextualMappedValueRating and NumericRating.
   TextualMappedValueRating will calculate the aggregated value as explained above.
   The NumericRating expects numeric values as ratings and will perform the weighted average with those values directly. The resulting aggregated rating will be the actual result being shown.
   Note: setting the aggregation type to an empty value will avoid calculating the aggregated rating.
   On the other hand, rating agencies which are not defined explicitly will fallback to NumericRating aggregation type (e.g. in the above configuration example, the ESG rating agency "sustainalytics" is not defined: the aggregation for that rating will use the NumericRating method).
3. The "Mapped Value" of a rating defines the value it will use for that rating when calculating the aggregated rating in TextualMappedValueRating mode.
   Note: an empty "Mapped Value" will cause the position with that rating to be ignored in the calculation (e.g. "NR" for "Not Rated" has an empty mapped value). Additionally, the "mapped values" should be unique so that re-mapping from the resulting value to the textual representation is unambiguous. In case of non-unique values, the system will fallback to the first rating found with that value.
   There should be no "holes" in the mapped values, otherwise the resulting value may have no matching textual rating for it and would thus show an empty value instead.

Note that failure in calculating the aggregated rating will simply show an empty value.
Possible reasons for failures are:

• NumericRating is used but ratings are not numbers
• TextualMappedValueRating is used but a rating is not defined (e.g. rating "ZZZ" is not part of the defined ratings for that agency and thus the calculation is aborted)
• TextualMappedValueRating is used but the resulting aggregated rating does not match any mapped value (e.g. result is 3 but there is no rating with a mapped value equal to 3)

The "Interest Rate" column is now available in the "Positions" and "Positions Search" widgets:

This column is also available in the reporting in the positions list.

Note: Assetmax automatically updates the whole 2024 to include this figures in portfolio positions.

A new type of portfolio, "Benchmark", can now be created which allows defining benchmark instruments on categories.
Benchmark portfolios can then be configured on reference portfolios such as strategies, tactics and model portfolios to allow calculating the performance of such benchmark portfolios using the category weights defined on the reference portfolios: the performance values will be available for Performance Attribution, Position Performance and Portfolio Performance.

For more information about Performance Attribution and related configuration, please see here.

In the Portfolio Management - Model PF widget, it is possible to create this type of portfolios:

This will create empty category positions which follow the chosen classification.

It is possible to set a benchmark instrument on leaf categories ("end" categories which do not have any sub-categories) which will be used as the benchmark instrument for that category.

It is also possible to create new versions to switch benchmark instruments from a certain date. It is also possible to switch an already set instrument in an existing valuation version: note that a day close will need to be performed on the strategy, tactic and model portfolios that uses the benchmark portfolio to calculate the "benchmark view" data with the new instruments.

Once the benchmark portfolio has been created and configured, it is possible to set it as "Benchmark portfolio" on Strategy, Tactic and Model portfolios:

Saving the portfolio configuration will perform the calculation of the benchmark portfolio applied to the portfolio category weights.
For example, the following strategy portfolio is linked to the above benchmark portfolio and defines the following weights on the categories:

In the "Position Performance" tab, the position performance of the strategy portfolio is shown (since the strategy does not have any model position, no position performance is calculated):

By enabling the "benchmark view", the benchmark portfolio's instruments are applied to the strategy category weights and the position performance is calculated on the resulting positions:

The same "benchmark view" switch is available also in the "Performance" tab:

The benchmark view is available also in the "Performance Attribution" widget.
By enabling the "Use benchmark portfolio if available" the attribution benchmark values will be calculated using the "benchmark view" values of the chosen performance reference portfolio instead of the performance figures of the performance reference portfolio itself.
If no benchmark portfolio is defined on the reference portfolio, the system falls back to the performance values of the reference portfolio itself.

For custody and consolidated portfolios, the configuration of reference portfolios and performance attribution have been rearranged and moved to the "Configuration - portfolio" widget to centralize the portfolio configuration. The "Configuration - Performance Attribution" widget has been removed.

Before the fix, it could be that the most relevant exchanges were not listed first in the list of results. Now, the most liquid exchange (if available) appears first in the list. The domestic exchange (having the same country as the instrument's issuer) is also preferred to foreign markets.

The most liquid and domestic exchanges are highlighted in the list.

Before the fix, the imported history was excluded from the performance calculation, even when the Incl. History option was selected.

New crypto currencies that were added:

• ARB
• OP
• TIA
• STRK
• SUI
• TON
• POL

Before the fix, the positions' contributions were not included in the summary (total) row of the reporting Positions component. Furthermore, some of the contributions' values were not available in the reporting component.

Now these issues are fixed.

Positions metrics can now be aggregated at category level. The total aggregated value will also be shown in the summary row:

NOTE: to view the aggregated values, the "Calculate aggregated values" option needs to be checked:

The total aggregated values will match the corresponding portfolio aggregated values displayed in the Metrics widget:

Previously, only time-weighted performance data could be imported. Now, you can import time-weighted, money-weighted, or both types.

Just fill in the relevant columns in the Excel sheet.

Here’s an example of importing both TWR (Time-Weighted Return) and MWR (Money-Weighted Return):

In the positions widget, right-clicking on the cash account item will exclude private equity transactions from the drop-down.

It is possible for a Private Equity to recall some of the profits it has distributed to the investors. The recallable amount is declared, after which it can be recalled or expire.

Recallable distribution operations can be created using existing widgets for managing private equities. Additional UI columns have been added to the Private Equity tab to show the current recallable value.

A person is considered as REVOKED when all the roles within the given mandate are invalid. (when valid to date on the role has passed)

Persons in REVOKED status will be shown with an additional red label – REVOKED. They will be also sorted to be at the bottom of the drop-down list. The new label will appear on person's drop-downs on creating contact protocol, creating report issuance, adding address, creating or modifying operations.

• New label while adding a new correspondence address:
  
• New label on adding a new operation:
  
• Adding new contact:
  

A new button in the "Notifications" window allows marking all the notifications for the current user as read.

Period types QTD (Quarter-to-Date) and YoY (Year-over-Year) can now be enabled as precalculated period types.
Enabling them makes them available in all widgets where a period type can be selected.

In the portfolio Positions widget, new columns for the enabled period types will be available as well.

Enabling new types will cause the day close operations job to take a bit more time to perform all calculations (since it has additional periods to calculate), and the disk space usage will increase as well. An estimate of enabling an additional period type is ~20% increased portfolio calculation time and ~20% increased disk space of the size corresponding to the period-dependent data (not of the full database size).
Please contact your CRM for an estimation of the disk space growth.

Note: the YoY period type is a rolling period and as such, some incremental calculations cannot be applied to it. This causes the calculations for this period to be slower than for the other periods. In terms of disk usage, there are no differences with respect to the other period types.

To enable new period types, please contact your CRM/support.
Enabling of new period types will require the system to be restarted. Once enabled, a special job will be executed which will calculate the portfolios since inception for the enabled periods only. The calculation will occur for all types of portfolios (custody, consolidated, strategies, tactics and model portfolios). Please note that only the data related to the specified period types will be affected and that the rest of the portfolio valuations won't be changed.
This calculation may both take quite a lot of time and will increase the used disk space.
Once the calculation has finished, selecting the newly enabled period type will show the corresponding data.
Selecting the period type while the calculations are not finished yet may show incomplete data.

As for enabling period types, it is now also possible to disable default period types in case they are completely unused.
This allows regaining disk space and to slightly speed up portfolio calculations, if needed.
The current list of default period types is: DTD, MTD, YTD, Since Inception and Since Initial Load.
Note: the DTD period cannot be disabled as it is required as a basis for all other period types.
We advise avoiding disabling default period types unless they are completely unused.
Please contact your CRM in case a period type needs to be disabled.

Loading transactions and positions in the corresponding search widgets will apply a limit on the result by default.
This avoids showing too much data which would not be useful anyway, especially when too broad filters have been applied, potentially by mistake.
Showing limited number of records will both speed up the loading duration and will avoid slowing down the system.

The default limit for both transactions and positions is set to 1'000. This value can be configured in case the default one is too restrictive for the daily work. Please contact your CRM to modify the default limits. Different limit values can be configured for reconciliation module and portfolio management module, and for transactions and positions, respectively.

In case the limit is reached when loading transactions and/or positions, a blinking warning message will be visible and the limit field will be available to allow increasing or removing the limit in case a specific usage requires more data than usual to be loaded.

1. Blinking warning message about results being limited.
2. Editable limit field to modify the default limit.
   Inserting 0 will not apply any limit. Please consider modifying the filters before removing the limit.
   Modifying the limit field will cause the data to be re-loaded with the newly inserted limit.

The limit is applied to the following widgets:

• Global dashboard - Positions search
• Global dashboard - Operations search
• Global dashboard - Maturity Positions
• Portfolio Management - Order Management
• Portfolios - Transactions

Note: exporting positions and transactions will apply the current limit.

Furthermore, the limit is applied also in Reconciliation - Messages widget:

Note: as shown in the message for custody holdings, the various export buttons will apply the limit only in case a selection is expected. Otherwise, the limit will not be applied.

When selecting a custom time period for a report component and using the 'Hide if no operations' option for the report page, the report generation would break when trying to evaluate the custom date expression. This functionality should now work correctly.

Before the fix, the contact emails on the side of the name were blank. Now this issue is fixed, with the emails being correctly visualized next to the name.

Before the fix, the "Scenario" input field could be visualized wrongly when resizing the widget. Now the size of the field is visualized correctly regardless of the widget's size.

It is now possible to choose the risk model that performs the calculations in the Reporting "Ratio Analysis" widget.

On occasion, the flow amount was incorrectly empty; the fix ensures the handling of these cases.

A new field has been added on Current Accounts that allows storing arbitrary user notes that will not be used in any kind of computations or reporting:

The behavior of creating new versions of the questionnaires by clicking "Create new version" has been enhanced to provide a clear differentiation between using the same template or different when it comes to copying data including answers.

The "Copy data from previous protocol" checkbox is now checked by default to avoid issues with accidental failure to tick which led to missing data on the new version.

Behaves the same when there are more versions of the same template.

Additionally, when selecting a different template for the questionnaire, the user will be shown a warning: questionnaire answers won't be copied to the new version but only the underlying protocol's data, since, being different templates, the existing answers may not match the new template's questions.

The classification filter in the Reference Model rebalancing configuration window was re-enabled.

This allows selecting a category to rebalance from a classification which differs from the reference portfolio classification.

In case the reference portfolio has target weights defined on the categories themselves which do not contain any model position, a warning will be shown, as in that case, all the positions of that category will be closed.

A similar warning message is shown in the group transaction rebalancing:

Using Document Management - Document import widget PDF files are imported to the Assetmax.

This feature has been enhanced to support the parsing of XML documents, allowing data to be read not just from PDF files but also from XML files.

XML parsing is added for Pictet bank, but it's configurable for any custodian.

When a report does not have any layout attached, it creates issue during report preview or report generation. Now a detailed error message is shown to display exactly the problem in order to easily fix it.

During order print (for example)

Or in report preview

The Valuations Generation Job has been enhanced with various improvements and additions:

• Mandates/Portfolios filters - new filters have been added to the job to select portfolios:

  

  • The added filters are:
    • Mandate types: select one or more mandate relation types (such as Internal, Advisory, Discretionary, etc)
    • Relationship manager/s: select one or more Mandate Relationship Managers
    • Portfolio manager/s: select one or more Portfolio Managers
    • Mandate tags: select one or more mandate tags
    • Exclude mandate tags: select mandate tags to exclude from the results (i.e. all mandates with those tags will not be considered)
    • Portfolio tags: select one or more portfolio tags
    • Exclude portfolio tags: select portfolio tags to exclude from the results (i.e. all portfolios with those tags will not be considered)
    • Portfolio - Reconciliation Frequencies: considers portfolios with the selected Reconciliation Frequencies (as set in the Portfolio Configuration, e.g. Daily, Weekly, ..)
    • Mandate Report Issuance Periodicities: considers mandates which have Report issuance entries with any of the selected periodicities.
                              

• Save to folder - it is possible to specify a custom output folder (on the filesystem) where the generated reports will be stored. Also customized filename can be specified. Our template language can be used in those fields.

  

  • Some examples:

    • Folder path (template):

      \\192.168.0.5\output\${date;date(yyyy-MM-dd)}\${if mnd}${mnd.rmIdent}${else}${pf.ownerIdent}${end}

      Result: will write the files to a shared folder, and the folders will be structured as follows:

      <reference date>/<RM or PM>/

      e.g.:

      2024-07-31/MB/

      2024-07-31/BA/

      "MB" and "BA" are examples of RM idents or PM idents. The RM will be used for normal mandate portfolios, while for consolidated portfolios the PM will be used.

      It's possible also to use "/" to specify paths, for example: C:/Output/${date;date(yyyy-MM-dd)}/${if mnd}${mnd.rmIdent}${else}${pf.ownerIdent}${end}
                                

    • Filename (template):
      ${pf.ident}_${if mnd}${if mnd.accountPoliceNr}${mnd.accountPoliceNr}_${end}${end}${date;date(yyyyMMdd)}_${report.name}_${now;dateTime(yyyy-MM-dd_HH-mm-ss)}

      Result: the filename will contain portfolio, mandate and report data: <Portfolio Ident><Mandate Account Police Nr.><Reference Date><Report Name><Now>.pdf

      Some examples:

      PF-291000.1_Rubrik2_20240731_ReportName_2024-08-20_11-10-04.pdf
                    

• Upload to SFTP Server - similarly to the "Save to folder" option, with this option it's possible to upload the generated report files to an SFTP server. The same template language can be used also here for the target folder path and filename.

  

  • Examples:

    • Sftp Folder (template):

      /${date;date(yyyy-MM-dd)}/${if mnd}${mnd.rmIdent}${else}${pf.ownerIdent}${end}

      Result: similarly to the Folder example, this will also create folder structures such as  <reference date>/<RM or PM>/

    • Sftp Filename (template):

      see previous example of "Filename (template)"
                          

• Report Options added - there were some missing reporting options which have been added to the Job:

  • Currency
  • Performance Period Type
  • Performance from date (can be set only when Performance Period Type = Custom)
  • Incl. History
  • Use Strike price (instead of spot)
  • Short Put Only exposure
  • Force Delta 1

                     

High Risk Persons widget has a new column "Status" that shows whether a Person is 'Active', 'Inactive', 'Prospect'.

In the Exposure editing window, in some rare occurrences, it could happen that the "Save" button was pressed twice, which could cause both requests to be saved and the resulting exposure to reach 200%. This has been solved by blocking the "Save" button at an earlier stage, before the actual saving occurs.

Positions Export is available in the Download widget.

The behavior of cancelling orders in Assetmax has been enhanced to provide a clear differentiation between cancelling an order in Assetmax vs sending a cancellation request to the bank (via Trading Interface, such as FIX or OpenWealth).

To summarize the changes:

• The standard "Cancel" button will only set the operation as Cancelled in Assetmax (i.e. this means that no cancellation request will be sent to the bank)

  

• To send a cancellation request to the bank, the user must use the "Send cancellation request" button (available in the transaction's context-menu)
  Note: this was renamed from "Cancel pending" to "Send cancellation request"

  

• The "Execute" button has been renamed to "Submit order"

  

                 

Detailed explanation:

In the simplest case, when using the standard "Cancel" button on Orders which have not been sent via Trading Interface: the usual confirmation message will be shown, and the order will be cancelled in Assetmax. In this case there is no relevant consequence as the order was not sent to the bank via FIX/OpenWealth.

Instead, when attempting to cancel an order that has been sent via Trading Interface, the user will be shown a warning with more extensive information. Before confirming this action, he will be able to decide if he wants to cancel the order only in Assetmax or if he would like to send a cancellation request to the bank.

If the user decides to set such operation/s as "cancelled", he will need to provide the reason in a mandatory field in the confirmation popup.

If instead he needs to actually send the cancellation request to the bank, he will use the "Send cancellation request" in the transaction's context-menu, as mentioned previously:

                   

New columns have been added to the widgets: "Transactions" and "Order Management" containing the details of the cancellation:

• Cancelled by user: who cancelled the transaction
• Cancellation date/time: when the cancellation was done
• Cancellation reason: the text that was entered when performing the cancellation (as mentioned: this is mandatory only when cancelling a FIX/OpenWealth order)

The advanced query 'Questionnaire Export' has been optimized and is now much faster, especially when exporting lots of nominatives, questionnaires, etc.

In the context of the Open Wealth Order Placement a small configuration has been introduced to change the refresh interval used to update Orders statuses.

The existing standard query "All Fixed Income" has been enhanced:

• New parameter:

  • "Include Loans": when checked also Loans instruments will be included in the final output
                            

• Modified parameters:

  • "Reference Date" (previously named "Metric Date"): The reference date is used to load the metrics for bonds (as was happening previously), and also to load the actual interest rate of the loaded instruments.

  

                          

• New columns added:

  • Name override
  • ISIN
  • Valor
  • Internal code
  • Custody internal code
  • Currency
  • Interest Rate
  • Interest Rate - Quote Date
  • Calculate a.i. (override)
  • Calculate a.i.
  • Force a.i. reset
  • Issue Date
  • Effective Date
  • Coupon type
  • Next payment
  • First payment
  • Payment at amount change
  • Payment at rate change
  • Payment at end of month
  • Payments/year
  • Fixing currency
  • Day cc
  • Next due date

In the Portfolio dashboard - Positions widget: fixed issue that caused transactions to be generated when using the "Calculate weights only (Model Rebalancing)" option

Importing bonds data using the Excel template import type: bonds, will no longer overwrite ratings when no value is provided in the Excel file.
Only when the specific rating value is specified it will update the corresponding instrument rating.

In the Portfolio dashboard - Positions widget: fixed issue that caused transactions to be generated when using the "Calculate weights only (Model Rebalancing)" option

The Institution Threshold Restriction check previously overlooked positions that did not have an associated institution, leading to potential breaches being missed. Now, the system checks every position for breaches, regardless of whether the position has an associated institution or not.

In the Portfolio dashboard - Positions widget: fixed issue that caused transactions to be generated when using the "Calculate weights only (Model Rebalancing)" option

In the Portfolio dashboard - Positions widget: fixed issue that caused transactions to be generated when using the "Calculate weights only (Model Rebalancing)" option

After the fix, the page no longer gets stuck when loading a large number of contact protocols.

Before the fix, the "Export All" button exported all the available tasks, without filtering for the current mandate or nominative. Now this issue is fixed.

Portfolio - Advanced Search - the following bugs were fixed:

1. Report options button is now enabled when multiple portfolios are selected
   
2. The delete button is now disabled when all portfolios are deselected

When the mandate risk calculation was performed via events triggering (e.g. modify the KYC of a nominative), the check itself was performed by using the context of the current user. Now this has been changed and the calculation is always done in the context of the SYSTEM user.

Furthermore, questionnaire synchronization is performed by the SYSTEM user in case the user that triggers the synchronization does not have access to the questionnaire that should be updated.

Finance - The mandate archiving process has been optimized for all clients that use invoice numbers and is now faster

After the fix, even when having a huge number of Products, the Finance Configuration page will not become unresponsive and will work as expected.

Fixed an issue that was preventing the mandate cloning to work for large portfolios.

Instrument time series reference data can now be audited and versioned:

NOTE: if you have, in general, versioning enabled, and instruments or instrument ticks versioning is enabled, then instrument time series will start versioning automatically after this update. Otherwise, please contact your CRM to enable auditing & versioning.

As always, clicking on the history icon will show the history of that field:

Under the Compliance module, in the "Audit - Audit Events" widget, it is possible to search for "Instrument Timeserie" object type and view the related audit events:

The result will show, other than the actual changes, also the time serie's instrument and, under the "Linked object" column, the time serie type (+ identifier if different from the type):

Name matching hits can now be versioned. Specifically, the "Match decision" and "Notes" fields:

NOTE: if, in general, you have versioning enabled, after the update these fields will automatically start to be versioned. Otherwise, please contact your CRM to enable auditing & versioning.
Search hits that already contain a value in either of the two fields will show the usual "unversioned" to "<current value>" changes done by the VERSIONING user:

As always, clicking on the history icon will show the history of that field:

Under the Compliance module, in the "Audit - Audit Events" widget, it is possible to search for "Name Match Hit" object type:

The result will show, other than the actual changes, the person the hit refers to and, under the "Linked object" column, the entry UID and search time, so that it is possible to find the entry in the name matching searches of that person:

Identification column (entry UID)

The name match entry UID column, "Identification" (identifier of the match in the corresponding database in which it was found) has been added to the name matching search hits grid:

Financial Data: Added Drag and Drop Functionality to Financial Data. In the following example. we're moving Appartment City Zurich to "Accrual" folder:

1- Dragging the necessary instrument:

2- Confirming the move:

3- Instrument is now under the specific target folder

Additionally, added a "Move To" functionality to the context menu:

1- Right-click on the desired instrument, select "Move To" from the menu:

2- We get the following box:

3- We select the needed folder, in our case we want to put TEST BENCHMARK 1 back directly under Root:

4- We click the bottom-right button, and we get the same confirmation box as before:

5- Clicking yes moves the instrument to the desired folder

This functionality also works on folders, moving the folder and all its contents to the required destination.

Fixed an issue that was causing the descriptions' column to not show any description in the Cat. Contribution by Currencies widget.

Before:

After:

1. Fixed field's label.
   Additionally, made all period types available instead of only YTD, MTD and DTD.

2. Added "From date" field which enables when the Custom period is selected.

   

An issue has been fixed in the Document Expiration Job that could cause several tasks to be created for old documents revisions. The job will now consider only the latest revision of each document when checking for expiration.

Before the fix, it was possible to disable all the weekdays whenever a job was set as not active. This could lead the job to an invalid state.

Now this is not possible anymore, an error will be visualized whenever there's an attempt to disable the last active weekday.

Fixed a small issue that would happen in case an instrument ident is too long. This could happen in some circumstances when generating idents for certain instrument types (e.g. for Call Deposits).

History

The new edit window shows on the left ❶ side all classifications and the dates when the categorization was changed. To change exposure figures, change the date from which the exposure figures should be valid using ❷ and choose the classification you want to edit using ❸ , then double click on the exposure cell ❹ in % and enter the new figure.

All Assetmax widgets that use exposure information (Exposure Charts, Position Table, Restriction Checks, ...) use the exposure categorization available at the selected reference date.

Portfolio category

In some special cases (e.g. when working with a strict category portfolio strategy) it might be useful to assign a category to a portfolio without having to assign it to all its constituents.

When assigned at portfolio level, all positions (including cash accounts) will inherit the portfolio category.

Documentation:

https://docs.assetmax.ch/docs/knowledge-base/financial-database/#3-2-categorization-aka-classification-aka-exposure

Creating a transaction on an empty position created from a model portfolio used to end in error when breach was detected and force reason submitted.
Now this has been fixed.

The risk widget now shows a selection of common risk figures.

The widget also shows figures for the reference portfolio (Strategy or Tactic), benchmarks (as defined in the Benchmarks widget) or financial instruments or additional portfolios added through the “Add Series” button.

• Standard Deviation (annualized)
• Expected Shortfall (by default 10d, 95% confidence)
• Value at Risk (by default 10d, 95% confidence)
• Sharpe Ratio (annualized): against the risk free rate defined in Assetmax’s risk configuration or 0 if no risk free rate has been configured
• Correlation to Portfolio: correlation of Benchmark reference indices to the selected portfolio
• Tracking Error (annualized)
• Information Ratio (annualized)

Documentation:

https://docs.assetmax.ch/docs/knowledge-base/assetmax-market-risk-analysis/

The Reporting component "Dynamic Performance Chart" has been enhanced with more viewing options to display the period performance of the main portfolio (in bars) and/or of the additional series selected (in a scatter plot).

More specifically, the following options are now available in the Report component configuration:

• Show Cumulated Perf. (default: enabled) - Show the cumulated performance for the main portfolio (selected portfolio). This will be shown using a line chart.
  
• Show Data Periodicity Perf. (default: disabled) - Show the data periodicity performance of the main portfolio (e.g. 'Yearly'). This will be shown using 'bars'.
  
• Additional Series - Show Cumulated Perf. (default: enabled) - Show the cumulated performance for the additional series (such as portfolio benchmarks, reference portfolio, or manually selected instruments). This performance is shown using a line chart.
  
• Additional Series - Show Data Periodicity Perf. (default: disabled) - Show the data periodicity performance of the additional series (such as the 'Yearly' performance of portfolio benchmarks, reference portfolio, or manually selected instruments). This performance value is shown using dots/markers - i.e. a scatter plot).
  

               

If needed, the series names can be overridden manually using the "Series names override" section in the report component configuration.

                
             

Examples of the report component:

• Showing the main portfolio cumulated performance + data periodicity performance + additional series showing only the data periodicity performance.
  

• Showing the performances with all options active (main portfolio cumulated performance, data periodicity performance, additional series cumulated performance and additional series data periodicity performance)

  

An issue has been fixed in the Document Expiration Job that could cause several tasks to be created for old documents revisions. The job will now consider only the latest revision of each document when checking for expiration.

With the "light" theme, the collapse button of the navigation bar was not visible:

This has been fixed:

The step "Do deactivate instruments without position" has been sped up.

Depending on the database size, that step could be up to 10 times faster.

The wrong permission was being checked to grant access to the "Risk" widget under "Configuration" module.

The correct permission, AdminRiskView, is now being checked.

The logic for instrument names fetched from Infront Data feed is improved.

1. For bonds, we use interest rate and issuer name, whenever available
2. For stocks, we use the issuer name
3. For other instruments we use the instrument names unified at the Infront Financial Database

Rebalancing process used to incorrectly ignore the "No RB" flag for empty positions defined in the related Model Portfolio.
This caused simulated transactions being created on such positions when rebalancing, no matter of the flag.

The Modified Duration, YTM and Dividend Yield columns of the positions widget were showing the value corresponding to the previous day instead of the current day, even if it was available in the corresponding time series ticks.

This has been fixed and the value for the current date is shown instead.
To fix the values retroactively for positions with the above problem a recalculation of the portfolio is needed.

FIX Transactions were not-removable.
Now FIX transactions in statuses Reject or Cancelled that did not generate any transaction (amount was zero) can be removed.
Additional warning will be shown in such cases.

FIX: fixed issue with missing messages caused by ClOrdIDs not yet stored on the database

A bug that prevented scheduled jobs from being deleted has been fixed.

It is possible for Private Equities to return a paid fee in case of unsatisfactory performance. This process is called clawback.

Support for clawback operations has been added and they can be created using the existing widgets for managing Private Equity (Porfolio positions, Reconciliations, Transactions...). Once the operation is created, the amount returned will be taken into account and the impact can be seen when checking the Profit & Loss widget or Private Equity widget (under Product Fees).

Finance - Products - With this fix all folders and reports will be loaded correctly

New name search database provider introduced for interested clients – SGR – that can be used for nominative search and free search.
The new system can be used alongside Worldcheck or as a replacement.

SGR is a smaller database than Worldcheck, after importing full databases Assetmax contains about:

SGR - 2,900,000 entries - 2,500,000 individuals and 360,000 companies.

Worldcheck - 5,300,000 entries - 4,500,000 individuals and 780,000 companies.

It is important to bare in mind, that if you do not want to switch to the new SGR database - no action is required, Worldcheck is the default database.

In case you decide to switch databases:

• A separate license from SGR Compliance is required, please contact your CRM about the pricing.
• All the current data, e.g. all the already existing hits will remain.
• No searches will be done against Worldcheck, the only results would come from SGR.

To switch from one provider to the other, some technical changes will need to take place that support/your CRM will take care of:

• make sure to have an SGR account and license details,
• change the user.conf to enable SGR and disable Worldcheck,
• restart Assetmax server,
• run the proper scripts to clear the unused Worldcheck data,
• setup the name match DB update jobs for SGR.

Depending on the configuration 2 standard providers are supported:

• Worldcheck
• SGR

Additionally, any number of custom file-based name database providers can be configured. They have to use the same file format as either Worldcheck or SGR.

In the examples below four providers are enabled:

• Worldcheck (built in)
• SGR (built in)
• Custom Worldcheck (file database based on Worldcheck)
• Custom SGR (file database based on SGR)

Search will automatically use all the configured, enabled databases.

Nominative search:

Additional data in SGR

SGR file database contains basic data on matches. Additional data will be shown in “Additional data” tab, where also match details will be available to download as PDF:

Note: This is only available for SGR searches (preconfigured SGR provider). Worldcheck or manually configured database only providers based on SGR will have “Additional data” grayed out.

Database Name Match DB Update

WorldCheck DB Update Job has been renamed to Database Name Match DB Update.
It now allows to select a provider (built in or custom) for the import.

1. Provider - One of the configured providers.
2. File path – full patch to the import file. If not selected, import file will be downloaded from online location (only for built in providers - “Worldcheck” and “SGR”).
3. Do import – setting to false allows to skip import and only recalculate phonetic interpretations.
4. Update all entries - Forces creation of info objects for all entries, not only the ones that were updated from the previous import.
5. Recalc. Interpretations - Allows to recalculate phonetic interpretations.
6. Worldcheck - File type - for Worldcheck import.
7. Delete file path - Path for the file with Worldcheck deleted entries.
8. Do delete - processes the deleted entries file.
9. SGR - File type – Two options available – Full or Delta. Only applicable with "File path" set, for manual import.
10. SGR - Import type - Described below.

SGR allows to download Full file or Delta, for any combination of interest areas: Adverse Media, PEP, Local Politicians, Legal & Enforcement, Sanctions.

Delta files represent changes to the previous day, so to have correct, full data one Full import is required, and then every day, a Delta import has to follow.

This job downloads data from previous day, so if it is configured to run every day past midnight, it will download the freshest available data, which is delivered by SGR at 17.30 UTC.

Full files are delivered on Mondays, Delta files are delivered every day.

Full files usually are available for any combination of interest areas, while Delta files are smaller and only a subset of areas may be available for any given day. In this case, the job will import the biggest available subset.

There are 3 types of import:

Latest Delta - Downloads and imports Delta from the previous day, all available areas.

Latest Full - Downloads and imports Full file from the previous Monday, all available areas.

Complete - Downloads and imports Full file from the previous Monday, then delta files for every following day.

Example configuration

Scenario 1. Two instances of the job:

1. Full import, Tuesdays, past 00:00 (mindful about other jobs running at that hours).
2. Delta import, other days, past 00:00.

This will allow having a consistent and up to date state at all times.

Because of the size of SGR database, full import can take significant time. After the first successful Full import it can be disabled and Delta import job can be set up to run every day instead.

Scenario 2. One Complete import at weekends

Scenario 3. One Latest Full import every Tuesday past 00:00

For any additional questions or doubts, please contact your CRM.

Added an additional check on back end side in order to avoid multiple executions of the same order

Previously, only dividends from stock instruments were considered in cash flow projections. Now, dividends for all instrument types are also taken into account.

A new corporate action type "Other Distributions," has been added, functioning similarly to dividends.

By default, this new option is not included in existing report components.

The new corporate action type will appear in the Financial Data > Corporate Actions widget.

Additionally, it will be available in all cash flow projection options and the report component in Cash Flows Projection.

The "Other Distributions" will appear as "CorporateActionOther" in the cash flow projections table, ensuring comprehensive data inclusion for all instrument types.

Fixed an issue where the instrument symbol could not be retrieved.

It is now properly loaded, using the pcomp_symbol field:

The amx.operations function now supports consolidated portfolios.

IDs passed as input to the portfolioIds parameter that correspond to a consolidated portfolio are expanded to retrieve the transactions of the underlying portfolios.

The "Restore Default" button in the Portfolio Valuations section is now disabled by default, ensuring a more intuitive user experience. Previously, this button was not disabled by default due to a missing connection with the stored filter settings. This update ensures that the button accurately reflects whether custom filters have been applied.

If a transaction is executed with an amount which is different than the original ordered amount, this will trigger the recalculation of the transaction fees.

For example, if a transaction is rejected, all fees will be reset to 0.

Added a new parameter to the amx.contribution function:

referenceCurrency

to allow for conversion of the performance figures in different currencies, just like the option available in the Assetmax UI.

Available since Excel Addin v. 2.13.0

Added a new parameter to the amx.operations function:

includeCancelled

The parameter is set to FALSE by default.

When the parameter is set to TRUE, cancelled operations will be included in the results. Please note that to distinguish between cancelled operations and NOT cancelled operations, the field pfop_cancelled must be added to the function return fields. Values for pfop_cancelled field are TRUE/FALSE. TRUE means the operation is cancelled.

Available since Excel Addin v. 2.13.0

Successfully completed changes related to database updates to ensure data type consistency

There was an issue with the Mandate Overview (Chart) widget where switching portfolios did not automatically refresh the data, displaying information from the previous portfolio instead. This problem has now been resolved, and the widget behaves correctly.

Before, when booking a Fixed Deposit Refund, Call Deposit Refund or Fixed Term Loan Refund transaction including interests, the interests have not been reflected in Credited Interests. Two separate transactions – one for the refund and one for the interest payment – needed to be booked in order to have the interests reflected in Credited Interests. Now, also when booking it in one transaction, the interests are reflected in Credited Interests.

This change also fixes the analogous problem for similar operation types. So, the following operation types are affected by this change:
- FixedDepositRefund
- CallDepositRefund
- CallDepositDecrease
- FixedTermLoanRefund
- FixedTermLoanRoll
- FixedTermLoanInterestAmortization

If this needs to be adjusted for a past transaction, a day close can be performed.

Before the fix, it could happen that the categories appeared in the wrong order in the generated report and in Portfolio Analysis : Exposure (Bar).

Reporting: To allow for more granular filtering, Maturities-Overview-Chart and Maturities-Overview-Grid now have the Classification and Categories filters available:

Additionally, all instrument types that have a maturity are now selectable:

Same for the Categories, the full set of Categories for each classification is now selectable, providing more customization options, as each will filter on the category or sub-category level selected:

In the World-Check widget filters will be also applied for the export nominatives.

A new rebalancing mode is now available for mandate and consolidated portfolios: Category Investment (Model Rebalancing).

This type of rebalancing allows investing/divesting in a specific category a specified investment amount or percentage of the portfolio.
For example, 2 use cases could be:

• additional cash was added to the portfolio and the new investment should be allocated in the Equities category rather than rebalancing the whole portfolio
• liquidity is currently at 10% but 15% is needed to cover some future costs: divest of Equities for 5% of the portfolio

The configuration options are similar to the Model Rebalancing ones:

1. An investment amount or investment percentage of portfolio is required. To specify the investment as a percentage of the portfolio, switch from "Money" to the corresponding option:
   
2. The category in which to invest/divest is required. The category can be selected on any level: e.g. Equities as top level or Equities CH as sub-level. The rebalancing will touch only the selected category (and, of course, the category in which the cash accounts are categorized since buying and selling shares will affect the cash).
   Note: selecting a category in which no positions are present may fail since there would be no positions to invest in. This is not true in case model positions are defined for that category and the "Apply reference model rebalancing" is checked. See the next point for more details.
3. These options define the strategy to use to rebalance the investment in the selected category.
   There are 2 ways to rebalance a category:
   1. "Apply reference model rebalancing" will use the model positions of the reference portfolio configured on the portfolio to try to reach the same weights, but proportionally scaled to reach the intended target % after the investment. E.g. if Equities is currently at 50% of the portfolio and the investment corresponds to 20% of the portfolio, the target % is 70%. If the reference portfolio has model positions in Equities which sum up to 40% (e.g. eq 1=15%, eq 2=25%), they will be proportionally scaled to reach the target of 70% (i.e. eq 1= 26.25%, eq 2= 43.75%).
      "Use drifiting weights" will use the drifting weights of the model positions instead of the weights themselves.
      When no model positions are present in the selected category, even if "Apply reference model rebalancing" is checked, then the system falls back to the "Cash allocation strategy", which corresponds to the second way of rebalancing.
   2. "Cash allocation strategy" defines how the investment amount should be allocated on the positions within the selected category.
      The strategy will be used when "Apply reference model rebalancing" is unchecked or when there are no model positions for the selected category.
      1. Pro Rata: The investment amount is distributed proportionally across the positions in the category based on their current weights. The relative weights of the positions within the category remain the same.
      2. Equal value: The investment amount is distributed equally among the positions in the category. The value of the positions in the category will change by the same amount.
      3. Equal target %: The investment amount is distributed so that the positions are equally distributed within the category after the rebalance. The target weight will be the same for all positions within the category.

Example

We invest 50k CHF in Equities, allocating the cash using "Pro Rata" cash allocation strategy.
We set all below options to 0% and 0 rounding to be as precise as possible in investing the whole 50k.

After rebalancing, the following is the result:

1. 50k CHF have been investment from the CHF cash account
2. The weights of the positions under Equities have changed by the same amount (Cash: 69.40% -> 20.22% [-49.18%]; Equities: 30.60% -> 79.78% [+49.18%]). The investment amount was allocated using the "Pro Rata" strategy.

For the full documentation on portfolio rebalancing including the below changes, click here.

New options have been added to the portfolio rebalancing:

Consolidated portfolio rebalancing

It is now possible to rebalance a consolidated portfolio against the model portfolio configured on it.

In the new field "Cash portfolio", one of the underlying portfolios composing the consolidated portfolio can be selected.
The "cash portfolio" will be treated as the "cash account" from/to which funds are transferred in order to buy/sell the positions within the underlying portfolios.
This will cause the cash accounts of the underlying portfolios to remain seemingly unchanged, except for the cash portfolio's cash accounts.

It is possible to define a default cash portfolio for a consolidated portfolio in the consolidated portfolio configuration widget:

When set, the "Cash portfolio" field will be automatically initialized to the defined portfolio. It is still possible to override the cash portfolio before rebalancing.

Executing the rebalancing will generate transactions on the underlying portfolios in order to reach the target weights defined in the model/reference portfolio.
If a cash portfolio has been selected, incoming payments/outgoing transfers will be generated from/to the cash portfolio to the other underlying portfolios to cover for the needed purchases/sales.

New option - Investment logic for categories without a model

A new rebalancing option, "Investment logic for categories without a model", is available to rebalance portfolios (also for "normal", non-consolidated portfolios) which allows to define how the delta weight (the difference in weight between the current weight and the target weight) of categories without model positions need to be distributed among the positions being part of that category.

Note: the selected strategy will not be applied on categories where model positions are defined. Only categories without any model position will use the selected strategy.

For example, with the following strategy portfolio, the investment logic will be applied only to the categories "Other fixed income", "Equity Switzerland" and "Equity Europe ex Switzerland", but not to "Bonds CHF" as it contains model positions:

This allows to avoid defining the specific model positions of a reference portfolio and rebalance the portfolio keeping the already existing positions.
This means that strategy and tactic portfolios can now be used to rebalance portfolios, not only model portfolios.
Therefore, full strategy portfolios now also have the rebalancing configuration options as the model portfolios do:

When clicking on the small "?" icon next to the "Investment logic for categories without a model" option, a small window appears which briefly explains the behavior of each strategy.

Pro Rata: The delta weight is distributed proportionally across the positions in the category based on their current weights. The relative weights of the positions within the category remain the same.

Equal value: The value of the delta weight is distributed equally among the positions in the category. The value of the positions in the category will change by the same amount.

Equal target %:The delta weight is distributed so that the positions are equally distributed within the category after the rebalance. The target weight will be the same for all positions within the category.

Consolidated portfolio rebalancing limitations

There are a few cases in which the rebalancing fails on consolidated portfolios:

• when underlying portfolios have positions in common (e.g. 2 or more underlying portfolios contain the same instrument) and the reference portfolio defines a target weight for that position's instrument. In this case, how the target weight should be reached is undefined since it could be reached in multiple ways (the positions could be bought/sold on a single or multiple portfolios with the same or different weights).
• when the reference portfolio defines a model position which is not present in any of the underlying portfolios. Also in this case, how the target weight should be reached is undefined: the position could be bought on a single portfolio, or different parts on different portfolios.
• when the model portfolio defines a target weight on a category but no underlying portfolio contains positions in that category. It is not possible to modify a category weight if no position is present in it (note: it doesn't fail, but it cannot reach the intended target weight).

Consolidated portfolio amount types

In the "Positions" widget, when updating the simulated trade input field, it is now also possible to specify as amount type either "% of consolidated portfolio" or "Target % of consolidated portfolio":

This will calculate the transaction amount needed to increase/decrease the weight or reach the target weight based on the consolidated portfolio value rather the the underlying portfolio value which the position belongs to.
Note: it is possible to update a position simulated trade only when positions are not aggregated, as otherwise, it would be undefined which underlying portfolio the trade should be created on.

It is possible to select the "% of consolidated portfolio" also in the Trade transaction dialog when opening it within a consolidated portfolio context:

Fixed issue where the Operations Notification job would fail if the checkbox parameter "Use gross amount" was not checked. This scenario is now handled properly.

The corporate actions grid in Financial data module has been enhanced:

1. It is now possible to mark certain rows as "Manual" for manually created/managed rows.
   Newly created rows will default to "Manual" being checked.
2. Renamed "Type" and "Subtype" to "Provider Type" and "Provider Subtype".
3. Added the "Export Excel" button which will export to Excel the current state of the grid.
   The print button was not working and has been fixed.

In addition, the state of the grid is now persisted so that columns visibility, order and sorting is kept between sessions.

Fixed an issue where the "Cancel" button was enabled for FIX operations with Execution status: Fill / Traded.

The "Cancel" button is now properly disabled in these cases.

Before the fix, the Positions search widget didn't consider the translations for the Mandate type column. Now, the column correctly shows the translations.

Before the fix, the advanced query Pending Operations would fail when processing operations with no FX rate. This issue is now fixed.

Some small translations corrections have been performed in the Tasks and Contact Protocols widgets

Prior the fix, the generation of a ROA report would fail for mandates with more than three relationship managers. Now the report will be generated, ignoring the additional relationship managers.

The new Main Dashboard is a highly requested feature designed to enhance your experience in Assetmax by providing quick access to all relevant mandate information and global KPIs. The redesigned dashboard includes several improvements and new features that make it more efficient and user-friendly.

Key Features:

• 11 New KPIs: Track more aspects of your performance with eleven new key performance indicators.
• Customizable KPI Layout: Arrange the KPI display to suit your preferences and priorities (1).
• Redesigned KPI Detailed Windows: Enhanced detailed windows for KPIs provide more information in a clearer layout (2).
• Additional Columns in Mandates Table: More data points are now available directly in the mandates table (3).
• Dynamic Grouping in Mandates Table: Group rows up to three levels for better data organization and insights (4).
• Collapsible and Expandable Rows: Collapse or expand rows in the mandate table to focus on what matters most (5).
• Mandate Information on Single Line: View up to three pieces of mandate information on a single line for a streamlined view (6).
• Exportable Mandates Table: Easily export the mandates table for offline analysis or sharing (7).
• Improved Performance: Enjoy faster load times and smoother interactions.

When any underlying portfolio had custody bank or mandate removed, the whole Consolidated report would crash:
This has been fixed.

The Portfolio Loss Reporting Job has been enhanced with the addition of some parameters to allow processing a subset of Mandates, according to the actual user's needs. The added filters are the following:

Mandates Selection

• Mandate Statuses - select which mandate statuses should be considered. For example: 'Open', 'Opening' and 'Closing'mandates.
  Default: 'Open'
• Mandate Types - select the mandate relation types that should be processed. For example: Advisory, Discretionary, etc.
  Default: no filtering (all types are considered)
• Account Holder Domicile - filter mandates based on the account holder Legal Domicile
  Default: no filtering
• Account Holder Nationality - filter mandates based on the account holder Nationality
  Default: no filtering

If needed, 2 other parameters have been added to have more control on which performance values are checked:

Portfolio Performance

• Performance Value Type - select the performance value type to be used, such as Net, NetLoansExcluded, Gross, etc
  Default: Net
• Performance Methodology - select the performance methodology to be used between Time Weighted or Money Weighted
  Default: TimeWeighted

A new standard query, "All Instruments with last quote", has been added to retrieve instrument information according to the specified timeseries.

For each instrument, in addition to basic information, also the last price and date for selected timeseries are shown:

The query expects as parameter the type of time series, e.g. LastPrice, NAV, AdjustedPrice, YieldToMaturity, ...
The time series type must be typed exactly as visible in the Financial Data module (upper and lower case characters included).

Please note that the last column was added because sometimes it can happen that a timeseries name and type are not the same, so it's easier to find the correct one, if needed.
If the name is different, but it's empty, then the Type is still shown.

For example:

Fixed an issue where a custodian message could not be loaded into Assetmax if a specific account custody ident could not be linked to a single account because the custody ident is assigned to multiple accounts. In this situation, a meaningful error message is now displayed providing the user with the account custody ident that generated the error.

An issue during printing of KYC form (not questionnaire) had been fixed.
Now form can be exported in pdf as usual by clicking on Print form button

Before the fix, multiple imports of the Risk Scenarios configuration file would create duplicated entries, causing an issue when loading the risk scenario in Portfolios : Risk Scenario [BETA].

The issue is now fixed, updating the existing risk scenarios instead.

In Configuration > Import, it is possible to export templates of the newly supported import types:

With these imports, it is possible to update almost any of those objects' fields.

Note: if the identifying columns contain values that do not find an existing object, a new one is created.
For example, if the anonymized ident of a mandate is specified and no mandates are found with the specified identifier, a new mandate is created.

Note: contact protocols are always newly created as there is no uniquely identifying field to find an existing contact protocol.

Filled questionnaires import enhancement

The import of questionnaires' answers has been enhanced with the possibility of specifying a configuration sheet which defines mappings from a questionnaire template to another one. E.g. if an answer's question has an ident Q_2 and the corresponding template of the target questionnaire has a different ident, for example, Q_7.3, a mapping can be specified that would import answers for Q_2 under the question Q_7.3.
This is useful in case an already filled questionnaire needs to be mapped to a newly imported questionnaire template, without the need to re-insert all the answers manually.

Here is an example of configuration sheet:

In the Flow of Funds job, the following options have been added/modified to better control which dates are going to be checked by the job:

• [new] Force check from date: The selected (dynamic) date will make the job include reconciled transactions which were reconciled or modified after that date. This will potentially re-check already checked periods and will include operations that were not detected before due to various reasons, e.g.: price changes which caused the operation value to now breach the rules, mandate risk changed, etc...
  This is the same behavior as when "Force check from rule start date" is checked, but in that case, the starting date is the rule's start date.
  This option is disabled if "Force check from rule start date" is checked.
  If the specified date results being earlier than the rule's start date, the rule's start date is used instead.
• Min. Trade Date From: enhanced the dynamic date selection with additional options:
  Otherwise, works exactly as before: i.e. it will only consider transactions with trade date greater or equal to the specified date.

Suggested usage of new options

In general, the "Flow of Funds check Operations" job detects the range of dates it needs to (re-)process and then checks the reconciled transactions in that range.
When doing so, it can happen that transactions that were previously checked and were not considered to breach the configured rule, are actually now detected.
This could be due to various reasons that cause the transaction's context to be different than in a previous job execution, for example:

• The linked mandate's risk changed (and thus a different threshold value is being checked)
• The transaction value changed (due to price or FX rates changes)
• The linked mandate is no longer marked as "Internal" ("internal" mandates are ignored for rules that check "all portfolios")
• Existing flow of fund violation was manually deleted
• ...

To avoid (too) old transactions being detected by this job, we advise not to use the "Force check from rule start date" option but rather use a combination of "Force check from date" and "Min. Trade Date from":

• Force check from date: 3 months ago - the job will always consider reconciled transactions that were reconciled or modified up to 3 months ago. Note: this does not consider the "trade date" of the transaction, but when the transaction was reconciled or modified. E.g. if we modify today a transaction with trade date 6 months ago, that transaction will be considered by the job.
  Transactions reconciled or modified earlier than 3 months ago will not be re-checked.
• Min. Trade Date From: 1 year ago - from the reconciled transactions above, consider only the ones with trade date greater or equal to 1 year ago.

The dynamic date select field has been enhanced with additional options:

Options marked with the "edit" icon will require a manual selection:

• a specific date (for the Custom type), or
• an amount (for the types with "<period> ago")

With Custom type:

With a "<period> ago" type:

Scheduled jobs that were using the dynamic date select field were only showing the following types until now:

• Custom
• Today
• Yesterday
• Previous Business Day

All of the those jobs (e.g. Day Close Operations job, Valuations Generation job, etc...) will now show the full list of dynamic date types.

Portfolio Search now allows searching for Strategy, Tactic and Model portfolios:

The Excel Addin now supports the Portfolio Performance History functionality.

New function: =amx.performancehistory(...)

The output of the function reflects the same results found in the Performance widget in Portfolios module in Assetmax.

Assetmax UI:

Excel Addin:

See the complete documentation at the following link:

https://docs.assetmax.ch/docs/knowledge-base/excel-addin-reference/#amx-performancehistory

Available since Excel Addin v. 2.12.0.

In Advanced Mandate Search widget new columns are available for display in result grid.

• Added configurable columns to advanced mandate search: Description, Custodian RM, Compliance officer, Restriction notes, LEI (Legal Entity Identifier), Closing date.
• Fixed issue with configurable columns on advanced mandate search: Mgmt. unit Identifier, Mgmt. unit Name.

Added a new Standard Query "Name Matching Hits" which returns all name matching hits with a decision (match/non-match) for all nominatives

The standard query 'All Nominatives' has been enhanced with a small addition:

• 'Nominative RMs': this column will contain the Relationship Manager/s that have been set on the Nominative.

                   

Nominative / Base Data:

           

Query output:

Assetmax generates files in MMASCII format soon after data are processed by the parser, if the MMASCII export is enabled.

The output folder is set in the assetmax.conf file:

Assetmax generates one file for the transactions and one file for the positions:

The final user has to manually select and import these two files in PM.

Some report components displaying exposure data have the possibility of filtering portfolio positions by categories so that the exposure data refer only to the subset of categories selected and not to the entire portfolio.

For example, show the exposure data for "Bonds" only, but for the "Currencies" classification:

For the following groups of instrument types, the categories filtering was not applied correctly and their values could affect the exposure data even if not part of the selected categories:

• forwards
• fx futures
• fx options

This issue has been solved so that positions not in the selected categories will not affect the exposure values.

Restriction Breaches: Previously, the user could change the status of a breach without writing a comment despite the "Mandatory Comment" flag being checked. After this fix, this is no longer possible, and the flag correctly prevents the user from doing so.

When the "Mandatory Comment" flag is selected, the text will show "(Mandatory)" next to the status statement.

1- In case the Comment is filled, the Save button is enabled normally:

2- In case the comment isn't filled, the Save button will be disabled, and a red border and a tooltip will appear reminding the user that the field is required:

The export to Excel of Restriction Breaches included only the "last status" of breaches/passes.
Now the following export options are available:
    - "Standard": this will export breaches/passes with their last status (i.e. as was done prior to this change)
    - "With status history": this will export the breaches/passes including their history

In the export with status history, one has to select the date from when to include the history.

Example of export with status history:

When importing an instruments from an excel spreadsheet, an omitted field should now be correctly ignored instead of defaulting the field to the types default value.

Before the fix, a task could not be created for expired documents having multiple revisions. This issue is now fixed, as the tasks are linked to each document's expired revision.

The error in the exporting PF comparison is resolved by preventing duplicate sheet names.

The report component Cumulated P&L / Performance could be very slow for consolidated portfolios for Money Weighted performance in case the user generating the report did not have permission to read all portfolios.

This has been sped up so that it takes as much time as for users with permission to read all portfolios (or system admins).

Added Exchange field to the Rebalancing Configuration window which allows to select a specific Exchange or "Smart Order Routing" for the orders execution applied to the generated transactions

Implemented enhancements to our dividend projection system to ensure greater flexibility and accuracy in handling dividend payments:

• Changed loading mechanism for projecting dividends, limiting the loading process to dividends with payment dates falling within a specified period range (default 1 year back). This period range is configurable, allowing for adjustments based on business requirements.
• This implementation serves to prevent the projection of dividends for instruments that have stopped their dividend payments.

We enhanced the dividend projection logic to ensure greater flexibility and accuracy in handling dividend payments:

• Added support for projecting multiple dividends occurring on the same payment date or within a configurable number of days (default 5 days) prior to the latest dividend payment, as some instruments pay multiple dividends at same payment date.

Assetmax now support drawdown calculation and visualization for portfolios and instruments.

Portfolios

We have added a portfolio widget to show the historical drawdown for a portfolio.

The widget can also show other reference portfolios or instruments for comparison.

Financial Database

We added two new script functions to calculate drawdown time series. These time series can then be used in the portfolio widget for comparison purposes.

1. Drawdown based on price time series
2. Drawdown based on instrument performance time series

In the Performance Attribution, an issue in the calculation of the performance per investment category has been corrected. The values of the performance per investment category are now calculated directly instead of basing the calculation on corresponding contribution results and position weights.
Please note that the attribution calculation will be performed on the fly when loading the data, therefore no day close is necessary.

Portfolio Management - Search: The recently added fields of the nationality and domicile of the Account Holder and the Beneficial Owner had a small issue where saving the search or clearing wasn't taking into consideration these fields. Issue has been fixed, and they will now be properly saved and cleared when searching:

Portfolio Management - Order Management: Users with TransactionNotPlacedCancel will now correctly see the Cancel button and be able to use it when appropriate:

Fixed corner cases for the category restriction check where the calculated weight, due to some small rounding issues, would result in values such as 99.999999999999% instead of 100%, causing breaches in restrictions configured with a threshold of a minimum weight of 100% of a specific category or sum of categories (i.e. all the portfolio within the specified set of categories).

For example, a restriction configured as "Portfolio composed of Cash and Equities only":

could have been affected by such an issue (not guaranteed, though).

New columns have been added to the Transactions grid in the Order Management and Portfolio dashboards:

• Investment Profile: the investment profile that has been set on the Mandate
• Account/Deposit ident: the 'ident' of the cash account or deposit, loaded from the main flow of the transaction

New columns will be also included in the excel export.

It is now possible to create bLink consent, which will be used for OpenWealth Order Placement API.

This can be done under Portfolio Management in the new Custodian Links widget:

To create a new consent simply click on Add new. On the dialog select bLink as Link Type, then select one of the available providers from bLink, and the respective custodian from Assetmax.

If the response from bLink to initiate the consent creation is successful the user will be forwarded to the consent creation page of the selected bLink provider.
For example, using the bLink Simulator 2 provider:

After successfully completing the consent creation, the status of the link changes to "valid" and the user can use it to send orders through the OpenWealth Order Placement API.

When exporting the standard "All Beneficial Owners" query, the column "Anonymized Name BO" was not being rendered correctly, causing the shifting of content of the last columns.
The specific case has been fixed and future cases prevented.

Loading of transactions and positions in the Reconciliation module, when using broad filters, can take a lot of time, and can potentially slow down the overall Assetmax application. For this reason, to enhance the performance and reduce load, a limit ('max results') has been introduced. By default a maximum of 1'000 records will be loaded. This will ensure that cases in which filters are set to be too broad (e.g. no custodian filter, including all reconciled transactions, no filter on dates, etc) the number of records will be limited, and no overall slow downs will occur.

It's important to note that this limit does not apply to the 'Automatic Reconciliation' functionality. This means that the automatic reconciliation will still process all the entries that match the selected filters, even if these are above the limit of 1'000 records.

In case of absolute need though, a filter has been added within the Advanced options to modify/remove this limit:

This is available both in the Transactions and Positions widgets.

It is advised to keep the 'Max results' filter active though, as this will provide the best performance.

Add support for configuring the names of configuration folders for specific SIX VDFS selection files using the vdfs configuration table in the database. If folder names are not configured the default folder names are used.

Before the fix, it was possible to mistakenly link a cash position with the wrong structured element type (e.g., security deposit). Now, this is prevented from happening.

Added Private Equities columns to Positions Search and Operation Search on Global Dashboard and Portfolio Dashboard, as well as to the Transactions Search on the Portfolio Dashboard.

Client Portal: Fixed issue where YTD, MTD, and DTD data wasn't properly displayed:

An improvement in terms of speed has been implemented for pre-trade restrictions checks.
The biggest improvement is for the case when the pre-trade check results in breaches: before, the system was performing an additional, unnecessary restrictions check.

General slight improvements have been performed for the following specific restrictions (these apply to all restriction checks, not only for pre-trade checks):

• Category restriction
• Deviation from Model
• Deviation from TAA
• Strategy restriction

Checking restrictions for a portfolio where most restrictions use the above types should improve by a factor of ~1.3.
The pre-trade checks should improve by a factor of ~2.5-3.

In the WorldCheck DB Update job a new parameter has been added to be able to process a custom list of deleted entries, instead of downloading the 'delete' file directly from World Check.
The new parameter is called "Delete file path" and similarly to the already existing "File path" parameter it can contain a path to a locally stored file on the server.

The provided file will be processed as a "delete file" CSV.
Expected format of file is CSV file without header with UID from name_db_entry and timestamp splitted with tab. Example: world_check_delete_file.csv

Before the fix, the New / Edit Job window size could become too large, for example if several options were selected for a field.

Now, the size of the window is fixed, and the options will be rendered in multiple rows.

Fixed an issue that was preventing the addition of new printers:

Sorting

Before the fix, sorting the scheduled jobs by schedule time could behave unexpectedly. Now the jobs are correctly sorted by the time they are expected to execute.

Interrupted Jobs

Before the fix, if a job's execution was interrupted for example by restarting Assetmax, it could still be marked as successful. Now interrupted jobs are marked as failed, with a proper error message.

Fixed a problem when attempting to print certificate letter to pdf caused by incorrect handling of different row types.

Prevent from removing the default time serie, allow setting another one as default instead.

Disabling the default option on a time serie is not possible anymore. When trying to do so, a tooltip is visualized, suggesting how to change the default one for the instrument.

When setting a time serie as the default one, a dialog is visualized to confirm the action.

Portfolio - Investment Profile: Now when retrieving the risk ability from the profile of the user, Assetmax properly checks the user configuration for the investment profile.

The following fixes have been implemented when importing PDF advices for UBP and Vontobel:

• UBP: Statements, Fiscal Statements, Valuations - correctly detected as UBP advices
• Vontobel: advices with incomplete portfolio identifiers still correctly detected as Vontobel advices

Fixed an issue that was causing, in rare occurrences, freshly edited restrictions to not use the latest changes during restriction checks.