CSI Lawyer version 12.0 corrections 24.9.24

The below CSI Lawyer defects found in version 12.0 have been fixed and published. The CSI Lawyer version 12.1 – besides bringing new functionalities – will also correct them.

CSI Lawyer customers making their software updates from a customer specific or MSI update package can request a new 12.0 package from CSI.

List filters

• You could change the filters of the matter list, e.g. the date filter, by typing in that field, but the editing did not affect the matters displayed in the list. Now if the text written in the field finds a new filter value, e.g. “yesterday” and the new filter is confirmed with Enter or clicking with the mouse, the matter list is updated accordingly.

Conflict checks

• When a conflict check was made from the conflict search, the current user was shown as the responsible person, even though the responsible person was actually the customer responsible. The information was only displayed correctly when the saved conflict check window was opened again.

Matters

• There were errors in the matter views: 1) The Budgeted Matters view listed all active matters regardless of whether they had budgeted hours or not. 2) The “Matters with no entries for 12 months” view listed all active and inactive matters that had no transaction or expense entries for the last 12 months, even though the intention was to import only active ones.
• The access rights of the persons responsible for a protected matter were not removed, even if the user’s role of responsibility in a normal matter or team membership in a normal or insider matter was removed.
• A deactivated (passive) insurance company was selectable in the legal insurance information.

Pricing

• The software retrieved the hour price for the transaction from the role price list previously attached to the customer, even though its currency differed from the matter’s currency and the price list had since been unlinked.

Transactions

• A normal user who did not have extended rights to matters and preliminary invoices could use the Delete button on the keyboard to remove transactions added by others to matters where he/she did not have a responsibility role.
• MyDesk lost the transaction duration step defined in the business unit parameters (6 min, 15 min, etc.) when the application was closed in between.
• In MyDesk / CSI Mobile, transactions recorded by the user to insider matters were visible, even though the user no longer was a member of the matter team in question or belonged to the insider register.

Preliminary invoices

• The price adjustment made to the gross amount on the preliminary invoice did not take into account the setting determining the VAT percentage for the invoice, when the parameter selection was “According to the last invoice row date”.
• Marking several preliminary invoices as reviewed with the mass function gave an error message.
• When previewing the preliminary invoice for Swedish matters, the “Moms 25.5%” text did not fit on one line on the preliminary invoice’s specification page (when using the Finnish and country-neutral specification page templates).
• In the main/sub-matter structure, the rounded totals of the preliminary invoices and the actual invoice could differ from each other, because the software previously calculated the rounding per preliminary invoice and when the roundings were summed up for the actual invoice, the rounding for certain numbers no longer hit the nearest whole number. After the correction, rounding is calculated from the total sum of the preliminary invoices.
• When previewing an approved sub preliminary invoice, the invoice rows did not appear on the specification page.
• When a price adjustment was made to a foreign currency matter which had an expense in the bookkeeping currency, the software displayed the wrong net amount in the foreign currency “Modified Net Amounts” field before any changes were made. The total amount was missing the expense in the foreign currency.

Invoices

• It was possible to change the payer of the invoice to a customer which had a different taxability.
• After the Finnish VAT change, the preview of the invoice from the matter (without creating an invoice) incorrectly showed the old 24% tax rate, even though both the transaction date and “until the selected day” date of the preview were on or after September 1, 2024.
• Maventa rejected Finvoice invoices on which the user had selected to hide the zero rows, if the invoice contained only a tax-free expense and a zero-priced transaction with normal VAT.
• Transactions that had already been invoiced with 24% VAT before the change in the Finnish value added tax, were wrongly given 25,5% VAT on a proof invoice which was created after 1/9/24.
• The invoice rows in a proof invoice incorrectly received 25.5% VAT, even though the date of the proof invoice was set to a day that was before the Finnish VAT change on September 1, 2024.

Payments and customer fund transactions

• The “Import reference payments” function imported from camt-format materials (camt 052/053) also other credit transactions than customer payments when the country-specific plugin for Estonia, Latvia and Lithuania was in use.
• The number series of customer fund transactions and vouchers did not follow the formatting defined for them.

Integrations and customizations

• If the customer’s business ID was missing when the identification was started in DOKS, the error message in Swedish incorrectly referred to a missing address.
• NetDocuments API tokens expired under a certain error condition. When a team member was added to a matter protected by access rights or to an insider assignment, after updating the access rights, the software gave an error message that the credentials had expired.
• The Fortnox accounting integration now brings the expense (net amount) credited in Fortnox to the CSI software with a minus sign. Thus, Fortnox and CSI show the same numbers, and the customer can monitor the status from either system.
• When using the subcontracting functionality, the transfer of transactions from the subcontractor to the supplier was unable to transfer numbers (billable hours, unit price or total price) or dates if the default formats of the date or numbers in the sender’s and recipient’s operating systems were different.  After the correction: 1) If the date field format conversion is not successful at the sender end, the transaction is logged for the current day and an important note is added:  ‘Unknown date format: ‘{0}’. Conversion failed. Transfer date set as the date of the transaction.’ {0} is the date in the format sent by the subcontractor. Finally, a warning is displayed if there are date errors in the transferable transactions. 2) If the conversion of the formatting of a number field is not successful, an error message is displayed, and the transfer is cancelled.
• If the Status field was customized into the matter, corporate customer or private customer view, the view took a long time to load and eventually the status information was not displayed