This maintenance build contains minor programme improvements and some bug fixes.
Derecognition of small amounts
Since invoices and partial invoices are rounded to two digits, it can happen that a few cents remain after partial invoices have been added to the final invoice. Such trivial amounts can now easily be booked out.
If a small amount remains, this is displayed in the "Controlling" tab in the mandate settings:
If the software detects a small amount (< 0.05), the button "Write-off partial payments" is automatically displayed. If you click on this button, the small amount is booked out of the corresponding partial invoice by creating a surcharge/deduction.
The new button is for convenience. You can also get rid of the petty cash amount by selecting the command "Write-off partial payments" in the action menu of the dossier. This function has always been available, but was somewhat hidden. In contrast to the new button, which only appears for small amounts, the function "Write-off partial payment" is also available in the menu for larger amounts.
The difference is that small amounts only lead to an addition/deduction in the partial account, whereas larger amounts are transferred by the software to the bookkeeping (e.g. to the account "transitory items"). Here, such larger amounts are then available for reimbursement or for crediting to another mandate..
Allocation of 'otherwise invoiced' services
Services invoiced elsewhere can be newly selected in the dossier and assigned to any invoices via the action menu. This function is only useful for users who use automatic revenue distribution. With automatic revenue distribution, the incoming fee revenues are distributed on the basis of the database on which the invoice is based. Services invoiced elsewhere change this database (and thus the revenue distribution), as these hours were productively performed by the respective clerks.
Inheritance of Revenue Distribution Rules
The Revenue Distribution Module automatically distributes the incoming fee to the partners and staff involved on the basis of defined rules. The distribution rule is stored in the case and the invoices created from this case onwards "inherit" the distribution rule from the case at the time of creation. But what if invoices have already been created and the rule is to be changed again later? With this new build, an updated rule at case level can be inherited by the already created unprinted or unpaid invoices with one click. This saves the work of searching for each invoice, opening it and updating the rule manually.
Import accounting entries
Accounting entries can now not only be exported but also imported. To do this, you must provide the bookings to be imported in a TEXT, .csv or .xml format. With the help of the generic import editor, the bookings are then first imported into an intermediate table. The field allocation is then set in the interim table. If everything is set correctly, the bookings are then transferred to the database. The exact procedure is described in detail in a separate FAQ article.
Limiting the file size in the document archive
When archiving documents in the DMS (document archive) of timeSensor LEGAL, there was previously a maximum file size of 50 MB. However, the size of a file that you can still archive does not depend on timeSensor LEGAL, but on the (free) RAM available on your workstation. Therefore, users who have a workstation with enough RAM can archive larger files. As of this build, the system administrator can increase the maximum permissible file size to up to 250 MB by adjusting the permissible value in the Settings area under Admin/Special/System.
However, after archiving such a large file, you should definitely check briefly whether the file could be saved correctly by opening it once. A corresponding warning is issued as soon as the file exceeds the size of 50 MB.
Bug fixes and small improvements
Bug fixes and small improvements from various areas round off this maintenance update.