Setting workflows for requests and purchase orders

Prev Next

For each request type, you can define roles or specific employees who can review, approve, and close requests and purchase orders (if enabled for your company). You can also define that an approval step in the lifecycle is not relevant or needed for the company, for example, the review one.

The configured request type approval workflows can be flexible and based on the hierarchy levels at your company (for example, Second level manager), specific people (for example, budget owners of cost centers and defined managers of expense categories), or Payhawk roles (Payhawk accountants and Payhawk administrators).

Once a request type has been created, it will automatically be assigned an approval workflow based on its configuration. Requests and purchase orders created before the new workflow will keep the previously applied one.

You can configure an approval workflow for a request type either from the Settings > Requests > Workflow tab of the request type or from Settings > Workflows > Requests.

To update the workflow for a specific request type:

  1. From the Payhawk web portal, navigate to Settings > Requests > Types.

  2. Select the desired request type.

  3. Go to its Workflows tab and click on Edit workflow.

    Alternatively, click on Go to workflows and you'll be redirected to the Settings > Workflows > Requests screen.

  4. Create an approval workflow that suits your requirements by following the steps for defining custom workflows and noting the following specifics that are valid for request types:

    • The Submit step is always visible.

    • The Review and Approve steps are optional for you to define. If any or both steps are irrelevant to your internal processes, you may skip them.

    • The Create purchase order step will be visible if purchase orders have been enabled for your company's Payhawk account.

    • The Receive step can be added, removed, and configured for the specific approval workflow.

      Workflow diagram showing payment methods and receipt categories for hardware requests.

    • The Invoice step is always visible unless the payment is set to card only.

    • The Pay step allows you to configure the available payment methods for a specific request type. You can choose to enable payment options, allowing employees to pay for their submitted request by card, by bank transfer, or select No payment needed.

      • If you enable the Bill option:  

        • Employees will be allowed to select bank transfer as the payment method for submitted requests of this type.

        • The approval workflow for the Bill expense type will be updated accordingly to support the following approval scenarios: No request, Matched request, or Request with discrepancy.

        • If an employee chooses the Bill option, the request can only be linked to a bill expense later on.

      • If you enable the Card option:  

        • Employees will be allowed to choose card payment for submitted requests of this type. If the Card option is selected, the request can only be linked to a card expense afterwards.

        • The approval workflow for the Card expense type will be updated accordingly to support the following approval scenarios: No request, Matched request, or Request with discrepancy.

        • If an employee chooses the Card option, they can choose from cards assigned to them or request a single-use card. If a single-use card is selected, it will be automatically issued in the requester’s name upon approval of the request.

      • If you enable the No payment needed option:

        • This option provides flexibility for cases where a payment is not required. The requester or reviewer can decide whether the request will be paid by card, by bank transfer, or not at all.

        • For example, a request may not need payment if the items have already been purchased or are in stock.

    • The Close step is always visible. It includes predefined rules for automatically closing requests when the auto-close option is activated and also specifies the default roles authorized to manually close requests if auto-close is not used.

      Whenever you need to set a workflow for a request lifecycle step, you can apply the steps for defining custom workflows. Alternatively, if any of the steps that can be skipped are unnecessary, you can remove them by clicking their three-dot menu and selecting Delete.

  5. Click on Publish workflow to apply all the changes you've made.

Useful resources