Detailed changelog for Continia Document Capture 2025 R2
This article lists all new updates, features, service packs, and hotfixes for Continia Document Capture 2025 R2.
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).
Bemærk
The changelog for Document Capture also includes the release notes for the 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.
Vigtigt
Document Capture 2025 R2 supports the following version of Microsoft Dynamics 365 Business Central: Business Central 2025 R2 (v27).
Document Capture 2025 R2, Service Pack 1
Release date, online: November 3, 2025
App version: 27.1.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | The following only applies to the North American and Canadian (US/CA) localizations. When importing documents in Document Capture, there can sometimes be a difference between the sales tax amounts imported from the vendor document and the amounts calculated in Business Central. To prevent the need for manual handling of such differences, a new setting – Allow automatic update of tax amount – has been added to the General Ledger Setup page. This setting enables the automatic adjustment of tax amounts when registering purchase documents. When Allow automatic update of tax amount is enabled, the assigned tax amount is automatically adjusted to match the imported tax amount – provided that the difference between Assigned Amount Incl. Tax and Imported Amount Incl. Tax on the purchase document is within the Maximum Allowed Difference Incl. Tax defined on the General Ledger Setup page, together with Allow Tax Difference on the Purchases & Payables Setup page. The tax difference amount is distributed across all tax lines on the document’s statistics page, but only for document lines that contain tax. If needed, you can still make manual adjustments. When both Max. Tax Difference Allowed and Maximum Allowed Difference Incl. Tax are defined on the General Ledger Setup page, the lower value of the two is used as the maximum allowed difference. This setting is enabled by default for new installations of Document Capture. For existing users upgrading to this version, the setting can be enabled manually if desired. | 70531 |
| Documents and Templates | When dimensions in Business Central are renamed, any related header or line fields in Document Capture templates are renamed accordingly. | 68709 |
| Documents and Templates | To support standard Business Central functionality, the Allow automatic update of VAT amount setting on the General Ledger Setup page now requires the Allow VAT Difference switch to be enabled on the Purchases & Payables Setup page. If both Max. VAT Difference Allowed and Maximum Allowed Difference Incl. VAT are defined on the General Ledger Setup, the lower value of the two is used as the maximum allowed difference. The VAT difference amount is distributed across all VAT lines in the document’s statistics page, but only for document lines that contain VAT. If needed, you can still make manual adjustments on the statistics page. For more information, see Automatic amount validation. | 70046 |
| General Application | The Document Capture group on the Explorer More Roles page has been extended to include further relevant links. | 60196 |
| Purchase Documents | The Description field on the Standard Amount Distribution Code Card page has been extended to support up to 100 characters. | 68830 |
| eDocuments | Previously, unit of measure translations lacked the flexibility to support all client scenarios. To address this, the UOM translation logic has been redesigned to allow more precise and context-aware translations. Translations are now applied based on four levels of priority:
| 65759 |
| eDocuments | The validation process for eDocuments performed prior to sending has been redesigned. Previously, a custom validation mechanism was used – based on the configured XML structure. Now, a schematron-based validation is used to ensure that all eDocuments comply with the required standards and are fully valid before being sent. | 67327 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | When importing and registering a vendor document that includes a QR code without an amount, the QR-Bill section is now shown on the created purchase invoice. | 65893 |
| Documents and Templates | The Post Code field length has been extended from 10 to 20 characters in the Create Customer/Vendor guide to support longer postal codes. | 68883 |
| Documents and Templates | When changing the When Value is Empty setting on a template line field card from Use Formula to [empty] or any of the copy value options, the formula was still applied. Now, you are asked to confirm whether to keep the formula or remove it. | 69112 |
| Documents and Templates | When using the move to company functionality with Use Unidentified Company Documents enabled on the Document Capture Setup page, and you did not have access to all companies in the database, the following error message was shown:
| 69295 |
| Documents and Templates | The following change only applies to the Danish (DK) localization. When registering a purchase document with multiple lines to the journal and with the digital voucher setup enabled, the following error message was displayed:
| 69470 |
| Documents and Templates | When a formula referencing another template field was specified on a template field card, performing a manual capture resulted in an empty value for the field containing the formula. The formula was only resolved when using the Recognize Fields action. This behavior has been updated, and formulas are also resolved during manual field capture. | 69958 |
| Documents and Templates | In the sales category, minor rounding differences between calculated and captured values previously caused line validation to display an error comment, which ultimately blocked registration. This has been changed so that registration is only blocked if the difference exceeds 0.01 or, if defined, the Amount Rounding Precision specified on the Currencies page. | 70024 |
| Documents and Templates | Filling out the Translate To No. value in the line section on the document card could lead to the following error, even if you had the recommended permission sets:
| 70093 |
| Documents and Templates | When using the Correct, Cancel, or Create Corrective Credit Memo actions on a posted purchase invoice, the attachments on the invoice were not correctly copied to the new documents while using the following document storage types: File System, File Service, and Azure Blob Storage. Now, all attachments are always properly saved as miscellaneous files no matter what storage type is used. | 70435 |
| Document Approval | When adding attachments with file names longer than 80 characters in the Web Approval Portal, the following error message was shown:
| 67162 |
| Document Approval | When opening the Continia User Setup page from the Purchase Approval Setup guide step for configuring approval workflows, the approval configuration fields were hidden. | 70226 |
| General Application | Creating a corrective credit memo creation from a posted purchase invoices now only copies the original attachments, preventing unrelated documents from being included. | 67241 |
| General Application | When certain Continia email scenarios were assigned to an email account, the upgrade to Document Capture version 27 would fail due to the following error:
| 70585 |
| Order & Receipt Matching | When matching a purchase document line that used a non-base unit of measure, the quantity in the resulting purchase document was incorrectly calculated. This was due to the Qty. per Unit of Measure being applied during registration, leading to an incorrect quantity. | 67946 |
| Purchase Contracts | When registering a purchase document linked to a purchase contract configured with Auto Approve Within Variance = Yes, and using a template where Submit for Approval is set as Invoice Reg. Step 2, the purchase invoice was created and released – even though the associated purchase contract had not yet been approved. | 70005 |
| Purchase Documents | When posting purchase allocations, the Source Currency Code, Source Currency VAT Amount, and Source Currency Amount fields on the general ledger entries are now populated. | 58638 |
| eDocuments | For NemHandel OIOUBL invoices, the Invoice/cac:Delivery/cac:DeliveryLocation node was missing in the exported XML. Now, the cbc:DeliveryLocation node is correctly included in NemHandel OIOUBL invoice exports. | 69774 |
| eDocuments | When sending electronic documents to a receiver in a different country, IBAN and SWIFT codes are used instead of bank account details. Additionally, an international payment means code (31, by default) is added to the document. This default can be customized in the field International Payment Means on the Payment Means Setup page. The field priority in Company Information/Bank Account tables has changed for some payment means codes. The priorities are, from first used to last used: FIK (Danish localization)
| 70234 |
| eDocuments | Previously, drilling down on the Capture from eDocument field on the Template Field Card page caused the Capture from eDocument page to open with the Name control always empty. The Name field is now properly populated. | 70476 |
| eDocuments | Previously, when test mode was activated, an error could occur due to a failed receiver participation lookup. Now, when operating in test mode, the receiver lookup is suppressed, ensuring smooth execution. | 70646 |
| General Application | Previously, the Published in Registry setting on the Continia Delivery Network Participations page did not always reflect the actual publication status. It now correctly indicates whether the participation has been published. | 59706 |
| General Application | Previously, the Swedish Party Identification was inserted into the eDocument XML using an incorrect format. It is now inserted in the correct format. | 69397 |
Document Capture 2025 R2, hotfix 2
Release date, online: October 29, 2025
App version: 27.0.2
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| eDocuments | In rare cases, the data upgrade to Document Capture version 27.0 could fail during the procedure FillDocumentRootNodeName. | 70872 |
| eDocuments | Previously, importing an XML document via XML import could trigger the following error message:
| 70953 |
Document Capture 2025 R2, hotfix 1
Release date, online: October 20, 2025
App version: 27.0.1
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | When a template field using a formula referenced another template field with a fixed-value formula, the result sometimes remained empty. | 69910 |
| General Application | When certain Continia email scenarios were assigned to an email account, the upgrade to Document Capture version 27 would fail due to the following error:
| 70585 |
Document Capture 2025 R2
Pre-release date, online: September 17, 2025
Release date, online: October 1, 2025
Release date, on-premises: October 8, 2025
App version: 27.0.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | When deleting a vendor, any unused templates associated with that vendor are also deleted automatically – provided the user has the necessary permissions to delete templates. If not, only the vendor is deleted. | 50687 |
| Documents and Templates | To improve flexibility when registering sales documents, the following document error comment has been made configurable:
| 63888 |
| Documents and Templates | When a template field is set to the Lookup data type, the Translate To field on the Template Field Card also functions as a lookup field now. This allows you to select values dynamically, rather than entering them manually. To enable this functionality, lookup values must be configured for both the source table and source field of the template field. | 64315 |
| Documents and Templates | When using the Move To Company action in document journal, the window for selecting the destination company and category only shows the Display Name of the destination companies now - not the company name. However, if a company's display name is not configured, the company name is populated instead. | 65052 |
| Documents and Templates | Support for capturing Business Central Sustainability activity values and calculating them from emission values has been added to the document journal and document card. | 67922 |
| Document Approval | Previously, when updating the Number field in a purchase document line via the Web Approval Portal to a fixed asset account, the existing values for Quantity, Price, and Amount were removed. These values are now retained. | 56809 |
| General Application | A Download action has been added to the Document Attachments page, allowing you to download the document directly without viewing the content beforehand. If multiple records are selected, the Download and Open actions are disabled to align with standard Business Central functionality. | 64599 |
| General Application | The following changes have been applied to the Document Capture permissions sets:
| 68497 |
| General Application | The field handling of Buyer Reference and Order Reference in Document Output (DO) and Continia Delivery Network (CDN) has been reworked for the PEPPOL BIS 3, OIOUBL, and XRechnung formats. Current field mapping:
| 60261 |
| Order & Receipt Matching | When using unit of measure-based purchase order/receipt matching, the Invoice Matching and Credit Memo Matching pages have been improved with the following:
| 64931 |
| Platform and Technology | The Continia Users and Continia User Setup tables have been refactored and moved to Continia Business Foundation app. Functionality specific to users has also been moved to separate apps:
| 69889 |
| Platform and Technology | With the release of Document Capture 2025 R2 (27.00), support is only provided for Business Central 2025 release wave 2 (BC v27). This was previously announced in the pre-release newsletters. | 54588 |
| Purchase Documents | To prevent the manual handling of invoices related to VAT rounding differences, a new field - Allow automatic update of VAT amount - has been added to the General Ledger Setup page. This setting enables automatic updates of VAT amounts when registering purchase documents. When Allow automatic update of VAT amount is enabled, the assigned VAT amount is automatically adjusted to match the imported VAT amount - provided that the difference between the purchase document’s Assigned Amount Incl. VAT and Imported Amount Incl. VAT is within the Maximum Allowed Difference Incl. VAT defined in the general ledger setup. This setting is enabled by default for new installations of Document Capture. For existing users upgrading to this version, the setting is disabled by default and can be enabled manually if this behavior is desired. | 63726 |
| Purchase Documents | Capture of item tracking information at the line level has been added to the Purchase category for PDF invoices. This functionality currently only applies to invoice creation without order or receipt matching. Tracking capture is enabled by adding by adding one or more of the following line fields to the template: Lot No., Serial No., or Package No. To ensure that tracking information is parsed to the purchase invoice line, at least one of these fields must contain a value. The line fields Expiration Date and Warranty Date have also been added. If present, values from these fields are parsed along with the tracking information. | 64510 |
| eDocuments | The Network Profile field on the XML Structure Setup page has been replaced by a new field: Supported by Network Profiles. Selecting this field opens the updated Network Profiles page, where the prioritization of profiles can be adjusted. The top profile in the list is now automatically selected during document sending. Additionally, wildcard profile matching has been introduced to support cases where the recipient’s exact profile identifier is unknown. This ensures the correct profile – either a wildcard match or an exact match – is selected when sending documents in the PINT format (e.g.: PINT A-NZ). | 64224 |
| eDocuments | Line discount amounts are now automatically recognized when importing electronic orders and order changes. | 65802 |
| eDocuments | When processing an order response that updates an existing purchase order – and the order is in a status other than Open – you're now prompted to reopen the order before continuing. Previously, you had to navigate to the order, reopen it manually, and then return to the document journal to complete the update. | 66254 |
| eDocuments | Previously, when updating the Electronic Format field in Continia Customer Setup or Continia Vendor Setup, the Send From Participation field retained its value. Now, Send From Participation is intentionally reset when the Electronic Format field is modified to prevent invalid configurations. | 66547 |
| eDocuments | The AdditionalItemProperty node and its child nodes Name and Value have been added to the OIOUBLINVOICE and OIOUBLCREDITMEMO eDocuments XML structures. | 67958 |
| eDocuments | Added a new setting to the Continia eDocuments Setup page: Attach PDF to eDocuments. When enabled, a PDF version of the document is automatically generated and embedded into the XML file. | 68101 |
| eDocuments | You can now identify and connect with customers and vendors capable of receiving electronic documents more quickly and easily by using the eCandidates feature. This is possible either individually or in batches. | 68415 |
Bug fixes
All relevant bug fixes released in service packs and hotfixes up to Service Pack 3, hotfix 3 for Document Capture 2025 R1 (26.00) are also included in Document Capture 2025 R2 (27.00). The description of these bug fixes is not repeated on this page.
| Functional area | Description | ID |
|---|---|---|
| General Application | When sending invoices as OIOUBL electronic documents, the schematron validation failed if an invoice discount was applied. The following error was shown:
| 66577 |
| Documents and Templates | The error message displayed when using the Move to Company action without selecting a destination category has been updated for clarity. | 64346 |
| Documents and Templates | Previously, when recognizing an XML document where a template field's XML path contained unsupported characters, Business Central could return an error that caused the page to close unexpectedly. | 65747 |
| Documents and Templates | Due to a change introduced in Document Capture 26.0, the following error could occur when importing documents:
| 66128 |
| Documents and Templates | The value in the template line field Discount % is now included when using the Create Line on Purchase Order function on the Invoice Matching page. The value is only transferred if the Discount Amount line field is zero. | 66890 |
| Purchase Documents | When registering different purchase documents (e.g.: invoices and credit memos) that had been assigned the same number during posting, attachments from both documents were incorrectly shown together. | 66059 |
| Purchase Documents | For easier lookup of the registered document details, a Document Card action has been added to the action group Order on the Sales Order page. | 66235 |
| eDocuments | The Send Electronic Confirmation action has been added to the posted Purchase Invoice page. | 55909 |
| eDocuments | During document import, values from the XML Note element were not populated on the document when mapped to a field. | 67905 |
| eDocuments | In some cases, when sending an eDocument through the Peppol network, the actual delivery date would not be exported – which could cause issues when sending to a receiver that needed that information. Now, the actual delivery date are always exported. | 68372 |