- 16/11/2026
- 76 minutter at læse
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.
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).
Vigtigt
Document Capture 2026 R2 supports the following version of Microsoft Dynamics 365 Business Central: Business Central 2026 R2 (v29).
Document Capture 2026 R2, Service Pack 1, hotfix 1
Release date, online: November 9, 2026
Release date, on premises: TBC
Document Capture version: 29.1.1
Continia Delivery Network version: 29.1
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Order & Receipt Matching | Important | 69483 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | The AI column on document lines now displays Alternative when a different account is entered manually or a translation is deleted from the Line Translations page. The AI suggestions remain available in the drill-down for review and selection. The Recognize Fields action now also removes any remaining AI suggestions from the document lines. | 86261 |
| Documents and Templates | Previously, importing a configuration file using the Set Up Document Capture guide in Document Capture 29.1 could trigger the following error if the file contained a template with an XML stylesheet:
These configuration files can now be imported successfully. Additionally, the custom instructions on templates are now included when exporting and importing templates using configuration files. | 86583 |
| General Application | Previously, dragging a file onto the Documents FactBox opened the file instead of attaching it to the document. The file is now correctly attached to the document when dropped onto the FactBox. | 86479 |
Document Capture 2026 R2, Service Pack 1
Release date, online: October 30, 2026
Release date, on premises: TBC
Document Capture version: 29.1
Continia Delivery Network version: 29.1
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | Previously, when Auto Move to Company was enabled on a document category, inter-company invoices received through the Continia Delivery Network (CDN) could be moved to another company if the buyer or seller identification text matched that company. | 64086 |
| Documents and Templates | Previously, when registering a sales document, item reservations were not automatically created on the resulting sales order – even when the item's Reserved Quantity field on the item was set to Always and sufficient inventory was available. | 71754 |
| Documents and Templates | A new option, Generative AI, has been added to the Line Recognition Method field on the template card. When selected, the document is sent to a generative-AI model, which extracts line values – as well as header field values, if the new Capture Header field on the template card is enabled. The extracted values are populated into the header and line fields, allowing field rules, validation, and registration to work as they do for other captured documents. | 81670 |
| Documents and Templates | You can now configure a minimum confidence level for AI suggestions on each template using the Minimum Confidence Level to Apply setting on the AI Capability FastTab. | 83978 |
| General Application | The OnAfterBuildApprovalEntriesForUser event is now always raised when the Purchase Approval Entries and Purchase Contract Approval Entries pages build their lists of approval entries. | 78658 |
| Order & Receipt Matching | Previously, when manually matching purchase invoices or credit memos on the Invoice Matching or Credit Memo Matching page, the matched quantity was not linked to the corresponding line in Document Lines. | 69483 |
| Order & Receipt Matching | When purchase order approval is enabled and a document in the document journal is matched to a purchase order that has not yet been approved, a configurable warning comment is now displayed. The comment informs you that the purchase order requires approval and that automatic approval of the resulting purchase document will fail. | 81194 |
| Country and Regional | French eReporting now validates whether the seller has a VAT identifier when an invoice is reported with an exempt VAT category. If the VAT identifier is missing, an entry is added to the report log, allowing the issue to be identified before the receiving platform rejects the file. | 83110 |
| Country and Regional | Scenario flow handling for French eDocuments has been enhanced to ensure that invoices and credit memos contain the business process information required by the French eInvoicing platform.
eDocuments sent in other electronic formats are not affected. The eDocument scenario flow can now also be set or changed directly on the Posted Sales Invoice and Posted Sales Credit Memo pages. This allows documents that were posted without a scenario flow to be corrected without cancelling and reposting them. Selecting a scenario flow populates the corresponding scenario values and updates the customer's scenario flow history in the same way as during posting. | 82960 |
| Country and Regional | The FA(3) styled view has been updated to incorporate the latest changes provided by IT.integro. | 83779 |
| Country and Regional | Receiver IDs used when sending eDocuments through the French eInvoicing network can now include a suffix, providing greater flexibility when identifying individual receiving entities. The suffix type can be configured per customer or vendor using the new Receiver ID Suffix Type field in the eDocument setup. | 81424 |
| 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.
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 are unaffected. | 82082 |
| eDocuments | The business process code reported in F10.1 is now automatically determined from the document when no value is specified in the Scenario Framework. This ensures that the correct code is reported for goods, services, and mixed invoices, including final invoices that settle an earlier prepayment.
If a value is specified in the Scenario Framework, it takes precedence. If the document does not contain enough information to determine the code, B1 is used as the default, and this is recorded in the report log. | 82097 |
| eDocuments | A Recalculate action is now available on the eReport Card and eReports list pages, where multiple eReports can be selected and recalculated at once.
| 81778 |
| eDocuments | Required #PMT#, #PMD#, and #AAB# document notes are now generated automatically when you send eDocuments through the France PA network. These notes can also be configured manually on the Payment Means Setup page. | 82138 |
| eDocuments | The CII XML structure used for ZUGFeRD and XRechnung invoices has been enhanced to improve compliance with EN 16931 and XRechnung validation rules. The improvements include exporting line discounts as line allowances, correctly rounding line totals, and including the buyer reference. | 83332 |
| eDocuments | Invoice responses (application rResponses) can now be sent from purchase credit memos, extending the functionality already available for purchase invoices. The supported response types are Accepted and Rejected. | 82965 |
| eDocuments | Customer Onboarding records are now handled according to the environment type when copying a Business Central environment. When copying to a different environment type, such as from production to sandbox, the Customer Onboarding records (Onboarding Company and Alternate Company Name) are deleted. When copying to an environment of the same type, these records are preserved. | 82277 |
| eDocuments | When creating a participation in the Continia Delivery Network, Customer Onboarding is now skipped if Test Mode is enabled, allowing participations to be created without completing customer onboarding. When Test Mode is disabled, Customer Onboarding is still required. | 82554 |
| 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 |
| General Application | The Participation Onboarding assisted setup now takes the activated Continia apps into account when displaying available document flows, profiles, and business roles. This ensures that companies can only register for document exchange capabilities supported by their activated apps. | 82566 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | Previously, opening the Continia AI Capabilities page could fail with the following error:
This occurred when a capability had the status Setup required in a language where the translated status exceeded 20 characters, such as German, Spanish, Portuguese, or French. The page now opens correctly in all languages. | 84504 |
| Documents and Templates | Previously, when the configured document storage type was File Service and the category code was included in the archive paths, using the Change Category action in the document journal moved the document to the new category but left its related files in the original category folder. As a result, the document image was no longer displayed – and downloading the PDF failed. | 78161 |
| Documents and Templates | Previously, when multiple item references existed for the same item number, line translation could incorrectly use an item reference whose Ending Date had passed, resulting in the line being translated to the wrong item. | 81706 |
| Documents and Templates | Previously, when a document imported with the Process PDF files with XML files setting enabled (e.g.: a ZUGFeRD invoice) was moved to another company using the Move to Company action, the attached files (e.g.: the original PDF and any files embedded in it) were not moved along with the document if Document Storage Type was set to File Service on the Document Capture Setup page. | 82931 |
| Documents and Templates | Previously, importing an XML document from the Display Documents page could result in the following error if Auto Move to Company was enabled for the document category and the document was moved to another company during import:
| 83170 |
| Documents and Templates | Previously, when using AI-enhanced line recognition, item tracking details were not always captured – resulting in some lines not being marked in the Has Tracking Lines column in the Lines section. Item tracking details are now correctly recognized, regardless of the capture method used. | 83446 |
| Documents and Templates | Previously, when an account name was entered in the No. or Bal. Account No. field on a document, the G/L account lookup did not respect the Direct Posting setting. | 83512 |
| Documents and Templates | Previously, the Recognize Lines field on the Document Card page displayed No for XML documents even when lines had been recognized. Additionally, setting the field to No did not prevent line recognition. | 83761 |
| Documents and Templates | Previously, when a fixed account was configured in Accounts for Amounts and Auto Suggest Type and No. was enabled on the template, AI account suggestions were still generated during field recognition. | 83966 |
| Documents and Templates | Previously, when a translation was entered manually on a line with an unconfirmed AI suggestion, the translation was not saved to the translation table until it was entered a second time. The translation is now saved the first time it is entered. | 84237 |
| Documents and Templates | Previously, the Recognize Fields action started AI header suggestions even when the document's Line Posting Description field was empty. This resulted in unnecessary processing time and could produce low-confidence suggestions. | 85137 |
| Documents and Templates | Previously, the AI header suggestion status could remain in the Header Pending Review state even when a new AI suggestion run found no G/L account to suggest. The status is now cleared when there are no suggestions left to review, ensuring that it reflects the actual suggestion results. | 85579 |
| General Application | Previously, opening a purchase document or a purchase document list, such as the Purchase Invoices page, could trigger the following error if the document contained an item charge without a value in Gen. Prod. Posting Group:
The amounts displayed by Document Capture on purchase document pages are now calculated without checking or updating the item charge lines. However, the Gen. Prod. Posting Group is still required when the document is posted. | 74256 |
| General Application | Previously, when opening a page containing the Documents FactBox (e.g.: the Vendor Card page), the following error could occur if the number contained special characters such as (, ), or &:
| 81997 |
| General Application | When posting purchase allocations, VAT is now calculated across positive and negative allocation lines with the same VAT rate, preventing rounding differences between the total allocation amount and the purchase invoice total. | 82343 |
| General Application | The existing automatic correction of minor rounding differences during registration of purchase documents has been extended to include the Non-Deductible VAT Amount. This applies when Enable Non-Deductible VAT is enabled in VAT Setup, and both Allow automatic update of VAT amount and Allow VAT Difference are enabled in General Ledger Setup. Manual adjustments can still be made in Statistics. | 83842 |
| General Application | Previously, when Auto Suggest with AI was enabled on a template, clicking the Recognize Fields action while an AI-enhanced line suggestion job was still queued or running could result in the following error:
Now, when Recognize Fields is clicked while the AI line suggestion status is Queued or In Process, a confirmation dialog appears with the following message:
Clicking Yes cancels or stops the current job before starting field recognition. Clicking No leaves the job running or queued without starting field recognition. | 85120 |
| Order & Receipt Matching | Previously, when multiple document lines were matched to the same purchase receipt line with item tracking, selecting the Item Tracking Entries action in the Purchase Receipt Lines part of the Invoice Matching page could trigger the following error:
| 70239 |
| Order & Receipt Matching | Previously, registering a purchase credit memo matched to a purchase return order could result in the following error if the return order lines contained items of type Non-Inventory or Service and were created using the Get Posted Document Lines to Reverse or Copy Document action:
| 84301 |
| Order & Receipt Matching | Previously, when two or more document lines were matched to the same posted purchase receipt line with item tracking, the following error could occur:
| 84626 |
| Order & Receipt Matching | Previously, registering a document containing an item line with a negative quantity could result in an item tracking quantity error, even when the line had no item tracking or reservations. This error no longer occurs for lines without item tracking or reservations. Quantity validation for lines with item tracking remains unchanged. | 85001 |
| Purchase Contracts | Previously, attempting to automatically approve an invoice matched to a purchase contract in a company using a language other than English could trigger the following error:
| 66153 |
| Purchase Contracts | When a purchase contract is created using a Purchase Contract Template with a defined Default Line Type and Default Line No., the contract now includes at least one line with the specified values. This does not apply if the contract is created from a document containing values that result in purchase contract lines being created automatically. | 81808 |
| Purchase Contracts | Previously, registering a purchase contract invoice with Invoice Reg. Step 2 set to Post on the template card could initiate posting of the purchase lines before verifying whether the document was eligible for automatic posting. Additional checks have now been introduced to ensure that the document's eligibility is verified before posting begins. | 82252 |
| Purchase Contracts | The Yearly Amount field on a purchase contract line now reflects the line's total accrued amount over its lifetime if the contract line's duration is shorter than one year. This also ensures that the current amount and yearly tax amount are calculated correctly. | 82862 |
| Purchase Documents | Previously, when AI suggested a value for a document line without an existing translation, two separate errors were displayed in the document's Comments FastTab: one indicating that the line needed to be translated and another indicating that the AI suggestion had to be confirmed. | 84006 |
| Purchase Documents | Matched purchase order and purchase return order lines are now received or shipped when the invoice or credit memo is posted, regardless of whether the document was created through Document Capture. Item tracking information from a captured document is still applied when available. | 84523 |
| Purchase Documents | Previously, posting a purchase allocation with VAT could trigger the following error if its currency matched the Additional Reporting Currency:
Purchase allocations can now be posted successfully under these conditions. | 84879 |
| Country and Regional | Previously, when an eInvoice was exchanged with a party whose identifier included a routing suffix, such as a French SIREN with a suffix, the invoice response (CDAR) could be sent to the recipient's identifier without the suffix. Invoice responses are now sent to the same endpoint as the invoice they respond to, ensuring that routing suffixes are preserved. | 83092 |
| Country and Regional | Previously when sending an eDocument using the French CII or Factur-X formats, the following errors could appear in the validation log:
| 82795 |
| Country and Regional | Previously, the following XML elements were not correctly mapped to their corresponding fields on the eBilling Header when processing documents using the CIIEN-16931 XML structure:
| 82799 |
| Country and Regional | Previously, when sending an eDocument through the France PA network, the following error could occur:
This could occur when the eDocument Line Types setup was incomplete. The complete setup can now be imported using the relevant eDocuments setup guide. | 82877 |
| Country and Regional | Previously, when sending a corrective credit memo for France in the CII format, the issue date of the referenced invoice was formatted as YYYY-MM-DD instead of the required YYYYMMDD. As a result, the credit memo could fail validation with the following error:
The issue date of the referenced invoice is now formatted as YYYYMMDD, allowing corrective credit memos to pass French CII validation. | 82925 |
| Country and Regional | Previously, amount fields in French eDocuments could be generated with excessive decimal precision, resulting in an invalid document and validation errors, such as:
Amount values are now generated with the required decimal precision, ensuring that French eDocuments comply with the required format. | 82963 |
| Country and Regional | The grouping of report types into eReports is now predefined, eliminating the need to configure groups on the eReport Groups page. Invoice and transaction data are combined into one eReport, while payment data is grouped into a separate eReport. When the app is updated, open eReports for the same reporting period that belong together are automatically merged into one eReport. eReports that have already been sent remain unchanged. | 83023 |
| Country and Regional | Previously, French self-billing documents could not be sent successfully through the French eInvoicing network. | 83424 |
| Country and Regional | Previously, when a general journal document contained multiple lines, amounts could be counted more than once in F10.3 eReporting, resulting in overstated declared amounts. Each document is now counted only once, ensuring that the correct amounts are reported. | 83616 |
| Country and Regional | Previously, eReports were not validated against the schematron rules before being sent. As a result, an eReport that did not meet the required format could still be sent. Each eReport is now validated against the schematron rules before it is sent. If validation fails, the eReport is not sent and the validation errors are logged. | 83619 |
| Country and Regional | Previously, in Business Central online, the Scenario Flow field could not be changed on the Posted Sales Invoice and Posted Sales Credit Memo pages – even if you had the required permission sets. | 83743 |
| Country and Regional | Previously, the job responsible for sending eReports stopped if an error occurred, preventing further eReports from being sent until the job was restarted manually. The job now automatically retries up to three times before stopping. | 83878 |
| Country and Regional | Previously, when changing the VAT regime in the country setup for France or clearing eReport Nos. in the eReporting setup, the error message displayed for an eReport that had not yet been sent could provide incorrect guidance. The error message now provides the appropriate guidance based on the status of the eReport. | 83991 |
| Country and Regional | Previously, the Approved tile on the Role Center also counted eReports that were not yet due, and the tiles were not refreshed when returning to the page. The Approved tile has been renamed Ready to Send and now only counts eReports whose reporting period is closed and whose due date has been reached. The Role Center tiles are now also refreshed when returning to the page. | 84061 |
| Country and Regional | Previously, the delivery date reported in an eReport could be incorrect. The eReport now uses the actual delivery date from posted shipments or receipts. If no delivery date is found, the field is left empty and a warning is displayed. | 84137 |
| Country and Regional | Previously, French eReporting retrieved the VAT exemption code from the Full VATEX Code field on the VAT Clauses page. The code is now retrieved from the VATEX Code field on the VAT Posting Setup page, and existing codes are automatically copied to this field when the app is updated. Action required | 84273 |
| Country and Regional | Previously, the eReporting Setup page was read-only for users who did not have the SUPER permission set, even if they had the necessary administrator permissions. | 85357 |
| Country and Regional | The Issue Date is now correctly populated for referenced invoices in credit memos, preventing validation errors during document sending. | 82238 |
| Country and Regional | Previously, payments applied to invoices during posting were not included in the F10.2 and F10.4 payment declarations. | 82259 |
| Country and Regional | Previously, flow F10.2 incorrectly reported payments from French B2B customers instead of foreign B2B customers. Additionally, flows F10.1 and F10.3 excluded invoices with the scenario codes USECASE-20 and USECASE-21, preventing prepayments and their related documents from being reported. | 82260 |
| Country and Regional | Previously, when a credit memo was created using the Cancel action on a posted invoice, or when a Prepayment Credit Memo was created, the reference to the original invoice was not correctly identified during French e-reporting. As French e-reporting requires credit memos to reference the invoices they correct, this caused reporting to fail for the entire period. Both types of credit memos are now reported with the correct invoice reference. | 82455 |
| Country and Regional | Previously, if a document failed a check during eReport generation, the eReport could not be generated for the entire reporting period. The eReport is now generated for the full period, with any failed checks recorded in the eReport Log. If the log contains unresolved entries, confirmation is required before the eReport can be approved. | 82681 |
| Country and Regional | Sales prepayments can now be included in eReporting. Posted prepayment invoices are reported as document type 386, while posted prepayment credit memos are reported as document type 503. | 80629 |
| Country and Regional | Previously, French eReporting transmissions could be rejected during validation by the receiving platform, and transmissions without a receiver identifier could not be sent. The FR report XML has been corrected for the IssueDateTime format, seller and buyer identification – including the seller's tax representative and the transmission type used when a report is resubmitted. These transmissions are now accepted and can be sent successfully. | 81893 |
| 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 | Previously, when the country/region specified in Company Information had no ISO Code, the scheduled Continia Delivery Network metadata update failed with the following error:
As a result, the job queue repeatedly retried the update. The metadata update now completes even if the ISO Code is missing. Network identifier types are still updated, but no default identifier type is assigned for the company's country/region until the ISO Code is entered on the Countries/Regions page and the metadata update is run again. | 82737 |
| eDocuments | Previously, when the job queue entry responsible for updating Continia Delivery Network metadata ran under a user with only the Continia Delivery Network - Basic permission set, the job failed with the following error:
The job queue repeatedly retried the job, preventing updates to networks, identifier types, network profiles, and profile document types. The Continia Delivery Network - Basic permission set now includes the permissions required to update the metadata, allowing the job to complete successfully for users with basic permissions. | 82738 |
| eDocuments | Previously, the eDocument Status field on posted purchase credit memos could be left empty after posting instead of being set to Received. The field is now correctly set to Received when a purchase credit memo is posted. | 83283 |
| eDocuments | Previously, sending a posted sales credit memo in ZUGFeRD format resulted in the following error because the format only included an XML structure for invoices:
The ZUGFeRD format now also includes an XML structure for credit memos, allowing posted sales credit memos to be sent in this format. Incoming credit notes in ZUGFeRD format are now also correctly recognized as credit memos. | 83367 |
| eDocuments | Previously, French eReports could fail validation because dates were not formatted using the required AAAAMMJJ format and the sender was not identified as an approved platform. Dates are now formatted as AAAAMMJJ, and the sender is identified using identifier type 0238 and role code WK – allowing the eReports to pass French validation. | 83641 |
| eDocuments | Previously, users with the DO-BASIC permission set could encounter the following error when assigning an eDocument Scenario Flow code to a sales document:
The Continia Delivery Network - Scenario Framework app now includes the required indirect permissions, allowing users with the DO-BASIC permission set to assign eDocument Scenario Flow codes to sales documents. | 84154 |
| eDocuments | Previously, when resolving VAT as the endpoint type for a Norwegian customer whose VAT Number was formatted as | 84433 |
| eDocuments | A new action has been added to the Continia eDocuments Setup page, allowing users to rerun the automatic mapping between Business Central records and their corresponding code list values. | 82187 |
| eDocuments | The required ICD-FR SchemeID is now correctly populated when a delivery location identifier is present, ensuring compliance with French validation rules and preventing document rejection during submission. | 82188 |
| eDocuments | The reliability of the eDocuments receiving capabilities check has been improved to ensure that receiving endpoint information is determined independently for each customer. | 82231 |
| eDocuments | Previously, the style sheet used for displaying UBL-FR files in a reader-friendly format could incorrectly show Unknown Document Type. | 82488 |
| eDocuments | Previously, users with the DO-BASIC permission set could encounter the following error when assigning an eDocument Scenario Flow code to a sales document:
The Continia Delivery Network - Scenario Framework app now includes the required indirect permissions, allowing users with the DO-BASIC permission set to assign eDocument Scenario Flow codes to sales documents. | 80406 |
| eDocuments | Previously, when discovering receiving capabilities using the eCandidates page, the FR:CTC identification type was not included in the discovery process. This could prevent receiving capabilities from being identified correctly for customers in France, where FR:CTC is commonly used. | 81540 |
| eDocuments | When sending a sales credit memo using the French CII format, the generated XML incorrectly used document type code 380 (invoice) instead of 381 (credit memo) because the document type could be overwritten by default scenario flows. | 81773 |
| eDocuments | France PA participants could not receive plain Peppol BIS 3 invoices and credit memos because the four France PA network profiles for Peppol BIS Billing 3.0 and Peppol BIS Self-Billing 3.0 were not mapped to any XML structure. | 82035 |
| General Application | Previously, the Company Name, Country Code, and VAT Registration No. columns on the Network Participations page could be empty because the company onboarding data was not retrieved after an upgrade. | 85418 |
Document Capture 2026 R2, hotfix 1
Release date, online: October 24, 2026
Document Capture version: 29.0.1
Continia Delivery Network version: 29.0.1
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Previously, the AI capabilities for account and line suggestions were added only when Document Capture was installed for the first time. Companies that upgraded from an earlier version – including from Document Capture 2026 R1 (28.0) to 2026 R2 (29.0) – did not get these capabilities, so the suggestions were not available. | 85537 |
Continia Delivery Network 2026 R2, hotfix 1
Release date, online: October 21, 2026
Document Capture version: 29.0.0
Continia Delivery Network version: 29.0.1
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | When an OIOUBL invoice that contained a prepaid amount was sent, the following validation errors occurred:
The cac:PrepaidPayment section is now generated when a prepaid amount is specified, and the Payment Terms amount is set to match the payable amount. | 84515 |
| eDocuments | Previously, when delegated users would complete the Customer Onboarding, they would receive an error, that they are not allowed to schedule background tasks. This would roll back changes in Business Central and force users to resync with the backend before completing the onboarding- This is now fixed, and delegated users can now complete the Customer Onboarding without scheduling the background job. | 83263 |
Document Capture 2026 R2
Pre-release date, online: September 21, 2026
Release date, online: October 1, 2026
Release date, on-premises: October 11, 2026
Document Capture version: 29.0.0
Continia Delivery Network version: 29.0.0
Bemærk
This changelog is subject to changes until the official release is live.
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 |
| Documents and Templates | 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 |
| Documents and Templates | 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 |
| Documents and Templates | 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 |
| Country and Regional | Receiver IDs used when sending eDocuments through the French eInvoicing network can now include a suffix, providing greater flexibility when identifying individual receiving entities. The suffix type can be configured per customer or vendor using the new Receiver ID Suffix Type field in the eDocument setup. The functionality is extensible, allowing partners to define custom suffix types by extending the Receiver ID Suffix Type enum and implementing the IRcv ID Suffix interface. When a suffix type is available, it can be selected for the relevant customer or vendor. | 81424 |
| 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 28.5 for Document Capture 2026 R1 (28.00) are also included in Document Capture 2026 R2 (29.0). 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, upgrading Document Capture to version 29.0 could fail with the following error:
This occurred in companies where one or more approval forwarding entries existed and the Document Approval module was not activated at the time of upgrade. The upgrade now completes successfully, regardless of the activation state of Document Approval. | 83799 |
| 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 iInvoices 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 the 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 |
| Country and Regional | Previously, when an invoice was exchanged with a party whose identifier included a routing suffix, such as a French SIREN with a suffix, the invoice response (CDAR) could be sent to the recipient's identifier without the suffix. Invoice responses are now sent to the same endpoint as the invoice they respond to, ensuring that routing suffixes are preserved. | 83092 |
| Country and Regional | Previously, eReports were not validated against the schematron rules before being sent. As a result, an eReport that did not meet the required format could still be sent. Each eReport is now validated against the schematron rules before it is sent. If validation fails, the eReport is not sent – and the validation errors are logged. | 83619 |
| Country and Regional | Previously, in Business Central online, the Scenario Flow field could not be changed on the Posted Sales Invoice and Posted Sales Credit Memo pages, even for users with the required permission sets. This was because Business Central online only allows posted documents to be modified through the standard update process. The Scenario Flow field has now been added to the page that opens from the Update Document action. The scenario flow can therefore be changed on posted sales invoices and credit memos in Business Central online, with the changes saved through the standard update process. | 83743 |
| eDocuments | Previously, French eReports could fail validation because dates were not formatted using the required AAAAMMJJ format and the sender was not identified as an approved platform. Dates are now formatted as AAAAMMJJ, and the sender is identified using identifier type 0238 and role code WK – allowing the eReports to pass French validation. | 83641 |
| eDocuments | Previously, when discovering receiving capabilities using the eCandidates page, the FR:CTC identification type was not included in the discovery process. This could prevent receiving capabilities from being identified correctly for customers in France. The FR:CTC identification type is now included when discovering receiving capabilities. To ensure that FR:CTC is evaluated for existing customers, run Refresh List with Customers with the Force Refresh Cache setting enabled. | 81540 |
| 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 |