CSI Lawyer 12.0 update package 29.11.23

We’ll release today a new update package for CSI Lawyer 12.0. The update package will fix the following software defects (the ones fixed also in version 11.0 are marked with an asterisk):

Customer

• When a new customer was being created and an address added to it, the software gave a warning when saving the customer and did not save any information in the database. If a new customer was being added through the principal field of the matter, the software gave an error message when saving the matter and the saving function failed.

Matter

• When a user tried and close a matter which had phases but no entities preventing closing, the software gave an error message and the function failed. *

Preliminary invoice

• When previewing a preliminary invoice that had a transaction with a text longer than 500 characters, the software gave an error message about the failure to apply restrictions.
• When the payer had been given a discount on the main preliminary invoice, the preview of the approved main preliminary invoice did not show the entire discount, but only the discount on the sub preliminary invoice. *
• There was a rounding error in the preliminary invoice preview when the payer had a discount. The rounding error disappeared when an invoice was created from the preliminary invoice. *
• Changing the payer shares of the preliminary invoice added an unnecessary rounding row to preliminary invoices (also to approved ones). On the actual invoice, the row was no longer visible. *

Invoice

• Invoice VAT calculated by invoice row caused problems with the total amount of uplifted/downlifted invoices containing a large number of invoice rows. VAT is now calculated from the invoice’s net amount again. 
• The creation of the Finvoice 3.0 invoice data did not work correctly with a taxable, partially credited invoice: the VAT amount of the entire invoice did not match with the total amount of the VATs of the invoice rows.
• When bookkeeping material was created from an invoice using the EstonianEInvoice plugin, the xml file did not contain the customer number.
• In certain situations, an unnecessary share row was displayed in the invoice although there was only one payer. 
• If an invoice was created without a preliminary invoice, no advance was used to the general expense. *

Payment demand

• When a new payment demand was sent from an overdue invoice for which one payment reminder had already been sent as an e-invoice, the number of payment demands for that invoice in the Overdue invoices view incorrectly changed from one to three.

Credit invoice

• On a credit invoice including tax-free expenses and taxable transactions, the rounding and VAT were displayed incorrectly.

Bookkeeping integrations

• The Netvisor integration transferred the invoice to Netvisor without information about the invoice currency. Now the bookkeeping currency is always included. *

Reports and views

• If the payer of the invoice was a private person living in the EU region, the EU sales diary incorrectly showed the invoice in the Other region and not in the EU region.
• In the “Open transactions and expenses” report, there were incorrect terms.
• When editing a view, there should be data in each column of the criteria row, but saving the incomplete criteria row did not give an error message, and the saved row was lost when the view was reopened in the edit mode.  After correction, the software gives an appropriate error message. *

Other

• When signing in to the software with Entra ID (formerly Azure ID) failed, and the user interface language was either English or Swedish the software failed to give the error message in the correct language. *
• When a customer using the MSI installation package was connecting the software to the database, the software prompted to install the WebView2 component and took the user to the Microsoft site.