Abakion Legal 27.1.202619.5836 & Abakion Legal DK 27.1.202619.5833

You can now save a history of your searches as a PDF document to provide evidence of how searches were conducted and what results were found. The feature is available from the Register KYC page, where a new button "Save search history" allows you to select between searches. These are saved as PDF files in the relevant KYC folder in SharePoint.

The search history displays the key fields from your searches, such as date, user who performed the search, and search results. You can filter by user and date before saving.

A new queue called Upcoming Tasks has been added to the Abakion Legal Basic role center. The queue displays tasks due within the next 14 days, providing a quick overview of what is coming up.

The number of days can be configured via a new date formula in Abakion Legal Setup. If the Upcoming Tasks Date Formula field is not filled in, a default of 14 days is used. Clicking the queue opens the task list filtered to the selected period.

The queue is placed between Overdue Tasks and All Tasks on the role center.

The Matter Label with Party report has been given a new layout with a left-aligned header section. The new layout is set as the default and will automatically be used when printing.

The previous layout with a right-aligned header is still available and can be selected via Report Layout Selection in Business Central if preferred.

Previously, the invoice logic required a client to always have an associated customer card. This meant that clients used as invoice recipients — e.g. co-clients without their own matters — could not be invoiced correctly, as the system was unable to find the necessary invoicing information.

The process has now been changed so that invoicing is always based on the contact card rather than the customer card. Clients and parties are therefore treated equally in the invoice logic, and it is now possible to invoice using a client card without a customer card being created.

The client card has been given a new Invoicing panel where all invoicing-related fields are now consolidated. Fields such as Include Time Entries on Invoice and Fee Specification Level have been moved here from the general panel, and new fields have been added: Default Invoice Currency Code, Document Sending Profile, Gen. Business Posting Group and VAT Business Posting Group. With the Abakion Legal DK app, EAN No. and OIOUBL Profile Code are also added to the client card. When a customer card is created from the client card, any values entered manually are respected — they are no longer overwritten by the customer template defaults.

A new checkbox Hide Zero Entries on Reports has been added to Work Types. When checked, entries with an amount of 0.00 for that work type will automatically be hidden on the time report.

The function evaluates each entry individually. This means that if one employee has registered 0.00 and another has registered an amount for the same work type, only the zero entry will be hidden — the other registration will still be shown.

The checkbox can be set on multiple work types simultaneously, and all will be respected on the report.

The My Matters view, which was previously only available in the role center, is now also available as a FactBox on the right-hand side of the screen.

The FactBox has been added to the Matter List, Archived Matter List and Matter Card, providing a quick overview of the matters assigned to the current user — without having to navigate back to the role center.

The FactBox is positioned at the bottom of the right-hand panel so it does not interfere with existing FactBoxes.

It is now possible to edit Date, Description and Employee directly from the Task List without opening the individual task card. Use the Edit List button in the action bar to enable editing. This saves time, for example when a main hearing is rescheduled and multiple tasks need to be updated with new deadlines, descriptions or employees.

The Allowed Time Interval (minutes) field can now be specified directly on the client card. Previously, the time interval was controlled centrally via Abakion Legal Setup only, meaning all clients shared the same interval.

With this change, the central value can be overridden for individual clients. This is particularly relevant for clients with specific billing requirements — e.g. clients receiving LEDES invoices, where the time interval typically needs to follow a specific standard. Instead of adjusting the central setup to suit one client's requirements, the interval can now be set precisely where the need exists.

If the field is not filled in on the client card, the value from Abakion Legal Setup is used as a fallback. The field is not shown by default on the client card and must be added via page personalisation.

It is now possible to enable a restriction that prevents time from being registered on a matter with a date prior to the matter's creation date. The setting is found in Abakion Legal Setup under the Employees and Time Registration group and is called Block Time Registration Before Matter Creation Date.

If an employee attempts to create or edit a time registration with a posting date before the matter's creation date, the line will be marked with an error — in the same way as for blocked or archived matters. The same applies if you attempt to change the posting date on an already posted entry in Job Ledger Entries.

The setting is disabled by default, so existing behaviour is not changed unless the office administrator enables it.

The Format String and Date Format fields on data source lines now correctly support formatting of field types such as time (Time), datetime (DateTime) and integer (Integer) — in addition to the previously supported date and decimal fields.

Previously, Format String and Date Format were only applied to date and decimal values. If a data source line pointed to a time field, the formatting was ignored and the value was inserted unformatted in the document.

The system now looks up the actual field type and applies the formatting correctly. For example, if you have a time displayed as 19:14:27 and want it shown as 19.14 (hours and minutes with a period, without seconds), you can set Format String to <Hours24>.<Minutes,2> on the relevant data source line.

Note that Format String and Date Format are now mutually exclusive: if Format String is filled in, it is used. Date Format is only used if Format String is empty.

It is now possible to configure the Allowed Time Interval (minutes) field directly on the Matter Card. The field controls which time intervals are valid when registering time entries on the matter — for example, a value of 6 means that time may only be registered in intervals divisible by 6 minutes.

If the field is not filled in on the Matter Card, the value from the client card is automatically applied. If it is not filled in there either, the value from Abakion Legal Setup is used. The order of priority is therefore: matter → client → Abakion Legal Setup.

The field is hidden by default on the Matter Card and can be shown via the Personalise page in the same way as on the client card.

When an attention person was removed or changed on the Matter Contact Card, the change was not always synchronised correctly to the client's Relations line. This meant that an old attention name still appeared on new invoice drafts, even though the field was blank on the matter contact card.

This has now been fixed so that deletion and changes to the attention on the Matter Contact Card correctly take effect on the relation line — and new invoice drafts reflect the current attention person.

The subject line of emails containing invoices and credit memos was previously generated automatically by fixed logic in the system. It was not possible for customers to customise or translate the subject line.

The subject can now be configured in the Dictionary in the same way as is already known from reminder emails. Create a dictionary entry with the bookmark InvoiceEmailSubject %1 %2 %3 for invoices or CreditMemoEmailSubject %1 %2 %3 for credit memos, and add translations for the relevant language codes. The merge fields are replaced automatically: %1 = document number, %2 = document name and %3 = company name.

For new companies, default values for Danish and English are inserted automatically, e.g. "%3 - Invoice No. %1". For existing companies, the dictionary entries must be created manually — until then, the previous default logic is used, so existing emails are not affected.

The Long Date Formatting field in Invoice Setup has been replaced by a new field called Date Format. Where previously you could only choose between short date format (dd-mm-yy) and long date format (e.g. "April 10, 2026"), you can now choose between three options via a dropdown.

The change applies to all dates on sales documents — including invoice date, due date, period indication and payment terms — across invoices, credit memos and drafts.

Existing customers who had enabled long date format will automatically be migrated to the corresponding setting in the new field, so no manual setup is required after updating.

A new page, Liability Adjustments, has been added which saves a history of completed Liability adjustments.

When you run the Adjust Client/Matter Liability report and select Save in the settings, the run is automatically saved with the date, time, Liability date, adjustment amount and who ran the report. The report is saved as a PDF and can be opened at any time via the Show Historical PDF action on the relevant entry.

The change ensures that Liability adjustments are retained in the system, and that you can always document and retrieve previous runs.

It is now possible to save reminder emails in SharePoint in the same way as invoice and credit memo emails. The function is enabled with the new field Save Reminder Emails in DMS in Document Setup.

Reminder emails are saved in the folder specified in the Invoice Folder field in Document Setup. A separate folder for reminders is not created — they are saved together with invoices and credit memos.

The email subject line is controlled via the Dictionary with the bookmark ReminderEmailSubject %1 %2 %3 %4 %5, where %1 is the reminder number, %2 is the document name, %3 is the company name, %4 is the matter number and %5 is the reminder level. The subject line follows the language code of the invoice recipient (Bill-to Contact) and is independent of the user's language layer.

Note: If the same reminder is sent multiple times, only the first email is saved in SharePoint. This is because the file is written with the same filename, and SharePoint does not overwrite an existing file. Rename the existing file in SharePoint before resending if both emails need to be saved.

A new setting has been added to the Payment Agent Setup page: Vendor Payment Method from Agent. The setting controls where the payment method code is retrieved from when a new vendor is created via a payment agent entry.

When the setting is disabled (default), everything works as before — the vendor receives its payment method from the vendor template. When the setting is enabled, the payment method code is instead retrieved from the payment agent entry, so it automatically reflects the payment method registered on the specific payment.

The change only affects newly created vendors. Existing vendors are not affected.

New validations and automatic population have been added to ensure that Liability Level and Group No. always match on the Customer Card and Job Card.

When you create a new matter from a client, the system now automatically retrieves Liability Level and Group No. from the customer card — so you no longer need to remember to fill them in manually.

The validations are active when Use Group Liability is enabled in Invoice Setup. The system then prevents invalid combinations: if a customer has Liability level Client, the job card cannot be set to Group — and vice versa. It is also not possible to enter a Group No. on either the customer card or the job card unless the Liability level is Group. If Group No. is removed from the customer card, the Liability level is automatically reset to Client, and associated matters are updated accordingly. When Use Group Liability is disabled, Group No. operates independently of the Liability level and no validation of the relationship between the two fields is performed.

The Liability Level field on the Customer Card is now correctly displayed with English labels (Client and Group) in the English user interface.

The AI Setup page has been restructured internally so that it now functions as a shared setup for all AI features in Abakion Legal. There are no changes to the user experience.

The bookmarks for Court District are now available in the Contact Relation data source, which is used when merging documents via SharePoint.

When new data sources are created, the court district bookmarks will automatically be included in Contact Relation. Existing data sources are not updated automatically — if you want the bookmarks on an already created data source, they must be added manually.

When a production database was copied to e.g. a sandbox, the SharePoint setup was carried over — and the integration could unintentionally run against the production SharePoint sites.

Two new fields have been added to the SharePoint Setup page: Environment Name and Company Name. These fields indicate which environment and company the setup belongs to. If the current values do not match the saved ones (e.g. after a database copy), the SharePoint integration is automatically disabled. All existing configuration is retained — nothing is deleted.

On the SharePoint Setup page, a notification is displayed if there is a mismatch, with a message about what the setup is configured for and what the current environment is. Use the new Populate Server Info action to activate the integration for the current environment with a single click.

The setup packages for Abakion Legal (both DK BASIC and EN BASIC) now contain a full set of country codes equivalent to a standard Cronus company. Previously, only three country codes were created on import, meaning the consultant had to create the rest manually.

The country code for Germany has been corrected from D to DE, and the spelling error "Storbritanien" has been corrected to Storbritannien in the Danish package.

When importing into a new company, all country codes are created automatically and can be used immediately on contacts, customers and vendors. Re-importing the package does not create duplicates.

When an employee was deleted via Inactive Contacts, the associated user in the system was not handled automatically. This meant the user remained active even after the employee had been removed.

Inactive Contacts has now been extended so that when an employee is deleted, the associated user in the system is also deactivated. The user setup linked to the employee is also deleted.

The fix ensures that inactive employees do not leave active user accounts in the system.

When an employee was deleted via Inactive Contacts, the employee's Employee dimension code was not removed from existing entries. The employee's identity was therefore still visible in general ledger, matter, resource and bank account entries.

This has now been fixed. The dimension value is automatically replaced with the initials for deleted employees configured in Personal Data Setup.

The correspondence list on the client card did not show the same columns as the correspondence list on the matter card. Among other things, the Date Modified column was missing and could not be added.

The correspondence list on the client card has now been updated to match the equivalent list on the matter card. In addition, the Show on Portal field has been removed as it was no longer in use.

When attempting to import a timer line into a time registration for an archived or blocked matter, an unclear error message was previously displayed stating that the matter could not be found in the related table.

A descriptive error message is now shown instead: Cannot transfer the timer line. Matter [matter number] is archived or blocked.

When registering time on a matter marked as non-billable, the error message was previously only shown when the user left the line or the page. The validation is now performed as soon as a work type is selected, making it impossible to choose a billable work type on a non-billable matter.

If attempted anyway, the error message is shown immediately: Billable time may not be registered on this matter.

The Default Time column on work types was not being applied during time registration. This has now been fixed so that the default time is automatically populated when a work type is selected.

Note: If a quantity has already been entered, it will be overwritten by the default quantity when a work type with default time is selected. The function only applies to time registration in Business Central — not in the Outlook add-in.

If Contact Validation Setup was set to matter time registration and Mandatory Fields were configured on the matter, time registrations with missing mandatory information (e.g. missing Responsible Lawyer) could incorrectly be saved without a validation error — the error only appeared afterwards in the job queue and not in the registration page itself.

Validation now checks mandatory fields directly in Time Registrations, so the user receives an error message immediately if a mandatory field is not filled in.

The Show Price Explanation function on Job Ledger Entries displayed a misleading message when no price line was found for the relevant currency in Abakion Legal Resource Prices. The message stated that the price was set to 0 on a resource group — when in reality no price line had been found at all.

The fix now correctly distinguishes between three scenarios: (1) a price line was found, (2) no price line was found but the resource card has a default price, and (3) neither a price line nor a default price was found. The price explanation now clearly describes which scenario applies.

When filling in the Client Civil Registration No. field in a CMI flow with a value that did not follow the Danish CPR format (DDMMYY + four digits), a runtime error ("The value cannot be evaluated to type Integer") could occur when executing the CMI step.

The error occurred because the validation attempted to calculate a date of birth from the entered characters without first checking that the input was actually numeric. If letters were included in the value, for example, the calculation would fail.

The validation has now been corrected so that invalid input is handled correctly without producing an incomprehensible error message.

The Matter Budget field in the Details FactBox on the Time Registrations page always showed 0.00 — even when a budget had been created on the matter via Matter Planning Lines.

The error meant that the matter budget could not be seen during time registration, while the correct amount was displayed elsewhere, e.g. in the FactBox on the Matter Contact Card.

The error has now been fixed so that Matter Budget in the FactBox on Time Registrations shows the correct amount, regardless of whether all entries are shown or filtered from the latest budget date.

The Next Activity field on the matter card could display an incorrect date, even when no task or workflow was associated with the matter. The date also moved forward automatically by one year at a time without any visible reason.

The error was caused by the next activity calculation not correctly identifying the associated matter before retrieving the date. This has now been fixed so that Next Activity always shows the correct date based on the matter's own tasks and workflows — or is empty if there are none.

When a posted invoice for a matter in currency was copied forward and the exchange rate was subsequently updated on the document, an error occurred on posting.

The cause was that the matter number was not transferred correctly to the sales line when the document was copied. When the posting date was then changed and the exchange rate updated, the system attempted to recalculate the currency based on lines that were missing the matter number — and failed.

The fix ensures that the matter number is now transferred correctly when copying the document forward, so that changing the posting date and recalculating the exchange rate can be completed without errors.

When invoicing and settling matters in foreign currency (currency matters), errors could occur in the calculation of Usage Amount (LCY) and the associated amounts in the local currency.

The following errors have been fixed: When posting an invoice in foreign currency on an LCY matter, the currency factor on the Job ledger entries was not applied correctly, causing the amounts in local currency to be incorrect. In addition, the exchange rate was not updated correctly when time was settled back into the distribution, which could cause an over-coverage. Finally, the currency code was missing on reposting entries, and the currency factor on these entries was incorrectly set to 1 instead of reflecting the invoice rate.

The fixes ensure that Usage Amount (LCY), currency code and currency factor are now calculated and saved correctly across invoicing, settlement and reposting on currency matters.

On English invoices and credit memos, the accompanying PDF attachment was previously named using the Danish text "Fakturanr." or "Kreditnotanr." — regardless of the language the invoice was issued in. This meant English-speaking customers received a PDF with a Danish document name.

The error was caused by the document name being hard-coded to Danish text instead of retrieving the language-specific translation. The fix means the document name is now looked up via the translation table based on the customer's language code, so English customers receive "Invoice No." and "Credit Memo No." as the document name. The same applies to the attached time report PDF, which is now named "Tidsrapport - faktura" or "Time Report - Invoice" depending on the customer's language setting.

Upon update: Translation entries are automatically created in the Dictionary for the standard language codes DK and ENU. If the office uses other language codes, the corresponding translation entries must be created manually in the Dictionary.

When changing the invoice recipient on a sales invoice to a contact person belonging to a different client than the existing invoice client, Invoice Email was retrieved from the contact's general email address instead of the contact's Invoice E-Mail. In addition, Invoice CC Email was not updated at all.

The error has now been fixed so that Invoice Email is correctly retrieved from the contact's dedicated invoice email address — with fallback to the client's invoice email address — even when the contact person belongs to a different client. In the same way, Invoice CC Email is now also updated correctly in this scenario.

The behaviour was already correct when the contact person belonged to the same client, or when the contact was a party without their own customer card.

When a general journal line was created for a matter with a customer in foreign currency (e.g. EUR), the warning for Max. Matter Credit Limit (LCY) could be triggered at incorrect amounts. The warning appeared either too early or too late depending on the exchange rate.

The cause was that the matter balance was calculated in the customer's currency instead of in the local currency. Since the limit is defined in local currency (LCY), the comparison produced a misleading result.

The error has been fixed so that the matter balance is now always calculated in local currency. The warning is therefore triggered precisely when the calculated balance in LCY exceeds the configured limit in Abakion Legal Setup.

When the Client Interest Calculation distributed interest across matters under a client, the matter balance was calculated as of today's date instead of the interest period end date. This meant that matters that had a balance during the interest period but were settled afterwards did not receive their share of the interest.

The distribution of interest is now based on the matter balance as of the interest period end date. Archived matters are not included in the distribution. Please note that matters that previously did not receive interest (because they were settled at a later date) may now receive an interest amount and therefore need to be settled again.

The Interim Invoice Remaining Amount (LCY) field in the Matter Information FactBox on the Matter Contact Card and Matter List showed no value, even when Interim invoices had been registered on the matter.

The cause was that the calculation was no longer retrieving data from the correct location after the Interim invoice functionality was changed. The field has now been corrected to correctly calculate the outstanding Interim amount on the matter.

At the same time, the field caption has been updated to Interim Invoice Remaining Amount (LCY) to clarify that the amount is shown in local currency — consistent with Balance (LCY) and Client Balance (LCY) in the same FactBox.

The Adjust Exchange Rates report calculated an incorrect Liability balance in a specific scenario: when a matter's Liability Level was set to Client, but the associated customer's Liability Level was set to Group.

The error meant that the exchange rate adjustment amount was in some cases posted to the wrong account.

The fix ensures that it is the matter's Liability level — not the customer's — that is used as the basis for the balance calculation in the exchange rate adjustment report.

In the Client Interest Calculation report, all of a client's archived matters were shown in the matter overview — including matters with no balance in the period that do not contribute to the interest calculation.

The report now only shows the matters that actually contribute to the interest calculation. Archived matters with no interest share are filtered out and no longer displayed.

When the Dimension 1 Mandatory setting is enabled in General Ledger Setup, the system automatically blocks bank accounts that are missing correct dimension setup. Previously, the user received no message if they tried to remove the block on a bank account with invalid dimensions — the block remained, but with no explanation.

A clear error message is now displayed explaining the reason. If Dimension 1 is missing and a posting group has been selected, the message states that the dimension must be filled in. If the default dimension has an invalid value posting (not set to "Same Code"), the message states which dimension needs to be corrected.

When reminders were created via Create Reminders, global relations — e.g. Client Manager — were retrieved from the matter. If a field was empty on the matter, it remained empty on the reminder, even if the same relation was filled in on the client.

This meant that global relations maintained only on the client card never made it onto reminders created per matter or per document.

The fix adds fallback logic: for each of the six global relation fields, the system now checks whether the value is empty on the matter — and if so, retrieves the value from the client. The fallback lookup only occurs when the reminder is linked to a matter.

When exporting client payments to Danske Bank, company clients with a populated Date of Birth field could incorrectly be rejected with the error message "Missing reference number" — even though the client had a valid CVR number.

The cause was that the system checked for date of birth before CVR number. If a company client had a date of birth, it was treated as a private client without a CPR number, and the export was rejected. The priority has now been corrected so that the CVR number is always used as the reference for company clients, regardless of whether a date of birth is populated.

In Correspondence on the matter card, the Number of Entries column was displayed incorrectly for folders whose name started the same as another folder. For example, the Documents folder would show 12 entries instead of 6, because entries from the Documents 2 folder were incorrectly included in the count.

The error was caused by the counting logic matching on the beginning of the folder name instead of the exact name. This has now been fixed so that Number of Entries only counts files that actually reside in the relevant folder.

Amounts and dates on Invoices, Credit Memos and Drafts were previously formatted based on a fixed list of language codes in the code. This meant that new languages or variants — e.g. EN-US vs. EN-GB — did not always get the correct decimal and thousands separator or the right date format.

The formatting has now been changed so that it automatically looks up the ISO language code in the Language Code table. The decimal and thousands separator and date format are then determined by the configured ISO code — e.g. en-US for United States, en-GB for United Kingdom and da-DK for Denmark. If a language code does not have an ISO code filled in, en-US is used as the default.

The fix applies to both BaseApp and DKApp, and no further setup is required beyond the ISO language code being filled in in the Language Code setup.