Detailed changelog for Continia Document Output 2025 R2
This article lists all new updates, features, service packs, and hotfixes for Continia Document Output 2025 R2.
Tip
As a Continia partner, you can be notified of new Document Output versions and service packs whenever they're released. To sign up for this service, go to Receive a notification upon new Document Output releases in the Continia PartnerZone (only available to partners).
Note
The changelog for Document Output 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 Output 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.
Important
Document Output 2025 R2 supports the following version of Microsoft Dynamics 365 Business Central: Business Central 2025 R2 (v27).
Document Output 2025 R2 Service Pack 1, hotfix 2
Release date, online: November 12, 2025
App version: 27.1.2
Bug Fixes
| Functional Area | Description | ID |
|---|---|---|
| Documents and Templates | Previously, when modifying or inserting lines in Sales Orders or Purchase Orders (Sales Lines or Purchase Lines), the Handled field on the document header was automatically reset. This behavior has been changed. The Handled field on Sales Orders and Purchase Orders will no longer be reset automatically when lines are modified or inserted. To reset the Handled status on a document, the new ResetDocumentHandledStatus procedure from codeunit 6175302 CDO Handled Fields Management must be used. This change ensures that the Handled status is only reset intentionally, providing more control over document processing logic. | 70668 |
Document Output 2025 R2 Service Pack 1, hotfix 1
Release date, online: November 11, 2025
App version: 27.1.1
Internal release.
Document Output 2025 R2 Service Pack 1
Release date, online: November 10, 2025
App version: 27.1
Bug Fixes
| Functional Area | Description | ID |
|---|---|---|
| Documents and Templates | Enabled the use of Boolean values as variant fields on templates, regardless of the selected UI language. Previously, when attempting to use a Boolean value as a variant on a template in a non-English UI language, the system did not recognize the value correctly, resulting in incorrect template behavior. | 62302 |
| Documents and Templates | When email templates used merge tables with field links that had empty values (such as linking sales shipments to invoices), all records were displayed instead of only the related records. The system now correctly handles empty link field values by not showing the merge table if no matching records are found, ensuring only relevant records appear in merge tables. | 62796 |
| Documents and Templates | Resolved an issue where the Issued Reminders tile on the Document Output dashboard displayed an incorrect document count. The tile now accurately shows the number of unhandled documents by applying the same filtering criteria as used on the drilldown page (Document Output -> Issued Reminders). | 69773 |
| Documents and Templates | When using the Use Queued by User ID option on the Email template card the system will now use the user ID of the user who queued the email to retrieve the "From Email Address". | 70079 |
| Documents and Templates | Previously, when modifying or inserting lines in Sales Orders or Purchase Orders (Sales Lines or Purchase Lines), the Handled field on the document header was automatically reset. This behavior has been changed. The Handled field on Sales Orders and Purchase Orders will no longer be reset automatically when lines are modified or inserted. To reset the Handled status on a document, the new ResetDocumentHandledStatus procedure from codeunit 6175302 CDO Handled Fields Management must be used. This change ensures that the Handled status is only reset intentionally, providing more control over document processing logic. | 70668 |
| General Application | Previously, when users attempted to modify records in CDO Send Code Output Profile (TableData 6175300) without the required permissions, the following error occurred:
| 69840 |
| General Application | When sending emails with a specified sender email address that didn't exist in the system, Document Output correctly fell back to the default Business Central email account for sending. However, the Document Output Log incorrectly displayed the original non-existent email address in the From Address field instead of the actual email address used. The log now correctly records the email address that was actually used to send the email, providing accurate audit trails for troubleshooting and compliance purposes. | 69981 |
Document Output 2025 R2, hotfix 2
Release date, online: October 22, 2025
App version: 27.0.2
Bug Fixes
| Functional Area | Description | ID |
|---|---|---|
| General Application | Fixed an issue where the print PDF function did not display the report request page. Users can now configure print settings before generating PDFs. | 70285 |
| General Application | Fixed an issue where the Customer Ledger Entry No. was cleared on prepayment sales invoices, causing the Remaining Amount to incorrectly display as 0. The event subscriber for prepayment posting now properly preserves the ledger entry reference while resetting only the CDO tracking fields. | 70565 |
Document Output 2025 R2, hotfix 1
Release date, online: October 2, 2025
App version: 27.0.1
Bug Fixes
| Functional Area | Description | ID |
|---|---|---|
| General Application | When modifying certain fields on purchase orders where the field CDO Handled has value <TRUE>, the following error occurred:
| 69893 |
| General Application | Fixed permission issue preventing users from posting prepayment credit memos and other documents. The CDO Subscribers codeunit now includes all required permissions for protected tables, resolving "You do not have permission to modify" errors that occurred during document posting operations. | 70040 |
Document Output 2025 R2
Pre-release date, online: September 20, 2025
Release date, online: October 2, 2025
App version: 27.0.0
New or Changed Functionality
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | A new eSeal feature has been added to automatically apply electronic seals to PDF documents sent to customers, verifying the origin, integrity and signing entity's identity. The feature can be configured individually for each customer and integrates with existing document workflows, ensuring that PDF documents are secured without manual steps. This feature is available when activating the new Security module. | 57475 |
| Documents and Templates | Added ability to select file format (PDF, Excel, or Word) at the Template line reports (Report overwrite), on the Email Template Lines. This allows sending the same document type in different formats based on recipient preferences or template Variants, providing greater flexibility in document delivery. | 59059 |
| General Application | The field handling of Buyer Reference and Order Reference in Document Output (DO) and Continia Delivery Network (CDN) has been reworked for PEPPOL BIS 3, OIOUBL, and xRechnung formats. Current field mapping:
| 60261 |
| General Application | Added events to allow customization of document template selection when attaching invoices and credit memos to reminders. Partners can now override the default template selection for special document types like rental invoices and credit memos, enabling proper document generation for specialized modules and complete coverage of all open documents scenarios. | 68393 |
| General Application | The following changes have been made to the Document Output permission sets:
For more information about permission sets, see Document Output Permissions. | 68586 |
| General Application | Enhanced Document Output with a new modular architecture that provides better scalability and easier feature management. The system now supports distinct Essential and Security modules, improving license management and feature organization. With the introduction of the Security module, the features PDF-Password and Sign-PDF will be moved from the Essential module to the Security module. This means that the interface elements related to these features will no longer be visible unless the Security module is enabled. | 68971 |
| 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 |
| XML Export | Added support for payment discounts in XML export when exporting electronic documents from sales invoices and service invoices. | 66305 |
Bug Fixes
| Functional area | Description | ID |
|---|---|---|
| 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 |
| 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 |
| General Application | When copying a company in an on-premises installation and Continia eDocuments wasn't licensed, the following error message was shown:
| 67696 |
| General Application | When canceling the dialog for Post and Send/Print on sales orders with partial deliveries, previous invoices were incorrectly sent to the customer. The operation is now properly aborted when canceling the posting dialog. | 69296 |
| 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 guideline specified document context parameter 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 | Previously, eDocuments for sales invoices and credit memos containing comment type lines could generate incorrect tax totals. | 65765 |
| XML Export | When creating ZUGFeRD eDocuments, the following error could occur in some situations:
| 65816 |
| XML Export | When creating an electronic document in Document Output the following error could occur:
| 66999 |
| XML Export | Previously, incorrect taxable amounts were shown in Document Output when price incl. VAT was set to true in an OIOUBL electronic invoice. | 67038 |
| XML Export | When sending an electronic document through Document Output, the following error message cold be shown:
| 67147 |
| XML Export | Previously, if the VAT percentage value had a comma as the decimal separator (e.g.: 25,5), the VAT amounts in the XML document were incorrectly calculated. Now, either a comma (,) or a dot (.) can be used as the decimal separator. | 67550 |
| XML Export | Non-invoiced lines were incorrectly included in the VAT breakdown section of the XML, even when they were not present in the lines section. | 67945 |
| XML Export | Previously, when exporting an e-document with Belgian payment discounts applied, a discrepancy could occasionally be observed between the discount shown in Business Central and the one in the e-document. | 68037 |
| XML Export | The MultiplierFactorNumeric node in eDocuments for the Document Output export functionality was previously formatted as an integer, which could result in invalid eDocuments. It is now correctly formatted as a decimal. | 68216 |
| XML Export | Previously, when attempting to connect multiple candidates from the eCandidates page using the Batch Connect action, the candidates were not connected as expected in some cases. | 68824 |
| XML Export | When exporting an OIOUBL invoice containing a reverse VAT charge, the XML document failed to pass validation – and the following error message was shown:
| 69047 |