Detailed changelog for Continia Document Output 2026 R2, including CDN

Added support for multiple variant criteria on a template line, so a single template can route documents on a combination of fields, such as location and department, instead of one variant field.

When a document is sent, the line matching the most criteria is used, with Priority and then line number settling ties, and a line without criteria acting as a catch-all.

Existing templates are upgraded automatically, and variant values now work regardless of the language the setup was made in.

You can read more about the new feature here: Multiple variant fields in templates

Added automatic processing of invoice responses in Document Output.

When a recipient accepts or rejects an electronic invoice sent through the Continia Delivery Network, the response is now processed automatically, and the status on the sent invoice is updated accordingly.

Rejection responses and orphaned responses are visable from the Role Center in the new cue eDocuments Requiring Attention.

You can now share a single Azure Blob container across multiple companies in Document Output by storing each company’s blobs in its own folder, matching Document Capture’s layout.

Existing setups are unaffected and keep the current flat layout with no data moved.

Added a new Automations section to the Document Output Setup page, where you can enable or disable Document Output's background jobs and see their current status without leaving the setup page.

The section covers the email queue, customer statement, and invoice response jobs.

Receiver IDs used when sending eDocuments through the French e-invoicing 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 eDocuments 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. Once a suffix type is available, it can be selected for the relevant customer or vendor.

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:

• Set and update the scenario flow on custom document records.
• Open the Record Coding Values page for a record.
• Copy scenario values between records.
• Validate that required header and record values have been populated.
• Transfer scenario coding from unposted to posted documents during posting, consistent with standard Business Central documents.

The Scenario Flow and Record Coding Value tables and their related enums are also available to extensions.

Standard Business Central sales, purchase, and service documents are unaffected and continue to work as before.

On the Unhandled Issued Reminders page, clicking the value in the Email Log column did not open the email log because the drilldown link was inactive.

This has been fixed, and the Email Log value now opens the Document Output Log filtered to the selected issued reminder.

When using Move up on the first entry or Move down on the last entry in Email template recipient setup, an error occurred.

These actions are now handled correctly so no error occurs at the top or bottom of the list.

When Do not send if negative balance was enabled, automatic due date statements were sent to customers with negative balances.

This has now been fixed, and the customer balance is checked before sending due date statements to match the behavior of automatic period statements.

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.

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 Force Refresh Cache enabled.

Previously, when performing a lookup on the Participation field on any eDocuments Setup Card page, the following error could occur if the new eDocuments experience was disabled:

• The supplied field number '70' cannot be found in the 'Participation' table.

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.

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.

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.