CSI Lawyer 11.0 update package 16.8.23

Today 16.8.23 we’ll release a new update package for CSI Lawyer 11.0. 

We warmly recommend updating the software to the new version in order to improve its reliability and usability. Customers using their own update package are welcome to request a new update package from us. We’ll always deliver it free of charge.

The new update package will fix the following software errors:

Customer

• The expiration date of the customer’s identification event was incorrectly calculated from the verification date of the identification event. After correction, the expiration of an identification event is calculated from the  actual identification date.
• The identification expiration date was incorrectly calculated for the customer’s identification event, even when the identification level was ‘Not required’. The incorrect information appeared in the list of customer identifications, but not in the order window.
• When deactivating a customer that did not have a customer responsible defined, the software gave an uninformative ‘…no elements’ error message. 

Matter

• On the Insurance tab of a matter party, the ‘box within a box’ option was automatically selected in the ‘Create invoice for deductible’ field, although it should not even have been selectable.
• It was possible to link to a matter a role price having a currency which was not the matter currency.

Entries

• In CSI Mobile and CSI MyDesk, it was in certain situations possible to modify a transaction’s hours, even if the transaction was on an invoice or on a preliminary invoice with status ‘Uplifted/Downlifted’, ‘Reviewed’ or ‘Approved’.
• When a cost-forward expense to be invoiced by payer taxability was registered to a matter and, in the purchase information of the expense, a VAT rate different from the customer’s taxability was selected, the expense was added to the invoice based on the selection made in the VAT field and not the payer’s actual taxability.

Preliminary invoice

• When the matter had two payers and, on the preliminary invoice, the shares of both payers were changed and the ‘Calculate’ button then selected, the software gave an error and the operation failed.
• When previewing a preliminary invoice containing both expenses and transactions in a foreign currency, it showed an extra row of shares and rounding if the ‘Round invoices to whole number’ parameter was on.
• In the main/sub-matter structure, when preliminary invoices were created from the main matter where an advance was available, after approving the sub-preliminary invoices and the main preliminary invoice the preview of the main preliminary invoice incorrectly showed a smaller advance usage than before approving the sub-preliminary invoices.

Invoice

• When ‘monthly’ was selected as the invoicing period, the date check functioned incorrectly and the ‘Billable Matters until the end of the previous invoicing period’ view did not show all billable matters.
• When rounding was in use and an invoice was created from an approved preliminary invoice for which the payer had been changed, the rounding was missing from the invoice.
• If the Lithuanian country package with invoice templates was in use and several invoices were printed at a time, the Lithuanian texts were printed several times.
• In the LEDES material, the foreign currency exchange rate was calculated according to the wrong date and an unnecessary payment row was displayed even when the payment adjustment had been cancelled.

Payments

• The excess of an overpayment imported as reference material was automatically posted, although automatic posting must only be done for payments transferred by the bookkeeping integration.
• When a payment adjustment in foreign currency was canceled from an invoice, the software processed the payment’s VAT incorrectly. 

Reports and views

• When a report was added as a quick selection for a user group, it was not possible to delete the report.
• If the view was created based on a Boolean custom field, it did not work correctly in certain situations.

Integraatiot

• When the M-Files document management system was in use and, in an insider matter, a user saved information that did not affect M-Files access rights (for example, editing the matter subject), the access rights were still updated.
• In the Fennoa integration, there was a problem related to rounding of sums in the reconciliation calculation which caused unnecessary warnings in the integration log.
• If the number formatting of the normal invoice contained letters, the Fennoa integration was unable to adjust a credit invoice to it.
• The Fortnox integration did not transfer cost centers to Fortnox but produced an error message if the cost center name had more than 6 characters. 
• The Fortnox integration transferred the credit invoice containing a discount with the wrong amount. The credit invoice itself was displayed correctly in Fortnox, but the amount was incorrect in Fortnox’s ledger report as the discount was added to the credit amount.
• When the bookkeeping currency of the CSI database was SEK and , in Fortnox, an euro payment was registered for an invoice in euros the Fortnox integration incorrectly transferred the payment in SEK, so the adjusted amount was too small.
• The bookkeeping integration tried and retransfer the invoice to the bookkeeping system, if it was modified at the same time as the integration was transferring it. The correction applies to all productized bookkeeping integrations.
• In the configuration window of the bookkeeping integration, the content of certain fields was not displayed on the small screen.

Settings

• When adding target budgets, the transaction type category was lacking language translations, so the texts were always in Finnish.