You can define approval policies based on your company’s internal finance controls: from a simple one-step approval for all payables, to multi-step policies involving team-level reviews, compliance checks on wallet addresses, and treasury sign-off for high-value payments. Approval steps can be customized based on the conditions of a payable, include one more approvers and be skipped, if conditions don't apply.
Thanks to the ability to create approval policies based on tags - that is, the custom tags you can add to payables - you can create highly customized policies, tailored to what your company needs.
You can find some examples below:
Example #1: An approval policy to manage approvals for large payables:
Step | Applies when | Approvals required |
Finance Review | Unconditional (any bill) | At least 1 out of 2 |
CFO Review | Bill amount ≥ $1,000 | 1 out of 1 |
Example #2: An approval policy to manage approvals per team:
Approval steps that don’t apply are skipped automatically. For example, the Marketing approver won’t review bills without the "Marketing" tag.
Step | Applies when | Approvals required |
Finance Review* | Unconditional (any bill) | At least 1 out of 2 |
Marketing Review | Bill has tag "Marketing" | 1 out of 1 |
Sales Review | Bill has tag "Sales" | 1 out of 1 |
Tech Review | Bill has tag "Tech" | 1 out of 1 |
CFO Review | Bill amount ≥ $1,000 | 1 out of 1 |
*If you have tag-based approval steps in your policy, make sure to add an unconditional step where your team can allocate the right tag to the payable. Otherwise, the payable is automatically approved as no tag was found (→ What happens if an approval policy does not apply?).