Lexolution Insolvency Integration

Purpose of the Handout

This handout outlines the technical background and necessary configurations to use the KMS Inso interface. It is primarily aimed at administrators who need to be able to fully set up the systems.

Technical Background

The interface connects the systems winsolvenz.p4 and LEXolution.KMS/LEXolution.FoMa.
This allows cases with debtors to be efficiently and easily forwarded for collection.

Cases can be automatically transferred from winsolvenz.p4 to LEXolution. In LEXolution.KMS, a corresponding KMS insolvency file is created for each case with participants and responsible parties, eliminating the need for duplicate files and contacts.

The same applies to the ability to automatically transfer debtors from winsolvenz.p4 to LEXolution.
A KMS file is created for each debtor in LEXolution.KMS.
The file is assigned as a sub-file to the case file. This eliminates duplicate files and contacts, which is a significant workload reduction given the number of debtor claims that can exist in a case.

Furthermore, debtor claims (one or more per debtor) are automatically transferred to the corresponding KMS files in LEXolution.KMS.
The claims can be viewed in LEXolution.KMS and, if necessary, further transferred to LEXolution.FoMa. The claims do not need to be re-entered in LEXolution.FoMa, eliminating duplicate entries.

Configuration in winsolvenz.4

Program Base/License

A KMS Inso export requires winsolvenz.p4 version 10.1 or higher; an export from winsolvenz.p3 is not possible.
An enterprise license for winsolvenz.p4 must be available in the firm for the export.

Employee Code Administrator

Under Settings/Administrator in winsolvenz P4, an employee with an employee code must be entered among the insolvency administrators that matches the employee code of a lead attorney in LEXolution.
The code is alphanumeric and can be up to five characters long.

Fig. Entry of Employee Code in winsolvenz P4

System Settings

Under Settings/Firm/General Settings, the URL for the Lexolution interface and the AppID must be entered.
The settings are called

KLexolution Interface External App-ID and Lexolution Interface URL

The URL is composed of “http://[Servername_KMS]:[Port]”

Server Name: The server where the Lexolution server service is running.
Port Number: The port where the external Lexolution interface is running (default is 8002).

The external App-ID must be created in LEXolution under Administration/System/ in System Administration/External Applications.

Role/Permission for Export

The employee designated for export must be assigned the Export LEXolution role under Settings/Users. This role is a so-called combination role, meaning the user must be assigned at least one other role (even if the user has been assigned one of the administrator roles).

Export of winsolvenz.p4 Insolvency Files as Case Files in LEXolution
  • Export is possible directly from a case or file.
  • One or more files can be exported at once.
  • Each export is only possible once.
  • If a file has been exported, it is marked with a check in the Exported LEXolution column.

Data exported includes information about the case, the debtor, and the debtor's attorney (if represented). The court and the insolvency administrator are also exported.

Export of winsolvenz.p4 Debtors as Collection Files in LEXolution

Export of one or more debtors from Assets/Debtors with marked claims is possible.
If no claim has been created yet, the export of pure address data is also possible.
The export of an address and a claim is only possible once each.
Whether a claim has been exported is visible in the grid in the Column Status Claim Collection and in the corresponding field in the lower right detail.

If the directory position contains a challenge, the claim is considered a challenge claim for export.
For all other directory positions, the claim is considered a collection for export.

In collection and claim files, claims of one type are combined into one file if they are exported simultaneously.
Claims that have not yet been exported can be exported later in another batch.

Configuration in LEXolution

Program Base/License

LEXolution supports import from winsolvenz P4 starting with version 5.3 FP1.
In the “STP.Kms.Server.exe.config,” the following key must be set to value 1.

<add key\="IsExternalCommunicationServiceEnabled" value\="1"></add\>

Configure winsolvenz.p4 as an External Application

Under System/External Applications, an application ID must be assigned for winsolvenz.p4.

It is important that the App-ID in LEXolution matches the one assigned in winsolvenz.p4 under Settings/System as the Lexolution(KMS) interface external application ID.

winsolvenz.p4 Users in LEXolution

The winsolvenz.p4 users who perform an export must be set up with the same usernames in LEXolution (including any domain prefix).
Administration - User Management/Users/ e.g., rnd2025.1 as shown in the figure.

Lead Attorney

Under Firm/Employees on the Master Data tab, assign the employee code.
The code must be identical to the code of the insolvency administrator to whom the case and collection files are exported (max five characters, alphanumeric).

Functional Rights for Import

Possible functional rights for import include:

Legal Areas

The legal areas "Civil Law" and "Insolvency Law" must be created under
Administration/Specialized Administration - (General)/List Entries.
In the filter, "Case Legal Areas" must be selected.
Insolvency Law is assigned to the procedural file and to collection files in case of contestation upon import.
Civil Law is assigned to collection files that are not under contestation.

Case Participation Types

The participation types "Representative," "Debtor," and "Insolvency Administrator" must be created.

Case Number Range

The case number range is created under Administration/Number Ranges as the type Case Number.
The abbreviation WZ must be used, and the number range must be allowed.

Related to