Detailed Changelog for Continia Expense Management 2024 R1
This article lists all new features and bug fixes for each version of Continia Expense Management 2024 R1.
Tip
As a Continia partner, you can be notified of new Expense Management versions and service packs whenever they're released. To sign up for this service, go to this page in the Continia PartnerZone (only available to partners).
Important
Currently, Expense Management supports BC v14 and the three latest versions of Business Central. This will change with the release of Expense Management 2025 R1 (26.00) in April 2025. Expense Management 2025 R1 (26.00) and all future versions from then on will only support the three latest versions of Business Central.
The next version of Expense Management – Expense Management 2024 R2 (25.00) – will be the last version with support for Business Central April 2019 (BC v14).
Expense Management 2024 R1
Release date, online: April 2, 2024
Release date, on-premises: April 11, 2024
App version: 24.0.0
Fob version: 24.0.0
Note
With its 2024 spring release, Expense Management will make a version leap from 12.00 to 24.00, meaning that versions 13.00–23.00 don't exist and never will. This was done in order to align the versioning of Expense Management with that of Microsoft Dynamics 365 Business Central.
New or changed functionality
| Functional area | Description | Id |
|---|---|---|
| Country and Regional | In the Belgian localization, an option to post an expense report by using multiple document numbers has been introduced. This is to ease the payment processing and is especially helpful for the EB Payment Journal. The functionality can be enabled in Expense Management Setup on the Expense Report tab: Post on multiple document numbers. | 46157 |
| Country and Regional | With the introduction of Enforced Digital Vouchers in BC23.2, attaching documentation as incoming documents, prior to posting purchase document and journals, will in certain localizations become mandatory. When using Expense Management in an environment where Enforced Digital Vouchers are configured to check for attached files prior to posting, Expense Management will transfer the underlying digital vouchers to the posted documents. When posting an Expense, the digital voucher will be enforced, and the expense cannot be posted without providing an attachment, which becomes the digital voucher. When posting Mileage and Per Diem, a tax report extract will be generated. This serves as a digital voucher for these documents. How to enable the feature:
| 50995 |
| Credit Card Transactions | When using Enable Multiple User per Card on payment types, the credit card mapping fields (specified on Expense Management Setup) were shared across multiple payment types, making it difficult to use the functionality when having multiple payment types with different mapping rules. The functionality is now moved on a Payment Type level and it makes it possible to have different fields for different payment types. | 53513 |
| Credit Card Transactions | Transactions posted at import are no longer marked as System-Created Entry in the ledgers. | 53759 |
| Expenses | Expense Management now supports distribution codes, giving the possibility to automatically allocate expenses based on predefined rules on the expense types. The distribution codes can be added on the expense types and automatic allocations will be triggered when the document is sent for approval. In the Australian localization, the distribution codes can also allocate based on the GST percentage, once the AMOUNT INCLIDING TAX field is used. The allocation will also happen if the user changes expense types on the documents. | 50042 |
| Expenses | An EventPublisher "OnBeforeValidateAttachments" has been added in Codeunit 6086321 "CEM Expense-Validate" to allow bypassing our standard Expense Attachments validation. | 51117 |
| Expenses | The field Matched to Bank Transaction has been added on Posted Expense List and Card pages. | 53354 |
| General Application | The following events were updated in Codeunit 6086338 "CEM Settlement-Post":
| 49134 |
| General Application | A new GDPR Retention Period (Years) field has been added to the Expense Management Setup page, to be used with the newly introduced Run GDPR Maintenance action on the Expense Management Setup page. This action deletes all data stored in Expense Management related to the posted documents older than the GDPR retention period (fiscal years) specified. | 49231 |
| General Application | Posting Date has been added to expenses and mileages. | 50039 |
| General Application | Updated By Delegation User was changed to Submitted By Delegated User. | 50295 |
| General Application | Submitted By Delegated User is added to Expense Report. | 50297 |
| General Application | The following procedures on Page 6086402 "CEM Client Addin - Settlement" are now available for external access:
| 50553 |
| General Application | The column User ID has been removed from the Document Log Entries and System Log Entries pages. The change has been made to comply with GDPR legislation in certain countries, such as Germany. To adhere to bookkeeping legislation in other countries, like Denmark, the value remains accessible via Page Inspection (zoom). A user with sufficient permissions is still able to inspect the user ID by using the Page Inspection (zoom). | 52236 |
| General Application | Enabling the option Check for attachment before posting of purchase document in the Expense Management Setup page specifies if the system should display an error message if no incoming document or Expense Management file is associated with the document at the time of posting. The check is imposed both on purchase documents and purchase journals. The option only applies to on-premises environments and Business Central versions 23.1 and earlier. | 52927 |
| Per Diem | When users travel to the same destination for more than 3 months, the rate will be set to taxable in Per Diem. This is known as the "3-months rule" in Germany, and it's only available in this localization. The setting can be enabled from the Expense Management setup page under the Per Diem tab. This functionality relies on the Address Code to do the calculations. | 46291 |
| Purchase Contracts | The system analyzes posted expenses and searches for recurring expenses, 3 in a row, to find possible purchase contracts. The users will get a notification on the Expense Card and the Expense List pages if, based on the analysis results, the selected expense is recurring. There are two different notifications:
| 50208 |
Bug fixes
| Functional area | Description | Id |
|---|---|---|
| Credit Card Transactions | The error message appearing when creating Bank Transactions where Bank Country/Region field is not in the Bank Country Mapping table, has been improved. | 41048 |
| Credit Card Transactions | When using the EM Bank Reconciliations with multiple bank accounts, the Balance Last Statement and Statement No. would have been incorrectly calculated. | 53165 |
| Document Approval | Approvers are now able to modify Expense Allocations when Expense is part of an Expense Report in Pending Approval Status. | 54255 |
| General Application | Following Event Publishers have been made public/external:
| 49563 |
| General Application | The RTC Client would have crashed if the first attachment file was not available. The issue was introduced in the version 12.01. | 52792 |
| Country and Regional | In the Australian localization, when using distribution codes and both the AMOUNT INCLUDING TAX and the TAX AMOUNT were configured, the following error would have occurred when the system was trying to do the automatic allocation.
| 53517 |