Skip to content

Rules and the review queue

Categorise routine transactions automatically, and route only the ones that need a human.

Last updated October 23, 2026

Most imported lines are routine. Rules book those straight to an account, and anything a rule can't place waits for you instead of landing in the wrong category.

Rules

A rule matches the description of an imported transaction and routes it to an account.

  • Match string — the text to look for in the description.
  • Match type — how strictly to compare.
  • Target account — where matching transactions are booked.
  • Priority — rules evaluate top to bottom; the first match wins.

Create one with ⌥⌘R from anywhere, or ⌘N in the Rules section. Reorder with ⌥⌘↑ / ⌥⌘↓; delete with ⌘⌫ (⌘Z to undo). A rule applies on your next import — it doesn't rewrite transactions you've already reviewed.

The review queue

Lines a rule doesn't cover are parked and shown in the Import section's routing queue, where you assign each one:

  • Assign books a line against any active ledger account.
  • Point it at an Expense or Income account and it reads as a normal categorised line; point it at an Asset, Liability, or Equity account and it reads as a transfer.
  • Dismiss drops a line without booking it (for example, a payment that shouldn't count as spending); dismissed lines stay restorable.
  • New account inside the composer creates a category on the spot.

Budget views flag parked items as unreviewed — not counted in the actuals, so a quietly growing queue is visible where it matters. See Budgets.

Transfer matching

Money moving between two of your own accounts shouldn't be counted as spending. Chord matches a money-out (a bank payment) against a money-in (a card payment received) of equal amount near in date and nets them into a single transfer, resolving both halves.

Matching runs during import. Cross-currency transfers (CAD ↔ USD) are supported and post an FX adjustment so the books stay balanced. See CAD and USD exchange rates.

Related

Still stuck?

Email [email protected] with your macOS version and what you were doing.