Detailed Changelog for Continia Document Capture 2024 R1

This article lists all new features and bug fixes for each version of Continia Document Capture 2024 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 this page in the Continia PartnerZone (only available to partners).

Important

Currently, Document Capture supports BC v14 and the three latest versions of Business Central. This will change with the release of Document Capture 2025 R1 (26.00) in April 2025. Document Capture 2025 R1 (26.00) and all future versions from then on will only support the three latest versions of Business Central.

The next version of Document Capture – Document Capture 2024 R2 (25.00) – is the last version with support for Business Central April 2019 (BC v14).

Document Capture 2024 R1 Service Pack 2, hotfix 1

Release date, online: September 26, 2024
App version: 24.2.1.0

Only released in Business Central online.

Bug fixes

Functional areaDescriptionID
Purchase DocumentsThe following error no longer occurs when more than one drag-and-drop category is in use, and you attempt to open a purchase order:
  • The Document does not exist. Identification fields and values: Entry No.='1'
58808
eDocumentsWhen enabling Continia eDocuments from the Continia Feature Management page or running the Continia eDocuments Wizard from search with the Copy and convert existing customer and vendor templates setting enabled, the following error no longer occurs:
  • /???:Invoice/???:PaymentMeans/???:PaymentID[@schemeAgencyID='320'and@schemeID='urn:oioubl:\id:paymentid-1.1']" is not valid for the XML Path field on the XML Structure table. An error occured while interpreting the filter: Did not expect '=
59579
eDocumentsWhen importing an eDocument or using Recognize Fields on it, the following error no longer occurs:
  • The supplied field number '<Field Number>' cannot be found in the '<Table Name>' table.
59408
eDocumentsWhen sending an invoice via the Continia Delivery Network, the following error no longer appears:
  • The length of the string is <Length of string>, but it must be less than or equal to 30 characters. Value: <Value>

Document Capture 2024 R1 Service Pack 2

Release date, online: August 23, 2024
Release date, on-premises: August 23, 2024
App version: 24.2.0
FOB version: 24.02

New or changed functionality

Functional areaDescriptionID
General ApplicationWhen using the standard functionality Merge duplicate records available in Business Central, any Document Capture documents associated with Vendors or Customers being merged are included in the merge process.
Note that moving Document Capture documents is supported in BC 24.00 and newer versions.
54671
Platform and TechnologyEvents have been added to the solution. For details, see Event Publishers for Document Capture 2024 R1 (24.00).55364
Platform and TechnologyThe Continia Web Approval Portal has been updated to version 24.0.3.57382

Bug fixes

Functional areaDescriptionID
Country and RegionalThis change only applies to the BE localization:

In the list of template field Document Type, all captions that previously started with "O:" have been changed to start with "V:".
54471
Country and RegionalIn some localizations, an incorrect Account Type was potentially selected when using the Recognize Fields action.56942
Document and TemplatesWhen using File Service as a Document Storage Type in the Document Capture Setup, the Document Categories were made inaccessible if an imported filename exceeded 100 characters. The following error message was returned:
  • The length of the string is <Length>, but it must be less then or equal to 100 characters. Value: <File Name>.
The filename length has been increased to the maximum length a field can have. 
50565
Document and TemplatesWhen doing line recognition, template suggestions were in some cases unintentionally shown – even if they where previously applied. Accepting the suggestion again produced the error message Record in the table Template Suggestion already exists.55042
Document and TemplatesDuring document import, a new template was wrongly created for the document when there was already a template available in another company for the same vendor. Now, a new template won't be created – and the template number won't be populated in the document journal. Instead, you must run Recognize Fields manually in the document journal. This triggers the following dialog:
  • A template for <Vendor No.> <Vendor Name> has been found in company <Company Name>, do you want to copy this template?
55407
Document and TemplatesWhen the Secure Archive feature was enabled and either Auto Split or Merge From Same E-mail were used, these actions were incorrectly regarded as file changes – resulting in the following error when posting an invoice:
  • One of the files (<Doc No.>) associated with this document has been changed since it was imported. This is not allowed when Secure Archive is enabled.
This error has been removed. Additionally, extra document logging has been added to record the split and merge actions performed, recognizing these actions as accepted.
55986
Document and TemplatesWhen filtering document lines in the Document Card, the highlighted field in the document viewer didn't correspond with the actual line selected in the Document Lines subpage. To address this, the Line No. column is shown on the lines subpage, if not already present, when filtering. The column is removed automatically when the filter is released.56132
Document and TemplatesWhen registering a document in the Contact category using the Register & Show option, the following error message was displayed:
  • The Interaction Log Entry does not exist. Identification fields and value: Entry No.='<Entry No.>'.
56559
Document and TemplatesWhen using document search in environments with XML documents, users could experience a degraded performance caused by unnecessary external calls to Continia Online. These external calls have been removed, resulting in a better search performance.56889
Document and TemplatesThe Sales category Force Register action used to require a value in Account for Amount Excl. VAT. This has been changed, so the Sales category Force Register action works in the same way as the Purchase category Force Register action.57512
Document and TemplatesAttachments weren't displayed when using Find Entries, nor were they displayed in the Documents FactBox and Document Viewer in the General Journal and General Ledger Entries pages.58058
Document and TemplatesThe Document Viewer and Documents FactBox wasn't shown in the General Ledger Entries.58385
eDocumentsThe currency CHF has been added as a Translate From value in the template field translation for all localizations.56774
General ApplicationThese two issues related to attached files have been corrected:
  • The Attachments field on posted documents would, in certain cases, display a different number of attached files than the number of files shown in the list if the attachments page was opened.
  • When registering an invoice in the PURCHASE category with the Match and Update Order register option, the name of that attachment would be "Order xxx". This has been changed to "Invoice (Order xxx)" to make it clearer that the attachment originates from an invoice.
53168
General ApplicationWhen using the Line Capture Version 2.0 codeunit to recognize line values, the auto calculation of missing line values isn't done for zero-values if a zero-value is captured in the document.55041
General ApplicationWhen capturing an MEM entity value longer than 20 characters, the following overflow error message was returned:
  • The length of the string is <Captured Value Length>, but it must be less than or equal to 20 characters. Value: <Captured Value>
Now values over 20 characters are truncated.
56954
General ApplicationWhen switching document storage type from File System to File Service, the following error was returned:
  • The path specified in Archive File Path could not be found. Please check that the folder exists and that you have access to the folder before changing Document Storage Type.
57182
General ApplicationThis change only applies to the AT, CH, and DE localizations' master template BESTELLUNG-DE,CH,AT:
  • Description changed from "Default GB" to "Standard - DE, CH and AT"
  • Language Code changed from "ENG" to "DEU"
57528
Order & Receipt MatchingThis change only applies to the DK localization:

When registering a purchase document with the Payment ID (FIK-kode), using the Invoice Reg. Step 1 setting as Match and Update Order in the Template Card, the Payment Method Code, Payment Reference, and Creditor No. weren't populated in the matched purchase order.
47894
Platform and TechnologyThe field Web Site URL on the Continia Web Portal Card is now hidden, as it shouldn't be used.51051
Platform and TechnologyIf the Show Embedded PDF as Default field is marked but there is no PDF, the HTML is displayed – instead of no visualization at all.57113
Purchase DocumentsWhen registering a purchase document as a prepayment, it was possible to select a fully invoiced purchase order. Now, when selecting purchase orders, the fully invoiced purchase orders are hidden. Attempting to specify fully invoiced purchase order manually results in an error comment, and the registration of the document is prevented.45585
Purchase DocumentsOn a purchase order line, you can now only change its line's Type if the purchase order status is Open or Pending Approval and you're allowed to edit pending documents. Previously, any user could change the line type to comment (which ultimately deletes the line) – even after a document had been released. This left room for mistakes.53734
Purchase DocumentsThe action Change Imported Amounts has been moved to the action group Credit Memo on the the Purchase Credit Memo page.54044
Purchase DocumentsPreviously, the Vendor Create function in the document journal would sometimes return the overflow error The length of the string is XX, but it must be less than or equal to YY characters when the field value was longer than YY.54450
Purchase DocumentsThe Create Digital Vouchers for Document Capture Documents has been added to allow existing customers who chose to enable the Enhanced Digital Vouchers feature to post invoices created before the enabling.

This report identifies purchase invoices that lack an entry in the Incoming Document table. It tries to find a corresponding Document Capture document and copy this to the Incoming Document table.
57521
Platform and TechnologyFixed an issue where the document import could fail, resulting in the following error message:
  • The value "XXXXXXXXXXXXXX" can't be evaluated into type Decimal.
57844
Purchase DocumentsIn some cases when no lines were recognized, the line field values in the created purchase invoice could have been overwritten with false data if the template line field had a value in Field in Purchase Line under the Transfer Value to... group on the General FastTab.53707

Document Capture 2024 R1 Service Pack 1, hotfix 6

Release date, online: August 7, 2024
App version: 24.1.6

Only released in Business Central online.

New or changed functionality

Functional areaDescriptionID
eDocumentsThe field Order Line No. has been added to the eBilling Lines, though by default it's not visible. The Order Line No. is required when sending eDocuments to Dutch customers.57907

Bug fixes

Functional areaDescriptionID
General ApplicationThe following issues have been fixed:
  • The Attachments field on posted documents would in certain cases display a different number of attached files compared to what was shown in the list if the attachments page was opened.
  • When registering an invoice in the PURCHASE category with the Match and Update Order register option, the name of that attachment would be 'Order xxx'. This has been changed to 'Invoice (Order xxx)' to make it clear that the attachment originates from an invoice.
53168

Document Capture 2024 R1 Service Pack 1, hotfix 5

Release date, online: July 18, 2024
App version: 24.1.5

Only released in Business Central online.

Bug fixes

Functional areaDescriptionID
Purchase DocumentsIn Document Capture 24.00 Service Pack 1, hotfix 2 (task ID 56612), changes were implemented to ensure that documents attached to a purchase or sales order are also visible on the corresponding posted invoice.

These changes unwantedly caused documents added to a posted invoice via drag and drop to be attached to the originating order instead.

To address this, the code introduced in the original bug fix (ID 56612) has been removed. A better solution to this issue is being actively sought, but there's currently no estimated release date for the fix.
57907

Document Capture 2024 R1 Service Pack 1, hotfix 4

Release date, online: July 5, 2024
App version: 24.1.4

Only released in Business Central online.

Bug fixes

Functional areaDescriptionID
Documents and TemplatesWhen customers try to upgrade to Document Capture 24.1.3, they could encounter this error:
  • The Continia Company Setup does not exist. Identification fields and values Primary key=
As a result of the errors, the app update is terminated, and nothing has been upgraded.
57539
Purchase documentsDocument preview was missing from the General Ledger Entries when sales or purchase documents were registered in the document journal, and the corresponding sales or purchase documents in Business Central were created and posted.56931

Document Capture 2024 R1 Service Pack 1, hotfix 3

Release date, online: July 3, 2024
App version: 24.1.3

Only released in Business Central online.

Bug fixes

Functional areaDescriptionID
Documents and
Templates
Registering documents in companies, where: 
  • Digital Vouchers are created automatically (Enforce Digital Vouchers), and
  • The field Require Approval To Create set to "Yes" in Incoming Documents Setup 
would produce the following error when registering a document:
  •  This incoming document requires releasing.
57484
Documents and
Templates
When customers try to upgrade to Document Capture 24.1.2, they could encounter these errors:
  • This incoming document requires releasing
  • The Continia Company Setup does not exist. Identification fields and values Primary key=''
As a result of the errors, the app update is terminated, and nothing has been upgraded.
57495

Document Capture 2024 R1 Service Pack 1, hotfix 2

Release date, online: July 2, 2024
App version: 24.1.2

Only released in Business Central online.

Bug fixes

Functional areaDescriptionID
Documents and TemplatesWhen the Secure Archive feature was enabled and either of the following features were used:
  • Auto Split
  • Merge From Same E-mail
These actions were incorrectly regarded as file changes, resulting in the following error when posting an invoice:
  • One of the files (<Doc No.>) associated with this document has been changed since it was imported. This is not allowed when Secure Archive is enabled.
This error has now been removed. Additionally, extra document logging has been added to record the split and merge actions performed, recognizing these actions as accepted.
55986
Purchase DocumentsWhen creating Purchase Order with attachments from the Purchase Order category, the attachments were later not available in the Posted Purchase Invoice.56612
Purchase DocumentsRelevant only to Danish cloud-based production tenants:

With the mandatory enforcement of digital vouchers starting on July 1, 2024, Document Capture automatically generates digital vouchers based on Document Capture files.

Before this date, many customers could have registered documents and created purchase documents without any automatically generated digital vouchers. The posting of these documents is therefore blocked.

When this hotfix is installed, Document Capture searches for all purchase documents in the Purchase Header table and check if they originate from Document Capture. If so, a digital voucher is created.
57438

Document Capture 2024 R1 Service Pack 1, hotfix 1

Release date, online: June 4, 2024
App version: 24.1.1

Only released in Business Central online.

Bug fixes

Functional areaDescriptionID
Documents and TemplatesWhen registering a document, with lines recognized, in the Sales category, the unit price on the created Sales Order or Sales Credit Memo was unintentionally taken from the DC document. This behavior has been changed to use the default sales prices as specified in Business Central.
56645
Document ApprovalAfter migrating from Business Central on-premises to Business Central online, the Delegate to me link in the email could sometimes wrongly point to the old on-premises server, preventing users from being able to open the link.56646
General ApplicationWhen completing the cloud migration, users got the following error:
  • The request to remove the integration runtime failed.
    Do you want to continue with disabling the replication?

    Error:
    The supplied field number '6085618' cannot be found in the 'Document Category' table.
56738
Platform and TechnologyWhen upgrading to Document Capture 24.00, users might encounter the following error:
  • "The length of the string is <length>, but it must be less than or equal to 50 characters. Value: <Field value>
56737

Document Capture 2024 R1 Service Pack 1

Release date, online: May 28, 2024
Release date, on-premises: May 29, 2024
App version: 24.1.0
FOB version: 24.01

New or changed functionality

Functional areaDescriptionID
Documents and TemplatesAdded vendor bank account validation for Australian bank accounts (EFT BSB).40793
Documents and TemplatesThe event OnBeforeSetRetentionPeriod(ToDate,Handled) is added in the codeunit CDC Data Maintenance Mgt. This makes it possible to bypass the 2 year limit on deletion of document words and document values specified in the Retention Perion (Years) field on the Document Capture Setup page 54734
Document ApprovalWhen migrating from Business Central on-premises to Business Central online and utilizing the Web Approval Portal, an invalid configuration could be migrated. This could block the export of users to Continia Online. Now, the web portal configuration is sanitized to make sure that users can be exported to Continia Online.54937
Document ApprovalThe following change only applies to Business Central online.

When exporting users, the current Web Approval Portal setup is validated to ensure that it is supported in Business Central online. If the setup if not supported, the following error is shown:
  • Web portal code <code> is not supported in Business Central Online.
54943
eDocumentsAdded a new job queue entry, eDocuments metadata update, which is scheduled to run once a day at a random time between 06:00PM and 05:00AM. This job queue is used for updating participations and networks metadata. Two new fields have been added to the Continia eDocuments Setup page:
  • Update Metadata Automatically: A boolean field for enabling or disabling the job queue entry.
  • Metadata Update Job Status: A text field showing the status of the job queue entry. Select the field to open the related Job Queue Entry Card.
51250
eDocumentsAdded a new job queue entry, eDocuments document update, which is scheduled to run every 30 minutes. This job queue is used for updating document statuses, download new documents and receipts. Two new fields have been added to the Continia eDocuments Setup page:
  • Update Documents Status Automatically: A boolean field for enabling or disabling the job queue entry.
  • Documents Update Job Status: A text field showing the status of the job queue entry. Select the field to open the related Job Queue Entry Card.
51251
eDocumentsThe following changes have been made when sending Peppol and OIOUBL sales invoices and credit memos:
  • Improved handling of discounts.
  • Improved handling of multiple tax rates.
  • Added support for comment lines.
54789
eDocumentsIntroducing two new fields:
  • Use Document Information for Customer Party on the Customer eDocument Setup page.
  • Use Document Information for Seller Party on the Vendor eDocument Setup page.
When exporting a document, you now have the option to retrieve the customer or seller party details directly from the eDocument rather than from the customer/vendor card.
54901
eDocumentsAdded the action Open Xml File to the following pages:
  • Incoming eBilling Document
  • eBilling Outgoing Document Card
  • eBilling Response
  • eOrder Document
  • eOrder Response
55318
General ApplicationBy enabling the Check Item Prices option on the template in the Sales category, the item's recognized unit cost is validated against the price specified on the item card.

If any special prices or discounts are configured for the item, the price check is conducted against the relevant special price or special discount.

Should the unit cost of the recognized item differs from the special price or unit price calculated from the item card, a warning is displayed in the comment section. If the Line Discount % template line field contains a valid value or a special discount is configured for the item, the discount percentage is included in the unit cost comparison.

47648
General ApplicationWith Binary Stream MEM installed and the entity dimension value was missing in the Document Journal, the following message was shown in the comment section:
  • Multi Entity Company is not specified.
The message has been updated to include fields from the Multi-Entity Management Setup:
  • MEM <Entity Label> is not specified (<Entity Dimension>).
54434
General ApplicationAdded identification rules to the XRECHNUNG-ID XML identification template to support XRechnung version 2.3 and 3.0.
56585
Platform and TechnologyEvents have been added to the solution. For details, please see Event Publishers for Document Capture 2024 R1 (24.00).55364
Platform and TechnologyThe Continia Web Approval Portal has been updated to version 24.2
56581
Purchase DocumentsPreviously, it was possible from a general journal or purchase journal to delete attachments associated to a posted ledger entry having the same document number as the unposted journal entry. Now, it is only possible in the journals to view the attachments that are related to the posted entries.

In addition to the above change, the attachments added to an unposted general or purchase journal with the same document number as the posted entry are viewable from the general ledger entries but can't be deleted.
54349

Bug fixes

Functional areaDescriptionID
Country and RegionalThe following change only applies to the NL localization: When registering a purchase invoice without any setup under Accounts for Amounts, the value in the Doc. Amount VAT field on the purchase invoice was not populated.54763
Documents and TemplatesWhen a document was moved to another company, the OK field in the Document Journal was not cleared.52596
Documents and TemplatesThe field Line Recognition Method was wrongly shown in the Template Card for XML templates.53554
Documents and TemplatesThe following change only applies to the Danish localization:

In order to ensure that the recognized payment id (FIK-kode) is correctly captured, the master template is now configured to validate the payment-id during document recognition.

The codeunit field Is Valid on the template field PAYMENT-ID on all Danish master templates is now pre-populated with codeunit 6085738 CDC Is Valid Payment-Id (DK).
53628
Documents and TemplatesThe field Insert on new Templates was missing on the Template Field Card for the master templates. The field has been added to the page as an additional field and is easily displayed using the Show more action.54126
Documents and TemplatesThe vendor creation guide now doesn't fill in the currency code if the recognized value is identical to the LCY Code configured in the General Ledger Setup page.54231
Documents and TemplatesOptimized the document import processing time by skipping merge operations when templates are not configured to automatically combine PDF files from the same email into one Document Capture document.
54373
Documents and TemplatesFixed an issue with the function Recreate Template, where the vendor relation was lost.
54804
Documents and TemplatesCorrected a bug that caused the Document Log Entries to be sorted in a non chronological way in the Document Log Summary page54831
Documents and TemplatesUsing Document Capture without having an internet connection, the users were presented with the following error when opening the document journal:
  • Client ID must have a value in CSC Client Credential: Primary Key=. It cannot be zero or empty.
54856
Documents and TemplatesFixed an issue where template suggestions was shown on document categories with no AI data.54924
Documents and TemplatesThe following change only applies to the BE localization: The create vendor guide has been changed to use the Enterprise No. field instead of VAT Registration No., if the field is supported.54999
Documents and TemplatesWhen selecting the Add Template Field action on a document that originates from Continia eDocuments, the following error message was shown:
  • The value of INDEXING parameter 1 is outside of the permitted range. The current value is: -1. The permitted range is: from 0 to 2.147.483.647.
55010
Documents and TemplatesAdded support for the template field setting Decimal Separator when using AI for capturing the document lines.55068
Documents and TemplatesIt is now possible to disable the Search for Value option on the Template Field Card page.55122
Documents and TemplatesWhen moving documents to another company, the following error could occur:
  • The length of the string is 11, but it must be less than or equal to 10 characters. Value: <Document No.>
55515
Documents and TemplatesAfter migrating from Business Central on-premises to Business Central Online, users could encounter the following error when trying to open the Document Category page:
  • Metadata object CodeUnit <id> was not found.
56138
eDocumentsWhen using the Find Entries action in the Document Capture Document Card or Document Journal pages for an eOrder or eBilling response, the users were not directed to the related documents.53815
eDocumentsThe eDocument validation conducted before sending the document to the Continia Delivery Network has been improved.53908
eDocumentsWhen sending eDocuments through Continia Delivery Network, the party information values were missing:
  • .../cac:Party/cac:PartyLegalEntity/cac:RegistrationAddress/cbc:CityName
  • .../cac:Party/cac:PartyLegalEntity/cac:RegistrationAddress/cac:Country/cbc:IdentificationCode
54245
eDocumentsWhen an eDocument Response in Continia eDocuments Setup page was configured and the customer or vendor was missing the eDocuments setup, the below error message was shown when sending the eDocument response:
  • You are trying to send a network document ([eDocument format]) to [Recipient Type] [Recipient No.], who is not registered in the network.
Now, if the eDocuments setup for the customer or vendor is missing, automated actions are not executed.
54306
eDocumentsWhen eDocument automation is configured (in the Continia eDocument Setup page, under the eBilling Response group, in the Send In Process field) and an OIOUBL invoice was received, the automation triggered the creation of an invoice eBilling response.  Since the OIOUBL invoice response does not support a response code for a document being in process, the response code value was not assigned to the eDocument. This would generate the following error message when attempting to open the purchase invoice related to the invoice response:
  • The supplied field number '180' cannot be found in the 'eDocument Response Header' table.
Now, before creating the invoice response, eDocuments checks if the response code is supported. If it is not, the response can't be sent.
54307
eDocumentsThe following changes have been made for eOrder responses:
  • When creating an eOrder response from a sales order, the missing value AcceptIndicator for the OIOUBL format, which is based on whether the order is accepted or rejected, has been added.
  • In the creation process of an OIOUBL eOrder Response Simple eDocument, when the attempt to generate response lines was unsuccessful, the following error message was shown: 
    • eDocument Line Action has no translated code list value code for <Line Response Action>.
The system now refrains from creating response lines if the eDocument format does not support them.
  • When recognizing an OIOUBL eOrder Response Simple eDocument in Document Capture the following error was shown:
    • The Code List does not exist. Identification fields and values: ID=''. 
54309
eDocumentsWhen recognizing an eDocument with the Continia eDocuments feature enabled and an XML Structure was not found, the following error occurred:
  • "No XML structure was found for the current XML document"
Now the XML document is handled using the XML Import functionality using the master and identification templates.
54405
eDocumentsAdded improved support for sending eDocuments with multiple VAT rates.54781
eDocumentsSales invoice line comments were not included in the PEPPOL BIS3 Invoice XML node /Invoice/cac:InvoiceLine/cbc:Note.

When a sales invoice header contained multiple notes, these notes were generated in the PEPPOL BIS 3 Invoice XML node /Invoice/cbc:Note. However, this format only permits one note. To comply with the standard, all comments are now merged into a single note, with each comment separated by a line break.
54921
eDocumentsWhen sending an purchase order through Continia Delivery Network using the OIOUBLORDER XML structure, the eDocument validation (eDocument Status -> Actions -> Validation Log) failed with the following error message:
  • "ID is mandatory for line 0". 
In order to solve this issue, import a new Continia eDocuments Setup from Continia Online using the Document Capture Assisted Setup Guide. During the import, only select the actual eDocuments Setup record, not the XML Structure Setup or Electronic Format. Please note, this will overwrite the existing configuration in the Continia eDocuments Setup page.
54989
eDocumentsImporting a Peppol invoice with line discounts would result in the discount not being properly applied to the lines.54994
eDocumentsWhen opening the VAT Subtotals page from the eOrder or eBilling card, only header records are now being shown.
55028
eDocumentsWhen sending an eDocument containing comment lines, the following validation errors occurred.
  • Base Quantity Price is mandatory for line <Line No.>.
  • Line Amount is mandatory for line <Line No.>.
  • VAT Category ID is mandatory for line <Line No.>.
55031
eDocumentsThe discount fields on the eBilling pages have been changed to calculated fields based on the related records in the underlying charge and allowance table.

A new field Source Type has been added to the list of charges and allowances signifying if the record is related to a document line or the document header.
55051
eDocumentsWhen opening the Document Capture role center or the document journal, the values regarding eDocuments in the Ready to Import and Documents for Import cues were incorrect when more than one document category was defined in the Continia Delivery Network participation profiles. 55116
eDocumentsThe fields Translate to Type an Translate to No. on the Discounts and Charges page, available from the eDocument card, have been hidden as they cannot be used.55125
eDocumentsAdded the eDocuments Requiring Attention cue to the Document Capture Activities on the rolecenter.55316
eDocumentsWhen recognizing eDocument in Document Capture using different languages in Business Central the following error appeared:
  • <Another Language Option Value> is not an option. The existing options are: <Current Language Option 0 Value,Current Language Option 1 Value,Current Language Option 2 Value,...>
This was caused when one user created a table field filter in one language and another user would use Document Capture in another language. Read Manually convert table filters in the CDC Table Field Filters to see how you can correct all the table field filters.
55320
eDocumentsWhen creating an eDocument, the following error could occur:
  • The length of the string is <String Length>, but it must be less than or equal to 50 characters. Value: <String Value>
55627
eDocumentsWhen sending an OIOUBL eDocument, you could in some situations experience a Divide by zero error.
55652
eDocumentsWhen sending a Posted Sales Invoice or Purchase Order that has varying VAT percentages on different lines (e.g., 25% and 10%) through Continia Delivery Network, the following error appeared:
  • The record in table VAT Sub Total already exists. Identification fields and values: Header Table No.=<eDocument Header Table No.>Header Type=<eDocument  Header Type>,Document No.=<eDocument No.>,Document Line No.=<eDocument Line No..>,VAT Category Id=<VAT Category ID>
56103
eDocumentsWhen sending multiple electronic billing responses through Continia Delivery Network from a purchase order (by selecting Send Electronic Confirmation and then Send in the eBilling Response page), the eDocument Status from the second response onward was unintentionally set to Failed.
56133
eDocumentsPreviously, when sending an electronic document from a purchase order or a posted sales invoice (by selecting Send..., choosing Through Continia Delivery Network in the Electronic Document field, and then selecting OK), the eDocument Status would change to Failed. This issue has been resolved, and the status and document are now handled correctly.

When opening the page Outgoing Network Documents, the following error appeared:
  • You do not have the following permissions on TableData CTS-CDN Document: Modify.
56143
eDocumentsPreviously, the field eDocument Status on outgoing documents was not updated, if a user with insufficient permissions opened the Outgoing Network Documents page. Now, the needed indirect permissions have been updated.

When updating FOB-based versions, you must run specific codeunits to add the permissions. For details, please see the following article. https://docs.continia.com/en-us/continia-document-capture/development-and-administration/document-capture-permissions#updating-permissions-when-implementing-service-packs
56154
eDocumentsWhen sending an invoice or credit memo as an eDocument, the invoice number in the eDocument was filled in by the eBilling Header No. instead of the Posted Sales Invoice No. or the Posted Sales Credit Memo No.
56179
eDocumentsWhen the Recipient ID was incorrectly set to Sender ID, the invoice response documents were not sent.56181
General ApplicationFor template field DOCTYPE, the English caption for prepayment has been added to the following localizations:
  • AT,BE,CH,DE,DK,ES,FI,FR,NL,NO,SE
48652
General ApplicationWhen running the Export OCR Configuration while using file service as the storage type and without having the on-premises app installed, the EWS secret was incorrectly exported as empty.
52954
General ApplicationThe GDPR Maintenance process has been updated to run exclusively through the standard Document Capture categories only.  The second confirmation now displays the number of documents that will be affected.54360
General ApplicationAll supported languages have been added for the W1 localization on the following pages:
  • Customer Card
  • Customer List
  • Vendor Card
  • Vendor List
  • Sales Order
  • Purchase Order
  • Purchase Invoice
  • Purchase Credit Memo
  • Purch. Cr. Memo Subform
  • Posted Sales Invoice
  • Posted Sales Credit Memo
  • Posted Purchase Invoice
  • Posted Purchase Credit Memo
  • Posted Purch. Cr. Memo Subform
  • Document Sending Profile
  • Select Sending Options
  • Service Order
  • Posted Service Credit Memo
  • Posted Service Invoice
54376
General ApplicationWhen exporting the attachments using the Export Attachments report, the unregistered documents were exported without a name.54701
General ApplicationWhen users opened the Role Center without having an internet connection, they were presented with the following error:
  • A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (auth.continiaonline.com:443) A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
54855
General ApplicationWhen configuring the Document Storage Type as File Service in the Document Capture Setup and the file service failed to respond, opening Document Capture Setup page resulted in the following error message:
  • No connection could be made because the target machine actively refused it. (<Service URL>)
55664
Order & Receipt MatchingPreviously the option fields Match on Vendor Order No. and Match on Vendor Shipment No. were only visible on the template card if the corresponding template header or line  fields were added to the template. This behaviour has been extended to add and show the fields on the template when creating it, if the fields on the master template are configured with the matching option Yes - Always.49102
Order & Receipt MatchingWhen matching a purchase invoice having Prices Including VAT set to Yes against a purchase order having Prices Including VAT set to No, the Direct Unit Cost on the purchase order lines was copied to the invoice lines and was not recalculated (taking into account the VAT amount to be applied).53229
Order & Receipt MatchingWhen recognizing a delivery note for updating the purchase order Quantity to Receive and all document lines were completely matched, a warning was wrongly shown:
  • WARNING: Partial Match
55128
Purchase ContractsPreviously, when registering a document linked to purchase contract and a value was specified in the Deferral Code field under the Accounts for Amounts page, the selected deferral code value was ignored. Now, the deferral code value is assigned to the created invoice/credit memo lines.53937
Purchase ContractsCaptions of the Job No. and Job Task No. fields on the purchase contract lines and purchase contract lines archive have been adjusted to reflect the standard field caption changes since Business Central 2024 R1. Therefore, the fields are renamed to Project No. and Project Task No.54205
Purchase DocumentsThe following change only applies to the US localization.

Having a purchase document with Prices Including Tax set to Yes, the following error message was shown when opening the purchase documents list for orders, invoices, credit memos, and return orders:
  • Prices Including Tax must be equal to 'No' in Purchase Header: Document Type=<Document Type>, No.=<Document No.>. Current value is 'Yes'.
51338
Purchase DocumentsWhen creating general or purchase journal lines from the Document Journal and the Document No. in the journal was changed, the related document (attachment) was not updated with the new Document No. This resulted in either a lost link between the journal lines and the document, or the journal lines was linked to a wrong document.54266
Purchase DocumentsThe warning and error messages in the Comments section in the Document Journal, when auto-matching delivery notes in the Purchase Order category, have been improved. If the quantity in the document line is greater than the quantity in the matched purchase order line, matching will be removed automatically and the following configurable comment will be shown:
  • The quantity (<Document Line Quantity>) on line <Document Line No.> is greater than the matched quantity (<Purchase Order Line Quantity>) on the purchase order.
54350
Purchase DocumentsIn some cases, when trying to add attachments on the General Ledger Entries page using drag & drop, the following error message was shown:
  • You cannot attach a file to the journal line. Document no. and account no. are both required.
54380
Purchase DocumentsWhen selecting the Document Card action in the Purchase Orders page for a manually created purchase order, the eDocuments order response page was in some situations opened. This behaviour was incorrect as the order response wasn't the source of the purchase order.

Now, when using the action Document Card in this scenario, an error message is shown:
  • This Order has not been created from Continia Document Capture.
54543
Purchase DocumentsWhen creating general/purchase journal lines from the document journal and posting them to the general ledger, it was possible to re-open the document by manually creating a general/purchase journal line with the same document number.

When creating general/purchase journal lines from the Document Journal and posting them to the general ledger, the Find Entries action would open a general/purchase journal instead of the General Ledger Entries page.
54957
Purchase DocumentsWhen creating general or purchase journal lines from the Document Journal and changing the Document No. using the Renumber Document Numbers action in the General or Purchase Journal pages, the related document was not updated with the new document number. This resulted in either losing the link between the journal lines and the document, or the journal lines being linked to the wrong document.

Now, the Renumber Document Numbers function will be blocked if there is at least one journal line linked to a document, and the following message will be shown:
  • Renumber document numbers is not allowed when journal lines linked to one or more documents. Please renumber document numbers manually.
54958

Document Capture 2024 R1, hotfix 1

Release date, online: May 1, 2024
App version: 24.0.1

Only released in Business Central online.

Bug fixes

Functional areaDescriptionID
Documents and TemplatesFixed an issue with the function Recreate Template, where the vendor relation was lost.54804
Documents and TemplatesFixed an issue where template suggestions were shown for document categories with no AI data.54924
Documents and TemplatesWhen updating vendor information on the vendor card, users could receive the following message:
  • Sorry, the current permissions prevented the action. (TableData 6085619 CDC AI Record Tree Relation Read: Continia Document Capture)
Read permissions for the table CDC AI Record Tree Relation have now been added to the permission set CDC ALL.
55245
General ApplicationThe following change only applies to Business Central online:

When users were exported to the Continia Web Approval Portal, a wrong web service URL was exported. This resulted in users encountering the following error when attempting to sign in to the Web Approval Portal:
  • Client found response content type of '', but expected 'text/xml'. The request failed with an empty response.
55428

Document Capture 2024 R1

Release date, online: April 2, 2024
Release date, on-premises: April 12, 2024
App version: 24.0.0
FOB version: 24.00

Note

With its 2024 spring release, Document Capture made a version leap from 12.00 to 24.00, meaning that versions 13.00–23.00 don't exist and never will. This was done in order to align the versioning of Document Capture with that of Microsoft Dynamics 365 Business Central.

New or changed functionality

Functional areaDescriptionID
Country and RegionalThe SAF-T data model includes reference to the voucher but not the voucher itself. The SAF-T audit file, which can be exported as a Business Central standard feature, will therefore cover the required information, as Document Capture builds on top of the Business Central standard bookkeeping features.

For more information about the SAF-T audit file in Business Central, please see the article below. https://learn.microsoft.com/en-us/dynamics365/business-central/localfunctionality/denmark/how-to-use-saft-audit-files-export?source=recommendations
50464
Documents and TemplatesThe Code field has been added as a non-editable field to the Template Field Card page. Select Show more to view the field.
47529
Documents and TemplatesThe below configurable message can now be configured as type Information:
  • The XML Document contains [discounts and charges] elements that are not created as Fields for this Template. Please use Add Template Field to add them.
In previous versions, it was only possible to configure the message type as Warning and Error.
47538
Documents and TemplatesTo simplify configuration, a Customizable Columns section for the custom searchable and sortable template header fields in the Document Journal's document list has been added to the Document Category card.
49668
Documents and TemplatesThe following improvements have been made in regards to the secure archive functionality:
  • Document Capture documents registered to a general ledger or purchase journal are now included in the secure archive.
  • Attachments (drag-and-drop) added through a general ledger or purchase journal are now included in the secure archive
  • An action to access the Document Log Summary is available on the Find Entries page.
49684
Documents and TemplatesA new field, Vendor Bank Account No., has been added to the Purchase category XML master templates. The field property Insert new on Template is set to False by default.

The Is Valid codeunit applied to the field checks that the captured bank account exists for the vendor. The template field validates the recognized value against the Bank Branch Code and Bank Account No. fields on the Vendor Bank Account Card. If the recognized bank account is does not exists on the vendor's bank list, an error comment is created. The function validates digits only (all other characters are ignored).

A new field, Vendor Phone No., has been added to the Purchase category XML master templates. The field property Insert new on Template is set to False by default.

The Is Valid codeunit applied to the field checks that the captured phone number exists for the vendor. The template field validates the recognized value against the Phone No. field on the vendor. If the recognized phone number does not exist or is different on the vendor, an error comment is created. The function validates digits only (all other characters are ignored).
49785
Documents and TemplatesPossibility to specify an Amount Distribution Code in the document line on the Document Card has been added. Translations can be added by using Translate To Type and Translate to No. fields in the document lines or the translations actions No. and Description in the lines section.49822
Documents and TemplatesThe actions Hide OK Lines and Show All Lines have been added to the Lines section on the Document Card. Toggling this will either hide lines that are marked as OK or show all captured lines. 50100
Documents and TemplatesThe Send Email To field has been added to the Document Sharing page. The following options are available:
  • Only Owner User
  • Only Shared To User
  • Both Users
This will add flexibility when sharing assigned documents by allowing you to specify which user receives the email notification. 
50281
Documents and TemplatesA new field, Vendor Phone No., has been added to the Purchase and Purchase Order category PDF master templates. The field property Required is set to False by default.

The Is Valid codeunit applied to the field checks that the captured phone number exists for the vendor. The template field validates the recognized value against the Phone No. field on the vendor. If the recognized phone number does not exist or is different on the vendor, an error comment is created. The function validates digits only (all other characters are ignored).
50468
Documents and TemplatesThe line recognition feature has been significantly improved with the introduction of the following features:
  • Support for the capture of document lines spanning multiple rows
  • Relative line capture including the ability to capture field captions at line level
  • Ability to capture only the part of the line field data that matches a specific rule
It is now possible to add or remove line fields without having to close and reopen the Document Card page.

In addition, the following features have been introduced and made available to customers using the OCR engine with AI recognition capabilities:
  • Ability to combine AI with manual capture
  • AI-based line recognition assistant notifying you about potential improvements
All customers will be migrated to the OCR engine with AI recognition capabilities gradually over the next three months. If you want to use the feature immediately, please reach out to the Continia support team.

For more information, see Enhanced Line Recognition.
50506
Documents and TemplatesThe following change only applies to Microsoft Dynamics 365 Business Central 2024 release wave 1 (BC v24) and newer versions.

With the release of Business Central 2024 R1, the captions of the standard fields Job No. and Job Task No. have been changed to Project No. and Project Task No. Therefore, the Document Capture template header field Job No. has been renamed to Project No.

When you upgrade to Document Capture 2024 R1 on Business Central 2024 R1, the template field is automatically renamed.
53978
Document ApprovalWhen rejecting a document shared with you by another colleague, the approval comment now includes the phrase "on behalf of" to clarify the context of the rejection. The comment will appear as follows:
  • Rejected by [ApproverID] on behalf of [Original ApproverID].
24436
Document ApprovalIn previous versions, the use of approval sharing could result in the scenario where a given approver would need to approve a document multiple time - one for each user who shared their approval requests and possibly the approvers own approval request.

The approval system now looks ahead to the next approval request in the approval sequence. If that approval request can be approved by the current approver the system will automatically approve that request as well.
  • The functionality is enabled for all supported purchase document types (invoice, credit memo, order and return order).
  • The feature is supported when using Continia Standard Approval and Approval Flow Codes.
  • Only approval request in a consecutive order in the approval sequence will be automatically approved.
  • Approval using Account and Dimensions Approval Permissions and Advanced Approval is NOT supported.
43910
Document ApprovalWhen configuring the XML template to Show Embedded PDF files as Default (instead of the styled XML view), embedded PDF files were shown only in Business Central. Now. Now, the embedded PDF files are also viewable in the Web Approval Portal.50908
General ApplicationTeaching tips have been added to the Suggest Header Field Captions page.40909
General Application
The following change only applies to Microsoft Dynamics 365 Business Central 2023 release wave 1 (BC v22) and newer versions.

Support for the data processing app QR-Bill Management for Switzerland has been added to the OCR process. The solution identifies valid QR code(s) and includes the following features:
  • Identify the vendor based on the IBAN recognized from the QR code.
  • Validate that the captured invoice amount is equal to the amount of the QR code.
  • Transfer the QR code content, when registering the document, to the respective fields in Microsoft Business Central and the Swiss QR Bill app. The following fields will be updated:
    • Swiss QR-Bill
    • Swiss QR-Bill IBAN
    • Swiss QR-Bill Bill Info
    • Swiss QR-Bill Unstr. Message
    • Swiss QR-Bill Amount
    • Swiss QR-Bill Currency
    • Payment Reference in the Purchase Header
41261
General ApplicationThe right and left arrow keys can be used to move the cursor between the Field and Value columns in the Document Header section on the Document Journal and Document Card pages.
42484
General ApplicationA new Retention Period (Years) field has been added to the Document Capture Setup page, to be used with the newly introduced Run Data Maintenance action on the Document Capture Setup page. This action deletes all OCR values in the Document Word, Document Value, and three AI data tables for documents older than the retention period (closed fiscal years) specified in the Document Capture setup.

Warning: Deleting historical OCR words and values will compromise the completeness of the Document Search function for documents exceeding the retention period. However, this will significantly enhance search speed for more recent documents. Furthermore, field recognition on documents may become faster, particularly for databases with extensive historical data. For further details, refer to the Continia Docs article.
45845
General ApplicationThe following change only applies to Microsoft Dynamics 365 Business Central 2024 release wave 1 (BC v24) and newer versions.

Multi-Entry Management from Binary Stream is now supported in Document Capture. When registering a document in the Document Journal with an Entity Dimension defined in the MEM Multi-Entity Management Setup page and configured as a template field, the field's value will be automatically populated in the purchase or sales documents. This eliminates the need for users to specify the entity dimension in a MEM dialog, simplifying the document registration process.

Due to the limitations in the Binary Stream Multi-Entry Management, registering documents in the Sales category does not invoke a MEM functionality when the entity dimension value is missing. To prevent registering documents in the Sales category without an entity value defined, the following non-configurable error comment is shown:
  • Multi Entity Company is missing.
To maintain seamless integration and performance with the new feature introduced in Document Capture 2024 R1, users may need to assess and consider the removal of custom MEM extensions.
46332
General ApplicationA new GDPR Retention Period (Years) field has been added to the Document Capture Setup page, to be used with the newly introduced Run GDPR Maintenance action on the Document Capture Setup page. This action deletes all data stored in Document Capture related to registered and posted documents older than the GDPR retention period (fiscal years) specified in the Document Capture setup. Additionally, the maintenance process considers the Allow Document Deletion From date on the Purchases & Payables Setup page and the Minimum Archive Period configured in the Secure Archive, if enabled. For further details, refer to the Continia Docs article.48611
General ApplicationThe column User ID has been removed from the Document Log Entries and System Log Entries pages. The change has been made to comply with GDPR legislation in certain countries, such as Germany. To adhere to bookkeeping legislation in other countries, like Denmark, the value remains accessible via Page Inspection (zoom). A user with sufficient permissions is still able to inspect the user ID by using the Page Inspection (zoom).49661
General ApplicationThis version introduces the Document Control Log which makes it easier to do a proactive follow-up on documents having one or more failed Secure Archive checks. The list is populated from a batch job that can be either executed or scheduled in the current user session.

The Document Control Log offers easy access to a number of related information through direct access to Find Entries and the Document Log Summary for further examination of the document.
49767
General ApplicationA link to the Document Log has been added to the Document Journal page. 50367
General ApplicationWith the introduction of Enforced Digital Vouchers in BC23.2, attaching documentation as incoming documents, prior to posting purchase document and journals, will in certain localizations become mandatory.

When using Document Capture in an environment where Enforced Digital Vouchers is configured to check for attached files prior to posting, Document Capture will automatically create a digital voucher when a document in registered as a purchase document or a journal entry. The primary document (OCR processed) and any drag and drop attachments, will automatically be added to a digital voucher associated with the purchase document or journal entry.

When using purchase allocations (part of the approval functionality available with Document Capture) the system can be configured to include the digital voucher, associated with the purchase document pending approval, in the G/L posting. Associating digital vouchers to purchase allocations is optional, regardless of localization and BC version.

How to enable the feature:
  • All versions prior to BC23.2: The feature can be enabled in Document Capture Setup,
  • BC23.2 and newer: The feature will be automatically enabled if Digital Voucher Setup and Digital Voucher Entry Setup is configured to check for attachments prior to posting.
  • Specifically for Denmark: When using BC23.2 or newer, and the environment is a production environment in Cloud, the digital voucher functionality is forcedly enabled from July 1st 2024. Consequentially Document Capture will automatically create digital vouchers from that date and onwards.
50510
General ApplicationPossibility to drag-and-drop attachments to the general and purchase journal lines has been added. Files can be attached using the action Attachments available in general and purchase journals.
50913
General ApplicationPreviously, the only supported migration path from on-premises to Business Central Online was from BC15.

Migrating directly from BC14 to BC24 in a single step is now supported.
51069
General ApplicationWhen sending a purchase approval status email to the approval users and the mail delivery fails, the error message shown now includes the email address of the failed recipient.52062
General ApplicationEnabling the option Check for attachment before posting of purchase document in the Document Capture Setup page specifies if the system should display an error message if no incoming document or Document Capture file is associated with the document at the time of posting. The check is imposed both on purchase documents and purchase journals.

The option only applies to on-premises environments and Business Central versions 23.1 and earlier.
52815
General ApplicationThe internal version of Document Capture 2024 R1 has been updated to 24 (the internal version of Document Capture 2023 R2 was 12). The change aims to align the Continia solution versions with those of Business Central, simplifying for Continia partners which versions of the solutions are compatible. The synchronization is particularly crucial for the Continia Core and Continia Delivery Network extensions.53678
General ApplicationNow the user export will only run if any changes necessitate a new export, reducing unnecessary excessive exports when configured in the Job Queue.

If the export is run in a database where the data for export is unchanged since the last export, the following notification will be shown:
  • Nothing is exported, because no changes have been done since the last export.
53851
Platform and TechnologyWith Document Capture 2024 R1 (24.00), we have released Document Capture for Microsoft Dynamics 365 Business Central 2024 release wave 1 (BC24).

Document Capture 2024 R1 (24.00) in Business Central online will not be available for Microsoft Dynamics 365 Business Central 2023 release wave 2 (BC23). You will only be able to use Document Capture 2024 R1 (24.00) in Business Central online when you have upgraded to Microsoft Dynamics 365 Business Central 2024 release wave 1 (BC24).
32409
Platform and TechnologyWith the release of Document Capture 2024 R1 (24.00), an upgrade tool that enables direct upgrade to Document Capture 2024 R1 (24.00) from the following versions is included:
  • Document Capture 8.00
  • Document Capture 9.00
  • Document Capture 10.00
  • Document Capture 11.00
  • Document Capture 12.00
The direct upgrade tool (Direct Upgrade to Document Capture 24.00 & Expense Management 24.00 - FOB) is available for download from the Continia PartnerZone.

For details, please see Upgrading to Continia Document Capture 2024 R1 (13.00) for FOB versions.
41925
Platform and TechnologyContinia has established a new data center in Australia – AU East. For more information, see Data Centers.

Note

This note was added later, on April 25, 2024, as it was unintentionally left out of the changelog when Document Capture 2024 R1 (DC24.00) was released.

52861
Platform and TechnologyThe Continia Web Approval Portal has been updated to version 24.0.054033
Platform and TechnologyWith the release of Document Capture 2024 R1 (24.00), support is provided for the following versions (BC v14 and the three latest versions of Business Central):
  • Business Central April 2019 (BC v14)
  • Business Central 2023 release wave 1 (BC v22)
  • Business Central 2023 release wave 2 (BC v23)
  • Business Central 2024 release wave 1 (BC v24)
54579
Purchase ContractsWhen registering a document (invoice) based on a purchase contract, it is possible to define if a comment purchase line with a posting description should be created. To manage this, the following three new fields have been added to the Purchase Contract Card page:
  • Create Posting Description Line: A boolean field that specifies whether a second comment purchase line will be created. The extra comment line is placed under the general comment line that contains the contract number.
  • Posting Description: An option field that specifies whether the purchase line description will be populated from the recognized document's posting description. The available options are:
    • No (default value): A purchase line with the invoice posting description will not be created.
    • Yes - If Present: A purchase line will be created with the posting description from the invoice if the description field contains a value. If the posting description value is blank, the Purchase Contract Description field's logic is considered.
    • Yes: A purchase line will be created with the posting description from the invoice if the description field contains a value.
  • Purchase Contract Description: A boolean field that specifies whether the purchase line description will be populated from the purchase contract description:
    • False: A purchase line with the purchase contract description will not be created.
    • True: A purchase line will be created with the purchase contract description if Posting Description is set to No or Yes - If Present and the invoice posting description contains no value.
45255
Purchase ContractsA new field, End Date, has been added to the Purchase Contract Lines.  This field is used to verify relations to a purchase contract line in multiple scenarios, when updating start and end date fields. If there are already posted invoices, which are linked to the purchase contract line and latest posting date is not within the contract line start and end dates, one of the following errors is shown:
  • The End Date can't be earlier than latest related invoice's posting date (<Posting Date>).
  • The Start Date can't be greater than latest related invoice's posting date (<Posting Date>).
When updating Invoice Date on the Document, which has a linked purchase contract, the system checks if the selected date is within the active contract line start and end dates. If not, one of the following document error comments is displayed:
  • The Invoice Date can't be before the Purchase Contract Line <Line No.> Start Date (<Start Date>).
  • The Invoice Date can't be after the Purchase Contract Line <Line No.> End Date (<End Date>).
45569
Purchase ContractsThe following feature is only available for the US localization of Document Capture.

Added support for defining tax differences on the purchase contract lines using the Purchase Contract Statistics page. To view and adjust the taxes breakdown for the purchase contract, the action Statistics is added to the Purchase Contract card.
46116
Purchase ContractsMultiple invoices related to the same purchase contract and within the purchase contract's invoicing period are not auto-approved.
47823
Purchase ContractsThe Continia Web Approval Portal has been extended to support the selection of purchase contracts for purchase invoices. The below three fields are added to Invoice Lines section in the Web Approval Portal enabling the approvers to select/change the associated contract number and contract line:
  • Purchase Contract No.
  • Purchase Contract Line No.
  • Purchase Contract Line Amount
48956
Purchase ContractsField Purch. Contracts Administrator in the Continia User Setup has been set to Obsolete = Pending. To replace the setup field, a new permission set CDC-PC-ADMIN has been created. Therefore, all Purchase Contracts administrators must be manually assigned this permission set after the upgrade.

The following fields on the Purchase Contracts List and Purchase Contract Card are now only visible to users who are assigned the CDC-PC-ADMIN or similar permissions:
  • Start Review
  • Return to Reviewer
  • Finish Review
  • Cancel Review
50886
Purchase ContractsTo ensure that the amounts on the created purchase invoice are based on the registered document instead of the purchase contract lines, a new option, Distribute Document Amount, has been added on the Purchase Contracts Setup page. With the option active, the document’s amount will be distributed across the active purchase contract lines which have the Price Type set to Variable Amount, when the document’s amount is recognized using a header template amount field

The purchase contract lines with the Price Type set to Fixed Amount are not included in the distribution process, and therefore transferred to the registered invoice with their original contract line amounts.

The configuration file has been updated for all localizations, ensuring that the Distribute Document Amount feature is automatically activated for new users of Purchase Contracts. Existing users upgrading to this version will not experience any changes in their current setup. However, by running the Document Capture Setup Guide or downloading the updated Purchase Contracts configuration file from the Purchase Contracts Setup page, the Distribute Document Amount feature will be activated.
53389
Purchase DocumentsYou can now enter a negative amount in the New Amount Excl. VAT field on the Change Document Amount page.  The error message displayed when entering a negative number in the New Amount Incl. VAT has been changed to the following:
  • Amount Incl. VAT must be zero or positive.
48535
Purchase DocumentsAdded a column showing the date and time the document was imported to the Document Log Summary page.49582
Purchase DocumentsThe possibility to handle vendor delivery notes in the Purchase Order category has been introduced. This feature builds on the existing purchase invoice matching user interface from the Purchase category, which makes it easy to navigate and utilize the functionality. With this new feature, delivery notes can be easily matched with purchase orders and posted as purchase receipts,
49672
Purchase DocumentsPreviously, the Incoming Document Files factbox was hidden if Document Capture was configured in the current company. As the incoming documents functionality is a key part of Microsoft's new Digital Vouchers feature, the factbox will not be hidden but instead showing it below the Document Viewer factbox.
51602
Purchase DocumentsWhen updating an existing purchase order in the Purchase Order category in the Document Journal, the following comment was shown:
  • WARNING: The Quantity (<Document Line Quantity>), Unit Cost(<Document Line Unit Cost>), Promised Receipt Date (<Document Line Promised Receipt Date>) on line <Document Line No.> will update the purchase order line Quantity (<Purchase Order Line Quantity>), Unit Cost(<Purchase Order Line Unit Cost>), Promised Receipt Date (<Purchase Order Line Promised Receipt Date>).
To indicate which purchase order line will be updated, the message has been improved:
  • WARNING: The Quantity (<Document Line Quantity>)), Unit Cost (<Document Line Unit Cost>), Promised Receipt Date (<Document Line Promised Receipt Date>) on line <Document Line No.> will update the Quantity (<Purchase Order Line Quantity>), Unit Cost (<Purchase Order Line Unit Cost>), Promised Receipt Date (<Purchase Order Line Promised Receipt Date>) on purchase order line <Purchase Order Line No.>.
52399
Purchase DocumentsWhen both the standard attachment action and the Document Capture attachment action are visible on the same page, the caption for the Document Capture action is changed to Document Capture Attachments.52781

Bug fixes

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

Functional areaDescriptionID
Documents and TemplatesWhen you register a sales document with document lines and use item translation by No. or Description, the sales line's Unit of Measure will now be automatically filled in on the registered sales document based on the item's specified Unit of Measure, even if the Unit of Measure field is left blank in both the document line and the translation settings.
48402
Documents and TemplatesWhen having configured the Document Storage option in the Document Capture Setup page as File Service and using Cloud OCR, XML files could not be imported.52904
Documents and TemplatesWhen manually entering values in the document line fields, on the Document Card, you experienced a warning and the document viewer could become unresponsive.53959
Document ApprovalWhen trying to assign a filter with a length over 80 characters by using lookup in Assigning Filter in the approval user group permission, the following error occurred:
  • The length of the string is <String Length>, but it must be less than or equal to 80 characters. Value: <String>
48914
General ApplicationChanged the way Document Capture requests the number of files to process when opening the Document Journal. This will speed up opening Document Journal immensely when using File Service as the storage type.53801
Order & Receipt MatchingWhen conducting a purchase order/receipt match and manually unmatching everything, you could end up with an empty comment section, potentially allowing you to register the invoice unnoticed. This was only possible if the Allow Register w/o Amounts option in the template was enabled.
45238
Order & Receipt MatchingWhen a matched amount was calculated during the match process, the amounts where rounded using the rounding precision from General Ledger setup, instead of the rounding precision from the currency involved.49716
Purchase ContractsThe following feature is only available for the US localization of Document Capture.

Support for tax calculation has been added to the Purchase Contract Card. The following two new fields have been added to the purchase contract header:
  • Tax Liable
  • Tax Area Code
The following three new fields have been added to the purchase contract lines:
  • Tax Liable
  • Tax Area Code
  • Tax Group Code
32643
Purchase DocumentsIf an invoice had the same document number as a credit memo, attachments from both documents would be shown on both the documents in the drag and drop section.42973
Purchase DocumentsWhen on a Document selecting a Standard Amount Distribution Code the lookup would codes that will cause an error later in the flow. Now, only selectable Standard Amount Distribution Codes for the vendor are presented to the user on the Document List with Image page. On the Accounts for Amounts page, the lookup will return an error immediately if the user selects an unselectable Standard Amount Distribution Code. The error is the following:
  • The selected Standard Amount Distribution Code ([Code]) is unavailable for vendor no. [VendorNo] ([VendorName]).
44152
Purchase DocumentsWhen having a Purchase Order with attachments, the drop-down was not visible.

The following changes have been made regarding the availability of the Document Viewer on the Purchase Order Card:
  • When registering a Purchase Order in the Purchase Order category and adding attachments to this, the dropdown menu contains the original Purchase Order and the Attachment category after. 
  • If the Purchase Order is created manually and a Purchase Invoice registered using the register option Match and Update Order, the dropdown will contain the Attachment category populated with the document files from all related invoices. 
  • If the Purchase Order is created manually, and all attachments are done using Drag and Drop, then the Document Viewer is not visible. 
51495