Categories and rules

The model underneath everything: categories, kinds, rules, rank, and how a transaction gets its category.

Two things decide what any transaction is: rules, which describe a pattern and the category it means, and overrides, which set the category on one transaction and nothing else. Everything on every other screen is downstream of those.

Categories

A category is a name and a kind — one of Spend, Income, Transfer, or Saving.

The kind is not decoration. Moving $2,000 to your own brokerage is not an expense, and neither is paying your credit card from your checking account, but both are transactions with large amounts on them. Kind is how the app knows to leave them out of a spending total. It's why the category rail starts with Spend and Income checked and Transfer and Saving unchecked, and why the spending chart doesn't count a transfer as money gone.

You get 24 categories when your workspace is created. Add, rename, and delete them from the Categories screen.

  • Renaming a category carries every rule that assigns it, and every transaction that was overridden to it, along with the new name.
  • Deleting one is refused while rules or overrides still point at it, unless you name a category to move them to. That's a prompt, not a wall: the dialog asks where they should go.

Rules

A rule says: transactions that look like this belong in that category. It has:

  • A pattern, and what to match it against — see below.
  • A pattern to exclude (optional), so a broad rule can carve out an exception.
  • A source (optional) — restrict the rule to one bank or card. Leave it as Any unless you mean it; a rule scoped to one card stops matching the same merchant on another.
  • A debit range and a credit range (optional) — match on amount.
  • A rank — which rule wins when several apply. See Rank.
  • Tags (optional) — free-form labels applied alongside the category.

At least one of pattern, source, or amount range is required. A rule with only a category and a rank would match every transaction you own, so it's rejected.

Description or merchant

Every rule matches its pattern against one of two things, and the choice matters more than anything else in the form.

Description tests the raw text the bank wrote, exactly as it appears in the statement — SQ *BLUE BOTTLE COFFEE #4471 SEATTLE WA.

Merchant tests the canonical merchant key instead: the same descriptor with the payment processor prefix, store numbers, reference blobs, card masks, and the trailing city and state removed, leaving BLUE BOTTLE COFFEE. Every charge from one merchant collapses onto one key regardless of which location, which processor, or which order number rode along.

Merchant is almost always what you want. A description rule for BLUE BOTTLE COFFEE #4471 SEATTLE matches one store; the merchant rule matches the merchant. When you open the rule editor from a transaction, the editor shows you that transaction's merchant key and offers a Match this merchant button that fills it in for you.

Patterns are regular expressions, matched case-insensitively, and they match anywhere in the text — AMAZON matches AMAZON MKTP US. Use | for alternatives (AMZN MKTP|AMAZON\.COM) and escape the characters that mean something to a regex, particularly . and *.

Rank

Rank breaks ties. Lower wins — a rank-50 rule beats a rank-100 rule. New rules default to 100, which is the baseline everything else sits at, so most of the time you don't touch it.

Use a lower rank to say "this one takes priority regardless of anything else" — a rule that pulls a specific subscription out of a broad Shopping rule, say. Use it sparingly: rank is a blunt instrument, and the resolution rules below already handle the common overlaps without it.

How a transaction gets its category

When rules are applied to a transaction:

  1. Every rule that matches it is collected.
  2. Of those, only the ones with the lowest rank stay in the running.
  3. The survivors are resolved:
    • One survivor — it applies.
    • Several, all naming the same category — that category applies. The transaction is attributed to the broadest of them, meaning the one with the shortest pattern. A charge covered by both MICHAELS STORES and MICHAELS STORES MORRISVILLE lands on the general rule, and isn't reported as a conflict, because there was never any disagreement about the answer.
    • Several naming different categories — the most specific one wins, meaning the longest pattern. UBER EATS beats UBER, which is the answer you'd have given.
    • Several tied at the top specificity and still disagreeing — that's a genuine conflict. No category is applied and the transaction goes to the review queue with both rules named. See Uncategorized transactions.

That last case is the only one that ever asks you a question, and it's the case where any answer the app picked would have been arbitrary.

Overrides beat rules

Setting the category directly on a transaction writes an override. An override always wins over whatever the rules concluded, and it survives rule edits, reapplies, and re-uploads of the same statement.

An override is a decision about one transaction. If the same merchant will charge you again next month, an override fixes today and nothing else; a rule fixes all of it. The category picker on a row and the rule editor sit next to each other for exactly that reason — see Reviewing rules.

Clearing an override hands the transaction back to the rules.

Edits propagate on their own

There is no "regenerate" button. Create, edit, or delete a rule and the affected transactions are re-checked in the background — the header capsule shows the progress, and the numbers on every screen settle on their own when it finishes.

Two consequences worth internalizing:

  • Editing a rule rewrites history. Change what AMAZON means and every Amazon charge you have ever loaded moves, not just the new ones. That is the point of the whole design, but it does mean a rule edit is not a small local change.
  • Deleting a rule recategorizes everything it was holding. The confirmation dialog tells you how many transactions that is before you commit.

Reapply rules, in the ⋮ menu, forces a full re-check of everything. You shouldn't normally need it — it's there for the rare case where a background pass failed and you want to be certain the whole corpus is current.