Detailed changelog for Continia Document Capture 2026 R1 incl. CDN
This article lists all new updates, features, service packs, and hotfixes for Continia Document Capture 2025 R2 and Continia Delivery Network (CDN).
When new versions of both apps are released together, the release notes for the CDN are listed along the release notes for that Document Capture release. When a new version of the CDN is released separately, its release notes are listed by themselves – and you must update the CDN app discretely.
| Solution | Current version |
|---|---|
| Document Capture | 28.0 |
| Continia Delivery Network | 27.3.4 |
Tip
As a Continia partner, you can be notified of new Document Capture versions and service packs when they're released. To sign up for this service, go to Receive a notification upon new Document Capture releases in the Continia PartnerZone (only available to partners).
Important
Document Capture 2025 R2 supports the following version of Microsoft Dynamics 365 Business Central: Business Central 2025 R2 (v27).
Document Capture 2026 R1
Pre-release date, online: March 20, 2026
Release date, online: April 1, 2026
Release date, on-premises: April 1, 2026
Document Capture version: 28.0.0
Continia Delivery Network version: 27.3.4
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | The following only applies to the Swiss (CH) localization. When recognizing documents, search texts now always take precedence over other identification methods. Previously, vendor (and template) identification through the IBAN from the QR code would bypass the search text identification step. | 68861 |
| Country and Regional | The following only applies to the United States (US) and Canadian (CA) localizations. When importing documents in Document Capture, there can sometimes be a difference between the sales tax amounts imported from the vendor document and the amounts calculated in Business Central. To prevent the need for manual handling of such differences, a new setting – Allow automatic update of tax amount – has been added to the General Ledger Setup page. This setting enables the automatic adjustment of tax amounts when registering purchase documents. When Allow automatic update of tax amount is enabled, the assigned tax amount is automatically adjusted to match the imported tax amount – provided that the difference between Assigned Amount Incl. Tax and Imported Amount Incl. Tax on the purchase document is within the Maximum Allowed Difference Incl. Tax defined in general ledger setup, together with Allow Tax Difference in the Purchases & Payables Setup page. The tax difference amount is distributed across all tax lines in the document’s statistics page, but only for document lines that contain tax. Users can still make manual adjustments if needed. When both Max. Tax Difference Allowed and Maximum Allowed Difference Incl. Tax in the general ledger setup are defined, the lower value of the two is used as the maximum allowed difference. This setting is enabled by default for new installations of Document Capture. For existing users upgrading to this version, the setting is disabled by default but can be enabled manually if this behavior is desired. For more information, see Automatic amount validation. | 70531 |
| Documents and Templates | It is now possible to create document lines of type Comment when recognizing invoice lines. This allows descriptive information – such as notes or text-only lines – to be captured and transferred during registration. Comment lines can be created from recognized or manually entered descriptions, and, when applicable, Business Central standard text codes can be applied as line description translations. For more information, see Capturing line fields in a document. | 46265 |
| Documents and Templates | The Discount % line template field was missing in the purchase OIOUBL master template. | 53753 |
| Documents and Templates | When the recognized bank account number in the Vendor Bank Account header template field contained leading zeros, validation could fail due to mismatched account number formatting. | 60349 |
| Documents and Templates | The option field Amount Validation has been added to the sales master template. | 65548 |
| Documents and Templates | When dimensions in Business Central are renamed, any related header or line fields in Document Capture templates are now renamed accordingly. | 68709 |
| Documents and Templates | Previously, when updating a purchase order in the Purchase Order category, template line fields configured with a destination field in the Transfer Value to... section on the General FastTab had no effect. These template field settings are now supported during order updates, allowing values to be transferred to the corresponding purchase order. | 69798 |
| Documents and Templates | To support standard Business Central functionality, the Allow automatic update of VAT amount setting in the General Ledger Setup now requires the Allow VAT Difference setting to be enabled on the Purchases & Payables Setup page. When both Max. VAT Difference Allowed and Maximum Allowed Difference Incl. VAT in the General Ledger Setup are defined, the lower value of the two is used as the maximum allowed difference. The VAT difference amount is distributed across all VAT lines in the document’s statistics page, but only for document lines that contain VAT. Users can still make manual adjustments in the statistics page if needed. For more information, see Automatic amount validation. | 70046 |
| Documents and Templates | Previously, duplicate invoice checks were only performed against registered or posted invoices. Duplicate detection now also includes documents in the document journal. A configurable comment is displayed when another open document with the same vendor and invoice number exists, and multiple comments are shown if duplicates are found across different stages. | 71251 |
| Documents and Templates | The document import functionality has been improved to ensure that processing continues even if one or more documents encounter errors during recognition or processing. Files must be in a valid format (i.e.: PDF or XML) to be processed. Files with an invalid structure are skipped, while all valid files continue to be imported and processed. An error is logged to identify the affected documents, and manual intervention is required. | 71357 |
| Documents and Templates | The following only applies to the Australian (AU), Belgian (BE), German (DE), New Zealand (NZ), and Worldwide (W1) localizations. Previously, values in business ID fields (i.e.: VAT Reg. No., ABN No., Enterprise No., and Registration No.) were only generated and maintained for vendors. With this release, the same logic now applies to customers, ensuring consistent identification of the document source across both master data types. | 74908 |
| Document Approval | Previously, when opening a document from an approval entry (e.g.: the Purchase Approval Entries page), it was possible to navigate to the next or previous documents based on the current approver’s filter. Now, opening a document from an approval entry only opens that specific document. Navigation to other documents is no longer available. This change was introduced to optimize performance when accessing documents through approval entries. | 68941 |
| Document Approval | Previously, when exporting users and no email account was configured, the error message provided no direct guidance. The error message has now been improved to include a Set up Email action, allowing direct access to the Email Accounts page to configure the required email account. | 72341 |
| Document Approval | The Approvals Permissions and Approval User Groups actions were unintentionally removed from the User Setup by Company page, and have now been restored. | 72857 |
| General Application | The Document Capture group on the Explore More Roles page has been extended to include further relevant links. | 60196 |
| General Application | A Don’t show this again action has been added to the imported documents notification, allowing users to permanently dismiss it during future imports. | 62030 |
| General Application | The CDC Basic permission set is no longer added during Document Capture configuration for users whose permissions are managed by security groups. | 72717 |
| General Application | When exporting documents and attachments, files are now organized into structured folders. Each vendor has a dedicated folder containing the original document and its related attachments. Within each folder, documents are grouped into subfolders based on their status (for example, unregistered, registered, or posted), making it easier to locate and manage exported files. For more information, see Exporting attachments. | 74359 |
| Platform and Technology | The shared access signature (SAS) and Microsoft Entra ID authentication types have been added as configuration options to the Azure Blob Storage document storage type on the Document Capture Setup page. For more information, see Setting up Azure Blob Storage. | 43474 |
| Platform and Technology | To enhance security, the following table fields have been moved to isolated storage to prevent direct access from outside the application:
| 59370 |
| Platform and Technology | Support for custom URLs (private endpoints) has been added as a configuration option to the Azure Blob Storage document storage type on the Document Capture Setup page. For more information, see Setting up Azure Blob Storage. | 59380 |
| Platform and Technology | Microsoft Graph is now supported as an email protocol option when using on-premises OCR. For more information, see Setting up email protocols and Creating and configuring email addresses for document import. | 69644 |
| Purchase Documents | The Description field on the Standard Amount Distribution Code Card page has been extended to support up to 100 characters. | 68830 |
| Purchase Documents | Digital voucher handling introduced in Document Capture 12.2 ensures that, when Enforced Digital Vouchers is enabled, a digital voucher is automatically created when registering a purchase document or journal entry. This functionality has now been extended to prepayments. When registering a prepayment in Document Capture, the attached PDF and any drag-and-drop attachments are automatically transferred to the digital voucher before posting. This ensures compliance with digital voucher validation and prevents errors caused by missing attachments. | 69928 |
| Purchase Documents | When registering purchase documents where a standard amount distribution code is applied, blank description values on the distribution code now default to the captured description from the document lines. | 73024 |
Bug fixes
All relevant bug fixes released in service packs and hotfixes up to Service Pack 3, hotfix 1 for Document Capture 2026 R2 (27.00) are also included in Document Capture 2026 R1 (28.00). The description of these bug fixes is not repeated on this page.
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | When using a Peppol or other XML-based template, it was not possible to use the Match Vendor Order No. and Match Vendor Shipment No. matching settings on the Template Card. This improvement only applies to newly created templates. | 65874 |
| Documents and Templates | On the Template Field Card, the settings Change Sign and Make Absolute Number are now interdependent. Enabling Make Absolute Number automatically disables Change Sign, and attempting to enable Change Sign fails if Make Absolute Number is already enabled. | 66019 |
| Documents and Templates | The validation of accounts for the header amount fields has been updated. The check now depends on whether line recognition is enabled. If line recognition is enabled, validation is only performed when Transfer Amount to Document is set to Always. If line recognition is disabled, validation is performed when Transfer Amount to Document is set to Always or If lines are not recognized. | 68426 |
| Documents and Templates | When using brackets in the Translation From field in line translations, the following error message was shown during field recognition:
| 69042 |
| Documents and Templates | When a template field in a formula referenced the DOCTYPE template field, the value remained empty. Also when manually updating a field, the change did not carry through to other fields where the current field was part of the formula. | 69054 |
| Documents and Templates | The G/L Account Field Code field on the Template Field Card is now automatically hidden when the field Transfer Amount to Document is set to empty. In addition to hiding the G/L Account Field Code field, its value is also cleared. | 69659 |
| Documents and Templates | Previously, using the Create Vendor action while processing a document in the Purchase Order category could trigger the following error message:
| 70251 |
| Documents and Templates | Previously, documents were not correctly split because the identification template only applied the first matching caption (e.g.: VAT Reg. No. or VAT Registration No.) across all pages. The recognition process now evaluates all configured captions per page, ensuring that documents are correctly split when different VAT registration numbers are identified. | 70587 |
| Documents and Templates | Using the New action on the Document Categories page now opens the Document Category card, allowing entry of all required information instead of creating a line directly in the list. This change prevents issues where not all fields were visible due to missing prerequisites when creating a document category from the list. | 70853 |
| Document Approval | When registering a credit note matched to a purchase return order or posted return shipment, the Line Amount (Order) was incorrectly displayed as zero in the Purchase Approval Entries. | 66588 |
| Document Approval | Shared approval entries listed on the Purchase Approval Entries page are now correctly sorted. | 69079 |
| Document Approval | When extensions added custom values to the Deferral Calculation Start Date enum, and such a value was used in a deferral template (with Deferral Code enabled in Document Capture Setup/Continia Web Approval), opening a document in the Web Approval Portal could result in the following error:
| 70474 |
| Document Approval | When the setting Can Edit Posting Lines was enabled in Continia User Setup, the No. field in purchase invoice lines of type fixed asset could not be changed while the document was pending approval. | 75818 |
| General Application | Email data is now correctly removed when the storage type is changed. Previously, if an email contained more than one document, the removal was not performed. | 59956 |
| General Application | Previously, when using the Export Attachments functionality with the Export Related Documents option enabled, only captured purchase invoices were exported – while other associated attachments were not included. | 72801 |
| General Application | Previously, after applying a filter in the document journal and refreshing the page (F5) or performing a hard refresh (Ctrl + F5), the Document Category title and the Vendor and Name columns could disappear. These elements are now correctly restored after reloading the page. | 73066 |
| General Application | The following only applies to the Swiss (CH) localization. When registering a Swiss QR-bill for a vendor with multiple existing vendor bank accounts, a duplicate bank account code could be generated – resulting in the following error message:
| 73145 |
| Order and Receipt Matching | Previously, when using the Get Order Lines... action on the purchase invoice page a second time on the same line, the following error message appeared when posting the invoice:
| 68151 |
| Order and Receipt Matching | When importing multiple multi-page receipts for the same purchase order into the Purchase Order category, the document viewer did not behave correctly. Selecting a document and navigating to the previous, next, first, or last pages could cause the viewer to jump to a page from a different document instead of continuing within the selected document. | 72383 |
| Purchase Contracts | The Open Purchase Contract action is now available on invoices created from a purchase contract. | 69135 |
| Purchase Documents | When the posting date of a purchase order was outside the Allowed Posting From and Allowed Posting To period defined in General Ledger Setup, it was not possible to post a purchase invoice matched to the purchase order using batch posting. Manual posting was not affected by this restriction. | 70208 |
| Purchase Documents | When using the Get Order Lines action multiple times on a purchase invoice, quantities are now handled correctly when purchase order lines are imported repeatedly and adjusted manually. Previously, this could result in incorrect updates to the Quantity Invoiced field on the purchase order lines. | 72361 |
| Purchase Documents | Previously, registering a Swiss QR-bill could trigger the following error due to the purchase header being retrieved again during QR data transfer:
| 73796 |
| Purchase Documents | Improved the visibility of drag-and-drop attachments on credit memos, including the correct display of the number of attachments on the document card. | 74163 |