Finance | Project Operations, Human Resources, ...

Vendor invoice workflow help: The must be a first approver and a second approver - The second approver is the manager/boss to the first approver.

(0) Share

Report

Posted on by Benjamin N.

Vendor invoice workflow help: The must be a first approver and a second approver - The second approver is the manager/boss to the first approver.

Hallo Forum

I am trying to set up a Vendor invoice workflow with the following requirements:

The must be a FIRST APPROVER, and then a SECOND APPROVER. The second approver is the manager/boss to the first approver.

The first approver is the Department owner
- This is working in the workflow
The second approver is the Manager/boss to the Department owner
- This is the GAP I am facing and cant solve

The solution I am thinking about for the GAP is as followed:

Create a new approval step and add:

Assignment type
- Hierarchy
  - Managerial hierarchy
  - Emplotee.line.manager.level = value x

But the issue is what should I select in "Start from" - I dont think that workflow originator or workflow owner works here? Since it will not refer back to the department owner?

Would a solution to create a Custom hierarchy token? etc a token with the value of "Last approved by" meaning it would refer back to the last person who approved something in the workflow?

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

SouravDam 11,730 on at

Like (0)

Report

Hi Benjamin N.,

Even though you create a custom node in workflow like as you mentioned "Last approved by"; I wonder what value you will select in that node so that it can trigger to the manager of the first approver? Because the first approver could be anyone from any department.

Instead, you can set a condition like below. Depending on the number of departments, multiple such nodes can be used in standard workflow.

1st level, set for the primary approver if the department is 001.

2nd level, set for the manager of that primary approver in the same department 001.

Regards,
Sourav

Was this reply helpful? Yes No
Benjamin N. 27 on at

Like (0)

Report

The solution will have between 1-100 departments so this form of solution will not work. Since the workflow will be too big.

Regarding the Custom Node/token. My thinking was:

The first approver is set in the Financial dimension "Department" where we set a Department owner. The first approval step will use the Department on the invoice header to send it to the right department owner.

If you could make a node/token "start from" Last approved by" would the value be the department owner of the given department, becasue he was the "last approver". meaning that the hiearchy will look at him in the managerial hierachy?

So if "Start from" is "Last approved by" = Department owner. The condition Employee.line.manager.level = value 1 will look at the departments owner manager?

Was this reply helpful? Yes No