> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dualentry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Bank Match Rules with Accounting Intelligence

> Describe a bank-match rule to Accounting Intelligence in plain language and approve its preview, instead of building the rule field by field in the Rules view.

Instead of filling in the Rules view field by field, you can describe the rule you want to Accounting Intelligence in plain language. It drafts the rule and shows you a preview before saving anything: the same describe-then-preview-then-commit pattern Accounting Intelligence uses for [drafting journal entries](../../../ai-automation/ai-accounting-copilot#drafting-journal-entries).

## Prerequisites

* A DualEntry role with permission to create Bank Match rules. Admin, Controller, and Accountant have this permission by default, but it's configurable, so check with your Admin if you're not sure.
* The GL account, vendor, customer, or category you want the rule to assign to already exists.

## Open the Copilot

Press **Option+Cmd+]** (Mac) or **Alt+Ctrl+]** (Windows), or select the Copilot button in the top bar. See [How the AI Accounting Copilot Works](../../../ai-automation/ai-accounting-copilot#opening-the-copilot) for all entry points: any of them reaches the same assistant.

## Describe the rule

Tell Accounting Intelligence what you want to match and where it should go. If you leave out details, it asks for them; when prompted, it looks for:

* **Conditions:** description or merchant text, amount or amount range, or check/reference number, optionally scoped to specific bank accounts.
* **Action:** which account, vendor/customer, category, or transaction type to assign.
* **Optional details:** a rule name, and whether it applies to deposits, withdrawals, or both.

For example:

> Create a rule that matches any bank transaction with "PAYROLL" in the description to my Payroll Clearing account. Apply it to withdrawals only. Name it "Payroll clearing sweep."

Or, to target a specific account and override a default classification:

> Create a rule that matches bank transactions from Chase 8189 containing "CHASE CARD" to Direct Expense, not vendor prepayment. Apply to withdrawals only.

## Review the preview and approve

Accounting Intelligence previews the rule before saving it. Check that the conditions and action match what you described, then approve to commit it. If the preview isn't right, describe the correction rather than trying to edit the preview directly. The approved rule appears in your rule list the same way as one created directly in the Rules view: it runs before Bank Match AI and follows the same [criteria and matching behavior](./how-to-create-a-rule).

## What's next

* [How to Create a Bank Match Rule](./how-to-create-a-rule) covers the same rule fields if you'd rather build one directly in the Rules view.
* [Common Errors with Bank Match](./common-errors) if the rule Accounting Intelligence creates doesn't behave the way you expected.