CSI Lawyer 12.1 update package 12.2.25

We have just published a new CSI Lawyer 12.1 update package. The version fixes the following software defects reported by our customers, and will also bring a few new functions, marked in the list with “NEW”.

Matter and matter request

• If a certain employee role price was already linked to a matter request and the same role price was tried to be added again, the software gave another, unnecessary error message after the actual error message: “Cannot insert the value NULL into column ‘request_guid’, table ‘database.dbo.RequestRole’; column does not allow nulls. UPDATE fails. The statement has been terminated.”
• The mass selection function of matters (Ctrl + a) was slow, although the selection function should not take more than a minute even with a large number of matters.
• If a matter was created by using as a template another matter where there were team members without the Hour price check box selected, the team members of the new matter still had that check box selected.
• Deletion of the matter failed if the matter was created from a matter request for which a conflict check had been performed.
• In the January 2025 update package, the “Billable matters” list had been changed to show matters with transactions/expenses in the status “open”, “on preliminary invoice” or “reviewed”. The list has now been corrected to show only the matters with transactions/expenses that are not on a preliminary invoice and whose status is “open” or “reviewed”. The list also calculates the sums of unbilled transactions and expenses by matter.  (NEW)

Transaction and work time entry

• The power user can now edit the type of several work time entries at once by selecting the work time entries and the “Edit multiple” function from the menu that opens with the right mouse button. (NEW)
• To a user performing a certain type of work, it is possible to define a default transaction type  which is added to transactions recorded by the user. The definition is done in the Settings > User parameters > Transactions/Transacion parameters > Default transaction type, and only billable transaction types can be set as default. The default transaction type hierarchy from strongest to weakest is: 1) Default transaction type set in the matter parameters, 2) Default transaction type set in the user parameters, 3) Default transaction type set in the business unit parameters of the matter, 4) Default transaction type set in the main business unit’s parameters. If the transaction types to be used in the matter are separately defined and they do not include the user’s default transaction type, the Transaction type field in the new transaction’s window will remain empty. (NEW)
• When a work time entry was copied for a period and the automatic creation of a transaction from the work time entry was enabled, the software did not notify the user that the copying function did not create transactions automatically.  As a correction, a note about this has been added to the “Copy for period” window.
• The hour price source of a transaction was not updated when the transaction was transferred from one matter to another.
• Power users were not able to add notes to transactions which already had been invoiced.

Proof invoice

• Sending a proof invoice as an e-mail attachment and creating the invoice material from a summary invoice failed if the user interface language of the main business unit was set to “Not selected”.

Preliminary invoice

• The preliminary invoice review process got stuck due to missing users, e.g. if the first reviewer was the “Matter assistant” and no assistant had been selected for the matter. After the correction, the missing users are skipped from the beginning of the process and the preliminary invoice is to be checked by a valid reviewer found in the process.
• The duplicate check of the preliminary invoice review cycle was working incorrectly in a certain situation. If two matter roles (e.g. assistant and invoicing contact person) were added to the review cycle and both roles were left blank in the matter, the software assumed “blank” as a duplicate.

Invoice materials

• In a certain situation, the net amount of the invoice rows on a credit invoice was calculated incorrectly when a entire invoice was credited. Due to this, the Finvoice, Peppol and TEAPPSXML materials were not valid.
• In the e-invoicing material in Finvoice format, the VAT amount calculated from the invoice rows did not match the VAT amount on the invoice. A check has been added to the XML format of the e-invoice ensuring that the VAT amount calculated from the invoice rows per VAT base corresponds to the amounts in the VAT specification of the invoice. If the amount differs, the difference is added/subtracted from the largest net invoice row having the same VAT base as the revised VAT base.

Reporting

• When the “Use invoice date as entry date” parameter was used and an advance was used when approving the preliminary invoice, the use date of the advance was incorrectly updated in the database and the advance was thus not displayed in the Open advances report.

Settings

• When a standard price was set for the transaction type in the settings, the hour price was reset to zero in the transaction type window, but it was still incorrectly displayed in the transaction type list.

Bookkeeping integrations

• In the 12.0 version of the CSI software, the Netvisor integration was unable to handle the decimals of the VAT percentage, which is why 25.5 % VAT base disappeared from the imported expenses.
• If there were many matters with the same number in the database, activation of the Netvisor add-on showed a random matter number in the error message. After the correction, the error message lists all matter numbers that are found in the database more than once. The fix has been made to all CSI’s productized accounting integrations.
• In the customer-specific Visma accounting integration, an error in one expense (for example, the absence of an expense subject) blocked the run and the rest of the expenses were not transferred to CSI. After the correction, “Utlägg från bokföring” is used as the expense subject in Visma, if necessary, and the Visma voucher number is saved for the imported expenses. At the same time, the logging of all accounting integrations has been improved to catch error situations. If for any reason the expense recording fails, the invalid expense is skipped and logged, and the other expenses are imported.

Document management integrations

• Updating user rights in the NetDocuments integration has been enhanced to make the process faster. After the update is completed, an e-mail about changes in access rights and possible errors is sent to the user who updated the NetDocuments access token.
• The linking of NetDocuments users and user groups did not display or log the error returned from the NetDocuments API in a user-friendly format.

Outlook Add-in

• In the Outlook Add-in, the icons for the Create Critical Task and Create Activity functions did not follow the order of the CSI software: 1. Task (Activity), 2. Critical Task.
• Both components of the Outlook Add-In had an unnecessary parameter “EffectiveValueSourceIds”.

Other

• The error messages displayed when having database connection issues were not user-friendly enough. Now the user is clearly showed whether the error is caused by the failure of the database connection to be created, a wrongly formatted connection key or an incorrect connection key password.