Detailed changelog for Continia Document Output 2026 R1, including CDN
This article lists all new updates, features, service packs, and hotfixes for Continia Document Output 2026 R1 and 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.
Tipp
As a Continia partner, you can be notified of new Document Output versions and service packs when 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).
Wichtig
Document Output 2026 R1 supports the following version of Microsoft Dynamics 365 Business Central: Business Central 2026 R1 (v28).
Document Output 2026 R1 Service Pack 2
Release date, online: June 1, 2026
Document Output version: 28.2.0
Continia Delivery Network version: 28.2.0
New or Changed Functionality
| Functional area | Description | ID |
|---|---|---|
| eDocuments | Automatic downloading of inbound eDocuments can now be enabled, disabled, and scheduled at a configurable interval from the Continia eDocuments Setup page. | 76910 |
| eDocuments | eDocument log entries are now stored in Azure Blob Storage based on the Log Storage Type setting in the Document Output Setup. Previously, only email log entries were stored in Azure Blob Storage while e-document XML data was always stored in the database; existing e-document entries can be migrated by running Move Logs from Document Output Setup. | 77805 |
| General Application | The default number series created during new eDocuments installations have been updated. The number series assigned to eBilling Document Nos., eOrder Document Nos., eDocument Response Document Nos., eOrder Response Document Nos., and eReminder Document Nos. now use the EDOCS prefix instead of DC. This change reflects that these number series can be used by both Document Capture and Document Output. When importing an eDocuments configuration file through the Set Up Document Capture or Set Up Document Output guide, existing number series in the Continia eDocuments Setup are now preserved. Previously, importing a configuration file could overwrite number series already configured in the setup. | 71223 |
| General Application | The performance of the Document Output Setup assisted setup guide has been significantly improved. As a result, migrations from Document Capture to Document Output now complete much faster and more reliably. These enhancements also prevent timeouts for customers with large data volumes, ensuring a smoother migration experience. | 78472 |
Bug Fixes
| Functional area | Description | ID |
|---|---|---|
| eDocuments | Previously, the customer GLN was used in the delivery details of exported electronic documents, even when the document contained a ship-to address with its own GLN. The GLN from the ship-to address is now used when available, ensuring that goods are delivered to the correct location. The customer GLN is used only as a fallback when no ship-to address is specified or when the ship-to address does not contain a GLN. | 57898 |
| eDocuments | Previously, sending a sales invoice or credit memo containing a fixed asset line could result in the eDocument being marked as Not Valid because the generated eDocument line was missing a name and unit of measure. During eDocument generation, the line name is now populated from the fixed asset description, falling back to the sales line description when the fixed asset description is empty. Unit of measure information is resolved from configured code list translations or the unit of measure's international standard code, falling back to EA when no value is available. | 69656 |
| eDocuments | When you used the Send eDocument action with an output profile configured to export only to a folder (with Send Through Network disabled), the following error occurred: - There is no Participation within the filter. Filters: CDN GUID: {00000000-0000-0000-0000-000000000000} This has now been fixed, and the action exports the XML to the configured folder without attempting a Continia Delivery Network send. | 77161 |
| eDocuments | When importing eDocuments configuration files through the Set Up eDocuments for Document Output or Set Up Document Output guide, all data was previously marked as Include by default, even when the corresponding records already existed in the database. Existing records are now excluded by default, and only data that does not already exist in the database is marked as Include. | 77401 |
| eDocuments | The setup status for eDocument sending now correctly reflects when Document Output has been activated but not fully configured. When attempting to send an eDocument, users are prompted to complete the Document Output Setup before eDocuments can be sent. | 77988 |
| General Application | In the Continia Delivery Network Onboarding setup guide, changing the country/region code to BE previously forced the Identification Type field to BE:EN. With this update, BE:EN is still suggested, but the value can now be changed. | 72477 |
| General Application | In certain cases, executing the CTS-CDN Upgrade Metadata Job job queue entry could cause the metadata upgrade to fail with the following error:
| 77406 |
Document Output 2026 R1 Service Pack 1, hotfix 3
Release date, online: May 19, 2026
Document Output version: 28.1.3
Continia Delivery Network version: 28.1.0
Bug Fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | On-premises customers without Document Output activated could not post sales orders or sales/service invoices due to missing permissions. This has now been fixed by skipping the subscriber code. | 78540 |
Document Output 2026 R1 Service Pack 1, hotfix 2
Release date, online: May 8, 2026
Release date, on-premises: May 12, 2026
Document Output version: 28.1.2
Continia Delivery Network version: 28.1.0
Bug Fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | When upgrading on large databases, the upgrade could time out due to unnecessary bulk updates of document records when setting up default output profiles. The upgrade now avoids these bulk updates when setting up default output profiles. | 77996 |
| General Application | When opening the Document Output Manual setup in certain languages, it could fail because translated titles exceeded the allowed length. The setup page now correctly handles long translations. | 78008 |
Document Output 2026 R1 Service Pack 1, hotfix 1
Release date, online: May 6, 2026
Document Output version: 28.1.1
Continia Delivery Network version: 28.1.0
Bug Fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | When opening the Document Output assisted setup in certain languages (for example, French, Spanish or Danish), it could fail because translated titles exceeded the allowed length. The setup page now correctly handles long translations. | 77789 |
Document Output 2026 R1 Service Pack 1
Release date, online: May 1, 2026
Release date, on-premises: May 4, 2026
Document Output version: 28.1.0
Continia Delivery Network version: 28.1.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | When exporting ZUGFeRD XML documents, they were saved with a UTF-8 BOM, which could trigger encoding warnings in external archiving systems such as DocuWare. ZUGFeRD XML documents are now saved as pure UTF-8 without BOM for improved compatibility. | 72935 |
| General Application | You can now configure automatic sending of posted sales and service invoices and credit memos per customer in Document Output. When enabled on the customer, documents are sent automatically on posting based on the customer’s output settings, and any send failures are logged in the Document Output error queue. | 75360 |
| General Application | The Migration assisted setup guide used when activating DO from DC now shows a customer conflict list with a recommended output profile and lets you choose the outcome (including returning later), and a notification is shown when a customer is used while a conflict remains unresolved. This ensures that unresolved conflicts no longer go unnoticed. | 76730 |
| eDocuments | It is now possible to import eDocuments configuration files from local storage or online sources and select specific setup data to be applied. This is supported through an additional step in the Set Up eDocuments for Document Output and Set Up Document Output guides. | 75971 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | Documents in the Document Output Queue were sent outside the configured time window when an associated Email Template job restricted sending to a specific window. Documents added to the queue are now held until the Emil Template job time window is active, while entries with no associated or no longer existing Emil Template jobs continue to be processed unconditionally. | 74771 |
| eDocuments | When connecting a customer using the Connect eCandidates guide on the eCandidates page, selecting an output profile without a configured sender profile could result in the following error:
| 75847 |
| eDocuments | When eDocument processing failed (create, validate, or send), subsequent post-processing steps still executed and incorrectly updated document counters, print flags, inserted CDO File records, and triggered delivery finalization. When an eDocument error occurs, the dispatcher now exits gracefully, so these post-processing steps are skipped. | 75954 |
| XML Export | When the Amount Rounding Precision (LCY) in the General Ledger Setup was set to more than two decimal places (for example, 0.00001), generating a Peppol BIS Billing 3.0 eDocument for a posted sales invoice or credit memo could result in an invalid document that failed schematron validation. The generated eDocument now uses the PayableRoundingAmount field to correctly handle rounding differences, ensuring that the document passes validation regardless of the configured rounding precision. | 76383 |
Document Output 2026 R1, hotfix 1
Release date, online: April 23, 2026
Document Output version: 28.0.1
Continia Delivery Network version: 28.0.0
Bug Fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | When the following chain of events occurs:
This has now been corrected, so that the proper XML is sent for each queued document. | 75084 |
Document Output 2026 R1
Pre-release date, online: March 23, 2026
Release date, online: April 1, 2026
Release date, on-premises: April 7, 2026
Document Output version: 28.0.0
Continia Delivery Network version: 28.0.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | You can now create custom HTML templates for payment links embedded in emails. The templates support merge fields for payment information from standard Business Central Payment Services and allow inclusion of inline images and branding. This enables a more professional and consistent payment experience while ensuring alignment with your company’s visual identity across all payment communications. | 71929 |
| Documents and Templates | The Fallback to Email option on the output profile now works with the new eDocuments flow. When enabled, the system checks whether the recipient is registered in the CDN network before sending. If the recipient is not found, the document is automatically sent by email instead of failing with an error. | 73365 |
| Documents and Templates | A confirmation dialog now appears when sending documents, and it shows the output profile (or “multiple selection”), the selected sending method, and the number of documents being sent. DO Setup now includes Hide Send Action Confirmation to suppress the dialog box. | 74870 |
| Documents and Templates | A new feature module, Enhanced Continia eDocuments, has been introduced. When enabled, this feature replaces the legacy XML Export functionality in Document Output (DO) with the more modern and flexible eDocuments Framework. A new Sender Profile code has been added as a replacement for Document Output's eDocument send code feature. Sender profiles contain all the information required to send electronic documents. For more details, see: Summary of changes to the sales eBilling flow from 2026 R1 | 74978 |
| Documents and Templates | The setup for hiding and showing standard Send actions on pages was previously managed through DO Setup and did not support configuration per category. A new Send Actions Visibility setup with categories and options to hide standard Email, Print, and the Document Output group is now available, with upgrade code that moves existing settings to the new setup. | 75012 |
| General Application | Role Centers that use Document Output have been refactored, and the queues are now separated into their own page to avoid showing them twice. A new Document Queue section now shows the status of documents being sent, printed, or downloaded, and a new Continia Delivery Network section shows the status of outgoing eDocuments, including failed deliveries for easier follow-up actions. | 71286 |
| General Application | The Document Output setup pages have been simplified and improved. Fields are now organized using toggles and conditional visibility, while legacy fields have been hidden to reduce visual clutter. | 72389 |
| General Application | You can now access Document Output menu options directly from the Account Receivables Administrator Role Center, including customer statements, unhandled sales documents, customer cards, and Document Output setup. This improves workflow efficiency for receivables management tasks. | 72937 |
| General Application | Added an OnBeforeGetOutputProfile event publisher to the GetOutputProfile method, enabling custom output profile selection logic based on location, dimensions, or other criteria. You can override the default customer/vendor-based lookup by setting IsHandled, while existing behavior remains unchanged when no subscribers exist. | 74221 |
| General Application | Participation management on the Continia Delivery Network Participation page has been extended with new actions that provide greater flexibility when onboarding and off-boarding participations. Two new actions, Get pre-existing participations and Delete, have been added under Actions > Management. The previous Delete action has been renamed to Suspend and remains available in the same location on the action bar. The following actions are now available:
| 74304 |
| General Application | When copying a company in Business Central, all participation-related data is now removed from the newly created company, ensuring a clean database without duplicates. | 74309 |
| General Application | Test capabilities for eDocuments and Continia Delivery Network have been enhanced to support more flexible and realistic testing scenarios. Onboarding and document exchange can now be tested in sandbox and on-premises environments without being restricted to test mode, including integration with external test networks. Test mode handling has been simplified and centralized in Continia eDocuments Setup, ensuring consistent behavior for participation creation, lifecycle management, and visibility. Additional improvements include the ability to upload XML files directly to the Continia Inbound Documents page for testing purposes, as well as clearer separation of test and production data. | 74489 |
| General Application | The email compose and preview experience has been redesigned with a modern interface that aligns with standard email layouts, delivering a more intuitive, streamlined, and user-friendly experience. | 75148 |
| Platform and Technology | The Shared Access Signature (SAS) and Microsoft Entra ID authentication types have been added as configuration options to the Azure Blob Storage document storage type in the Document Output Setup page. For more information, see Setting up Azure Blob Storage. | 73309 |
| Platform and Technology | Support for custom URLs (private endpoints) has been added as a configuration option to the Azure Blob Storage document storage type in the Document Output Setup page. For more information, see Setting up Azure Blob Storage. | 74702 |
| eDocuments | The eCandidates functionality has been enhanced with several improvements.
| 69665 |
| eDocuments | Configuration of participation and electronic format on the Customer Card, Vendor Card, Continia eDocuments Customer Setup, and Continia eDocuments Vendor Setup pages has been updated. Instead of selecting values in the Electronic Format and Send From Participation fields, configuration is now handled through the new Sender Profile field. The Electronic Format and Send From Participation fields remain available as non-editable information fields, reflecting the values defined in the selected sender profile. Selecting the Sender Profile field opens the Sender Profiles page, where electronic format and sender information are maintained. This page can also be accessed directly through search. | 74600 |
| eDocuments | The eDocuments XML structures have been updated to align with Document Output's XML export formats for OIOUBL invoice and credit note exports. For more information, see XML structure changes in Document Capture 2026 R1 (only available to partners). | 74877 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | When using merge fields %4 (last statement code) and %7 (next statement code) in customer statement templates, statement numbers were inconsistent between the generated file name and the email body. Statement numbers now remain consistent across document outputs by using session-based merge field caching. | 66858 |
| Documents and Templates | When sending documents using templates that merge many/large PDF attachments, the queue stopped and documents were not sent when the merged file exceeded the size limit, causing the following error:
| 73008 |
| General Application | When you clicked No in the Post and Send/Print confirmation dialog for service invoices, service credit memos, and service orders, the document was still sent or printed. The document is now only sent when posting is confirmed and successfully completed. | 72982 |
| General Application | When using email templates with a specific report ID configured, request pages could appear during write transactions. This has now been fixed, and the IsInWriteTransaction() check is applied consistently across all report execution paths. | 74254 |
| General Application | Previously, when opening a posted purchase invoice or credit memo, the following error could occur:
| 75306 |
| eDocuments | Previously, when importing the OIOUBL XML structure configuration, related network profiles had to be mapped manually. Without this mapping, exporting eDocuments could fail. Network profiles are now automatically mapped to the XML structures during import. | 75968 |