Release Notes LEXolution 9.1

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

  • E-invoicing in ZUGFeRD format
  • New RVG fee schedule as of June 1, 2025 (KostRÄG 2025)
  • Improved match rate for bank statement imports
  • Enhancements in LEXolution.BI

In addition, LEXolution is actively working on Pricing and a new case file view. These features will be available in an upcoming version of LEXolution.

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

Important Notes for Updating to Version 9.1.99

  • Major releases, feature packs, and service packs are cumulative and always include the complete current version.
  • LEXolution 9.1.99 requires Microsoft .NET Framework 4.8 on both the server and client side.
  • If not already installed, please 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.1.99 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.
  • If you are using the centralized STP User Management (UM), we recommend updating to version 1.5.163 or later and updating the STP common services to version 1.5.0.
  • Downloads for .NET Framework 4.8, the UM, and the common services can be found on our download page for LEXolution.
  • LEXolution 9.1.99 is approved for Windows 11, Windows Server 2022, Office 2021, and Office 365.
  • The LEXolution server update (the final step in the setup, using the Start LEXolution Server button) may take more than 15 minutes when updating from a version older than 6.4 on larger LEXolution databases containing millions of recorded services (time entries, disbursements).
  • LEXolution 9.1.99 requires IKAROS 2022 or later.

LEXolution.BI

  • LEXolution 9.1.99 requires LEXolution.BI 9.1

ADB Tool for Updating the Analytics Database

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

Documents (LEXolution.DMS)

  • Starting with version LEXolution.KMS 6.4.244, LEXolution.DMS is only used via the new interface. Note: The entry in the LEXolution server config is now equivalent to the entry . No manual changes to the config are therefore required.

Additional Notes

  • LEXolution 9.1.99 is approved for Office 2024.
  • Localizations for German, English, French, and Swiss German (de, en, fr, de-ch) are included in the setup packages starting from LEXolution.KMS 6.3.81 and are installed automatically. If a server-side localization is not desired (e.g., on an English app server with English error and notification messages in LEXolution), the relevant folder (e.g., en) can be removed from the app server.
  • With the rebranding of LEXolution.KMS to LEXolution in version 8.0.122, if you are using the STP Updater, the directory in the STP Updater repository must be updated:
    • For setup-based updates:
      • C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution.KMS Client -> C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution
      • C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution.KMS Word AddIn -> C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution Word AddIn
    • For individual file patches:
      • C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution.KMS Client -> C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution
      • C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution.KMS Word AddIn -> C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution Word AddIn

Version History

  • 04/25/2025 Release 9.1.99 (internal)
  • 05/20/2025 Release 9.1.99 (official)
  • 05/28/2025 Release 9.1.100 (bug fixes)

Changes in 9.1.100

Version 9.1.100 includes all changes from version 9.1.99 plus the bug fixes listed below. Version 9.1.100 is available for download from our official download page.

If you have already installed version 9.1.99, there are two options:

1.) Full update (server, client, Word Add-In, OnPremise Connector Add-In, ADB Tool) 2.) Apply patch (replace two DLL files in the LEXolution client directory)

We recommend applying the patch by replacing the two DLL files on the client side.

The patch, along with instructions, is also available on the download page.

Bug Fixes – LEXolution

  • Incorrect default responsible party when creating a deadline (#92212)
    • Previous behavior
      • When creating a new deadline, the logged-in user was set as the default responsible party instead of the lead attorney.
    • New behavior
      • When creating a new deadline, the lead attorney is once again set as the default responsible party.
  • Timeout error in bank statement import when automatically matching a large number of entries (#91460)
    • Previous behavior
      • During automatic matching in the bank statement import, a timeout error could occur when processing a very large number of entries.
    • New behavior
      • During automatic matching in the bank statement import, a timeout error no longer occurs when processing a very large number of entries.

Changes in 9.1.99

Billing

  • E-invoicing in ZUGFeRD format (New #81170)
    • Create e-invoices in ZUGFeRD format (#81181, #81187)
      • The ability to create e-invoices in ZUGFeRD format is now available.
      • The billing configuration of the case file can be used to specify which type of e-invoice (XRechnung or ZUGFeRD) should be used.
      • In the invoice draft and in the invoice, when using a billing agreement with a configured e-invoice, the type of e-invoice can be adjusted.
      • In invoice dispatch, depending on the type of e-invoice, either the XML or the PDF is now displayed in the system viewer and can be sent.
    • Update e-invoice terminology (#81182)
      • The previously used term "XRechnung" has been replaced with the general term "e-invoice."
      • The term "XRechnung" is used for e-invoices in XML format.
      • The term "ZUGFeRD" is used for e-invoices in PDF format.
    • ZUGFeRD-type e-invoices (#81178)
      • A ZUGFeRD e-invoice consists of a visual component (the PDF), to which an XML file containing the XRechnung is attached.
      • Under the German VAT Act (UStG), the XML file is the authoritative document.
      • The visual document of the ZUGFeRD invoice is automatically generated from the XML.
      • The layout used is one provided by KOSIT and cannot be individually customized.
  • New RVG fee schedule (KostRÄG 2025) (New #88994)
    • As part of the Act Amending the Law on Costs and Guardian Remuneration (KostBRÄG 2025), the RVG attorney fees have been increased with effect from June 1, 2025.
    • The updated RVG fee schedule rates effective June 1, 2025 are now available.

Other

  • New register type for contacts (Enhancement #82547)
    • The list of register types has been expanded to include the entry GsR for the commercial partnership register (Gesellschaftsregister).
  • New register type for locations (Enhancement #82547)
    • The list of register types has been expanded to include the entry GsR for the commercial partnership register (Gesellschaftsregister).
  • Bank statement import: match rate (Improvement #67999)
    • To improve the match rate when searching for open items, two options have been enhanced in the Administration settings under General Settings, on the Accounting tab, in the Bank Statement Import Match Rate section.
    • Option: Consider invoice numbers starting from
      • A number of up to 10 digits can be entered here.
      • If a value is entered, the numeric portion of the matched invoice number must be greater than or equal to the configured value. Examples:
        • Match 2024123A; numeric portion 2024123
        • Match 1000-2024; numeric portion 10002024
        • Match ABC/20034; numeric portion 20034
    • Option: Consider invoice recipient
      • When this option is enabled, open items must match not only by invoice number but also by the invoice recipient's name, which must exactly match the payer/payee or final payer/payee.
      • For individuals, both first name and last name are taken into account; otherwise, only the name is used.
  • Bookmark KmsKfaVorsteuerabzugsberechtigung with court-compliant text (Change #83092)
    • The wording in the bookmark has been updated to:
      • The applicant is not entitled to deduct input tax on the amounts.
      • The applicant is entitled to deduct input tax on the amounts.

Interfaces

  • REST API _(Enhancement #66934)_****
    • The REST API now supports versioning via a query parameter.
    • Without a parameter (default), version 1 is used as before.
  • Case file register template (Enhancement #75046)
    • For the Legal Workspace (New Matter Intake), LEXolution now provides the case file register template via the REST API and the LSB interface. This allows a case file register template to be selected in the Legal Workspace when creating a case file, and passed along when transferring the case file to LEXolution.
    • LEXolution then creates the corresponding folder structure in the connected DMS system (STP Documents OnPrem, Filesystem, iManage) based on the selected template.

LEXolution.BI

  • Acquisition distribution enhancement (Enhancement #79385)
    • A new feature has been implemented that allows the persisted acquisition distribution to be loaded and displayed in LEXolution.BI. To use the persisted acquisition distribution, the configuration parameter "AkquisitionsverteilungAusKMS" must be set to "false" in the Data Warehouse, and the configuration parameter "AkquisitionsverteilungAusKMSpersistiert" must be set to "true".
  • Enhancement of the "LEXolution.BI Info" dimension (Enhancement #81104)
    • The "LEXolution.BI Info" dimension has been added to all tabular models, as this information is essential for customers to verify whether LEXolution.BI is up to date and has run successfully.
  • Date dimensions: new hidden "Date" column formatted as a date (Enhancement #82129)
    • The date dimensions in the tabular models now include a hidden date field formatted as "Date." The following dimensions have been updated:
      • Service date
      • Invoice date
      • Payment date
      • Transaction date
      • Due date
      • Case file creation date
      • Case file archiving date
      • Service creation date
    • This makes it easier to use these fields with built-in DAX date calculation functions.
  • Input sanitization – removal of unsafe characters or encodings in ETL (Enhancement #84353)
    • When loading all text data, the input for LEXolution.BI is now sanitized by removing ASCII characters 00–1F. These were repeatedly causing issues with grouping and model processing. These are so-called control characters with no content relevance; more information at: https://de.wikipedia.org/wiki/Steuerzeichen
  • Employee dimensions extended with the "Gender" field (Enhancement #83069)
    • The "Gender" field has been added to all employee dimensions in the tabular models, enabling analysis and grouping by this field in Excel and Power BI. The new field is located under the "Job-Related Data" folder.
  • Practice group "Share" enhancement (Enhancement #84000)
    • The new measure "Practice Group Share" has been added to the tabular model under billing, showing the employee's share within the respective practice group. The totals row is always calculated as an average.
  • Employee dimensions: location field extended for comparisons (Enhancement #84388)
    • The "Location" field has been added to all employee dimensions in the tabular models, enabling analysis and grouping by this field in Excel and Power BI. The new field is located under the "Job-Related Data" folder.
  • Chronological sorting of the reference date in the Closing Balances dimension (Change #87318)
    • In the balance model, the reference date attribute in the Closing Balances dimension is now sorted chronologically. Previously, no sort order was defined. The reference date attribute is now sorted chronologically.
  • Closing balance: different date for default entry (Change #80964)
    • In the balance model, the reference date attribute in the Closing Balances dimension was always displayed as 11/30/2022. However, this value caused confusion, so it has been changed to 01/01/1900 to align with all other date dimensions.
  • Change detection for changes to the parent company in a group _(Change #88226)_****
    • The mechanism used to detect changes to parent companies in the Contact dimension has been improved. This ensures that even very large parent companies within a group are correctly updated when a parent company changes anywhere in the group.
  • Practice group FTE enhancement (Enhancement #88275)
    • The new measure "Practice Group FTE" has been added to the tabular model under billing, showing the employee's FTE at the time of the service. The totals row is always calculated as an average.
  • Service type dimension: new "Type of Disbursement" field (Enhancement #88677)
    • During the restructuring of the activity and disbursement dimension into the service type dimension, the "Type of Disbursement" field was removed. It has now been added back as part of this enhancement and is available in the new model, just as it was in the old model.
  • Extend FTE retroactively by 3 years for normalizing service comparisons (Enhancement #88728)
    • The FTE calculation in the billing model has been extended to cover 3 years of historical data (previously 2 years). In the statistics model, the FTE calculation has been reduced from 15 years to 10 years retroactively.
  • Statistics – extend partner-to-employee assignment (Enhancement #88739)
    • The partner-to-employee assignment has been added to the statistics model, enabling analyses based on this relationship.
  • Add case file responsibility dimension (Enhancement #77067)
    • When migrating from the old cube model, the case file responsibility dimension was not carried over. It has now been added as part of this enhancement and is available in the new model with the same attributes as in the old model.
  • Add missing translations (en, us, fr) (Enhancement #89074)
    • Translations for the new fields have been added across all models for the following languages: fr-FR, en-US, and en-UK.
  • DimContacts – Always load the most current (latest) addresses (Change #89257)
    • In LEXolution, a contact can have multiple addresses of the same type. If a contact had no V-Card address but had, for example, multiple business addresses, one of them would be loaded and stored in LEXolution.BI — but this was not necessarily the most recent one. This behavior has been changed so that LEXolution.BI now always loads the most recently created address and saves it to the contact.

Bug Fixes – LEXolution

  • Bank statement: payment billing distribution (#80039)
    • Previous behavior
      • If an open item was paid in full, then partially credited, and this negative open item was subsequently cleared in the bank statement view so that the open item was settled, the VAT was calculated from the payment amount using the applicable tax rate and distributed in the billing distribution. Depending on the payment amount and tax rate, rounding differences arose when back-calculating the net amount from the gross amount and splitting it into the fee and disbursement components, causing those components in the case file and attorney account reports to not always net to zero.
    • New behavior
      • When a payment fully settles an open item, any back-calculation differences from the gross amount are handled by using the open item components — rather than the paid components — as the default values in the billing distribution.
  • Bank statement: payment billing distribution (#79974)
    • Previous behavior
      • When paying an open item from consolidated invoices, with remaining amounts distributed across many sub-invoices, rounding differences could arise in the billing distribution when back-calculating the net amount from the gross amount and splitting it into fee and disbursement components, causing those components in the case file and attorney account reports to not always net to zero.
    • New behavior
      • When a payment fully settles an open item, any back-calculation differences from the gross amount are handled by using the open item components — rather than the paid components — as the default values in the billing distribution.
  • Bank statement: period filter (#47469)
    • Previous behavior
      • If a posting period different from the date was entered in the posting period filter in the bank statement view, then the user navigated to another view and back, the period filter would reset to match the date.
    • New behavior
      • The posting period filter no longer changes when navigating away from the bank statement view and returning to it.
  • Bank statement import: invoice numbers not found (#79447)
    • Previous behavior
      • During bank statement imports, open items were not suggested as matches if the payment reference included a "/" immediately before or after the invoice number without a space. Example: /[InvoiceNumber/.
    • New behavior
      • Invoice numbers are now recognized during the search and suggested as matches.
  • Administration: account labels (#79513)
    • Previous behavior
      • In the account labels view, it was possible to save general ledger accounts with a length greater than the configured maximum length.
    • New behavior
      • In the account labels view, saving account numbers longer than the configured maximum length is no longer possible.
  • New deadline: not all fields set to inactive after saving (#83458)
    • Previous behavior
      • In the deadlines dialog, after saving a new deadline, the Case File and Responsible Party input fields were not set to inactive and remained editable. However, any changes made could not be saved.
    • New behavior
      • The Case File and Responsible Party input fields are now inactive and cannot be edited.
  • Deadlines: entering a deadline (#84453)
    • Previous behavior
      • When entering a new deadline, manually changing the Responsibility field, and saving, the old value was displayed after saving even though the change had been saved.
    • New behavior
      • After saving, the Responsibility field displays the saved value.
  • Contacts: deletion (#75238)
    • Previous behavior
      • When deleting contacts, a timeout message was displayed and the contact could not be deleted. The cause was a potentially unoptimized check of the contact's usage in conflict checks.
    • New behavior
      • The usage check has been optimized, and the contact is deleted after a successful check.
  • Travel expense import: assignment and validation (#85731)
    • Previous behavior
      • The employee cost center from imported travel expenses was not used for employee assignment.
    • New behavior
      • If an employee cost center is imported and a cost center is defined in the employee master data, the assignment is carried out when a match is found.
  • Case file: archiving log (#49903)
    • Previous behavior
      • Long case file reference numbers were truncated in the archiving log.
    • New behavior
      • Column widths have been adjusted so that long case file reference numbers are displayed in full.
  • Case file: Transfer case file from Legal Workspace (New Matter Intake), LSB interface** (#89039)**
    • Previous behavior
      • When transferring case files using the LSB interface (used in the Legal Workspace), language and locale had to be submitted as separate values.
    • New behavior
      • If a language is specified when transferring the case file and the locale is left blank, the locale defined in the language list is used as the default.
  • Billing: invoice drafts (#87784)
    • Previous behavior
      • The "Create LEDES file" button was active even when only the e-invoice option was enabled.
    • New behavior
      • The "Create LEDES file" button is now only active when the LEDES option is enabled.
  • Bookmarks: consolidated invoice attachment: applied retainer (#87127)
    • Previous behavior
      • The "Consolidated Invoice Attachment: Applied Retainer" bookmark displayed "Invalid Bookmark."
    • New behavior
      • The bookmark returns a list of case files with applied retainers for an invoice, to display a list of applied retainers as supporting documentation.
  • Word Add-In: case file responsible parties (#87687)
    • Previous behavior
      • In the case file responsible parties dialog, only a few rows were displayed in the Assigned Secretariat section. With many secretariats, scrolling was required to make a selection.

Related to