The same transactions, over and over

Once your bank feed is connected, a rhythm sets in: the same handful of vendors show up again and again. The card processor's fee every week. The software subscription on the same day each month. The fuel station, the office-supply store, the recurring transfer. Categorizing each of these by hand, every single time, is exactly the kind of repetitive work software should do for you — and that's what bank feed rules are for. (General education, not accounting advice.)

What a bank feed rule is

A bank feed rule is a small instruction that watches incoming transactions and, when one matches a condition you've set, applies a category, a vendor name, or other details automatically. A typical rule reads like a sentence: when a transaction's description contains "GoDaddy", categorize it as Software & Subscriptions and set the vendor to GoDaddy. From then on, every matching transaction arrives pre-categorized, and your job shrinks from deciding to confirming.

The conditions usually key off what the bank actually sends — the description or memo text, the amount, sometimes the transaction type. Most systems let you combine conditions, so you can be as broad or as narrow as the situation calls for.

Writing rules you can actually trust

The art of bank feed rules is making them specific enough to be safe. A rule that's too loose will grab transactions it shouldn't and quietly file them in the wrong expense category — which is worse than no rule at all, because you stop looking. A few habits keep rules trustworthy:

  • Match on distinctive text. A description fragment unique to one vendor is far safer than a common word. A broad match on a single common term can sweep up unrelated charges that belong in very different categories.
  • Add an amount condition when the figure is stable. A subscription that's always the same dollar amount each month is a strong, reliable signal — pairing the vendor text with the exact amount makes the rule nearly foolproof.
  • Keep one rule to one meaning. If a single vendor sells you things that belong in different categories, don't force one rule to guess. Either split by another condition or leave that vendor for manual review.
  • Watch for overlap. When two rules could both match the same transaction, know which one wins in your system, so a transaction doesn't land somewhere you didn't intend.

A rule speeds up review — it doesn't replace it

The most important mindset: a rule should make your bank reconciliation faster, not invisible. Automation that runs without anyone watching is how miscategorized transactions pile up unnoticed until they distort your profit & loss statement. The healthy pattern is to let rules pre-fill the categorization and then glance down the list and confirm — a quick scan that catches the odd transaction a rule got wrong while still saving you nearly all the manual effort.

Think of rules as a smart first draft of your categorization. They handle the obvious, repetitive bulk of transactions so your attention is free for the handful that genuinely need judgment — a new vendor, an unusual amount, something that doesn't fit a pattern yet.

Keeping rules current

Rules drift out of date as the business changes. A vendor you stop using leaves a dead rule. A new recurring cost deserves a new one. A category you restructured in your chart of accounts may leave rules pointing at the wrong place. It's worth a quick look at your rule list every so often — pruning what's stale and adding rules for the recurring transactions you find yourself categorizing by hand — so the automation keeps matching how the business actually spends.

Hosting Books lets you set categorization rules on your bank feed and still surfaces every transaction for a quick confirming review, so the repetitive work is automated without the categorization happening behind your back.

This article is general educational information about accounting concepts and is not accounting advice for your specific situation.