Create an approval rule
Learn more about modifying payment and bank account approval rules
Users in roles with Organization Manage and Review permissions are allowed to modify approval rules. You can configure approvals rules from the Settings page.
All rule modifications (e.g. rule creation, edit, and delete actions) are logged in the Audit Trail. If you modify a rule, only new payments and bank accounts will be affected.
TAB-Payment Orders
You can set up one or more approval rules to specify Payment Orders that require human review. For example, you can set up rules to review large outgoing payments, or payments that were created manually in the dashboard.
Rules are evaluated in parallel, and multiple rules can trigger for a payment. The system will reduce which reviewers are required. For example, if Rule 1 requires one Finance reviewer, and Rule 2 requires one Finance reviewer, we simply say that they payment requires one Finance reviewer.
A single approval rule consists of conditions and reviewers.
Conditions
Conditions describe what needs to be true for a review to be required.
You can create one or more conditions, grouped into condition blocks. Within a condition block, conditions are AND'd together. Between condition blocks, conditions are OR'd together.
Each condition is expressed as a field, operator, and value combination. Below are the conditions that can be specified for payment approvals:
| Field | Operators | Values |
|---|---|---|
| Amount | <, ≤, >, ≥, =, ≠ | Number (e.g. 1000) |
| Created By | is in any, is not in any | A list of Users |
| Creation Source | is equal to, is not equal to, is in any, is not in any | API, Counterparty invitation form, by a User manually, bulk import, sweep |
| Direction | is equal to, is not equal to, is in any, is not in any | credit, debit |
| Metadata | is equal to, is not equal to, contains, does not contain, is missing, is present | Key and value |
| Payment Type | is equal to, is not equal to, is in any, is not in any | List of payment rails (e.g. ach, wire) |
| Receiving Account Type | is equal to, is not equal to, is in any, is not in any | internal_account, external_account |
| Currency | is equal to, is not equal to, is in any, is not in any | List of currencies (e.g. usd, gbp) |
Reviewers
Reviewers describe which Roles, and therefore which Users, can take actions. You can specify one or more reviewers. For example, you can specify that you want two users from Finance to review. You can even specify conditional logic for reviewers, for example, that you want one user from Finance or Administrators to review.
TAB-External Accounts
You can set up one or more approval rules to specify External Accounts that require human review. For example, you can set up rules to review bank accounts that are created through the dashboard.
Rules are evaluated in parallel, and multiple rules can trigger for a bank account. The system will reduce which reviewers are required. For example, if Rule 1 requires one Finance reviewer, and Rule 2 requires one Finance reviewer, we simply say that they payment requires one Finance reviewer.
A single approval rule consists of conditions and reviewers.
Conditions
Conditions describe what needs to be true for a review to be required.
You can create one or more conditions. Conditions are AND'd together within a single rule.
Each condition is expressed as a field, operator, and value combination. Below are the conditions that can be specified for bank account approvals:
| Field | Operators | Values |
|---|---|---|
| Metadata | contains, does not contain | Key and value |
| Created By User | is one of, is not one of | A list of Users |
| Creation Source | is equal to, is not equal to | API, Counterparty invitation form, by a User manually, bulk import |
| Verified By | is equal to, is not equal to | Plaid |
Reviewers
Reviewers describe which Roles, and therefore which Users, can take actions. You can specify one or more reviewers.
Updated 2 months ago