What is a "condition"?

In short, "Conditions" are like filters that you can apply to your policies to make sure that items are routed to the right policy based on their properties. We built them because we know that all items that need approval don't necessarily need to be approved by the same people - especially in larger businesses. For example, a payment for $10.00 of office supplies will likely not need the same attention as a supplier payment for $1,000,000.00.

Why would I use conditions?

Continuing the example above, you could create a default policy that applies to all payments (with no conditions) and another policy that applies to all payments over $1,000.00. You can then apply different approvers or approval stages to these distinct policies. The policy for larger payments might need approval from your CFO or Financial Controller, while the smaller payment may only need to be approved by a line manager (or no one at all).

Can I use multiple conditions?

You can stack multiple conditions onto a policy to make them as specific as you like. For example, you can create a policy for a group of expense codes and an upper and lower bound for expense amounts.

Our team continue to add new conditions for use. If there's something you'd like to request, please contact support!