Detailed Changelog for Continia Expense Management 2021 R1
This article lists all new features and bug fixes for each version of Continia Expense Management 2021 R1.
Important
This version of Expense Management is no longer supported. As a consequence of this, Continia will no longer correct any errors appearing in this version, and no further service packs relating to the version will be released. For supported versions of Expense Management, see Software Lifecycle Policy and Continia Expense Management On-Premises.
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).
Expense Management 2021 R1 Service Pack 7
Released: February 27, 2023
App version: 7.7.0.0
FOB version: 7.07.00
New or changed functionality
| Functional area | Description | Id |
|---|---|---|
| Per Diem | Per Diem calculations are now done on a day-to-day basis in the German, Austrian and Switzerland localizations, as opposed to the past when the sub-rates were applied only to the last day. | 43238 |
Bug fixes
| Functional area | Description | Id |
|---|---|---|
| Expenses | When trying to "Get Expenses" from an Expense Report, when the expense would have been matched, the following error was shown:
| 42497 |
| Expenses | When posting a matched expense in a system where posting transactions at import was disabled, when the expense currency matches the Bank Account currency, the posting amount was the result of an Amount LCY converted to the Bank Account currency. This was not necessary since the Bank Account currency matches the Expense Currency. | 42530 |
| Expenses | When posting allocations on an expense with the external reimbursement method set up, an error would not allow the expense to be posted.
| 43536 |
| General Application | When downloading a document which was ready to be automatically sent for approval but the user didn't have an approver, the synchronization process would have failed with the following error.
| 41481 |
| General Application | We have fixed a bug in the "Upload Company Logo" action on the Expense Management Setup page which prevented the logo from being sent to Continia Online, and consequently shown to app users. | 42717 |
| General Application | After an inbox entry was trying to update a posted document, all the following inbox entries were skipped by marking them as Accepted. | 44410 |
| Mileages | Wrong comments were shown on the posted Mileage card (belonging to expenses rather than mileage). | 43230 |
| Mileages | The event OnBeforeCheckMileage was never used in Codeunit 6086344 CEM Mileage - Check. Instead, OnAfterCheckMileage was wrongly called from two locations. | 43978 |
| Per Diem | The amount shown on a Per Diem was wrong in the Expense App and Expense Portal when a per diem had multiple currencies. We are now showing the total amounts in the local currency. | 42537 |
| Per Diem | Whenever using per diem sub-rates, a per diem starting precisely at midnight (00:00) was adding an extra full day allowance to the calculation. | 44537 |
Expense Management 2021 R1 Service Pack 6
Released: November 1, 2022
App version: 7.6.0.0
FOB version: 7.06.00
New or changed functionality
| Functional area | Description | Id |
|---|---|---|
| Expenses | We have added the following Event Publishers Codeunit 6086308 CEM Expense Inbox-Transfer
| 41366 |
Bug fixes
| Functional area | Description | Id |
|---|---|---|
| Expenses | Allocations did not inherit standard dimensions from the employee. | 35143 |
| Expenses | An issue has been fixed that was causing decimal differences in the sales taxes appended to the Purchase Invoice when the user would not have changed the sales taxes allocated amount. | 39083 |
| Expenses | An issue in the sales tax was causing the following error to be shown, even though the sales tax differences were within the setup ranges. This has been fixed.
| 39337 |
| Expenses | The Expense Report (Settlement) posting date is used to post all the sub-documents on the same date. However, on an expense, the exchange rates were not calculated in regard to that date, but based on the "Document Date". | 41026 |
| Expenses | When validating the expense “Document Date”, a recalculation of exchange rates will happen. | 41027 |
| Expenses | The expense report posting date is used for recalculating the currency exchange rates for expenses. Now amounts are recalculated to reflect currency exchange rates on expenses in an Expense Report (Settlement). Until now, these were only updated at posting time. | 41029 |
| Expenses | An issue has been fixed, resulting in an error where an allocated expense would have an allocation without a Job Task specified when the original expense had a Job specified. The error can be bypassed if the main expense Job is removed.
| 41145 |
| Expenses | When pressing "Show not matched" on the Reconciliation page, filters were applied only on the left side sub-page, but not on the right-side sub-page. | 41368 |
| Expenses | When importing transactions and processing them, the status was not updated so multiple transactions and expenses could have been created based on the same transaction inbox. The issue was introduced in versions 7.05 and 8.04. | 41841 |
| General Application | When changing the "Expense Reminder Code" or "Expense User Group" on the "Continia User Setup", it was possible to add non-existing values and the system would have accepted it. | 29465 |
| General Application | The field Approver Name was editable in View mode on the Continia User Setup Card page. | 34815 |
| General Application | A permission issue that could result in the following message has been fixed:
| 40808 |
| General Application | We have identified an issue that could lead to a duplicated ledger entry for an expense in the case where, in the same split of a second, 2 users would have posted it. The posting routine was able to prevent concurrent sessions, but not from the moment the button was pressed up to the moment the posting would start. We have now made an extra check to ensure this cannot happen. | 41300 |
| General Application | When downloading a document which was ready to be automatically sent for approval but the user didn't have an approver, the synchronization process would have failed with the following error.
| 41481 |
| General Application | When posting an expense report with a very long posting description, you would get the following error message:
| 41776 |
| Mileages | When attempting to modify a mileage rate that is already used for posting mileage entries, you would get the following error message.
| 38492 |
| Mileages | An issue in the Company Policies that was resulting in the following error, has been fixed. The issue was occurring when opening Company Policies from the drill down, on the field.
| 40815 |
| Mileages | A user who has the permission set CEM-NAVUSER, would get the following error when creating a mileage.
| 40953 |
| Mileages | An issue in the mileage calculation, where in a very specific situation, the low mileage rate was wrongly assigned instead of the high rate have been fixed. This happened when a mileage existed in 2 periods and when the sum of the total distance driven by a user was exceeding the low rate. | 41111 |
| Mileages | When setting up Expense Management Setup to show extra fields on the "Posted Mileage" and "Posted Mileage Card", the system would have been presenting extra fields for expenses instead. | 41345 |
| Mileages | When exporting configurations through the Expense Management Assisted Setup Guide, decimal values were converted to integers (e.g., 1.23 was converted to 123). This impacted mileage rates. | 42127 |
| Per Diem | When setting the First and Last Day Setup, Calculation Method to Sub rates immediately after creating the Per Diem Rate, you would get the following error message:
| 38538 |
| Per Diem | For Per Diem calculation, in certain conditions, if skipping one day rate when using sub-rates, an issue has been fixed. | 38931 |
| Per Diem | A wrong calculation on the Per Diem, when using hourly rates, on the last day of the trip has been fixed. | 38932 |
| Per Diem | We have fixed the following error in the Status Report, related to the Per Diem calculations over the number of hours:
| 39458 |
| Per Diem | When only one Per Diem Group would exist, the filed "Per Diem Group Code" was not visible on the Per Diem Card. | 40886 |
Expense Management 2021 R1 Service Pack 5
Released: July 1, 2022
App version: 7.5.0.0
FOB version: 7.05.00
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Expenses | We have implemented functionality to avoid and enforce the usage of Jobs/Tasks on sales tax allocation lines. Sales Tax allocation will no longer post Job ledger entries. This is especially relevant for the Canada Sales Tax. | 31943 |
| General Application | We are now processing the release notifications from the Notification Outbox as part of the normal synchronization with Continia Online. | 28682 |
| General Application | We are no longer marking the Ledger Entries as "System-Created Entry". This will allow reverting ledger entries posted by Expense Management. It also fixes an issue in the Australian localization, where the sales taxes were not posted in the "GST Purchase Entry" and tables alike. | 32161 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Credit Card Transactions | We've increased the length limit of the Transaction ID to 150 characters. | 13728 |
| Expenses | We have fixed an issue in MS Dynamics NAV 2009 R2, when an expense with Jobs was posted. There would have been an error like the one below. This issue doesn't affect other versions.
| 32562 |
| Expenses | We have found an issue that could create duplicated bank transactions out of one single bank transaction inbox. That would occur if multiple users processed the transaction inbox in the exact split of a second. The bookkeeper would have been informed if an expense existed twice, though. | 35047 |
| General Application | We have fixed a bug in NAV/BC where the first subdocument line on a Settlement (Expense Report) would not inherit the global dimensions from the main document. | 31238 |
| General Application | We have improved the caption on the request page of the batch posting of expenses, mileages and expense reports. | 31650 |
| General Application | When exporting the Expense Management configuration with the Expense Management Assisted Setup, the Vehicle table would always be exported. Now it is only exported if the user has selected to export Mileage Rate IDs. | 32335 |
| General Application | We have fixed an issue where the inbox entries would have failed with the error below. This was happening only when using the "O365 Authentification Email" on the Continia User.
| 34643 |
| General Application | We have identified an isuse that could lead to a duplicated ledger entry for an expense in the case where, in the same split of a second, 2 users would have posted it. The posting routine was able to prevent concurrent sessions, but not from the moment the button was pressed up to the moment the posting would start. We have now making an extra check to ensure this cannot happen. | 35019 |
| General Application | We have fixed an issue that was returning the following error in the Web Approval Portal, when custom fields would have been created with value longer than 50 characters. The issue was present on Mileage, Per Diem and Expense Report.
| 38431 |
| General Application | We have identified an issue that was not updating documents in the Expense App when they were paid, due to the fact that the payment was not made with a Document Type = Payment. We are now not checking anymore the Document Type, we only make sure the payment applies to the initial entry. | 38505 |
| General Application | We have fixed an issue that caused the error below when synchronizing. The issue has been introduced in version 9.2
| 38859 |
| General Application | We have fixed an issue that was causing the synchronization to stop with the error below when documents were pending to be deleted. The issue has only been seen in the Business Central cloud client.
| 38907 |
| Mileages | We have fixed an issue that was crashing the client while trying to calculate mileage amounts in an endless loop. This was happening when mileage rates would exist for 2 years in advance. The error received is the one below:
| 38457 |
| Per Diem | On the Per Diem rates, we have removed the fields "Half Day Starting Time" and "Half Day Latest Time" because they were not used anymore. | 32391 |
| Per Diem | We have fixed an issue on the Per Diem calculation in the case there where "First/Last Day Calculation Method" would have been "First/Last Day fixed rate". If the number of hours in the current day would have been precisely the same as "First/Last Day Minimum Stay", the rate was not applied but it should have been. | 34501 |
| Per Diem | We have fixed an issue that was causing the following error, when posting a Per Diem with reimbursement method = both:
| 38762 |
Expense Management 2021 R1 Service Pack 4
Released: March 10, 2022
App version: 7.4.0.0
FOB version: 7.04.00
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Credit Card Transactions | It is now possible to create statement transactions from the transaction import journal. | 29447 |
| General Application | We've included the sending of all release notifications from the Notification Outbox as part of the normal synchronization with Continia Online. | 28682 |
| General Application | We are no longer saving the default dimensions calculated at posting time, back to the original expense document. This has been causing issues in the past and it can lead to errors when posting a document in multiple transactions. | 30811 |
| General Application | We have enabled the feature of signing expense attachments digitally in the French and Belgium localizations. | 31662 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Expenses | Attendees were not copied to the Sales Tax allocation lines in the Canadian localization, when synchronizing expenses from Continia Online. | 28689 |
| Expenses | In a settlement where Cash and non-Cash expenses would have been found, out of which some had Jobs specified, the balancing account would have been calculated incorrectly and therefore the expense would be posted as if it was Cash when the expense was not marked as such. This is found in systems where "Matching Required" is Never. | 28963 |
| Expenses | We have fixed an issue where automatic allocations (due to Sales Tax) would not inherit Extra Fields values from the main expense to the allocation lines. | 29133 |
| Expenses | We have fixed an issue where automatically allocated expenses would not inherit Extra Fields from the main expense to the allocation lines. This was mainly a concern for the Sales Tax automatic allocation. | 29287 |
| Expenses | When automatically allocating due to sales taxes, the Tax Area Code was not copied to the tax lines. If "TAX AREA CODE" was a mandatory field, the expense would have encountered an error in the mobile app, preventing the sending. The user were supposed to manually type the "TAX AREA CODE" values on all the allocation lines. | 29339 |
| Expenses | When posting a reconciliation journal, the following error would appear if the statement lines were manually inserted (without having an underlying statement transaction). The Bank Transaction does not exists. Identification fields and value Entry No. = "0" | 29446 |
| Expenses | We have fixed an inconsistency error which was present when posting an expense where the default dimensions were changed during the posting. The error would come up with messages similar to the ones below. The changes to the Expense record cannot be saved because some information on the page is not up-to-date. Close the page, reopen it, and try again. Inconsistent read of field(s): 'Global Dimension 2 Code', on table 'Expense', identification values: 'Entry No.='xxxx'' | 29691 |
| General Application | We have fixed an issue when the same number series was used for both posted and un-posted settlements. In this case, the posted document would have still increased the number series number when it was not expected to do so. | 31575 |
| General Application | A filter on a Field Type of data type "Code" would have not worked unless the value was spelled with capital letters. This has been fixed by uppercasing the filter value. | 31255 |
| General Application | We have fixed a bug, where it was possible to reopen/recreate a document from NAV/BC, when that document had been deleted by the user in the app/portal. | 27291 |
| General Application | We have fixed an issue that was showing an error if the same filters were applied on similar fields. For example, PD-DESTINATION and P-DESTINATION. | 27407 |
| General Application | We have fixed an issue in the addin that was setting a default zoom of 1% on the attachments. | 28658 |
| General Application | We have fixed an issue on the Posting Setup, when copying the Expense or Mileage Account to the actual document. If no account was found on that user, it would have taken a posting account from any other user. | 28856 |
| General Application | We have fixed an issue which was leading to desynchronization issues on subdocuments belonging to a settlement. When documents were being downloaded in Business Central, if the user would have modified the documents in the exact same split of a second, the last change of the user would have never been downloaded inside Business Central. The sub-document would have failed in the Inbox with an error. | 28914 |
| General Application | Preview posting was sometimes failing with the error below when default dimensions were configured on accounts that were external to Expense Management (for example, a G/L Account). The functionality would have tried to copy those default dimensions back to the expense document. The functionality was failing to find the Expense Management document because, in preview mode, the relation between the expense document and the un-posted document [number] doesn't exist. The Expense Header does not exist. Identification fields and values: Document Type='Settlement',No.='[number]' | 28973 |
| General Application | "Tax Area Code" and "Tax Group Code" were missing on the Settlement expense subpage. | 29132 |
| General Application | We are now preventing non-reimbursable expenses to be sent to the Lessor/Bluegarden payroll interfaces. | 29137 |
| General Application | When synchronizing, there was functionality to recalculate mileage across all companies. This code was triggering permission errors when the user that synchronizes would have not had permissions on all the companies. We have changed the functionality so that it skips the calculations when the user doesn't have enough permissions. We do not foresee a major downside in doing so, as this calculation was mostly for presentation purposes. A mileage will always be recalculated before posting. | 29422 |
| General Application | We have fixed an issue in the field dependencies area where the error below would have prevented the calculations. The length of the string is 273, but it must be less than or equal to 250 characters. Value: The following users don't have access to value SALES in the field DEPARTMENT:[A very long list of users]. | 29735 |
| General Application | We have prevented the following error when synchronizing. If a user didn't have the CEM-SUPER permission set but had some basic Expense Management permissions, he would have gotten a similar error when he was trying to modify a Job or a Task, for example. The error would have occurred in areas of standard Business Central, but when using a field type was configured in Expense Management over that table (for example, Job/Task). You do not have the following permissions o TableData CEM Field Type: Modify | 30044 |
| General Application | We have fixed an issue where the number of documents was not correct in the Approval Portal. | 30722 |
| General Application | For OnPrem: In the EM versions 8.01 and 4.00.06 we have corrected an issue where default dimensions were not created at posting time. Unfortunately, the change further revealed another issue: the default dimension was then used for posting and re-added on the document, instead of the dimension added by the user. | 30737 |
| General Application | We have fixed an issue that was calculating wrong total amounts on the Per Diems in the Status Report. | 30927 |
| Mileages | We have prevented creating a mileage rate without a starting date. | 28971 |
| Per Diem | On the Per Diem, the number of hours was rounded to the next full hour, resulting in calculation problems when sub-rates were used. | 28824 |
| Per Diem | We have fixed an inconsistency error which was present when posting a per diem where the default dimensions were changed during the posting. The error would come up with messages similar to the ones below. The changes to the Per Diem record cannot be saved because some information on the page is not up-to-date. Close the page, reopen it, and try again. Inconsistent read of field(s): 'Global Dimension 2 Code', on table 'Per Diem', identification values: 'Entry No.='xxxx'' | 30813 |
Expense Management 2021 R1 Service Pack 3
Released: October 14, 2021
App version: 7.3.0.0
FOB version: 7.03.00
New or changed functionality
| Functional area | Description |
|---|---|
| General Application | A cue displaying the number of approval entries awaiting action has been added. When you select this tile, the Approval Entries page opens. |
| General Application | We have marked the method CalcLookupValForFieldAndParent as "external" in the table 6086345 "CEM Field Type". |
| General Application | We have added multiple new Event Publishers. |
| Credit Card Transactions | We have added support for TAB sepparated files in the Transaction Import. |
Bug fixes
| Functional area | Description |
|---|---|
| General Application | We have improved the functionality that was dependent on the permission sets name, so that renaming of permission sets will not affect the behaviour. We have improved some functionality that was dependent on the permission sets name, so that renaming of permission sets will not affect the behaviour. Further improvements have been done in the major releases, due to the necessity of data upgrades. |
| General Application | It was possible to post documents with a job but without a task. This was misleading, and an error message is now displayed when a task is expected. |
| General Application | The fields Employee Number and Employee Name have been removed from the Spanish version because employee posting would still require vendor information. |
| General Application | The Notification Outbox cue had a rather long Danish translation "Ubehandlede notifikationer". This has been changed to "Fejl". |
| General Application | We have fixed an issue that was leading to desynchronization of versions. |
| General Application | The error SET-NOT-FOUND isn't displayed anymore when a settlement is reopened. |
| General Application | In MS Dynamics NAV 2009 RTC, the expense fact box was not displayed. This issue has been fixed. |
| General Application | We have fixed an issue where the payment of a document was not changing states in the Expense App, when using purchase invoice posting. |
| General Application | A confirmation dialog that was displayed when web services were created in Expense Management has been removed. This was causing a problem when upgrading from EM 6.50 to 7.00. "The function UpdatePerCompany in the company initialization codeunit 6086102 in company Bejo BOB B.V. has failed due to the following error: 'Microsoft Dynamics NAV Server attempted to issue a client callback to show a confirmation dialog box: Do you want to update all web services for Continia Online? (CodeUnit 6086360 CEM Create Web Services). Client callbacks are not supported on Microsoft Dynamics NAV Server." |
| General Application | An issue causing the error "You do no have the following permissions on CodeUnit CEM Business Setup Management Execute" when opening Business Setup was fixed. |
| General Application | In the Configured Fields form in the classic client we displayed the following message in English: "Details are only displayed for Per Diem". Now the message is translated to the user's language. |
| General Application | We have prevented the error below in MS Dynamics NAV 2009 R2 and MS Dynamics NAV 2013. "You must define a CalcFormula for the Journal Field Name FlowField in the Transaction Import Field Mapping table." |
| General Application | Reopening a document was not possible if there were unproceessed inbox entries. We are now allowing reopening if the document is Pending Approval or Approved. |
| General Application | Approval notification was not sent in the Expense App for a document that was automatically sent for approval. |
| General Application | Approval notification was not sent in the Expense App for a document that was automatically approved due to company policies. |
| General Application | On the Settlement Card in the Classic client (NAV 2009 R2), when displaying a Per Diem line on the Settlement, and choosing Card from the Line menu button, it would display a Mileage. |
| General Application | We have done caption corrections with regards to expense approver ID. |
| Expenses | We have fixed an issue where the Tax Group Code was not copied from the Expense Type setup to the Expense. |
| Expenses | When an expense was reopened and re-sent to the user, there would be a notification as if the document was new. The notification has been changed to reflect the fact that it's an update. |
| Expenses | When expenses were allocated based on the sales tax, the functionality was not calculating correctly the tax amount. |
| Expenses | When sending a reminder email to the expense users we would in some cases give a wrong message or no message to explain the choices. Wrong message: "This expense contains values that have not been synchronized to Continia Online. This is required before this expense can be sent to the expense user. Would you like to synchronize values with Continia Online?" The message should have said: "Do you want to send a status e-mail to all the users or only to the selected ones?" |
| Expenses | We have fixed an issue where a promoted action on the expense allocations page would have said Category 4 instead of the actual caption. |
| Credit Card Transactions | We have added the duplicate check on the bank transaction id when importing transactions with the manual import tool. |
| Credit Card Transactions | In Business Central 2021 Wave 1 (Version 18) and onwards, it was not possible to do field mapping. We have fixed this. |
| Document Approval | Performance optimization when approving or rejecting documents in the Continia Web Approval Portal has been carried out. |
| Mileage | It was possible to change dimensions on a posted mileage. With this release, that's no longer possible. |
| Platform and Technology | A user with a limited permission set including CEM-NAVUSER could not use the function Send to Expense User on the pages Expense Card or Expenses. The user would get the following message: You do not have the following permissions on TableData CEM Synchronization Log: Read. |
Expense Management 2021 R1, hotfix 2
Released: August 8, 2021
App version: 7.2.1.0
FOB version: 7.02.01
Bug fixes
| Functional area | Description |
|---|---|
| General Application | An issue that was causing Job Ledger entries to be posted twice on a mileage has been fixed. The issue was introduced in EM 7.00. |
Expense Management 2021 R1 Service Pack 2
Released: June 3, 2021
App version: 7.2
FOB version: 7.02
Bug fixes
| Functional area | Description |
|---|---|
| General Application | We have fixed an issue that created inconsistencies in a Settlement if it was re-sent to the expense user. In the Expense App, its subdocuments would have not been shown while in the Expense portal they were shown but non-editable. |
| General Application | We have introduced the possibility to push notifications in the Expense app based on status changes in Business Central. |
| General Application | We have fixed an issue where the expenses and mileage would have not been able to be sent for approval because of the error below. "The expression Code cannot be Type-converted to a Integer value." |
| General Application | When reopening an approved document, the confirmation message was giving information as if the document was in pending expense user status. We have changed the message depending on the context. |
| General Application | Default User Export page would have opened the Continia User and not the Continia User Setup page, which made it possible to setup rules for users that didn't exist in the current company. |
| General Application | In the page Configured Fields, we have changed the shortcuts for moving fields up and down. They were previously Ctrl+Arrow Up and Ctrl+Arrow Down. These shortcuts did now work in the Web client. The shortcuts have been changed to Shift+Ctrl+Arrow Up and Shift+Ctrl+Arrow Down. |
| General Application | When a Field Type has more than 50.000 lookup values, performance on the App decreases. We now give a warning when the user updates the lookup values from the Field Types page. |
| General Application | We have fixed an issues where the Navigate page would not show Expense Management related documents, in an installation where Document Capture was not active. |
| General Application | The reimbursement method options have been changed from Vendor (On User) to Internal (On User) since the caption is no longer relevant because we have also introduced the possibility to post on an Employee, as well. |
| General Application | We have added actions to open the Default Continia User Setup page from the Expense User Group and Per Diem Group pages. |
| General Application | We have the following internal functions, for the purpose of customization development:
|
| General Application | Expense Management setup changes require sometimes synchronization with Continia Online. Until now, we have been asking the user if we would like to do so. We have now removed the dialog and the synchronization will happen automatically. |
| General Application | When using the Reimbursement Method External Payroll System you could get the following messages, which were not understandable. These messages have been improved. "You must not specify External Posting Account No. and Reimbursement Method in Expense Posting Setup for expense type External Posting Account Type." "You must not specify Expense Account and Reimbursement Method in Expense Posting Setup for expense type Expense Account Type." |
| General Application | Reimbursed amount was not shown for user paid corporate credit card. |
| General Application | We are now forcing a synchronization of Expense Management Setup with Continia Online after export of users. |
| General Application | We have prevented the error below. The error would appear when loading the attachment in the add-in due to the fact that the PDF file had a big number of pages. Unfortunately, we cannot display this file, so we chose to not show it instead of showing the error. "Generic Error Occured GDI+ " |
| General Application | In Business Central, the captions for Spanish Traditional were missing. |
| Expenses | We have fixed an issue relevant for the Sales Tax calculations: when an automatic allocation would occur, the Attendees from the original expense were not copied to the automatic Allocations. |
| Expenses | We have fixed an issue where the Tax Group Code was not copied from the Expense Type setup to the Expense. |
| Expenses | We have fixed an issue where an expense was posted without an amount when the Matching Method would have been Never Required and the Vendor on the user would have had a currency specified. |
| Expenses | On the expense, a validation error would occur when 2 different currencies had a 1:1 exchange rate. We have changed that comment from error to warning. |
| Transactions | When creating a new transaction template, the setup related to the CSV format was hidden. It is not displayed when opening the page. |
| Transactions | In a company where the Bank Account No. Series (in the General Ledger Setup) doesn’t allow manual series the following error message would occur when running the EM Setup wizard, because it would try to create the MASTERCARD bank account. We have decided to skip the Bank Account creation in this case. "You may not enter numbers manually. If you want to enter the number manually, please activate Manual Nos. in No. Series BANK." |
| Mileage | We have excluded the mileage rate checks for a vehicle that was not used. |
| Per Diem | When adding a Per Diem to a Settlement you get the error "Record(6086387) is not compaatible with Codeunit.Run(Record(6086320))." |
| Per Diem | We have changed the Per Diem calculation engine when using Sub-Rates, so that the subrates are only applied in the last day of the journey, not in the first day. |
| Per Diem | The Add to Settlement action on the Per Diems list, allow you to chose from a list of Settlements. The list showed all Settlements. It should only show Settlements with the same Continia User ID as on the selected Per Diem. This has been fixed. Now it works as for Expense and Mileage. |
Expense Management 2021 R1 Service Pack 1
Released: April 7, 2021
App version: 7.1
FOB version: 7.01
Bug fixes
| Functional area | Description |
|---|---|
| General Application | For the delegated user we have introduced the possibility to receive the notification email and the status report. |
| General Application | For the delegated user views we have added the date filters. |
| General Application | We have avoided a SETTL-NULL error in the Expense/Mileage/Per Diem inbox when "Keep history in Continia Online" was Never. The issue was occurring if the document belonged to a Settlement. |
| General Application | We fixed an issue where a synchronization would fail an error like "Continia User xxx not found." The issue was found when synchronizing in a multi company database, where mileage was used because of a cross-company mileage calculation due to company policies. The issue was introduced in EM 7.0. |
| General Application | We have fixed an issue where an attachment was stored in a wrong folder while moving an expense from a company to another (when storing to a file system) |
| General Application | A confirmation dialog was missing when posting a settlement, where one or more of the underlying documents had warning comments. |
| General Application | When running the Expense Management Setup Assistant, the system created Field Dependencies were not activated. This has been fixed. In case you have the older version, please run the “Consistency Check” action which will try to activate the dependencies. |
| General Application | We have fixed the error below, when opening the Company Policies page from the Expense Type in MS Dynamics NAV 2016 client: Error compiling dynamic control expression: 'not MileageFilterSet' at index '4'. The error is: End of expression expected. |
| General Application | We have fixed an issue in the Notification Outbox (former Release Notification Entries) page, when trying to sort the records after the field called "Table Name": Sorting cannot be done based on the Table Name field(s) in the Release Notification Entry table. |
| General Application | Upload Company Logo has been removed from the classic client (MS Dynamics NAV 2009). |
| General Application | When using Preferable Purchase Invoice, expenses are posted via the General Journal instead, because employee posting cannot be done on a Purchase Invoice level. We have added the same behaviour for Mileage and Per Diem, since it was possible to come to inconsistent setup on the user. |
| General Application | In the fob packages we have corrected the version of few objects which were introduced in EM 7.00 but were marked with VersionList EM 6.50. |
| General Application | We have fixed a bug on expense and per diem documents, requiring a vendor or employee to be set up on the Continia user, even though reimbursement method was set to external system. |
| General Application | The user's name is now displayed by default on the Expense Card, Mileage Card, the Per Diem Card and the corresponding document cards. |
| General Application | We have fixed the following permission error when trying to open the Manual Setup. "You do not have the following permissions on CodeUnit 'CDC Business Setup Subscr.' : Execute" |
| General Application | We have updated the Change Log documentation to reflect the new versioning system. |
| General Application | We have missed exposing events that were otherwise documented as being exposed. We have addressed the issue and the events are available again. |
| General Application | We have added multiple new Event Publishers. The updated list can be found here: Expense Management Event Publishers |
| General Application | We have fixed missing captions in the Expense Management Setup groups. |
| General Application | We have added the possibility to the Field Types from from the Field Dependency form in the classic client. |
| Expenses | When a non-refundable expense was allocated into a refundable and a non-refundable part, the Expense showed as Rejected in Continia Online and the Continia Expense app. We have changed it to Approved since some parts of the expense will be refunded. |
| Expenses | We have fixed an issue where the client add-in would not show correctly a PDF document that had only one page. The issue was found only in the on premise extensions in Business Central. |
| Per Diem | We have fixed an issue in the Per Diem calculation where the meals were not deducted from the total allowance, when the "First/Last Day calculation method" is set to "Sub Rates" or "First/Last Day fixed rates". |
| Per Diem | In approval entries comments were not shown for Per Diems. |
| Per Diem | We have prevented changing per diem details on a posted per diem. |
| Document Approval | We have fixed an issue, where an approver was not able to see documents rejected on behalf of someone else in the web approval portals history view. |
| Document Approval | We have added missing indirect permissions for Table 6086344 "CEM Credit Card User Mapping" needed for the CEM-APPROVE role. |
Expense Management 2021 R1, hotfix 1
Released: March 1, 2021
App version: 7.0.1.0
FOB version: 7.00.01
Bug fixes
| Functional area | Description |
|---|---|
| General Application | An issue found in Document Capture required that Expense Management is also rebuilt. Otherwise there was no change in the product. |
Expense Management 2021 R1
Released: March 1, 2021
App version: 7.0.0.0
FOB version: 7.00.00
New or changed functionality
| Functional area | Description |
|---|---|
| Platform and technology | All the methods inside the solution were marked as “internal”. A more detailed explanation can be found here: https://continia.zendesk.com/hc/da/articles/360018499999-Important-notice-about-internal-functions-in-the-next-versions-of-our-products |
| Platform and technology | When using the O365 email address, it is now possible to use also the Expense Portal and transfer documents from the Expense App/ Expense Portal to Business Central and the other way around. In the past it was only possible to use the Approval Portal. |
| Platform and technology | We have added multiple new Event Publishers. The updated list can be found here: https://continia.zendesk.com/hc/da/articles/360011785419-Expense-Management-Event-Publishers |
| General Application | We have added the possibility to create custom field dependencies that can be set up in Business Central and impact the user experience in the Expense App and the Expense Portal. The functionality existed in the past based on the Default Dimension and it was automatically calculated. This is no longer the case in the current version and setup is expected in the Field Dependency page. |
| General Application | We have added the possibility to set Company Policies. Documents can be automatically approved below a certain limit. A warning comment can be raised when the limit is exceeded. Also, a top limit can be set and the documents will not refund more than that particular limit. |
| General Application | We have done improvements on the Reimbursement pages, so that is more visible which amounts are refundable to the users. We have also added the possibility the Export to Excel the output of the page. |
| General Application | User Delegation - we have created the possibility to create documents on behalf of another user. This is now available also in the Expense App and in the Expense portal. In Business Central the functionality replaces the "User Responsibility" functionality. |
| General Application | We have moved the Assisted Setup functionality to Continia Core. There are no changes in the user experience. |
| General Application | We have changed the caption of the Expense Country/Region table to "EM Country/Region" to eliminate the confusion with the standard table. |
| General Application | We have renamed "Release notification entries" to "Notification Outbox" |
| General Application | We have improved the user experience in regards to reopening documents so that we prevent misuse. |
| General Application | We have added the queue "Notification Outbox" in the Role Center. |
| General Application | Various caption improvements. |
| Expenses | We have added the possibility to specify if an attachment is recommended, optional or mandatory on an Expense Type. The rule will then be respected also in the Expense App and the Expense Portal. |
| Expenses | We have made it easier to se if an expense has been allocated in the list of expenses by introducing the "Allocated" field. |
| Transactions | We have introduced the possibility of importing bank transactions based on manually created templates. In this way, custom transaction files can be mapped and imported manually from within Business Central. |
| Transactions | The primary key of the "Bank Transaction" and "Bank Transaction Inbox" tables is no longer generated in Continia Online, but it is incremented in Business Central. |
| Mileage | We have implemented the 60 days rule for mileage, specific for the Danish market. After refunding mileage for 60 days to the same address the system will help the bookkeeper with a warning. |
| Mileage | We have implemented the possibility to reduce the distance from home to office in a mileage. |
| Per Diem | We have change the default values on the Per Diem details for Breakfast, Lunch and Dinner. By default, they will not be marked as true anymore. |
Bug fixes
| Functional area | Description |
|---|---|
| General Application | In the Release Notifications page, we have changed a caption from "Expense Header" to "Settlement". |
| General Application | When loading the company logo, the message would have said "The company logo was uploaded" but it was only loaded in the database. We made sure the logo is also uploaded in Continia Online. |
| General Application | The Expense Management rolecenters would be inactive and block the client in Business Central 15 and 16 due to an issue in Business Central when controlling the visibility in the Activities page. In these clients, we are always showing these controls, even when Expense Management is not active, to avoid this issue. In Business Central 17 the functionality works as expected. |
| General Application | The status report would display "Paid Out" = 0 on settlements, where the first expense was non-reimbursable, even though other documents on the same settlement had been reimbursed. |
| General Application | We have changed the Lessor integration object name from "Expense Management 6.50 - Lessor Integration - NAV2013 R2 - 2018" to "Expense Management 6.50 - Lessor Integration - NAV2013 R2 - 2019" |
| General Application | Multiple fields from Expense Management Setup require a synchronization after their values have changed. We are now identifying these fields and asking the user to synchronize. This is a light synchronization and is expected to take very little time. |
| General Application | We have fixed an issue when changing from one Settlement Card to another one (page up/down) all the previous attachments were shown, even when this current settlement doesn't have any attachments. |
| Expenses | We have fixed an issue where the Country Code was not inherited from the Transactions to the Expense. |
| Transactions | We have fixed an issue that caused the Bank Country/Region Map values to not be saved. This was happening in a situation where the string to be mapped was the same as the country code. |
| Mileage | Mileage with company vehicles don't necessarily need a mileage rate. We have found and fixed an issue when a rate actually existed. The user total distance would have never been reset when a new mileage year started. |
| Per Diem | We have addressed an issue in the Per Diem calculation engine for the hourly ratio method, where a 24 hours calculation would bring different results depending on the time of the day the trip started. |