LEXolution 9.5 Release Notes

LEXolution 9.5 introduces new features, improvements, and fixes for known issues.
The highlights are:

• Salutation and signature image for invoices and correspondence
• ZUGFeRD invoices with the visual component from the finalized invoice document
• Accounting export with attachments for outgoing invoices
• Enhancements and configuration for analyzing conflict check results
• Sending emails via Microsoft Exchange Online

We hope you continue to enjoy using LEXolution — your Septeo LEXolution Team

Important Notes for Updating to Version 9.5.70

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

• LEXolution 9.5.70 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 to ensure the LEXolution update runs smoothly and without interruption.

• LEXolution 9.5.70 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. Downloads for .NET Framework 4.8, the UM, and the common services are available on our official download page.

• Updating STP common services to version 1.6.531 is strongly recommended. You can find this on the official download page.

• When using the central STP User Management and 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. The updates are available on the official download page.

  • STP Usermanagement App Version 1.8.0
  • STP Usermanagement Service Version 1.8.0
  • STP Usermanagement Domain Service Version 1.8.0
  • STP OnPremise Connector 1.8.0

• LEXolution 9.5.70 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.5.70 only supports TLS 1.2 (Transport Layer Security) for Microsoft-based communication interfaces.

• The LEXolution server update (last 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.5.70 requires IKAROS 2022 or higher.

LEXolution.BI

• LEXolution 9.5 requires LEXolution.BI 9.5

ADB Tool for Updating the Reporting Database

• If you are using the ADB Tool, it must also be updated to version 9.5.70 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

• 04/17/2026 Technical Release 9.5.69 (internal)
• 04/28/2026 Technical Release 9.5.70 (internal)
• 05/12/2026 Launch

Changes in Version 9.5.70

• Bug fix in the formatting of ZUGFeRD invoices with the visual component from the finalized invoice document (#101793)
• Changes to the sample application for the REST API

Changes in Version 9.5.69

Salutation and Signature Image for Invoices and Correspondence (#102990)

Salutations and signature images can now be used in invoices and when creating correspondence using the Word Add-In.
In the Salutations and Forms of Address view, salutations can be stored to match the corresponding forms of address. The content controls Recipient: Salutation, Cover Letter: Salutation, and Invoice: Salutation have been added to the Word Add-In for use in invoices and correspondence.
In the Employees view under the Document tab, a signature image can be stored. The content controls Lead Attorney Signature, Attorney Signature, and Attorney 2 Signature have been added to the Word Add-In for use in invoices and correspondence.

ZUGFeRD Invoices with Visual Component from the Finalized Invoice Document (#101793)

A system-wide setting is now available to specify whether the visual component for ZUGFeRD e-invoices is generated from the structured data or from the invoice document.
If Generate from invoice document is selected, the invoice document will be converted into a valid ZUGFeRD PDF if it is not already one, and the structured component will be appended; otherwise, only the structured component is appended during creation. If Generate from structured data (XML) is selected, a ZUGFeRD PDF is created from the invoice's XML data, and the XML data is appended as the structured component.
The ZUGFeRD visual component option can be configured in the General Settings view under the Documents tab.

Accounting Export with Attachments for Outgoing Invoices (#106894)

For accounting exports in DATEV format, it can now be configured so that the attachments for outgoing invoices are exported alongside the corresponding entries in the posting batch. If multiple postings are created for a single invoice, the attachment is only included once. For partial invoices, the document of the collective invoice is exported. The filename is output in the supplementary information for each posting with an exported document in the export file.

In the Export - Formats view, the Include attachments in export option must be enabled for the DATEV export format. When export files are created using this format configuration, attachments for export postings of type Posting with the posting category Debtor Open Item Invoice are retrieved from the configured document management system and saved in a ZIP archive.

Archive filename: Prefix [Date][, User abbreviation]\_[Id]\_[Timestamp]].zip

🛈 Note

In the Export - Settings view, the Export income/expense postings option must not be active, as in that case only payments against invoices will be exported.

Enhancements and Configuration for Analyzing Conflict Check Results (#107541)

Extended filtering options for conflict check results now make it possible to hide certain phonetic matches from the results or to display exactly those matches. Default values can be pre-set for easier use, and changes can be restricted via function rights. The filters No matches against other contact type and No matches against other salutation have been added to suppress matches where the found contact records have either a different contact type or a different salutation. For a reverse check, the filters Only matches against other contact type and Only matches against other salutation have been added to display exactly the hidden set. The function rights 10040 Conflict Check - No matches against other contact type and 10041 Conflict Check - No matches against other salutation can be used to control the use of these filters.

In the General Settings view under the Conflict Check tab, the options No matches against other contact type and No matches against other salutation have been added to set the default values for the Conflict Check Results view when it is opened.

Sending Emails via Microsoft Exchange Online (#80021)

Configuration and Setup

Once configured, emails can be sent via Microsoft Exchange Online. This applies to sending system notifications — such as those generated after creating the reporting database — as well as emails sent by users from views such as Invoice Dispatch. The access credentials can be stored in the server configuration of the Application Server. After restarting the server service, the connection will be available and ready to use. Detailed setup instructions are described in the technical documentation.
During setup, you define so-called channels, each of which is assigned an email address. Emails are sent later via these channels using the stored email address. Depending on how the channels are defined, sending can be configured for central senders, per-location senders, or personal sending.

Signing In to the STP Cloud

To send emails, you must sign in via the STP Cloud menu bar by clicking the button showing the user's initials. If no sign-in is active, -- is displayed. After a successful sign-in, the initials derived from the email address are shown on the sign-in button, and emails can be sent.

Sending Emails

Select the entries to be sent in the object list. After clicking the Send Email button, the Email Dispatch dialog opens, displaying all selected entries from the object list. Sending is done via a previously defined channel in the STP Cloud. The channel determines the sender email address. If a channel with a matching email address exists for the address shown in the Sender column, the channel is automatically filled in.
The Assign Channel button can be used to select alternative channels through which the email will be sent. The Save as Draft Only button creates email drafts that can be edited and sent from the drafts folder of the channel's email address. The email is sent to the recipient when dispatched. The Send Directly button creates and immediately sends the email. The sent email then appears in the sent items of the email address. The Close button closes the dialog. After clicking either Save as Draft Only or Send Directly, the entry in the object list receives the Dispatch Status values Sent and Completed.

🛈 Note

Please verify email delivery in your email client.

Bookmark for the Contact's Notes Field (#103050)

The content control Recipient: Notes is now available for use in the Word Add-In, allowing the contents of the Notes field from the contact (views Person, Organization, Authority) to be displayed when creating documents in Word.

Invoice Subject Extended (#103062)

The Subject field on the invoice has been expanded to support multi-line input. The data is displayed in the Invoice: Subject content control.

Note in Tax Situation Case File Accounts Can Be Edited After Use (#103067)

The Note in Invoice field in the Tax Situation - Case File Accounts view can now be edited after it has been used, allowing the text printed on the invoice to be adjusted without creating a new tax situation.

Improved Error Message When Generating Invoice Documents (#67004)

When generating invoices that include text containing invisible control characters (e.g., in activity descriptions), errors can occur because Word interprets these characters. The error typically only appears when the document is opened. For this reason, error handling has been added to the invoice creation process. If a control character is detected, an error message is displayed indicating an invalid character along with its character code. The text must be cleaned up in order to generate a valid invoice document.

Example The invisible character in the word Secretarial- is normally not visible and causes the errors described above.

Telephone, fax, copy, secretarial, and other office costs

Finalizing an Invoice as a PDF (#107028)

The Finalize invoice as PDF option, which previously had to be set as a database parameter, has been moved to the General Settings view under the Documents tab, so that changes can be made without direct database access. No functional changes have been made.
When this option is enabled, the invoice is created as a PDF document from the invoice draft when it is finalized.

🛈 Note

This option does not need to be enabled in order to create a ZUGFeRD invoice.

E-Invoice: Configuration of the Description in Field BT-154 (#107096)

For the structured component of the e-invoice, it is now possible to configure which elements are used in field BT-154 for hourly line items.
The option Display of invoice line items in e-invoice has been added in the General Settings view under the Documents tab. The field selection provides the following placeholders:

Alphanumeric characters can be used in the formatting. Control characters (e.g., line breaks) are not evaluated. If the field is left empty, the description is displayed.

LEXolution.BI: Statistics Extended with Case File Category (#111808)

In the Statistics model, the Number of Case Files fact has been extended with the Case File Category dimension to enable analysis by this category.

LEXolution.BI: Statistics Extended with Area of Law (#111809)

In the Statistics model, the Number of Case Files fact has been extended with the Case File Category dimension to enable analysis by this category.

LEXolution.BI: FTE Extension for Service Billing (#113459)

A link between the FTE dimension and its validity date from the Employee Statistics fact and the Service Billing model using the business transaction date has been created, enabling combined analysis of revenue and FTE.

LEXolution.BI: Average FTE Key Figure Extended (#114574)

The Statistics model has been extended with the key figure FTE Ø of Ʃ. This key figure calculates the average of the total FTE per employee. This key figure corresponds to the FTE key figure in the multidimensional model.

Access to LEXolution via REST API (#114405)

REST API access to LEXolution has been extended with the REST API Read all scope, making it possible to grant read-only access.

Extended Invoice Data When Creating via REST API (#105219)

The following invoice data fields have been added for invoices in the REST API: - Invoice code - E-invoice active - E-invoice type - LEDES active - Invoice subject

The following endpoints have been extended: - POST /Invoices - PUT Invoices/{id}/Finalize - PUT Invoices/{id}/SetToZeroFlatRate - DELETE Invoices/{id}

The following endpoints have been added to retrieve values for invoice code and e-invoice type: - GET /EInvoiceType - GET /InvoiceCode

Bug Fixes

Bank Statement View: Revenue Distribution Labels Displayed in Wrong Order for "Direct Retainer" Payment Type (#106854)

• Previous behavior
  In the Bank Statement view, for the German interface language, the revenue distribution labels for the "Direct Retainer" payment type were not displayed in the correct order.

• New behavior
  In the Bank Statement view, for the German interface language, the revenue distribution input labels for the "Direct Retainer" payment type are now displayed in the order: Fee / Disbursements / Tax-exempt disbursements.

Broken Link to the Litigation Cost Calculator (#115057)

• Previous behavior
  The link to the litigation cost calculator led to a page that no longer existed.

• New behavior
  The link to the litigation cost calculator has been updated to point to the new page.

Billing Address Displayed Twice When a Fixed Billing Address Is Stored (#67589)

• Previous behavior
  When creating an invoice with a billing recipient and a contact person, where a fixed value was entered in the salutation template of the billing recipient's address data, this value was displayed twice on the invoice because the same salutation template was used for both the billing recipient and the contact person.

• New behavior
  When creating the invoice, the salutation template from the address data is now used for the billing recipient, and the salutation template from the vCard address is used for the contact person. If no vCard address is stored, the global salutation template is used.

LEXolution.BI: No Distribution for Written-Off Tax-Exempt Disbursements with Applied Retainer (#81105)

• Previous behavior
  If all tax-exempt disbursements for an employee were written off and the employee had an applied retainer, no distribution was performed in the Service Billing fact. The distribution did occur in the Revenue fact.

• New behavior
  If all tax-exempt disbursements for an employee are written off and the employee has an applied retainer, a distribution is now performed in the Service Billing fact.

LEXolution.BI: Error with Open Items Where the Outstanding Amount Exceeds the Total Amount (#112818)

• Previous behavior
  If the outstanding amount of an open item was greater than the original total amount, an error occurred and these records were not loaded.

• New behavior
  The ETL has been adjusted so that open items are loaded even when the outstanding amount is greater than the original total amount.

Case File Creation in an Empty Database via REST API Fails (#112454)

• Previous behavior
  When creating case files via REST API using a system user in an empty database, the creation process failed with an error because the system user was not recognized.

• New behavior
  The system user is now identified correctly and case files are created successfully.

Error Message for Case Files with Secondary Currency in Certain Scenarios (#111894)

• Previous behavior
  If the billing configuration for a case file was created first and then a secondary currency was selected for the case file, an error occurred when editing the billing configuration. Invoice drafts could not be created.

• New behavior
  If the billing configuration is created before the secondary currency is set, no error message is displayed. In this case, the secondary currency is not active in the billing configuration. Invoice drafts can be created.
  If an invoice is to be created in a secondary currency, the secondary currency must match in both the case file and the case file's billing configuration.

Bank Statement: Employee Cost Center Not Written During Posting (#114289)

• Previous behavior
  When a posting suggestion of type Payment was created for an imported bank statement entry containing an employee with an assigned cost center, the cost center was not written to the bank statement entry during posting.

• New behavior
  When posting a Payment type posting suggestion for a bank statement entry, the cost center from the employee record is now written to the entry if one is stored there.

Reports 1204 and 1205 Calculate Group Totals Incorrectly in Some Cases (#116281)

• Previous behavior
  In some cases, the group totals per employee were calculated incorrectly in reports 1204 and 1205.

• New behavior
  The group total per employee is now consistently calculated based on the values belonging to that group in all cases.