Skip to content

Bank rules: how automatic categorizing works and its limits

Up to date as of November 20, 2026

A bank rule is a saved instruction: if a transaction looks like this, label it that way. It saves you from categorizing the same monthly fee by hand every month.

The names differ by program. Some call them bank rules, others auto-categorization or just rules. The idea is the same. This page draws on the documentation of one open-source finance tool to show the parts. Your own software may split them differently, so read its help pages.

What a rule doesNew bank line arrivesRule tests the conditionsConditions met: action runsYou review the result
A rule tests each new line and, if the test passes, applies its action.

The parts of a rule

Triggers are the conditions. Common ones in that documentation include the description being something specific, or the amount being above a set value.1

Actions are what happens when the conditions are met. The documentation lists changing the category, tags, description or accounts as typical examples.1

A rule can only use what a bank line carries. The bank transaction manual says a line records the date, amount, description and bank reference.2 That's the raw material. If the description is vague, the rule has little to work with.

All or any

Rules often let you choose how conditions combine. In this documentation, if a rule is strict, all triggers must match for it to fire.1 If it isn't strict, any one trigger is enough.1

Pick carelessly and you get odd results. A loose rule that fires on any one word catches lines you never meant. A strict rule with too many conditions misses the lines you did.

Order matters

The documentation says rules sit in groups, and each group has rules in a specific order.1 That order decides what happens when two rules could both apply. In that tool, you can also tell a rule to stop later rules from running.

If your software works this way, the first rule to match may win. Check whether yours does, and put your most specific rules first.

Where rules get it wrong

  1. The description is too general. A rule that sorts anything containing a store's name as "office supplies" will also catch a personal purchase made at the same store.
  2. One payee, many purposes. A supplier may sell you stock one month and equipment the next. One rule can't tell them apart.
  3. Combined or split payments. The bank transaction manual lists combined payments and split vouchers among the items to review when an amount only partly matches.2 A rule that assigns the whole amount to one category will be wrong.
  4. Complex conditions. The documentation admits it does not support complicated rules, such as mixing "and" with "or" in one rule.1 Your software may have the same limit.
  5. Actions that fail. The documentation says rule actions may fail, and that failures aren't always shown on screen.1
  6. Old transactions. Applying a rule to existing transactions is possible, per the documentation.1 It can change many lines at once. Check a sample first.

Rules are not matching

A rule sorts a line into a category. It doesn't prove the line is a payment against a particular invoice. That's the job of matching. A line categorized by a rule still counts toward your reconciliation, and a wrong category can sit unnoticed because the balances still agree.

That's the main risk. Reconciling checks totals. It doesn't check that "office supplies" holds office supplies.

Habits that limit the damage

  • Start with rules for lines that never vary, such as a fixed monthly fee.
  • Keep rules narrow. Add conditions rather than broadening them.
  • Review a few auto-categorized lines now and then, especially after adding a rule.
  • Don't edit the bank's description to make a rule fire. The manual says not to overwrite it merely to make matching easier.2
  • Ask your accountant which categories they need before you set rules, especially for anything that affects tax.

Whether an expense counts for tax purposes is a question for your accountant or the official tax authority, not for a rule.

Notes and sources

  1. How to use rules, Firefly III documentation
  2. Bank Transaction, ERPNext Documentation