Release Notes for Lexolution 9.5

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

• Greeting line and signature image for invoices and correspondence
• ZUGFeRD invoices with a visible component of the finalized invoice document
• Booking export with export of outgoing invoice receipts
• Enhancements and configuration options for analyzing conflict check results
• Sending emails via Microsoft Exchange Online

We hope you continue to enjoy using Lexolution. Best regards, your Septeo Lexolution Team

Important Notes for Updating to Version 9.5.70

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

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

• Lexolution 9.5.70 requires the Microsoft Visual C++ Redistributables 2015-2022 (x64 and x86) – 14.30.30704 on the client side. If your system already has a current Lexolution.DMS or winsolvenz.p4 installation, the C++ runtime is already present. You can find downloads for the .NET Framework 4.8 and for UM and the common services on our official download page.

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

• If you use 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 therefore required for smooth operation. 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.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 (final step in setup with the Start Lexolution Server button) may take over 15 minutes when updating from a version older than 6.4, especially with large Lexolution databases containing millions of recorded entries (times, expenses).

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

• 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

• Fixed formatting issue with ZUGFeRD invoices with visible component of the finalized invoice document (#101793)
• Changes to the sample application for the REST API

Changes in Version 9.5.69

Greeting Line and Signature Image for Invoices and Correspondence (#102990)

In invoices and when creating correspondence using the Word Add-In, greeting lines and signature images for signatures can now be used.
In the Letter Salutations and Greeting Lines view, you can store greeting lines to match the salutation formulas. For output in invoices and correspondence, the Word Add-In now includes the content controls Recipient: Greeting Line, Letter: Greeting Line, and Invoice: Greeting Line.
In the Employees view, under the Document tab, you can store a signature image for the signature. For output in invoices and correspondence, the Word Add-In now includes the content controls HVRA-Signature, RA-Signature, and RA2-Signature.

ZUGFeRD Invoices with Visible Component of the Finalized Invoice Document (#101793)

For e-invoices, you can set system-wide whether the visible component for the ZUGFeRD format is created from the structured part or from the invoice document.
If Create from Invoice Document is selected, the invoice document will be converted into a valid ZUGFeRD PDF and the structured part attached if it is not already a valid ZUGFeRD PDF; otherwise, only the structured part is attached when creating. If Create from Structured Data (xml) is selected, a ZUGFeRD PDF is created from the invoice's XML data and the XML data is attached as the structured part.
The ZUGFeRD Visible Component option can be set in the General Settings view under the Documents tab.

Invoice Sending via ComCenter (Exchange Online) (#80021)

Starting with Lexolution 9.5, it is possible to send emails (invoice delivery) via our Legal Communication Center, which then forwards them to Exchange Online.
Authentication uses a component based on the Microsoft Authentication Library (MSAL). Sending is available in the Invoice Sending view.

Booking Export with Outgoing Invoice Receipts (#106894)

For booking exports in DATEV format, you can configure the export so that the receipts for outgoing invoices are exported along with the bookings in the booking batch. If multiple bookings are created for one invoice, the receipt is only added once. For partial invoices, the document for the collective invoice is exported. In the export file, the file name is included in the additional information for each booking with an exported document.

In the Export - Formats view, for the DATEV export format, the Option Export Receipts must be activated. When export files are created with this format configuration, for export bookings of type Booking with booking type Debtor OPOS Invoice, the receipts are retrieved from the configured document management system and saved in a zip data archive.

Archive file name: Batch [Date][, User Initials]\_[Id]\_[Timestamp]].zip

🛈 Note

In the Export - Settings view, the Export EA Bookings option must not be active, as in this case only payments on invoices are exported.

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

With the expanded filtering options for conflict check results, you can now hide or specifically display certain phonetic matches. For easier use, default values can be preset and changes can be restricted by functional permissions. To hide matches, the filters No matches against other contact type and No matches against other salutation have been added. This means matches are not shown if the found contact records have a different contact type or a different salutation. For cross-checking, the filters Only matches against other contact type and Only matches against other salutation have been added to display exactly the hidden set. The functional permissions 10040 Conflict Check - No matches against other contact type and 10041 Conflict Check - No matches against other salutation 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 opening it.

Sending Emails via Microsoft Exchange Online (#80021)

Configuration and Setup

After configuration, emails can be sent via Microsoft Exchange Online. This applies to sending system notifications, such as after creating the reporting database, as well as sending emails by users from views like Invoice Sending. Login credentials can be stored in the application server's server configuration. After restarting the server service, the connection is available and can be used. Detailed setup instructions are provided in the technical documentation.
During setup, you define so-called channels to which an email is assigned. Emails are sent via these channels using the stored email address. Depending on how the channels are defined, sending can be set up for central senders, senders by location, or personal sending.

Logging in to the STP Cloud

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

Sending Emails

In the object list, select the entries you want to send. After clicking the Send Email button, the Email Sending dialog appears with all selected entries from the object list. Sending is done via a previously defined channel in the STP Cloud. The channel determines the sender's email address. If a channel with a matching email address exists for the sender column, the channel is filled in.
With the Assign Channel button, you can alternatively select other channels to send the email. With the Create Draft Only button, email drafts are created, which can be edited and sent from the draft folder of the channel's email address. The email is sent to the recipient when you send it. With the Send Directly button, the email is created and sent immediately. The sent email is then displayed under the sent objects for the email address. The Close button closes the dialog. After clicking Create Draft Only or Send Directly, the entry in the object list receives the Send Status Sent and Completed.

🛈 Note

Please check the email delivery in your email program.

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

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

Expanded Invoice Subject (#103062)

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

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

The Note in Invoice field in the StSachV - File Accounts view can now be edited after use, allowing you to adjust the text to be printed on the invoice without having to create a new tax case.

Improved Error Message When Creating Invoice Documents (#67004)

When creating invoices and using texts with invisible control characters (e.g., in activity descriptions), errors may occur because Word interprets these control characters. The error usually appears when opening the document. For this reason, error handling has been added when creating invoices. If a control character is found, an error message with "invalid character" and the character code is displayed. The text must be cleaned up to create a valid invoice document.

Example The invisible character in the word Sekretariats- is usually not displayed and leads to the errors mentioned above.

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

Finalizing an Invoice as PDF (#107028)

The option Finalize invoice as PDF, which previously had to be set as a parameter in the database, has now been added to the General Settings view under the Documents tab, so changes can be made without accessing the database. No functional changes have been made.
If this option is enabled, finalizing a draft invoice will create the invoice as a PDF document.

🛈 Note

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

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

For the structured part of the e-invoice, you can configure for hourly positions which components are used in field BT-154.
In the General Settings view under the Documents tab, the option Display invoice items E-Invoice has been added. The following placeholders are available in the field selection for

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

Lexolution.BI: Statistics Extended by File Category (#111808)

In the Statistics model, the fact "Number of Files" has been extended by the dimension "File Category" to allow for evaluation by this dimension.

Lexolution.BI: Statistics Extended by Legal Area (#111809)

In the Statistics model, the fact "Number of Files" has been extended by the dimension "File Category" to allow for evaluation by this dimension.

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

A link has been created between the FTE dimension and its validity date from the Employee Statistics fact to the Service Billing model using the business transaction date, allowing for evaluations that connect revenue and FTE.

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 sum of FTE per employee. This metric matches the FTE metric in the multidimensional model.

Access to Lexolution via REST API (#114405)

Access to Lexolution via REST API has been extended with the scope REST API Read all. This allows granting read-only access.

Extension of Invoice Data When Creating via REST API (#105219)

The following invoice data has 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}/SetToZeroFlatRate - DELETE Invoices/{id}

To determine the values for invoice code and e-invoice type, the following calls have been added: - GET /E-InvoiceType - GET /InvoiceCode

Bug Fixes

Account Statement View: For payment type "Direct Advance," the label for revenue distribution is incorrect (#106854)

• Previous behavior
  In the account statement view, for the German language, the labels for revenue distribution for the payment type "Direct Advance" were not displayed in the correct order.

• New behavior
  In the account statement view, for the German language, the labels for entering revenue distribution for the payment type "Direct Advance" are now displayed in the order Fee / Expenses / Tax-free Expenses.

Link to Process Cost Calculator Broken (#115057)

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

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

**Invoice address is displayed twice when a fixed invoice address is stored_(#67589)_**

• Previous behavior
  If an invoice is created with an invoice recipient and a contact person, and a fixed value is entered in the salutation template of the invoice recipient's contact address data, this value is displayed twice in the invoice because the salutation template was used for both the invoice recipient and the contact person.

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

Lexolution.BI: No distribution for written-off tax-free expenses with applied advance (#81105)

• Previous behavior
  If all tax-free expenses for an employee were written off and the employee had an applied advance, no distribution was made in the Service Billing fact. The distribution was made in the Revenue fact.

• New behavior
  If all tax-free expenses for an employee are written off and the employee has an applied advance, a distribution is now made in the Service Billing fact.

Lexolution.BI: Error with open items where the open amount is greater than the total amount (#112818)

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

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

Creating files in an empty database via REST API fails (#112454)

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

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

Error message for files with secondary currency in certain cases (#111894)

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

• New behavior
  If the billing configuration is created before setting the secondary currency, there is no longer an error message. In this case, 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 in the file and in the file's billing configuration must match.

Account Statement: Employee cost center not written when posting (#114289)

• Previous behavior
  If a booking proposal with the payment type Payment was created in an imported account statement, and an employee with an assigned cost center was entered, the cost center was not entered in the account statement entry when posting.

• New behavior
  When posting the booking proposal of the payment type Payment for an account statement entry, the cost center from the employee is now entered if it is stored there.

Reports 1204 and 1205 do not calculate group totals correctly in some cases (#116281)

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

• New behavior
  The group total per employee is now calculated identically in all cases using the values belonging to the group.