In the Payhawk Web Portal, Payhawk Administrators can now control the fields and values visibility for both expense types and request types in Settings > Fields library.
Payhawk Administrators can add only specific fields and their values with individual expense or request types with individual settings for required for submit and/or required for review. In addition, fields can now be set up to appear in an expense based on another drop-down field’s input.
Previously, Payhawk Administrators had to configure the expense fields for all expense and request types in Settings > Expense fields, without being able to configure individually the values that are visible depending on the expense type and without being able to define if the field is required when submitting or reviewing the expense based on the type of the expense.
Fields settings used to display a field based on the selected category which is now extended to a wider field selection such as custom fields.
What is changing?
Payhawk still keeps the fields concept and builds on top of the previously available features by adding conditional settings. This enhancement provides Payhawk Administrators with a centralized space to manage and configure fields and values visibility.
The new options are available in the centralized Fields library, previously Expense fields.
Payhawk introduces new visibility functionalities, including settings of values based on user’s team and role, or based on the expense or request type users are submitting.
Payhawk also changes existing functionalities in the system regarding how and where to manage the settings of fields and values.
For example, fields, including their workflows and settings, are now configured per expense and request type, rather than centralized.
In a nutshell, Payhawk reorganizes fields management and the way it’s presented in the system and extends the visibility settings of the master data.
Custom visibility of fields
Fields can be shown for one expense or request type, and be hidden for another expense or request type. For example, the field Business reason can be included in the expense type Reimbursement, and not be included in the expense type Bill.
Fields can also have different settings across different expense types. For example, if an expense has been made in a particular city, you can enable the field Location to be visible for the expense types Bill and Card payment, but not for Per diem, Mileage, and Reimbursement.
What is more, the field Location can have different settings between the two expense types Bill and Card payment, for example, the field can be required for submit and review for bills, but not for card payments.