Set Workflow Approvers Based on Global, Local, or Business Unit Currency Type

Modified on Tue, 3 Mar at 12:54 AM

For Projects you have always been able to specify a threshold value in global currency when defining workflow approvers. This is a great tool to ensure the right people approve the right things. Now you have the added flexibility to choose between using global (USD), the local (or project currency), or your Business Unit currency to set those boundaries.

Selecting a currency type will impact the Change Orders, Purchase Orders, Project Budget, Invoice, and Budget Change Order thresholds. 

If you want to make a change to the way you currently handle the workflow resource thresholds a support ticket will be the way to get started.

 

 

Example of impact:

The client has specified the use of local currency type. An approver has a budget approval limit of 200,000. A budget for a project in Germany has been submitted at 190,000 EUR (Local currency). This resource would be qualified to approve the budget as it is within the approval limit.

If on the other hand, the use of global currency had been selected, the approval would be based on the USD equivalent of 190,000 EUR ($206,185.15 USD at time of writing). In this scenario the approver would not be qualified to approve the budget since it exceeds the 200,000 approval limit in global currency.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article