CSI Lawyer 13.0 has been published

CSI Lawyer version 13.0 has been published and it is available for customers downloading their software updates from the web. For customers having a company-specific update package, we’ll start deliveries in the coming weeks.

The new features and changes are described in the “CSI Lawyer version 13.0 – Change document”, available on the Instructions. The version also brings corrections to some software defects reported on version 12.1.

Below you’ll find a list of the new features as well as corrected defects:

New Features

General usability improvements

• Individual reminders can now be sent to users by email, and a technical change has been made to email reminders and Outlook synchronization for critical tasks
• It is now possible to track the change history of deleted records retrospectively
• A new blue‑green default theme is available, along with a turquoise icon for important related notes

Customer

• Parallel trade names can be added to corporate customers and are included in conflict checks
• Conflict checks now cover not only the principal but also its corporate group and other parties
• Role-based conflicts caused by open matter requests are taken into account in conflict checks
• Inactive matter requests are excluded from conflict searches
• A warning is displayed if an open conflict check exists when creating a matter from a matter request
• Expiry calculation and warnings have been removed from identification events where the identification level is “Not required” or the matter has been closed
• An alternative invoicing method can be defined for the customer and matter parties
• Customer contacts can be deactivated when a corporate customer is deactivated

Matter request and matter

• The matter request window now displays contact details retrieved for the principal and allows storing matter-specific contact and invoicing details as well as role/user price lists
• An indicator has been added to the matter view to show when the subscription fee has been exceeded
• Invoice CC recipients defined at customer level can be overridden at matter level per party
• Unnecessary spaces have been removed from submatter numbering

Pricing

• Price lists added to the source matter are now copied when creating a matter with the “Use as template” function

Entries

• Timer values are automatically saved every minute
• When creating a transaction with the “Use as template” function, the date defaults to the current day
• Power users can close transaction posting periods on a monthly basis
• Expenses can be edited in bulk using the Edit multiple function
• Transfer information is stored in the notes of transactions/expenses moved to another matter

Invoicing

• Cost-forward invoicing for expense types can now be defined based on purchase information taxability
• The VAT share is shown on legal expense insurance invoices after the insurance company’s payment
• Invoice ribbon functions have been reorganized and their status handling clarified
• The invoice type is included in the name of the saved invoice PDF
• The hierarchy for determining invoice email recipients has been simplified
• The invoice front page has been updated to comply with Swedish legislation
• The rounding row from the original invoice is included in credit invoice
• The title of a payment reminder appears in the file name of the email attachment
• A separate email address can be defined for payment reminders

Payments

• When importing Camt-format payment data, the payer is matched also by name and duplicate checks are performed per payment

Reporting

• Certain total fields have been removed from the Transaction Summary (created, invoiced, paid) to eliminate inconsistencies

Access rights

• User group–specific editing rights for customers and matters have been refined
• Permissions for opening and editing matters have been separated into distinct parameters

Bookkeeping material and integrations

• In e-invoice bookkeeping material, the country is now indicated using a two-letter country code instead of the country name
• The parameter window for bookkeeping integrations has been clarified, and the Fortnox integration now supports multiple sales accounts

Corrected software defects

General

• The “Status reason” dropdown did not display reason options for an active matter if the same dropdown had previously been opened empty in a closed matter. After the fix, an empty “Status reason” dropdown will display a dash (-).
• At startup, a specific error caused the application to close without leaving any trace of the cause. After the fix, an error message is shown to the user and the error is logged in the log file.
• The appearance of the critical task calendar changed when a critical task was created by double-clicking the calendar, saving the new critical task details, and closing the critical task window.

Customer

• When the list of corporate customers contained a large number of rows and the “Parent company” column was visible but empty, sorting the list by parent company, creating a new customer, and even closing the window were extremely slow.

Pricing

• In the parameters of a private person, the hour price defined in the parameters of the corporate customer linked to its “Customer” field was displayed, even though this price is never used for private persons’ matters.
• When an hour price was defined in the parameters of a foreign-currency matter, the hour price of a new transaction was processed in the bookkeeping currency instead of the matter’s currency.

Entries

• If a default transaction type defined in the parameters (e.g. at user level) was of the type “Matter (billable)”, it was incorrectly possible to select an internal matter for the transaction. After the fix, the user will receive an error indicating that a billable transaction is being recorded to an internal matter.

Invoicing

• A price adjustment made to a preliminary invoice incorrectly populated the “Reviewed” date on the preliminary invoice.
• In certain situations, changing the payer on a preliminary invoice made it possible for the same payer to appear multiple times.
• A preliminary invoice could not be approved if it contained entries from a closed fiscal period and the “Use invoice date as entry date” parameter was enabled.

Integrations

• When automatic initiation of identifications was enabled in the DOKS integration and a new matter request was being created for a corporate customer, the software attempted to send identification data to DOKS and returned an error. After the fix, the integration no longer processes matter requests but only opened matters.
• The LEDES bookkeeping integration did not properly close open connections but instead crashed in certain situations.