CSI Lawyer 12.1 update package 16.12.25

We’ll publish a new CSI Lawyer 12.1 update package. Again, it fixes the software defects reported by customers. Note! Customers using an integration to Netvisor bookkeeping system will need to update to their integration before the year-end.

Identifications

• The “Expired and Expiring Identifications” view also listed customer identification events related to completed matters. After the fix, the view only includes identifications linked to active matters.

Matter requests and matters

• The matter request window displayed outdated information if it was opened in a certain situation without reloading the matter request list.
• When a matter request was created in the Conflict Search folder, the responsibility roles were not initialized according to the default parameters defined in the settings.
• The responsibility roles (matter owner, responsible person, and invoicing contact) set as defaults in the user parameters were not taken into account when creating a new matter request.
• After a new matter request was saved and the creator of the matter request was recorded in the responsibility fields according to the default roles defined in the settings (e.g., owner/responsible person = current user), changing the principal on the matter request incorrectly updated those roles to the person making the change.
• The invoicing contact parameter (Default Values parameter group) behaved differently on the matter request compared to the matter owner/responsible person parameters; when, for example, a customer responsible was defined for the “invoicing contact person” parameter, the software could not retrieve the information for the matter request.
• When customer-specific matter numbering was enabled, the matter received the wrong customer number when it was created from a matter request where the principal had been changed in a certain situation.
• The “Billable Matters” list search by text was slow, so database queries have been optimized.

Expenses

• When recording a new expense and selecting a matter for it, the details saved for the expense type in the settings (e.g., Unit and Unit Price) were cleared.

Preliminary invoices and invoices

• The quick preview of a preliminary invoice displayed VAT breakdown amounts incorrectly in the matter currency, even though another currency was defined as the print currency for the payer of the preliminary invoice.
• In the Swedish user interface, preliminärfakturor was misspelled in the notification shown to the user when selecting multiple preliminary invoices or invoice payers in order to create the invoices.
• Net amounts were missing from the advance invoice VAT details.
• On the Swedish invoice template, the actual payment term (e.g., 20 days) was also displayed as the title of the Payment Term field.

Reporting

• In the “Search Reports” window, it was possible to run actions from the right-click menu on reports that had not yet been retrieved from the database. Running the action caused an error.
• Opening the Edit View window via the settings was slow because unnecessary database calls were made.

Other

• When a normal user added a new user to the insider register, the addition took a long time. Duplicate searches were performed in the database, which have now been removed as part of the fix.
• The software could not display the name of an attachment in a note if the name contained an “&” character.
• The Settings window of the Change History did not open in certain situations, e.g., when in version 12.0 of the customer, a Notes field had been added to the matter change history, and the software was then updated to version 12.1.
• When creating a new non-hour-based transaction type, the text “Unit Price” changed to “Hour Price” in the transaction type window upon saving.

Document Management Integrations

• If NetDocuments was integrated with the CSI software and a NetDocuments API call failed due to a connection issue (e.g., when updating matter permissions via a mass action), the error was not shown in the mass action summary window but in a separate popup, requiring acknowledgment before continuing the mass action.
• The NetDocuments integration error log did not record which functions were active when the error occurred or the order in which they were called, making it harder to identify the source of the error.
• Updating permissions in NetDocuments caused the error “Incorrect syntax near ‘)’” if there were no protected matters. After the fix, no changes are made to permissions in this situation, and the user receives a notification that no matters with restricted permissions were found in the database.

Bookkeeping integrations

• NOTE! CSI’s Netvisor integration has used algorithms that Netvisor will stop supporting on 31 December 2025. The HMACSHA256 algorithm required by Netvisor has now been updated in the CSI software version 12.1. The integration must be updated to ensure it works beyond 2026. CSI will handle integration updates for cloud service customers centrally and will agree on updates for OnPremise customers individually.When a recent version of the Fortnox, Netvisor, or Procountor accounting integration was in use, but the CSI software version was released before 11/2025, invoice export failed if the invoice included a PDF.
• The Fortnox integration attempted to transfer inactive cost centers, causing unnecessary errors in the log. After the fix, inactive cost centers are not transferred to Fortnox, and if an invoice exported to Fortnox contains an inactive cost center, the cost center field is left blank on the invoice/invoice line, and a warning is logged in the integration log.
• The Fortnox integration could not check whether the customer or matter already existed in Fortnox. After the fix, the integration updates the CSI customer and matter details to the corresponding customer and project in Fortnox.
• The Fortnox integration could not handle an umlaut character (for example, the letter “ü”) in the Subject field of a transaction, which caused the invoice transfer to Fortnox to fail.
• When the invoice was in euros, the Visma Net integration imported the payment with the euro amount but in the bookkeeping currency (SEK), so the payment did not match the invoice’s outstanding amount. After the fix, the payment is imported in the bookkeeping currency and with the bookkeeping currency amount. However, note that if the exchange rates for the payment and the invoice differ in Visma Net, the payment imported into CSI may not match the invoice exactly. In such cases, the surplus for overpayments is posted and in case of underpayments, the invoice must be manually marked as paid, for example, by invoice alignment.