Detailed Changelog for Continia Expense Management 2023 R2

• Receive: Logs the incoming documents (expenses, mileages, per diems, expense reports, creditcard transactions). The log entries are inserted as soon as records are downloaded from Continia Online or inserted.
• Adding/removing attachments: Logs when document attachments are added or removed on the expenses and mileage.
• Discard duplicated transactions at import: Adds a log entry if a transaction is discarded due to having a duplicated ID.
• Deleted: Adds a log entry when a document is deleted.
• Split: Adds a log entry when an expense allocation is creating a new expense.
• Merge: Adds a log entry when one or more expenses are merged into one.
• Matched/Unmatched: Adds logs when expenses and transactions are matched and unmatched
• Add/Remove to Expense Report: Adds logs when documents are added or removed to an Expense Report.
• Approved: Adds a log entry when a document is approved.
• Posted: Adds a log when documents are posted. Expense Management can post directly on a Ledger Entry, case in which the "Document No." and the "Ledger Entry No." is specified. In other situations, Expense Management can generate purchase invoices and credit memos based on setup.
• Posted Invoice or Credit Memo updates: When Expense Management generates a purchase invoice or a credit memo, important changes on these documents are logged.

• Attachment download by synchronization with Continia Online
• Attachment added manually in Business Central
• Attachment modified using Split and Merge.

• When the user uploads the file using the Expense Mobile App, provided that "Enable Document Signing" has been synchronized with Continia Online.
• When the file is uploaded from within Business Central and "Enable Document Signing" is explicitly enabled. 

• Expense Management Setup
• Continia User Setup
• Continia User Setup Card
• Default User Setup
• Expense Types
  
• Company Policies
  
• Payment Type List
  
• Configured Field Types
  
• Mileage Rates
  
• Mileage Reimbursement
  
• Per Diem Rates
  
• Per Diem Reimbursement
  
• Bank Mapping Rules
  

• The purchase contract relation has been removed, as the new value in Continia User ID does not match with the Continia User ID on the purchase contract.

• An open expense already exists within the current invoicing period of the purchase contract. (entry number <Expense Entry Number>)

• A posted expense already exists within the current invoicing period of the purchase contract. (entry number <Expense Entry Number>)

• Multiple expenses already exist within the current invoicing period of the purchase contract. (entry numbers: <Expense Entry Numbers>)

• Only Original Approver
• Only Shared Approver
• Both Approvers

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.