New CSI Lawyer 10.1 update package 17.8.22

We’ll release a new update package for CSI Lawyer 10.1 today. The update version fixes the following software defects:

• In the assignments party folder, the party role columns were too narrow and couldn’t be widened.
• If a user added two parties to an assignment, marked them both as payers and added shares for them, only the upper one was properly saved but the lower one remained in the list without a role and a share.
• When an assignment was set as an insider assignment, the assignment window did not display it properly. The selection in the “Insider published” checkbox incorrectly indicated that the insider assignment had already been published. The “Insider” and “Published” are now two separate fields. 
• Synchronization of critical tasks to Outlook gave an error and the function failed although the Exchange parameters were set correctly.
• When a customer’s assignment had subscription pricing which repeated e.g. weekly on Mondays and a user tried, with the “Create next subscription fees” button, to create more transactions than allowed by the “End after” field, the function failed and the software gave an error not informing that all the subscription transactions had already been created.   
• When a user opened an advance invoice in the CSI LakiMies version 10.1, the software gave a strange error message which needed to be clicked a few times to open the advance invoice. 
• It was possible to create a preliminary invoice by phase, even though there were no phases defined for the assignment.
• If a corporate customer whose home country was other than an EU country was lacking a VAT number and a preliminary for the customer was created, the software treated the company equally to a private person and added VAT to the invoice although the invoice taxability was supposed to be export sales with VAT 0%.
• When the assignment had multiple payers from different countries and in the preliminary invoice the cost-forward selection of the expense was changed, the VAT and net amounts of payers were displayed incorrectly both in the preview of the preliminary invoice and in the actual invoice.
• When a user tried and create several invoices simultaneously in the Billable Assignments folder, the software crashed. 
• When the user had selected point ‘.’ as a decimal separator, sending an invoice in Finvoice 3.0 format to Maventa failed.
• If a user tried and create a payment demand for an invoice which was not due, yet, the software gave an unclear error message.  
• When the subject of an invoice row was longer than 255 characters, the Procountor integration was unable to cut the subject so the invoice was not transferred to Procountor but the user got an error message about the invoice row length. 
• Invoices could not be transferred to Procountor, if the payer’s VAT number was missing.
• When an invoice including expenses with 0% VAT was transferred to Procountor, the expenses got the status “No VAT handling” in Procountor.
• If there was an extra space in the end of the invoice payer’s zip code, the Fennoa integration was unable to remove it and did not transfer the invoice to Fennoa but informed the user about the incorrect zip code.   
• When a customer’s closed assignment was reactivated and a user then tried and send an invoice to Fortnox, the integration transferred to Fortnox the assignment closing date which remained in the database but didn’t transfer the invoice which had a later date. 
• When an assignment team member’s details were edited in the CSI software, it unnecessarily triggered a user rights update also in M-Files which was integrated into the software.