Detailed changelog for Continia Expense Management 2026 R2

You can now record the eDocument ID (NSeI Document No. in the Polish localization) and a new Missing NSeI No. Reason on expenses to support Polish KSeF reporting requirements. You can enable both fields for expenses through Configured Field Types in Business Central and in the Expense Portal/App.
During posting, the field values are transferred to the corresponding IT.integro Polish Localization fields, allowing them to propagate to the resulting ledger entries.

The following event publisher was added to Codeunit 6086330 "CEM Expense-Post". It provides an opportunity to modify filters set when determining whether to use an existing or create a new Purchase Invoice document during Expense posting:

• OnFindExistingPurchaseHeaderOnBeforeFindFirst().

A new event publisher was added to the Canadian localization app to allow modifications to Sales Tax lines before posting:

• OnBeforePostGLAccLine().

A dedicated Expense Setup page was added, bringing a consistent setup experience for Expense, Expense Report, Mileage, and Per Diem. You can open Expense Setup from the Modules list on the Expense Management Setup page (it is also available through Tell Me.)
When field setup cannot synchronize with Continia Online, closing a setup page now displays the issue as a message instead of preventing the page from closing.

You can now set up expense types with suggested G/L account mappings, instead of having to map them by hand.
From the Expense Types page, the new Set Up Expense Types dialog lists the expense types to be created and proposes a G/L account for each one. You can review and adjust each suggestion before anything is created, then choose Keep it to create the expense types and apply the accounts to the posting setup, or Discard it to close without changes.
Two suggestion methods are available. Continia AI compares your chart of accounts with the expense types and requires consent before any data is sent to the Continia AI service; you can review consent and change it in the dialog at any time. Name Matching works entirely inside Business Central without sending data anywhere, matching expense types to accounts by keyword. If AI consent was not granted, accounts are matched by name instead, and expense types with no confident match are left blank for you to complete.

Support for eInvoicing was added to Expense Management via integration with Continia Document Capture. You can now link expenses to eDocuments processed in Document Capture, allowing posting to be handled as a single accounting event and preventing duplicate purchase postings.
On the expense, the existing Applied Purch. Doc. No. field identifies the linked Document Capture document. When this field is populated, only the payment or refund side of the expense is posted, while the purchase posting is handled by the linked document. On the Document Capture side, a new Expense Entry No. field links back to the related expense.
Duplicate detection between Expense Management and Document Capture was also added. When an eDocument identifier is configured, the system scans Document Capture documents for matches based on document date, amount, and currency. If a likely match is found, configurable messages notify the bookkeeper about a possible matching document or warn that an expected eDocument has not yet been linked.
New eDocument Expected and Expense Expected flags make it possible to require pairing between expenses and eDocuments before posting. You can configure these settings in Payment Types, Document Capture Templates, or individual Document Capture Documents, allowing enforcement at both setup and document level.
A new Correct eDocument Dimensions setting was also added to Expense Management Setup. When enabled, dimensions from the expense transfer to linked Document Capture Document G/L entries after posting, using the Dimension Correction module. Correction history is tracked and you can view it using History of Dimension Corrections.

Default reimbursement settings were moved directly to the Continia User Setup and Expense User Group pages. You can now maintain the default vehicle, per diem group, and reimbursement methods for expenses, mileage, and per diems at the user or group level without using a separate Default User Setup page.
Existing defaults are migrated automatically when upgrading. Configuration files exported from earlier versions using the Continia Configuration wizard no longer transfer these settings.

Attachments from expenses and mileages are now shown directly on the posted entries and purchase documents they were posted to, so you can review a receipt without opening the original expense document. The attachment factbox appears on:

• G/L Entries
• Vendor Ledger Entries and Employee Ledger Entries
• Project Ledger Entries

You can now apply filters to DateTime fields and use advanced filter types, including ranges, when limiting the lookup values available in Configured Fields. This provides a more focused selection when choosing values from large lookup lists.
You can also review existing filters and refine them, to further limit the values shown to users.

The Mileage card and list were aligned with the other Expense Management document types:

• The document title on the Mileage card now shows only the entry number and user name, without the vehicle code and description.
• The approval action is now called Send for Approval on both the card and the list, where the card and list previously used different wording.
• The Approvals action is no longer promoted in the action bar on the Mileage card and is now found under Related > Mileage, matching the Mileage list.
• A Cancel Approval Request action was added to the Mileage list, mirroring the card.
• The user Name and No. columns are now shown in the Mileage list.
• The Attendees field on the Mileage card is now shown only when attendees are configured for mileage.

You can now calculate per diems with an explicit time zone, so the amount is the same no matter who opens or posts the document. Each per diem stores the time zone in which its times were captured, and the calculation uses that time zone to determine day boundaries. Departure and return times always show in the time zone where they were entered, rather than being converted to the time zone of the user viewing the document. This makes per diem amounts consistent for companies whose users, approvers, and travellers work across several time zones.
Turn the feature on with Enable time zone handling in Per Diem Setup when Enable Per Diem Destinations is active.
When the feature is enabled, the time zone is taken from the new Time Zone field on the departure country in Countries/Regions. It can be changed per document in Departure Time Zone and Return Time Zone on the Per Diem card, and in Arrival Time Zone on each destination, for trips that return to or pass through another country. If a time zone is missing, a validation comment on the per diem states that the amount may be calculated incorrectly.

Meal deduction handling for taxable Per Diem amounts was updated to better align with local tax practices. For German and Danish companies, the full taxable Per Diem is now paid without meal deductions after the 3-month rule or 12-month rule is triggered.
A new setup option was added to control whether meal deductions reduce taxable rates in the standard Per Diem calculation.

The Per Diem card and list were aligned with the other Expense Management document types:

• The document title on the Per Diem card now shows only the entry number and user name, without the per diem group code and description.
• The approval action is now called Send for Approval on both the card and the list, where the card previously used Send Approval Request.
• The Approvals action is no longer promoted in the action bar on the Per Diem card. You can now find it under Related > Per Diem, which matches the Per Diems list.
• A Cancel Approval Request action was added to the Per Diems list, mirroring the card.
• The column order in the Per Diems list was changed, so the user, travel dates, description, and status columns come first, followed by the amounts.

When entering a value in a Decimal field on the Extra Fields page with the Business Central language set to Spanish, the following error occurred:

• Se ha especificado un campo o atributo no válido para la propiedad Format. <Precisión,2:2><Formato Estándar,9>_.

The issue could also occur when using French or Swedish.