Detailed changelog for Continia Document Capture 2026 R2 incl. CDN
This article lists all new updates, features, service packs, and hotfixes for Continia Document Capture 2026 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 | 29.0 |
| Continia Delivery Network | 29.0 |
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)./h2
Important
Document Capture 2026 R2 supports the following version of Microsoft Dynamics 365 Business Central: Business Central 2026 R2 (v29).
Document Capture 2026 R2
Pre-release date, online: September 17, 2026
Release date, online: October 1, 2026
Release date, on-premises: TBD
Document Capture version: 29.0.0
Continia Delivery Network version: 29.0.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | On the Ready to Import page, the Email Received field has been renamed to Email Received UTC. New Email Received and OCR Processed fields have been added to display the email receipt time and OCR processing time in the user's local timezone. | 73864 |
| Documents and Templates | A new field, Process Document Type, has been added to the Document Category Card. This field controls how PDF and XML files are handled during import when both file types are attached to the same email. Depending on the selected option, either one or both file types are processed, while unprocessed file types are added as attachments. For more information, see Working with paper and PDF documents. | 53232 |
| Documents and Templates | A Document Status Code column has been added to the Message Center Setup page, enabling automatic assignment of document status codes based on predefined comments. | 54383 |
| Documents and Templates | The message shown when changing the value in the header field No. in the document journal has been updated for clarity. It now guides you to review potential changes in Accounts for Amounts, as values such as VAT posting groups and posting descriptions could be overwritten. | 57954 |
| Documents and Templates | Several labels and actions related to the custom columns functionality have been updated to align with standard Business Central naming:
| 58099 |
| Documents and Templates | Previously, when using AI line recognition, template line fields that had been manually recognized could only be reset to AI-only recognition by recreating the template. It is now possible to reset a line field to AI recognition by selecting the field and then left-clicking an empty area in the Document Viewer, allowing the AI engine to recognize the field again. | 63855 |
| Documents and Templates | Previously, changing the Notification Email Address on a document category did not trigger an automatic export of the OCR configuration files. The OCR configuration is now automatically exported when this field value is updated. | 65287 |
| Documents and Templates | Item tracking capture has been enhanced to make it easier to process documents containing multiple item tracking values. Multiple values can now be captured for each item line, allowing all relevant item tracking information to be captured directly from the document. | 69972 |
| Documents and Templates | Previously, blocked dimension values were included when looking up dimensions in Accounts for Amounts. Blocked values are now excluded from the list. | 72173 |
| Documents and Templates | Duplicate invoice validation has been improved to provide a complete overview of potential duplicates. Previously, when duplicates existed across unregistered, registered, and posted documents, not all relevant warning comments were displayed. All applicable duplicate warnings are now shown together, making it easier to identify and assess every potential duplicate before proceeding. | 75558 |
| Documents and Templates | Vendor VAT number and vendor bank account number validation comments can now be configured as errors, warnings, or information, providing greater flexibility in how mismatches are handled. This allows documents to be registered when a mismatch is acceptable for the specific business scenario. | 78551 |
| Document Approval | On the Approval Sharing - Document Capture (DC) page, the Both Users option in the Send Email To field was previously blocked and could not be selected. The option is now fully supported, allowing both the original approver and the substitute to receive notifications when the Send Status Email to Approvers function is used. | 54693 |
| General Application | Integrating Sustainability with Document Capture has been simplified through a new guide available in Assisted Setup. Completing the guide automatically adds the required sustainability fields to all purchase document master templates. | 69401 |
| General Application | When entering text in the document header No. or Bal. Account No. fields, the matching account is now automatically identified based on its name or search name, and the correct number is filled out. For the No. field, this is supported for G/L Account, Item, Resource, Fixed Asset, and Item Charge. For the Bal. Account No. field, this is supported for G/L Account and Bank Account. | 69567 |
| Order & Receipt Matching | Previously, when using the Create Line on Purchase Document action on the Match Lines page, only one order line could be created at a time. It is now possible to select multiple captured lines and create corresponding purchase order or return order lines in a single action. | 58617 |
| Order & Receipt Matching | When a partial receipt is received against a purchase order – and the auto-match configuration (e.g.: matching on order number, item number, and quantity) can not find a match for lines with differing quantities – it's now possible to manually set the Matched Quantity on the Order Lines section in the Order Matching. | 69212 |
| Order & Receipt Matching | Standard Business Central order matching actions introduced in BC 28.0 are hidden when using Document Capture. | 76809 |
| Order & Receipt Matching | It is now possible to enable a new purchase order and receipt matching engine that significantly improves the performance of three-way matching for purchase invoices and credit memos. The improvements apply to both header-level and line-level matching and are particularly beneficial in environments with large numbers of open purchase orders and receipts. | 78406 |
| Platform and Technology | When a GP-to-Business-Central cloud migration was performed in environments with Continia apps installed, the migration could fail in some cases. This occurred because Continia added entries to the Migration Table Mapping table without first verifying whether the migration was a GP-to-Business Central or a Business-Central-to-Business-Central migration. Now, Continia checks the product ID before adding custom table mappings – ensuring that GP-to-Business-Central migrations complete successfully. | 79154 |
| Purchase Contracts | A new field, Approval Date Adjustment, has been added to the Purchase Contract Card to define a lead-time period (a.k.a. offset) for contract approvals. | 57000 |
| Purchase Contracts | A Create Purchase Contract action has been added to the Purchase Contracts page, providing the same guided experience for creating purchase contracts as from the document journal. | 68051 |
| Purchase Contracts | When a document is matched to an unapproved purchase contract and Purchase Contract Approval is enabled, a configurable warning comment is now shown if the document is expected to be approved automatically based on the configured template's and contract's approval settings. The warning informs you that the purchase contract must be approved before the document is registered for the resulting purchase document to be approved automatically. | 69916 |
| Purchase Documents | When importing ZUGFeRD or other XML-based documents containing embedded files, the embedded files are now imported as well. | 70625 |
| Purchase Documents | When registering purchase documents where a Standard Amount Distribution Code is applied, blank values on the Standard Amount Distribution Code line now default to the captured value from the document. | 81294 |
| Purchase Documents | Document Capture now uses AI to suggest a G/L account, item, item charge, resource, or fixed asset for each unrecognized document line – significantly reducing the manual work required to code purchase invoices. For every suggestion, the AI provides a confidence level and a plain-language explanation of why the value was suggested, giving you the information needed to review and confirm the AI recommendation before it is applied to the document. | 81301 |
| Country and Regional | The scenario framework can now be used with custom document tables. Previously, the eDocument Scenario Flow field was only populated and transferred to posted documents for standard Business Central sales, purchase, and service documents. When the field was added to a custom document table, the scenario flow was not transferred to the posted document. A new public codeunit, CTS-CDNSF Scenario (6252612), has been added to the scenario framework, enabling extensions to:
The Scenario Flow and Record Coding Value tables, as well as their related enums, are also available to extensions. Standard Business Central sales, purchase, and service documents continue to work as before. | 82082 |
| eDocuments | Previously, only a predefined set of XML formats could be imported into Continia Inbound eDocuments through third-party integrations. This restriction has been removed, allowing partners to develop custom integrations that import other XML formats directly into Continia Inbound eDocuments. | 80998 |
| eDocuments | The app name and related texts in the Customer Onboarding app and Continia Delivery Network have been updated from Continia KYC to Continia Customer Onboarding. References to KYC as an industry term, as well as its use in AL object prefixes and telemetry identifiers, remain unchanged. | 81655 |
Bug fixes
All relevant bug fixes released in service packs and hotfixes up to ????? for Document Capture 2026 R1 (28.00) are also included in Document Capture 2026 R2 (29.00). The description of these bug fixes is not repeated on this page.
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | Previously, the Capture Only Match setting on field rules was not enforced when values were captured via AI recognition or key-value pair matching on PDF invoices. If a field rule was configured to capture only values matching a specific pattern (e.g.: a project number format), the rule could be ignored – resulting in incorrect or unfiltered values being stored. The rule is now applied consistently across all capture methods, ensuring that only matching values are captured. | 71811 |
| Documents and Templates | Previously, when using the Create Vendor or Create Customer actions in the document journal, clicking the Open PDF action opened the document preview in a reduced size – making the content difficult to read. | 72285 |
| Documents and Templates | Previously, XML identification templates could incorrectly prevent the creation or copying of PDF identification templates within the same document category. PDF and XML identification templates are now validated independently, allowing both types to be created and copied within the same document category. | 73231 |
| Documents and Templates | Previously, copying a template marked as default could result in multiple default templates for the same source. Copied templates are no longer set as default. | 74618 |
| Documents and Templates | Previously, the Capture Only Match setting on field rules was not enforced when processing XML documents. As a result, fields could be populated even when the captured value did not match the rule’s pattern (e.g.: a 6-digit order number). | 75110 |
| Documents and Templates | Previously, changing the Filter Type to Document Field in a look-up field's Source Table Filters could, in some cases, result in an incorrect validation error before the Filter value was populated. | 78053 |
| Documents and Templates | Previously, in rare cases where the AI-based OCR did not detect any invoice lines, the Recognize Lines field on the Document Card was not shown – even if lines were subsequently recognized manually. The field is now displayed when manually recognized invoice lines are present. | 79560 |
| Documents and Templates | Previously, when changing the When Value is Empty option on a template field, the confirmation dialog could incorrectly indicate the opposite of what would happen to the formula. The confirmation dialog now correctly indicates whether the formula will be cleared. | 81190 |
| Document Approval | When using approval flows configured with All to First Qualified, documents could previously be approved and released beyond assigned approval limits under certain forwarding conditions. | 72345 |
| Document Approval | Previously, purchase invoices matched to receipts or return shipments could, in some cases, be auto-approved even if the related purchase order was still pending approval. The status of the related purchase order is now validated before the invoice is auto-approved. | 74504 |
| Document Approval | When opening the Purchase Approval Request Entries page from Approval Entries by Approver, refreshing the page in the web browser (Ctrl + R or F5) removed all system-applied filters, causing all approval entries to be displayed regardless of the approver. | 75366 |
| General Application | Previously, sending an email with more than 200 characters in the subject line could result in the following error message during document import:
The subject line is now automatically truncated to 200 characters, ensuring successful import. | 76845 |
| General Application | Previously, selecting the Recognize Fields action for a PDF could in some cases result in the following error being shown:
| 76965 |
| General Application | In the Document Capture role center, selecting the Std. Amount Distributions Code menu item would incorrectly navigate to the Purchase Reason Codes page. | 78345 |
| Order & Receipt Matching | Previously, filtering credit memo matching by order no. could fail when the order number exceeded 20 characters. The filter now supports order no. values up to 250 characters. | 74536 |
| Platform and Technology | Previously, upgrading Document Capture to version 28.0 could fail with the following error:
This occurred in environments where one or more document categories had a legacy IMAP password value stored and the Advanced Capture module was not activated at the time of upgrade. | 77135 |
| Purchase Contracts | Previously, when a document was recognized and its vendor contract number matched an active purchase contract, the document was automatically linked to the contract and marked as OK. This happened even when the invoice amount differed from the contract amount or the contract contained expired lines. | 64444 |
| Purchase Contracts | On the Purchase Contract Card, modifying the Max. Allowed Line Variance % or the Max. Allowed Line Variance fields now triggers a new approval process by updating the Approval Status to Approval Needed. | 68109 |
| Purchase Contracts | Previously, no warning was shown when attempting to match an invoice line to a purchase contract line that had already been fully consumed for the current invoicing period. This could allow further matching and approval against an already consumed line. | 68166 |
| Purchase Contracts | In the document journal, recognized document lines are now automatically matched to the corresponding purchase contract lines when capturing a document linked to a purchase contract. | 76291 |
| Purchase Documents | Attachments from Posted Purchase Receipts were incorrectly shown on Posted Purchase Invoices with matching document numbers. | 65613 |
| Purchase Documents | When downloading an attachment from a posted document (invoice or credit memo), the internal storage filename was used instead of the original filename. This affected environments using Azure Blob Storage or File Service as the document storage type. | 75171 |
| Purchase Documents | Previously, when Secure Archive was enabled, deleted attachments were still included in the attachment count displayed in places such as Find Entries and invoice pages. The attachment count now correctly excludes deleted attachments. | 78214 |
| eDocuments | Added mapping of Prepaid Amount in the eBilling Header to the relevant field in the CIIEN16931 XML structure when sending ZUGFeRD eDocuments. | 82182 |
| eDocuments | The note on the final step of the onboarding assisted setup guide now correctly refers to the Network Participations page when explaining where the registration status can be reviewed. | 82071 |