LEXolution 9.4 Release Notes

LEXolution 9.4 introduces new features, improvements, and bug fixes. The highlights are:

• Fewer validation dialogs during invoicing
• Encryption of configuration files and support for Integrated Security
• User/employee abbreviation extended to 8 characters

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

Important Notes for Updating to Version 9.4.78

• Major releases, feature packs, and service packs are cumulative and always contain the complete current version.

• LEXolution 9.4.78 requires Microsoft .NET Framework 4.8 on both the server and client sides.

• If not already installed, install .NET Framework 4.8 in advance (e.g., during a scheduled maintenance window) on the LEXolution server and all clients to ensure the LEXolution update runs smoothly and without interruption.

• LEXolution 9.4.78 requires Microsoft Visual C++ Redistributables 2015–2022 (x64 and x86) – 14.30.30704 on the client side. If a current LEXolution.DMS or winsolvenz.p4 installation is present on the system, the C++ runtime is already installed.

• An update of STP Common Services to Version 1.6.531 is strongly recommended. You can find this on the official download page.

• If you are using the centralized STP User Management or any cloud services (e.g., New Matter Intake, Time Mobile), it is mandatory to update the following services to the specified versions. The new versions include important improvements to enhance the stability of the STP Cloud and are therefore required for smooth operation. You can find the updates on the official download page.

  • STP User Management App Version 1.8.0
  • STP User Management Service Version 1.8.0
  • STP User Management Domain Service Version 1.8.0
  • STP OnPremise Connector 1.8.0

• LEXolution 9.4.78 and LEXolution.BI are approved for:

  • Microsoft SQL Server from version 2016, including the latest version SQL Server 2025
  • Windows 11, Windows Server 2022, and Windows Server 2025
  • Office 2021, Office 2024, and Office 365

• Version 9.4.78 only supports TLS 1.2 (Transport Layer Security) for Microsoft-based communication interfaces.

• The LEXolution server update (the final step in the setup, using the Start LEXolution Server button) may take several minutes for larger LEXolution databases.

• LEXolution 9.4.78 requires IKAROS 2022 or later.

LEXolution.BI

• LEXolution 9.4.78 requires LEXolution.BI 9.4

ADB Tool for Updating the Reporting Database

• If you use the ADB Tool, it must also be updated to version 9.4.78 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).

Version History

• 01/23/2026 Technical Release 9.4.77 (internal)
• 02/06/2026 Technical Release 9.4.78 (internal)
• 02/19/2026 Launch

Changes in Version 9.4.78

• REST API Extension (#110350)

  • The REST API has been extended to support querying the secretarial staff assigned to an employee.

• LEXolution-IRIS-iManage Interface (#110612)

  • When creating case file and client workspaces from within LEXolution, access rights are now set to full access by default.

Changes in Version 9.4.77

1.) Fewer Validation Dialogs During Invoicing (#80020)

When finalizing invoices, cancellations, and credit notes, the validation logs have been consolidated into a single dialog displaying a combined list. This eliminates duplicate validations and improves clarity. Depending on the configuration of e-invoicing and/or LEDES, validations are performed and displayed directly in the log at the time of finalization.

The process for generating e-invoice and LEDES files has been changed so that each is now handled independently.

When e-invoice generation is configured, the e-invoice is created in the background after a successful validation with no errors and saved to the configured document storage location. If an error occurs during file creation, a log is displayed. You can then fix the issue and regenerate the file. When e-invoicing is configured, this document is treated as the authoritative invoice — for example, for sending purposes.

If LEDES invoice generation is enabled, validation takes place directly upon finalization and is shown in the dialog. The LEDES file is not created automatically. The user must generate the LEDES file separately. In this case, a dialog for post-processing the file can be configured as usual. Due to the dialog-driven post-processing and the separate transfer of the LEDES file, automatic generation has been removed from the finalization workflow.

2.) User/Employee Abbreviation Extended to 8 Characters (#102743)

In LEXolution, the length of both the employee and user abbreviation has been extended to 8 characters. This extension also makes it possible to use 8-character user abbreviations in the centralized User Management and synchronize them with LEXolution. If LEXolution is not linked to User Management, 8-character user abbreviations can be entered directly in the Users view. All tables that use the user abbreviation have been updated to display 8-character abbreviations — this applies, for example, to all tables with "Created by" and "Edited by" columns.

In the Employees view, the employee abbreviation input field has been extended to 8 characters. The employee abbreviation column in the Invoice Draft Overview report has also been extended.

The data importer has been updated to support 8-character employee and user abbreviations.

3.) Encryption of Configuration Files and Improvements for Integrated Security (#89468)

This feature provides the ability to:
* Encrypt password sections in configuration files, * Switch the database connection to Integrated Security.

This update does not require migration. The application can read both encrypted and unencrypted configuration files.

Several steps are required to make the switch. It is recommended to plan the migration independently of an update. Before proceeding, we strongly recommend reviewing the documentation.

3.1) Tool for Encrypting and Decrypting Configuration Files (#89470)

• This tool can be used to encrypt and decrypt the configuration files for the LEXolution application server and Integration Services.
• This tool is needed for the initial encryption or when making manual changes to the files.
• An update performed using an installer (setup.exe) does not require this tool.
• The tool must be copied by the user into the application directory and removed again after use.
• Please refer to the manuals for instructions on how to use the tool.

3.2) Database Updater Extension (#102745)

• The extended database updater allows you to configure the database connection string. You can choose between authenticating with a username and password or using Integrated Security.
• During an update, the configuration is read as before and the configured authentication method is used.
• A new section has been added for switching or modifying the database connection string, with the following options:
  • After a DB restore (run PostRestore script)
  • Create Windows user login (if not already present)
  • Create SQL Server user login
  • Delete old KMSReaderWriter
• The login credentials entered will be created on the database if they do not already exist, replacing any previous login data. Please note that other applications may also access the database and may need to be updated accordingly.
• Optionally, after changing the configuration, you can delete the previous database access via KMSReaderWriter.
• The database updater is included in the LEXolution Server setup.
• Please refer to the manuals for usage instructions.

4.) Billing

4.1) E-Invoice: Use the Service Date of Individual Items for Invoice Line Items for Hours and Additional Fees (#103053)

When generating e-invoices, the assignment of values for fields BT-134 (Invoicing Period Start Date) and BT-135 (Invoicing Period End Date) has been changed. For hourly line items and additional fees — when these have been recorded in the Additional Fees view — fields BT-134 and BT-135 are now populated with the service date of the respective line item.

5.) Miscellaneous

5.1) Extended Navigation from the Conflict Check Results View (#103049)

In the Conflict Check Results view, for rows with matches involving case file participants, buttons have been added in the participant details to open the contact and the contact information.

5.2) Change to the UK Sanctions List Download (#109161)

As of January 28, 2026, current data will only be available from a new address. LEXolution 9.4.78 supports the updated UK Sanctions List download.

6.) LEXolution.BI

6.1) Calculate the "Age of Open Items" KPI by Invoice Date (#105240)

In the Billing fact, the calculation of invoice age can now be configured to use the following date values, rather than always defaulting to the service date: * Invoice Date * Service Date

The configuration is done in SSIS_Configuration using the parameter "OPOSAlterLeistungrechnung" with the values "Leistungsdatum" (service date) or "Rechnungsdatum" (invoice date). The default value is service date.

6.2) New KPI: "Service Recorded X Days Later" (#105243)

The Billing fact has been extended with the new KPI "Service Recorded X Days Later." This calculates the difference between the "Service Date" and the "Recorded On" date.

7.) Bug Fixes

7.1) In the Contact Views, the Number of Case File Involvements Is Not Displayed Correctly in Certain Cases (#98507)

• Previous Behavior
  • In the Persons, Authorities, and Organizations views, the object list's Involvements column and the quick info tooltip took case file access rights into account, meaning the values were not identical for all users.
• New Behavior
  • In the Persons, Authorities, and Organizations views, the object list's Involvements column and the quick info tooltip now display the number of involvements without taking case file access rights into account. Note that in the object list, the number of involvements is counted without regard to involvement type, while the quick info tooltip displays case files by involvement type. In certain scenarios — for example, when the same involvement type is used twice for the same contact — the contact is counted only once in the quick info tooltip.

7.2) Billing: RVG as of 06/01/2025 (#107233)

• Previous Behavior
  • The settlement fee 1000 was suggested as a general fee of 1.5. The split into No. 1 and No. 2 was missing.
• New Behavior
  • Settlement fee 1000 is now split into No. 1 at 1.5 and No. 2 at 0.7.

7.3) NOAH Interface: Button to Create a Case Cannot Be Activated (#108031)

• Previous Behavior
  • Even with the NOAH interface configured and the required user permissions in place, the button to create a case was not displayed.
• New Behavior
  • With the NOAH interface configured and the required user permissions in place, the button to create a case in NOAH is now displayed correctly.

7.4) Interface: VAT ID Validation Returns an Error (#108721)

• Previous Behavior
  • Previously, VAT ID validation was performed via the XMLRPC interface. This interface is no longer supported by the tax authorities and was returning an error message.
• New Behavior
  • VAT ID validation is now performed via a REST API provided by the tax authorities and is returning results again.

7.5) Invoice Dispatch and Reminders Views (#107592)

• Previous Behavior
  • In the Invoice Dispatch and Reminders views, an error was displayed when sending documents by email if the case file language differed from the system language and no profession had been defined for the employee in the case file language.
• New Behavior
  • In the Invoice Dispatch and Reminders views, when sending an email, the employee's profession matching the case file language is used if one has been defined. If no profession is defined in the case file language, the configured system language is used instead.

7.6) Navigation: Error Messages When Using the Back Button (#94775)

• Previous Behavior
  • In certain views, if the object list filter was active and no data was displayed in the object list, pressing the "Back" button in the ribbon caused an error.
• New Behavior
  • When the filter is active in an object list and no data is displayed, pressing the "Back" button in the ribbon no longer causes an error.

7.7) LEXolution.BI: Revenue Fact – KPIs with Partner/Employee Are Always Reported by Department (#104717)

• Previous Behavior
  • A bug was fixed that caused the KPI calculation to always use the department assignment instead of the regular partner/employee assignment.
• New Behavior
  • The KPI calculation has been updated so that separate KPIs are reported for the department. The standard KPIs continue to use the partner/employee assignment.

7.8) LEXolution.BI: Fully Written-Off Services Are Not Included in the OPOS KPI in the Billing Fact (#104962)

• Previous Behavior
  • Invoices with fully written-off services were not included in the billing OPOS KPI. The issue was that service status 4 (non-billable) was being ignored in the OPOS calculation, even when an invoice amount was present.
• New Behavior
  • Service status 4 is now taken into account for fully written-off services with a flat-rate amount (invoice amount not equal to 0).

7.9) Time Fact – KPIs with Partner/Employee Are Always Reported by Department (#105546)

• Previous Behavior
  • A bug was fixed that caused the KPI calculation to always use the department assignment instead of the regular partner/employee assignment.
• New Behavior
  • The KPI calculation has been updated so that separate KPIs are reported for the department. The standard KPIs continue to use the partner/employee assignment.

7.10) Billing Distribution in the Account Statement Does Not Fully Distribute by Cause for Canceled Invoices (#108249)

• Previous Behavior
  • When a paid invoice was canceled and the payment was subsequently reassigned in the Account Statement view, the distribution was applied not only using the "Paid" option but also using the "Credited" option from the cancellation. As a result, the suggested amount in the billing distribution was incorrect in certain cases, and the entry in the Account Statement view could not be saved without manual adjustment. This occurred when the payment was distributed across multiple accounts or tax scenarios.
• New Behavior
  • When a paid invoice is canceled and the payment is subsequently reassigned in the Account Statement view, distribution is applied using only the "Paid" option.