edoc invoice and edoc workplace Release Notes
v26.9.8 v26.5.4.1 German English
Auto Light Dark
Auto Light Dark
v26.9.8 v26.5.4.1 German English

edoc invoice and edoc workplace Build 26.9.8

This release includes many new administrative features that make it easier to manage companies and vendors, particularly when it comes to data recognition.

In addition, we have completely revamped the feature in edoc workplace for managing e-mail servers used for e-mail notifications. The Workflow settings page in the edoc invoice administration has been removed. The new e-mail server settings now include various authentication methods.

In addition, we have fixed numerous bugs.

New functions and enhancements

ID 20150: Configure alternative company (fallback) for company not automatically detected

You can now specify an alternative company server-wide instead of automatically mapping any company to the invoice. The alternative company is used to automatically map all invoices without a recognized company to this alternative company.

Potential application scenarios:

For example, if you are certain that the vast majority of all invoices belong to a specific company, you can use that company as an alternative company. It is also possible to create a sort of "catch-all" company to which all invoices without a recognized company are mapped.

Important information about the update

For existing company, the update automatically adds the first company in the MongoDB database as an alternative company. Previously, this company was also automatically mapped when the company could not be detected.

If necessary, discuss with the stakeholders involved whether the setting should be changed.


ID 20145: Extend company recognition to include the "VAT IDs (standard)" field in the "Invoice Reader (edoc)" configuration

In the Invoice Reader (edoc) configuration, you can now specify at least one VAT ID per company, which is used by default as a unique identifier for the automated recognition of a company.

ID 19127: The transactional data export for "posted_group" must transfer only the corresponding inbox when the user completes the workflow

Starting with schema version 6, the transactional data export for posted_group transfers the group (inbox) of the user who completes the task once the workflow is finished.

If a user is a member of multiple groups (inbox), only the inbox for which the task's workflow has been completed will be exported.

If the user who completes the task is not a member of any group, posted_group remains empty.


ID 19979: Set the default bank account for vendors with multiple bank accounts

You can now specify a default bank account for each vendor, which is imported from the ERP system via a master data import or configured through a technical interface. The default bank account is displayed and pre-filled in the edoc invoice capture form, but cannot be changed. If no default bank account has been defined administratively, the application behaves as usual.


ID 20132: Remove workflow settings from edoc invoice

In the edoc invoice administration under Settings > Global settings, the configuration function Workflow settings for SMTP sending function for workflow notifications has been removed. You can now find the e-mail server settings in edoc workplace. With this new feature, additional methods are available to you besides basic authentication (Basic Auth).

Existing e-mail server settings are automatically migrated to edoc workplace.


ID 20129: Configure e-mail server settings centrally in edoc workplace for all workflow definitions

You can now use edoc workplace to centrally configure the e-mail server settings of the SMTP server for e-mail notifications across all workflow definitions.


ID 20134: Support OAuth 2.0 authentication for e-mail notifications

You can now configure OAuth 2.0 authentication for your SMTP servers in edoc workplace. This new option complements existing methods, such as basic authentication, and ensures that your e-mail notifications continue to be sent securely and reliably even if your provider disables basic authentication.

As an administrator, select the E-mail – SMTP – OAuth 2.0 connection method in the SMTP settings and enter the required information. The system then uses modern, token-based methods to log in to the SMTP mail server. Existing configurations remain fully functional and can be migrated gradually as needed.


ID 20228: Support Microsoft Entra authentication for e-mail notifications

You can now configure authentication via Microsoft Entra ID for your Microsoft SMTP servers in edoc workplace. This new option complements existing methods, such as basic authentication (Basic Auth) or generic OAuth 2 authentication, and ensures that your e-mail notifications continue to be sent securely and reliably even if your provider disables basic authentication.

As an administrator, select the E-mail – SMTP – Microsoft Entra connection method in the SMTP settings and enter the required information. The system then uses modern, token-based methods to log in to the SMTP mail server. Existing configurations remain fully functional and can be migrated gradually as needed.


ID 20307: Enable faster and more stable work in edoc workplace when faced with a high volume of tasks

You can now work with large amounts of data in edoc workplace. The processing of large amounts of data has been optimized in edoc workplace. The task list and overview load more quickly, and occasional errors when editing tasks no longer occur.

Bug fixes and improvements

Critical ID 20390: It takes a very long time to display the lists of values in the line item data fields

The display of value lists in the capture form under Line item data has been optimized, particularly for fields with defined dependencies, so that you can now select existing values more quickly.


Critical ID 20389: The one-second wait before each value list search under "Line item data" is too long

The response time for searching for values in fields with a drop-down list has been improved. When you click a field with a drop-down list under Line item data in the capture form, the values now appear more quickly.


Critical ID 20535: The screen reader does not read aloud the clerk (case worker) highlighted in the suggestion list

In the dialog box for forwarding a workflow, the screen reader now reads aloud the name of the clerk selected in the suggestion list without requiring you to select the name first.

High ID 20250: The type of additional document can no longer be selected during upload

When uploading additional documents to an invoice, you can now select the specified document type again, such as correspondence.


High ID 20384: The invoice cannot be approved even though the mandatory field check was successful

If no group responsible for approving invoices has been configured for a cost center, a message indicating the affected cost center will be displayed in the invoice approval dialog.


High ID 20383: The ZUGFeRD additional document is not linked to the invoice in the ECM system

For e-invoices, the included XML document is correctly linked back to the invoice when an external document management system is integrated. The XML view can once again be accessed directly from the invoice.

The correction applies only to newly received invoices. Any additional documents that were previously saved incorrectly will remain hidden, since no data migration takes place.


High ID 20227: Correctly transfer dependencies when copying a company and selectively delete imported values

Dependencies are correctly mapped when duplicating companies and when creating a company from templates, and can be used after the data import. You can delete imported dependency values for a selected rule in the respective company without changing other values or the import configuration.


Normal ID 20382: Packing slip line items with a unit price or total of 0.00 are not imported

Packing slip line items with a unit price or a total of 0.00 are now reliably transferred to the invoice line items and purchase order line items and remain there.

Normal ID 20431: When importing an invoice, import bank information only from a uniquely defined vendor account

When entering a vendor's bank account information in the capture form, the following now applies:

  • Vendor with multiple bank account details in the master data: When importing bank account details, the system now uses the bank account detail from the master data that uniquely matches the recognized IBAN of the bank account detail in the master data.

  • Vendor with only one bank account listed in the master data: If the IBAN is missing or differs from the one on the invoice, the bank account from the master data is used.

  • Vendor with no bank account linked in the master data: No bank account is used, even if one was identified on the invoice.


Normal ID 20380: The order of packing slips and purchase order numbers changes when the drop-down list is opened

When mapping packing slips to an invoice, the packing slips in the selection list are now displayed in the same order each time the list is opened: the most recent deliveries are displayed first, and for entries with the same date, the selection list is sorted by packing slip number.

When mapping purchase order numbers to an invoice, the drop-down list is now sorted by purchase order number.


Normal ID 20368: In the "Failed jobs" section of edoc invoice, the list cannot be filtered by date

You can now filter the queue list by date again in the edoc invoice administration under Settings > Failed jobs.


Normal ID 20356: The approval of the cost center in the approval dialog is clickable even though the required field validation has not been passed

If a mandatory field check has been enabled in the edoc invoice administration, you can now only approve the cost center in the approval dialog once the mandatory field check has been successfully completed.


Normal ID 20355: Fuzzy search in the duplicate check causes a memory overflow

The duplicate check has been revised. Under certain configurations, invoices could no longer be opened if the check was set to a single field with a very short value. The field comparison in the database now operates with high precision and returns only the actual duplicates. The detection result remains unchanged.

Normal ID 20159: The "Vendor specified" required field check is passed even though no record exists in the master data

The mandatory field check now once again detects when the vendor or company listed on an invoice is missing from the master data. You can only complete the task in the respective workflow step after the correct vendor or company has been specified.


Normal ID 19488: Tooltips for entries are missing in custom line item fields

Tooltips for values in custom fields under Line item data are now displayed again, even after the page has been refreshed or reopened.

Last updated: