Detailed changelog for Continia Document Capture 2025 R1

This article lists all new features and bug fixes for each version of Continia Document Capture 2025 R1.

Tip

As a Continia partner, you can be notified of new Document Capture versions and service packs whenever they're released. To sign up for this service, go to Receive a notification upon new Document Capture releases in the Continia PartnerZone.

Bemærk

Starting with Document Capture 2025 R1, the configuration files and the Continia Web Approval Portal are no longer included in the download package for Document Capture. However, you can find links to download the Web Approval Portal and the configuration files (per localization) within the installation package. The configuration files can also be downloaded directly from Document Capture.

Vigtigt

Document Capture 2025 R1 supports the following versions of Microsoft Dynamics 365 Business Central: Business Central 2025 R1 (v26), Business Central 2024 R2 (v25), and Business Central 2024 R1 (v24).

Document Capture 2025 R1, Service Pack 2

Release date, online: June 25, 2025
Release date, on-premises: June 25, 2025
App version: 26.2.0

New or changed functionality

Functional areaDescriptionID
Documents and TemplatesWhen deleting a vendor, any unused templates associated with that vendor will also be deleted automatically – provided that the user has the necessary permissions to delete templates. If not, only the vendor will be deleted.50687
Documents and TemplatesWhen using the Move to Company action in the document journal, the window for selecting the destination company and category now only shows the Display Name of the destination companies – and not the company name. If a company's display name is not configured, the company name is shown instead.65052
Order and Receipt MatchingWhen using unit of measure-based purchase order/receipt matching, the Invoice Matching and Credit Memo Matching pages have been improved with the following:
  • The base quantity and base unit cost values are displayed for purchase orders, purchase return orders, posted purchase receipts, posted return shipments, and document lines.
  • The standard quantity and unit cost fields for purchase orders, purchase return orders, posted purchase receipts, and posted return shipments can be shown or hidden using the Show Qty. and Unit Cost or Hide Qty. and Unit Cost actions.
64931
eDocumentsLine discount amounts are now automatically recognized when importing electronic orders and order changes.65802
eDocumentsWhen processing an order response that updates an existing purchase order – and the order is in a status other than Open –, you are 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
eDocumentsPreviously, when updating the Electronic Format field in the Continia Customer Setup or Continia Vendor Setup, the Send From Participation field retained its value. To prevent invalid configurations, Send From Participation is now intentionally reset when the Electronic Format field is modified.66547
XML ExportAdded support for payment discounts in XML export when exporting electronic documents from sales invoices and service invoices.66305

Bug fixes

Functional areaDescriptionID
Documents and TemplatesPreviously, attempting to open the document journal could result in the following error if security filters were applied to a customer or vendor:
  • A security filter has been applied to table <Table Name>. You cannot access records that are outside of this filter. Page document journal has to close.
Now, users with security filters applied can still open the document journal and view all documents. However, limited access to vendors or customers will restrict which documents can be recognized or processed.
57402
Documents and TemplatesPreviously, applied line recognition suggestions would not reappear if they were later manually reset. Now, various suggestions to improve line recognition continue to appear as long as the document values prompt a suggestion and the suggestion has not been explicitly disabled.59831
Documents and TemplatesPreviously, the act of registering either partially or completely matched documents could be blocked due to the following error comment:
  • No Account has been configured for <template field Amount Excl. VAT/GST/Tax>.
60850
Documents and TemplatesPreviously, capturing a negative amount value could cause an error if the Change Signoption on the Template Field Card was enabled.62307
Documents and TemplatesPreviously, when recognizing FIK codes, an incorrect value could be returned if the leading characters were incorrect. Attempting to fix the value manually could sometimes cause the last eight digits to be changed incorrectly. Now, the last eight digits always match the last eight digits of the recognized series.63625
Documents and TemplatesWhen using the Create/Select Template action in the document journal, it was possible to choose blocked templates. Now, you are only presented with eligible templates.64321
Documents and TemplatesIf the currently selected template or all templates for the vendor are blocked, a new template is now created when using Recognize Fields in the document journal.64385
Documents and TemplatesPreviously, it was possible to register a document that had an account type specified – but no account number – on the Accounts for Amounts page.64522
Documents and TemplatesWhen registering a purchase document with an invoice discount amount to the general journal or the purchase journal, the following error message was displayed:
  • The Purchase Header does not exist. Identification fields and values: Document Type='Quote',No.=''
An error is now displayed in the comment section before registering the document, stating that registering an invoice discount amount to a journal is not possible:
  • The Invoice Discount Amount cannot be registered in the journal.
64743
Documents and TemplatesNow, when selecting Move to Company in the document journal, the list of destination companies only includes companies that have Document Capture configured.64978
Documents and TemplatesPreviously, when using the Create Vendor action in the document journal, the recognized and suggested VAT number for the new vendor could in some cases be the VAT number of the receiver. Now, the VAT number field is left empty if the document value captured is the same as configured in the company information.65562
Documents and TemplatesThe document line field was not populated during document recognition when the When Value is Empty setting on the template field card was set to Copy value from previous line, Copy value from header field, or Copy value from line field.65830
Documents and TemplatesThe following only applies to the Swedish (SE) localization.

One of the options in the Item Charge Assignment Method field on the template card was incorrectly translated to Efter mängd. It's now correctly translated to Efter belopp.
66321
Documents and TemplatesWhen the Check Item Prices setting was enabled in the template card to validate item sales and purchase prices, the currency code in the document header was ignored – resulting in item prices being calculated based on the local currency.66509
Documents and TemplatesThe template header field Due Date was unintentionally left empty when the currency code was not recognized and LCY Code in the General Ledger Setup was also empty.66747
General ApplicationPreviously, when executing the storage migration process, it was possible to create a job queue entry without the necessary permissions – which caused the migration to fail without notifying you. Now, you can only initiate the storage migration process if you have the required permissions.64138
General ApplicationWhen the Check Item Prices setting was enabled in the template card to validate item sales and purchase prices, prices specified in the sales price list or purchase price list were not considered. Instead, it used the item price from the Item Card.65711
General ApplicationThe following only applies to the Belgian (BE) localization.

When creating a customer or vendor using the Create Customer or Create Vendor actions, the Enterprise No. was not transferred accordingly.
66002
General ApplicationWhen a customer or a vendor was deleted, the following error could occur:
  • Your changes cannot be saved at the moment because a record in the table ‘CDC All Record Tree Relation’ is being updated in a transaction that is executed by another session. You must wait until the other transaction is completed. This may take a while. Please try again later.
67215
Order and Receipt MatchingWhen matching a purchase invoice to a purchase receipt and registering the document as a new invoice, attachments from the purchase order – shown in the standard Business Central FactBox – were not transferred to the created purchase invoice.62312
Order and Receipt MatchingThe translations of the terms Match Base Quantity and Match Base Unit Cost have been updated on the Invoice Matching page for Danish, Finnish, and Norwegian (Bokmål) localizations.65328
Order and Receipt MatchingWhen adding line translations for sales or purchase items on the document card, the Base Unit of Measure value from the Item Card was applied instead of the Sales Unit of Measure or Purch. Unit of Measure.65647
Platform and TechnologyPreviously, when running the Import Files function, the following error message could occur:
  • The length of the string is 1091, but it must be less than or equal to 1024 characters. Value: The request to Continia Online failed.
    Http error: 502 - Message:
61206
Purchase DocumentsUsing Create, Cancel, or Create Corrective Credit Memo on a purchase invoice that was posted directly from a purchase order caused a large number of documents to be attached to the new document. This functionality has now been rolled back to its previous behavior: no attachments are copied to the new document when performing any of these actions.67175
Documents and TemplatesPreviously, when moving a ZUGFeRD document to another company using the Move to company action in the document journal, any attachments to the document would be lost.63087
eDocumentsA translation error in the Norwegian (NO) localization prevented the options in the Value Operation dropdown menu from appearing.65483
eDocumentsPreviously, it was not possible to open the Outgoing Network Documents page in solutions activated with demo credentials – such as cloud sandboxes or the demo portal.66263
eDocumentsWhen importing a document with multiple tax specifications on the document lines – each with the same tax percentage, tax category ID, and tax scheme ID – the following error was shown:
  • The record in "VAT Specification" already exists. Identification fields and values: <record primary key fields>
64022
eDocumentsThe following adjustments have been made to the eOrder creation process:
  • The /BuyerCustomerParty/EndpointID node now includes the country code in the eOrder XML.
  • The DueDate node is now included in the XML to prevent a schematron validation warning. It is populated based on the purchase order Due Date field.
65224
eDocumentsPreviously, the item number was not exported to the cac:BuyersItemIdentification element in the OIOUBL order XML structure. Now, the item number is correctly included in the OIOUBL order lines, ensuring valid XML structure for compliance and downstream processing.65858
eDocumentsPreviously, a 0 (zero) VAT percentage was not applied to the eOrder and eOrder change XML eDocuments. Now, 0% VAT is correctly included where applicable.66199
eDocumentsPreviously, when re-registering an order after the original had been deleted, the corresponding order response could not be processed due to the missing original order ID – and the following error occurred:
  • The Sales Header does not exist. Identification fields and values: Document Type='Order', No.=<Order No.>
66256
eDocumentsThe MultiplierFactorNumeric XML element, which represents the discount percentage, is now included in electronic orders.66257
eDocumentsLocal eDocument identification fields – such as Enterprise No. (BE) and ABN (AU) – are no longer imported into localizations where the corresponding fields are not present on the related source records.66366
eDocumentsThe following only applies to the Belgian (BE) localization.
Previously, vendor identification using the Enterprise No. in eBilling documents did not function as expected. This has been adjusted to improve the processing of eDocuments.
66464
eDocumentsIt is now possible to specify IBAN payments in OIOUBL electronic invoices, which was unintentionally blocked.66473
eDocumentsAdded missing tooltips to several fields on the eDocument Customer Setup page.66825
eDocumentsAllowance charges were missing in OIOUBL order lines, which could lead to incomplete or non-compliant order documents. Now, allowance charges are correctly included in the generated OIOUBL order lines.66970
XML ExportPreviously, eDocuments for sales invoices and credit memos containing comment type lines could generate incorrect tax totals. 65765

Document Capture 2025 R1, Service Pack 1, hotfix 2

Release date, online: May 30, 2025
App version: 26.1.2

Bug fixes

Functional areaDescriptionID
Purchase DocumentsWhen attempting to cancel a posted purchase invoice, the following error could occur:
  • App Document Capture is not activated.
66573
Documents and TemplatesWhen importing documents using a job queue, the following error could occur:
  • Microsoft Dynamics 365 Business Central Server attempted to issue a client callback to show a selection menu: (Table 6085579 CDC Template). Client callbacks are not supported on Microsoft Dynamics 365 Business Central Server.
66824

Document Capture 2025 R1, Service Pack 1, hotfix 1

Release date, online: May 27, 2025
App version: 26.1.1

Bug fixes

Functional areaDescriptionID
Purchase DocumentsWhen attempting to register a purchase order, the following error could appear:
  • The length of the string is xx, but it must be less than or equal to 80 characters. Value: <text>: <Document No.> Order No.: <Order No.>
64497

Document Capture 2025 R1, Service Pack 1

Release date, online: May 14, 2025
Release date, on-premises: May 14, 2025
App version: 26.1.0

New or changed functionality

Functional areaDescriptionID
eDocumentsThe Network Profile field on the XML Structure Setup page has been replaced by the Supported by Network Profiles field, which opens the updated Network Profiles page. This page allows you to tweak the prioritization of network profiles, and ensures that the top profile in the list is automatically selected.

Additionally, wildcard profile matching has been implemented to support scenarios where the recipient’s exact profile identifier is unknown. This ensures that the correct profile (wildcard or exact) is selected when sending documents in the PINT format (e.g.: PINT A-NZ).
64224
eDocumentsSupport for the PINT and PINT A-NZ Billing BIS formats has been added. The PINT A-NZ specification becomes mandatory for eInvoicing in Australia and New Zealand on 15 May 2025, replacing the A-NZ Peppol BIS 3.0 format – which is no longer supported.

For more information, see Understanding PINT and PINT A-NZ for eInvoicing in Australia and New Zealand.
62709
XML ExportThe 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:
  • Item net price MUST equal (Gross price - Allowance amount) when gross price is provided.
Comment lines containing a VAT posting group selected in the CII invoice/credit memo lines no longer result in an incorrect tax category being specified in the XML files.

The External Document No. field now appears in the CII invoice/credit memo XML files when it contains a value.
64933

Bug fixes

Functional areaDescriptionID
Documents and TemplatesPreviously, when using the Change Category action for an XML documents in the document journal, the following error could occur:
  • File Type must be equal to 'OCR' in Document: <Document No.> Current value is 'XML'.
Additionally, if the assigned category is incorrect, an error comment is now shown:
  • The assigned document category does not support this document. Please use the 'Change Category' action to move it to the <Document Category Code> category.
65717
eDocumentsPreviously, importing OIOUBL electronic documents that included line discounts could result in an incorrect unit price being captured.63275
eDocumentsWhen sending an order confirmation in the OIOUBL format where the Ship-To Country/Region Code was empty, the following error could occur:
  • The Country/Region does not exist. Identification fields and values: Code=''
64231
eDocumentsPreviously, when moving an unregistered eDocument to another company, an error could occur.64686
eDocumentsWhen sending an electronic Peppol document for a posted invoice containing lines with a quantity of 0, the following error was shown:
  • Attempted to divide by zero.
64881
eDocumentsPreviously, when exporting an OIOUBL XML document, a source document line with a unit of measure different from the base unit and a quantity per unit of measure other than 1 resulted in incorrect values in the XML file. The invoice line price amount was inaccurate, and the base quantity was set to the quantity per unit of measure.

Now, the base quantity is correctly set to 1, and the price amount reflects the price of a single item in the line.
64977
eDocumentsWhen importing OIOUBL invoice or credit memo responses, the following error could occur:
  • There is no Template within the filter. Filters: Category Code: PURCHASE, Type: Master, Data Type: XML, XML Identification Template: EBILLINGRESP-ID
65445
eDocumentsPreviously, the SenderParty EndpointID and ReceiverParty EndpointID nodes in the Peppol BIS3 and OIOUBL XML structures were incorrectly mapped, resulting in invalid eDocuments.65446
eDocumentsThe price amount node in the PINT and Peppol formats was limited to two decimal places. This limit has now been extended to support up to ten decimal places.65703
General ApplicationPreviously, 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 ApplicationWhen opening the Outgoing Network Documents page, the following error could occur:
  • Current permissions prevented the action.(CodeUnit 6225510 CTS-CDN eDocument Table Mgt. Execute: Continia Delivery Network)
This only applies to on-premises installations.
66285
XML ExportPreviously, 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 GuidelineSpecifiedDocumentContextParameter in the XML file.65200
XML ExportWhen 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 ExportWhen creating ZUGFeRD eDocuments, the following error could occur in some cases:
  • The following fields must be of the same type:
    Field: <from field name> <-- <to field name>
    Table: <from table name> <-- <to table name>
    Type: <from data type> <-- <to data type>
65816

Document Capture 2025 R1, hotfix 5

Release date, online: May 9, 2025
Release date, on-premises: May 9, 2025
App version: 26.0.5

Bug fixes

Functional areaDescriptionID
Documents and TemplatesWhen using the Select/Create Template action in the document journal, the choice of which master template to use when creating a vendor template had unintentionally been disabled.65855

Document Capture 2025 R1, hotfix 4

Release date, online: May 2, 2025
App version: 26.0.4

Bug fixes

Functional areaDescriptionID
General ApplicationOn-premises customers could, in certain scenarios, see the following error when upgrading Document Capture:
  • Could not upgrade the extension 'Continia Document Capture' by 'Continia Software' from version '<from version no>' to '<to version no>' for tenant '<tenant ID>' and company '<company name>' due to the following error: 'Sorry, the current permissions prevented the action. (Codeunit 6086228 CTS-CDN License Mgt. Execute: Continia Document Capture)'.
66135
General ApplicationWhen importing documents, the following error would occur due to a change introduced in Document Capture 26.0:
  • The following C/AL functions are limited during write transactions because one or more tables will be locked.

    Form.RunModal is not allowed in write transactions.

    Codeunit.Run is allowed in write transactions only if the return value is not used. For example, 'OK := Codeunit.Run()' is not allowed.

    Report.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'Report.RunModal(...,FALSE)' is allowed.

    XmlPort.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'XmlPort.RunModal(...,FALSE)' is allowed.

    Use the COMMIT function to save the changes before this call, or structure the code differently.
This change has been revised, and will be reintroduced later when the code is restructured.
66128

Document Capture 2025 R1, hotfix 3

Release date, online: April 28, 2025
App version: 26.0.3

Bug fixes

Functional areaDescriptionID
Documents and TemplatesWhen using the Select/CreateTemplate action in the document journal, the choice of which master template to use when creating a vendor template had unintentionally been disabled.65855
Documents and TemplatesTrying to change the value in the No. field on a purchase line for a document that was pending approval, while the Can Edit Posting Lines setting was enabled in the Continia User Setup, resulted in the following error:
  • Status must be equal to 'Open'  in Purchase Header: Document Type=<Document Type>, No.=<Document No.>. Current value is 'Pending Approval'.
65861
Purchase DocumentsPreviously, attachments copied using the CorrectCancel, or Create Corrective Credit Memo actions on a posted purchase invoice could not be opened from the newly created purchase document.65702

Document Capture 2025 R1, hotfix 2*

Release date, online: April 9, 2025
App version: 26.0.2

New or changed functionality

Functional areaDescriptionID
eDocumentsWhen sending an electronic Peppol document for a posted invoice containing lines with a quantity of 0, the following error was shown:
  • Attempted to divide by zero.
64881
eDocumentsThe following error was shown when running the Document Capture assisted setup:
  • Sorry, the current permissions prevented the action. (TableData 6086242 CTS-CDN eDoc. Payment Means eDocuments Payment Means Insert: Continia Document Capture).
65470

* The preview version of Document Capture 2025 R1 was released as 26.0.0, and the first official version was released as 26.0.1. Hence there's no hotfix 1.

Document Capture 2025 R1

Pre-release date, online: March 21, 2025
Release date, online: April 1, 2025
Release date, on-premises: April 9, 2025
App version: 26.0.1

New or changed functionality

Functional areaDescriptionID
Country and RegionalThe following only applies to the CH (Swiss) localization.

When creating a vendor bank account from a QR code, the following fields are automatically populated from the bank directory:
  • Name
  • Address
  • Address 2
  • City
  • Post Code
  • SWIFT Code
59483
Documents and TemplatesTo align with Business Central standards, the template field Account Type has been renamed to Type, and No. has been renamed to No.
These changes apply to the following pages:
  • Document Journal
  • Document Card
  • Accounts for Amounts
  • Assigned Amount Lines
Additionally, the field Ask to set Default Account No. on the template has been renamed to Ask to set Default No.
47816
Documents and TemplatesWhen selecting the Move To Company action in the document journal, you can now choose both the destination company and the destination category. This allows you to move documents to a different company and category in one step.49658
Documents and TemplatesThe Item Charge Assignment field on the template card is now only displayed when either of the template match invoice/credit memo options is set to match against receipt or return shipment lines.52054
Documents and TemplatesUsing the Create Lines action to create the first allocation line on the Purchase Allocations page could result in allocation lines with an incorrect document type. To prevent this, the Create Line action is now only enabled if at least one allocation line has already been created.53361
Documents and TemplatesWhen selecting the Run GDPR Maintenance action in Document Capture Setup to delete old documents, the associated document log entries are also removed.54731
Documents and TemplatesTo help identify the destination company when moving documents between companies, the Display Name field has been added to the Move to Company page. This field is available through page customization.56703
Documents and TemplatesValidation of Continia Sustainability template header and line fields has been added to the document journal and document card pages. Any validation notifications relating to the sustainability fields are displayed as configurable comments in the Comments section.57494
Documents and TemplatesThe Change Category action in the document journal now allows you to move a document to any category. Previously, you could only move documents between categories with the same Source Record Table ID.59661
Documents and TemplatesWhen changing a document's category by adding the Document Category Code column to the document journal and updating its value, the recognize fields functionality is now automatically activated in the destination category.59665
Documents and TemplatesWhen recognizing document lines using AI, it is now possible to override the AI’s suggested values for the following line fields:
  • Number
  • Description
  • Quantity
  • Unit Cost
  • Line Amount
You can manually capture values either by using the field caption or by selecting a different value directly from the document.
60606
Documents and TemplatesIn Accounts for Amounts, the sustainability fields are only editable when Type is G/L Account or Item.62103
Documents and TemplatesPreviously, opening a PDF file would automatically trigger a download to your computer. Now, PDFs open directly in the Business Central client using the new Business Central 2025 R1 standard feature: Preview PDF attachments directly in the web client. This allows you to view documents instantly, while still having the option to download them when needed.64353
Document ApprovalTo prevent approval blockages in the Web Approval Portal, enabling one of the following Continia approval workflows in the Document Capture Setup automatically creates an approval user group with the code ALL, but only if a group with the same name doesn’t already exist. The group includes all assigning and approval permissions on all types and dimensions.
  • Purchase invoice
  • Purchase credit memo
  • Purchase order approval
  • Purchase return order
45868
Document ApprovalThe settings Enable Order Approval and Enable Return Order Approval have been added to the Purchase Approval Setup assisted guide.49612
Document ApprovalAdded the Document Date field to the Purchase Approvals Entries page.53311
General ApplicationWhen selecting the Perform Document Check action in the document control log, the filter is now automatically set to show only failed lines – if any are identified.55040
General ApplicationRead-links have been added to Continia Document Capture entries on the Business Central Assisted Setup page, providing direct access to the related Continia Docs article.60550
Order and Receipt MatchingIt's now possible to match purchase invoices and credit memos to purchase orders/receipts or return orders that contain lines with the same line amount, even if they have different units of measure and, as a result, different unit costs. For further details, see Setting up order and receipt matching.27261
Order and Receipt MatchingTo clarify the potential impact on Quantity to Receive for unreceived order lines, the message shown when registering a matched purchase invoice to a purchase order that has already been matched has been extended.63587
Purchase DocumentsWhen using the Correct, Cancel, or Create Corrective Credit Memo actions on a posted purchase invoice, any attachment on the posted invoice is now copied to the document created in the cancel/correct process. The files are copied as drag-and-drop attachments.58765
Platform and TechnologyDocument Capture's custom FactBox pane resizing implementation, when running on Business Central 26.0 and above, has been deprecated in favor of Microsoft's latest native implementation.

Note that Microsoft's implementation limits the FactBox pane width to a maximum of 50% of the screen, whereas Document Capture's previous implementation allowed for wider expansion.
64858
eDocumentsThe new Payment Means feature provides you with more flexibility when configuring and using payment means in electronic invoices and credit memos.

For more information, see Using payment means in eDocuments.
62706
eDocumentsYou can now use the Create Vendor and Create Customer guides when working with XML/eDocuments received via the Continia Delivery Network.40795
eDocumentsFrom the Outgoing Network Documents page, you can now send copies of previously sent documents. This feature is available for eDocuments with the status Successful – and only for electronic document formats that support the Copy Indicator node. Currently, only the OIOUBL format supports it.

When using the Resend action, an eDocument record is created in the Continia Delivery Network, and the document copy is sent automatically. Additionally, a new Copy column has been added to the Outgoing Network Documents page to indicate that the sent eDocument is a copy.
55339
eDocumentsThe Document Receipts FactBox has been added to the eDocument Overview page.

A new field, Document Receipt Status, has been added to the following pages. This field displays the document's latest receipt status, allowing you to track its receipt state directly from the eDocument card.
  • eBilling Outgoing Document Card
  • eBilling Response
  • eOrder Document
  • eOrder Response
56152
eDocumentsThe following only applies to the DK (Danish) localization.

In the newer versions of Business Central, a notification could appear in the Role Center informing you that the company hasn't been registered in the NemHandel network – even if a participation was previously approved through Continia. To remove the notification, open the Continia Delivery Network Participations page containing the approved NemHandel participation.
56617
eDocumentsThe Skip action has been added to the Import eDocument Configurations step in the Set Up Continia eDocuments assisted guide. This action allows the setup to continue without importing a configuration. If this step is skipped and the setup has not been completed previously, the following error is shown:
  • The setup has failed. Please, restart the wizard and do not skip the configuration import.
60368
eDocumentsThe Set Up eDocuments assisted guide has been added to the standard Business Central Assisted Setup list.60369
eDocumentsThe following only applies to the BE (Belgian) localization.

The eDocuments source identification by enterprise number has been added to the following Document Capture templates.

EORDERCANCEL-ID (eOrder Cancellation - Ident.)
EORDERCHANGE-ID (eOrder Change - Identification)
EORDER-ID (eOrder - Identification)
EBILLING-ID (eBilling - Identification)
EORDERRESP-ID (eOrder - Identification)
EBILLINGRESP-ID (eInvoice Resp - Identification)
60665
eDocumentsPrior to this, utility statement (UTS) documents failed to be related to the corresponding invoice when the invoice was received using eDocuments.60906
eDocumentsPreviously, when sending a Peppol invoice through the Continia Delivery Network while using the standard payment discount functionality in Business Central, the generated electronic document did not reflect the discounts. Now, the discount amounts are correctly applied in the electronic document.61175
eDocumentsIt's now possible to set all participations within a company to test mode. To make use of this feature, go to the Continia eDocuments Setup page and enable the Test Mode option. When enabling test mode in a company, the following applies:
  • All communication through the Continia Deliver Network is suspended – no documents are received, and no documents are sent.
  • All supported business documents can be resent – regardless of their existing status. Both eDocuments (i.e.: eBilling, eOrder, and eResponse) and related network documents are recreated and marked with the status Test.
  • When a company is copied, all existing participations are put in test mode. This goes for companies created within the tenant using the copy functions on the Companies page or when SaaS environments are copied from the Admin Center.
61704
eDocumentsThe field Handle Incoming eBilling Docs has been added to the Continia eDocuments Setup page. This field specifies whether incoming electronic documents of type invoice or credit memo should be processed using the eDocuments feature.61800
eDocumentsTo support A-NZ Peppol BIS3 in Australia and New Zealand, two new XML structures have been added:
  • ANZPEPPOLBIS3CRMEMO - A-NZ Peppol BIS3 Credit Memo
  • ANZPEPPOLBIS3INV - A-NZ Peppol BIS3 Invoice
62091
eDocumentsThe XML Structure View page layout has been restructured to improve the user experience:
  • Fields which should not be edited (such as Sequence) have been moved to the FactBox as information. 
  • Fields which are edited less often (such as Line Node and Business Term) have been moved to the FactBox. These can be modified with the use of the new action Modify Details, under the Actions group.
62923
eDocumentsDisabled network profiles and participation ID types are now hidden, and cannot be selected or used for sending eDocuments. This ensures only active metadata is used, improving data integrity and compliance.63748

Bug fixes

All relevant bug fixes released in service packs and hotfixes up to Service Pack 2, hotfix 1, for Document Capture 2024 R2 (25.00) are also included in Document Capture 2025 R1 (26.00). The description of these bug fixes is not repeated on this page.

Functional areaDescriptionID
Country and RegionalPreviously, when creating a vendor from a PDF, recognized country codes with more than two characters would block the vendor creation.58737
Country and RegionalPreviously, the VAT Bus. Post. Group column on the Accounts for Amounts page was incorrectly translated in the Swedish localization to Moms produktbokföringsmall. It's now correctly translated to Moms rörelsebokföringsmall.62311
Country and RegionalA missing English localization has been added for the Delete Blanks field on the Template Field Card page.64951
Documents and TemplatesCaptions have been removed for the template template line field Order No. as lines fields are only recognized through manual marking. Therefore, the captions serve no purpose.45900
Documents and TemplatesWhen importing multiple files, a field recognition failure in one document prevented subsequent documents from being recognized.48432
Documents and TemplatesWhen using the drop shipment feature on a purchase order line, attempting to update the order quantity from the Purchase Order category would result in the following error:
  • Quantity on line cannot be updated. The line is linked to purchase order line , which is associated with sales order .
54332
Documents and TemplatesWhen reopening a registered document in the Contact category, the created interaction log entry remained on the contact – which could result in the document being registered multiple times. This issue occurred because the reopen codeunit was missing from the category card. A new codeunit has been added to ensure that previously registered data is cleared when reopening the document, preventing duplicate registrations.57119
Documents and TemplatesWhen capturing a value containing an operator character (such as | or &), the following error could sometimes occur due to incorrect handling of line translation values: 
  • The filter "..." is not valid for the Translate From field on the Data Translation table. The right side of '|' operators cannot be empty.
57901
Documents and TemplatesPreviously, capturing a value that contained certain special characters (such as \) would result in an "Unrecognized escape sequence" error. This has been adjusted for the following characters: , +, [, ], {, }, ?, (, ), *.58452
Documents and TemplatesPreviously, entering a negative value in the header field Type (née Account Type) would result in the following error: 
  • The SELECTSTR comma-string ,G/L Account,Item,Resource,Fixed Asset,Charge (Item),,Amount Distribution Code,Purchase Contract,Allocation Account does not contain a value for index -49999. Page Document Journal has to close.
Now, entering an invalid value clears the field – leaving it empty.
59880
Documents and TemplatesPreviously, registering a sales document with the same external document number as an existing sales order was not possible, as the registration was blocked by an error comment. To align with Business Central standards, it is now possible to register sales orders with duplicate external document numbers. The comment still appears in the document journal, but it will no longer block registration.61451
Documents and TemplatesIn certain cases, when recognizing purchase document lines that spanned across multiple pages, values from the last line were not captured.62183
Documents and TemplatesPreviously, if two or more master templates existed and none were set as default, the following error message appeared when attempting to create a template via the dialog that opens after selecting Recognize Fields:
  • An error occurred and the transaction is stopped. Contact your administrator or partner for further assistance.
Now, when selecting the Create New action, the first available template is used if no default master template has been configured.
62339
Documents and TemplatesThe template field rule for Belgian VAT registration numbers in the default setup has been updated from (BE)?0[0-9]{9} to (BE)?[0-9]{10} to ensure a correct identification, as the Belgian VAT numbers can begin with 0 or 1.64540
Document ApprovalSpaces have been adjusted in a warning comment related to matching the total amount of purchase receipts.53544
Document ApprovalWhen using the Send Approval Request action for an open purchase document and no workflow was found, the following misleading error was shown:
  • The approval request cannot be sent because the invoice is already pending approval or released.
For open purchase documents, the error message has been updated to:
  • The approval request cannot be sent because no suitable workflow could be found.
55657
Document ApprovalThe following caption and tooltip have been updated on the Document Capture Setup / Continia Web Approval page to better reflect the related functionality:
  • Amounts in LCY => Total amount in LCY
  • Specifies whether to show the amounts on documents in local currency if the document is in a foreign currency. => Specifies whether to show the total amount on documents in local currency if the document is in a foreign currency.
61523
Document ApprovalThe following page captions have been updated to use "- Document Capture" instead of "(DC)":
  • Approval Sharing - Document Capture
  • General Posting Setup - Document Capture
  • Vendor Posting Groups - Document Capture
This change standardizes the naming convention to improve clarity and consistency.
63549
General ApplicationIn certain cases, the Stop Line Recognition setting on the Template Field Card was ignored when capturing purchase document lines using the manual line recognition method. As a result, document lines following the totals were unintentionally captured.61536
General ApplicationWhen using the Create Vendor guide, it is now possible to clear the Country Code and Currency Code fields.64546
Purchase ContractsThe option Purchase Contracts has been removed from the Translate to Type field on the Line Translations page because it wasn't a valid option. The No. action should be used instead.54088
Purchase ContractsPreviously, when registering a purchase invoice with a purchase contract selected as the account type – and the Auto Approve Within Variance setting on the contract was set to No – the invoice could still be automatically released and approved, if other required conditions were met.63447
Purchase DocumentsThe misspelling of registrering has been adjusted to registering in several warning comments.59557
Purchase DocumentsIf a default remit-to code has been configured on the vendor level, the Remit-To Code field on the purchase invoice is now automatically set when registering a document.62426
eDocumentsThe template line field No. has been set to not required on the eOrder Response master template.62437