Detailed changelog for Continia Expense Management 2023 R2
This article lists all new features and bug fixes for each version of Continia Expense Management 2023 R2.
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 2024 R1 Service Pack 4
Release date: January 31, 2025
App version: 12.4.0
Fob version: 12.04
New or changed functionality
| Functional area | Description | Id |
|---|---|---|
| Mileages | (For Danish localization) When the 60-day rule is enabled, an error comment now generates 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 | (For Danish localization) To bring more clarity to calculating the 60-day rule, the 60-Day Rule Day Count and 60-Day Rule Destination fields have been added to the mileage list.
| 61550 |
| Mileages | (For Danish localization) When the 60-day rule is enabled, you can now see a warning comment if neither the From Home nor To Home checkboxes are ticked but there is a clear correlation to a previously used home address within the default range of 300 meters. | 62432 |
| Mileages | (For Danish localization) When the 60-day rule is enabled, you can now see a warning comment when GPS coordinates are missing on a mileage. GPS coordinates are used to calculate the proximity to a destination address and perform checks around the home address. Lacking GPS coordinates affects the calculation of the 60-day rule, causing the calculation to fall back on identifying similar destination addresses based solely on the address text. | 62433 |
| Mileages | (For 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 it with the previously used address. | 62467 |
Bug fixes
| Functional area | Description | Id |
|---|---|---|
| Document Approval | Users with a CEM-APPROVE permission set assigned to them no longer receive the following error when trying to add an attachment to an Expense Document in the Continia Web Approval Portal:
| 62512 |
| Expenses | Allocations containing personal items will now be included when creating an invoice for a business vendor. Previously, personal items were excluded from business invoices. However, they are now classified as company expenses and will be reflected in the purchase document. | 52886 |
| General Application | The reimbursement dialog displayed an incorrect user count under certain conditions. This has been resolved. | 55288 |
| General Application | When using the CEM Tax Report, the Settlement No. filter on the request page was not respected. | 58767 |
| General Application | When an expense report was reimbursed, it triggered a notification in the Expense App for each sub-document. This has now been resolved so there is only one notification sent for the whole document. | 59145 |
| General Application | When upgrading a company where a Digital Sign Attachments is enabled, without having a Company Code specified in the Continia Company Setup, the following error would show:
| 62215 |
Expense Management 2023 R2 Service Pack 3
Release date: July 1, 2024
App version: 12.3.0
FOB version: 12.03.00
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Credit Card Transactions | When the Card No. is blank on transactions imported as .csv file through Transaction template tool, users will get an error when trying to Approve and Transfer. | 54141 |
| Expenses | The field Matched to Bank Transaction has been added on Posted Expense List and Card pages. | 53354 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Document Approval | Approvers are now able to modify Expense Allocations when Expense is part of an Expense Report in Pending Approval Status. | 54255 |
| Expenses | When updating the foreign currency on an allocated expense, the Amount (LCY) would have not been recalculated. | 55645 |
| General Application | The RTC Client would have crashed if the first attachment file was not available. The issue was introduced in the version 12.01. | 52792 |
| General Application | The Expense Management Status Report kept failing when the Corporate Language was ESP. | 54225 |
| General Application | When having multiple attachments, only the first attachment was presented in the Roletailored Client. | 54392 |
| General Application | When posting expenses in foreign currencies where the Amount Rounding Precision allows more decimals than the local currency and Post in Expense Currency was enabled. The following error message was stopping the process.
| 54691 |
| General Application | When adding filters on a Field Type, in the No. Of Source Table Filters, the calculated No. of Lookup Values was not updated. The issue was only visually not updated. | 55300 |
| General Application | When automatically sending for approval expense reports, the process would only have been tried once after which it was abandoned, leaving extra work for the system administrators. The functionality now retries sending for approval every synchronization. | 55597 |
| Mileages | When calculating mileage over a certain Starting Distance, the lower rate was not applied. Instead the next year rate was picked up, if this was specified. | 55306 |
Expense Management 2023 R2 Service Pack 2, hotfix 1
Release date: April 9, 2024
App version: 12.2.1
FOB version: 12.02.01
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Mileages | In the Spanish localization, when posting a mileage, the Bill-to/Pay-to No. was not respected resulting in a posting error. | 54427 |
Expense Management 2023 R2 Service Pack 2
Release date: March 7, 2024
App version: 12.2.0
FOB version: 12.02.00
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | With the introduction of Enforced Digital Vouchers in BC23.2, attaching documentation as incoming documents, prior to posting purchase document and journals, will in certain localizations become mandatory. When using Expense Management in an environment where Enforced Digital Vouchers is configured to check for attached files prior to posting, Expense Management will transfer the underlying digital vouchers to the posted documents. When posting an Expense, the digital voucher will be enforced and the expense cannot be posted without providing an attachment which becomes the digital voucher. When posting Mileage and Per Diem, a tax report extract will be generated. This serves as a digital voucher for these documents. How to enable the feature:
| 50995 |
| General Application | Posting Date has been added to expenses and mileages. | 50039 |
| General Application | In the Web Approval Portal, when attempting to modify fields Project No. or Project Task No. on then Expense Allocation line, the following error would have stopped the user
| 52552 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Credit Card Transactions | When importing transactions with the Transaction Template it will no longer be possible to transfer data to the Transaction Import Journal unless a Bank Code is specified. The Bank Code is anyway necessary and will be reinforced later in the process, anyway. | 51874 |
| Credit Card Transactions | When importing transactions via the Transaction Import Journal, and a field value was longer than 250 characters, it would fail with the error below.
| 52139 |
| Expenses | When documents were approved due to Company Policy or Purchase Contracts, the Secure Archive log for approval was not created. | 50434 |
| Expenses | To prevent mismatches between the currency of expenses and their associated allocations, changing the Currency Code on an expense is no longer possible once allocations exist. This update ensures financial accuracy by maintaining consistent currency across expense entries and their allocations. | 51136 |
| Expenses | There is a new enhancement with the Enable Amount Distribution feature set and the Distribute by tax amount property enabled in the Distribution Code of the Expense Type. The Amount Including Tax field on the expense and its allocations now automatically updates, calculating and reflecting the corresponding tax values. | 51932 |
| Expenses | When a Distribution Code is applied to an Expense Type, and subsequently, the Expense Type is cleared from the expense, a new dialogue feature has been implemented. This dialog will prompt users to confirm whether they want to remove the automatically allocated lines that were added based on the Distribution Code. This ensures greater control and accuracy in expense allocation processes. | 52037 |
| Expenses | A negative expense would be created as a Purchase Invoice instead of a Credit Memo when a Preferable Purchase Invoice was set up. | 52434 |
| Expenses | Users with Can Edit Approved Documents enabled can now change the VAT Amount value on the Expense Card page when Expense has the status Pending Approval or Released. | 52514 |
| Expenses | The following Expense Comment now references the correct duplicate Expense Entry No.:
| 52582 |
| Expenses | Posting a Purchase Credit Memo for the business Vendor number (Vendor No. on the expense) would not trigger the automatic payment that had to be applied to that document. | 52803 |
| Expenses | When using the Vendor No. (business vendor) field on expenses, while having a Payment Type with a Vendor (bank account), the following error would have been raised, if the Continia User did not have a Vendor No. specified. The error has been replaced by a more meaningful one. We have fixed the following error when posting a Bank Purchase Invoice (a payment type posting on a Vendor).
| 52821 |
| Expenses | When an expense was marked as non-refundable (personal) and it involved the Vendor No. (business vendor) field, along with a Payment Type linked to a Vendor (bank account), a credit memo was issued to the business vendor. It was not correct to decide the document type based on the No Refund field on the expense, the document type should have always been Invoice for a positive expense and Cr. Memo for negative expenses. Furthermore, the creation of a business vendor document is skipped if the expense is non-refundable and the Payment Type posting Method is Post on the Expense User Account. | 52859 |
| Expenses | When navigating to Find Entries from a Purch. Cr. Memo generated by Expense Management, the expense was not shown in the Related Entries. | 52878 |
| Expenses | When a negative allocated Expense with Vendor Invoice No. was posted, multiple Purchase Credit Memos were created for each of the allocation lines instead of adding multiple allocation lines to the existing Purchase Credit Memo. | 52887 |
| Expenses | The field Payment Type is now visible on the Posted Expense Card page. | 52921 |
| Expenses | When downloading expense allocations with Billable set to True, the Job Line Type was not marked as Billable. | 52938 |
| General Application | On a Payment Type when Matched to Expense was set to Never Required, the fields related to the matching (variance, etc.) were not cleared of their values, this resulted in an error later in the process. | 50326 |
| General Application | On matched expenses, when the bank account currency code would have been different from the local currency (and the exchange rate was not available from the bank), currency differences would accumulate in the Intermediate Account because the posting date on the transaction would be different than the one on the expense. Posting Date was added on the expense. The posting date will be inherited from the bank transaction but available for editing for a user with the setting Can edit approved documents. | 51752 |
| General Application | When paying a cash expense the expense user was not receiving a push notification on his mobile app about the status change. | 51823 |
| General Application | When running the Tax Report the user name was incorrectly shown. | 51871 |
| General Application | Since version 12.1 it was not possible to export users having the same email address in the E-mail and O365 Authentication Email field. The functionality has now been reverted so that the email address can be overwritten both for authentication and email communication. | 52159 |
| General Application | When running the Tax Report, the date filters were not respected. | 52234 |
| General Application | We have added the missing Lessor Integration objects (.fob) for Business Central April 2019 (BCv14) on the release package. | 52298 |
| General Application | When changing the Document Date on a cash expense, the following error message was showing.
| 52328 |
| General Application | The value of Attendees Inbox table field Name is now being trimmed to 50 characters during Continia Online Synchronization to prevent the error:
| 52593 |
| General Application | When using the Vendor No. (business vendor) field on expenses, while having a Payment Type with a Vendor (bank account), an automatic payment was intended to happen when the invoice was posted. Instead, the error below would occur, while the invoice would have succeeded to post.
| 52835 |
| Mileages | When enabling 60-day-Rule, addresses without geo-coordinates (but with the same address text) would have not been taken into the consideration. | 53195 |
| Per Diem | When using the 3-months-rule and Multiple Destination was enabled on Per Diem, the system would prevent posting if the Address Code was not consistently specified. | 51933 |
Expense Management 2023 R2 Service Pack 1, hotfix 3
Release date: February 7, 2024
App version: 12.1.3
FOB version: 12.01.03
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Configuring an approval sharing record to send the approval status email to "Both Approvers" would in certain situations add the wrong recipient as CC to the email. The functionality has been disabled in this version of Expense Management. Existing approval sharing setup records configured to send the email to "Both Approvers" will be treated the same way as records configured to send to "Only Shared To User". The system will display an error message if the user attempts to configure an approval sharing setup record to send the approval status email to "Both Approvers". | 53175 |
Expense Management 2023 R2 Service Pack 1, hotfix 2
Release date: January 24, 2024
App version: 12.1.2
FOB version: 12.01.02
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Expenses | The field Tax Liable has been added to expenses to control Canada's tax calculations. Tax Liable is set by default when both Tax Group Code and Tax Area are specified. | 52421 |
| Expenses | On an allocated expense, when the Amount LCY decimal places were to be rounded because the total wouldn't fit 100%, in special conditions, this expense could not be posted because of CONSISTENT error:
| 52588 |
| General Application | When enabling the digital signing of documents, the functionality was too restrictive with attachment types that could not be signed anyway. For example, .eml attachments would have prevented the posting of that expense. The functionality is changed for checks only on relevant document types. (.png, .jpg, .pdf). | 52304 |
Expense Management 2023 R2 Service Pack 1, hotfix 1
Release date: December 21, 2023
App version: 12.1.1
FOB version: 12.01.01
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Document Approval | When a user accesses the Continia Web Approval Portal without using Document Capture, they encounter the following error:
| 52074 |
| General Application | When using the VAT/Tax amount fields, Expense Template Name and Expense Batch Name becomes mandatory for posting, but the fields were not visible. The following error would have occurred at posting time. "The Gen. Journal Batch does not exist. Identification fields and values: Journal Template Name='',Name=''". | 51878 |
| General Application | When using Post on multiple document numbers, in certain conditions the documents were grouped under the same document number, which was not the intention of the functionality. | 51994 |
| General Application | The 'Export Users' action on the Continia User Setup list was not visible if both Document Capture and Expense Management were installed, and no Web Portal had been configured. | 52077 |
| Per Diem | Fixed an issue with the per diem amount when the calculation became taxable because of the german 3-month-rule. | 52011 |
Expense Management 2023 R2 Service Pack 1
Release date: December 15, 2023
App version: 12.1.0
FOB version: 12.01.00
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | In the Belgian localization, an option to post an expense report by using multiple document numbers has been introduced. This is to ease the payment processing and is especially helpful for the EB Payment Journal. The functionality can be enabled in Expense Management Setup on the Expense Report tab: Post on multiple document numbers. | 46157 |
| Expenses | Expense Management now supports distribution codes, giving the possibility to automatically allocate expenses based on predefined rules on the expense types. The distribution codes can be added on the expense types and automatic allocations will be triggered when the document is sent for approval. In the Australian localization, the distribution codes can also allocate based on the GST percentage, once the AMOUNT INCLIDING TAX field is used. The allocation will also happen if the user changes expense types on the documents. | 50042 |
| Expenses | An EventPublisher "OnBeforeValidateAttachments" has been added in Codeunit 6086321"CEM Expense-Validate" to allow bypassing our standard Expense Attachments validation. | 51117 |
| General Application | "Updated By Delegation User" was changed to "Submitted By Delegated User". | 50295 |
| General Application | "Submitted By Delegated User" is added to Expense Report. | 50297 |
| General Application | The following procedures on Page 6086402 "CEM Client Addin - Settlement" are now available for external access:
| 50553 |
| Per Diem | When users travel to the same destination for more than 3 months, the rate will be set to taxable in Per Diem. This is known as the "3 months" in Germany, and it's only available in this localization. The setting can be enabled from the Expense Management setup page under the Per Diem tab. This functionality relies on the Address Code to do the calculations. | 46291 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Credit Card Transactions | When Payment Type was set to Selectable = No, the action Match or Create Expenses on Bank Transactions, was not visible. | 46193 |
| Credit Card Transactions | In rare circumstances, as when multiple synchronizations were running at the same time from different sessions, it would create two similar Bank Transaction entries with the same Transaction ID. | 50244 |
| Credit Card Transactions | When importing transactions via the Transaction Import Journal, the Currency Code on the Bank Transaction will be set to empty if it matches the local currency of the company. | 50454 |
| Credit Card Transactions | Importing Bank Transactions via Transaction Import Journal now correctly imports numerical (e.g. 840) Currency Code column value. | 51550 |
| Document Approval | When sending the approval mail for the sharing users, the mail was only sent to the first user. | 47819 |
| Expenses | When splitting an expense into multiple, the attachment file hash check would have failed even though the original file was not altered. | 49995 |
| Expenses | Secure Archive did not log when documents were automatically approved based on limits set with Company policies or purchase contracts set to auto approval. | 50434 |
| General Application | Bank Transactions were not able to be matched with Expenses in the status "Pending Approval" as it was causing an error for Users without "Can edit approved documents" enabled. | 27365 |
| General Application | On Expense Reports the attachment add-in was not showing properly when selecting a per diem. | 49988 |
| General Application | Expense Management (CA) is enabled to work in OnPrem installation. | 49994 |
| General Application | Fixed a bug where Outbox Notification entries are stuck in the Inbox in an error state but without an Error Text. | 50030 |
| General Application | An issue causing an error when running Report 6086314 "CEM Batch Post Settlements" via Job Queue has been fixed. | 50488 |
| General Application | Editing is re-enabled for the field "Status" of the following records (if other conditions are met). These were made non-editable unintentionally in version 12.0.0
| 50636 |
| General Application | When VAT is specified on the Payment Type balancing account, the error below will prevent posting the matched expense, when it should have prevented posting the bank transaction. The check is moved to the bank transaction posting checks.
| 50807 |
| General Application | "Configurable" field is available in the Comments page when it is opened from Settlement subdocuments (via Line -> Comments). | 50845 |
| General Application | Fixed an issue with the CEM-ALL permission set related to the secure archive feature. | 51208 |
| General Application | When integrating with Payment Management via the Continia Connectivity App, grouping payment suggestions would result in duplicated document entry numbers. | 51386 |
| General Application | Attempting to rotate a .jpeg file attachment no longer results in an error. | 51409 |
| Mileages | When synchronizing with Continia Online, a mileage recalculation is automatically triggered in all the companies for all the mileage rates available in the company and for all the mileages with status not posted. Because of the calculation on each mileage rate, the same mileage was recalculated multiple times, and this was causing performance issues. | 41445 |
| Mileages | The Mileage fields "From Home" and "To Home" can now be added to the Mileage subpage on Expense Report Card via page personalization. | 50489 |
| Mileages | When posting a mileage on a purchase invoice, the posting would fail if the "Mileage Tax" or "Mileage Fuel" account code was longer than 10 symbols. | 50641 |
| Mileages | The system went into a stage of a never-ending loop, if the date on Starting Distance, to calculate a lower rate than the main rate, was different from the date on the main rate. | 51566 |
| Per Diem | After modifying a Per Diem that had the status "Pending Expense User", attempting to modify Per Diem Details would cause multiple errors. | 31295 |
| Per Diem | When using Taxable Per Diem rates the calculations was not calculated correctly. | 51399 |
| Purchase Contracts | The relation was not removed when clearing the Purchase Contract Line No. value on the expense. | 47828 |
| Purchase Contracts | Previously, when submitting an expense with the purchase contract, which matches all the conditions for auto-approval, the expense was not released. Now, the expense is successfully released based on the purchase contract. | 50436 |
| Purchase Contracts | Previously, the 'Purchase Contract Missing' comment was not added for the expense with allocations, when one of the allocations has the Expense Type with the Purchase Contract set as Mandatory. | 51464 |
Expense Management 2023 R2, hotfix 2
Release date: November 17, 2023
App version: 12.0.2
FOB version: 12.00.02
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Mileages | When synchronizing with Continia Online, a mileage recalculation is automatically triggered in all the companies for all the mileage rates available in the company and for all the mileages with status not posted. Because of the calculation on each mileage rate, the same mileage was recalculated multiple times, and this was causing performance issues. | 41445 |
Expense Management 2023 R2, hotfix 1
Release date: November 8, 2023
App version: 12.0.1
FOB version: 12.00.01
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Credit Card Transactions | In rare circumstances, as when multiple synchronizations were running at the same time from different sessions, it would create two similar Bank Transaction entries with the same Transaction ID. | 50244 |
| General Application | Editing is re-enabled for the field "Status" of the following records (if other conditions are met). These were made non-editable unintentionally in version 12.0.0
| 50636 |
| Mileages | When posting a mileage on a purchase invoice, the posting would fail if the "Mileage Tax" or "Mileage Fuel" account code was longer than 10 symbols. | 50641 |
Expense Management 2023 R2
Release date: October 2, 2023
App version: 12.0.0
FOB version: 12.00
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Expenses | The expense user has the ability to edit the VAT Amount. This VAT Amount is utilized during the posting process and is incorporated into VAT differences when the General Ledger Setup includes this feature. In the Expense Portal and Mobile App, this functionality is enhanced by the inclusion of Optical Character Recognition (OCR) technology for reading the VAT Amount. Additionally, whenever feasible, the Expense Portal and Mobile App functions automatically allocate expenses based on various VAT percentages. You must configure the "VAT AMOUNT" field to take advantage of this functionality. Within the Expense Management CA app, similar functionality is available, replacing the automatic allocation of expenses based on Tax Areas. As sales tax amounts are now present, there is no longer a need for automatic expense allocation. This eliminates the requirement for specific expense types such as GST/HST and streamlines the process of posting to GL Accounts using General Journal posting. It also eliminates synchronization delays and resolves the limitation associated with "Expense/Capitalize. | 46817 |
| Expenses | When using the configuration file, new Expense Types, special Field Types with lookup functionality for airports and harbors based on Google Maps, as well as functionality for recording data related to carbon footprint calculations, have been added. When you set up Expense Management in a new system, the configuration package will include multiple Expense Types that can be used for recording carbon footprints. Additionally, Configured Fields and Field Dependencies have been adapted to make it easy to get started recording carbon footprint-related data. | 48377 |
| Expenses | Field dependencies are imported and exported with the assisted setup wizard. | 49110 |
| General Application | The field "Submit Date/Time" is added to all documents. The field is hidden by default and can be set to show by adding it through Personalized. | 39602 |
| General Application | Introducing the new CEM Image Quality (6086520) page, which offers users the ability to customize image size and quality settings. This feature provides the ability to override default values for Picture Size and Picture Quality, providing greater control. | 45546 |
| General Application | Fields "Matching tolerance Amount (%)" and "Matching tolerance Date (Days)" will be used in the future in our Expense Management Mobile App, when matching Expense with an existing receipt. | 45650 |
| General Application | The attachment images are automatically zoomed in to the "best-fit" size for the admin to avoid spending time adjusting zoom for every attachment. | 46689 |
| General Application | Support for multiple levels of parent-child field relations, similar to Project and Project Tasks. | 47388 |
| General Application | The Configurable Messages module is added, which allows control over the validation comments. In this module comments can be configured to have the type Information, Warning or Error. | 47591 |
| General Application | The "General Journals" action is removed from the Expense Management Role Center, as legacy views will no longer be supported in Business Central. | 48101 |
| General Application | Capabilities for autofill on the field types is added. Field values can be suggested in the Expense Portal and Expense Mobile App based on the previously used values. The autofill functionality is controlled from the field types available only for Code and Option data types. The functionality is enabled by default but can be disabled for each individual Field Type. | 48617 |
| General Application | The Secure Archive in Expense Management preserves original digital documents for bookkeeping, safeguarding them from tampering or deletion. These documents remain traceable within legally defined secure periods. The built-in log function tracks document processes from receipt to bookkeeping. To use the log function independently, you can enable it without Secure Archive's restrictions. | 48680 |
| General Application | The document logging functionality is included to enable in Expense Management Setup. Enabling this feature will record the following changes:
| 49168 |
| General Application | Files imported in Expense Management will get a Hash (SHA1). When Secure Archive is enabled the Hashing will help to determine if files related to a given historic posting are identical to the time of posting. The Hash value is calculated when one of the following events occurs:
| 49226 |
| General Application | Files imported through Expense Management will be undergo conversion into a digitally signed PDF when Secure Archive is enabled. Additionally the original file will be retained. The file signature occur under the following circumstances:
| 49227 |
| General Application | By enabling the Secure Archive functionality, you can establish a timeframe during which the posted purchase invoices and posted purchase credit memos are protected from deletion. | 49229 |
| General Application | An action to Continia Hub has been added to the home tab for the following pages:
| 49491 |
| Purchase Contracts | Purchase Contracts cues is added to the Expense Management Rolecenter. The cues will show when the Purchase Contract application area is enabled. This can be enabled in the Expense Management Setup. | 44331 |
| Purchase Contracts | When the user changes Continia User Id on an expense, which has a relation to a purchase contract, the following comment will be added for the expense:
| 45018 |
| Purchase Contracts | Actions to the Expenses and Posted Expenses pages is added: Open Purchase Contract and Create Purchase Contract. Additionally, introduced new fields to the Expenses and Posted Expenses pages: Purchase Contract, Purchase Contract No., Purchase Contract Line No., and Purchase Contract Line Amount. | 46412 |
| Purchase Contracts | A new field, Enable Purchase Contracts, has been added to the Expense Management Setup, and is used to disable or enable Purchase Contracts functionality. | 47339 |
| Purchase Contracts | When a new expense is linked to a purchase contract line that already has an association with a posted or open expense, a validation process is initiated to ensure that these expenses do not fall within the invoicing period specified by the related purchase contract. The following comments are appended based on the circumstances: If the purchase contract line is linked to an open expense within the current invoicing period of the purchase contract:
| 47347 |
| Document Approval | A new option field, Send Email To, replacing the field Forward Emails, has been implemented on the Approval Sharing (EM) page. The following options are available:
| 48773 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Expenses | The "Vendor No." on expenses is used to represent the business from where the purchase was made. When a "Vendor No." is added to an expense similar to the "Vendor No." set on Continia User Setup, an error will be raised. | 32586 |
| Expenses | After a transaction is matched to an expense, which is completed by the expense user, the expense is sent back to the expense user unintentionally. | 49381 |
| Expenses | When downloading expenses with allocations from Continia Online, the "TAX GROUP CODE" value was removed when the field was not configured. | 49546 |
| General Application | When posting an expense on an Employee, with posting groups specified, the following error would appear. Gen. Posting Type must be equal to ' ' in Gen. Journal Line: Journal Template Name=, Journal Batch Name=, Line No.=0. Current value is 'Purchase'. | 49922 |
| Mileages | Posting negative mileage is supported when using Purchase Invoice. | 49849 |
| Purchase Contracts | In the past, when linking an expense to a purchase contract, no consideration was given to the Contract End Date and Start Date. However, there have been updates: Now, if the Expense Document Date precedes the Purchase Contract's Start Date, the system will generate the following error message: This expense is associated with a purchase contract, and therefore, the Document Date must occur after the purchase contract's start date. Conversely, if the Expense Document Date falls after the Purchase Contract's End Date, the following error will be displayed: This expense is linked to a purchase contract, and as such, the Document Date must precede the purchase contract's end date. Moreover, if the Expense Document Date is earlier than the Purchase Contract Line's Start Date, the system will provide the following error: This expense is associated with a purchase contract line, and consequently, the Document Date must precede the purchase contract line's start date. | 47338 |