Abakion Legal 27.1.202632.6333

Two new fields, Matter Category 1 and Matter Category 2, have been added to the Matter Contact Card and as default columns in the matter overview. The fields let you categorize matters by two independent criteria that you define yourselves – for example industry, geography, or priority, depending on what is relevant to your business.

Each field has its own lookup table, where you maintain your own valid values (code and description). The two categories are completely independent of each other, and each lookup table also shows how many matters currently use a given value.

The names Matter Category 1 and Matter Category 2 can be customized under Abakion Legal Setup, so you can give the fields names that fit your own categorization. If the name fields are left empty, the default names are used automatically.

Note that at this point the fields can only be filled in and displayed – there is no integration with reports, invoicing, etc.

A new Sector field has been added, which can be filled in on clients and matters. The field is shown on the client card under the Classification group, and on the matter card under "Show more" in the client info group. Sector is not a dimension, but a lookup to a new sector table with code and description.

In Client Matter Intake (CMI) the fields Client Sector and Matter Sector have been added to both CMI screens. When creating a brand-new client, the user fills in Client Sector themselves, which is then automatically suggested as Matter Sector. When creating a matter for an already existing client, both fields are filled in automatically based on the client's sector; here, Client Sector is read-only – just like the client's other fields in that situation – while Matter Sector can still be changed.

Note: This change requires the CMI app to be updated.

When a secretary or case handler creates a new payment request in the payment agent, the fields are now validated before the request can be sent to bookkeeping. It is no longer possible to submit a request if no summary code has been selected, if the Description field or Notification to recipient is empty, or if no payment method code has been selected.

If payment method code BTD is selected, either a Pay-to account must be chosen from the vendor's list, or a bank registration number and bank account number must be entered manually. The registration number must consist of 4 digits and the bank account number of 10 digits, and letters or special characters can no longer be entered in these fields.

If a FIK payment method code (71, 04, or 73) is selected, Payment ID and Creditor number must be filled in, where the creditor number must consist of 8 digits with no letters.

If the fields are not filled in correctly, a user-friendly error message is shown, so the request cannot be submitted to bookkeeping with incomplete or incorrect information.

In newer versions of Business Central, Microsoft has introduced a new setup page for reminder terms, where reminder levels are shown as part of Reminder Terms Setup instead of the previously standalone Reminder Levels page. Until now, our customizations — including the mail template field and the Templates button — only worked on the old page.

Our customizations have now also been added to the new Reminder Level Setup view, so the Templates button is available in the same place and opens correctly filtered to the relevant reminder terms and level. The old Reminder Levels page continues to work unchanged, so both pages work side by side during the transition period.

There is no change to the underlying logic for sending reminders or emails — the change only affects where the functionality is shown.

A new column, Start Date, has been added to the Employee Price List report, showing the date from which the displayed price applies. At the same time, an error has been fixed where the employee's full name could show a double space if the employee had no middle name registered.

In addition, a new filter, Job Title Category, has been added to the report's request page, so the report can be limited to employees with a specific job title category.

A new field, Summary Code, has been added to G/L Entry.

The field is filled in automatically with the value from the corresponding field on the journal line when a general journal is posted. The field cannot be edited directly on the entry.

Note that the transfer only applies to entries posted via the general journal — the field is not transferred when sales or purchase documents are posted.

The field is not shown on the screen in this version.

On the Contact Matter Subtype page, the fields Matters created and Matters completed showed incorrect numbers, because a filter accounting for whether a matter was archived was missing.

Matters completed is now calculated based on the matter's archiving date instead of its creation date, so only matters actually closed (archived) within the selected period are counted.

For matters that were already archived before the fix, the archiving date has also been filled in automatically via an update run, so historical figures are now correct as well.

When creating a new subfolder in Folders while a file was simultaneously selected, the new folder was shown with incorrect indentation in the folder tree. The error did not resolve itself — a full synchronization was required to fix the display, since a partial synchronization could not correct it.

The issue has now been fixed, so new subfolders are shown with correct indentation from the start, regardless of whether a file is selected at the time of creation.

In the Time Specification - Invoice Draft and Time Specification - Invoice reports, the columns for client number and job number are now shown with text retrieved from the dictionary, instead of being hardcoded in the report.

Two new translations have been added to the dictionary:

• TimeSpecClientNoCaption – Client No. / Client No.
• TimeSpecJobNoCaption – Job No. / Job No.

This means the text for these two fields can now be translated and customized via the dictionary, as is already the case for other fields in the reports (e.g. date and description). The existing texts have been kept as default, so existing layouts continue to look the same as before.

When the Tasks list was opened via the Tasks button in the menu on the matter card, the horizontal scrollbar started centered instead of aligned left. This meant the user had to manually scroll back to the left to see the first columns, such as Closed, Date, Type, and Description.

The error occurred because the page opened in edit mode, which caused Business Central to automatically focus on the first editable field in the list, pulling the scrollbar to the right with it. The page now opens in view mode instead, so the scrollbar starts on the left as expected. To edit an entry, you now need to click Edit List.

The issue only occurred when opening via the button on the matter card — not when navigating directly to the task list.

On the Matter Statement report, the postal code was missing on both the client's address and the company's (office) address, so only the city was shown. The bank details on the report also only showed the account number, without the corresponding registration number.

The report has now been fixed so that postal code and city are shown together on both addresses, and the registration number is shown together with the account number on the Account No. line.

At the same time, the obsolete Giro No. field has been removed from the report.

When deleting selected time entries via the Delete Selected Entries action on the Time Entries Out of Sync page, the user could experience a permission error on job ledger entries – this also happened for users with full rights (SUPER).

The error was caused by the system attempting to update a job ledger entry that had not been retrieved correctly. This has now been fixed.

Time entries that had been correctly settled were shown in red with a validation error on the time registration screen. The page inspection showed the error "Job ledger entry is closed", even though the related job ledger entry had been correctly invoiced and there was no actual problem with the entry.

The error occurred because the validation triggered simply because the related job ledger entry was closed at invoicing — without accounting for whether the time entry actually deviated from the closed job ledger entry. This has now been fixed, so a time entry that matches its settled job ledger entry is no longer flagged with an error. However, if there are unposted changes on the time entry that cannot be written back, the error is still shown correctly.

It is still not possible to change a time entry on a closed job ledger entry — here, the error "Job ledger entry is closed" is still shown as expected. Entries already affected are cleared automatically via the scheduled rerun, or manually with "Retry" on the Time Entries with Errors page.

In the Matter List w/ Balance report, the Hide matters with existing bank accounts setting could cause all of a client's matters to be hidden in the report — even if only a single matter for that client actually had an associated bank account.

The error occurred because the report did not distinguish between a bank account associated with the client in general and a bank account associated with a specific matter. This has now been fixed, so the filtering happens in two steps: if the client has a bank account with no matter association, all of the client's matters are hidden as expected. If a bank account is only associated with one specific matter, only that matter is now hidden — the client's other matters are still shown correctly.

The background process that synchronizes time entries to job ledger entries could, in rare cases, start multiple times simultaneously. This caused locking conflicts and error messages, and in the worst case, duplicate job ledger entries were created for the same time entry. In addition, a single faulty time entry (e.g. "another user has changed the entry") could stop an entire ongoing run and put the time queue in Error status.

We have therefore rebuilt the time queue itself. Synchronization now runs in shorter, defined batches (10 minutes by default) instead of running continuously for up to 5 hours, and the system now ensures in a more robust way that no more than one synchronization ever runs at the same time. Each time entry is also processed individually and in isolation, so an error on one entry can no longer stop the rest of the synchronization — and even if two runs were to overlap, duplicate job ledger entries can no longer occur.

On the Abakion Legal Setup page, a new group, Time Queue, has been added with settings for loop duration and retry interval for failed entries, as well as status fields for the queue and retry queue. This also includes the new actions Stop Time Queue and Start Time Queue, so synchronization can quickly be stopped and restarted as needed. Failed time entries are also automatically retried (hourly by default) instead of having to be fixed manually.

Finally, an error has been fixed where a time entry marked for deletion was never removed from the queue if the related job ledger entry had already been deleted — the entry was instead processed in vain on every run.

When creating combined invoices (invoices not linked to a specific matter), the invoice's currency code could be set incorrectly for clients set up as a customer.

The invoice previously retrieved the currency code from the client's general currency field instead of the customers's Default Invoicing Currency Code. This has now been fixed, so combined invoices correctly use the debtor's Default Invoicing Currency Code. If the customer has not specified an invoicing currency, the invoice is set to the local currency (DKK).

The Annual Report report previously showed the incorrect heading "Closing Trial Balance" — both on the request page and on the printed report itself.

The text has now been corrected in both places, so both the request page and the report heading correctly show "Annual Report". The report's functionality and layout are unchanged.

As part of the fix, a translation error has also been corrected on a field on the request page, which now correctly shows "Show amounts in additional reporting currency".

This release prepares for a fix to an error on the Bank Account Card, where editing the Name field (and other fields) could not be saved.

The field Linked to Matter Time on bank accounts has been renamed internally and replaced with a new field. Existing data is automatically moved to the new field the next time the user logs in — this happens in the background and requires no action.

Note: The actual error when editing the Bank Account Card has not yet been resolved in this release. That will happen in an upcoming release, where the old field is removed entirely and the issue disappears for the user.

When sending a reminder for a combined invoice covering multiple matters for the same client, the invoice was attached as a PDF once per matter, instead of once in total. For example, if the combined invoice had 14 matters, the customer received the reminder email with 14 identical invoice attachments.

The error occurred because each matter on the combined invoice generated a separate reminder line, and the invoice was attached for each line without checking whether the document had already been attached. This has now been fixed, so each invoice document is only attached once per reminder, regardless of how many matters the combined invoice covers.

Reminders covering multiple different invoices are not affected — here, each invoice is still correctly attached once.

When performing Cancel Application on a payment covering invoices from multiple different matters, the postings created by the cancellation could get the wrong matter number and other matter-related information. The cause was that the system used the information from one of the matters for all the other entries in the cancellation – instead of retaining each entry's own matter. Among other things, this meant it was no longer possible to trace the G/L entries back to the correct matter, and the split between receivables and payables as well as matter reporting became incorrect. The error has now been fixed, so both detailed debtor entries and G/L entries are now correct.

When completing a search step in CMI (e.g. conflict or party search), the system could show an error if one of the contacts found had a very long address. The error occurred when the search result was to be saved as a search line.

The cause was that the Address field on the search line could not hold as many characters as the field on the search result. This has now been fixed, so the field can hold addresses of the same length as the rest of the system, and the search can be completed without errors.

There was an error in the search engine's phonetic search that could be triggered when a name generated a phonetic search string close to an internal limit of 50 characters. The error was first discovered via CMI matter creation, where the search step could fail with a technical error message stating the search string was too long – but the problem lay in the search engine itself and could therefore in principle occur anywhere phonetic search is used.

The cause was that the search engine wraps the phonetic search string with wildcard characters, which in certain cases made the string a few characters longer than the allowed limit. Search from the Outlook add-in has also been fixed.

Users should therefore no longer experience this error, whether the search happens via CMI matter creation or via the Outlook add-in.

When a matter was created via the CMI form with automatic time registration enabled (set up under CMI Setup → Matter Time Registration), the time entry could be created with an error. The error appeared as "missing the following information: Responsible Attorney" on the time entry — even though the Responsible Attorney field was in fact filled in correctly on the CMI form before the matter was created.

The cause was an ordering issue in the internal process: the time entry was validated before the matter's contact information had finished being created. The process has now been fixed, so the time entry is created after all necessary information on the matter is in place, allowing validation to complete correctly.

The fix applies to both regular matter time registration and time registration in connection with KYC.