Businesses can now add flows like “If the Accounting Category is `Client Expenses`, then require Customer/Job to be filled out” to their submission policies. This also gives businesses control over the order in which fields are required (i.e. “first show X, then Y, then Z”).
How does it work?
When a user submits an expense, the workflow checks if any conditional requirements are triggered based on the information they've entered. For example, if an employee selects a specific GL account, additional fields like Customer/Job can be automatically required to be filled out.
How do I access this feature?
Navigate to Company → Expense Policy → Expense Requirements to configure your workflow.
How do I add a conditional coding to my workflow?
Note: Without setting a condition, these fields will be required for all expenses.
Common use cases and how to set them up
Use case 1: If Accounting Category is Sales, require Customer to be filled out
Note: ensure that the input of the condition is required earlier on in the workflow. In other words, ensure you require an Accounting Category at the beginning, otherwise, the employee will never select the Accounting Category and thus the Customer field will never be required.
Use case 2: If Client is filled in, require Billable
Use case 3: I want to ensure employees fill out GL Account first, Customer/Job second, and then Billable (in that order)
What will cardholders see once the workflow is set up?
Submission policy requirements will show up as soon as the condition in the workflow is met.
FAQ
Q: What if I want to require a field for all inputs that "are not" a specific value?
A: Fear not! Conditional coding in the submission policy also allows users to set values to "is not" for this case.