Release Notes for Lexolution 9.4

With Lexolution 9.4, new features and improvements have been introduced, and known issues have been resolved. The highlights include:

• Fewer validation dialogs during invoicing
• Encryption of configuration files and use of Integrated Security
• Extension of user/employee abbreviations to 8 characters

The STP Lexolution Team wishes you continued success with Lexolution!

Important Notes for Updating to Version 9.4.78

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

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

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

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

• It is strongly recommended to update the STP common services to version 1.6.531. You can find it on the official download page.

• If you are using the central STP User Management and/or 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 required for smooth operation. The updates are available 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 (final step in setup with 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 (usually 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 allow querying of secretarial staff assigned to an employee.

• Lexolution-IRIS-iManage Interface (#110612)

  • When creating file and client workspaces from 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, credit notes, and cancellations, the validation logs have been consolidated into a single dialog with a displayed list. This avoids duplicate validations and improves clarity. Depending on the configuration of e-invoicing and/or LEDES, validations are performed and displayed directly in the log upon finalization.

The process for creating e-invoice and LEDES files has been changed and now occurs independently.

If e-invoicing is configured, after successful validation with no errors, the e-invoice is created in the background and saved in the configured document storage. If an error occurs while creating the file, a log is displayed. The cause can then be fixed and the file recreated. If e-invoicing is configured, this document is considered the relevant invoice, e.g., for sending.

If LEDES invoice creation is enabled, validation occurs directly upon finalization and is displayed in the dialog. The LEDES file is not created automatically. The user must create the LEDES file separately. In this case, as usual, a dialog for post-processing the file can be configured. Due to dialog-driven post-processing and separate transfer of the LEDES file, automatic creation during finalization has been removed.

2.) Extension of User/Employee Abbreviations to 8 Characters (#102743)

In Lexolution, the length of employee and user abbreviations has been extended to 8 characters. This allows the use of 8-character user abbreviations in central user management and synchronization with Lexolution. If Lexolution is not linked to user management, 8-character user abbreviations can be entered in the Users view. All tables using user abbreviations have been updated to display 8-character abbreviations. This affects, for example, all tables with Creator and Editor columns.

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

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

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

This feature allows you to:
* Encrypt password sections in configuration files, * Switch database connections to Integrated Security.

The update does not require you to switch immediately. The application can read both encrypted and unencrypted configuration files.

Several steps are required for the switch. It is recommended to plan the switch independently of an update. Please be sure to read the documentation before use.

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

• This tool allows you to encrypt and decrypt the configuration files of the Lexolution application server and integration services.
• This tool is needed for initial encryption or when making manual changes to the files.
• An update performed with an installer (setup.exe) does not require this tool.
• The tool must be copied by the user into the application directory and removed after use.
• Please refer to the manuals for instructions on using the tool.

3.2) Database Updater Extension (#102745)

• The extended database updater allows you to configure the database connection string. You can choose between logging in with username and password or using integrated security.
• During the update, the configuration is read as before and the configured authentication is used.
• A new section has been added for switching or changing the database connection string, with the following options:
  • After a DB restore (run PostRestore script)
  • Create Windows user login (if not present)
  • Create SQL Server user login
  • Delete old KMSReaderWriter
• The entered login values will be created in the database if not already present and will replace previous login data. Please note that other applications may also access the database and may need to be updated as well.
• 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 instructions on use.

4.) Billing

4.1) E-Invoice: Use Service Date of Each Entry for Invoice Items for Hours and Other Fees (#103053)

When creating e-invoices, the assignment of values for fields BT-134 (start date of billing period) and BT-135 (end date of billing period) has been changed. For hourly items and other fees (if entered in the Other Fees view), fields BT-134 and BT-135 are filled with the service date of the entry.

5.) Other

5.1) Extension of Jumps from the Conflict Check Results View (#103049)

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

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

Starting January 28, 2026, current data can only be retrieved from the new address. Lexolution 9.4.78 supports the new download for the UK sanctions list.

6.) Lexolution.BI

6.1) Calculate the “Old OPOS” Metric by Invoice Date (#105240)

In the Fact Billing module, the calculation of invoice age can now be configured for the following date values, instead of always using the service date: * Invoice date * Service date

Configuration is done in SSIS_Configuration with the parameter “OPOSAlterLeistungrechnung” and the values “Leistungsdatum” (service date) or “Rechnungsdatum” (invoice date). The default is service date.

6.2) New Metric “Service Recorded X Days Later” (#105243)

The billing module has been extended with the metric “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 Contacts Views, the Number of Participations in Files Is Not Displayed Correctly in Certain Cases (#98507)

• Previous behavior
  • In the Persons, Authorities, and Organizations views, the object list column for participations and the quick info considered file access rights, so values were not identical for all users.
• New behavior
  • In the Persons, Authorities, and Organizations views, the object list column for participations and the quick info now display the number of participations without considering file access rights. Note that in the object list, the number of participations is counted without considering the type of participation, and in the quick info, files are shown by participation type. In certain cases, e.g., if the same participation type is used twice for the same contact, the contact is only counted once in the quick info.

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
  • The 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
  • Despite a configured interface to NOAH and the necessary user rights, the button to create a case was not displayed.
• New behavior
  • With a configured interface to NOAH and the necessary user rights, the button to create a case in NOAH is now displayed.

7.4) Interface: VAT Identification Check Returns an Error (#108721)

• Previous behavior
  • Previously, VAT identification was checked via the XMLRPC interface. This interface is no longer supported by the tax authorities and returns an error message.
• New behavior
  • The VAT identification check is now performed via a REST API from the tax authorities and returns 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 file language was different from the system language and no job title was defined for the employee in the file language.
• New behavior
  • In the Invoice Dispatch and Reminders views, when sending the email, the employee's job title in the file language will be used if it has been defined. If no job title is defined in the file language, the configured system language will be used.

7.6) Navigation: Error messages when using Back in navigation (#94775)

• Previous behavior
  • If the filter in the object list was activated in certain views and no data was displayed in the object list, pressing the "Back" button in the ribbon would display an error.
• New behavior
  • If the filter is activated in the object lists and no data is displayed in the object list, no error will be shown when the "Back" button in the ribbon is pressed.

7.7) Lexolution.BI: Fact Revenue - Metrics with Partner / Employee are always shown by department (#104717)

• Previous behavior
  • A bug was fixed that caused the metrics calculation to always use the department assignment instead of the regular partner/employee assignment.
• New behavior
  • The calculation of metrics has been adjusted so that separate metrics are shown for the department. The standard metrics still use the partner/employee assignment.

7.8) Lexolution.BI: In the performance accounting, fully written-off services are not included in the OPOS metric (#104962)

• Previous behavior
  • Invoices with fully written-off services were not included in the OPOS metric for services. The issue was that service status 4 (not billable) was ignored in the OPOS calculation, even though there was an invoice amount.
• New behavior
  • Service status 4 is now included for fully written-off services with a flat amount (invoice amount not equal to 0).

7.9) Fact Times - Metrics with Partner / Employee are always shown by department (#105546)

• Previous behavior
  • A bug was fixed that caused the metrics calculation to always use the department assignment instead of the regular partner/employee assignment.
• New behavior
  • The calculation of metrics has been adjusted so that separate metrics are shown for the department. The standard metrics still use the partner/employee assignment.

7.10) Billing distribution in the account statement does not fully distribute by reason for canceled invoices (#108249)

• Previous behavior
  • If a paid invoice is canceled and the payment is then reallocated in the account statement view, the distribution was not only by the "Paid" option but also by the "Credited" option from the cancellation. As a result, the suggested amount for the billing distribution was not correct 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 cases.
• New behavior
  • If a paid invoice is canceled and the payment is then reallocated in the account statement view, the distribution is now only by the "Paid" option.