Release Notes for Lexolution 9.6

With Lexolution 9.6, new features and improvements have been introduced, and known issues have been fixed.
The highlights are:

• Apply negative outstanding items to an invoice
• Transfer/retrieve appointments, deadlines, and reminders to Exchange Online as calendar entries via MS Graph API
• Create export bookings with location cost centers

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

Important Notes for Updating to Version 9.6.77

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

• Lexolution 9.6.77 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.6.77 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. You can find downloads for the .NET Framework 4.8 and for UM and common services on our official download page.

• If you use the central STP User Management and cloud services (e.g., New Matter Intake, Time Mobile), it is absolutely necessary 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. You can find the updates on the official download page.

  • STP Common.Service Version 1.6.530.0 (or higher)
  • STP UserManagement Version 1.11.0
  • STP OnPremise Connector Version 1.10.0

• Lexolution 9.6.77 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.6.77 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 on large Lexolution databases with millions of recorded entries (times, expenses).

IKAROS

• Lexolution 9.6.77 requires IKAROS 2022 or higher.

Lexolution.BI

• Lexolution 9.6.77 requires Lexolution.BI 9.6

ADB Tool for Updating the Reporting Database

• If you use the ADB Tool, the tool must also be updated to version 9.6.77 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

• 07/17/2026 Technical Release 9.6.74 (internal)
• 07/22/2026 Technical Release 9.6.76 (internal)
• 08/13/2026 Launch 9.6.76
• 08/18/2026 Release 9.6.77 (bug fix)

Changes in Version 9.6.77

Error with Conflict Check Result, Invoice Dispatch, and Dunning List (#126052)

• Previous behavior
  When opening the views Files > Conflict Check > Result View, Billing > Invoice Dispatch, and Accounting > Dunning List, an error message appeared and the respective view could not be opened.

• New behavior
  These views can now be opened again.

Changes in Version 9.6.76

Merge Fields Gross Total and Fee: Advance Payment Items Not Working with Batch Invoices (#123767)

• Previous behavior
  When creating batch invoices, the Gross Total merge field would sometimes display Merge Field Error if there were no outstanding items. When creating credit notes and cancellations, the Fee: Advance Payment Items merge field would sometimes display Merge Field Error if not all batch invoice data was present.

• New behavior
  The Gross Total and Fee: Advance Payment Items merge fields now display data as expected.

QR Invoice (Switzerland) and EPC Code Merge Fields Did Not Use the Due Amount (#123637)

• Previous behavior
  With the introduction of the Due Amount after applying outstanding items, the following merge fields did not correctly display the amount to be paid: Invoice: Payment Amount, Invoice: Payment Amount (formatted), Invoice: Payment Amount (decimal), Invoice: Payment Amount (whole), Invoice: Payment Amount, Invoice: QR Code, Invoice: ESR Coding Line, and EPC Code.

• New behavior
  These merge fields now use the Due Amount as the amount to be paid when outstanding items are applied.

Changes in Version 9.6.74

Apply Negative Outstanding Items to an Invoice (#89717)

This feature allows you to reduce the due amount on an invoice by applying overpayments.

In the billing view, under Invoice Items and Applications, the Apply Outstanding Items function is available. Access to this function is controlled by the permission 7084 Invoice Drafts - Invoice Items - Apply Outstanding Items.

In the selection dialog, you can choose filtered outstanding items to apply if: - the outstanding item is overpaid and therefore negative, - the invoice recipient is the same, - it is an outstanding item in the base currency, - outstanding items are from partial invoices.

The following cannot be applied: - outstanding items from advance invoices, - outstanding items from split invoices, - outstanding items from a cumulative origin.

For each Applied Outstanding Item, an invoice item is added at the end of the invoice to reduce the payment amount. After that, an Amount Due invoice item is automatically added. When adding, the full amount of the outstanding item is applied, but the amount can be manually reduced.

The current outstanding amount is displayed in detail. With the Apply Amount button, this amount can be transferred to the Amount field to update the amount to be applied in the invoice item if there have been changes in the meantime.

When finalizing the invoice, it is validated that the entered amount (negative) is not greater than the remaining outstanding amount (negative).

Booking When Finalizing the Invoice

The transfer of the outstanding item to the invoice is done via the configured account with the account function Clearing Account in the Account Functions view.

Canceling Invoices (#108053)

When canceling invoices, any booked Remainder to Foreign Currency is not canceled. A negative outstanding item is created again.

Merge Fields

The Invoice Items merge field has been updated for the types Applied Outstanding Item and Amount Due to adjust the formatting of invoice documents. If these types are not used, the Other Items invoice item is used for display.
The Fee: Advance Payment Items merge field has been updated to include lines for Applied Outstanding Item and Amount Due, to supplement the Gross Total merge field and enable output.

The invoice draft overview report has been expanded to include the new invoice items.

E-Invoice

For e-invoices, all invoice items of the type Applied Outstanding Items are summarized in the Paid Amount position.

LEDES Export

There are no changes for the LEDES export, as no services are billed. The applied outstanding items are not included in the LEDES file.

🛈 Note

Please check your invoice templates and adjust them before using the new invoice items. Templates for initial delivery are provided in the delivery directory. The following templates have been updated there: Systemvorlagen_credit_note_de.docx, Systemvorlagen_flat_rate_invoice_de.docx, Systemvorlagen_flat_rate_invoice_details_de.docx, Systemvorlagen_rvg_invoice_de.docx, Systemvorlagen_splitt_invoice_de.docx, Systemvorlagen_hourly_invoice_de.docx, Systemvorlagen_advance_invoice_de.docx, Systemvorlagen_advance_invoice_de_rvg.docx.

Transfer/Retrieve Appointments, Deadlines, and Reminders to Exchange Online as Calendar Entries via MS Graph API (#114939)

This feature allows appointments, deadlines, and reminders to be displayed in a separate Lexolution Calendar for each employee in Outlook. Reminders and deadlines, as well as pre-deadlines, are transferred as all-day events. The transfer is done via MS Graph API and must be set up in MS Entra by the firm before use. Simultaneous use of the old and new integration is not intended.

Employee View

In the Employee view, in the Exchange Calendar ribbon group, functions have been added to manage the connection. The functions are executed for all selected employees.

The Test Mailboxes function checks whether all prerequisites for the connection are met and outputs the result as a log.

For the previous integration via SIS, you can check if entries exist. These can be deleted before activating the new integration to avoid duplicates.

For the new integration, functions are available to check, transfer, and delete entries. Optionally, a date can be entered.

After successful testing and initialization, automatic transfer can be activated to permanently transfer changes. In the object list, the Exchange Calendar Active column shows the status.

If communication data in the vCard is changed, a warning is displayed when the integration is active.

Create Export Bookings with Location Cost Centers (#115285)

For exporting bookings and revenue distributions from Lexolution, the Export - Settings view has been expanded with the Export Cost Center field to include the Location Cost Center option. The cost center field has also been added to the Locations view.

When using the Export Cost Center option, the cost center from the location is transferred to the cost center field of the export booking and output in the export file during booking export.

Additional Filters in the Employee View (#115194)

The employee view has been expanded with the Filter ribbon group, including filters for Employees and active/inactive employees.

New "File" Filter in the Calendar View (#115268)

A new filter for files is now available in the calendar view.
Using the Filter ribbon group, you can select a specific file to display only the appointments associated with that file.

The new file filter can be combined with existing filters:
If at least one other filter is active in addition to the file filter, only appointments that meet all selected filter criteria (AND logic) are displayed.
The file filter is available in all calendar views (day/week/month) and only considers appointments created in Lexolution.

Jump Directly from the Files View to the Calendar View via Context Menu (#115272)

You can jump from a file directly to the calendar via the context menu. To do this, select the desired file in the files view and open the context menu with a right-click.

The calendar view will open, with the file filter preset to the selected file and the display filter preset to appointments.

Selecting Participants in the Word Add-In: Automatic Preselection of Addresses and Contacts (#115217)

When using the Recipient Address content control in the Word Add-In, the Select Participants dialog appears when updating document data.
The following logic applies for preselection:
If you select a contact in the Case Participants section, the corresponding vCard address in the Addresses section is automatically preselected.

If a contact person is also saved for the selected contact in the case, the Include Contact Person option is automatically enabled. If a correspondence address for the contact person is available, the Include Contact Person's Correspondence Address option is also automatically enabled.

If there are no additional details (contact person, correspondence address) saved for a contact, the previous behavior remains unchanged: the first row in the “Addresses” section is selected, and both options remain disabled.

Case: Open Case in a New Tab from the Case View (#115525)

In the open case view, you can select a case and, while holding down the [CTRL] key, open it in a new tab via the context menu and the Cases menu item.

Case: Access to Performance Overviews (#115352)

🛈 Note

Adjustment of function permissions required.

In the Cases view, the following function permissions have been added to allow users with read access to the case to access Performance Overviews 1 and 2.

• 10007 - Case Performance Overview 1 - read
• 10042 - Case - Performance Overview 2 - read

🛈 Note

The function permission 10007 has been renamed from Case – Quick Info – Update Services to Case Performance Overview 1 - read.

Cases View: Display of the “Acquisition Distribution” Panel (#115620)

🛈 Note

The Acquisition Distribution panel is now only displayed in the Cases view for users with the following function permission: - 50029 Cases - Read Acquisition Distribution

Previously, the panel was always displayed even if acquisition distribution was not used.

Cases View: Added Column for Archived Cases (#115213)

The column with the icon for archived cases has been re-added to the Cases view.

Cases View: Added Column for Old Case Number (#123249)

In the Cases view, the “Old Case Number” column has been added in the column editor of the object list.

Contacts: Show Address Addition as a Column in Lists (#115346)

In the People, Organizations, Authorities, and Contacts views, as well as in the duplicate check and selection dialogs, the Address Addition column has been expanded.

Reminders View: Email Sending via ComCenter (#114994)

In the Reminders view, email sending has been standardized to use ComCenter, just like in the Invoice Sending view.

BI: New: Facts Without User/Department Assignment Varied Between ETL Runs (#123306)

Performance accounting facts that could not be assigned to a user or HVRA were not always assigned the same way: depending on the ETL run, they would randomly end up either in the Unknown Department (“-”) or under “in own cases.” As a result, department-based reports were not reproducible. These completely unknown facts are now clearly and permanently assigned to the Unknown Department (“-”). The regular assignment to “in own cases” was not affected and remains unchanged.

BI: Improved: Faster Fact Loading in Performance Accounting (#123439)

The “Last” marker for each business transaction (last row) was previously determined via separate lookups, which executed the source query a second time—this was a noticeable time factor with data sets of several million rows. This marker is now calculated directly in the source query. As a result, the data is only read once, ETL run time is reduced, and identical queries no longer need to be maintained twice.

BI: Improved: Activity Type and Service Type Loaded from a Single Source (#123440)

The Activity Type and Service Type dimensions were previously loaded via two separate processes from different sources, even though the data is over 90% identical. Both are now created in a single load process from the same source: time entries are only read and cleaned once. This shortens load times and ensures both dimensions always come from the same, consistent data set.

BI: Improved: Faster and Leaner ETL Runs for Fact Processing (#123517)

The ETL (Extract, Transform, Load) process for fact processing has been optimized in several areas without changing the reports. Overall, the ETL run starts faster and uses fewer resources.

BI: New: Negative Open Items Shown as “Liability” (#123529)

Since version 9.6, negative invoices and thus negative open items are possible. Previously, these were generally classified as “Overpaid”—that is, for unpaid negative invoices where the firm owes money to the invoice recipient. Such cases now receive the separate status “Liability”; “Overpaid” is reserved for true overpayments of positive invoices. This way, receivables, liabilities, and overpayments are clearly distinguished in all reports.

BI: New: More Reliable Installation with BiManager (Version 3.6) (#123565)

When installing packages with BiManager, configurations could be lost and errors could go unnoticed—the installer sometimes reported success even if the installation was incomplete, or it would hang. Fixed issues include: - the server instance of the Tabular Model remains available even after a restart - errors are now clearly reported instead of being swallowed internally.

BI: Improved: Lower Memory Usage for the “Performance Accounting” Model (#123572)

The tabular “Performance Accounting” model now uses significantly less memory: thanks to optimized storage of key columns, model size was reduced by about 21% in a reference test—the savings increase with more data. For Excel and Power BI users, nothing changes functionally—all metrics remain the same, as does processing time. Available for SQL 2017–2025.

Bug Fixes

Booking Export Aborted with “User Code Too Long” Error (#121053)

• Previous Behavior
  In certain cases, using 8-character user codes could cause the booking export to abort.

• New Behavior
  Booking export with user codes up to 8 characters is now possible.

Bookmark “Fee: Total Unbilled Services” Formatting Error (#116460)

• Previous Behavior
  In the “Fee: Total Unbilled Services” bookmark, the thousands separator was not displayed.

• New Behavior
  The thousands separator is now displayed in the “Fee: Total Unbilled Services” bookmark.

Booking Export: Duplicate File Names in Zip Archive (#117421)

• Previous Behavior
  In certain cases, the same file was written multiple times with identical file names into the zip archive for booking export receipts.

• New Behavior
  The invoice file is now written exactly once into the zip archive.

Word Add-In: Uncontrolled Error Message for Unsaved Documents When Closing Word (#121455)

• Previous Behavior
  In certain cases, closing Word would trigger an error message from the Word Add-In if there were unsaved files and the technical order of closing was “Close Document,” then “Close Application.”

• New Behavior
  The system’s closing order no longer causes an error message.

BI: Missing Culture/Language in Reports for Cases from 2021 (#116890)

• Previous Behavior
  In reports by culture or language, the information was missing for cases from 2021 onward. The reason was a change that made culture no longer a required field in all cases.

• New Behavior
  BI now determines culture via the ID of the saved language. If a different culture is also set for the case, it takes priority. This ensures culture and language are fully reported for cases again.

BI: Stichtag in Closing Balance Caused Errors on English-Language Servers (#117198)

• Previous Behavior
  The Stichtag column in the Closing Balance dimension was set as a date format and caused processing errors on English-language Analysis Servers.

• New Behavior
  The cutoff date is now displayed language-independently. Sorting is preserved.

BI: Load Error for External Plan Data on English-Language Servers (#120620)

• Previous Behavior
  Loading external plan data failed with an error (“incompatible data types” in Lookup DatumKey). The cause was different handling of date values (Date vs. Timestamp), which only occurred on certain English-language servers with different collation.

• New Behavior
  Date assignment now uses a numeric key, making it language- and server-independent.

BI: Missing Revenue for Attorneys with Fully Written-Off Services (#121040)

• Previous Behavior
  If an attorney received revenue only through manual revenue allocation (via negative credit, equivalent to invoicing), while their own services were fully written off, this revenue was not recognized and was missing from the report.

• New Behavior
  The load for written-off services now also includes revenue for people with no or fully written-off services, without double-loading data. The same applies to transfers in payments.

BI: Tax-Free Expenses from Draft Invoices Without Invoice Component Assignment (#123307)

• Previous Behavior
  Tax-free expenses from draft invoices were systematically not assigned to a valid invoice component and ended up in the Unknown member. As a result, reports by invoice component were incomplete in these cases.

• New Behavior
  These items are now always assigned to their invoice component, so reports are complete again.

BI: Oldest Outstanding Services Missing from Age Structure of Closing Balance (#123564)

• Previous Behavior
  Outstanding services older than about five years (1,800 days) were not assigned to any age cluster in the closing balance and were missing from all age-class reports. This affected the oldest and most critical services for evaluation. Totals without age reference (e.g., total balance, quantities) were not affected.

• New Behavior
  All outstanding services are now correctly assigned to their age cluster, including the “> 1800 days” category.

BI: Missing Hours for Split Invoices Without Fee Distribution (#123570)

• Previous Behavior
  

Billed and draft services from split invoices without attorney account fee allocation (typically: flat-rate or split invoices later set to €0) were previously not captured in the service recording—there was no loading path for this scenario. As a result, reports of billed hours per employee or invoice were too low. Time and revenue views were not affected.

• New behavior
  These services are now loaded retroactively and shown with the status “Not billable”; revenue totals remain unchanged.

BI: Missing hours when fees are transferred via €0 credit note (#123571)

• Previous behavior
  If a fee was transferred from one attorney to another via a €0 credit note, the receiving attorney would get credit and payment lines in the attorney account, but never a “Invoice” line. As a result, their billed hours were completely missing from the invoice page or even counted negatively. This affected all reports of billed hours (billed duration per attorney, realization rates, practice group service allocation).

• New behavior
  The hours are now shown exactly once on the invoice page. Revenue remains exactly the same down to the cent, as it is correctly reflected in the credit and payment lines. Also fixed: written-off services from split invoices that were previously missing from the invoice side.

BI: Unrealistic paid hours when payment is received after full credit note (#123575)

• Previous behavior
  If an invoice was fully credited (canceled) and a payment was still received afterward, the report of paid service hours would show unrealistic values—sometimes millions of negative hours for a single case. A single affected invoice would distort the paid duration. Only hours with the status “Paid/Partially Paid” were affected. Revenue was always correct.

• New behavior
  A payment can now never show more hours than the service actually has.

BI: Billed activities with hours counted multiple times (#123576)

• Previous behavior
  The same billed activity could, in certain scenarios, appear multiple times on the invoice page. As a result, billed hours per attorney, file, or period were too high. Revenue was not affected, but all hour-based reports were.

• New behavior
  Each activity now counts its duration exactly once again—billed hours now match the recorded times.

BI: Written-off services counted twice in split invoices (#123577)

• Previous behavior
  For split invoices, written-off services were counted again in full in addition to the correct allocation. Activities were affected, but revenue remained correct.

• New behavior
  Written-off services on split invoices are now only counted once.

BI: Additional fees shown multiple times in inventory after cancellation and new billing (#123768)

• Previous behavior
  When assigning the invoice to the additional fee, canceled invoices in the cancellation/rebilling chain were also counted, instead of just the valid ones. Each canceled step created an extra inventory line. As a result, the quantity and value (sales price) of these fees were too high, and some inventory lines referred to an already canceled invoice. This only affected the inventory and sales price view, not revenue figures.

• New behavior
  The invoice is now taken directly from the inventory entry, which already carries the correct invoice for each transaction (creation = none), instead of using a workaround that collects the entire cancellation history. As a result, each transaction now has exactly one inventory line with the correct invoice.