Detailed changelog for Continia Document Capture 2025 R1
This article lists all new features and bug fixes for each version of Continia Document Capture 2025 R1.
Tip
As a Continia partner, you can be notified of new Document Capture versions and service packs whenever they're released. To sign up for this service, go to Receive a notification upon new Document Capture releases in the Continia PartnerZone.
Note
Starting with Document Capture 2025 R1, the configuration files and the Continia Web Approval Portal are no longer included in the download package for Document Capture. However, you can find links to download the Web Approval Portal and the configuration files (per localization) within the installation package. The configuration files can also be downloaded directly from Document Capture.
Important
Document Capture 2025 R1 supports the following versions of Microsoft Dynamics 365 Business Central: Business Central 2025 R1 (v26), Business Central 2024 R2 (v25), and Business Central 2024 R1 (v24).
Document Capture 2025 R1, Service Pack 1
Release date, online: May 14, 2025
Release date, on-premises: May 14, 2025
App version: 26.1.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| eDocuments | The Network Profile field on the XML Structure Setup page has been replaced by the Supported by Network Profiles field, which opens the updated Network Profiles page. This page allows you to tweak the prioritization of network profiles, and ensures that the top profile in the list is automatically selected. Additionally, wildcard profile matching has been implemented to support scenarios where the recipient’s exact profile identifier is unknown. This ensures that the correct profile (wildcard or exact) is selected when sending documents in the PINT format (e.g.: PINT A-NZ). | 64224 |
| eDocuments | Support for the PINT and PINT A-NZ Billing BIS formats has been added. The PINT A-NZ specification becomes mandatory for eInvoicing in Australia and New Zealand on 15 May 2025, replacing the A-NZ Peppol BIS 3.0 format – which is no longer supported. For more information, see Understanding PINT and PINT A-NZ for eInvoicing in Australia and New Zealand. | 62709 |
| XML Export | The following improvements have been added to the ZUGFeRD format: Lines in CII invoices/credit memos with a 0% line discount no longer trigger the following warning when validating an XML file:
The External Document No. field now appears in the CII invoice/credit memo XML files when it contains a value. | 64933 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | Previously, when using the Change Category action for an XML documents in the document journal, the following error could occur:
| 65717 |
| eDocuments | Previously, importing OIOUBL electronic documents that included line discounts could result in an incorrect unit price being captured. | 63275 |
| eDocuments | When sending an order confirmation in the OIOUBL format where the Ship-To Country/Region Code was empty, the following error could occur:
| 64231 |
| eDocuments | Previously, when moving an unregistered eDocument to another company, an error could occur. | 64686 |
| eDocuments | When sending an electronic Peppol document for a posted invoice containing lines with a quantity of 0, the following error was shown:
| 64881 |
| eDocuments | Previously, when exporting an OIOUBL XML document, a source document line with a unit of measure different from the base unit and a quantity per unit of measure other than 1 resulted in incorrect values in the XML file. The invoice line price amount was inaccurate, and the base quantity was set to the quantity per unit of measure. Now, the base quantity is correctly set to 1, and the price amount reflects the price of a single item in the line. | 64977 |
| eDocuments | When importing OIOUBL invoice or credit memo responses, the following error could occur:
| 65445 |
| eDocuments | Previously, the SenderParty EndpointID and ReceiverParty EndpointID nodes in the Peppol BIS3 and OIOUBL XML structures were incorrectly mapped, resulting in invalid eDocuments. | 65446 |
| eDocuments | The price amount node in the PINT and Peppol formats was limited to two decimal places. This limit has now been extended to support up to ten decimal places. | 65703 |
| General Application | Previously, the sending of NemHandel eDocuments was considered successful if no negative receipt was received within 48 hours, even when no delivery confirmation was available. Now, both positive and negative receipts can be received for outgoing NemHandel eDocuments, allowing for more accurate tracking of delivery status. | 65596 |
| General Application | When opening the Outgoing Network Documents page, the following error could occur:
| 66285 |
| XML Export | Previously, creating a Document Output setup for a customer and changing the output profile to ZUGFeRD could cause CII invoices and credit memos to use the incorrect GuidelineSpecifiedDocumentContextParameter in the XML file. | 65200 |
| XML Export | When sending a Peppol document based on an invoice where Price Incl. VAT was set to true, the resulting document could in some cases include the invoice line price amount with VAT included – instead of excluding VAT as expected. | 65235 |
| XML Export | When creating ZUGFeRD eDocuments, the following error could occur in some cases:
| 65816 |
Document Capture 2025 R1, hotfix 5
Release date, online: May 9, 2025
Release date, on-premises: May 9, 2025
App version: 26.0.5
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | When the possibility to choose which master template should be used when creating a vendor template was enabled, the actual choice made by users wasn't respected. Now the chosen template is used. | 65855 |
Document Capture 2025 R1, hotfix 4
Release date, online: May 2, 2025
App version: 26.0.4
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | On-premises customers could, in certain scenarios, see the following error when upgrading Document Capture:
| 66135 |
| General Application | When importing documents, the following error would occur due to a change introduced in Document Capture 26.0:
| 66128 |
Document Capture 2025 R1, hotfix 3
Release date, online: April 28, 2025
App version: 26.0.3
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | When using the Select/CreateTemplate action in the document journal, the choice of which master template to use when creating a vendor template had unintentionally been disabled. | 65855 |
| Documents and Templates | Trying to change the value in the No. field on a purchase line for a document that was pending approval, while the Can Edit Posting Lines setting was enabled in the Continia User Setup, resulted in the following error:
| 65861 |
| Purchase Documents | Previously, attachments copied using the Correct, Cancel, or Create Corrective Credit Memo actions on a posted purchase invoice could not be opened from the newly created purchase document. | 65702 |
Document Capture 2025 R1, hotfix 2*
Release date, online: April 9, 2025
App version: 26.0.2
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| eDocuments | When sending an electronic Peppol document for a posted invoice containing lines with a quantity of 0, the following error was shown:
| 64881 |
| eDocuments | The following error was shown when running the Document Capture assisted setup:
| 65470 |
* The preview version of Document Capture 2025 R1 was released as 26.0.0, and the first official version was released as 26.0.1. Hence there's no hotfix 1.
Document Capture 2025 R1
Pre-release date, online: March 21, 2025
Release date, online: April 1, 2025
Release date, on-premises: April 9, 2025
App version: 26.0.1
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | The following only applies to the CH (Swiss) localization. When creating a vendor bank account from a QR code, the following fields are automatically populated from the bank directory:
| 59483 |
| Documents and Templates | To align with Business Central standards, the template field Account Type has been renamed to Type, and No. has been renamed to No. These changes apply to the following pages:
| 47816 |
| Documents and Templates | When selecting the Move To Company action in the document journal, you can now choose both the destination company and the destination category. This allows you to move documents to a different company and category in one step. | 49658 |
| Documents and Templates | The Item Charge Assignment field on the template card is now only displayed when either of the template match invoice/credit memo options is set to match against receipt or return shipment lines. | 52054 |
| Documents and Templates | Using the Create Lines action to create the first allocation line on the Purchase Allocations page could result in allocation lines with an incorrect document type. To prevent this, the Create Line action is now only enabled if at least one allocation line has already been created. | 53361 |
| Documents and Templates | When selecting the Run GDPR Maintenance action in Document Capture Setup to delete old documents, the associated document log entries are also removed. | 54731 |
| Documents and Templates | To help identify the destination company when moving documents between companies, the Display Name field has been added to the Move to Company page. This field is available through page customization. | 56703 |
| Documents and Templates | Validation of Continia Sustainability template header and line fields has been added to the document journal and document card pages. Any validation notifications relating to the sustainability fields are displayed as configurable comments in the Comments section. | 57494 |
| Documents and Templates | The Change Category action in the document journal now allows you to move a document to any category. Previously, you could only move documents between categories with the same Source Record Table ID. | 59661 |
| Documents and Templates | When changing a document's category by adding the Document Category Code column to the document journal and updating its value, the recognize fields functionality is now automatically activated in the destination category. | 59665 |
| Documents and Templates | When recognizing document lines using AI, it is now possible to override the AI’s suggested values for the following line fields:
| 60606 |
| Documents and Templates | In Accounts for Amounts, the sustainability fields are only editable when Type is G/L Account or Item. | 62103 |
| Documents and Templates | Previously, opening a PDF file would automatically trigger a download to your computer. Now, PDFs open directly in the Business Central client using the new Business Central 2025 R1 standard feature: Preview PDF attachments directly in the web client. This allows you to view documents instantly, while still having the option to download them when needed. | 64353 |
| Document Approval | To prevent approval blockages in the Web Approval Portal, enabling one of the following Continia approval workflows in the Document Capture Setup automatically creates an approval user group with the code ALL, but only if a group with the same name doesn’t already exist. The group includes all assigning and approval permissions on all types and dimensions.
| 45868 |
| Document Approval | The settings Enable Order Approval and Enable Return Order Approval have been added to the Purchase Approval Setup assisted guide. | 49612 |
| Document Approval | Added the Document Date field to the Purchase Approvals Entries page. | 53311 |
| General Application | When selecting the Perform Document Check action in the document control log, the filter is now automatically set to show only failed lines – if any are identified. | 55040 |
| General Application | Read-links have been added to Continia Document Capture entries on the Business Central Assisted Setup page, providing direct access to the related Continia Docs article. | 60550 |
| Order & Receipt Matching | It's now possible to match purchase invoices and credit memos to purchase orders/receipts or return orders that contain lines with the same line amount, even if they have different units of measure and, as a result, different unit costs. For further details, see Setting up order and receipt matching. | 27261 |
| Order & Receipt Matching | To clarify the potential impact on Quantity to Receive for unreceived order lines, the message shown when registering a matched purchase invoice to a purchase order that has already been matched has been extended. | 63587 |
| Purchase Documents | When using the Correct, Cancel, or Create Corrective Credit Memo actions on a posted purchase invoice, any attachment on the posted invoice is now copied to the document created in the cancel/correct process. The files are copied as drag-and-drop attachments. | 58765 |
| Platform and Technology | Document Capture's custom FactBox pane resizing implementation, when running on Business Central 26.0 and above, has been deprecated in favor of Microsoft's latest native implementation. Note that Microsoft's implementation limits the FactBox pane width to a maximum of 50% of the screen, whereas Document Capture's previous implementation allowed for wider expansion. | 64858 |
| eDocuments | The new Payment Means feature provides you with more flexibility when configuring and using payment means in electronic invoices and credit memos. For more information, see Using payment means in eDocuments. | 62706 |
| eDocuments | You can now use the Create Vendor and Create Customer guides when working with XML/eDocuments received via the Continia Delivery Network. | 40795 |
| eDocuments | From the Outgoing Network Documents page, you can now send copies of previously sent documents. This feature is available for eDocuments with the status Successful – and only for electronic document formats that support the Copy Indicator node. Currently, only the OIOUBL format supports it. When using the Resend action, an eDocument record is created in the Continia Delivery Network, and the document copy is sent automatically. Additionally, a new Copy column has been added to the Outgoing Network Documents page to indicate that the sent eDocument is a copy. | 55339 |
| eDocuments | The Document Receipts FactBox has been added to the eDocument Overview page. A new field, Document Receipt Status, has been added to the following pages. This field displays the document's latest receipt status, allowing you to track its receipt state directly from the eDocument card.
| 56152 |
| eDocuments | The following only applies to the DK (Danish) localization. In the newer versions of Business Central, a notification could appear in the Role Center informing you that the company hasn't been registered in the NemHandel network – even if a participation was previously approved through Continia. To remove the notification, open the Continia Delivery Network Participations page containing the approved NemHandel participation. | 56617 |
| eDocuments | The Skip action has been added to the Import eDocument Configurations step in the Set Up Continia eDocuments assisted guide. This action allows the setup to continue without importing a configuration. If this step is skipped and the setup has not been completed previously, the following error is shown:
| 60368 |
| eDocuments | The Set Up eDocuments assisted guide has been added to the standard Business Central Assisted Setup list. | 60369 |
| eDocuments | The following only applies to the BE (Belgian) localization. The eDocuments source identification by enterprise number has been added to the following Document Capture templates. EORDERCANCEL-ID (eOrder Cancellation - Ident.) EORDERCHANGE-ID (eOrder Change - Identification) EORDER-ID (eOrder - Identification) EBILLING-ID (eBilling - Identification) EORDERRESP-ID (eOrder - Identification) EBILLINGRESP-ID (eInvoice Resp - Identification) | 60665 |
| eDocuments | Prior to this, utility statement (UTS) documents failed to be related to the corresponding invoice when the invoice was received using eDocuments. | 60906 |
| eDocuments | Previously, when sending a Peppol invoice through the Continia Delivery Network while using the standard payment discount functionality in Business Central, the generated electronic document did not reflect the discounts. Now, the discount amounts are correctly applied in the electronic document. | 61175 |
| eDocuments | It's now possible to set all participations within a company to test mode. To make use of this feature, go to the Continia eDocuments Setup page and enable the Test Mode option. When enabling test mode in a company, the following applies:
| 61704 |
| eDocuments | The field Handle Incoming eBilling Docs has been added to the Continia eDocuments Setup page. This field specifies whether incoming electronic documents of type invoice or credit memo should be processed using the eDocuments feature. | 61800 |
| eDocuments | To support A-NZ Peppol BIS3 in Australia and New Zealand, two new XML structures have been added:
| 62091 |
| eDocuments | The XML Structure View page layout has been restructured to improve the user experience:
| 62923 |
| eDocuments | Disabled network profiles and participation ID types are now hidden, and cannot be selected or used for sending eDocuments. This ensures only active metadata is used, improving data integrity and compliance. | 63748 |
Bug fixes
All relevant bug fixes released in service packs and hotfixes up to Service Pack 2, hotfix 1, for Document Capture 2024 R2 (25.00) are also included in Document Capture 2025 R1 (26.00). The description of these bug fixes is not repeated on this page.
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | Previously, when creating a vendor from a PDF, recognized country codes with more than two characters would block the vendor creation. | 58737 |
| Country and Regional | Previously, the VAT Bus. Post. Group column on the Accounts for Amounts page was incorrectly translated in the Swedish localization to Moms produktbokföringsmall. It's now correctly translated to Moms rörelsebokföringsmall. | 62311 |
| Country and Regional | A missing English localization has been added for the Delete Blanks field on the Template Field Card page. | 64951 |
| Documents and Templates | Captions have been removed for the template template line field Order No. as lines fields are only recognized through manual marking. Therefore, the captions serve no purpose. | 45900 |
| Documents and Templates | When importing multiple files, a field recognition failure in one document prevented subsequent documents from being recognized. | 48432 |
| Documents and Templates | When using the drop shipment feature on a purchase order line, attempting to update the order quantity from the Purchase Order category would result in the following error:
| 54332 |
| Documents and Templates | When reopening a registered document in the Contact category, the created interaction log entry remained on the contact – which could result in the document being registered multiple times. This issue occurred because the reopen codeunit was missing from the category card. A new codeunit has been added to ensure that previously registered data is cleared when reopening the document, preventing duplicate registrations. | 57119 |
| Documents and Templates | When capturing a value containing an operator character (such as | or &), the following error could sometimes occur due to incorrect handling of line translation values:
| 57901 |
| Documents and Templates | Previously, capturing a value that contained certain special characters (such as \) would result in an "Unrecognized escape sequence" error. This has been adjusted for the following characters: , +, [, ], {, }, ?, (, ), *. | 58452 |
| Documents and Templates | Previously, entering a negative value in the header field Type (née Account Type) would result in the following error:
| 59880 |
| Documents and Templates | Previously, registering a sales document with the same external document number as an existing sales order was not possible, as the registration was blocked by an error comment. To align with Business Central standards, it is now possible to register sales orders with duplicate external document numbers. The comment still appears in the document journal, but it will no longer block registration. | 61451 |
| Documents and Templates | In certain cases, when recognizing purchase document lines that spanned across multiple pages, values from the last line were not captured. | 62183 |
| Documents and Templates | Previously, if two or more master templates existed and none were set as default, the following error message appeared when attempting to create a template via the dialog that opens after selecting Recognize Fields:
| 62339 |
| Documents and Templates | The template field rule for Belgian VAT registration numbers in the default setup has been updated from (BE)?0[0-9]{9} to (BE)?[0-9]{10} to ensure a correct identification, as the Belgian VAT numbers can begin with 0 or 1. | 64540 |
| Document Approval | Spaces have been adjusted in a warning comment related to matching the total amount of purchase receipts. | 53544 |
| Document Approval | When using the Send Approval Request action for an open purchase document and no workflow was found, the following misleading error was shown:
| 55657 |
| Document Approval | The following caption and tooltip have been updated on the Document Capture Setup / Continia Web Approval page to better reflect the related functionality:
| 61523 |
| Document Approval | The following page captions have been updated to use "- Document Capture" instead of "(DC)":
| 63549 |
| General Application | In certain cases, the Stop Line Recognition setting on the Template Field Card was ignored when capturing purchase document lines using the manual line recognition method. As a result, document lines following the totals were unintentionally captured. | 61536 |
| General Application | When using the Create Vendor guide, it is now possible to clear the Country Code and Currency Code fields. | 64546 |
| Purchase Contracts | The option Purchase Contracts has been removed from the Translate to Type field on the Line Translations page because it wasn't a valid option. The No. action should be used instead. | 54088 |
| Purchase Contracts | Previously, when registering a purchase invoice with a purchase contract selected as the account type – and the Auto Approve Within Variance setting on the contract was set to No – the invoice could still be automatically released and approved, if other required conditions were met. | 63447 |
| Purchase Documents | The misspelling of registrering has been adjusted to registering in several warning comments. | 59557 |
| Purchase Documents | If a default remit-to code has been configured on the vendor level, the Remit-To Code field on the purchase invoice is now automatically set when registering a document. | 62426 |
| eDocuments | The template line field No. has been set to not required on the eOrder Response master template. | 62437 |