CSI Lawyer 12.1 update package 14.5.25

We have released a new update package for CSI Lawyer 12.1, fixing software defects reported by customers.

Matters

• If a role price list or user price list had been defined for the matter, the “Use as template” action did not copy the price list for the new matter.
• Closing multiple matters at once recorded the closing reason for only one of the matters.

Invoices

• The quick preview of the preliminary invoice did not work if a default invoice template was not selected.
• When involving suitable amounts, invoices with several payers resulted in the error “The period does not contain any matching elements” when trying to create a Finvoice material. The fix applies to version 12.0, as the fix for 12.1 was published already  2-25.

Credit invoices

• If the “Round invoices to whole number” parameter was enabled and the invoice had only expenses, partial invoice crediting did not work correctly.
• Credit invoices for multi-payer foreign currency matters were generated with incorrect amounts. The total amount displayed was the total of all invoices, when only each individual’s share should have been displayed.
• When a credit invoice was cancelled, the correct date for the cancellation was left blank in the database. After the correction, it is also checked that the windows of both the normal invoice and the credit invoice show the correct date in the History popup instead of the invoice date.

Reporting

• The new “Conflict Check Parties” report lacked title rows and translations.
• The reporting views regarding the invoicing of main and sub-matters have been updated. Should you get an error message after the update, please be in touch with the CSI support team.

Bookkeeping integrations

• In the Procountor integration, the duplicate check of the archiving ID of reference payments did not transfer some payments. If two payments had the same archiving ID, the latter was not imported. After the correction, the payments with the same archiving ID are imported if they are different payments.
• In CSI, if there was a space at the end of the cost center name, the Hogia integration tried to recreate it in Hogia and logged an error each time because Hogia recognized it as a duplicate despite the space.
• The invoices transferred to Hogia did not show the matter number on the sales account rows. 

Document management integrations

• The NetDocuments integration was unable to manage user rights properly if the Customer and Matter metadata had been overridden.
• In the iManage integration, an HTTP error code 429 means that so many requests have been sent to the server within a certain period that the maximum number of requests has been exceeded for security reasons and to ensure the operation of the system. If an error 429 is received in the iManage API call, the user receives an error message indicating the time after which requests can be resent.

Customizations

• The software allowed relational type customizations without a relational field, in which case the custom field did not work.