Release Notes LEXolution 9.5

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 including attachments for outgoing invoices
• Extensions and configuration for analyzing conflict check results
• Sending emails via Microsoft Exchange Online

We hope you continue to enjoy 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 the 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 a current LEXolution.DMS or winsolvenz.p4 installation is present on the system, the C++ Runtime is already installed. Downloads for .NET Framework 4.8 and for the UM and common services can be found 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 centralized STP User Management and when using 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 can be found 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.5.70 and LEXolution.BI are approved for use with

  • Microsoft SQL Server from version 2016 up to and 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 (the final step in the setup, triggered by clicking the Start LEXolution Server button) may take over 15 minutes when updating from a version older than 6.4 on larger LEXolution databases containing millions of recorded entries (time and expense records).

• LEXolution 9.5.70 requires IKAROS 2022 or higher.

LEXolution.BI

• LEXolution 9.5 requires LEXolution.BI 9.5

ADB Tool for Updating the Analytics Database

• If you use 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 corresponding to the forms of address can be stored. To output these in invoices and correspondence, the content controls Recipient: Salutation, Cover Letter: Salutation, and Invoice: Salutation have been added to the Word Add-In.
In the Staff view, under the Document tab, a signature image can be stored. To output these in invoices and correspondence, the content controls Lead Attorney Signature, Attorney Signature, and Attorney 2 Signature have been added to the Word Add-In.

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

For e-invoices, a system-wide setting can now be configured to determine whether the visual component for the ZUGFeRD format 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 data will be appended; otherwise, only the structured data 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 to include the attachments for outgoing invoices 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 from the consolidated invoice is exported. The filename is output in the additional information for each posting that includes an exported document in the export file.

In the Export - Formats view, the Include attachments on 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 Accounts Receivable Open Item Invoice are retrieved from the configured document management system and saved to a ZIP archive.

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

🛈 Note

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

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

With the expanded filtering options for conflict check results, it is now possible to hide specific phonetic matches from the results or display exactly those matches. Default values can be pre-configured for ease of use, and changes can be restricted via function permissions. To hide certain matches, the filters No matches against different contact type and No matches against different salutation have been added. These suppress matches where the found contact records have either a different contact type or a different salutation. For a cross-check, the filters Only matches against different contact type and Only matches against different salutation have been added to display exactly the hidden set of results. The use of these filters can be controlled via the function permissions 10040 Conflict Check - No matches against different contact type and 10041 Conflict Check - No matches against different salutation.

In the General Settings view, under the Conflict Check tab, the options No matches against different contact type and No matches against different 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 the sending of system notifications — such as those sent after the analytics database is created — as well as to emails sent by users from views such as Invoice Dispatch. 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 this setup, you define so-called channels, each of which is assigned an email address. These channels, together with their associated email addresses, are then used for sending. Depending on how the channels are defined, sending can be configured for central senders, senders per location, 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 displaying the user's initials. If no sign-in is active, -- is displayed. After a successful sign-in, the user's initials derived from their email address appear on the sign-in button, and emails can then be sent.

Sending Emails

In the object list, select the entries you want to send. 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 is available for the address shown in the Sender column, the channel is filled in automatically.
Using the Assign Channel button, you can alternatively select other channels through which the email will be sent. The Create 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 upon dispatch. The Send Directly button creates the email and sends it immediately. After sending, the email appears in the sent items of the email address. The Close button closes the dialog. After clicking either Create Draft Only or Send Directly, the entry in the object list receives the Dispatch Status of Sent and Completed.

🛈 Note

Please verify that the email was sent in your email client.

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

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

Invoice Subject Line 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 Matter — Case File Accounts Can Be Edited After Use (#103067)

The Note on Invoice field in the Tax Matter - Case File Accounts view can now be edited after it has already been used, making it possible to adjust the text printed on the invoice without having to create a new tax matter.

Improved Error Message When Creating Invoice Documents (#67004)

When generating invoices that contain text with 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 not normally 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 parameter in the database, 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, finalizing an invoice will convert the invoice draft document into a PDF.

🛈 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 to the General Settings view under the Documents tab. The following placeholders are available in the field selector:

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 reporting by that dimension.

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 reporting by that dimension.

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

A link has been created between the FTE dimension and its validity date from the Staff Statistics fact and the Service Billing model, using the transaction date, to enable reporting that combines revenue and FTE data.

LEXolution.BI: Extension of the Average FTE Metric (#114574)

The Statistics model has been extended with the metric FTE Ø of Ʃ. This metric calculates the average of the sum of FTE per staff member. This metric corresponds to the FTE metric in the multidimensional model.

Access to LEXolution via REST API (#114405)

REST API access to LEXolution has been extended with the scope REST API Read all. Using this scope makes 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 calls have been extended: - POST /Invoices - PUT Invoices/{id}/Finalize - PUT Invoices/{id}/SetToZeroLumpSum - DELETE Invoices/{id}

The following calls have been added to retrieve values for invoice code and e-invoice type: - GET /E-InvoiceType - GET /InvoiceCode

Bug Fixes

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

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

• New behavior
  In the Bank Statement view, when the interface language is set to German, the revenue distribution input labels for the "Direct Retainer" payment type are now displayed in the correct order: Fees / Expenses / Tax-Exempt Expenses.

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 address data for the billing recipient's contact, that 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 Expenses with an Applied Retainer (#81105)

• Previous behavior
  When all tax-exempt expenses for a staff member were written off and the staff member had an applied retainer, no distribution was performed in the Service Billing fact. The distribution did occur in the Revenue fact.

• New behavior
  When all tax-exempt expenses for a staff member are written off and the staff member has an applied retainer, a distribution is now also performed in the Service Billing fact.

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

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

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

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

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

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

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

• Previous behavior
  If the billing configuration for a case file was created first and a secondary currency was then selected in 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 appears. 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: Staff Cost Center Not Written During Posting (#114289)

• Previous behavior
  When a posting suggestion of payment type Payment was created for an imported bank statement entry — where a staff member with an assigned cost center was entered — 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 is now taken from the staff member, provided one is stored there.

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

• Previous behavior
  In some cases, reports 1204 and 1205 did not calculate the group totals per staff member correctly.

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