Detailed Changelog for Continia Expense Management 2022 R1

This article lists all new features and bug fixes for each version of Continia Expense Management 2022 R1.

Expense Management 2022 R1 Service Pack 2

Released: June 17, 2022
App version: 9.2.0.0
FOB version: 9.02.00

New or changed functionality

Functional areaDescriptionId
Document ApprovalWe have added the possibility to add "Out of office" settings from the Approval Entries page.28378
ExpensesWe 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 ApplicationWe are now marking "User Delegation" entries as Disabled. A delegation could have become invalid because they were wrongly setup or because it became invalid over time.  The administrator can now easily identify disabled delegations and either fix them or remove them in the Expense User Delegation page.27907
General ApplicationWe have changed the behavior when rejecting a document. In the past if "Auto submit for approval" was set, the rejected document was sent to the user (status = Pending Expense User), otherwise, it would have been kept in Status = Open. Since this was inconsistent with the behavior when approving a document, we have changed so that all the rejected documents are sent to the Expense User, independently of setup.
28189
General ApplicationWe are now processing the release notifications from the Notification Outbox as part of the normal synchronization with Continia Online.28682
General ApplicationWe 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
General ApplicationWe have made it possible to un-assign payment types from users. The corresponding payment type is automatically un-asigned when a credit card is deleted.32275
General ApplicationWe have made it possible to configure a mandatory field that is "Hidden by Default". The field becomes mandatory only when visible to the user. Therefore we have made ATTENDEES mandatory by default when you reset your configuration to the default setup, in the Configured Fields page.32434
General ApplicationWe have reintroduced the Field Type EMPLOYEE NO. so that it can be used in posting descriptions in the Expense Management Setup. It is an internal system field and it cannot be configured. The EMPLOYEE NO. will show the User ID from the posted document, but without an eventual domain name.34700
General ApplicationWe have added the possibility to show the Base Amount, VAT Amount and Percentage on the expenses lines on a settlement. Similar to what is already on the expense card page.34790
General ApplicationWe have created a tool meant to be use before upgrading from on premise to cloud, to help with the transition of attachments. The tool will move the document storage to Database and convert PDF files into PNG (necessary in later versions for preview). The process is described in the following article: https://continia.zendesk.com/hc/en-us/articles/360014053519
34921
General Application

In Business Central 2021 release wave 1 (BC18), email scenarios are now supported for the following processes:

  • Expense Management Approval Status Email - Used when sending the approval status email.
  • Continia Welcome Email - Used when sending the welcome emails to Continia users.
  • Expense Management Status Email - Used when sending status emails to the expense users.
  • Expense Management Reminder Email - Used when sending status emails to expense users that have pending documents.

38400
General ApplicationWhen using Business Central online, the Document Capture Activities part is only visible if Document Capture is activated.
38656
General ApplicationWe have added the following Event Publishers

Table 6086309 CEM Posting Setup
  • OnBeforeModifyExistingExpense
  • OnBeforeModifyExistingMileage

Table 6086320 CEM Expense
  • OnExpenseTypeValidateBeforeExpValidation
  • OnAfterNewCalculatedAccount

Table 6086330 CEM Bank Transaction
  • OnBeforeInsertExpense

Codeunit 6086338 "CEM Settlement-Post"
  • OnBeforeCreateGenJnlBalanceEntrySet
Codeunit 6086319 "CEM NAV-version Mgt."
  • OnBeforeBalancePostGenJnlLine

38675
Platform and TechnologyYou can now change the size of the document view in the BC Web Client. This applies to the preview of the attachments on expenses, approvals, mileage and in the expense report.
Article: https://continia.zendesk.com/hc/da/articles/4404757400722-How-to-change-the-size-of-the-document-view-in-BC-Web-Client
28928

Bug fixes

Functional areaDescriptionId
Credit Card TransactionsWe have fixed an issue that was causing the upgrade to EM 9.00 and 9.01 to fail with the error below when the Bank Account number would have been a string longer than 10 characters.
  • The length of the string is 12, but it must be less than or equal to 10 characters. Value: LONGER_THAN_10_VALUE
34393
Credit Card TransactionsWe have fixed an issue, where rejecting a bank activation request, could result in the following error message during synchronization.

"Bank Code missing. Continia Online has provided an agreement activation but the bank doesn't exist."
38522
ExpensesWe have fixed an error, when attempting to merge two expenses that are not both cash/private card. Error Message:
  • Merge not allowed
32723
ExpensesIn earlier versions it was possible to use a system field from one table, as an extra field in another. We have prevented that, but if such fields still exist in your configuration you would get this error. Example from the Expense Report Inbox.
  • "The Field Name COUNTRY/REGION is a system field and cannot be imported as an extra field."
In order to fix the configuration issue, please run the function Reset to Default Setup. In order to fix the expense report inbox entries in error, please find the COUNTRY/REGION Extra Field and delete the entry. Then, you can add the value of the COUNTRY/REGION on the Expense Report Inbox entry, instead.
32732
ExpensesWe have fixed an issue when submitting unmatched expenses with a payment type, for which matching is not required. The expense would not be send automatically for approval, as it should.
The user would get a comment saying: 
  • User has corporate credit card in Continia User Credit Card List. Verify this expense is not waiting for transaction to be matched.
32755
ExpensesWe have fixed a bug that wasn't allowing the payment type to be edited when a user had no payment types assigned.34518
ExpensesWe have fixed a bug when creating a new expense in NAV/BC, would result in an error, if the Expense User had only one payment type assigned.34816
ExpensesWe 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 ApplicationWe have fixed an issue that was suggesting translation "Code" for the dimensions when creating a Field Type. 19608
General ApplicationWe have fixed a caption issue on the "Field Type Dependencies" page.26878
General ApplicationWe have disabled the drilldown functionality on the "Continia User Name" on all the pages since it was revealing a different result than the lookup on the Continia User ID. This was not only bringing confusion but sometimes it would lead to other issues, as well.28322
General ApplicationFunctions or actions modifying Approval Entries could in some cases experience a performance issue. This has been fixed. 28367
General ApplicationWe have done some performance improvements based on feedback from the Application Insight logs.28370
General ApplicationWe have fixed a number of issues related to Continia Users with Limited Document Visibility. Some are related to approvers others are general. 
1) A Continia User with limited document visibility can only view his or hers own documents. The restriction also applied to approvers with limited document visibility. Now we allow the next approver of the document to view the document, even if otherwise limited to only view own documents. The approver would get the following error message:
  • "Document X for User Y cannot be displayed because you only have access to your own documents."

If the approver is also an expense user with delegations the message would be: 
  • "Document X for User Y cannot be displayed because you are only allowed to handle documents for the following users: Z."

Where "Document" would be either Expense, Mileage, Per Diem or Expense Report/Settlement.

2) In older versions of Expense Management the message was wrong and looked like this: 
  • "Expense Expense for X cannot be displayed because you only have access to your own documents."

3) We also found that in special cases, some users with limited document visibility would have had access to posted per diems where they shouldn't have had access. This has been fixed.
4) When opening an expense document by choosing View from the reimbursement matrix and release notification entries, it was in some cases possible to view the document in the wrong page and to navigate to other documents. This has been fixed.

5) The view document action button in the reimbursement details, approval entries and release notifications had three different icons. They now all have the View icon. 

6) In the Approval Entries (Forms only), the press the Show button and then choose the View option. It would not display per diems. This has been fixed. 

7) Posted Expenses, Mileage, and Expense Report would not give an error message when a user with limited document visibility opened the Posted Document Card page. The Posted Per Diem card did give a message. This has been changed to that the logic on the Posted Card is the same as on the normal Card. 

8) We were missing the Check Data Version on several document card pages.
30712
General ApplicationWe have fixed an issue that was causing the error below. It would occur when posting a Per Diem, for a user that was part of a group and there was posting setup only for the group.
  • "There is no Posting Setup within the filter. Filters: Type: Per Diem,Type Code: ACCOMMODATION."
31553
General ApplicationIn version 9.00 we prevented creating a custom Field Type with the same code as a Global Dimension and this is an issue we have corrected. Global dimension codes are no longer reserved Field Type codes. 32249
General ApplicationWhen 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 ApplicationWe did not increase the object Version number when we changed the captions "Settlement" to "Expense Report" in the following objects. 
Table 6086327 CEM Expense Management Cue
Table 6086340 CEM Settlement Overview Line 
Table 6086354 CEM Continia User Statistics
Table 6086361 CEM Comment
Table 6086364 CEM Reminder
Table 6086371 CEM Comment Line
Table 6086401 CEM Attachment Pages
Table 6086402 CEM Attachment Pages Inbox
Report 6086315 CEM Batch Post Per Diems
Codeunit 6086323 CEM Comment Mgt.
Codeunit 6086326 CEM Navigate Settlement - Find
Codeunit 6086339 CEM Settlement-Post (Yes/No)
Codeunit 6086359 CEM Move to Company
Codeunit 6086370 CEM Workflow Event Handling
Codeunit 6086371 CEM Workflow Response Handling
Codeunit 6086381 CEM Settlement - Validate
Codeunit 6086382 CEM Settlement - Send to User
Page 6086305 CEM Reminders
Page 6086308 CEM Limited Role Center
Page 6086409 CEM Expense Settlements
Page 6086431 CEM Continia User Factbox
32340
General ApplicationWe have fixed an issue in the Assisted Setup that was leading to the errors below.

"Sorry, we just updated this page. Reopen it, and try again." 

"PD-BREAKFAST is a required Per Diem Detail system field. Please configure it before synchronizing."
32349
General ApplicationWe have fixed a bug in the approval portal, where an approver could experience the following error message:

"You do not have the following permissions on TableData Job: Read."
32358
General ApplicationWe corrected a spelling mistake on the approval page.32373
General ApplicationWe have fixed a silent error that could be found in a Business Central client, when looking for the "Last Known Error". This was happening after a synchronization occurred, in a system where the Default Payment Type was, in the same time, assigned to a user. The error would come from the database, when trying to insert a duplicate entry.
" Error code: 85132273
DB:RecordExists
"CEM Online Synch. Mgt."(CodeUnit 6086305).UpdateLookupValueAcces line 46 - Continia Expense Management 365 by Continia Software
"CEM Online Synch. Mgt."(CodeUnit 6086305).SetupValueAccess line 8 - Continia Expense Management 365 by Continia Software
"CEM Online Synch. Mgt."(CodeUnit 6086305).SetupContiniaOnline line 6 - Continia Expense Management 365 by Continia Software
"CEM Online Synch. Mgt."(CodeUnit 6086305).Code line 44 - Continia Expense Management 365 by Continia Software
"CEM Online Synch. Mgt."(CodeUnit 6086305).OnRun(Trigger) line 2 - Continia Expense Management 365 by Continia Software
"CEM Configured Field Types"(Page 6086446)."ForceSynchronize - OnAction"(Trigger) line 5 - Continia Expense Management 365 by Continia Software "
32566
General ApplicationWe have fixed an error in the upload company logo functionality, which would fail silently, and roll back the changes to the company logo.32567
General ApplicationWe have marked the table 6086373 Vehicle User and the page 6086403 CEM Vehicle User List as deprecated.32730
General ApplicationWe have corrected some spelling errors.32753
General ApplicationIf you had DEPARTMENT and PROJECT as global dimensions 1 and 2, we would add them as system field types when choosing the action Reset to Default Setup on the Configured Fields page. That was a mistake. Field types pointing to global dimensions are not considered system fields. If you have this issue, simply run the Reset to Default Setup action again. 32815
General ApplicationIn an earlier version we renamed Settlement to Expense Report, but when creating demo data with the Expense Management Wizard (Assisted Setup), we continued to create a Source Code called SETTLEMENT. We have now changed it to REPORT.32818
General ApplicationWe have added a new Codeunit to automatically update Field Dependencies, intended to be used in the Job Queues. Codeunit 6086569 CEM Update Field Dependencies will update lookup values and update system field type dependencies. If any field type dependency has been disabled due to conflicts, the Codeunit will stop with the first error found. 32881
General ApplicationWe have fixed an upgrade issue that would have been logged with the error below: 
  • CEM Upgrade Functions"(CodeUnit 6086107).EM800UpgradePerDiemTables line 41
34438
General ApplicationWe have fixed an upgrade issue that would have been logged with the error below: 
  • CEM Upgrade Functions"(CodeUnit 6086107).MoveMandatoryEditableValues line 7
34439
General ApplicationWe have fixed an upgrade issue that would have been logged with the error below: 
  • CEM Upgrade Functions"(CodeUnit 6086107).CreatePaymentTypes line 75
34440
General ApplicationWe have corrected an issue that was naming all the Expense Management permission sets wrongly. The permission sets were prefixed with "CCEM" instead of "CEM" and this was leading to issues after the upgrade.34471
General ApplicationThe field type dependency can be disabled with the following message: 
  • The following users don't have access to value X in the field Y
  • The following user groups don't have access to value X in the field Y
We have improved the consistency check to not disable field type dependencies in the case where user also had a restricted lookup value access on the specific value in the condition for the field dependency.
34547
General ApplicationAn expense document could be stuck in the inbox with this error text. 
  • The Field Name  was not found in the Field Type table.
This has been fixed.
34581
General ApplicationWe 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.
  •  "User with user ID <email> does not exist in the Continia User table."
34643
General ApplicationWe 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 ApplicationWe have fixed a bug, where a blank drop down list was presented, when trying to look up a vendor account on the payment type card.38354
General ApplicationWe have extended the "Reset to Default Setup" function on Configured Fields, to automatically add the default dimensions, if not already there. The default setup file is therefore no longer containing dimension fields. This solves an issue where default dimensions were added by the setup file, but the dimension codes wouldn't actually match the dimensions in the system. For example, field type PROJECT must have been linked to dimension PROJEKT in a Danish localization. 38367
General ApplicationWe 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.
  • The length of the string is 51, but it must be less than or equal to 50 characters. Value: A very long description, longer than 50 characters.
38431
General ApplicationWe 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
MileageWe 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:
  • There is insufficient memory to execute this function. This can be caused by recursive function calls. Contact your system administrator.
38457
MileageThe information on the "To Distance", in the mileage details was always 0. There is no expected impact on the calculation of the mileage rates, the issue is just a visibility one. This behavior was introduced in version 9.0.38468
Per DiemsIf was possible to set the arrival time of the first destination to earlier than the departure time of the Per Diem and it was possible to set the arrival time of the last destination to later than the arrival time of the Per Diem. We are now preventing this.27121
Per DiemsOn 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 DiemsWe have identified and fixed a wrong calculation on the Per Diem, when using hourly rates, on the last day of the trip.34367
Per DiemsWe 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 DiemsWe have fixed an issue on the per diem calculation where the meal value deducted a wrong amount for rates where "Meal Value Method" was an Amount instead of Percentage
34502
Per DiemsWhen configuring the "Description 2" field on a per diem the per diem would be stuck in the Inbox with the following error text:
  • The Field Name P-DESCRIPTION 2 is a system field and cannot be imported as an extra field.
34618
Per DiemsWe have fixed an issue where a Per Diem would show the following error if the "Daily Meal Allowance" was not set.
  • Attempted to divide by zero.
34625
Per DiemsWe have fixed an issue in the Per Diem calculation that was, in certain conditions, skipping one day rate when using sub-rates.38607

Expense Management 2022 R1, hotfix 2

Released: May 3, 2022
App version: 9.1.0.2
FOB version: 9.01.02

Bug fixes

Functional areaDescriptionId
ExpensesWe have fixed a bug that wasn't allowing the payment type to be edited when a user had no payment types assigned.34518

Expense Management 2022 R1, hotfix 1

Released: May 2, 2022
App version: 9.1.0.1
FOB version: 9.01.01

Bug fixes

Functional areaDescriptionId
Credit Card TransactionsWe have fixed an issue that was causing the upgrade to EM 9.00 and 9.01 to fail with the error below when the Bank Account number would have been a string longer than 10 characters.
  • The length of the string is 12, but it must be less than or equal to 10 characters. Value: LONGER_THAN_10_VALUE
34393
General ApplicationWe have fixed an upgrade issue that would have been logged with the error below: 
  • CEM Upgrade Functions"(CodeUnit 6086107).EM800UpgradePerDiemTables line 41
34438
General ApplicationWe have fixed an upgrade issue that would have been logged with the error below: 
  • CEM Upgrade Functions"(CodeUnit 6086107).MoveMandatoryEditableValues line 7
34439
General ApplicationWe have fixed an upgrade issue that would have been logged with the error below: 
  • CEM Upgrade Functions"(CodeUnit 6086107).CreatePaymentTypes line 75
34440
General ApplicationWe have corrected an issue that was naming all the Expense Management permission sets wrongly. The permission sets were prefixed with "CCEM" instead of "CEM" and this was leading to issues after the upgrade.34471

Expense Management 2022 R1 Service Pack 1

Released: April 1, 2022
App version: 9.1.0.0
FOB version: 9.01.00

New or changed functionality

Functional areaDescriptionId
Document ApprovalWe have added an event publisher to Codeunit 6086312: OnBeforeApprovalMgtCode()31358
General ApplicationConfigured Fields are dynamically added or removed based on when functionality is enabled or disabled in Expense Management Setup.  We have added an action to help the user access the Configured Fields page directly from the Expense Management Setup page. 
29018
General ApplicationWe have removed the "Error Email" field from the Expense Management Setup, as this field had been made redundant by other improvements on the Continia User Setup.  We have also removed the field "SMTP Require SSL/TLS" which becomes obsolete in the enhanced email context. 31577
General ApplicationWe have enabled the feature of signing expense attachments digitally in the French and Belgium localizations.31662
General ApplicationWe have added the Job and Task description in the Approval Portal.32035
MileagesWe've amended the sixty day check with a crude text string comparison on the addresses in cases where geo coordinates are not available (e.g. legacy data from prior to introduction of the feature).31850
Per DiemsIn the Norwegian localization, when calculating per diem allowances, we have changed the rounding precision to the nearest ones so that it complies with the legislation. In the past it was based on the currency rounding precisions. 31865
Per DiemsOn per diems sub-rates, we have added the possibility to specify the minimum number of hours after which a full day allowance is refunded.31866
Platform and TechnologyWith Expense Management 2022 R1 service pack 1 (9.01), we have released Expense Management for Microsoft Dynamics 365 Business Central 2022 release wave 1 (BC20).

Expense Management 2022 R1 service pack 1 (9.01) in Business Central online will not be available for Microsoft Dynamics 365 Business Central 2021 release wave 2 (BC19). You will only be able to use Expense Management 2022 R1 service pack 1 (9.01) in Business Central online when you have upgraded to Microsoft Dynamics 365 Business Central 2022 release wave 1 (BC20).
32415

Bug fixes

Functional areaDescriptionId
Credit Card TransactionsWe've increased the length limit of the Transaction ID which the bank can send to 150 characters.13728
Credit Card TransactionsWe have fixed the following error when synchronizing the activation of a bank agreement:  " The bank does not exist. Identification fields and value Code='',Country/Region Code='' "31742
ExpensesWhen no Expense Type was specified on the expense we gave two error messages.  This has been reduced to one: "Expense Type must be specified." The second message "You must specify Expense Account Type and Expense Account in Expense Posting Setup for expense type ." only appears when the expense type is specified.27782
ExpensesWe have fixed a bug on the expense card, where for cases of reverse charge VAT, the VAT and Base Amount was displayed wrongly.31410
ExpensesWe have fixed a bug where the Payment Type field was uneditable on the Expense List Page.31454
ExpensesWhen using the Vendor number (business vendor) on expenses, the payments on the Vendor were only applied in the Spanish localization. We are now applying the payments in all localizations.31630
ExpensesThe Reimbursement page was showing the error below if an expense didn't have a payment type.  "Continia User Setup: The Payment Type does not exist. Identification fields and values: Code=''"31641
ExpensesWe have moved the "Submit Cash Expenses in LCY" from Expense Management Setup to Payment Type.31948
General ApplicationWe 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 ApplicationExpense Management can store documents in three different locations: on the server hard disk (file system), the database, and in an azure blob storage. When running the Expense Management Setup Assisted Setup, the user could only choose File System and Database. We have added Azure Blob Storage to the Wizard. 28806
General ApplicationWe 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 ApplicationWe have fixed a bug where it was possible to send a welcome mail to an Expense Management user with an "empty" link to the Expense Portal.31566
General ApplicationWe 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 ApplicationWe have improved the caption on the request page of the batch posting of expenses, mileages and expense reports.31650
General ApplicationIn 9.00 we introduced a bug where Lookup Value Access on User Groups did not get synchronized to Continia Online. Lookup Value Access restricts the values a user or a user group can see in the Expense App/Portal. The issue was that, for a group, we would have shown all the values, not only those specific to the group. We have now corrected the issue.31805
General ApplicationWe did not increase the object version number when we changed the captions "Settlement" to "Status Report" in the following objects. Therefore we have done it now.
Page 6086301 "CEM Role Center" 
Page 6086302 "CEM Activities"
31912
General ApplicationWe added an image to the Tax Report action on the posted document lists.32152
General ApplicationWe have fixed an issue in the Assisted Setup that was leading to the errors below. "Sorry, we just updated this page. Reopen it, and try again." 
"PD-BREAKFAST is a required Per Diem Detail system field. Please configure it before synchronizing."
32349
Mileages

On the Approval Entries page, on a mileage, when choosing the action Details.

You would get the error message Allocations are not supported on mileage.

Now it will open the page Mileage Details.

28305
MileagesDue to an issue in created demo data, the system could end up having two default vehicles. When trying to unselect one of them you would get an error message. 
There can only be one default Vehicle.
This has been changed so that when the user sets default to Yes on a vehicle, then all others vehicles are automatically have default set to No.
31992
Per DiemsPer Diem taxable amounts were calculated wrongly for a Per Diem with Sub-Rates, when the trip was shorter than 24 hours. This functionality was introduced in EM 9.00.31640
Per DiemsMeal taxable allocation values were wrongly calculated. This functionality was released in EM 9.0031867
Platform and TechnologyWe have added support for Automated Data Upgrade in Business Central Spring 2019 Release (BC14).32280

Expense Management 2022 R1

Released: March 1, 2022
App version: 9.0.0.0
FOB version: 9.00.00

New or changed functionality

Functional areaDescription
ExpensesWe have introduced the concept of Payment Types, which replaces the Cash/Private field and takes over functionality from Expense Management and Credit Card.
A payment type is an account that defines the behavior of an expense. On the Payment Type, you can specify the posting accounts, if matching is required or if the user has to be reimbursed.
As part of the upgrade, all the expenses will have a Payment Type added, if a decision can be taken and if the expense can be updated.
General ApplicationWe have added more setup pages to the Business Setup (Manual Setup) list.
General ApplicationWhen choosing to add a Field Type to a configured Field, the user was presented with the complete list of Field Types. We have optimized this to only show the list of relevant fields.
General ApplicationWe have improved the usability of Field Type and Configured Fields. From the Configured Fields, you can create field types and the card page will lead you through the possible settings. We have removed the Field Type list and we expect the Configured Fields page to be the entry point.
General ApplicationWe have removed the field type "EMPLOYEE NO".
General ApplicationWe are now showing the Filter column by default in the Table Filters of the Field Types.
General ApplicationWhen specifying the Source Table on the Field Type, the user can directly type the table caption or part of it. For example, "Currency", "currency", "curr", "4" (the table id) are all valid values.
Furthermore, the user can copy the Source Table information from the Help, About this page and paste it directly to the Source Table field. For example, "Currency (4)" will also work.
General ApplicationThe setup file now activates history in the Cloud to 6 months by default.
General ApplicationWe have renamed "Settlement" to "Expense Report".
General ApplicationTeaching Tips on Expense Page.
General ApplicationTeaching Tips on Mileage Page.
General ApplicationTeaching Tips on Per Diem Page.
General ApplicationTeaching Tips on Expense Report Page.
General ApplicationTeaching Tips on Bank Transactions Page.
General ApplicationWe have renamed the "Navigate" action to "Find Entries", to be more consistent with the standard Business Central client.
General ApplicationWe have added Description 2 on Mileage and Per Diem.
General ApplicationDigital signing is also available in France.
ExpensesWe can now disable standard approval notifications.
ExpensesWe have also added the External Document No. to the expenses that are matched.
Per DiemWe have introduced the possibility to disable the Accommodation or Meal allowances on the Per Diem.
Per DiemOn the Per Diem sub-rates, the percentage of meals is subtracted from the sub-rate value. In the past, a meal amount was calculated from a full day. This functionality comes to help the Austrian Per Diem rules.
Per DiemWe have added several features for Per Diems, in order to support requirements in the Norwegian market.
We have added the possibility to add taxable rates on top of the tax-free rates.
We have added the possibility to add an accommodation type like a hotel, guest house, etc.
We have added a tax report which can be handed to the tax authorities, which sums all the main details about a document so that the validity of the document can be assesed.
Platform and TechnologyWe have improved the Icon (Image) handling. An icon can be chosen from a predefined list of images and it's present on the main account types: Expense Types, Vehicles, Allowances, Payment Types.
Platform and TechnologyWith the release of Expense Management 2022 R1 (9.00), we only support Business Central 2019 Spring (BC14) and newer versions.

Even though we don't support Business Central October 2018 (BC13) or older versions in Expense Management 2022 R1 (9.00), we will still support the old NAV/Business Central versions in future service packs released for Expense Management 2021 R2 (8.00).

Bug fixes

All relevant bugfixes released in service pack 1 to service pack 2, hotfix 3 for Expense Management 2021 R2 (8.00), service pack 1 to 3 for Expense Management 2021 R1 (7.00), and service pack 1 to 4 for Expense Management 2020 R2 (6.50) are also included in Expense Management 2022 R1 (9.00). The description of these bugfixes is not repeated on this page.


Functional areaDescription
General ApplicationWe have fixed an issue that was calculating wrong total amounts on the Per Diems, in the Status Report.
General ApplicationWe 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.
General ApplicationWe have fixed an issue in the addin that was setting a default zoom of 1% on the attachments.
General ApplicationWe have fixed an issue where the number of documents was not correct in the Approval Portal.
General ApplicationWe have fixed a bug where an empty agreement was created when an activation request was rejected.