Detailed Changelog for Continia Expense Management 2025 R1
This article lists all new features and bug fixes for each version of Continia Expense Management 2025 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 Receive a notification in the Continia PartnerZone (only available to partners).
Important
Expense Management supports the three latest versions of Business Central.
Expense Management 2025 R1, Service Pack 2, Hotfix 0
Release date online: June 24, 2025
Release date on-premises: June, 24, 2025
App version: 26.2.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Document Approval | Custom filters applied on the Approval Entries – Expense Management page now remain active as users work with approval records. This enhancement improves usability by preserving filter context. In addition, the following procedures have been made available for external access for better extensibility and integration:
| 66088 |
| Expenses | To enhance the integration between Expense Management and Document Capture, the system now automatically sends expenses for approval when the user selects Process with Document Capture. Additionally, expenses that have been sent to Document Capture will automatically be posted when they're approved. | 63252 |
| Expenses | When using Expense Management with Continia Sustainability, it is now mandatory to specify an Emission Unit Code on an expense if an Emission Quantity is provided. | 65797 |
| General Application | Procedure SetGlobalVars in report CEM Status Report is now available for external access. | 64982 |
| Per Diem | On the Per Diem Rate page, meal values for breakfast, lunch, and dinner now display dynamically based on your configuration:
| 65790 |
| Platform and Technology | The custom FactBox pane resizing implementation has been disabled when running on Business Central 26.0 and above, in favor of Microsoft's new native resizing feature. The native implementation limits the FactBox pane width to a maximum of 50% of the screen, whereas the previous custom implementation allowed for wider expansion. | 65063 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Credit Card Transactions | It is now easier to process bank transactions that were initially marked as excluded from posting. When you uncheck the Exclude Entry field on a bank transaction, the transaction is automatically posted, ensuring that the correct G/L accounts are updated if the transaction is later matched to an expense. When the Exclude Entry field is unchecked manually, a confirmation dialog appears with the following message:
| 62739 |
| Credit Card Transactions | Previously, when importing a bank transaction where the string value of the Business Country/Region field exceeded 10 characters, the system would bypass the Bank/Region mapping functionality and present the following error in the Bank Transaction Inbox:
| 65419 |
| Credit Card Transactions | The following error previously occurred when the Business Name field on a bank transaction exceeded 100 characters:
| 66319 |
| Credit Card Transactions | Duplicate transactions are now properly detected, even when currency mapping is applied. | 66338 |
| Document Approval | Previously, some users encountered the following error when attempting to open the cross-company dashboard in the Continia Web Approval Portal:
| 63853 |
| Document Approval | Previously, rejecting an approval entry in Expense Management could cause the following error to occur:
| 64691 |
| Document Approval | Users assigned the CEM-APPROVE permission set would previously encounter the following error in the Web Approval Portal or Business Central client when attempting to approve an expense matched to a bank transaction:
| 66207 |
| Document Approval | Continia approver users with Limit Document Visibility enabled would previously encounter the following error when trying to open a document card using the View action on the Approval Entries - Expense Management page:
| 66358 |
| Document Approval | Expense Management approver users were previously unable to open the Approval Entries - Expense Management page due to the following permission error, which occurred when one of the documents was a matched expense created in a version prior to Expense Management 26.0:
| 66523 |
| Document Approval | Cancelling an Expense Report approval request using the Cancel Approval Request action on the Expense Report card page now works as expected and changes the status of all of it's subdocuments to Open. | 66664 |
| Document Approval | Continia approver users with Limit Document Visibility enabled previously encountered the following error when trying to open an Expense Report sub-document card using the View action on Expense Report subpages:
| 66965 |
| Expenses | It is now mandatory to specify a Payment Type on an expense in order to create expense allocations using the Expense Amount Distribution functionality. This change ensures that allocations are created with the correct financial context and helps prevent incomplete or invalid distribution entries. | 64392 |
| Expenses | When using a Distribution Code to automatically allocate expenses, configurations with an odd number of distribution lines could result in incorrect rounding. This caused an inconsistency error when posting the expense. | 64797 |
| Expenses | When attempting to run Expense Management Online Synchronization in Business Central, the following error appeared if a user entered a Vendor Invoice No. on an expense document that exceeded the 30-character limit:
| 64865 |
| Expenses | The default setup for the integration with Continia Sustainability has been improved for the HOTEL expense type in the Danish (DK) and United States (US) localizations. | 65125 |
| Expenses | It is no longer possible to configure a Payment Type to both:
| 65436 |
| Expenses | When using a Distribution Code to automatically allocate expenses, the user-entered expense Tax Amount was previously ignored. Instead, standard tax values were calculated for the allocated lines, which could result in un-expected tax amounts being posted. | 65498 |
| Expenses | To ensure consistency with the Expense card page, the following VAT-related fields have been added to the Expenses page:
| 65716 |
| Expenses | The Expense Payment Type lookup page in Business Central now correctly displays all Payment Types assigned to the user’s Expense Group. | 66136 |
| Expenses | The Expense Description field is now automatically filled with the Merchant value when the E-DESCRIPTION configured field is not mandatory. If E-DESCRIPTION is mandatory, the Description field will remain empty to enforce user input. The Merchant value is automatically inherited from the AI Receipt Scanner for cash expenses or from the transaction Business Description when the expense is matched. Additionally, the Merchant field has been added to the Posted Expense Card and the Expense Report subpage corresponding to expenses. | 66401 |
| Expenses | An expense that was automatically allocated due to company policies, and later modified manually by the expense user, would previously generate the following error message in the Expense Inbox when attempting to synchronize the updates:
| 66481 |
| Expenses | For expenses processed with Document Capture - when a Document Capture template was configured to match & update order, the expenses did not not link the generated purchase order document to the expense, resulting in the following:
| 66692 |
| Expenses | When Expense Posting is set to Preferable Purchase Invoice, posting an Expense now correctly creates a purchase invoice for the vendor specified on the Payment Type. | 66933 |
| General Application | Several issues in the attachment viewer have been resolved to improve usability and accuracy when working with document attachments:
| 64013 |
| General Application | In Business Central version 25.2.x, it was briefly possible to assign a blocked dimension value to the Global Dimension 1 Code and Global Dimension 2 Code fields across all Expense Management document types. This could result in the following posting error:
| 64203 |
| General Application | The attachment viewer in expense and mileage entries now correctly displays the attachment counter when navigating between multiple documents. | 64745 |
| General Application | When creating mileage entries, using the Mileage card page opened directly from an expense report, the attachment add-in would display an incorrect attachment. | 64781 |
| General Application | In a localized version of Business Central, the following error would have prevented users from posting expense documents where sustainability accounts were specified:
| 64846 |
| General Application | When attempting to post an expense with long values in the fields Invoice No. or Vendor Invoice No., the following error would appear:
| 64867 |
| General Application | When clearing the last expense from the Expense List, the viewer previously continued to display the last associated attachment, even though no expenses remained. | 65543 |
| General Application | Previously, when attempting to post a Mileage or Per Diem entry in a Business Central client localized for Belgium (BE), the following error occurred:
| 65634 |
| General Application | The access check for configured field dependency lookup values now correctly evaluates both the user's individual access and their group access permissions. Previously, lookup values might have been incorrectly hidden if the user lacked direct access, even when group-level access was granted. | 65706 |
| General Application | When attempting to upgrade to Business Central version 26, the following error would occur if the company was not activated but Expense Management documents, that have never been synchronized with Continia Online, existed.
| 65995 |
| General Application | One of the following errors could occur when attempting to directly or indirectly modify Expense Management documents that had never been synchronized with Continia Online, in a company where Expense Management was not activated:
| 66286 |
| General Application | When using the Find Entries action on the Posted Expense Reports page, project ledger entries are now shown to users even when the documents have only created project ledger entries without general ledger entries (for example, when Project No. is specified but the Reimbursement Method is set to External). | 66788 |
| Mileages | The configurable comment: The applied rate is more than a year old. in mileage entries has been updated:
| 65527 |
| Mileages | A mileage subject to company policies that refund up to a limit would previously result in the following error when posting:
| 66333 |
| Per Diem | When Per Diem reimbursement method is set to Both, the system now correctly posts the per diem to general journal. | 66572 |
| Per Diem | Previously, when Multi Destinations was disabled in the Expense Management Setup, the Per Diem Details subpage was not displayed on posted Per Diem cards, even though relevant data existed. | 67000 |
| Per Diem | Previously, when posting Per Diems that included more than one Allowance Type and using Dataloen's external payroll integration, only one allowance entry was automatically transferred. The remaining entries were left in the External Interface Queue with the status On Hold, requiring manual processing. All allowance entries included in a Per Diem are now correctly sent to Dataloen in a single automated process. | 67069 |
Expense Management 2025 R1, Service Pack 1, Hotfix 2
Release date online: June 4, 2025
App version: 26.1.2
Only released in Business Central Cloud.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Per Diems | When the Per Diem reimbursement method is set to Both, the system now correctly posts the Per Diem to the general journal. | 66572 |
| Expense Reports | Cancelling an Expense Report approval request using Cancel Approval Request on the Expense Report card, changes the status of all of its subdocuments to Open. | 66664 |
| Expenses | For expenses processed with Document Capture, when the Document Capture template had been configured to match and update the order, the expenses would not link the generated purchase order document to the expense. This resulted in the following:
| 66692 |
| Expense Reports | When using Find Entries on the Posted Expense Reports page, project ledger entries are now shown to users even when the documents have only created project ledger entries without general ledger entries (for example, when Project No. is specified but the Reimbursement Method is set to External). | 66788 |
| Expenses | When Expense Posting is set to Preferable Purchase Invoice, posting an Expense now correctly creates a purchase invoice for the vendor specified on the Payment Type. | 66933 |
| Document Approval | Continia approver users with Limit Document Visibility enabled would previously encounter the following error when trying to open an Expense Report sub-document card using View on Expense Report subpages:
| 66965 |
Expense Management 2025 R1, Service Pack 1, Hotfix 1
Release date online: May 21, 2025
Release date on-premises: May 21, 2025
App version: 26.1.1
Only released in Business Central Cloud.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Credit Card Transactions | The following error would previously occur when the Business Name field on a bank transaction exceeded 100 characters:
| 66319 |
| Credit Card Transactions | Duplicate transactions are now properly detected, even when currency mapping is applied. | 66338 |
| Document Approval | Continia approver users with Limit Document Visibility enabled would previously encounter the following error when trying to open a document card using the View action on the Approval Entries - Expense Management page:
| 66358 |
| Document Approval | Expense Management approver users were previously unable to open the Approval Entries - Expense Management page due to the following permission error, which occurred when one of the documents was a matched expense created in a version prior to Expense Management 26.0:
| 66523 |
| Expenses | The Expense Description field is now automatically filled with the Merchant value when the E-DESCRIPTION configured field is not mandatory. If E-DESCRIPTION is mandatory, the Description field will remain empty to enforce user input. The Merchant value is automatically inherited from the AI Receipt Scanner for cash expenses or from the transaction Business Description when the expense is matched. Additionally, the Merchant field has been added to the Posted Expense Card and the Expense Report subpage corresponding to expenses. | 66401 |
| Expenses | An expense that was automatically allocated due to company policies, and later modified manually by the expense user, would previously generate the following error message in the Expense Inbox when attempting to synchronize the updates:
| 66481 |
| Mileages | A mileage subject to company policies that refund up to a limit would previously result in the following error when posting:
| 66333 |
Expense Management 2025 R1, Service Pack 1, Hotfix 0
Release date online: May 14, 2025
Release date on-premises: May 14, 2025
App version: 26.1.0
Only released in Business Central Cloud.
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| General Application | This version includes no deliveries and is a technical release only. | 66453 |
Expense Management 2025 R1, Hotfix 4
Release date: May 7, 2025
App version: 26.0.4
Only released in Business Central Cloud.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Document Approval | Users assigned the CEM-APPROVE permission set would previously encounter the following error in the Web Approval Portal or Business Central client when attempting to approve an expense matched to a bank transaction:
| 66207 |
| Expenses | When using a Distribution Code to automatically allocate expenses, configurations with an odd number of distribution lines could result in incorrect rounding. This caused an inconsistency error when posting the expense. | 64797 |
| Expenses | When using a Distribution Code to automatically allocate expenses, the user-entered expense Tax Amount was previously ignored. Instead, standard tax values were calculated for the allocated lines, which could result in un-expected tax amounts being posted. | 65498 |
| General Application | When attempting to upgrade to Business Central version 26, the following error would occur if the company was not activated but Expense Management documents, that have never been synchronized with Continia Online, existed.
| 65995 |
Expense Management 2025 R1, Hotfix 3
Release date: April 10, 2025
*App version: 26.0.3
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | When attempting to post a Mileage or a Per Diem in a Belgium (BE) localized Business Central client the following error would previously occur:
| 65634 |
Expense Management 2025 R1, Hotfix 2
Release date: April 1, 2025
Release date on-premises: April 10, 2025
App version: 26.0.2
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| General Application | This version 26.0.2 marks the official release of Expense Management 2025 R1. The preview version was released as 26.0.0, with minor updates included in version 26.0.1. This current version includes no deliveries and is a technical release only. | 65650 |
Expense Management 2025 R1, Hotfix 1
Release date: April 1. 2025
Release date online: April 9, 2025
App version: 26.0.1
Only released in Business Central online.
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| General Application | Procedure SetGlobalVars in report CEM Status Report has been made available for external access. | 64982 |
| Platform and Technology | The custom FactBox pane resizing implementation has been disabled when running on Business Central 26.0 and above, in favor of Microsoft's new native resizing feature. Note that the native implementation limits the FactBox pane width to a maximum of 50% of the screen, whereas the previous custom implementation allowed for wider expansion. | 65063 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Document Approval | Rejecting an Expense Management approval entry would previously cause the following error to occur:
| 64691 |
| Expenses | When attempting to run Expense Management Online Synchronization in Business Central, the following error would appear if a user entered a Vendor Invoice No. on an expense document that exceeded the 30-character limit:
| 64865 |
| General Application | When creating mileage entries using the Mileage card page, opened directly from an expense report, the attachment add-in would display an incorrect attachment. | 64781 |
| General Application | In a localized version of Business Central, the following error would have prevented users from posting expense documents where sustainability accounts were specified:
| 64846 |
| General Application | When attempting to post an expense with long values in the fields Invoice No. or Vendor Invoice No., the following error would appear:
| 64867 |
Expense Management 2025 R1
Pre-release date: March 21, 2025
Release date, online: April 1, 2025
Release date, on-premises: April 1, 2025
App version: 26.00
Released on-premise and in Business Central online.
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | In the Canadian localization, functionality has been enhanced to support multiple tax jurisdictions of the same type (e.g., PST1 and PST2). The Tax Amount is now distributed proportionally based on the respective tax percentages for each tax entry. Previously, this setup would have resulted in an error. This improvement is particularly useful for expenses that are capitalized. | 60308 |
| Credit Card Transactions | More flexibility has been introduced when changing Payment Type or creditcard settings. Users can now modify these details even when there are transactions and expenses that are not yet posted. Previously, these changes were restricted until the documents were posted. | 60587 |
| Credit Card Transactions | Upon opening, the CEM Banks page now automatically populates with supported banks, so you no longer have to manually select the Get Supported Banks action. | 62654 |
| Credit Card Transactions | You can now correct the Continia User Credit Card record if an incorrect User ID or Payment Type was assigned, even where Bank Transactions are present. The system automatically updates the associated open Bank Transactions with the new values. However, posted and/or matched transactions will not be updated, they instead retain their original settings. Additionally, you can remove, delete, or update the associated credit cards from the payment type. When the Posting Method or Matching Method is updated to an option that doesn't require associate cards, the user is asked if the associated cards should be removed. You cannot change the Currency Code of a Bank Account or a Vendor that is related to a Payment Type that has bank transactions. | 62677 |
| Document Approval | Users can now click the Approval By field in Expense Report card, and list pages, to open the approval entries page for the document, similar to other Expense Management document types. | 46382 |
| Document Approval | You can now handle document approval directly on Expense Management document cards, streamlining the approval process. Moreover, approval-related actions are now reorganized into groups, similar to those on purchase documents. On document card pages, the following new action groups have been introduced:
| 60573 |
| Document Approval | In the Business Central client, when a document is rejected and sent back to the previous approver, the system now prompts the user to provide a comment. | 60596 |
| Document Approval | The following event has been added to Codeunit CEM Approval Management:
| 61006 |
| Expense Mobile App and Portal | When the 60-Day Rule is enabled, a confirmation message now appears if the selected address differs from the home address, but is within 500 meters. This ensures users are informed of minor address discrepancies before proceeding. | 62019 |
| Expenses | You can now view an unlimited number of expense types on the Expense Reimbursement page by navigating using the Next/Previous actions. | 44715 |
| Expenses | Deleting a document from the Documents for Import queue in Document Capture now clears the Applied Document No. field on the linked expense. If the expense has already been posted, the expense will also reopen. | 59523 |
| Expenses | The Invoice No. is transferred to the External Document No. when posting, together with information about the expense document number. The Invoice No. is captured by the AI Receipt Scanner. In the Spanish localization, you can configure the Vendor Invoice No. field for expense user input, for similar purposes. In this case, the Vendor Invoice No. value will transfer to the External Document No. | 9773 |
| Expenses | You can now send Expenses to Document Capture, even if the attachment is not a PDF. | 59779 |
| Expenses | You can now specify the Volume Unit on the Expense Management Setup page. The Volume Unit and the Distance Unit are used in various areas, including the sustainability fields that require this type of information. | 60178 |
| Expenses | When Applied Purch. Doc No. is manually updated, Process with Document Capture will no longer send the document for OCR processing, because a document is already applied. | 60651 |
| Expenses | The field Business Description has been renamed to Merchant. The values for this field are now inherited from the matching transactions or from the AI Receipt Scanner in the Expense Mobile App and Expense Portal. As a result, the Copy Description from Bank Transaction setting in Expense Management has been removed. | 61237 |
| Expenses | Invoice documents associated with an expense report cannot be processed using Document Capture. To process the document, you must first detach it from the expense report. This restriction ensures proper handling of invoice documents within the system. | 61240 |
| Expenses | The following event has been added to Report CEM Export Attachments:
| 61796 |
| Expenses | The Post in Expense Currency feature now ensures that expenses for users associated with an Employee, where the Currency Code is specified, are posted in their respective currencies. This is consistent with the behavior for users associated with a Vendor and ensures consistency in currency handling across different user types. | 62142 |
| General Application | For Expense Report posting, the ledger entries corresponding to the expense user (Employee/Vendor) can now be grouped based on the document type (expense, mileage, per diem) or combined for the entire expense report. This enhancement provides greater flexibility in financial reporting and reconciliation. However, you cannot group ledger entries in the following cases:
| 38895 |
| General Application | Users can now select which documents to post using the Post Batch functionality on Expense Management document list pages. This applies to all Expense Management document types. | 45456 |
| General Application | You can now open card pages for expenses, mileages, and per diems directly from an expense report, allowing for easier access and review of individual entries. | 45892 |
| General Application | When running a data maintenance job, you can now see an overview of the data scheduled for deletion. Additionally, the date intervals have been aligned with those in Document Capture. | 54571 |
| General Application | The DESCRIPTION configured field, used for expenses, mileages, and expense reports, has been split into individual fields for each document type. This change allows for different descriptions on each document type, and provides for greater flexibility and customization. | 55259 |
| General Application | The field types JOBNO and TASK have been renamed to PROJECT NO. and PROJECT TASK NO., respectively. This change improves consistency in terminology across the system. | 56888 |
| General Application | Improvements have been made to enhance the user experience when managing sustainability-related data. | 59226 |
| General Application | A new field Posted Document No. has been added to the Posted Expense Report card and list pages. It shows the Document No. of the ledger entries created during Expense Report posting. The field is visible when Post on multiple document numbers is disabled on Expense Management Setup page. | 59765 |
| General Application | Global Dimension fields have been added to the following pages: CEM Per Diem Reimbursement Details, CEM Expense Reimbursement Details, CEM Mileage Reimbursement Details. | 59766 |
| General Application | Posting is now restricted on blocked General Posting Groups and VAT Posting Groups, preventing transactions from being posted to blocked accounts. | 59826 |
| General Application | Rejecting a document in Document Capture now clears the Applied Document No. on a linked expense. If the expense has already been posted, it will also reopen. | 59914 |
| General Application | Boolean (Yes/No) values are now supported in field dependencies, allowing for improved flexibility in conditional logic and data validation. | 60327 |
| General Application | In approval emails, the domain name is now removed from the user name. | 60560 |
| General Application | The Transaction Description field for expenses, which previously displayed the merchant's name only when an expense was created from a bank transaction, has been updated. Merchant names are now also captured via OCR from the Expense Portal or Expense Mobile App. To enhance clarity, the Transaction Description field has been replaced with a new Merchant field, which is automatically populated by OCR and bank transactions. | 60637 |
| General Application | During the upgrade from v24 to v25, the Sustainability fields and their values are converted. Previously, these values were not managed. | 60663 |
| General Application | When running Run GDPR Maintenance in Expense Management Setup to delete old documents, the associated Document Log entries are now also removed. | 60996 |
| General Application | The sustainability fields are now editable on the Posted Expense Card page, enabling the completion of sustainability data after upgrading from earlier versions of Expense Management. | 61612 |
| General Application | The EM Countries/Regions page now automatically populates with standard Country/Region records upon opening. | 61773 |
| General Application | The values in the Request Page fields for batch posting reports are now retained for future use. | 61937 |
| General Application | The caption for the configured field <DOCUMENT DATE> has been changed from "Registration Date" to "Document Date". | 62651 |
| General Application | Multiple controls, especially pages, have been renamed to include the - Expense Management suffix instead of abbreviations such as EM. This improves clarity and consistency across the system. | 63290 |
| General Application | The following event publisher has been added to Table 6086333 CEM Exp. Posting Desc. Field to enable customization of the Posting Description field when posting Expense Management documents:
| 63479 |
| General Application | The configured field BILLABLE has been renamed to PROJECT BILLABLE. | 63673 |
| General Application | You can now preview PDFs directly from the attachment list avoiding having to download them to do so. | 64399 |
| Mileages | Project ledger entries are now posted independently of the reimbursement method, allowing expenses to be posted to projects in Business Central while processing employee reimbursements externally. | 42271 |
| Mileages | In the Danish localization, when the 60-day rule is enabled, an error comment now displays if both the From Home and To Home fields are selected simultaneously. This ensures that only valid mileage data is processed and helps maintain accurate records. | 61287 |
| Mileages | To improve clarity in calculating the 60-day rule in Danish localization, the 60-Day Rule Day Count and 60-Day Rule Destination fields have been added to the mileage list.
| 61550 |
| Mileages | The following event has been added to Table CEM Mileage Rate:
| 61621 |
| Mileages | In the Danish localization, when the 60-day rule is enabled, a warning comment now appears if neither the From Home nor To Home checkboxes are selected, but there is a clear correlation to a previously used home address within the default range of 300 meters. | 62432 |
| Mileages | In the Danish localization, when the 60-day rule is enabled, a warning comment now appears if GPS coordinates are missing on a mileage. GPS coordinates are used to determine proximity to a destination address and validate home address checks. If GPS coordinates are missing, the system defaults to identifying similar destination addresses based solely on the address text, which may affect the accuracy of the 60-day rule calculation. | 62433 |
| Mileages | In the Danish localization, when the 60-day rule is enabled, you can now see a warning comment if a mileage has either From Home or To Home specified but the home address is outside the 300 meter range when comparing with the previously used address. | 62467 |
| Mileages | An event publisher has been added to Codeunit CEM Mileage-Reimburse:
| 64123 |
| Per Diem | For improved transparency of calculations, a new FactBox has been added to Per Diem, displaying a summary of the calculations. Additionally, you can now access a detailed daily calculation breakdown by navigating on the amount. | 62095 |
| Per Diem | On the Per Diem Rate page, the captions for the fields Breakfast, Lunch, and Dinner are now dynamically updated based on the selected Value Method. If the value method is percentage-based, a percentage sign (%) is appended to the captions. If the value method is based on real amounts, the currency code is displayed instead. This improvement ensures the captions clearly reflect the context of the entered values. | 62106 |
| Per Diem | You can now view per diem details directly on the Per Diem Card and the posted Per Diem Card without opening any extra pages. You can also view and modify allowances directly on the Per Diem Card, again, avoiding having to navigate to additional pages. This update streamlines workflows and improves efficiency for users managing per diem expenses. | 62794 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Credit Card Transactions | On Continia User Credit Cards, a filter is applied so only matching credit cards are available for assignment. | 61879 |
| Expenses | The dynamically calculated VAT Amount field, in the Amounts group on the Expense Card page, has been renamed to VAT Amount (Calculated) to better indicate that the value of this field is calculated automatically. It also better distinguishes from the optional editable VAT Amount field that you can enable via Configurable Fields functionality. A similar change has also been made to the Expense Report's Expenses subpage. | 52757 |
| General Application | When creating demo data, the GENERAL journal template is now selected by default if it exists. | 44365 |
| General Application | Performance of the Consistency Check in field dependencies has been optimized to improve efficiency and reduce processing time. | 56183 |
| General Application | Business Central users now only see the Continia Expense Management Activities cue and tiles on their role centers if they have an appropriate permission set assigned to them (CEM-SUPER, CEM-NAVUSER, or CEM-APPROVE). This ensures the Continia Expense Management role center cue and tiles are hidden from users who are not intended to interact with Expense Management. | 61960 |
| General Application | The Expense Management Online Synchronization process has been improved to prevent documents from getting stuck in their inboxes with the following errors:
| 63245 |
| General Application | Context-sensitive help page URLs have been fixed to ensure they direct users to the correct help pages. | 64337 |