LEXolution 9.2 Release Notes

With LEXolution 9.2, new features and numerous improvements have been delivered, and known issues have been resolved. The highlights are:

  • Merger and complete redesign of the Case Files/Case File Favorites views
  • Negative invoices without a preceding invoice
  • Crediting of advance payments in e-invoices as a line item
  • Consolidation of documentation in the stp.one Help Center

We hope you continue to enjoy LEXolution — your STP LEXolution Team

Important Notes for Updating to Version 9.2.84

  • Major releases, feature packs, and service packs are cumulative and always contain the complete current version.
  • LEXolution 9.2.84 requires Microsoft .NET Framework 4.8 on both the server and client side.
  • If not already installed, install .NET Framework 4.8 in advance (e.g., during a scheduled maintenance window) on the LEXolution server and on clients so that the LEXolution update runs smoothly and without interruption.
  • LEXolution 9.2.84 requires Microsoft Visual C++ Redistributables 2015–2022 (x64 and x86) – 14.30.30704 on the client side. If the system already has a current LEXolution.DMS or winsolvenz.p4 installation, the C++ runtime is already present.
  • If you are using the centralized STP User Management (UM), we recommend updating to version 1.5.163 or later and updating STP common services to version 1.5.0.
  • Downloads for .NET Framework 4.8, the UM, and the common services can be found on our download page for LEXolution.
  • LEXolution 9.2.84 is approved for Windows 11, Windows Server 2022, Office 2021, and Office 365.
  • The LEXolution server update (the final step in the setup using the Start LEXolution Server button) may take over 15 minutes when updating from a version earlier than 6.4 on larger LEXolution databases containing millions of recorded services (time entries, disbursements).
  • LEXolution 9.2.84 requires IKAROS 2022 or higher.

LEXolution.BI

  • LEXolution 9.2.84 requires LEXolution.BI 9.2

ADB Tool for Updating the Reporting Database

  • If you use the ADB tool, it must also be updated to version 9.2.84 on the relevant server (typically the SQL server). Please use the new config from the zip package and adjust the settings accordingly (database connection, number of threads, port, tables to exclude).

Documents (LEXolution.DMS)

  • Starting with version LEXolution.KMS 6.4.244, LEXolution.DMS is only accessed via the new interface. Note: The entry in the LEXolution server config is now equivalent to the entry . No manual changes to the config are therefore required.

Additional Notes

  • LEXolution 9.2.84 is approved for Office 2024.
  • Localizations for German, English, French, and Swiss German (de, en, fr, de-ch) are included in the setup packages from LEXolution.KMS 6.3.81 onward and are installed automatically. If a server-side localization is not desired (e.g., on an English app server with English error and notification messages in LEXolution), the relevant folder (e.g., en) can be removed from the app server.
  • With the rebranding of LEXolution.KMS to LEXolution in version 8.0.122, if you are using the STP Updater, the directory in the STP Updater repository must be updated:
    • For setup-based updates:
      • C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution.KMS Client -> C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution
      • C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution.KMS Word AddIn -> C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution Word AddIn
    • For patching individual files:
      • C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution.KMS Client -> C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution
      • C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution.KMS Word AddIn -> C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution Word AddIn

Version History

  • 07/25/2025 Release 9.2.79 (internal)
  • 08/08/2025 Release 9.2.81 (internal)
  • 09/02/2025 Launch
  • 09/16/2025 Release 9.2.84 (bug fixes and enhancements)
  • 10/31/2025 Patch_Lx9284_01 for conflict check

Patch_Lx9284_01 for Conflict Check

The patch can be downloaded from the download directory. The installation instructions for the patch are included in the readme.txt file in the patch zip package.

Bug Fixes

  • Conflict check does not remain in "accepted" status (#104170)
    • Previous behavior
      • LEXolution 9.2.84 is configured so that a conflict check starts automatically after X minutes following a KFC-relevant change. See Administration > System > General Settings > Conflict Check section. If a KFC was manually executed within that time and, for example, accepted or rejected, it would still run again and revert to "Review required" status.
    • New behavior
      • The system now checks whether the KFC has a final status before placing it in the queue for automatic execution after X minutes. This ensures that a KFC that has already been reviewed does not revert to "Review required" status.
  • Conflict check incomplete for subject-matter conflicts with conflict keywords (#104294)
    • Previous behavior
      • When a conflict keyword with a description was added to a case file in LEXolution, or when the description of a conflict keyword was changed, the search index for conflict keywords was not updated during that process. As a result, a subject-matter conflict based on conflict keywords was not detected. The issue did not occur for case files with conflict keywords that were created via the cloud (New Matter Intake).
    • New behavior
      • When a conflict keyword is added or changed for a case file in LEXolution, the search index is updated so that the corresponding subject-matter conflicts are detected.

Changes in 9.2.84

Version 9.2.84 includes all changes from version 9.2.81, plus the bug fixes listed below. Version 9.2.84 can be downloaded from our official download page.

Collision Lists

  • Extension of collision list imports (#100424)
    • The import of collision lists for the scope of conflict checks has been extended to include the US SDN sanctions list. Once configured, the list is read in and updated automatically.

Bug Fixes

  • Deadlines/follow-ups: Filter does not correctly recognize dates in certain cases (#89142)
    • Previous behavior
      • In certain cases, a time component was saved along with the date when saving deadlines and follow-ups. In reports, filtering for these deadlines did not work correctly.
    • New behavior
      • When saving deadlines and follow-ups, only a date is stored — no time component. This also applies to pre-deadline dates. For deadlines that were already saved with a time component, the time portion is set to 0 during the update.
  • Deadlines: When entering a new emergency deadline, the start date and end date fields cannot be edited in certain cases (#100871)
    • Previous behavior
      • When entering a new emergency deadline from the Case Files view, the deadline start and end date fields could not be edited.
    • New behavior
      • When entering a new emergency deadline from the Case Files view, the deadline start and end date fields can now be edited.
  • Billing: RVG fee 4141 based on 4104 has incorrect range (#100087)
    • Previous behavior
      • When fee 4141 based on 4104 was selected, the range of 44.00 to 319.00 was applied.
    • New behavior
      • When fee 4141 based on 4104 is selected, the range of 48.00 to 348.00 is applied.

Changes in 9.2.79 / 9.2.81

Case File

New default layout

An example of an alternative user-specific layout with the case file list on the left and 3 areas for various details

Another example of a user-specific layout offering a cleaner overview with less information displayed at a glance

  • Interface customization options in the Case Files view (#48707, #82074, #82074)

    • The case file data area and the former quick info area have been replaced in the default layout by 3 sections. Instead of a single detail view with fixed tabs, these sections contain individual panels that can be repositioned and moved between sections. Panels that are not needed can be permanently shown or hidden. User-defined settings are saved by closing the view via the X on the Case Files tab.
    • In the panel tables, column order and displayed columns can be saved per panel in the user profile.
    • Panel tables can be displayed as cards. The display order can be changed, and changes can be saved in the user profile.

  • Filters in the Case Files view (#58681)

    • When the view is opened, the Favorites filter is active by default, showing the user's personal case file favorites. All case files with a status of "Potential" or "In Progress" and all case file types are also shown. The location field is no longer pre-filled.
    • The Context Filter option is set and activated automatically by the system when the view is opened via a context menu jump.

  • Created date and modified date in panels (#50388)

    • In the panel tables, the 4 columns "Created by," "Created on," "Modified by," and "Modified on" are displayed independently of any changes to the case file, and are specific to each panel.

  • Case file creation and editing (#49141, #49142, #57457, #76484)

    • After entering the required fields in the Case File Data panel, the record must be saved. If values are defined as required fields in property lists, they will be prompted for afterward. Once saved, additional data such as parties and responsible persons can be added in the other panels. The "old case file number" field can be edited to allow manual data transfers. Newly created case files are automatically added to case file favorites.

  • Starting a conflict check (#50653, #67351)

    • Since data such as parties, conflict keywords, and case file status can now be edited and saved independently in the case file view, there is no longer a single unified trigger for starting a conflict check. The conflict check can therefore be triggered manually or on a scheduled basis when the status "Execution required" is set.

  • Setting the case file status (#49229, #58484, #66055, #67335)

    • When creating a case file, you can choose between "Potential" and "In Progress," depending on the configuration. In all other cases, the status of a case file can be changed via the "Set Case File Status" function in the ribbon. The mandate decision date contains either the date of the mandate decision or the date of the mandate rejection. If a mandate is rejected, a reason for rejection must be entered. The order of status transitions is not validated, so it is possible to revert a case file that is "In Progress" back to "Potential," provided the "Potential" status is permitted.

  • Parties panel (#49871, #50073, #50111)

    • This panel displays the parties involved in the case file. The functions New, View, Edit, Delete, and Copy are available.

  • Responsible persons panel (#49872, #50283, #50166)

    • This panel displays the responsible persons for the case file. The functions New, View, Edit, and Delete are available. If the involvement types HVRA, HV location, or FoMa case handler are selected, any responsible person already assigned to the case file is replaced by the new entry.

  • Legal areas panel (#49875, #50388)

    • This panel displays the legal areas associated with the case file.

  • Categories panel (#49877, #51217)

    • This panel displays the categories associated with the case file. The functions Add and Delete are available.

  • Deadlines panel (#49970, #51220, #65629) This panel displays the deadlines for the case file. The functions New, View, Edit, Pre-deadline seen, Completed, and Print are available. A filter allows completed deadlines to also be shown.

  • Follow-ups panel (#49971, #51221) This panel displays the follow-ups for the case file. The functions New, View, Edit, Completed, Completed & New, and Print are available. A filter allows completed follow-ups to also be shown.

  • Acquisition percentage shares panel (#50588, #50589)

    • This panel displays the acquisition percentage shares for the case file.

  • Access rights panel (#51216, #49873, #89528) This panel displays the access rights for the case file. The functions New User, New User Group, View, Edit, and Delete are available.

  • Conflict keywords panel (#51222, #49972, #76487)

    • This panel displays the conflict keywords for the case file.
    • The functions New, View, Edit, and Delete are available for conflict keywords.

  • Conflict check panel (#49257, #49974, #66344)

    • The conflict check panel displays the conflict potential and the status of the most recent conflict check.
    • The conflict potential can be changed using the Edit button.
    • The following functions are available for the conflict check: Create manually, Open conflict check, Show results, and Start.

  • Case file hierarchy panel (#66341)

    • This panel displays the case file hierarchy. The functions Edit and Delete are available, as well as a jump to the Case File Hierarchy view.

  • Additional data panel (#49258, #76483)

    • In the case file view, the Additional Data panels are displayed and can be edited by clicking the button in the panel.

  • Billing information panel (49261)

    • This panel displays the billing information for the case file. The functional rights
      • 10100 Case file – Billing information – read
      • 10101 Case file – Billing information – edit now apply only to billing information and no longer to the billing configuration, as this is displayed in separate panels.

  • Billing configuration panel (#49975, #51224, #66337, #66338)

    • This panel displays the billing configuration linked to the case file. The functions Edit, Resulting rates, Agreed rates, and Service catalog are available. The following functional rights have been added for the billing configuration:
      • 10026 Case files – Read billing configuration
      • 10027 Case files – Edit billing configuration
      • 10028 Case files – Create new billing configuration

  • Property lists panel (#51218, #49887)

    • This panel displays the property lists for the case file.

  • Appointments panel (#51219, #49969)

    • This panel displays the appointments for the case file.

  • Case file relationships panel (#51223, #49973)

    • This panel displays the case file relationships for the case file.

  • Case file info panel (#95418)

    • This panel provides a summary of the most important information about the case file — similar to the quick info in the previous case file view.

  • Performance summaries for the case file (#49976, #66063)

    • Performance summaries 1 and 2 for the case file can be accessed via buttons in the ribbon.

  • Copy case file (#50304)

    • When copying case files, a dialog is displayed with the key case file data, allowing it to be adjusted. Associated data objects such as parties and responsible persons are copied in the same scope as before and can be modified after the copy is complete.

  • Case file cover sheet (#49008)

    • In the ribbon, under Documents, there is an option to create a case file cover sheet or open an existing one.

  • Functional right for deleting case files (#49145)

    • The functional right "10025 Case files – delete" is provided for deleting case files.
      • Only case files in LEXolution are deleted, where this is possible.
      • If case files are referenced in invoices, deadlines, bookings, completed conflict checks, or similar records, they can no longer be deleted.

  • The Case File Favorites view has been removed (#66339)

    • The Case File Favorites view has been removed.
    • When the Case Files view is opened, the Favorites setting is active by default, so your selected case file favorites are displayed.
    • Newly created case files are automatically added to case file favorites.

Negative Invoices Without a Preceding Invoice

  • Finalizing invoices with a negative amount (#91992)
    • Invoices with an invoice amount or payment amount less than 0 can be finalized. In revenue distribution, revenues are reduced accordingly.
    • When crediting advance payments, the sum of the credited amounts must not exceed the invoice amount.
  • Handling of negative invoices in billing distribution and revenue distribution (#92613, #92519, #92910)
    • The sign of the original open item amount is compared with the debit/credit indicator of the payment/credit note to determine whether the payment/credit note increases the open item.
      This means:
      • Open item positive and payment/credit note in debit — the open item is reduced;
      • Open item positive and payment/credit note in credit — the open item is increased;
      • Open item negative and payment/credit note in credit — the open item is reduced;
      • Open item negative and payment/credit note in debit — the open item is increased.
      The distribution type is then determined accordingly. If the open item amount increases, distribution is based on the "open" or "agreed" type; otherwise, distribution is based on "paid."
    • The bank statement import uses the same logic.

Crediting Advance Payments in E-Invoices

  • Crediting advance payments in e-invoices as a line item (#89859)
    • Credited advance payments are included in e-invoices as a net line item and reduce the invoice amount taking the applicable tax rate into account. To achieve this, the following fields are populated in the e-invoice: BT-129 Quantity with the value -1, BT-130 with the unit "piece," BT-146 Net price per unit with the credited advance payment amount (net). The net total price BT-131 is calculated as [BT-129] * [BT-146] and reduces the invoice amount. The field BT-153 Description is dynamically populated with the following text: Advance payment from [payment date of the advance payment invoice] for document [invoice number of the advance payment] gross amount [credited gross amount] tax amount [credited tax amount].

Documentation in the Help Center

  • All documentation for LEXolution can now be found in our new stp.one Help Center. (#89464)

    The documentation is organized into:

    • Manual
      • Online help in the most current version
    • Release Notes
      • Release notes per version
    • Technical Information
      • Installation guides
      • Technical documentation
    • Specialist Documents and Information
      • Handouts for use cases

    The documentation can still be accessed directly from the application using the Help key, as before.

Miscellaneous

  • System: General Settings – Scheduled Conflict Check (#89527)
    • In the Conflict Check section, there is a setting called "Start conflict check on schedule." This option must be enabled if conflict checks with the status "Execution required" are to be started automatically. The interval can be set in minutes. After configuration, the server service must be restarted to activate the setting. This option replaces the previous behavior of automatically starting the conflict check when a case file was saved.
  • Case files: Case file register and System: Case file register templates (#70116)
    • Case file register templates are only available when the file system is configured as the document management system.
    • The functional right "4050 – Read case file register templates" has been renamed to "Read case file register" and now applies only to the case file register, rather than also to the case file register templates as before.
    • The functional right "5054 – Read case file register templates" has been newly added for the Case File Register Templates view, so that it can be edited. The functional rights "4051 – Create new case file register templates" and "4053 – Delete case file register templates" have been removed. The user rights of the configured file system apply here.
  • Conflict check: Create new case file from conflict check (#89903)
    • The dialog for creating a case file has been updated to match the Case File Data panel in the Case Files view.
    • The individual dialogs display the free KFC or the created case file in the title.
    • After the case file is created, you can choose in the dialog to switch to the case file view for the newly created case file.

LEXolution.BI

  • Employee dimension: Years of professional experience calculated to the day (#93242)
    • In all employee dimensions, years of professional experience are now calculated to the exact day, always as the difference between today's date and the admission date. This change was made because previously, employees admitted in the same year were shown with the same number of years of experience, even if one was admitted at the beginning of the year and another at the end.
  • Employee dimension: Date of birth in the statistics model (#93244)
    • The date of birth field has been expanded in all employee dimensions within the tabular statistics model. This enables analysis and grouping by this field in Excel and Power BI. The new fields are located under the Professional Data folder within the Lead case handler, HVRA, HVRA Parent Case File, Employee, and Partner dimensions.
  • Invoice component dimension – Invoice number series attribute (#93245)
    • The Number series abbreviation field has been expanded in the Invoice Component dimension within the tabular billing model. This enables analysis and grouping by this field in Excel and Power BI. The new field is located under the Additional Fields

Related to