Detailed changelog for Continia Document Output 2026 R1, including CDN

An eReport now remains open for changes until it is sent, and eReports can be processed and sent directly from the eReports list. The following changes have been made:

• A document posted after its reporting period has been processed will be added to that period's eReport. An eReport that was already approved returns to the Ready for Approval status, so the change can be approved.
• The next reporting period starts only after the eReport has been sent.
• The new Process References action on the References page and the eReports list processes references on demand.
• The new Send action on the eReports list sends all approved eReports that are due, not only the selected one.
• The Rejected status is renamed to On Hold and the Reject action to Hold. The Reopen action is now also available for eReports with the On Hold status and returns them to Ready for Approval.

An eReport can no longer be sent before its reporting period has ended. In which case, the following message is displayed:

• eReport <No.> cannot be sent until its reporting period has ended. The period ends <Period End Date>.

Added support for the French Factur-X format across sending and receiving processes. This update introduces support for handling Factur-X documents, including the associated PDF invoice file:

• Added support for sending Factur-X PDF documents through the Continia Delivery Network.
• Extended network document storage to support PDF attachments alongside XML content.
• Added support for downloading and storing incoming Factur-X PDF files when receiving electronic documents.
• Improved document recognition and processing of incoming Factur-X documents through Document Capture.
• Ensured that received Factur-X PDF files are now stored on the corresponding purchase documents, allowing users to access and view the original invoice PDF directly from Business Central.
• Added a preconfigured FACTURE-X output profile to simplify the setup of the Factur-X electronic format.

Onboarding a participation in the Continia Delivery Network was previously done in a single guide that collected the legal company information and the network registration in one go, and could register the company in only one network at a time. Onboarding has now been split into a company onboarding and a network registration, and both are new.

Company identity is now verified up front by our new company onboarding solution, which is a prerequisite for registering in a network. It collects the legal company information and obtains the signatory's approval. The same onboarded company can be registered in several networks, and companies that trade under more than one name can register a participation under an alternate company name.

Network registration is now done in a new onboarding assisted setup, which you open from Network Participations > Create Participation. If no company has been onboarded yet, Start Company Onboarding takes you to the company onboarding, and the assisted setup continues with the network registration afterwards.

You can now join both your domestic network and the international network in one run, each with its own identifier and its own Publish in Registry setting. Instead of selecting individual document types, you select a Business Role that describes whether your organization sells, buys, or both, and the assisted setup derives the document directions from it and offers the document flows that the selected networks support. Using Advanced Setup is still available if you would rather configure the network profiles and their roles directly.

The assisted setup is delivered in a separate extension, Continia Delivery Network Onboarding, which is automatically installed and requires Continia Document Capture or Continia Document Output to be activated before it can be opened. Participations registered before the update are migrated automatically, so no manual re-registration is needed.

You can read more about our new participation onboarding process in Setting up the Continia Delivery Network.

When the statement email template’s open-documents output was set to a single PDF, clicking Open Email on the Document Output Customer Card could fail for customers with many open documents, with the following resulting error:

• Could not perform post request to https://EUN-pdfapi.continiaonline.com/api/v1.0/pdf/merge.json — Status code: 422 — Message: Combine - LoadFromStream1 caused an error. Status: GenericError, Page: 0.

This has now been fixed.

When selecting multiple posted sales invoices and using the standard Send action to send them as eDocuments, the following error occurred:

• You can not call this function with this variable type.

This has now been fixed, and multiple selected documents are now sent correctly in one action.

When sending a sales invoice or sales credit memo, any comments on the business document are included into the OIOUBL xml file in the Note field in the document header. This release fixes two issues in this regard:

• Having multiple comment lines in the business document could lead to multiple instances of the Note class in the xml file. This would be flagged as either a warning or error when sending the document.
• Comment lines were never exported on sales credit memos.

When you chose the assist edit on the eDocuments Scenario Flow field on a posted document, such as a Posted Sales Invoice and the scenario flow carried no special payer type, the following error occurred:

• The eDocument Scenario Header Value does not exist. Identification fields and values: Source Table ID='<Table ID>',System ID='<System ID>'

When opening Show Error Details in the Document Output log for entries created by a user with a different language setting, the following error occurred:

• 'Factuur' is not an option. The existing options are: Invoice,Credit Memo.

Error details now display correctly regardless of the language of the user who created the log entry.

When sending emails using the Azure App or Azure User E-Mail sending method, the following error could intermittently occur:

• - InvalidAuthenticationToken - Lifetime validation failed, the token is expired.

Document Output now determines the token expiry directly from the sign-in response, so sending is no longer affected by time zone or daylight saving changes, and an isolated extra sign-in on a mailbox’s first send after installing the update is expected.

The following only applies to the French (FR) localization. Previously, the VAT declared for a payment in Flow 10.2 and Flow 10.4 was selected by posting date, so the declared amount could be missing or counted twice when the payment date differed from the invoice date, or when several payments settled the same invoice on the same date.

The VAT is now matched to the individual payment application, and unapplying a payment declares the VAT taken back as a negative amount, so that a payment and its reversal cancel each other out.

The following only applies to the French (FR) localization.

Previously, the amounts reported for payments in the F10.2 and F10.4 eReports were too low, because only the VAT part of each payment was included instead of the full amount paid. Payments are now reported with their full amount, including VAT.

Previously, the XML structure for French UBL credit notes was mapped to the wrong network profile, which caused the following error when sending credit notes:

• You're trying to send an electronic document to Customer <Customer No.>, but you're not registered to send this type of document. Your participation: PA France - <Participation Identifier> Electronic document: French UBL Credit Memo (EXTENDED-CTC-FR)

When a sales or service invoice or credit memo was sent as an XML document and a discount was entered in Line Discount % on the lines, the discount percentage was missing from the exported document, only the discount amount was included. The percentage was read from Line Discount Calculation, which stays empty on posted documents when the discount is entered as a percentage. The line discount percentage is now exported for PEPPOL BIS3, XRechnung and OIOUBL documents, together with the base amount it applies to.

The document level discount percentage is now exported, both percentages are calculated from the exported discount and base amounts. For OIOUBL the value is written as a factor, and for PEPPOL BIS3 and XRechnung as a percentage, as each format requires.

Resolved an issue that prevented document header comments to be exported correctly in the follow combinations of XML format and business document type:

• OIOUBL: sales credit memo, service invoice, and service credit memo
• CII: sales credit memo, service invoice, and service credit memo
• Peppol: service invoice

The change is only relevant for XML Export (not eDocuments)

When you onboarded to the PA France network, the onboarding assisted setup guide required you to upload a signed plateforme agréée (PA) designation form before you could continue to the participation information. This step has been removed from the assisted setup guide, and the form is no longer submitted as part of the participation registration.

Onboarding to the PA France network now continues directly from the network selection to the participation information, so you no longer need to prepare and sign the designation form before setting up the participation.

When trying to send a lifecycle update document in the CDAR format for the PA France network, the following error was displayed:

• The sender role is missing for the document type Application Response in the network profile France CDAR.

The Peppol identifier format for new Danish (0184) participations has been updated to comply with the Peppol eDEC codelist requirements. When you register a new Danish Peppol participation, Business Central now sends the 8-digit CVR number directly, without adding a DK prefix.

This change ensures compliance with the upcoming PEPPOL-COMMON-R042 schematron rule, which requires Danish identifiers under scheme 0184 to use the 8-digit-only format.

Existing participations that were previously registered with the DK prefix are not affected and continue to work as before.

For eDocuments sent through the Peppol network, sender and receiver identifier endpoints are now sourced from their authoritative records. The sender identifier is read as-is from the participation record in Business Central, and the receiver identifier is retrieved from the Continia Delivery Network lookup at send time.

Previously, Business Central could reformat or transform Peppol identifier values before writing them into the eDocument XML. With the PEPPOL-COMMON-R042 rule now enforcing an 8-digit-only format for Danish (0184) participations, local formatting risked producing non-compliant documents. Identifier values are now passed through without modification.

For other networks, such as Nemhandel, identifier sourcing is unchanged.

A new Manually Import NSeI Documents setting has been added under the new eDocuments Bridge - IT Integro FastTab on the Continia eDocuments Setup page.

When enabled, NSeI documents are no longer imported automatically. Instead, you import them manually using the Import to Continia eDocuments action on the NSeI Incoming Documents page. When disabled (default), documents continue to be imported automatically, as before.

In previous versions of Document Capture and Document Output, each product brought a selection of tiles to a number of Role Centers. From this version forward, these controls have been replaced by a new common activity eDocuments group.

The following tiles are included in this release:

• Documents requiring attention will contain a list of all business documents that in different ways need manual follow up. The list provides easy access to the business document, the eDocument, as well as any validation errors associated with the document. Entries on the list can be cleared manually for optimal house keeping. Documents will surface here if they:

  • Failed schematron validation during sending.
  • Failed transmission on the network.
  • Get a business rejection from the receiver.
• In Process shows all outgoing network documents with the status "In process".
• Sent Last Week is the list of outgoing network documents sent over the last week.

When the Sender Profile was missing in both the Output Profile and Customer Setup (or Vendor Setup), the system incorrectly showed the following error:

• XML Structure Setup is empty.

The validation now shows an actionable error, which allows users to navigate directly to relevant Output Profile or Customer Setup (or Vendor Setup) pages, where the Sender Profile is missing.

Whenever you open the Participations page, Business Central now also synchronizes participation identifier values from the Continia Delivery Network. If an identifier value has been updated on the network side – for example, to comply with updated Peppol format requirements – your local participation record is automatically updated to reflect the current value.

This ensures that your Business Central records stay in sync with the Continia Delivery Network without any manual intervention.

When registering an incoming PEPPOL Order Response against a purchase order using a Document Capture template set to Update Order, the supplier’s promised delivery date was captured but not applied to the purchase order’s Promised Receipt Date on the header or lines.

Registration now updates the purchase order’s Promised Receipt Date from the response’s promised delivery period. Furthermore, the possibility to Create Template Field on the template and apply it to the purchase order has been added.

When a document had multiple attachments with the same file name, sending electronic documents failed with the following error:

• record already exists / Der Datensatz … existiert bereits

Attachments with duplicate names are now embedded correctly, with a number added to distinguish them.

When opening Continia Solution Management on on-premises installations where Document Output was installed but not licensed or activated, users without Document Output permissions got a permissions error:

• Die aktuellen Berechtigungen haben die Aktion leider verhindert. (CodeUnit 6175299 CDO Functions Execute: Continia Document Output)

This has now been fixed, and Continia Solution Management opens correctly regardless of which Continia permission sets are assigned.

When you ran Copy Document on purchase or sales documents, the following error could occur and the copy was aborted:

• The changes to the Purchase Header record cannot be saved because some information on the page is not up-to-date. Close the page, reopen it, and try again.

This has now been fixed, and Copy Document no longer fails in companies where Document Output is installed but not activated.

Previously, all eDocuments blob files were stored in the Business Central database, which could significantly increase the database size over time in environments with high document volumes.

eDocuments files can now be archived to Azure Blob Storage. The archive location and retention period can be configured in Continia eDocuments Setup. Eligible documents, including files attached to existing documents, are automatically moved to the selected storage by a scheduled background task while remaining accessible.

For more information, see Setting up Continia eDocuments.

Previously, when sending a sales invoice as an eDocument where the assigned payment terms had a blank Description field, the following error could occur:

• The record in table Payment Terms already exists. Identification fields and values: Header Table No.='0',Header Type='0',Document No.='',Document Line No.='0',Entry No.='0' .

Previously, when the self-billing feature was enabled and a customer was assigned a custom country/region code, the following error could occur when sending eBilling documents:

• <Country/Region Code> is not a valid option.

Previously, when applying a Related Field ID in Source Field Mappings for eDocument business term codes in the scenario framework, the following error could occur:

• Microsoft.Dynamics.Nav.Runtime.NavKeyRef variable not initialized.

Previously, exporting a Peppol eDocument from a sales document could fail when the Order No. field was populated and the External Document No. field was left empty, resulting in the following error:

• The content model does not allow element cbc:SalesOrderID to appear as the first child.

Previously, when using the Post and Send action to send sales orders or sales invoices as e-documents, the following error could occur:

• The document exchange service is not enabled.

Support for onboarding to the PA France network has been added to Continia Delivery Network.

The Continia Delivery Network Onboarding assisted setup now guides users through selecting the PA France network, uploading the required PA designation form, entering the required identification information, confirming company details, and selecting the applicable profiles.

Onboarding to the PA France network is available only when Continia Document Capture (FR) or Continia Document Output (FR) is installed.

Continia eDocuments now supports the French electronic invoicing legislation (réforme de la facturation électronique).

Available as a beta release, French customers can send, receive, and report compliant electronic invoices through Continia's certified Plateforme Agréée (PA) directly from Business Central.

The beta release includes:

• Onboarding to the PA France network, including upload of the signed PA designation form.
• Sending and receiving structured invoices in UBL 2.1 and CII using the French EXTENDED-CTC-FR profile (based on EN 16931 / AFNOR XP Z12-012).
• Support for the mandatory lifecycle status updates required by the French Continuous Transaction Controls (CTC) model.
• eReporting for transactions outside the e-invoicing scope, including B2C and cross-border B2B transactions.

Support for Factur-X (hybrid PDF/A-3) is planned for a future release.

For an overview of the functionality included in the beta release, see Understanding eInvoicing in France.

When accessing the CSC Feature Management page in an on-premises environment, the following error occurred:

• The current permissions unfortunately prevented the action. (CodeUnit 6175279 CDO Module Manager Execute: Continia Document Output)

This has now been fixed.

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.

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.

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.

In certain cases, executing the CTS-CDN Upgrade Metadata Job job queue entry could cause the metadata upgrade to fail with the following error:

• The current permissions prevented the action. (TableData 6086245 CTS-CDN Configuration Setup CDN Setup: Modify: Continia Delivery Network)

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:

• The selected Output Profile <Output Profile> is not configured for eDocuments. Please select a different Output Profile.

Now, a sender profile is no longer required on the output profile when connecting eCandidates.

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.

When the following chain of events occurs:

1. A customer uses e-document (such as PEPPOL or OIOUBL) with batch queue processing (not manual single sends)
2. Multiple documents are queued and processed in the same session
3. One queue entry fails (most commonly because the referenced document was canceled or deleted between queuing and processing)
4. A subsequent entry is processed successfully

– the successful entry after the failure may pick up the XML from the last successfully processed entry before the failure, resulting in the wrong customer's e-document being attached.

This has now been corrected, so that the proper XML is sent for each queued document.

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:

• Get pre-existing participations
  - Retrieves a list of participations that are already registered in CDN based on the current client credentials.

  Note

  The list excludes:

  • Participations already created in the current company
  • Participations created in other companies within the same environment
• Suspend
  - Disables the participation in both the local company and CDN .
  - If the participation has status Draft, it is removed from both Business Central and CDN.
  - For all other statuses, the participation is suspended
• Delete
  - Removes the participation record from the current company without notifying CDN.
  - The participation remains unchanged in CDN (demo or production), provided it has already been registered.

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.

The eCandidates functionality has been enhanced with several improvements.

• Refreshing eCandidates for customers and vendors is now performed using two reports, enabling scheduling and filtering of which records to include.
• It is now possible to refresh individual eCandidates.
• The refresh of the eCandidates list can now be configured to update receiving capabilities from external sources.
• Various minor adjustments related to the merged eDocuments and Document Output functionality.

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:

• The data does not represent a valid JSON token/.

The merge handling now prevents this failure for oversized merged attachments, so that document sending no longer stops the queue.

Previously, when opening a posted purchase invoice or credit memo, the following error could occur:

• Unfortunately, The current permissions have prevented the action. (CodeUnit 6225559 CTS-CDN eDocument Feature Execute: Continia Delivery Network)