Overview:

Customers may notice that in the Process Discovery dashboard, the dimension “Invoices handled by task recipient” now shows “Other” instead of individual usernames in the following sections:

1. Receiving:

 

2. Matching:

 

At the same time, usernames are still visible in workflow section:

 

3. Workflow:

 

This behavior is expected and is the result of a logic update introduced in April’2026 to improve data accuracy.

 

Summary of Changes (Logic Update):

The Process Discovery dashboard now relies strictly on task‑level recipient data when displaying Invoices handled by task recipient.

Previously, some usernames could appear based on inferred actions, even when no task was formally assigned to a user. This could lead to misleading attribution.

Now what does it means:

In earlier versions, the system sometimes displayed usernames based on actions performed in the process, even if the task was not officially assigned to any user, which sometimes caused incorrect user attribution.

After the update:

• Only tasks with an explicitly assigned recipient show a username.
• Tasks without a recipient are grouped and shown as “Other”.

Benefit of this change:

• This change ensures that user information in the dashboard will now be more accurate and consistent.
• It will be easier to clearly identify which user actually handled a task.

Phase‑specific behavior explained:

1. Receiving phase

• Receiving activities are often system‑driven or background actions.
• These tasks do not usually have a user assigned as a recipient.
• As a result, invoices are shown under “Other”.

This is expected behavior.

2. Matching phase

While manual matching actions exist, not all matching activities create a task with a recipient.

Common reasons:

• Some user actions are logged at the invoice or line level, not as a user‑assigned task.
• Automated or background matching steps do not have a task owner.

Because the dashboard now shows only task recipients, invoices where matching tasks have no assigned recipient are displayed as “Other”.

This does not mean manual matching disappeared. The data is still included, but grouped correctly.

3. Workflow phase

Workflow tasks (e.g. review, approval):

• Always have explicit assignees.
• Therefore, usernames continue to appear correctly.

This difference is by design.

Why were usernames visible earlier?

In earlier versions:

• User information could appear due to action‑based inference.
• Names could be shown even when no task recipient existed.

This was not intended behavior and could result in incorrect conclusions about who actually handled an invoice.

The April’2026 update corrected this.

What does “Other” mean?

Other indicates:

• The invoice passed through a task without an assigned task recipient.
• The task was system‑handled or did not store a user assignment.

It does not mean:

• Missing data
• Lost information
• A configuration issue

Upcoming terminology improvement:

To improve clarity, “Other” will be renamed to “Unassigned” in a future update.

This is a label change only and does not affect logic or data content.