Detailed changelog for Continia Document Capture 2026 R1 incl. CDN
This article lists all new updates, features, service packs, and hotfixes for Continia Document Capture 2026 R1 and 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 Capture 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.
Tip
As a Continia partner, you can be notified of new Document Capture versions and service packs when they're released. To sign up for this service, go to Receive a notification upon new Document Capture releases in the Continia PartnerZone (only available to partners).
Vigtigt
Document Capture 2026 R1 supports the following version of Microsoft Dynamics 365 Business Central: Business Central 2026 R1 (v28).
Document Capture 2026 R1, Service Pack 2
Release date, online: June 1, 2026
Release date, on premises: June 1, 2026
Document Capture version: 28.2
Continia Delivery Network version: 28.2
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | A new field, Process Document Type, has been added to the Document Category Card. This field controls how PDF and XML files are handled during import when both file types are attached to the same email. Depending on the selected option, either one or both file types are processed, while unprocessed file types are added as attachments. For more information, see Working with paper and PDF documents. | 53232 |
| Documents and Templates | The message shown when changing the value in the header field No. in the document journal has been updated for clarity. It now guides users to review potential changes in Accounts for Amounts, as values such as VAT posting groups and posting descriptions could be overwritten. For more information, see Accounts for Amounts. | 57954 |
| General Application | Integrating Sustainability with Document Capture has been simplified through a new guide available in Assisted Setup. Completing the guide automatically adds the required sustainability fields to all purchase document master templates. For more information, see Setting up the Sustainability integration. | 69401 |
| 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 the fact 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 guides, existing number series in Continia eDocuments Setup are now preserved. Previously, importing a configuration file could overwrite number series already configured in the setup. | 71223 |
| eDocuments | The automatic downloading of inbound eDocuments can now be enabled, disabled, and scheduled at a configurable interval from the Continia eDocuments Setup page. | 76910 |
| eDocuments | Some vendor bank account numbers contained spaces and exceeded the length of the Bill-to Account No. field. As a result, the recognized bank account number could be truncated during XML document recognition. The Bill-to Account No. field length has been increased from 30 to 50 characters, allowing the full bank account number to be stored. | 75301 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | Document actions could remain disabled after changing the Status Filter and clearing filters in the document journal. | 67954 |
| Documents and Templates | When the Document Storage Type field in Document Capture Setup was set to File Service and Process PDF files with XML Files in the document category was enabled, importing ZUGFeRD files could fail because the XML file path was not created when no TIFF file was present. The import now uses the correct temporary file path for XML/CXML files so the MetaDoc file path is created and ZUGFeRD imports work as expected. | 74228 |
| Documents and Templates | The following only applies to the Spanish (ES) localization. The duplicate vendor invoice number check in the document journal now filters vendor ledger entries by document date instead of posting date, aligning with standard Business Central functionality. | 74882 |
| Documents and Templates | When capturing document data in the document journal, template scoring could cause a template with fewer matching search texts to be selected over a more suitable template. The template with the highest number of matching search texts is now selected when using Recognize Fields. | 77211 |
| Documents and Templates | Previously, when selecting Resource or Allocation Account in the Translate to Type document line field on the document card page, the following error message could be displayed:
| 78264 |
| Document Approval | When opening the Purchase Approval Request Entries or Purchase Contract Approval Request Entries page from Approval Entries by Approver, functionality introduced in Document Capture 28.0 unintentionally removed the filters on these pages. As a result, all approval entries were displayed regardless of status or due date. The filters are now applied correctly, ensuring that only open and/or overdue approval entries are shown. | 78271 |
| General Application | Previously, XML attachments containing tab characters in the attachment element (for example, EmbeddedDocumentBinaryObject) could not be opened after import. | 75413 |
| General Application | When the amount including VAT on a purchase allocation differs from the total amount including VAT on the corresponding purchase invoice due to rounding, the rounding difference is now automatically distributed proportionally across the allocation lines. This applies when Allow VAT Difference is enabled in Purchases & Payables Setup and the difference falls within the threshold defined by Maximum Allowed Difference Incl. VAT in General Ledger Setup. | 76707 |
| General Application | When entering 0 in the Retention Period (Years) or GDPR Retention Period (Years) fields in Document Capture Setup, the following error could occur:
| 78192 |
| 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, running the CTS-CDN Upgrade Metadata Job job queue entry could cause the metadata upgrade to fail with the following error:
| 77406 |
| Purchase Contracts | Creating a purchase contract line using a G/L account with an incomplete VAT posting setup could result in the following error:
| 77185 |
| Purchase Contracts | The following applies to installations where the Business Central Sustainability app is installed and configured. When registering a purchase document that was matched line-by-line to a purchase contract, the following error could occur:
| 77659 |
| Purchase Documents | Previously, unrelated attachments could appear on sales orders because the attachment FactBox did not filter on the Created Doc. No. field. The FactBox now only shows attachments related to the selected sales order. | 65673 |
| Purchase Documents | When using the Get Order Lines action on purchase invoices, purchase order lines with negative quantities were previously filtered out and could not be selected. | 74217 |
| Documents and Templates | When recognizing a document in Document Capture using the eDocuments framework, having multiple master templates within the same document category could result in the following error:
| 71422 |
| eDocuments | Previously, when a production environment was copied to a sandbox, Test Mode was not automatically enabled in Continia eDocuments Setup. As a result, the Continia Delivery Network Participations page could not be opened, and document exchange operations (for example, posting or sending invoices) could fail with the following error:
| 77474 |
| eDocuments | The FA(3) KSeF document viewer now displays the invoice currency in the Do zapłaty and Do rozliczenia fields. Previously, these fields always displayed PLN regardless of the invoice currency, which could result in incorrect currency information for foreign-currency invoices. | 77841 |
| 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, you are prompted to complete the Document Output setup before eDocuments can be sent. | 77988 |
| 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 |
Document Capture 2026 R1, Service Pack 1, hotfix 2
Release date, online: May 22, 2026
Document Capture version: 28.1.2
Continia Delivery Network version: 28.1.2
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Document Approval | When submitting documents for approval using approval flows, and approval sharing was active, approving a purchase invoice as a shared-to user not included in the approval flow could result in the following error:
| 78340 |
Continia Delivery Network 2026 R1, Service Pack 1, hotfix 2
Release date, online: May 18, 2026
Document Capture version: 28.1.1
Continia Delivery Network version: 28.1.2
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| eDocuments | After upgrading eDocuments from version 27 to version 28, validation errors could occur due to missing configuration upgrade changes related to document creation. In these situations, errors similar to the following could occur:
| 76795 |
Document Capture 2026 R1, Service Pack 1, hotfix 1
Release date, online: May 5, 2026
Release date, on-premises: May 6, 2026
Document Capture version: 28.1.1
Continia Delivery Network version: 28.1.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | Bank account numbers could be incorrectly identified as not matching when comparing captured values with the Bank Sort Code and Bank Account No. on the vendor account bank card. This occurred when the account number contained leading zeros that were structurally significant (for example, branch 1234 and account 0056789 compared with captured value 12340056789). | 77718 |
Document Capture 2026 R1, Service Pack 1
Release date, online: May 1, 2026
Release date, on-premises: May 4, 2026
Document Capture version: 28.1.0
Continia Delivery Network version: 28.1.0
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Order and Receipt Matching | Previously, when using the Create Line on Purchase Document action on the Match Lines page, only one order line could be created at a time. It is now possible to select multiple captured lines and create corresponding purchase order or return order lines in a single action. | 58617 |
| Order and Receipt Matching | Standard Business Central order matching actions introduced in BC 28.0 are hidden when using Continia Document Capture. When Document Capture is active, the standard Business Central Get Order Lines and Matched Order Lines actions (along with their corresponding columns) are hidden on purchase invoice and posted purchase invoice lines to avoid duplication with Document Capture’s order matching functionality. Users can continue to use the dedicated Document Capture matching experience without interference from standard Business Central features. | 76809 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | Previously, the Capture Only Match setting on field rules was not enforced when values were captured via AI recognition or key-value pair matching on PDF invoices. If a field rule was configured to capture only values matching a specific pattern (e.g.: a project number format), the rule could be ignored, resulting in incorrect or unfiltered values being stored. The rule is now applied consistently across all capture methods, ensuring that only matching values are captured. | 71811 |
| Documents and Templates | Previously, when using the Create Vendor or Create Customer action in the document journal, clicking the Open PDF action opened the document preview in a reduced size, making the content difficult to read. | 72285 |
| Documents and Templates | Previously, copying a template marked as default could result in multiple default templates for the same source. Copied templates are no longer set as default. | 74618 |
| Documents and Templates | Previously, the Capture Only Match setting on field rules was not enforced when processing XML documents. As a result, fields could be populated even when the captured value did not match the rule’s pattern (e.g.: a six-digit order number). | 75110 |
| Document Approval | When using approval flows configured with All to First Qualified, documents could previously be approved and released beyond assigned approval limits under certain forwarding conditions. | 72345 |
| Document Approval | When opening the Purchase Approval Request Entries page from Approval Entries by Approver, refreshing the page in the web browser (Ctrl + F5) removed all system-applied filters, causing all approval entries to be displayed regardless of the approver. | 75366 |
| General Application | Previously, sending an email with more than 200 characters in the subject line could result in the following error during document import:
| 76845 |
| Platform and Technology | Previously, upgrading Document Capture to version 28.0 could fail with the following error:
| 77135 |
| Purchase Documents | Attachments from posted purchase receipts were incorrectly shown on posted purchase invoices with matching document numbers. | 65613 |
| Purchase Documents | When downloading an attachment from a posted document (invoice or credit memo), the internal storage filename was used instead of the original filename. This affected environments using Azure Blob Storage or File Service as the document storage type. | 75171 |
| eDocuments | The VAT ID type retrieval logic in eDocument creation has been updated to use the vendor’s country/region code instead of the company’s country/region. The PartyLegalEntity node now correctly reflects the supplier’s national scheme. | 76390 |
| eDocuments | Customers with the status Connected in Document Capture were incorrectly shown as Can Connect on the eCandidates page after upgrading to version 28.0. | 75960 |
Document Capture 2026 R1, hotfix 1
Release date, online: April 23, 2026
Document Capture version: 28.0.1
Continia Delivery Network version: 28.0.0
| Functional area | Description | ID |
|---|---|---|
| Platform and Technology | Previously, upgrading Document Capture to version 28.0 could fail with the following error:
| 77135 |
Document Capture 2026 R1
Pre-release date, online: March 20, 2026
Release date, online: April 1, 2026
Release date, on-premises: April 15
Document Capture version: 28.0.0
Continia Delivery Network version: 28.0.0
Vigtigt
Due to security measures recently introduced by Microsoft, outgoing HTTP calls from Business Central to internal addresses are blocked by default. Therefore, customers with on-premises setups must take action to continue accessing the Continia Web Approval and the Continia File Service. For more information, see Anti-SSRF security measure blocking access to the Web Approval Portal and Continia File Service.
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | The following only applies to the Swiss (CH) localization. When recognizing documents, search texts now always take precedence over other identification methods. Previously, vendor (and template) identification through the IBAN from the QR code would bypass the search text identification step. | 68861 |
| Country and Regional | The following only applies to the United States (US) and Canadian (CA) localizations. When importing documents in Document Capture, there can sometimes be a difference between the sales tax amounts imported from the vendor document and the amounts calculated in Business Central. To prevent the need for manual handling of such differences, a new setting – Allow automatic update of tax amount – has been added to the General Ledger Setup page. This setting enables the automatic adjustment of tax amounts when registering purchase documents. When Allow automatic update of tax amount is enabled, the assigned tax amount is automatically adjusted to match the imported tax amount – provided that the difference between Assigned Amount Incl. Tax and Imported Amount Incl. Tax on the purchase document is within the Maximum Allowed Difference Incl. Tax defined in general ledger setup, together with Allow Tax Difference in the Purchases & Payables Setup page. The tax difference amount is distributed across all tax lines in the document’s statistics page, but only for document lines that contain tax. Users can still make manual adjustments if needed. When both Max. Tax Difference Allowed and Maximum Allowed Difference Incl. Tax in the general ledger setup are defined, the lower value of the two is used as the maximum allowed difference. This setting is enabled by default for new installations of Document Capture. For existing users upgrading to this version, the setting is disabled by default but can be enabled manually if this behavior is desired. For more information, see Automatic amount validation. | 70531 |
| Documents and Templates | It is now possible to create document lines of type Comment when recognizing invoice lines. This allows descriptive information – such as notes or text-only lines – to be captured and transferred during registration. Comment lines can be created from recognized or manually entered descriptions, and, when applicable, Business Central standard text codes can be applied as line description translations. For more information, see Capturing line fields in a document. | 46265 |
| Documents and Templates | The Discount % line template field was missing in the purchase OIOUBL master template. | 53753 |
| Documents and Templates | When the recognized bank account number in the Vendor Bank Account header template field contained leading zeros, validation could fail due to mismatched account number formatting. | 60349 |
| Documents and Templates | The option field Amount Validation has been added to the sales master template. | 65548 |
| Documents and Templates | When dimensions in Business Central are renamed, any related header or line fields in Document Capture templates are now renamed accordingly. | 68709 |
| Documents and Templates | Previously, when updating a purchase order in the Purchase Order category, template line fields configured with a destination field in the Transfer Value to... section on the General FastTab had no effect. These template field settings are now supported during order updates, allowing values to be transferred to the corresponding purchase order. | 69798 |
| Documents and Templates | To support standard Business Central functionality, the Allow automatic update of VAT amount setting in the General Ledger Setup now requires the Allow VAT Difference setting to be enabled on the Purchases & Payables Setup page. When both Max. VAT Difference Allowed and Maximum Allowed Difference Incl. VAT in the General Ledger Setup are defined, the lower value of the two is used as the maximum allowed difference. The VAT difference amount is distributed across all VAT lines in the document’s statistics page, but only for document lines that contain VAT. Users can still make manual adjustments in the statistics page if needed. For more information, see Automatic amount validation. | 70046 |
| Documents and Templates | Previously, duplicate invoice checks were only performed against registered or posted invoices. Duplicate detection now also includes documents in the document journal. A configurable comment is displayed when another open document with the same vendor and invoice number exists, and multiple comments are shown if duplicates are found across different stages. | 71251 |
| Documents and Templates | The document import functionality has been improved to ensure that processing continues even if one or more documents encounter errors during recognition or processing. Files must be in a valid format (i.e.: PDF or XML) to be processed. Files with an invalid structure are skipped, while all valid files continue to be imported and processed. An error is logged to identify the affected documents, and manual intervention is required. | 71357 |
| Documents and Templates | The following only applies to the Australian (AU), Belgian (BE), German (DE), New Zealand (NZ), and Worldwide (W1) localizations. Previously, values in business ID fields (i.e.: VAT Reg. No., ABN No., Enterprise No., and Registration No.) were only generated and maintained for vendors. With this release, the same logic now applies to customers, ensuring consistent identification of the document source across both master data types. | 74908 |
| Document Approval | Previously, when opening a document from an approval entry (e.g.: the Purchase Approval Entries page), it was possible to navigate to the next or previous documents based on the current approver’s filter. Now, opening a document from an approval entry only opens that specific document. Navigation to other documents is no longer available. This change was introduced to optimize performance when accessing documents through approval entries. | 68941 |
| Document Approval | Previously, when exporting users and no email account was configured, the error message provided no direct guidance. The error message has now been improved to include a Set up Email action, allowing direct access to the Email Accounts page to configure the required email account. | 72341 |
| Document Approval | The Approvals Permissions and Approval User Groups actions were unintentionally removed from the User Setup by Company page, and have now been restored. | 72857 |
| General Application | The Document Capture group on the Explore More Roles page has been extended to include further relevant links. | 60196 |
| General Application | A Don’t show this again action has been added to the imported documents notification, allowing users to permanently dismiss it during future imports. | 62030 |
| General Application | The CDC Basic permission set is no longer added during Document Capture configuration for users whose permissions are managed by security groups. | 72717 |
| General Application | When exporting documents and attachments, files are now organized into structured folders. Each vendor has a dedicated folder containing the original document and its related attachments. Within each folder, documents are grouped into subfolders based on their status (e.g.: unregistered, registered, or posted), making it easier to locate and manage exported files. For more information, see Exporting attachments. | 74359 |
| 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 on the Document Capture Setup page. For more information, see Setting up Azure Blob Storage. | 43474 |
| Platform and Technology | To enhance security, the following table fields have been moved to isolated storage to prevent direct access from outside the application:
| 59370 |
| Platform and Technology | Support for custom URLs (private endpoints) has been added as a configuration option to the Azure Blob Storage document storage type on the Document Capture Setup page. For more information, see Setting up Azure Blob Storage. | 59380 |
| Platform and Technology | Microsoft Graph is now supported as an email protocol option when using on-premises OCR. For more information, see Setting up email protocols and Creating and configuring email addresses for document import. | 69644 |
| Purchase Documents | The Description field on the Standard Amount Distribution Code Card page has been extended to support up to 100 characters. | 68830 |
| Purchase Documents | Digital voucher handling introduced in Document Capture 12.2 ensures that, when Enforced Digital Vouchers is enabled, a digital voucher is automatically created when registering a purchase document or journal entry. This functionality has now been extended to prepayments. When registering a prepayment in Document Capture, the attached PDF and any drag-and-drop attachments are automatically transferred to the digital voucher before posting. This ensures compliance with digital voucher validation and prevents errors caused by missing attachments. | 69928 |
| Purchase Documents | When registering purchase documents where a standard amount distribution code is applied, blank description values on the distribution code now default to the captured description from the document lines. | 73024 |
| eDocuments | 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
| 74304 |
| eDocuments | 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 |
| eDocuments | Test capabilities for eDocuments and the 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. For more information, see Setting up Continia eDocuments. | 74489 |
| eDocuments | Multiple purchase orders can now be sent as eDocuments in a single action by selecting multiple records on the Purchase Orders page and using the Send action. | 73281 |
| eDocuments | Configuration of the 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. Clicking 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 |
| eDocuments | Several improvements have been made to the eCandidates functionality.
| 69665 |
Bug fixes
All relevant bug fixes released in service packs and hotfixes up to Service Pack 3, hotfix 1 for Document Capture 2026 R2 (27.00) are also included in Document Capture 2026 R1 (28.00). The description of these bug fixes is not repeated on this page.
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | When using a Peppol or other XML-based template, it was not possible to use the Match Vendor Order No. and Match Vendor Shipment No. matching settings on the Template Card. This improvement only applies to newly created templates. | 65874 |
| Documents and Templates | On the Template Field Card, the settings Change Sign and Make Absolute Number are now interdependent. Enabling Make Absolute Number automatically disables Change Sign, and attempting to enable Change Sign fails if Make Absolute Number is already enabled. | 66019 |
| Documents and Templates | The validation of accounts for the header amount fields has been updated. The check now depends on whether line recognition is enabled. If line recognition is enabled, validation is only performed when Transfer Amount to Document is set to Always. If line recognition is disabled, validation is performed when Transfer Amount to Document is set to Always or If lines are not recognized. | 68426 |
| Documents and Templates | When using brackets in the Translation From field in line translations, the following error message was shown during field recognition:
| 69042 |
| Documents and Templates | When a template field in a formula referenced the DOCTYPE template field, the value remained empty. Also when manually updating a field, the change did not carry through to other fields where the current field was part of the formula. | 69054 |
| Documents and Templates | The G/L Account Field Code field on the Template Field Card is now automatically hidden when the field Transfer Amount to Document is set to empty. In addition to hiding the G/L Account Field Code field, its value is also cleared. | 69659 |
| Documents and Templates | Previously, using the Create Vendor action while processing a document in the Purchase Order category could trigger the following error message:
| 70251 |
| Documents and Templates | Previously, documents were not correctly split because the identification template only applied the first matching caption (e.g.: VAT Reg. No. or VAT Registration No.) across all pages. The recognition process now evaluates all configured captions per page, ensuring that documents are correctly split when different VAT registration numbers are identified. | 70587 |
| Documents and Templates | Using the New action on the Document Categories page now opens the Document Category card, allowing entry of all required information instead of creating a line directly in the list. This change prevents issues where not all fields were visible due to missing prerequisites when creating a document category from the list. | 70853 |
| Document Approval | When registering a credit note matched to a purchase return order or posted return shipment, the Line Amount (Order) was incorrectly displayed as zero in the Purchase Approval Entries. | 66588 |
| Document Approval | Shared approval entries listed on the Purchase Approval Entries page are now correctly sorted. | 69079 |
| Document Approval | When extensions added custom values to the Deferral Calculation Start Date enum, and such a value was used in a deferral template (with Deferral Code enabled in Document Capture Setup/Continia Web Approval), opening a document in the Web Approval Portal could result in the following error:
| 70474 |
| Document Approval | When the setting Can Edit Posting Lines was enabled in Continia User Setup, the No. field in purchase invoice lines of type fixed asset could not be changed while the document was pending approval. | 75818 |
| General Application | Email data is now correctly removed when the storage type is changed. Previously, if an email contained more than one document, the removal was not performed. | 59956 |
| General Application | Previously, when using the Export Attachments functionality with the Export Related Documents option enabled, only captured purchase invoices were exported – while other associated attachments were not included. | 72801 |
| General Application | Previously, after applying a filter in the document journal and refreshing the page (F5) or performing a hard refresh (Ctrl + F5), the Document Category title and the Vendor and Name columns could disappear. These elements are now correctly restored after reloading the page. | 73066 |
| General Application | The following only applies to the Swiss (CH) localization. When registering a Swiss QR-bill for a vendor with multiple existing vendor bank accounts, a duplicate bank account code could be generated – resulting in the following error message:
| 73145 |
| Order and Receipt Matching | Previously, when using the Get Order Lines... action on the purchase invoice page a second time on the same line, the following error message appeared when posting the invoice:
| 68151 |
| Order and Receipt Matching | When importing multiple multi-page receipts for the same purchase order into the Purchase Order category, the document viewer did not behave correctly. Selecting a document and navigating to the previous, next, first, or last pages could cause the viewer to jump to a page from a different document instead of continuing within the selected document. | 72383 |
| Purchase Contracts | The Open Purchase Contract action is now available on invoices created from a purchase contract. | 69135 |
| Purchase Documents | When the posting date of a purchase order was outside the Allowed Posting From and Allowed Posting To period defined in General Ledger Setup, it was not possible to post a purchase invoice matched to the purchase order using batch posting. Manual posting was not affected by this restriction. | 70208 |
| Purchase Documents | When using the Get Order Lines action multiple times on a purchase invoice, quantities are now handled correctly when purchase order lines are imported repeatedly and adjusted manually. Previously, this could result in incorrect updates to the Quantity Invoiced field on the purchase order lines. | 72361 |
| Purchase Documents | Previously, registering a Swiss QR-bill could trigger the following error due to the purchase header being retrieved again during QR data transfer:
| 73796 |
| Purchase Documents | Improved the visibility of drag-and-drop attachments on credit memos, including the correct display of the number of attachments on the document card. | 74163 |
| eDocuments | When a template field was configured to capture from an eDocument table field (such as eBilling or eOrder header and line tables), and invalid filters were applied, the following error message was displayed:
| 70929 |
| eDocuments | Filters on sources (typically vendors and customers) defined on the document category were not applied when identifying the source on XML documents using business identification fields. This could result in blocked vendors being recognized on documents. | 75106 |
| eDocuments | When opening an FA(3) XML document in the Web Approval Portal, the styled view was only partially displayed. | 75446 |
| 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 |
| eDocuments | Previously, when opening a posted purchase invoice or credit memo, the following error could occur:
| 75306 |