Skip to content
Tutorials Center
My learning

Topics

Lesson 20 of 36 ยท Banking and Reconciliation

Bank Rules and Auto-Matching

Create QuickBooks bank rules that categorize repeat transactions automatically, understand conditions, priority and auto-add, and test your rule logic with a runnable stand-in.

Most small businesses see the same transactions every month: the software subscription, the fuel stop, the payment processor's deposit. Bank rules teach QuickBooks Online to categorize these automatically, so your review queue shrinks to the unusual items.

QuickBooks cannot run on this site. The steps describe QuickBooks Online; the TryIts are JavaScript stand-ins that mimic how a rule engine evaluates conditions. They are an aid for understanding, not the real engine.

Creating a rule

Open Transactions > Bank transactions and choose Rules (or Manage rules), then New rule. A rule has three parts.

1. Name and type. Name it so you can find it later ("Monthly hosting"). Choose whether it applies to money in or money out, and which bank accounts it covers (one or all).

2. Conditions. You describe the transactions it should catch. Each condition looks at the Description, Bank text or Amount, and compares it with a test such as Contains, Doesn't contain, Is exactly, Equals, Is greater than or Is less than. Combine several conditions with All (every condition must be true) or Any (at least one).

3. Actions. Choose what happens when the rule matches: the Transaction type (expense, transfer, deposit or check), the Category or categories (with a split by percentage or amount if you need one), the Payee, and optional tags and a memo.

The final choice is whether to Automatically add matching transactions. With auto-add off, QuickBooks only suggests the categorization in For review and you click Add. With auto-add on, the transaction goes straight to the Categorized tab.

Start with auto-add turned off. Watch the suggestions for a month. When you have never needed to correct one, turn auto-add on.

Writing good conditions

Be specific enough that the rule only catches what you intend, but not so specific that it never fires.

Goal Condition Risk
Catch every fuel purchase Description contains "SHELL" or "CHEVRON" (Any) Matches a coffee bought at the same station
One monthly subscription Description contains "HOSTCO" and Amount equals 29.00 Misses a price rise
Card processor deposits Bank text contains "PAYPROC DEP" None, but sales tax and fees may need a split

Descriptions come from the bank and often contain extra numbers and dates. Choose a stable fragment such as the merchant name rather than a full line that changes every month.

If two rules both match a transaction, QuickBooks applies the one higher in the list. Drag rules into priority order, with specific rules above general ones.

flowchart LR
    A["New bank line"] --> B{"Rule 1 matches?"}
    B -- Yes --> C["Apply rule 1"]
    B -- No --> D{"Rule 2 matches?"}
    D -- Yes --> E["Apply rule 2"]
    D -- No --> F["Stays in For review"]

Rules are tried from the top of the list; the first match wins.

QuickBooks also tries to auto-match a downloaded line to an existing transaction by comparing amount, date and payee before it shows you suggestions. That is separate from rules and needs no setup.

A stand-in rule engine

This stand-in evaluates conditions with All/Any logic and applies the first rule that matches, which is the behavior described above.

JS First matching rule wins

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notice that the second HOSTCO line (a different amount) falls through to Needs review. That is the rule doing its job: an unexpected price deserves a look.

JS Which rule would catch the most lines?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Maintaining rules

Review your rules every few months. Delete or edit rules for vendors you no longer use. A rule that categorizes everything from one big retailer as "Supplies" will quietly misfile a personal purchase. In the rule's Rules list, QuickBooks shows how many transactions each rule has handled, which helps you find dead rules.

Rules apply only to new downloads. To change history, edit the transactions themselves. If you find a mistake caused by a rule, fix the transaction and the rule at the same time, or it will repeat.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A rule has two conditions joined by All. When does it fire?

    All means every condition must be true. Any means at least one.
  2. 2. What happens with auto-add turned off?

    Without auto-add, the rule fills in the category in For review, and you confirm each transaction.
  3. 3. Two rules match the same transaction. Which one applies?

    Rules run in list order and the first match wins, so put specific rules above general ones.
  4. 4. Why prefer a merchant name fragment over a full bank description in a condition?

    A stable fragment keeps matching month after month, while a full line with a date or reference number rarely repeats.

Summary

  • A bank rule has conditions (All or Any) and actions (type, category, payee).
  • Auto-add posts matches straight to Categorized; start with it off.
  • Rules are tried in order and the first match wins.
  • Rules affect new downloads only; review and prune them regularly.

Next: Reconciling an Account