Authorization flow improvement - Support for several responsibles per entity
Business case:
Line-level 4EP enabled.
Case 1
Customer would like to require suppliers to state Cost Center on the invoices, and use this for initial distribution (or fetch authorizer if invoice is in Distribute). They also want CC managers to be setup as 2nd approvers. This is not possible in current solution.
Case 2
Customer have a cost-center based organization, meaning that approval flows should be based on responsible related to a Cost center.
i.e. a Cost center could have both first, second and third approvers, where the second and third could be responsible for several CCs.
There is currently no support for this in MediusFlow. Instead it's elaborated with setting supervisor as 3rd approver, which both increases maintenance (when 3rd approver is connected to a user instead of the CC itself) and might cause issues when delegating (temporary delegation).
Case 3
When supervisor is setup as next approver, and the invoice is delegated to the supervisor, routing could be made more efficient with the possibility to state a "2nd" or "optional" supervisor.
Case 4
Company or supplier responsible might be configured for orderbased workflow purposes. In order to setup other persons/roles for the expense workflow, additional responsible fields would be required.
By additional fields for responsible users - on both Dimension values, User, Company, Supplier (and possibly other entities) - and corresponding fields in BRs, distribution can be better optimized and easier to maintain.
Current behavior:
Limited configuration possibilities, as described above.
Expected behavior:
Extended configuration possibilities, as described above.
Anne Sophie Kuss
shared this idea
-
Jan Lindholm
commented
Our company has also a need to have several supervisors/approvers. We cannot use only one supervisor per attestant because the responsibility to approve the invoices is distributed on several persons.
-
Anne Sophie Kuss
commented
Support for several responsibles per entity
Business case:
Line-level 4EP enabled.Case 1
Customer would like to require suppliers to state Cost Center on the invoices, and use this for initial distribution (or fetch authorizer if invoice is in Distribute). They also want CC managers to be setup as 2nd approvers. This is not possible in current solution.Case 2
Customer have a cost-center based organization, meaning that approval flows should be based on responsible related to a Cost center.
i.e. a Cost center could have both first, second and third approvers, where the second and third could be responsible for several CCs.
There is currently no support for this in MediusFlow. Instead it's elaborated with setting supervisor as 3rd approver, which both increases maintenance (when 3rd approver is connected to a user instead of the CC itself) and might cause issues when delegating (temporary delegation).Case 3
When supervisor is setup as next approver, and the invoice is delegated to the supervisor, routing could be made more efficient with the possibility to state a "2nd" or "optional" supervisor.Case 4
Company or supplier responsible might be configured for orderbased workflow purposes. In order to setup other persons/roles for the expense workflow, additional responsible fields would be required.
By additional fields for responsible users - on both Dimension values, User, Company, Supplier (and possibly other entities) - and corresponding fields in BRs, distribution can be better optimized and easier to maintain.
Current behavior:
Limited configuration possibilities, as described above.
Expected behavior:
Extended configuration possibilities, as described above.