New Payhawk offices in Stockholm and Warsaw | Learn more

Workflow fallbacks and advanced controls

Prev Next

A defined workflow may depend on a role or role extension that is not available - for example, no Team Manager for a specific team or no Custom Field Manager for a specific custom field value.

In such cases, you can rely on the default workflow fallback mechanisms Payhawk provides or define your custom ones.

Fallbacks act as backup approvers when the defined approver is not available. To let other people approve in the same step, you can also assign multiple approvers to a step, and to hand over your approvals while you are away, enable the out-of-office mode.

If someone changes a field that an approval workflow uses, you can also choose what happens to the expenses pending approval.

System fallback mechanisms

If an approver or a category, team, or custom filed value has been added, removed, or updated, Payhawk will apply the below fallback mechanisms for expense requests by default.

If Payhawk cannot identify an approver for a defined workflow and no custom fallback is set, the expense request will be forwarded to all users with the built-in Payhawk Administrator role. Users with a custom role do not receive it, even if that role includes administrator permissions. To send these requests to other users, set a custom fallback that points to specific users, as described in customizing the fallback behavior.

Customizing the fallback behavior

The default mechanisms of the workflow fallbacks can be customized and set to the individual needs of your company.

To define custom fallback behavior:

  1. In the Payhawk Web Portal, go to the Settings > Workflows > Advanced tab.

  2. Click on Edit fallbacks.

  3. From the drop-down menus, define the desired fallback behavior.

  4. Click on Save changes.

Payhawk will be unable to execute fallback mechanisms when roles or role extensions are set to rely on each other in a loop, creating an endless cycle with no resolution (cyclical fallback behavior). For example, if Role A falls back to Role B, Role B falls back to Role C, and Role C falls back to Role A.

In such cases, Payhawk will send an approval request based on the defined custom role.

Payhawk Web Portal: the Fallback settings on the Advanced tab of Workflows, with a fallback selected for each trigger and the Save changes button.

Viewing the currently defined workflow fallbacks

You can view the currently defined workflow fallbacks under each step in its edit mode.

Payhawk workflow builder: the Step details panel with In all other cases expanded, showing what happens if none of the conditions are met and the fallbacks for the step.

Advanced workflow controls

If someone changes a field that an approval workflow uses, for example, the Team field, you can choose what happens to the expenses pending approval in that workflow.

The following options are available:

  • Continue - The approval carries on from the current step.

  • Return to employee - The approval stops and goes back to the employee to submit again.

  • Restart approval - The approval starts again from the first step with the new values. No one needs to resubmit the expense.

To choose an option:

  1. In the Payhawk Web Portal, go to the Settings > Workflows > Advanced tab.

  2. Under Administrative controls, click on Edit.

  3. In the panel that opens, select Continue, Return to employee, or Restart approval.

    Payhawk Web Portal: the Administrative controls panel with Return to employee selected for When a field used by the approval changes, and the Save changes button.

  4. Click on Save changes.

Useful resources