# Configure account rules

You can configure account rules to add an approval layer for payment actions taken on your account.

By setting up approvers you can delegate authority, increase transparency, and closely monitor payment actions.

For example, you can configure an approval flow for refunds above a specified threshold. This can help to prevent refund abuse and avoid processing fees resulting from accidental refunds.

By default, users with the [Admin role](https://www.checkout.com/docs/business-operations/use-the-dashboard/manage-users/user-permissions.md#Pre-defined_roles) can view, create, and manage account rules. Alternatively, you can create a [custom role](https://www.checkout.com/docs/business-operations/use-the-dashboard/manage-users/user-permissions.md#Custom_roles) with the following permissions:

- _View the list of rules_
- _Create, edit, or delete rules_

Before you create an account rule, at least one user on the account must have permission to act as an approver.

---

## Create a custom approver role for refunds

> **Information**
>
> A user cannot have multiple roles assigned. If you need to add approval permissions to a user with a pre-defined role, you must create a custom role for them instead.

You must be an account admin to create, edit, or delete custom roles.

1. Sign in to the [Dashboard](https://dashboard.checkout.com).
2. Select the _Settings menu_ in the top navigation bar, and then select _Settings_.
3. Under _Team settings_, select _Roles and permissions_.
4. In the _Popular roles_ section, select _View all roles_.
5. Select _New role_.
6. Enter a name for the custom role. For example, Refund Approver.
7. Enter a description for the custom role.
8. Select _Payments > Permissions_ to display payment-related permissions.
9. Select the `View, approve or reject pending refund requests triggered by account rules` permission, and any other permissions the user requires.
10. Select _Create custom role_ to save the new role.

To assign the role to a user:

1. Sign in to the [Dashboard](https://dashboard.checkout.com).
2. Select the _Settings menu_ in the top navigation bar, and then select _Settings_.
3. Under _Team settings_, select _Roles and permissions_.
4. Select a user.
5. Use the _Role_ drop-down in the details window to update the user's role.
6. Select the legal entities and entity segments you want the user to have access to. The approver must have access to the entity the account rule is being added to.
7. Select _Save_.

---

## Create an account rule

1. Sign in to the [Dashboard](https://dashboard.checkout.com).
2. Select the _Settings menu_ in the top navigation bar, and then select _Settings_.
3. Under _Business settings_, select _Account rules_.
4. Select _Create rule_.
5. Select the _Type_ of rule to create. For example, _Refund_.
6. Enter a name for the rule.
7. Select the entities the rule will apply to.
8. Configure the triggers for the approval request.
9. For _Refund_ type rules, enter an _Amount threshold_ and a currency. An approval request will be triggered if a user attempts to action a refund equal to or above the threshold.
10. To add more threshold triggers, select _Add another threshold_. For example, if you need a threshold in a different currency.
11. Select _Create rule_.

Once created, users with the required permissions will be able to view or manage existing rules from the _Account rules_ page under _Settings menu_ > _Settings_.

---

## Respond to a request

When a user performs an action that requires approval, users with the custom approver role for that entity will receive an email. For example, if a user attempts to perform a refund equal to or above a threshold specified in an account rule.

The email will direct the approver to approve or reject the action in the Dashboard, and provide a reason for their decision.

The user who initiated the action will be notified of the approver's decision on the Dashboard.

Approval requests expire after one week. If the request expires, the user who initiated the action will have to perform the action again to request a new review.

> **Information**
>
> A user cannot approve an action that they initiated, even if they're configured as an approver.